CN114826869A - Device management method and device management system - Google Patents
Device management method and device management system Download PDFInfo
- Publication number
- CN114826869A CN114826869A CN202210212979.3A CN202210212979A CN114826869A CN 114826869 A CN114826869 A CN 114826869A CN 202210212979 A CN202210212979 A CN 202210212979A CN 114826869 A CN114826869 A CN 114826869A
- Authority
- CN
- China
- Prior art keywords
- edge
- interface
- management system
- device management
- equipment
- 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.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 390
- 230000006978 adaptation Effects 0.000 claims abstract description 51
- 230000004048 modification Effects 0.000 claims abstract description 22
- 238000012986 modification Methods 0.000 claims abstract description 22
- 238000000034 method Methods 0.000 claims description 32
- 238000004891 communication Methods 0.000 claims description 14
- 230000006870 function Effects 0.000 claims description 13
- 230000008859 change Effects 0.000 claims description 10
- 230000004044 response Effects 0.000 claims description 6
- 239000000306 component Substances 0.000 description 48
- 239000010410 layer Substances 0.000 description 20
- 238000010586 diagram Methods 0.000 description 19
- 238000005516 engineering process Methods 0.000 description 10
- 230000002567 autonomic effect Effects 0.000 description 6
- 239000008186 active pharmaceutical agent Substances 0.000 description 5
- 238000004590 computer program Methods 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000002085 persistent effect Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 239000002131 composite material Substances 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 239000002355 dual-layer Substances 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
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/04—Network management architectures or arrangements
- H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
-
- 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
- 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
-
- 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/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Abstract
The present disclosure relates to a device management method and a device management system. The device management system includes an edge device management system, an edge computing system, and an interface adaptation module. The edge computing system includes an interface layer including at least one device management interface. The interface adaptation module is adapted to the device management interface. The interface adaptation module is connected with the edge device management system and is used for realizing the interface function represented by the device management interface. The edge computing system interacts with the edge device management system via a device management interface and an interface adaptation module. Therefore, the edge computing system and the edge equipment management system are decoupled, better downward compatibility is realized, and the existing equipment management system can be accessed to the edge computing system with smaller adaptation and modification cost in a non-invasive manner.
Description
Technical Field
The present disclosure relates to the field of cloud computing technologies, and in particular, to an equipment management method and an equipment management system.
Background
The cloud-going pace of the traditional enterprise is further accelerated by external factors such as new crown epidemic situation, cloud-going subsidy, new capital construction and the like, the cloud-going of the enterprise is normalized day by day, and a traditional central cloud computing mode is generally adopted. However, with The rapid development of technologies such as 5G, IoT (The Internet of Things), The number of edge devices is increased explosively, according to The statistical data of global system for mobile communications association (GSMA), The number of devices of The Internet of Things increases rapidly in 2010-2020, and The composite increase rate reaches 19%; the number of internet of things devices (including cellular and non-cellular) networking worldwide in 2025 is expected to reach about 246 hundred million.
Due to the demands for time delay, data privacy, and the like, edge computing is widely applied to various industries such as autopilot, agriculture, energy, transportation, and the like. Cloud-native technologies and concepts, represented by containers, microservices, DevOps (a method to automate processes between development and operation), emphasize loosely-coupled architecture and simple, convenient, and extensible capabilities, aiming to achieve consistent cloud computing experience across different infrastructures through unified standards. Compared with the current development, operation and maintenance mode, the cloud is native and is more suitable for the scene of edge cloud computing, integrated application distribution and cooperative management can be provided for the cloud edge, and the problems of large-scale application delivery, operation and maintenance and management and control of the edge side are solved. The trend that cloud edge-end integration is realized by cloud primary sinking is increasingly shown.
Because various heterogeneous devices can be produced in the edge scene facing the market demand, along with the gradual technology upgrading process, the complexity of the mass device terminals is determined, including the diversity of communication protocols and architecture composition, the complexity of the network environment and the non-uniformity of data interface standards, and the like, and the characteristics bring great challenges to the aspects of operation and maintenance management of edge nodes and devices, improvement of the reliability of edge application, resource utilization rate and the like. Meanwhile, for the existing IOT equipment management solution, the management and control of the equipment and the deployment of the application are split, and under the trend of cloud originality, how to perform cloud edge unified management is also a great challenge.
Therefore, there is a need for a non-intrusive, edge cloud native smart device management scheme with better downward ecological compatibility.
Disclosure of Invention
The technical problem to be solved by the present disclosure is to provide a non-intrusive edge cloud native smart device management scheme with better downward ecological compatibility.
According to a first aspect of the present disclosure, there is provided a device management system including: an edge device management system; an edge computing system comprising an interface layer, the interface layer comprising at least one device management interface; and the interface adaptation module is connected with the edge equipment management system and is used for realizing the interface function represented by the equipment management interface, and the edge computing system interacts with the edge equipment management system through the equipment management interface and the interface adaptation module.
Optionally, the edge computing system includes a cloud node and at least one edge node, the edge node includes a device management component, the edge device management system connects to the physical device and obtains device state management data of the physical device, the device management component obtains the device state management data from the edge device management system via a device management interface and an interface adaptation module, and the device management component further sends the device state management data to the cloud node.
Optionally, the device management interface includes an information acquisition interface and/or an operation interface, where the information acquisition interface is used to acquire information of the edge device management system, and the operation interface is used to operate a physical device connected to the edge device management system; and/or the interface adaptation module comprises an identity query plug-in and/or a device state operation plug-in, wherein the identity query plug-in is used for querying information of the edge device management system, and the device state operation plug-in is used for accessing device state management data of physical devices connected with the edge device management system.
Optionally, in response to a change of the device state represented by the device state management data in the cloud node from the first device state to the second device state, the cloud node sends the modification information to the device management component, the device management component sends the modification information to the edge device management system via the operation interface and the device state operation plug-in, and the edge device management system converts the modification information into an operation instruction and sends the operation instruction to the physical device, so as to switch the device state of the physical device from the first device state to the second device state.
Optionally, the device management component obtains the device state management data of the physical device by calling the device state operation plug-in, and sends the device state management data to the cloud node, so as to update the device state management data stored in the cloud node.
Optionally, the device management component monitors a change condition of information of the edge device management system in the cloud node, if the edge device management system which meets the condition and is not bound to the device management component is monitored, the device management component and the edge device management system are bound, the state of the edge device management system is updated to be bound, and the device management component is connected with an interface adaptation module connected with the edge device management system through a device management interface according to resource information of the edge device management system in the cloud node.
Optionally, the device state management data in the cloud node includes: device configuration information for describing a configuration and/or resources of the physical device; and/or device service information, which is used for describing a communication mode between the physical device and the edge device management system; and/or device information defining the physical device and device configuration information and/or device service information associated with the physical device.
According to a second aspect of the present disclosure, there is provided a device management method, including: providing, by an edge computing system, an interface layer, the interface layer including at least one device management interface; and deploying an interface adaptation module adapted to the device management interface so that the edge computing system interacts with the edge device management system via the device management interface and the interface adaptation module, wherein the interface adaptation module is connected with the edge device management system and is used for realizing an interface function represented by the device management interface.
Optionally, the edge computing system includes a cloud node and at least one edge node, the edge node includes a device management component, and the method further includes: the edge device management system is connected with the physical device to obtain the device state management data of the physical device, and the device management component obtains the device state management data from the edge device management system through the device management interface and the interface adaptation module and sends the device state management data to the cloud end node.
Optionally, the device management interface includes an information acquisition interface and/or an operation interface, where the information acquisition interface is used to acquire information of the edge device management system, and the operation interface is used to interact with the edge device management system to operate a physical device connected to the edge device management system; and/or the interface adaptation module comprises an identity query plug-in and/or a device state operation plug-in, wherein the identity query plug-in is used for querying information of the edge device management system, and the device state operation plug-in is used for accessing device state management data of physical devices connected with the edge device management system.
Optionally, the method further comprises: in response to the fact that the device state represented by the device state management data in the cloud node is modified from the first device state to the second device state, the cloud node sends modification information to the device management component; the equipment management component sends the modification information to the edge equipment management system through the operation interface and the equipment state operation plug-in; and the edge device management system converts the modification information into an operation instruction and sends the operation instruction to the physical device so as to switch the device state of the physical device from the first device state to the second device state.
According to a third aspect of the present disclosure, there is provided a computing device comprising: a processor; and a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method as described in the second aspect above.
According to a fourth aspect of the present disclosure, there is provided a computer program product comprising executable code which, when executed by a processor of an electronic device, causes the processor to perform the method according to the second aspect as described above.
According to a fifth aspect of the present disclosure, there is provided a non-transitory machine-readable storage medium having stored thereon executable code which, when executed by a processor of an electronic device, causes the processor to perform the method of the second aspect as described above.
According to the method, the interface layer comprising at least one equipment management interface is abstracted by the edge computing system, and the interface adaptation module adapted to the equipment management interface is realized by the edge equipment management system, so that the edge computing system and the edge equipment management system are decoupled, better downward compatibility is realized, and the existing equipment management system can be accessed to the edge computing system with lower adaptation change cost in a non-intrusive way.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent by describing in greater detail exemplary embodiments thereof with reference to the attached drawings, in which like reference numerals generally represent like parts throughout.
Fig. 1 shows a schematic structural diagram of a device management system according to an embodiment of the present disclosure.
Fig. 2 shows a schematic structural diagram of a device management system according to another embodiment of the present disclosure.
Fig. 3 shows a schematic structural diagram of a device management system according to another embodiment of the present disclosure.
FIG. 4 illustrates a schematic diagram of object model abstraction for a physical device.
Fig. 5 shows a schematic diagram defining an edge device management platform instance.
Fig. 6 shows a call flow diagram of the device management interface.
Fig. 7 is a schematic overall flow chart showing how to operate and manage the edge device in the cloud.
FIG. 8 shows a schematic structural diagram of a computing device, according to one embodiment of the present disclosure.
Detailed Description
Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
A central cloud is an internet-based computing approach by which shared software and hardware resources and information can be provided to computers and other devices on demand. Typical cloud computing providers often offer general-purpose Web applications that can be accessed through software such as a browser or other Web service, with both the software and data stored on the server. Cloud computing services typically provide common online business applications that are accessed through a browser, and software and data may be stored in a data center.
The edge cloud computing is constructed on an edge infrastructure between a central cloud and terminal equipment, is the sinking of cloud computing capacity from the center to the edge, and emphasizes that the application requirements which cannot be met in a centralized cloud computing mode are solved through integration and cooperative management of cloud edges.
Cloud-native is a set of technologies, which is beneficial for organizations to construct and run elastically extensible applications in novel dynamic environments such as public cloud, private cloud, hybrid cloud and the like. Representative technologies of cloud-native include containers, service grids, microservices, immutable infrastructure, and declarative APIs. These techniques enable the construction of a loosely coupled system that is fault tolerant, easy to manage, and easy to observe. In conjunction with reliable automation, cloud-native technology enables engineers to easily make frequent and predictable major changes to the system.
The Edge computing is divided into three parts, namely 'Cloud', 'Far Edge' and 'Near Edge', and respectively corresponds to a common public Cloud (public Cloud)/private Cloud, an IDC (Internet data center)/CDN (content delivery network or content delivery network) node under the Cloud and an equipment terminal; namely a commonly-called three-layer structure of cloud, edge and end. By sinking the central cloud computing power to the edge computing step by step, mass data generated by the edge device can be processed nearby, low time delay and privacy are met, and meanwhile occupation of network bandwidth is greatly reduced.
In a process of incorporating management of a physical device (also referred to as a physical end device, an end device, a terminal device, or an edge device) into a cloud-side computing platform (also referred to as an edge computing system or an edge computing platform), the following problems mainly exist when a cloud native technology is adopted to solve device management and data processing: 1. from the technical implementation point of view, it is difficult to implement efficient cloud edge-end integration cooperation either by changing the overall system architecture (for example, packing and sinking the entire control plane and Kubelet in kubernets to the edge side); or it is difficult to heavily modify core components (e.g., the logic of mashup device management in Kubelet) to get new properties of the upstream community in a timely manner; 2. the standardized definition and abstraction of the object model and the corresponding data analysis processing flow under the cloud native visual angle are lacked; 3. the existing device management system (also called a device management platform) cannot be adapted, and ecological compatibility is insufficient.
It is therefore an object of the present disclosure to provide a non-intrusive, more ecological-downward-compatible device management scheme.
Fig. 1 shows a schematic structural diagram of a device management system according to an embodiment of the present disclosure.
As shown in fig. 1, the device management system may include an edge computing system 110, an edge device management system 120, and an interface adaptation module 123. The edge computing system may also be referred to as an edge computing platform and the edge device management system may also be referred to as an edge device management platform.
The edge computing system 110 includes an interface layer 111, the interface layer 111 including at least one device management interface (device management API). API is an abbreviation for Application Programming Interface.
The interface adaptation module 123 is adapted to the device management interface, and is configured to implement an interface function represented by the device management interface. That is, the device management interface defines one or more interface functions, and the interface adaptation module 123 is configured to implement the interface functions defined by the device management interface. The device management interface may implement the interface function defined by the device management interface by calling the interface adaptation module 123.
The interface functionality characterized by the device management interface may refer to functionality that interacts with the edge device management system 120. For example, the device management interface may include an interface that acquires information from the edge device management system 120, an interface that operates on a physical device to which the edge device management system 120 is connected.
The interface adaptation module 123 may include a plurality of plug-ins respectively adapted to the device management interfaces, where each plug-in is used to implement the interface capability represented by the device management interface to which it is adapted. That is, the device management interface may define a method for implementing a particular capability, and the plug-in may be considered a specific implementation of the method defined by the device management interface.
The interface adaptation module 123 interfaces with the edge device management system 120. The edge computing system 110 interacts with the edge device management system 120 via a device management interface and interface adaptation module 123 in the interface layer 111.
Therefore, under the action of the interface layer 111 and the interface adaptation module 123, the edge computing system 110 and the edge device management system 120 can be decoupled, better downward compatibility is realized, and the existing device management platform can be migrated (i.e., accessed) to the edge computing system with smaller adaptation change cost in a non-intrusive manner.
For example, when migrating an existing edge device management system into an edge computing system, only an interface adaptation module (e.g., a plug-in) for implementing a device management interface needs to be provided by a manufacturer of the edge device management system, and the edge device management system can be non-invasively accessed into the edge computing system through such a small adaptation change, so that the existing edge device management system has better downward compatibility.
The edge computing system may be a cloud edge computing platform built based on kubernets (K8s, a distributed architecture solution based on container technology). The edge computing system can realize management, operation and maintenance of the edge nodes and the application thereof under the condition of unstable cloud edge network environment, and simultaneously reuse the capacity of the node pool thereof, thereby realizing closed loop of the application flow of the edge node pool level.
Fig. 2 shows a schematic structural diagram of a device management system according to another embodiment of the present disclosure.
As shown in fig. 2, the device management system may include a cloud node, at least one edge node, and at least one edge device management system. In this embodiment, the edge computing system may include a cloud node and an edge node. Optionally, the physical device located at the terminal may also be included in the edge computing system.
The Cloud node is located in the Cloud (Cloud), i.e., the central Cloud.
The edge node and the edge device management system are located at the edge end, namely the edge cloud.
The edge cloud may include a plurality of edge nodes, the edge nodes in the edge cloud may be logically divided into different edge node pools according to a geographic network environment, and applications and services in each edge node pool implement a closed-loop traffic.
Each edge node may associate (i.e., bind) one or more edge device management systems. Different edge nodes may be associated with different edge device management systems. The edge device management system may be considered to be deployed within a pool of edge nodes in which the edge nodes associated therewith reside.
The edge device management system is used for discovering the physical device, connecting the discovered physical device and acquiring the device state management data of the connected physical device. The edge node may obtain device state management data (which may also be referred to as device state management and control data) from the edge device management platform and send the device state management data to the cloud end node. Therefore, the physical equipment found by the side can be mapped to the cloud in time.
In response to the device state management data in the cloud node being modified, the cloud node may send modification information to the edge device management system via the edge node, the edge device management system managing the device state of the physical device based on the modification information. Therefore, the user can achieve the purposes of operation, maintenance and management of complex physical equipment in a cloud-native manner only by modifying the cloud data (for example, declaratively modifying the field corresponding to the attribute of the equipment desired to be controlled in the equipment state management data).
The device state management data in the cloud node may be data that is obtained by performing physical model abstraction on the physical device and that can highly summarize the state of the physical device. The physical model (device twin) defines the digital representation of an entity (such as a sensor, an on-board device, an industrial device, etc.) in a physical space in a cloud-native system, and describes the basic characteristics (what) of the entity, the main capabilities (what can be done), the data produced (what information can be conveyed) from the dimensions of attributes, services and events.
Device state management data resulting from the object model abstraction of a physical Device may include, but is not limited to, Device configuration information (Device profile), Device service information (Device service), and Device information (Device).
The operation of object model abstraction on the physical device may be performed by an edge node (e.g., a device management component in the edge node). That is, the device state management data acquired by the edge device management system may be information related to the physical device directly acquired from the physical device, which is not abstracted by the object model and cannot highly summarize the state of the physical device. After receiving the information sent by the edge device management system, the edge node may perform object model abstraction on the physical device based on the information, so as to obtain the three types of information capable of highly summarizing the state of the physical device.
Device configuration information (which may also be referred to as a device profile) is used to describe the configuration and/or resources of a physical device. The device configuration information describes a type of device using the same protocol, including some general information such as manufacturer name, device description, and device model number. The device configuration information also defines the type of resources (e.g., temperature, humidity) that such devices provide and how to read/write these resources.
The device service information is used to describe the communication mode between the physical device and the edge device management system. The device service information can be regarded as an abstraction for an edge connector interacting with the device, and defines how to access the device to the edge device management system, including information of a communication protocol, a communication address, and the like of the device.
The device information is used to define the physical devices and device configuration information and/or device service information associated with the physical devices. Each device information may associate a device configuration information and a device service information. The device information may be considered an abstraction for real-world mid-end devices, such as: appliances, alarm systems, hvac equipment, lighting, sensors, etc. that give detailed definitions of specific devices, including associated device configuration information (which type of device they belong to), associated device service information (what communication means to use), and device specific attributes (such as the on-off status of the lighting device, etc.).
The edge device management system may be an edge device management platform instance created for a physical device for which management is desired. Each edge device management platform instance may represent an edge device management solution. The communication means, operation interfaces, etc. exposed by different edge device management platform instances may be different. In the case where there are multiple edge device management platform instances, it would be a very complicated and repetitive project if the edge computing system were to fit each edge device management platform instance on a one-to-one basis.
To decouple the edge computing system from the edge device management system, the present disclosure provides that the edge computing system can abstract out an interface layer, and the edge device management system provides end device management capabilities for the edge computing system by providing an interface adaptation module (plug-in, e.g., device management platform plug-in) that adapts the device management interface in the interface layer.
The device management interface may be deployed in a pool of edge nodes for invocation by the edge nodes. The edge node may also include a device management component. The equipment management system also comprises an interface adaptation module adapted to the equipment management interface, and the interface adaptation module is connected with the edge equipment management system. The device management component interacts with the edge device management system via a device management interface and an interface adaptation module. The interface adaptation module may be deployed in an edge computing system (e.g., a pool of edge nodes) for the device management component in the edge node to communicate with.
The device management interface may include an information acquisition interface and/or an operation interface. The information acquisition interface is used for acquiring information of the edge device management system, and the operation interface is used for operating the physical device connected with the edge device management system.
Accordingly, the interface adaptation module includes an identity query plug-in and/or a device state operation plug-in. The identity query plug-in is adaptive to the information acquisition interface and is used for querying the information of the edge equipment management system. The device state operation plug-in is adapted to the operation interface and is used for accessing the device state management data of the physical device connected with the edge device management system.
In response to a change in the device state represented by the device state management data in the cloud node from the first device state to the second device state, the cloud node may send the change information to the device management component. The device management component may send the modification information to the edge device management system via the operations interface and the device state operations plug-in. The edge device management system may convert the modification information into an operation instruction to be sent to the physical device, so as to switch the device state of the physical device from the first device state to the second device state.
The device management component can also obtain the device state management data of the physical device by calling the device state operation plug-in, and send the device state management data to the cloud end node, so as to update the device state management data stored in the cloud end node. That is, the device state management data in the second device state may be sent to the edge node via the device state operation plug-in and the operation interface, and the edge node sends the device state management data to the cloud end node for updating, so as to map the real-time state of the physical device to the cloud end.
The details of the present disclosure are further described below in conjunction with specific embodiments.
Fig. 3 shows a schematic structural diagram of a device management system according to another embodiment of the present disclosure. As shown in fig. 3, all devices may be hosted in the same cluster, and may be divided into three layers, a central cloud, an edge cloud, and an end device, according to geographic location.
The central cloud includes cloud nodes. Cloud Control panels (such as kubernets Control Panel components) and Cloud Control components (such as Cloud Controllers) are deployed on the Cloud nodes. The edge node and the end device can upload the core management and control data of the edge node and the end device to the cloud for storage as resources through an interface service component (Kubernets API Server). The core management data (i.e. the above-mentioned device status management data) of the end device may include three resources related to device management: device, Device profile, and Device service.
The operation of the administrator on cluster resources (such as device state management data) stored in the cloud and related to the end device can be transmitted to the edge node, and transmitted to the corresponding edge device management platform through the edge node, and finally the edge device management platform executes corresponding operation on the end device, so that the purpose that the edge device is influenced by a cloud native mode can be achieved.
The edge cloud may include a large number of edge nodes, and different edge nodes are logically divided into different node pools according to a geographic network environment, and applications and services in each node pool implement a closed-loop traffic.
Each edge node may include an edge autonomic element (Hub element) that is coupled to the cloud interface service element. The edge autonomic element is operable to provide edge autonomic capabilities for the edge nodes. For example, the edge autonomic element may cache cloud data, and when a cloud edge breaks a network, some or all system elements in the edge node may obtain data from the edge autonomic element to implement edge autonomy.
A Device management component (Device Controller) may communicate with the interface services component via an edge autonomic component (Hub component). The edge node realizes communication with an edge Device management Platform (Device management Platform) by calling a Device management Interface (Device Interface) by a Device management component and a Device management Platform plug-in (Device management Platform plug-in) which is adapted to the Device management Interface and realized by an edge Device management Platform supplier.
The edge device management platform is deployed in the edge node pool, various physical devices (such as IoT devices) are continuously discovered and accessed downwards, device state management data is cached, and when the data is monitored to be modified by the device management component, modified content is transmitted to the physical devices, so that the purpose of influencing the physical devices is achieved.
End devices (i.e., terminal devices) may include physical devices supporting various communication protocols, supporting various functions, such as: temperature and humidity sensor, photosensitive sensor, traffic lights, etc. The end device can access the nearby edge device management platform through wireless network, Bluetooth and other modes, and the state of the end device is controlled by the edge device management platform. The end device may input/receive program and data results from the communication facility to the edge device management platform.
FIG. 4 illustrates a schematic diagram of object model abstraction for a physical device.
As shown in fig. 4, the Device state management data obtained by abstracting the physical model of the physical Device mainly includes three types of Device information (Device), Device configuration information (Device profile), and Device service information (Device service).
The device information is associated with a device configuration information and a device service information, respectively.
The Device service information may include Device Registration information (Device Registration), Device Communication information (Device Communication), and Device Data acquisition information (Device Data acquisition). For example, the Device service information may include addressing information, which may specifically include a Device IP Address (Device IP Address), a Device Port (Device Port), and a Device Endpoint Address (Device Endpoint)/Uniform Resource Identifier (URI).
The device configuration information may include Vendor specific device attributes (Vendor specific device attributes), device resource Type (Type of device resources), and supported instructions (Type of supported command). The device resource type may refer to a type of data collected from device. For example, the device configuration information may include a Value Descriptor, and the Value Descriptor (Value Descriptor) may specifically include a device resource Description (Description of the device resource) and a device resource Format (Format of the device resource). The device resource format may refer to a 64-bit integer data type (int64), a boolean type (bool), and the like.
The present disclosure may also define an edge device management platform instance. Data obtained by defining the edge device management platform instance can be regarded as resource information of the edge device management platform and stored in a cloud, and the resource information can include but is not limited to platform basic information, how the platform accesses information, and with whom the platform is bound, and the like.
Fig. 5 shows a schematic diagram defining an edge device management platform instance.
As shown in fig. 5, the resource information obtained by defining the edge device management platform instance may include a Description of the edge device management platform (Description of the device management platform), platform Binding information (Binding information about the device platform), and a platform Access method (Access method of the device management platform).
In order to decouple the edge computing platform and the edge device management platform, an interface layer is abstracted in this embodiment, the edge device management platform implements corresponding plug-ins by adapting device management interfaces in the interface layer, and provides end device management capability for the cloud native edge computing platform, and the detailed definitions of the interfaces are as follows:
1. interface (information acquisition interface) for acquiring basic information of edge device management platform
2. Interface (operation interface) interacting with equipment platform and adding, deleting, modifying and checking resources on edge equipment platform
The interfaces can be called by a gRPC (open source remote procedure call system).
An edge Device management Platform provider needs to provide two components, namely, a Device management Platform instance (DMP) and a Device management Platform plug-in (DMPP).
The edge device management platform provides its corresponding cr (storage resource). The interface layer may provide a corresponding crd (custom Resource definition) for edge device management to manage the accessed existing edge device management platform. CR is used to represent a custom resource in Kubernetes. CRD is the definition of CR, i.e., used to describe CR.
Fig. 6 shows a call flow diagram of the device management interface.
As shown in fig. 6, assuming that a device management platform provider provides an edge device management platform instance and implements a plug-in interacting with the platform, a sequence diagram of related device management platform plug-in deployment and interface call is as follows:
1. an administrator creates a DMP resource in the cluster;
2. the equipment management component can observe the change of the DMP resources through the interface service component, when the DMP resources which meet the conditions and are not bound are displayed in the state, the state of the DMP resources is updated, and the equipment management component and the DMP resources are displayed to be bound;
3. the equipment management component is connected with the DMPP according to the information (how to connect the corresponding DMPP, including the entrance, the identity information and the like) in the DMP resource;
4. the equipment management component determines the basic information and the health state of the platform by calling an Identity interface of the DMPP;
5. if the edge Device management platform operates normally, the Device management component communicates with the edge Device management platform through Device, Device profile, Device service and other operation interfaces to control the edge instance (i.e. physical Device) accessing the platform.
After the following basic environment and components are built, the edge device can be operated and managed at the cloud end:
1. an edge computing platform base environment;
2. the method comprises the steps that extended resource definitions such as Device, Device profile, Device service and Device management platform are registered in a cluster (such as a cloud), so that the cluster can support the addition, deletion, modification and check of the resources;
3. the equipment management platform supplier provides and installs the adapted edge equipment management scheme, namely deploys the edge equipment management platform instance and the edge equipment management platform plug-in;
4. the device management platform supplier provides and installs the adapted edge device management scheme, namely deploys the edge device management platform instance and the edge device management platform plug-in.
Fig. 7 is a schematic overall flow chart showing how to operate and manage the edge device in the cloud.
As shown in fig. 7, the DMPP includes an Identity query interface (i.e., the above-mentioned Identity query plug-in) and a Device/Device profile/Device service operation interface (i.e., the above-mentioned Device status operation plug-in), which may specifically include an add-on interface createjxx (.), a delete interface DeleteXXX (. -), and a modify interface UpdateXXX (·). The overall process of operating and managing the edge device at the cloud end comprises the following steps:
1. the Device management component calls a related interface realized by a Device management platform plug-in to acquire the state of the platform and the state data of the currently accessed platform Device, and abstracts the state data into Device, Device profile and Device service;
2. the Device management component synchronizes the Device, the Device profile and the Device service to the cloud end through the interface service component;
3. the method comprises the following steps that an administrator monitors the existing equipment state of a cloud in real time, and directly modifies the expected state of certain equipment when needed, such as changing the color of a small lamp into red;
4. the Device management component monitors the Device, the Device profile and the Device service resource of the cloud in real time, and returns the expected state data of the resource related to the cloud to the Device management component in real time if the expected state data of the resource is changed;
5. the device management component calls interfaces such as CreateXXX (.), DeleteXXX (.)) or UpdateXXX (.)) of the DMPP to send a device resource modification message;
6. the DMPP sends the modification condition of the cloud resource to an edge device management platform example through remote calling;
7. the edge device management platform instance converts the state modification content into related communication content to be transmitted to the actual physical end device, for example: changing the color of the small lamp to red;
8. the device management component obtains the real-time status of the device by calling the UpdateXXX (a.) interface of the DMPP,
9. the device management component synchronizes the real-time state of the device to the cloud end;
10. the administrator observes the state of the actual physical end Device by observing the data changes of the Device, Device profile and Device service resources in the cluster.
In conclusion, the object model abstraction is performed on the end equipment, the control state of the end equipment can be highly summarized, and meanwhile, a whole set of cloud native IOT end equipment management API is provided, so that cloud native management of the end equipment is realized, and uniform cloud native management of enterprise IT and OT system management is facilitated; the Kubernetes non-intrusive edge cloud native device management solution can seamlessly issue complete cloud native control capability to the layer of the terminal on the basis of not losing cloud native characteristics, and has good upward compatibility; according to the method, an interface layer is abstracted, various edge device management platforms realize corresponding plug-ins through adapting the interfaces, and therefore end device management capacity can be provided for the cloud native edge computing platform, decoupling of the edge computing platform and the edge device management platform is achieved, better downward compatibility is achieved, and the existing IOT device management platform can be migrated with the minimum adaptation change cost.
The present disclosure may also be implemented as a device management method, such as may be an edge cloud native smart device management method.
An interface layer may be provided by the edge computing system, the interface layer including at least one device management interface. And deploying an interface adaptation module (such as a plug-in) adapted to the device management interface so that the edge computing system interacts with the edge device management system via the device management interface and the device management platform plug-in, wherein the interface adaptation module is connected with the edge device management system, and the interface adaptation module is used for realizing the interface function represented by the device management interface.
An edge computing system may include a cloud node and at least one edge node, the edge node including a device management component. The method may further comprise: the edge device management system is connected with the physical device to obtain the device state management data of the physical device, and the device management component obtains the device state management data from the edge device management system through the device management interface and the interface adaptation module and sends the device state management data to the cloud end node. For details concerning the process, reference may be made to the relevant description above.
Fig. 8 shows a schematic structural diagram of a computing device that can be used to implement the device management method according to an embodiment of the present disclosure.
Referring to fig. 8, computing device 800 includes memory 810 and processor 820.
The processor 820 may be a multi-core processor or may include multiple processors. In some embodiments, processor 820 may include a general-purpose host processor and one or more special coprocessors such as a Graphics Processor (GPU), a Digital Signal Processor (DSP), or the like. In some embodiments, processor 820 may be implemented using custom circuitry, such as an Application Specific Integrated Circuit (ASIC) or a Field Programmable Gate Array (FPGA).
The memory 810 may include various types of storage units, such as system memory, Read Only Memory (ROM), and permanent storage. Wherein the ROM may store static data or instructions for the processor 820 or other modules of the computer. The persistent storage device may be a read-write storage device. The persistent storage may be a non-volatile storage device that does not lose stored instructions and data even after the computer is powered off. In some embodiments, the persistent storage device employs a mass storage device (e.g., magnetic or optical disk, flash memory) as the persistent storage device. In other embodiments, the permanent storage may be a removable storage device (e.g., floppy disk, optical drive). The system memory may be a read-write memory device or a volatile read-write memory device, such as a dynamic random access memory. The system memory may store instructions and data that some or all of the processors require at runtime. In addition, the memory 810 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), magnetic and/or optical disks, may also be employed. In some embodiments, memory 810 may include a removable storage device that is readable and/or writable, such as a Compact Disc (CD), a read-only digital versatile disc (e.g., DVD-ROM, dual layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (e.g., SD card, min SD card, Micro-SD card, etc.), a magnetic floppy disc, or the like. Computer-readable storage media do not contain carrier waves or transitory electronic signals transmitted by wireless or wired means.
The memory 810 has stored thereon executable code, which when processed by the processor 820, causes the processor 820 to perform the device management methods described above.
The device management system, method and computing device according to the present invention have been described in detail above with reference to the accompanying drawings.
Furthermore, the method according to the invention may also be implemented as a computer program or computer program product comprising computer program code instructions for carrying out the above-mentioned steps defined in the above-mentioned method of the invention.
Alternatively, the invention may also be embodied as a non-transitory machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) having stored thereon executable code (or a computer program, or computer instruction code) which, when executed by a processor of an electronic device (or computing device, server, etc.), causes the processor to perform the steps of the above-described method according to the invention.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (12)
1. A device management system, comprising:
an edge device management system;
an edge computing system comprising an interface layer comprising at least one device management interface; and
an interface adaptation module adapted to the device management interface, the interface adaptation module being connected to the edge device management system, the interface adaptation module being configured to implement an interface function characterized by the device management interface,
the edge computing system interacts with the edge device management system via the device management interface and the interface adaptation module.
2. The device management system of claim 1,
the edge computing system comprises a cloud end node and at least one edge node,
the edge node includes a device management component that,
the edge device management system is connected with the physical device to acquire the device state management data of the physical device,
the device management component acquires the device state management data from the edge device management system through the device management interface and the interface adaptation module, and sends the device state management data to the cloud node.
3. The device management system of claim 2, wherein,
the equipment management interface comprises an information acquisition interface and/or an operation interface, the information acquisition interface is used for acquiring the information of the edge equipment management system, and the operation interface is used for operating the physical equipment connected with the edge equipment management system; and/or
The interface adaptation module comprises an identity query plug-in and/or an equipment state operation plug-in, wherein the identity query plug-in is used for querying the information of the edge equipment management system, and the equipment state operation plug-in is used for accessing the equipment state management data of the physical equipment connected with the edge equipment management system.
4. The device management system of claim 3, wherein,
in response to a device state characterized by the device state management data in the cloud node being modified from a first device state to a second device state, the cloud node sending modification information to the device management component,
the device management component sends the modification information to the edge device management system via the operation interface and the device state operation plug-in,
and the edge device management system converts the modification information into an operation instruction and sends the operation instruction to the physical device so as to switch the device state of the physical device from the first device state to the second device state.
5. The device management system of claim 4, wherein,
the device management component acquires the device state management data of the physical device by calling the device state operation plug-in and sends the device state management data to the cloud node so as to update the device state management data stored in the cloud node.
6. The device management system of claim 2, wherein,
the equipment management component monitors the change condition of the edge equipment management system information in the cloud end node,
if the edge device management system which meets the conditions and is not bound with the device management component is monitored, the device management component and the edge device management system are bound, the state of the edge device management system is updated to be bound,
and the equipment management component is connected with an interface adaptation module connected with the edge equipment management system through the equipment management interface according to the resource information of the edge equipment management system in the cloud node.
7. The device management system of any of claims 2 to 6, wherein the device state management data in the cloud nodes comprises:
device configuration information for describing a configuration and/or resources of the physical device; and/or
The equipment service information is used for describing a communication mode between the physical equipment and the edge equipment management system; and/or
Device information for defining the physical device and device configuration information and/or device service information associated with the physical device.
8. A device management method, comprising:
providing, by an edge computing system, an interface layer, the interface layer comprising at least one device management interface;
deploying an interface adaptation module adapted to the device management interface to enable the edge computing system to interact with the edge device management system via the device management interface and the interface adaptation module, wherein the interface adaptation module is connected to the edge device management system and is configured to implement an interface function characterized by the device management interface.
9. The method of claim 8, wherein the edge computing system comprises a cloud node and at least one edge node, the edge node comprising a device management component, the method further comprising:
connecting the physical device by the edge device management system, acquiring device state management data of the physical device,
and the equipment management component acquires the equipment state management data from the edge equipment management system through the equipment management interface and the interface adaptation module and sends the equipment state management data to the cloud end node.
10. The method of claim 8, wherein,
the equipment management interface comprises an information acquisition interface and/or an operation interface, the information acquisition interface is used for acquiring the information of the edge equipment management system, and the operation interface is used for operating the physical equipment connected with the edge equipment management system; and/or
The interface adaptation module comprises an identity query plug-in and/or an equipment state operation plug-in, wherein the identity query plug-in is used for querying the information of the edge equipment management system, and the equipment state operation plug-in is used for accessing the equipment state management data of the physical equipment connected with the edge equipment management system.
11. The method of claim 10, further comprising:
in response to the device state represented by the device state management data in the cloud node being modified from a first device state to a second device state, the cloud node sending modification information to the device management component;
the equipment management component sends the modification information to the edge equipment management system through the operation interface and the equipment state operation plug-in;
and the edge device management system converts the modification information into an operation instruction and sends the operation instruction to the physical device so as to switch the device state of the physical device from the first device state to the second device state.
12. A computing device, comprising:
a processor; and
a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method of any of claims 8 to 11.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210212979.3A CN114826869B (en) | 2022-03-04 | 2022-03-04 | Device management method and device management system |
| PCT/CN2023/078853 WO2023165483A1 (en) | 2022-03-04 | 2023-02-28 | Device management method and device management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210212979.3A CN114826869B (en) | 2022-03-04 | 2022-03-04 | Device management method and device management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114826869A true CN114826869A (en) | 2022-07-29 |
| CN114826869B CN114826869B (en) | 2023-11-28 |
Family
ID=82528609
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210212979.3A Active CN114826869B (en) | 2022-03-04 | 2022-03-04 | Device management method and device management system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114826869B (en) |
| WO (1) | WO2023165483A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023165483A1 (en) * | 2022-03-04 | 2023-09-07 | 阿里巴巴（中国）有限公司 | Device management method and device management system |
| CN117118981A (en) * | 2023-10-19 | 2023-11-24 | 广州翼辉信息技术有限公司 | Industrial cloud platform communication method based on CODESYS programming environment |
Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109617796A (en) * | 2018-11-15 | 2019-04-12 | 江苏东洲物联科技有限公司 | A kind of edge calculations gateway of rule-based engine |
| CN111049876A (en) * | 2019-10-18 | 2020-04-21 | 烽火通信科技股份有限公司 | Lightweight telecom cloud edge computing system architecture |
| CN111314149A (en) * | 2020-02-26 | 2020-06-19 | 赛特斯信息科技股份有限公司 | System for realizing unified monitoring operation and maintenance management based on multiple edge cloud platforms |
| CN111629040A (en) * | 2020-05-20 | 2020-09-04 | 中移雄安信息通信科技有限公司 | Cloud edge coordination method, device, system, equipment and medium |
| CN111800283A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Network system, service providing and resource scheduling method, device and storage medium |
| CN111901173A (en) * | 2020-07-30 | 2020-11-06 | 山东超越数控电子股份有限公司 | Cloud edge cooperative system construction method, device, equipment and readable medium |
| CN112165479A (en) * | 2020-09-22 | 2021-01-01 | 北京智芯微电子科技有限公司 | Cloud edge cooperative management and control system of power distribution network |
| CN112202900A (en) * | 2020-09-30 | 2021-01-08 | 无锡雪浪数制科技有限公司 | Novel-architecture edge computing system |
| US10986184B1 (en) * | 2019-03-05 | 2021-04-20 | Edjx, Inc. | Systems and methods for it management of distributed computing resources on a peer-to-peer network |
| US20210132976A1 (en) * | 2019-11-03 | 2021-05-06 | Microsoft Technology Licensing, Llc | Cloud-based managed networking service that enables users to consume managed virtualized network functions at edge locations |
| CN112769938A (en) * | 2021-01-12 | 2021-05-07 | 烽火通信科技股份有限公司 | Kubernetes cloud edge communication system and method based on QUIC |
| CN112839072A (en) * | 2020-10-19 | 2021-05-25 | 南京中兴新软件有限责任公司 | Data processing method, device, system, computer equipment and readable medium |
| CN113114482A (en) * | 2021-03-08 | 2021-07-13 | 中国—东盟信息港股份有限公司 | Container-based hybrid cloud management system and method |
| CN113296903A (en) * | 2021-02-01 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Edge cloud system, edge control method, control node and storage medium |
| CN113515350A (en) * | 2021-07-29 | 2021-10-19 | 广州高维网络科技有限公司 | Hybrid cloud computing management platform |
| WO2021208780A1 (en) * | 2020-04-14 | 2021-10-21 | 中兴通讯股份有限公司 | Management method for cdn function virtualization, electronic device, and computer readable medium |
| CN113566864A (en) * | 2021-09-03 | 2021-10-29 | 合肥米克光电技术有限公司 | Distributed machine vision system based on 5G and edge calculation |
| CN113676512A (en) * | 2021-07-14 | 2021-11-19 | 阿里巴巴新加坡控股有限公司 | Network system, resource processing method and equipment |
| CN113708974A (en) * | 2021-09-03 | 2021-11-26 | 南方电网数字电网研究院有限公司 | Edge cloud network system based on self-adaptive networking and cooperation method |
| CN113741282A (en) * | 2021-09-06 | 2021-12-03 | 山东恒远智能科技有限公司 | Intelligent management system and method for equipment based on edge computing |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105245427A (en) * | 2015-11-24 | 2016-01-13 | 深圳酷宅科技有限公司 | Multi-Internet of Things cloud platform terminal access and control system based on bus adaption |
| US20180084085A1 (en) * | 2016-09-20 | 2018-03-22 | Arrayent, Inc. | Cross platform device virtualization for an iot system |
| CN109743401A (en) * | 2019-01-30 | 2019-05-10 | 南京我在智能科技有限公司 | A kind of intelligent device management system based on Internet of Things edge calculations server |
| CN111049930A (en) * | 2019-12-26 | 2020-04-21 | 广州鲁邦通物联网科技有限公司 | IOT agent layer and communication method |
| CN111416845B (en) * | 2020-03-12 | 2023-09-26 | 腾讯云计算（北京）有限责任公司 | Method, device and storage medium for configuring edge equipment |
| CN114826869B (en) * | 2022-03-04 | 2023-11-28 | 阿里巴巴（中国）有限公司 | Device management method and device management system |
-
2022
- 2022-03-04 CN CN202210212979.3A patent/CN114826869B/en active Active
-
2023
- 2023-02-28 WO PCT/CN2023/078853 patent/WO2023165483A1/en unknown
Patent Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109617796A (en) * | 2018-11-15 | 2019-04-12 | 江苏东洲物联科技有限公司 | A kind of edge calculations gateway of rule-based engine |
| US10986184B1 (en) * | 2019-03-05 | 2021-04-20 | Edjx, Inc. | Systems and methods for it management of distributed computing resources on a peer-to-peer network |
| CN111800283A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Network system, service providing and resource scheduling method, device and storage medium |
| CN111049876A (en) * | 2019-10-18 | 2020-04-21 | 烽火通信科技股份有限公司 | Lightweight telecom cloud edge computing system architecture |
| US20210132976A1 (en) * | 2019-11-03 | 2021-05-06 | Microsoft Technology Licensing, Llc | Cloud-based managed networking service that enables users to consume managed virtualized network functions at edge locations |
| CN111314149A (en) * | 2020-02-26 | 2020-06-19 | 赛特斯信息科技股份有限公司 | System for realizing unified monitoring operation and maintenance management based on multiple edge cloud platforms |
| WO2021208780A1 (en) * | 2020-04-14 | 2021-10-21 | 中兴通讯股份有限公司 | Management method for cdn function virtualization, electronic device, and computer readable medium |
| CN111629040A (en) * | 2020-05-20 | 2020-09-04 | 中移雄安信息通信科技有限公司 | Cloud edge coordination method, device, system, equipment and medium |
| CN111901173A (en) * | 2020-07-30 | 2020-11-06 | 山东超越数控电子股份有限公司 | Cloud edge cooperative system construction method, device, equipment and readable medium |
| CN112165479A (en) * | 2020-09-22 | 2021-01-01 | 北京智芯微电子科技有限公司 | Cloud edge cooperative management and control system of power distribution network |
| CN112202900A (en) * | 2020-09-30 | 2021-01-08 | 无锡雪浪数制科技有限公司 | Novel-architecture edge computing system |
| CN112839072A (en) * | 2020-10-19 | 2021-05-25 | 南京中兴新软件有限责任公司 | Data processing method, device, system, computer equipment and readable medium |
| CN112769938A (en) * | 2021-01-12 | 2021-05-07 | 烽火通信科技股份有限公司 | Kubernetes cloud edge communication system and method based on QUIC |
| CN113296903A (en) * | 2021-02-01 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Edge cloud system, edge control method, control node and storage medium |
| CN113114482A (en) * | 2021-03-08 | 2021-07-13 | 中国—东盟信息港股份有限公司 | Container-based hybrid cloud management system and method |
| CN113676512A (en) * | 2021-07-14 | 2021-11-19 | 阿里巴巴新加坡控股有限公司 | Network system, resource processing method and equipment |
| CN113515350A (en) * | 2021-07-29 | 2021-10-19 | 广州高维网络科技有限公司 | Hybrid cloud computing management platform |
| CN113566864A (en) * | 2021-09-03 | 2021-10-29 | 合肥米克光电技术有限公司 | Distributed machine vision system based on 5G and edge calculation |
| CN113708974A (en) * | 2021-09-03 | 2021-11-26 | 南方电网数字电网研究院有限公司 | Edge cloud network system based on self-adaptive networking and cooperation method |
| CN113741282A (en) * | 2021-09-06 | 2021-12-03 | 山东恒远智能科技有限公司 | Intelligent management system and method for equipment based on edge computing |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023165483A1 (en) * | 2022-03-04 | 2023-09-07 | 阿里巴巴（中国）有限公司 | Device management method and device management system |
| CN117118981A (en) * | 2023-10-19 | 2023-11-24 | 广州翼辉信息技术有限公司 | Industrial cloud platform communication method based on CODESYS programming environment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114826869B (en) | 2023-11-28 |
| WO2023165483A1 (en) | 2023-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2014278314B2 (en) | Distributed lock management in a cloud computing environment | |
| US9661064B2 (en) | Systems and methods for deploying legacy software in the cloud | |
| CN113296927A (en) | Construction method of service grid instance, service grid system and multi-cluster system | |
| CN114826869B (en) | Device management method and device management system | |
| WO2019127418A1 (en) | Network service management method, related device and system | |
| CN106953848B (en) | Software defined network implementation method based on ForCES | |
| CN112202615B (en) | Multi-CNI cooperative work system and method | |
| CN111371679A (en) | Method for realizing API gateway based on kubernets and Kong | |
| CN113296950B (en) | Processing method, processing device, electronic equipment and readable storage medium | |
| US9507748B2 (en) | Platform runtime abstraction | |
| CN111010304A (en) | Method for integrating Dubbo service and Kubernetes system | |
| CN113301116A (en) | Cross-network communication method, device, system and equipment for microservice application | |
| CN103685608A (en) | Method and device for automatically configuring IP (Internet Protocol) address of security virtual machine | |
| CN112035217A (en) | Cluster processing method and device, electronic equipment and computer readable storage medium | |
| CN115086166B (en) | Computing system, container network configuration method, and storage medium | |
| US20110035477A1 (en) | Network clustering technology | |
| JP2024501005A (en) | Management method and device for container clusters | |
| CN115378944B (en) | Network system, service grid configuration method, storage medium and electronic equipment | |
| CN115048060B (en) | Storage management method and device, electronic equipment and storage medium | |
| CN116506295A (en) | Method, device, equipment and medium for constructing service function chain of containerized virtual network element | |
| US10841119B1 (en) | Device representation management using representation types | |
| US11695632B1 (en) | Management and control across heterogeneous edge devices of a client network using device abstractions | |
| CN115361389B (en) | Cloud computing instance creating method and device | |
| US9992282B1 (en) | Enabling heterogeneous storage management using storage from cloud computing platform | |
| US11704159B2 (en) | System and method for unified infrastructure architecture |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |