WO2019233275A1 - 一种窄带物联网中eUICC数据传输方法和装置 - Google Patents

一种窄带物联网中eUICC数据传输方法和装置 Download PDF

Info

Publication number
WO2019233275A1
WO2019233275A1 PCT/CN2019/087768 CN2019087768W WO2019233275A1 WO 2019233275 A1 WO2019233275 A1 WO 2019233275A1 CN 2019087768 W CN2019087768 W CN 2019087768W WO 2019233275 A1 WO2019233275 A1 WO 2019233275A1
Authority
WO
WIPO (PCT)
Prior art keywords
euicc
lwm2m
communication device
message
platform
Prior art date
Application number
PCT/CN2019/087768
Other languages
English (en)
French (fr)
Inventor
徐蓓
张永靖
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019233275A1 publication Critical patent/WO2019233275A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • the present application relates to the field of communications, and more particularly, to a method and device for transmitting eUICC data in a narrowband Internet of Things.
  • the embedded universal integrated circuit (eUICC) standard developed by the Global Mobile Communications Alliance system (global system for mobile communications communications, GSMA) allows remote configuration of user data on the eUICC, such as eUICC downloading users remotely from an application server User data contracted on a certain operator network, and then the user equipment configured with the eUICC accesses the operator's communication network.
  • eUICC embedded universal integrated circuit
  • the bandwidth and transmission rate of NB-IoT networks are low to achieve wide coverage and low power consumption.
  • Most of the existing transmission protocols are not suitable for data transmission in the NB-IoT network.
  • HTTPS Hypertext Transfer Protocol
  • the HTTPS three-way handshake protocol has timer protection, and the NB-IoT network has a low rate, which causes the timer to time out, it is not suitable to establish a session between the application server and the eUICC through HTTPS under the NB-IoT network.
  • the present application provides a method and device for transmitting eUICC data in a narrowband Internet of Things.
  • a session between an application server and an eUICC on an M2M communication device can be established under the NB-IoT network, thereby completing data transmission.
  • a method for transmitting eUICC data in a narrowband Internet of Things includes: a machine-to-machine M2M communication device receives a lightweight machine-to-machine LwM2M message sent by the Internet of Things IoT platform.
  • the LwM2M message may include application instructions and target data sent to the embedded universal integrated circuit card eUICC by the subscription management SM platform, and the application instructions are used to indicate that the communication is the SM platform and the eUICC. Communication between applications on the Internet; the M2M communication device sends the LwM2M message to the eUICC associated therewith; the eUICC sends target data in the LwM2M message to the eUICC according to the application instruction Application.
  • the target data in the LwM2M message delivered by the IoT platform may include the profile of the target operator issued by the subscription management SM platform to the eUICC or the activation information of the profile.
  • the eUICC may The profile activation information described above completes the download or activation of the target operator profile.
  • the target data in the LwM2M message issued by the IoT platform can be configured with information.
  • the eUICC can perform corresponding configuration according to the received configuration information.
  • the M2M communication device may send the LwM2M message to the eUICC associated with the M2M communication device, and the application server may perform data transmission with the eUICC on the M2M terminal through the IoT platform under the LwM2M protocol.
  • the target data in the LwM2M message issued by the IoT platform includes a profile of the target operator issued by the subscription management SM platform to the eUICC or activation information of the profile.
  • the M2M communication device is associated with the eUICC
  • the LwM2M message includes an application identifier and download or activation information of the target operator's profile
  • an application instruction is used to instruct the eUICC to link the target operator's
  • the download or activation information of the profile is forwarded to the application on the eUICC.
  • the request message includes the download or activation information of the profile of the embedded universal integrated circuit card eUICC that needs to be switched from the current operator to the target operator.
  • the IoT platform can convert the request message sent by the SM platform to an LwM2M message under the LwM2M protocol. After the request message sent by the SM platform is converted into an LwM2M message, the message format (DataFormat) corresponding to the LwM2M message can be consistent with the request message.
  • DataFormat the message format (DataFormat) corresponding to the LwM2M message
  • the embodiment of the present application does not specifically limit an implementation manner in which the IoT platform sends an LwM2M message to the M2M communication device.
  • the IoT platform may send the LwM2M message to the M2M communication device, and the M2M communication device may forward the LwM2M message to the target eUICC according to the application instruction in the LwM2M message.
  • the IoT platform may send the LwM2M message to the M2M communication device.
  • the M2M communication device may send the LwM2M message to the client module of the M2M communication device according to the first identification in the first LwM2M message.
  • the client module may send the first LwM2M message to the server module of the M2M communication device, and the server module of the M2M communication device may send the first LwM2M message to the target eUICC.
  • the eUICC can be made to support LwM2M to complete the download and activation of the profile.
  • the LwM2M message further includes a first identifier.
  • the first identifier may be used to instruct the M2M communication device to forward the download or activation information of the target operator's profile to the eUICC.
  • the eUICC may forward the download or activation information of the profile of the target operator in the LwM2M message to the application App on the eUICC according to the application instruction in the LwM2M message.
  • the IoT platform receives a first LwM2M registration request sent by the M2M communication device.
  • the first LwM2M registration request is used by the eUICC to request LwM2M registration with the IoT platform.
  • the first LwM2M registration request includes a first identifier, and the first identifier is used to indicate that the first LwM2M registration request is Sent by eUICC's LwM2M client.
  • the eUICC can request LwM2M registration directly to the IoT platform.
  • the M2M communication device can forward the first LwM2M registration information requested by the eUICC to the IoT platform for registration to the IoT platform, the M2M The communication device may be said to support the LwM2M GW route mode.
  • the first identifier may be used to instruct the M2M communication device to send the LwM2M request message sent by the IoT platform to the eUICC.
  • the first identifier may be used to indicate the IoT platform.
  • the LwM2M registration request message sent by the M2M communication device may include an eUICC request for LwM2M registration with the IoT platform.
  • the M2M communication device can be enabled to support LwM2M and GW routing through pre-configuration, eUICC supports the LwM2M protocol, and the IoT platform supports the LwM2M protocol.
  • the method before the IoT platform sends the first LwM2M message to a machine M2M communication device, the method further includes: the IoT platform receives the M2M communication device sent First LwM2M registration request.
  • the eUICC may request LwM2M registration from the M2M communication device, and the M2M communication device may request LwM2M registration with the IoT platform, so that the eUICC can download and activate the profile according to the profile sent by the SM platform to complete the download and activation of the profile.
  • the M2M communication device may be referred to as supporting a LwM2M GW proxy mode.
  • the M2M communication device can be configured to support the LwM2M GW proxy mode through pre-configuration, the eUICC supports the LwM2M protocol, and the IoT platform supports the LwM2M protocol.
  • the method before the IoT platform sends the first LwM2M message to a machine M2M communication device, the method further includes: the IoT platform receives a client of the M2M communication device The second LwM2M registration request sent by the module.
  • the second LwM2M registration request is used by the M2M communication device to request LwM2M registration with the IoT platform.
  • the method further includes: receiving, by the M2M communication device, a response message sent by the eUICC.
  • the response message is a response result of an application on the eUICC to a request message sent by the SM platform
  • the response message includes an application indication and a first identifier
  • the first identifier is used to indicate that the A response message is sent to the IoT platform
  • the application instruction is used to instruct to return the response message to the SM platform.
  • a method for transmitting eUICC data in a narrowband Internet of Things includes: a machine-to-machine M2M communication device receives a lightweight machine-to-machine LwM2M message sent by the Internet of Things IoT platform, the LwM2M message includes an application instruction and The contract management manages target data sent to the embedded universal integrated circuit card eUICC by the SM platform, and the application indication is used to indicate that this communication is communication between the SM platform and an application on the eUICC; the M2M communication device Sending the LwM2M message to the eUICC associated with it.
  • the M2M communication device may send the LwM2M message to the eUICC associated with the M2M communication device, and the application server may perform data transmission with the eUICC on the M2M terminal through the IoT platform under the LwM2M protocol.
  • the first LwM2M message includes application instructions and download or activation information of a profile of a target operator issued by a subscription management SM platform, and the M2M
  • the communication device is associated with an embedded universal integrated circuit card eUICC, the eUICC needs to be switched from the current operator to the target operator, and the application instruction is used to instruct the eUICC to download the profile of the target operator or The activation information is forwarded to the application on the eUICC.
  • the M2M communication device sends the profile issued by the SM or the activation information of the profile to the eUICC according to an application instruction in the LwM2M message.
  • the method further includes: the M2M communication device receives the response message sent by the eUICC; and the M2M communication device will receive all the received messages according to the application instruction.
  • the response message is sent to the SM platform.
  • the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform, and the response message includes the application indication.
  • the LwM2M message further includes a first first identifier, where the first identifier is used to indicate communication between the IoT platform and the eUICC .
  • the M2M communication device sends the profile or the activation information of the profile to the eUICC according to a first first identifier in the LwM2M message.
  • the M2M communication device receives the response message sent by the eUICC; the M2M communication device sends the response message to the SM platform.
  • the response message includes the application indication and the first identifier.
  • the method before the M2M communication device sends the profile or the activation information of the profile to the eUICC, the method further includes: the M2M communication device receives The LwM2M registration request sent by the eUICC; the M2M communication device sends the LwM2M registration request to the IoT platform, and the LwM2M registration request includes the first identifier.
  • the LwM2M registration request is used by the eUICC to request LwM2M registration with the IoT platform.
  • a method for transmitting eUICC data in a narrowband Internet of Things includes: a lightweight machine-to-machine LwM2M message sent by an embedded universal integrated circuit card eUICC receiver to a machine M2M communication device, and the LwM2M message includes Application instruction and contract management target data sent to the eUICC by the SM platform, the application instruction is used to indicate that this communication is communication between the SM platform and an application on the eUICC, and the eUICC communicates with the M2M Device association; the eUICC sends the target data in the LwM2M message to an application on the eUICC according to the application instruction.
  • the target data includes a profile of the target operator delivered to the eUICC by the subscription management SM platform or activation information of the profile.
  • the first LwM2M message includes an application instruction and a profile of a target operator issued by a subscription management SM platform or activation information of the profile, and the profile or activation information of the profile is used to indicate
  • the embedded universal integrated circuit card eUICC is switched from the current operator to the target operator, and the application instruction is used to instruct communication between the SM platform and an application on the eUICC.
  • the method further includes: the eUICC sends a response message to the machine-to-machine M2M communication device.
  • the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform, and the response message includes the application indication.
  • the method further includes: the eUICC sends an LwM2M registration request to the M2M communication device.
  • the LwM2M registration request is used by the eUICC to request LwM2M registration with an IoT IoT platform, or used by the eUICC to request LwM2M registration with the IoT platform.
  • a method for transmitting eUICC data in a narrowband Internet of Things includes: the Internet of Things IoT platform receives a request message sent by the contract management SM platform, where the request message includes an application instruction and the contract management SM platform sends the request message to the The target data of the eUICC, the application indication is used to indicate that this communication is a communication between the SM platform and an application on the eUICC; the IoT platform converts the request message into a lightweight machine-to-machine LwM2M message The IoT platform sends the LwM2M message to a machine-to-machine M2M communication device, and the M2M communication device is associated with the eUICC.
  • the target data includes a profile of the target operator issued by the subscription management SM platform to the eUICC or activation information of the profile.
  • the request message includes a profile of a target operator or activation information of the profile, and the profile or activation information of the profile is used to instruct an embedded universal integrated circuit card eUICC to switch from a current operator. To the target operator.
  • the aforementioned LwM2M message includes an application indication and activation information of the profile or the profile, and the application indication is used to instruct communication between the SM platform and an application on the eUICC.
  • the IoT platform can convert the request message sent by the SM platform to an LwM2M message under the LwM2M protocol. After the request message sent by the SM platform is converted into an LwM2M message, the message format (DataFormat) corresponding to the LwM2M message can be consistent with the request message.
  • DataFormat the message format (DataFormat) corresponding to the LwM2M message
  • the embodiment of the present application does not specifically limit an implementation manner in which the IoT platform sends an LwM2M message to the M2M communication device.
  • the IoT platform may send the LwM2M message to the M2M communication device, and the M2M communication device may forward the LwM2M message to the target eUICC according to the application instruction in the LwM2M message.
  • the IoT platform may send the LwM2M message to the M2M communication device.
  • the M2M communication device may send the LwM2M message to the client module of the M2M communication device according to the first first identifier in the LwM2M message.
  • the client module may send the LwM2M message to the server module of the M2M communication device, and the server module of the M2M communication device may send the LwM2M message to the target eUICC.
  • the eUICC can be made to support LwM2M to complete the download and activation of the profile.
  • the method further includes: the IoT platform receives a response message sent by the M2M communication device; and the IoT platform sends all the information according to the application instruction.
  • the response message is sent to the SM platform.
  • the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform, and the response message includes the application indication.
  • the LwM2M message further includes a first first identifier, and the first first identifier is used to indicate communication between the IoT platform and the eUICC.
  • the method before the IoT platform sends the LwM2M message to a machine-to-machine M2M communication device, the method further includes: the IoT platform receives a message sent by the M2M communication device LwM2M registration request.
  • the LwM2M registration request is used by the eUICC to request LwM2M registration with the IoT platform, and the LwM2M registration request includes the first identifier.
  • the eUICC can request LwM2M registration directly to the IoT platform.
  • the M2M communication device can forward the LwM2M registration information requested by the eUICC to the IoT platform to the IoT platform, and the M2M communication device It can be said to support the LwM2M GW route mode.
  • the first identifier may be used to instruct the M2M communication device to send the LwM2M request message sent by the IoT platform to the eUICC.
  • the first identifier may be used to indicate the IoT platform.
  • the LwM2M registration request message sent by the M2M communication device may include an eUICC request for LwM2M registration with the IoT platform.
  • the method further includes: receiving, by the IoT platform, a response message sent by the M2M communication device, where the response message includes the application indication and the first first Identification; said sending said response message to said SM platform according to said application instruction.
  • a machine-to-machine M2M communication device includes an embedded universal integrated circuit card eUICC, and the M2M communication device includes:
  • a first receiving module configured to receive a lightweight machine-to-machine LwM2M message sent by the Internet of Things IoT platform, where the LwM2M message includes application instructions and contract management SM platform target data sent to the embedded universal integrated circuit card eUICC;
  • the application indication is used to indicate that this communication is communication between the SM platform and an application on the eUICC;
  • a first sending module configured to send the LwM2M message to the eUICC associated with the LwM2M message
  • the second sending module is used for the eUICC to send the target data in the LwM2M message to the application on the eUICC according to the application instruction.
  • the target data includes a profile of the target operator issued by the subscription management SM platform to the eUICC or activation information of the profile.
  • the first sending module is specifically configured to send the profile issued by the SM or the activation information of the profile to the according to an application instruction in the LwM2M message. eUICC.
  • the M2M communication device further includes:
  • a third sending module configured to send a response message to the M2M communication device, where the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform, and the response
  • the message includes the application indication
  • a fourth sending module is configured to send the received response message to the SM platform according to the application instruction.
  • the LwM2M message further includes a first identifier, where the first identifier is used to indicate communication between the IoT platform and the eUICC.
  • the first sending module is specifically configured to send the profile or the activation information of the profile to the eUICC according to a first identifier in the first LwM2M message.
  • the M2M communication device further includes:
  • a fifth sending module configured for an application on the eUICC to send the response message to the M2M communication device
  • a sixth sending module is configured to send the response message to the SM platform, wherein the response message includes the application indication and the first identifier.
  • the M2M communication device further includes:
  • a seventh sending module configured for the eUICC to send an LwM2M registration request to the M2M communication device, and the LwM2M registration request is used for the eUICC to request LwM2M registration with the IoT platform;
  • An eighth sending module is configured for the M2M communication device to send the received LwM2M registration request to the IoT platform, and the LwM2M registration request includes the first identifier.
  • a machine-to-machine M2M communication device includes:
  • a first receiving module configured to receive a lightweight machine-to-machine LwM2M message sent by the Internet of Things IoT platform, where the LwM2M message includes application instructions and contract management SM platform target data sent to the embedded universal integrated circuit card eUICC;
  • the application indication is used to indicate that this communication is communication between the SM platform and an application on the eUICC;
  • a first sending module configured to send the LwM2M message to the eUICC associated with the LwM2M message.
  • the target data includes a profile of the target operator sent to the eUICC by the subscription management SM platform or activation information of the profile.
  • the first sending module is specifically configured to: according to an application instruction in the LwM2M message, send the profile issued by the SM or the activation information of the profile to the eUICC.
  • the M2M communication device further includes:
  • a second receiving module configured to receive the response message sent by the eUICC, where the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform, the The response message includes the application indication;
  • a second sending module is configured to send the received response message to the SM platform according to the application instruction.
  • the LwM2M message further includes a first first identifier, and the first identifier is used to indicate communication between the IoT platform and the eUICC.
  • the first sending module is specifically configured to send the profile or the activation information of the profile to the eUICC according to a first identifier in the LwM2M message.
  • the M2M communication device further includes:
  • a third receiving module configured to receive the response message sent by the eUICC
  • a third sending module is configured to send the response message to the SM platform, wherein the response message includes the application indication and the first identifier.
  • the M2M communication device further includes:
  • a fourth receiving module configured to receive an LwM2M registration request sent by the eUICC, where the LwM2M registration request is used by the eUICC to request LwM2M registration with the IoT platform;
  • a fourth sending module is configured to send the LwM2M registration request to the IoT platform, where the LwM2M registration request includes the first identifier.
  • an embedded universal integrated circuit card eUICC includes:
  • the first receiving module is used for a lightweight machine-to-machine LwM2M message sent by the receiver-to-machine M2M communication device.
  • the LwM2M message includes an application instruction and target data sent to the eUICC by the subscription management SM platform.
  • the application instruction is used for Indicates that the communication is communication between the SM platform and an application on the eUICC, and the eUICC is associated with the M2M communication device;
  • a first sending module configured to send the target data in the LwM2M message to an application on the eUICC according to the application instruction.
  • the target data includes a profile of the target operator sent to the eUICC by the subscription management SM platform or activation information of the profile.
  • the eUICC further includes:
  • a second sending module configured to send a response message to the machine-to-machine M2M communication device, where the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform,
  • the response message includes the application indication.
  • the eUICC further includes:
  • a third sending module configured to send an LwM2M registration request to the M2M communication device, the LwM2M registration request is used for the eUICC request for LwM2M registration with an IoT IoT platform, or for the eUICC request for the IoT platform Perform LwM2M registration.
  • an IoT IoT platform is provided, and the platform includes:
  • the first receiving module is configured to receive a request message sent by the subscription management SM platform, where the request message includes an application instruction and target data sent to the eUICC by the subscription management SM platform, and the application instruction is used to indicate that the communication is the Communication between an SM platform and an application on the eUICC;
  • a processing module configured to convert the request message into a first lightweight machine-to-machine LwM2M message
  • a first sending module is configured to send the LwM2M message to a machine-to-machine M2M communication device, and the M2M communication device is associated with the eUICC.
  • the target data includes a profile of the target operator sent to the eUICC by the subscription management SM platform or activation information of the profile.
  • the platform further includes:
  • a second receiving module configured to receive a response message sent by the M2M communication device, where the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform;
  • the response message includes the application indication;
  • a second sending module is configured to send the response message to the SM platform according to the application instruction.
  • the LwM2M message further includes a first identifier, where the first identifier is used to indicate communication between the IoT platform and the eUICC.
  • the platform further includes:
  • a third receiving module is configured to receive an LwM2M registration request sent by the M2M communication device, the LwM2M registration request is used by the eUICC to request LwM2M registration with the IoT platform, and the LwM2M registration request includes the first identifier .
  • the platform further includes:
  • a fourth receiving module configured to receive a response message sent by the M2M communication device, where the response message includes the application indication and the first identifier;
  • a third sending module configured to send the response message to the SM platform according to the application instruction.
  • a machine-to-machine M2M communication device includes an embedded universal integrated circuit card eUICC, and the M2M communication device includes a receiver, a transmitter, a memory, and a processor.
  • eUICC embedded universal integrated circuit card
  • a machine-to-machine M2M communication device including: a receiver, a transmitter, a memory, and a processor.
  • the receiver, the transmitter, and the memory communicate with each other through an internal connection path.
  • the receiver is configured to receive a message or data sent by a device other than the M2M communication device, and forward the message or data to the processor; and the transmitter is configured to send a message or data to the device.
  • the device sends a message or data;
  • the memory is used to store a program;
  • the processor is used to execute a program stored in the memory; when the program is executed, the M2M communication device executes the second aspect or the second aspect Method in any of the possible implementations of the aspect.
  • an embedded universal integrated circuit card eUICC includes: a receiver, a transmitter, a memory, and a processor.
  • the receiver is configured to receive a message or data sent by a device other than the eUICC, and forward the message or data to the processor; the transmitter is configured to send a message to an application on the eUICC according to an instruction of the processor. Or data; the memory is used to store a program; the processor is used to execute a program stored in the memory, and when the program is executed, cause the eUICC to execute the third aspect or any of the third aspects as possible Method of implementation.
  • an Internet of Things IoT platform including: a receiver, a transmitter, a memory, and a processor.
  • the receiver is configured to receive a message or data sent by a device outside the IoT platform, and forward the message or data to the processor; and the sender is configured to send a message or data to a device outside the IoT platform according to an instruction of the processor.
  • the device sends a message or data; the memory is used to store a program; the processor is used to execute a program stored in the memory, and when the program is executed, cause the IoT platform to execute the fourth aspect or the fourth aspect
  • the method in any possible implementation.
  • a computer-readable medium for storing a computer program, the computer program including instructions for performing a method in any possible implementation manner of any of the foregoing aspects.
  • a computer program product includes computer program code that, when the computer program code is executed by a computer, causes the computer to execute a method in any possible implementation manner of any of the foregoing aspects. .
  • a communication chip in which instructions are stored that, when running on a device for wireless communication, cause the communication chip to execute the method in any possible implementation manner of any of the above aspects.
  • FIG. 1 is a schematic block diagram of a possible architecture for implementing eUICC remote configuration and management.
  • FIG. 2 is a schematic block diagram of a possible LwM2M protocol stack.
  • FIG. 3 is a schematic block diagram of establishing a session between an SM platform and an eUICC based on an LwM2M protocol according to an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of a possible terminal device.
  • FIG. 5 is a schematic block diagram of a modem.
  • FIG. 6 is a schematic flowchart of a communication method according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a possible communication method according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another possible communication method according to an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a machine-to-machine M2M communication device 900 according to an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of an embedded universal integrated circuit card eUICC 1000 provided in an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of an IoT platform 1100 provided by an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of a machine-to-machine M2M communication device 1200 according to an embodiment of the present application.
  • FIG. 13 is a schematic block diagram of an embedded universal integrated circuit card eUICC 1300 provided by an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of an IoT platform 1400 provided by an embodiment of the present application.
  • NB-IoT narrowband Internet of Things
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet radio service
  • LTE long-term evolution
  • FDD frequency division duplex
  • TDD LTE time division duplex
  • UMTS universal mobile communication system
  • the embodiment of the present application does not specifically limit the type of the terminal device, and may be, for example, user equipment, access terminal, terminal device, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal , Wireless network equipment, user agent, or user device.
  • the terminal may include, but is not limited to, a mobile station (MS), a mobile phone (mobile phone), a user equipment (UE), a mobile phone (handset), a portable device (portable equipment), a cellular phone, a cordless phone, a conversation Initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital processing (PDA), radio frequency identification (RFID) terminal equipment for logistics, Wireless communication-capable handheld devices, computing devices, or other devices connected to wireless modems, in-vehicle devices, wearable devices, the Internet of Things, terminal devices in the vehicle network, and terminal devices in the future 5G network or future evolution of public land mobile Terminal equipment in a public network (PLMN) network.
  • MS mobile station
  • UE user equipment
  • UE mobile phone
  • handset portable device
  • cellular phone a cellular phone
  • cordless phone a conversation Initiation protocol (SIP) phone
  • SIP conversation Initiation protocol
  • WLL wireless local loop
  • PDA personal digital processing
  • the terminal device may also be a wearable device.
  • Wearable devices can also be referred to as wearable smart devices, which are the general name for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a device that is worn directly on the body or is integrated into the user's clothing or accessories.
  • Wearable devices are not only a hardware device, but also powerful functions through software support, data interaction, and cloud interaction.
  • Broad-spectrum wearable smart devices include full-featured, large-sized, full or partial functions that do not rely on smart phones, such as smart watches or smart glasses, and only focus on certain types of application functions. Use, such as smart bracelets, smart jewelry, etc. for physical signs monitoring.
  • the terminal device may be various carriers moving at high speed, for example, shared bicycles, shared cars, and the like.
  • the terminal device can also be various smart meters, such as water meters, electricity meters, and gas meters.
  • the terminal device may also be various monitoring devices or home appliances.
  • FIG. 1 is a schematic block diagram of an architecture for implementing remote configuration and management of eUICC.
  • the architecture for implementing the remote configuration and management of the eUICC shown in FIG. 1 may include a subscription management (SM) platform 110 and an eUICC 120.
  • SM subscription management
  • the SM platform 110 can establish a session with the eUICC 120.
  • the SM platform 110 can switch the profile loaded on the eUICC 120 based on the air interface (OTA), so that the eUICC 120 can be switched from the current mobile network operator (MNO) to the target MNO.
  • OTA air interface
  • profile is a special term in the field of communication, which can be understood as a user subscription data set or a collection of personal subscription service data used to sign on a certain operator network. It is a data collection of mobile user information, which can include users Identification information (such as user identity, authentication parameters, etc.) and service contract information.
  • the data contained in the profile may include, but is not limited to, a profile type, for example, a subscriber identity module (SIM) alliance profile package (SIM) profile; an international mobile subscriber identity (IMSI) code ; Integrated circuit card identification (ICCID) code; secure digital (SD) memory card executable file loading assistance (aide, AID) program (executable load file AID for SD); SD memory card Executable module assistance (executable module AID for SD).
  • SIM subscriber identity module
  • IMSI international mobile subscriber identity
  • ICCID Integrated circuit card identification
  • SD secure digital
  • the SM platform 110 may send the generated profile to the eUICC 120 through a short 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 download or activate the profile, so that the eUICC 120 is switched from the current MNO to the target MNO.
  • the SM platform 110 may be an application server.
  • the following describes the SM platform 110 and eUICC 120 respectively.
  • the SM platform 110 is the core of eUICC remote management.
  • the SM platform 110 can perform management operations such as downloading, installing, activating, deactivating, and deleting a profile according to a request initiated by an MNO or a user.
  • the functions of the SM platform 110 mainly include two parts: subscription management data preparation (SM-DP), and subscription management security routing (SM-SR).
  • SM-DP is mainly responsible for generating and storing profiles according to the data provided by the target MNO.
  • SM-SR is mainly responsible for establishing the channel to eUICC 120, and can download the profile route generated by SM-DP to eUICC 120.
  • eUICC 120 can be an embedded UICC card, which can be connected to a terminal device such as a modem (which can be a circuit or a baseband chip).
  • the eUICC 120 can communicate with other devices or equipment outside the terminal device through the modem.
  • the eUICC 120 can provide users with the ability to implement MNO changes based on the air interface (OTA) without the need to replace the eUICC physical entity itself.
  • eUICC 120 can provide security services similar to ordinary smart cards for mobile network access authentication and user identity authentication, and can be used to remotely manage multiple mobile network operations and personal management services.
  • the SM platform can transmit the generated profile to the eUICC through the established transmission channel according to the MNO or user request.
  • Profile installation eUICC can install downloaded profiles as executable applications and file systems. Profile installation can be performed concurrently with profile download. Successfully installed profiles can enter a deactivated state.
  • the SM platform can activate the profile that is currently in the deactivated state on the eUICC, so that files and applications in the profile can be selected through the interface between the terminal device and the eUICC.
  • the SM platform can deactivate the currently active profile on the eUICC, so that files and applications in the profile cannot be selected through the interface between the terminal device and the eUICC.
  • Light weight machine to machine is an Internet of Things protocol defined by the Open Mobile Alliance (OMA).
  • LwM2M's protocol stack structure can be seen in Figure 2.
  • the LwM2M protocol 210 belongs to an application layer protocol and is located on top of a Constrained Application Protocol (CoAP) 220.
  • CoAP 220 can perform datagram transmission layer security (DTLS) 230 encryption processing.
  • DTLS datagram transmission layer security
  • UDP user packet protocol
  • SMS short message service
  • the LwM2M protocol can package messages into objects (Objects, Obj) 260 and can be transmitted through the above protocol. Objects will be described later in detail, so I won't repeat them here.
  • the SMS 250 may be a short message service located on a device, and the SMS 255 may be a short message service located on a smart card.
  • the header of the LwM2M protocol is smaller than the header of HTTPS, and the LwM2M protocol can establish an IoT platform (as a server sever) and an M2M communication device (as a client client) on a terminal device without requiring multiple handshake. Conversation. Therefore, in the NB-IoT network, a session between the application server (for example, the SM platform) and the eUICC on the terminal device can be established through the LwM2M protocol, thereby implementing data transmission.
  • FIG. 3 uses FIG. 3 as an example to describe in detail a session established between an application server (for example, an SM platform) and an eUICC on a terminal device through the LwM2M protocol.
  • an application server for example, an SM platform
  • an eUICC on a terminal device through the LwM2M protocol.
  • FIG. 3 is a schematic block diagram of establishing a session between an SM platform and an eUICC based on an LwM2M protocol according to an embodiment of the present application.
  • FIG. 3 may include a SM platform 310, an IoT platform 320, a terminal device 330, an M2M communication device 340, and an eUICC 350.
  • the SM platform 310 may correspond to the SM platform 110 in FIG. 1, and may send a profile download request sent by the MNO to the terminal device 330 through the IoT platform.
  • the SM platform 310 can convert the profile download request sent by the MNO into an LwM2M message (for example, the profile download request can be packaged into LwM2M objects) and then sent to the IoT platform 320, or the profile download request sent by the MNO can be converted into other types of messages Send to IoT platform 320.
  • the IoT platform 320 can be used as a device management platform in the LwM2M protocol.
  • the IoT platform 320 can send messages sent by the SM platform 310 to the terminal device 330 through the LwM2M protocol.
  • the IoT platform 320 needs to convert the message sent by the SM platform 310 into an LwM2M message and then send it to the terminal device 330.
  • the IoT platform 320 receives the LwM2M message of the terminal device 330 before it can be forwarded to the SM platform 310. .
  • the terminal device 330 is configured with an M2M communication device 340 and an eUICC 350.
  • the LwM2M message received by the terminal device 330 can be processed by the M2M communication device 340 on the terminal device 330.
  • a schematic structural diagram of the terminal device 330 may be shown in FIG. 4.
  • the M2M communication device 340 may be a chip, or may be an integrated circuit or other device.
  • the M2M communication device 340 may forward the received LwM2M message to the eUICC 350.
  • a schematic structural diagram of the M2M communication device 340 may be shown in FIG. 5.
  • the eUICC 350 may correspond to the eUICC 120 in FIG. 1.
  • the eUICC 350 and the M2M communication device 340 can perform communication and information exchange. Physically, the eUICC 350 can be a device independent of the M2M communication device 340, and the eUICC350 can also be a device bound to the M2M communication device 340 (for example, the eUICC350 is embedded in the M2M communication device by welding or other methods 340).
  • the eUICC350 forwards the received LwM2M message to the application on the eUICC350 through the transceiver on the M2M communication device 340.
  • FIG. 4 is a schematic block diagram of a possible terminal device.
  • the terminal device 330 in FIG. 4 may include an application processor (AP) 410, a modem (modem) 420, a wireless transceiver 430, and eUICC480, and optionally, a user interface 440, a memory 450, a camera 460, and a voice. Input and output interface 470.
  • the AP 410 can be an ultra-large-scale integrated circuit that extends time-frequency functions and special interfaces on the basis of a low-power central processing unit (central processing unit, CPU).
  • the AP 410 runs an operating system and application software.
  • the modem 420 may correspond to the M2M communication device 340 in FIG. 3.
  • the modem 420 can be called a baseband chip, and its main function is to send and receive various data, such as the realization of the main functions in wireless communication standards such as the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP).
  • the modem 420 is equivalent to a communication protocol processor and can be responsible for data processing.
  • the modem 420 can be used as a separate chip, or it can be combined with other chips or circuits to form a system-level chip or integrated circuit.
  • the chip or integrated circuit can be applied to all terminal devices that implement wireless communication functions.
  • the terminal device 330 may receive and transmit data through the wireless transceiver 430.
  • the memory 450 may be used to store one or more of computer program instructions, preset parameters, data obtained by computer intermediate operations, and the like.
  • the following describes the internal logical structure of the modem 420 with the M2M communication device 340 as the modem 420.
  • FIG. 5 is a schematic block diagram of a modem modem according to an embodiment of the present application.
  • the modem 420 shown in FIG. 5 may include a receiving data processor 510, a controller 520, and a transmitting data processor 530.
  • the data receiver 510 can receive data sent by the IoT platform through a physical layer (PHY) protocol, and can demodulate the received data through functions such as channel decoding, demodulation, equalization, and channel estimation.
  • PHY physical layer
  • the processor 520 may process data through a protocol layer, and the processor 520 may use a media access control (MAC) layer protocol, a radio link control (RLC) layer protocol, and a packet data convergence protocol (packet) Data protocol (PDCP), radio resource control (RRC) layer protocols process data.
  • MAC media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • RRC radio resource control
  • the data transmitter 530 may modulate data after processing such as channel coding, modulation, and symbol generation, and may send data to a UICC connected to the modem 420 through a PHY layer protocol.
  • the modem 420 shown in FIG. 5 can also have built-in storage, called on-chip memory, for example, terminal device to computer multiplexer (TCM), static random access memory (static random access memory) , SRAM) and so on.
  • on-chip memory for example, terminal device to computer multiplexer (TCM), static random access memory (static random access memory) , SRAM) and so on.
  • TCM terminal device to computer multiplexer
  • static random access memory static random access memory
  • SRAM static random access memory
  • the modem 420 can also communicate with off-chip memory.
  • the off-chip memory can include but is not limited to: read-only memory (ROM), random access memory (RAM), U disk, mobile hard disk, Optical discs, magnetic storage devices, etc.
  • the communication method provided in the embodiment of the present application can establish a session between an application server (such as an SM platform) and an eUICC on an M2M communication device under the NB-IoT network, thereby completing data transmission.
  • an application server such as an SM platform
  • an eUICC on an M2M communication device under the NB-IoT network
  • FIG. 6 is a schematic flowchart of a communication method according to an embodiment of the present application.
  • the method in FIG. 6 may include steps 610-630. Steps 610-630 are described below respectively.
  • step 610 the M2M communication device receives an LwM2M message sent by the IoT platform.
  • the embodiment of the present application does not specifically limit the LwM2M message sent by the IoT platform.
  • the LwM2M message may include a profile delivered by the SM platform to an eUICC user and a target operator to sign up with the target operator or activation information of the profile.
  • personal payment applications and application servers running on the eUICC may also transmit personal payment and consumption information through LwM2M messages between the IoT platform and M2M communication devices.
  • the M2M communication device in the embodiment of the present application is a communication module in a terminal device.
  • the M2M communication device may be a chip, or may be an integrated circuit or other device.
  • the M2M communication device can be applied to all devices that implement wireless communication functions.
  • the M2M communication device may be a modem modem. For a detailed description of the modem, refer to the description in FIG. 5, and details are not described herein again.
  • the LwM2M message may include an application indication (for example, App ID), and the M2M communication device may forward the LwM2M message to the application on the eUICC according to the application indication.
  • App ID for example, App ID
  • the IoT platform may forward the LwM2M message to the machine-to-machine M2M communication device, and the application indication (for example, App ID) in the LwM2M message may be used to indicate that this communication is communication between the SM platform and an application on the eUICC.
  • the application indication for example, App ID
  • the so-called application on the eUICC refers to an application instance or application process or application program running on the eUICC.
  • the application instruction may be used to indicate the profile of the target operator or the profile to be returned
  • the response result of the activation information is sent to the SM platform.
  • the application instruction may be used to instruct the M2M communication device to forward the profile of the target operator or the activation information of the profile to an application on the eUICC.
  • step 620 the M2M communication device sends a LwM2M message to the eUICC associated therewith.
  • the eUICC can be connected with an M2M communication device, and the eUICC can communicate with other devices or devices other than the terminal device through the M2M communication device.
  • the implementation manner that the M2M communication device sends the LwM2M message to the eUICC in the embodiment of the present application is not specifically limited.
  • the LwM2M message delivered by the SM may be sent to the eUICC according to an application instruction in the LwM2M message.
  • the LwM2M message delivered by the SM may also be sent to the eUICC according to the first instruction in the LwM2M message. Detailed description will be given below with reference to FIGS. 7 to 8, and details are not described herein again.
  • step 630 the eUICC sends the target data in the LwM2M message to the application on the eUICC according to the application instruction.
  • the application server may establish a session between the application server and the eUICC on the M2M communication device through the LwM2M protocol, thereby completing data transmission.
  • the LwM2M message may include a profile of a target operator issued by the subscription management SM platform to the eUICC or activation information of the profile.
  • the IoT platform can convert the request message sent by the SM platform to an LwM2M message under the LwM2M protocol.
  • this application can package the request message sent by the SM platform into an LwM2M application data object (App Container Data Object), which can realize the conversion of the request message sent by the SM platform into an LwM2M message under the LwM2M protocol.
  • LwM2M application data object App Container Data Object
  • each LwM2M entity for example, each device supporting the LwM2M protocol
  • the accessible service is abstracted into one object, and each object office can have three levels.
  • an object may include several objects (Objects) that provide different functions, for example, several different sensors.
  • each of the above functions may be provided by multiple Object-Instances.
  • Objects objects
  • a temperature reading function is provided.
  • the functions that the above object instance can actually accomplish may be referred to as resources.
  • a universal resource identifier can be as follows: ⁇ / Object ID / Object-Instance ID / Resource ID>.
  • commonly used URI formats can be ⁇ / 1/0>, ⁇ / 1/1>, ⁇ / 2/0>, ⁇ / 2/1>, ⁇ / 2/2>, ⁇ / 2/3>, ⁇ / 2/4>, ⁇ / 3/0>, ⁇ / 4/0>, ⁇ / 5/0>, ⁇ / 19/0>, ⁇ / 19/1>.
  • the URI respectively identifies the Object ID, Object-Instance ID, and Resource ID of the resource accessed, where the last two IDs can be optional.
  • the contract management SM platform may send download or activation request information of the profile of the target operator to the IoT platform.
  • the download or activation request information sent may include information of the target eUICC, so that the target eUICC can download, install, or activate the profile of the target operator, which can cause the target eUICC to switch from the profile of the current operator to the profile of the target operator. .
  • the first LwM2M message further includes a first identifier, and the first identifier is used to instruct the M2M communication device to forward the download or activation information of the target operator's profile to the M2M communication device. eUICC.
  • the IoT platform may receive the first LwM2M registration request.
  • the IoT platform may also receive a second LwM2M registration request.
  • the second LwM2M registration request may be used by the M2M communication device to request LwM2M registration with the IoT platform.
  • the following uses the eUICC to request registration with the IoT platform LwM2M as an example for detailed description.
  • the eUICC may request to register directly with the IoT platform LwM2M.
  • the M2M communication device may forward the first LwM2M registration information requested by the eUICC to the IoT platform for registration to the IoT platform.
  • the M2M communication device may be referred to as supporting an LwM2M gateway (getway, GW) route mode.
  • the M2M communication device can support the LwM2M GW route mode, the eUICC supports the LwM2M protocol, and the IoT platform supports the LwM2M protocol.
  • the M2M communication device can support the LwM2M GW route mode
  • the M2M communication device, the IoT platform, and the eUICC can be pre-configured.
  • the pre-configuration of the M2M communication device can be implemented by software code.
  • the M2M communication device can support the function of LwM2M gateway.
  • the M2M communication device can parse the LwM2M message of the eUICC card to realize the support of data transmission through the LwM2M protocol.
  • pre-configuration of the IoT platform can be implemented by software code, which supports data transmission under the LwM2M protocol.
  • the eUICC App can be pre-configured as an APP on the LwM2M server, and the IoT platform can forward the LwM2M message to an App on the LwM2M client to implement support for data transmission through the LwM2M protocol.
  • the IoT platform can hold parsing new application identifiers.
  • IP Internet protocol
  • the pre-configuration of the eUICC may be implemented by software code.
  • eUICC supports data transmission under the LwM2M protocol.
  • the pre-configured eUICC can be used as a LwM2M client, which can complete the data transmission function.
  • an eUICC session description protocol (SDP) file can be configured in advance, and an LwM2M service can be set, so that the eUICC and the terminal device can support data transmission through the LwM2M protocol.
  • SDP eUICC session description protocol
  • an LwM2M service can be set, so that the eUICC and the terminal device can support data transmission through the LwM2M protocol.
  • an embedded subscriber identity module (eSIM) App can be configured as an App on the LwM2M client.
  • the eUICC can forward the LwM2M message to an App on the LwM2M client.
  • an App on the LwM2M client can forward the LwM2M message to an App on the LwM2M client.
  • a channel (service description) from the eUICC to the M2M communication device can be established to implement support for data transmission through the LwM2M protocol.
  • the eUICC may be set as a resource and a service (service ID) supported by the client, and the service ID is LwM2M.
  • the embodiment of the present application does not specifically limit a specific implementation manner in which the M2M communication device can forward the first LwM2M registration information to the eUICC.
  • FIG. 7 is a schematic flowchart of a possible communication method according to an embodiment of the present application.
  • the method in FIG. 7 may include steps 710-790. Steps 710-790 are described in detail below.
  • the eUICC may support the LwM2M protocol
  • the M2M communication device supports the LwM2M GW routing mode
  • the eUICC and the M2M communication device may be registered to the IoT platform at the same time.
  • the download and activation of the profile can be done through the LwM2M protocol, which can support eUICC.
  • the IoT platform can serve as the server of the LwM2M protocol
  • eUICC can serve as the client of the LwM2M protocol
  • the M2M communication device can serve as the server / client of the LwM2M protocol.
  • the IoT platform and eUICC can have an application layer protocol (App ID), and the IoT platform can implement application layer data transmission through the LwM2M layer protocol.
  • App ID application layer protocol
  • Step 710 The eUICC initiates a bearer independent protocol (BIP) channel to the M2M communication device.
  • BIP bearer independent protocol
  • the eUICC may initiate a BIP channel to the M2M communication device, and a link with the M2M communication device may be established through the BIP channel.
  • the eUICC can actively open a channel command to the M2M communication device, so that the M2M communication device opens a BIP channel, so that the M2M communication device can establish a data connection with the IoT platform.
  • Step 715 The eUICC sends an LwM2M registration request to the M2M communication device.
  • the eUICC can act as an LwM2M client module to initiate an LwM2M registration request to the IoT platform.
  • the eUICC can send the LwM2M registration request message to the M2M communication device.
  • the above registration request message may carry AppDataDataContainerObj.
  • AppDataDataContainerObj may be ⁇ / 19/0>, ⁇ / 19/1>.
  • 19 in ⁇ / 19/0> and ⁇ / 19/1> can be used to indicate that the ID of an object registered by the eUICC with the IoT platform is 19, 0 can be used to indicate the downlink message sent by the IoT platform to the eUICC, 1 It can be used to indicate the uplink message sent by the eUICC to the IoT platform.
  • step 715 may be as follows:
  • Step 720 The M2M communication device modifies the URI in the registration request.
  • the M2M communication device After receiving a message from the eUICC requesting registration with the IoT platform, the M2M communication device can package the new message that the M2M communication device requests to register with the IoT platform and the message from the eUICC requesting registration with the IoT platform into one session Send to IoT platform.
  • the M2M communication device may modify the URI in the registration message, and may add a first identifier to a session sent to the IoT platform.
  • a client can be eUICC.
  • the token ID in the registration message may be the same as the original message.
  • step 720 may be as follows:
  • eUICC can be used to indicate that the payload also includes eUICC information, for example, a message sent by the eUICC requesting registration with the IoT platform.
  • Step 725 The M2M communication device forwards the packaged LwM2M registration request to the IoT platform.
  • the specific implementation of the LwM2M registration message packaged by the M2M communication device with the eUICC and the M2M communication device is as follows:
  • Step 730 The IoT platform parses the received LwM2M registration request, and obtains a registration request message of the eUICC and the M2M communication device.
  • Step 735 The IoT platform returns a registration response result to the M2M communication device.
  • the registration response result can be returned to the M2M communication device.
  • the registration response result may include two addresses. One location may be used to instruct the M2M communication device to return the registration response result to the module, and the other location may be used to instruct the M2M communication device to return the registration response result to. eUICC.
  • step 735 is as follows:
  • location: / rd / 5a3f can be used to instruct the M2M communication device to return the registration response result to the module
  • step 740 is as follows:
  • Step 743 The M2M communication device sends an LwM2M registration response result to the eUICC.
  • Step 745 Optionally, the eUICC initiates BIP to the M2M communication device.
  • the eUICC may initiate a BIP to the M2M communication device after receiving the registration response message forwarded by the M2M communication device.
  • the eUICC can actively close the channel to the M2M communication device, so that the M2M communication device closes the BIP channel, so that the M2M communication device can disconnect the data connection with the IoT platform.
  • Step 750 The IoT platform receives a download profile request message (download profile) sent by the SM platform.
  • Step 755 The IoT platform sends a download profile request message to the M2M communication device.
  • the IoT platform After receiving the download profile request message sent by the SM platform, the IoT platform can package the request message into an AppDataContainerObj object. Since the IoT platform finds that the destination client of the download profile request message is eUICC, the IoT platform can add an application instruction to the destination URL.
  • App ID for example, App ID
  • the first identifier in the embodiment of the present application may be used to instruct the M2M communication device to forward the download or activation information of the target operator's profile to the eUICC.
  • the application instruction may be used to instruct the eUICC to send the download or activation information of the profile of the target operator to the App on the eUICC.
  • step 755 is as follows:
  • the created security domain-profile (ISD-P) of the profile can be used to store the profile.
  • token bucket ID (token ID) in the LwM2M request message may be the same as the original request message.
  • the M2M communication device may first obtain a BIP channel between the M2M communication device and the eUICC.
  • Step 765 The M2M communication device sends a request message to the eUICC.
  • step 765 is as follows:
  • Step 770 The eUICC forwards the request message to the eUICC App according to the application instruction (for example, App ID).
  • token ID in this message may be the same as the original request message.
  • Step 775 The eUICC returns the LwM2M execution result to the M2M communication device.
  • the eUICC can package the execution results of the eUICC App to the LwM2M App Data Container Obj, and can reserve the BIP channel according to the Data Format.
  • the execution result of the eUICC App described above may be a response result of a request message sent by the SM platform for an application on the eUICC.
  • the execution result may include an application instruction (for example, App ID), which is used to instruct the IoT platform to return the execution result to the SM platform.
  • step 775 is as follows:
  • Step 780 The M2M communication device forwards the LwM2M execution result to the IoT platform.
  • token ID in the execution result may be the same as the original request message.
  • step 780 is as follows:
  • Step 785 The IoT platform sends a download profile response message (download profile Rsp) to the SM platform.
  • the IoT platform After receiving the LwM2M execution result sent by the M2M communication device, the IoT platform can convert the LwM2M execution result into the format of the original download profile request message according to the application instruction (for example, App ID) in the LwM2M execution result, and then convert the converted Download the profile response message to the SM platform.
  • the application instruction for example, App ID
  • Step 790 The IoT platform receives an activation profile request message (enable profile) sent by the target MNO.
  • the IoT platform can send an activation profile request message to the eUICC, so that the eUICC can complete the download and activation of the profile through the LwM2M protocol, thereby completing the profile switching from the current operator to the target operator.
  • LwM2M can directly establish a session between the remote server and the eUICC on the terminal without multiple handshake. Therefore, the embodiment of the present application can reduce the interaction messages between the eUICC and the remote server, and reduce the eUICC.
  • the complexity of the protocol stack improves the transmission efficiency of the network.
  • the following uses the M2M communication device to request LwM2M registration with the IoT platform as an example for description.
  • the eUICC may request LwM2M registration from the M2M communication device.
  • the M2M communication device may send a LwM2M registration request to the IoT platform, so that the eUICC can support the LwM2M protocol, and can be based on
  • the profile download and activation request sent by the SM platform can complete the download and activation of the profile, and switch from the profile of the current operator to the profile of the target operator. It will be described in detail below with reference to FIG. 8, and is not repeated here.
  • the eUICC may request LwM2M registration from the M2M communication device, and the M2M communication device may request LwM2M registration with the IoT platform, so that the eUICC can download and activate the profile according to the profile sent by the SM platform to complete the download and activation of the profile.
  • the M2M communication device may be referred to as supporting a LwM2M GW proxy mode.
  • the M2M communication device can be configured to support the LwM2M GW proxy mode through pre-configuration, eUICC supports the LwM2M protocol, and the IoT platform supports the LwM2M protocol.
  • pre-configuration of the M2M communication device may be implemented by software code, and the M2M communication device may support data transmission through the LwM2M protocol.
  • the M2M communication device can be pre-configured to support the function of LwM2M gateway and proxy.
  • the LwM2M server module and client module of the M2M communication device can be pre-configured to map to each other as an App, and the server of the M2M communication device can forward LwM2M messages to the client to implement support for data transmission through the LwM2M protocol.
  • the M2M communication device can be pre-configured to support AppData, Container, and DataFormat, and forward the LwM2M message to the eUICC to support data transmission through the LwM2M protocol.
  • the M2M communication device can support both the LwM2M client module and the LwM2M server module.
  • the device management (DM) function can be completed by the LwM2M client module.
  • the M2M communication device can support App Data, Container, and Data Format as follows: It can send a request to create an ISD-P (SMS, create ISD-P, Req) through a short message service (SMS), or through The SMS sends a response to create an ISD-P (SMS, create ISD-P, Rsp), or a key group request to create an ISD-P (establish ISD-P key set Req), or a key group response to create an ISD-P (establish ISD-key set Rsp), it can also be a request to send data (send data Req), or it can be a response to send data (send data Rsp).
  • SMS short message service
  • SMS short message service
  • SMS short message service
  • the SMS sends a response to create an ISD-P (SMS, create ISD-P, Rsp), or a key group request to create an ISD-P (establish ISD-P key set Req), or a key group response to create an ISD
  • pre-configuration of the IoT platform can be implemented by software code, and the IoT platform can support data transmission through the LwM2M protocol.
  • the eUICC App can be pre-configured as an App on the LwM2M server, and the IoT platform can forward LwM2M messages to the eUICC App to support data transmission through the LwM2M protocol.
  • the IoT platform can be pre-configured to support the App Data, Container, and Data Format, and forward the LwM2M message to the eUICC to support data transmission through the LwM2M protocol.
  • the App Data and Container Data Format supported by the IoT platform are as follows: it can be a short message service (SMS) to send a request to create an ISD-P (SMS, create ISD-P, Req), or It is a response to create an ISD-P (SMS, create ISD-P, Rsp) sent by SMS, or a key group request to create an ISD-P (establish ISD-P key set Req), or the key to create an ISD-P
  • SMS short message service
  • SMS create ISD-P
  • Rsp key group request to create an ISD-P
  • the group response can also be a request to send data (send data Req), or a response to send data (send data Rsp).
  • the pre-configuration of the eUICC may be implemented by software code.
  • eUICC supports data transmission under the LwM2M protocol.
  • the pre-configured eUICC can be used as a LwM2M client, which can complete the data transmission function.
  • an eUICC session description protocol (SDP) file can be configured in advance, and an LwM2M service can be set, so that the eUICC and the terminal device can support data transmission through the LwM2M protocol.
  • SDP eUICC session description protocol
  • an LwM2M service can be set, so that the eUICC and the terminal device can support data transmission through the LwM2M protocol.
  • an embedded subscriber identity module (eSIM) App can be configured as an App on the LwM2M client.
  • the eUICC can forward the LwM2M message to an App on the LwM2M client.
  • an App on the LwM2M client can forward the LwM2M message to an App on the LwM2M client.
  • a channel (service description) from the eUICC to the M2M communication device can be established to implement support for data transmission through the LwM2M protocol.
  • the eUICC can be pre-configured to support AppData, Container, and DataFormat, and forward the LwM2M message to the application on the eUICC, so as to support data transmission through the LwM2M protocol.
  • the eUICC can be pre-configured so that the App can support the Data and Obj Data Format of the eUICC as follows: It can be a short message service (SMS) to send a request to create an ISD-P ( SMS, create ISD-P Req), or a response to create an ISD-P via SMS (SMS, create ISD-P Rsp), or a key group request to create an ISD-P (establish ISD-P key set Req ), It can also be a key group response to create an ISD-P (establish ISD-P key set Rsp), it can also be a request to send data (send data Req), or it can be a response to send data (send data Rsp).
  • SMS short message service
  • the M2M communication device in a case where the M2M communication device can support the LwM2M proxy mode, the M2M communication device can support both the LwM2M client (client) and the server (sever).
  • the client and server on the M2M communication device can be mapped to each other through an application indication (for example, App ID), and the mapping relationship is consistent with the application indication (for example, App ID). Therefore, after the M2M communication device receives the message sent by the eUICC, the M2M communication device can forward the message to the IoT platform based on the above mapping relationship.
  • the client module of the M2M communication device can receive the registration information sent by the eUICC to the M2M communication device to perform LwM2M registration, and the server module of the M2M communication device can report to The IoT platform sends registration information that the M2M communication device requests to perform LwM2M registration with the IoT platform.
  • FIG. 8 is a schematic flowchart of another possible communication method according to an embodiment of the present application.
  • the method in FIG. 8 may include steps 810-890. Steps 810-890 are described in detail below respectively.
  • the eUICC supports the LwM2M protocol
  • the M2M communication device supports the LwM2M GW proxy mode
  • the eUICC is only registered to the M2M communication device.
  • the download and activation of the profile can be done through the LwM2M protocol, which can support eUICC.
  • the IoT platform can serve as the server of the LwM2M protocol
  • eUICC can serve as the client of the LwM2M protocol
  • the M2M communication device can serve as the server / client (clien) of the LwM2M protocol.
  • the IoT platform and eUICC can have an application layer protocol (App ID), and the IoT platform can implement application layer data transmission through the LwM2M layer protocol.
  • Step 810 The eUICC initiates a BIP channel to the M2M communication device.
  • the eUICC may initiate a BIP channel to the M2M communication device, and a link with the M2M communication device may be established through the BIP channel.
  • the eUICC can actively open a channel command to the M2M communication device, so that the M2M communication device opens a BIP channel, so that the M2M communication device can establish a data connection with the IoT platform.
  • Step 815 The eUICC sends an LwM2M registration request to the M2M communication device.
  • the eUICC can act as an LwM2M client module to initiate a registration request to the M2M communication device, and the server module of the M2M communication device receives the eUICC to initiate a registration request to the M2M communication device. That is, the eUICC actively initiates registration with the M2M communication device.
  • the registration request carries the App Data Container Obj, for example, the App Data Container Obj can be ⁇ / 19/0>, ⁇ / 19/1>.
  • Step 820 The M2M communication device initiates an LwM2M registration request to the IoT platform.
  • the LwM2M registration request may carry AppDataContainerObj.
  • AppDataDataContainerObj may be ⁇ / 1>, ⁇ / 2>, ⁇ / 3>, ⁇ / 4>, ⁇ / 5>, ⁇ / 19>.
  • Step 825 The IoT platform receives a download profile request message (download profile) sent by the SM platform.
  • the download profile request message sent by the target MNO in this application may include an application indication (for example, App_ID) may indicate that the download profile request message is sent to the App on the eUICC.
  • App_ID an application indication
  • Step 830 The IoT platform sends a download profile request message to the M2M communication device.
  • the IoT platform After receiving the download profile request message sent by the SM platform, the IoT platform can write the request message into the AppDataDataContainerObj object.
  • step 830 may be as follows:
  • Step 835 The M2M communication device forwards the request message to the LwM2M server module according to the application instruction (for example, App_ID), and the LwM2M server module forwards the request message to the eUICC.
  • App_ID the application instruction
  • eUICC the application instruction for example, App_ID
  • the client module of the M2M communication device After the client module of the M2M communication device receives the LwM2M download profile request message sent by the IoT platform, it can forward the request message to the server module of the M2M communication device according to the application instruction (for example, App_ID) in the Data Format.
  • the server module of the M2M communication device can directly forward the LwM2M request message to the eUICC.
  • token ID in the LwM2M request message during the foregoing forwarding process may be the same as the original request message.
  • the M2M communication device may first obtain a BIP channel between the M2M communication device and the eUICC.
  • Step 840 The M2M communication device sends an LwM2M request message to the eUICC.
  • the server module of the M2M communication device can directly forward the LwM2M request message to the eUICC.
  • step 840 may be as follows:
  • Step 845 The eUICC forwards the request message to the eUICC App according to the application instruction (for example, App_ID).
  • token ID in this message may be the same as the original request message.
  • Step 847 The eUICC returns the LwM2M execution result to the M2M communication device.
  • the eUICC can package the LwM2M execution results of the eUICC App into the LwM2M App Data Container Obj, and can reserve the BIP channel according to the Data Format.
  • the execution result of the eUICC App described above may be a response result of a request message sent by the SM platform for an application on the eUICC.
  • the execution result may include an application instruction (for example, App ID), which is used to instruct the IoT platform to return the execution result to the SM platform.
  • step 847 is as follows:
  • Step 850 The M2M communication device sends the execution result to the LwM2M client according to the application instruction App_ID, and the LwM2M client transparently transmits the result to the IoT platform.
  • the Sever module of the M2M communication device can send the execution result to the client module, and the client module can then transparently transmit the execution result to the IoT platform.
  • step 850 The specific implementation of step 850 is as follows:
  • Step 853 The M2M communication device sends the LwM2M execution result to the IoT platform.
  • Step 855 The IoT platform sends a download profile response message (download profile Rsp) to the SM platform.
  • the IoT platform After receiving the LwM2M execution result sent by the M2M communication device, the IoT platform can convert the LwM2M execution result into the format of the original download profile request message according to the application instruction (for example, App ID) in the LwM2M execution result. Download the profile response message to the SM platform.
  • App ID for example, App ID
  • Step 860 The IoT platform receives an activation profile request message (enable profile) sent by the target MNO.
  • the IoT platform can send an activation profile request message to the eUICC, so that the eUICC can complete the download and activation of the profile through the LwM2M protocol, thereby completing the profile switching from the current operator to the target operator.
  • interaction messages between the eUICC and the remote server can be reduced, and network transmission efficiency can be improved. It can reduce the complexity of the protocol stack of the eUICC and reduce the cost of the eUICC.
  • the wireless network communication method provided by the embodiment of the present invention is described in detail above with reference to FIGS. 1 to 8, and the embodiment of the communication device of the present application will be described in detail below with reference to FIGS. 9 to 14. It should be understood that the description of the method embodiment and the description of the communication device embodiment correspond to each other. Therefore, for the parts that are not described in detail, reference may be made to the foregoing method embodiment.
  • FIG. 9 shows a schematic block diagram of a machine-to-machine M2M communication device 900 according to an embodiment of the present application.
  • the M2M communication device 900 may include an embedded universal integrated circuit card eUICC, and each module of the M2M communication device 900 is used for Each action or process performed by the M2M communication device in the foregoing method is performed.
  • eUICC embedded universal integrated circuit card
  • FIG. 9 is a schematic block diagram of a machine-to-machine M2M communication device 900 according to an embodiment of the present application.
  • the M2M communication device 900 may include:
  • the first receiving module 901 is configured to receive a lightweight machine-to-machine LwM2M message sent by the Internet of Things IoT platform.
  • the LwM2M message includes application instructions and contract management SM platform target data sent to the embedded universal integrated circuit card eUICC.
  • the application instruction is used to indicate that this communication is communication between the SM platform and an application on the eUICC.
  • a first sending module 902 is configured to send the LwM2M message to the eUICC associated with the LwM2M message.
  • the second sending module 903 is configured to send the target data in the LwM2M message to an application on the eUICC according to the application instruction.
  • a session between an application server (for example, an SM platform) and an eUICC on a terminal can be established under the NB-IoT network, thereby completing data transmission.
  • an application server for example, an SM platform
  • an eUICC on a terminal can be established under the NB-IoT network, thereby completing data transmission.
  • the target data includes a profile of the target operator sent to the eUICC by the subscription management SM platform or activation information of the profile.
  • the first sending module 902 is specifically configured to send the profile issued by the SM or the activation information of the profile to the eUICC according to an application instruction in the LwM2M message.
  • the M2M communication device 900 further includes:
  • the third sending module 904 is configured to send a response message to the M2M communication device.
  • the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform, and the response message includes the application indication.
  • the fourth sending module 905 is configured to send the received response message to the SM platform according to the application instruction.
  • the first LwM2M message further includes a first identifier, and the first identifier is used to indicate communication between the IoT platform and the eUICC.
  • the first sending module 902 is specifically configured to send the profile or the activation information of the profile to the eUICC according to a first first identifier in the first LwM2M message. .
  • the M2M communication device 900 further includes:
  • a fifth sending module 906 is configured for an application on the eUICC to send the response message to the M2M communication device.
  • a sixth sending module 907 is configured to send the response message to the SM platform, where the response message includes the application indication and the first identifier.
  • the M2M communication device 900 further includes:
  • a seventh sending module 908, configured to send the eUICC to the M2M communication device an LwM2M registration request, and the first LwM2M registration request is used to request the eUICC to perform LwM2M registration with the IoT platform;
  • An eighth sending module 909 is configured for the M2M communication device to send the received LwM2M registration request to the IoT platform, and the first LwM2M registration request includes the first identifier.
  • the M2M communication device may support the LwM2M protocol to complete the download and activation of the profile, thereby implementing the eUICC switching from the current operator to the target operator.
  • FIG. 10 shows a schematic block diagram of an embedded universal integrated circuit card eUICC1000 according to an embodiment of the present application.
  • Each module in the eUICC 1000 is used to perform actions or processes performed by the eUICC in the foregoing method.
  • FIG. 10 is a schematic block diagram of an embedded universal integrated circuit card eUICC 1000 provided in an embodiment of the present application.
  • the eUICC 1000 can include:
  • the first receiving module 1001 is configured to receive a lightweight machine-to-machine LwM2M message sent by the machine-to-machine M2M communication device.
  • the LwM2M message includes an application instruction and target data sent to the eUICC by the subscription management SM platform.
  • the application instruction is used for In order to indicate that this communication is communication between the SM platform and an application on the eUICC, the eUICC is associated with the M2M communication device.
  • the first sending module 1002 is configured to send the target data in the LwM2M message to an application on the eUICC according to the application instruction.
  • a session between an application server (for example, an SM platform) and an eUICC on a terminal can be established under the NB-IoT network, thereby completing data transmission.
  • an application server for example, an SM platform
  • an eUICC on a terminal can be established under the NB-IoT network, thereby completing data transmission.
  • the target data includes a profile of the target operator sent to the eUICC by the subscription management SM platform or activation information of the profile.
  • the eUICC 1000 further includes:
  • the second sending module 1003 is configured to send a response message to the machine-to-machine M2M communication device.
  • the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform, and the response message includes the application indication.
  • the eUICC1000 further includes:
  • the third sending module 1004 is configured to send a first LwM2M registration request to the M2M communication device.
  • the first LwM2M registration request is used by the eUICC to request LwM2M registration with an IoT IoT platform, or used by the eUICC to request LwM2M registration with the IoT platform.
  • the eUICC can support the LwM2M protocol to complete the download and activation of the profile, thereby implementing the eUICC to switch from the current operator to the target operator.
  • FIG. 11 shows a schematic block diagram of an Internet of Things IoT platform 1100 according to an embodiment of the present application.
  • Each module in the IoT platform 1100 is used to perform each action or process performed by the IoT platform in the foregoing method.
  • FIG. 11 is a schematic block diagram of an IoT platform 1100 according to an embodiment of the present application.
  • the IoT platform 1100 may include:
  • the first receiving module 1101 is configured to receive a request message sent by the subscription management SM platform, where the request message includes an application instruction and target data sent to the eUICC by the subscription management SM platform, and the application instruction is used to indicate that the communication is required The communication between the SM platform and the application on the eUICC.
  • Processing module 1102 for converting the request message into a lightweight machine-to-machine LwM2M message.
  • a first sending module 1103 is configured to send the LwM2M message to a machine-to-machine M2M communication device, and the M2M communication device is associated with the eUICC.
  • a session between an application server (for example, an SM platform) and an eUICC on a terminal can be established under the NB-IoT network, thereby completing data transmission.
  • an application server for example, an SM platform
  • an eUICC on a terminal can be established under the NB-IoT network, thereby completing data transmission.
  • the target data includes a profile of the target operator sent to the eUICC by the subscription management SM platform or activation information of the profile.
  • the platform 1100 further includes:
  • the second receiving module 1104 is configured to receive a response message sent by the M2M communication device.
  • the response message is a response result of an application on the eUICC to the profile or profile activation information sent by the SM platform, and the response message includes the application indication.
  • the second sending module 1105 is configured to send the response message to the SM platform according to the application instruction.
  • the LwM2M message further includes a first identifier, and the first identifier is used to indicate communication between the IoT platform and the eUICC.
  • the platform 1100 further includes:
  • the third receiving module 1106 is configured to receive a first LwM2M registration request sent by the M2M communication device.
  • the first LwM2M registration request is used by the eUICC to request LwM2M registration with the IoT platform, and the first LwM2M registration request includes the first identifier.
  • the platform 1100 further includes:
  • the fourth receiving module 1107 is configured to receive a response message sent by the M2M communication device, where the response message includes the application instruction and the first identifier.
  • the third sending module 1108 is configured to send the response message to the SM platform according to the application instruction.
  • FIG. 12 is a schematic block diagram of a machine-to-machine M2M communication device 1200 according to an embodiment of the present application.
  • the M2M communication device 1200 includes eUIC.
  • the M2M communication device 1200 may include a processor 1201, a receiver 1202, a transmitter 1203, and a memory 1204.
  • the M2M communication device 1200 may be, for example, the modem 420 shown in FIG. 5, and the M2M communication device 1200 may include an on-chip memory 1204 and may also interact with an off-chip memory.
  • the receiver 1202 may correspond to the data receiver 510 in FIG. 5, the processor 1201 may correspond to the controller 520 in FIG. 5, and the transmitter 1203 may correspond to the data transmitter 530 in FIG. 5.
  • the processor 1201 may be communicatively connected with the receiver 1202 and the transmitter 1203.
  • the memory 1204 may be on-chip storage, and may be used to store program code and data of the network device. Therefore, the memory 1004 may be a storage unit inside the processor 1201, or an external storage unit independent of the processor 1201, or may include a storage unit inside the processor 1201 and an external storage unit independent of the processor 1201. component.
  • the network device may further include a bus 1205.
  • the receiver 1202, the transmitter 1203, and the memory 1204 can be connected to the processor 1201 through the bus 1205;
  • the bus 1205 can be a Peripheral Component Interconnect (PCI) bus or an extended industry standard structure (Extended Industry Standard) Architecture, EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 1205 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 12, but it does not mean that there is only one bus or one type of bus.
  • the processor 1201 may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), and a field programmable gate.
  • Array Field Programmable Gate Array, FPGA or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • the processor may also be a combination that realizes computing functions, for example, a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the function / implementation process of the receiver 1202 and the transmitter 1203 may also be implemented through pins or circuits.
  • FIG. 13 is a schematic block diagram of an embedded universal integrated circuit card eUICC 1300 provided by an embodiment of the present application.
  • the eUICC 1300 may include a processor 1301, a receiver 1302, a transmitter 1303, and a memory 1304.
  • the processor 1301 may be communicatively connected with the receiver 1302 and the transmitter 1303.
  • the memory 1304 may be used to store program code and data of the network device. Therefore, the memory 1304 may be a storage unit inside the processor 1301, or an external storage unit independent of the processor 1301, or may include a storage unit inside the processor 1301 and an external storage unit independent of the processor 1301. component.
  • the network device may further include a bus 1305.
  • the receiver 1302, the transmitter 1303, and the memory 1304 can be connected to the processor 1301 through the bus 1305.
  • the bus 1305 can be a Peripheral Component Interconnect (PCI) bus or an extended industry standard structure (Extended Industry Standard). Architecture, EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard
  • the bus 1305 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 13, but it does not mean that there is only one bus or one type of bus.
  • the processor 1301 may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), and a field programmable gate.
  • Array Field Programmable Gate Array, FPGA or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • the processor may also be a combination that realizes computing functions, for example, a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the function / implementation process of the receiver 1302 and the transmitter 1303 may also be implemented through pins or circuits.
  • FIG. 14 is a schematic block diagram of an IoT platform 1400 provided by an embodiment of the present application.
  • the IoT platform 1400 may include a processor 1401, a receiver 1402, a transmitter 1403, and a memory 1404.
  • the processor 1401 may be communicatively connected with the receiver 1402 and the transmitter 1403.
  • the memory 1404 may be used to store program code and data of the network device. Therefore, the memory 1404 may be a storage unit inside the processor 1401, or an external storage unit independent of the processor 1401, or may include a storage unit inside the processor 1401 and an external storage unit independent of the processor 1401. component.
  • the network device may further include a bus 1405.
  • the receiver 1402, the transmitter 1403, and the memory 1404 can be connected to the processor 1401 through a bus 1405;
  • the bus 1405 can be a Peripheral Component Interconnect (PCI) bus or an extended industry standard structure (Extended Industry Standard) Architecture, EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 1405 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 14, but it does not mean that there is only one bus or one type of bus.
  • the processor 1401 may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), and a field programmable gate.
  • Array Field Programmable Gate Array, FPGA or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • the processor may also be a combination that realizes computing functions, for example, a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the receiver 1402 and the transmitter 1403 may be circuits including the antenna and the transmitter chain and the receiver chain described above, and the two may be independent circuits or the same circuit.
  • 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 a method in any possible implementation manner of any of the foregoing aspects.
  • An embodiment of the present application further provides a chip system, which is applied to a communication device.
  • the chip system includes at least one processor, at least one memory, and an interface circuit.
  • the interface circuit is responsible for information exchange between the chip system and the outside world.
  • the at least one memory, the interface circuit, and the at least one processor are interconnected through a line, and the at least one memory stores instructions; the instructions are executed by the at least one processor to perform all the above aspects. The operation of the communication device in the method described below.
  • An embodiment of the present application further provides a computer program product, which is applied to a communication device.
  • the computer program product includes a series of instructions. When the instructions are executed, the method described in the foregoing aspects is performed. Operation of communication equipment.
  • system and “network” are often used interchangeably herein.
  • the term “and / or” in this document is only a kind of association relationship describing related objects, which means that there can be three kinds of relationships, for example, A and / or B can mean: A exists alone, A and B exist simultaneously, and exists alone B these three cases.
  • the character "/" in this text generally indicates that the related objects are an "or" relationship.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B based on A does not mean determining B based solely on A, but also determining B based on A and / or other information.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, a computer, a server, or a data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes one or more available medium integration.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks, and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Telephone Function (AREA)

Abstract

本申请提供了一种窄带物联网中eUICC数据传输的方法和装置。所述方法包括：机器到机器M2M通信装置接收物联网IoT平台发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC；所述eUICC根据所述应用指示将所述LwM2M消息中的目标数据发送至所述eUICC上的应用。本申请提供的技术方案可以在NB-IoT网络下建立应用服务器(例如，SM平台)与终端设备上的eUICC之间的会话，从而完成数据传输。

Description

一种窄带物联网中eUICC数据传输方法和装置
本申请要求于2018年6月8日提交中国国家知识产权局、申请号为201810589619.9、发明名称为“一种窄带物联网中eUICC数据传输方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种窄带物联网中eUICC数据传输方法和装置。
背景技术
全球移动通信联盟系统(global system for mobile communications alliance，GSMA)制定的嵌入式通用集成电路卡(embedded universal integrated circuit card，eUICC)标准允许远程配置eUICC上的用户数据，如eUICC远程从应用服务器下载用户在某一运营商网络签约的用户数据，并进而使配置该eUICC的用户设备接入该运营商的通信网络。随着窄带物联网(narrowband internet of things，NB-IoT)技术的发展，窄带物联网中的终端设备也急需应用eUICC技术标准，使得窄带物联网终端无需更换SIM卡就可以接入不同运营商的网络。
然而，NB-IoT网络的带宽和传输速率较低，以实现广覆盖和低功耗。现有的传输协议多不适合在NB-IoT网络中进行数据传输，如超文本传送安全协议(hyper text transfer protocol secure，HTTPS)消息头较大，对带宽要求较高，所以在NB-IoT网络下不适合通过HTTPS建立应用服务器与eUICC之间的会话。其次，由于HTTPS三次握手协议中有定时器保护，而NB-IoT网络的速率较低，导致定时器超时，所以在NB-IoT网络下不适合通过HTTPS建立应用服务器与eUICC之间的会话。
因此，如何在NB-IoT网络下建立应用服务器与M2M通信装置上的eUICC之间的会话，从而完成数据传输成为当前亟需解决的问题。
发明内容
本申请提供一种窄带物联网中eUICC数据传输方法和装置，可以在NB-IoT网络下建立应用服务器与M2M通信装置上的eUICC之间的会话，从而完成数据传输。
第一方面，提供了一种窄带物联网中eUICC数据传输方法，该通信方法包括：机器到机器M2M通信装置接收物联网IoT平台发送的轻量机器到机器LwM2M消息。
本申请实施例中，LwM2M消息可以包括应用指示和签约管理SM平台下发给嵌入式通用集成电路卡eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC；所述eUICC根据所述应用指示将所述LwM2M消息中的目标数据发送至所述eUICC上的应用。
本申请实施例对IoT平台发送的LwM2M消息不做具体限定。作为一个示例，IoT平台下发的LwM2M消息中的目标数据可以包括所述签约管理SM平台下发给eUICC的目标运营商的 简介profile或所述profile的激活信息，例如，eUICC可以根据profile或所述profile的激活信息完成目标运营商profile的下载或激活。作为一个示例，IoT平台下发的LwM2M消息中的目标数据可以配置信息，例如，eUICC可以根据接收到的配置信息进行相应的配置。
本申请实施例中，M2M通信装置可以将LwM2M消息发送至与M2M通信装置关联的eUICC，应用服务器可以在LwM2M协议下，可以通过物联网IoT平台与M2M终端上的eUICC进行数据传输。
可选地，在一些实施例中，IoT平台下发的LwM2M消息中的目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
应理解，所述M2M通信装置与所述eUICC关联，所述LwM2M消息包括应用标识以及所述目标运营商的profile的下载或激活信息，应用指示用于指示所述eUICC将所述目标运营商的profile的下载或激活信息转发至所述eUICC上的应用。
本申请实施例中请求消息包括嵌入式通用集成电路卡eUICC需要从当前运营商切换至目标运营商的简介profile的下载或激活信息。
应理解，IoT平台可以将SM平台发送的请求消息转换至LwM2M协议下的LwM2M消息。将SM平台发送的请求消息转换成LwM2M消息后，LwM2M消息对应的消息格式(DataFormat)可以与请求消息的一致。
本申请实施例对IoT平台向M2M通信装置发送LwM2M消息的实现方式不做具体限定。作为一个示例，IoT平台可以将LwM2M消息发送至M2M通信装置，M2M通信装置可以根据LwM2M消息中的应用指示，可以将该LwM2M消息转发至目标eUICC。作为另一个示例，IoT平台可以将LwM2M消息发送至M2M通信装置，M2M通信装置可以根据第一LwM2M消息中的第一标识，可以将该LwM2M消息发送给M2M通信装置的client模块，M2M通信装置的client模块可以将该第一LwM2M消息发送给M2M通信装置的server模块，M2M通信装置的server模块可以将该第一LwM2M消息发送至目标eUICC。
上述技术方案中，可以使得eUICC支持LwM2M完成profile的下载和激活。
结合第一方面，在第一方面的某些可能的实现方式中，所述LwM2M消息还包括第一标识。
应理解，所述第一标识可以用于指示所述M2M通信装置将所述目标运营商的profile的下载或激活信息转发至所述eUICC。
eUICC可以根据一LwM2M消息中的应用指示，将该LwM2M消息中的目标运营商的profile的下载或激活信息转发至eUICC上的应用App。
在第一方面的某些可能的实现方式中，所述IoT平台接收所述M2M通信装置发送的第一LwM2M注册请求。
所述第一LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册，所述第一LwM2M注册请求包括第一标识，所述第一标识用于指示所述第一LwM2M注册请求是由eUICC的LwM2M客户端发送的。
应理解，eUICC可以请求直接向IoT平台进行LwM2M注册，此时，由于eUICC与M2M通信装置关联，该M2M通信装置可以将eUICC向IoT平台请求注册的第一LwM2M注册信息转发至IoT平台，该M2M通信装置可以称为支持LwM2M GW route模式。
在M2M通信装置可以支持LwM2M GW route的实施例中，第一标识可以为例如，？sd＝eUICC。该第一标识可以用于指示M2M通信装置将IoT平台发送的LwM2M请求消息发送至eUICC。在LwM2M注册过程中，该第一标识可以用于指示IoT平台，M2M通信装置发送的LwM2M注册请求消息中可以包括eUICC请求向IoT平台进行LwM2M注册。
可选地，在一些可能的实施例中，可以通过预先配置，可以使M2M通信装置支持LwM2M GW route，eUICC支持LwM2M协议，IoT平台支持LwM2M协议。
在第一方面的某些可能的实现方式中，在所述IoT平台向机器M2M通信装置发送所述第一LwM2M消息之前，所述方法还包括：所述IoT平台接收所述M2M通信装置发送的第一LwM2M注册请求。
本申请实施例中eUICC可以向M2M通信装置请求进行LwM2M注册，M2M通信装置可以请求向IoT平台进行LwM2M注册，使得该eUICC可以根据SM平台发送的profile下载和激活请求从而可以完成profile的下载和激活。该M2M通信装置可以称为支持LwM2M GW代理(proxy)模式。
可选地，在一些可能的实施例中，可以通过预先配置，可以使M2M通信装置支持LwM2M GW proxy模式，eUICC支持LwM2M协议，IoT平台支持LwM2M协议。
在第一方面的某些可能的实现方式中，在所述IoT平台向机器M2M通信装置发送所述第一LwM2M消息之前，所述方法还包括：所述IoT平台接收所述M2M通信装置的client模块发送的第二LwM2M注册请求。
应理解，所述第二LwM2M注册请求用于所述M2M通信装置请求向所述IoT平台进行LwM2M注册。
在第一方面的某些可能的实现方式中，所述方法还包括：所述M2M通信装置接收所述eUICC发送的响应消息。
应理解，所述响应消息为所述eUICC上的应用对所述SM平台发送的请求消息的响应结果，所述响应消息包括应用指示和第一标识，所述第一标识用于指示将所述响应消息发送至所述IoT平台，所述应用指示用于指示将所述响应消息返回至所述SM平台。
第二方面，提供了一种窄带物联网中eUICC数据传输方法，该方法包括：机器到机器M2M通信装置接收物联网IoT平台发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给嵌入式通用集成电路卡eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC。
本申请实施例中，M2M通信装置可以将LwM2M消息发送至与M2M通信装置关联的eUICC，应用服务器可以在LwM2M协议下，可以通过物联网IoT平台与M2M终端上的eUICC进行数据传输。
结合第二方面，在第二方面的某些可能的实现方式中，所述第一LwM2M消息包括应用指示以及签约管理SM平台下发的目标运营商的简介profile的下载或激活信息，所述M2M通信装置与嵌入式通用集成电路卡eUICC相关联，所述eUICC需要从当前运营商切换至所述目标运营商，所述应用指示用于指示所述eUICC将所述目标运营商的profile的下载或激活信息转发至所述eUICC上的应用。
在第二方面的某些可能的实现方式中，所述M2M通信装置根据所述LwM2M消息中的应用指示，将所述SM下发的profile或所述profile的激活信息发送至所述eUICC。
在第二方面的某些可能的实现方式中，所述方法还包括：所述M2M通信装置接收所述eUICC发送的所述响应消息；所述M2M通信装置根据所述应用指示将收到的所述响应消息发送至所述SM平台。
本申请实施例中，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示。
结合第二方面，在第二方面的某些可能的实现方式中，所述LwM2M消息还包括第一第一标识，所述第一标识用于指示所述IoT平台与所述eUICC之间的通信。
在第二方面的某些可能的实现方式中，所述M2M通信装置根据所述LwM2M消息中的第一第一标识，将所述profile或所述profile的激活信息发送至所述eUICC。
在第二方面的某些可能的实现方式中，所述M2M通信装置接收所述eUICC发送的所述响应消息；所述M2M通信装置将所述响应消息发送至所述SM平台。
本申请实施例中，所述响应消息包括所述应用指示和所述第一标识。
在第二方面的某些可能的实现方式中，在所述M2M通信装置将所述profile或所述profile的激活信息发送至所述eUICC之前，所述方法还包括：所述M2M通信装置接收所述eUICC发送的LwM2M注册请求；所述M2M通信装置将所述LwM2M注册请求发送至所述IoT平台，所述LwM2M注册请求包括所述第一标识。
本申请实施例中，所述LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册。
第三方面，提供了一种窄带物联网中eUICC数据传输方法，该方法包括：嵌入式通用集成电路卡eUICC接收机器到机器M2M通信装置发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信，所述eUICC与所述M2M通信装置关联；所述eUICC根据所述应用指示将所述LwM2M消息中的目标数据发送至所述eUICC上的应用。
结合第三方面，在第三方面的某些可能的实现方式中，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
本申请实施例中，所述第一LwM2M消息包括应用指示以及签约管理SM平台下发的目标运营商的简介profile或所述profile的激活信息，所述profile或所述profile的激活信息用于指示嵌入式通用集成电路卡eUICC从当前运营商切换至所述目标运营商，所述应用指示用于指示所述SM平台与所述eUICC上的应用之间的通信。
结合第三方面，在第三方面的某些可能的实现方式中，所述方法还包括：所述eUICC向所述机器到机器M2M通信装置发送响应消息。
本申请实施例中，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示。
结合第三方面，在第三方面的某些可能的实现方式中，在所述嵌入式通用集成电路卡eUICC接收机器到机器M2M通信装置发送的第一轻量机器到机器LwM2M消息之前，所述方法 还包括：所述eUICC向所述M2M通信装置发送LwM2M注册请求。
本申请实施例中，所述LwM2M注册请求用于所述eUICC请求向物联网IoT平台进行LwM2M注册，或用于所述eUICC请求向所述IoT平台进行LwM2M注册。
第四方面，提供了一种窄带物联网中eUICC数据传输方法，该方法包括：物联网IoT平台接收签约管理SM平台发送的请求消息，所述请求消息包括应用指示和签约管理SM平台下发给eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；所述IoT平台将所述请求消息转换成轻量机器到机器LwM2M消息；所述IoT平台向机器到机器M2M通信装置发送所述LwM2M消息，所述M2M通信装置与所述eUICC关联。
结合第四方面，在第四方面的某些可能的实现方式中，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
本申请实施例中，所述请求消息包括目标运营商的简介profile或所述profile的激活信息，所述profile或所述profile的激活信息用于指示嵌入式通用集成电路卡eUICC从当前运营商切换至所述目标运营商。
上述提及的LwM2M消息包括应用指示以及所述profile或所述profile的激活信息，所述所述应用指示用于指示所述SM平台与所述eUICC上的应用之间的通信。
应理解，IoT平台可以将SM平台发送的请求消息转换至LwM2M协议下的LwM2M消息。将SM平台发送的请求消息转换成LwM2M消息后，LwM2M消息对应的消息格式(DataFormat)可以与请求消息的一致。
本申请实施例对IoT平台向M2M通信装置发送LwM2M消息的实现方式不做具体限定。作为一个示例，IoT平台可以将LwM2M消息发送至M2M通信装置，M2M通信装置可以根据LwM2M消息中的应用指示，可以将该LwM2M消息转发至目标eUICC。作为另一个示例，IoT平台可以将LwM2M消息发送至M2M通信装置，M2M通信装置可以根据LwM2M消息中的第一第一标识，可以将该LwM2M消息发送给M2M通信装置的client模块，M2M通信装置的client模块可以将该LwM2M消息发送给M2M通信装置的server模块，M2M通信装置的server模块可以将该LwM2M消息发送至目标eUICC。
上述技术方案中，可以使得eUICC支持LwM2M完成profile的下载和激活。
结合第四方面，在第四方面的某些可能的实现方式中，所述方法还包括：所述IoT平台接收所述M2M通信装置发送的响应消息；所述IoT平台根据所述应用指示将所述响应消息发送至所述SM平台。
本申请实施例中，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示。
在第四方面的某些可能的实现方式中，所述LwM2M消息还包括第一第一标识，所述第一第一标识用于指示所述IoT平台与所述eUICC之间的通信。
在第四方面的某些可能的实现方式中，在所述IoT平台向机器到机器M2M通信装置发送所述LwM2M消息之前，所述方法还包括：所述IoT平台接收所述M2M通信装置发送的LwM2M注册请求。
本申请实施例中，所述LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M 注册，所述LwM2M注册请求包括所述第一标识。
应理解，eUICC可以请求直接向IoT平台进行LwM2M注册，此时，由于eUICC与M2M通信装置关联，该M2M通信装置可以将eUICC向IoT平台请求注册的LwM2M注册信息转发至IoT平台，该M2M通信装置可以称为支持LwM2M GW route模式。
在M2M通信装置可以支持LwM2M GW route的实施例中，第一第一标识可以为例如，？sd＝eUICC。该第一标识可以用于指示M2M通信装置将IoT平台发送的LwM2M请求消息发送至eUICC。在LwM2M注册过程中，该第一标识可以用于指示IoT平台，M2M通信装置发送的LwM2M注册请求消息中可以包括eUICC请求向IoT平台进行LwM2M注册。
在第四方面的某些可能的实现方式中，所述方法还包括：所述IoT平台接收所述M2M通信装置发送的响应消息，所述响应消息包括所述应用指示和所述第一第一标识；所述根据所述应用指示将所述响应消息发送至所述SM平台。
第五方面，提供了一种机器到机器M2M通信装置，所述M2M通信装置包括嵌入式通用集成电路卡eUICC，所述M2M通信装置包括：
第一接收模块，用于接收物联网IoT平台发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给嵌入式通用集成电路卡eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；
第一发送模块，用于将所述LwM2M消息发送至与之关联的所述eUICC；
第二发送模块，用于所述eUICC根据所述应用指示将所述LwM2M消息中的目标数据发送至所述eUICC上的应用。
在第五方面的某些可能的实现方式中，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
在第五方面的某些可能的实现方式中，第一发送模块具体用于：根据所述LwM2M消息中的应用指示，将所述SM下发的profile或所述profile的激活信息发送至所述eUICC。
在第五方面的某些可能的实现方式中，所述M2M通信装置还包括：
第三发送模块，用于向所述M2M通信装置发送响应消息，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示；
第四发送模块，用于根据所述应用指示将收到的所述响应消息发送至所述SM平台。
在第五方面的某些可能的实现方式中，所述LwM2M消息还包括第一标识，所述第一标识用于指示所述IoT平台与所述eUICC之间的通信。
在第五方面的某些可能的实现方式中，第一发送模块具体用于：根据所述第一LwM2M消息中的第一标识，将所述profile或所述profile的激活信息发送至所述eUICC。
在第五方面的某些可能的实现方式中，所述M2M通信装置还包括：
第五发送模块，用于所述eUICC上的应用向所述M2M通信装置发送所述响应消息；
第六发送模块，用于将所述响应消息发送至所述SM平台，其中，所述响应消息包括所述应用指示和所述第一标识。
在第五方面的某些可能的实现方式中，所述M2M通信装置还包括：
第七发送模块，用于所述eUICC向所述M2M通信装置发送LwM2M注册请求，所述LwM2M 注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册；
第八发送模块，用于所述M2M通信装置将收到的所述LwM2M注册请求发送至所述IoT平台，所述LwM2M注册请求包括所述第一标识。
第六方面，提供了一种机器到机器M2M通信装置，所述M2M通信装置包括：
第一接收模块，用于接收物联网IoT平台发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给嵌入式通用集成电路卡eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；
第一发送模块，用于将所述LwM2M消息发送至与之关联的所述eUICC。
在第六方面的某些可能的实现方式中，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
在第六方面的某些可能的实现方式中，第一发送模块具体用于：根据所述LwM2M消息中的应用指示，将所述SM下发的profile或所述profile的激活信息发送至所述eUICC。
在第六方面的某些可能的实现方式中，所述M2M通信装置还包括：
第二接收模块，用于接收所述eUICC发送的所述响应消息，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示；
第二发送模块，用于根据所述应用指示将收到的所述响应消息发送至所述SM平台。
在第六方面的某些可能的实现方式中，所述LwM2M消息还包括第一第一标识，所述第一标识用于指示所述IoT平台与所述eUICC之间的通信。
在第六方面的某些可能的实现方式中，第一发送模块具体用于：根据所述LwM2M消息中的第一标识，将所述profile或所述profile的激活信息发送至所述eUICC。
在第六方面的某些可能的实现方式中，所述M2M通信装置还包括：
第三接收模块，用于接收所述eUICC发送的所述响应消息；
第三发送模块，用于将所述响应消息发送至所述SM平台，其中，所述响应消息包括所述应用指示和所述第一标识。
在第六方面的某些可能的实现方式中，所述M2M通信装置还包括：
第四接收模块，用于接收所述eUICC发送的LwM2M注册请求，所述LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册；
第四发送模块，用于将所述LwM2M注册请求发送至所述IoT平台，所述LwM2M注册请求包括所述第一标识。
第七方面，提供了一种嵌入式通用集成电路卡eUICC，所述eUICC包括：
第一接收模块，用于接收机器到机器M2M通信装置发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信，所述eUICC与所述M2M通信装置关联；
第一发送模块，用于根据所述应用指示将所述LwM2M消息中的目标数据发送至所述eUICC上的应用。
在第七方面的某些可能的实现方式中，所述目标数据包括所述签约管理SM平台下发给 eUICC的目标运营商的简介profile或所述profile的激活信息。
在第七方面的某些可能的实现方式中，所述eUICC还包括：
第二发送模块，用于向所述机器到机器M2M通信装置发送响应消息，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示。
在第七方面的某些可能的实现方式中，所述eUICC还包括：
第三发送模块，用于向所述M2M通信装置发送LwM2M注册请求，所述LwM2M注册请求用于所述eUICC请求向物联网IoT平台进行LwM2M注册，或用于所述eUICC请求向所述IoT平台进行LwM2M注册。
第八方面，提供了一种物联网IoT平台，所述平台包括：
第一接收模块，用于接收签约管理SM平台发送的请求消息，所述请求消息包括应用指示和签约管理SM平台下发给eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；
处理模块，用于将所述请求消息转换成第一轻量机器到机器LwM2M消息；
第一发送模块，用于向机器到机器M2M通信装置发送所述LwM2M消息，所述M2M通信装置与所述eUICC关联。
在第八方面的某些可能的实现方式中，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
在第八方面的某些可能的实现方式中，所述平台还包括：
第二接收模块，用于接收所述M2M通信装置发送的响应消息，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示；
第二发送模块，用于根据所述应用指示将所述响应消息发送至所述SM平台。
在第八方面的某些可能的实现方式中，所述LwM2M消息还包括第一标识，所述第一标识用于指示所述IoT平台与所述eUICC之间的通信。
在第八方面的某些可能的实现方式中，所述平台还包括：
第三接收模块，用于接收所述M2M通信装置发送的LwM2M注册请求，所述LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册，所述LwM2M注册请求包括所述第一标识。
在第八方面的某些可能的实现方式中，所述平台还包括：
第四接收模块，用于接收所述M2M通信装置发送的响应消息，所述响应消息包括所述应用指示和所述第一标识；
第三发送模块，用于根据所述应用指示将所述响应消息发送至所述SM平台。
第九方面，提供了一种机器到机器M2M通信装置，所述所述M2M通信装置包括嵌入式通用集成电路卡eUICC，所述M2M通信装置包括：接收器、发送器、存储器和处理器。
其中，该接收器、发送器、存储器通过内部连接通路互相通信。所述接收器用于接收所述M2M通信装置之外的装置发送的消息或数据，并转发给所述处理器；所述发送器用于根据所述处理器的指令向所述eUICC发送消息或数据；所述存储器用于存储程序；所述处 理器用于执行所述存储器中存储的程序，当所述程序被执行时，所述M2M通信装置执行如执行第一方面或第一方面的任一种可能的实现方式中的方法。
第十方面，提供了一种机器到机器M2M通信装置，包括：接收器、发送器、存储器和处理器。
其中，该接收器、发送器、存储器通过内部连接通路互相通信。所述接收器用于接收所述M2M通信装置之外的装置发送的消息或数据，并转发给所述处理器；所述发送器用于根据所述处理器的指令向所述M2M通信装置之外的装置发送消息或数据；所述存储器用于存储程序；所述处理器用于执行所述存储器中存储的程序，当所述程序被执行时，所述M2M通信装置执行如执行第二方面或第二方面的任一种可能的实现方式中的方法。
第十一方面，提供了一种嵌入式通用集成电路卡eUICC，其特征在于，所述eUICC包括：接收器、发送器、存储器和处理器。
其中，所述接收器用于接收所述eUICC之外的装置发送的消息或数据，并转发给所述处理器；所述发送器用于根据所述处理器的指令向所述eUICC上的应用发送消息或数据；所述存储器用于存储程序；所述处理器用于执行所述存储器中存储的程序，当所述程序被执行时，使得该eUICC执行如第三方面或第三方面的任一种可能的实现方式中的方法。
第十二方面，提供了一种物联网IoT平台，包括：接收器、发送器、存储器和处理器。
其中，所述接收器用于接收所述IoT平台之外的装置发送的消息或数据，并转发给所述处理器；所述发送器用于根据所述处理器的指令向所述IoT平台之外的装置发送消息或数据；所述存储器用于存储程序；所述处理器用于执行所述存储器中存储的程序，当所述程序被执行时，使得该IoT平台执行如第四方面或第四方面的任一种可能的实现方式中的方法。
第十三方面，提供了一种提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行上述任一方面的任意可能的实现方式中的方法的指令。
第十四方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码被计算机运行时，使得该计算机执行上述任一方面的任意可能的实现方式中的方法。
第十五方面，提供了一种通信芯片，其中存储有指令，当其在无线通信的装置上运行时，使得所述通信芯片执行上述任一方面的任意可能的实现方式中的方法。
附图说明
图1是一种可能的实现eUICC远程配置和管理的体系架构的示意性框图。
图2一种可能的LwM2M协议栈的示意性框图。
图3是本申请实施例提供的一种基于LwM2M协议建立SM平台与eUICC之间的会话的示意性框图。
图4是一种可能的终端设备的示意性框图。
图5是一种调制解调器modem的示意性框图。
图6是本申请实施例提供的一种通信方法的示意性流程图。
图7是本申请实施例提供的一种可能的通信方法的示意性流程图。
图8是本申请实施例提供的另一种可能的通信方法的示意性流程图。
图9是本申请实施例提供的机器到机器M2M通信装置900的示意性框图。
图10是本申请实施例提供的嵌入式通用集成电路卡eUICC 1000的示意性框图。
图11是本申请实施例提供的物联网IoT平台1100的示意性框图。
图12是本申请实施例提供的一种机器到机器M2M通信装置1200的示意性框图。
图13是本申请实施例提供的一种嵌入式通用集成电路卡eUICC 1300的示意性框图。
图14是本申请实施例提供的一种物联网IoT平台1400的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
应理解，本申请实施例的技术方案可以应用于各种通信系统，例如：基于蜂窝的窄带物联网(narrow band internet of things，NB-IoT)系统、全球移动通讯(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、未来的第五代(5th generation，5G)系统或新无线(new radio，NR)等。
本申请实施例对终端设备的类型不做具体限定，例如可以是用户设备、接入终端、终端设备、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线网络设备、用户代理或用户装置。终端可以包括但不限于移动台(mobile station，MS)、移动电话(mobile telephone)、用户设备(user equipment，UE)、手机(handset)、便携设备(portable equipment)、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、物流用的射频识别(radio frequency identification，RFID)终端设备，具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备、物联网、车辆网中的终端设备以及未来5G网络中的终端设备或者未来演进的公共陆地移动网络(public land mobile network，PLMN)网络中的终端设备等。
作为示例而非限定，在本发明实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
作为另一个示例，在本发明实施例中，该终端设备可以是各种高速移动的载体，例如，共享单车，共享汽车等。该终端设备还可以是各种智能表具，例如，水表、电表、燃气表等。该终端设备还可以是各种监控设备或家电设备。
图1是一种实现eUICC远程配置和管理的体系架构的示意性框图。
图1所示的实现eUICC远程配置和管理的体系架构可以包括签约管理(subscription management，SM)平台110、eUICC 120。在GSMA的制定的eUICC标准中，SM平台110可以建立与eUICC 120之间的会话。SM平台110可以基于空中接口(over the air，OTA)切换eUICC 120上加载的简介profile，从而可以实现eUICC 120从当前的移动网络运营商(mobile network operators，MNO)切换至目标MNO。
应理解，profile为通信领域的一个专用术语，可以理解为用户签约数据集，或用于在某个运营商网络签约的个人签约业务数据的集合，是一个移动用户信息的数据集合，可以包括用户识别信息(例如用户身份、认证参数等信息)和业务签约信息。
profile中包含的数据例如可以包括但不限于：profile类型，例如，用户身份识别(subscriber identification module，SIM)联盟简介包(SIM profile alliance package)；国际移动用户识别(international mobile subscriber identification，IMSI)码；集成电路卡识别(integrate circuit card identity，ICCID)码；安全数字(secure digital，SD)存储卡的可执行文件加载辅助(aide，AID)程序(executable load file AID for SD)；SD存储卡的可执行模块辅助(executable module AID for SD)等。
具体地，SM平台110可以在收到目标MNO或用户发送的profile下载请求之后，可以通过短信将生成的profile下发至eUICC 120，SM平台110对eUICC 120中的profile进行管理。例如，SM平台110可以通知eUICC 120下载或激活profile，从而实现eUICC 120从当前的MNO切换至目标MNO。
应理解，SM平台110可以是一种应用服务器。
下面分别对SM平台110、eUICC 120进行介绍。
SM平台110是eUICC远程管理的核心，SM平台110可以根据MNO或用户发起的请求对profile进行下载、安装、激活、去激活、删除等管理操作。SM平台110的功能主要包括两部分：签约管理数据准备(subscription management data preparation，SM-DP)、签约管理安全路由(subscription management secure routing，SM-SR)。其中，SM-DP主要负责根据目标MNO提供的数据生成和存储profile。SM-SR主要负责建立到eUICC 120的通道，并可以将SM-DP生成的profile路由下载到eUICC 120上。
eUICC 120可以是嵌入式UICC卡，可以与终端设备中的如调制解调器modem(可以是电路或基带芯片)连接。eUICC 120可以通过modem与终端设备外的其它装置或设备通信。eUICC 120可以给用户提供基于空中接口(over the air，OTA)实现MNO变更的能力，而不需要更换eUICC物理实体本身。eUICC 120可以提供与普通智能卡类似的移动网络接入鉴权和用户身份认证的安全服务，并可以用于远程管理多个移动网络运营个人管理服务。
下面对profile的几种管理操作进行描述。
profile下载：SM平台可以根据MNO或用户请求，可以将生成的profile通过建立的传输通道传送到eUICC中。
profile安装：eUICC可以将下载的profile安装为可执行的应用和文件系统，profile安装可以和profile下载同时进行，成功安装的profile可以进入去激活状态。
profile激活：根据MNO或用户请求，SM平台可以将eUICC上当前处于去激活状态profile激活，使得profile中的文件和应用可以通过终端设备和eUICC之间的接口进行选择。
profile去激活：根据MNO或用户请求，SM平台可以将eUICC上当前处于激活状态的profile去激活，使得profile中的文件和应用不可以通过终端设备和eUICC之间的接口进行选择。
轻量机器到机器(light weight machine to machine，LwM2M)是开放移动联盟(open mobile alliance，OMA)定义的物联网协议。
LwM2M的协议栈结构可以参见图2。其中，LwM2M协议210属于应用层协议，位于约束应用协议(constrained Application protocol，CoAP)220之上。CoAP 220可以进行数据包传输层安全性协议(datagram transport layer security，DTLS)230加密的处理，最后可以通过用户数据包协议(user packet protocol，UDP)240或短消息业务(short message service，SMS)250或SMS255的方式传送。该LwM2M协议可以将消息打包到对象(objects，Obj)260中，并可以通过上述协议进行传输。后面会具体描述Objects，此处不再赘述。
应理解，SMS250可以是位于设备(on device)上的短消息业务，SMS255可以是位于智能卡(on smartcard)上的短消息业务。
LwM2M协议的消息头较HTTPS的消息头较小，且LwM2M协议不需要通过多次握手就可以建立物联网IoT平台(作为服务器sever)和终端设备上的M2M通信装置(作为客户端client)之间的会话。因此在NB-IoT网络中，可以通过LwM2M协议建立应用服务器(例如，SM平台)与终端设备上的eUICC之间的会话，从而实现数据传输。
下面以图3为示例，详细描述通过LwM2M协议建立应用服务器(例如，SM平台)与终端设备上的eUICC之间的会话。
图3是本申请实施例提供的一种基于LwM2M协议建立SM平台与eUICC之间的会话的示意性框图。
图3可以包括SM平台310、IoT平台320、终端设备330、M2M通信装置340、eUICC 350。
SM平台310可以对应到图1中的SM平台110，可以将MNO发送的profile下载请求通过IoT平台发送至终端设备330。SM平台310可以将MNO发送的profile下载请求转换成LwM2M消息(例如，可以将profile下载请求打包到LwM2M Objects)后发送至IoT平台320，也可以将MNO发送的profile下载请求转换成其它类型的消息发送至IoT平台320。
IoT平台320可以作为LwM2M协议中的设备管理平台，IoT平台320可以将SM平台310发送的消息通过LwM2M协议发送至终端设备330，当SM平台310和IoT平台320间不是通过LwM2M协议进行消息传输时，IoT平台320需要将SM平台310发送的消息转换为LwM2M消息后发送至终端设备330，IoT平台320收到的终端设备330的LwM2M消息，也要先进行协议转换后，才能转发给SM平台310。
终端设备330中配置了M2M通信装置340和eUICC350，终端设备330接收到的LwM2M 消息可以由终端设备330上的M2M通信装置340处理。终端设备330的示意性结构图可以如图4所示。
M2M通信装置340可以是芯片，也可以是集成电路或其他装置，M2M通信装置340可以将接收到的LwM2M消息转发至eUICC350。M2M通信装置340的示意性结构图可以如图5所示。
eUICC 350可以对应到图1中的eUICC 120。eUICC350和M2M通信装置340可以进行通信和信息交换。物理形态上，eUICC 350可以是独立于M2M通信装置340的装置，eUICC350也可以是与M2M通信装置340中绑定在一起的装置(例如，通过焊接的方式或其他方式将eUICC350嵌入在M2M通信装置340中)。eUICC350通过M2M通信装置340上的收发器将接收到的LwM2M消息转发至eUICC350上的应用。
图4是一种可能的终端设备的示意性框图。图4中的终端设备330可以包括应用处理器(application processor，AP)410、调制解调器(modem)420、无线收发器430、eUICC480，可选的，还包括用户接口440、存储器450、相机460、语音输入输出接口470。
AP 410可以是在低功耗的中央处理器(central processing unit，CPU)的基础上扩展时频功能和专用接口的超大规模集成电路，AP 410上运行了操作系统和应用软件。
modem 420可以对应于图3中的M2M通信装置340。modem 420可以被称为基带芯片，主要的作用是发送和接受各种数据，如实现第三代合作伙伴计划(3rd generation partnership project，3GPP)等无线通信标准中的主要功能。modem 420相当于一个通信协议处理器，可以负责数据处理。
modem 420可以作为单独的芯片，也可以与其他芯片或电路在一起形成系统级芯片或集成电路。该芯片或集成电路可以应用于所有实现无线通信功能的终端设备。
终端设备330可以通过无线收发器430进行数据的接收和发送。
存储器450可以用于存储计算机程序指令、预设的参数、计算机中间运算得到的数据等中间的一个或多个。
下面以M2M通信装置340为modem 420，对modem 420的内部逻辑结构进行描述。
图5是本申请实施例提供的一种调制解调器modem的示意性框图。图5所示的调制解调器(modem)420可以包括接收数据处理器510、控制器520、发送数据处理器530。
数据接收器510可以通过物理层(physical layer，PHY)协议接收IoT平台发送的数据，并可以经过信道解码、解调、均衡、信道估计等功能对接收到的数据进行解调。
处理器520可以通过协议层对数据进行处理，处理器520可以通过介质访问控制(media access control，MAC)层协议、无线链路控制(radio link control，RLC)层协议、分组数据汇聚协议(packet data convergence protocol，PDCP)、无线资源控制(radio resource control，RRC)层协议对数据进行处理。
数据发送器530可以经过信道编码、调制、符号生成等处理之后的数据进行调制，并可以通过PHY层协议向与modem 420相连的UICC发送数据。
图5所示的modem 420中还可以内置存储，称为片内存储器，例如，终端设备至计算机多路转接器(terminal device to computer multiplexer，TCM)、静态随机存取存储器(static random access memory，SRAM)等。
modem 420还可以与片外存储器进行通信，片外存储器可以包括但不限于：只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、U盘、移动硬盘、光盘、磁性存储装置等。
本申请实施例提供的通信方法可以在NB-IoT网络下建立应用服务器(如SM平台)与M2M通信装置上的eUICC之间的会话，从而完成数据传输。
下面对本申请实施例提供的通信方法进行描述。
图6是本申请实施例提供的一种通信方法的示意性流程图。图6的方法可以包括步骤610-630，下面分别对步骤610-630进行描述。
在步骤610中，M2M通信装置接收IoT平台发送的LwM2M消息。
本申请实施例对IoT平台发送的LwM2M消息不做具体限定。作为一个示例，该LwM2M消息可以包括SM平台下发给eUICC用户在目标运营商签约的profile或所述profile的激活信息。作为另一个示例，eUICC上运行的个人支付应用和应用服务器间还可以通过IoT平台和M2M通信装置间的LwM2M消息传输个人支付和消费信息。
本申请实施例中的M2M通信装置是终端设备中的一个通信模块，该M2M通信装置可以是一个芯片，也可以是集成电路或其他装置。该M2M通信装置可应用于所有实现无线通信功能的设备。作为一个示例，该M2M通信装置可以是调制解调器modem，具体有关modem的描述请参见图5的描述，此处不再赘述。
LwM2M消息可以包括一个应用指示(例如，App ID)，M2M通信装置可以根据应用指示将LwM2M消息转发至eUICC上的应用。
具体地，IoT平台可以将LwM2M消息转发至机器到机器M2M通信装置，LwM2M消息中的应用指示(例如，App ID)可以用于指示本次通信为SM平台与eUICC上的应用之间的通信。所谓eUICC上的应用，指在eUICC上运行的应用实例或应用进程或应用程序。
以LwM2M消息为profile或所述profile的激活信息为例，M2M通信装置在向IoT平台发送上行消息的过程中，该应用指示可以用于指示将返回的对目标运营商的profile或所述profile的激活信息的响应结果发送至SM平台。M2M通信装置在接收IoT平台发送的下行消息的过程，该应用指示可以用于指示M2M通信装置将目标运营商的profile或所述profile的激活信息转发至所述eUICC上的应用。
在步骤620中，M2M通信装置将LwM2M消息发送至与之关联的eUICC。
应理解，eUICC可以M2M通信装置相连，eUICC可以通过M2M通信装置与终端设备外的其它装置或设备通信。
本申请实施例中M2M通信装置将LwM2M消息发送至eUICC的实现方式不做具体限定。作为一个示例，可以根据LwM2M消息中的应用指示，将所述SM下发的LwM2M消息发送至所述eUICC。作为一个示例，还可以根据LwM2M消息中的第一指示，将所述SM下发的LwM2M消息发送至所述eUICC。下面会结合图7至图8进行详细描述，此处不再赘述。
在步骤630中，eUICC根据应用指示将LwM2M消息中的目标数据发送至eUICC上的应用。
本申请实施例中，应用服务器可以通过LwM2M协议建立应用服务器与M2M通信装置上的eUICC之间的会话，从而完成数据传输。
可选地，在一些实施例中，LwM2M消息可以包括签约管理SM平台下发给eUICC的目标 运营商的profile或所述profile的激活信息。
下面以LwM2M消息包括profile或所述profile的激活信息为例进行说明。
IoT平台可以将SM平台发送的请求消息转换至LwM2M协议下的LwM2M消息。例如，本申请可以将SM平台发送的请求消息打包到LwM2M应用数据对象(App Data Container Obj)中，可以实现将SM平台发送的请求消息转换至LwM2M协议下的LwM2M消息。
应理解，在LwM2M协议中，对于每一个LwM2M实体(例如，每一个支持LwM2M协议的设备)，可访问服务被抽象为一个一个的对象，每一个对象局可以有三种层次。作为一个示例，一个对象可以包括若干个提供不同功能的对象(Object)，例如，若干个不同的传感器。作为另一个示例，上述每一种功能可能由多个对象实例(Object-Instance)提供，例如，对个温度传感器，都提供温度读取功能。作为另一个示例，上述对象实例实际可以完成的功能可以称为资源(Resource)。
在LwM2M协议中，统一资源标识符(universal resource identifier，URI)的格式可以如下所示：</Object ID/Object-Instance ID/Resource ID>。例如，常用的URI格式可以有</1/0>、</1/1>、</2/0>、</2/1>、</2/2>、</2/3>、</2/4>、</3/0>、</4/0>、</5/0>、</19/0>、</19/1>。
需要注意的是，URI分别标识了访问资源的Object ID、Object-Instance ID、Resource ID，其中，后两个ID可以是可选地。
本申请实施例中签约管理SM平台可以将目标运营商的简介profile的下载或激活请求信息发送至IoT平台。发送的下载或激活请求信息中可以包括目标eUICC的信息，以便于目标eUICC可以将目标运营商的简介profile下载、安装或激活，可以使得目标eUICC从当前运营商的profile切换至目标运营商的profile。
可选地，在一些实施例中，第一LwM2M消息还包括第一标识，所述第一标识用于指示所述M2M通信装置将所述目标运营商的profile的下载或激活信息转发至所述eUICC。
本申请实施例中，可以在IoT平台向M2M通信装置发送第一LwM2M消息之前，IoT平台可以接收第一LwM2M注册请求。IoT平台还可以接收第二LwM2M注册请求，该第二LwM2M注册请求可以用于M2M通信装置请求向IoT平台进行LwM2M注册。
下面以eUICC请求向IoT平台LwM2M注册为例进行详细说明。
本申请实施例中eUICC可以请求直接向IoT平台LwM2M注册，此时，由于eUICC与M2M通信装置关联，该M2M通信装置可以将eUICC向IoT平台请求注册的第一LwM2M注册信息转发至IoT平台，该M2M通信装置可以称为支持LwM2M网关(getway，GW)路由(route)模式。
可选地，在一些实施例中，可以通过预先配置，M2M通信装置可以支持LwM2M GW route模式，eUICC支持LwM2M协议，IoT平台支持LwM2M协议。
具体地，如果M2M通信装置可以支持LwM2M GW route模式，可以对M2M通信装置、IoT平台、eUICC进行预先配置。
作为一个示例，可以通过软件代码实现对M2M通信装置的预先配置，该M2M通信装置可以支持LwM2M gateway route的功能，该M2M通信装置能够解析eUICC卡的LwM2M消息，实现支持通过LwM2M协议进行数据传输。
作为另一个示例，可以通过软件代码实现对IoT平台的预先配置，该IoT平台支持在LwM2M协议下进行数据传输。例如，可以预先配置eUICC App可以作为LwM2M服务器(server)上的某个APP，IoT平台可以将该LwM2M消息转发至LwM2M client上的某个App，实现支持通过LwM2M协议进行数据传输。又如，可以预先配置该IoT平台支持解析新的应用标识(例如，第一标识(例如？sd＝))，实现支持通过LwM2M协议进行数据传输。
应理解，该IoT平台可以持解析新的应用标识，当该IoT平台受到具有相同的互联网协议(internet protocal，IP)和端口(port)的两个客户端(client)模块，该IoT平台可以根据解析出的第一标识(例如？sd＝)确定其中一个client可以是eUICC。
作为另一个示例，可以通过软件代码实现对eUICC的预先配置。eUICC支持在LwM2M协议下进行数据传输。例如，可以预先配置的eUICC可以作为LwM2M client，可以完成数据传输功能。又如，可以预先配置eUICC会话描述协议(session description protocol，SDP)文件，设置LwM2M业务，让eUICC与终端设备之间可以支持通过LwM2M协议进行数据传输。又如，可以配置嵌入式用户身份模块(embeddedsubscriber identity module，eSIM)App作为LwM2M client上的某个App，eUICC可以在收到LwM2M消息后，可以将该LwM2M消息转发至LwM2M client上的某个App，实现支持通过LwM2M协议进行数据传输。又如，可以建立eUICC到M2M通信装置的通道(服务描述service declaration)，实现支持通过LwM2M协议进行数据传输。
应理解，可以设置该eUICC作为client所支持的资源以及服务(service ID)，该service ID为LwM2M。
在一些实施例中，如果M2M通信装置可以称为支持GW route模式，该M2M通信装置可以将eUICC向IoT平台请求注册的第一LwM2M注册信息转发至eUICC，该第一LwM2M注册信息可以包括所述第一标识(例如？sd＝)。IoT平台接收到所述第一LwM2M注册信息，可以根据该第一标识(例如？sd＝)确定M2M通信装置发送的注册信息可以包括eUICC向IoT平台请求注册的第一LwM2M注册信息。下面结合图5对这种实现方式进行详细描述，此处不再赘述。
本申请实施例对M2M通信装置可以将第一LwM2M注册信息转发至eUICC的具体实现方式不做具体限定。作为一个示例，M2M通信装置可以仅将该第一LwM2M注册信息转发至eUICC，IoT平台接收到所述第一LwM2M注册信息中的第一标识(例如？sd＝eUICC)确定该注册请求是eUICC向IoT平台请求注册。作为另一个示例，M2M通信装置可以将第一LwM2M注册信息和M2M通信装置向IoT平台请求注册的注册消息都打包发送至IoT平台，IoT平台可以根据打包消息中的第一标识(例如？sd＝eUICC)确定M2M通信装置发送的注册信息eUICC向IoT平台请求注册的第一LwM2M注册信息。下面结合图8对这种实现方式进行详细描述。
下面结合具体的例子，更加详细地描述本申请实施例中，M2M通信装置可以支持LwM2M GW route模式时，可以通过LwM2M协议完成profile的下载和激活的具体实现方式。应注意，下文的例子仅仅是为了帮助本领域技术人员理解本申请实施例，而非要将申请实施例限制于所示例的具体数值或具体场景。本领域技术人员根据文所给出的例子，显然可以进行各种等价的修改或变化，这样的修改和变化也落入本申请实施例的范围内。
图7是本申请实施例提供的一种可能的通信方法的示意性流程图。图7的方法可以包 括步骤710-790，下面分别对步骤710-790进行详细描述。
应理解，本申请实施例中，eUICC可以支持LwM2M协议、M2M通信装置支持LwM2M GW路由(route)模式，eUICC和M2M通信装置可以同时注册到IoT平台。可以通过LwM2M协议完成profile的下载和激活，从而可以支持eUICC。
如图7所示的协议栈，IoT平台可以作为LwM2M协议的服务器(sever)，eUICC可以作为LwM2M协议的客户端(client)，M2M通信装置可以作为LwM2M协议的服务器(sever)/客户端(client)。IoT平台和eUICC可以具有应用层协议(App ID)，IoT平台可以通过LwM2M层协议可以实现应用层数据的传输。
步骤710：eUICC向M2M通信装置发起与承载无关的协议(bearer independent protocol，BIP)通道。
eUICC可以向M2M通信装置发起BIP通道，可以通过该BIP通道建立与M2M通信装置之间的链路。例如，eUICC可以主动向M2M通信装置open channel命令，使得M2M通信装置打开BIP通道，以便于M2M通信装置可以与IoT平台建立数据连接。
步骤715：eUICC向M2M通信装置发送LwM2M注册请求。
eUICC可以作为LwM2M client模块向IoT平台发起LwM2M注册请求，该eUICC可以将该LwM2M注册请求消息发送至M2M通信装置。
上述注册请求消息可以携带App Data Container Obj，例如，App Data Container Obj可以是</19/0>、</19/1>。
应理解，</19/0>、</19/1>中的19可以用于表示eUICC向IoT平台注册一个对象的ID为19，0可以用于表示IoT平台向eUICC发送的下行消息，1可以用于表示eUICC向IoT平台发送的上行消息。
步骤715的具体实现方式可以如下所示：
POST/rd？ep＝{eUICC Name}&lt＝{Lifetime}&sms＝{MSISDN}&lwm2m＝{version}&b＝{binding},
payload:</19/0>,</19/1>。
步骤720：M2M通信装置修改注册请求中的URI。
M2M通信装置可以在收到eUICC发送的请求向IoT平台进行注册的消息之后，可以将M2M通信装置请求向IoT平台进行注册的新消息与eUICC发送的请求向IoT平台进行注册的消息打包至一个会话发送给IoT平台。
该M2M通信装置可以修改注册消息中的URI，可以在发送给IoT平台的一个会话中增加第一标识。作为一个示例，该第一标识可以是例如，？sd＝eUICC。该第一标识(例如？sd＝eUICC)可以用于表示当IoT平台受到具有相同的IP+port的两个client，该IoT平台可以根据解析出的第一标识(例如？sd＝eUICC)确定其中一个client可以是eUICC。
也就是说，IoT平台可以根据解析出的第一标识(例如？sd＝eUICC)确定M2M通信装置发送的两个注册请求中有一个注册请求可以是eUICC请求进行注册的。
应注意，该注册消息中的token ID可以与原消息相同。
步骤720的具体实现方式可以如下所示：
POST/rd？ep＝{GW Name}&lt＝{Lifetime}&sms＝{MSISDN}&lwm2m＝{version}& b＝{binding}？sd＝eUICC
payload：</1/0>,</1/1>,</2/0>,</2/1>,</2/2>,</2/3>,</2/4>,</3/0>,</4/0>,</5>,</19/0>,</19/1>/rd？ep＝{eUICC Name}&lt＝{Lifetime}&sms＝{MSISDN}&lwm2m＝{version}&b＝{binding}
？sd＝</19/0>,</19/1>
其中，？sd＝eUICC可以用于表示payload中还包括eUICC的信息，例如，eUICC发送的请求向IoT平台进行注册的消息。
步骤725：M2M通信装置将打包后的LwM2M注册请求转发至IoT平台。
M2M通信装置打包eUICC和M2M通信装置的LwM2M注册消息的具体实现方式如下所示：
POST/rd？ep＝{GW Name}&lt＝{Lifetime}&sms＝{MSISDN}&lwm2m＝{version}&b＝{binding}？sd＝eUICC
payload：</1/0>,</1/1>,</2/0>,</2/1>,</2/2>,</2/3>,</2/4>,</3/0>,</4/0>,</5>,</19/0>,</19/1>/rd？ep＝{eUICC Name}&lt＝{Lifetime}&sms＝{MSISDN}&lwm2m＝{version}&b＝{binding}
？sd＝</19/0>,</19/1>
步骤730：IoT平台解析收到的LwM2M注册请求，获取eUICC和M2M通信装置的注册请求消息。
IoT平台可以在收到M2M通信装置发送的注册消息后，可以解析该注册消息中携带的第一标识(例如？sd＝eUICC)。该IoT平台可以根据？sd＝eUICC确定注册消息中还包括eUICC请求向IoT平台进行注册的注册消息。
步骤735：IoT平台向M2M通信装置返回注册响应结果。
IoT平台可以在解析到该注册消息中携带的？sd＝eUICC后，可以向M2M通信装置返回注册响应结果。该注册响应结果可以包括两个地址(location)，其中，一个location可以用于指示M2M通信装置将该注册响应结果返回模组，另一个location可以用于指示M2M通信装置将该注册响应结果返回至eUICC。
步骤735的具体实现方式如下所示：
created location:/rd/5a3f，
payload:location？sd＝/rd/5b4a
其中，location:/rd/5a3f可以用于指示M2M通信装置将该注册响应结果返回模组，location？sd＝/rd/5b4a可以用于指示M2M通信装置将该注册响应结果返回至eUICC。
步骤740：M2M通信装置解析注册响应结果，根据第一标识(例如？sd＝)将该消息转发至eUICC。
M2M通信装置可以在收到IoT平台发送的注册响应结果后，可以从payload中解析出？sd＝/rd/5b4a。该M2M通信装置可以删除第一标识(例如？sd＝)，可以在转换为正常的注册响应消息后返回至eUICC。
步骤740的具体实现方式如下所示：
created location:/rd/5b4a
步骤743：M2M通信装置向eUICC发送LwM2M注册响应结果。
步骤745：可选地，eUICC向M2M通信装置发起BIP。
可选地，eUICC可以在接收到M2M通信装置转发的注册响应消息后，可以向M2M通信装置发起BIP。例如，eUICC可以主动向M2M通信装置close channel命令，使得M2M通信装置关闭BIP通道，使得M2M通信装置可以与IoT平台断开数据连接。
步骤750：IoT平台接收SM平台发送的下载profile请求消息(download profile)。
步骤755：IoT平台将下载profile请求消息发送至M2M通信装置。
IoT平台可以在接收到SM平台发送的下载profile请求消息之后，可以将该请求消息打包至App Data Container Obj对象中。由于IoT平台发现该下载profile请求消息的目的client是eUICC，该IoT平台可以在目的URL中增加应用指示。
上述提及的下载profile请求消息可以包括应用指示(例如，App ID)以及第一标识(例如，？sd＝eUICC)。
本申请实施例中第一标识可以用于指示所述M2M通信装置将所述目标运营商的profile的下载或激活信息转发至所述eUICC。应用指示可以用于指示eUICC将目标运营商的profile的下载或激活信息发送至eUICC上的App。
IoT平台可以设置Data Format和上述请求消息的类型一致，与平台一致的App_ID可以设置为一个特殊值，例如，App_ID＝255。
步骤755的具体实现方式如下所示：
PUT/19/0？sd＝eUICC
Data Format:create ISD-P Req,App_ID＝255；
Data:ES5.create ISD-P Req
应理解，创建的简介的主安全域(the security domain-profile，ISD-P)可以用于存储所述profile。可以有标识指示当前ISD-P中的profile的状态，创建的该ISD-P的状态可以是激活状态，也可以是去激活状态。
步骤760：M2M通信装置解析请求消息，根据第一标识(例如？sd＝eUICC)将该消息转发至eUICC。
M2M通信装置可以在收到IoT平台发送的下载profile请求消息之后，可以解析请求消息中携带的第一标识(例如？sd＝eUICC)，判断该请求消息是否发送给eUICC。如果请求消息中携带有？sd＝eUICC，可以将该请求消息转发至eUICC。
应注意，LwM2M请求消息中的令牌桶ID(token ID)可以与原请求消息相同。
可选地，如果步骤740中eUICC主动向M2M通信装置close channel命令，该M2M通信装置可以先获取M2M通信装置与eUICC之间的BIP通道。
具体的建立M2M通信装置与eUICC之间的BIP通道可以参照步骤810中的描述，此处不再赘述。
步骤765：M2M通信装置向eUICC发送请求消息。
M2M通信装置向eUICC转发请求消息，同时可以删除请求消息中携带的第一标识(例如？sd＝eUICC)。
步骤765的具体实现方式如下所示：
PUT/19/0
Data Format:create ISD-P Req,App_ID＝255；
Data:ES5.create ISD-P Req
步骤770：eUICC根据应用指示(例如，App ID)，将请求消息转发至eUICC App。
eUICC可以在接收到M2M通信装置发送的请求消息后，可以根据请求消息Data Format中的应用指示，例如，App_ID＝255，可以将该请求消息转发至eUICC App，从而可以完成ISD-P的创建。
应注意，该消息中的token ID可以与原请求消息相同。
步骤775：eUICC将LwM2M执行结果返回M2M通信装置。
eUICC可以将eUICC App的执行结果打包至LwM2M App Data Container Obj中，并可以根据Data Format保留BIP通道。
应理解，上述eUICC App的执行结果可以是为所述eUICC上的应用对所述SM平台发送的请求消息的响应结果。执行结果中可以包括应用指示(例如，App ID)，用于指示IoT平台将所述执行结果返回至所述SM平台。
步骤775的具体实现方式如下所示：
PUT/19/0
Data Format:create ISD-P Rsp,App_ID＝255
步骤780：M2M通信装置将LwM2M执行结果转发至IoT平台。
M2M通信装置可以在收到eUICC发送的LwM2M执行结果之后，可以在目标URL中增加第一标识(例如？sd＝eUICC)，并可以将该执行结果转发至IoT平台。
应注意，该执行结果中的token ID可以与原请求消息相同。
步骤780的具体实现方式如下所示：
PUT/19/1？sd＝eUICC
Data Format:create ISD-P Rsp,App_ID＝255
步骤785：IoT平台向SM平台发送下载profile响应消息(download profile Rsp)。
IoT平台在收到M2M通信装置发送的LwM2M执行结果之后，可以根据LwM2M执行结果中的应用指示(例如，App ID)将LwM2M执行结果转化成原下载profile请求消息的格式后，再将转换后的下载profile响应消息发送至SM平台。
步骤790：IoT平台接收目标MNO发送的激活profile请求消息(enable profile)。
IoT平台可以将激活profile请求消息发送至eUICC，使得eUICC可以通过LwM2M协议完成profile的下载和激活，从而完成profile从当前运营商切换至目标运营商。
具体发送激活profile请求消息的流程请参考步骤710-780中发送下载profile请求消息的流程，此处不再赘述。
本申请实施例中，LwM2M可以不用多次握手就可以直接建立远端服务器与终端上的eUICC之间的会话，因此，本申请实施例可以减少eUICC和远端服务器之间的交互消息，减少eUICC的协议栈复杂性，提升网络的传输效率。
下面以M2M通信装置请求向IoT平台进行LwM2M注册为例进行说明。
本申请实施例中eUICC可以向M2M通信装置请求进行LwM2M注册，此时，由于eUICC 与M2M通信装置关联，M2M通信装置可以向IoT平台发送LwM2M的注册请求，使得该eUICC可以支持LwM2M协议，可以根据SM平台发送的profile下载和激活请求从而可以完成profile的下载和激活，实现从当前运营商的profile切换至目标运营商的profile。下面会结合图8进行详细描述，此处不再赘述。
本申请实施例中eUICC可以向M2M通信装置请求进行LwM2M注册，M2M通信装置可以请求向IoT平台进行LwM2M注册，使得该eUICC可以根据SM平台发送的profile下载和激活请求从而可以完成profile的下载和激活。该M2M通信装置可以称为支持LwM2M GW代理(proxy)模式。
可选地，在一些实施例中，可以通过预先配置，可以使M2M通信装置支持LwM2M GW proxy模式，eUICC支持LwM2M协议，IoT平台支持LwM2M协议。
作为一个示例，可以通过软件代码实现对M2M通信装置的预先配置，该M2M通信装置可以支持通过LwM2M协议进行数据传输。例如，可以预先配置M2M通信装置支持LwM2M gateway proxy的功能。又如，可以预先配置M2M通信装置的LwM2M server模块和client模块相互映射为App，M2M通信装置的server可以将LwM2M消息转发至client，实现支持通过LwM2M协议进行数据传输。又如，可以预先配置M2M通信装置支持App Data Container Obj Data Format，将该LwM2M消息转发至eUICC，实现支持通过LwM2M协议进行数据传输。
应理解，该M2M通信装置既可以支持LwM2M client模块，也可以支持LwM2M server模块。其中，设备管理(device management，DM)功能可以由LwM2M client模块完成。
应理解，server模块和client模块相互映射为App，其APP_ID可以与平台一致，例如，该APP_ID＝255。
该M2M通信装置可以的支持App Data Container Obj Data Format如下所示：可以是通过短信服务(short messaging service，SMS)发送创建ISD-P的请求(SMS，create ISD-P Req)，还可以是通过SMS发送创建ISD-P的响应(SMS，create ISD-P Rsp)，还可以是创建ISD-P的关键组请求(establish ISD-P key set Req)，还可以是创建ISD-P的关键组响应(establish ISD-P key set Rsp)，还可以是发送数据的请求(send data Req)，还可以是发送数据的响应(send data Rsp)。
作为另一个示例，可以通过软件代码实现对IoT平台的预先配置，该IoT平台可以可以支持通过LwM2M协议进行数据传输。例如，可以预先配置eUICC App可以作为LwM2M server上的某个App，该IoT平台可以将LwM2M消息转发至eUICC App，实现支持通过LwM2M协议进行数据传输。又如，可以预先配置IoT平台可以支持App Data Container Obj Data Format，将该LwM2M消息转发至eUICC，实现支持通过LwM2M协议进行数据传输。
应理解，eUICC App的App_ID可以是一个特殊值，例如，该App_ID＝255。
还应理解，IoT平台可以支持的App Data Container Obj Data Format如下所示：可以是通过短信服务(short messaging service，SMS)发送创建ISD-P的请求(SMS，create ISD-P Req)，还可以是通过SMS发送创建ISD-P的响应(SMS，create ISD-P Rsp)，还可以是创建ISD-P的关键组请求(establish ISD-P key set Req)，还可以是创建ISD-P的关键组响应(establish ISD-P key set Rsp)，还可以是发送数据的请求(send data Req)，还可以是发送数 据的响应(send data Rsp)。
作为另一个示例，可以通过软件代码实现对eUICC的预先配置。eUICC支持在LwM2M协议下进行数据传输。例如，可以预先配置的eUICC可以作为LwM2M client，可以完成数据传输功能。又如，可以预先配置eUICC会话描述协议(session description protocol，SDP)文件，设置LwM2M业务，让eUICC与终端设备之间可以支持通过LwM2M协议进行数据传输。又如，可以配置嵌入式用户身份模块(embeddedsubscriber identity module，eSIM)App作为LwM2M client上的某个App，eUICC可以在收到LwM2M消息后，可以将该LwM2M消息转发至LwM2M client上的某个App，实现支持通过LwM2M协议进行数据传输。又如，可以建立eUICC到M2M通信装置的通道(服务描述service declaration)，实现支持通过LwM2M协议进行数据传输。又如，可以预先配置eUICC可以支持App Data Container Obj Data Format，将该LwM2M消息转发至eUICC上的应用，实现支持通过LwM2M协议进行数据传输。
应理解，eSIM App作为LwM2M client上的某个APP，其APP_ID可以与M2M通信装置一致，例如，该APP_ID＝255。
还应理解，又如，可以对eUICC进行预先配置，使得该eUICC可以支持的App Data Container Obj Data Format如下所示：可以是通过短信服务(short messaging service，SMS)发送创建ISD-P的请求(SMS，create ISD-P Req)，还可以是通过SMS发送创建ISD-P的响应(SMS，create ISD-P Rsp)，还可以是创建ISD-P的关键组请求(establish ISD-P key set Req)，还可以是创建ISD-P的关键组响应(establish ISD-P key set Rsp)，还可以是发送数据的请求(send data Req)，还可以是发送数据的响应(send data Rsp)。
本申请实施例中，在M2M通信装置可以支持LwM2M proxy模式的情况下，M2M通信装置可以同时支持LwM2M客户端(client)和服务器(sever)。M2M通信装置上的client和sever可以通过应用指示(例如，App ID)相互映射，其映射关系与应用指示(例如，App ID)一致。从而可以在M2M通信装置接收到eUICC发送的消息之后，M2M通信装置可以上述映射关系，可以将该消息转发至IoT平台。
在一些实施例中，如果M2M通信装置可以称为支持GW proxy模式，该M2M通信装置的client模块可以接收eUICC向M2M通信装置发送的请求进行LwM2M注册的注册信息，M2M通信装置的server模块可以向IoT平台发送M2M通信装置请求向该IoT平台进行LwM2M注册的注册信息。
下面结合具体的例子，更加详细地描述本申请实施例中，M2M通信装置可以称为支持GW proxy模式时，可以通过LwM2M协议完成profile的下载和激活的具体实现方式。应注意，下文的例子仅仅是为了帮助本领域技术人员理解本申请实施例，而非要将申请实施例限制于所示例的具体数值或具体场景。本领域技术人员根据文所给出的例子，显然可以进行各种等价的修改或变化，这样的修改和变化也落入本申请实施例的范围内。
图8是本申请实施例提供的另一种可能的通信方法的示意性流程图。图8的方法可以包括步骤810-890，下面分别对步骤810-890进行详细描述。
应理解，本申请实施例中，eUICC支持LwM2M协议、M2M通信装置支持LwM2M GW代理(proxy)模式，eUICC只注册到M2M通信装置。可以通过LwM2M协议完成profile 的下载和激活，从而可以支持eUICC。
如图8所示的协议栈，IoT平台可以作为LwM2M协议的服务器(sever)，eUICC可以作为LwM2M协议的客户端(client)，M2M通信装置可以作为LwM2M协议的服务器(sever)/客户端(clien)t。IoT平台和eUICC可以具有应用层协议(App ID)，IoT平台可以通过LwM2M层协议可以实现应用层数据的传输。
步骤810：eUICC向M2M通信装置发起BIP通道。
eUICC可以向M2M通信装置发起BIP通道，可以通过该BIP通道建立与M2M通信装置之间的链路。例如，eUICC可以主动向M2M通信装置open channel命令，使得M2M通信装置打开BIP通道，以便于M2M通信装置可以与IoT平台建立数据连接。
步骤815：eUICC向M2M通信装置发送LwM2M注册请求。
eUICC可以作为LwM2M client模块向M2M通信装置发起注册请求，M2M通信装置的server模块接收eUICC向M2M通信装置发起注册请求。也就是说，eUICC主动发起向M2M通信装置进行注册。
该注册请求以携带App Data Container Obj，例如，App Data Container Obj可以是</19/0>、</19/1>。
步骤820：M2M通信装置向IoT平台发起LwM2M注册请求。
该LwM2M注册请求可以携带App Data Container Obj，例如，App Data Container Obj可以是</1>、</2>、</3>、</4>、</5>、</19>。
步骤825：IoT平台接收SM平台发送的下载profile请求消息(download profile)。
本申请中目标MNO发送的下载profile请求消息可以包括一个应用指示(例如，App_ID)可以指示将该下载profile请求消息发送至eUICC上的App。
步骤830：IoT平台将下载profile请求消息发送至M2M通信装置。
IoT平台可以在接收到SM平台发送的下载profile请求消息之后，可以将该请求消息写入App Data Container Obj对象中。
IoT平台可以设置Data Format和上述请求消息的类型一致，与M2M通信装置一致的应用指示App_ID可以设置为一个特殊值，例如，App_ID＝255。
步骤830的具体实现方式可以如下所示：
PUT/19/0
Data Format:create ISD-P Req,App_ID＝255；
Data:ES5.create ISD-P Req
步骤835：M2M通信装置根据应用指示(例如，App_ID)，将该请求消息转发至LwM2M server模块，LwM2M server模块将该请求消息转发至eUICC。
M2M通信装置的client模块收到IoT平台发送的LwM2M下载profile请求消息之后，可以根据Data Format中的应用指示(例如，App_ID)，将该请求消息转发至M2M通信装置的server模块。M2M通信装置的server模块可以直接将该LwM2M请求消息转发至eUICC。
应注意，上述转发过程中的LwM2M请求消息中的token ID可以与原请求消息相同。
可选地，如果eUICC主动向M2M通信装置close channel命令，该M2M通信装置可以先获取M2M通信装置与eUICC之间的BIP通道。
具体的建立M2M通信装置与eUICC之间的BIP通道可以参照步骤810中的描述，此处不再赘述。
步骤840：M2M通信装置向eUICC发送LwM2M请求消息。
M2M通信装置的server模块可以直接将该LwM2M请求消息转发至eUICC。
步骤840的具体实现方式可以如下所示：
PUT/19/0
Data Format:create ISD-P Req,App_ID＝255；
Data:ES5.create ISD-P Req
步骤845：eUICC根据应用指示(例如，App_ID)，将请求消息转发至eUICC App。
eUICC可以对收到的LwM2M请求消息进行解析，可以根据Data Format中的应用指示(例如，App_ID＝255)，可以将该请求消息转发至eUICC App，从而可以完成ISD-P的创建。
应注意，该消息中的token ID可以与原请求消息相同。
步骤847：eUICC将LwM2M执行结果返回M2M通信装置。
eUICC可以将eUICC App的LwM2M执行结果打包至LwM2M App Data Container Obj中，并可以根据Data Format保留BIP通道。
应理解，上述eUICC App的执行结果可以是为所述eUICC上的应用对所述SM平台发送的请求消息的响应结果。执行结果中可以包括应用指示(例如，App ID)，用于指示IoT平台将所述执行结果返回至所述SM平台。
步骤847的具体实现方式如下所示：
PUT/rd/5b4a/19/1
Data Format:create ISD-P Rsp,App_ID＝255.
步骤850：M2M通信装置根据应用指示App_ID，将执行结果发送给LwM2M client，LwM2M client将该结果透传至IoT平台。
M2M通信装置可以根据Data Format中的应用指示App_ID＝255，可以将该执行结果发送至M2M通信装置的sever模块。M2M通信装置的sever模块可以将该执行结果发送至client模块，client模块可以再将该执行结果透传至IoT平台。
步骤850的具体实现方式如下所示：
PUT/rd/5b4a/19/1
Data Format:create ISD-P Rsp,App_ID＝255.
步骤853：M2M通信装置向IoT平台发送LwM2M执行结果。
步骤855：IoT平台向SM平台发送下载profile响应消息(download profile Rsp)。
IoT平台在收到M2M通信装置发送的LwM2M执行结果之后，可以根据LwM2M执行结果中的应用指示(例如，App ID)将LwM2M执行结果转化成原下载profile请求消息的格式后，可以将转换后的下载profile响应消息发送至SM平台。
步骤860：IoT平台接收目标MNO发送的激活profile请求消息(enable profile)。
IoT平台可以将激活profile请求消息发送至eUICC，使得eUICC可以通过LwM2M协议完成profile的下载和激活，从而完成profile从当前运营商切换至目标运营商。
具体发送激活profile请求消息的流程请参考步骤810-860中发送下载profile请求消息 的流程，此处不再赘述。
本申请实施例中，可以减少eUICC和远端服务器之间的交互消息，可以提升网络的传输效率。可以减少eUICC的协议栈复杂性，降低eUICC的成本。
上文结合图1至图8，详细描述了本发明实施例提供的无线网络通信方法，下面将结合图9至图14，详细描述本申请的通信设备实施例。应理解，方法实施例的描述与通信设备实施例的描述相互对应，因此，未详细描述的部分可以参见前面方法实施例。
图9示出了本申请实施例的机器到机器M2M通信装置900的示意性框图，该M2M通信装置900中可以包括嵌入的嵌入式通用集成电路卡eUICC，该M2M通信装置900各模块分别用于执行上述方法中M2M通信装置所执行的各动作或处理过程，这里，为了避免赘述，详细说明可以参照上文中的描述。
图9是本申请实施例提供的机器到机器M2M通信装置900的示意性框图。该M2M通信装置900可以包括：
第一接收模块901，用于接收物联网IoT平台发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给嵌入式通用集成电路卡eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信。
第一发送模块902，用于将所述LwM2M消息发送至与之关联的所述eUICC。
第二发送模块903，用于根据所述应用指示将所述LwM2M消息中的目标数据发送至所述eUICC上的应用。
本申请实施例可以在NB-IoT网络下建立应用服务器(例如，SM平台)与终端上的eUICC之间的会话，从而完成数据传输。
可选地，在一些实施例中，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
可选地，在一些实施例中，第一发送模块902具体用于：根据所述LwM2M消息中的应用指示，将所述SM下发的profile或所述profile的激活信息发送至所述eUICC。
可选地，在一些实施例中，所述M2M通信装置900还包括：
第三发送模块904，用于向所述M2M通信装置发送响应消息。
所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示。
第四发送模块905，用于根据所述应用指示将收到的所述响应消息发送至所述SM平台。
可选地，在一些实施例中，所述第一LwM2M消息还包括第一标识，所述第一标识用于指示所述IoT平台与所述eUICC之间的通信。
可选地，在一些实施例中，第一发送模块902具体用于：根据所述第一LwM2M消息中的第一第一标识，将所述profile或所述profile的激活信息发送至所述eUICC。
可选地，在一些实施例中，所述M2M通信装置900还包括：
第五发送模块906，用于所述eUICC上的应用向所述M2M通信装置发送所述响应消息。
第六发送模块907，用于将所述响应消息发送至所述SM平台，其中，所述响应消息包括所述应用指示和所述第一标识。
可选地，在一些实施例中，所述M2M通信装置900还包括：
第七发送模块908，用于所述eUICC向所述M2M通信装置发送LwM2M注册请求，所述第一LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册；
第八发送模块909，用于所述M2M通信装置将收到的所述LwM2M注册请求发送至所述IoT平台，所述第一LwM2M注册请求包括所述第一标识。
本申请实施例中，M2M通信装置可以支持LwM2M协议完成profile的下载和激活，从而实现eUICC从当前运营商切换至目标运营商。
图10示出了本申请实施例的嵌入式通用集成电路卡eUICC1000的示意性框图，该eUICC 1000中各模块分别用于执行上述方法中eUICC所执行的各动作或处理过程，这里，为了避免赘述，详细说明可以参照上文中的描述。
图10是本申请实施例提供的嵌入式通用集成电路卡eUICC 1000的示意性框图。该eUICC 1000可以包括：
第一接收模块1001，用于接收机器到机器M2M通信装置发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信，所述eUICC与所述M2M通信装置关联。
第一发送模块1002，用于根据所述应用指示将所述LwM2M消息中的目标数据发送至所述eUICC上的应用。
本申请实施例可以在NB-IoT网络下建立应用服务器(例如，SM平台)与终端上的eUICC之间的会话，从而完成数据传输。
可选地，在一些实施例中，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
可选地，在一些实施例中，所述eUICC 1000还包括：
第二发送模块1003，用于向所述机器到机器M2M通信装置发送响应消息。
所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示。
可选地，在一些实施例中，所述eUICC1000还包括：
第三发送模块1004，用于向所述M2M通信装置发送第一LwM2M注册请求。
所述第一LwM2M注册请求用于所述eUICC请求向物联网IoT平台进行LwM2M注册，或用于所述eUICC请求向所述IoT平台进行LwM2M注册。
本申请实施例中，eUICC可以支持LwM2M协议完成profile的下载和激活，从而实现eUICC从当前运营商切换至目标运营商。
图11示出了本申请实施例的物联网IoT平台1100的示意性框图，该IoT平台1100中各模块分别用于执行上述方法中IoT平台所执行的各动作或处理过程，这里，为了避免赘述，详细说明可以参照上文中的描述。
图11是本申请实施例提供的IoT平台1100的示意性框图。该IoT平台1100可以包括：
第一接收模块1101，用于接收签约管理SM平台发送的请求消息，所述请求消息包括应用指示和签约管理SM平台下发给eUICC的目标数据，所述应用指示用于指示本次通信 为所述SM平台与所述eUICC上的应用之间的通信。
处理模块1102，用于将所述请求消息转换成轻量机器到机器LwM2M消息.
第一发送模块1103，用于向机器到机器M2M通信装置发送所述LwM2M消息，所述M2M通信装置与所述eUICC关联。
本申请实施例可以在NB-IoT网络下建立应用服务器(例如，SM平台)与终端上的eUICC之间的会话，从而完成数据传输。
可选地，在一些实施例中，目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
可选地，在一些实施例中，所述平台1100还包括：
第二接收模块1104，用于接收所述M2M通信装置发送的响应消息。
所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示。
第二发送模块1105，用于根据所述应用指示将所述响应消息发送至所述SM平台。
可选地，在一些实施例中，所述LwM2M消息还包括第一标识，所述第一标识用于指示所述IoT平台与所述eUICC之间的通信。
可选地，在一些实施例中，所述平台1100还包括：
第三接收模块1106，用于接收所述M2M通信装置发送的第一LwM2M注册请求。
所述第一LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册，所述第一LwM2M注册请求包括所述第一标识。
可选地，在一些实施例中，所述平台1100还包括：
第四接收模块1107，用于接收所述M2M通信装置发送的响应消息，所述响应消息包括所述应用指示和所述第一标识。
第三发送模块1108，用于根据所述应用指示将所述响应消息发送至所述SM平台。
图12是本申请实施例提供的一种机器到机器M2M通信装置1200的示意性框图。该M2M通信装置1200包括eUIC。该M2M通信装置1200可以包括：处理器1201、接收器1202、发送器1203、以及存储器1204。
应理解，该M2M通信装置1200例如可以是图5所示的modem420，该M2M通信装置1200可以包括片内存储器1204，还可以与片外存储器交互。
接收器1202可以对应于图5中的数据接收器510，处理器1201可以对应于图5中的控制器520，发送器1203可以对应于图5中的数据发送器530。
其中，该处理器1201可以与接收器1202和发送器1203通信连接。该存储器1204可以是片内存储，可以用于存储该网络设备的程序代码和数据。因此，该存储器1004可以是处理器1201内部的存储单元，也可以是与处理器1201独立的外部存储单元，还可以是包括处理器1201内部的存储单元和与处理器1201独立的外部存储单元的部件。
可选的，网络设备还可以包括总线1205。其中，接收器1202、发送器1203、以及存储器1204可以通过总线1205与处理器1201连接；总线1205可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线1205可以分为地址总线、数据总线、控制 总线等。为便于表示，图12中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器1201例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
可选的，当M2M通信装置1200是芯片时，那么接收器1202和发送器1203的功能/实现过程还可以通过管脚或电路等来实现。
图13是本申请实施例提供的一种嵌入式通用集成电路卡eUICC 1300的示意性框图。该eUICC 1300可以包括：处理器1301、接收器1302、发送器1303、以及存储器1304。
其中，该处理器1301可以与接收器1302和发送器1303通信连接。该存储器1304可以用于存储该网络设备的程序代码和数据。因此，该存储器1304可以是处理器1301内部的存储单元，也可以是与处理器1301独立的外部存储单元，还可以是包括处理器1301内部的存储单元和与处理器1301独立的外部存储单元的部件。
可选的，网络设备还可以包括总线1305。其中，接收器1302、发送器1303、以及存储器1304可以通过总线1305与处理器1301连接；总线1305可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线1305可以分为地址总线、数据总线、控制总线等。为便于表示，图13中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器1301例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
可选的，当M2M通信装置1300是芯片时，那么接收器1302和发送器1303的功能/实现过程还可以通过管脚或电路等来实现。
图14是本申请实施例提供的一种物联网IoT平台1400的示意性框图。该IoT平台1400可以包括：处理器1401、接收器1402、发送器1403、以及存储器1404。
其中，该处理器1401可以与接收器1402和发送器1403通信连接。该存储器1404可以用于存储该网络设备的程序代码和数据。因此，该存储器1404可以是处理器1401内部的存储单元，也可以是与处理器1401独立的外部存储单元，还可以是包括处理器1401内部的存储单元和与处理器1401独立的外部存储单元的部件。
可选的，网络设备还可以包括总线1405。其中，接收器1402、发送器1403、以及存储器1404可以通过总线1405与处理器1401连接；总线1405可以是外设部件互连标准 (Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线1405可以分为地址总线、数据总线、控制总线等。为便于表示，图14中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器1401例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
接收器1402和发送器1403可以是包括上述天线和发射机链和接收机链的电路，二者可以是独立的电路，也可以是同一个电路。
本申请实施例还提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行上述任一方面的任意可能的实现方式中的方法的指令。
本申请实施例还提供了一种芯片系统，应用于通信设备中，该芯片系统包括：至少一个处理器、至少一个存储器和接口电路，所述接口电路负责所述芯片系统与外界的信息交互，所述至少一个存储器、所述接口电路和所述至少一个处理器通过线路互联，所述至少一个存储器中存储有指令；所述指令被所述至少一个处理器执行，以进行上述各个方面的所述的方法中所述通信设备的操作。
本申请实施例还提供了一种计算机程序产品，应用于通信设备中，所述计算机程序产品包括一系列指令，当所述指令被运行时，以进行上述各个方面的所述的方法中所述通信设备的操作。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其他任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计 算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如数字视频光盘(digital video disc，DVD))、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例中方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种窄带物联网中eUICC数据传输方法，其特征在于，所述方法包括：
    机器到机器M2M通信装置接收物联网IoT平台发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给嵌入式通用集成电路卡eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；
    所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC；
    所述eUICC根据所述应用指示将所述LwM2M消息中的目标数据发送至所述eUICC上的应用。
  2. 如权利要求1所述的方法，其特征在于，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
  3. 如权利要求2所述的方法，其特征在于，所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC，包括：
    所述M2M通信装置根据所述应用指示，将所述SM平台下发的profile或所述profile的激活信息发送至所述eUICC。
  4. 如权利要求2或3所述的方法，其特征在于，所述方法还包括：
    所述eUICC上的应用向所述M2M通信装置发送响应消息，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示；
    所述M2M通信装置根据所述应用指示将收到的所述响应消息发送至所述SM平台。
  5. 如权利要求1所述的方法，其特征在于，所述LwM2M消息还包括第一标识，所述第一标识用于指示本次通信为所述IoT平台与所述eUICC之间的通信。
  6. 如权利要求5所述的方法，其特征在于，所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC，包括：
    所述M2M通信装置根据所述LwM2M消息中的第一标识，将所述profile或所述profile的激活信息发送至所述eUICC。
  7. 如权利要求5或6所述的方法，其特征在于，所述方法还包括：
    所述eUICC上的应用向所述M2M通信装置发送所述响应消息；
    所述M2M通信装置将所述响应消息发送至所述SM平台，其中，所述响应消息包括所述应用指示和所述第一标识。
  8. 如权利要求5至7中任一项所述的方法，其特征在于，在所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC之前，所述方法还包括：
    所述eUICC向所述M2M通信装置发送LwM2M注册请求，所述LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册；
    所述M2M通信装置将收到的所述LwM2M注册请求发送至所述IoT平台，所述LwM2M注册请求包括所述第一标识。
  9. 一种窄带物联网中eUICC数据传输方法，其特征在于，所述方法包括：
    机器到机器M2M通信装置接收物联网IoT平台发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给嵌入式通用集成电路卡eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；
    所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC。
  10. 如权利要求9所述的方法，其特征在于，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
  11. 如权利要求10所述的方法，其特征在于，所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC，包括：
    所述M2M通信装置根据所述LwM2M消息中的应用指示，将所述SM平台下发的profile或所述profile的激活信息发送至所述eUICC。
  12. 如权利要求11所述的方法，其特征在于，所述方法还包括：
    所述M2M通信装置接收所述eUICC发送的所述响应消息，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示；
    所述M2M通信装置根据所述应用指示将收到的所述响应消息发送至所述SM平台。
  13. 如权利要求9所述的方法，其特征在于，所述LwM2M消息还包括第一标识，所述第一标识用于指示本次通信为所述IoT平台与所述eUICC之间的通信。
  14. 如权利要求13所述的方法，其特征在于，所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC，包括：
    所述M2M通信装置根据所述LwM2M消息中的第一标识，将所述profile或所述profile的激活信息发送至所述eUICC。
  15. 如权利要求13或14所述的方法，其特征在于，所述方法还包括：
    所述M2M通信装置接收所述eUICC发送的所述响应消息；
    所述M2M通信装置将所述响应消息发送至所述SM平台，其中，所述响应消息包括所述应用指示和所述第一标识。
  16. 如权利要求13至15中任一项所述的方法，其特征在于，在所述M2M通信装置将所述LwM2M消息发送至与之关联的所述eUICC之前，所述方法还包括：
    所述M2M通信装置接收所述eUICC发送的LwM2M注册请求，所述LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册；
    所述M2M通信装置将所述LwM2M注册请求发送至所述IoT平台，所述LwM2M注册请求包括所述第一标识。
  17. 一种窄带物联网中eUICC数据传输方法，其特征在于，所述方法包括：
    嵌入式通用集成电路卡eUICC接收机器到机器M2M通信装置发送的轻量机器到机器LwM2M消息，所述LwM2M消息包括应用指示和签约管理SM平台下发给eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信，所述eUICC与所述M2M通信装置关联；
    所述eUICC根据所述应用指示将所述LwM2M消息中的目标数据发送至所述eUICC上的 应用。
  18. 如权利要求17所述的方法，其特征在于，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
  19. 如权利要求17所述的方法，其特征在于，所述方法还包括：
    所述eUICC向所述M2M通信装置发送响应消息，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示。
  20. 如权利要求18或19所述的方法，其特征在于，在所述嵌入式通用集成电路卡eUICC接收机器到机器M2M通信装置发送的轻量机器到机器LwM2M消息之前，所述方法还包括：
    所述eUICC向所述M2M通信装置发送LwM2M注册请求，所述LwM2M注册请求用于所述eUICC请求向物联网IoT平台进行LwM2M注册，或用于所述eUICC请求向所述IoT平台进行LwM2M注册。
  21. 一种窄带物联网中eUICC数据传输方法，其特征在于，所述方法包括：
    物联网IoT平台接收签约管理SM平台发送的请求消息，所述请求消息包括应用指示和签约管理SM平台下发给eUICC的目标数据，所述应用指示用于指示本次通信为所述SM平台与所述eUICC上的应用之间的通信；
    所述IoT平台将所述请求消息转换成轻量机器到机器LwM2M消息；
    所述IoT平台向机器到机器M2M通信装置发送所述LwM2M消息，所述M2M通信装置与所述eUICC关联。
  22. 如权利要求21所述的方法，其特征在于，所述目标数据包括所述签约管理SM平台下发给eUICC的目标运营商的简介profile或所述profile的激活信息。
  23. 如权利要求21所述的方法，其特征在于，所述方法还包括：
    所述IoT平台接收所述M2M通信装置发送的响应消息，所述响应消息为所述eUICC上的应用对所述SM平台发送的所述profile或profile的激活信息的响应结果，所述响应消息包括所述应用指示；
    所述IoT平台根据所述应用指示将所述响应消息发送至所述SM平台。
  24. 如权利要求21所述的方法，其特征在于，所述LwM2M消息还包括第一标识，所述第一标识用于指示所述IoT平台与所述eUICC之间的通信。
  25. 如权利要求24所述的方法，其特征在于，在所述IoT平台向机器到机器M2M通信装置发送所述LwM2M消息之前，所述方法还包括：
    所述IoT平台接收所述M2M通信装置发送的LwM2M注册请求，所述LwM2M注册请求用于所述eUICC请求向所述IoT平台进行LwM2M注册，所述LwM2M注册请求包括所述第一标识。
  26. 如权利要求24或25所述的方法，其特征在于，所述方法还包括：
    所述IoT平台接收所述M2M通信装置发送的响应消息，所述响应消息包括所述应用指示和所述第一标识；
    所述根据所述应用指示将所述响应消息发送至所述SM平台。
  27. 一种机器到机器M2M通信装置，其特征在于，所述M2M通信装置包括：接收器、发送器、存储器和处理器，
    所述接收器用于接收所述M2M通信装置之外的装置发送的消息或数据，并转发给所述处理器处理；
    所述发送器用于根据所述处理器的指令向所述M2M通信装置之外的装置发送消息或数据；
    所述存储器用于存储程序；
    所述处理器用于执行所述存储器中存储的程序，当所述程序被执行时，所述M2M通信装置执行如权利要求9至16中任一项所述的方法。
  28. 一种嵌入式通用集成电路卡eUICC，其特征在于，所述eUICC包括：接收器、发送器、存储器和处理器，
    所述接收器用于接收所述eUICC之外的装置发送的消息或数据，并转发给所述处理器；
    所述发送器用于根据所述处理器的指令向所述eUICC上的应用发送消息或数据；
    所述存储器用于存储程序；
    所述处理器用于执行所述存储器中存储的程序，当所述程序被执行时，所述eUICC执行如权利要求17至20中任一项所述的方法。
  29. 一种物联网IoT平台，其特征在于，所述平台包括：接收器、发送器、存储器和处理器，
    所述接收器用于接收所述IoT平台之外的装置发送的消息或数据，并转发给所述处理器；
    所述发送器用于根据所述处理器的指令向所述IoT平台之外的装置发送消息或数据；
    所述存储器用于存储程序；
    所述处理器用于执行所述存储器中存储的程序，当所述程序被执行时，所述IoT平台执行如权利要求21至26中任一项所述的方法。
  30. 一种计算机可读存储介质，其特征在于，包括计算机指令，当所述计算机指令在计算机上运行时，使得所述计算机执行如权利要求1至26中任一项所述的方法。
PCT/CN2019/087768 2018-06-08 2019-05-21 一种窄带物联网中eUICC数据传输方法和装置 WO2019233275A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810589619.9 2018-06-08
CN201810589619.9A CN110582076B (zh) 2018-06-08 2018-06-08 一种窄带物联网中eUICC数据传输方法和装置

Publications (1)

Publication Number Publication Date
WO2019233275A1 true WO2019233275A1 (zh) 2019-12-12

Family

ID=68769242

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/087768 WO2019233275A1 (zh) 2018-06-08 2019-05-21 一种窄带物联网中eUICC数据传输方法和装置

Country Status (2)

Country Link
CN (1) CN110582076B (zh)
WO (1) WO2019233275A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10827329B1 (en) 2020-02-26 2020-11-03 At&T Mobility Ii Llc Facilitation of dynamic edge computations for 6G or other next generation network
CN113543293A (zh) * 2021-06-21 2021-10-22 天翼物联科技有限公司 支持低功耗运行的窄带物联网终端及其控制方法
EP3955607A1 (en) * 2020-08-13 2022-02-16 Deutsche Telekom AG Method for transmitting and/or for using a profile information or at least parts thereof, system, client communication device, server entity, program and computer program product
CN114125892A (zh) * 2021-10-13 2022-03-01 东信和平科技股份有限公司 eSIM远程配置管理方法、终端设备、融合RSP平台及系统
US11418933B2 (en) 2020-03-19 2022-08-16 At&T Mobility Ii Llc Facilitation of container management for internet of things devices for 5G or other next generation network

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111372249B (zh) * 2020-03-10 2023-02-17 中国信息通信研究院 物联网eSIM终端码号下载流程一致性测试系统及方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102202390A (zh) * 2010-03-25 2011-09-28 中兴通讯股份有限公司 一种对无线传感器节点实现管理的方法及系统
CN102215560A (zh) * 2010-04-08 2011-10-12 中兴通讯股份有限公司 一种对m2m终端实现管理的方法及系统
CN102238573A (zh) * 2010-04-30 2011-11-09 中兴通讯股份有限公司 一种m2m业务的架构及实现m2m业务的方法
CN106411843A (zh) * 2015-08-03 2017-02-15 阿姆有限公司 服务器发起的远程装置注册
CN107888539A (zh) * 2016-09-29 2018-04-06 中兴通讯股份有限公司 物联网终端接入装置及方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103458004B (zh) * 2013-08-15 2017-03-01 中国联合网络通信集团有限公司 物联网设备签约信息变更方法和设备
US10212261B2 (en) * 2016-04-08 2019-02-19 Analog Devices Global Network connectivity for constrained wireless sensor nodes
CN108112011A (zh) * 2016-11-24 2018-06-01 中国电信股份有限公司 远程管理嵌入式通用集成电路卡的方法、装置和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102202390A (zh) * 2010-03-25 2011-09-28 中兴通讯股份有限公司 一种对无线传感器节点实现管理的方法及系统
CN102215560A (zh) * 2010-04-08 2011-10-12 中兴通讯股份有限公司 一种对m2m终端实现管理的方法及系统
CN102238573A (zh) * 2010-04-30 2011-11-09 中兴通讯股份有限公司 一种m2m业务的架构及实现m2m业务的方法
CN106411843A (zh) * 2015-08-03 2017-02-15 阿姆有限公司 服务器发起的远程装置注册
CN107888539A (zh) * 2016-09-29 2018-04-06 中兴通讯股份有限公司 物联网终端接入装置及方法

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10827329B1 (en) 2020-02-26 2020-11-03 At&T Mobility Ii Llc Facilitation of dynamic edge computations for 6G or other next generation network
US11310642B2 (en) 2020-02-26 2022-04-19 At&T Intellectual Property I, L.P. Facilitation of dynamic edge computations for 6G or other next generation network
US11418933B2 (en) 2020-03-19 2022-08-16 At&T Mobility Ii Llc Facilitation of container management for internet of things devices for 5G or other next generation network
EP3955607A1 (en) * 2020-08-13 2022-02-16 Deutsche Telekom AG Method for transmitting and/or for using a profile information or at least parts thereof, system, client communication device, server entity, program and computer program product
CN113543293A (zh) * 2021-06-21 2021-10-22 天翼物联科技有限公司 支持低功耗运行的窄带物联网终端及其控制方法
CN113543293B (zh) * 2021-06-21 2023-06-27 天翼物联科技有限公司 支持低功耗运行的窄带物联网终端及其控制方法
CN114125892A (zh) * 2021-10-13 2022-03-01 东信和平科技股份有限公司 eSIM远程配置管理方法、终端设备、融合RSP平台及系统

Also Published As

Publication number Publication date
CN110582076B (zh) 2020-12-01
CN110582076A (zh) 2019-12-17

Similar Documents

Publication Publication Date Title
WO2019233275A1 (zh) 一种窄带物联网中eUICC数据传输方法和装置
US11706321B2 (en) System and method for using T8 API to deliver data over an IP path
EP3662638B1 (en) Transport method selection for delivery of server notifications
US11917503B2 (en) SMS via NAS carried by non-cellular access
US20210076436A1 (en) Device-to-device communication method, terminal device, and network device
WO2020019987A1 (zh) 一种物联网中传输eUICC数据的方法、装置
JP7035082B2 (ja) ユーザプレーンリンク確立方法、基地局、およびモビリティ管理デバイス
CN110557846B (zh) 一种数据传输方法、终端设备及网络设备
CN115065988B (zh) 中继传输的方法、中继终端和远端终端
US20230254922A1 (en) Multipath transmission method and communication apparatus
US11792639B2 (en) Remote SIM provisioning
WO2022057662A1 (zh) 一种服务器选择方法和装置
US20230224699A1 (en) Remote SIM Provisioning
WO2018205154A1 (zh) 一种数据处理方法及终端设备、网络设备
CN114503625B (zh) 一种通信方法、装置以及系统
EP3644632A1 (en) Communication method and device
WO2023160394A1 (zh) 通信的方法和装置
CN114342462B (zh) 无线通信方法和设备
WO2023142717A1 (zh) 一种确定用户设备路由选择策略的方法和装置
US11881961B2 (en) Communication method and related apparatus
US20230328628A1 (en) System and method for using t8 api to deliver data over an ip path
WO2022151357A1 (zh) 通信方法、装置、设备及存储介质
WO2023015474A1 (zh) 用于无线通信装置的方法、装置、存储介质和芯片系统
CN115706973A (zh) 一种安全通信的方法及通信装置
CN117528460A (zh) 消息可靠传输方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19815544

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19815544

Country of ref document: EP

Kind code of ref document: A1