Method and apparatus for ensuring continued reliability of device operation in cloud degraded mode - Patents.com
A primary network with backup devices maintaining subset data and heartbeat confirmation ensures reliable device operations during failures, addressing the complexity and cost issues of traditional redundancy methods.
Patent Information
- Application Number
- JP2023044054
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-10-09
- Filing Date
- 2023-03-20
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2039-10-01
AI Technical Summary
Existing cloud-based systems face challenges in maintaining operational reliability for IoT devices and other connected devices due to the complexity and cost of replicating the entire system in multiple locations for redundancy, which can lead to inconsistent data synchronization and management issues.
Implementing a primary network with backup network devices that maintain a subset of device state data, including heartbeat confirmation data, allowing devices to operate reliably during failures by using a secondary network with a heartbeat-only backup system, ensuring authorization through revocation agents and heartbeat confirmation signals.
This approach simplifies data consistency management and reduces costs while maintaining reliable device operations during network failures by using a secondary network with a heartbeat-only backup system, ensuring authorized device operations without complete data redundancy.
Smart Images

Figure 0007588670000001 
Figure 0007588670000002 
Figure 0007588670000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a network in a cloud-degraded mode. For reliable operation of connected devices. [Background technology]
[0002] background There are cloud services that require a very high degree of operational reliability to support Internet of Things (IoT) devices and other devices. Devices tend to require heartbeats (also called keep-alive signals) back from the cloud environment to ensure that the device can continue to execute a task or operation that was in progress. At the point where the device becomes critical, the problem arises that the cloud service becomes a large part of the reliability of the entire system.
[0003] One way to increase the reliability of cloud services is to replicate the entire system in two or more locations, effectively providing N+1 redundancy. However, this technique is difficult to manage, and full consistency between two systems can be complex and expensive. Summary of the Invention [Means for solving the problem]
[0004] overview A primary network, such as a primary cloud network, includes one or more network devices, such as servers, that store device state data for various devices that communicate with the primary network. For example, the devices include Internet of Things (IoT) devices, wireless base stations, end-user devices (wireless mobile devices and wired devices), or other devices. In one example, a backup network device, such as one or more servers in a secondary network, such as a secondary cloud network, is a smaller system that backs up a subset of the state data that the primary network maintains. In some implementations, the backup device in the secondary network maintains a copy of valid heartbeat confirmation data (keep-alive signal data) obtained from the primary network. In one example, only the keep-alive signal data is backed up by the secondary network. However, any subset of device state data may be backed up, as long as it includes a backup of the keep-alive data, also referred to as heartbeat confirmation data.
[0005] In some implementations, the system is comprised of a primary service provided by one or more servers in a primary cloud infrastructure and a heartbeat-only system (HBO) maintained through a backup device in a secondary cloud infrastructure. The secondary network is associated with the primary network. In some implementations, the systems, methods, and apparatus may also have an invalidation agent invalidate the heartbeat validation data before, during, or after a failure condition.
[0006] The heartbeat verification data is data that indicates that the device is permitted to continue operation with the primary cloud. In one example, the heartbeat verification data is stored in a table in the secondary network, allowing the second system to provide maximum separation without requiring a completely rewritten software service. This allows consistent operation of IoT devices or other devices to be maintained even during failure conditions of the primary network without always having a perfect consistent copy of state data across multiple cloud infrastructures and without smaller independent services to ensure reliability across parts of the cloud network. Providing the heartbeat can be replicated in a greatly simplified manner, possibly even to the point of being a static web page handler. However, any suitable operation may be used to provide the heartbeat. Maintaining consistent state is greatly simplified by the secondary cloud system being updated with device heartbeat confirmation data by the primary cloud system.
[0007] Aspects of the present disclosure provide reliable operation of a network-connected device in a cloud degraded mode. One aspect of the present disclosure provides a method for providing operational reliability of a communication device adapted to communicate with a first network. If a network failure condition exists that prevents communication between the communication device and a network device of a first network, the method includes receiving, at data processing hardware of a secondary network, a heartbeat request from the communication device requesting permission that the communication device may perform a device operation. The method further includes the data processing hardware obtaining device status data associated with the communication device. The method further includes the data processing hardware determining whether the communication device is authorized to perform the device operation based on the device status data associated with the communication device. If the communication device is authorized to perform the device operation, the method further includes the data processing hardware sending a heartbeat confirmation signal to the communication device. The heartbeat confirmation signal authorizes the communication device to perform the device operation.
[0008] Implementations of the present disclosure may include one or more of any of the following features: Obtaining the device state data may include receiving the device state data associated with the communication device from the network device of the first network. In some implementations, if the device state data is received prior to receiving the heartbeat request from the communication device and if the network failure condition does not exist, the method includes storing the device state data in a backup data store, retrieving the device state data from the backup data store using a device identifier that identifies the communication device, and associating the communication device with the device state data stored in the backup data store. In some examples, determining whether the communication device is authorized to perform the device operation includes determining whether the device state data includes heartbeat confirmation data. The heartbeat confirmation data may indicate permission from the network device of the first network that the communication device may perform the operation. If the device state data includes heartbeat confirmation data, the method may include determining that the communication device is authorized to perform the device operation. If the device state data does not include heartbeat confirmation data, the method may include determining that the communications device is not authorized to receive the heartbeat confirmation signal. In some examples, the method includes preventing the communications device from performing the device operation by preventing transmission of the heartbeat confirmation signal to the communications device if the device state data does not include heartbeat confirmation data.
[0009] In some implementations, determining that the communications device is authorized to perform the device operation includes determining whether the device state data includes disabling data that disables the communications device's ability to perform the device operation. In these implementations, if the device state data includes heartbeat validation data and does not include disabling data, the method determines that the communications device is authorized to perform the device operation. However, if the device state data includes revocation data and heartbeat confirmation data, the method may include revoking permission for the communications device to perform the device operation and preventing the communications device from performing the operation by withholding transmission of the heartbeat confirmation signal to the communications device. The revocation data may indicate that a software update of the communications device is required, that the communications device is not in compliance with a contractual agreement, and / or that resources required for the communications device to perform the device operation are unavailable to the communications device.
[0010] In some examples, the network device of the first network is configured to push device status data associated with the communication device to the data processing hardware prior to the network failure condition. Additionally or alternatively, the network device of the first network may be configured to transmit the device status data associated with the communication device in response to a pull operation by the data processing hardware. The device status data may include a device identifier that identifies the communication device, disabling data that disables the communication device's ability to perform the device operation, operational reliability information associated with the communication device, a payment status, the communication device's ability to update organizational metadata, and / or an aggregation calculation of overall environment health.
[0011] If the network failure condition does not exist, the communication device may be configured to send the heartbeat request to the network device of the first network for permission to perform a device operation, and the network device of the first network may be configured to send the heartbeat confirmation signal to the communication device. The network device may be further configured to update the device state data associated with the communication device to include the heartbeat confirmation signal sent to the communication device. In some implementations, the network failure condition exists if the communication device does not receive a heartbeat confirmation signal from the network device within a threshold period of time after sending a heartbeat request to the network device of the first network. The communication device may include an Internet of Things (IoT) device, a temperature sensor, a wireless base station, a mobile device, and / or a smart appliance.
[0012] Another aspect of the present disclosure provides a system for reliable operation of a network-connected device in a cloud degraded mode. An aspect of the present disclosure includes data processing hardware in a backup network and memory hardware in communication with the data processing hardware. The memory hardware may store instructions that, when executed on the data processing hardware, cause the data processing hardware to perform an operation. If a network failure condition exists that prevents communication between a communication device and a network device of a first network, the operation includes receiving a heartbeat request from the communication device. The heartbeat request requests permission that the communication device may perform a device operation. The operation further includes obtaining device status data associated with the communication device and determining whether the communication device is authorized to perform the device operation based on the device status data associated with the communication device. If the communication device is authorized to perform the device operation, the operation includes transmitting a heartbeat confirmation signal to the communication device. The heartbeat confirmation signal authorizes the communication device to perform the device operation.
[0013] Implementations of the present disclosure may include any one or more of the following features. Obtaining state data may include receiving the device state data associated with the communication device from the network device of the first network. In some implementations, if the device state data is received prior to receiving the heartbeat request from the communication device and if the network failure condition does not exist, the operations include storing the device state data in a backup data store, retrieving the device state data from the backup data store using a device identifier that identifies the communication device, and associating the communication device with the device state data stored in the backup data store. In some examples, determining whether the communication device is authorized to perform the device operation includes determining whether the device state data includes heartbeat confirmation data. The heartbeat confirmation data may indicate permission from the network device of the first network that the communication device may perform the device operation. If the device state data includes heartbeat confirmation data, the operations may include determining that the communication device is authorized to perform the device operation. If the device state data does not include heartbeat confirmation data, the operations may include determining that the communication device is not authorized to receive the heartbeat confirmation signal. The action may include preventing the communications device from performing the device action by preventing transmission of the heartbeat confirmation signal to the communications device if the device state data does not include heartbeat confirmation data.
[0014] In some implementations, determining that the communications device is authorized to perform the device operation includes determining whether the device state data includes disabling data that disables the communications device's ability to perform the device operation. In these implementations, if the device state data includes heartbeat confirmation data and does not include disabling data, the operation includes determining that the communications device is authorized to perform the device operation. However, if the device state data includes disabling data and heartbeat confirmation data, the operation may include revoking permission for the communications device to perform the device operation and preventing the communications device from performing the operation by withholding transmission of the heartbeat confirmation signal to the communications device. The disabling data may indicate that a software update of the communications device is required, that the communications device is not in compliance with a contractual agreement, and / or that resources required for the communications device to perform the device operation are unavailable to the communications device.
[0015] In some examples, the network device of the first network is configured to push device status data associated with the communication device to the data processing hardware prior to the network failure condition. Additionally or alternatively, the network device of the first network may be configured to transmit the device status data associated with the communication device in response to a pull operation by the data processing hardware. The device status data may include a device identifier that identifies the communication device, disabling data that disables the communication device's ability to perform the device operation, operational reliability information associated with the communication device, a payment status, the communication device's ability to update organizational metadata, and / or an aggregate calculation of overall environmental health.
[0016] If the network failure condition does not exist, the communications device may be configured to send the heartbeat request to the network device of the first network, and the network device of the first network may be configured to send the heartbeat confirmation signal to the communications device. The network device may be configured to configure the communications device to include the heartbeat confirmation signal sent to the communications device. and updating the device status data associated with the network device of the first network. In some implementations, the network failure condition exists if the communication device does not receive a heartbeat confirmation signal from the network device of the first network within a threshold period after sending a heartbeat request to the network device of the first network. The communication device may include an Internet of Things (IoT) device, a temperature sensor, a wireless base station, a mobile device, and / or a smart appliance.
[0017] Like reference numbers in the various drawings indicate like elements. [Brief description of the drawings]
[0018] [Figure 1] FIG. 1 is a schematic diagram of an example of a network system including a primary network and a secondary network. [Diagram 2] 2 is a schematic diagram of an example of a network device used in a primary network of the network system of FIG. 1. [Diagram 3] 2 is a schematic diagram of an example of a backup device used in a secondary network of the network system of FIG. 1. [Figure 4] 1 is a flow chart diagram of an example arrangement of operations for a method of providing operational reliability for a communication device adapted to communicate with a primary network. [Diagram 5] 1 is a flow chart diagram of an example arrangement of operations for a method of providing operational reliability for a communication device adapted to communicate with a primary network. [Figure 6] 1 is a flow chart diagram of an example arrangement of operations for a method of providing operational reliability for a communication device adapted to communicate with a primary network. [Figure 7] FIG. 1 is a schematic diagram of an example computing device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0019] Detailed Description FIG. 1 illustrates an example of a network system 100 using a primary network 102 and a secondary network 104. In one example, the primary network 102 is a cloud network infrastructure operated by a first provider, and the secondary network 104 is a different cloud network infrastructure operated by a different service provider. However, any suitable network configuration may be used. Various communication devices 106, 106a-e register with and communicate with the primary network 102 by techniques such as via wireless or wired interfaces. Although an example of five different types of communication devices 106 is shown, any number of communication devices 106 may register with and communicate with the primary network 102 at any given time. For example, some communication devices 106a, 106b, 106e may include Internet of Things (IoT) devices or user equipment (UE) devices, such as temperature sensors or smart appliances in a building, or mobile computing devices (e.g., smartphones, tablets, wearables, etc.). Other communication devices 106c, 106d may include wireless base stations. In the illustrated example, each of the communication devices 106 communicates with the primary network 102 via an Internet Protocol (IP)-based communication protocol or other suitable protocol. In one example, one or more of the communication devices 106 may communicate with the primary network 102 and the secondary network 104 via a Domain Name System (DNS) as part of an Internet-based cloud network system. The primary network 102 includes a primary network device 200. The network device 200 (e.g., the primary network device 200 of FIG. 1) may be one or more servers, such as a web server, that communicates with one or more of the communication devices 106. As such, the network device 200 includes data processing hardware 210 and memory hardware 220 that communicates with the data processing hardware 210. In some examples, the network device 200 may include a network device 200 that is connected to the network device 200 via a network interface 202. The device 200 runs a software application or service, such as a web registration service 202. The communication devices 106 may register with the web registration service 202 to receive a heartbeat confirmation signal 126 (also called a heartbeat confirmation or keep-alive signal) that allows the communication devices 106 to continue performing a task or operation that was in progress. All of the communication devices 106 may be of the same type, such as all IoT type devices, or may be various combinations of different types of devices, such as smartphones and wireless base stations that the smartphones may wish to use for communication. An example of the primary network 102 includes a Citizens Broadband Radio Service (CBRS) system, although the primary network 102 may be any suitable system.
[0020] A communication device 106, such as IoT device 106a, sends a heartbeat request 128 to the network device 200 (e.g., data processing hardware 210) in the primary network 102 requesting a heartbeat confirmation signal 126 back from the network device 200. The heartbeat confirmation signal 126 may include the heartbeat confirmation data 118. When the IoT device 106a receives the heartbeat confirmation signal 126, the IoT device 106a continues to perform its current task or operation with the primary network 102 since a network failure condition 130 does not exist. The communication of the heartbeat request 128 and the heartbeat confirmation signal 126 between the communication device and the network device 200 may occur at least once every 20 seconds, once every 240 seconds, or during any suitable period of time. In some implementations, the server 200 records device state data 110 indicative of the heartbeat confirmation data 118 issued to each particular communication device 106 and stores the device state data 110 along with a device identifier (ID) 114 associated with that particular communication device 106 in a device state data store 212 in communication with the network device 200. In some examples, the device state data store 212 resides on the memory hardware 220 of the network device 200. The device state data 110 stored in the device state data store 212 includes other information, including information related to the execution of a current task or operation with the primary network 102. The device state data 110 may include, but is not limited to, data representing a payment status, an ability to update organizational metadata, an aggregate calculation of the overall environmental health, and / or other suitable data. As long as the IoT device 106a receives a corresponding heartbeat confirmation signal 126 in response to issuing a heartbeat request 128, the IoT device 106a knows that it can continue to operate with the primary network 102. However, if, for example, the IoT device 106a does not receive a heartbeat confirmation signal 126 from the primary network 102, the IoT device 106a recognizes that a network failure condition 130 has occurred in the primary network 102.In some examples, if the communication device 106 does not receive a heartbeat confirmation signal 126 within a predetermined period of time after issuing / transmitting a heartbeat request 128, the communication device 106 recognizes that a network failure condition 130 exists.
[0021] In some examples, the primary network 102 is a cloud network of a first provider. The cloud network 102 (e.g., the primary network 102 (FIG. 1)) may include a primary network device 200. The primary network device may execute a web registration service 202. In some examples, the communication device registers with the web registration service 202 to perform operations with the primary network 102. The device state data 110 may be state data stored while the communication device 106 performs operations with the primary cloud network. For example, if the IoT device 106a is a mobile device communicating in a CBRS system and the primary network 102 supports a spectrum analysis system (SAS) of the CBRS system, the IoT device 106a may send a heartbeat request 128 to the primary network device 200 of the primary network 102 to indicate that the IoT device 106a is able to communicate with the primary network 102. The network device 200 of the primary network 102 may receive a corresponding heartbeat confirmation signal 126. As such, the network device 200 of the primary network 102 may store the heartbeat confirmation data 118 in the device state data store 212 as device state data 110 that is linked to the IoT device 106a via the corresponding device ID 114, whereby the device state data 110 indicates that the operational instance of the IoT device 106a in the primary network 102 is proper, i.e., the IoT device 106a is properly registered with the web registration service 202.
[0022] In some examples, the secondary network 104 includes a backup network device 300. The backup network device 300 may also be referred to as a fallback network device 300, a backup device 300, or a mirror network device 300. The network device 300 may be one or more servers, such as a web server, that communicates with one or more of the communication devices 106. As such, the backup network device 300 includes data processing hardware 310 and memory hardware 320 that communicates with the data processing hardware 310. The memory hardware 320 may store instructions that, when executed on the data processing hardware 310, cause the data processing hardware 310 to perform operations as described with respect to flowcharts 400, 500, and 600 (FIGS. 4-6). In this example, the backup network device 300 of the secondary network 104 stores or mirrors a subset of the device state data 110 stored by the primary network device 200 in the data store 212 of the primary network 102. A subset of the state data 110 obtained from the primary network 102 is backed up by the backup network device 300 and is illustrated in FIG. 1 as backed up device state data 110. Thus, the network device 300 serves as a backup or fallback device for the subset of the device state data 110 during, for example, a network failure condition 130 associated with the primary network 102 as perceived by the communication device 106. The subset of the state data 110 is provided by the primary network 102 via any suitable mechanism, such as being pushed to or pulled by the secondary network 104 as part of a backup operation associated with a cloud instance of an application running in the cloud. A software application running on the backup device 300 may perform the backup operation.In this example, the secondary network 104 is a smaller cloud network than the cloud network of the primary network 102, thereby reducing the cost and operational complexity of the backup system. Also, the backup device 300 in the secondary network 104 backs up only a subset of the state data 110 maintained by the primary network 102 for each of the devices in communication with the primary network 102, thereby reducing storage costs and operational complexity. For example, the secondary network 104 may not allow the communication device 106 to newly register. That is, in some implementations, the backup device 300 does not run a web registration service.
[0023] The network system 100 further includes a revocation agent 120 (e.g., a heartbeat revocation agent 120 (FIG. 1)), which may be any suitable device authorized to revocation the communication devices 106 with respect to the primary network 102 and the secondary network 104. The revocation agent 120 may provide corresponding revocation data 124, 124a to the primary network device 200 associated with the primary network 102 and / or provide corresponding revocation data 124, 124b to the backup device 300 associated with the secondary network 104. A software service provider, system administrator, or other entity may use the revocation agent 120 to disable (e.g., disable) a particular communication device 106. The revocation data 124 may identify those particular communication devices 106 that should not receive heartbeat confirmation signals 126 from the networks 102, 104 when requested (e.g., via a heartbeat request 128). More specifically, the revocation data 124 instructs the primary network device 200 and / or the backup device 300 not to transmit heartbeat confirmation signals 126 to the particular communication device 106, thereby disabling the ability of that particular communication device 106 to perform a task or operation. The revocation agent 120 may determine that resources required by the communication device 106 to perform a device operation are unavailable to the communication device 106. This may be done, for example, in a CBRS system when the revocation agent 120 determines that a particular frequency or set of frequencies is unavailable from base station 106c for use by communication device 106b. For example, frequencies or particular frequencies used by one or more base stations (e.g., 106c) in the CBRS system may be determined by the system and / or the revocation agent 120 to be in use by government entities and unavailable to non-government devices. The communication device 106b may be prevented from attempting to access those frequencies. Other systems may prevent an Internet of Things (IoT) device 106a from using the primary network 102 if a software update is required, if the owner of the communications device has not complied with contractual agreements related to software use, or based on other criteria.
[0024] The backup device 300 includes memory such as a backup data store 318 that stores a backed-up subset of the device state data 110, including the heartbeat confirmation data 118. The heartbeat confirmation data 118 includes a copy of the valid heartbeat confirmation data 118 obtained from the primary network 102. In some implementations, the invalidation data 124a provided to the primary network device 200 is propagated to the backup device 300 and stored in the backup data store 318. For example, the subset of the state data 110 backed up by the backup network device 300 may include data representing a mapping of data between the communication device and the invalidation agent 120. In some implementations, the invalidation data 124b provided to the backup network device 300 is stored in the backup data store 318. In another example, only the keep-alive signal data 118 (heartbeat confirmation data) is backed up by the secondary network 104. This may allow for a small amount of memory usage, such as in a table format.
[0025] Thus, the backup device 300 of the secondary network 104 backs up only the operational reliability information of the particular communication device in communication with the primary network 102. In one example, only keep-alive signal data, also referred to as heartbeat confirmation data 118, is backed up from the primary network 102. The heartbeat confirmation data 118 is associated with an ongoing communication or task that the device is performing with the primary network 102 and may indicate that the primary network device 200 of the primary network 102 allows the communication device 106 to continue performing the task or operation when a network failure condition 130 exists that prevents communication between the communication device 106 and the primary network device 200. In some implementations, the revocation data 124b is provided directly to the backup device 300 during a network failure condition 130 associated with the primary network 102. The operations described herein provide a kind of If This Then That level of functionality such that the heartbeat deauthorization continues to propagate to revoke the permission that the communication device may continue performing the task or operation during a network failure condition 130 associated with the primary network 102. For example, if the invalidation agent 120 Upon detecting a network failure condition 130 associated with the primary network 102, the invalidation agent 120 may send an invalidation message 122 to the backup device 300. The present invention provides a very simple technique for configuring and processing the heartbeat signal protocol. As described above, the system is configured in one example with a primary service and a heartbeat dedicated backup service. The primary service runs on the cloud infrastructure of the primary network 102, while the heartbeat dedicated service runs on an entirely separate cloud infrastructure, i.e., the secondary network 104, and has the ability to verify operability of the secondary network 104 to the device 106 in response to a network failure condition 130 associated with the primary network 102.
[0026] With reference to FIG. 2 , the network device 200 may execute a web registration service 202, and the communication device 106 may register with the web registration service 202 to receive a heartbeat signal 126 (also referred to as a heartbeat confirmation signal, a keep-alive signal, or simply a heartbeat) that allows the communication device 106 to initiate or continue to perform a task or operation. In the illustrated example, the communication device 106 may send a heartbeat request 128 to the network device 200 and receive a corresponding heartbeat confirmation signal 126. In some implementations, the communication device 106 receives the heartbeat signal 126 continuously (e.g., periodically) and continues to perform a task or operation in response to receiving the heartbeat signal 126. In some examples, for a particular communication device 106 that communicates with the network device 200 (e.g., via communication of a heartbeat request 128 and a corresponding heartbeat confirmation signal 126), the network device 200 records the device state data 110 in a device state data store 212 along with a device identifier (ID) 114 associated with the particular communication device 106. The device ID 114 may uniquely identify the communication device 106. The device state data 110 may include any information related to an operation or task performed by the communication device 106, such as, but not limited to, a payment status, an ability to update organizational metadata, data representing an aggregate calculation of overall environmental health, and / or other suitable data. The device ID 114 may be used, for example, as an index to search for or identify the device state data 110 stored in the data store 212 and associated with a particular communication device 106. The device state data 110 associated with a particular communication device 106 may be updated over time using the device ID 114 as an index. For example, the network device 200 may update the device state data 110 as the communication device 106 continues to perform a task or operation in response to receiving a heartbeat confirmation signal 126 from the network device 200.In some examples, the device state data 110 includes heartbeat confirmation data 118 associated with a heartbeat confirmation signal 126 transmitted by the network device 200 to the communication device 106 to authorize the communication device 106 to perform a task or operation.
[0027] In some implementations, the network device 200 updates the heartbeat confirmation data 118 each time the network device 200 transmits a heartbeat signal 126 to the communication device 106. As such, the heartbeat confirmation data 118 may provide a log of time-stamped heartbeat requests 128 received from the communication device 106 and time-stamped heartbeat signals 126 transmitted to the communication device 106. In the illustrated example, the device state data 110 may reflect the most recent time that the network device 200 permitted the communication device 106 to initiate or continue to perform a task or operation. In some examples, the network device 200 receives an invalidation message 122 from the invalidation agent 120. The invalidation message 122 may include heartbeat invalidation data 124, 124a indicating that the communication device 106 should not receive a heartbeat confirmation signal 126 from the primary network device 200. For example, if the Internet of Things (IoT) device 106a requires a software update to address a potential security vulnerability or pursuant to a contractual agreement, such as the owner of the IoT device 106a obtaining or maintaining a valid software license. If not, the IoT device 106a may be prevented from using the primary network 102. The revocation message 122 may include heartbeat revocation data 124, 124a including an indication of these criteria or other criteria that the communication device 106 should not receive heartbeat confirmation signals 126 from the primary network device 200, if possible. The revocation data 124a may include a device identifier 114 (e.g., device ID 114 (FIG. 1)) that identifies a particular communication device 106 that should not receive heartbeat confirmation signals 126 including heartbeat confirmation data 118 indicating permission by the primary network device 200 (e.g., by the web registration service 202) that the particular communication device 106 may perform a task or operation. Thus, in response to receiving the revocation data l24a included in the revocation message 122 from the revocation agent 120 (e.g., heartbeat revocation agent 120 (FIG. 1)), the network device 200 may refuse to transmit heartbeat confirmation signals 126 to the communication device 106 identified by the revocation data l24a. For example, when the network device 200 receives a heartbeat request 128 from the communication device 106 to perform a task or operation, the network device 200 may determine whether the device state data 110 of the communication device 106 includes invalidation data 124 by querying the data store 212 with the associated device ID 114. If the invalidation data 124 is present, the network device 200 may prevent the communication device 106 from performing the task or operation by refusing to send a corresponding heartbeat confirmation signal 126 to the communication device 106. In some examples, when the network device 200 stops sending the heartbeat confirmation signal 126 to the communication device 106, the network device 200 stops updating the heartbeat confirmation data 118 in the device state data 110. In some examples, the device state data 110 includes the received invalidation data 124a.As such, the network device 200 may be configured to update the device status data 110 with revocation data 124a received from the revocation agent 120 indicating that a particular communication device 106 should no longer receive a heartbeat confirmation signal 126 from the network device 200.
[0028] With reference to FIG. 3, the backup device 300 may execute a backup controller 302 and a confirmation controller 304. The confirmation controller 304 may also be referred to as a backup confirmation controller 304 or a heartbeat confirmation controller 304. In some examples, a network failure condition 130 (FIG. 1) associated with the primary network 102 may occur as recognized by the communication device 106. For example, the communication device 106 may be unable to connect to the primary network 102 or may not receive a heartbeat confirmation 126 within a threshold period of time after sending a heartbeat request 128. The network failure condition 130 associated with the primary network 102 may be caused by a power outage affecting the primary network 102, or a damaged communication cable or fiber, or other obstruction that prevents communication between the communication device 106 and the primary network 102. In some examples, the network failure condition 130 is due to the communication device 106 being unable to communicate with the primary network 102 despite the primary network 102 being otherwise operational. Other causes of the network failure condition 130 may also apply. In some examples, if the communication device 106 fails to receive a heartbeat confirmation 126 within a threshold period, the communication device 106 attempts to re-register with the web registration service 202. In these examples, a network failure state 130 may be established if the communication device 106 fails to re-register with the web registration service 202 within a connection timeout period. Because the communication device 106 may not receive a heartbeat confirmation signal 126 from the primary network 102 during the network failure state 130, the communication device 106 ceases performing a task or operation that is conditioned on receiving a periodic heartbeat confirmation signal 126. In some examples, during the network failure state 130 associated with the primary network, the communication device 106 may not re-register with the primary network 102. 300。 In the illustrated example, during the network failure condition 130, the communication device 106 transmits the heartbeat request 128 to the backup heartbeat confirmation controller 304 of the backup device 300 and receives a corresponding heartbeat confirmation signal 126 (also called a keep-alive signal) that allows the communication device 106 to continue performing a task or operation despite the communication device 106 being unable to communicate with the primary network device 200 of the primary network 102. Here, before sending the heartbeat confirmation signal 126 to the communication device 106, the backup heartbeat confirmation controller 304 may first query the backup controller 302 to determine whether the backed-up device state data 110 associated with the communication device 106 indicates that the communication device 106 is authorized to receive the heartbeat confirmation signal 126.
[0029] In the illustrated example, the device heartbeat backup controller 302 receives at least a subset of the device state data 110 from the primary network device 200 of the primary network 102. The subset of the state data 110 may include the heartbeat confirmation data 118, the device ID 114 associated with the communication device 106, and any invalidation data 124a received by the primary network registered device 200 (e.g., the primary network device 200 (FIG. 1)) from the heartbeat invalidation agent 120. In some examples, the received state data 110 (e.g., the device state data 110 (FIG. 1)) includes all state data 110 associated with the communication device 106 stored in the device state data store 212 of the primary network 102 as described above. In some examples, the received state data 110 includes only the heartbeat confirmation data 118. Other subsets of the state data 110 may be received by the backup controller 302. In some implementations, while the primary network device 200 is sending a heartbeat confirmation signal 126 to the communication device 106, the primary network device 200 pushes the device state data 110 to the backup controller 302. In these implementations, the primary network device 200 may periodically push the device state data 110 associated with the communication device 106 to the backup controller 302 as the state data 110 changes, or under other suitable circumstances. In further implementations, the backup controller 302 of the backup device 300 pulls the device state data 110 from the primary network 102 during a pull operation. For example, the backup controller 302 may pull the device state data 110 from the primary network device 200 as part of a scheduled backup operation and / or in response to the backup confirmation controller 304 receiving a heartbeat request 128 from the communication device.For example, the backup controller 302 may pull a subset of the state data 110 of one or more communication devices 106 by querying the primary network device 200 with the associated device ID(s) 114. In some examples, the backup controller 302 backs up the device state data 110 received from the primary network device 200 to a backup data store 318. Similar to the device state data store 212 of FIG. 2, the backup data store 318 may index the received device state data 110 stored in the backup data store 318 with the device ID 114 that identifies the communication device 106 associated with the device state data 110. In one example, the backup device 300 includes a lookup table indexed by the device ID 114. Other techniques for storing, indexing, searching, and retrieving the received device state data 110 from the backup data store 318 are possible.
[0030] As described above with reference to FIG. 2, the received device state data 110 may reflect the most recent time that the network device 200 permitted the communication device 106 to initiate or continue to execute a task or operation. Thus, the received device state data 110 stored in the backup data store 318 may reflect the most recent time that the network device 200 permitted the communication device 106 to initiate or continue to execute a task or operation. Here, the device state data 110 received by the backup controller 302 may further include heartbeat disable data 124, 124a previously received by the primary network device 200 of the primary network 102 in an disable message 122 from the disable agent 120. That is, the device heartbeat backup controller 302 may receive the disable data 124, 124a indirectly via the primary network 102, rather than directly from the heartbeat disable agent 120. Thus, the received device state data 110 stored in the backup data store 318 may reflect an indication that the communication device 106 should not receive a heartbeat confirmation signal 126. In some examples, the backup controller 302 receives the invalidation message 122 directly from the invalidation agent 120. The invalidation message 122 may include heartbeat invalidation data 124, 124b (e.g., invalidation data 124, 124b (FIG. 1)) indicating that the communication device 106 should not receive a heartbeat confirmation signal 126 from the backup confirmation controller 304 of the secondary network 104 in response to the communication device 106 sending a heartbeat request 128 to the backup confirmation controller 304. The invalidation data 124b may include a device ID 114 identifying a particular communication device 106 that should not receive a heartbeat confirmation signal 126 including heartbeat confirmation data 118 that would otherwise allow the particular communication device 106 to perform a task or operation.The invalidation agent 120 may provide the corresponding invalidation data 124, 124a to a primary network device 200 associated with the primary network 102 and / or may provide the corresponding invalidation data 124, 124b to a backup controller 302 associated with the secondary network 104. In some examples, the invalidation agent 120 sends an invalidation message 122 to a backup device 300 of the secondary network 104 only if a network failure condition 130 exists. For example, when the invalidation agent 120 detects or otherwise learns of a network failure condition 130 that prevents communication between a particular communication device 106 and a primary network device 200 of the primary network 102, the invalidation agent 120 may send an invalidation message 122 including the invalidation data 124b to the backup controller 302. In some examples, in response to receiving an invalidation message 122 associated with a particular communication device 106, the backup controller 302 updates the device state data 110 stored in the backup data store 318 to include invalidation data 124b associated with the communication device 106, e.g., indexed by device ID 114. In the example shown, the heartbeat invalidation agent 120 may use the invalidation data 124 associated with the communication device 106 to cause the backup controller 302 of the backup device 300 to not send a heartbeat validation signal during a network failure condition 130 associated with the primary network by invalidating all heartbeat validation data 118 associated with the communication device 106.
[0031] In some examples, in response to receiving a heartbeat request 128 from the communication device 106, the backup heartbeat confirmation controller 304 determines whether to send a heartbeat confirmation 126 to the communication device 106 to allow the communication device 106 to initiate or continue executing a task or operation. The heartbeat confirmation controller 304 determines whether to send a heartbeat confirmation 126 to the communication device 106 to allow the communication device 106 to initiate or continue executing a task or operation based on the backed up device state data 110 stored in the backup data store 318. In response to the request, the backup controller 304 may determine whether to send a heartbeat confirmation signal 126 to the communication device 106. Here, the backup controller 304 may retrieve the backed-up device state data 110 from the backup data store 318 using the associated device ID 114 by querying the backup controller 302. In some examples, the backup heartbeat confirmation controller 304 provides the heartbeat request 128 and the associated device ID 114 to the backup controller 302. The backup controller 302 may retrieve the backed-up device state data 110 using, for example, the associated device ID 114 and provide the backed-up device state data 110 to the backup heartbeat confirmation controller 304. In some examples, the backup heartbeat confirmation controller 304 retrieves the backed-up device state data 110 directly from the backup data store 318. The backup heartbeat confirmation controller 304 may retrieve the backed-up device state data 110 using other techniques. Alternatively, the backup controller 302 may determine that the retrieved backed-up device state data 110 includes the heartbeat confirmation data 118 without the invalidation data 124 and provide a signal to the backup confirmation controller 304 indicating that the communications device 106 should receive the heartbeat confirmation signal 126. In some examples, the backup controller 302 provides the retrieved backed-up device state data 110 to the backup heartbeat confirmation controller 304, which determines whether to send the heartbeat confirmation signal 126 to the communications device 106 based on the backed-up device state data 110. For example, if the device state data 110 includes the heartbeat confirmation data 118 and the invalidation data 124 is not present, the backup confirmation controller 304 may determine to send the heartbeat confirmation signal 126 to the communications device 106.As discussed above, the heartbeat confirmation data 118 may reflect the most recent time that the network device 200 authorized the communications device 106 to initiate or continue executing a task or operation. In some examples, if the heartbeat confirmation data 118 in the backup data store 318 indicates that the network device 200 previously authorized the communications device 106 to initiate or continue executing a task or operation, the backup heartbeat confirmation controller 304 may determine to send a heartbeat confirmation 126 to the communications device 106. If the backed-up device state data 110 does not include heartbeat confirmation data 118 associated with the communications device 106, the backup heartbeat confirmation controller 304 may determine not to send a heartbeat confirmation 126 to the communications device 106. Other techniques for determining whether to send a heartbeat confirmation 126 to the communications device 106 based on the heartbeat confirmation data 118 are possible. In some examples, when the backup heartbeat verification controller 304 sends a heartbeat verification signal 126 to the communication device 106, the backup heartbeat verification controller 304 updates the heartbeat verification data 118 associated with the communication device 106 in the backup data store 318.
[0032] The backed-up device state data 110 may include invalidation data 124 received indirectly by the backup controller 302 via the primary network device 200 of the primary network 102 as part of the device state data 110 received by the backup controller 302 during a push or pull operation, or directly from the invalidation agent 120, and stored in the backup data store 318. Similarly, if the heartbeat invalidation agent 120 provides invalidation data 124b to the controller 302 while the controller 302 is performing a retrieval operation of the backed-up device state data 110, the backup controller 302 need only append the invalidation data 124 to the backed-up device state data 110 being sent to the backup verification controller 304. In some examples, based on the invalidation data 124, the backup verification controller 304 may update the invalidation data 124 (e.g., the heartbeat invalidation agent 120) to include the invalidation data 124b. The backup verification controller 304 may refuse to send a heartbeat confirmation signal 126 to a communication device 106 identified by the heartbeat invalidation data 124 (FIG. 1). For example, when the backup verification controller 304 receives a heartbeat request 128 from a communication device 106 to perform a task or operation, the backup verification controller 304 (or the backup controller 302) may determine whether the device state data 110 associated with the communication device 106 includes invalidation data 124 by querying the backup data store 318 using the device ID 114. If invalidation data 124 is present, the backup verification controller 304 may revoke permission for the communication device 106 to perform the device operation and may withhold or refuse to send the corresponding heartbeat confirmation signal 126 to the communication device 106, thereby preventing the communication device 106 from performing the task or operation.
[0033] 4 is a flowchart of an example of an operation configuration for a method 400 of providing operational reliability of a communication device 106 adapted to communicate with a primary network 102. In an operation 402, if a network failure condition 130 exists that prevents communication between the communication device 106 and a network device 200 (e.g., primary network device 200 (FIG. 1)) of a first network 102 (e.g., primary network 102 (FIG. 1)), the method 400 includes receiving a heartbeat request 128 from the communication device 106 requesting permission for the communication device 106 to perform a device operation in the data processing hardware 310 of the second network 104 (e.g., backup network 104 or secondary network 104 (FIG. 1)). In some implementations, the communication device 106 is configured to transmit the heartbeat request 128 to the network device 200 of the first network 102 and receive a corresponding heartbeat confirmation signal 126 from the network device 200 if the network failure condition 130 does not exist. In some scenarios, a network failure condition 130 exists if the communication device 106 does not receive a heartbeat confirmation signal 126 from the network device 200 of the first network 102 within a threshold period of time after sending a heartbeat request 128 to the network device 200.
[0034] At operation 404, the method 400 includes the data processing hardware 310 obtaining the device state data 110 associated with the communication device 106. For example, the data processing hardware 310 may receive the device state data 110 directly or indirectly from the network device 200 of the first network 102. For example, when communication between the communication device 106 and the network device 200 is not degraded (e.g., no failure condition 130 exists), the network device 200 may periodically push the device state data 110 to the data processing hardware 310, which may store the device state data 110 in the backup data store 318. Thus, the data processing hardware 300 may access the backup data store 318 during the network failure condition 130 to retrieve the device state data 110 stored in the backup data store 318 for the particular communication device 106. Additionally or alternatively, the data processing hardware 310 may perform a pull operation to obtain the device state data 110 from the network device 200. Here, the data processing hardware 310 may perform the pull operation by querying the network device 200 to retrieve the device state data 110 for the particular communication device 106. The query may include a device identifier 114 that identifies the communication device 106 such that the network device 200 can retrieve the associated device state data 110 from the data store 212.
[0035] At operation 406, the method 400 continues by the data processing hardware 310 controlling the communication device The method 400 may include determining whether the communications device 106 is authorized to perform the device operation based on the device state data 110 associated with the communications device 106. For example, if the device state data 110 includes heartbeat confirmation data 118 indicating permission from the network device 200 of the first network 102 that the communications device 106 may perform the device operation, then the method 400 may determine that the communications device 106 is authorized to perform the device operation. However, if the device state data 110 does not include the heartbeat confirmation data 118, then the method 400 may determine that the communications device 106 is not authorized to perform the device operation. Furthermore, if the device state data 110 includes the revocation data 124 despite having the heartbeat confirmation data 118, then the method 400 may determine that the communications device 106 is not authorized to perform the device operation.
[0036] At operation 408, the method 400 includes the data processing hardware 310 sending a heartbeat confirmation signal 126 to the communications device 106 if the communications device 106 is authorized to perform the device operation, where the heartbeat confirmation signal 126 authorizes the communications device 106 to perform the device operation. Alternatively, in a scenario in which the communications device 106 is not authorized to perform the device operation (e.g., there is no heartbeat confirmation data 118 and / or the device state data 110 includes disabling data 124), the data processing hardware 310 may prevent the communications device 106 from performing the device operation by withholding sending the heartbeat confirmation signal 126 to the communications device 106.
[0037] An example of the operation of the backup device 300 is described with reference to Figures 5 and 6. In some implementations, the device heartbeat backup controller 302 backs up a subset of the device state data 110 from the primary network 102, including the heartbeat confirmation data 118 stored as device state data 110, for one or more communication devices 106, 106a-106e using the primary network 102. The backup occurs by storing the subset of the state data 110 in the data store 318 for each device identifier 114. For example, a data store record may include the device identifier 114 of each of the communication devices 106a-106e along with the corresponding heartbeat confirmation data 118 that the primary network 102 stored as device state data 110. A network failure condition 130 may occur, such as an IoT device 106a being unable to connect to the primary network 102, as indicated by an IP address failure due to a DNS attempt by the device making a heartbeat request 128 to the primary network 102 to connect to the primary network 102.
[0038] In one example, the network failure condition 130 is indicated by a device, such as a communication device making an Internet Protocol address request to the secondary network 104 via DNS, because the communication device was unable to receive a proper response when attempting to connect to the primary network 102 via DNS attempt after being connected to the secondary network 104 (backup device) 300. The IoT device 106a issues a heartbeat request 128 to the secondary network 104. In response to the heartbeat request from the device, the backup heartbeat verification controller 304 provides a heartbeat verification 126 to the communication device 106 based on the backed up heartbeat verification data 118 associated with the heartbeat request 128 from the device. In one example, the backup heartbeat verification controller 304 searches the device state data 110 in the backup data store 318 using the device ID 114 submitted by the IoT device 106a as part of the heartbeat request 128. The heartbeat verification controller 304 may determine whether the received device ID 114 matches the device ID 114 stored as part of the subset of the device state data 110. If the device ID 114 is backed up, then the communication device 106 returns a heartbeat confirmation 126 with the corresponding backed up heartbeat confirmation data 118. The communication device can then continue with its tasks, such as continuing to execute in-memory programs that do not require the primary network 102 to be operational.
[0039] 5 and 6, if the revocation agent 120 is used in the system 100, a software service provider, system administrator, or other entity may use the revocation agent 120 to designate a particular communication device using a device identifier 114 to indicate that the communication device should not receive a heartbeat confirmation 126 from a network (e.g., the primary network 102 or the secondary network 104) in response to a heartbeat confirmation request 128 from the communication device 106. This may be done, for example, if the revocation agent 120 determines that a particular frequency or set of frequencies is unavailable from base station 106c for use by communication device 106b. The communication device 106b may be prevented from attempting to access the particular frequency. This may be preferred in a CBRS-type system. For example, a frequency or particular frequency used by one or more base stations (e.g., 106c) in the CBRS system may be determined by the system and / or the revocation agent 120 to be unavailable to non-governmental devices because it is in use by a government agency or device. For example, if a particular frequency is not in use by a base station, the frequency is deemed available for public use by user equipment, and a heartbeat confirmation 126 may then be sent from the secondary network 104 to each IoT device 106a. Other systems may prevent Internet of Things (IoT) devices from using the primary network 102 if a software update is required, if the owner of the communication device is not in compliance with contractual agreements made related to software use, or based on other criteria. Digital policy certificates or other mechanisms may be used to determine when to send revocation data 124a and / or 124b to the respective networks. Also, the operation is described in connection with the use of multiple end user communication devices 106. However, the system may be used with any suitable number of end user communication devices 106 as desired.Additionally, the description of Figures 5 and 6 is provided in the context of the subset of state data 110 being only the heartbeat confirmation data 118 associated with each of the multiple devices using the primary network 102, as opposed to other examples in which the subset of state data includes more than the heartbeat confirmation data 118.
[0040] As shown in block 502, the method 500 includes the backup device 300 receiving only heartbeat confirmation data 118 (and corresponding device IDs 114) associated with a plurality of devices using the primary network 102 from the primary network device 200. The backed up heartbeat confirmation data 118 is a subset of the device state data 110 that the server 200 maintains for each device. As shown in block 504, the method includes backing up only the heartbeat confirmation data 118 for the plurality of devices using the primary network 102. This is done by the device heartbeat backup controller 302 backing up only the heartbeat confirmation data 118 from the primary network 102. As shown in block 506, the method includes providing a heartbeat confirmation 126 based on the backed up heartbeat confirmation data 118 to at least one of the plurality of devices in response to a network failure condition 130 and in response to a heartbeat request 128 from at least one of the plurality of devices. This is done by the backup heartbeat confirmation controller 304 in this example.
[0041] As shown in block 508, an invalidation message from the invalidation agent 120 The invalidation agent 120 receives invalidation data 124b for the secondary network 104, such as via 122, and in response to a network failure condition 130 and in response to a heartbeat request 128 from at least one device, denies a heartbeat confirmation 126 to the requesting device if the invalidation data 124b indicates that the communication device 106 is to be disabled. In other words, the invalidation message 122 can come at any time. If the invalidation message 122 is sent after a heartbeat confirmation 126 has already been sent, the subsequent heartbeat request 128 is denied because the invalidation agent 120 has indicated with the invalidation data 124b that it no longer wants the communication device to have a heartbeat confirmation 126.
[0042] In another example, upon the first heartbeat request 128 from a device after a network failure condition 130 occurs, if the invalidation data 124b indicates that the communication device is disabled, then the heartbeat confirmation 126 is not sent and the backup heartbeat confirmation controller 304 does not issue the heartbeat confirmation 126. In one example, the invalidation data 124 is stored as part of the data record for each device such that the backed-up device state data includes the device identifier 114 for each subject device, the corresponding backed-up heartbeat confirmation data 118 from the primary network 102, and any invalidation data 124b received for the particular communication device from the invalidation agent 120. Thus, the invalidation data 124b in one example includes the device ID 114 plus data indicating whether the communication device 106 should be disabled. Thus, the backup device 300 denies the heartbeat confirmation 126 for the communication device making the heartbeat request 128 based on the invalidation message 122 from the invalidation agent 120.
[0043] 6, from a system perspective, as shown in block 602, the method 600 includes a device registering or connecting to the primary network 102 via a DNS address. As shown in block 604, if the connection is successful, the method proceeds to block 606, where the server 200 (e.g., the primary network device 200 (FIG. 1)) updates the heartbeat OK (heartbeat confirmation data) 118 table stored as device status data 110. This may include, for example, placing data in a memory table, database record, or other format to indicate that a heartbeat confirmation 126 was sent to the device that requested the heartbeat. The server 200 also provides the heartbeat confirmation data 118 to the secondary network 104 as part of a backup operation. The heartbeat confirmation data 118 is provided continuously by the primary network 102 as long as the primary network 102 is operating properly. However, if there is a network failure condition 130 associated with the primary network 102 as recognized by a communication device 106, such as IoT device 106a, the communication device attempts to connect to the secondary network 104, for example, via DNS, as shown in block 608. As shown in block 610, the backup device 300, and in this example the backup heartbeat confirmation controller 304, checks the backed up state data in the backup data store 318 based on the device ID 114 to determine whether the backed up data indicates that the most recently stored heartbeat by the primary network 102 indicates that a heartbeat confirmation 126 was provided by the device by the primary network 102 prior to the network failure condition 130. As shown in block 612, the backup network device 300 further checks a database record associated with the device to see if the invalidation agent 120 has sent an invalidation message 122 for the device. If so, the secondary network 104 denies the heartbeat confirmation 126 to the requesting communication device 106, as shown in block 614.However, if the revocation agent 120 has not indicated that the communication device 106 should be revoked, then the revocation agent 120 may proceed to revoking the communication device 106, as shown in block 616. The backup network device 300 responds to communication devices requesting a heartbeat from the secondary network 104 with a heartbeat confirmation 126 based on the backed up heartbeat confirmation data 118 .
[0044] Among other advantages, by using a second, smaller cloud system that maintains a copy of valid heartbeat information, such as in a table, the second system can have maximum isolation without a completely rewritten software service. The secondary network 104 and backup device 300 allow the entire system to maintain a consistent view of the devices in the primary network 102 without a complete constant copy of the data at all times and without a smaller independent software service to ensure reliability. In one example, there is a static page handler that only remembers the most important aspect of the operation, namely providing a heartbeat confirmation signal 126 to the device. The secondary network 104 only needs to be updated with the heartbeat confirmation data 118 by the primary network 102, making maintaining a consistent state of the devices much simpler than traditional methods. The device ID 114 and the corresponding heartbeat confirmation data 118 herein may be the same data. For example, if a table is used, the presence of the device ID 114 in the table itself can be the heartbeat confirmation data 118 for a particular communication device.
[0045] 7 is a schematic diagram of an example of a computing device 700 that may be used to implement the systems (e.g., network device 200 and backup network device 300) and methods (e.g., methods 400, 500, 600) described herein. Computing device 700 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, mobile computing devices, wearable computing devices (e.g., headsets and / or watches), servers, blade servers, mainframes, and other suitable computers. The components illustrated herein, their connections and relationships, and their functions are intended to be merely exemplary and are not intended to limit the implementation of the inventions described and / or claimed herein.
[0046] Computing device 700 includes a processor 710 (also referred to as processing hardware or data processing hardware), a memory 720 (also referred to as memory hardware), a storage device 730, a high-speed interface / controller 740 that connects to memory 720 and a high-speed expansion port 750, and a low-speed interface / controller 760 that connects to a low-speed bus 770 and storage device 730. Each of components 710, 720, 730, 740, 750, and 760 are interconnected using various buses and may be mounted on a common motherboard or otherwise as appropriate. Processor 710 may process instructions for execution within computing device 700, including instructions stored in memory 720 or on storage device 730 for displaying graphical information for a graphical user interface (GUI) on an external input / output device, such as a display 780 coupled to high-speed interface 740. In other implementations, multiple processors and / or multiple buses may be used as appropriate, along with multiple memories and multiple types of memories. Also, multiple computing devices 700 may be connected, with each device providing a portion of the required operations (eg, as a server bank, a group of blade servers, or a multi-processor system).
[0047] The memory 720 stores information non-transitoryly within the computing device 700. The memory 720 may be a computer-readable medium, a volatile memory unit, or a non-volatile memory. The non-transient memory 720 may be a memory unit. The non-transient memory 720 may be a physical device used to temporarily or permanently store programs (e.g., sequences of instructions) or data (e.g., program state information) for use by the computing device 700. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electronically erasable programmable read-only memory (EEPROM) (e.g., commonly used for firmware such as boot programs). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and disks or tapes.
[0048] The storage device 730 can provide mass storage for the computing device 700. In some implementations, the storage device 730 is a computer-readable medium. In various different implementations, the storage device 730 can be a floppy disk device, a hard disk device, an optical disk device or a tape device, a flash memory or other similar solid-state memory device, or an array of devices (including a storage area network or other configuration of devices). In still other implementations, a computer program product is tangibly embodied in an information carrier. The computer program product includes instructions that, when executed, perform one or more methods, such as the methods described above. The information carrier is a computer-readable or machine-readable medium, such as the memory 720, the storage device 730, or the memory on processor 710.
[0049] The high-speed controller 740 manages bandwidth-intensive operations for the computing device 700, while the low-speed controller 760 manages less bandwidth-intensive operations. Such duty allocation is merely exemplary. In some implementations, the high-speed controller 740 is coupled to the memory 720, coupled to the display 780 (e.g., via a graphics processor or accelerator), and coupled to a high-speed expansion port 750 that may accept various expansion cards (not shown). In some implementations, the low-speed controller 760 is coupled to the storage device 730 and to a low-speed expansion port 790. The low-speed expansion port 790, which may include various communication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet), may be coupled to one or more input / output devices (such as a keyboard, pointing device, scanner, or networking device (such as a switch or router)) via, for example, a network adapter.
[0050] The computing device 700 may be implemented in a number of different forms, as shown in the figure: for example, it may be implemented as a standard server 700a or multiples of a cluster of such servers 700a, as a laptop computer 700b, or as part of a rack server system 700c.
[0051] Various implementations of the systems and techniques described herein may be realized in digital electronic and / or optical circuitry, integrated circuits, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations in the form of one or more computer programs executable and / or interpretable on a programmable system including at least one programmable processor, which may be special purpose or general purpose, and storage. The system is coupled to transmit and receive data and instructions to and from at least one input device and at least one output device.
[0052] These computer programs (also known as programs, software, software applications or codes) include machine instructions for a programmable processor and may be implemented in the form of high-level procedural programming languages and / or object-oriented programming languages and / or assembly / machine languages. The terms "machine-readable medium" and "computer-readable medium" herein shall mean any computer program product, non-transitory computer-readable medium, apparatus and / or device (e.g., magnetic disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as a machine-readable signal. The term "machine-readable signal" shall mean any signal used to provide machine instructions and / or data to a programmable processor.
[0053] The processes and logic flows described herein can be executed by one or more programmable processors that execute one or more computer programs to perform functions by operating on input data and generating output. These processes and logic flows can also be executed by special purpose logic circuitry (e.g., FPGAs (field programmable gate arrays) or ASICs (application specific integrated circuits)). Examples of processors suitable for executing computer programs include general purpose and special purpose microprocessors, as well as any one or more processors of any type of digital computer. Generally, a processor receives instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also includes one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or is operatively coupled to receive data from, transmit data to, or transmit data to, one or more mass storage devices. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, examples of which include semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
[0054] To provide for user interaction, one or more aspects of the disclosure can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touch screen) for displaying information to the user, and optionally a keyboard and pointing device (e.g., a mouse or trackball) by which the user can provide input to the computer. Other types of devices may also be used to provide for user interaction. For example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback), and input from the user may be received in any form, including acoustic input, speech input, or tactile input. The computer may also send and receive documents to a device used by the user, for example, in response to a request received from a web browser, to a user's client device. The user can interact with the device by sending web pages to the web browser on the device.
[0055] Several implementations have been described. However, it will be understood that various modifications may be made without departing from the spirit and scope of the present disclosure. Accordingly, other implementations are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results.
Claims
1. A method performed by a communications device, a first network device of a first network, and a second network device of a second network, comprising: the communications device sending a first heartbeat request to the first network device requesting a first heartbeat confirmation signal from the first network device; determining that a fault condition exists after the communications device fails to receive the first heartbeat confirmation signal from the first network device for a threshold period of time; and transmitting, in response to the communications device determining that the failure condition exists, a second heartbeat request to the second network device requesting a second heartbeat confirmation signal from the second network device, the second network being different from the first network, the method further comprising: receiving, by the communications device, the second heartbeat confirmation signal from the second network device; and performing a device action by the communications device in response to receiving the second heartbeat confirmation signal; sending the second heartbeat request comprises requesting permission to perform the device operation; the second heartbeat request is configured to cause the second network device to determine that the communications device is authorized to perform the device operation based on device state data associated with the communications device; the first network device, pushing the device state data associated with the communications device prior to the failure condition to the second network device; or transmitting the device state data associated with the communications device in response to a pull action by the second network device; The method is configured to perform at least one of the following:
2. The device status data includes: A device identifier that identifies the communication device; Disabling data that disables the ability of the communications device to perform the device operation; or Payment status, The method of claim 1 , comprising at least one of:
3. The method of claim 1 , wherein the device state data includes heartbeat confirmation data indicating permission from the first network device of the first network that the communications device may perform the device operation.
4. The method of any one of claims 1 to 3, wherein the fault condition comprises a network fault condition that prevents communication between the communication device and the first network device on the first network.
5. The method further comprises: the communications device sending a third heartbeat request to the second network device requesting a third heartbeat confirmation signal from the second network device; and ceasing execution of the device operation after the communications device has failed to receive the third heartbeat confirmation signal from the second network device for the threshold period.
6. The method further comprises: the communications device sending a third heartbeat request to the second network device requesting a third heartbeat confirmation signal from the second network device; receiving, by the communications device, the third heartbeat confirmation signal from the second network device; The method of any one of claims 1 to 4, comprising the communications device continuing to perform the device operation in response to receiving the third heartbeat confirmation signal.
7. The method of any one of claims 1 to 6, further comprising the communications device registering with the first network device of the first network to receive a heartbeat confirmation signal before sending the first heartbeat request to the first network device of the first network.
8. 1. A system comprising: A communication device; a first network device in a first network; a second network device of the second network; The communication device includes: sending a first heartbeat request to the first network device requesting a first heartbeat confirmation signal from the first network device; determining that a fault condition exists after failing to receive the first heartbeat confirmation signal from the first network device for a threshold period of time; In response to determining that the failure condition exists, transmitting a second heartbeat request to the second network device requesting a second heartbeat confirmation signal from the second network device, the second network being different from the first network, the communications device: receiving the second heartbeat confirmation signal from the second network device; performing a device action in response to receiving the second heartbeat confirmation signal; sending the second heartbeat request comprises requesting permission to perform the device operation; the second heartbeat request is configured to cause the second network device to determine that the communications device is authorized to perform the device operation based on device state data associated with the communications device; The first network device is pushing the device state data associated with the communications device prior to the failure condition to the second network device; or transmitting the device state data associated with the communications device in response to a pull action by the second network device; The system is configured to perform at least one of the following:
9. The device status data includes: A device identifier that identifies the communication device; Disabling data that disables the ability of the communications device to perform the device operation; or Payment status, The system of claim 8 , comprising at least one of:
10. The system of claim 8 , wherein the device state data includes heartbeat confirmation data indicating permission from the first network device of the first network that the communications device may perform the device operation.
11. The system of any one of claims 8 to 10, wherein the fault condition comprises a network fault condition that prevents communication between the communication device and the first network device on the first network.
12. The communication device transmits a third heartbeat request to the second network device, requesting a third heartbeat confirmation signal from the second network device. The system of any one of claims 8 to 11, wherein the communications device stops executing the device operation after failing to receive the third heartbeat confirmation signal from the second network device for the threshold period.
13. The communications device according to claim 12, further comprising: a third heartbeat request for transmitting a third heartbeat confirmation signal from the second network device to the second network device; the communications device receiving the third heartbeat confirmation signal from the second network device; The system of any one of claims 8 to 11, wherein the communications device continues to perform the device operation in response to receiving the third heartbeat confirmation signal.
14. A system as described in any one of claims 8 to 13, wherein the communications device registers with the first network device to receive a heartbeat confirmation signal before sending the first heartbeat request to the first network device of the first network.
15. A program causing the communication device, the first network device, and the second network device to execute the method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Method and system for client recovery strategies in redundant server configurations
JP2013544408A
Method and apparatus for ensuring continuous reliable device operation in a cloud degraded mode
JP2022504548A
