WO2023231993A1 - 边缘设备的自愈方法、装置、电子设备及存储介质 - Google Patents
边缘设备的自愈方法、装置、电子设备及存储介质 Download PDFInfo
- Publication number
- WO2023231993A1 WO2023231993A1 PCT/CN2023/096963 CN2023096963W WO2023231993A1 WO 2023231993 A1 WO2023231993 A1 WO 2023231993A1 CN 2023096963 W CN2023096963 W CN 2023096963W WO 2023231993 A1 WO2023231993 A1 WO 2023231993A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- edge device
- edge
- cluster
- self
- healing
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 230000002159 abnormal effect Effects 0.000 claims abstract description 48
- 230000036541 health Effects 0.000 claims abstract description 4
- 230000003862 health status Effects 0.000 claims description 73
- 238000004590 computer program Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 46
- 238000012423 maintenance Methods 0.000 description 14
- 238000010586 diagram Methods 0.000 description 12
- 230000007246 mechanism Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 6
- 238000012544 monitoring process Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000005856 abnormality Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 238000004364 calculation method Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000013024 troubleshooting Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000012384 transportation and delivery Methods 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 239000006227 byproduct Substances 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000035876 healing Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
Definitions
- One or more embodiments of this specification relate to the field of computer technology, and in particular, to a self-healing method, device, electronic device, and storage medium for an edge device.
- an edge device is a physical device located at a remote location at the edge of the network. Because real-life electronic terminals (such as cameras, sensors, etc.) often generate a large amount of data, uploading all the data to the cloud will inevitably cause huge pressure on the cloud; in order to To share the pressure from the cloud, edge devices have emerged.
- the edge device can be responsible for data calculation and storage within its own scope. The edge device then uploads the processed data to the cloud, thereby achieving cloud-edge collaboration, that is, close collaboration between the cloud and the edge. To maximize the application value of cloud computing and edge computing.
- one or more embodiments of this specification provide a self-healing method, device, electronic device, and storage medium for an edge device.
- a self-healing method for edge devices is proposed.
- the method is applied to a cloud server.
- the cloud server maintains an edge device information collection of edge device clusters and a collection of edge device information for the edge device cluster.
- Task allocation of edge devices included in the collection; the method includes:
- a self-healing method for an edge device is proposed.
- the method is applied to a second edge device in an edge device cluster.
- the method includes:
- the self-healing instruction is issued by the cloud server according to the maintained health status of the first edge device in the edge device cluster when the health status of the first edge device in the edge device cluster is abnormal.
- the second edge device is generated after determining the second edge device based on the edge device information set and the task allocation situation of the first edge device;
- a self-healing device for an edge device is proposed.
- the device is applied to a cloud server.
- the cloud server maintains an edge device information collection of an edge device cluster and a set of edge device information for the edge device.
- Task distribution of edge devices included in the collection; the devices include:
- a health status determination unit configured to determine the health status of edge devices included in the edge device cluster
- the second edge device determining unit is configured to determine the edge device cluster from the edge device cluster based on the edge device information set and the task allocation situation of the first edge device when the health status of the first edge device is abnormal.
- An instruction issuing unit is configured to issue a self-healing instruction to the edge device cluster, where the self-healing instruction is used to instruct the second edge device to take over a task pre-assigned to the first edge device.
- a self-healing device for an edge device is proposed.
- the device is applied to a second edge device in an edge device cluster.
- the device includes:
- the acquisition unit is configured to acquire a self-healing instruction issued by the cloud server.
- the self-healing instruction is generated by the cloud server according to all maintained data when the health status of the first edge device in the edge device cluster is abnormal.
- the second edge device is generated after the edge device information set of the edge device cluster and the task allocation situation of the first edge device are determined;
- a takeover unit configured to take over tasks pre-assigned to the first edge device according to the self-healing instruction.
- an electronic device including:
- Memory used to store instructions executable by the processor
- the processor executes the steps of the method described in the first aspect or the second aspect by running the executable instructions.
- a computer-readable storage medium on which computer instructions are stored. When the instructions are executed by a processor, the method described in the first or second aspect is implemented. A step of.
- this specification provides a self-healing solution for edge devices.
- the cloud server maintains the edge device information set of the edge device cluster and the task allocation for the edge devices included in the set, so that the cloud server can determine the The health status of the edge devices included in the edge device cluster, and when the health status of the first edge device is abnormal, the cloud issues a self-healing instruction, so that the second edge device takes over the task execution of the first edge device, and then Realizing the self-healing of edge devices can ensure that tasks on edge devices can be executed smoothly and continuously even if operation and maintenance personnel do not go to the site for maintenance, ensuring the normal operation of tasks.
- Figure 1 is a schematic architectural diagram of a self-healing system for edge devices provided in an exemplary embodiment
- Figure 2 is a flow chart of a self-healing method for edge devices provided by an exemplary embodiment
- Figure 3 is a schematic diagram of a neighbor edge device reporting provided by an exemplary embodiment
- Figure 4 is a schematic diagram of a main edge device reporting provided by an exemplary embodiment
- Figure 5 is a schematic diagram of a road parking management device provided by an exemplary embodiment
- Figure 6 is a schematic structural diagram of a road parking management device provided by an exemplary embodiment
- Figure 7 is a flow chart of a self-healing method for edge devices provided by an exemplary embodiment
- Figure 8 is a schematic structural diagram of a device provided by an exemplary embodiment
- Figure 9 is a block diagram of a self-healing device for an edge device provided by an exemplary embodiment
- Figure 10 is a block diagram of a self-healing device for an edge device provided by an exemplary embodiment.
- the steps of the corresponding method are not necessarily performed in the order shown and described in this specification.
- the method may include more steps than described in this specification or less.
- a single step described in this specification may be broken down into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. describe.
- an edge device is a physical device located at a remote location at the edge of the network. Because real-life electronic terminals (such as cameras, sensors, etc.) often generate a large amount of data, uploading all the data to the cloud will cause huge pressure on the cloud. In order to share Under the pressure of the cloud, edge devices emerge as the times require. The edge device can be responsible for data calculation and storage within its own scope. The edge device then uploads the processed data to the cloud, thereby achieving cloud-edge collaboration, that is, close collaboration between the cloud and edge. Maximize the application value of cloud computing and edge computing.
- the cloud can generate corresponding alarm information, allowing operation and maintenance personnel to go to the site for manual maintenance and troubleshooting based on the alarm information.
- manual maintenance and troubleshooting methods will inevitably cause additional operation and maintenance cost burdens, and until the maintenance is completed, the tasks of the edge equipment cannot be performed smoothly and continuously.
- this specification provides a self-healing method for edge devices to solve the above technical problems existing in related technologies.
- the self-healing method of the edge device described in this description will be described in detail below with reference to Figures 1-9.
- FIG. 1 is a schematic architectural diagram of a self-healing system for edge devices provided by an exemplary embodiment.
- the system may include an edge device cluster 10 and a cloud server 11 , where the edge device cluster 10 may include an edge device 101 , an edge device 102 and an edge device 103 .
- the cloud server 11 can be deployed as a virtual server hosted by a host cluster.
- the cloud server 11 can be configured with the self-healing method of edge devices described in this specification, and the cloud server 11 maintains an edge device list of the edge device cluster and each edge device list. Task allocation of an edge device.
- the cloud server can determine the health status of the edge devices (such as edge device 101, edge device 102 and edge device 103) included in the edge device cluster 10. In the first edge device When the health status is abnormal, the cloud server 11 can determine the second edge device from the edge device cluster according to the edge device information collection list and the task allocation of the first edge device.
- the cloud server 11 can determine the edge device 102 as the second edge device based on the edge device information collection list and the task allocation of the edge device 101. At this time, the cloud server 11 issues a self-healing instruction, which is used to instruct the edge device 102 to take over the tasks pre-assigned to the edge device 101 .
- edge device 101 can be deployed in a network that supports multi-functional integration such as communication, control, and device access, and effectively manages and controls access.
- Hardware device for example, the hardware device can be PLC (Programmable Logic Controller programmable logic controller), smart router or smart sensor, etc.
- PLC Programmable Logic Controller programmable logic controller
- smart router or smart sensor, etc.
- the edge device is a hardware device that does not have data collection functions such as a PLC or a smart router, the edge device needs to be connected to an additional sensor, and the sensor collects data, and the edge device performs data classification, analysis, and packaging. wait.
- the edge device is a smart sensor
- the smart sensor collects, classifies, analyzes, and packages the data locally, and uploads it to the cloud server 11 . If an abnormality occurs in the first edge device, based on the self-healing instructions issued by the cloud server 11, the second edge device can take over the tasks of the first edge device, thereby realizing self-healing of the edge device.
- the cloud server Based on the architecture of the self-healing system of edge devices described above, the cloud server maintains the edge device information set of the edge device cluster and the task allocation for the edge devices included in the set, so that the cloud server can determine the edges contained in the edge device cluster.
- Figure 2 is a flow chart of a self-healing method for an edge device provided by an exemplary embodiment. As shown in Figure 2, the method may include the following steps:
- Step 202 Determine the health status of edge devices included in the edge device cluster.
- the health status of edge devices can be divided into two types, one is normal and the other is abnormal; abnormal health status may mean that the software or hardware of the edge device is abnormal, or the abnormal health status may mean that the edge device is offline.
- abnormal health status may mean that the software or hardware of the edge device is abnormal
- the abnormal health status may mean that the edge device is offline.
- the edge device although the edge device appears to be online, it cannot perform tasks normally due to software or hardware failures. At this time, it can be determined that the health status of the edge device is abnormal; or, the edge device appears to be offline, although it cannot be determined at this time. If the edge device has software or hardware failures but cannot continue to perform tasks because it is offline, it can also be directly determined that the health status of the edge device is abnormal.
- the cloud server can independently monitor the health status of the edge devices included in the edge device cluster; the method of independent monitoring can be a heartbeat mechanism.
- the edge device in the edge device cluster can send a heartbeat signal to the cloud server according to a preset period (such as every 2 seconds). When the cloud server does not receive the heartbeat signal after exceeding the preset period (2 seconds), When the signal is received, the cloud server can determine that the health status of the edge device is abnormal.
- the method of autonomous monitoring can also be that the cloud server sends a response signal to the edge device in the edge device cluster. For example, the cloud server sends a response signal every 2 seconds. If within the preset period after sending the response signal (such as 2 seconds) and still does not receive the feedback signal from the edge device, it can be determined that the health status of the edge device is abnormal.
- the cloud server in order to alleviate the pressure on the cloud server, can also receive health status information proactively reported by the edge device cluster; wherein the health status information includes reports by neighbor edge devices of the abnormal edge device, or by the edge device.
- the main edge devices in the cluster report uniformly. In some scenarios, reporting cannot be implemented normally because the edge device is abnormal.
- the health status information of the abnormal edge device can be reported by the neighbor edge device of the abnormal edge device.
- the neighbor edge device 101 can also promptly discover the abnormal edge device 102 based on the above-mentioned heartbeat mechanism, and the neighbor edge device 101 can report the health status information of the edge device 102 to the cloud server 11 .
- a primary edge device in order to reduce the interaction between edge devices and cloud servers in the cluster, a primary edge device, or master node, can be configured in the edge device cluster, as shown in Figure 4.
- the primary edge device can be Based on the above heartbeat mechanism, the device 401 detects the abnormal edge device 102 in time, and the main edge device 401 uniformly reports it to the cloud server, thereby reducing the interaction between multiple edge devices and the cloud server and reducing the pressure on the cloud server.
- the main edge device can be elected in various ways. For example, the edge device with the largest ID can be used as the main edge device, or the edge device can be randomly selected as the main edge device, or the edge device with the highest priority can be selected according to the preset priority.
- the main edge device As the main edge device, etc., this manual does not limit this. Of course, because the main edge device may also be abnormal, you can also set up a backup edge device at this time.
- the backup edge device can also discover whether the main edge device is abnormal based on the above heartbeat mechanism. When the main edge device is abnormal, the backup edge device will Take over task execution from the main edge device. Based on the three methods of independent monitoring by the cloud server and/or active reporting by the edge device cluster, the cloud server can determine the health status of the edge device and thereby detect abnormal edge devices in a timely manner.
- Step 204 When the health status of the first edge device is abnormal, determine a second edge device from the edge device cluster based on the edge device information set and the task allocation of the first edge device.
- the specific expression form of the edge device collection can be a network topology. That is to say, the cloud server can serve as an edge device information collection in the form of a network topology.
- the network topology can record the connection relationship between each edge device of the edge device cluster.
- the cloud server can also display the network topology in the form of a chart in the display area, such as a display screen in a data center, to visualize the information so that operation and maintenance personnel can more intuitively understand the status of the edge devices in the edge device cluster. connection relationship.
- the edge device information set can also record the binding relationship of the edge device to each sensor, and the binding relationship can be regarded as as before The assignment of tasks described.
- the cloud server can select an edge device that supports the task and has idle resources from the edge device information set according to the task pre-assigned to the first edge device as the second edge device.
- the second edge device is not determined by any edge device, because the first edge device still performs the task normally before the abnormality occurs. Therefore, in order to continue executing the task, the second edge device determined by the cloud server needs to be able to support the first edge device.
- the task execution of the edge device, and the second edge device has idle resources to execute the task, and the second edge device is determined through the above screening, the task can be successfully transferred to the second edge device for execution, thereby ensuring the smooth and continuous execution of the task.
- the cloud server can further filter, for example: the most recent first edge device can be selected.
- the candidate second edge device is used as the final second edge device, the final second edge device is randomly determined from the candidate second edge devices, the final second edge device is determined from the candidate second edge devices according to a preset priority, or the final second edge device can be determined based on Candidate second edge devices are sequentially selected according to the ID size of the device, that is, the candidate second edge device with the largest (or smallest) device ID is used as the final second edge device, etc. This specification does not limit this.
- Step 206 Issue a self-healing instruction to the edge device cluster, where the self-healing instruction is used to instruct the second edge device to take over the task pre-assigned to the first edge device.
- the cloud server can determine the second edge device, and after determining the second edge device, the cloud server can generate a self-healing instruction.
- the cloud server can send the self-healing instruction to the second edge device; or, if there is a main edge device in the edge device cluster, send the self-healing instruction to the main edge device.
- the cloud server can issue the self-healing instruction to the primary edge device 401, and the primary edge device forwards the self-healing instruction to the second edge device.
- the interaction between the cloud server and the edge device cluster can be reduced, and the operating pressure of the cloud server can be reduced.
- the cloud server can also deliver the configuration information adopted by the first edge device to the edge device cluster, so that the second edge device can be configured according to the configuration information.
- the configuration information performs tasks taken over from the first edge device.
- the cloud server can deliver the configuration information adopted by the first edge device.
- the configuration information can be the configuration information of road markings, or the configuration information of parking rules, etc., so that the second edge device can normally take over the first edge device and execute the corresponding Task.
- the edge devices in the edge device cluster can be in the same multicast group, then the cloud The server can receive the device information of the new edge device reported by the edge device cluster.
- the new edge device is discovered by any edge device in the edge device cluster based on the notification information sent by the new edge device for the multicast group;
- the cloud server can update the edge device information set of the edge device cluster it maintains and the task allocation for the edge devices included in the set based on the device information of the newly added edge device.
- the edge device 103 is a new edge device, so the edge device information set maintained by the cloud server at this time does not include the device information of the edge device 103 and the tasks of the edge device 103.
- the newly added edge device 103 can send notification information to the above-mentioned multicast group, so that the edge device cluster captures the edge device 103, thereby reporting the device information of the edge device 103 to the cloud server, so that the cloud
- the server updates the edge device information set of the edge device cluster it maintains and the task allocation for the edge devices included in the set.
- the reporting process can be as described above, that is, reported to the cloud server through the neighbor edge device, or reported to the cloud server by the main edge device, but generally, because the health status of the newly added edge device is normal, Therefore, the newly added edge device can also independently report device information to the cloud server or the main edge device. This manual does not limit this.
- the edge device cluster may include multiple road parking management devices deployed on a preset road section; wherein the tasks assigned to the edge devices include: connecting with sensors deployed on the preset road section and cooperating with the sensors Collect parking data.
- the self-healing method of the above-mentioned edge device will be described in detail below in conjunction with Figures 5 and 6.
- a cloud server 11 and an edge device cluster 10 can be deployed.
- the cloud server 11 can be further configured with a parking service engine as shown in Figure 6, and the edge device cluster 10 can include road parking.
- an application can be generated based on the local area network cluster as shown in Figure 6.
- road parking management device A can determine the name of the cluster and determine the multicast group corresponding to the cluster through a LAN cluster generation application, so that other road parking management devices can join the multicast group.
- the edge device cluster 10 can establish a connection with the Internet of Things platform as shown in Figure 6, and the Internet of Things platform interacts with the cloud server in a unified manner.
- Road parking management equipment A is bound to camera A1 and camera A2 through channel 1 and channel 2 respectively.
- Camera A1 and camera A2 can collect road picture data and upload it to road parking management equipment A, so that road parking management equipment A can analyze and calculate the picture data based on its own configuration information.
- road parking management equipment A can use The parking spaces are calculated from the screen data collected by camera A1 and camera A2.
- road parking management device B can send a notification message to the multicast group where the edge device cluster 10 is located, so that the road parking management device A can discover the new edge device, that is, the road parking management device A can discover the road parking Manage device B, and use the device information of road parking management device B, for example, Parkedge-biz (domain name), Device-link (device label) and Device-access (device access) as shown in Figure 6, as above.
- the device information is reported to the edge device information collection module in the parking service engine as shown in Figure 6, so that the parking service engine can update the edge device information collection maintained by itself and the edge devices contained in the edge device cluster 10.
- Task operation status that is, the parking service engine can obtain the device information of road parking management equipment B and the task operation status of road parking management equipment B.
- road parking management equipment B is bound to camera B1 and camera B2 respectively through channel 3 and channel 4, and through the screen data collected by camera B1 and camera B2, road parking management equipment B can be based on its Its own configuration information determines whether the vehicle in the screen is on the line.
- road parking management device A and road parking management device B can monitor each other based on the heartbeat mechanism as mentioned above.
- This heartbeat mechanism can be implemented through the application of the multicast mechanism in the parking edge application as shown in Figure 6.
- road parking management equipment B can promptly detect that the health status of road parking management equipment A is abnormal, and report it to the parking service engine through the cloud event reporting application as shown in Figure 6.
- the abnormal health status information of the road parking management device A can also be reported to the parking service engine by the main road parking management device (not shown in Figure 5), and then reported to the parking service engine by the main road parking management device, so that the parking service engine
- the abnormal event monitoring module in the system can receive the abnormal health status information in a timely manner.
- the main road parking management device can be implemented through the master node election application as shown in Figure 6.
- the road parking management device can initiate the master node election and determine the master node according to the election results.
- the parking service engine can also autonomously monitor each edge device in the edge device cluster 10 through the cluster health monitoring module. After the parking service engine as shown in Figure 6 determines that the road parking management device A is abnormal, the parking service engine needs to determine the second edge device at this time, because the road parking management device B has idle resources (i.e. channel 1 and channel 2 ). At the same time, road parking management equipment B also supports the calculation of parking spaces. At this time, the parking service engine can issue self-healing instructions through the self-healing instruction issuance module as shown in Figure 6.
- the self-healing command can be directly sent to the road parking management device B or to the main road parking management device, and the main road parking management device forwards the self-healing command to the road parking management device B.
- the parking edge applications mentioned above all need to be written to the local database to realize the call of data.
- road parking management device B can be bound to camera A1 and camera A2 through channel 1 and channel 2 respectively, and receive the configuration information of road parking management device A delivered by the cloud server through the configuration information delivery module shown in Figure 6 , the configuration information can be stored in the configuration management as shown in Figure 6 In application.
- road parking management device B can calculate parking spaces based on the configuration information in the configuration management application and based on the images collected by cameras A1 and A2, that is, the second edge device takes over from the first edge device as described in this specification. Task execution.
- Figure 7 is a self-healing method of an edge device provided by an exemplary embodiment.
- a flow chart of a healing method which method includes the following steps:
- Step 702 Obtain the self-healing instruction issued by the cloud server.
- the self-healing instruction is generated by the cloud server according to the maintained edge when the health status of the first edge device in the edge device cluster is abnormal.
- the second edge device is generated after the edge device information set of the device cluster and the task allocation situation of the first edge device are determined.
- the second edge device can receive self-healing instructions directly issued by the cloud server; or, when the edge device cluster includes a primary edge device and the second edge device is not the primary edge device, the second edge device can Receive the self-healing instructions forwarded by the main edge device after being issued by the cloud server.
- Step 704 Take over the task pre-assigned to the first edge device according to the self-healing instruction.
- the second edge device can also obtain the configuration information corresponding to the first edge device issued by the cloud server, and perform tasks taken over from the first edge device according to the configuration information.
- the second edge device can monitor the health status of the neighbor edge device through the heartbeat mechanism; when the health status of the neighbor edge device is abnormal, the second edge device can report the corresponding health status of the neighbor edge device to the cloud server. Status information, or report the health status information corresponding to the neighbor edge device to the main edge device in the edge device cluster so that the main edge device uniformly reports it to the cloud server.
- the edge devices in the edge device cluster can be in the same multicast group.
- the second edge device can receive the notification message for the multicast group to discover the new edge device; the second edge device can add the new edge device to the multicast group.
- the device information of the device is reported to the cloud server to update the edge device information set of the edge device cluster maintained by the cloud server and the task allocation for the edge devices included in the set.
- the edge device cluster includes multiple road parking management devices deployed on a preset road section, where the tasks assigned to the first edge device include: connecting with sensors deployed on the preset road section and collaborating with the sensors to collect parking data.
- the self-healing method of edge devices described in this specification uses the cloud server to maintain the edge device information set of the edge device cluster and the task allocation for the edge devices included in the set, so that the cloud server can determine the The health status of the edge devices contained in the edge device cluster, and the health status of the first edge device is Under abnormal circumstances, the cloud issues a self-healing command, allowing the second edge device to take over the task execution of the first edge device, thereby realizing self-healing of the edge device. Even if the operation and maintenance personnel do not go to the site for maintenance, they can Ensuring that tasks on edge devices can be executed smoothly and continuously ensures the normal operation of tasks.
- Figure 8 is a schematic structural diagram of a device provided by an exemplary embodiment. Please refer to Figure 8.
- the device includes a processor 802, an internal bus 804, a network interface 806, a memory 808 and a non-volatile memory 810.
- the processor 802 reads the corresponding computer program from the non-volatile memory 810 into the memory 808 and then runs it.
- the execution subject of the following processing flow is not limited to each A logic unit can also be a hardware or logic device.
- FIG. 9 is a block diagram of a self-healing device for an edge device provided by an exemplary embodiment of this specification.
- This device can be applied to the equipment shown in Figure 8 to implement the technical solution of this specification.
- the device is applied to a cloud server.
- the cloud server maintains an edge device information set of an edge device cluster and the information contained in the set. Task allocation of edge devices; the devices include:
- Health status determination unit 902 used to determine the health status of edge devices included in the edge device cluster
- the second edge device determining unit 904 is configured to determine from the edge device cluster based on the edge device information set and the task allocation of the first edge device when the health status of the first edge device is abnormal. out of the second edge device;
- the instruction issuing unit 906 is configured to issue a self-healing instruction to the edge device cluster, where the self-healing instruction is used to instruct the second edge device to take over a task pre-assigned to the first edge device.
- the health status determination unit 902 is specifically used to:
- the edge device cluster Receive health status information proactively reported by the edge device cluster; wherein the health status information includes reporting by neighbor edge devices of the abnormal edge device, or unified reporting by the main edge device in the edge device cluster.
- the second edge device determining unit 904 is specifically used to:
- an edge device that supports the task and has idle resources is selected from the edge device information set as the second edge device.
- the instruction issuing unit 906 is specifically used to:
- the self-healing instruction is sent to the master edge device.
- the device also includes:
- the configuration information delivery unit 908 is configured to deliver the configuration information adopted by the first edge device to the edge device cluster, so that the second edge device performs takeover from the first edge device according to the configuration information. task.
- the edge devices in the edge device cluster are in the same multicast group.
- the device also includes:
- the update unit 910 is configured to receive the device information of the new edge device reported by the edge device cluster.
- the new edge device is configured by any edge device in the edge device cluster according to the new edge device. It is discovered through the notification information sent by the broadcast group; based on the device information of the newly added edge device, it updates the edge device information set of the edge device cluster it maintains and the task allocation for the edge devices included in the set.
- the edge device cluster includes multiple road parking management devices deployed on a preset road section; wherein the tasks assigned to the edge devices include: connecting with sensors deployed on the preset road section and coordinating The sensors collect parking data.
- this specification also provides a self-healing device applied to an edge device on the edge device side.
- FIG. 10 is a block diagram of a self-healing device for an edge device provided by an exemplary embodiment of this specification.
- This device can be applied to the device as shown in Figure 8 to implement the technical solution of this specification.
- the device is applied to the second edge device in the edge device cluster.
- the device includes:
- the acquisition unit 1002 is used to acquire a self-healing instruction issued by the cloud server.
- the self-healing instruction is generated by the cloud server according to the maintained health status of the first edge device in the edge device cluster when the health status of the first edge device in the edge device cluster is abnormal.
- the second edge device is generated after the edge device information set of the edge device cluster and the task allocation situation of the first edge device are determined;
- the taking over unit 1004 is configured to take over the tasks pre-assigned to the first edge device according to the self-healing instruction.
- the acquisition unit 1002 is specifically used to:
- the edge device cluster includes a primary edge device and the second edge device is not the primary edge device, receive a self-healing instruction forwarded by the primary edge device after being issued by the cloud server.
- the device also includes:
- the configuration information obtaining unit 1006 is configured to obtain the configuration information corresponding to the first edge device issued by the cloud server; and perform tasks taken over from the first edge device according to the configuration information.
- the device also includes:
- the monitoring unit 1008 is used to monitor the health status of the neighbor edge device; when the health status of the neighbor edge device is abnormal, report the health status information corresponding to the neighbor edge device to the cloud server, or report the health status information corresponding to the neighbor edge device to the edge device.
- the main edge device in the device cluster reports health status information corresponding to the neighbor edge device to be uniformly reported to the cloud server by the main edge device.
- the edge devices in the edge device cluster are in the same multicast group.
- the device also includes:
- the notification information receiving unit 1010 is configured to receive notification messages for the multicast group to discover new edge devices; and report the device information of the new edge devices to the cloud server to update the edge devices maintained by it.
- the edge device cluster includes multiple road parking management devices deployed on a preset road section; wherein the task assigned to the first edge device includes: communicating with sensors deployed on the preset road section. Connect and collaborate with the sensors to collect parking data.
- the device embodiment since it basically corresponds to the method embodiment, please refer to the partial description of the method embodiment for relevant details.
- the device embodiments described above are only illustrative.
- the modules described as separate components may or may not be physically separated.
- the components shown as modules may or may not be physical modules, that is, they may be located in One place, or it can be distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. Persons of ordinary skill in the art can understand and implement the method without any creative effort.
- a typical implementation device is a computer, which may be in the form of a personal computer, a laptop, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, or a game controller. desktop, tablet, wearable device, or a combination of any of these devices.
- a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
- processors CPUs
- input/output interfaces network interfaces
- memory volatile and non-volatile memory
- Memory may include non-permanent storage in computer-readable media, random access memory (RAM), and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM).
- RAM random access memory
- ROM read-only memory
- flash RAM flash memory
- Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information.
- Information may be computer-readable instructions, data structures, modules of programs, or other data.
- Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory.
- PRAM phase change memory
- SRAM static random access memory
- DRAM dynamic random access memory
- RAM random access memory
- read-only memory read-only memory
- ROM read-only memory
- EEPROM electrically erasable programmable read-only memory
- flash memory or other memory technology
- compact disc read-only memory CD-ROM
- DVD digital versatile disc
- Magnetic tape cartridges magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium, can be used to store information that can be accessed by computing devices.
- computer-readable media does not include transient computer-readable media (transitory media), such as modulated data signals and carrier waves.
- first, second, third, etc. may use the terms first, second, third, etc. to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
- first information may also be called second information, and similarly, the second information may also be called first information.
- word “if” as used herein may be interpreted as "when” or “when” or “in response to determining.”
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Computer And Data Communications (AREA)
- Alarm Systems (AREA)
Abstract
本说明书一个或多个实施例提供一种边缘设备的自愈方法、装置、电子设备及存储介质，所述方法包括：确定所述边缘设备集群所含边缘设备的健康状况；在第一边缘设备的健康状况为异常的情况下，根据所述边缘设备信息集合和所述第一边缘设备的任务分配情况从所述边缘设备集群中确定出第二边缘设备；向所述边缘设备集群下发自愈指令，所述自愈指令用于指示所述第二边缘设备接替预先分配至所述第一边缘设备的任务。
Description
本申请要求于2022年05月30日提交中国专利局、申请号为202210605517.8、申请名称为“边缘设备的自愈方法、装置、电子设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本说明书一个或多个实施例涉及计算机技术领域，尤其涉及一种边缘设备的自愈方法、装置、电子设备及存储介质。
边缘设备顾名思义是一种位于网络边缘远程位置的物理设备，因为现实中的电子终端(如摄像头、传感器等)往往会产生大量数据，若将数据全部上传至云端势必会造成云端的巨大压力；为了分担云端的压力，边缘设备应运而生，边缘设备可以负责自己范围内的数据计算和存储工作，之后由边缘设备将处理后的数据上传至云端，从而实现云边协同，即云边的紧密协同来最大化云计算和边缘计算的应用价值。
然而，在相关技术中，假设某一边缘设备出现异常，则此时只能安排运维人员前去人工检修，排除故障。
发明内容
有鉴于此，本说明书一个或多个实施例提供一种边缘设备的自愈方法、装置、电子设备及存储介质。
为实现上述目的，本说明书一个或多个实施例提供技术方案如下：
根据本说明书一个或多个实施例的第一方面，提出了一种边缘设备的自愈方法，所述方法应用于云端服务器，所述云端服务器维护有边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况；所述方法包括：
确定所述边缘设备集群所含边缘设备的健康状况；
在第一边缘设备的健康状况为异常的情况下，根据所述边缘设备信息集合和所述第一边缘设备的任务分配情况从所述边缘设备集群中确定出第二边缘设备；
向所述边缘设备集群下发自愈指令，所述自愈指令用于指示所述第二边缘设备接替预先分配至所述第一边缘设备的任务。
根据本说明书一个或多个实施例的第二方面，提出了一种边缘设备的自愈方法，所述方法应用于边缘设备集群中的第二边缘设备，所述方法包括：
获取云端服务器下发的自愈指令，所述自愈指令由所述云端服务器在所述边缘设备集群中的第一边缘设备的健康状况为异常的情况下，根据维护的所述边缘设备集群的边缘设备信息集合和所述第一边缘设备的任务分配情况确定出所述第二边缘设备后生成；
根据所述自愈指令，接替预先分配至所述第一边缘设备的任务。
根据本说明书一个或多个实施例的第三方面，提出了一种边缘设备的自愈装置，所述装置应用于云端服务器，所述云端服务器维护有边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况；所述装置包括：
健康状况确定单元，用于确定所述边缘设备集群所含边缘设备的健康状况；
第二边缘设备确定单元，用于在第一边缘设备的健康状况为异常的情况下，根据所述边缘设备信息集合和所述第一边缘设备的任务分配情况从所述边缘设备集群中确定出第二边缘设备；
指令下发单元，用于向所述边缘设备集群下发自愈指令，所述自愈指令用于指示所述第二边缘设备接替预先分配至所述第一边缘设备的任务。
根据本说明书一个或多个实施例的第四方面，提出了一种边缘设备的自愈装置，所述装置应用于边缘设备集群中的第二边缘设备，所述装置包括：
获取单元，用于获取云端服务器下发的自愈指令，所述自愈指令由所述云端服务器在所述边缘设备集群中的第一边缘设备的健康状况为异常的情况下，根据维护的所述边缘设备集群的边缘设备信息集合和所述第一边缘设备的任务分配情况确定出所述第二边缘设备后生成；
接替单元，用于根据所述自愈指令，接替预先分配至所述第一边缘设备的任务。
根据本说明书一个或多个实施例的第五方面，提出了一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器通过运行所述可执行指令以实现如上述第一方面或第二方面所述方法的步骤。
根据本说明书一个或多个实施例的第六方面，提供一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如上述第一方面或第二方面所述方法的步骤。
由上述方案可知，本说明书通过提供一种边缘设备的自愈方案，由云端服务器维护边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况，使得云端服务器可以确定所述边缘设备集群所含边缘设备的健康状况，并在第一边缘设备的健康状况为异常的情况下，由云端下发自愈指令，从而使第二边缘设备接替第一边缘设备的任务执行，继而实现边缘设备的自愈，即便运维人员并未前去现场进行检修，也能够确保边缘设备上的任务能够顺利、持续执行，保证了任务的正常运行。
图1是一示例性实施例提供的一种边缘设备的自愈系统的架构示意图；
图2是一示例性实施例提供的一种边缘设备的自愈方法的流程图；
图3是一示例性实施例提供的一种邻居边缘设备上报的示意图；
图4是一示例性实施例提供的一种主边缘设备上报的示意图；
图5是一示例性实施例提供的一种道路停车管理设备的示意图；
图6是一示例性实施例提供的一种道路停车管理设备的结构示意图；
图7是一示例性实施例提供的一种边缘设备的自愈方法的流程图；
图8是一示例性实施例提供的一种设备的示意结构图；
图9一示例性实施例提供的一种边缘设备的自愈装置的框图；
图10一示例性实施例提供的一种边缘设备的自愈装置的框图。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本说明书一个或多个实施例相一致的所有实施方式。相反，它们仅是与本说明书一个或多个实施例的一些方面相一致的装置和方法的例子。
需要说明的是：在其他实施例中并不一定按照本说明书示出和描述的顺序来执行相应方法的步骤。在一些其他实施例中，其方法所包括的步骤可以比本说明书所描述的更多或
更少。此外，本说明书中所描述的单个步骤，在其他实施例中可能被分解为多个步骤进行描述；而本说明书中所描述的多个步骤，在其他实施例中也可能被合并为单个步骤进行描述。
边缘设备顾名思义是一种位于网络边缘远程位置的物理设备，因为现实中的电子终端(如摄像头、传感器等)往往会产生大量数据，若将数据全部上传至云端会造成云端的巨大压力，为了分担云端的压力，边缘设备应运而生，边缘设备可以负责自己范围内的数据计算和存储工作，之后由边缘设备将处理后的数据上传至云端，从而实现云边协同，即云边的紧密协同来最大化云计算和边缘计算的应用价值。
然而，在相关技术中，假设某一边缘设备出现异常，则云端可以生成对应的告警信息，从而使运维人员基于该告警信息前往现场进行人工检修，排除故障。然而人工检修排除故障的方法势必会造成额外的运维成本的负担，而且在检修完成之前，该边缘设备的任务也无法顺利、持续执行。
有鉴于此，本说明书提供了一种边缘设备的自愈方法，以解决相关技术中存在的上述技术问题。下面结合图1-图9对本说明所述的边缘设备的自愈方法进行详细说明。
请参见图1，图1是一示例性实施例提供的一种边缘设备的自愈系统的架构示意图。如图1所示，该系统可以包括边缘设备集群10和云端服务器11，其中，边缘设备集群10可以包括边缘设备101、边缘设备102以及边缘设备103。
所述云端服务器11可以部署在主机集群承载的虚拟服务器，该云端服务器11可以配置有本说明书所述的边缘设备的自愈方法，且该云端服务器11维护有边缘设备集群的边缘设备列表和每一边缘设备的任务分配情况，此时，该云端服务器可以确定边缘设备集群10中所含边缘设备(如边缘设备101、边缘设备102以及边缘设备103)的健康状况，在在第一边缘设备的健康状况为异常的情况下，云端服务器11可以根据所述边缘设备信息集合列表和所述第一边缘设备的任务分配情况从所述边缘设备集群中确定出第二边缘设备，例如，假设边缘设备101的健康状况为异常，则云端服务器11可以根据边缘设备信息集合列表和边缘设备101的任务分配情况确定边缘设备102为第二边缘设备。此时，云端服务器11下发自愈指令，该自愈指令用于指示边缘设备102接替预先分配至边缘设备101的任务。
多个边缘设备(如边缘设备101、边缘设备102以及边缘设备103)构成边缘设备集群10，边缘设备101可以部署在支持通信、控制、设备接入等多功能集成，有效管理和控制接入的硬件设备，例如，该硬件设备可以为PLC(Programmable Logic
Controller可编程逻辑控制器)、智能路由器或智能传感器等。当该边缘设备为PLC、智能路由器等不具有数据采集功能的硬件设备时，则该边缘设备需要额外连接传感器，并由该传感器来采集数据，由该边缘设备进行数据的归类、分析、封装等。当该边缘设备为智能传感器时，则此时由该智能传感器就地实现对数据的采集、归类、分析、封装，并上传至云端服务器11。若第一边缘设备出现异常，则基于云端服务器11下发的自愈指令，可以由第二边缘设备接替第一边缘设备的任务，从而实现边缘设备的自愈。
基于上述边缘设备的自愈系统的架构，通过由云端服务器维护边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况，使得云端服务器可以确定所述边缘设备集群所含边缘设备的健康状况，并在第一边缘设备的健康状况为异常的情况下，由云端下发自愈指令，从而使第二边缘设备接替第一边缘设备的任务执行，继而实现边缘设备的自愈，即便运维人员并未前去现场进行检修，也能够确保边缘设备上的任务能够顺利、持续执行，保证了任务的正常运行。
为了描述的方便，下面结合附图对本说明书所述的边缘设备的自愈方法进行详细描述。
请参见图2，图2是一示例性实施例提供的一种边缘设备的自愈方法的流程图。如图2所示，所述方法可以包括以下步骤：
步骤202，确定所述边缘设备集群所含边缘设备的健康状况。
边缘设备的健康状况可以划分为两种，一为正常，二为异常；异常健康状况可以是指该边缘设备的软件或硬件存在异常，或者该异常健康状况可以是指该边缘设备下线。换言之，边缘设备虽然显示在线，但其因为软件或硬件的故障而无法正常执行任务，此时可以确定该边缘设备的健康状况为异常；或者，该边缘设备显示下线，虽然此时无法确定该边缘设备是否存在软、硬件的故障，但因为其下线无法继续执行任务，则也可以直接确定该边缘设备的健康状况为异常。
本说明书并不限制确定边缘设备集群所含边缘设备的健康状况的方式，在一实施例中可由云端服务器自主监测所述边缘设备集群所含边缘设备的健康状况；自主监测的方式可以为心跳机制，举例而言，边缘设备集群中的边缘设备可以根据预设周期(如每隔2秒)向云端服务器发送心跳信号，当云端服务器在超过该预设周期(2秒)仍未接收到该心跳信号时，此时云端服务器可以确定该边缘设备的健康状况为异常。当然自主监测的方式还可以是由云端服务器下发响应信号至该边缘设备集群中的边缘设备，如云端服务器每隔2秒下发响应信号，若在下发响应信号后的预设周期内(如2
秒)仍未接收到边缘设备反馈信号，则可以确定该边缘设备的健康状况为异常。
在另一实施例中，为了缓解云端服务器的压力，还可以由云端服务器接收边缘设备集群主动上报的健康状况信息；其中，健康状况信息包括由异常边缘设备的邻居边缘设备上报，或由边缘设备集群中的主边缘设备统一上报。在一些场景中，因为边缘设备出现异常而无法正常实现上报，则此时异常边缘设备的健康状况信息可以由该异常边缘设备的邻居边缘设备上报，如图3所示，当边缘设备102的健康状况为异常时，邻居边缘设备101也可以基于上述心跳机制来及时发现异常边缘设备102，并且该邻居边缘设备101可以将该边缘设备102的健康状况信息上报至云端服务器11。在另一些场景中，为了减少集群中边缘设备与云端服务器的交互，可以在边缘设备集群中配置主边缘设备，或称之为主节点，如图4所示，则此时，可以由主边缘设备401基于上述心跳机制，及时发现异常边缘设备102，并由该主边缘设备401统一上报至云端服务器，从而减少多个边缘设备与云端服务器的交互，减轻云端服务器的压力。需要说明的是，主边缘设备的选举方式可以是多样的，例如可以将边缘设备ID最大的作为主边缘设备，或随机选取边缘设备作为主边缘设备，或按照预设优先级，将优先级最大的作为主边缘设备等，本说明书对此不进行限制。当然，因为主边缘设备也可能出现异常，此时还可以设置备用边缘设备，备用边缘设备也可以基于上述心跳机制，发现主边缘设备是否出现异常，当主边缘设备出现异常时，由备用边缘设备来接替主边缘设备的任务执行。基于云端服务器自主监测和/或边缘设备集群主动上报这三种方式，可以使云端服务器确定边缘设备的健康状况，从而及时发现异常边缘设备。
步骤204，在第一边缘设备的健康状况为异常的情况下，根据所述边缘设备信息集合和所述第一边缘设备的任务分配情况从所述边缘设备集群中确定出第二边缘设备。
边缘设备集合的具体表现形式可以为网络拓扑，也就是说，云端服务器可以以网络拓扑的形式作为边缘设备信息集合，该网络拓扑可以记载有该边缘设备集群的各个边缘设备之间的连接关系，当然，云端服务器也可以将该网络拓扑以图表的形式显示于显示区域，如数据中心的显示屏，即将信息资讯可视化处理，使运维人员可以更为直观的了解到边缘设备集群中边缘设备的连接关系。需要说明的是，当边缘设备还绑定有传感器(如摄像头)的情况下，该边缘设备信息集合也可以记载有边缘设备各自绑定传感器的绑定关系，该绑定关系可以视为如前所述的任务分配情况。
在一实施例中，云端服务器可以根据预先分配至第一边缘设备的任务，从边缘设备信息集合中选取支持该任务且存在空闲资源的边缘设备，以作为第二边缘设备。换
言之，第二边缘设备的确定并非是任意边缘设备，因为第一边缘设备在出现异常前仍正常执行任务，所以，为了任务的继续执行，云端服务器确定的第二边缘设备需要能够支持第一边缘设备的任务执行，且该第二边缘设备存在执行该任务的空闲资源，通过上述筛选确定第二边缘设备，可以使任务成功转移至第二边缘设备执行，从而保证任务的顺利、持续执行。当然，在某一实施例中，可能存在多个可选的第二边缘设备，即存在多个边缘设备满足上述筛选条件，此时，云端服务器可以进一步筛选，例如：可以选取第一边缘设备最近的候选第二边缘设备作为最终第二边缘设备、随机从候选第二边缘设备中确定最终第二边缘设备、根据预设的优先级从候选第二边缘设备中确定最终第二边缘设备或者可以根据设备的ID大小来顺序选取候选第二边缘设备，即将设备的ID最大(或最小)的候选第二边缘设备作为最终第二边缘设备等，本说明书对此不进行限制。
步骤206，向所述边缘设备集群下发自愈指令，所述自愈指令用于指示所述第二边缘设备接替预先分配至所述第一边缘设备的任务。
如前所述，云端服务器可以确定第二边缘设备，则云端服务器在确定第二边缘设备后，可以生成自愈指令。在一实施例中，云端服务器可以将上述自愈指令下发至第二边缘设备；或，在边缘设备集群中存在主边缘设备的情况下，下发所述自愈指令至主边缘设备。如图4所示，假设边缘设备集群中存在主边缘设备401，则云端服务器可以下发该自愈指令至主边缘设备401，由主边缘设备来转发该自愈指令至第二边缘设备。通过主边缘设备，可以减少云端服务器与边缘设备集群之间的交互，减少云端服务器的运行压力。
在一实施例中，因为第一边缘设备执行的并非为通用常规任务，则此时，云端服务器还可以向边缘设备集群下发第一边缘设备采用的配置信息，以使第二边缘设备根据该配置信息执行从第一边缘设备接替的任务。当然，若第一边缘设备执行的是通用任务，或该第二边缘设备已经在某一次任务接替时接收并保存该配置信息，则此时也可以不下发第一边缘设备采用的配置信息，本说明书对此不进行限制。为了保证第二边缘设备可以正常接替第一边缘设备的任务，云端服务器可以下发第一边缘设备采用的配置信息。举例而言，在道路停车管理场景下，该配置信息可以为道路划线的配置信息，也可以为停车规则的配置信息等，从而使第二边缘设备可以正常接替第一边缘设备并执行对应的任务。
在一实施例中，边缘设备集群中的边缘设备可以处于同一多播组内，则此时云端
服务器可以接收边缘设备集群上报的新增边缘设备的设备信息，该新增边缘设备由边缘设备集群中的任一边缘设备根据该新增边缘设备针对所述多播组发送的通知信息而发现；云端服务器可以根据新增边缘设备的设备信息，更新自身维护的边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况。举例而言，在图4所示的实施例中，边缘设备103为新增边缘设备，那么此时云端服务器维护的边缘设备信息集合并没有该边缘设备103的设备信息以及该边缘设备103的任务分配情况，所以，该新增边缘设备103可以针对上述多播组，发送通知信息，以使边缘设备集群捕捉到该边缘设备103，从而上报该边缘设备103的设备信息至云端服务器，以使云端服务器更新其自身维护的边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况。需要说明的是，该上报过程可以如前所述，即通过邻居边缘设备上报至云端服务器，或由主边缘设备上报至云端服务器，但一般的，因为该新增边缘设备的健康状况为正常，所以也可以由该新增边缘设备自主上报设备信息至云端服务器或主边缘设备，本说明书对此不进行限制。
在一实施例中，边缘设备集群可以包括部署于预设路段的多台道路停车管理设备；其中，分配至边缘设备的任务包括：与预设路段处部署的传感器进行连接，并协同所述传感器采集停车数据。如图5所示，下面结合图5和图6对上述边缘设备的自愈方法进行详细描述。
在预设路段的道路停车场景下，可以部署有云端服务器11以及边缘设备集群10，该云端服务器11可以进一步被配置有如图6中所示的停车服务引擎，而边缘设备集群10可以包括道路停车管理设备A以及道路停车管理设备B。对于边缘设备集群10的生成，可以基于如图6所示的局域网集群生成应用。例如，道路停车管理设备A可以通过局域网集群生成应用确定集群的名称并确定该集群对应的多播组等，从而可以使其他道路停车管理设备加入该多播组。边缘设备集群10可以与如图6所示的物联网平台建立连接，并由该物联网平台统一与云端服务器进行交互，当然该物联网平台也可以集成于所述云端服务器，甚至也可以取消物联网平台，而是边缘设备集群10直接与云端服务器进行交互，本说明书对此不进行限制。道路停车管理设备A通过通道1以及通道2分别与摄像头A1和摄像头A2绑定。摄像头A1和摄像头A2可以采集道路画面数据并上传至道路停车管理设备A，从而道路停车管理设备A可以基于其自身的配置信息对该画面数据进行分析、计算，例如：道路停车管理设备A可以利用摄像头A1和摄像头A2采集的画面数据计算出停车空位。若，道路停车管理设备B为新增边
缘设备，此时道路停车管理设备B可以向边缘设备集群10所在的多播组发送通知消息，从而道路停车管理设备A可以发现该新增的边缘设备，即道路停车管理设备A可以发现道路停车管理设备B，并将道路停车管理设备B的设备信息，例如，如图6所示的Parkedge-biz(域名)、Device-link(设备标签)以及Device-access(设备接入)可以作为如前所述的设备信息，上报至如图6所示的停车服务引擎中的边缘设备信息集合模块，从而使得停车服务引擎可以更新其自身维护的边缘设备信息集合以及边缘设备集群10所含边缘设备的任务运行情况，即停车服务引擎可以获得道路停车管理设备B的设备信息以及道路停车管理设备B的任务运行情况。例如，如图5所示，道路停车管理设备B通过通道3和通道4，分别与摄像头B1、摄像头B2绑定，且通过摄像头B1和摄像头B2采集的画面数据，道路停车管理设备B可以基于其自身的配置信息确定画面中的车辆是否压线。此时，道路停车管理设备A和道路停车管理设备B可以基于如前所述的心跳机制互相监测，该心跳机制可以通过如图6所示的停车边缘应用中的多播机制应用实现。假设道路停车管理设备A出现异常，则道路停车管理设备B可以及时发现道路停车管理设备A的健康状况为异常，并通过如图6所示的云端事件上报应用，将其上报至停车服务引擎。当然，道路停车管理设备A的异常健康状况信息也可以由主道路停车管理设备(图5未标出)上报至停车服务引擎，并由主道路停车管理设备上报至停车服务引擎，从而停车服务引擎中的异常事件监听模块可以及时接收该异常健康状况信息。其中，主道路停车管理设备可以通过如图6所示的主节点选举应用来实现，例如通过主节点选举应用，该道路停车管理设备可以发起主节点选举，并根据选举结果确定主节点。或者，如前所述，停车服务引擎也可以通过集群健康监测模块自主监测边缘设备集群10中的各个边缘设备。在如图6所示的停车服务引擎确定道路停车管理设备A出现异常后，则此时停车服务引擎需要确定第二边缘设备，而因为道路停车管理设备B存在空闲资源(即通道1以及通道2)，同时，道路停车管理设备B也支持停车空位的计算，则此时停车服务引擎可以通过如图6所示的自愈指令下发模块下发自愈指令。当然如前所述，该自愈指令可以直接下发至道路停车管理设备B也可以下发至主道路停车管理设备，并由主道路停车管理设备转发该自愈指令至道路停车管理设备B。当然，如前所述的停车边缘应用均需要写入本地数据库，从而实现数据的调用。此时，道路停车管理设备B可以通过通道1以及通道2分别与摄像头A1和摄像头A2绑定，并接收云端服务器通过图6所示的配置信息下发模块下发道路停车管理设备A的配置信息，该配置信息可以存储于如图6所示的配置管
理应用中。至此，道路停车管理设备B可以根据配置管理应用中的配置信息，并基于摄像头A1、A2采集的画面，实现停车空位的计算，即本说明书所述的由第二边缘设备接替第一边缘设备的任务执行。
相较于云端服务器侧的自愈方法，本说明书还提供一种应用于第二边缘设备侧的自愈方法，请参见图7，图7是一示例性实施例提供的一种边缘设备的自愈方法的流程图，所述方法包括以下步骤：
步骤702，获取云端服务器下发的自愈指令，所述自愈指令由所述云端服务器在所述边缘设备集群中的第一边缘设备的健康状况为异常的情况下，根据维护的所述边缘设备集群的边缘设备信息集合和所述第一边缘设备的任务分配情况确定出所述第二边缘设备后生成。
如前所述，第二边缘设备可以接收云端服务器直接下发的自愈指令；或，在边缘设备集群包括主边缘设备且该第二边缘设备并非主边缘设备的情况下，第二边缘设备可以接收云端服务器下发后由主边缘设备转发的自愈指令。
步骤704，根据所述自愈指令，接替预先分配至所述第一边缘设备的任务。
在一实施例中，第二边缘设备还可以获取所述云端服务器下发的所述第一边缘设备对应的配置信息，并根据所述配置信息执行从所述第一边缘设备接替的任务。
如前所述，第二边缘设备可以通过心跳机制监测邻居边缘设备的健康状况；在该邻居边缘设备健康状况出现异常的情况下，第二边缘设备可以向云端服务器上报该邻居边缘设备对应的健康状况信息，或者向边缘设备集群中的主边缘设备上报该邻居边缘设备对应的健康状况信息以由主边缘设备统一上报至云端服务器。
边缘设备集群中的边缘设备可以处于同一多播组内，此时第二边缘设备可以接收针对该多播组的通知消息，以发现新增边缘设备；第二边缘设备可以将该新增边缘设备的设备信息上报至云端服务器，以更新云端服务器维护的边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况。
边缘设备集群包括部署于预设路段的多台道路停车管理设备，其中，分配至第一边缘设备的任务包括：与该预设路段处部署的传感器进行连接，并协同所述传感器采集停车数据。
由上述技术方案可知，本说明书所述的边缘设备的自愈方法，由云端服务器维护边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况，使得云端服务器可以确定所述边缘设备集群所含边缘设备的健康状况，并在第一边缘设备的健康状况为
异常的情况下，由云端下发自愈指令，从而使第二边缘设备接替第一边缘设备的任务执行，继而实现边缘设备的自愈，即便运维人员并未前去现场进行检修，也能够确保边缘设备上的任务能够顺利、持续执行，即保证了任务的正常运行。
图8是一示例性实施例提供的一种设备的示意结构图。请参考图8，在硬件层面，该设备包括处理器802、内部总线804、网络接口806、内存808以及非易失性存储器810，当然还可能包括其他功能所需要的硬件。本说明书一个或多个实施例可以基于软件方式来实现，比如由处理器802从非易失性存储器810中读取对应的计算机程序到内存808中然后运行。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图9，图9是本说明书一示例性实施例提供的一种边缘设备的自愈装置的框图。该装置可以应用于如图8所示的设备中，以实现本说明书的技术方案，所述装置应用于云端服务器，所述云端服务器维护有边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况；所述装置包括：
健康状况确定单元902，用于确定所述边缘设备集群所含边缘设备的健康状况；
第二边缘设备确定单元904，用于在第一边缘设备的健康状况为异常的情况下，根据所述边缘设备信息集合和所述第一边缘设备的任务分配情况从所述边缘设备集群中确定出第二边缘设备；
指令下发单元906，用于向所述边缘设备集群下发自愈指令，所述自愈指令用于指示所述第二边缘设备接替预先分配至所述第一边缘设备的任务。
可选的，所述健康状况确定单元902具体用于：
自主监测所述边缘设备集群所含边缘设备的健康状况；和/或，
接收所述边缘设备集群主动上报的健康状况信息；其中，所述健康状况信息包括由异常边缘设备的邻居边缘设备上报，或由所述边缘设备集群中的主边缘设备统一上报。
可选的，所述第二边缘设备确定单元904具体用于：
根据预先分配至所述第一边缘设备的任务，从所述边缘设备信息集合中选取支持该任务且存在空闲资源的边缘设备，以作为所述第二边缘设备。
可选的，所述指令下发单元906具体用于：
将所述自愈指令下发至所述第二边缘设备；或，
在所述边缘设备集群中存在主边缘设备的情况下，下发所述自愈指令至所述主边缘设备。
可选的，所述装置还包括：
配置信息下发单元908，用于向所述边缘设备集群下发所述第一边缘设备采用的配置信息，以使所述第二边缘设备根据所述配置信息执行从所述第一边缘设备接替的任务。
可选的，所述边缘设备集群中的边缘设备处于同一多播组内。
可选的，所述装置还包括：
更新单元910，用于接收所述边缘设备集群上报的新增边缘设备的设备信息，所述新增边缘设备由所述边缘设备集群中的任一边缘设备根据该新增边缘设备针对所述多播组发送的通知信息而发现；根据所述新增边缘设备的设备信息，更新自身维护的边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况。
可选的，所述边缘设备集群包括部署于预设路段的多台道路停车管理设备；其中，分配至所述边缘设备的任务包括：与所述预设路段处部署的传感器进行连接，并协同所述传感器采集停车数据。
相对应的，本说明书还提供一种应用于边缘设备侧的边缘设备的自愈装置。请参考图10，图10是本说明书一示例性实施例提供的一种边缘设备的自愈装置的框图。该装置可以应用于如图8所示的设备中，以实现本说明书的技术方案，所述装置应用于边缘设备集群中的第二边缘设备，所述装置包括：
获取单元1002，用于获取云端服务器下发的自愈指令，所述自愈指令由所述云端服务器在所述边缘设备集群中的第一边缘设备的健康状况为异常的情况下，根据维护的所述边缘设备集群的边缘设备信息集合和所述第一边缘设备的任务分配情况确定出所述第二边缘设备后生成；
接替单元1004，用于根据所述自愈指令，接替预先分配至所述第一边缘设备的任务。
可选的，所述获取单元1002具体用于：
接收所述云端服务器直接下发的自愈指令；或，
在所述边缘设备集群包括主边缘设备且所述第二边缘设备并非所述主边缘设备的情况下，接收所述云端服务器下发后由所述主边缘设备转发的自愈指令。
可选的，所述装置还包括：
配置信息获取单元1006，用于获取所述云端服务器下发的所述第一边缘设备对应的配置信息；根据所述配置信息执行从所述第一边缘设备接替的任务。
可选的，所述装置还包括：
监测单元1008，用于监测邻居边缘设备的健康状况；在所述邻居边缘设备健康状况出现异常的情况下，向所述云端服务器上报所述邻居边缘设备对应的健康状况信息，或者向所述边缘设备集群中的主边缘设备上报所述邻居边缘设备对应的健康状况信息以由所述主边缘设备统一上报至所述云端服务器。
可选的，所述边缘设备集群中的边缘设备处于同一多播组内。
可选的，所述装置还包括：
通知信息接收单元1010，用于接收针对所述多播组的通知消息，以发现新增边缘设备；将所述新增边缘设备的设备信息上报至所述云端服务器，以更新其维护的边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况。
可选的，所述边缘设备集群包括部署于预设路段的多台道路停车管理设备；其中，所述分配至所述第一边缘设备的任务包括：与所述预设路段处部署的传感器进行连接，并协同所述传感器采集停车数据。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本说明书方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的
示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带、磁盘存储、量子存储器、基于石墨烯的存储介质或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在本说明书一个或多个实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本说明书一个或多个实施例的较佳实施例而已，并不用以限制本说明书一个或多个实施例，凡在本说明书一个或多个实施例的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本说明书一个或多个实施例保护的范围之内。
Claims (17)
- 一种边缘设备的自愈方法，其特征在于，应用于云端服务器，所述云端服务器维护有边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况；所述方法包括：确定所述边缘设备集群所含边缘设备的健康状况；在第一边缘设备的健康状况为异常的情况下，根据所述边缘设备信息集合和所述第一边缘设备的任务分配情况从所述边缘设备集群中确定出第二边缘设备；向所述边缘设备集群下发自愈指令，所述自愈指令用于指示所述第二边缘设备接替预先分配至所述第一边缘设备的任务。
- 根据权利要求1所述的方法，其特征在于，所述确定所述边缘设备集群所含边缘设备的健康状况，包括：自主监测所述边缘设备集群所含边缘设备的健康状况；和/或，接收所述边缘设备集群主动上报的健康状况信息；其中，所述健康状况信息包括由异常边缘设备的邻居边缘设备上报，或由所述边缘设备集群中的主边缘设备统一上报。
- 根据权利要求1所述的方法，其特征在于，所述根据所述边缘设备信息集合和所述第一边缘设备的任务分配情况从所述边缘设备集群中确定出第二边缘设备，包括：根据预先分配至所述第一边缘设备的任务，从所述边缘设备信息集合中选取支持该任务且存在空闲资源的边缘设备，以作为所述第二边缘设备。
- 根据权利要求1所述的方法，其特征在于，所述下发自愈指令，包括：将所述自愈指令下发至所述第二边缘设备；或，在所述边缘设备集群中存在主边缘设备的情况下，下发所述自愈指令至所述主边缘设备。
- 根据权利要求1所述的方法，其特征在于，所述方法还包括：向所述边缘设备集群下发所述第一边缘设备采用的配置信息，以使所述第二边缘设备根据所述配置信息执行从所述第一边缘设备接替的任务。
- 根据权利要求1所述的方法，其特征在于，所述边缘设备集群中的边缘设备处于同一多播组内，所述方法还包括：接收所述边缘设备集群上报的新增边缘设备的设备信息，所述新增边缘设备由所述边缘设备集群中的任一边缘设备根据该新增边缘设备针对所述多播组发送的通知信 息而发现；根据所述新增边缘设备的设备信息，更新自身维护的边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况。
- 根据权利要求1所述的方法，其特征在于，所述边缘设备集群包括部署于预设路段的多台道路停车管理设备；其中，分配至所述边缘设备的任务包括：与所述预设路段处部署的传感器进行连接，并协同所述传感器采集停车数据。
- 一种边缘设备的自愈方法，其特征在于，应用于边缘设备集群中的第二边缘设备，所述方法包括：获取云端服务器下发的自愈指令，所述自愈指令由所述云端服务器在所述边缘设备集群中的第一边缘设备的健康状况为异常的情况下，根据维护的所述边缘设备集群的边缘设备信息集合和所述第一边缘设备的任务分配情况确定出所述第二边缘设备后生成；根据所述自愈指令，接替预先分配至所述第一边缘设备的任务。
- 根据权利要求8所述的方法，其特征在于，所述获取云端服务器下发的自愈指令，包括：接收所述云端服务器直接下发的自愈指令；或，在所述边缘设备集群包括主边缘设备且所述第二边缘设备并非所述主边缘设备的情况下，接收所述云端服务器下发后由所述主边缘设备转发的自愈指令。
- 根据权利要求8所述的方法，其特征在于，所述方法还包括：获取所述云端服务器下发的所述第一边缘设备对应的配置信息；根据所述配置信息执行从所述第一边缘设备接替的任务。
- 根据权利要求8所述的方法，其特征在于，所述方法还包括：监测邻居边缘设备的健康状况；在所述邻居边缘设备健康状况出现异常的情况下，向所述云端服务器上报所述邻居边缘设备对应的健康状况信息，或者向所述边缘设备集群中的主边缘设备上报所述邻居边缘设备对应的健康状况信息以由所述主边缘设备统一上报至所述云端服务器。
- 根据权利要求8所述的方法，其特征在于，所述边缘设备集群中的边缘设备处于同一多播组内；所述方法还包括：接收针对所述多播组的通知消息，以发现新增边缘设备；将所述新增边缘设备的设备信息上报至所述云端服务器，以更新其维护的边缘设 备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况。
- 根据权利要求8所述的方法，其特征在于，所述边缘设备集群包括部署于预设路段的多台道路停车管理设备；其中，所述分配至所述第一边缘设备的任务包括：与所述预设路段处部署的传感器进行连接，并协同所述传感器采集停车数据。
- 一种边缘设备的自愈装置，其特征在于，应用于云端服务器，所述云端服务器维护有边缘设备集群的边缘设备信息集合和针对该集合所含边缘设备的任务分配情况；所述装置包括：健康状况确定单元，用于确定所述边缘设备集群所含边缘设备的健康状况；第二边缘设备确定单元，用于在第一边缘设备的健康状况为异常的情况下，根据所述边缘设备信息集合和所述第一边缘设备的任务分配情况从所述边缘设备集群中确定出第二边缘设备；指令下发单元，用于向所述边缘设备集群下发自愈指令，所述自愈指令用于指示所述第二边缘设备接替预先分配至所述第一边缘设备的任务。
- 一种边缘设备的自愈装置，其特征在于，应用于边缘设备集群中的第二边缘设备，所述装置包括：获取单元，用于获取云端服务器下发的自愈指令，所述自愈指令由所述云端服务器在所述边缘设备集群中的第一边缘设备的健康状况为异常的情况下，根据维护的所述边缘设备集群的边缘设备信息集合和所述第一边缘设备的任务分配情况确定出所述第二边缘设备后生成；接替单元，用于根据所述自愈指令，接替预先分配至所述第一边缘设备的任务。
- 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述程序被处理器执行时实现如权利要求1至7或8至13中任一所述方法的步骤。
- 一种电子设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其特征在于，所述处理器执行所述程序时实现如权利要求1至7或8至13中任一所述方法的步骤。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210605517.8A CN114979188A (zh) | 2022-05-30 | 2022-05-30 | 边缘设备的自愈方法、装置、电子设备及存储介质 |
| CN202210605517.8 | 2022-05-30 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2023231993A1 true WO2023231993A1 (zh) | 2023-12-07 |
Family
ID=82957207
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2023/096963 WO2023231993A1 (zh) | 2022-05-30 | 2023-05-29 | 边缘设备的自愈方法、装置、电子设备及存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114979188A (zh) |
| WO (1) | WO2023231993A1 (zh) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114979188A (zh) * | 2022-05-30 | 2022-08-30 | 阿里云计算有限公司 | 边缘设备的自愈方法、装置、电子设备及存储介质 |
| CN118101440B (zh) * | 2024-04-26 | 2024-08-16 | 成都秦川物联网科技股份有限公司 | 基于云计算的工业物联网数据分析方法、物联网系统及设备 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8589441B1 (en) * | 2012-05-18 | 2013-11-19 | Hitachi, Ltd. | Information processing system and method for controlling the same |
| CN109379774A (zh) * | 2018-11-08 | 2019-02-22 | 网宿科技股份有限公司 | 智能调度方法、终端设备、边缘节点集群与智能调度系统 |
| CN112788088A (zh) * | 2019-11-11 | 2021-05-11 | 财团法人工业技术研究院 | 多边缘云的网络通信控制方法及边缘运算系统 |
| CN112788089A (zh) * | 2019-11-11 | 2021-05-11 | 财团法人工业技术研究院 | 多边缘云的网络通讯控制方法及边缘运算装置与系统 |
| CN114979188A (zh) * | 2022-05-30 | 2022-08-30 | 阿里云计算有限公司 | 边缘设备的自愈方法、装置、电子设备及存储介质 |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8108733B2 (en) * | 2010-05-12 | 2012-01-31 | International Business Machines Corporation | Monitoring distributed software health and membership in a compute cluster |
| CN105429883B (zh) * | 2015-10-22 | 2018-05-18 | 上海斐讯数据通信技术有限公司 | 多个智能设备与服务器设备的长连接方法及智能设备 |
| CN105357116B (zh) * | 2015-10-23 | 2018-04-06 | 上海斐讯数据通信技术有限公司 | 一种多终端访问服务器的方法和智能终端 |
| CN107332880A (zh) * | 2017-06-05 | 2017-11-07 | 深圳市酷开网络科技有限公司 | 信息推送的方法、装置及计算机可读存储介质 |
| CN111869163B (zh) * | 2018-03-19 | 2022-05-24 | 华为技术有限公司 | 一种故障检测的方法、装置及系统 |
| CN112087312B (zh) * | 2019-06-15 | 2023-02-03 | 华为云计算技术有限公司 | 一种提供边缘服务的方法、装置和设备 |
| CN110581782B (zh) * | 2019-09-17 | 2022-07-12 | 中国联合网络通信集团有限公司 | 一种容灾数据的处理方法、装置及系统 |
| CN111294845B (zh) * | 2020-02-13 | 2023-07-25 | 天翼数字生活科技有限公司 | 节点切换方法、装置、计算机设备和存储介质 |
| CN113742173A (zh) * | 2021-08-30 | 2021-12-03 | 浙江大华技术股份有限公司 | 多设备集群的控制方法、设备主控装置及可读存储介质 |
-
2022
- 2022-05-30 CN CN202210605517.8A patent/CN114979188A/zh active Pending
-
2023
- 2023-05-29 WO PCT/CN2023/096963 patent/WO2023231993A1/zh unknown
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8589441B1 (en) * | 2012-05-18 | 2013-11-19 | Hitachi, Ltd. | Information processing system and method for controlling the same |
| CN109379774A (zh) * | 2018-11-08 | 2019-02-22 | 网宿科技股份有限公司 | 智能调度方法、终端设备、边缘节点集群与智能调度系统 |
| CN112788088A (zh) * | 2019-11-11 | 2021-05-11 | 财团法人工业技术研究院 | 多边缘云的网络通信控制方法及边缘运算系统 |
| CN112788089A (zh) * | 2019-11-11 | 2021-05-11 | 财团法人工业技术研究院 | 多边缘云的网络通讯控制方法及边缘运算装置与系统 |
| CN114979188A (zh) * | 2022-05-30 | 2022-08-30 | 阿里云计算有限公司 | 边缘设备的自愈方法、装置、电子设备及存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114979188A (zh) | 2022-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2023231993A1 (zh) | 边缘设备的自愈方法、装置、电子设备及存储介质 | |
| US10834015B2 (en) | Dynamic resource allocation for sensor devices on a mixed-infrastructure network | |
| CN111818159B (zh) | 数据处理节点的管理方法、装置、设备及存储介质 | |
| CN107092522B (zh) | 实时数据的计算方法及装置 | |
| US7225356B2 (en) | System for managing operational failure occurrences in processing devices | |
| US7849178B2 (en) | Grid computing implementation | |
| US20130166621A1 (en) | Cloud robot system and method of integrating the same | |
| US10826812B2 (en) | Multiple quorum witness | |
| CN113296903A (zh) | 边缘云系统、边缘管控方法、管控节点及存储介质 | |
| WO2017080161A1 (zh) | 云计算中报警信息的处理方法及装置 | |
| CN103546313A (zh) | 基于云计算的it运维管理系统 | |
| CN112351051A (zh) | 云服务处理方法、装置、云服务器、系统及存储介质 | |
| CN111949444A (zh) | 一种基于分布式服务集群的数据备份与恢复系统及方法 | |
| JP7341244B2 (ja) | クラスタ管理方法、装置、およびシステム | |
| CN112579304A (zh) | 基于分布式平台的资源调度方法、装置、设备及介质 | |
| CA3030504A1 (en) | Blockchain network and task scheduling method therefor | |
| CN112698838B (zh) | 多云容器部署系统及其容器部署方法 | |
| CN106230622B (zh) | 一种集群实现方法及装置 | |
| CN113946408A (zh) | 云原生边缘容器控制方法、系统及存储介质 | |
| CN114189495B (zh) | 基于域名的节点调度方法、系统、终端和存储介质 | |
| CN116915827A (zh) | 物联网边缘网关的数据传输方法、装置、电子设备及介质 | |
| CN111418187A (zh) | 云网络中的可伸缩统计和分析机制 | |
| CN111901421A (zh) | 一种数据处理方法及相关设备 | |
| CN114697197A (zh) | 边缘计算设备和方法 | |
| CN118331188A (zh) | 边缘计算自动化控制方法、装置和系统 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23815172 Country of ref document: EP Kind code of ref document: A1 |