WO2020019987A1 - Method and apparatus for transmitting euicc data in internet of things - Google Patents

Abstract

Provided is a method for transmitting eUICC data in the Internet of Things. The method comprises: an Internet of Things (IoT) platform acquiring an SMS message transceiving capability of a communication network; where the communication network does not support an SMS message transceiving function, the IoT platform converting an SMS message to be sent to the terminal device to a first LwM2M message, wherein the SMS message comprises target data sent to an embedded universal integrated circuit card (eUICC), and a data format of the target data of the eUICC comprised in the LwM2M message is SMS; and the IoT platform sending the LwM2M message to the terminal device. In the technical solution provided in the present application, an application server (for example, an SM platform) can send, on the Internet of Things, the SMS message to the eUICC on the terminal device, so as to complete remote configuration of user data on the eUICC.

Description

Method and device for transmitting eUICC data in internet of things

This application claims the priority of a Chinese patent application filed on July 27, 2018 with the State Intellectual Property Office of China, application number 201810847436.2, and application name "A Method and Device for Transmission of eUICC Data in the Internet of Things", its entire content Incorporated by reference in this application.

Technical field

This application relates to the field of communications, and more specifically, to a method and device for transmitting eUICC data in the Internet of Things.

Background technique

The embedded universal integrated circuit card (eUICC) standard developed by the Global Mobile System Alliance (GSMA) for mobile communications (GSMA) standard remotely configures the eUICC through short message service (SMS) messages. User data. For example, the eUICC remotely activates user data that a user signs on a certain operator network from an application server, and then enables the user equipment configured with the eUICC to access the operator's communication network.

With the development of Internet of Things (IoT) technology, terminal equipment in the Internet of Things also urgently needs to apply the eUICC technology standard, so that IoT terminal equipment can access different operations without changing the subscriber identity module (SIM) card Business network.

Taking narrowband Internet of Things (NB-IoT) as an example, the bandwidth and transmission rate of NB-IoT networks are low to achieve wide coverage and low power consumption. Therefore, many existing transmission protocols are not suitable for NB-IoT. -Data transmission in the IoT network. For example, the Hypertext Transfer Protocol (HTTPS) message header has a large header and high bandwidth requirements. The HTTPS three-way handshake protocol has timer protection, and the NB-IoT network has a lower rate, which causes the timer to time out. Therefore, it is not suitable to establish a session between the application server and the eUICC through HTTPS under the NB-IoT network. Secondly, because the NB-IoT network needs to upgrade the short message service center (SMSC) or mobile switching center (MSC) in the existing network, it can send or receive short message services (short message (Service (SMS)) message, so SMS message function is not supported under NB-IoT network.

Therefore, how the application server (for example, the SM platform) sends an SMS message to the eUICC in the terminal device under the Internet of Things, thereby completing the remote configuration of user data on the eUICC has become an urgent problem to be solved.

Summary of the Invention

The present application provides a method and device for transmitting eUICC data in the Internet of Things. An application server (for example, an SM platform) in an IoT network can send SMS messages to the eUICC in a terminal device, thereby completing remote configuration of user data on the eUICC.

In a first aspect, a method for transmitting eUICC data in the Internet of Things is provided. The method includes: the Internet of Things IoT platform acquires the ability to send and receive SMS messages of a communication network; the IoT platform does not support the sending and receiving of SMS messages in the communication network In the case of a function, the SMS message to be sent to the terminal device is converted into a first LwM2M message; the IoT platform sends the first LwM2M message to the terminal device.

In the embodiment of the present application, the IoT platform can acquire the SMS message receiving and transmitting capabilities of the communication network, and can convert the SMS message to be sent to the terminal device into a first LwM2M message if the communication network does not support the sending and receiving function of the SMS message.

In the embodiment of the present application, there are various specific implementation manners for the IoT platform to obtain whether the communication network supports SMS, which is not specifically limited in this application. As an example, the IoT platform may acquire the sending and receiving capabilities of SMS messages of the communication network through a service capability open function (service capability exposure function (SCEF)). For example, the IoT platform may call an application programming interface (API), and obtain the sending and receiving capabilities of SMS messages of the communication network through SCEF.

It should be understood that SCEF may be a capability open function logical unit defined in 3GPP, and SCEF may securely open network element service capabilities provided by a network interface defined by 3GPP to a third-party service provider. SCEF can be deployed on the core network side or open to the outside as a part of the IoT platform's logical functions.

The SMS message in the embodiment of the present application may be an eUICC issued by the application server to the terminal device. In the embodiment of the present application, the application server and the IoT platform may be deployed separately, and the application server may also be integrated in the IoT platform. Be specific.

Optionally, in some embodiments, if the application server and the IoT platform can be deployed separately, the IoT platform may convert an SMS message to be sent to the terminal device into a first LwM2M message.

Optionally, in some embodiments, if the application server can also be integrated into the IoT platform, the IoT platform can receive the SMS message sent by the application server, and the IoT platform can convert the received SMS message into a first LwM2M message.

The embodiment of the present application does not specifically limit the SMS message to be sent to the terminal device. As an example, the SMS message may include activation information of a profile with which the eUICC is contracted by the target operator in the terminal device. As another example, the SMS message may include other configuration information delivered to the eUICC user in the form of an SMS message.

In the embodiment of the present application, the IoT platform (as the server sever) may encapsulate the received SMS message into a first LwM2M message, and may send the LwM2M message to the M2M communication device (LwM2M client client in the terminal device) under the LwM2M protocol. ). As an example, the IoT platform may encapsulate the received SMS message into an LwM2M application data object (app data container object), and may set the data format of the target data included in the LwM2M message to "SMS" , So that the SMS message sent by the SM platform can be converted to the first LwM2M message under the LwM2M protocol.

It should be understood that the LwM2M application data object may include the content of the target data delivered to the eUICC, the data format of the target data, and a description of the target data.

Specifically, the IoT platform may set the data format of the target data to SMS. After receiving the first LwM2M message, the M2M communication device in the terminal device may, according to the data format of the target data included in the first LwM2M message, be: The SMS may forward the SMS message in the first LwM2M message to the short message module in the terminal device. The short message module can forward the target data in the parsed SMS message to the eUICC in the terminal device. Under the IoT network, an application server (for example, the SM platform) can be implemented to send the SMS message to the eUICC in the terminal device. Remotely configure user data on the eUICC.

In the embodiment of the present application, in an IoT network, a session between an application server (for example, an SM platform) and an eUICC on a terminal device can be established through the LwM2M protocol, and an SMS message can be sent to the eUICC in the terminal device, so that Remotely configure user data on the eUICC.

With reference to the first aspect, in some implementations of the first aspect, the SMS message to be sent to the terminal device is from an application server, and the IoT platform converts the SMS message to be sent to the terminal device into a first LwM2M message Before, the method further includes: receiving, by the IoT platform, the SMS message sent by an application server.

With reference to the first aspect, in some implementation manners of the first aspect, the IoT platform acquires the sending and receiving capabilities of SMS messages of the communication network through a service capability open network element SCEF.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the IoT platform acquires the ability to send and receive SMS messages of a terminal device; and the IoT platform supports the sending and receiving of SMS messages on the terminal device Function, if the communication network does not support the sending and receiving function of the SMS message, the SMS message is converted into the first LwM2M message.

In the embodiment of the present application, there are various specific implementation manners for the IoT platform to obtain whether the terminal device supports SMS, which is not specifically limited in this application. As an example, when the IoT platform is directly connected to the SM platform, the IoT platform may send an LwM2M request message to the M2M communication device on the terminal device to query the SMS capability. As another example, when the IoT platform is connected to the SMSC, the IoT platform can subscribe to the SMSC and support SMS, but the network on which it is located does not support the list of SMS terminal devices. The SMSC can update the destination terminal devices that are subscribed by the IoT platform. SMS messages are forwarded to the IoT platform.

With reference to the first aspect, in some implementations of the first aspect, the IoT platform sends an LwM2M request message to the terminal device; the IoT platform receives a response message to the LwM2M request message sent by the terminal device .

It should be understood that the response message includes indication information of an SMS message sending and receiving capability of the terminal device. The IoT platform may determine the sending and receiving capabilities of the SMS message of the terminal device according to the indication information in the response message.

With reference to the first aspect, in some implementations of the first aspect, the IoT platform receives LwM2M registration information sent by a terminal device.

The IoT platform may receive LwM2M registration information sent by a terminal device, where the LwM2M registration information includes indication information of an SMS messaging capability of the terminal device. The IoT platform may determine the sending and receiving capabilities of the SMS message of the terminal device according to the instruction information.

With reference to the first aspect, in some implementations of the first aspect, the target data includes profile activation information delivered by the application server to a target operator of the eUICC in the terminal device, and the profile activation information is used And activate the profile of the target operator downloaded in the eUICC.

With reference to the first aspect, in some implementations of the first aspect, before the IoT IoT platform receives a short message service SMS message sent by an application server, the method further includes: the IoT platform receives the A request message, where the request message includes profile download data sent by the application server to the target operator of the eUICC; the IoT platform converts the request message into a second LwM2M message; the IoT platform sends Sending, by the terminal device, the second LwM2M message.

With reference to the first aspect, in some implementations of the first aspect, before the IoT platform sends the first LwM2M or the second LwM2M to the terminal device, the method further includes:

The IoT platform determines that the terminal device is capable of analyzing target data sent to the eUICC or the profile download data.

With reference to the first aspect, in some implementations of the first aspect, the IoT platform receives a third LwM2M message sent by the terminal device, the third LwM2M message includes an indication bit, and the indication bit is used to indicate the Whether the terminal device has the ability to analyze the target data sent to the eUICC or the profile download data;

The IoT platform determines that the terminal device is capable of analyzing the target data sent to the eUICC or the profile download data according to the indicated bit.

In a second aspect, a method for transmitting eUICC data in the Internet of Things is provided. The method includes:

The terminal device receives a first lightweight machine-to-machine LwM2M message sent by the Internet of Things IoT platform; the terminal device sends the target data to the eUICC according to a data format including target data in the first LwM2M message.

The first LwM2M message includes target data sent by the application server to the embedded universal integrated circuit card eUICC in the terminal device, and the data format of the target data of the eUICC included in the first LwM2M message is short. Message service SMS.

With reference to the second aspect, in some implementations of the second aspect, the method further includes: the terminal device receiving a second LwM2M message sent by the IoT IoT platform, where the second LwM2M message includes the application The server sends a profile download profile to a target operator of the eUICC; the terminal device sends the second LwM2M message to the eUICC.

With reference to the second aspect, in some implementations of the second aspect, the terminal device has one or more of the following capabilities: the ability to send and receive SMS messages, the ability to parse target data sent to the eUICC, and analysis Ability to download data to the profile sent to the eUICC.

In a third aspect, an IoT platform is provided. The IoT platform includes:

A first obtaining module, configured to obtain a sending and receiving capability of an SMS message of a communication network, and the IoT platform communicates with a terminal device through the communication network;

A first processing module, configured to convert an SMS message to be sent to the terminal device into a first lightweight machine-to-machine LwM2M message when the communication network does not support the sending and receiving function of the SMS message, and the SMS message includes Send the target data to the embedded universal integrated circuit card eUICC in the terminal device, and the data format of the target data included in the first LwM2M message is SMS;

A first sending module, configured to send the first LwM2M message to a terminal device.

With reference to the third aspect, in some implementations of the third aspect, the SMS message to be sent to the terminal device is from an application server, and the IoT platform converts the SMS message to be sent to the terminal device into a first lightweight Before the machine-to-machine LwM2M message, the IoT platform further includes:

The first receiving module is configured to receive the SMS message sent by an application server.

With reference to the third aspect, in some implementation manners of the third aspect, the first obtaining module is specifically configured to:

The service capability open network element SCEF obtains the sending and receiving capability of the SMS message of the communication network.

With reference to the third aspect, in some implementations of the third aspect, the IoT platform further includes:

A second acquisition module, configured to acquire a sending and receiving capability of an SMS message of the terminal device;

A second processing module is configured to convert the SMS message into the first LwM2M message when the terminal device supports the sending and receiving function of the SMS message, and the communication network does not support the sending and receiving function of the SMS message.

With reference to the third aspect, in some implementation manners of the third aspect, the second obtaining module is specifically configured to:

Sending a LwM2M request message to all terminal devices, where the LwM2M request message is used to request to obtain the sending and receiving capabilities of the SMS messages of the terminal device;

Receiving a response message to the LwM2M request message sent by the terminal device, where the response message includes indication information about an SMS messaging capability of the terminal device.

With reference to the third aspect, in some implementation manners of the third aspect, the second obtaining module is further specifically configured to:

Receiving LwM2M registration information sent by the terminal device, where the LwM2M registration information includes indication information of a sending and receiving capability of the SMS message of the terminal device;

Determine the sending and receiving capability of the SMS message of the terminal device according to the indication information in the LwM2M registration information.

With reference to the third aspect, in some implementations of the third aspect, the target data includes profile activation information delivered by the application server to a target operator of the eUICC in the terminal device, and the profile activation information is used And activate the profile of the target operator downloaded in the eUICC.

With reference to the third aspect, in some implementations of the third aspect, before the IoT platform sends the first LwM2M or the second LwM2M to the terminal device, the IoT platform further includes:

A third obtaining module, configured to receive a request message sent by the application server, where the request message includes download data of a profile of a target operator delivered by the application server to the eUICC;

A third processing module, configured to convert the request message into a second LwM2M message;

A second sending module, configured to send the second LwM2M message to the terminal device.

With reference to the third aspect, in some implementations of the third aspect, the IoT platform further includes:

A determining module, configured to determine that the terminal device has a capability of analyzing the target data sent to the eUICC or the profile download data.

With reference to the third aspect, in some implementation manners of the third aspect, the determining module is specifically configured to:

Receive a third LwM2M message sent by the terminal device, the third LwM2M message includes an indication bit, and the indication bit is used to indicate that the terminal device is capable of analyzing the target data sent to the eUICC or the profile download data Ability;

According to the indicated bit, it is determined that the terminal device is capable of analyzing target data sent to the eUICC or the profile download data.

According to a fourth aspect, a terminal device is provided, where the terminal device includes:

The first receiving module is configured to receive a first lightweight machine-to-machine LwM2M message sent by the IoT IoT platform, where the first LwM2M message includes a target issued by an application server to the embedded universal integrated circuit card eUICC in the terminal device Data, the data format of the target data of the eUICC included in the first LwM2M message is short message service SMS;

A first sending module, configured to send the target data to a short message module according to a data format of the target data in the first LwM2M message, and the terminal device includes the short message module;

A second sending module is used for the short message module to send the target data to the eUICC.

With reference to the fourth aspect, in some implementations of the fourth aspect, the terminal device has one or more of the following capabilities: the ability to send and receive SMS messages, the ability to parse target data sent to the eUICC, and analysis Ability to download data to the profile sent to the eUICC.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the terminal device further includes:

A second receiving module, configured to receive a second LwM2M message sent by the IoT IoT platform, where the second LwM2M message includes profile download data sent by the application server to a target operator of the eUICC;

A third sending module, configured to send the second LwM2M message to the eUICC.

In a fifth aspect, an IoT IoT platform is provided, including: a receiver, a transmitter, a memory, and a processor.

The memory is configured to store a program; the processor is configured to execute a program stored in the memory, wherein the processor may be communicatively connected with a transceiver. The memory may be used to store program code and data of the terminal device. Therefore, the memory may be a storage unit inside the processor, or an external storage unit independent of the processor, or a component including a storage unit inside the processor and an external storage unit independent of the processor.

Optionally, the processor may be a general-purpose processor, and may be implemented by hardware or software. When implemented by hardware, the processor may be a logic circuit, integrated circuit, etc .; when implemented by software, the processor may be a general-purpose processor, realized by reading software codes stored in a memory, and the memory may be Integrated in the processor, it can be located outside the processor and stand alone.

When the program is executed, the processor is configured to: obtain a sending and receiving capability of an SMS message of a communication network, and the IoT platform communicates with a terminal device through the communication network;

The processor is further configured to convert the SMS message to be sent to the terminal device into a first lightweight machine-to-machine LwM2M message if the communication network does not support the sending and receiving function of the SMS message. The SMS message includes target data sent to the embedded universal integrated circuit card eUICC in the terminal device, and the data format of the target data included in the first LwM2M message is SMS;

The transmitter is configured to send the first LwM2M message to a terminal device.

With reference to the fifth aspect, in some implementations of the fifth aspect, the SMS message to be sent to the terminal device is from an application server, and the IoT platform converts the SMS message to be sent to the terminal device into a first lightweight Before the machine-to-machine LwM2M message, the receiver is configured to receive the SMS message sent by an application server.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the processor is specifically configured to: acquire, through a service capability open network element SCEF, the sending and receiving capability of the SMS message of the communication network.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the IoT platform further includes:

The processor is further configured to: obtain a sending and receiving capability of an SMS message of the terminal device;

The processor is further configured to convert the SMS message into the first LwM2M message when the terminal device supports the sending and receiving function of the SMS message and the communication network does not support the sending and receiving function of the SMS message.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the processor is specifically configured to send an LwM2M request message to the terminal device, where the LwM2M request message is used to request to obtain an SMS message of the terminal device. Transmit and receive capability

The receiver is specifically configured to receive a response message to the LwM2M request message sent by the terminal device, where the response message includes indication information about an SMS messaging capability of the terminal device.

With reference to the fifth aspect, in some implementations of the fifth aspect, the processor is specifically executed by the receiver: receiving LwM2M registration information sent by the terminal device, where the LwM2M registration information includes the terminal device's Indication information of the sending and receiving capabilities of the SMS message;

The processor is specifically configured to determine the sending and receiving capability of the SMS message of the terminal device according to the indication information in the LwM2M registration information.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the target data includes profile activation information delivered by the application server to a target operator of the eUICC in the terminal device, and the profile activation information is used And activate the profile of the target operator downloaded in the eUICC.

With reference to the fifth aspect, in some implementations of the fifth aspect, before the IoT platform sends the first LwM2M or the second LwM2M to the terminal device, the processor in the IoT platform further passes the The receiver executes: receiving a request message sent by the application server, where the request message includes the profile download data sent by the application server to the target operator of the eUICC;

The processor is specifically configured to: convert the request message into a second LwM2M message;

The sender is specifically configured to send the second LwM2M message to the terminal device.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the processor in the IoT platform is further configured to determine that the terminal device is capable of analyzing the target data sent to the eUICC or the profile download data. ability.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the processor is specifically executed by the receiver: receiving a third LwM2M message sent by the terminal device, where the third LwM2M message includes an indication bit, so The indication bit is used to indicate that the terminal device is capable of analyzing the target data sent to the eUICC or the profile download data;

The processor is specifically configured to determine, according to the indicated bit, that the terminal device is capable of analyzing the target data sent to the eUICC or the profile download data.

According to a sixth aspect, a terminal device is provided. The terminal device includes: a machine-to-machine M2M communication device, a transceiver, a short message module, an embedded universal integrated circuit card eUICC,

The M2M communication device performs the following operations through the transceiver: receiving a first lightweight machine-to-machine LwM2M message sent by the IoT IoT platform, and the first LwM2M message includes an application server sending an embedded message to the terminal device. The target data of the universal integrated circuit card eUICC, and the data format of the target data of the eUICC included in the first LwM2M message is short message service SMS;

The M2M communication device is configured to send the target data to a short message module according to a data format of the target data included in the first LwM2M message;

The short message module is configured to send the target data to the eUICC.

With reference to the sixth aspect, in some implementations of the sixth aspect, the M2M communication device further performs the following operations through the transceiver: receiving a second LwM2M message sent by the IoT platform, where the second LwM2M message includes Downloading data by the application server to a profile of a target operator of the eUICC;

The M2M communication device is configured to send the second LwM2M message to the eUICC.

With reference to the sixth aspect, in some implementations of the sixth aspect, the terminal device has one or more of the following capabilities: the ability to send and receive SMS messages, the ability to parse target data sent to the eUICC, and analysis Ability to download data to the profile sent to the eUICC.

According to a seventh aspect, there is provided a computer-readable medium for storing a computer program, the computer program including instructions for performing the foregoing first aspect or a method in any possible implementation manner of the first aspect.

According to an eighth aspect, there is provided a computer-readable medium for storing a computer program, the computer program including instructions for performing the foregoing second aspect or the method in any possible implementation manner of the second aspect.

According to a ninth aspect, a computer program product is provided. The computer program product includes computer program code. When the computer program code is executed by a computer, the computer is caused to execute the first aspect or any possible implementation manner of the first aspect. Methods.

According to a tenth aspect, a computer program product is provided. The computer program product includes computer program code. When the computer program code is executed by a computer, the computer is caused to execute the second aspect or any possible implementation manner of the second aspect. Methods.

According to an eleventh aspect, a communication chip is provided, in which instructions are stored, which when executed on a device for wireless communication, causes the communication chip to execute the method of the first aspect or any possible implementation manner of the first aspect. .

According to a twelfth aspect, a communication chip is provided, in which instructions are stored, which when executed on a wireless communication device, causes the communication chip to execute the method in the second aspect or any possible implementation manner of the second aspect. .

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram of a possible architecture for implementing eUICC remote configuration and management.

FIG. 2 is a schematic block diagram of a possible LwM2M protocol stack.

FIG. 3 is a schematic block diagram of establishing a session between an SM platform and an eUICC based on the LwM2M protocol according to an embodiment of the present application.

FIG. 4 is a schematic block diagram of a possible terminal device.

FIG. 5 is a schematic block diagram of a modem.

FIG. 6 is a schematic flowchart of a method for transmitting eUICC data in the Internet of Things according to an embodiment of the present application.

FIG. 7 is a schematic flowchart of acquiring an SMS support capability according to an embodiment of the present application.

FIG. 8 is a schematic flowchart of acquiring an SMS support capability according to an embodiment of the present application.

FIG. 9 is a schematic flowchart of a method for transmitting eUICC data in the Internet of Things according to an embodiment of the present application.

FIG. 10 is a schematic flowchart of a method for transmitting eUICC data in the Internet of Things according to another embodiment of the present application.

FIG. 11 is a schematic diagram of the number of messages between the eUICC and the application server before using the method for transmitting data of the present application.

FIG. 12 is a schematic diagram of the number of messages between the eUICC and the application server after using the data transmission method of the present application.

FIG. 13 is a schematic block diagram of an IoT platform 1300 provided by an embodiment of the present application.

FIG. 14 is a schematic block diagram of a terminal device 1400 according to an embodiment of the present application.

FIG. 15 is a schematic block diagram of an IoT platform 1500 provided by an embodiment of the present application.

detailed description

The technical solutions in this application will be described below with reference to the drawings.

It should be understood that the technical solutions in the embodiments of the present application can be applied to various communication systems, for example: a cellular-based Internet of Things (IoT) system, a narrowband Internet of Things (NB-IoT) system, Global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (general packet wireless service) packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile communication system (universal Mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, future 5th generation (5G) systems, or new wireless (NR).

The embodiment of the present application does not specifically limit the type of the terminal device, and may be, for example, a user equipment, an access terminal, a terminal device, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, and a user terminal. , Wireless network equipment, user agent, or user device. Terminals may include, but are not limited to, mobile stations (MS), mobile phones (user phones), user equipment (UE), handsets, portable equipment (portable equipment), cellular phones, cordless phones, conversations Initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital processing (PDA), radio frequency identification (RFID) terminal equipment for logistics, Wireless communication-capable handheld devices, computing devices, or other devices connected to wireless modems, in-vehicle devices, wearable devices, the Internet of Things, terminal devices in the vehicle network, and terminal devices in the future 5G network or future evolved public land mobile Terminal equipment in a public (PLMN) network.

By way of example and not limitation, in this embodiment of the present invention, the terminal device may also be a wearable device. Wearable devices can also be referred to as wearable smart devices. They are the general name for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a device that is worn directly on the body or is integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also powerful functions through software support, data interaction, and cloud interaction. Broad-spectrum wearable smart devices include full-featured, large-sized, full or partial functions that do not rely on smart phones, such as smart watches or smart glasses, and only focus on certain types of application functions, and need to cooperate with other devices such as smart phones Use, such as smart bracelets, smart jewelry, etc. for physical signs monitoring.

As another example, in this embodiment of the present invention, the terminal device may be various carriers moving at high speed, for example, shared bicycles, shared cars, and the like. The terminal device can also be various smart meters, such as water meters, electricity meters, gas meters, and so on. The terminal device may also be various monitoring devices or home appliances.

FIG. 1 is a schematic block diagram of an architecture for implementing remote configuration and management of eUICC.

The architecture for implementing eUICC remote configuration and management shown in FIG. 1 may include a subscription management (SM) platform 110 and eUICC 120. In the eUICC standard formulated by GSMA, the SM platform 110 can establish a session with the eUICC 120. The SM platform 110 can switch the profile loaded on the eUICC 120 based on the air interface (OTA), so that the eUICC 120 can be switched from the current mobile network operator (MNO) to the target MNO.

It should be understood that profile is a special term in the communication field, which can be understood as a user subscription data set or a collection of personal subscription service data used to sign on a certain operator network. It is a data collection of mobile user information, which can include users Identification information (such as user identity, authentication parameters, etc.) and service contract information.

The data contained in the profile may include, but is not limited to, a profile type, for example, a subscriber identity module (SIM) alliance profile package (SIM profile profile package), an international mobile subscriber identity (IMSI) code , Integrated circuit card identification (ICCID) code, secure digital (SD) memory card executable file loading assistance (aide, AID) program (executable load file AID for SD), SD memory card Executable module assistance (executable module AID for SD).

Specifically, after receiving the profile download request sent by the target MNO or the user, the SM platform 110 may send the generated profile to the eUICC 120 through an SMS message, and the SM platform 110 manages the profile in the eUICC 120. For example, the SM platform 110 may notify the eUICC 120 to activate the profile, so that the eUICC 120 is switched from the current MNO to the target MNO.

It should be understood that the SM platform 110 may be an application server.

The following describes the SM platform 110 and eUICC 120 respectively.

The SM platform 110 is the core of the eUICC remote management. The SM platform 110 can perform management operations such as downloading, installing, activating, deactivating, and deleting a profile according to a request initiated by an MNO or a user. The functions of the SM platform 110 mainly include two parts: subscription management data preparation (SM-DP), and subscription management security routing (SM-SR). Among them, SM-DP is mainly responsible for generating and storing profiles according to the data provided by the target MNO. SM-SR is mainly responsible for establishing the channel to eUICC 120, and can download the profile route generated by SM-DP to eUICC 120.

eUICC 120 can be an embedded UICC card, which can be connected to a terminal device such as a modem (which can be a circuit or a baseband chip). The eUICC 120 can communicate with other devices or equipment outside the terminal device through the modem. The eUICC 120 can provide users with the ability to implement MNO changes based on the air interface (OTA) without the need to replace the eUICC physical entity itself. eUICC 120 can provide security services similar to ordinary smart cards for mobile network access authentication and user identity authentication, and can be used to remotely manage multiple mobile network operations and personal management services.

The following describes several management operations of the profile.

Profile download: The SM platform can transmit the generated profile to the eUICC through the established transmission channel according to the MNO or user request.

Profile installation: eUICC can install the downloaded profile as an executable application and file system. Profile installation can be performed simultaneously with profile download. Successfully installed profiles can enter the deactivated state.

Profile activation: According to the MNO or user request, the SM platform can activate the profile that is currently in the deactivated state on the eUICC, so that files and applications in the profile can be selected through the interface between the terminal device and the eUICC.

Profile deactivation: According to the MNO or user request, the SM platform can deactivate the currently active profile on the eUICC, so that files and applications in the profile cannot be selected through the interface between the terminal device and the eUICC.

Referring to FIG. 2, in an architecture for implementing remote configuration and management of the eUICC, a session is established between the SM platform 110 and the eUICC 120 through a hypertext transfer protocol (HTTPS) message. After receiving the profile download request sent by the target MNO or the user, the SM platform 110 may send the generated profile to the eUICC 120 through an SMS message.

With the development of IoT network technology, terminal equipment in the Internet of Things also urgently needs to apply the eUICC technology standard, so that the Internet of Things terminal equipment can access the networks of different operators without replacing the SIM card. However, the terminal equipment of the IoT network may have the following two problems in applying the eUICC technology standard:

The following takes the narrowband IoT NB-IoT as an example for detailed description.

On the one hand, the NB-IoT network is not suitable for establishing a session between the application server and the eUICC through the HTTPS protocol. As an example, in order to achieve wide coverage and low power consumption, the NB-IoT network has a low bandwidth and transmission rate, and the HTTPS message header is large and requires high bandwidth. Therefore, under the NB-IoT network, Not suitable for establishing a session between the application server and the eUICC through the HTTPS protocol. As another example, due to the timer protection in the HTTPS three-way handshake protocol, and the low speed of the NB-IoT network causes the timer to time out, it is not suitable to establish an application server and eUICC through the HTTPS protocol under the NB-IoT network. Conversation.

On the other hand, the NB-IoT network does not support the sending and receiving of SMS messages. In the existing NB-IoT standard, there are two ways for the NB-IoT network to obtain SMS messages. As an example, the terminal device can transmit SMS messages through the SGd interface. For example, the path for the SMS message to be transmitted by the SGd interface is: SMSC-mobility management entity (MME) -evolutionary NodeB, eNB, or eNodeB ) -UE. As another example, the terminal device may also transmit the SMS message through the SGs interface. For example, the path for transmitting the SMS message by the SGd interface is: SMSC-MSC-MME-eNodeB-UE.

Because the above two ways of obtaining SMS messages have requirements for the SMSC and / or MSC in the existing network, the SMSC and / or MSC in the existing network need to be upgraded or expanded. However, the operator's existing network integrates SMSCs and / or MSCs from multiple vendors, and cannot upgrade or expand the SMSCs and / or MSCs. Therefore, the sending and receiving of SMS messages is not supported under the NB-IoT network.

In view of the above-mentioned problems in applying the eUICC technology standard in the IoT network, on the one hand, in the embodiment of the present application, a session between the SM platform and the eUICC can be established through a light weight machine to machine (LwM2M) protocol. On the other hand, the embodiment of the present application can encapsulate the SMS message delivered by the SM platform into an LwM2M message, so that the SMS message can be transmitted in the IoT network.

The following describes in detail a session established between the SM platform and the eUICC through the LwM2M protocol in the embodiments of the present application.

The LwM2M protocol is an Internet of Things protocol defined by the Open Mobile Alliance (OMA).

The structure of LwM2M's protocol stack can be seen in Figure 2. Among them, the LwM2M protocol 210 belongs to an application layer protocol and is located on top of a Constrained Application Protocol (CoAP) 220. CoAP 220 can perform datagram transmission layer security (DTLS) 230 encryption processing. Finally, it can use user packet protocol (UDP) 240 or short message service (SMS). 250 or SMS255 transmission. The LwM2M protocol can package messages into objects (Objects, Obj) 260 and can be transmitted through the above protocol. Objects will be described later in detail, so I won't repeat them here.

It should be understood that the SMS 250 may be a short message service located on a device, and the SMS 255 may be a short message service located on a smart card.

The header of the LwM2M protocol is smaller than the header of HTTPS, and the LwM2M protocol can establish a connection between the IoT IoT platform (as a server) and the M2M communication device (as a client client) on the terminal device without requiring multiple handshake. Conversation. Therefore, in an IoT network, a session between an application server (for example, an SM platform) and an eUICC on a terminal device can be established through the LwM2M protocol, thereby implementing data transmission.

The following uses FIG. 3 as an example to describe in detail a session established between an application server (for example, an SM platform) and an eUICC on a terminal device through the LwM2M protocol.

FIG. 3 is a schematic block diagram of establishing a session between an SM platform and an eUICC based on the LwM2M protocol according to an embodiment of the present application.

FIG. 3 may include an SM platform 310, an IoT platform 320, a terminal device 330, an M2M communication device 340, and an eUICC 350.

The SM platform 310 may correspond to the SM platform 110 in FIG. 1. In the embodiment of the present application, the SM platform 310 may be an application server, the SM platform 310 may be deployed separately from the IoT platform 320, and the SM platform 310 may also be integrated with the IoT platform 320 However, this application does not specifically limit this.

The following uses the example where the SM platform 310 can be deployed separately from the IoT platform 320 as an example.

The SM platform 310 may send the profile download request sent by the MNO to the terminal device 330 through the IoT platform. The SM platform 310 can convert the profile download request sent by the MNO into an LwM2M message (for example, the profile download request can be packaged into LwM2M objects) and then sent to the IoT platform 320. It can also convert the profile download request sent by the MNO into other types of messages Send to IoT platform 320.

The IoT platform 320 can be used as a device management platform in the LwM2M protocol. The IoT platform 320 can send messages sent by the SM platform 310 to the terminal device 330 through the LwM2M protocol. When the SM platform 310 and the IoT platform 320 do not transmit messages through the LwM2M protocol, The IoT platform 320 needs to convert the message sent by the SM platform 310 into an LwM2M message and then send it to the terminal device 330. The IoT platform 320 receives the LwM2M message of the terminal device 330 before it can be forwarded to the SM platform 310. .

The terminal device 330 is configured with an M2M communication device 340 and an eUICC 350. The LwM2M message received by the terminal device 330 can be processed by the M2M communication device 340 on the terminal device 330. A schematic structural diagram of the terminal device 330 may be shown in FIG. 4.

The M2M communication device 340 may be a chip, or may be an integrated circuit or other device. The M2M communication device 340 may forward the received LwM2M message to the eUICC 350. A schematic structural diagram of the M2M communication device 340 may be shown in FIG. 5.

The eUICC 350 may correspond to the eUICC 120 in FIG. 1. The eUICC 350 and the M2M communication device 340 can perform communication and information exchange. Physically, the eUICC 350 can be a device that is independent of the M2M communication device 340, and the eUICC350 can also be a device bound to the M2M communication device 340 (for example, the eUICC350 is embedded in the M2M communication device by welding or other methods 340). The eUICC350 forwards the received LwM2M message to the eUICC350 through the transceiver on the M2M communication device 340.

FIG. 4 is a schematic block diagram of a possible terminal device. The terminal device 330 in FIG. 4 may include: an M2M communication device 420, a wireless transceiver 430, an eUICC 480, and a short message module 490.

Optionally, the terminal device 330 further includes an application processor (AP) 410, a user interface 440, a memory 450, a camera 460, and a voice input / output interface 470.

The AP 410 can be an ultra-large-scale integrated circuit that extends time-frequency functions and special interfaces on the basis of a low-power central processing unit (central processing unit, CPU). The AP 410 runs an operating system and application software.

The M2M communication device 420 may correspond to the M2M communication device 340 in FIG. 3. As an example, the M2M communication device 420 may be a modem modem. The modem modem may be referred to as a baseband chip, and its main function is to send and receive various data, such as implementing the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP). And other major functions in wireless communication standards. The modem can be equivalent to a communication protocol processor and can be responsible for data processing.

The M2M communication device 420 can be used as a separate chip, or it can be combined with other chips or circuits to form a system-level chip or integrated circuit. The chip or integrated circuit can be applied to all terminal devices that implement wireless communication functions.

The terminal device 330 may receive and transmit data through the wireless transceiver 430.

The short message module 490 may be used to process and parse SMS messages. The short message module may be a chip, or may be an integrated circuit or other device.

The memory 450 may be used to store one or more of computer program instructions, preset parameters, and data obtained by computer intermediate operations.

The M2M communication device 420 is used as the modem modem 420 to describe the internal logical structure of the modem 420.

FIG. 5 is a schematic block diagram of a modem modem according to an embodiment of the present application. The modem 420 shown in FIG. 5 may include a receiving data processor 510, a controller 520, and a transmitting data processor 530.

The data receiver 510 may receive data sent by the IoT platform through a physical layer (PHY) protocol, and may demodulate the received data through functions such as channel decoding, demodulation, equalization, and channel estimation.

The processor 520 may process data through a protocol layer, and the processor 520 may use a media access control (MAC) layer protocol, a radio link control (RLC) layer protocol, and a packet data convergence protocol (packet) Data protocol (PDCP), radio resource control (RRC) layer protocols process data.

The data transmitter 530 may modulate data after processing such as channel coding, modulation, and symbol generation, and may send data to a UICC connected to the modem 420 through a PHY layer protocol.

The modem 420 shown in FIG. 5 can also have built-in storage, called on-chip memory, for example, terminal device to computer multiplexer (TCM), static random access memory (static random access memory) , SRAM) and so on.

The modem 420 can also communicate with off-chip memory. The off-chip memory can include but is not limited to: read-only memory (ROM), random access memory (RAM), U disk, mobile hard disk, Optical discs, magnetic storage devices, etc.

In the method for transmitting eUICC data in the Internet of Things provided by the embodiments of the present application, under the Internet of Things, an application server (for example, an SM platform) sends an SMS message to the eUICC on the M2M communication device, thereby completing remote configuration of user data on the eUICC.

The following describes a method for transmitting eUICC data in the Internet of Things provided by the embodiments of the present application.

FIG. 6 is a schematic flowchart of a method for transmitting eUICC data in the Internet of Things according to an embodiment of the present application. The method in FIG. 6 may include steps 610-630. Steps 610-630 are described below respectively.

In step 610, the IoT platform acquires the sending and receiving capabilities of SMS messages of the communication network.

In the embodiment of the present application, the IoT platform can acquire the SMS message receiving and transmitting capabilities of the communication network, and can convert the SMS message to be sent to the terminal device into a first LwM2M message if the communication network does not support the sending and receiving function of the SMS message.

In the embodiment of the present application, there are various specific implementation manners for the IoT platform to obtain whether the communication network supports SMS, which is not specifically limited in this application. As an example, the IoT platform may acquire the sending and receiving capabilities of SMS messages of the communication network through a service capability open function (service capability exposure function (SCEF)). For example, the IoT platform can call an application programming interface (API), and obtain the sending and receiving capabilities of SMS messages of the communication network through SCEF.

It should be understood that SCEF may be a capability open function logical unit defined in 3GPP, and SCEF may securely open network element service capabilities provided by a network interface defined by 3GPP to a third-party service provider. SCEF can be deployed on the core network side or open to the outside as a part of the IoT platform's logical functions.

The SMS message in the embodiment of the present application may be an eUICC issued by the application server to the terminal device. In the embodiment of the present application, the application server and the IoT platform may be deployed separately, and the application server may also be integrated in the IoT platform. Be specific.

Optionally, in some embodiments, if the application server and the IoT platform can be deployed separately, the IoT platform may convert an SMS message to be sent to the terminal device into a first LwM2M message.

Optionally, in some embodiments, if the application server can also be integrated into the IoT platform, the IoT platform can receive the SMS message sent by the application server, and the IoT platform can convert the received SMS message into a first LwM2M message.

The embodiment of the present application does not specifically limit the target data included in the SMS message to be sent to the terminal device. As an example, the target data may include activation data delivered by an application server (for example, an SM platform) to a profile contracted by an eUICC user with a target operator. As another example, the target data may further include other configuration data delivered by the application server (for example, the SM platform) to the eUICC user in the form of an SMS message.

In step 620, if the communication network does not support the sending and receiving function of the SMS message, the IoT platform converts the SMS message to be sent to the terminal device into a first LwM2M message.

In the embodiment of the present application, when the communication network does not support the sending and receiving function of the SMS message, the IoT platform (LwM2M server) can encapsulate the received SMS message into an LwM2M message, and can send the first LwM2M message under the LwM2M protocol To the M2M communication device (LwM2M client) in the terminal device. As an example, the content of the SMS message that the IoT platform can receive is packaged into an LwM2M application data object (app data container object), and the data format of the target data included in the first LwM2M message can be set to "SMS", so that the SMS message sent by the SM platform can be converted to the first LwM2M message under the LwM2M protocol.

It should be understood that in the LwM2M protocol, for each LwM2M entity (for example, each device supporting the LwM2M protocol), the accessible service is abstracted into one object, and each object office can have three levels. As an example, an object may include several objects that provide different functions, for example, several different sensors. As another example, each of the above functions may be provided by multiple object-instances, for example, a temperature reading function is provided for each temperature sensor. As another example, the functions that the above-mentioned object instance can actually accomplish may be referred to as a resource.

In the LwM2M protocol, the format of a universal resource identifier (URI) can be as follows: </ object ID / object-instance ID / resource ID>. For example, commonly used URI formats can be </ 1/0>, </ 1/1>, </ 2/0>, </ 2/1>, </ 2/2>, </ 2/3>, </ 2/4>, </ 3/0>, </ 4/0>, </ 5/0>, </ 19/0>, </ 19/1>.

The M2M communication device in the terminal device may send the first LwM2M message to the eUICC in the terminal device according to the data format of the target data included in the first LwM2M message. As an example, the M2M communication device in the terminal device may send the content of the SMS message in the LwM2M message to the corresponding short message module according to the target data data format included in the first LwM2M message. The short message The module can forward the SMS message to the eUICC in the terminal device.

The M2M communication device in the embodiment of the present application may be a communication module in a terminal device, and the M2M communication device may be a chip, an integrated circuit, or another device. The M2M communication device can be applied to all devices that implement wireless communication functions. As an example, the M2M communication device may be a modem modem. For a detailed description of the modem, refer to FIG. 5, which is not repeated here.

The short message module in the embodiment of the present application is a module in a terminal device, and the short message module may be used to process an SMS message. The short message module may be a chip, or may be an integrated circuit or other device.

In step 630, the IoT platform sends a first LwM2M message to the terminal device.

The terminal device may include an eUICC and an M2M communication device. The IoT platform may send the first LwM2M message to the M2M communication device in the terminal device. The M2M communication device may send the target data in the first LwM2M message to the terminal device. eUICC.

For a specific description of the terminal device, reference may be made to the description of the terminal device 330 in FIG. 4, and details are not described herein again. In the embodiment of the present application, the message header of the LwM2M protocol is smaller than that of HTTPS, and the LwM2M protocol can establish an IoT IoT platform (as a server sever) and an M2M communication device on the terminal device (as Client). In addition, the IoT platform (as the server sever) can convert the SMS message into a first LwM2M message, and can set the data format of the first LwM2M message to "SMS". Therefore, in the IoT network, a session between the application server (for example, the SM platform) and the eUICC on the terminal device can be established through the LwM2M protocol, and an SMS message can be sent to the eUICC on the M2M communication device, thereby completing remote configuration on the eUICC. User data.

The following uses the activation information of the profile whose target data included in the first LwM2M message is the eUICC as an example for detailed description.

The IoT platform receives the activation information (SMS message) of the profile sent by the SM platform, and can convert the SMS message to the first LwM2M message under the LwM2M protocol. For example, this application may package an SMS message sent by the SM platform into an LwM2M application data object (app data container object), and may implement the conversion of the request message sent by the SM platform into the first LwM2M message under the LwM2M protocol. The specific implementation of the IoT platform converting the activation information of the profile sent by the SM platform into the first LwM2M message under the LwM2M protocol will be described in detail below with reference to FIG. 9 and will not be repeated here.

Optionally, in some embodiments, before the IoT platform receives the activation information (SMS message) of the profile sent by the application server (for example, the SM platform), the IoT platform may also receive the profile sent by the application server (for example, the SM platform). Download information. The IoT platform can convert the profile download information into a second LwM2M message under the LwM2M protocol, and can send the LwM2M message to the eUICC. The specific implementation of the IoT platform converting the profile download information sent by the SM platform into a second LwM2M message under the LwM2M protocol will be described in detail below with reference to FIG. 10, and will not be repeated here.

It should be understood that, in the embodiment of the present application, the IoT platform needs to convert the activation information (SMS message) and / or profile download information of the profile received by the application server into an LwM2M message under the LwM2M protocol. Therefore, the data format in the LwM2M application data (LwM2M app data) needs to be extended, as shown in Table 1.

Table 1 LwM2M application data extension

Referring to Table 1, the embodiment of the present application can extend the LwM2M data format in the LwM2M application data container (app data container), and the object ID of the app data container is 19. LwM2M app data container can include data, data security (data), data description (data description), data format (data format), application ID (app ID) and other items.

The embodiments of the present application can extend the data format of the app data container. The extended data format can also include: short message service SMS, request to create ISD-P (create ISD-P, Req), response to create ISD-P ( create ISD-P Rsp), request to create ISD-P key (establish ISD-P key set Req), response to create ISD-P key (establish ISD-P key set Rsp), request to send data (send data Req), response to send data (send data Rsp).

It should be understood that the created ISD-P can be used to store the profile. The state of the created ISD-P may be an activated state (operator enabled profile), or a deactivated state (operator disabled profile).

In the embodiment of the present application, the LwM2M device capability management (LwM2M device capability management) object can be extended, as shown in Table 2.

Table 2 LwM2M device capability management object extension (LwM2M device capability management)

Referring to Table 2, the embodiment of the present application can extend the LwM2M device capability management object. The connectivity in the LwM2M device function group can increase the sending and receiving capabilities of the SMS messages of the terminal device, and the terminal device can analyze the target data sent to the eUICC or profile download capability.

It should be understood that after the expansion, the LwM2M message can be used to indicate whether the terminal device has the capability of receiving and sending SMS messages, and the ability to parse the target data sent to the eUICC or the profile to download data.

In the embodiment of the present application, the IoT platform may determine whether the terminal device has the ability to parse the activation data of the eUICC profile or download data of the profile by using the indication bit in the LwM2M message sent by the terminal device.

Optionally, in the embodiment of the present application, before the IoT platform converts the activation information (SMS message) of the profile sent by the SM platform to the first LwM2M message under the LwM2M protocol, the IoT platform obtains whether the terminal device and / or the communication network has The ability to send and receive SMS messages. The IoT platform can convert the activation information (SMS message) of the profile sent by the SM platform to the first LwM2M message under the LwM2M protocol when the terminal device has the ability to send and receive SMS messages and the communication network does not have the ability to send and receive SMS messages. Send to M2M communication device in terminal equipment.

In the embodiment of the present application, there are various specific implementation manners for the IoT platform to obtain whether the terminal device has the capability of receiving and sending SMS messages, and this application does not specifically limit this. As an example, when the IoT platform is directly connected to the SM platform, the IoT platform may send a request message to the terminal device to obtain the sending and receiving capabilities of the SMS message of the terminal device. The IoT platform may The included instruction information determines the SMS messaging capability of the terminal device. As another example, when the IoT platform is connected to the SMSC, the IoT platform may subscribe to the SMSC for a list of terminal devices that have the ability to send and receive SMS messages, but whose communication network does not have the ability to send and receive SMS messages. The following two specific implementation manners are described in detail below with reference to FIG. 7 to FIG. 8, which are not repeated here.

The following describes a specific implementation manner in which the IoT platform obtains whether the terminal device and / or the communication network has the capability of receiving and sending SMS messages in the embodiments of the present application in more detail with reference to specific examples. It should be noted that the example of FIG. 7 is only for helping those skilled in the art to understand the embodiments of the present application, and is not intended to limit the embodiments of the application to the specific values or specific scenarios shown. Those skilled in the art can obviously make various equivalent modifications or changes according to the example of FIG. 7 given in the text, and such modifications and changes also fall within the scope of the embodiments of the present application.

FIG. 7 is a schematic flowchart of acquiring a terminal device and / or a communication network having an SMS message sending and receiving capability according to an embodiment of the present application. The method in FIG. 7 may include steps 710-790. Steps 710-790 are described in detail below.

It should be understood that the SM platform can be deployed separately from the IoT platform as an example for detailed description in FIG. 7.

In step 710, the SM platform sends an SMS message to the IoT platform.

In the embodiment of the present application, the SMS message sent by the SM platform to the IoT platform may be used to activate the profile loaded on the eUICC in the terminal device.

In the embodiment of the present application, the SM platform may send an SMS message to the IoT platform (LwM2M server) through an API interface.

In step 720, the IoT platform obtains information about the communication network of the destination terminal device according to the destination terminal device of the SMS message.

In the embodiment of the present application, after receiving the SMS message sent by the SM platform, the IoT platform can obtain whether the destination terminal device has the ability to send and receive SMS messages, and can also obtain whether the communication network has the ability to send and receive SMS messages.

The IoT platform can convert the SMS message sent by the SM platform into an LwM2M message and send it to the terminal device when the destination terminal device has the ability to send and receive SMS messages and the communication network does not have the ability to send and receive SMS messages.

For the specific implementation of whether the IoT platform obtains the destination terminal device's ability to send and receive SMS messages, see the description in steps 730-740.

In step 730, the IoT platform sends a LwM2M request message to the destination terminal device.

The IoT platform may send an LwM2M request message to a target terminal device, and may be used to request to obtain the sending and receiving capability of the SMS message of the terminal device.

In step 740, the destination terminal device returns an SMS capability query result.

After receiving the request message sent by the IoT platform, the destination terminal device may send a response message to the IoT platform, where the response message includes the indication information of the SMS messaging capability of the destination terminal device.

As an example, the indication information included in the response message may be used to indicate the connectivity property ID (property ID) in the device capability management (LwM2M device capability) object of the destination terminal device, and the property ID may be used to indicate SMS messaging capability of the destination terminal device. For example, the query result indicated by the indication information included in the response message is: 2.05content (2 0x04), as shown in FIG. 2. The indication information may indicate that the destination terminal device has an SMS message sending and receiving capability.

For a specific implementation manner of the IoT platform obtaining whether the communication network has an SMS messaging capability, refer to the description in steps 750-790.

In step 750, the IoT platform sends a query request (SMS capability) of the communication network SMS messaging capability to the SCEF of MNO2.

If the device type of the destination terminal device is an IoT terminal device, the IoT platform can obtain the SMS messaging capability of the communication network through SCEF of the communication network.

For example, if the communication network of the IoT terminal device is MNO2, the IoT platform can call the API interface to obtain the SCEF of MNO2 whether MNO2 has the ability to send and receive SMS messages.

In step 760, the SCEF sends a query request (SMS capability request) for the SMS message sending and receiving capability of MNO2 to the MME.

The SCEF can send the query request to the MME after receiving the query request for the SMS message sending and receiving capability of the MNO2 sent by the IoT platform, so as to obtain whether the MNO2 has the SMS message sending and receiving capability.

In step 770, the MME returns the query result of the SMS messaging capability of MNO2 to the SCEF.

The MME can determine whether the MNO2 has the ability to send and receive SMS messages according to whether the MNO2 supports the SGd interface and / or the SGs interface. For specific information about the SGd interface and / or the SGs interface, refer to the foregoing description, which is not repeated here.

If the MME determines that the SGd interface and / or the SGs interface is not supported (SMSC and / or MSC is unavailable), it can be determined that MNO2 does not have the ability to send and receive SMS messages.

In step 780, the SCEF returns the query result of the SMS messaging capability of MNO2 to the IoT platform.

SCEF can send the query result to the IoT platform based on the results fed back by the MME.

In step 790, the IoT platform stores the query result of the SMS messaging capabilities of the MNO2 and the destination terminal device.

The IoT platform stores the query result of the SMS messaging capability of the destination terminal device returned in step 740 and the query result of the SMS messaging capability of MNO2 returned in step 780.

The following describes, in combination with specific examples, another specific implementation manner in which the IoT platform obtains whether a terminal device and / or a communication network has an SMS messaging capability in the embodiment of the present application in more detail. It should be noted that the example in FIG. 8 is only for helping those skilled in the art to understand the embodiments of the present application, and is not intended to limit the embodiments of the application to the specific values or specific scenarios shown. Those skilled in the art can obviously make various equivalent modifications or changes according to the example of FIG. 8 given in the text, and such modifications and changes also fall within the scope of the embodiments of the present application.

FIG. 8 is a schematic flowchart of another method for obtaining a terminal device and / or a communication network with an SMS message sending and receiving capability according to an embodiment of the present application. The method in FIG. 8 may include steps 810-870. Steps 810-870 are described in detail below.

In the system architecture shown in Figure 8, the SM platform is connected to the IoT platform through the SMSC.

It should be understood that the SM platform can be deployed separately from the IoT platform as an example for detailed description in FIG. 8.

Step 810: The terminal device registers with the IoT platform and reports the LwM2M device capability management object.

During the registration process of each terminal device with the IoT platform (as the LwM2M server sever), a device capability management (LwM2M device capability) object of each terminal device can be reported, such as an object </ 15/0>.

Step 820: The IoT platform acquires whether the terminal device has the capability of receiving and sending SMS messages, and has the ability to analyze the target data sent to the eUICC or the profile download data.

The IoT platform can receive a registration message for each terminal device, and the indication information included in the registration message can indicate whether each terminal device has the ability to send and receive MS messages, and analyze the target data sent to the eUICC or the profile download data. ability.

As an example, if the query result indicated by the indication information in the registration message of the terminal device received by the IoT platform is: 2.05content (2 0x04), referring to FIG. 2, the indication information may indicate that the terminal device has an SMS messaging capability.

As another example, if the query result indicated by the indication information in the registration message of the terminal device received by the IoT platform is: 2.05content (2 0x05), see FIG. 2, the instruction information may indicate that the terminal device has The eUICC's target data or the profile's ability to download data.

Step 830: The IoT platform acquires the SMS messaging capability of the communication network MNO2.

According to the result of step 820, the IoT platform can screen out terminal devices that have the ability to send and receive SMS messages and that have the ability to analyze the target data sent to the eUICC or the profile to download data.

The IoT platform can also obtain the SMS messaging capabilities of the communication network MNO2.

For example, if the communication network of the IoT terminal device is MNO2, the IoT platform can call the API interface to obtain the SCEF of MNO2 whether MNO2 has the ability to send and receive SMS messages.

Step 840: The IoT platform subscribes the SMS message of the terminal device in the terminal list to the SMSC.

The IoT platform can obtain the ability to send and receive SMS messages according to the query results in steps 820 and 830, and have the ability to analyze the target data sent to the eUICC or the profile to download data, but the communication network does not have the ability to send and receive SMS messages. List of terminal devices. The IoT platform can subscribe to the SMSC's SMS messages for the terminal devices in the list.

For example, the IoT platform may call an API interface to subscribe to SMSC's SMS messages from the terminal devices in the list.

Step 850: The SM platform sends a profile activation request message (SMS message) to the SMSC.

Step 860: The SMSC determines that the destination terminal device of the SMS message is subscribed and forwards the SMS message to the IoT platform.

The SMSC can determine whether the destination terminal device of the SMS message is subscribed after receiving the SMS message issued by the SM platform. If the destination terminal device of the SMS message is subscribed by the IoT platform, the SMSC may deliver the SMS message to the IoT platform.

Step 870: The SMSC sends a profile activation request message to the IoT platform.

The SMSC can forward the profile activation request message to the IoT platform by calling the API interface.

As mentioned above, the IoT platform can convert the profile activation request message (SMS message) sent by the SM platform into the first LwM2M message under the LwM2M protocol. It should be understood that the IoT platform can convert the profile activation request message (SMS message) into the first under the LwM2M protocol in a scenario where the terminal device has the ability to send and receive SMS messages and its communication network does not have the ability to send and receive SMS messages. LwM2M message, and may send the first LwM2M message to the terminal device.

In the following, a specific example is used to describe in detail the specific implementation of the IoT platform converting a profile activation request message (SMS message) into a first LwM2M message under the LwM2M protocol in the embodiment of the present application. It should be noted that the example in FIG. 9 is only for helping those skilled in the art to understand the embodiments of the present application, and is not intended to limit the embodiments of the application to the specific values or specific scenarios shown. Those skilled in the art can obviously make various equivalent modifications or changes according to the example shown in FIG. 9, and such modifications and changes also fall within the scope of the embodiments of the present application.

FIG. 9 is a schematic flowchart of a method for transmitting eUICC data in the Internet of Things according to an embodiment of the present application. The method of FIG. 9 may include steps 910-975. Steps 910-975 are described in detail below.

It should be understood that, in the method for transmitting eUICC data in the Internet of Things shown in FIG. 9, the IoT platform may determine in advance whether the terminal device and the communication network have the ability to send and receive SMS messages. The specific acquisition manner may refer to the method shown in FIG. 7 or the method shown in FIG. 8, which is not specifically limited in this embodiment of the present application.

It should also be understood that the SM platform can be deployed separately from the IoT platform as an example for detailed description in FIG. 9.

Refer to steps 910-945 for the process of downlink transmitting SMS messages (from the SM platform to the eUICC).

In step 910, the operator MNO1 sends a profile activation request to the SM platform.

It should be understood that the eUICC in the terminal device has loaded multiple profiles, among which, the current network operator MNO2 needs to be deactivated, and the switched operator MNO1 needs to be activated. For the specific steps of downloading the profile by the eUICC, please refer to the description in FIG. 10 below, which will not be repeated here.

The operator MNO1 after the handover can send a profile activation request to the SM platform in the form of an SMS message. The profile activation request can be used to request activation of the profile of the operator MNO1 on the eUICC, so that the user equipment of the eUICC can be configured to access the operation.商 MNO1's communication network.

Step 915: The SM platform sends a profile activation request to the IoT platform.

After receiving the profile activation request in the form of an SMS message, the SM platform can send the SMS message to. For example, the SM platform can call an API interface to send SMS messages to the IoT platform. IoT platform (as LwM2M)

Step 920: The IoT platform determines the destination terminal device of the SMS message and the sending and receiving capabilities of the SMS message of its communication network MNO2.

After receiving the profile activation request in the form of an SMS message sent by the SM platform, the IoT platform can determine the sending and receiving capabilities of the SMS message of the destination device of the SMS message and the sending and receiving capability of the SMS message of the communication network.

Step 925: If the destination terminal device and its communication network have the ability to send and receive SMS messages, the IoT platform converts the SMS messages into LwM2M messages.

If the destination terminal device of the SMS message is an IoT terminal (it can also be understood as an M2M communication device serving as a LwM2M client on the terminal device), the current communication network of the IoT terminal is the operator MNO2. The IoT platform can judge the sending and receiving capabilities of the SMS messages of the IoT terminal and the operator MNO2. If the IoT terminal has the ability to send and receive SMS messages, and the operator MNO2 does not have the ability to send and receive SMS messages, the IoT platform can convert the SMS messages into LwM2M messages. The IoT platform can call adapters to modify the parameters of SMS messages. For example, adapter can set the originator address of the SMS message to a specified value (for example, it can be 037E11), and adapter can set the SMS type of the SMS message to class2. (Can be used to indicate that the SMS message is sent to the eUICC).

After setting the parameters of the SMS message, the IoT platform can convert the SMS message into an LwM2M message under the LwM2M protocol.

For example, the IoT platform can organize the SMS message content into LwM2M messages according to LwM2M app, container, and object. You can refer to the description of LwM2M app and data container in Table 1. LwM2M app and data container can include data, data security, data description, data format, and application ID (app) ID). In the embodiment of the present application, the IoT platform can store the contents of the SMS message in data, the data format can be set to "SMS", and the data description can be set to "profile activation request", so that the SMS message can be converted into LwM2M under the LwM2M protocol Message.

Optionally, in some embodiments, the IoT platform may establish a mapping relationship between the LwM2M message and the SM platform, and may store the mapping relationship. When the IoT platform receives the uplink SMS message sent by the terminal device, it can return the uplink SMS message to the corresponding SM platform according to the mapping relationship.

Step 930: The IoT platform sends the LwM2M message to the destination terminal device (for example, an M2M communication device in the terminal device).

The IoT platform can send the LwM2M message converted from the SMS message to the destination terminal device.

Step 935: The M2M communication device in the destination terminal device performs special processing on the SMS message in Data according to the data format of the LwM2M message.

The M2M communication device in the destination terminal device can parse the received LwM2M message, and can forward the content of the SMS message in data to the destination terminal device according to the data format (data format) in the data object of the LwM2M app container. Short message module. The short message module can parse the SMS message, and can forward the SMS message to the eUICC in the terminal device according to the type of the short message in the SMS message being class2.

It should be understood that the short message module can parse the SMS message and can process the SMS message. For specific processing, see the description in step 940.

Step 940: The short message module on the M2M communication device in the destination terminal device forwards the SMS message data to the eUICC through the local interface.

The short message module can forward the SMS message data to the eUICC through the newly added local interface (local interfacea) of the eUICC in the destination terminal device.

It should be understood that the short message module may be a module in the destination terminal device.

In the embodiment of the present application, the eUICC may include a main security domain of the profile (ISD-P) and a main security domain of the route (ISD-R). The eUICC can download data through the ISD-R routing profile. The ISD-P can be used to store profile data. The ISD-P can have an identifier indicating the status of the profile in the current ISD-P (operator enabled or deactivated) (operator disabled profile)).

In the embodiment of the present application, a new local interfacea can be added to the ISD-R, and the eUICC can receive the profile data sent by the terminal device (for example, the eUICC can receive the profile data sent by the short message module through the local interfacea), thereby realizing the download and activation of the profile , Can simplify the protocol stack on the eUICC to support eUICC functions.

Optionally, in some embodiments, the M2M communication device may establish a mapping relationship between the LwM2M message and the IoT platform, and may store the mapping relationship. The M2M communication device may return the uplink SMS message to the corresponding IoT platform according to the mapping relationship when receiving the uplink SMS message sent by the eUICC.

Step 945: The eUICC completes profile switching according to the content of the SMS message.

The eUICC may activate the profile of the operator MNO1 on the ISD-P according to the SMS message sent by the short message module, and complete the access of the terminal device of the eUICC to the communication network of the operator MNO1 after the handover.

Refer to steps 950-975 for the process of uplink transmission of SMS messages (from eUICC to SM platform).

Step 950: The eUICC returns a successful SMS response message to the M2M communication device in the destination terminal device.

Step 955: The short message module in the destination terminal device converts the SMS message into an LwM2M response message.

After receiving the operation result returned by the eUICC, the short message module in the destination terminal device can call adapter to modify the parameters of the SMS message. As an example, the adapter can set the destination address of the SMS message according to the originator address of the SMS message. For example, if the originator address of the SMS message is a specified value (for example, 037E11), the adapter can set the destination address of the SMS message to a specified value (for example, 037E11), and the SMS message can be forwarded to the destination terminal device. M2M communication device.

As the LwM2M client, the M2M communication device in the destination terminal device can convert the received SMS messages into LwM2M response messages according to the LwM2M app data container object organization. Refer to the description of the LwM2M app and data container in Table 1. The M2M communication device in the destination terminal device can set the data format to "SMS" and store the content of the SMS message in data.

Step 960: The M2M communication device in the destination terminal device forwards the LwM2M response message to the IoT platform.

The M2M communication device in the destination terminal device may forward the LwM2M response message to the IoT platform according to the mapping relationship stored in step 930.

Step 965: The IoT platform forwards the LwM2M response message to the SM platform.

After receiving the LwM2M response message, the IoT platform can parse the LwM2M response message. The content of the SMS message stored in the LwM2M response message data can be forwarded to the SM platform according to the mapping relationship stored in step 920.

In step 970, the SM platform sends a profile activation response to the switched operator MNO1.

Step 975: The SM platform sends a profile deactivation notification to the operator MNO2.

Optionally, in some embodiments, before the IoT platform receives the activation information (SMS message) of the profile sent by the application server (for example, the SM platform), the IoT platform may also receive the profile sent by the application server (for example, the SM platform). Download the data.

In the embodiment of the present application, the application server (for example, the SM platform) can send an SMS message to the eUICC on the M2M communication device under the IoT network, thereby completing remotely configuring user data on the eUICC.

The specific implementation of the IoT platform converting the profile download data into the LwM2M message under the LwM2M protocol in the embodiments of the present application is described in more detail below with specific examples. It should be noted that the example of FIG. 10 is only for helping those skilled in the art to understand the embodiments of the present application, and is not intended to limit the embodiments of the application to the specific values or specific scenarios shown. Those skilled in the art can obviously make various equivalent modifications or changes according to the example of FIG. 10 given in the text, and such modifications and changes also fall within the scope of the embodiments of the present application.

FIG. 10 is a schematic flowchart of a method for transmitting eUICC data in the Internet of Things according to another embodiment of the present application. The method in FIG. 10 may include steps 1010-1070. Steps 1010-1070 are described in detail below.

It should be understood that during the process of downloading data in the profile shown in FIG. 10, the IoT platform may determine in advance whether the terminal device has the ability to analyze the target data sent to the eUICC or the profile download data. The specific determination manner may refer to the method shown in FIG. 7 or the method shown in FIG. 8, which is not specifically limited in this embodiment of the present application.

It should also be understood that the SM platform can be deployed separately from the IoT platform as an example for detailed description in FIG. 10.

The process of downloading the profile shown in FIG. 10 may include creating an ISD-P (create ISD-P), establishing a key (key establishment), and downloading a profile (profile download).

The process of creating an ISD is described in detail below in conjunction with steps 1010-1040.

In step 1010, the operator MNO1 sends a profile download request (profile download) to the SM platform.

In step 1015, the SM platform sends a create ISD-P request (create ISD-P request) to the IoT platform (as LwM2M server).

Step 1020: The IoT platform converts the ISD-P request message into an LwM2M message under the LwM2M protocol.

After receiving the ISD-P creation request sent by the SM platform, the IoT platform can determine whether the destination terminal device of the request message has the ability to parse the target data sent to the eUICC or the profile download data.

As an example, if the destination terminal device has the capability to parse the target data or the profile download data sent to the eUICC, and the network access type of the target terminal is IoT. The IoT platform can organize the creation of ISD-P request messages into LwM2M messages according to the LwM2M app data container object. You can refer to the description of LwM2M app data container in Table 1. The IoT platform can package the ISD-P request message into the data of LwM2M app app container data, and you can set the data format to "create ISD-P Req".

Step 1025: The IoT platform sends the LwM2M message to the M2M communication device (as the LwM2M client) in the destination terminal device.

Step 1030: The M2M communication device in the terminal device forwards the creation ISD-P request data in Data to the eUICC in the destination terminal device according to the data format of the LwM2M message.

The M2M communication device in the terminal device can parse the received LwM2M message, and according to the data in the LwM2M app data container object format is "create ISD-P Req", the data in the data of the LwM2M app data container object is passed through the local The interface is sent to the eUICC in the terminal device.

Step 1033: The M2M communication device in the terminal device sends the creation data of the ISD-P request to the eUICC.

In step 1035, the eUICC returns a create ISD-P response message (create ISD-P Rsp) to the M2M communication device in the terminal device.

Step 1038, the M2M communication device in the terminal device converts the create ISD-P response message (create ISD-P Rsp) into an LwM2M response message,

Step 1040: The M2M communication device in the terminal device sends the LwM2M response message to the IoT platform.

The M2M communication device in the terminal device can package the response message (create ISD-P Rsp) into the data of the LwM2M app container object, and the data format can be set to "create ISD-P Rsp".

The following describes the process of key establishment in detail in conjunction with steps 1045-1070.

Step 1045: The SM platform sends an ISD-P key creation request message (establish ISD-P key set Req) to the IoT platform (as LwM2M server).

Step 1050: The IoT platform converts the ISD-P key request message into an LwM2M message under the LwM2M protocol.

After receiving the ISD-P key creation request sent by the SM platform, the IoT platform can determine whether the destination terminal device of the request message has the ability to parse the target data sent to the eUICC or the profile download data.

As an example, if the destination terminal device has the capability to parse the target data sent to the eUICC or the profile download data, and the network access type of the target terminal is an IoT network. The IoT platform can transform the ISD-P key creation request into an LwM2M message according to the LwM2M app, data container, and object. You can refer to the description of the LwM2M app data container in Table 1. The IoT platform can package the ISD-P key creation request into the data of the LwM2M app app container data, and the data format can be set to "establish ISD-P key set Req". .

Step 1055: The IoT platform sends the LwM2M message to the M2M communication device (as the LwM2M client) in the destination terminal device.

Step 1060: The M2M communication device will forward the data of the ISD-P key request message in Data to the eUICC in the destination terminal device according to the data format of the LwM2M message.

The M2M communication device in the terminal device can parse the received LwM2M message, and according to the data format of the LwM2M app data container object is "establish ISD-P key set Req", the data in the data of the LwM2M app data container object The local interface is sent to the eUICC in the terminal device.

Step 1063: The M2M communication device in the terminal device sends to the eUICC the ISD-P key creation request data.

In step 1065, the M2M communication device in the terminal device receives an ISD-P key creation response message (establish ISD-P key set Rsp) returned by the eUICC.

Step 1068: The M2M communication device in the terminal device converts the response message (establish ISD-P key set Rsp) into an LwM2M response message.

Step 1070: The M2M communication device in the terminal device sends the LwM2M response message to the IoT platform.

The M2M communication device in the terminal device can package the response message (establish ISD-P key set Rsp) into the data of the LwM2M app container object, and the data format can be set to "establish ISD-P key set Rsp".

The following describes the process of profile download in detail with steps 1075-1099.

Step 1075: The SM platform forwards the send data request (data req) message to the IoT platform (as LwM2M server).

In step 1080, the IoT platform converts the send data request message into an LwM2M message under the LwM2M protocol.

After receiving the data transmission request message forwarded by the SM platform, the IoT platform can determine whether the destination terminal device of the request message has the ability to parse the target data sent to the eUICC or the profile download data.

As an example, if the destination terminal device has the capability to parse the target data sent to the eUICC or the profile download data, and the network access type of the target terminal is an IoT network. The IoT platform can convert the send data request message into LwM2M messages according to the LwM2M app, data container, and object organization. You can refer to the description of LwM2M app data container in Table 1. The IoT platform can package the send data request message into the data of LwM2M app data container object, and you can set the data format to "send data Req".

Step 1085, the IoT platform sends the LwM2M message to the M2M communication device (as the LwM2M client) in the destination terminal device.

Step 1090: The M2M communication device in the terminal device will forward the data in the data to the eUICC in the destination terminal device according to the data format of the LwM2M message.

Step 1093: The M2M communication device in the terminal device forwards the data to the eUICC in the destination terminal device.

The M2M communication device in the terminal device can parse the received LwM2M message, and according to the data format of the LwM2M app data container object is "send data Req", the M2M communication device passes the data in the data of the LwM2M app data container object The interface is sent to the eUICC in the terminal device.

Step 1095: The M2M communication device in the terminal device receives the eUICC and sends a data response message (send data Rsp).

Step 1098: The M2M communication device in the terminal device converts a response message (send data Rsp) into an LwM2M response message and sends it to the IoT platform.

The M2M communication device in the terminal device can package the response message (send data Rsp) into the data of the LwM2M app data container object, and the data format can be set to "send data Rsp".

Step 1099: The M2M communication device in the terminal device sends the LwM2M response message to the IoT platform.

In the embodiment of the present application, in the process of remotely configuring user data on the eUICC, interaction messages between the eUICC and the application server (for example, the SM platform) can be reduced, and network transmission efficiency can be improved.

Referring to the number of interaction messages in FIG. 11 to FIG. 12 below, this embodiment describes in detail how the embodiments of the present application reduce the interaction messages between the eUICC and the application server (for example, the SM platform), thereby improving the transmission efficiency of the network.

FIG. 11 is a schematic diagram of the number of messages between the eUICC and the application server before using the method for transmitting data of the present application. As shown in FIG. 11, in the process of remotely configuring user data on the eUICC, the number of interaction messages between the eUICC and the application server is 13 times. The interaction messages between eUICC and the application server are: 1 SMS request to establish a connection message, 3 handshake (transmission control protocol (TCP)) messages, 1 create ISD-P Req message, and 1 create ISD -P Rsp message, 1 establish ISD-P key set Req message, 1 establish ISD-P key set Rsp message, 1 send data Req message, 1 send data RSP message, 3 profile activation message (e.g., 1 One SMS enabled profile Rsp message, one SMS enabled profile Req message, one SMS handle default notification message).

FIG. 12 is a schematic diagram of the number of messages between the eUICC and the application server after using the data transmission method of the present application.

As shown in FIG. 12, during the process of remotely configuring user data on the eUICC, the number of interaction messages between the eUICC and the application server is 9 times. The interactive messages between eUICC and the application server are: 1 create ISD-P Req message, 1 create ISD-P Rsp message, 1 establish ISD-P key Req message, and 1 establish ISD-P key Rset Message, 1 send data, Req message, 1 send data, Rsp message, 3 profile activation messages (for example, 1 SMS enabled profile Rsp message, 1 SMS enabled profile Req message, 1 SMS handle default default notification message).

Therefore, during the process of remotely configuring user data on the eUICC (complete the profile download and activation process), before using the method for transmitting eUICC data in the Internet of Things provided by the embodiments of this application, the number of interaction messages between the eUICC and the application server is 13 times. After using the method for transmitting eUICC data in the Internet of Things provided by the embodiments of the present application, the number of interaction messages between the eUICC and the application server is 9 times. The transmission efficiency of the network can be improved by about 30%.

The method for sending data by the eUICC in the Internet of Things provided by the embodiment of the present invention is described in detail above with reference to FIG. 1 to FIG. 12. The device embodiment of the present application will be described in detail below with reference to FIGS. 13 to 15. It should be understood that the description of the method embodiment and the description of the device embodiment correspond to each other. Therefore, for the parts that are not described in detail, reference may be made to the foregoing method embodiment.

FIG. 13 shows a schematic block diagram of an IoT platform 1300 according to an embodiment of the present application. Each module in the IoT platform 1300 is used to perform each action or process performed by the IoT platform in the foregoing method. Here, in order to avoid redundant descriptions For detailed description, please refer to the description above.

FIG. 13 is a schematic block diagram of an IoT platform 1300 according to an embodiment of the present application. The IoT platform 1300 may include:

A first obtaining module 1310, configured to obtain a sending and receiving capability of an SMS message of a communication network, and the IoT platform communicates with a terminal device through the communication network;

A first processing module 1320, configured to convert an SMS message to be sent to the terminal device into a first lightweight machine-to-machine LwM2M message when the communication network does not support the sending and receiving function of the SMS message, and the SMS message Including target data sent to the embedded universal integrated circuit card eUICC in the terminal device, and a data format of the target data included in the first LwM2M message is SMS;

The first sending module 1330 is configured to send the first LwM2M message to a terminal device.

Optionally, in some embodiments, the SMS message to be sent to the terminal device is from an application server, and before the IoT platform converts the SMS message to be sent to the terminal device into a first lightweight machine-to-machine LwM2M message The IoT platform 1300 further includes:

The first receiving module 1340 is configured to receive the SMS message sent by an application server.

Optionally, in some embodiments, the first obtaining module 1310 is specifically configured to:

The service capability open network element SCEF obtains the sending and receiving capability of the SMS message of the communication network.

Optionally, in some embodiments, the IoT platform 1300 further includes:

A second obtaining module 1350, configured to obtain a sending and receiving capability of an SMS message of the terminal device;

A second processing module 1360 is configured to convert the SMS message into the first LwM2M message when the terminal device supports the sending and receiving function of the SMS message, and the communication network does not support the sending and receiving function of the SMS message.

Optionally, in some embodiments, the second obtaining module 1350 is specifically configured to:

Sending an LwM2M request message to all terminal devices, where the LwM2M request message is used to request to obtain the sending and receiving capabilities of the SMS messages of the terminal device;

Receiving a response message to the LwM2M request message sent by the terminal device, where the response message includes indication information about an SMS messaging capability of the terminal device.

Optionally, in some embodiments, the second obtaining module 1350 is further specifically configured to:

Receiving LwM2M registration information sent by the terminal device, where the LwM2M registration information includes indication information of a sending and receiving capability of the SMS message of the terminal device;

Determine the sending and receiving capability of the SMS message of the terminal device according to the indication information in the LwM2M registration information.

Optionally, in some embodiments, the target data includes profile activation information delivered by the application server to a target operator of the eUICC in the terminal device, and the profile activation information is used to activate the eUICC. Download the profile of the target operator.

Optionally, in some embodiments, before the IoT platform sends the first LwM2M or the second LwM2M to the terminal device, the IoT platform 1300 further includes:

A third obtaining module 1370, configured to receive a request message sent by the application server, where the request message includes the profile download data sent by the application server to the target operator of the eUICC;

A third processing module 1375, configured to convert the request message into a second LwM2M message;

The second sending module 1380 is configured to send the second LwM2M message to the terminal device.

Optionally, in some embodiments, the IoT platform 1300 further includes:

A determining module 1385 is configured to determine that the terminal device has a capability of analyzing target data sent to the eUICC or the profile download data.

Optionally, in some embodiments, the determining module 1385 is specifically configured to:

Receive a third LwM2M message sent by the terminal device, the third LwM2M message includes an indication bit, and the indication bit is used to indicate that the terminal device is capable of analyzing the target data sent to the eUICC or the profile download data Ability;

According to the indication bit, it is determined that the terminal device is capable of analyzing the target data sent to the eUICC or the profile download data.

In the IoT platform 1300 provided in the embodiment of the present application, the header of the LwM2M protocol is smaller than that of the HTTPS header, and the LwM2M protocol can establish an IoT IoT platform (as a server) and terminal devices without multiple handshake. Session between M2M communication devices (as client). Therefore, in the IoT network, the session between the application server (for example, the SM platform) and the eUICC on the terminal device can be established through the LwM2M protocol, and the data format of the LwM2M message can be set. The application server can send SMS messages in the IoT network To the eUICC on the M2M communication device to complete the remote configuration of the user data on the eUICC.

FIG. 14 shows a schematic block diagram of a terminal device according to an embodiment of the present application. Each module in the terminal device 1400 is used to perform each action or process performed by the terminal device in the foregoing method. Here, in order to avoid redundant description, detailed description is provided. You can refer to the description above.

FIG. 14 is a schematic block diagram of a terminal device 1400 according to an embodiment of the present application. The terminal device 1400 may include:

A first receiving module 1410 is configured to receive a first lightweight machine-to-machine LwM2M message sent by the Internet of Things IoT platform, where the first LwM2M message includes a message sent by an application server to an embedded universal integrated circuit card eUICC in the terminal device. Target data, the data format of the target data of the eUICC included in the first LwM2M message is short message service SMS;

A first sending module 1420, configured to send the target data to a short message module according to a data format of the target data in the first LwM2M message, and the terminal device includes the short message module;

The second sending module 1430 is configured to send the target data to the eUICC by the short message module.

Optionally, in some embodiments, the terminal device has one or more of the following capabilities: the ability to send and receive SMS messages, the ability to parse target data sent to the eUICC, and the profile download capability.

Optionally, in some embodiments, the terminal device 1400 further includes:

A second receiving module 1450, configured to receive a second LwM2M message sent by the IoT IoT platform, where the second LwM2M message includes download data of a profile of a target operator delivered by the application server to the eUICC;

A first processing module 1460, configured to send the second LwM2M message to the eUICC;

In the terminal device 1400 provided in the embodiment of the present application, since the message header of the LwM2M protocol is smaller than that of HTTPS, and the LwM2M protocol can establish an IoT IoT platform (as a server) and terminal devices on the terminal device without multiple handshake Session between M2M communication devices (as client). Therefore, in the IoT network, the session between the application server (for example, the SM platform) and the eUICC on the terminal device can be established through the LwM2M protocol, and the data format of the LwM2M message can be set. Under the IoT network, the application server can send SMS messages To the eUICC on the M2M communication device to complete the remote configuration of the user data on the eUICC.

FIG. 15 is a schematic block diagram of an IoT platform 1500 provided by an embodiment of the present application. The IoT platform 1500 may include a processor 1501, a receiver 1502, a transmitter 1503, and a memory 1504.

The processor 1501 may be communicatively connected with the receiver 1502 and the transmitter 1503. The memory 1504 may be used to store program code and data of the network device. Therefore, the memory 1504 may be a storage unit inside the processor 1501, or an external storage unit independent of the processor 1501, or may include a storage unit inside the processor 1501 and an external storage unit independent of the processor 1501. component.

Optionally, the IoT platform 1500 may further include a bus 1505. Among them, the receiver 1502, the transmitter 1503, and the memory 1504 can be connected to the processor 1501 through the bus 1505; the bus 1505 can be a peripheral component interconnect (PCI) bus or an extended industry standard structure (extended industry standard structure) architecture, EISA) bus, etc. The bus 1505 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 15, but it does not mean that there is only one bus or one type of bus.

The processor 1501 may be, for example, 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 (field programmable array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure. The processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.

The receiver 1502 and the transmitter 1503 may be circuits including the antenna and the transmitter chain and the receiver chain described above, and the two may be independent circuits or the same circuit.

When the program is executed, the processor 1501 is configured to: obtain a sending and receiving capability of an SMS message of a communication network, and the IoT platform communicates with a terminal device through the communication network;

The processor 1501 is further configured to convert the SMS message to be sent to the terminal device into a first lightweight machine-to-machine LwM2M message if the communication network does not support the sending and receiving function of the SMS message. The SMS message includes target data sent to the embedded universal integrated circuit card eUICC in the terminal device, and the data format of the target data included in the first LwM2M message is SMS;

The transmitter 1503 is configured to send the first LwM2M message to a terminal device.

Optionally, in some embodiments, the SMS message to be sent to the terminal device is from an application server, and before the IoT platform converts the SMS message to be sent to the terminal device into a first lightweight machine-to-machine LwM2M message The receiver 1502 is configured to receive the SMS message sent by an application server.

Optionally, in some embodiments, the processor 1501 is specifically configured to obtain the sending and receiving capabilities of the SMS message of the communication network through a service capability open network element SCEF.

Optionally, in some embodiments, the IoT platform 1500 further includes:

The processor 1501 is further configured to: obtain a sending and receiving capability of an SMS message of the terminal device;

The processor 1501 is further configured to convert the SMS message into the first LwM2M message when the terminal device supports the sending and receiving function of the SMS message and the communication network does not support the sending and receiving function of the SMS message.

Optionally, in some embodiments, the processor 1501 is specifically configured to: send an LwM2M request message to the terminal device, where the LwM2M request message is used to request to obtain the sending and receiving capability of the SMS message of the terminal device;

The receiver 1502 is specifically configured to receive a response message to the LwM2M request message sent by the terminal device, where the response message includes indication information about an SMS messaging capability of the terminal device.

Optionally, in some embodiments, the processor 1501 specifically executes through the receiver 1502: receiving LwM2M registration information sent by the terminal device, where the LwM2M registration information includes the SMS message of the terminal device Instruction information of transmitting and receiving capabilities;

The processor 1501 is specifically configured to determine the sending and receiving capability of the SMS message of the terminal device according to the indication information in the LwM2M registration information.

Optionally, in some embodiments, the target data includes profile activation information delivered by the application server to a target operator of the eUICC in the terminal device, and the profile activation information is used to activate the eUICC. Download the profile of the target operator.

Optionally, in some embodiments, before the IoT platform sends the first LwM2M or the second LwM2M to the terminal device, the processor 1501 in the IoT platform 1500 is further executed by the receiver 1502 Receiving a request message sent by the application server, where the request message includes profile download data sent by the application server to a target operator of the eUICC;

The processor 1501 is specifically configured to: convert the request message into a second LwM2M message;

The sender 1503 is specifically configured to send the second LwM2M message to the terminal device.

Optionally, in some embodiments, the processor 1501 in the IoT platform 1500 is further configured to determine that the terminal device is capable of analyzing target data sent to the eUICC or the profile download data.

Optionally, in some embodiments, the processor 1501 specifically executes through the receiver 1502: receiving a third LwM2M message sent by the terminal device, where the third LwM2M message includes an indicator bit, and the indicator bit is used for Instructing the terminal device to have the ability to parse the target data sent to the eUICC or the profile download data;

The processor 1501 is specifically configured to determine, according to the indicated bit, that the terminal device is capable of analyzing the target data sent to the eUICC or the profile download data.

An embodiment of the present application further provides a terminal device. For the terminal device, refer to a schematic structural diagram of a terminal device 330 shown in FIG. 4. The terminal device 330 may include: a machine-to-machine M2M communication device 420, a wireless transceiver 430, a short message module 490, and an embedded universal integrated circuit card eUICC480.

The M2M communication device 420 performs the following operations through the wireless transceiver 430: receiving a first lightweight machine-to-machine LwM2M message sent by an IoT IoT platform, and the first LwM2M message includes an application server sending the message to the The target data of the embedded universal integrated circuit card eUICC in the terminal device, and the data format of the target data of the eUICC included in the first LwM2M message is short message service SMS;

The M2M communication device 420 is configured to: send the target data to a short message module according to a data format of the target data included in the first LwM2M message;

The short message module 490 is configured to send the target data to the eUICC.

Optionally, in some embodiments, the M2M communication device 420 further performs the following operations through the wireless transceiver 430: receiving a second LwM2M message sent by the IoT platform, where the second LwM2M message includes the application Downloading data by the server to the profile of the target operator of the eUICC;

The M2M communication device 420 is configured to: send the second LwM2M message to the eUICC.

Optionally, in some embodiments, the terminal device 330 has one or more of the following capabilities: the ability to send and receive SMS messages, the ability to parse target data sent to the eUICC, and the eUICC Ability to download data from a profile.

An embodiment of the present application further provides a computer-readable medium for storing a computer program, where the computer program includes instructions for performing each action or processing procedure performed by the IoT platform in the foregoing method.

An embodiment of the present application further provides a computer-readable medium for storing a computer program, where the computer program includes instructions for performing each action or processing procedure performed by the terminal device in the foregoing method.

An embodiment of the present application further provides a computer program product. The computer program product includes: a computer program code that, when the computer program code is executed by a computer, causes the computer to perform various actions or processes performed by the IoT platform in the foregoing method. process.

The embodiment of the present application further provides a computer program product, the computer program product comprising: computer program code, when the computer program code is executed by a computer, causing the computer to perform various actions or processes performed by the terminal device in the foregoing method .

An embodiment of the present application further provides a chip system, which is applied to a communication device. The chip system includes at least one processor, at least one memory, and an interface circuit, and the interface circuit is responsible for information exchange between the chip system and the outside world. The at least one memory, the interface circuit, and the at least one processor are interconnected through a line, and the at least one memory stores instructions; the instructions are executed by the at least one processor to perform the oT platform in the foregoing method. Each action or process performed.

An embodiment of the present application further provides a chip system, which is applied to a communication device. The chip system includes at least one processor, at least one memory, and an interface circuit, and the interface circuit is responsible for information exchange between the chip system and the outside world. The at least one memory, the interface circuit, and the at least one processor are interconnected through a line, and the at least one memory stores instructions; the instructions are executed by the at least one processor to perform the terminal device in the foregoing method. Each action or process performed.

The terms “component”, “module”, “system” and the like used in this application are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and / or a computer. By way of illustration, both an application running on a computing device and a computing device can be components. One or more components can reside within a process and / or thread of execution, and a component can be localized on one computer and / or distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. A component may pass according to a signal having one or more data packets (e.g., data from two components that interact with another component between a local system, a distributed system, and / or a network, such as the Internet that interacts with other systems through signals). Local and / or remote processes to communicate.

It should be understood that the manner, situation, category, and division of the embodiments in the embodiments of the present application are only for convenience of description, and should not constitute a special limitation. The various manners, categories, situations, and features in the embodiments are not inconsistent. Cases can be combined.

It should also be understood that, in the embodiments of the present application, "first", "second", "third" and the like are only used to refer to different objects, and do not indicate that there are other restrictions on the referred objects.

In addition, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this document is only a kind of association relationship describing related objects, which means that there can be three kinds of relationships, for example, A and / or B can mean: A exists alone, A and B exist simultaneously, and exists alone B these three cases. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

It should be understood that in the embodiment of the present application, “B corresponding to A” means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B based on A does not mean determining B based on A alone, but also determining B based on A and / or other information.

Those of ordinary skill in the art may realize that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .

The above are only specific embodiments of the present invention, but the scope of protection of the present invention is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present invention. It should be covered by the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (18)

1. A method for transmitting eUICC data in the Internet of Things, comprising:

   The IoT platform of the Internet of Things obtains the sending and receiving capabilities of SMS messages of the short message service of the communication network, and the IoT platform communicates with the terminal device through the communication network;

   The IoT platform converts an SMS message to be sent to the terminal device into a first lightweight machine-to-machine LwM2M message when the communication network does not support the sending and receiving function of SMS messages, and the SMS message includes The target data of the embedded universal integrated circuit card eUICC in the terminal device is described, and the data format of the target data included in the first LwM2M message is an SMS format;

   Sending, by the IoT platform, the first LwM2M message to the terminal device.
2. The method according to claim 1, wherein the SMS message to be sent to the terminal device is from an application server, and the IoT platform converts the SMS message to be sent to the terminal device into a first lightweight machine-to-machine Before the LwM2M message, the method further includes:

   Receiving, by the IoT platform, the SMS message sent by an application server.
3. The method according to claim 1 or 2, wherein before the IoT platform converts the SMS message into the first lightweight machine-to-machine LwM2M message, the method further comprises:

   The IoT platform acquires the sending and receiving capabilities of the SMS messages of the terminal device; and when the communication network does not support the sending and receiving function of the SMS messages, the IoT platform converts the SMS messages to be sent to the terminal device into the first LwM2M messages, including:

   The IoT platform converts an SMS message to be sent to the terminal device into a first LwM2M message when the communication network does not support the sending and receiving function of SMS messages and the terminal device supports the sending and receiving function of SMS messages.
4. The method according to claim 3, wherein the acquiring, by the IoT platform, the sending and receiving capabilities of SMS messages of the terminal device comprises:

   Sending, by the IoT platform, a LwM2M request message to the terminal device, where the LwM2M request message is used to request to obtain the sending and receiving capability of the SMS message of the terminal device;

   Receiving, by the IoT platform, a response message to the LwM2M request message sent by the terminal device, where the response message includes indication information of an SMS messaging capability of the terminal device.
5. The method according to claim 3, wherein the acquiring, by the IoT platform, the sending and receiving capabilities of SMS messages of the terminal device comprises:

   The IoT platform receives LwM2M registration information sent by the terminal device, and the LwM2M registration information includes indication information of an SMS message sending and receiving capability of the terminal device.
6. The method according to any one of claims 1 to 5. It is characterized in that the ability of the IoT platform to obtain the sending and receiving of SMS messages of the communication network includes:

   The IoT platform acquires the sending and receiving capabilities of SMS messages of the communication network through a service capability open network element SCEF.
7. The method according to any one of claims 1 to 6, wherein the target data includes profile activation information delivered to a target operator of the eUICC in the terminal device, and the profile activation information is used for Activate the profile of the target operator in the eUICC.
8. The method according to claim 7, wherein before the IoT IoT platform sends the first LwM2M message to the terminal device, the method further comprises:

   The IoT platform sends a second LwM2M message to the terminal device, and the second LwM2M message includes download data of a profile delivered to a target operator of the eUICC in the terminal device.
9. The method according to any one of claims 1 to 8, before the IoT platform sends the first LwM2M message or the second LwM2M message to the terminal device, the method further comprises:

   The IoT platform determines that the terminal device is capable of analyzing target data sent to the eUICC or the profile download data.
10. The method according to claim 9, wherein the determining by the IoT platform that the terminal device has the ability to analyze the target data sent to the eUICC or the profile download data specifically comprises:

    Receiving, by the IoT platform, a third LwM2M message sent by the terminal device, where the third LwM2M message includes an indication bit, and the indication bit is used to indicate whether the terminal device is capable of analyzing the target data sent to the eUICC The ability of the profile to download data;

    The IoT platform determines that the terminal device is capable of analyzing the target data sent to the eUICC or the profile download data according to the indicated bit.
11. A method for transmitting eUICC data in the Internet of Things, comprising:

    The terminal device receives a first lightweight machine-to-machine LwM2M message sent by the Internet of Things IoT platform, the first LwM2M message includes target data delivered to the embedded universal integrated circuit card eUICC in the terminal device, and the first LwM2M The data format of the target data of the eUICC included in the message is short message service SMS;

    Sending, by the terminal device, the target data to the eUICC according to a data format of the target data included in the first LwM2M message.
12. The method according to claim 10, wherein before the terminal device receives the first lightweight machine-to-machine LwM2M message sent by the Internet of Things IoT platform, the method further comprises:

    Receiving, by the terminal device, a second LwM2M message sent by the IoT platform, where the second LwM2M message includes download data of a profile sent to a target operator of the eUICC;

    Sending, by the terminal device, the second LwM2M message to the eUICC.
13. The method according to claim 11 or 12, wherein the terminal device has one or more of the following capabilities: an ability to send and receive SMS messages, an ability to parse target data sent to the eUICC, and The ability to download data to the profile of the eUICC.
14. An IoT IoT platform, characterized in that the platform includes: a receiver, a transmitter, a memory, and a processor,

    The receiver is configured to receive a message or data sent by a device outside the IoT platform, and forward the message or data to the processor;

    The transmitter is configured to send a message or data to a device outside the IoT platform according to an instruction of the processor;

    The memory is used to store a program;

    The processor is configured to execute a program stored in the memory, and when the program is executed, the IoT platform executes the method according to any one of claims 1 to 10.
15. A terminal device, characterized in that the terminal device includes: a machine-to-machine M2M communication device, a transceiver, a short message module, an embedded universal integrated circuit card eUICC,

    The M2M communication device performs the following operations through the transceiver: receiving a first lightweight machine-to-machine LwM2M message sent by the IoT IoT platform, and the first LwM2M message includes an embedded universal integration issued to the terminal device. The target data of the circuit card eUICC, and the data format of the target data of the eUICC included in the first LwM2M message is short message service SMS;

    The M2M communication device is configured to send the target data to a short message module according to a data format of the target data included in the first LwM2M message;

    The short message module is configured to send the target data to the eUICC.
16. The terminal device according to claim 15, wherein the M2M communication device further performs the following operations through the transceiver: receiving a second LwM2M message sent by the IoT platform, and the second LwM2M message includes a delivery Download data to the profile of the target operator of the eUICC;

    The M2M communication device is configured to send the second LwM2M message to the eUICC.
17. The terminal device according to claim 15 or 16, wherein the terminal device has one or more of the following capabilities: the ability to send and receive SMS messages, the ability to parse target data sent to the eUICC, and analysis Ability to download data to the profile sent to the eUICC.
18. A computer-readable storage medium, comprising computer instructions, which, when the computer instructions are run on a computer, cause the computer to execute the method according to any one of claims 1 to 13.

Images