Unified management platform compatible with multiple protocols

Abstract

A unified management platform compatible with multiple protocols comprises a communication interface assembly and a control assembly, and the communication interface assembly can communicate with service assemblies of multiple protocols; the control assembly is used for communicating with the service assembly of multiple protocols through the communication interface assembly, managing the Internet of Things equipment supporting the GSMA SGP.01 / 02 protocol when communicating with the service assembly of the GSMA SGP.01 / 02 protocol, and managing the Internet of Things equipment cooperatively supporting the GSMA SGP.21 / 22 protocol when communicating with the service assembly of the GSMA SGP.21 / 22 protocol. And when communicating with the service component of the GSMA SGP.21 / 22 protocol, managing the Internet of Things equipment which cooperatively supports the GSMA SGP.31 / 32 protocol. According to the invention, the eSIM management process can be simplified, three eSIM standards including an MGSMA SGP.01 / 02 protocol, a GSMA SGP.21 / 22 protocol and a GSMA SGP.31 / 32 protocol can be integrated in one platform, and unified management of existing equipment, stock equipment and future equipment is realized.

Description

Technical Field

[0001] The present invention relates to the field of Internet of Things communications, and in particular to a unified management platform compatible with multiple protocols. Background Art

[0002] With the rapid development and popularization of the Internet of Things (IoT), communication between devices has become increasingly important. Machine-to-machine (M2M) communication, as an important part of the IoT, enables devices to automatically transmit data and perform operations without human intervention. However, with the increase in the number of connected devices and the diversification of usage scenarios, traditional physical SIM cards are gradually unable to meet the flexible network access needs.

[0003] To solve these problems, embedded SIM (eSIM) technology came into being. eSIM is a programmable SIM card built into the device that allows remote downloading and switching of operator profiles. Through remote configuration management, eSIM greatly improves the flexibility and convenience of network access for devices around the world.

[0004] The GSMA SGP.01 / 02 protocol is about the application standard of eUICC (embedded universal integrated circuit card) in M2M devices. The GSMA SGP.01 / 02 protocol can realize the remote configuration and management of eUICC in M2M devices, allowing devices to switch between different operator networks, improving flexibility and connectivity, and introducing related communication components for secure management and distribution of SIM card profiles.

[0005] The GSMA SGP.21 / SGP.22 protocol is an important technical specification for eUICC on consumer devices. It is designed for use cases involving personal interaction between consumers and devices. The GSMA SGP.21 / SGP.22 protocol introduces the Local Provisioning Assistant (LPA) in the device or within the eUICC. The process of changing the operator profile on the consumer's eSIM involves activating the LPA to notify the consumer's eSIM; unlike the M2M eSIM setup, no technical integration is required between the consumer eSIM and the operator. Profile changes are usually initiated on the device itself, and users can manually activate the changes through the user interface.

[0006] GSMA SGP.31 / 32 is an important technical specification for eUICC on IoT devices (i.e., eSIM IoT technical specification). This specification aims to solve the problem of eUICC remote configuration in IoT devices under limited connectivity and limited user interface. It covers the remote configuration and management of eUICC in IoT devices, especially for devices with limited network or user interface. By introducing components such as the IoT Remote Management Platform (eSIM IoT Remote Manager, EIM for short) and the IoT Profile Assistant (IPA), large-scale deployment and management of IoT devices are achieved, and the flexibility and scalability of devices are improved.

[0007] The above-mentioned protocols focus on different application scenarios and stipulate corresponding technical specifications, which significantly increases the complexity of the system when supporting multiple types of IoT devices and managing different eSIM protocols; and makes the unified management between existing IoT devices, stock IoT devices and future new devices face challenges. Summary of the invention

[0008] In view of the above problems, the present invention provides a unified management platform compatible with multiple protocols, which is described in detail below.

[0009] According to the first aspect, an embodiment provides a unified management platform compatible with multiple protocols, including: a communication interface component and a control component;

[0010] The communication interface component can communicate with service components of multiple protocols, and the multiple protocols include any two or three of the GSMASGP.01 / 02 protocol, the GSMA SGP.21 / 22 protocol and the GSMA SGP.31 / 32 protocol; the service components of the GSMASGP.01 / 02 protocol include the first Internet of Things management platform NgIOT, the secure router SM-SR of the subscription manager and the data preparer SM-DP of the subscription management, the service components of the GSMA SGP.21 / 22 protocol include the second Internet of Things management platform NgIOT, the data preparation server SM-DP+ of the subscription management and the message forwarding server Link, and the service components of the GSMA SGP.31 / 32 protocol include the Internet of Things remote management platform EIM and the data preparation server SM-DP+ of the subscription management;

[0011] The control component is used to manage any two or three of the first type of IoT devices supporting the GSMASGP.01 / 02 protocol, the second type of IoT devices supporting the GSMASGP.21 / 22 protocol, and the second type of IoT devices supporting the GSMA SGP.31 / 32 protocol;

[0012] The control component manages the first type of IoT devices including:

[0013] The control component sends the operation instruction to the first Internet of Things management platform NgIOT, so that the first Internet of Things management platform NgIOT communicates with the security router SM-SR of the subscription manager, so that the security router SM-SR of the subscription manager communicates with the first type of Internet of Things device, so that the first type of Internet of Things device performs the corresponding operation; and / or, the control component sends the operation instruction to the security router SM-SR of the subscription manager, so that the security router SM-SR of the subscription manager communicates with the first type of Internet of Things device, so that the first type of Internet of Things device performs the corresponding operation; and / or, the control component sends the operation instruction to the Internet of Things remote management platform EIM, so that the Internet of Things remote management platform EIM communicates with the first type of Internet of Things device, so that the first type of Internet of Things device performs the corresponding operation;

[0014] The control component manages the second type of IoT devices including:

[0015] The control component sends the operation instruction to the second Internet of Things management platform NgIOT, so that the second Internet of Things management platform NgIOT communicates with the message forwarding server Link, so that the message forwarding server Link communicates with the second type of Internet of Things devices, so that the second type of Internet of Things devices perform corresponding operations; and / or, the control component sends the operation instruction to the message forwarding server Link, so that the message forwarding server Link communicates with the second type of Internet of Things devices, so that the second type of Internet of Things devices perform corresponding operations; and / or, the control component sends the operation instruction to the Internet of Things remote management platform EIM, so that the Internet of Things remote management platform EIM communicates with the second type of Internet of Things devices, so that the second type of Internet of Things devices perform corresponding operations;

[0016] The control component manages the third type of IoT devices including:

[0017] The control component sends the operation instruction to the Internet of Things remote management platform EIM, so that the Internet of Things remote management platform EIM communicates with the third type of Internet of Things device, so that the third type of Internet of Things device performs the corresponding operation.

[0018] In some embodiments, the management of the first category of IoT devices by the control component further includes: if the operation instruction is used to trigger the downloading of a configuration file, the security router SM-SR of the subscription manager also communicates with the data preparer SM-DP of the subscription management, so that the data preparer SM-DP of the subscription management sends the configuration file to the first category of IoT devices, so that the eUICC of the first category of IoT devices is configured based on the configuration file; wherein the data preparer SM-DP of the subscription management can communicate with the operator server to obtain the configuration file.

[0019] In some embodiments, the control component's management of the first type of IoT devices further includes:

[0020] The control component receives data or information uploaded by the first type of Internet of Things device through the subscription manager's security router SM-SR and the first Internet of Things management platform NgIOT in sequence; and / or, the control component receives data or information uploaded by the first type of Internet of Things device directly through the subscription manager's security router SM-SR; and / or, the control component receives data or information uploaded by the first type of Internet of Things device through the Internet of Things remote management platform EIM.

[0021] In some embodiments, the control component's management of the second category of IoT devices also includes: if the operation instruction is used to trigger the download of the configuration file, the second IoT management platform NgIOT also communicates with the data preparation server SM-DP+ for subscription management, so that the data preparation server SM-DP+ for subscription management sends the configuration file to the second category of IoT devices, so that the local configuration file assistant LPA of the second category of IoT devices is configured based on the configuration file; or, if the operation instruction is used to trigger the download of the configuration file, the IoT remote management platform EIM also communicates with the data preparation server SM-DP+ for subscription management, so that the data preparer SM-DP communicates, so that the data preparation server SM-DP+ for subscription management sends the configuration file to the second category of IoT devices, so that the local configuration file assistant LPA of the second category of IoT devices is configured based on the configuration file.

[0022] In some embodiments, the control component's management of the second-category IoT device also includes: the control component receiving data or information uploaded by the second-category IoT device via the message forwarding server Link and the second IoT management platform NgIOT in sequence; and / or, the control component receiving data or information directly uploaded by the second-category IoT device via the message forwarding server Link; and / or, the control component receiving data or information uploaded by the second-category IoT device via the IoT remote management platform EIM.

[0023] In some embodiments, the control component's management of the third category of IoT devices also includes: if the operation instruction is used to trigger the download of a configuration file, the IoT remote management platform EIM also communicates with the data preparation server SM-DP+ for subscription management, so that the data preparer SM-DP communicates, so that the data preparation server SM-DP+ for subscription management directly sends the configuration file or sends it through the IoT remote management platform EIM to the third category of IoT devices, so that the IoT configuration file assistant IPA of the third category of IoT devices is configured based on the configuration file.

[0024] In some embodiments, the management of the second type of IoT devices by the control component also includes: the control component receiving data or information uploaded by the third type of IoT devices via the IoT remote management platform EIM.

[0025] In some embodiments, the data uploaded by the IoT devices include the environmental data collected by them, and the control component controls the storage of the environmental data uploaded by various IoT devices in a distributed database for retrieval and analysis.

[0026] In some embodiments, the information uploaded by the IoT device includes its operating status information. The control component monitors the operating status information of each IoT device in real time, and displays it through a user interface and / or issues an alarm message when an abnormality is detected.

[0027] According to a second aspect, an embodiment provides a unified management platform compatible with multiple protocols, including:

[0028] A communication interface component, wherein the communication interface component can communicate with a service component of multiple protocols, wherein the multiple protocols include any two or three of the GSMA SGP.01 / 02 protocol, the GSMA SGP.21 / 22 protocol, and the GSMA SGP.31 / 32 protocol;

[0029] A control component is used to communicate with service components of multiple protocols through the communication interface component, manage SIM card profiles and eUICCs for IoT devices supporting the GSMA SGP.01 / 02 protocol when communicating with the service component of the GSMA SGP.01 / 02 protocol, manage eSIM card profiles for the local profile assistant LPA in the IoT device supporting the GSMA SGP.21 / 22 protocol when communicating with the service component of the GSMA SGP.21 / 22 protocol, and manage eSIM card profiles for the IoT profile assistant IPA in the IoT device supporting the GSMA SGP.31 / 32 protocol when communicating with the service component of the GSMA SGP.21 / 22 protocol.

[0030] The unified management platform compatible with multiple protocols according to the above-mentioned embodiment can simplify the eSIM management process, reduce the technical gap between different device types and eSIM standards, and integrate three eSIM standards, namely, MGSMA SGP.01 / 02 protocol, GSMA SGP.21 / 22 protocol and GSMA SGP.31 / 32 protocol, into one platform to achieve unified management of existing devices, stock devices and future devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A schematic diagram of the structure of a unified management platform compatible with multiple protocols according to an embodiment of the present invention;

[0032] Figure 2 A schematic diagram of management of a first type of IoT device by a unified management platform compatible with multiple protocols in an embodiment;

[0033] Figure 3 A schematic diagram of management of a first type of IoT device by a unified management platform compatible with multiple protocols in an embodiment;

[0034] Figure 4 A schematic diagram of management of a first type of IoT device by a unified management platform compatible with multiple protocols in an embodiment;

[0035] Figure 5 A schematic diagram of managing the second type of IoT devices by a unified management platform compatible with multiple protocols in an embodiment;

[0036] Figure 6 A schematic diagram of managing the second type of IoT devices by a unified management platform compatible with multiple protocols in an embodiment;

[0037] Figure 7 A schematic diagram of managing the second type of IoT devices by a unified management platform compatible with multiple protocols in an embodiment;

[0038] Figure 8 A schematic diagram of managing a third type of IoT device by a unified management platform compatible with multiple protocols in an embodiment;

[0039] Fig. 9 The present invention is a schematic diagram of managing a first-category IoT device, a second-category IoT device, and a third-category IoT device by a unified management platform compatible with multiple protocols in an embodiment. DETAILED DESCRIPTION

[0040] The present invention is further described in detail below by specific embodiments in conjunction with the accompanying drawings. Wherein similar elements in different embodiments adopt associated similar element numbers. In the following embodiments, many detailed descriptions are for making the present application better understood. However, those skilled in the art can easily recognize that some features can be omitted in different situations, or can be replaced by other elements, materials, methods. In some cases, some operations related to the present application are not shown or described in the specification, this is to avoid the core part of the present application being overwhelmed by too much description, and for those skilled in the art, it is not necessary to describe these related operations in detail, and they can fully understand the related operations according to the description in the specification and the general technical knowledge in the art.

[0041] In addition, the features, operations or characteristics described in the specification can be combined in any appropriate manner to form various implementations. At the same time, the steps or actions in the method description can also be interchanged or adjusted in a manner that is obvious to those skilled in the art. Therefore, the various sequences in the specification and the drawings are only for the purpose of clearly describing a certain embodiment and are not meant to be a required sequence, unless otherwise specified that a certain sequence must be followed.

[0042] The serial numbers of the components in this document, such as "first", "second", etc., are only used to distinguish the objects described and do not have any order or technical meaning. The "connection" and "coupling" mentioned in this application, unless otherwise specified, include direct and indirect connections (couplings).

[0043] The existence of many protocols and technical specifications such as GSMA SGP.01 / 02, GSMA SGP.21 / SGP.22 and GSMA SGP.31 / 32 has caused some problems in the configuration and management of existing eSIMs.

[0044] High management complexity: Different eSIM protocol standards define their own communication components. Different eSIMs need to be configured and managed separately, which leads to complex operation processes and high management costs.

[0045] Poor system integration: The existing eSIM management system operates independently and lacks unified integration capabilities. This architecture results in poor interoperability between different types of devices, making it difficult to achieve centralized management and coordination of devices.

[0046] Insufficient flexibility and scalability: Faced with diverse device types and rapidly evolving eSIM standards, existing platforms lack sufficient flexibility and scalability to efficiently manage and expand new devices or new standards.

[0047] Please refer to Figure 1The present application proposes a unified management platform 100 compatible with multiple protocols, which may also be referred to as an Orchestration platform 100; the unified management platform 100 or the Orchestration platform 100 includes a communication interface component 110 and a control component 120, which are described in detail below.

[0048] The communication interface component 110 can communicate with service components of multiple protocols, wherein the multiple protocols include any two or three of the GSMASGP.01 / 02 protocol, the GSMA SGP.21 / 22 protocol and the GSMASGP.31 / 32 protocol.

[0049] The GSMA SGP.01 / 02 protocol or technical specification is about the application standard of eUICC in M2M devices. It introduces key components such as the Internet of Things management platform NgIOT, the subscription manager's secure router SM-SR and the subscription management data preparer SM-DP, which are used to configure, manage and distribute SIM profiles and eUICC itself. Therefore, the service components of the GSMA SGP.01 / 02 protocol may include the first Internet of Things management platform NgIOT, the subscription manager's secure router SM-SR and the subscription management data preparer SM-DP.

[0050] The GSMA SGP.21 / 22 protocol or technical specification is an important technical specification for eUICC on consumer devices. It introduces the Internet of Things management platform NgIOT, the data preparation server SM-DP+ for subscription management, and the message forwarding server Link, and introduces the concept of the local configuration assistant LPA to assist users in configuring and managing eUICC on consumer devices. Therefore, the service components of the GSMA SGP.21 / 22 protocol may include the second Internet of Things management platform NgIOT, the data preparation server SM-DP+ for subscription management, and the message forwarding server Link.

[0051] GSMA SGP.31 and SGP.32 are important technical specifications for eSIM on IoT devices. They introduce the IoT remote management platform EIM and the data preparation server SM-DP+ for subscription management, and configure the IoT profile assistant IPA for IoT devices. The IoT profile assistant IPA can run directly on the eUICC (LPAe) or IoT device (LPAd). The IoT remote management platform EIM can promote large-scale deployment and management of IoT devices that support eSIM. Therefore, the service components of the GSMA SGP.31 / 32 protocol can include the IoT remote management platform EIM and the data preparation server SM-DP+ for subscription management.

[0052] In some embodiments, the control component 120 is used to manage any two or three of the first type of IoT device 01 supporting the GSMA SGP.01 / 02 protocol, the second type of IoT device 02 supporting the GSMA SGP.21 / 22 protocol, and the second type of IoT device 02 supporting the GSMA SGP.31 / 32 protocol.

[0053] In some examples, the communication interface component 110 can communicate with the service component of the GSMA SGP.01 / 02 protocol and the service component of the GSMA SGP.21 / 22 protocol. Therefore, the control component 120 is used to manage the first type of IoT device 01 supporting the GSMA SGP.01 / 02 protocol and the second type of IoT device 02 supporting the GSMA SGP.21 / 22 protocol.

[0054] For example, the control component 120 manages the SIM card profile and eUICC of the IoT device supporting the GSMA SGP.01 / 02 protocol when communicating with the service component of the GSMA SGP.01 / 02 protocol through the communication interface component 110; the control component 120 manages the eSIM card profile of the local profile assistant LPA in the IoT device supporting the GSMA SGP.21 / 22 protocol when communicating with the service component of the GSMA SGP.21 / 22 protocol through the communication interface component 110.

[0055] In some examples, the communication interface component 110 can communicate with the service component of the GSMA SGP.01 / 02 protocol and the service component of the GSMA SGP.31 / 32 protocol. Therefore, the control component 120 is used to manage the first type of IoT device 01 supporting the GSMA SGP.01 / 02 protocol and the third type of IoT device 03 supporting the GSMA SGP.31 / 32 protocol.

[0056] For example, the control component 120 manages the SIM card profile and eUICC of the IoT device supporting the GSMA SGP.01 / 02 protocol when communicating with the service component of the GSMA SGP.01 / 02 protocol through the communication interface component 110; the control component 120 manages the eSIM card profile of the IoT profile assistant IPA in the IoT device supporting the GSMA SGP.31 / 32 protocol when communicating with the service component of the GSMA SGP.21 / 22 protocol through the communication interface component 110.

[0057] In some examples, the communication interface component 110 can communicate with the service component of the GSMA SGP.21 / 22 protocol and the service component of the GSMA SGP.31 / 32 protocol. Therefore, the control component 120 is used to manage the second type of IoT device 02 supporting the GSMA SGP.21 / 22 protocol and the third type of IoT device 03 supporting the GSMA SGP.31 / 32 protocol.

[0058] For example, when the control component 120 communicates with the service component of the GSMA SGP.21 / 22 protocol through the communication interface component 110, the control component 120 manages the eSIM card profile for the local profile assistant LPA in the IoT device that supports the GSMA SGP.21 / 22 protocol; when the control component 120 communicates with the service component of the GSMA SGP.21 / 22 protocol through the communication interface component 110, the control component 120 manages the eSIM card profile for the IoT profile assistant IPA in the IoT device that supports the GSMA SGP.31 / 32 protocol.

[0059] In some examples, the communication interface component 110 can communicate with the service component of the GSMA SGP.01 / 02 protocol, the service component of the GSMA SGP.21 / 22 protocol, and the service component of the GSMA SGP.31 / 32 protocol. Therefore, the control component 120 is used to manage the first type of IoT device 01 supporting the GSMA SGP.01 / 02 protocol, the second type of IoT device 02 supporting the GSMA SGP.21 / 22 protocol, and the third type of IoT device 03 supporting the GSMA SGP.31 / 32 protocol.

[0060] For example, the control component 120 manages the SIM card profile and eUICC of the IoT device supporting the GSMA SGP.01 / 02 protocol when communicating with the service component of the GSMA SGP.01 / 02 protocol through the communication interface component 110; the control component 120 manages the eSIM card profile of the local profile assistant LPA in the IoT device supporting the GSMA SGP.21 / 22 protocol when communicating with the service component of the GSMA SGP.21 / 22 protocol through the communication interface component 110; the control component 120 manages the eSIM card profile of the IoT profile assistant IPA in the IoT device supporting the GSMA SGP.31 / 32 protocol when communicating with the service component of the GSMA SGP.21 / 22 protocol through the communication interface component 110.

[0061] The following describes in detail how the unified management platform 100 of the present application manages each type of IoT device.

[0062] 1. Combine the following Figures 2 to 4 The management of the first type of IoT device 01 is described.

[0063] In some embodiments, the unified management platform 100 is able to communicate with the first Internet of Things management platform NgIOT, and the control component 120 of the unified management platform 100 sends the operation instructions to the first Internet of Things management platform NgIOT. The first Internet of Things management platform NgIOT communicates with the security router SM-SR of the subscription manager to inform it of the target operation to be performed. Then the security router SM-SR of the subscription manager communicates with the first type of Internet of Things device 01, so that the first type of Internet of Things device 01 performs the corresponding operation, such as receiving a new configuration file or performing a configuration file switch (that is, switching operators). In some examples, if the operation instruction is used to trigger the download of the configuration file, the control component 120 sends the operation instruction to the first IoT management platform NgIOT, and the first IoT management platform NgIOT communicates with the secure router SM-SR of the subscription manager to inform it of the target operation to be performed. The secure router SM-SR of the subscription manager also communicates with the data preparer SM-DP of the subscription management, so that the data preparer SM-DP of the subscription management sends the configuration file to the first type of IoT device 01, so that the eUICC of the first type of IoT device 01 is configured based on the configuration file, for example, the eUICC of the first type of IoT device 01 performs secure download and storage of the configuration file under the guidance of the secure router SM-SR of the subscription manager, and activates the new configuration file as needed. After the new configuration file is successfully downloaded and activated, the first type of IoT device 01 can be connected to the network of the new operator to complete the entire business process. Among them, the data preparer SM-DP of the subscription management can communicate with the operator server to obtain the configuration file.

[0064] In some embodiments, the unified management platform 100 is able to communicate with the secure router SM-SR of the subscription manager, and the control component 120 of the unified management platform 100 directly sends the operation instructions to the secure router SM-SR of the subscription manager, informing it of the target operation to be performed, and then the secure router SM-SR of the subscription manager communicates with the first type of Internet of Things device 01, so that the first type of Internet of Things device 01 performs the corresponding operation, such as receiving a new configuration file or performing a configuration file switch (i.e., switching operators). In some examples, if the operation instruction is used to trigger the download of the configuration file, the control component 120 sends the operation instruction to the secure router SM-SR of the subscription manager, and the secure router SM-SR of the subscription manager also communicates with the data preparer SM-DP of the subscription management, so that the data preparer SM-DP of the subscription management sends the configuration file to the first type of IoT device 01, so that the eUICC of the first type of IoT device 01 is configured based on the configuration file, for example, the eUICC of the first type of IoT device 01 performs secure download and storage of the configuration file under the guidance of the secure router SM-SR of the subscription manager, and activates the new configuration file as needed. After the new configuration file is successfully downloaded and activated, the first type of IoT device 01 can be connected to the network of the new operator to complete the entire business process. Among them, the data preparer SM-DP of the subscription management can communicate with the operator server to obtain the configuration file.

[0065] In some embodiments, the unified management platform 100 is able to communicate with the IoT remote management platform EIM, and the control component 120 of the unified management platform 100 sends the operation instruction to the IoT remote management platform EIM, so that the IoT remote management platform EIM communicates with the first type of IoT device 01, so that the first type of IoT device 01 performs the corresponding operation, such as receiving a new configuration file or performing a configuration file switch (i.e., switching operators). In some examples, if the operation instruction is used to trigger the download of the configuration file, the control component 120 sends the operation instruction to the IoT remote management platform EIM, and the IoT remote management platform EIM also communicates with the data preparer SM-DP for subscription management, so that the data preparer SM-DP for subscription management sends the configuration file to the first type of IoT device 01, so that the eUICC of the first type of IoT device 01 is configured based on the configuration file; wherein, the data preparer SM-DP for subscription management is able to communicate with the operator server to obtain the configuration file. In some examples, if the operation instruction is used to trigger the download of the configuration file, the control component 120 sends the operation instruction to the IoT remote management platform EIM, and the IoT remote management platform EIM also communicates with the data preparation server SM-DP+ for subscription management. The data preparation server SM-DP+ for subscription management sends the configuration file to the first type of IoT device 01 through the IoT remote management platform EIM, so that the eUICC of the first type of IoT device 01 is configured based on the configuration file; wherein, the data preparation server SM-DP+ for subscription management can communicate with the operator server to obtain the configuration file.

[0066] In some examples, after the first type of IoT device 01 is initialized and started, the IoT remote management platform EIM can communicate with the first type of IoT device 01 through the MQTT protocol or the HTTP protocol: when using the MQTT protocol, the IoT remote management platform EIM actively sends commands through PUSH, and when using the HTTP protocol, the IoT remote management platform EIM stores the instructions. When the first type of IoT device 01 initiates an HTTP request, the first type of IoT device 01 obtains the command through PULL and executes the corresponding eSIM operation.

[0067] In some embodiments, the control component 120 receives data or information uploaded by the first type of IoT device 01 through the secure router SM-SR of the subscription manager and the first IoT management platform NgIOT in sequence. In some embodiments, the control component 120 receives data or information directly uploaded by the first type of IoT device 01 through the secure router SM-SR of the subscription manager. In some embodiments, the control component 120 receives data or information uploaded by the first type of IoT device 01 through the IoT remote management platform EIM.

[0068] In some embodiments, the data uploaded by the first type of IoT device 01 includes the environmental data collected by it, and the control component 120 controls the storage of the environmental data uploaded by the first type of IoT device 01 in a distributed database for calling and analysis. The environmental data can be the data collected by the first type of IoT device 01 through its sensor module or data interface, such as temperature, humidity, pressure, position, etc.

[0069] In some embodiments, the information uploaded by the first type of IoT device 01 includes its operating status information. The control component 120 monitors the operating status information of the first type of IoT device 01 in real time, and displays it through the user interface and / or issues an alarm message when an abnormality is detected.

[0070] 2. Combine the following Figures 5 to 7 Explain the management of the second type of IoT device 02

[0071] In some embodiments, the unified management platform 100 is able to communicate with the second Internet of Things management platform NgIOT, and the control component 120 of the unified management platform 100 sends the operation instruction to the second Internet of Things management platform NgIOT, and the second Internet of Things management platform NgIOT communicates with the subscription message forwarding server Link, so that the message forwarding server Link communicates with the second type of Internet of Things device 02, so that the second type of Internet of Things device 02 performs corresponding operations, such as receiving a new configuration file or performing a configuration file switch (that is, switching operators). In some examples, if the operation instruction is used to trigger the download of the configuration file, the control component 120 of the unified management platform 100 sends the operation instruction to the second Internet of Things management platform NgIOT, and the second Internet of Things management platform NgIOT also communicates with the subscription management data preparation server SM-DP+, so that the subscription management data preparation server SM-DP+ sends the configuration file to the second type of Internet of Things device 02, so that the local configuration file assistant LPA of the second type of Internet of Things device 02 is configured based on the configuration file; wherein, the subscription management data preparation server SM-DP+ can communicate with the operator server to obtain the configuration file.

[0072] In some embodiments, the unified management platform 100 is able to communicate with the message forwarding server Link, and the control component 120 of the unified management platform 100 directly sends the operation instructions to the message forwarding server Link, so that the message forwarding server Link communicates with the second type of Internet of Things device 02, so that the second type of Internet of Things device 02 performs corresponding operations, such as performing configuration file switching (that is, switching operators).

[0073] In some embodiments, the unified management platform 100 is able to communicate with the Internet of Things remote management platform EIM, and the control component of the unified management platform 100 sends the operation instruction to the Internet of Things remote management platform EIM, so that the Internet of Things remote management platform EIM communicates with the second type of Internet of Things device 02, so that the second type of Internet of Things device 02 performs corresponding operations, such as receiving a new configuration file or performing a configuration file switch (that is, switching operators). In some examples, if the operation instruction is used to trigger the download of the configuration file, the control component 120 sends the operation instruction to the Internet of Things remote management platform EIM, and the Internet of Things remote management platform EIM also communicates with the subscription management data preparation server SM-DP+, and the subscription management data preparation server SM-DP+ sends the configuration file to the second type of Internet of Things device 02 through the Internet of Things remote management platform EIM, so that the local configuration file assistant LPA of the second type of Internet of Things device 02 is configured based on the configuration file; wherein, the subscription management data preparation server SM-DP+ is able to communicate with the operator server to obtain the configuration file.

[0074] In some examples, after the second type of IoT device 02 is initialized and started, the message forwarding server Link can communicate with the second type of IoT device 02 through the MQTT protocol or the HTTP protocol: the message forwarding server Link receives the startup information of the device through the HTTP or MQTT protocol, and based on the received information, forwards the IoT device startup status or request to the corresponding second IoT management platform NgIOT and / or the unified management platform 100 through PUSH or PULL.

[0075] In some embodiments, the control component 120 receives data or information uploaded by the second type of IoT device 02 via the message forwarding server Link and the second IoT management platform NgIOT in sequence. In some embodiments, the control component 120 receives data or information directly uploaded by the second type of IoT device 02 via the message forwarding server Link. In some embodiments, the control component 120 receives data or information uploaded by the second type of IoT device 02 via the IoT remote management platform EIM.

[0076] In some embodiments, the data uploaded by the second type of IoT device 02 includes the environmental data collected by it, and the control component 120 controls the storage of the environmental data uploaded by the second type of IoT device 02 in a distributed database for calling and analysis. The environmental data can be data collected by the second type of IoT device 02 through its sensor module or data interface, such as temperature, humidity, pressure, position, etc.

[0077] In some embodiments, the information uploaded by the second type of Internet of Things device 02 includes its operating status information. The control component 120 monitors the operating status information of the second type of Internet of Things device 02 in real time, and displays it through the user interface and / or issues an alarm message when an abnormality is detected.

[0078] 3. Combine the following Figure 8 The management of the third type of IoT device 03 is explained.

[0079] In some embodiments, the unified management platform 100 can communicate with the Internet of Things remote management platform EIM, and the control component 120 of the unified management platform 100 sends the operation instruction to the Internet of Things remote management platform EIM, so that the Internet of Things remote management platform EIM communicates with the third-category Internet of Things device 03, so that the third-category Internet of Things device 03 performs the corresponding operation. In some examples, if the operation instruction is used to trigger the download of the configuration file, after the control component 120 of the unified management platform 100 sends the operation instruction to the Internet of Things remote management platform EIM, the Internet of Things remote management platform EIM also communicates with the data preparation server SM-DP+ for subscription management, so that the data preparer SM-DP communicates, so that the data preparation server SM-DP+ for subscription management directly sends the configuration file or sends it to the third-category Internet of Things device 03 through the Internet of Things remote management platform EIM, so that the Internet of Things configuration file assistant IPA of the third-category Internet of Things device 03 is configured based on the configuration file.

[0080] In some embodiments, the control component 120 receives data or information uploaded by the third type of IoT device 03 via the IoT remote management platform EIM.

[0081] In some embodiments, the data uploaded by the third type of IoT device 03 includes the environmental data collected by it, and the control component 120 controls the storage of the environmental data uploaded by the third type of IoT device 03 in a distributed database for calling and analysis. The environmental data can be the data collected by the third type of IoT device 03 through its sensor module or data interface, such as temperature, humidity, pressure, position, etc.

[0082] In some embodiments, the information uploaded by the third-category IoT device 03 includes its operating status information. The control component 120 monitors the operating status information of the third-category IoT device 03 in real time, and displays it through the user interface and / or issues an alarm message when an abnormality is detected.

[0083] In some examples, after the third-category IoT device 03 is initialized and started, the IoT remote management platform EIM can communicate with the third-category IoT device 03 through the MQTT protocol or the HTTP protocol: when using the MQTT protocol, the IoT remote management platform EIM actively sends commands through PUSH, and when using the HTTP protocol, the IoT remote management platform EIM stores the instructions. When the third-category IoT device 03 initiates an HTTP request, the third-category IoT device 03 obtains the command through PULL and executes the corresponding eSIM operation.

[0084] The above is some description of the unified management platform 100 . Fig. 9 The unified management platform 100 is a schematic diagram showing that it is compatible with and manages three protocols among the GSMA SGP.01 / 02 protocol, the GSMA SGP.21 / 22 protocol and the GSMA SGP.31 / 32 protocol.

[0085] In some embodiments, the unified management platform 100 may be implemented using a microservice architecture, where processing functions of different protocols are integrated into a microservice module.

[0086] In other embodiments, the unified management platform 100 can be designed as a modular architecture, allowing different microservice modules to handle different types of eSIM standards and device types respectively; this modular architecture has the following characteristics (different designs and implementations such as different components, functions, layers, microservices or overall single architecture): each module is independently responsible for the management of an eSIM standard (such as one module specifically manages the SGP.21 / SGP.22 standard, and another module manages the SGP.31 / SGP.32 standard); the modules are integrated together through a unified interface layer to achieve cross-module communication and data sharing. This design ensures the integrity of the system while maintaining the independence of each module; since each module is independent, the platform can dynamically load and unload modules as needed to adapt to different devices and standards, providing flexible expansion capabilities; the advantage of this modular architecture is that it allows finer-grained control and higher flexibility, and can adjust and optimize the functions of each module according to specific needs, while avoiding the design complexity of a single large platform.

[0087] In other embodiments, the unified management platform 100 can be designed through a plug-in architecture. The unified management platform 100 adopts a modular design, and the core functional modules and additional functions are extended by means of plug-ins. This architecture allows different functional modules to be dynamically loaded or unloaded without modifying or restarting the entire system. In addition, a standardized plug-in development interface (API) is provided, and developers can develop new plug-ins as needed. For example, develop plug-ins that support new eSIM configuration management, device monitoring, protocol conversion, or network optimization. The unified management platform 100 may include a plug-in management system that allows administrators to view, enable, disable, and update plug-ins. Administrators can select appropriate plug-ins to expand the functionality of the platform based on different needs and scenarios. Plug-in functions can also be extended, such as protocol conversion plug-ins: plug-ins can implement protocol conversion functions, such as automatically converting CoAP to HTTP between devices and platforms, converting MQTT to HTTP / 2, or supporting conversion of non-standard protocols to standard protocols. This enables the platform to be compatible with more types of devices and network conditions; for example, network optimization plug-ins: plug-ins can analyze current network conditions (such as bandwidth, latency, jitter) and automatically adjust data transmission strategies; for example, when the network is congested, plug-ins can dynamically adjust the frequency of data packet transmission or switch to a more efficient protocol; for example, intelligent operator switching plug-ins: plug-ins are used to implement intelligent operator switching strategies, and machine learning algorithms are used to predict the best switching time and target operator. For example, plug-ins can monitor parameters such as signal strength, network quality and data costs in real time, and automatically select the best operator based on historical data and prediction models; for example, security enhancement plug-ins: provide additional security function plug-ins, such as data encryption, authentication and authorization mechanisms. These plug-ins can be loaded as needed to ensure the secure transmission and storage of sensitive data. As for the management and upgrade of plug-ins, plug-ins can be updated or upgraded online through the plug-in management system of the unified management platform 100 without stopping the system or affecting the running services, so that the system can obtain the latest functions and security updates while running uninterruptedly. Using containerization technology (such as Docker) or virtualization technology (such as Kubernetes) to deploy and manage plug-ins makes the installation, upgrade and uninstallation process of plug-ins easier and safer. For the communication between plug-ins and the platform: plug-ins communicate with the platform core module through standardized interfaces. The platform core module can send control instructions to plug-ins and receive status reports from plug-ins to ensure the coordinated work of the entire system. In addition, an event-driven mechanism is introduced. When a specific event occurs (such as a change in device status or a change in network conditions), the corresponding plug-in is triggered to perform a specific task. This mechanism can improve the system's response speed and resource utilization.

[0088] In addition, regarding the data communication of the unified management platform 100, in addition to the above-mentioned methods, there may be other methods.

[0089] The unified management platform 100 may interact with the device in a request-response mode.

[0090] In addition, an alternative solution may use a push mechanism, whereby the unified management platform 100 actively pushes data to the device when there is an update (such as a new eSIM configuration file or an operator switching request); the advantage of this method is that it is highly real-time and is suitable for application scenarios with high requirements for response time (such as quickly switching network operators).

[0091] The IoT device can also pull the latest eSIM profile or carrier information from the unified management platform 100 periodically or based on conditions (such as low signal strength or cross-regional movement). The advantage of this method is that the control is simpler, and the device only requests updates when needed, reducing unnecessary data transmission.

[0092] The IoT device can also periodically poll the unified management platform 100 to check whether there are new updates or instructions, for example, by sending a query request to the platform at regular intervals. The advantage of the periodic polling mechanism is that it is simple to implement, but it may increase the network load, so it is suitable for scenarios with infrequent updates.

[0093] IoT devices can also subscribe to specific topics (such as "profile update" or "carrier switching"). The platform publishes messages when there are updates, and only devices that have subscribed to the topic will receive the message. This mechanism effectively reduces the network load and ensures that only devices in need are notified, which is suitable for large-scale device management scenarios.

[0094] In addition, CoAP can be used instead of HTTP or MQTT for communication, which is particularly suitable for resource-constrained devices (such as low-power IoT devices). CoAP supports a lightweight request-response mode and an optional resource observation mechanism. Using the CoAP protocol between IoT devices and the unified management platform 100 can reduce data overhead and save network bandwidth while providing HTTP-like functions (such as GET, POST, PUT, DELETE, etc.).

[0095] It is also possible to combine different protocols (such as MQTT and HTTP / 2) and switch dynamically according to network conditions and data types. MQTT is suitable for low-latency, real-time data transmission, while HTTP / 2 is used for large data block transmission. The advantage of hybrid protocols is that they can be optimized as needed, such as giving priority to MQTT in low-bandwidth or high-latency environments and using HTTP / 2 in high-bandwidth, low-latency environments, thereby improving the performance and responsiveness of the overall system.

[0096] In addition, operator switching is also important, which can be based on one or more switching strategies or mechanisms.

[0097] For example, a switching strategy based on geographic location: using GPS or other location services to determine the geographic location of IoT devices, and automatically triggering the operator switching logic when the IoT device moves to a different geographic area. This strategy can achieve seamless switching by downloading the required operator configuration files in advance or dynamically updating, reducing the delay of network switching.

[0098] Another example is based on local caching and priority management: multiple operators' configuration files are cached locally on IoT devices, and the appropriate operator is dynamically selected based on signal quality, data charges, and usage policies. This method reduces dependence on the platform, enables faster switching, and can still perform switching operations when there is no network connection.

[0099] Another example is the AI / ML-based predictive switching mechanism: using artificial intelligence (AI) or machine learning (ML) algorithms to predict the possible movement path of the device and network coverage changes, and prepare corresponding operator configuration files in advance. This solution can significantly improve the efficiency of switching and user experience, especially in complex network environments or high-speed mobile scenarios.

[0100] Through the unified management platform 100 of the present application, the eSIM management process can be simplified, the technical gap between different device types and eSIM standards can be reduced, and three eSIM standards, namely MGSMA SGP.01 / 02 protocol, GSMA SGP.21 / 22 protocol and GSMA SGP.31 / 32 protocol, can be integrated into one platform to achieve unified management of existing devices, stock devices and future devices.

[0101] Taking the second type of IoT device 02 supporting the GSMA SGP.21 / 22 protocol as an example, when the second type of IoT device 02 supporting the GSMA SGP.21 / 22 protocol is connected, the second type of IoT device 02 sends authentication information such as device ID, model, supported protocol version, etc. to the unified management platform 100 through the message forwarding server Link. The control component 120 of the Orchestration platform 100 uses a pre-shared key (PSK) or a digital certificate to authenticate the access device to ensure the legitimacy of the access device; the authentication process can be performed in an encrypted channel (such as TLS1.2 or 1.3) to prevent data from being eavesdropped and tampered with; after successful authentication, the Orchestration platform 100 registers the information of the access device into the management database, assigns a unique device identifier (i.e., device ID) to the access device, and includes the access device in the management scope. For registered IoT devices, the Orchestration platform 100 first checks the current eSIM configuration status of the second type of IoT device 02. If an update or initial configuration is required, the Orchestration platform 100 sends a Profile download command to the second type of IoT device 02 through the message forwarding server Link. After receiving the configuration data, the second type of IoT device 02 verifies the integrity and validity of the data, applies the new configuration and feeds back the configuration result (success or failure) to the Orchestration platform 100. The feedback is usually returned in the form of an encrypted and signed message to prevent forgery. During the operation of the second type of IoT device 02, it packages the collected data and sends it to the message forwarding server Link via the MQTT or HTTP / 2 protocol. The message forwarding server Link transmits the data to the Orchestration platform 100 according to the preset routing rules and queue strategies. After receiving the data, the Orchestration platform 100 stores it in a distributed database and uses data analysis tools for processing and analysis.

[0102] Users can interact with the system through the user interface (Web or mobile application) of the Orchestration platform 100. The user interface provides functions such as device status monitoring, configuration management, and data analysis to support users in device management operations. The user interface can adopt a responsive design, support multiple languages ​​and customization functions, and ensure consistency and ease of use of the user experience.

[0103] In some examples, the Orchestration platform 100 can not only directly manage the second type of IoT devices 02 that support the GSMA SGP.21 / 22 protocol, but also seamlessly connect with the previously independent first IoT management platform NgIOT and / or the second IoT management platform NgIOT. By communicating through the HTTP protocol, this connection capability allows enterprises to continue to use existing IoT management systems and avoid large-scale system replacement.

[0104] In addition, the Orchestration platform 100 can also communicate directly with the secure router SM-SR of the subscription manager, which means that the Orchestration platform 100 can directly manage eSIM configuration and device information without relying on the old platform, and perform secure subscription management and device information updates.

[0105] The Orchestration platform 100 achieves higher flexibility and compatibility by supporting docking with previously independent IoT management platforms (such as the first IoT management platform NgIOT and / or the second IoT management platform NgIOT), as well as docking with the subscription manager's secure router SM-SR and the message forwarding server Link. While being compatible with existing devices and systems, the Orchestration platform 100 can also quickly adapt to the introduction of new devices and new technologies, and can efficiently handle eSIM configuration, data transmission, remote control and status monitoring of various IoT device types to meet diverse IoT application needs.

[0106] Take a children's watch company as an example. It has existing devices and new devices. The existing devices are already in use and support traditional IoT management protocols (such as GSMA SGP.01 / 02 protocols), but may not have eSIM functions; while the new devices support eSIM technology. The new devices are IoT devices that support GSMA SGP.21 / 22 protocols or GSMA SGP.31 / 32 protocols.

[0107] Centralized management of new and old devices is achieved through the Orchestration platform 100, and eSIM technology is used to remotely configure and manage new devices, as well as unify operator selection and eSIM profile management.

[0108] Specifically, existing devices are connected to the Orchestration platform 100. The Orchestration platform 100 supports management protocols for traditional devices, such as MQTT and HTTP, which enables existing devices to communicate with the Orchestration platform 100. New devices are also connected to the Orchestration platform 100. Since these new devices support eSIM functions (SGP.21 / 22 and SGP.31 / 32 standards), they communicate with the Orchestration platform 100 through MQTT, HTTP and specific eSIM management interfaces (such as ESipa and ESep).

[0109] The Orchestration platform 100 classifies all devices into existing devices and new devices through scanning and identification, wherein the existing devices do not have the eSIM function, while the new devices have the eSIM function. For the existing devices, the Orchestration platform 100 continues to use the traditional management method. For the new devices, the Orchestration platform 100 will use the IoT remote management platform EIM for remote configuration.

[0110] The Orchestration platform 100 can communicate directly with the data preparer SM-DP and / or the data preparation server SM-DP+ of the subscription management, and can also communicate with the secure router SM-SR of the subscription manager to prepare and generate new eSIM configuration files, which are customized according to the operator's requirements and the usage scenarios of the device. Once the eSIM configuration file is prepared, the IoT remote management platform EIM pushes the configuration file securely to the new device through the ESipa or ESep interface. The new device connects to the network and authenticates according to the received configuration file to complete the activation of the eSIM.

[0111] The Orchestration Platform 100 allows customers to switch freely between multiple operators. Through the Orchestration Platform 100, customers can select local operators in different countries in real time to optimize communication costs and network coverage.

[0112] When a device moves to a new country, the Orchestration platform 100 can automatically detect the location of the device and trigger the operator switching process. The IoT remote management platform EIM can update the eSIM profile on the device to connect to the new operator network.

[0113] Orchestration platform 100 provides real-time status monitoring for all devices, whether they are existing or newly purchased. Administrators can view information such as device connection status, data usage, battery power, etc. Through Orchestration platform 100, administrators can manage devices in a unified manner, including pushing software updates, restarting devices, adjusting configurations, and other operations.

[0114] Through Orchestration Platform 100, customers have achieved the following goals:

[0115] Efficient management: All devices can be managed through a unified platform without considering the type of device and eSIM support; flexibility is improved: through eSIM technology, devices can easily switch operators and reduce international roaming charges; operating costs are reduced: automated eSIM management reduces the need for manual operations and reduces labor costs; real-time response capabilities: the platform provides real-time monitoring and management capabilities, allowing customers to respond quickly to device failures or network problems.

[0116] The unified management platform 100 or Orchestration platform 100 of the present application has many advantages.

[0117] Simplify system architecture and reduce management complexity: By supporting multiple eSIM standards on a unified platform, the present invention simplifies the management requirements for different devices and standards, and reduces the complexity of developing and maintaining multiple independent systems; as the number and types of devices increase, the unified management platform 100 can efficiently handle the management tasks of these devices, greatly reducing system complexity and operation and maintenance costs.

[0118] Enhanced device compatibility and future scalability: The unified management platform 100 provided by the present invention is highly flexible and can support seamless collaboration between existing devices, stock devices and future new devices; this ensures compatibility between different devices and eSIM standards, avoids interoperability issues caused by technology updates, and provides infrastructure support for the expansion of future devices.

[0119] Improve resource utilization and management efficiency: By uniformly managing and coordinating multiple devices, the present invention significantly improves the resource utilization of the system. The centralized management of devices makes resource allocation more reasonable, avoiding repeated configuration and resource waste. In addition, the unified Orchestration platform 100 can accelerate the remote configuration and management process of eSIM, and improve the overall response speed and processing efficiency of the system.

[0120] Improve system stability and reliability: This invention integrates eSIM management of different standards into one platform, reducing technical risks in cross-standard or cross-platform operations, thereby improving system stability. At the same time, centralized management makes fault diagnosis and problem troubleshooting more direct and effective, further enhancing system reliability.

[0121] Reduce overall operating costs: Since the present invention simplifies the management and device coordination of multi-standard eSIMs, it greatly reduces the development, deployment and maintenance requirements of different systems, directly reducing overall operating costs. In addition, the compatibility of devices and future expansion capabilities reduce the economic burden of repeated investments and future technology upgrades.

[0122] This document is described with reference to various exemplary embodiments. However, those skilled in the art will recognize that changes and modifications may be made to the exemplary embodiments without departing from the scope of this document. For example, various operating steps and components for performing the operating steps may be implemented in different ways (e.g., one or more steps may be deleted, modified, or incorporated into other steps) depending on the specific application or considering any number of cost functions associated with the operation of the system.

[0123] Although the principles of this invention have been shown in various embodiments, many modifications of structures, arrangements, proportions, elements, materials and components particularly suitable for specific environments and operational requirements can be used without departing from the principles and scope of this invention. The above modifications and other changes or amendments will be included in the scope of this invention.

[0124] The foregoing specific description has been described with reference to various embodiments. However, those skilled in the art will recognize that various modifications and changes can be made without departing from the scope of the present disclosure. Therefore, the consideration of the present disclosure will be illustrative rather than restrictive, and all these modifications will be included in its scope. Similarly, the advantages, other advantages and solutions to the problems of various embodiments have been described above. However, the benefits, advantages, solutions to the problems and any elements that can produce these, or make them more clear, should not be interpreted as critical, necessary or necessary. The term "include" and any other variants used in this article are all non-exclusive inclusions, so that the process, method, article or device including the list of elements not only includes these elements, but also includes other elements that are not explicitly listed or do not belong to the process, method, system, article or device. In addition, the term "coupled" and any other variants used in this article refer to physical connections, electrical connections, magnetic connections, optical connections, communication connections, functional connections and / or any other connections.

[0125] Those skilled in the art will appreciate that many changes may be made to the details of the above-described embodiments without departing from the basic principles of the invention. Therefore, the scope of the present invention should be determined solely by the claims.

Claims

1. A unified management platform compatible with multiple protocols, characterized in that: include: Communication interface components and control components; The communication interface component can communicate with service components of multiple protocols, and the multiple protocols include any two or three of the GSMASGP.01 / 02 protocol, the GSMASGP.21 / 22 protocol and the GSMA SGP.31 / 32 protocol; the service components of the GSMASGP.01 / 02 protocol include the first Internet of Things management platform NgIOT, the secure router SM-SR of the subscription manager and the data preparer SM-DP of the subscription management, the service components of the GSMASGP.21 / 22 protocol include the second Internet of Things management platform NgIOT, the data preparation server SM-DP+ of the subscription management and the message forwarding server Link, and the service components of the GSMASGP.31 / 32 protocol include the Internet of Things remote management platform EIM and the data preparation server SM-DP+ of the subscription management; The control component is used to manage any two or three of the first type of IoT devices supporting the GSMA SGP.01 / 02 protocol, the second type of IoT devices supporting the GSMA SGP.21 / 22 protocol, and the second type of IoT devices supporting the GSMA SGP.31 / 32 protocol; The control component manages the first type of IoT devices including: The control component sends the operation instruction to the first Internet of Things management platform NgIOT, so that the first Internet of Things management platform NgIOT communicates with the security router SM-SR of the subscription manager, so that the security router SM-SR of the subscription manager communicates with the first type of Internet of Things device, so that the first type of Internet of Things device performs the corresponding operation; and / or, the control component sends the operation instruction to the security router SM-SR of the subscription manager, so that the security router SM-SR of the subscription manager communicates with the first type of Internet of Things device, so that the first type of Internet of Things device performs the corresponding operation; and / or, the control component sends the operation instruction to the Internet of Things remote management platform EIM, so that the Internet of Things remote management platform EIM communicates with the first type of Internet of Things device, so that the first type of Internet of Things device performs the corresponding operation; The control component manages the second type of IoT devices including: The control component sends the operation instruction to the second Internet of Things management platform NgIOT, so that the second Internet of Things management platform NgIOT communicates with the message forwarding server Link, so that the message forwarding server Link communicates with the second type of Internet of Things devices, so that the second type of Internet of Things devices perform corresponding operations; and / or, the control component sends the operation instruction to the message forwarding server Link, so that the message forwarding server Link communicates with the second type of Internet of Things devices, so that the second type of Internet of Things devices perform corresponding operations; and / or, the control component sends the operation instruction to the Internet of Things remote management platform EIM, so that the Internet of Things remote management platform EIM communicates with the second type of Internet of Things devices, so that the second type of Internet of Things devices perform corresponding operations; The control component manages the third type of IoT devices including: The control component sends the operation instruction to the Internet of Things remote management platform EIM, so that the Internet of Things remote management platform EIM communicates with the third type of Internet of Things device, so that the third type of Internet of Things device performs the corresponding operation.

2. The unified management platform according to claim 1, characterized in that: The management of the first category of IoT devices by the control component also includes: if the operation instruction is used to trigger the downloading of a configuration file, the security router SM-SR of the subscription manager also communicates with the data preparer SM-DP of the subscription management, so that the data preparer SM-DP of the subscription management sends the configuration file to the first category of IoT devices, so that the eUICC of the first category of IoT devices is configured based on the configuration file; wherein the data preparer SM-DP of the subscription management can communicate with the operator server to obtain the configuration file.

3. The unified management platform according to claim 1, characterized in that: The control component's management of the first type of IoT devices also includes: The control component receives data or information uploaded by the first type of Internet of Things device through the subscription manager's security router SM-SR and the first Internet of Things management platform NgIOT in sequence; and / or, the control component receives data or information uploaded by the first type of Internet of Things device directly through the subscription manager's security router SM-SR; and / or, the control component receives data or information uploaded by the first type of Internet of Things device through the Internet of Things remote management platform EIM.

4. The unified management platform according to claim 1, characterized in that: The control component's management of the second category of IoT devices also includes: if the operation instruction is used to trigger the download of the configuration file, the second IoT management platform NgIOT also communicates with the data preparation server SM-DP+ for subscription management, so that the data preparation server SM-DP+ for subscription management sends the configuration file to the second category of IoT devices, so that the local configuration file assistant LPA of the second category of IoT devices is configured based on the configuration file; or, if the operation instruction is used to trigger the download of the configuration file, the IoT remote management platform EIM also communicates with the data preparation server SM-DP+ for subscription management, so that the data preparer SM-DP communicates, so that the data preparation server SM-DP+ for subscription management sends the configuration file to the second category of IoT devices, so that the local configuration file assistant LPA of the second category of IoT devices is configured based on the configuration file.

5. The unified management platform according to claim 1, characterized in that: The control component's management of the second-category IoT device also includes: the control component receiving data or information uploaded by the second-category IoT device via the message forwarding server Link and the second IoT management platform NgIOT in sequence; and / or, the control component receiving data or information directly uploaded by the second-category IoT device via the message forwarding server Link; and / or, the control component receiving data or information uploaded by the second-category IoT device via the IoT remote management platform EIM.

6. The unified management platform according to claim 1, characterized in that: The control component's management of the third category IoT device also includes: if the operation instruction is used to trigger the download of the configuration file, the IoT remote management platform EIM also communicates with the data preparation server SM-DP+ for subscription management, so that the data preparer SM-DP communicates, so that the data preparation server SM-DP+ for subscription management directly sends the configuration file or sends it through the IoT remote management platform EIM to the third category IoT device, so that the IoT configuration file assistant IPA of the third category IoT device is configured based on the configuration file.

7. The unified management platform according to claim 1, characterized in that: The control component's management of the second-category IoT device also includes: the control component receiving data or information uploaded by the third-category IoT device via the IoT remote management platform EIM.

8. The unified management platform according to claim 3, 5 or 7, characterized in that: The data uploaded by the IoT devices include the environmental data collected by them. The control component controls the storage of the environmental data uploaded by various IoT devices in a distributed database for calling and analysis.

9. The unified management platform according to claim 3, 5 or 7, characterized in that: The information uploaded by the IoT devices includes their operating status information. The control component monitors the operating status information of each IoT device in real time, and displays it through the user interface and / or issues an alarm message when an abnormality is detected.

10. A unified management platform compatible with multiple protocols, characterized in that: include: A communication interface component, wherein the communication interface component can communicate with a service component of multiple protocols, wherein the multiple protocols include any two or three of the GSMA SGP.01 / 02 protocol, the GSMA SGP.21 / 22 protocol, and the GSMA SGP.31 / 32 protocol; A control component is used to communicate with service components of multiple protocols through the communication interface component, manage SIM card profiles and eUICCs for IoT devices supporting GSMA SGP.01 / 02 protocols when communicating with service components of GSMA SGP.01 / 02 protocols, manage eSIM card profiles for a local profile assistant LPA in IoT devices supporting GSMA SGP.21 / 22 protocols when communicating with service components of GSMA SGP.21 / 22 protocols, and manage eSIM card profiles for an IoT profile assistant IPA in IoT devices supporting GSMA SGP.31 / 32 protocols when communicating with service components of GSMA SGP.21 / 22 protocols.

Images