CN111917588B - Edge device management method, device, edge gateway device and storage medium - Google Patents
Edge device management method, device, edge gateway device and storage medium Download PDFInfo
- Publication number
- CN111917588B CN111917588B CN202010795820.XA CN202010795820A CN111917588B CN 111917588 B CN111917588 B CN 111917588B CN 202010795820 A CN202010795820 A CN 202010795820A CN 111917588 B CN111917588 B CN 111917588B
- Authority
- CN
- China
- Prior art keywords
- edge
- container
- equipment
- state change
- management state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
Abstract
The application relates to the technical field of edge equipment management, and provides an edge equipment management method, an edge equipment management device, edge gateway equipment and a storage medium. The method comprises the following steps: an edge device triggering a management state change of the edge gateway device is determined, then a container created for the edge device in the edge gateway device is determined, and processing adapted to the management state change is performed on the container in response to the management state change. According to the method and the device, based on isolation operation and management of the container, real-time efficient management of the edge gateway device when the corresponding edge device triggers management state changes such as access, exit and update can be achieved, the problem that the response mechanism of the edge gateway device is insufficient in real time due to frequent access, exit or update of a large number of edge devices is solved, the management efficiency of the edge gateway device to the edge device is improved, operation and maintenance investment is reduced, operation reliability can be improved, and various management requirements of the rapid response distributed edge device are met.
Description
Technical Field
The present invention relates to the field of edge device management technologies, and in particular, to an edge device management method, an edge device management apparatus, an edge gateway device, and a storage medium.
Background
With the popularization of new energy systems and the access of various distributed resources, the access of mass edge equipment is promoted. The edge gateway device needs to dynamically monitor the state of the edge device, and also needs to respond to various data request requirements of the edge device, such as access, exit, update, and the like, in an efficient and real-time manner. However, the huge amount of access of edge devices of different types and different manufacturers has significant influence on the management of edge gateway devices, and the edge gateway is required to provide an edge device management method which is efficient, convenient, easy to maintain and capable of responding quickly.
The edge gateway equipment provided in the traditional technology mainly realizes data access of various devices, realizes data forwarding according to the requirements of the edge devices, and has higher communication interface characteristics and communication protocol dependence on the edge devices. When a large number of different types of edge devices are frequently accessed, exited and updated, the original gateway system lacks a quick response mechanism, so that the management efficiency of the edge gateway device on the accessed edge device is lower, and the long-term stable operation of the edge gateway is possibly influenced due to excessive data redundancy and reduced device reliability.
Disclosure of Invention
In view of the foregoing, it is desirable to provide an edge device management method, an apparatus, an edge gateway device, and a storage medium.
An edge device management method applied to an edge gateway device, the method comprising:
determining edge equipment triggering the edge gateway equipment to generate management state change;
determining a container created in the edge gateway device for the edge device; the container configuration information of the container is generated according to the equipment configuration information of the edge equipment;
in response to the management state change, a process is performed on the container that is compatible with the management state change.
An edge device management apparatus, applied to an edge gateway device, comprising:
the device determining module is used for determining edge devices triggering the edge gateway devices to change management states;
a container determining module, configured to determine a container created for the edge device in the edge gateway device; the container configuration information of the container is generated according to the equipment configuration information of the edge equipment;
and the container processing module is used for responding to the management state change and executing processing which is suitable for the management state change on the container.
An edge gateway device comprising a memory storing a computer program and a processor that when executing the computer program performs the steps of:
determining edge equipment triggering the edge gateway equipment to generate management state change; determining a container created in the edge gateway device for the edge device; the container configuration information of the container is generated according to the equipment configuration information of the edge equipment; in response to the management state change, a process is performed on the container that is compatible with the management state change.
A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
determining edge equipment triggering the edge gateway equipment to generate management state change; determining a container created in the edge gateway device for the edge device; the container configuration information of the container is generated according to the equipment configuration information of the edge equipment; in response to the management state change, a process is performed on the container that is compatible with the management state change.
The edge device management method, the edge device management device, the edge gateway device and the storage medium determine edge devices triggering the edge gateway device to generate management state change, then determine containers which are created for the edge devices in the edge gateway device, respond to the management state change, and execute processing which is suitable for the management state change on the containers. The method and the device can realize real-time and efficient management when the edge gateway device triggers the management state changes such as access, exit and update to the corresponding edge device based on the isolated operation and management of the container, solve the problem of insufficient real-time response mechanism of the edge gateway device caused by frequent access, exit or update of a large number of edge devices, improve the management efficiency of the edge gateway device to the edge device, reduce operation and maintenance investment, improve operation reliability and meet various management requirements of the quick response distributed edge device.
Drawings
FIG. 1 is a flow chart of a method for managing an edge device according to an embodiment;
FIG. 2 is a schematic flow diagram of edge device access in one embodiment;
FIG. 3 is a schematic flow diagram of edge device disconnection in one embodiment;
FIG. 4 is a flow diagram of edge device update in one embodiment;
FIG. 5 is a block diagram of an edge device management apparatus in one embodiment;
fig. 6 is an internal block diagram of an edge gateway device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
The edge equipment management method provided by the application can be applied to the edge gateway equipment to manage the accessed edge equipment. In one embodiment, as shown in fig. 1, the edge device management method may include the steps of:
step S101, determining edge equipment triggering the edge gateway equipment to generate management state change;
in this step, the edge gateway device may manage edge devices that access itself, and the edge gateway device may have management states for the edge devices, which may include which edge devices the edge gateway device currently accesses, which operational states the edge device currently is in, and so on. The edge device may change the management state of the triggering edge gateway device, which may include, but is not limited to, edge device access, edge device disconnection, and edge device update. Specifically, the edge device access may correspond to accessing newly added edge devices in the distributed system, where the newly added edge devices may be devices covering different types, different manufacturers, and different communication interfaces; the disconnection (or the exit) of the edge equipment can correspond to the decommissioning, damage, overhaul and other scenes of the original edge equipment in the distributed system; the edge device update then corresponds to a functional upgrade, a model upgrade, a configuration upgrade, etc. of the edge device itself.
Step S102, determining a container created for the edge device in the edge gateway device.
In this step, the edge gateway device may determine the container created for the edge device among its own devices. Specifically, for the accessed edge device, the edge gateway device is configured with a container for the accessed edge device, and for this case, the edge gateway device only needs to find the corresponding container according to the device identifier of the edge device; for newly accessed edge equipment, the edge gateway equipment can newly establish a container for the edge equipment, and container configuration information for configuring the container is generated according to equipment configuration information of the corresponding edge equipment, so that each container configured in the edge gateway equipment has a mapping relation with the corresponding edge equipment.
Step S103, in response to the management state change, processing compatible with the management state change is performed on the container.
Based on the edge device and container with the mapping relation, the edge gateway device can utilize the isolation characteristic of containerization operation, and when detecting that the edge device triggers a certain management state change, the edge gateway device executes corresponding processing on the independent container corresponding to the edge device, thereby realizing management functions such as edge device access, edge device disconnection, edge device update and the like of each different edge device.
The edge device management method determines the edge device triggering the edge gateway device to generate management state change, then determines the container established for the edge device in the edge gateway device, and responds to the management state change to execute the processing adapting to the management state change on the container. According to the scheme, based on isolation operation and management of the container, real-time efficient management of the edge gateway equipment when the corresponding edge equipment triggers management state changes such as access, exit and update can be realized, the problem that the response mechanism of the edge gateway equipment is insufficient in real time due to frequent access, exit or update of a large number of edge equipment is solved, the management efficiency of the edge gateway equipment to the edge equipment is improved, the operation and maintenance investment is reduced, the operation reliability is improved, and various management requirements of the quick response distributed edge equipment are met.
The following describes the edge device management method provided in the present application in detail with examples of management state changes being edge device access, edge device disconnection, and edge device update, respectively.
In one embodiment, the management state change may include edge device access; the determining the container created for the edge device in the edge gateway device in step S102 may include:
sending a device configuration information acquisition request to the edge device, and acquiring device configuration information fed back by the edge device; generating container configuration information according to the device configuration information, and creating a container in the edge gateway device by using the container configuration information.
Specifically, referring to fig. 2, the edge device access may correspond to accessing a newly added edge device in the distributed system, and may be an edge device covering different types, different manufacturers, and different communication interfaces. After the edge equipment is connected with the edge gateway equipment through physical connection, the edge gateway equipment detects corresponding communication connection signals, sends an equipment configuration information acquisition request to the edge equipment, feeds back equipment configuration information to the edge gateway equipment after receiving the equipment configuration information acquisition request, and generates container configuration information according to the equipment configuration information after the equipment configuration information is successfully acquired by the edge gateway equipment; if the acquisition fails, the access failure of the edge equipment can be judged. The edge equipment can be in different communication modes such as Ethernet, industrial field bus, narrowband wireless, near field communication and the like in a physical access mode; the device configuration information of the edge device can comprise an edge device unique mark code, state information and communication configuration information of the edge device under the same communication network; the container configuration information may include information such as storage capacity, memory capacity, communication configuration, and hardware interface necessary for the container to operate. The edge gateway device may create a container and update the configuration information of the container with the generated container configuration information. The constraint of configuration information is used for creating the container, and functions such as storage, memory use and data acquisition inside the container are not influenced outside the container in an isolation mode.
Further, in response to the management state change in step S103, performing a process corresponding to the management state change on the container may include:
running the container to trigger the container to perform model interaction with the edge equipment; if the model interaction is successful, a mapping relation between the container and the edge equipment is established in the edge gateway equipment, and an application function of the container is started to trigger the container to independently operate; and if the model interaction fails, stopping the operation of the container and deleting the container.
Specifically, referring to fig. 2, after a container is created for a newly accessed edge device and container configuration information is updated, the newly created container is operated to trigger an initialization function of the container or first operation of a newly created container, so that the container starts to interact with the edge device to perform model interaction. The results of the model interaction may include two types, one being successful and the other being failed.
If the model interaction fails, the newly-built container is withdrawn, the operation of the container is stopped, the container is deleted, the failure of the access of the edge equipment is judged, and the access management of the edge gateway equipment to the edge equipment is finished. Specifically, the model interaction failure indicates that the function verification of the edge device fails, the capability of accessing the distributed edge network is not provided, the newly-built container is stopped and deleted, and the method specifically can include deleting the device configuration information, the container configuration information, the allocated resources such as storage, memory, hardware and the like, and the isolated resource deletion does not affect other edge device functions on the edge gateway device.
If the model interaction is successful, the edge gateway device can register the newly built container, and a mapping relation is established between the newly built container and the accessed edge device. The mapping relationship can be used for representing the corresponding relationship between the actual edge equipment and the affiliated container and is used for inquiring the later equipment management. Then, the edge gateway device starts the container application function of the container, and can further run the application function of the container according to the model conversion result, so that the container with the mapping relation with the edge device can independently run, the success of the access of the edge device is determined, and the access management of the edge device is finished.
In one embodiment, the management state change may include an edge device disconnection; the determining the container created for the edge device in the edge gateway device in step S102 may include:
and determining a container with a mapping relation with the edge equipment in the edge gateway equipment.
Specifically, referring to fig. 3, for an accessed edge device, an edge gateway device may determine a container having a mapping relationship with the accessed edge device when the accessed edge device is disconnected. The physical connection between the accessed edge device and the edge gateway device is disconnected, specifically, the edge gateway device detects that the communication connection signal of the edge device is lost.
Further, in response to the management state change in step S103, performing a process corresponding to the management state change on the container may include:
suspending the application function of the container; detecting whether the edge equipment resumes connection within a preset delay; and executing corresponding processing on the container according to the connection recovery detection result.
After determining a container having a mapping relation with the disconnected edge device, the edge gateway device can suspend the application function of the container, delay and wait for the communication recovery of the edge device, that is, detect whether the edge device recovers the communication connection within a preset delay, so as to execute corresponding processing on the container according to the connection recovery detection result. Wherein the accessed edge device indicates physical access failure through disconnection of the physical connection.
Further, the method for performing corresponding processing on the container according to the connection recovery detection result specifically includes:
if the edge equipment resumes connection within the preset delay, resuming the operation of the application function of the container; if the edge equipment does not recover the connection within the preset delay, stopping the container, removing the mapping relation between the container and the edge equipment, and deleting the container.
Specifically, if the edge device resumes connection within the preset delay, the operation of the application function of the corresponding container is resumed, the edge device continues to operate normally, and the disconnection management of the edge gateway device on the edge device is ended. The communication connection of the edge device is restored, which indicates that the connection loss of the edge device is caused by interference and does not exit from the system operation, so that the edge gateway device can restore the operation of the application function in the corresponding container.
If the edge equipment does not recover the connection within the preset time delay, stopping the application function of the corresponding container, stopping the container, releasing the mapping relation between the edge equipment and the container, and deleting the container. At this time, the edge device is successfully withdrawn from the edge gateway device, and other edge device functions of the edge gateway device can continue to operate, so that the withdrawal management of the edge gateway device for the edge device is ended.
In one embodiment, the management state change includes an edge device update; after determining that the edge gateway device triggers the edge device with the management state change in step S101, the method further includes the following steps:
and acquiring new equipment configuration information of the edge equipment, and generating new container configuration information according to the new equipment configuration information.
Specifically, the edge device may initiate an update request of the device configuration information to the edge gateway device, and the edge gateway device may obtain new device configuration information or called new device configuration information of the edge device according to the request. If the new device configuration information is not acquired, the edge gateway device judges that the updating is not performed, and the original container of the edge device keeps running. If the new device configuration information is successfully obtained, the edge gateway device may verify the new device configuration information and generate new container configuration information according to the new device configuration information.
Further, determining the container created for the edge device in the edge gateway device in step S102 may include: and determining a container with a mapping relation with the edge equipment in the edge gateway equipment. For the accessed edge device, the edge gateway device creates a container with a mapping relation with the accessed edge device, and when the accessed edge device needs to be updated, the edge gateway device can determine the container with the mapping relation with the edge device.
Further, in response to the management state change in step S103, performing processing adapted to the management state change on the container may include:
detecting whether the configuration of the container needs to be updated; if not, stopping the container, creating the container with the same configuration as the container as a first new container, running the first new container to trigger the first new container to perform model interaction with the edge equipment, if the model interaction is successful, removing the mapping relation between the container and the edge equipment, deleting the container, establishing the mapping relation between the first new container and the edge equipment in the edge gateway equipment, and starting the application function of the first new container to trigger the first new container to independently run; if so, stopping the container, newly creating a second new container, updating the second new container by using the new container configuration information, operating the second new container to trigger the second new container to perform model interaction with the edge equipment, if the model interaction is successful, removing the mapping relation between the container and the edge equipment, deleting the container, establishing the mapping relation between the second new container and the edge equipment in the edge gateway equipment, and starting the application function of the second new container to trigger the second new container to independently operate.
Referring to fig. 4, specifically, after the edge gateway device determines a container having a mapping relationship with the edge device that needs to be updated, it may be checked whether the container configuration needs to be updated.
If the updating is not needed, stopping the container which has the mapping relation with the edge equipment, copying a container which has the same configuration as the container to be used as a first new container, and operating the first new container so as to update the function of the edge equipment by using the independent container configuration. The first new container is triggered to perform model interactions with the edge device based on the first run of the first new container. If the model interaction is successful, the establishment of the first new container is judged to be successful, the mapping relation between the edge equipment and the original container is released, and the original container is logged out and deleted, wherein the original container comprises all original container configuration information. And the edge gateway device can establish the mapping relation between the first new container and the edge device, register the first new container, start the operation of the container application function of the first new container, successfully update the edge device, and end the update management of the edge gateway device on the edge device. Further, in some embodiments, after the foregoing running of the first new container, if the model interaction fails, the first new container is exited and stopped, the first new container is deleted, and it is determined that the edge device function update fails, the original container continues to run according to the original configuration, and the update management of the edge gateway device on the edge device ends.
If the new container needs to be updated, stopping the container which has the mapping relation with the edge equipment, creating an independent container, namely a second new container, and updating the second new container by using the new container configuration information. And then, running the second new container, and triggering the second new container to perform model interaction with the edge equipment based on the first running of the second new container.
If the model interaction is successful, judging that the second new container is successfully established, removing the mapping relation between the edge equipment and the original container, and canceling and deleting the original container, including all the original container configuration information. And the edge gateway device can establish a mapping relation between the second new container and the edge device, register the second new container, start running the container application function of the second new container, update the edge device successfully, and end the update management of the edge gateway device on the edge device. Further, in some embodiments, after the foregoing running of the second new container, if the model interaction fails, the second new container is exited and stopped, the second new container is deleted, and it is determined that the edge device function update fails, the original container continues to run according to the original configuration, and the update management of the edge gateway device on the edge device ends.
According to the technical scheme provided by the embodiment of the application, the mapping relation is automatically established between the edge equipment and the operation container, the mapping relation can be automatically updated along with the change of the state of the edge equipment, a containerized management mechanism in the process of accessing and exiting the system of the edge equipment is provided, the real-time state of mapping the container to the equipment is generated, operated and stopped, an edge equipment function updating mechanism operated by the independent container is also provided, seamless updating of new functions of the edge equipment and noninductivity of function rollback are realized, after huge amounts of edge equipment of different types and manufacturers are accessed, the influence on the management of the edge gateway equipment system is greatly reduced, and therefore various requirements of the distributed edge equipment can be responded quickly, namely, the efficient real-time access, the exit and the function updating of the edge equipment are realized through the isolated operation and storage management of the container, the problem that the response mechanism caused by frequent access, exit and function updating of a large number of different types of equipment is reduced is solved, the operation and maintenance investment is reduced, the problem of excessive data redundancy caused by the edge equipment function updating is also solved, and the operation reliability is improved.
It should be understood that, although the steps in the flowcharts of fig. 1 to 4 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps of fig. 1 to 4 may include a plurality of steps or stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the execution of the steps or stages is not necessarily sequential, but may be performed in turn or alternately with at least a portion of the steps or stages of other steps or steps.
In one embodiment, as shown in fig. 5, there is provided an edge device management apparatus applied to an edge gateway device, the apparatus 500 includes:
a device determining module 501, configured to determine an edge device that triggers the edge gateway device to change a management state;
a container determining module 502, configured to determine a container created in the edge gateway device for the edge device; the container configuration information of the container is generated according to the equipment configuration information of the edge equipment;
a container processing module 503 for executing processing adapted to the management state change on the container in response to the management state change.
In one embodiment, the management state change includes at least one of edge device access, edge device disconnection, or edge device update.
In one embodiment, the management state change includes the edge device access; the container determining module 502 is further configured to send a device configuration information acquisition request to the edge device, and acquire the device configuration information fed back by the edge device; generating the container configuration information according to the equipment configuration information, and creating the container in the edge gateway equipment by utilizing the container configuration information; a container processing module 503, further configured to run the container to trigger the container to perform model interaction with the edge device; if the model interaction is successful, a mapping relation between the container and the edge equipment is established in the edge gateway equipment, and an application function of the container is started to trigger the container to independently operate; and if the model interaction fails, stopping the operation of the container and deleting the container.
In one embodiment, the management state change includes the edge device disconnecting; a container determining module 502, configured to determine a container in the edge gateway device that has a mapping relationship with the edge device; a container handling module 503 further configured to suspend application functions of the container; detecting whether the edge equipment resumes connection within a preset delay; and executing corresponding processing on the container according to the connection recovery detection result.
In one embodiment, the container processing module 503 is further configured to resume operation of an application function of the container if the edge device resumes connection within the preset delay; and if the edge equipment does not recover connection within the preset delay, stopping the container, releasing the mapping relation between the container and the edge equipment, and deleting the container.
In one embodiment, the management state change includes the edge device update; the apparatus 500 may further include: the new information generation module is used for acquiring new equipment configuration information of the edge equipment and generating new container configuration information according to the new equipment configuration information; a container determining module 502, configured to determine a container in the edge gateway device that has a mapping relationship with the edge device; a container processing module 503, configured to further detect whether the configuration of the container needs to be updated; if not, stopping the container, creating a container with the same configuration as the container as a first new container, running the first new container to trigger the first new container to perform model interaction with the edge equipment, if the model interaction is successful, removing the mapping relation between the container and the edge equipment, deleting the container, establishing the mapping relation between the first new container and the edge equipment in the edge gateway equipment, and starting the application function of the first new container to trigger the first new container to independently run; if yes, stopping the container, newly creating a second new container, updating the second new container by using the new container configuration information, operating the second new container to trigger the second new container to perform model interaction with the edge equipment, if the model interaction is successful, removing the mapping relation between the container and the edge equipment, deleting the container, establishing the mapping relation between the second new container and the edge equipment in the edge gateway equipment, and starting the application function of the second new container to trigger the second new container to independently operate.
In one embodiment, the container processing module 503 is further configured to, after the first new container is executed, if the model interaction fails, exit and stop the first new container, delete the first new container, and resume the stopped execution of the container; the container processing module 503 is further configured to, after running the second new container, if the model interaction fails, exit and stop the second new container, delete the second new container, and resume the stopped running of the container.
For specific limitations of the edge device management apparatus, reference may be made to the above limitation of the edge device management method, and no further description is given here. The respective modules in the above-described edge device management apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or independent of a processor in the edge gateway device, or may be stored in software in a memory in the edge gateway device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, an edge gateway device is provided, the internal structure of which may be as shown in fig. 6. The edge gateway device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the edge gateway device is configured to provide computing and control capabilities. The memory of the edge gateway device includes a non-volatile storage medium, an internal memory. The nonvolatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the edge gateway device is used to communicate with external devices via a network connection. The computer program is executed by a processor to implement an edge device management method.
Those skilled in the art will appreciate that the structure shown in fig. 6 is merely a block diagram of a portion of the structure associated with the present application and is not limiting of the edge gateway device to which the present application is applied, and that a particular edge gateway device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment, there is also provided an edge gateway device including a memory and a processor, the memory storing a computer program, the processor implementing the steps of the method embodiments described above when executing the computer program.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of the method embodiments described above.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (10)
1. An edge device management method, applied to an edge gateway device, comprising:
determining edge equipment triggering the edge gateway equipment to generate management state change;
determining a container created in the edge gateway device for the edge device; the container configuration information of the container is generated according to the equipment configuration information of the edge equipment; performing a process on the container in response to the management state change, the process being compatible with the management state change;
the determining a container created in the edge gateway device for the edge device includes: identifying the type of the management state change triggered by the target edge device; the target edge device is the edge device triggering the edge gateway device to generate management state change, and the type of the management state change at least comprises edge device access, edge device disconnection and edge device update;
according to the type of the management state change, the type of the target edge equipment is confirmed; the types of the target edge devices comprise edge devices which are accessed to the edge gateway device and edge devices which are newly accessed to the edge gateway device;
and according to the type of the target edge equipment, confirming a container corresponding to the target edge equipment in the edge gateway equipment.
2. The method of claim 1, wherein the management state change comprises at least one of edge device access, edge device disconnection, or edge device update.
3. The method of claim 2, wherein the step of determining the position of the substrate comprises,
the management state change comprises the edge device access;
the determining a container created in the edge gateway device for the edge device includes:
sending a device configuration information acquisition request to the edge device, and acquiring the device configuration information fed back by the edge device;
generating the container configuration information according to the equipment configuration information, and creating the container in the edge gateway equipment by utilizing the container configuration information;
the processing, responsive to the management state change, of the container in response to the management state change, includes:
operating the container to trigger the container to perform model interaction with the edge device;
if the model interaction is successful, a mapping relation between the container and the edge equipment is established in the edge gateway equipment, and an application function of the container is started to trigger the container to independently operate;
and if the model interaction fails, stopping the operation of the container and deleting the container.
4. The method of claim 2, wherein the step of determining the position of the substrate comprises,
the management state change includes the edge device disconnection;
the determining a container created in the edge gateway device for the edge device includes:
determining a container with a mapping relation with the edge equipment in the edge gateway equipment;
the processing, responsive to the management state change, of the container in response to the management state change, includes:
suspending application functions of the container;
detecting whether the edge equipment resumes connection within a preset delay;
and executing corresponding processing on the container according to the connection recovery detection result.
5. The method of claim 4, wherein the performing the corresponding processing on the container according to the connection restoration detection result comprises:
if the edge equipment resumes connection within the preset delay, resuming the operation of the application function of the container;
and if the edge equipment does not recover connection within the preset delay, stopping the container, releasing the mapping relation between the container and the edge equipment, and deleting the container.
6. The method of claim 2, wherein the step of determining the position of the substrate comprises,
the management state change includes the edge device update;
after determining the edge device triggering the edge gateway device to change the management state, the method further comprises:
acquiring new equipment configuration information of the edge equipment, and generating new container configuration information according to the new equipment configuration information;
the determining a container created in the edge gateway device for the edge device includes:
determining a container with a mapping relation with the edge equipment in the edge gateway equipment;
the processing, responsive to the management state change, of the container in response to the management state change, includes:
detecting whether the configuration of the container needs to be updated;
if not, stopping the container, creating a container with the same configuration as the container as a first new container, running the first new container to trigger the first new container to perform model interaction with the edge equipment, if the model interaction is successful, removing the mapping relation between the container and the edge equipment, deleting the container, establishing the mapping relation between the first new container and the edge equipment in the edge gateway equipment, and starting the application function of the first new container to trigger the first new container to independently run;
if yes, stopping the container, newly creating a second new container, updating the second new container by using the new container configuration information, operating the second new container to trigger the second new container to perform model interaction with the edge equipment, if the model interaction is successful, removing the mapping relation between the container and the edge equipment, deleting the container, establishing the mapping relation between the second new container and the edge equipment in the edge gateway equipment, and starting the application function of the second new container to trigger the second new container to independently operate.
7. The method of claim 6, wherein the step of providing the first layer comprises,
after said running said first new container, said method further comprises:
if the model interaction fails, the first new container is exited and stopped, the first new container is deleted, and the stopped operation of the container is restored;
after said running said second new container, said method further comprises:
and if the model interaction fails, the second new container is exited and stopped, the second new container is deleted, and the stopped operation of the container is restored.
8. An edge device management apparatus, applied to an edge gateway device, comprising:
the device determining module is used for determining edge devices triggering the edge gateway devices to change management states;
a container determining module, configured to determine a container created for the edge device in the edge gateway device; the container configuration information of the container is generated according to the equipment configuration information of the edge equipment;
a container processing module for executing a process adapted to the management state change on the container in response to the management state change;
the container determining module is further used for identifying the type of the management state change triggered by the target edge device; the target edge device is the edge device triggering the edge gateway device to generate management state change, and the type of the management state change at least comprises edge device access, edge device disconnection and edge device update; according to the type of the management state change, the type of the target edge equipment is confirmed; the types of the target edge devices comprise edge devices which are accessed to the edge gateway device and edge devices which are newly accessed to the edge gateway device; and according to the type of the target edge equipment, confirming a container corresponding to the target edge equipment in the edge gateway equipment.
9. An edge gateway device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010795820.XA CN111917588B (en) | 2020-08-10 | 2020-08-10 | Edge device management method, device, edge gateway device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010795820.XA CN111917588B (en) | 2020-08-10 | 2020-08-10 | Edge device management method, device, edge gateway device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111917588A CN111917588A (en) | 2020-11-10 |
| CN111917588B true CN111917588B (en) | 2023-06-06 |
Family
ID=73283542
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010795820.XA Active CN111917588B (en) | 2020-08-10 | 2020-08-10 | Edge device management method, device, edge gateway device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111917588B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112565030A (en) * | 2020-11-24 | 2021-03-26 | 广东电网有限责任公司电力调度控制中心 | Edge gateway proxy method and device based on message queue telemetry transmission |
| CN114244706B (en) * | 2021-11-30 | 2022-07-29 | 慧之安信息技术股份有限公司 | Edge device access method and system based on rule type protocol conversion engine |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106169994A (en) * | 2016-06-29 | 2016-11-30 | 中国联合网络通信集团有限公司 | The method of controlling security communicated between container and device |
| US9667509B1 (en) * | 2015-01-26 | 2017-05-30 | Amdocs Software Systems Limited | System, method, and computer program for secluding a service in a network based on network function virtualization (NFV) |
| KR20190134285A (en) * | 2018-05-25 | 2019-12-04 | 현대오토에버 주식회사 | Container-based edge-gateway and system |
| CN110569109A (en) * | 2019-09-11 | 2019-12-13 | 广州虎牙科技有限公司 | container updating method, control node and edge node |
| CN110968400A (en) * | 2019-12-18 | 2020-04-07 | 深圳奇迹智慧网络有限公司 | Application program execution method and device, computer equipment and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017053319A1 (en) * | 2015-09-22 | 2017-03-30 | Mobile Iron, Inc. | Containerized architecture to manage internet-connected devices |
| CN106302448B (en) * | 2016-08-15 | 2020-03-13 | 中国联合网络通信集团有限公司 | Remote access control method and device |
| CN109067890B (en) * | 2018-08-20 | 2021-06-29 | 广东电网有限责任公司 | CDN node edge computing system based on docker container |
| CN109600380B (en) * | 2018-12-19 | 2020-11-10 | 北京创鑫旅程网络技术有限公司 | Data transmission method and device |
| CN111212134A (en) * | 2019-12-31 | 2020-05-29 | 北京金山云网络技术有限公司 | Request message processing method and device, edge computing system and electronic equipment |
-
2020
- 2020-08-10 CN CN202010795820.XA patent/CN111917588B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9667509B1 (en) * | 2015-01-26 | 2017-05-30 | Amdocs Software Systems Limited | System, method, and computer program for secluding a service in a network based on network function virtualization (NFV) |
| CN106169994A (en) * | 2016-06-29 | 2016-11-30 | 中国联合网络通信集团有限公司 | The method of controlling security communicated between container and device |
| KR20190134285A (en) * | 2018-05-25 | 2019-12-04 | 현대오토에버 주식회사 | Container-based edge-gateway and system |
| CN110569109A (en) * | 2019-09-11 | 2019-12-13 | 广州虎牙科技有限公司 | container updating method, control node and edge node |
| CN110968400A (en) * | 2019-12-18 | 2020-04-07 | 深圳奇迹智慧网络有限公司 | Application program execution method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111917588A (en) | 2020-11-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7634681B2 (en) | Failure recovery method | |
| US11907561B2 (en) | Data backup method and apparatus | |
| CN105933391A (en) | Node capacity expansion method, device and system | |
| CN107005426B (en) | Method and device for managing life cycle of virtual network function | |
| CN111917588B (en) | Edge device management method, device, edge gateway device and storage medium | |
| CN111651523B (en) | MySQL data synchronization method and system of Kubernetes container platform | |
| CN109325016B (en) | Data migration method, device, medium and electronic equipment | |
| CN102355369A (en) | Virtual clustered system as well as processing method and processing device thereof | |
| WO2019061352A1 (en) | Data loading method and device | |
| CN102932409B (en) | The method and system that a kind of virtual machine moves online | |
| JP6663478B2 (en) | Data migration method and computer system | |
| CN104866234A (en) | Data migration method, device and system | |
| CN112052230B (en) | Multi-machine room data synchronization method, computing device and storage medium | |
| CN106814977A (en) | The management method and system of the multi-path software based on many storage manufacturers | |
| WO2021120968A1 (en) | Server capacity expansion method and capacity expansion system | |
| CN101877655A (en) | Network management system, network management server and method | |
| CN113515316A (en) | Novel edge cloud operating system | |
| CN104793981A (en) | Online snapshot managing method and device for virtual machine cluster | |
| US20020073409A1 (en) | Telecommunications platform with processor cluster and method of operation thereof | |
| CN104517067A (en) | Method, device and system for data access | |
| CN107168774B (en) | Virtual machine migration method and system based on local storage | |
| CN113835834A (en) | K8S container cluster-based computing node capacity expansion method and system | |
| US8812900B2 (en) | Managing storage providers in a clustered appliance environment | |
| CN112328429A (en) | Hard disk snapshot method and device based on Openstack | |
| CN115220737A (en) | Mirror image deployment method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Room 86, room 406, No.1, Yichuang street, Zhongxin Guangzhou Knowledge City, Huangpu District, Guangzhou City, Guangdong Province Applicant after: Southern Power Grid Digital Grid Research Institute Co.,Ltd. Address before: 511458 Room 1301, Chengtou Building, 106 Fengze East Road, Nansha District, Guangzhou City, Guangdong Province (self-compiled 1301-12159) Applicant before: Southern Power Grid Digital Grid Research Institute Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230410 Address after: Full Floor 14, Unit 3, Building 2, No. 11, Middle Spectra Road, Huangpu District, Guangzhou, Guangdong 510700 Applicant after: China Southern Power Grid Digital Grid Technology (Guangdong) Co.,Ltd. Address before: Room 86, room 406, No.1, Yichuang street, Zhongxin Guangzhou Knowledge City, Huangpu District, Guangzhou City, Guangdong Province Applicant before: Southern Power Grid Digital Grid Research Institute Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |