CN114826869B - Device management method and device management system - Google Patents
Device management method and device management system Download PDFInfo
- Publication number
- CN114826869B CN114826869B CN202210212979.3A CN202210212979A CN114826869B CN 114826869 B CN114826869 B CN 114826869B CN 202210212979 A CN202210212979 A CN 202210212979A CN 114826869 B CN114826869 B CN 114826869B
- Authority
- CN
- China
- Prior art keywords
- edge
- interface
- device management
- management system
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 390
- 230000006978 adaptation Effects 0.000 claims abstract description 49
- 230000004048 modification Effects 0.000 claims abstract description 25
- 238000012986 modification Methods 0.000 claims abstract description 25
- 230000006870 function Effects 0.000 claims abstract description 16
- 238000000034 method Methods 0.000 claims description 27
- 238000004891 communication Methods 0.000 claims description 15
- 230000004044 response Effects 0.000 claims description 4
- 230000008859 change Effects 0.000 claims description 3
- 239000000306 component Substances 0.000 description 56
- 239000010410 layer Substances 0.000 description 17
- 238000010586 diagram Methods 0.000 description 15
- 238000005516 engineering process Methods 0.000 description 9
- MKGIQRNAGSSHRV-UHFFFAOYSA-N 1,1-dimethyl-4-phenylpiperazin-1-ium Chemical compound C1C[N+](C)(C)CCN1C1=CC=CC=C1 MKGIQRNAGSSHRV-UHFFFAOYSA-N 0.000 description 8
- 230000002085 persistent 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 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 235000006085 Vigna mungo var mungo Nutrition 0.000 description 1
- 240000005616 Vigna mungo var. mungo Species 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 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
- 239000002360 explosive Substances 0.000 description 1
- 230000037406 food intake Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000004801 process automation 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
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 comprises an edge device management system, an edge computing system and an interface adaptation module. The edge computing system includes an interface layer that includes 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 equipment management system and is used for realizing interface functions represented by the equipment management interface. The edge computing system interacts with the edge device management system via the device management interface and the interface adaptation module. Thus, the decoupling of the edge computing system and the edge device management system realizes better downward compatibility, and the existing device management system can be connected into the edge computing system with smaller adaptation and modification cost in a non-invasive way.
Description
Technical Field
The disclosure relates to the technical field of cloud computing, in particular to a device management method and a device management system.
Background
External factors such as new crown epidemic situation, cloud-up subsidy, new capital construction and the like further accelerate the cloud-up pace of the traditional enterprises, the cloud-up of the enterprises is gradually normalized, 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, internet of things) and the like, the number of edge devices is increased in an explosive manner, and according to the statistical data display of global system for mobile communications (GSMA), the number of global internet of things devices is increased at a high speed in 2010-2020, and the composite growth rate is up to 19%; the 2025 worldwide internet of things devices (including cellular and non-cellular) are expected to be up to about 246 billions in number.
Edge computing is widely used in various industries such as autopilot, agriculture, energy, traffic, etc. for demands such as latency and data privacy. Cloud native technologies and concepts represented by containers, micro services, devOps (a method of implementing process automation between development and operation) emphasize loosely coupled architecture and simple and convenient expansion capabilities, aiming at implementing consistent cloud computing experience across different infrastructures through unified standards. Compared with the current development operation and maintenance mode, the cloud native is more suitable for the scene of edge cloud computing, can provide integrated application distribution and collaborative management for the cloud edge, and solves the problems of large-scale application delivery, operation and maintenance and management and control of the edge side. The trend of realizing the integration of the cloud edge end by the cloud primary sinking is increasingly apparent.
The edge scene is oriented to market demands to produce various heterogeneous devices, and the complexity of the mass device terminals, including the diversity of communication protocols and architecture components, the complexity of the network environment where the terminal is located, the dissimilarity of data interface standards and the like are determined along with the gradual technology upgrading process, so that 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, utilization rate of resources and the like. Meanwhile, for the existing IOT device management solution, the management and control of the devices and the deployment of the applications are cut, and under the trend of cloud native, how to perform unified management of cloud edge is also a great challenge.
Therefore, there is a need for a non-invasive, better downward ecological compatibility edge cloud native smart device management scheme.
Disclosure of Invention
The technical problem to be solved by the present disclosure is to provide a non-invasive edge cloud native intelligent device management scheme with better downward ecological compatibility.
According to a first aspect of the present disclosure, there is provided 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 the interface adaptation module is adapted to the equipment management interface, the interface adaptation module is connected with the edge equipment management system, the interface adaptation module is used for realizing interface functions 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 is connected with the physical device, device state management data of the physical device is obtained, 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, the information acquisition interface is used for acquiring information of the edge device management system, and the operation interface is used for operating physical devices connected with the edge device management system; and/or the interface adaptation module comprises an identity inquiry plug-in and/or a device state operation plug-in, wherein the identity inquiry plug-in is used for inquiring information of the edge device management system, and the device state operation plug-in is used for accessing device state management data of the physical device connected with the edge device management system.
Optionally, in response to the device state characterized by the device state management data in the cloud node modifying 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 acquires device state management data of the physical device by calling a device state operation plug-in, and sends the device state management data to the cloud node to update the device state management data stored in the cloud node.
Optionally, the device management component monitors the change condition of the 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 with the device management component is monitored, the device management component binds with the edge device management system, 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 the 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 describing configuration and/or resources of the physical device; and/or device service information describing a communication manner 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 the edge computing system, an interface layer comprising at least one device management interface; an interface adaptation module adapted to the device management interface is deployed 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 the interface adaptation module is used for realizing interface functions represented by the device management interface.
Optionally, the edge computing system includes a cloud node and at least one edge node, the edge node including a device management component, the method further comprising: the edge equipment management system is connected with the physical equipment to acquire equipment state management data of the physical equipment, 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 node.
Optionally, the device management interface includes 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 interacting with the edge device management system to operate physical devices connected with the edge device management system; and/or the interface adaptation module comprises an identity inquiry plug-in and/or a device state operation plug-in, wherein the identity inquiry plug-in is used for inquiring information of the edge device management system, and the device state operation plug-in is used for accessing device state management data of the physical device connected with the edge device management system.
Optionally, the method further comprises: responding to the device state characterized by the device state management data in the cloud node to modify from the first device state to the second device state, and sending modification information to the device management component by the cloud node; the device management component sends the modification information to the edge device management system through the operation interface and the device state operation plug-in; 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 as described in the second aspect 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 a method as described in the second aspect above.
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 decoupling of the edge computing system and the edge equipment management system is realized, better downward compatibility is realized, and the existing equipment management system can be accessed to the edge computing system with smaller adaptation cost in a non-invasive way.
Drawings
The foregoing and other objects, features and advantages of the disclosure will be apparent from the following more particular descriptions of exemplary embodiments of the disclosure as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts throughout exemplary embodiments of the disclosure.
Fig. 1 illustrates a schematic structure of a device management system according to an embodiment of the present disclosure.
Fig. 2 illustrates a schematic structure of a device management system according to another embodiment of the present disclosure.
Fig. 3 illustrates a schematic structure of a device management system according to another embodiment of the present disclosure.
Fig. 4 shows a schematic diagram of object model abstraction for a physical device.
FIG. 5 illustrates a schematic diagram of defining an edge device management platform instance.
Fig. 6 shows a schematic call flow diagram of the device management interface.
Fig. 7 shows an overall flow diagram of how to manage edge devices in cloud operation.
Fig. 8 illustrates a structural schematic 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.
The central cloud is an internet-based computing manner by which shared software and hardware resources and information can be provided to computers and other devices as needed. Typical cloud computing providers often provide 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 a server. Cloud computing services typically provide a generic online commerce application accessed through a browser, software and data can be stored in a data center.
The edge cloud computing is constructed on an edge infrastructure between the central cloud and the terminal equipment, the cloud computing capability sinks from the center to the edge, and the application requirements which cannot be met under the centralized cloud computing mode are emphasized through the integration and collaborative management of cloud edges.
Cloud protogenesis is a collection of a series of technologies which are beneficial to each organization to construct and run elastically expandable applications in novel dynamic environments such as public cloud, private cloud, hybrid cloud and the like. Representative technologies for cloud proto include containers, service grids, micro-services, immutable infrastructure, and declarative APIs. These techniques enable the construction of loosely coupled systems that are fault tolerant, easy to manage and easy to observe. In combination with reliable automation means, cloud-based technology enables engineers to easily make frequent and predictable significant changes to the system.
The Edge calculation is divided into three parts, namely 'Cloud', 'Far Edge', 'Near Edge', which respectively correspond to common public Cloud (public Cloud)/private Cloud, cloud IDC (internet data center)/CDN (content delivery network) nodes and equipment terminals; namely a three-layer structure of cloud, edge and end. By sinking the central cloud computing force step by step to the edge computing, massive data generated by the edge device are processed nearby, low time delay and privacy are met, and occupation of network bandwidth is greatly reduced.
In the process of incorporating management of physical devices (also referred to as physical end devices, terminal devices or edge end devices) into a cloud computing platform (also referred to as an edge computing system or edge computing platform), the following problems mainly exist when the cloud technology is adopted to solve device management and data processing: 1. from the technical realization point of view, it is difficult to realize efficient cloud-edge end integrated coordination by changing the whole system architecture (for example, sinking the whole control plane and Kubelet package in Kubernetes to the edge side); or it is difficult to obtain new characteristics of upstream communities in time by severely modifying core components (e.g., logic that mashes up a large number of device management in Kubelet); 2. lack of standardized definition and abstraction of object models and corresponding data analysis and processing flows under the view angle of cloud protogenesis; 3. the existing device management system (also referred to as a device management platform) cannot be adapted, and the downward ecological compatibility is insufficient.
It is therefore an object of the present disclosure to propose a device management scheme that is non-invasive, better in downward ecological compatibility.
Fig. 1 illustrates a schematic structure 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. Edge computing systems may also be referred to as edge computing platforms, and edge device management systems may also be referred to as edge device management platforms.
The edge computing system 110 includes an interface layer 111, the interface layer 111 including at least one device management interface (device management API). The API is an abbreviation for Application Programming Interface (application programming interface).
The interface adapting module 123 is adapted to the device management interface, and is configured to implement interface functions 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 interface functions defined by the device management interface by calling the interface adaptation module 123.
The interface functions characterized by the device management interface may refer to functions that interact with the edge device management system 120. For example, the device management interface may include an interface to obtain information from the edge device management system 120, an interface to operate physical devices 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 one by one, each plug-in being configured to implement interface capabilities characterized by the device management interface to which it is adapted. That is, the device management interface may define a method for implementing a specific capability, and the plug-in may be regarded as a specific implementation of the method defined by the device management interface.
The interface adaptation module 123 is connected to 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.
Thus, 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, so that better downward compatibility is realized, and the existing device management platform can be non-invasively migrated (i.e. accessed) to the edge computing system with smaller adaptation and modification cost.
For example, for an existing edge device management system, when the edge device management system is migrated into an edge computing system, only an interface adaptation module (such as a plug-in) for realizing 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 the minor adaptation, so that the edge device management system has better downward compatibility.
The edge computing system may be a cloud computing platform built based on Kubernetes (K8 s, a distributed architecture solution based on container technology). The edge computing system can realize the management operation and maintenance of the edge node and the application thereof under the condition of unstable cloud edge network environment, and simultaneously multiplexes the capacity of the node pool thereof, thereby realizing the application flow closed loop of the edge node pool level.
Fig. 2 illustrates a schematic structure 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. Alternatively, the physical device at the terminal may also be included in the edge computing system.
The Cloud node is located in the Cloud (Cloud), i.e., the center Cloud.
The edge nodes and the edge device management system are located at the edge end, i.e., edge cloud.
The edge cloud can comprise a plurality of edge nodes, the edge nodes in the edge cloud can be logically divided into different edge node pools according to the geographic network environment, and applications and services in each edge node pool realize flow closed loop.
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 where the edge nodes associated therewith reside.
The edge device management system is used for discovering physical devices, connecting the discovered physical devices and acquiring device state management data of the connected physical devices. The edge node may obtain device state management data (also referred to as device state management data) from the edge device management platform and send the device state management data to the cloud 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 device state of the physical device being managed by the edge device management system based on the modification information. Therefore, the user only needs to modify cloud data (for example, declaratively modify fields corresponding to the device attributes desired to be managed in the device state management data), namely, the purpose of operating, maintaining and managing complex physical devices can be achieved in a cloud native mode.
The device state management data in the cloud node may refer to data, which is obtained by performing object model abstraction on the physical device and can highly summarize the state of the physical device. The object model (device twinning) defines a digitized representation of an entity (e.g., sensor, in-vehicle device, industrial equipment, etc.) in physical space in a cloud proto-system, and describes the essential features of the entity (what is), primary capabilities (what can do), and the resulting data (what information can be transferred), from the dimensions of attributes, services, events, etc.
Device state management data resulting from object model abstraction of a physical Device may include, but is not limited to, device configuration information (DeviceProfile), device service information (DeviceService), and Device information (Device).
The operations of object model abstraction of a 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 abstract 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 can abstract the physical device according to the information to obtain the three kinds of information capable of highly summarizing the state of the physical device.
Device configuration information (which may also be referred to as a device configuration file) is used to describe the configuration and/or resources of the 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 manner of communication between the physical device and the edge device management system. Device service information may be viewed as an abstraction for the edge connector that interacts with the device, defining how to access the device to an edge device management system, including information about the device's communication protocol, communication address, etc.
The device information is used to define the physical device and device configuration information and/or device service information associated with the physical device. Each device information may be associated with one device configuration information and device service information. Device information may be considered an abstraction for end devices in the real world, such as: appliances, alarm systems, hvac equipment, lighting, sensors, etc., which give detailed definitions of specific equipment, including associated equipment configuration information (which class of equipment to which it belongs), associated equipment service information (which communication mode to use), and equipment specific attributes (e.g., on-off status of lighting equipment, etc.).
The edge device management system may be an edge device management platform instance created for the physical device that is desired to be managed. Each edge device management platform instance may characterize an edge device management solution. The manner of communication, the operation interface, etc., exposed by the different edge device management platform instances may vary. In the case where there are multiple edge device management platform instances, this would be a very complex and repetitive project if the edge computing system were to be adapted one-to-one with each edge device management platform instance.
To decouple the edge computing system from the edge device management system, the present disclosure proposes that the edge computing system can abstract an interface layer, and that the edge device management system provides end device management capabilities to the edge computing system by providing an interface adaptation module (plug-in, such as a device management platform plug-in) that adapts the device management interfaces in the interface layer.
The device management interface may be deployed in an edge node pool for invocation by the edge node. The edge node may also include a device management component. The device management system also comprises an interface adapting module adapting to the device management interface, and the interface adapting module is connected with the edge device 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., an edge node pool) for device management components in the edge nodes to communicate therewith.
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 equipment management system, and the operation interface is used for operating the physical equipment connected with the edge equipment management system.
Accordingly, the interface adaptation module comprises an identity inquiry plug-in and/or a device state operation plug-in. The identity inquiry plug-in is matched with the information acquisition interface and is used for inquiring the information of the edge equipment management system. The device state operation plug-in is adapted to the operation interface for accessing device state management data of the physical device connected to the edge device management system.
In response to a device state characterized by device state management data in the cloud node modifying from a first device state to a second device state, the cloud node may send modification information to the device management component. The device management component may send the modification information to the edge device management system via the operation interface and the device state operation plug-in. The edge device management system may convert the modification information into an operation instruction to be sent to the physical device 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 acquire device state management data of the physical device by calling a device state operation plug-in, and send the device state management data to the cloud node so as to update the device state management data stored in the cloud 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 node for updating, so as to map the real-time state of the physical device to the cloud.
Details of the disclosure are further described below in connection with specific embodiments.
Fig. 3 illustrates a schematic structure of a device management system according to another embodiment of the present disclosure. As shown in fig. 3, all devices may be in the same cluster, and may be classified into a center cloud, an edge cloud, and an end device according to geographic locations.
The central cloud includes cloud nodes. Cloud control panels (Cloud Control Panel, e.g., kubernetes control plane components) and cloud control components (Cloud Controllers, e.g., cloud controllers) are deployed on cloud nodes. The edge node and the end device can upload core control data of the edge node and the end device as resources to the cloud for storage through an interface service component (Kubernetes API Server). The core management data of the end device (i.e., the device state management data mentioned above) may include three resources related to device management: device, deviceProfile and DeviceService.
The operations of the manager on cluster resources (such as equipment state management data) related to the end equipment, which are stored in the cloud, can be transferred to the edge nodes, and transferred to the corresponding edge equipment management platforms through the edge nodes, and finally the corresponding operations are executed on the end equipment by the edge equipment management platforms, so that the purpose that the cloud primary mode influences the edge equipment can be achieved.
The edge cloud may include a large number of edge nodes, and different edge nodes are logically partitioned into different node pools, with applications and services within each node pool implementing traffic closed loops, depending on the geographic network environment.
Each edge node may include an edge autonomous component (Hub component) that interfaces with an interface service component of the cloud. The edge autonomous component is operative to provide edge autonomous capabilities for the edge node. For example, the edge autonomous component may cache cloud data, and when the cloud edge breaks, some or all of the system components in the edge node may acquire data from the edge autonomous component, so as to implement edge autonomous.
The device management component (Device Controller) can communicate with the interface service component via an edge autonomous component (Hub component). The edge node enables communication with the edge Device management platform (Device Manage Platform) through a Device management Interface (Device Interface) invoked by the Device management component and a Device management platform plug-in (Device Manage Platform Plugin) implemented by an edge Device management platform vendor adapted to the Device management Interface.
The edge device management platform is deployed in the edge node pool, continuously discovers and accesses various physical devices (such as the IoT devices) downwards, caches the device state management data, and transmits the modification content to the physical devices after monitoring that the data are modified by the device management component so as to achieve the purpose of influencing the physical devices.
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 terminal equipment can be accessed to a nearby edge equipment management platform in a wireless network mode, a Bluetooth mode and the like, and the state of the terminal equipment is controlled by the edge equipment management platform. The end device may input/receive program and data results from the communication facility to the edge device management platform.
Fig. 4 shows a schematic diagram of object model abstraction for a physical device.
As shown in fig. 4, the Device state management data obtained by performing object model abstraction on 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 Ingestion). For example, the Device service information may include addressing information, which may include, in particular, a Device IP address (Device IP Address), a Device Port (Device Port), and a Device terminal address (Device Endpoint)/uniform resource identifier (URI, uniform Resource Identifier).
The device configuration information may include vendor-related device attributes (Vendor specific device attributes), device resource types (Type of device resources), and supported instructions (Type of supported command). The device resource type may refer to the type of device acquisition data (data collected from device). For example, the device configuration information may include a Value Descriptor, which may include a device resource description (Description of the device resource) and a device resource format (Format of the device resource) in particular. The device resource format may refer to a 64-bit integer data type (int 64), boolean (bool), etc.
The present disclosure may also define edge device management platform instances. The data defined for the edge device management platform instance can be regarded as resource information of the edge device management platform to be stored in the cloud, and the resource information can include, but is not limited to, platform basic information, how the platform is accessed, information of who the platform is bound with, and the like.
FIG. 5 illustrates a schematic diagram of defining an edge device management platform instance.
As shown in fig. 5, the resource information defined about the edge device management platform instance may include an edge device management platform description (Description of device manage platform), platform binding information (Binding information about the device platform), and a platform access mode (Access method of device manage platform).
In order to decouple the edge computing platform from the edge device management platform, an interface layer is abstracted in this embodiment, the edge device management platform implements a corresponding plug-in through a device management interface in the adaptation interface layer, and provides an end device management capability for the cloud native edge computing platform, and the detailed definition of the interface is as follows:
1. interface for acquiring basic information of edge equipment management platform (information acquisition interface)
2. Interface (operation interface) for interacting with equipment platform and adding, deleting and checking resources on edge equipment platform
The interfaces can be called through gRPC (open source remote procedure call system).
The edge device management platform provider needs to provide two components, an edge device management platform instance (Device Manage Platform, DMP) and a device management platform plug-in (Device Manage Platform Plugin, DMPP).
The edge device management platform provides its own corresponding CR (Custom Resource). The interface layer may provide a corresponding CRD (Custom Resource Definition) for edge device management to manage the existing edge device management platform for access. CR is used to represent a custom resource in Kubernetes. CRD is a definition of CR, i.e. to describe CR.
Fig. 6 shows a schematic 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 that interacts with the platform, the relevant device management platform plug-in deployment and interface call timing diagrams are as follows:
1. an administrator creates a DMP resource in the cluster;
2. the device management component observes the change of the DMP resource through the interface service component, and updates the state of the DMP resource when the DMP resource which meets the condition and is not yet bound is displayed in the state, and the device management component and the DMP resource are bound;
3. the device management component connects the DMPP according to information (how to connect the corresponding DMPP, including an entry, identity information, etc.) in the DMP resource;
4. the device management component determines the basic information and health state of the platform by calling the Identity interface of the DMPP;
5. If the edge device management platform is functioning properly, the device management component communicates with the edge device management platform through Device, deviceProfile and DeviceService, etc., operating interfaces to handle the edge instance (i.e., physical device) accessing the platform.
After the following basic environments and components are built, the edge device can be operated and managed at the cloud:
1. an edge computing platform base environment;
2. the Device, deviceProfile, deviceService and Device manager platform and other extended resource definitions are registered in the cluster (such as cloud) so that the cluster can support the addition, deletion and modification of the resources;
3. the equipment management platform provider provides and installs an adapted edge equipment management scheme, namely an edge equipment management platform instance and an edge equipment management platform plug-in are deployed;
4. the device management platform provider provides and installs the adapted edge device management scheme, i.e. an edge device management platform instance and an edge device management platform plug-in are deployed.
Fig. 7 shows an overall flow diagram of how to manage edge devices in cloud operation.
As shown in fig. 7, the Device management platform plug-in DMPP includes an Identity query interface (i.e., the Identity query plug-in described above) and a Device/Device profile/Device service operation interface (i.e., the Device status operation plug-in described above), and the operation interfaces may specifically include an add interface createxx (..), a delete interface deletexx (..), and a modify interface updatexx (..). The overall flow of managing the edge device at the cloud end is as follows:
1. The device management component invokes a related interface realized by a device management platform plug-in to acquire the state of the platform and the state data of the platform device which is accessed at present, and abstracts the state data into Device, deviceProfile and deviceService;
2. the equipment management component synchronizes Device, deviceProfile and DeviceService to the cloud through the interface service component;
3. the administrator monitors the existing device state of the cloud in real time, and directly modifies the expected state of a certain device when needed, such as changing the color of the small lamp into red;
4. the equipment management component monitors equipment, equipment profile and equipment service resources of the cloud in real time, and if the expected state data of the resources related to the cloud changes, the expected state data is returned to the equipment management component in real time;
5. the device management component invokes interfaces of createXXX (.+ -.), deleeXXX (.+ -.) or updateXXX (.+ -.) of the DMPP, etc., to send a device resource modification message;
6. the DMPP sends the modification condition of the cloud resource to an edge equipment management platform instance through remote call;
7. the edge device management platform instance converts the state modification content into related communication content and transmits the related communication content to actual physical end devices, 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 invoking the updatxxx (..) interface of the DMPP,
9. the device management component synchronizes the real-time state of the device to the cloud;
10. and the administrator observes the state of the actual physical terminal equipment through observing the data changes of the Device, the Device profile and the Device service resources in the cluster.
In summary, the opposite terminal equipment disclosed by the invention carries out object model abstraction, so that the management and control state of the terminal equipment can be highly summarized, and a set of cloud native IOT terminal equipment management API is provided, so that the cloud native management of the terminal equipment is realized, and the unified cloud native of enterprise IT and OT system management is conveniently realized; the method is a Kubernetes non-invasive type edge cloud primary equipment management solution, and on the basis of not losing the cloud primary characteristics, the complete cloud primary management and control capability can be issued to the end layer in a seamless manner, so that the method has good upward compatibility; the cloud native edge computing platform and the cloud native edge computing platform have the advantages that an interface layer is abstracted, various edge device management platforms realize corresponding plug-ins through adapting the interfaces, so that end device management capability can be provided for the cloud native edge computing platform, decoupling of the edge computing platform and the edge device management platform is realized, better downward compatibility is realized, and the existing IOT device management platform can be migrated with minimum adapting and changing cost.
The 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. An interface adapting module (such as a plug-in) adapted to the device management interface is deployed, 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 adapting module is connected with the edge device management system, and the interface adapting module is used for realizing interface functions represented by the device management interface.
The 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 equipment management system is connected with the physical equipment to acquire equipment state management data of the physical equipment, 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 node. Details concerning the method can be found in the above related description.
Fig. 8 illustrates a schematic diagram of a computing device that may be used to implement the device management methods described above, according to one embodiment of the present disclosure.
Referring to fig. 8, a computing device 800 includes a memory 810 and a processor 820.
Processor 820 may be a multi-core processor or may include multiple processors. In some embodiments, processor 820 may comprise a general-purpose main processor and one or more special coprocessors such as, for example, a Graphics Processor (GPU), a Digital Signal Processor (DSP), etc. In some embodiments, processor 820 may be implemented using custom circuitry, for example, an application specific integrated circuit (ASIC, application Specific Integrated Circuit) or a field programmable gate array (FPGA, field Programmable Gate Arrays).
Memory 810 may include various types of storage units, such as system memory, read Only Memory (ROM), and persistent storage. Where the ROM may store static data or instructions that are required by the processor 820 or other modules of the computer. The persistent storage may be a readable and writable storage. The persistent storage may be a non-volatile memory device that does not lose stored instructions and data even after the computer is powered down. 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 persistent storage may be a removable storage device (e.g., diskette, optical drive). The system memory may be a read-write memory device or a volatile read-write memory device, such as dynamic random access memory. The system memory may store instructions and data that are required by some or all of the processors at runtime. Furthermore, 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 disks, and/or optical disks may also be employed. In some implementations, memory 810 may include a readable and/or writable removable storage device 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 super-density optical disc, a flash memory card (e.g., SD card, min SD card, micro-SD card, etc.), a magnetic floppy disk, and the like. The computer readable storage medium does not contain a carrier wave or an instantaneous electronic signal transmitted by wireless or wired transmission.
The memory 810 has stored thereon executable code that, 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 hereinabove 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 performing the 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 flowcharts 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.
The foregoing description of embodiments of the invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or 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 various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the improvement of 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 that is an edge device management platform instance created for a physical device that is desired to be managed;
an edge computing system comprising an interface layer, the 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 interface functions 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, wherein,
the edge computing system includes a cloud node and at least one edge node,
the edge node comprises a device management component,
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 obtains the device state management data from the edge device management system via the device management interface and the interface adaptation module, and the device management component also sends the device state management data to the cloud node.
3. The device management system of claim 2, wherein,
the device management interface comprises an information acquisition interface and/or an operation interface, wherein the information acquisition interface is used for acquiring information of an edge device management system, and the operation interface is used for operating physical devices connected with the edge device management system; and/or
The interface adaptation module comprises an identity inquiry plug-in and/or a device state operation plug-in, wherein the identity inquiry plug-in is used for inquiring 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.
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,
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 device management component monitors the change condition of the information of the edge device management system in the cloud node,
if the edge equipment management system which meets the condition and is not bound with the equipment management component is monitored, the equipment management component is bound with the edge equipment management system, the state of the edge equipment 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 node comprises:
Device configuration information describing configuration and/or resources of the physical device; and/or
Device service information describing a communication mode between the physical device and the edge device management system; and/or
And the device information is used for defining the physical device and the device configuration information and/or the device service information associated with the physical device.
8. A device management method, comprising:
providing, by an edge computing system, an interface layer comprising at least one device management interface;
an interface adaptation module adapted to the device management interface is deployed, so that the edge computing system interacts with an 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, the interface adaptation module is used for realizing interface functions represented by the device management interface, and the edge device management system is an edge device management platform instance created for physical devices expected to be managed.
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:
The edge device management system is connected with the physical device to acquire the 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 node.
10. The method of claim 9, wherein,
the device management interface comprises an information acquisition interface and/or an operation interface, wherein the information acquisition interface is used for acquiring information of an edge device management system, and the operation interface is used for operating physical devices connected with the edge device management system; and/or
The interface adaptation module comprises an identity inquiry plug-in and/or a device state operation plug-in, wherein the identity inquiry plug-in is used for inquiring 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.
11. The method of claim 10, further comprising:
modifying the equipment state represented by the equipment state management data in the cloud node from a first equipment state to a second equipment state, and sending modification information to the equipment management component by the cloud node;
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;
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 CN114826869A (en) | 2022-07-29 |
| CN114826869B true 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) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114826869B (en) * | 2022-03-04 | 2023-11-28 | 阿里巴巴（中国）有限公司 | 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 (19)
| 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 |
| 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 (7)
| 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 |
| US11132217B2 (en) * | 2019-11-03 | 2021-09-28 | Microsoft Technology Licensing, Llc | Cloud-based managed networking service that enables users to consume managed virtualized network functions at edge locations |
| 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 (19)
| 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 |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114826869A (en) | 2022-07-29 |
| WO2023165483A1 (en) | 2023-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107426034B (en) | Large-scale container scheduling system and method based on cloud platform | |
| Van Steen et al. | A brief introduction to distributed systems | |
| CN114826869B (en) | Device management method and device management system | |
| CN102377796B (en) | Heterogeneous service integrating system and method based on OSGi (open service gateway initiative) | |
| Hughes et al. | LooCI: a loosely-coupled component infrastructure for networked embedded systems | |
| CN109542611A (en) | Database, that is, service system, database dispatching method, equipment and storage medium | |
| US20080270411A1 (en) | Distributed behavior controlled execution of modeled applications | |
| US20180084085A1 (en) | Cross platform device virtualization for an iot system | |
| US9692794B2 (en) | Aggregation of sensor appliances using device registers and wiring brokers | |
| CN104156216A (en) | Heterogeneous storage management system and method oriented to cloud computing | |
| WO2019057055A1 (en) | Task processing method and apparatus, electronic device, and storage medium | |
| CN113301116A (en) | Cross-network communication method, device, system and equipment for microservice application | |
| Mohamed et al. | Service-oriented middleware approaches for wireless sensor networks | |
| CN113867230A (en) | Modbus remote operation control system | |
| CN112887356A (en) | System for sharing memory data distribution service and operation method thereof | |
| US20110035477A1 (en) | Network clustering technology | |
| CN115883669A (en) | Data distribution method, system, equipment and medium | |
| US9705978B1 (en) | Dependency graph management | |
| Cavalieri et al. | Realising interoperability between opc ua and ocf | |
| US20170237687A1 (en) | Resource trees by management controller | |
| Li et al. | Multiple protocols interworking with open connectivity foundation in fog networks | |
| CN115378944B (en) | Network system, service grid configuration method, storage medium and electronic equipment | |
| Nguyen et al. | Software-defined virtual sensors for provisioning iot services on demand | |
| CN115103012B (en) | Geospatial information microservice integration system and method | |
| Gaitan et al. | An IoT middleware framework for industrial applications |
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 |