Wireless access of vacuum systems

GB2703703APending Publication Date: 2026-08-05EDWARDS LTD
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
GB · GB
Patent Type
Applications
Current Assignee / Owner
EDWARDS LTD
Filing Date
2024-12-18
Publication Date
2026-08-05

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

A communication interface for a system, comprising wireless access point (AP) 20 circuitry configured to provide wireless communication with a mobile device (MD) 10 using a communication protocol; det
Need to check novelty before this filing date? Find Prior Art

Description

FIELD OF THE INVENTION The field of the invention relates to vacuum systems and in particular, to wirelessly accessing such systems. BACKGROUND Maintenance engineers, equipped with wireless mobile devices, have a requirement to connect to vacuum systems such as vacuum pumps in order to check status, update software, download logfiles and in certain situations, exert control, e.g. stopping or starting the pump. A site containing multiple vacuum systems can be densely populated with these systems and unless an unambiguous method of wirelessly connecting to the intended vacuum system is used, then a user may unintentionally connect their mobile device to the wrong system . The importance of this becomes paramount if the user were to exert control of the vacuum system from the mobile device, potentially damaging customer products. It would be desirable to provide a way of allowing a user to connect to a vacuum system in a straightforward manner, while inhibiting the user from connecting to the wrong vacuum system. SUMMARY One aspect provides a communication interface for a vacuum system, said communication interface comprising: wireless access point circuitry configured to provide wireless peer to peer communication with a mobile device using a first communication protocol; detection circuitry configured to wirelessly detect a tag located within 10cm of said interface using a second communication protocol, said tag comprising an identifier identifying said mobile device; said wireless access point circuitry being configured to generate an identifier for identifying said wireless access point to said mobile device in response to detecting said tag, said identifier including said mobile device identifier. It was recognised that wirelessly connecting to vacuum system devices is a practical way of allowing a user to perform tasks such as checking status, updating software, downloading logfiles and in certain situations, exerting control however, such wireless access may require some restrictions. Different wireless communication protocols exist that have different properties and it was recognised that such properties could be used to provide both the desired access and some control of this access. In particular, by using a communication protocol with low coverage and that therefore requires proximity for successful operation, successful detection of devices can be limited to those adjacent to the vacuum system. The use of an identifier transmitted using this protocol could then be used to control access to a wireless access point that operates using a different wider ranging communication protocol. In this way access can be limited automatically to devices within a certain distance of the vacuum system. The tag may be located within the mobile device, or it may be a separate unit. Although the limit may be 10 cm, in some cases it is smaller at about 5cms, and in other cases could be up to 30cm. In some embodiments, said wireless access point circuitry is configured to broadcast an indication of said generated identifier. The generated identifier may not be broadcast and the mobile device may simply attempt to access a system identified by an identifier that includes the identifier of the mobile device. This inhibits other devices from detecting the identifier of the wireless access point and attempting to access it. Alternatively, the generated identifier may be broadcast, or in some cases an indication of the identifier that does not include the mobile device identifier may be broadcast, again this latter may be done to increase security. In some embodiments, said wireless access point circuitry is configured to maintain said generated identifier for a predetermined time following detection of said tag, and where no valid connection request is received within said time period to discard said generated identifier. In order to increase security the communication interface may be configured to only retain the generated identifier for a predetermined time and if no connection request is received within that time period, the generated identifier will be discarded and no longer be used by the communication interface. Where the wireless access point broadcasts an indication of the identifier, then when it is discarded this broadcast will stop. Once the identifier is discarded then any connection request including this identifier will be rejected. In some embodiments, said wireless access point circuitry is configured in response to detection of a connection request to determine whether the mobile device transmitting the request is identified by said mobile device identifier and where not, to not allow said connection request. Access to the communication interface and therefore the vacuum system may be limited to mobile devices identified by the detected identifier. In some embodiments, said wireless access point circuitry is further configured to determine whether said connection request comprises a valid password and where not to not allow said connection request. To increase security there may be a password associated with a connection request, which password may be stored on the mobile device. In some cases it may be encrypted. In some embodiments, said password is encrypted and said communication interface further comprises decryption circuitry configured to decrypt said password. ln some embodiments, said tag comprises said password, said tag detector being configured to detect said password and said mobile device identifier. In some embodiments both said mobile identifier and password on said tag are encrypted. In some embodiments, said password includes said mobile identifier. Although the first communication protocol may be a number of things, in some embodiments, said wireless access point circuitry is configured to provide wireless peer to peer communication using WiFi Direct following the IEEE802.11 standard, and said generated identifier comprises a service set identifier SSID. WiFi Direct is an efficient way of providing peer to peer wireless communication with a high data rate and low latency. In some embodiments, said second communication protocol comprises one of near field communication NFC protocol or radio frequency identification RFID protocol. The second communication protocol that is configured to limit the distance of operation may be NFC or RFID. Passive NFC tags for example, are robust, low cost small and easily programmed. The mobile identifier may be a number of things provided it can identify the mobile device. In some embodiments, said mobile device identifier comprises a media access control MAC address of said mobile device. In others it may be specific or unique to a user such that a user may have several devices programmed with the same identifier for use with an application for accessing the vacuum system, each of these devices may be used with the same tag. In some embodiments, said communication interface comprises indicator circuitry configured to indicate at least one of the following: detection of said mobile device and connection of said mobile device to said vacuum system. ln some embodiments, said indicator circuitry comprises one of a visual indicator or an audio indicator. The visual indicator may be simple coloured lights or it may be a display. In some embodiments, said wireless access point circuitry is configured in response to detection of a disconnect event at a connected mobile device, to discard said generated identifier. Detection of the disconnect event may be receipt at the wireless access point circuitry of a disconnection request made by a user of the mobile device. Alternatively, it may be some other event such as the user turning the Wi Fi off. The generated identifier may be discarded when the mobile device disconnects, making the communication interface available to be set up for connection with other devices and also improving security. In some embodiments, said communication interface is configured to broadcast a default identifier not comprising said mobile device identifier in response to no tag having been detected or following a generated identifier having been discarded. Where there is no current maintained generated identifier, then a default identifier may be broadcast, this may allow the operation of wireless access points of multiple systems to be checked without the need to connect to each of them. A further aspect provides a vacuum system comprising a communication interface according to one aspect. The vacuum system may comprise a vacuum system controller. The vacuum system may comprise one or more of: a vacuum pump, abatement system and vacuum gauge. The vacuum system may be configured to host a website for said vacuum system, said mobile device being configured to browse said website on connection to said vacuum system. A further aspect provides a method of wirelessly connecting a mobile device to a vacuum system, said method comprising: bringing a tag comprising an identifier identifying said mobile device within 10cm of a communication interface according to any preceding claim; transmitting a connection request comprising a wireless access point identifier including said identifier identifying said mobile device. In some embodiments, the method further comprises prior to transmitting said connection request scanning for a wireless access point identifier comprising said identifier and in response to detecting said wireless access point identifier then performing said transmitting of said connection request. A yet further aspect provides a wirelessly readable tag comprising an identifier identifying a mobile device and a computer program comprising computer readable instructions which when executed by a processor on said mobile device are operable to control said mobile device to connect to a communication interface according to one aspect by: transmitting a connection request comprising a wireless access point identifier comprising said identifier identifying said mobile device. In some embodiments, said computer program is further operable to control said mobile device to scan for a wireless access point identifier including said identifier of said mobile device; and in response to detecting said wireless access point identifier transmitting said connection request to said access point. In some embodiments, said connection request further comprises a password. In some embodiments, said password in encrypted. ln some embodiments, said computer program is further operable to control said mobile device following connection to said vacuum system, to display a webpage for said vacuum system received from said vacuum system. In some embodiments, said computer program is further operable to control said mobile device to display a disconnect control interface and in response to activation of said disconnect control interface, to transmit a disconnect request to said communication interface. Further particular and preferred aspects are set out in the accompanying independent and dependent claims. Features of the dependent claims may be combined with features of the independent claims as appropriate, and in combinations other than those explicitly set out in the claims. Where an apparatus feature is described as being operable to provide a function, it will be appreciated that this includes an apparatus feature which provides that function or which is adapted or configured to provide that function. BRIEF DESCRIPTION OF THE DRAWINGS Embodiments of the present invention will now be described further, with reference to the accompanying drawings, in which: Figure 1 shows a user using a mobile device and tag according to an embodiment to access a vacuum system with a communication interface according to an embodiment; Figure 2 shows a flow diagram illustrating steps in a method performed by a user accessing a vacuum system; Figure 3 shows a flow diagram illustrating steps in a method performed by a mobile device with a computer program according to an embodiment; and Figure 4 shows a flow diagram illustrating steps in a method performed by a communication interface of a vacuum system DESCRIPTION OF THE EMBODIMENTS Before discussing the embodiments in any more detail, first an overview will be provided. Embodiments seek to ensure, in the case where many vacuum pumps are present on the same site many of which may be equipped with a wireless access point such as WiFi, that it is clear to the user of a mobile computing device which vacuum pump the mobile device is wirelessly connecting to. Embodiments provide a connection that is not dependent on the presence of a centralised WiFi network. The pump creates a WiFi access point to which the mobile device can connect, i.e. a peer-to-peer connection. A WiFi direct connection offers a high data rate which will allows the user of the mobile device to browse web pages, perform software updates and transfer large files between the vacuum pump and mobile device, in a timely manner. Embodiments provide a WiFi connection that is temporary, only existing when the user of the mobile device seeks to connect to the vacuum pump. This improves security by reducing the window of opportunity for a hacker to try to access the pump via WiFi. Embodiments provide a method that uses passive NFC tags which are robust, low cost, small and easily programmed, using low-cost hardware. There is no requirement for the NFC tag to communicate with the mobile device. Embodiments provide vacuum pumps within a building that are equipped with WiFi electronics that allow each of them to create their own WiFi Access Point, which in turns creates a WLAN (wireless local area network). Each pump may be equipped with NFC tag reader electronics and a pump controller, comprising a microprocessor, which is running the pump control software. A person who wishes to connect wirelessly to a pump, has a tag that operates on a different communication protocol to the wireless access point, such as an NFC tag. The tag is programmed with a mobile device identifier, in this example the MAC address (Medium Access Control address) of the person’s mobile device and in some cases with a password. The wireless mobile device can be a tablet or phone or laptop. For additional security, the programming of the MAC address on the NFC tag can be restricted to be performed by a person in the role of ‘administrator’, as opposed to the end user. Also, the MAC address stored on the NFC tag and in some cases the password may be encrypted. The pump controller will have the means to decrypt the data read from the card. Embodiments provide a software application, that runs on the mobile device, is designed to continuously scan the WiFi local area network (WLAN) looking for a specific SSID (Service Set Identifier) that is appended with the mobile device’s MAC Address, e.g. the coded SSID could be “VacuumPump 00:9A:CD:3C:4D:5E”. The SSID text preceding the code number could identify the access point as belonging to a vacuum pump and can be the same for all vacuum pumps on the site. Note: all 802.11 infrastructure devices will send out a beacon frame, containing the SSID, approximately every 100ms (this is the default for many devices, but can be configured to be either faster or slower). Embodiments provide a mobile device that can also be programmed with a hidden password for logging into a vacuum pump’s WiFi access point. The password could be encrypted within the mobile application, so it cannot be read by someone examining the mobile device. In use, when the user “taps” or brings the NFC tag within a few centimetres of the tag reader on the pump, the pump controller software automatically reads the MAC address. The pump controller then broadcasts the coded SSID, containing the MAC address. When the application on the mobile device detects an SSID on the WLAN that contains its own MAC address, it attempts to connect to the vacuum pump’s WiFi access point, using the password. When the pump controller detects a device is attempting to connect it verifies that the MAC address matches that which it has just read from the NFC tag. If the MAC address matches, then the connection is established. If there is a password requirement then it also checks for the password. Once connection is established, the mobile device application may automatically launch a web browser and display web pages that are served by the pump controller. The pump controller comprising a web server. The pump controller may also flash or illuminate a connection indicator light, mounted on an external surface of the pump, visible to the user, to show connection has been established. The connection lamp could use different colours to indicate the connection status. E.g. red = not connected, blue = card being read, green = connected. Instead, or in addition to the connection lamp, the connection status could be displayed as text on a display on the pump. The text display could provide additional information, such as name(s) of connected devices and the number of connections and the device in control. Alternatively, and / or additionally an audible sound (beep) could be emitted by the pump when the tag is read. If the pump controller does not detect a connection attempt from the mobile device within a preset timeout period, then the pump controller stops broadcasting the SSID containing the MAC address. The mobile device application can provide a button, on a user interface, to disconnect it from the vacuum pump WiFi. When the pump controller detects the disconnection, it will cease to broadcast the coded SSID. Another method for disconnection may be for the user to tap the tag on the NFC reader. When the pump controller detects a “tap” whilst maintaining an active connection it will compare the MAC address, read from the NFC tag, and if it matches that of the connected device, it will then disconnect the device and switch off the connection indicator light. Prior to reading an NFC tag, the pump may broadcast a default SSID, that does not contain a MAC address. The default SSID could contain a pump number for simple identification purposes. The advantage of the pump broadcasting a default SSID is that it may allow a group of pumps to be checked to see if they are providing a WiFi signal, using a WiFi scanning system and without needing to use an NFC tag. It could also be possible to connect to a pump via the default SSID and the pump could provide limited information to the mobile device, this information being selected to be information that cannot cause a problem for the pump e.g. pump number and status such as running or stopped. This may allow a user who was not sure of the actual physical location of the pump to identify the pump and then connect using the NFC tag. In other embodiments, a username may be stored on the NFC tag, e.g. “PumaVaclava123” in addition to the MAC Address. The pump control software would read the name from the NFC tag and broadcast this as the WiFi SSID, e.g. “VacuumPump-PumaVaclava123”. The user of the mobile device would then attempt to connect to the vacuum pump manually by looking for and selecting an SSID containing their username, in the list of WiFi connections. The pump controller would complete the connection if the MAC Address, read from the NFC tag and / or password, matched that of the mobile device attempting to connect. In some embodiments, the SSID may remain “hidden” i.e. it is not broadcast. However, the connecting device can establish a connection because it will be continuously scanning the network, attempting to connect to an SSID that contains the appropriate MAC Address and password. In some embodiments, RFID technology may be used in place of NFC technology. This would be a direct substitution and the same method and options for connection would be possible. In some embodiments, an NFC tag or NFC hardware that is built into mobile device may be used. In some embodiments, the pump controller may restrict the connection to allow only one wireless mobile device to connect at a time. This would avoid different users simultaneously trying to control the pump. Figure 1 schematically shows a user wirelessly accessing a vacuum pump 30 within a manufacturing site that contains multiple vacuum pumps 30. The user has a mobile device 10 which may be a tablet or mobile phone or other processing device and in this embodiment the user has a separate NFC tag 12 which is programmed with an identifier of the mobile device 10 and a password. In this embodiment the identifier is the MAC address, but it may be an identifier specific to the user and that the mobile device is programmed to use with a vacuum system accessing application. When the user wants to access a vacuum pump 30 he approaches the wireless communication interface 20 of the vacuum pump 30 that he wishes to access with the NFC tag 12 and the NFC tag detector 22 detects the tag 12 when it is in close proximity to the detector, generally within 5cm. The tag detector 22 then reads the mobile device 10 identifier on the tag and the password. The wireless communication interface 20 will then generate a WiFi access point identifier that includes the mobile device identifier, and in some embodiments the WiFi access point 24 will broadcast this identifier. Where the WiFi access point broadcasts the identifier, the mobile device 10 will scan for a WiFi access point identifier that includes its MAC address and on detection of one it will send a connection request including the password. The WFi access point will detect the request and on determining that the mobile device 10 has the MAC address and / or password corresponding to that read from the NFC tag 12 it will allow connection with the mobile device. In some embodiments an indicator 34 on the vacuum system may then be illuminated indicating that the mobile device 10 has successfully connected to the vacuum system 30. Once the mobile device has connected to the WiFi access point 24 then in some cases the WiFi access point may host a web service for the pump and this may automatically open on the mobile device 10. Mobile device 10 may then communicate via the access point 24 with the pump controller 32 and may download logs of operation, control the vacuum pump and / or provide software updates. The mobile device 10 may display a disconnect button and when the user has finished accessing the vacuum system, the user may press the disconnect button and this may cause the WiFi access point to discard the identifier of the WiFi access point that includes the mobile device identifier and to stop broadcasting this identifier. In some embodiments rather than having a disconnect button on the mobile device the user may simply tap the NFC tag 12 to the tag detector 22 and this will provide the disconnection. In some embodiments where the communication interface 20 has not received a connection request within a predetermined time following detection of the NFC tag 12 then it will discard the WiFi identifier that it has generated that includes the mobile device identifier and the communication access interface will no longer be available for connection to that mobile device. In this way, a user can enter a manufacturing site with multiple vacuum systems, in this case vacuum pumps, and can by the use of the NFC tag 12, select the appropriate vacuum system and reliably connect to this one and not inadvertently to any of the other nearby systems. Figure 2 schematically shows steps in a method performed by a user accessing a vacuum system according to an embodiment. In a step S1 the user starts an application on their mobile device, and the mobile device scans for a wireless access point identifier that includes the mobile device identifier. At a further step S2 the user taps a communication interface of the vacuum system with a tag programmed with the identifier of a mobile device of the user. Step S1 and S2 may be performed in any order. Then at step D6 the mobile device determines whether a web page has loaded in the browser on the mobile device, the web page loading being indicative of an access point having been detected and when it has step S3 is performed where the user interacts with the mobile device via the loaded web page, to perform one or more of the following: monitor data, provide a software update of the pump, control the pump operation and / or change the pump configuration, such as the pump speed, standby mode, maximum temperature, pressure limits etc.. At step D7 the user determines whether all operations are complete and when so performs step S4 and presses the disconnect button and the mobile device disconnects from the access point of the vacuum pump and the web page is no longer loaded on the mobile device. Figure 3 shows steps in a method performed on the mobile device according to an embodiment. At step D5 it is determined if the app on the mobile device has been started. When it has at step S20 the mobile device scans for a wireless access point identifier that includes the mobile device identifier. At step D15 the mobile device determines whether or not the access point has been detected and when it has then step S30 is performed and a connection request for connecting to the wireless access point is generated and at step S40 the connection request is transmitted. In some embodiments there is then a step S50 where information for a web page for the vacuum system is received and at step S60 the mobile device displays the web page. In some embodiments at step S70 the mobile device displays a disconnect button. The mobile device may then perform step S80 and step S84 where requests for system data logs are sent and data logs received and stored (step S80), these may be controlled by the web server, or they may be requested by the user. Other tasks controlled by the user may also be performed (step S84) such as the transmission of software updates, configuration changes or the transmission of commands for controlling the pump. Then at D25 it is determined if the user has pressed the disconnect button. If not, further operations may be performed while if yes, then the method proceeds to step S90 where the mobile device may transmit a disconnect signal and disconnect from the wireless access point. Figure 4 shows steps in a method performed at a communication interface of a vacuum system according to an embodiment. At step S100 the communication interface of the vacuum system detects a NFC tag which includes a mobile device identifier. At step S110 the communication interface generates a wireless access point identifier that includes the mobile device identifier. At step S120 the communication interface broadcasts the wireless access point identifier. At step D105 it is determined whether a predetermined time has elapsed since detection of the NFC tag and if it has then the wireless access point identifier is discarded. If it has not then step S130 is performed where a connection request is received within this predetermined time, and it is then determined at step D115 whether the connection request is from the identified mobile device, that is the mobile device identified by the identifier in the NFC tag. If it is then connection is allowed at step S140. If not then the method returns to step D105 and step S130 to determine if another connection is received within the predetermined time. At step D135 it is determined whether a disconnect event has occurred, this may be the receipt of a disconnect request or the turning off of the mobile device Wi Fi for example. If it has then the mobile device is disconnected at step S160 and at step S170 the generated wireless access point identifier is discarded. If no disconnect event has occurred then connection continues and at step D145 it is determined whether a predetermined time has elapsed since receipt of a user command. If it has then the mobile device is disconnected at step S160 and at step S170 the generated wireless access point identifier is discarded. If not then at step S150 user commands are received and transmitted to the pump controller, and responses from the pump controller are transmitted back to the mobile device. This continues until either there is a prolonged period of inactivity, i.e. no user commands for a predetermined time or a disconnect request is received. Although illustrative embodiments of the invention have been disclosed in detail herein, with reference to the accompanying drawings, it is understood that the invention is not limited to the precise embodiment and that various changes and modifications can be effected therein by one skilled in the art without departing from the scope of the invention as defined by the appended claims and their equivalents. REFERENCE SIGNS 10 mobile device 12 NFC tag 20 wireless communication interface 5 22 NFC tag detector 24 Wi Fi Access point 30 vacuum pump 32 vacuum pump controller 34 visual indicator io

Claims

1. A communication interface for a vacuum system, said communication interface comprising:wireless access point circuitry configured to provide wireless peer to peer communication with a mobile device using a first communication protocol;detection circuitry configured to wirelessly detect a tag located within 10cm of said interface using a second communication protocol, said tag comprising an identifier identifying said mobile device;said wireless access point circuitry being configured to generate an identifier for identifying said wireless access point to said mobile device in response to detecting said tag, said identifier including said mobile device identifier.

2. A communication interface according to claim 1, said wireless access point circuitry being configured to broadcast an indication of said generated identifier.

3. A communication interface according to any preceding claim, said wireless access point circuitry being configured to maintain said generated identifier for a predetermined time following detection of said tag, and where no valid connection request is received within said time period to discard said generated identifier.

4. A communication interface according to any preceding claim, said wireless access point circuitry being further configured to determine whether said connection request comprises a valid password and where not to not allow said connection request.

5. A communication interface according to claim 4, wherein said tag comprises said password, said tag detector being configured to detect said password and said mobile device identifier.

6. A communication interface according to any preceding claim, wherein said wireless access point circuitry is configured to provide wireless peer to peer communication using WiFi Direct following the IEEE802.11 standard, and said generated identifier comprises a service set identifier SSID.

7. A communication interface according to any preceding claim, wherein said second communication protocol comprises one of near field communication NFC protocol or radio frequency identification RFID protocol.

8. A communication interface according to any preceding claim, said communication interface comprising indicator circuitry to indicate at least one of the following: detection of said mobile device and connection of said mobile device to said vacuum system.

9. A communication interface according to any preceding claim, said wireless access point circuitry being configured in response to detection of a disconnect event at a connected mobile device, to discard said generated identifier.

10. A communication interface according to any preceding claim, said communication interface being configured to broadcast a default identifier not comprising said mobile device identifier in response to no tag having been detected or following a generated identifier having been discarded.

11. A vacuum system comprising a communication interface according to any one of claims 1 to 10.

12. A method of wirelessly connecting a mobile device to a vacuum system, said method comprising:bringing a tag comprising an identifier identifying said mobile device within 10cm of a communication interface according to any preceding claim;transmitting a connection request comprising a wireless access point identifier including said identifier identifying said mobile device.

13. A wirelessly readable tag comprising an identifier identifying a mobile device and a computer program comprising computer readable instructions which when executed by a processor on said mobile device are operable to control said 5 mobile device to connect to a communication interface according to any one of claims 1 to 11 by:generating and transmitting a connection request comprising a wireless access point identifier comprising said identifier identifying said mobile device.io 14. A wirelessly readable tag and computer program according to claim 13, said computer program further controlling said mobile device toscan for a wireless access point identifier including said identifier of said mobile device; andin response to detecting said wireless access point identifier generating 15 and transmitting said connection request to said access point.

15. A wirelessly readable tag and computer program according to claim 13 or 14, wherein said connection request further comprises a password.

Citation Information

Patent Citations

  • ViewUS20180332630A1onEspacenetopensinnewtab