Device access method, related platform and computer storage medium

Abstract

Embodiments of the present application disclose a device access method, a related platform and a computer storage medium, wherein the method comprises: a server cluster sending a first message to an IoT platform, the first message carrying an identifier of an IoT device, and being used for requesting authentication of the IoT device; and receiving a second message returned by the IoT platform, the second message being used for indicating that the authentication of the IoT device is successful, and carrying an identifier of an IoT edge computing platform associated with the identifier of the IoT device, the IoT edge computing platform being an application program running in a container mode on the server cluster, and being used for processing service data of devices of the same type as the IoT device. By using the embodiments of the present application, the problems of plug-in incompatibility, low security performance and even performance conflict of the IoT edge computing platform can be solved due to the complex service types supported by the IoT edge computing platform.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to device access methods, related platforms, and computer storage media. Background Technology

[0002] With the rapid development of Internet of Things (IoT) technology, IoT platforms have been designed to reduce the computing load on devices and perform real-time analysis and filtering of business data from a large number of IoT devices. However, for some business scenarios with high performance requirements and massive data transmission, such as vehicle-to-everything (V2X) networks with high latency requirements, the data analysis, filtering, and compression processes in the IoT platform need to be moved to the network edge.

[0003] To realize the data processing of the aforementioned IoT platform, an IoT edge computing platform is proposed. Currently, the designed IoT edge computing platform is built on the Java Modular System (Open Service Gateway Initiative, OSGI) framework and can be used to process business data from different industries and fields. Specifically, various business plugins are deployed on the IoT edge computing platform to process corresponding types of business data, such as plugins for processing vehicle networking services. However, in practice, it has been found that to support the processing of different business data, the business plugins deployed on the IoT edge computing platform come from various industries. Because different industries and fields use different, even significantly different, communication protocols; furthermore, even within the same industry, different manufacturers' devices are designed with different communication protocols. This will lead to problems such as plugin incompatibility, low security, and even performance conflicts in the IoT edge computing platform. Summary of the Invention

[0004] This invention discloses a device access method, a related platform, and a computer storage medium. It can design a corresponding IoT edge computing platform according to the business type, so that the IoT edge computing platform can be used to process the business data of the target type of device, and can solve the problems of plug-in incompatibility, low security, and performance conflicts in the prior art.

[0005] In a first aspect, embodiments of the present invention disclose a device access method, the method comprising:

[0006] The server cluster sends a first message to the IoT platform. The first message carries the identifier of the IoT device and is used to request the IoT platform to authenticate the IoT device.

[0007] The server cluster receives a second message returned by the IoT platform. The second message indicates that the IoT platform has successfully authenticated the IoT device. The second message also carries the identifier of the IoT edge computing platform associated with the identifier of the IoT device. The IoT edge computing platform is a containerized application running on the server cluster, used to process business data of devices of the same type as the IoT device.

[0008] By implementing the embodiments of the present invention, the problems of incompatibility of plug-ins, low security performance, or even performance conflicts in the IoT edge computing platform can be solved due to the complex types of business that the IoT edge computing platform supports.

[0009] Secondly, embodiments of the present invention provide yet another device access method, the method comprising:

[0010] The IoT platform receives a first message sent by the server cluster. The first message carries the identifier of the IoT device and is used to request the IoT platform to authenticate the IoT device. The server cluster deploys an IoT edge computing platform, which is a containerized application running on the server cluster and is used to process business data of devices of the same type as the IoT device.

[0011] The IoT platform sends a second message to the server cluster. The second message indicates that the IoT device has been successfully authenticated. The second message carries the identifier of the IoT edge computing platform associated with the identifier of the IoT device. The IoT platform stores the association between the identifier of the IoT device and the identifier of the IoT edge computing platform.

[0012] In conjunction with the embodiments described in the first or second aspect of the present invention, in some possible embodiments, the IoT edge computing platform includes N containers, which are created based on the same target image. The target image includes at least one plugin that supports hot-loading deployment for processing business data of devices of the same type as the IoT device, where N is a positive integer.

[0013] In conjunction with the embodiments described in the first or second aspect of the present invention, in some possible embodiments, the IoT edge computing platform is divided according to business influencing factors. Different IoT edge computing platforms are used to process business data of different types of devices. The business influencing factors include at least one of the following: business type, industry in which the business is located, and field in which the business is located.

[0014] Specifically, embodiments of the present invention can design different IoT edge computing platforms for different business types to process business data of corresponding types of devices, achieve secure isolation between businesses, and better solve many problems existing in the prior art.

[0015] In conjunction with the embodiments described in the first or second aspect of this invention, in some possible embodiments, the IoT edge computing platform includes differentiated components deployed as plug-ins, and the IoT edge computing platform shares the same basic components; wherein, the differentiated components are applications that are different from the basic components and are used to process business data of target type devices. Specifically, the IoT edge computing platform designed by this invention can share the same basic components, and the differentiated components are deployed as plug-ins into the target image used to build the IoT edge computing platform, which can save resources.

[0016] In conjunction with the embodiments described in the first or second aspect of the present invention, in some possible embodiments, any two containers in the IoT edge computing platform support data sharing and data backup.

[0017] In conjunction with the embodiments described in the first or second aspect of the present invention, in some possible embodiments, before the IoT platform receives the first message from the IoT device sent by the server cluster, it further includes:

[0018] The IoT platform determines the server cluster based on the business needs of the target type of device;

[0019] A first creation message is sent to the server cluster. The first creation message is used to instruct the creation of the IoT edge computing platform in the server cluster. The first creation message carries a target image. The IoT edge computing platform includes N containers created based on the target image, where N is a positive integer.

[0020] Accordingly, before the server cluster sends the first message from the IoT device to the IoT platform, it also includes:

[0021] The server cluster receives a first creation message sent by the IoT platform. The first creation message is used to instruct the creation of the IoT edge computing platform in the server cluster. The first creation message carries a target image. The IoT platform at least stores the association relationship between the identifier of the IoT device and the identifier of the target image.

[0022] The server cluster creates the IoT edge computing platform in the server cluster according to the instructions of the first creation message, wherein the IoT edge computing platform includes N containers created based on the target image, where N is a positive integer.

[0023] Furthermore, in conjunction with the embodiments described in the second aspect of the present invention, in some possible embodiments, the method further includes:

[0024] The IoT platform receives a binding message sent by the IoT device, the binding message carrying the identity identifier of the IoT device;

[0025] The IoT platform determines the device description information of the IoT device based on the identity identifier and assigns the IoT device identifier to the IoT device. The IoT platform stores the association relationship between the device description information of the IoT device and the identifier of the IoT edge computing platform.

[0026] The IoT platform creates and saves the association between the device description information of the IoT device, the identifier of the IoT device, and the identifier of the IoT edge computing platform.

[0027] Specifically, the IoT platform can pre-obtain device description information (profile) of the target type device, and determine its corresponding target image (template) based on the profile. This target image is used to construct the IoT edge computing platform. That is, the IoT platform can determine the association between the profile of the target type device and the target image or the IoT edge computing platform based on the profile of the target type device. The target type device refers to a device of the same type as the IoT device. Subsequently, when the IoT platform receives a binding message from the IoT device, it determines the profile corresponding to the IoT device based on the IoT device's identity identifier in the binding message and assigns the IoT device's identifier to the IoT device. Further, the IoT platform binds and saves the association between the device description information of the IoT device, the identifier of the IoT device, and the identifier of the IoT edge computing platform.

[0028] In conjunction with the embodiments described in the first or second aspect of the present invention, in some possible embodiments, after the server cluster creates the IoT edge computing platform, the method further includes:

[0029] The server cluster sends a first registration message to the IoT platform through the main container to record the first registration message in the IoT platform; wherein, the first registration message carries the identifier of the main container, the identifier of the IoT edge computing platform and the identifier of the server cluster, and the main container is any one of the N containers.

[0030] Accordingly, the IoT platform receives the first registration message and records the first registration message.

[0031] In conjunction with the embodiments described in the first aspect of the present invention, in some possible embodiments, the method further includes:

[0032] The server cluster uses a load balancing strategy to select a target container from the N containers for processing the business data of the IoT device in the target container.

[0033] In conjunction with the embodiments described in the first or second aspect of the present invention, in some possible embodiments, the method further includes:

[0034] The server cluster sends a second registration message to the IoT platform through the target container to record the first registration message in the IoT platform; wherein the second registration message carries the identifier of the IoT device, the identifier of the target container, the identifier of the IoT edge computing platform, and the identifier of the server cluster.

[0035] Accordingly, the IoT platform receives the second registration message and records the second registration message.

[0036] In conjunction with the embodiments described in the first or second aspect of the present invention, in some possible embodiments, the method further includes:

[0037] The server cluster sends a load notification message to the IoT platform. The load notification message carries the total load of the IoT edge computing platform so that the IoT platform can determine a backup cluster based on the total load of the IoT edge computing platform in the server cluster. When the server cluster is overloaded, the backup cluster can use the IoT edge computing platform to process the business data of the IoT devices.

[0038] Accordingly, the IoT platform receives a load notification message sent by the server cluster, the load notification message carrying the total load of the IoT edge computing platform; based on the total load of the IoT edge computing platform, a backup cluster of the server cluster is determined, and the IoT edge computing platform is deployed in the backup cluster.

[0039] Furthermore, the IoT platform can also send backup notification messages to the server cluster, the backup notification messages carrying the identifier of the backup cluster.

[0040] The server cluster service overload can refer to the total load of the IoT edge computing platform in the server cluster being greater than or equal to a first threshold, or it can refer to the load of the target container in the IoT edge computing platform being greater than or equal to a second threshold (preset load threshold).

[0041] In conjunction with the embodiments described in the first or second aspect of the present invention, in some possible embodiments, the method further includes:

[0042] If the load of the target container is greater than or equal to a first threshold, the server cluster determines a backup service cluster; wherein, the server cluster stores the identifier of the backup cluster, and the IoT edge computing platform is deployed in the backup cluster;

[0043] The server cluster sends a third message to the backup cluster. The third message carries the identifier of the IoT edge computing platform and the identifier of the IoT device, instructing the backup cluster to use the IoT edge computing platform to process the business data of the IoT device.

[0044] Optionally, if the load of the target container is greater than or equal to a first threshold, the server cluster may send a service overload message to the IoT device to notify that the server cluster is under heavy load. Furthermore, it may prompt the administrator whether to add a new container within the IoT edge computing platform in the server cluster.

[0045] In some possible embodiments, the distance between the location of the backup cluster and the location of the server cluster is within a preset range. That is, the backup cluster is a cluster close to / adjacent to the server cluster, and the backup cluster also deploys the IoT edge computing platform to process the business data of the IoT devices.

[0046] In conjunction with the embodiments described in the first or second aspect of the present invention, in some possible embodiments, the method further includes:

[0047] The IoT platform sends a second creation message to the server cluster. The second creation message is used to instruct the creation of a new container in the IoT edge computing platform. The second creation message is generated by the IoT platform according to the business needs of the IoT device, or generated by the IoT platform when it receives a creation confirmation instruction. The creation confirmation instruction is used to instruct the creation of a new container in the IoT edge computing platform.

[0048] Accordingly, the server cluster receives a second creation message sent by the IoT platform; then, based on the second creation message, it creates a new container in the IoT edge computing platform so that the newly added container can be used to process business data of devices of the same type as the IoT device.

[0049] Thirdly, embodiments of the present invention disclose a server cluster, including an IoT edge computing platform and an access service instance;

[0050] The access service instance is used to send a first message to the IoT platform; wherein the first message carries the identifier of the IoT device and is used to request the IoT platform to authenticate the IoT device;

[0051] The access service instance is further configured to receive a second message returned by the IoT platform and forward it to the IoT edge computing platform. The second message is configured to indicate that the IoT device has been successfully authenticated and carries the identifier of the IoT edge computing platform associated with the identifier of the IoT device. The IoT platform stores the association relationship between the identifier of the IoT device and the identifier of the IoT edge computing platform.

[0052] The IoT edge computing platform is used to process the business data of the IoT device when the second message indicates that the IoT device has been successfully authenticated.

[0053] In some possible embodiments, the IoT edge computing platform is created based on the business needs of the IoT device, and the server cluster further includes a scheduler;

[0054] The scheduler is used to receive a service creation instruction sent by the IoT platform and create the access service instance according to the service creation instruction;

[0055] The scheduler is further configured to receive a first creation message sent by the IoT platform, and create the IoT edge computing platform in the server cluster according to the instructions of the first creation message; wherein, the first creation message carries a target image, the IoT edge computing platform includes N CIG containers created based on the target image, where N is a positive integer; the IoT platform at least stores the association relationship between the identifier of the IoT device and the identifier of the target image.

[0056] In some possible embodiments,

[0057] The IoT edge computing platform is further configured to send a first registration message to the IoT platform through the main container, so as to record the first registration message in the IoT platform; wherein, the first registration message carries the identifier of the main container, the identifier of the IoT edge computing platform and the identifier of the server cluster, and the main container is any one of the N containers.

[0058] In some possible embodiments, the IoT edge computing platform is also configured to receive a response message sent by the IoT platform, the response message carrying the address of the access service instance and the addresses of the N containers respectively.

[0059] In some possible embodiments, the scheduler is further configured to receive a second creation message sent by the IoT platform, and add a container in the IoT edge computing platform according to the indication of the second creation message; wherein the second creation message is generated by the IoT platform according to the business needs of the IoT device, or generated by the IoT platform when it receives a creation confirmation instruction, and the creation confirmation instruction is used to determine to create a new container in the IoT edge computing platform.

[0060] In some possible embodiments,

[0061] The IoT edge computing platform is further configured to, upon receiving the second message, select a target container from the N containers using a load balancing strategy, for processing the business data of the IoT device in the target container.

[0062] In some possible embodiments, the IoT edge computing platform is further configured to send a second registration message to the IoT platform through the target container to record the second registration message in the IoT platform; wherein the second registration message carries the identifier of the IoT device, the identifier of the target container, the identifier of the IoT edge computing platform, and the identifier of the server cluster.

[0063] In some possible embodiments, the IoT edge computing platform is further configured to determine a backup cluster when the load of the target container is greater than or equal to a first threshold; wherein the server cluster stores the identifier of the backup cluster, and the IoT edge computing platform is deployed in the backup cluster; and a third message is sent to the access service instance of the backup cluster through the access service instance, the third message carrying the identifier of the IoT edge computing platform and the identifier of the IoT device, to instruct the backup cluster to use the IoT edge computing platform to process the business data of the IoT device.

[0064] In some possible embodiments, the IoT edge computing platform is further configured to send a load notification message to the IoT platform, the load notification message carrying the total load of the IoT edge computing platform, so as to determine the backup cluster in the IoT platform based on the total load of the IoT edge computing platform.

[0065] Fourthly, embodiments of the present invention provide an IoT platform, including a connection management unit;

[0066] The connection management unit is used to receive a first message sent by the server cluster. The first message carries the identifier of the IoT device and is used to request the IoT platform to authenticate the IoT device. The server cluster is equipped with an IoT edge computing platform, which is a containerized application running on the server cluster and is used to process business data of devices of the same type as the IoT device.

[0067] The connection management unit is further configured to send a second message to the server cluster, the second message indicating that the IoT device has been successfully authenticated, and the second message carries the identifier of the IoT edge computing platform associated with the identifier of the IoT device, and the connection management unit stores the association relationship between the identifier of the IoT device and the identifier of the IoT edge computing platform.

[0068] In some possible embodiments, a mirror repository is also included;

[0069] The image repository is used to obtain device description information of at least one type of device, allocate corresponding images to the device description information of the at least one type of device, and send the association relationship between at least one image and the device description information of at least one type of device to the connection management module; wherein one type of device corresponds to one image.

[0070] The connection management unit is also used to store the association between the at least one image and the device description information of at least one type of device, wherein the device description information of the at least one type of device includes the device description information of the IoT device;

[0071] The connection management unit is further configured to receive a binding message sent by the IoT device, the binding message carrying the identity identifier of the IoT device; determine the device description information of the IoT device based on the identity identifier, and assign the IoT device identifier to the IoT device; wherein, the IoT platform stores the association relationship between the description information of the IoT device and the identifier of the IoT edge computing platform;

[0072] The connection management unit is also used to create an association between the device description information of the IoT device, the identifier of the IoT device, and the identifier of the IoT edge computing platform.

[0073] In some possible embodiments, a plugin repository and a cluster management unit are also included;

[0074] The plugin repository is used to store at least one plugin;

[0075] The cluster management unit is used to determine the server cluster according to the business requirements of the target type device, and send a service creation instruction to the server cluster. The service creation request is used to instruct the creation of an access service instance in the server cluster, so as to realize message transmission between the IoT device and the connection management unit through the access service instance.

[0076] The cluster management unit is further configured to send a first creation message to the server cluster. The first creation message is used to instruct the creation of the IoT edge computing platform in the server cluster. The first creation message carries a target image. The IoT edge computing platform includes N containers created based on the target image, where N is a positive integer.

[0077] In some possible embodiments,

[0078] The cluster management unit is further configured to receive a first registration message sent by the server cluster through the main container and record the first registration message; wherein the first registration message carries the identifier of the main container, the identifier of the IoT edge computing platform, and the identifier of the server cluster.

[0079] In some possible embodiments,

[0080] The cluster management unit is further configured to send a second creation message to the server cluster. The second creation message is used to instruct the creation of a new container in the IoT edge computing platform. The second creation message is generated by the IoT platform according to the business needs of the IoT device, or generated by the IoT platform when it receives a creation confirmation instruction. The creation confirmation instruction is used to instruct the creation of a new container in the IoT edge computing platform.

[0081] In some possible embodiments,

[0082] The connection management unit is further configured to receive a second registration message sent by the server cluster through the target container and record the second registration message; wherein the second registration message carries the identifier of the IoT device, the identifier of the target container, the identifier of the IoT edge computing platform and the identifier of the server cluster, and the target container is selected by the IoT edge computing platform from the N containers using a load balancing strategy to process the business data of the IoT device.

[0083] In some possible embodiments, a cluster management unit is also included;

[0084] The cluster management unit is used to receive load notification messages sent by the server cluster, the load notification messages carrying the total load of the IoT edge computing platform;

[0085] The cluster management unit is further configured to determine a backup cluster of the server cluster based on the total load of the IoT edge computing platform. The backup cluster is equipped with the IoT edge computing platform so that, in the event of overload of the server cluster, the IoT edge computing platform in the backup cluster can be used to process the business data of the IoT devices.

[0086] In some possible embodiments,

[0087] The cluster management unit is also used to send a backup notification message to the server cluster, the backup notification message carrying the identifier of the backup cluster.

[0088] For details regarding the contents not shown or described in the third or fourth aspect embodiments, please refer to the foregoing embodiments; they will not be repeated here.

[0089] Fifthly, embodiments of the present invention disclose a network device including a functional unit for performing the method described in the first aspect.

[0090] In a sixth aspect, embodiments of the present invention disclose yet another network device, including a functional unit for performing the method described in the second aspect.

[0091] In a seventh aspect, embodiments of the present invention provide yet another network device, including a memory, a communication interface, and a processor coupled to the memory and the communication interface; the memory is used to store instructions, the processor is used to execute the instructions, and the communication interface is used to communicate with other network devices under the control of the processor; wherein, when the processor executes the instructions, it performs the method described in the first aspect above.

[0092] Eighthly, embodiments of the present invention provide yet another network device, including a memory, a communication interface, and a processor coupled to the memory and the communication interface; the memory is used to store instructions, the processor is used to execute the instructions, and the communication interface is used to communicate with other network devices under the control of the processor; wherein, when the processor executes the instructions, it performs the method described in the second aspect above.

[0093] A ninth aspect provides a computer-readable storage medium storing program code for device access. The program code includes instructions for performing the method described in the first aspect.

[0094] In a tenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing program code for device access. The program code includes instructions for performing the method described in the second aspect above.

[0095] In an eleventh aspect, a computer program product including instructions is provided, which, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0096] In a twelfth aspect, a computer program product including instructions is provided, which, when run on a computer, causes the computer to perform the method described in the second aspect above.

[0097] By implementing the embodiments of the present invention, the problems of incompatibility of plug-ins, low security performance, or even performance conflicts in the IoT edge computing platform can be solved due to the complex types of business that the IoT edge computing platform supports. Attached Figure Description

[0098] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0099] Figure 1A This is a schematic diagram of the structure of an IoT edge computing platform provided in an embodiment of the present invention.

[0100] Figure 1B This is a schematic diagram of a container group provided in an embodiment of the present invention.

[0101] Figure 1C This is a schematic diagram of a server cluster deployed with an IoT edge computing platform, provided by an embodiment of the present invention.

[0102] Figure 1D This is a schematic diagram of a data synchronization scenario provided by an embodiment of the present invention.

[0103] Figure 1E This is a schematic diagram of a relationship provided in an embodiment of the present invention.

[0104] Figures 2A-2D This is a flowchart illustrating several device access methods provided in embodiments of the present invention.

[0105] Figure 3A and Figure 3B These are schematic diagrams of two network frameworks provided in embodiments of the present invention.

[0106] Figures 4-7 This is a flowchart illustrating several other device access methods provided in embodiments of the present invention.

[0107] Figure 8A This is a schematic diagram of the structure of a network device provided in an embodiment of the present invention.

[0108] Figure 8BThis is a schematic diagram of another network device provided in an embodiment of the present invention. Detailed Implementation

[0109] The technical solutions in the embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0110] In the process of submitting this application, the applicant discovered that, in order to meet the needs of business scenarios with high performance requirements and massive data transmission, it is necessary to move data processing processes such as data analysis, filtering, and compression involved in the IoT platform to the network edge. To achieve this, the applicant proposes the following two IoT edge computing platforms.

[0111] The first type is an IoT edge computing platform built on the Java Modular System (Open Service Gateway Initiative, OSGI) framework. Research has found that IoT edge computing platforms deploy business plugins from various industries, which can lead to incompatibility, low security, and performance conflicts between these plugins.

[0112] The second approach is to build an IoT edge computing platform based on container technology. Specifically, business plugins (such as third-party application plugins) and other functional services are deployed in containers within the IoT edge computing platform. The built-in isolation mechanism of containers resolves potential incompatibility issues, data leaks (lower security), and performance conflicts between different business plugins. However, in practice, it has been found that deploying each business plugin or functional service separately in a container leads to a significant waste of resources and increases platform construction costs.

[0113] To address the aforementioned issues, this application proposes an IoT edge computing platform that supports lightweight and containerized deployment, as well as a device access method based on this IoT edge computing platform, which will be described in detail below.

[0114] First, this application describes the proposed IoT edge computing platform. This IoT edge computing platform can be designed based on business influencing factors, with different platforms used to process business data from different types of devices, i.e., processing business data from different business types. Furthermore, each IoT edge computing platform is deployed using a containerized approach to achieve secure isolation between different business plugins, avoiding issues such as plugin incompatibility, low security, and performance conflicts. These business influencing factors include, but are not limited to, any one or more combinations of the following: business type, the industry in which the business operates, and the domain in which the business operates.

[0115] The "business type" here refers to the classification of services offered by different IoT devices within the Internet of Things (IoT), such as connected vehicle services, smart home services, etc. The "industry" refers to the industry in which different IoT devices or their services operate, such as the mobile phone industry, the automotive industry, etc. The "domain" refers to the domain in which different IoT devices (i.e., their services) operate within the IoT, such as the terminal domain, etc. Generally, the scope of a domain is more defined than that of an industry; currently, the distinction between "industry" and "domain" is not very clear.

[0116] However, to address issues such as application incompatibility, low security, and even performance conflicts arising from cross-industry or cross-domain applications, this application designs different IoT edge computing platforms for different industries or domains to process business data from IoT devices within those industries / domains. Optionally, IoT edge computing platforms can also be designed based on the business types within different industries / domains, enabling the platform to process business data from IoT devices corresponding to that business type. For example, one IoT edge computing platform can be designed to process business data in the Internet of Vehicles (IoV) field, and another can be designed to process business data in the smart home field, and so on.

[0117] In this application, the IoT edge computing platform refers to an application deployed on one or more physical servers (also known as a server cluster) for processing business data of target type devices, i.e., processing business data of a certain type of business. For example, the business data of the Internet of Vehicles (IoV) mentioned above. Optionally, the IoT edge computing platform described in this application may also be referred to as an IoT edge computing platform type, used to process business data of a certain type (i.e., target type) of business.

[0118] Optionally, to save resources, the IoT edge computing platform can share the same basic components, such as Java classes. To handle business data from different types or manufacturers of devices, the IoT edge computing platform also deploys corresponding differentiated components. These differentiated components can be deployed as plug-ins, for example, by bundling them into a bundle. These differentiated components are different from the basic components and are used to handle business data from different types of devices. For example, applications handling connected vehicle business data and applications handling smart home business data can both be differentiated components, deployed as plug-ins to their respective IoT edge computing platforms.

[0119] To achieve service isolation between different IoT edge computing platforms, this application employs container technology to design the IoT edge computing platform. Specifically, for different IoT edge computing platforms, this application uses container isolation. That is, this application uses containers to deploy the IoT edge computing platform. Specifically, as follows... Figure 1A This diagram illustrates the internal structure of two IoT computing edge platforms. Figure 1A The diagram illustrates IoT edge computing platforms for handling connected vehicle (V2X) and smart home services, respectively. The basic protocol stack shown is a fundamental component; vehicle-to-everything (V2X) plugins, device commands, and protocol plugins are distinct components and will not be detailed here. The IoT platform communication module enables communication between the IoT edge computing platforms and the IoT platform itself. The OSGI framework is the underlying architecture of the Java system and will not be detailed here; the management module will be described in detail below.

[0120] Optionally, depending on business needs (e.g., the total amount of business data to be processed by a certain type of IoT device), the IoT edge computing platform may be designed / include N containers, where N containers are created based on the same image, and N is a positive integer. That is, the N containers belong to the same type and are all used to process business data for a certain type of device (i.e., the target type of device). In other words, the IoT edge computing platform is created based on an image. Different IoT edge computing platforms correspond to different images, with one IoT edge computing platform corresponding to one image; that is, there is a one-to-one correspondence between the IoT edge computing platform and the image.

[0121] The image includes one or more plugins that support open, integrated deployment. This includes various programs deployed as plugins, such as pre-built shared basic components, protocol plugins (i.e., protocol applications) provided by mainstream device manufacturers, functional plugins, and differentiated components (i.e., applications that handle specific business logic). Optionally, the plugins support hot-reload deployment; details regarding hot-reload are not provided in this application. It is understood that the target image is a template for creating containers. This template packages the data and applications required to run the containers. These applications include, but are not limited to, the differentiated components deployed as plugins, the protocol plugins provided by device manufacturers, and the functional plugins mentioned above.

[0122] Since the IoT edge computing platform is used to process business data from a certain type of device, and the IoT edge computing platform includes N containers, it can be understood as being composed of N containers. Accordingly, the IoT edge computing platform described in this application can also be referred to as a container group. Accordingly, to achieve mutual discovery of containers of the same type, a container management module is designed in the containers, specifically a Karaf container management module. This module enables mutual discovery of containers of the same type to automatically form / assemble container groups, as detailed below. Figure 1BAs shown. Optionally, this container management module can also realize data synchronization between N containers. The specific data synchronization mechanism will be described in detail below. The container management module also refers to an application, which can be packaged as a plugin in the target image used to create the container; this application will not elaborate further.

[0123] In an optional embodiment, the IoT edge computing platform (i.e., N containers) can be deployed in a server cluster, which includes, but is not limited to, one or more servers. It should be understood that the server cluster can support the deployment of one or more IoT edge computing platforms to handle business data applied to processing one or more types of devices. Specifically, as follows... Figure 1C This illustrates the deployment of three IoT edge computing platforms on the same server cluster. Specifically, these can be a first edge computing platform for handling vehicle networking services, a second edge computing platform for handling smart home services, and a third edge computing platform for handling voice services. The number of containers included in each edge computing platform is not limited, and they can be the same or different.

[0124] In an optional embodiment, data sharing and backup can be supported between any two containers in the IoT edge computing platform. That is, a data synchronization mechanism is supported between containers within the same IoT edge computing platform. Optionally, to determine which containers store / backup the same data, a data distribution table can be used to record this information, and this data distribution table can be synchronously recorded in each container of the IoT edge computing platform. Figure 1D As shown, the IoT edge computing platform includes three containers. Containers 1 to 3 respectively store data 1, data 2, and data 3, and the illustrations show master data 1, master data 2, and master data 3, respectively. To prevent data loss in a single container from being irretrievable, this application involves a data synchronization mechanism that supports data backup between any two containers within the same IoT edge computing platform. Each container synchronously stores a data distribution table to record which container contains each type of data. Figure 1D The master data 1 is backed up to container 2 (i.e., backup data 1 in the diagram), data 2 is backed up to container 3 (backup data 2 in the diagram), and master data 3 is backed up to container 1 (backup data 3 in the diagram). Accordingly, the data distribution table stores the relationship between which container the master data and backup data are located in. Table 1 below shows a schematic diagram of such a data distribution table.

[0125] Table 1

[0126] Data Identifier Main data storage location Backup data storage location Data 1 Container 1 Container 2 Data 2 Container 2 Container 3 Data 3 Container 3 Container 1 … … …

[0127] Optionally, when data is deleted or added to a container, the data distribution table can be updated synchronously. For example, if data 1 is deleted from container 1 in the above example, then when the IoT edge computing platform needs to use data 1, it can obtain the backup data 1 from container 2.

[0128] Optionally, when a container in the IoT edge computing platform fails, the data in the other containers in the edge computing platform can be re-distributed and stored, which will not be described in detail here.

[0129] The following describes embodiments involving the image, IoT edge computing platform, and different types of devices (specifically, device profiles). Specifically, to address issues such as incompatibility between plugins, low security, and performance conflicts in existing technologies, this application proposes different IoT edge computing platforms to process business data from different types of devices. These different IoT edge computing platforms are built upon different images; one IoT edge computing platform corresponds to one image. For details, please refer to the foregoing embodiments, which will not be repeated here. The following section elaborates on the concept behind constructing the IoT edge computing platform in this application, focusing on the image, IoT edge computing platform, and profiles of different types of devices.

[0130] Specifically, such as Figure 1E A schematic diagram illustrating this relationship is provided. This diagram includes a mirror repository and device information for different types of devices (the diagram shows the device identifier and corresponding device description profile for a target type of device). The mirror repository stores at least one image, and each image is used to build an IoT edge computing platform. Details regarding the images can be found in the preceding embodiments and will not be repeated here. Optionally, to distinguish different images, a corresponding identifier can be assigned to each image, i.e., the image's identifier, which can specifically be the image's name, number, etc.

[0131] To differentiate between business functions, different IoT edge computing platforms need to be built for different types of devices. Each type of device may include multiple devices, each with its own device information (also known as device record information). This device information includes, but is not limited to, device profile, device identifier, manufacturer, and system version. The device profile may include, but is not limited to, device name, device type, and device model, as detailed below. Furthermore, there is no limit to the number of each type of device; that is, each type of device may include multiple devices.

[0132] It should be understood that, to distinguish between devices and their device description information, each device has its own device identifier (device ID shown in the diagram), and each type of device's device description information also has its own profile identifier, i.e., profileID. For example, a certain type of in-vehicle device includes multiple in-vehicle devices 1 and multiple in-vehicle devices 2 manufactured by different manufacturers, and different users can freely purchase either in-vehicle device 1 or in-vehicle device 2. Corresponding to Figure 1E For example, this type of in-vehicle device belongs to the target type of device. The profile of this type of in-vehicle device includes separate profiles for in-vehicle device 1 and in-vehicle device 2. The device information of this type of in-vehicle device may include the device identifiers corresponding to multiple in-vehicle devices 1, multiple in-vehicle devices 2, and so on. Accordingly, to process the business data of this type of in-vehicle device, an IoT edge computing platform can be designed for it. That is, as... Figure 1E Each type of device corresponds to a profile group containing device description information. Furthermore, each type of device can be associated with a designed IoT edge computing platform, which also has a corresponding image; details will not be elaborated here.

[0133] Based on the embodiments of the aforementioned IoT edge computing platform, the following describes relevant embodiments of the device access method involved in this application. Specifically, as shown... Figure 2A This is a flowchart illustrating a device access method provided in an embodiment of the present invention. Figure 2A The method shown includes the following implementation steps:

[0134] Step S201: The server cluster sends a first message to the IoT platform. The first message carries the identifier of the IoT device and is used to request the IoT device to authenticate itself. Accordingly, the IoT platform receives the first message.

[0135] In this application, the first message may be a device online message sent by the IoT device to the server cluster, used to request the IoT platform to authenticate the IoT device. Accordingly, after receiving the first message, the server cluster forwards it to the IoT platform.

[0136] Step S202: The IoT platform returns a second message to the server cluster. The second message indicates that the IoT platform has successfully authenticated the IoT device. The second message also carries the identifier of the IoT edge computing platform associated with the identifier of the IoT device. Accordingly, the server cluster receives the second message.

[0137] Specifically, after receiving the first message, the IoT platform can parse the first message to obtain the identifier of the IoT device. Then, based on the identifier of the IoT device, it authenticates the IoT device and returns a corresponding second message to the server cluster. The second message is used to indicate whether the IoT platform successfully authenticated the IoT device, i.e., whether the authentication was successful or failed. If the authentication fails, the process can end. If the authentication is successful, the second message also carries the identifier of the IoT edge computing platform associated with the identifier of the IoT device.

[0138] The IoT edge computing platform is a containerized application running on the server cluster, used to process business data from devices of the same type as the IoT device, i.e., to process business data from target-type devices. The target-type devices are those of the same type as the IoT device.

[0139] In an optional embodiment, the IoT platform stores the association / mapping relationship between the identifiers of the IoT devices and the identifiers of the IoT edge computing platform. Specifically, as shown below... Figure 2B Before step S201, the method may further include the following implementation steps:

[0140] S101, The IoT device sends a binding message (or registration message) to the IoT platform, the binding message carrying the identity identifier of the IoT device; correspondingly, the IoT platform receives the binding message.

[0141] The identity identifier of the IoT device is a unique identifier key used to represent the IoT device, which may include, but is not limited to, the IoT device's media access control (MAC) and international mobile subscriber identity (IMSI).

[0142] S102. After receiving the binding message, the IoT platform determines the device description information of the IoT device and the identifier of the IoT edge computing platform associated with the device description information based on the identity identifier, and assigns the IoT device identifier to the IoT device. The IoT platform pre-stores the association relationship between the device description information and the identifier of the IoT edge computing platform. Correspondingly, the IoT device can send a binding response message to the IoT platform, the binding response message carrying the identifier of the IoT device.

[0143] Specifically, after receiving the binding message, the IoT platform can query the device description information associated with the identity key from the connection management unit based on the IoT device's identity key. Simultaneously, it also learns the IoT edge computing platform associated with the device description information. Optionally, it also queries the identifier of the target image used to build the IoT edge computing platform. For details regarding the device description information, please refer to the relevant descriptions in the foregoing embodiments; they will not be repeated here.

[0144] Furthermore, the IoT platform can assign a unique identifier to the IoT device, namely the IoT device ID. Optionally, the IoT platform can return a binding / registration response message to the IoT device, the registration response message carrying the IoT device's identifier.

[0145] S103. The IoT platform creates and saves the association between the device description information of the IoT device, the identifier of the IoT device, and the identifier of the IoT edge computing platform.

[0146] In alternative embodiments, such as Figure 2C Before step S201, the method further includes the following implementation steps:

[0147] Step S104: The IoT platform determines the server cluster based on the business needs of the target type of device, so as to create an IoT edge computing platform in the server cluster for processing the business data of the target type of device.

[0148] Specifically, based on business planning and the business needs of the target type of devices, the IoT platform determines that an IoT edge computing platform needs to be created in an edge area data center to process the business data of the target type of devices. The edge area data center is the server cluster described in this application, which includes, but is not limited to, one or more servers.

[0149] Step S105: The IoT platform sends a first creation message to the server cluster. The first creation message carries a target image, indicating that the IoT edge computing platform should be created in the server cluster based on the target image. Correspondingly, the server cluster receives the first creation message. For details regarding the target image and the IoT edge computing platform, please refer to the descriptions in the foregoing embodiments; they will not be repeated here.

[0150] Step S106: After receiving the first creation message, the server cluster creates the IoT edge computing platform based on the target image.

[0151] Specifically, the server cluster creates N containers based on the target image, and these N containers constitute the IoT edge computing platform. Here, N is a positive integer, and its size depends on the business needs of the target type of device. If the business needs of the target type of device are large, i.e., the amount of business data to be processed is large, then the value of N can be relatively large; conversely, the value of N can be designed to be relatively small. Optionally, the size of N is also limited by the hardware resources of the server cluster deploying the containers, which will not be detailed here.

[0152] Optionally, as the business data of the target type of devices increases, the IoT platform can subsequently create new containers in the IoT edge computing platform according to the business needs of the target type of devices. Specifically, a second creation message can be sent to the server cluster to instruct the creation of a new container in the IoT edge computing platform. This will be described in detail below and will not be elaborated here.

[0153] In an optional embodiment, the method after step S106 may further include the following implementation steps:

[0154] Step S107: The server cluster sends a first registration message to the IoT platform through the main container. Correspondingly, the IoT platform receives and records the first registration message. The first registration message carries at least the identifier of the main container. Optionally, it may also carry the identifier of the server cluster and the identifier of the IoT edge computing platform. The main container can be any one of the N containers in the IoT edge computing platform, or a user-defined container or a system-defined container, etc., which is not limited in this application. Specifically, the first registration message can be a registration message to register the server cluster, the IoT edge computing platform in the server cluster, and the containers included in the IoT edge computing platform to the IoT platform.

[0155] In an optional embodiment, the IoT edge computing platform includes N containers created based on the same target image. After step S202, the method may further include the following implementation steps:

[0156] Step S203: The server cluster selects a target container from the N containers according to the load balancing strategy, so as to process the business data of the IoT device in the target container.

[0157] Specifically, multiple IoT edge computing platforms can be deployed on the server cluster to process business data from different types of devices. These multiple IoT edge computing platforms can be distinguished by specific identifiers. After receiving the second message, the server cluster can parse the message to obtain the identifier of the IoT edge computing platform used to process the business data of the IoT device. Accordingly, in step S203, the server cluster can first locate the IoT edge computing platform corresponding to the identifier, such as an edge computing platform used to process vehicle networking services. Then, from the N containers included in the IoT edge computing platform, the container with the lowest load is selected as the target container. This allows the target container to process the business data of the IoT device when it reports business data to the IoT edge computing platform. For details regarding the IoT edge computing platform, please refer to the relevant descriptions in the foregoing embodiments; they will not be repeated here.

[0158] Step S204: The server cluster sends a second registration message to the IoT platform through the target container to record the second registration message in the IoT platform. The second registration message instructs that the business data of the IoT device be processed in the target container under the IoT edge computing platform in the server cluster. The second registration message carries at least the identifier of the target container. Optionally, the second registration message may also carry information such as the identifier of the IoT device, the identifier of the IoT edge computing platform, and the identifier of the server cluster; this application does not limit this information.

[0159] In alternative embodiments, such as Figure 2D The method may also include the following implementation steps:

[0160] Step S205: The server cluster sends a load notification message to the IoT platform, the load notification message carrying the total load of the IoT edge computing platform. Correspondingly, the IoT platform receives the load notification message.

[0161] The total load of the IoT edge computing platform refers to the total amount of business data processed by N containers in the edge computing platform, or the total number of devices responsible for processing business data.

[0162] Step S206: The IoT platform determines a backup cluster for the server cluster based on the total load of the IoT edge computing platform in the server cluster, so that the IoT edge computing platform in the backup cluster can be used to process the business data of the IoT devices when the server cluster is overloaded.

[0163] Specifically, the IoT edge computing platform can be deployed across M service clusters, which are divided according to different regional locations. That is, the M service clusters are located in M ​​different regional locations. Each of the M service clusters includes at least the backup cluster and the server cluster. Each of the M service clusters can communicate with the IoT platform, sending the total load of the IoT edge computing platform within its respective cluster to the IoT platform. Optionally, it can also send the regional location of its respective service cluster.

[0164] Accordingly, the IoT platform can select a suitable backup cluster (also a backup server cluster) based on the total load of each edge computing platform in the M service clusters and their regional locations. Preferably, the backup cluster is closest to the regional location of each of the server clusters, within a preset range. That is, the backup cluster is another server cluster that is close to / adjacent to the server cluster.

[0165] The server cluster service overload refers to the total load of the IoT edge computing platform in the server cluster being greater than or equal to a first load threshold, or the load of the target container in the server cluster being greater than or equal to a second load threshold. In other words, if the target container with the least load is overloaded, then the IoT edge computing platform in the server cluster is also overloaded.

[0166] Step S207: The IoT platform sends a backup notification message to the server cluster, the backup notification message carrying the identifier of the backup cluster.

[0167] In specific step S207, the server cluster can send a load notification message to the IoT platform through the main container. Correspondingly, in step S208, the IoT platform can specifically notify the main container in the IoT edge computing platform of the backup notification message to store the identifier of the backup cluster in the main container, which will be described in detail below.

[0168] In an optional embodiment, the method may further include the following implementation steps:

[0169] Step S208: When the server cluster determines that the load on the target container is greater than or equal to a first threshold, it determines the backup cluster; wherein, the server cluster stores the identifier of the backup cluster.

[0170] Step S209: The server cluster sends a third message to the backup cluster. The third message carries the identifier of the IoT device and the identifier of the IoT edge computing platform to instruct the backup cluster to use the IoT edge computing platform to process the business data of the IoT device.

[0171] In an optional embodiment, after receiving the third message, the backup cluster can send a corresponding registration message to the IoT platform, the registration message carrying the identifier of the backup cluster. Optionally, it may also carry the identifier of the IoT device and the identifier of the IoT edge computing platform, etc.

[0172] By implementing the embodiments of the present invention, IoT edge computing platforms can be designed according to business types, with different IoT edge computing platforms used to process business data from different types of devices. Furthermore, the IoT edge computing platforms are deployed using a containerized approach to address issues such as plugin incompatibility, low security, and performance conflicts in existing technologies. This allows for the allocation of IoT devices to the corresponding IoT edge computing platforms when they are connected, thereby processing the business data of those IoT devices and improving the security and reliability of business processing.

[0173] Next, a schematic diagram of the network framework applicable to this application is presented. The following section details the network framework diagram of the IoT platform involved in this application and the server cluster deployed with the IoT edge computing platform.

[0174] like Figure 3A This is a schematic diagram of the network architecture of an IoT platform provided by an embodiment of the present invention. Figure 3A The IoT platform includes a plugin repository 102, an image repository 104, and a connection management unit 106. Optionally, it may also include a cluster management unit 108. Wherein:

[0175] The plugin repository 102 is used to store at least one plugin, which may specifically be an application packaged into the image in a plugin manner.

[0176] The image repository 104 is used to store at least one image, where each image corresponds to an IoT edge computing platform. Different images correspond to different IoT edge computing platforms, used to process business data from different types of devices. Specifically, one image is used to build a type of container, i.e., an IoT edge computing platform. For a detailed description of the images, containers, and IoT edge computing platforms, please refer to the foregoing embodiments; further details will not be repeated here.

[0177] The connection management unit 106 is used to store the association between device description information and the image (specifically, the image's identifier). The device description information can refer to the device description information of a certain IoT device or a certain type of IoT device, which specifically includes, but is not limited to, device type, device model, communication protocol used by the device (such as Zigbee), device service attributes (such as which services it supports and the application scenarios of the device), etc.

[0178] Optionally, the cluster management unit 108 is responsible for managing various components in the server cluster, such as creation and configuration operations, which will be described in detail below.

[0179] like Figure 3B This is a schematic diagram of a network framework for a server cluster provided in an embodiment of the present invention. In practical applications, the server cluster can refer to a cluster composed of one or more physical servers. In the embodiments of this application, as... Figure 3B The server cluster may include a scheduler 202, at least one IoT edge computing platform 204, and an access service instance 206. Optionally, it may also include a Domain Name System (DNS) server 208. Wherein:

[0180] The scheduler 202 is responsible for scheduling resources, such as server hardware and memory resource allocation, to assist in the construction of container or IoT edge computing platforms, which will be described in detail below.

[0181] The IoT edge computing platform 204 includes N containers, each responsible for processing business data from a specific type of device (i.e., target type devices), such as processing business data in the Internet of Vehicles (IoV). One IoT edge computing platform handles business data for one type of device, while different IoT edge computing platforms handle different types of business data.

[0182] The access service (load balancing, LB) instance 206 is responsible for connecting IoT devices to the server cluster based on their current location, so as to utilize the corresponding IoT edge computing platform to process the IoT devices' business data. Optionally, the access service has packet routing and business load balancing functions, which will be described in detail below.

[0183] The DNS server 208 is used to record and provide domain name addresses so that the IoT device can log in / access the IoT edge computing platform of the server cluster based on the domain name address, and then use the platform to process the business data of the IoT device. This application will not go into detail.

[0184] The various components or functional units involved in the server cluster described in this application will be elaborated in detail below, and will not be described in detail here.

[0185] The following is based on Figure 3A and Figure 3B The network framework diagram shown illustrates in detail the various components of the IoT platform 100 and the various components of the server cluster 200 as described above. Figures 2A-2D The collaborative relationship described in the embodiments.

[0186] First, based on Figure 3A and Figure 3B The network framework diagram shown is used to illustrate the concept of a network architecture. Figure 2C Taking an example embodiment, the following describes the collaborative relationship between the IoT platform and the various components in the server cluster in creating the IoT edge computing platform embodiment. Please refer to [link to example embodiment]. Figure 4 .

[0187] 1-3. The cluster management unit 108 sends a service creation request to the server cluster, instructing the creation of an access service instance 206 in the server cluster. Correspondingly, the service cluster receives the service creation request and creates the access service instance 206 through the scheduler 202. After creating the access service instance 206, it sends the corresponding domain name address to the local DNS server 208 and registers the domain name address in the DNS server.

[0188] Specifically, the cluster management unit 108 can determine the server cluster to be used to create the IoT edge computing platform based on business planning or the business needs of the target type devices. Before creating the IoT edge computing platform, a corresponding access service instance 206 needs to be created through the scheduler 202 so that IoT devices can access the server cluster through this access service instance, and then access the IoT edge computing platform within the cluster. After the access service instance 206 is created, the domain name address supporting the online access of the target type devices can be refreshed to the local DNS server. The target type devices refer to devices of the same type as the IoT devices.

[0189] 4-5. The IoT platform needs to obtain the basic components and other functional components used to process the business data of the target type device from the plug-in repository 102, package them into the corresponding target image based on the system framework (such as OSGI), and store the target image in the image repository 104.

[0190] 6-7. The cluster management unit 108 sends a first creation message to the scheduler 202. The first creation message carries the target image and is used to instruct the creation of the IoT edge computing platform based on the target image. Accordingly, the scheduler 202 receives the first creation message and creates the IoT edge computing platform (specifically N containers) in the server cluster based on the target image.

[0191] It should be understood that steps 4-7 above are primarily used to create the IoT edge computing platform 204 within the server cluster for processing business data from the target type of devices. Specifically, the cluster management unit first retrieves the target image from the image repository 104 and then generates a first creation message. Next, the first creation message is sent to the scheduler 202 of the server cluster, instructing the scheduler 202 to create N containers. Correspondingly, the scheduler receives the first creation message and completes the creation and deployment of the N containers within the server cluster, thus completing the creation and deployment of the IoT edge computing platform.

[0192] The first creation message carries the target image (i.e., image file), which is used to build the N containers.

[0193] Optionally, based on the container management unit in the target image, after the N containers are created, the N containers can automatically discover and form a container group, i.e., the IoT edge computing platform. For details regarding the IoT edge computing platform and the container management unit, please refer to the relevant descriptions in the foregoing embodiments, which will not be repeated here.

[0194] 8. The IoT edge computing platform 204 can select a main container from N containers. Specifically, the main container can be any one of the N containers, or it can be a user-defined container or a system-defined container. For example, in the figure, container 1 is selected as the main container.

[0195] 9-10. Optionally, the main container sends a first registration message (specifically, a registration message) to the cluster management unit 108 of the IoT platform to register the server cluster to the IoT platform. Correspondingly, the cluster management unit 108 may return a first response message, which carries the address of the access service instance for IoT devices to access the access service instance corresponding to that address.

[0196] The first registration message may carry any combination of one or more of the following: the identifier of the main container, the identifier of the IoT edge computing platform, and the identifier of the server cluster. The first response message is used to indicate that the IoT platform has successfully registered the server cluster and records the first registration message in the IoT platform. Specifically, the cluster management unit 108 may return the first response message to the main container and then notify the address of the access service instance 206 through the main container. The address of the access service instance refers to a virtual address, which may be an internet protocol (IP) address, etc., which will not be detailed in this application.

[0197] 11. The main container sends the relevant information of the IoT edge computing platform 204 to the access service instance 206 to update the corresponding routing information in the access service instance.

[0198] The relevant information may include, but is not limited to, the identifier of the IoT edge computing platform, the addresses (specifically virtual addresses, such as IP addresses) of the N containers in the IoT edge computing platform, and the address of the access service instance. The routing information is associated with the relevant information and is used by the access service instance to connect the corresponding IoT device to the server cluster, or to route the service data reported by the IoT device to the relevant container in the IoT edge computing platform for processing.

[0199] 12. Optionally, the cluster management unit 208 can also perform configuration and management operations on the IoT edge computing platform through the main container. For example, the main container can configure parameters for each container in the IoT edge computing platform, and can also manage plugins for related containers in the IoT edge computing platform through the main container, such as deletion, version updates, etc., which will not be detailed in this application.

[0200] Secondly, based on Figure 3A The diagram shows the framework of the IoT platform. Figure 2B Taking an example embodiment, the following details the collaborative relationships between various components in the IoT platform in the embodiment of registering IoT devices in the IoT platform. Please refer to [reference needed]. Figure 5 .

[0201] S11. The first device sends its device description information (specifically, a profile file) to the connection management unit 106 of the IoT platform. Correspondingly, the connection management platform 106 receives the device description information of the first device.

[0202] Specifically, when a manufacturer releases a new IoT device, it needs to upload the device description information to the IoT platform's connection management unit. That is, the first device can be an IoT device belonging to a specific target type.

[0203] It should be understood that each device corresponds to a unique device description, and different types of devices may have different device descriptions. For example, all Huawei Honor 7 phones correspond to a single device description. For details regarding the device description information, please refer to the foregoing embodiments; further details will not be repeated here.

[0204] S12. After receiving the device description information of the first device, the connection management unit 106 can notify the mirror repository 104. Accordingly, the mirror repository 104 can determine the identifier of the IoT edge computing platform corresponding to the device description information based on the device description information of the first device, and send the association relationship between the device description information and the identifier of the IoT edge computing platform to the connection management platform.

[0205] Specifically, when the connection management unit 106 receives new device description information, it can notify the image repository. Accordingly, the image repository categorizes the device according to the device description information into the corresponding IoT edge computing platform, that is, into the image (or template) corresponding to the IoT edge computing platform to be created. Further, the connection management unit 106 is notified of the association / mapping relationship between the device description information and the identifier of the IoT edge computing platform.

[0206] S13. The second device sends a binding message (specifically, a registration message) to the connection management unit 106. The binding message carries the identity identifier of the IoT device and is used to request binding or registering the IoT device to the IoT platform. Accordingly, the connection management unit 106 receives the binding message. For details regarding the identity identifier, please refer to the relevant descriptions in the foregoing embodiments; they will not be repeated here.

[0207] In this application, the second device may be an IoT device, or it may refer to a device with a designated application (APP), such as a mobile phone, to register the IoT device to the IoT platform through the application. The IoT device to be registered here is of the same type as the first device. Optionally, the first device and the second device may be the same device or different devices; this application does not impose any limitations.

[0208] S14. The connection management unit 106 returns a response message to the second device, the response message carrying the identifier of the IoT device. Accordingly, the second device receives the response message and obtains the identifier of the IoT device.

[0209] Specifically, after receiving the binding message, the connection management unit can determine the device description information of the IoT device based on the IoT device's identity identifier, assign an identifier to the IoT device, and then send the IoT device's identifier information to the second device through a response message. Optionally, the response message may also include other information, such as the security key negotiated between the IoT device and the IoT platform, which will not be detailed in this application.

[0210] S15. Optionally, the second device may send a notification message to the connection management unit 106, the notification message being used to notify of successful reception of the IoT device's identifier. Accordingly, the connection management unit receives the notification message.

[0211] Optionally, the notification message may also carry settings information about the IoT device, such as description information and device attributes set by the application, which will not be described in detail in this application.

[0212] S16. After receiving the notification message, the connection management unit 106 can bind and associate the device description information, the identifier of the IoT device, and the identifier of the IoT edge computing platform. Furthermore, it saves the association between them.

[0213] Next, based on the foregoing embodiments, such as Figure 3A and Figure 3B The network framework diagram shown below will be used as an example. Figure 2A Taking the embodiment as an example, the cooperative relationship between the various components in the IoT platform 100 and the various components in the server cluster 200 in this embodiment is described in detail. Please refer to [the relevant documentation]. Figure 6 .

[0214] S21. The IoT device accesses the access service instance 208 of the server cluster via a pre-planned DNS. Specifically, the IoT device accesses the access service instance of the server cluster based on its domain name address and current location.

[0215] S22, the access service instance 208 sends a first message to the connection management unit 106 of the IoT platform, the first message carrying the identifier of the IoT device. Correspondingly, the connection management unit 106 receives the first message.

[0216] Specifically, the first message can be an IoT device's online message. The IoT device connects to the nearest access service instance 208 based on its current location. Then, the access service instance forwards the first message to the connection management unit for authentication of the IoT device within the IoT platform.

[0217] S23. The connection management unit 106 returns a second message to the access service instance 208, the second message being used to indicate whether the IoT device authentication is successful or fails.

[0218] When the second message indicates that the IoT device authentication has failed, it can be forwarded to the IoT device to notify it of the authentication failure and terminate the process. When the second message indicates that the IoT device authentication has succeeded, it carries the identifier of the IoT edge computing platform associated with the IoT device's identifier. Optionally, the second message may also carry other information, such as a certificate indicating successful authentication, which is not limited or detailed in this application. Optionally, the access service instance 208 may record the second message.

[0219] S24-S25, Further, the access service instance 208 can return an authentication result to the IoT device, for example, by forwarding the second message to the IoT device. Simultaneously, the access service instance can locate the IoT edge computing platform from the server cluster based on the identifier of the IoT edge computing platform. Further, the access service instance 208 can also send a device access message to the IoT edge computing platform 204 to notify the IoT device to access the IoT edge computing platform. Correspondingly, the IoT edge computing platform receives the device access message and selects a target container from N containers in the IoT edge computing platform to process the business data of the IoT device using the target container.

[0220] Specifically, the IoT edge computing platform can select the container with the lowest load from N containers according to a load balancing strategy, and use the target container to process the service data reported by the IoT device. For example, container 2 in the figure is selected as the target container. Optionally, the device information of the IoT device can also be recorded in the target container. The device information includes, but is not limited to, the identifier, device type, and device model of the IoT device, which will not be described in detail in this application.

[0221] S26. Optionally, the IoT edge computing platform 204 sends a second registration message to the connection management unit 106 through the target container to record the second registration message in the connection management unit 106. The second registration message carries one or more of the following information: the identifier of the IoT device, the identifier of the target container, the identifier of the IoT edge computing platform, and the identifier of the server cluster.

[0222] Optionally, when the second registration message carries the identifier of the IoT device, the identifier of the target container, the identifier of the IoT edge computing platform, and the identifier of the server cluster, the second registration message can be used to indicate the communication link between the IoT device and the IoT platform.

[0223] S27. Optionally, the IoT device may subsequently report data, such as its service data, through the communication link. Accordingly, when the target container receives the service data from the IoT device, it processes the service data.

[0224] Next, based on the foregoing embodiments, such as Figure 3A and Figure 3B The network framework diagram shown below will be used as an example. Figure 2D Taking the embodiment as an example, the cooperative relationship between the various components in the IoT platform 100 and the various components in the server cluster 200 in this embodiment is described in detail. Please refer to [the relevant documentation]. Figure 7 .

[0225] S31-S32, the IoT edge computing platform 204 in the server cluster can calculate the total load of the IoT edge computing platform. Further, the IoT edge computing platform can send a load notification message to the cluster management unit 108, the load notification message carrying the total load of the IoT edge computing platform, to determine the backup cluster for the server cluster. Correspondingly, the cluster management unit 108 receives the load notification message.

[0226] Specifically, the IoT edge computing platform 204 can periodically or in real-time calculate the total load of the IoT edge computing platform. This total load can be the total amount of business data carried by each of the N containers in the IoT edge computing platform, or the total number of IoT devices corresponding to the business data to be processed by each container. For example, each container within the IoT edge computing platform can periodically send its own load to the main container, and the main container can then aggregate and calculate the total load of the IoT edge computing platform. Then, the main container sends a load notification message to the cluster management module of the IoT platform to notify the total load of the IoT edge computing platform in this service cluster.

[0227] Optionally, other server clusters can also use the same method to periodically or in real-time report the total load of the IoT edge computing platform in their respective clusters to the cluster management module.

[0228] S33-S34, the cluster management unit 108 determines a backup cluster 300 for the server cluster based on the total load. Further, it sends a backup notification message to the IoT edge computing platform 204, the backup notification message carrying the identifier of the backup cluster.

[0229] Specifically, the cluster management unit 108 can select a backup cluster based on the regional location of the server cluster and the total load of the received IoT edge computing platform. This backup cluster is used to process the business data of the IoT devices when the IoT edge computing platform under the server cluster is overloaded. Preferably, the location interval between the backup cluster and the server cluster is within a preset range, or the distance interval is less than a preset distance threshold, etc., which is not limited in this application. Optionally, the cluster management unit can also update the pre-stored backup cluster. For details, please refer to the relevant descriptions in the foregoing embodiments, which will not be repeated here.

[0230] Accordingly, after the backup cluster is determined, a backup notification message can be sent to the main container to record the backup cluster in the main container.

[0231] S35-37. Optionally, after successful authentication, the IoT device can record its device information in the target container of the IoT edge computing platform 204 to process its business data in the target container. If the load of the target container is determined to be greater than or equal to a first threshold, a backup cluster can be obtained from the main container to process the IoT device's business data in the backup cluster.

[0232] For details, please refer to the above. Figure 2A or Figure 6 In this embodiment, after the IoT platform successfully authenticates the IoT device, the IoT edge computing platform under the server cluster can select a container with the lowest load as the target container to process the business data of the IoT device. If the load of the target container is greater than or equal to a first threshold, it indicates that the business load in the server cluster is too high, and there are currently no resources to process the business data of the IoT device. Accordingly, the IoT edge computing platform can obtain the identifier of the previously recorded backup cluster from the main container. Both the server cluster and the backup cluster deploy the IoT edge computing platform to process business data from devices of the same type as the IoT device. It should be understood that the backup cluster and the server cluster have the same network framework, as detailed in the foregoing implementation, and will not be elaborated here.

[0233] 38. Optionally, if the IoT edge computing platform 204 determines that the load of the target container is greater than or equal to a first threshold, it can send an overload notification message to the cluster management unit 108 through the main container. The overload notification message is used to notify the IoT edge computing platform 204 of service overload, and optionally may also prompt whether a new container needs to be created in the IoT edge computing platform 204 to process the service data of the IoT device.

[0234] Accordingly, after receiving the overload notification message, the cluster management unit 108 can prompt the administrator whether to add new containers in the IoT edge computing platform 204. If a container creation confirmation instruction is received from the user, a second creation message is sent to the IoT edge computing platform 204 through the main container to instruct the addition of new containers in the IoT edge computing platform 204. Optionally, the second creation message may carry information such as the number of new containers and the identifier of the IoT edge computing platform. Further, the IoT edge computing platform 204 receives the second creation message and adds new containers for subsequent processing of business data from devices of the same type as the IoT device.

[0235] S39. The main container in the IoT edge computing platform 204 sends a third message to the access service instance 306 in the backup cluster 300 through the access server instance 206. The third message is used to notify the backup cluster to process the business data of the IoT device using the IoT edge computing platform. Accordingly, the access service instance 306 receives the third message.

[0236] The third message may carry the identifier of the IoT edge computing platform and the identifier of the IoT device. Optionally, the third message may also carry other information, such as a certificate indicating successful authentication of the IoT device.

[0237] S40. Optionally, the access service instance 306 may send device access information to the IoT edge computing platform 304 in the backup cluster 300 to notify the IoT device to access the IoT edge computing platform 304. Accordingly, the IoT edge computing platform receives the device access message and selects a target container from N containers in the IoT edge computing platform to process the business data of the IoT device using the target container.

[0238] Specifically, after receiving the third message, the access service instance 306 parses the message to obtain the identifier of the IoT edge computing platform. Then, it uses this identifier to locate the corresponding IoT edge computing platform from the backup cluster. Further, it sends a device access message to the IoT edge computing platform. For a more detailed explanation of the device access message and the target container, please refer to the foregoing. Figure 6 The embodiments described herein will not be repeated here.

[0239] S41. Optionally, the target container of the IoT edge computing platform 304 sends a corresponding registration message, such as third registration information, to the connection management unit 106 to record the third registration message in the connection management unit 106. The third registration message carries information such as the identifier of the IoT device, the identifier of the target container, the identifier of the IoT edge computing platform, and the identifier of the backup cluster, to indicate the communication link between the IoT device and the IoT platform. Subsequently, the IoT device can report business data to the target container in the IoT edge computing platform 304 according to this communication link for processing.

[0240] For details regarding steps S30-S41 of this application, please refer to the foregoing. Figure 6 The relevant descriptions in steps S24-27 of the embodiments will not be repeated here.

[0241] By implementing the embodiments of the present invention, different IoT edge computing platforms can be provided to process business data of different types of devices. Moreover, the IoT edge computing platform is deployed in a containerized manner, which solves the problems of plug-in incompatibility, low security performance and even performance conflicts existing in the prior art, thereby improving the security and reliability of business processing.

[0242] The above primarily describes the solutions provided by the embodiments of the present invention from the perspective of the interaction between the IoT platform and the server cluster (or IoT edge computing platform). In practical applications, the IoT platform and the IoT edge computing platform can be deployed in network devices (such as servers), and the server cluster can specifically include one or more servers (i.e., a server cluster). It is understood that, in order to achieve the above functions, the network device includes the corresponding hardware structure and / or software modules for executing each function. Based on the units and algorithm steps of the various examples described in the embodiments disclosed in this invention, the embodiments of the present invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of the embodiments of the present invention.

[0243] In this embodiment of the invention, network devices can be divided into functional units according to the above method examples. For example, each function can be divided into its own functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0244] When using integrated units, Figure 8A A possible structural diagram of the network device involved in the above embodiments is shown. The network device 700 includes a processing unit 702 and a communication unit 703. The processing unit 702 is used to control and manage the operation of the network device 700.

[0245] In one possible embodiment, the processing unit 702 is used to support the network device 700 in performing operations. Figure 2A In steps S203 and S208, Figure 2C Step S106, and / or other steps for performing the techniques described herein. Communication unit 703 is used to support communication between network device 700 and other devices; for example, communication unit 703 is used to support network device 700 in performing... Figure 2A Steps S201, S204, S205, and S209, Figure 2C Step S107, and / or other steps for performing the techniques described herein.

[0246] In yet another possible embodiment, the processing unit 702 is used to support the network device 700 in performing [the task]. Figure 2A In step S206, Figure 2B In steps S102 and S103, Figure 2C Step S104, and / or other steps for performing the techniques described herein. Communication unit 703 is used to support communication between network device 700 and other devices; for example, communication unit 703 is used to support network device 700 in performing... Figure 2A Steps S202, S207, and S209, Figure 2B In step S101, Figure 2C Steps S105 and S108, and / or other steps for performing the techniques described herein.

[0247] The network device 700 may also include a storage unit 701 for storing the program code and data of the network device 700.

[0248] The processing unit 702 can be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this invention. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication unit 703 can be a communication interface, transceiver, transceiver circuit, etc., where "communication interface" is a general term and can include one or more interfaces, such as the interface between a network device and other devices. The storage unit 701 can be a memory.

[0249] When the processing unit 702 is a processor, the communication unit 703 is a communication interface, and the storage unit 701 is a memory, the network device involved in the embodiments of the present invention can be... Figure 8B The network device shown.

[0250] See Figure 8BAs shown, the network device 710 includes a processor 712, a communication interface 713, and a memory 77. Optionally, the network device 710 may also include a bus 714. The communication interface 713, processor 712, and memory 77 can be interconnected via the bus 714; the bus 714 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus 714 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 8B The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0251] The above Figure 8A or Figure 8B The specific implementation of the network device shown can also be referred to the corresponding description of the foregoing method embodiments, which will not be repeated here.

[0252] The steps of the methods or algorithms described in conjunction with the embodiments of this invention can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device. Alternatively, the processor and storage medium can exist as discrete components in the network device.

[0253] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

Claims

1. A device access method, characterized in that, The method includes: The IoT platform obtains the identifier of the IoT device; The IoT platform determines the target IoT edge computing platform based on the identifier of the IoT device; The IoT platform sends a first message to the server cluster, the first message carrying the identifier of the target IoT edge computing platform; wherein, The server cluster is deployed with multiple IoT edge computing platforms, each of which is an application for processing business data of a type of IoT device. The target IoT edge computing platform includes N containers, wherein the N containers are created based on the same target image, the target image includes at least one plugin that supports hot-reload deployment, used to process business data of devices of the same type as the IoT device, and the N containers are all used to process business data of devices of the same type as the IoT device, where N is a positive integer greater than 1.

2. The method according to claim 1, characterized in that, The IoT platform obtains the identifier of the IoT device, including: The IoT platform receives a second message sent by the server cluster, the second message carrying the identifier of the IoT device.

3. The method according to claim 2, characterized in that, The second message is used to request the IoT platform to authenticate the IoT device; the first message is used to indicate that the IoT platform has successfully authenticated the IoT device.

4. The method according to claim 2 or 3, characterized in that, Before the IoT platform receives the second message sent by the server cluster, the method further includes: The IoT platform receives a binding message sent by the IoT device, the binding message carrying the identity identifier of the IoT device; The IoT platform determines the device description information of the IoT device based on the identity identifier, and assigns the IoT device identifier to the IoT device. The IoT platform creates and stores the association between the identifier of the IoT device and the identifier of the IoT edge computing platform.

5. The method according to claim 4, characterized in that, The IoT platform determines the target IoT edge computing platform based on the identifier of the IoT device, including: The IoT platform determines the target IoT edge computing platform based on the identifier of the IoT device and the association relationship.

6. The method according to claim 1, characterized in that, The method further includes: The IoT platform sends a creation message to the server cluster, the creation message being used to instruct the creation of the target IoT edge computing platform in the server cluster, the creation message carrying the target image.

7. The method according to claim 1, characterized in that, The method further includes: The IoT platform receives a load notification message sent by the server cluster, the load notification message carrying the total load of the target IoT edge computing platform; The IoT platform determines a backup cluster for the server cluster based on the total load of the target IoT edge computing platform. The backup cluster is equipped with the target IoT edge computing platform so that, in the event of overload of the server cluster, the target IoT edge computing platform in the backup cluster can be used to process the business data of the IoT devices.

8. The method according to claim 7, characterized in that, The method further includes: The IoT platform sends a backup notification message to the server cluster, and the backup notification message carries the identifier of the backup cluster.

9. A device access method, characterized in that, The method includes: The server cluster receives a first message from the IoT platform, the first message carrying the identifier of the target IoT edge computing platform associated with the identifier of the IoT device; wherein, The server cluster is deployed with multiple IoT edge computing platforms. Each of the multiple IoT edge computing platforms is an application used to process business data of a type of IoT device. The target IoT edge computing platform includes N containers, which are created based on the same target image. The target image includes at least one plugin that supports hot-reload deployment and is used to process business data of devices of the same type as the IoT device. All N containers are used to process business data of devices of the same type as the IoT device, and N is a positive integer greater than 1.

10. The method according to claim 9, characterized in that, The multiple IoT edge computing platforms are created based on business influencing factors. Different IoT edge computing platforms are used to process business data from different types of devices. The business influencing factors include at least one of the following: business type, industry in which the business is located, and field in which the business is located.

11. The method according to claim 9 or 10, characterized in that, Before the server cluster receives the first message sent by the IoT platform, the method further includes: The server cluster sends a second message to the IoT platform, the second message carrying the identifier of the IoT device.

12. The method according to claim 11, characterized in that, The second message is used to request the IoT platform to authenticate the IoT device; the first message is used to indicate that the IoT platform has successfully authenticated the IoT device.

13. The method according to claim 9, characterized in that, The target IoT edge computing platform includes differentiated components deployed as plug-ins, and the target IoT edge computing platform shares the same basic components; wherein, the differentiated components are different from the basic components and are applications that process device business data of the same type as the IoT devices.

14. The method according to claim 9, characterized in that, Any two containers in the target IoT edge computing platform support data sharing and data backup.

15. The method according to claim 9, characterized in that, The method further includes: The server cluster uses a load balancing strategy to select a target container from the N containers for processing the business data of the IoT device in the target container.

16. The method according to claim 15, characterized in that, The method further includes: If the load of the target container is greater than or equal to a first threshold, the server cluster determines a backup cluster; wherein, the server cluster stores the identifier of the backup cluster, and the target IoT edge computing platform is deployed in the backup cluster; The server cluster sends a third message to the backup cluster. The third message carries the identifier of the target IoT edge computing platform and the identifier of the IoT device, instructing the backup cluster to process the business data of the IoT device using the target IoT edge computing platform.

17. A device access system, comprising a server cluster and an IoT platform, characterized in that, The server cluster is used to receive a first message sent by the IoT platform. The first message carries the identifier of a target IoT edge computing platform associated with the identifier of the IoT device. Multiple IoT edge computing platforms are deployed on the server cluster. Each of the multiple IoT edge computing platforms is an application used to process business data of a type of IoT device. The target IoT edge computing platform includes N containers, wherein the N containers are created based on the same target image. The target image includes at least one plugin that supports hot-reload deployment, used to process business data of devices of the same type as the IoT device. All N containers are used to process business data of devices of the same type as the IoT device, and N is a positive integer greater than 1. The IoT platform is used to obtain the identifier of the IoT device, determine the target IoT edge computing platform based on the identifier of the IoT device, and send the first message to the server cluster.

18. The system according to claim 17, characterized in that, The server cluster is also used to send a second message to the IoT platform, the second message carrying the identifier of the IoT device; The IoT platform is also used to receive the second message and obtain the identifier of the IoT device based on the second message.

19. The system according to claim 17 or 18, characterized in that... The IoT platform is also used to receive a binding message sent by the IoT device, the binding message carrying the identity identifier of the IoT device, determine the device description information of the IoT device based on the identity identifier, assign the IoT device identifier to the IoT device, and create and save the association between the IoT device identifier and the identifier of the IoT edge computing platform.

20. The system according to claim 17, characterized in that, The IoT platform is also used to send a creation message to the server cluster, the creation message being used to instruct the creation of the target IoT edge computing platform in the server cluster, the creation message carrying the target image; The server cluster is also used to create the target IoT edge computing platform based on the target image.

21. An IoT platform, characterized in that, The IoT platform includes multiple functional modules that interact with each other to implement the method of any one of claims 1-8.

22. A server cluster, characterized in that, The server cluster includes multiple functional modules that interact with each other to implement the method of any one of claims 9-16.

23. A network device, characterized in that, The device includes a memory, a communication interface, and a processor coupled to the memory and the communication interface; the memory is used to store instructions, the processor is used to execute the instructions, and the communication interface is used to communicate with other network devices under the control of the processor; wherein, when the processor executes the instructions, it performs the method as described in any one of claims 1-16.

24. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 16.

Images