CN110769384A

CN110769384A - Method and device for transmitting eUICC data in Internet of things

Info

Publication number: CN110769384A
Application number: CN201810847436.2A
Authority: CN
Inventors: 徐蓓; 张永靖
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2018-07-27
Filing date: 2018-07-27
Publication date: 2020-02-07
Anticipated expiration: 2038-07-27
Also published as: CN110769384B; WO2020019987A1

Abstract

The application provides a method for transmitting eUICC data in the Internet of things, which comprises the following steps: the method comprises the steps that an IoT platform of the Internet of things acquires the sending and receiving capacity of an SMS message of a communication network; the IoT platform converts an SMS message to be sent to the terminal equipment into a first LwM2M message under the condition that the communication network does not support the transceiving function of the SMS message, wherein the SMS message comprises target data issued to an embedded universal integrated circuit card (eUICC), and the data format of the target data of the eUICC included in the LwM2M message is SMS; the IoT platform sends the LwM2M message to a terminal device. In the technical scheme provided by the application, an application server (e.g., an SM platform) can send an SMs message to an eUICC on a terminal device under an internet of things, thereby completing remote configuration of user data on the eUICC.

Description

Method and device for transmitting eUICC data in Internet of things

Technical Field

The present application relates to the field of communications, and in particular, to a method and an apparatus for transmitting eUICC data in the internet of things.

Background

An embedded universal integrated circuit card (eUICC) standard established by global system for mobile communications alliance (GSMA) remotely configures user data on the eUICC via Short Message Service (SMS) messages. For example, the eUICC remotely activates, from an application server, user data signed up by a user in a certain operator network, and further enables user equipment configuring the eUICC to access a communication network of the operator.

With the development of internet of things (IoT) technology, the terminal device in the internet of things also needs to apply the eUICC technology standard, so that the IoT terminal device can access to networks of different operators without replacing a Subscriber Identity Module (SIM) card.

Taking narrowband internet of things (NB-IoT) as an example, the bandwidth and transmission rate of the NB-IoT network are low to achieve wide coverage and low power consumption, and therefore, most of the existing transmission protocols are not suitable for data transmission in the NB-IoT network. For example, a hypertext transfer protocol security (HTTPS) message header is large and has a high requirement on bandwidth, a HTTPS three-way handshake protocol has timer protection, and an NB-IoT network has a low rate and causes a timer to time out, so that it is not suitable for establishing a session between an application server and an eUICC through HTTPS in the NB-IoT network. Secondly, since the NB-IoT network needs to upgrade a Short Message Service Center (SMSC) or a Mobile Switching Center (MSC) in an existing network to transmit or receive a Short Message Service (SMS) message, the SMS message function is not supported under the NB-IoT network.

Therefore, how an application server (e.g., an SM platform) sends an SMs message to an eUICC in a terminal device under an internet of things, so that remote configuration of user data on the eUICC is a problem that needs to be solved at present.

Disclosure of Invention

An application server (for example, an SM platform) can send an SMS message to an eUICC in a terminal device under an IoT network, so that remote configuration of user data on the eUICC is completed.

In a first aspect, a method for transmitting eUICC data in the internet of things is provided, where the method includes: the method comprises the steps that an IoT platform of the Internet of things acquires the sending and receiving capacity of an SMS message of a communication network; the IoT platform converts an SMS message to be sent to the terminal device into a first LwM2M message if the communication network does not support the transceiving function of the SMS message; the IoT platform sends the first LwM2M message to a terminal device.

The IoT platform in the embodiment of the present application may acquire the transceiving capability of the SMS message of the communication network, and may convert the SMS message to be sent to the terminal device into the first LwM2M message if the communication network does not support the transceiving function of the SMS message.

In the embodiment of the present application, there are various specific implementation manners for the IoT platform to acquire whether the communication network supports SMS, which is not specifically limited in the present application. As an example, the IoT platform may obtain the transceiving capability of the SMS message of the communication network through a Service Capability Exposure Function (SCEF). For example, the IoT platform may call an Application Programming Interface (API) and obtain the SMS messaging capability of the communication network through the SCEF.

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

In the embodiment of the present application, the SMS message may be sent by an application server to an eUICC in the terminal device, the application server and an IoT platform may be separately deployed in the embodiment of the present application, and the application server may also be integrated in the IoT platform, which is not specifically limited in this embodiment of the present application.

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

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

The SMS message to be sent to the terminal device is not particularly limited in the embodiments of the present application. As an example, the SMS message may include activation information of a profile signed up by the eUICC at the target operator in the terminal device. As another example, the SMS message may include other configuration information sent 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) in the terminal device under the LwM2M protocol. As one 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 (data format) of the target data included in the LwM2M message to "SMS," thereby enabling conversion of the SMS message sent by the SM platform 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 sent to the eUICC, the data format of the target data, the description of the target data, and the like.

Specifically, the IoT platform may set the data format of the target data to SMS, and the M2M communicator in the terminal device may, after receiving the first LwM2M message, forward the SMS message in the first LwM2M message to the short message module in the terminal device according to the data format of the target data included in the first LwM2M message to SMS. The SMS message module may forward the target data in the parsed SMS message to the eUICC in the terminal device, and under the IoT network, an application server (e.g., an SM platform) may be implemented to send the SMS message to the eUICC in the terminal device, so that the user data on the eUICC can be remotely configured.

In the embodiment of the application, in an IoT network, a session between an application server (e.g., SM platform) and an eUICC on a terminal device can be established through an LwM2M protocol, and an SMs message can be sent to the eUICC in the terminal device, so that user data on the eUICC can be remotely configured.

With reference to the first aspect, in certain implementations of the first aspect, before the SMS message to the terminal device comes from an application server and the IoT platform converts the SMS message to the terminal device into a first LwM2M message, the method further includes: the IoT platform receives the SMS message sent by an application server.

With reference to the first aspect, in certain implementations of the first aspect, the IoT platform obtains the transceiving capability of the SMS message of the communication network through a service capability openness network element SCEF.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the IoT platform acquires the sending and receiving capacity of the SMS message of the terminal equipment; the IoT platform converts the SMS message into the first LwM2M message if the terminal device supports the messaging functionality of SMS messages and the communication network does not support the messaging functionality of SMS messages.

In the embodiment of the present application, there are various specific implementation manners for the IoT platform to acquire whether the terminal device supports SMS, which is not specifically limited in the present application. As one example, in the case where the IoT platform is directly connected with the SM platform, the IoT platform may send an LwM2M request message querying SMs capabilities to the M2M communication device on the terminal device. As another example, where the IoT platform is connected to the SMSC, the IoT platform may subscribe to a list of terminal devices that may support SMS to the SMSC, but whose network does not support SMS, and the SMSC may forward SMS messages for destination terminal devices subscribed to by the IoT platform to the IoT platform.

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

It will be appreciated that the response message includes information indicative of the SMS messaging capability of the terminal device. The IoT platform may determine the transceiving capabilities of the SMS message for the terminal device from the indication information in the response message.

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

An IoT platform may receive LwM2M registration information sent by a terminal device, the LwM2M registration information including indication information of SMS messaging capabilities of the terminal device. The IoT platform may determine the SMS messaging capabilities of the terminal device based on the indication information.

With reference to the first aspect, in some implementation manners of the first aspect, the target data includes profile activation information of a target operator of the eUICC in the terminal device, where the profile activation information is used to activate a profile of the target operator downloaded in the eUICC.

With reference to the first aspect, in certain implementations of the first aspect, before the internet of things IoT platform receives the short message service SMS message sent by the application server, the method further includes: the IoT platform receives a request message sent by the application server, wherein the request message comprises profile download data of a target operator issued to the eUICC by the application server; the IoT platform converting the request message into a second LwM2M message; the IoT platform sends the second LwM2M message to the terminal device.

With reference to the first aspect, in certain 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 equipment has the capability of analyzing the target data or the profile download data sent to the eUICC.

With reference to the first aspect, in certain implementations of the first aspect, the IoT platform receives a third LwM2M message sent by the terminal device, where the third LwM2M message includes an indication bit indicating whether the terminal device is capable of parsing the target data or the profile download data sent to the eUICC;

and the IoT platform determines that the terminal equipment has the capability of analyzing the target data or the profile download data sent to the eUICC according to the indicated bit.

In a second aspect, a method for transmitting eUICC data in the internet of things is provided, where the method includes:

the terminal equipment receives a first lightweight machine-to-machine LwM2M message sent by an IoT platform; and the terminal equipment sends the target data to the eUICC according to the data format of the target data included in the first LwM2M message.

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

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the terminal equipment receives a second LwM2M message sent by the IoT platform, wherein the second LwM2M message comprises profile download data of a target operator of the eUICC, and the profile download data is issued by the application server; and the terminal equipment sends the second LwM2M message to the eUICC.

With reference to the second aspect, in certain implementations of the second aspect, the terminal device is provided with one or more of the following capabilities: the capability of SMS messaging, the capability of analyzing target data sent to the eUICC, and the capability of analyzing profile download data sent to the eUICC.

In a third aspect, an internet of things (IoT) platform is provided, the IoT platform comprising:

the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring the transceiving capacity of an SMS message of a communication network, and the IoT platform is communicated with terminal equipment through the communication network;

a first processing module, configured to, in a case where the communication network does not support a transceiving function of an SMS message, convert an SMS message to be sent to the terminal device into a first lightweight machine-to-machine LwM2M message, where the SMS message includes target data to be sent to an 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 an SMS;

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

With reference to the third aspect, in certain implementations of the third aspect, the SMS message to the terminal device is from an application server, the IoT platform further includes, before converting the SMS message to the terminal device into a first lightweight machine-to-machine LwM2M message:

and the first receiving module is used for receiving the SMS message sent by the application server.

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

and acquiring the sending and receiving capacity of the SMS message of the communication network through a service capacity open network element SCEF.

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

the second acquisition module is used for acquiring the sending and receiving capacity of the SMS message of the terminal equipment;

a second processing module, configured to, in a case that the terminal device supports a function of sending and receiving SMS messages and the communication network does not support the function of sending and receiving SMS messages, convert the SMS messages into the first LwM2M message.

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

sending an LwM2M request message to a terminal device, wherein the LwM2M request message is used for requesting to acquire the transceiving capacity of the SMS message of the terminal device;

and receiving a response message to the LwM2M request message, which is sent by the terminal equipment, wherein the response message comprises indication information of the SMS messaging capability of the terminal equipment.

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, wherein the LwM2M registration information comprises indication information of transceiving capacity of the SMS message of the terminal device;

and determining the sending and receiving capabilities of the SMS message of the terminal equipment according to the indication information in the LwM2M registration information.

With reference to the third aspect, in some implementation manners of the third aspect, the target data includes profile activation information of a target operator of the eUICC in the terminal device, where the profile activation information is used to activate a profile of the target operator downloaded in the eUICC.

With reference to the third aspect, in certain 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 profile download data of a target operator of the eUICC issued by the application server;

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.

and the determining module is used for determining that the terminal equipment has the capability of analyzing the target data sent to the eUICC or the profile download data.

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

receiving 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 that the terminal device has a capability of parsing target data or profile download data sent to the eUICC;

and determining that the terminal equipment has the capability of analyzing the target data or the profile download data sent to the eUICC according to the indicated bit.

In a fourth aspect, a terminal device is provided, the terminal device comprising:

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

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

a second sending module, configured to send the target data to the eUICC by the short message module.

With reference to the fourth aspect, in some implementations of the fourth aspect, the terminal device is capable of one or more of the following capabilities: the capability of SMS messaging, the capability of analyzing target data sent to the eUICC, and the capability of analyzing profile download data sent to the eUICC.

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

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

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

In a fifth aspect, an internet of things (IoT) platform is provided, including: a receiver, a transmitter, a memory, and a processor.

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

Alternatively, the processor may be a general-purpose processor, and may be implemented by hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory, which may be integrated with the processor, located external to the processor, or stand-alone.

When the program is executed, the processor is configured to: acquiring the sending and receiving capacity of an SMS message of a communication network, wherein the IoT platform is communicated with terminal equipment through the communication network;

the processor is further configured to: for converting an SMS message to be sent to the terminal device into a first lightweight machine-to-machine, LwM2M, message, the SMS message including target data to be sent to an embedded universal integrated circuit card, eUICC, in the terminal device, in case the communication network does not support transceiving functionality for SMS messages, the data format of the target data included in the first LwM2M message being SMS;

the transmitter is configured to: and sending the first LwM2M message to a terminal device.

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

With reference to the fifth aspect, in certain implementations of the fifth aspect, the processor is specifically configured to: and acquiring the sending and receiving capacity of the SMS message of the communication network through a service capacity open network element SCEF.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the IoT platform further includes:

the processor is further configured to: acquiring the transmitting and receiving capacity of the SMS message of the terminal equipment;

the processor is further configured to: in case the terminal device supports the transceiving function of SMS messages and the communication network does not support the transceiving function of SMS messages, converting the SMS messages into the first LwM2M message.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the processor is specifically configured to: sending an LwM2M request message to a terminal device, wherein the LwM2M request message is used for requesting to acquire the transceiving capacity of the SMS message of the terminal device;

the receiver is specifically configured to: and receiving a response message to the LwM2M request message, which is sent by the terminal equipment, wherein the response message comprises indication information of the SMS messaging capability of the terminal equipment.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the processor is specifically configured to perform, by the receiver: receiving LwM2M registration information sent by the terminal device, wherein the LwM2M registration information comprises indication information of transceiving capacity of the SMS message of the terminal device;

the processor is specifically configured to: and determining the sending and receiving capabilities of the SMS message of the terminal equipment 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 of a target operator of the eUICC in the terminal device, where the profile activation information is used to activate a profile of the target operator downloaded in the eUICC.

With reference to the fifth aspect, in certain 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 performs, by the receiver: receiving a request message sent by the application server, wherein the request message comprises profile download data of a target operator of the eUICC issued by the application server;

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

the transmitter is specifically configured to: sending the second LwM2M message to the terminal device.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the processor in the IoT platform is further to: and determining that the terminal equipment has the capability of analyzing the target data or the profile download data sent to the eUICC.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the processor is specifically configured to perform, by the receiver: receiving 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 that the terminal device has a capability of parsing target data or profile download data sent to the eUICC;

the processor is specifically configured to: and determining that the terminal equipment has the capability of analyzing the target data or the profile download data sent to the eUICC according to the indicated bit.

In a sixth aspect, a terminal device is provided, which includes: machine-to-machine M2M communication means, transceiver, short message module, embedded universal integrated circuit card eUICC,

the M2M communication device performing the following operations by the transceiver: receiving a first LwM2M message sent by an IoT platform, wherein the first LwM2M message includes target data issued by an application server to an eUICC (embedded universal integrated circuit card) in the terminal equipment, and the target data included in the first LwM2M message is received

The data format of the target data of the eUICC is Short Message Service (SMS);

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

the short message module is used for: and sending the target data to the eUICC.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the M2M communication device further performs, by the transceiver: receiving a second LwM2M message sent by the IoT platform, wherein the second LwM2M message includes profile download data of a target operator issued by the application server to the eUICC;

the M2M communication device is configured to: sending the second LwM2M message to the eUICC.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the terminal device is capable of one or more of the following capabilities: the capability of SMS messaging, the capability of analyzing target data sent to the eUICC, and the capability of analyzing profile download data sent to the eUICC.

In a seventh aspect, a computer-readable medium is provided for storing a computer program comprising instructions for performing the method of the first aspect or any possible implementation manner of the first aspect.

In an eighth aspect, there is provided a computer readable medium for storing a computer program comprising instructions for performing the method of the second aspect or any possible implementation manner of the second aspect.

In a ninth aspect, there is provided a computer program product comprising: computer program code which, when run by a computer, causes the computer to perform the method of the first aspect or any possible implementation of the first aspect.

In a tenth aspect, there is provided a computer program product comprising: computer program code which, when run by a computer, causes the computer to perform the method of the second aspect or any possible implementation of the second aspect.

In an eleventh aspect, there is provided a communication chip having instructions stored therein, which when run on an apparatus for wireless communication, cause the communication chip to perform the method of the first aspect or any possible implementation manner of the first aspect.

In a twelfth aspect, there is provided a communication chip having instructions stored therein, which when run on a device for wireless communication, cause the communication chip to perform the method of the second aspect or any possible implementation manner of the second aspect.

Drawings

Figure 1 is a schematic block diagram of one possible architecture for implementing eUICC remote provisioning and management.

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

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

Fig. 4 is a schematic block diagram of one possible terminal device.

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

Fig. 6 is a schematic flow chart of a method for transmitting eUICC data in the internet of things according to the embodiment of the present application.

Fig. 7 is a schematic flow chart of acquiring SMS support capability according to an embodiment of the present application.

Fig. 8 is a schematic flow chart of acquiring 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 the embodiment of the present application.

Fig. 10 is a schematic flow chart of a method for transmitting eUICC data in the internet of things according to another embodiment of the present application.

Fig. 11 is a diagram illustrating 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 diagram illustrating the number of messages between the eUICC and the application server after using the method for transmitting data of the present application.

Fig. 13 is a schematic block diagram of an internet of things IoT platform 1300 provided in an embodiment of the present application.

Fig. 14 is a schematic block diagram of a terminal device 1400 provided in an embodiment of the present application.

Fig. 15 is a schematic block diagram of an internet of things IoT platform 1500 provided in an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

It should be understood that the technical solutions of the embodiments of the present application may be applied to various communication systems, for example: a cellular-based internet of things (IoT) system, a narrowband internet of things (NB-IoT) system, a global system for mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a universal mobile communication system (universal mobile telecommunications system, UMTS), a universal microwave access (microwave access) system, a future radio communication system (WiMAX, 5) or the like.

The type of the terminal device is not particularly limited in this embodiment, and may be, for example, a user equipment, an access terminal, a terminal device, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless network device, a user agent, or a user equipment. The terminal may include, but is not limited to, a Mobile Station (MS), a mobile phone (mobile telephone), a User Equipment (UE), a handset (handset), a portable device (portable equipment), a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a radio frequency identification for logistics (RFID) terminal device, a handheld device having a wireless communication function, a computing device or other devices connected to a wireless modem, a vehicle-mounted device, a wearable device, an internet of things, a terminal device in a vehicle network, and a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

By way of example, and not limitation, in embodiments of the present invention, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

As another example, in the embodiment of the present invention, the terminal device may be various carriers moving at high speed, for example, a shared bicycle, a shared automobile, and the like. The terminal equipment can also be various intelligent meters, such as a water meter, an electric meter, a gas meter and the like. The terminal device can also be various monitoring devices or household appliances.

Figure 1 is a schematic block diagram of an architecture that enables remote provisioning and management of an eUICC.

The architecture for implementing the remote configuration and management of the eUICC shown in fig. 1 may include a Subscription Management (SM) platform 110 and an eUICC 120. In the established eUICC standard of GSMA, the SM platform 110 can establish a session with the eUICC 120. The SM platform 110 may switch the profile loaded on the eUICC 120 based on an Over The Air (OTA), so that the eUICC 120 may switch from a current Mobile Network Operator (MNO) to a target MNO.

It should be understood that profile is a special term in the field of communications, and may be understood as a user subscription data set, or a collection of personal subscription service data for subscribing to a certain operator network, and is a data set of mobile user information, and may include user identification information (e.g., information such as user identity, authentication parameters, etc.) and service subscription information.

The data contained in the profile may include, for example, but is not limited to: the profile type includes, for example, a Subscriber Identity Module (SIM) alliance profile (SIM) package, an International Mobile Subscriber Identity (IMSI) code, an Integrated Circuit Card Identity (ICCID) code, an executable file loading AID (AID) program (executable file AID for SD) of a Secure Digital (SD) memory card, an executable module AID (executable module AID for SD) of a SD memory card, and the like.

Specifically, after receiving a profile download request sent by a target MNO or a user, the SM platform 110 may issue 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 profile, thereby enabling the eUICC 120 to switch from the current MNO to the target MNO.

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

The SM platform 110 and the eUICC 120 are described below.

The SM platform 110 is a core of the eUICC remote management, and the SM platform 110 may perform management operations such as downloading, installing, activating, deactivating, deleting, and the like on a profile according to a request initiated by an MNO or a user. The functionality of the SM platform 110 mainly includes two parts: subscription management data preparation (SM-DP), subscription management secure routing (SM-SR). The SM-DP is mainly responsible for generating and storing profile according to data provided by the target MNO. The SM-SR is mainly responsible for establishing a tunnel to the eUICC 120, and may download a profile route generated by the SM-DP to the eUICC 120.

The eUICC 120 can be an embedded UICC card that can interface with, for example, a modem (which can be a circuit or baseband chip) in a terminal device. The eUICC 120 can communicate with other devices or devices outside the terminal equipment through the modem. The eUICC 120 can provide the user with the ability to implement MNO changes over the air interface (OTA) without replacing the eUICC physical entity itself. The eUICC 120 can provide security services for mobile network access authentication and user identity authentication similar to a common smart card and can be used to remotely manage multiple mobile networks operating personal management services.

Several management operations of the profile are described below.

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

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

profile activation: according to the MNO or the user request, the SM platform may activate the profile currently in a deactivated state on the eUICC, so that the file and the application in the profile may be selected through an interface between the terminal device and the eUICC.

profile deactivation: according to the MNO or the user request, the SM platform may deactivate the profile currently in the activated state on the eUICC, so that the files and applications in the profile may not be selected through the interface between the terminal device and the eUICC.

Referring to fig. 2, in an architecture for implementing the remote configuration and management of the eUICC, a session is established between the SM platform 110 and the eUICC 120 through a Hyper Text Transfer Protocol Secure (HTTPS) message. The SM platform 110 may issue the generated profile to the eUICC 120 through an SMs message after receiving a profile download request sent by the target MNO or the user.

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

the details are described below by taking a narrowband internet of things NB-IoT as an example.

On the one hand, it is not appropriate to establish a session between an application server and an eUICC over HTTPS protocol under NB-IoT networks. 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 has a high bandwidth requirement, so that it is not suitable to establish a session between the application server and the eUICC through the HTTPS protocol under the NB-IoT network. As another example, since there is timer protection in HTTPS three-way handshake protocol, and the rate of NB-IoT network is low, resulting in timer timeout, it is not suitable to establish a session between an application server and an eUICC over HTTPS protocol under NB-IoT network.

On the other hand, the function of SMS messaging is not supported under the NB-IoT network. In the existing NB-IoT standard, there are two ways for the NB-IoT network to obtain the SMS message. As an example, the terminal device may transmit the SMS message through the SGd interface, for example, the path of the SGd interface transmitting the SMS message is: SMSC-Mobility Management Entities (MMEs) -evolved base stations (enbs or enodebs) -UEs. As another example, the terminal device may also transmit the SMS message through the SGs interface, for example, the path of the SGd interface transmitting the SMS message is: SMSC-MSC-MME-eNodeB-UE.

Because the above two approaches for obtaining the SMS message 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 carrier's existing network integrates SMSCs and/or MSCs of multiple manufacturers, and cannot upgrade or expand the SMSCs and/or MSCs. Therefore, the function of SMS messaging is not supported under the NB-IoT network.

In view of the above problems in applying the eUICC technology standard under the IoT network, in one aspect, in the embodiments of the present application, a session between an SM platform and an eUICC can be established through a light weight machine to machine (LwM 2M) protocol. On the other hand, the embodiment of the present application may encapsulate the SMs message sent by the SM platform into the LwM2M message, so that the SMs message may be transmitted under the IoT network.

The following describes in detail the establishment of a session between the SM platform and the eUICC via the LwM2M protocol in the embodiment of the present application.

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

The protocol stack structure of LwM2M can be seen in fig. 2. The LwM2M protocol 210 belongs to an Application layer protocol, and is located above a constrained Application protocol (CoAP) 220. The CoAP 220 may perform processing of encrypting a packet transport layer security (DTLS) 230, and may finally transmit the encrypted data through a user packet protocol (UDP) 240, a Short Message Service (SMS) 250, or an SMS 255. The LwM2M protocol may package messages into objects (Obj) 260 and may be transported via the above-described protocol. The object objects will be described in detail later, and will not be described in detail herein.

It should be understood that the SMS250 may be a short message service located on a device (on device) and the SMS255 may be a short message service located on a smart card (on smartcard).

The message header of the LwM2M protocol is smaller than that of the HTTPS, and the LwM2M protocol can establish a session between the internet of things IoT platform (as a server) and the M2M communication device (as a client) on the terminal device without multiple handshakes. In an IoT network, therefore, a session between an application server (e.g., SM platform) and an eUICC on a terminal device can be established through the LwM2M protocol, thereby enabling data transmission.

The establishment of a session between an application server (e.g., SM platform) and the eUICC on the terminal device via the LwM2M protocol is described in detail below, taking fig. 3 as an example.

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

SM platform 310 may correspond to SM platform 110 in fig. 1, and in this embodiment, SM platform 310 may be an application server, SM platform 310 may be deployed separately from IoT platform 320, and SM platform 310 may also be integrated in IoT platform 320, which is not specifically limited in this application.

The following is exemplified by an example where SM platform 310 may be deployed separately from IoT platform 320.

The SM platform 310 may send a profile download request sent by the MNO to the terminal device 330 through the IoT platform. The SM platform 310 may convert the profile download request sent by the MNO into an LwM2M message (e.g., the profile download request may be packaged into LwM2M Objects) and then sent to the IoT platform 320, or may convert the profile download request sent by the MNO into other types of messages and send to the IoT platform 320.

The IoT platform 320 may serve as a device management platform in the LwM2M protocol, the IoT platform 320 may send a message 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 perform message transmission through the LwM2M protocol, the IoT platform 320 needs to convert the message sent by the SM platform 310 into an LwM2M message and send the message to the terminal device 330, and the LwM2M message of the terminal device 330 received by the IoT platform 320 also needs to perform protocol conversion before being forwarded to the SM platform 310.

The M2M communication device 340 and the eUICC350 are configured in the terminal equipment 330, and the LwM2M message received by the terminal equipment 330 can be processed by the M2M communication device 340 on the terminal equipment 330. A schematic block diagram of the terminal device 330 may be as shown in fig. 4.

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

The eUICC350 can correspond to the eUICC 120 in fig. 1. The eUICC350 and the M2M communication device 340 can communicate and exchange information. Physically, the eUICC350 can be a separate device from the M2M communication device 340, or the eUICC350 can be a device bound to the M2M communication device 340 (e.g., by soldering or otherwise embedding the eUICC350 in the M2M communication device 340). The eUICC350 forwards the received LwM2M message to the eUICC350 through a transceiver on the M2M communication device 340.

Fig. 4 is a schematic block diagram of one possible terminal device. The terminal device 330 in fig. 4 may include: M2M communication device 420, wireless transceiver 430, eUICC480, 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 may be a very large scale integrated circuit (vlsi) that extends a time-frequency function and a dedicated interface on the basis of a Central Processing Unit (CPU) with low power consumption, and an operating system and application software are run on the AP 410.

The M2M communication device 420 may correspond to the M2M communication device 340 in fig. 3. As one example, the M2M communicator 420 may be a modem, which may be referred to as a baseband chip, and primarily functions to transmit and receive various data, such as implementing the primary functions in a wireless communication standard such as the third generation partnership project (3 GPP). The modem may correspond to a communication protocol processor and may be responsible for data processing.

The M2M communication device 420 may be provided as a separate chip or may be formed together with other chips or circuits as a system-on-chip or integrated circuit. The chip or the integrated circuit can be applied to all terminal devices which realize wireless communication functions.

The terminal device 330 can perform reception and transmission of data through the wireless transceiver 430.

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

The memory 450 may be used to store one or more of computer program instructions, preset parameters, data resulting from computer intermediate operations, and the like.

The internal logical structure of the modem420 will be described below with the M2M communicator 420 as the modem 420.

Fig. 5 is a schematic block diagram of a modem according to an embodiment of the present application. The modem (modem)420 shown in fig. 5 may include a reception data processor 510, a controller 520, a transmission data processor 530.

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

The processor 520 may process data through a protocol layer, and the processor 520 may process data through a Medium Access Control (MAC) layer protocol, a Radio Link Control (RLC) layer protocol, a Packet Data Convergence Protocol (PDCP), and a Radio Resource Control (RRC) layer protocol.

The data transmitter 530 may modulate data after channel coding, modulation, symbol generation, etc., and may transmit the data to the UICC connected to the modem420 through a PHY layer protocol.

The modem420 shown in fig. 5 may also have a built-in memory called an on-chip memory, such as a terminal device To Computer Multiplexer (TCM), a Static Random Access Memory (SRAM), and the like.

The modem420 may also communicate with off-chip memory, which may include, but is not limited to: read-only memory (ROM), Random Access Memory (RAM), a usb disk, a removable hard disk, an optical disk, a magnetic storage device, and the like.

The method for transmitting the eUICC data in the Internet of things provided by the embodiment of the application can be used for sending an SMS message to the eUICC on the M2M communication device by an application server (for example, an SM platform) under the Internet of things, so that the remote configuration of the user data on the eUICC is completed.

The method for transmitting the eUICC data in the internet of things provided by the embodiment of the present application is described below.

Fig. 6 is a schematic flow chart of a method for transmitting eUICC data in the internet of things according to the embodiment of the present application. The method of FIG. 6 may include steps 610-630, and the steps 610-630 are described below.

In step 610, the IoT platform obtains the SMS messaging capabilities of the communication network.

The target data included in the SMS message to be sent to the terminal device is not particularly limited in the embodiments of the present application. As an example, the target data may include activation data of a profile issued by an application server (e.g., SM platform) to the eUICC user signed up at the target operator. As another example, the target data may also include other configuration data that is sent by an application server (e.g., SM platform) to the eUICC user in the form of an SMs message.

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

The embodiment of the application may enable an IoT platform (LwM2M server) to encapsulate the received SMS message into an LwM2M message when the communication network does not support the SMS message transceiving function, and may send the first LwM2M message to an M2M communication device (LwM2M client) in the terminal device under an LwM2M protocol. As an example, the IoT platform may package the content of the received SMS message into an LwM2M application data object (app data container object) and may set the data format (data format) of the target data included in the first LwM2M message to "SMS", such that translation of the SMS message sent by the SM platform into the first LwM2M message under the LwM2M protocol may be implemented.

It should be appreciated that in the LwM2M protocol, for each LwM2M entity (e.g., each device supporting the LwM2M protocol), accessible services are abstracted into one object, and there may be three levels for each object bureau. As an example, an object may comprise several objects (objects) providing different functions, e.g. several different sensors. As another example, each of the above functions may be provided by multiple object-instances (object-instances), such as providing a temperature reading function for each temperature sensor. As another example, the functionality that the above-described object instances may actually perform may be referred to as a resource (rsource).

In the LwM2M protocol, the format of a Uniform Resource Identifier (URI) may be as follows: </object ID/object-instance ID/resource ID >. For example, commonly used URI formats may be any of the formats: 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 equipment may send the first LwM2M message to the eUICC in the terminal equipment according to the data format (data format) of the target data included in the first LwM2M message. As an example, the M2M communication device in the terminal equipment may be "SMS" according to the target data format included in the first LwM2M message, and may send the SMS message content in the LwM2M message to a corresponding short message module, which may forward the SMS message to the eUICC in the terminal equipment.

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 other devices. The M2M communication device is applicable to all devices that implement wireless communication functions. As an example, the M2M communication device may be a modem, and for details of the modem, reference is made to fig. 5, which is not described herein again.

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

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

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

For a detailed description of the terminal device, reference may be made to the description of the terminal device 330 in fig. 4, which is not described herein again. In the embodiment of the application, the message header of the LwM2M protocol is smaller than that of the HTTPS, and the LwM2M protocol can establish a session between the IoT platform of the internet of things (serving as the server) and the M2M communication device (serving as the client) on the terminal device without multiple handshakes. Also, the IoT platform (as a server sever) may convert the SMS message into a first LwM2M message and may set a data format of the first LwM2M message to "SMS". Thus, in an IoT network, a session between an application server (e.g., SM platform) and the eUICC on the terminal device can be established via the LwM2M protocol, and an SMs message can be sent to the eUICC on the M2M communication device, thereby completing the remote provisioning of user data on the eUICC.

The following description will take the activation information of the profile of the eUICC as the target data included in the first LwM2M message as an example.

The IoT platform receives the activation information (SMs message) of the profile sent by the SM platform and may convert the SMs message to the first LwM2M message under the LwM2M protocol. For example, the SMs message sent by the SM platform may be packaged into an LwM2M application data object (app data container object), and the conversion of the request message sent by the SM platform into the first LwM2M message under the LwM2M protocol may be implemented. A detailed description will be given below, with reference to fig. 9, of a specific implementation manner in which the IoT platform converts the activation information of the profile sent by the SM platform into the first LwM2M message under the LwM2M protocol, which is not described herein again.

Optionally, in some embodiments, the IoT platform may also receive the profile download information sent by the application server (e.g., SM platform) before the IoT platform receives the activation information (SMs message) of the profile sent by the application server (e.g., SM platform). The IoT platform may convert the profile download information into a second LwM2M message under the LwM2M protocol and may send the LwM2M message to the eUICC. A detailed description will be given below, with reference to fig. 10, of a specific implementation manner in which the IoT platform converts the profile download information sent by the SM platform into the second LwM2M message under the LwM2M protocol, which is not described herein again.

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 the profile download information received from the profile sent by the application server into the LwM2M message under the LwM2M protocol. Therefore, an extension to the data format (data format) in the LwM2M application data (LwM2M app data) is required, as shown in table 1.

Table 1 LwM2M application data extensions

Referring to table 1, the embodiment of the present application may extend LwM2M data format in an LwM2M application data container (app data container), where the object ID of the app data container is 19. The LwM2M app datacontainer may include a plurality of items of data (data), data security (data priority), data description (datadescription), data format (data format), application id (app id), and the like.

The data format in the app data container can be extended in the embodiment of the application, and the extended data format may further 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 (respond ISD-P key setReq), response to create ISD-P key (respond ISD-P key set Rsp), request to transmit data (senddata Req), response to transmit data (send data Rsp).

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

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

TABLE 2 LwM2M device capability management object extensions (LwM2M device capability management)

Referring to table 2, in the embodiment of the present application, an LwM2M device capability management object may be extended, and a connection capability in an LwM2M device functional group may increase a sending and receiving capability of an SMS message of a terminal device, and a capability of the terminal device to analyze target data sent to the eUICC or download data from the profiler.

It should be understood that after the extension, whether the terminal device has the transceiving capability of the SMS message, the capability of parsing the target data sent to the eUICC, or the capability of downloading the profile data may be indicated by the LwM2M message.

In this embodiment of the application, the IoT platform may determine, through an indicator bit in an LwM2M message sent by the terminal device, whether the terminal device has the capability of parsing the activation data of the etiicprofile or the download data of the profile.

Optionally, in this embodiment of the present application, before the IoT platform converts the activation information (SMs message) of the profile sent by the SM platform into the first LwM2M message under the LwM2M protocol, the IoT platform acquires whether the terminal device and/or the communication network have the transceiving capability of the SMs message. The IoT platform may convert the activation information (SMS message) of the profile sent by the SM platform to a first LwM2M message under the LwM2M protocol to send to the M2M communication device in the terminal device if the terminal device is SMS message capable and the communication network is not SMS message capable.

In the embodiment of the present application, there are various specific implementation manners for the IoT platform to acquire whether the terminal device has the SMS message transceiving capability, and this application is not particularly limited thereto. As an example, in the case where the IoT platform is directly connected with the SM platform, the IoT platform may send a request message to the terminal device to acquire the SMs messaging capability of the terminal device, and the IoT platform may determine the SMs messaging capability of the terminal device according to the indication information included in the response message sent by the terminal device. As another example, in the case where the IoT platform is connected to the SMSC, the IoT platform may subscribe to the SMSC with a list of terminal devices that are capable of transceiving SMS messages, but whose communication network is not capable of transceiving SMS messages. The two specific implementations are described in detail below with reference to fig. 7 to 8, and are not described herein again.

In the embodiments of the present application, a specific implementation manner of the IoT platform acquiring whether the terminal device and/or the communication network have the capability of sending and receiving the SMS message is described in more detail below with reference to a specific example. It should be noted that the example of fig. 7 is only for assisting the skilled person in understanding the embodiments of the present application, and is not intended to limit the embodiments of the present application to the specific values or specific scenarios illustrated. It will be apparent to those skilled in the art from the example of fig. 7 given herein that various equivalent modifications or variations may be made, and such modifications or variations fall within the scope of the embodiments of the present application.

Fig. 7 is a schematic flow chart of acquiring the terminal device and/or the communication network with SMS message transceiving capability according to the embodiment of the present application. The method of FIG. 7 may include steps 710-790, which are described in detail below in relation to steps 710-790, respectively.

It should be understood that fig. 7 is detailed by taking as an example that the SM platform can be deployed separately from the IoT platform.

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

In this embodiment of the 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 the API interface.

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

In the embodiment of the application, after receiving the SMs message sent by the SM platform, the IoT platform may acquire whether the destination terminal device has the capability of sending and receiving the SMs message, and may also acquire whether the communication network has the capability of sending and receiving the SMs message.

The IoT platform may convert the SMS message sent by the SM platform into an LwM2M message to send to the terminal device if the destination terminal device is capable of sending and receiving SMS messages and the communication network is not capable of sending and receiving SMS messages.

The specific implementation manner of the IoT platform acquiring whether the destination terminal device has the SMS messaging capability is described in step 730 and 740.

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

The IoT platform may send an LwM2M request message to a destination terminal device that may be used to request to obtain the transceiving capabilities of the SMS message for the terminal device.

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

The destination terminal device may send a response message to the IoT platform after receiving the request message sent by the IoT platform, the response message including 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 a connectivity property ID (property ID) in a device capability management (LwM2M device capability management) object of the destination terminal device, which 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 (20 x04), see fig. 2, the indication may indicate that the destination terminal device is SMS messaging capable.

The specific implementation of the IoT platform to obtain whether the communication network has SMS messaging capability is described in steps 750 and 790.

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

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

For example, if the communication network of the IoT terminal device is the MNO2, the IoT platform may call the API interface to obtain to the SCEF of the MNO2 whether the MNO2 is SMS message capable.

In step 760, the SCEF sends an inquiry request (SMS capabilityrequest) for the SMS messaging capability of MNO2 to the MME.

The SCEF may, after receiving the query request for the SMS messaging capabilities of MNO2 sent by the IoT platform, send the query request to the MME in order to obtain whether MNO2 is provisioned with the SMS messaging capabilities.

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

The MME may determine whether the MNO2 is SMS messaging capable based on whether the MNO2 supports the SGd interface and/or the SGs interface. For details of the SGd interface and/or the SGs interface, please refer to the foregoing description, which is not repeated herein.

If the MME determines that the SGd interface and/or SGs interface is not supported (SMSC and/or MSC is not available), it may determine that MNO2 does not have SMS message transceiving capability.

In step 780, the SCEF returns the query result of the MNO's 2 SMS messaging capabilities to the IoT platform.

The SCEF may send the query result to the IoT platform according to the result fed back by the MME.

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

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

Another specific implementation manner of the IoT platform acquiring whether the terminal device and/or the communication network are provided with the SMS messaging capability in the embodiment of the present application is described in more detail below with reference to a specific example. It should be noted that the example of fig. 8 is only for assisting the skilled person in understanding the embodiments of the present application, and is not intended to limit the embodiments of the present application to the specific values or specific scenarios illustrated. It will be apparent to those skilled in the art from the example of fig. 8 given herein that various equivalent modifications or changes may be made, and such modifications and changes are intended to fall within the scope of the embodiments of the present application.

Fig. 8 is a schematic flow chart of another method for acquiring the terminal device and/or the communication network with SMS message transceiving capability according to the embodiment of the present application. The method of FIG. 8 may include steps 810-870, which are described in detail below in relation to steps 810-870, respectively.

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

It should be understood that fig. 8 is detailed by taking as an example that the SM platform can be deployed separately from the IoT platform.

Step 810, the terminal device registers to the IoT platform and reports the LwM2M device capability discovery object.

Each terminal device may report a device capability management (LwM2M device capability management) object, such as the object 15/0, of each terminal device during registration with the IoT platform (as the LwM2M server segment).

Step 820, the IoT platform obtains whether the terminal device has the capability of sending and receiving SMS messages, and has the capability of analyzing the target data or the profile download data sent to the eUICC.

The IoT platform may receive a registration message for each terminal device, where the indication information included in the registration message may indicate whether each terminal device has the capability of transceiving an MS message, the capability of parsing target data sent to the eUICC, or the capability of downloading the profile data.

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 (20 x04), see fig. 2, the indication may indicate that the terminal device is SMS messaging capable.

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 (20 x05), see fig. 2, the indication information may indicate that the terminal device has the capability of parsing the target data or the profile download data sent to the eUICC.

At step 830, the IoT platform obtains the SMS messaging capabilities of the communication network MNO 2.

The IoT platform may screen out the terminal device that has the SMS message transceiving capability and the capability of parsing the target data or the profile download data sent to the eUICC according to the result of step 820.

The IoT platform may also acquire the SMS messaging capabilities of the communication network MNO 2.

At step 840, the IoT platform subscribes to the SMSC for the SMS message for the terminal device in the terminal list.

The IoT platform may obtain, according to the query results of step 820 and step 830, a list of terminal devices that have SMS message transceiving capability, and have the capability of parsing the target data or the profile download data sent to the eUICC, but the communication network does not have SMS message transceiving capability. The IoT platform may subscribe to the SMSC for SMS messages for terminal devices in the list.

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

In step 850, the SM platform sends a profile activation request message (SMs message) to the SMSC.

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

The SMSC may determine whether a destination terminal device of the SMs message is subscribed after receiving the SMs message delivered by the SM platform. If the destination terminal device of the SMS message is subscribed by the IoT platform, the SMSC may issue the SMS message to the IoT platform.

The SMSC sends a profile activation request message to the IoT platform, step 870.

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

It was mentioned above that the IoT platform may 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 may convert the profile activation request message (SMS message) into the first LwM2M message under the LwM2M protocol and may send the first LwM2M message to the terminal device in a scenario where the terminal device is SMS message capable and its communication network is not SMS message capable.

In the embodiment of the present application, a specific implementation manner of the IoT platform converting the profile activation request message (SMS message) into the first LwM2M message under the LwM2M protocol is described in more detail below with reference to a specific example. It should be noted that the example of fig. 9 is only for assisting the skilled person in understanding the embodiments of the present application, and is not intended to limit the embodiments of the present application to the specific values or specific scenarios illustrated. It will be apparent to those skilled in the art from the example given in fig. 9 that various equivalent modifications or changes may be made, 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 the embodiment of the present application. The method of FIG. 9 may include steps 910 + 975, which are described in detail below with respect to steps 910 + 975, respectively.

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 are capable of sending and receiving SMS messages. The specific obtaining manner may refer to the method shown in fig. 7, or may refer to the method shown in fig. 8, which is not specifically limited in this embodiment of the present application.

It should also be understood that fig. 9 is detailed with the example that the SM platform can be deployed separately from the IoT platform.

The process of downstream transmitting the SMS message (from the SM platform to the eUICC) refers to step 910-945.

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, where the current network operator MNO2 needs to be deactivated and the switched operator MNO1 needs to be activated. For details about the step of downloading the profile by the eUICC, please refer to the description in fig. 10 below, which is not described herein again.

The switched operator MNO1 may send a profile activation request to the SM platform in the form of an SMS message, where the profile activation request may be used to request activation of a profile of an operator MNO1 on the eUICC, so that the user equipment of the eUICC may be configured to access the communication network of the operator MNO 1.

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

The SM platform may send the SMs message to after receiving a profile activation request in the form of an SMs message. For example, the SM platform may call an API interface to send SMs messages to the IoT platform. IoT platform (as LwM2M sever)

At step 920, the IoT platform determines the destination terminal device of the SMS message and the SMS message transceiving capability of its communication network MNO 2.

The IoT platform may determine the SMs message transceiving capability of the SMs message destination terminal device and the SMs message transceiving capability of the communication network after receiving the profile activation request in the form of the SMs message sent by the SM platform.

If the destination terminal device and its communication network have the SMS message transceiving capability, the IoT platform converts the SMS message into an LwM2M message, step 925.

If the destination terminal device of the SMS message is an IoT terminal (which may also be understood as an M2M communication device on the terminal device as LwM2 Mclient), the IoT terminal is currently the carrier MNO 2. The IoT platform may determine the SMS messaging capabilities of the IoT terminal and the carrier MNO 2. If the IoT terminal is SMS messaging capable and the carrier MNO2 is not SMS messaging capable, the IoT platform may convert the SMS message into an LwM2M message. The IoT platform may invoke an adapter (adaptor) to modify parameters of the SMS message, for example, the adaptor may set a starting address (origin address) of the SMS message to a specified value (e.g., may be 037E11), and the adaptor may set a SMS type of the SMS message to class2 (which may be used to indicate that the SMS message is sent to the eUICC).

The IoT platform may, after setting the parameters of the SMS message, convert the SMS message into an LwM2M message under the LwM2M protocol.

For example, the IoT platform may convert SMS message content organized as LwM2M app data container objects into LwM2M messages. Referring to the description of LwM2M app data container in table 1, LwM2M app data container may include a plurality of items of data (data), data security (data priority), data description (data description), data format (data format), application id (app id), and the like. The IoT platform in the embodiment of the application may store the SMS message content in the data, may set the data format to "SMS", and may set the data description to "profile activation request", so that the SMS message may be converted into an LwM2M message under an LwM2M protocol.

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

At step 930, the IoT platform sends the LwM2M message to the destination terminal device (e.g., M2M communication means in the terminal device).

The IoT platform may send the LwM2M message into which the SMS message is converted to the destination end device.

In step 935, the M2M communicator in the destination terminal performs special processing on the SMS message in Data according to the Data format of LwM2M message.

The M2M communicator in the destination terminal device may parse the received LwM2M message and may forward the SMS message content in the data to the short message module in the destination terminal device according to the data format (data format) in the LwM2Mapp data container object as "SMS". The SMS message module may parse the SMS message, and may forward the SMS message to the eUICC in the terminal device according to a type of the short message in the SMS message, i.e., class 2.

It should be understood that the short message module may parse the SMS message and may process the SMS message. For a specific processing, refer to the description in step 940.

And step 940, the short message module on the M2M communication device in the destination terminal equipment forwards the SMS message data to the eUICC through the local interface.

The SMS message module may forward the SMS message data to the eUICC through a newly added local interface (localinterface) of the eUICC in the destination terminal device.

It should be understood that the short message module may be one of the destination terminal devices.

In this embodiment of the present application, the eUICC may include a security domain-profile (ISD-P) and a routing main security domain (ISD-R). The eUICC can download data by ISD-R routing profile, the ISD-P can be used for storing the profile data, and the ISD-P can have an identifier indicating the state (activated profile) or deactivated profile) of the profile in the current ISD-P.

According to the embodiment of the application, a local interface can be newly added in the ISD-R, and the eUICC can receive the profile data sent by the terminal equipment (for example, the eUICC can receive the profile data sent by the short message module through the local interface), so that the downloading and activation of the profile are realized, and the function that a protocol stack on the eUICC supports the eUICC can be simplified.

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

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

The eUICC can activate (enabled profile) of the operator MNO1 on the ISD-P according to the SMS message sent by the short message module, and complete access of the terminal device of the eUICC to the communication network of the switched operator MNO 1.

The process of upstream transmitting the SMS message (from the eUICC to the SM platform) please refer to step 950 and 975.

In step 950, the eUICC returns a response SMS message to activate successfully to the M2M communication device in the destination terminal equipment.

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

After receiving the operation result returned by the eUICC, the short message module in the destination terminal device may call the adaptor to modify the parameters of the SMS message. As an example, the address may set a destination address (destination address) of the SMS message according to an originatoraddress of the SMS message. For example, if the origin address of the SMS message is a specified value (e.g., may be 037E11), the adaptor may set the destination address of the SMS message to the specified value (e.g., may be 037E11) and may forward the SMS message to the M2M communicator in the destination terminal device.

The M2M communication device in the destination terminal device, as an LwM2M client, may convert the received SMS message into an LwM2M response message organized according to LwM2M app data container object. Referring to the description of LwM2Mapp data connector in table 1, the M2M communication means in the destination terminal device may set the data format to "SMS" and store the SMS message content in the data.

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

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.

At step 965, the IoT platform forwards the LwM2M response message to the SM platform.

The IoT platform may parse the LwM2M response message upon receiving the LwM2M response message. And may forward the SMS message content stored in the LwM2M response message data 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 MNO 1.

Step 975, the SM platform sends a profile deactivation notification to the operator MNO 2.

Optionally, in some embodiments, the IoT platform may also receive the profile download data sent by the application server (e.g., SM platform) before the IoT platform receives the activation information (SMs message) of the profile sent by the application server (e.g., SM platform).

In an embodiment of the present application, an application server (e.g., SM platform) may send an SMs message to an eUICC on an M2M communication device under an IoT network, thereby completing remote provisioning of user data on the eUICC.

A specific implementation manner of the IoT platform converting the profile download data into the LwM2M message under the LwM2M protocol in the embodiment of the present application is described in more detail below with reference to a specific example. It should be noted that the example of fig. 10 is only for assisting the skilled person in understanding the embodiments of the present application, and is not intended to limit the embodiments of the application to the specific values or specific scenarios illustrated. It will be apparent to those skilled in the art from the example of fig. 10 given herein that various equivalent modifications or variations may be made, and such modifications or variations are intended to fall within the scope of the embodiments of the present application.

Fig. 10 is a schematic flow chart of a method for transmitting eUICC data in the internet of things according to another embodiment of the present application. The method of FIG. 10 may include steps 1010 and 1070, which are described in detail below in relation to steps 1010 and 1070, respectively.

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

It should also be understood that fig. 10 is detailed with the example that the SM platform can be deployed separately from the IoT platform.

The process of downloading profile data shown in fig. 10 may include creating ISD-P (create ISD-P), establishing key (key initialization), and downloading profile (profile download).

The process of creating 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.

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

At step 1020, the IoT platform converts the ISD-P request message into an LwM2M message under the LwM2M protocol.

After receiving the request for creating the ISD-P sent by the SM platform, the IoT platform may determine whether the destination terminal device of the request message has the capability of parsing the target data or the profile download data sent to the eUICC.

As an example, if the destination terminal device has the capability of parsing the target data or the profile download data sent to the eUICC, and the network access type of the destination terminal is IoT. The IoT platform may convert the create ISD-P request message, organized as LwM2M app data container object, into an LwM2M message. As can be seen from the description of LwM2M app data container in table 1, the IoT platform may package the create ISD-P request message into the data of the LwM2Mapp data container object, and may set the data format to "create ISD-P Req".

At step 1025, the IoT platform sends an LwM2M message to the M2M communication device in the destination terminal device (as an LwM2M client).

In step 1030, the M2M communication device in the terminal equipment forwards the create ISD-P request Data in the Data to the eUICC in the destination terminal equipment according to the Data format (Data format) of the LwM2M message.

The M2M communication device in the terminal device may parse the received LwM2M message, and may send the data in the data of the LwM2M app datacontainer object to the eUICC in the terminal device through the local interface according to the data format of the LwM2M appdatacontainer object being "create ISD-P Req".

In step 1033, the M2M communication device in the terminal equipment sends create ISD-P request data to the eUICC.

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

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

in step 1040, the M2M communication device in the terminal device sends an LwM2M response message to the IoT platform.

The M2M communication device in the terminal device may pack the response message (create ISD-psp) into the data of the LwM2Mapp data container object, and may set the data format to "create ISD-psp Rsp".

The process of key establish is described in detail below in conjunction with steps 1045-.

In step 1045, the SM platform sends a create ISD-P key set Req create ISD-P key request message to the IoT platform (as LwM2M server).

At step 1050, the IoT platform converts the create ISD-P key request message into an LwM2M message under the LwM2M protocol.

After receiving the request for creating the ISD-P key sent by the SM platform, the IoT platform may determine whether the destination terminal device of the request message has the capability of parsing the target data sent to the eUICC or the profile download data.

As an example, if the destination terminal device has the capability of parsing the target data or the profile download data sent to the eUICC, and the network access type of the destination terminal is an IoT network. The IoT platform may convert the create ISD-P key request organized by LwM2M app data container object into an LwM2M message. As can be seen from the description of LwM2M app data container in table 1, the IoT platform may package the create ISD-P key request into the data of the LwM2M app data container object, may set the data format to "estabilishmid-P key set Req".

At step 1055, the IoT platform sends the LwM2M message to the M2M communication device in the destination terminal device (as LwM2M client).

In step 1060, the M2M communication device forwards the create ISD-P key request message Data in the Data to the eUICC in the destination terminal equipment according to the Data format of the LwM2M message.

The M2M communication device in the terminal equipment may parse the received LwM2M message, and may send the data in the data of the LwM2Mapp data container object to the eUICC in the terminal equipment through the local interface according to that the data format in the LwM2M appdata container object is "estabilish ISD-P key set Req".

Step 1063, the M2M communication device in the terminal equipment sends the create ISD-P key request data to the eUICC.

Step 1065, the M2M communication apparatus in the terminal device receives the create ISD-P key set Rsp returned by the eUICC.

In step 1068, the M2M communication device in the terminal equipment converts the response message (tastish ISD-P key setRsp) into an LwM2M response message.

In step 1070, the M2M communication device in the terminal equipment sends an LwM2M response message to the IoT platform.

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

The process of profile download is described in detail below in conjunction with steps 1075-.

At step 1075, the SM platform forwards the send data request (send dataReq) message to the IoT platform (as LwM2M server).

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

After receiving the data sending request message forwarded by the SM platform, the IoT platform may determine whether the destination terminal device of the request message has the capability of parsing the target data or the profile download data sent to the eUICC.

As an example, if the destination terminal device has the capability of parsing the target data or the profile download data sent to the eUICC, and the network access type of the destination terminal is an IoT network. The IoT platform may convert the send data request message, organized as LwM2M app data container object, into an LwM2M message. As can be seen from the description of LwM2M app data container in table 1, the IoT platform may package the send data request message into the data of LwM2Mapp data container object, and may set the data format to "send data Req".

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

Step 1090, the M2M communication device in the terminal equipment forwards the data in the data to the eUICC in the destination terminal equipment according to the data format of the LwM2M message.

Step 1093, the M2M communication device in the terminal equipment forwards the data to the eUICC in the destination terminal equipment.

The M2M communication device in the terminal equipment can parse the received LwM2M message, and according to the fact that the data format in the LwM2M appdata container object is "send data Req", the M2M communication device sends the data in the data of the LwM2Mapp data container object to the eUICC in the terminal equipment through the local interface.

In step 1095, the M2M communication device in the terminal equipment receives the eUICC return send data response message (send dataRsp).

In step 1098, the M2M communication device in the terminal equipment converts the response message (send data Rsp) into an LwM2M response message, and sends it to the IoT platform.

The M2M communication device in the terminal apparatus may pack a response message (send data Rsp) into data of LwM2M appdata container object, and may set the data format to "send data Rsp".

In step 1099, the M2M communicator in the terminal device sends an LwM2M response message to the IoT platform.

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

In the following, with reference to the number of interactive messages in fig. 11-12, how to reduce interactive messages between the eUICC and the application server (e.g., SM platform) in the embodiment of the present application is described in detail, so as to improve transmission efficiency of the network.

Fig. 11 is a diagram illustrating 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 completing the remote configuration of the user data on the eUICC, the number of times of the interactive messages between the eUICC and the application server is 13. The interactive messages between the eUICC and the application server are respectively: 1 SMS request establish connection message, 3 handshakes (transmission control protocol, TCP)) message, 1 createISD-P Req message, 1 create ISD-P Rsp message, 1 interest ISD-P key set Req message, 1 interest ISD-P key set Rsp message, 1 sense data Req message, 1 sense data Rsp message, 3 profile activation messages (e.g., 1 SMS enabled profile Rsp message, 1 SMS enabled profile Req message, 1 SMS handle default message).

As shown in fig. 12, in the process of completing the remote configuration of the user data on the eUICC, the number of times of the interactive messages between the eUICC and the application server is 9. The interactive messages between the eUICC and the application server are respectively: 1 create ISD-PReq message, 1 create ISD-P Rsp message, 1 estabilish ISD-P key set Req message, 1 estabilish ISD-P key set Rsp message, 1 send data Req message, 1 send data Rsp message, 3 profile activation messages (e.g., 1 SMS enabled profile Rsp message, 1 SMS enabled profile Req message, 1 SMS handle default notification message).

Therefore, in the process of completing remote configuration of user data on the eUICC (completing profile downloading and activating processes), before the method for transmitting eUICC data in the internet of things provided by the embodiment of the present application is used, the number of times of interactive messages between the eUICC and the application server is 13. After the method for transmitting the eUICC data in the Internet of things provided by the embodiment of the application is used, the number of times of message interaction between the eUICC and the application server is 9. 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 in the embodiment of the present invention is described in detail above with reference to fig. 1 to 12, and the apparatus embodiment of the present application is described in detail below with reference to fig. 13 to 15. It is to be understood that the description of the method embodiments corresponds to the description of the apparatus embodiments, and therefore reference may be made to the preceding method embodiments for parts not described in detail.

Fig. 13 shows a schematic block diagram of an internet of things IoT platform 1300 according to an embodiment of the present disclosure, where each module in the IoT platform 1300 is respectively configured to perform each action or process performed by the IoT platform in the foregoing method, and here, for avoiding redundancy, detailed description may refer to the description above.

Fig. 13 is a schematic block diagram of an IoT platform 1300 provided by an embodiment of the present application. The IoT platform 1300 may include:

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

a first processing module 1320, configured to, in a case that the communication network does not support a transceiving function of an SMS message, convert an SMS message to be sent to the terminal device into a first lightweight machine to machine LwM2M message, where the SMS message includes target data to be sent to an 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 an SMS;

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

Optionally, in some embodiments, the SMS message to the terminal device is from an application server, the IoT platform 1300 further comprises, before converting the SMS message to the terminal device into the first lightweight machine-to-machine LwM2M message:

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

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

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

a second obtaining module 1350, configured to obtain the SMS message transceiving capability of the terminal device;

a second processing module 1360, configured to, in a case where the terminal device supports a function of transceiving SMS messages and the communication network does not support a function of transceiving SMS messages, convert the SMS messages into the first LwM2M message.

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

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

Optionally, in some embodiments, the target data includes profile activation information of a target operator of the eUICC in the terminal device, where the profile activation information is used to activate the profile of the target operator downloaded in the eUICC.

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 comprises:

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

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

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

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

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

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

and determining that the terminal equipment has the capability of analyzing the target data or the profile download data sent to the eUICC according to the indication bit.

According to the IoT platform 1300 provided in the embodiment of the present application, since the message header of the LwM2M protocol is smaller than that of the HTTPS, and the LwM2M protocol can establish a session between the IoT platform of the internet of things (serving as the server) and the M2M communication device (serving as the client) on the terminal device without multiple handshakes. Thus, in an IoT network, a session between an application server (e.g., SM platform) and the eUICC on the terminal device can be established via the LwM2M protocol, and the data format of the LwM2M message can be set, under which the application server can send SMs messages to the eUICC on the M2M communication device, thereby completing the remote provisioning of user data on the eUICC.

Fig. 14 shows a schematic block diagram of a terminal device according to an embodiment of the present application, where each module in the terminal device 1400 is respectively configured to execute each action or processing procedure executed by the terminal device in the foregoing method, and here, for avoiding repeated descriptions, detailed descriptions may refer to the description above.

Fig. 14 is a schematic block diagram of a terminal device 1400 provided in an embodiment of the present application. The terminal device 1400 may include:

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

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

a second sending module 1430, configured to send the target data to the eUICC by the short message module.

Optionally, in some embodiments, the terminal device is provided with one or more of the following capabilities: the capability of SMS messaging, the capability of analyzing target data sent to the eUICC, and the capability of analyzing profile download data sent to the eUICC.

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 internet of things IoT platform, where the second LwM2M message includes profile download data of a target operator of the eUICC sent by the application server;

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

according to the terminal device 1400 provided by the embodiment of the application, the message header of the LwM2M protocol is smaller than that of the HTTPS, and the LwM2M protocol can establish a session between the IoT platform of the internet of things (serving as the server farm) and the M2M communication device (serving as the client) on the terminal device without multiple handshakes. Thus, in an IoT network, a session between an application server (e.g., SM platform) and the eUICC on the terminal device can be established via the LwM2M protocol, and the data format of the LwM2M message can be set, under which the application server can send SMs messages to the eUICC on the M2M communication device, thereby completing the remote provisioning of user data on the eUICC.

Fig. 15 is a schematic block diagram of an internet of things IoT platform 1500 provided in 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 coupled to the receiver 1502 and the transmitter 1503. The memory 1504 may be used to store program codes and data for the network device. Therefore, the memory 1504 may be a storage unit inside the processor 1501, an external storage unit independent of the processor 1501, or a component including a storage unit inside the processor 1501 and an external storage unit independent of the processor 1501.

Optionally, IoT platform 1500 may also include a bus 1505. Wherein the receiver 1502, transmitter 1503, and memory 1504 may be coupled to the processor 1501 by bus 1505; the bus 1505 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. The bus 1505 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 15, but this is not intended to represent only one bus or 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 (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others.

The receiver 1502 and transmitter 1503 may be circuits that include the above-described antenna and transmitter and receiver chains, which may be separate circuits or the same circuit.

When the program is executed, the processor 1501 is configured to: acquiring the sending and receiving capacity of an SMS message of a communication network, wherein the IoT platform is communicated with terminal equipment through the communication network;

the processor 1501 is further configured to: for converting an SMS message to be sent to the terminal device into a first lightweight machine-to-machine, LwM2M, message, the SMS message including target data to be sent to an embedded universal integrated circuit card, eUICC, in the terminal device, in case the communication network does not support transceiving functionality for SMS messages, the data format of the target data included in the first LwM2M message being SMS;

the transmitter 1503 is configured to: and sending the first LwM2M message to a terminal device.

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

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

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

processor 1501 is also configured to: acquiring the transmitting and receiving capacity of the SMS message of the terminal equipment;

processor 1501 is also configured to: in case the terminal device supports the transceiving function of SMS messages and the communication network does not support the transceiving function of SMS messages, converting the SMS messages into the first LwM2M message.

Optionally, in some embodiments, the processor 1501 is specifically configured to: sending an LwM2M request message to a terminal device, wherein the LwM2M request message is used for requesting to acquire the transceiving capacity of the SMS message of the terminal device;

the receiver 1502 is specifically configured to: and receiving a response message to the LwM2M request message, which is sent by the terminal equipment, wherein the response message comprises indication information of the SMS messaging capability of the terminal equipment.

Optionally, in some embodiments, the processor 1501 specifically executes, by the receiver 1502: receiving LwM2M registration information sent by the terminal device, wherein the LwM2M registration information comprises indication information of transceiving capacity of the SMS message of the terminal device;

the processor 1501 is specifically configured to: and determining the sending and receiving capabilities of the SMS message of the terminal equipment according to the indication information in the LwM2M registration information.

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 further performs, through the receiver 1502: receiving a request message sent by the application server, wherein the request message comprises profile download data of a target operator of the eUICC issued by the application server;

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

the transmitter 1503 is specifically configured to: sending the second LwM2M message to the terminal device.

Optionally, in some embodiments, the processor 1501 in the IoT platform 1500 is further configured to: and determining that the terminal equipment has the capability of analyzing the target data or the profile download data sent to the eUICC.

Optionally, in some embodiments, the processor 1501 is specifically configured to execute, by the receiver 1502: receiving 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 that the terminal device has a capability of parsing target data or profile download data sent to the eUICC;

the processor 1501 is specifically configured to: and determining that the terminal equipment has the capability of analyzing the target data or the profile download data sent to the eUICC according to the indicated bit.

The terminal device according to the embodiment of the present application may refer to a schematic structure diagram of the terminal device 330 shown in fig. 4. The terminal device 330 may include: machine-to-machine M2M communication means 420, wireless transceiver 430, short message module 490, embedded universal integrated circuit card eUICC 480.

Wherein the M2M communication device 420 performs the following operations through the wireless transceiver 430: receiving a first LwM2M message sent by an IoT platform, wherein the first LwM2M message includes target data issued by an application server to an eUICC (embedded universal integrated circuit card) in the terminal equipment, and a data format of the target data of the eUICC included in the first LwM2M message is a Short Message Service (SMS);

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

the short message module 490 is configured to: and sending the target data to the eUICC.

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

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

Optionally, in some embodiments, the terminal device 330 is provided with one or more of the following capabilities: the capability of SMS messaging, the capability of analyzing target data sent to the eUICC, and the capability of analyzing profile download data sent to the eUICC.

Embodiments of the present application also provide a computer-readable medium for storing a computer program, where the computer program includes instructions for executing each action or process performed by the IoT platform in the above-described 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 executing each action or processing procedure executed by the terminal device in the foregoing method.

An embodiment of the present application further provides a computer program product, where the computer program product includes: computer program code which, when run by a computer, causes the computer to perform the actions or processes performed by the IoT platform in the above-described method.

An embodiment of the present application further provides a computer program product, where the computer program product includes: computer program code which, when run by a computer, causes the computer to perform the actions or processes performed by the terminal device in the above-described method.

An embodiment of the present application further provides a chip system, which is applied to a communication device, and the chip system includes: the chip system comprises at least one processor, at least one memory and an interface circuit, wherein the interface circuit is responsible for information interaction between the chip system and the outside, the at least one memory, the interface circuit and the at least one processor are interconnected through lines, and instructions are stored in the at least one memory; the instructions are executed by the at least one processor to perform the actions or processes performed by the oT platform in the above-described method.

An embodiment of the present application further provides a chip system, which is applied to a communication device, and the chip system includes: the chip system comprises at least one processor, at least one memory and an interface circuit, wherein the interface circuit is responsible for information interaction between the chip system and the outside, the at least one memory, the interface circuit and the at least one processor are interconnected through lines, and instructions are stored in the at least one memory; the instructions are executed by the at least one processor to perform the actions or processes performed by the terminal device in the above-described method.

As used in this application, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on 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 the computing device can be a component. 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. The components may communicate by way of local and/or remote processes based on a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, and/or across a network, such as the internet with other systems by way of the signal).

It should be understood that the manner, the case, the category, and the division of the embodiments are only for convenience of description and should not be construed as a particular limitation, and features in various manners, the category, the case, and the embodiments may be combined without contradiction.

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

Additionally, the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in 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, from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for transmitting eUICC data in the Internet of things is characterized by comprising the following steps:

the method comprises the steps that an IoT platform of the Internet of things acquires the transceiving capacity of a Short Message Service (SMS) message of a communication network, and the IoT platform communicates with terminal equipment through the communication network;

the IoT platform converts an SMS message to be sent to the terminal equipment into a first lightweight machine-to-machine (LwM 2M) message if the communication network does not support transceiving function of the SMS message, wherein the SMS message comprises target data sent to an embedded universal integrated circuit card (eUICC) in the terminal equipment, and the data format of the target data included in the first LwM2M message is an SMS format;

the IoT platform sends the first LwM2M message to the terminal device.

2. The method of claim 1, wherein the SMS message to the terminal device is from an application server, wherein the IoT platform is prior to converting the SMS message to the terminal device into a first lightweight machine-to-machine (LwM 2M) message, wherein the method further comprises,

the IoT platform receives the SMS message sent by an application server.

3. The method of claim 1 or 2, wherein prior to the IoT platform converting the SMS message into the first lightweight machine-to-machine LwM2M message, the method further comprises:

the IoT platform acquires the sending and receiving capacity of the SMS message of the terminal equipment; the IoT platform, when the communication network does not support the SMS messaging function, converts an SMS message to be sent to the terminal device into a first LwM2M message, which specifically includes:

the IoT platform converts an SMS message to be sent to the terminal device into a first LwM2M message if the communication network does not support the messaging functionality of SMS messages and the terminal device supports the messaging functionality of SMS messages.

4. The method of claim 3, wherein the IoT platform obtains the SMS messaging capability of the terminal device, comprising:

the IoT platform sends an LwM2M request message to the terminal device, wherein the LwM2M request message is used for requesting to acquire the transceiving capacity of the SMS message of the terminal device;

the IoT platform receives a response message sent by the terminal device to the LwM2M request message, wherein the response message comprises indication information of the SMS messaging capability of the terminal device.

5. The method of claim 3, wherein the IoT platform obtains the SMS messaging capability of the terminal device, comprising:

the IoT platform receives LwM2M registration information sent by the terminal device, the LwM2M registration information including information indicative of SMS messaging capabilities of the terminal device.

6. The method of any one of claims 1 to 5. Wherein the IoT platform obtains the sending and receiving capability of the SMS message of the communication network, and comprises:

and the IoT platform acquires the transceiving capacity of the SMS message of the communication network through a service capacity open network element (SCEF).

7. The method according to any one of claims 1 to 6, wherein the target data includes profile activation information of a target operator issued to the eUICC in the terminal device, and the profile activation information is used for activating the profile of the target operator in the eUICC.

8. The method of claim 7, wherein before the internet of things (IoT) platform sends the first LwM2M message to the terminal device, the method further comprises:

and the IoT platform sends a second LwM2M message to the terminal equipment, wherein the second LwM2M message comprises profile download data of a target operator of the eUICC in the terminal equipment.

9. The method of any of claims 1-8, prior to the IoT platform sending the first LwM2M message or the second LwM2M message to the terminal device, the method further comprising:

10. The method of claim 9, wherein the determining, by the IoT platform, that the terminal device has the capability to parse the target data or the profile download data sent to the eUICC comprises:

the IoT platform receives a third LwM2M message sent by the terminal device, wherein the third LwM2M message includes an indication bit, and the indication bit is used for indicating whether the terminal device has the capability of resolving the target data or the profile download data sent to the eUICC;

11. A method for transmitting eUICC data in the Internet of things is characterized by comprising the following steps:

the method comprises the steps that a terminal device receives a first LwM2M message sent by an IoT platform, wherein the first LwM2M message comprises target data issued to an eUICC (embedded universal integrated circuit card) in the terminal device, and the data format of the target data of the eUICC included in the first LwM2M message is a Short Message Service (SMS);

and the terminal equipment sends the target data to the eUICC according to the data format of the target data included in the first LwM2M message.

12. The method of claim 10, wherein before the terminal device receives a first lightweight machine-to-machine (LwM 2M) message sent by an Internet of things (IoT) platform, the method further comprises:

the terminal equipment receives a second LwM2M message sent by the IoT platform, wherein the second LwM2M message comprises profile download data of a target operator issued to the eUICC;

and the terminal equipment sends the second LwM2M message to the eUICC.

13. The method according to claim 11 or 12, wherein the terminal device is capable of one or more of the following capabilities: the capability of SMS messaging, the capability of analyzing target data sent to the eUICC, and the capability of analyzing profile download data sent to the eUICC.

14. An internet of things (IoT) platform, the platform comprising: a receiver, a transmitter, a memory, and a processor,

the receiver is used for receiving messages or data sent by a device outside the IoT platform and forwarding the messages or data to the processor;

the transmitter is used for transmitting messages or data to a device outside the IoT platform according to the instructions of the processor;

the memory is used for storing programs;

the processor is to execute a program stored in the memory, which when executed, the IoT platform performs the method of any of claims 1-10.

15. A terminal device, characterized in that the terminal device comprises: machine-to-machine M2M communication means, transceiver, short message module, embedded universal integrated circuit card eUICC,

the M2M communication device performing the following operations by the transceiver: receiving a first LwM2M message sent by an IoT (Internet of things) platform, wherein the first LwM2M message comprises target data issued to an eUICC (embedded universal integrated circuit card) in the terminal equipment, and the data format of the target data of the eUICC included in the first LwM2M message is a Short Message Service (SMS);

the short message module is used for: and sending the target data to the eUICC.

16. The terminal device of claim 15, wherein the M2M communication means further performs the following operations by the transceiver: receiving a second LwM2M message sent by the IoT platform, wherein the second LwM2M message comprises profile download data of a target operator issued to the eUICC;

17. The terminal device according to claim 15 or 16, characterized in that the terminal device is provided with one or more of the following capabilities: the capability of SMS messaging, the capability of analyzing target data sent to the eUICC, and the capability of analyzing profile download data sent to the eUICC.

18. A computer readable storage medium comprising computer instructions which, when run on a computer, cause the computer to perform the method of any of claims 1 to 13.