Method of managing updates to offline devices

Abstract

A method to manage updates to electronic devices of a mesh network in an offline environment is provided. Each electronic device of the mesh network includes a memory, the memory including a proxy device count indicating an active number of devices in the mesh network acting as a proxy device connected to a mobile device. The method includes receiving, by a device of the mesh network, a connection request to the device by the mobile device, and checking, by the device, the proxy device count. Responsive to a determination that the proxy device count is less than a maximum number of proxy devices, the device: connects to the mobile device, increments the proxy device count by one, and communicates a first message to other devices of the mesh network that the device acts as a proxy device to synchronize the proxy device count across the mesh network.

Description

METHOD OF MANAGING UPDATES TO OFFLINE DEVICESCROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of Indian Provisional Application No. 202311058960 filed September 2, 2023.BACKGROUND

[0002] Electronic devices such as hazardous area light fixtures can be configured as part of a mesh network to enable collective control. In certain industrial applications, cloud / extemal network connectivity may not be possible or available for these electronic devices, resulting in the devices effectively operating offline. The lack of online access from the devices themselves as well as potentially any mobile device that may be used to provide an over-the-air (OTA) update creates a constraint on the features available to these electronic devices.

[0003] When there is cloud / extemal connectivity, there are checks to limit the number of users managed by the cloud / extemal network that can access the mesh network. The number of users that can access the mesh network is limited so that two or more users are not attempting to change a setting on one or more of the devices in the mesh network at the same time . Limiting the number of users that can access and / or change the settings on the devices in the mesh network is therefore also needed when the mesh network is offline.BRIEF SUMMARY

[0004] Methods for managing updates to electronic devices of a mesh network in an offline environment are provided. Through the described methods, it is possible to limit the number of mobile devices accessing electronic devices configured in a mesh network as well as limit how many users can update features on the electronic devices of the mesh network in case external connectivity is not available. In addition, mobile users, via mobile devices, can track which features have been changed on each electronic device in the mesh network.

[0005] A method to manage updates to electronic devices of a mesh network in an offline environment is provided. Each electronic device of the mesh network includes a memory, the memory including a proxy device count indicating an active number of electronic devices in the mesh network acting as a proxy device connected to a mobile device. The method includes receiving, by an electronic device of the mesh network, a connection request to the electronic device by the mobile device, and checking, by the electronic device, the proxy device count. Responsive to a determination that the proxy device count is less than a maximum number ofproxy devices, the electronic device: connects to the mobile device, increments the proxy device count by one, and communicates a first message to other electronic devices of the mesh network that the electronic device acts as a proxy device to synchronize the proxy device count across the mesh network.

[0006] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1 illustrates an example operating environment of mesh devices.

[0008] FIG. 2 illustrates a schematic diagram of an electronic device of the mesh network.

[0009] FIG. 3 illustrates an example implementation of a common list.

[0010] FIG. 4 illustrates an example implementation of an individual list.

[0011] FIG. 5 illustrates a process flow describing a method to manage updates to electronic devices of a mesh network in an offline environment.

[0012] FIG. 6 illustrates an example scenario for offline electronic devices in a mesh network.DETAILED DESCRIPTION

[0013] Methods for managing updates to electronic devices of a mesh network in an offline environment are provided. Through the described methods, it is possible to limit the number of mobile devices accessing electronic devices configured in a mesh network as well as limit how many users can update features on the electronic devices of the mesh network in case external connectivity is not available. In addition, mobile users, via mobile devices, can track which features have been changed on each electronic device in the mesh network.

[0014] While a few electronic devices are shown in the figures for illustrative purposes, the number of electronic devices in the mesh network 110 can be any number. For example, there may be 100 electronic devices in the mesh network 110.

[0015] FIG. 1 illustrates an example operating environment of mesh devices. Referring to FIG. 1, a plurality of electronic devices 100 can communicate with each other over a mesh network 110. The mesh network can be a Bluetooth® low energy (BLE) mesh, Zigbee mesh, Wi-Fi mesh, as well as other wireless networks. The electronic devices 100 are represented as nodes in the mesh network 110. The mesh network may be a partially connected mesh networkor a fully connected mesh network. Nodes in the network 110 can relay messages by flooding (the message is sent through every outgoing link except the one the message was received from) or routing (the message hops from node to node until it reaches its destination). When communicating by a flooding technique, controlled flooding may be used, for example SNCP (Sequence Number Controlled Flooding) and RPF (reverse path forwarding).

[0016] For a device that is not part of the mesh network, such as mobile device 150, communication on the mesh network 110 is conducted via a proxy device 160. The mobile device 150 configures the plurality of electronic devices 100 (i.e., provisioning) into the mesh network 110 and controls features on the plurality of electronic devices 100 via a mobile application running on the mobile device 150. In order to ensure that this provisioning operation is done securely, the mobile application and the proxy device 160 authenticate one another to make sure that the proxy device 160 is a valid device and that the mobile application is valid to communicate with the mesh network 110. When there is cloud connectivity, the mobile application communicates directly with a cloud network in order to conduct this validation via a cryptographic application in the cloud network. During cloud connectivity, the current local time is read from a cloud server and communicated from the mobile device 150 to each of the plurality of electronic remote devices 100 in the mesh network 110 via the proxy device 160 by a broadcast mechanism. All the nodes in mesh network 110 are capable of transferring data to a nearby node in the same mesh network using the broadcast mechanism such that all nodes receive the information simultaneously and hence do not send an acknowledgement. Many times, however, the mesh network 110 is located in areas without cloud connectivity and / or access to the mobile device 150.

[0017] FIG. 2 illustrates a schematic diagram of an electronic device of the mesh network. The electronic device 100 includes a memory 202 and a real time clock (RTC) 208. The memory 202 is a non-volatile memory that can include an internal memory and flash memory. The RTC 208 (along with the respective clocks on the other electronic devices in the mesh network) can be utilized to set a schedule for the mesh network 110. The memory 202 includes a proxy device count indicating the active number of electronic devices in the mesh network 110 acting as a proxy device 160 connected to a mobile device 150. In addition, the electronic device 100 includes two lists, a common list 204 and an individual list 206 that are stored within the memory 202. The two lists 204 and 206 help the offline mesh network 110 to maintain data synchronization and to limit the number of mobile devices allowed to access the mesh network 110. While one electronic device 100 has been illustrated in FIG. 2, each electronic device in the mesh network 110 includes memory and a real time clock as described.Each electronic device 100 in the mesh network 110 includes the proxy device count, the common list 204 and the individual list 206 stored in its corresponding memory 202.

[0018] FIG. 3 illustrates an example implementation of a common list. The common list can be a list of devices actively updated by multiple users. In some cases, the common list 204 can be a bit list such that each electronic device 100 corresponds to one bit in the bit list. The bit (e.g., a flag) is set to a ‘ 1’ when the corresponding electronic device 100 is being updated by multiple mobile devices 150. The bit is cleared to a ‘0’ when the corresponding electronic device 100 is no longer being updated by multiple mobile devices 150. In addition, the common list includes an address of the electronic device 100 that is being updated by multiple devices 150. Each electronic device 100 maintains the same common list 204. In other words, the common list 204 is the same for all the electronic devices 100 in the mesh network 110.

[0019] In order to synchronize the common list 204 among each electronic device 100 in the mesh network 110, each electronic device 100 sends a message to the other electronic devices 100 in the mesh network 110 via the broadcast mechanism, for example, when the electronic device 100 is being actively updated by multiple mobile devices 150. For example, once the electronic device identifies, within a stipulated amount of time, e.g., 1 minute, that it has received commands from two different mobile devices, e.g., two different user identifications, the electronic device 100 will send the message by a broadcast. The message will include the address of the electronic device 100 and the bit corresponding to the electronic device 100 set in the bit list. Each of the other electronic devices 100 can then set the bit corresponding to the electronic device 100 sending the message in their corresponding common list 204 and save the corresponding address. Likewise, the electronic device 100 sends a message to the other electronic devices 100 in the mesh network via the broadcast mechanism when it is no longer being actively updated by multiple mobile devices 150, e.g., when simultaneous write operation is not observed by the electronic device 100 for a stipulated amount of time, e.g., 5 minutes. This can occur, for example, when the mobile device disconnects from the mesh network 110. The message will include the address of the electronic device 100 and its corresponding bit in the bit list cleared.

[0020] From the common list 204, a mobile device 150 connected to the mesh network 110 via a proxy device 160 can show a user which electronic devices 100 are being actively updated by multiple mobile devices 150. Utilizing a bit list prevents the mesh network 110 from circulating a large quantity of data each time multiple mobile devices connect / disconnect to an electronic device 100 in the mesh network 110. For example, if there are 100 electronic devices 100 in the mesh network 110 and each electronic device 100 corresponds to one bit in a bit list,only 12 bytes of data is needed for the bit list. The common list can have a maximum size of 25 bytes, for example, depending on the size of memory available.

[0021] FIG. 4 illustrates an example implementation of an individual list. The individual list 206 includes information such as a list of features of the electronic device 100 as well as a user identification of the mobile device 150 that most recently changed a corresponding feature . Each electronic device 100 maintains its own individual list 204 pertaining to its features only. In other words, the individual list 206 can be different for all the electronic devices 100 in the mesh network 110. Features of the electronic device 100 as listed in the feature list of the individual list can include a weekly schedule, a holiday list and schedule, a time as kept by a real time clock (RTC) in the memory of the electronic device, and an OTA upgrade (e.g., for firmware updates). In some cases, the time of an update to a feature can also be logged into the individual list 206.

[0022] FIG. 5 illustrates a process flow describing a method to manage updates to electronic devices of a mesh network in an offline environment. The mesh network 110 includes the electronic device and other electronic devices 100. In some cases, method 500 begins when an electronic device 100 receives (510) a connection request by a mobile device 150 to connect to the electronic device 100. Referring to FIG. 5, the method 500 includes checking (520), by the electronic device 100, the proxy device count. Responsive to the determination that the proxy device count is less than a maximum number, connecting, (530) by the electronic device 100, to the mobile device 150, incrementing (540) the proxy device count by one, and communicating (550) a first message to the other electronic devices 100 of the mesh network 110 that the electronic device acts as a proxy device to synchronize the proxy device count across the mesh network 110. When the mobile device 150 disconnects from the mesh network 110, the electronic device 100 communicates a second message to the other electronic devices 100 of the mesh network 110 to synchronize the proxy device count and reduces its proxy device count by one. Responsive to the determination that the proxy device count is equal to or greater than the maximum number, the electronic device 100 communicates to the mobile device 150 that access to the mesh network 110 is denied.

[0023] The first message, the second message, and other messaging between the electronic devices 100 in the mesh network is communicated as a broadcast message, for example, so that each of the other electronic devices 100 receives the message simultaneously or almost simultaneously. While broadcast is used throughout the disclosure as a communication mode between the electronic devices 100 in the mesh network 110, other modes of communication can also be utilized by the electronic devices 100, such as unicast (e.g., sent from one node toanother node in the mesh network) and groupcast / multicast (sent from one node to a subset, or group, of nodes in the mesh network).

[0024] An example scenario for offline electronic devices in a mesh network is illustrated in FIG. 6. Mesh network 110 includes offline electronic devices 101, 102, 103, and 104. A first mobile device 151 attempts to connect to electronic device 101 with the result that electronic device 101 performs the method 500 described above. Electronic device 101 receives (510) a connection request from mobile device 151. Electronic device 101 checks (520) the proxy device count stored in its memory 202. Since the proxy device count is zero, e.g., less than a maximum number of proxy devices allowed in the mesh network, the electronic device 101 connects to the mobile device 151, increments (540) the proxy device count to one and communicates (550) in a first message to all the other electronic devices (shown in FIG. 6 by arrows from electronic device 101 to other devices 102, 103, and 104), 102, 103, and 104, that it is acting as a proxy device 160. Upon receiving the first message, each of the other electronic devices 102, 103, 104, can increment by one their respective proxy device counts thereby synchronizing the proxy device count in the mesh network 110. Similarly, a second mobile device 152 attempts to connect to electronic device 104 such that electronic device 104 receives a connection request from mobile device 152. Method 500 will thus be performed by electronic device 104. Since the maximum number of proxy devices is one, the connection is allowed by electronic device 104. After the connection is made and a second message communicated (not shown) to the other electronic devices 101, 102, and 103 in the mesh network 110, the proxy device count is now two. A third mobile device 153 attempts to connect to electronic device 103 such that electronic device 103 receives (510) a connection request from mobile device 153. When electronic device 103 checks (510) the proxy device count and determines that the proxy device count is now two, e.g., the maximum number of proxy devices allowed in the mesh network, electronic device 103 communicates to mobile device 153 that access to the mesh network 110 is denied. While the maximum number of proxy devices allowed in the mesh network 110 in the scenario illustrated in FIG. 6 is two, the maximum number of proxy devices can be any number greater than zero.

[0025] Once a mobile device 150 is connected to a proxy device 160, the mobile device 150 can make updates to the features of the electronic device 100. It is important for mobile users to recognize when the electronic device 100 is being actively updated by multiple electronic devices. When an electronic device 100 of the mesh network 110 is being actively updated within a time period by multiple devices, the electronic device 100 sets the corresponding bit in its bit list. Then, the electronic device 100 communicates by a third message to the otherelectronic devices 100 in the mesh network that the electronic device 100 is being updated by multiple users to synchronize the common list 204 among all the electronic devices in the mesh network 110. Upon receiving the third message, the other electronic devices 100 in the mesh network 110 can set the corresponding bit in their bit lists for the electronic device communicating the information.

[0026] In some cases, the electronic device 100 can issue a warning to connected mobile devices 150 when it is being updated by multiple mobile devices 150. Likewise, when one or both of the multiple mobile devices 150 disconnects from the electronic device 100 and stops actively updating the electronic device 100 within a time period, the electronic device 100 clears the corresponding bit in the bit list. The electronic device 100 then communicates in a third message to the other electronic devices 100 in the mesh network 110 that the electronic device 100 is no longer being updated by multiple users to synchronize the common list 204 for all the electronic devices 100 in the mesh network 110. In some cases, the time period can be in a range of one minute to thirty minutes.

[0027] As stated previously, each electronic device 100 maintains its own corresponding individual list 206 having its features and the user identification number of the mobile device that most recently changed a feature. In some cases, the time the feature was changed is also available in the individual list 206. When a connected mobile device 150 updates a feature on the electronic device 100, the electronic device 100 updates its individual list 206 with the user identification number of the mobile device 150 that is updating the feature.

[0028] In operation, when a mesh network of electronic devices is offline such that it has lost connectivity, the mesh network can act as a virtual cloud and synchronize data between the electronic devices in the mesh network. Utilizing the described methods, the electronic devices in the mesh network can limit the number of mobile devices that can connect to the mesh network. By the electronic devices maintaining a common list and an individual list, the users can know when multiple mobile devices are accessing and updating features on the electronic devices. For example, a mobile user via the mobile device, when accessing the network via a proxy device, can see by looking at the common list what electronic devices are being actively updated by multiple mobile devices. Then, the mobile user can access an electronic device being actively updated by multiple mobile devices and obtain details on which features have been updated on the electronic device and by which mobile devices.

[0029] Although the subject matter has been described in language specific to structural features and / or acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specificfeatures and acts described above are disclosed as examples of implementing the claims and other equivalent features and acts are intended to be within the scope of the claims.

Claims

CLAIMSWhat is claimed is:

1. A method to manage updates to electronic devices of a mesh network in an offline environment, wherein each electronic device includes a memory, the memory including a proxy device count indicating an active number of electronic devices in the mesh network acting as a proxy device connected to a mobile device, the method comprising: receiving, by an electronic device of the mesh network, a connection request to the electronic device by the mobile device; checking, by the electronic device, the proxy device count; and responsive to a determination that the proxy device count is less than a maximum number of proxy devices, the electronic device: connects to the mobile device; increments the proxy device count by one; and communicates a first message to other electronic devices of the mesh network that the electronic device acts as a proxy device to synchronize the proxy device count across the mesh network.

2. The method of claim 1, further comprising responsive to the determination that the proxy device count is greater than or equal to the maximum number, the electronic device: communicates to the mobile device that access to the mesh network is denied.

3. The method of claim 1, wherein when the mobile device disconnects from the mesh network, the electronic device: reduces the proxy device count by one, and communicates a second message to the other electronic devices in the mesh network that the electronic device no longer acts as proxy electronic device to synchronize the proxy device count across the mesh network.

4. The method of claim 1, further comprising: receiving a third message from a further electronic device in the mesh network to indicate that the further electronic device acts as a proxy; and incrementing the proxy device count by one.

5. The method of claim 1, further comprising: receiving a third message from a further electronic device in the mesh network to indicate that the further electronic device no longer acts as a proxy; and reducing the proxy device count by one.

6. The method of claim 1, wherein each electronic device in the mesh network includes a common list and an individual list stored in the memory of the electronic device, wherein the common list comprises a bit list so that each bit in the bit list corresponds to one electronic device in the mesh network and a set bit indicates the corresponding electronic device is being updated by multiple mobile devices, and wherein the individual list comprises a list of features of the corresponding electronic device and a user identification of the mobile device that most recently changed a feature in the list of features.

7. The method of claim 6, further comprising: synchronizing the common list when the electronic device is actively being updated by multiple mobile devices within a time period by: setting the corresponding bit in the bit list when the electronic device is being updated by multiple mobile devices within the time period; and communicating a third message to the other electronic devices in the mesh network, the third message including the bit list and an address of the electronic device, to indicate that the electronic device is being actively updated by multiple mobile devices.

8. The method of claim 7, wherein the time period is in a range of one to thirty minutes.

9. The method of claim 7, further comprising issuing a warning, by the electronic device, to each connected mobile device that the electronic device is being updated by multiple users.

10. The method of claim 6, further comprising: synchronizing the common list when the electronic device is not being updated by multiple mobile devices within a time period by: clearing the corresponding bit in the bit list when the electronic device is not being updated by multiple mobile devices within the time period; and communicating in a third message to the other electronic devices in the mesh network that the electronic device is not being actively updated by multiple mobile users.

11. The method of claim 10, wherein the time period is in a range of one to thirty minutes.

12. The method of claim 6, further comprising responsive to an update to a feature on the electronic device by the connected mobile device, updating the individual list with the feature changed and the user identification of the mobile device.

13. The method of claim 12, wherein a time of the update is logged into the individual list when the feature is changed.

14. The method of claim 1, wherein the maximum number of proxy devices in the mesh network is two.

15. The method of claim 1, wherein the mesh network is a Bluetooth® low energy network.

16. The method of claim 1, wherein communication between the electronic devices of the mesh network, including between the proxy device and the other electronic devices, is broadcast.

Images