eSIM configuration methods, electronic devices, storage media and software products

By transmitting eSIM configuration file fragments through a non-IP data channel, the applicability of eSIM remote configuration solutions in scenarios without an operating system, low power consumption, offline, or weak network conditions is resolved, enabling eSIM configuration in these environments and improving the reliability and security of configuration.

CN123123876APending Publication Date: 2026-11-17ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611350613.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-01
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing eSIM remote configuration solutions rely on IP network coverage and the terminal's ability to provide an LPA module operating environment. They are difficult to implement eSIM remote configuration in scenarios without an operating system, low power consumption, offline, or weak network conditions, and their applicability needs to be improved.

Method used

eSIM profile fragments are transmitted via non-IP data channels, including USSD, CAT-TP, NBIoT, CBS, and SMS-PP channels. Utilizing existing mobile communication network signaling channels and card application toolkit functionality, terminal devices can complete configuration without IP network connectivity and LPA modules.

Benefits of technology

eSIM remote configuration can be completed even in scenarios with no IP network coverage, weak network, low power consumption, or no operating system, expanding the applicability of eSIM remote configuration solutions and improving the reliability and security of configuration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123876A_ABST
    Figure CN123123876A_ABST
Patent Text Reader

Abstract

This disclosure provides an eSIM configuration method, electronic device, storage medium, and program product, relating to the field of communication technology. The method is applied to terminal devices and aims to improve the applicability of eSIM remote configuration schemes. The method includes: receiving control plane messages sent by a configuration server through a first data channel; wherein the first data channel is a non-network protocol IP data channel, and the control plane messages include embedded Subscriber Identity Module (eSIM) profile fragments; obtaining an eSIM profile based on the eSIM profile fragments in the control plane messages; and writing the eSIM profile into an embedded Universal Integrated Circuit Card (eUICC) to complete the eSIM configuration.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to an eSIM configuration method, electronic device, storage medium, and program product. Background Technology

[0002] The core of Embedded Subscriber Identity Module (eSIM) technology lies in replacing the traditional pluggable Subscriber Identity Module (SIM) card with an embedded Universal Integrated Circuit Card (eUICC) soldered onto the terminal's motherboard. The eUICC does not pre-install operator subscription information and supports remote configuration of the eSIM's profile. The terminal can select and activate the profile as needed to access the corresponding operator's network.

[0003] In eSIM remote configuration schemes in related technologies, the terminal side is usually equipped with a Local Profile Assistant (LPA) module as a local management agent. The LPA module can establish a connection with the operator's Enhanced Subscription Manager Data Preparation+ (SM-DP+) server through the Internet Protocol (IP) network, receive the eSIM configuration file sent by the SM-DP+ server, and then write the eSIM configuration file into the eUICC to complete the eSIM remote configuration.

[0004] However, eSIM remote configuration solutions in related technologies rely on IP network coverage and the terminal's ability to provide an LPA module operating environment. It is difficult to implement eSIM remote configuration in terminals without an operating system, in low-power, offline, or weak network scenarios. The applicability of eSIM remote configuration solutions needs to be improved. Summary of the Invention

[0005] This disclosure provides an eSIM configuration method, electronic device, storage medium, and program product, aimed at improving the applicability of eSIM remote configuration solutions.

[0006] In a first aspect, this disclosure provides an eSIM configuration method, which is applied to a terminal device. The method includes: receiving a control plane message sent by a configuration server through a first data channel; wherein the first data channel is a non-network protocol IP data channel, and the control plane message includes an embedded user identification module eSIM configuration file fragment; obtaining an eSIM configuration file based on the eSIM configuration file fragment in the control plane message; and writing the eSIM configuration file into an embedded universal integrated circuit card eUICC to complete the eSIM configuration.

[0007] Secondly, this disclosure provides an eSIM configuration device applied to a terminal device; the device includes a receiving module and a processing module. The receiving module is configured to receive control plane messages sent by a configuration server through a first data channel; wherein the first data channel is a non-network protocol IP data channel, and the control plane messages include embedded Subscriber Identity Module (eSIM) profile fragments. The processing module is configured to obtain an eSIM profile based on the eSIM profile fragments in the control plane messages; and write the eSIM profile to an embedded Universal Integrated Circuit Card (eUICC) to complete the eSIM configuration.

[0008] Thirdly, this disclosure provides an eSIM configuration method, which is applied to a configuration server. The method includes: sending control plane messages to a terminal device through a first data channel; the first data channel is a non-network protocol IP data channel; the control plane messages include embedded user identification module eSIM configuration file fragments.

[0009] Fourthly, this disclosure provides an eSIM configuration device applied to a configuration server. The device includes a transmitting module. The transmitting module is used to transmit control plane messages to a terminal device via a first data channel; the first data channel is a non-network protocol IP data channel; the control plane messages include fragments of an embedded Subscriber Identity Module (SIM) eSIM configuration file.

[0010] Fifthly, this disclosure provides an electronic device comprising: a processor and a memory for storing processor-executable instructions; wherein, when the processor is configured to execute instructions, the electronic device performs the method described above in the first or third aspect.

[0011] In a sixth aspect, this disclosure provides a computer-readable storage medium, including a non-transitory computer-readable storage medium storing computer instructions that, when executed on an electronic device, cause the electronic device to perform the method described in the first or third aspect above.

[0012] In a seventh aspect, this disclosure provides a computer program product including computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the methods described above in the first or third aspect.

[0013] In this disclosure, the terminal device can receive control plane messages sent by the configuration server through the first data channel of the non-IP data channel. The control plane messages carry eSIM configuration file fragments, so that the transmission of the eSIM configuration file does not depend on the IP network connection, nor does the terminal device need to provide the operating environment of the LPA module. This reduces the processing power and network coverage requirements of the terminal device during the eSIM remote configuration process. eSIM remote configuration can also be completed in scenarios such as no IP network coverage, weak network, low power consumption, or no operating system, thus expanding the scope of application of the eSIM remote configuration scheme and improving its applicability. Attached Figure Description

[0014] The accompanying drawings are provided to further understand the technical solutions of the present invention and constitute a part of the specification. They are used together with the embodiments of this disclosure to explain the technical solutions of the present invention and do not constitute a limitation on the technical solutions of the present invention.

[0015] Figure 1 This is a schematic diagram of the composition of the eSIM configuration system provided in the embodiments of this disclosure; Figure 2 A flowchart illustrating an eSIM configuration method provided in an embodiment of this disclosure; Figure 3 A flowchart illustrating another eSIM configuration method provided in this embodiment of the disclosure; Figure 4 A flowchart illustrating yet another eSIM configuration method provided in this disclosure embodiment; Figure 5 A flowchart illustrating yet another eSIM configuration method provided in this disclosure embodiment; Figure 6 A flowchart illustrating yet another eSIM configuration method provided in this disclosure embodiment; Figure 7 This is a flowchart of exception handling and retransmission triggering provided in the embodiments of this disclosure; Figure 8 This is a schematic diagram illustrating the composition of an eSIM configuration device provided in an embodiment of the present disclosure; Figure 9 This is a schematic diagram illustrating the composition of another eSIM configuration device provided in an embodiment of the present disclosure; Figure 10 This is a schematic diagram illustrating the composition of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0016] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0017] Unless the context otherwise requires, throughout the specification and claims, the term "comprise" and other forms such as the third-person singular "comprises" and the present participle "comprising" are interpreted as open-ended and encompassing, meaning "including, but not limited to." In the description of the specification, terms such as "one embodiment," "some embodiments," "exemplary embodiments," "example," "specific example," or "some examples" are intended to indicate that a particular feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of this disclosure. The illustrative representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics mentioned may be included in any suitable manner in any one or more embodiments or examples.

[0018] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this disclosure, unless otherwise stated, "a plurality of" means two or more.

[0019] In this disclosure, the terms "exemplarily" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplarily" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the terms "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0020] In addition, the use of “based on” implies openness and inclusivity, because processes, steps, calculations or other actions “based on” one or more of the stated conditions or values ​​may in practice be based on additional conditions or values ​​beyond those stated.

[0021] Traditional SIM cards are typically inserted into a terminal's card slot as separate physical cards. Each SIM card is tied to a contract with a specific operator, requiring users to replace the physical card when changing operators or devices. This process is cumbersome and carries the risk of card loss or damage. For miniaturized terminals such as IoT devices and wearable devices, the physical card slot and SIM card replacement process become significant factors restricting their miniaturization and large-scale deployment.

[0022] To address this, eSIM technology has been proposed. The core of eSIM technology lies in replacing the traditional removable SIM card with an eUICC soldered onto the terminal's motherboard. The eUICC does not pre-install operator subscription information and supports remote configuration of the eSIM profile. The terminal can select and activate the profile as needed to access the corresponding operator's network.

[0023] In eSIM remote configuration schemes in related technologies, the terminal side is usually equipped with a Local Profile Assistant (LPA) module as a local management agent. The LPA module can establish a connection with the operator's Enhanced Subscription Manager Data Preparation+ (SM-DP+) server through the Internet Protocol (IP) network, receive the eSIM configuration file sent by the SM-DP+ server, and then write the eSIM configuration file into the eUICC to complete the eSIM remote configuration.

[0024] However, eSIM remote configuration solutions in related technologies rely on IP network coverage and the terminal's ability to provide an LPA module operating environment. It is difficult to implement eSIM remote configuration in terminals without an operating system, in low-power, offline, or weak network scenarios. The applicability of eSIM remote configuration solutions needs to be improved.

[0025] Based on this, the present disclosure provides an eSIM configuration method, electronic device, storage medium, and program product that can transmit control plane messages carrying eSIM configuration files through non-IP data channels without relying on IP network connections and the operating environment of the LPA module within the terminal. This makes it suitable for terminal devices in scenarios such as no operating system, low power consumption, offline, or weak network conditions, thus improving the applicability of eSIM remote configuration.

[0026] The following description is provided in conjunction with the accompanying drawings.

[0027] Figure 1 This is a schematic diagram illustrating the composition of an eSIM configuration system provided in an embodiment of this disclosure. Figure 1As shown, the eSIM configuration system may include a configuration server 100 and a terminal device 200.

[0028] The configuration server 100 can be a server with eSIM configuration file generation, management, and distribution functions. For example, the configuration server 100 can be a Subscription Manager Data Preparation (SM-DP) server, an SM-DP+ server, an operator-owned eSIM configuration management server, a third-party eSIM configuration management server, or an IoT management server, etc. This disclosure does not limit the specific form of the configuration server 100.

[0029] The aforementioned server can be a single server or a server cluster consisting of multiple servers. In some embodiments, the server cluster can also be a distributed cluster. Optionally, the server can also be implemented on a cloud platform, such as a private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, inter-cloud, and multi-cloud, or any combination thereof. This disclosure does not impose any limitations on this.

[0030] The configuration server 100 can be used to send control plane messages to the terminal device through a first data channel; the first data channel is a non-network protocol IP data channel; the control plane messages include fragments of the embedded Subscriber Identity Module (eSIM) profile. Specific details can be found in the following method embodiments, and will not be repeated here.

[0031] Terminal device 200 can be a handheld device (such as a mobile phone or tablet), an in-vehicle device, a wearable device, an IoT device in an Internet of Things (IoT) system, an Ambient IoT device, or a computing device, etc. Figure 1 The example shown is a mobile phone as the terminal device 200. This disclosure does not limit the specific form of the terminal device 200.

[0032] Terminal device 200 can be used to obtain the eSIM profile based on eSIM profile fragments in control plane messages; and write the eSIM profile to the embedded universal integrated circuit card eUICC to complete the eSIM configuration. Specific details can be found in the following method embodiments, and will not be repeated here.

[0033] In some embodiments, the hardware configuration of the terminal device 200 may include an eUICC chip, a main control processor, non-volatile memory (such as flash memory) or electrically erasable programmable read-only memory (EEPROM). Only Memory (EEPROM), communication modules, and security units (such as Secure Element (SE), Trusted Execution Environment (TEE), or eUICC built-in security zone).

[0034] The main control processor is used to run the downloaded firmware. Non-volatile memory is used to cache eSIM profile fragments and the complete eSIM profile sent by the configuration server 100. The communication module is used to receive eSIM profile fragments sent by the configuration server 100. The security unit is used to perform sender identity verification on the eSIM profile fragments and integrity verification on the eSIM profile.

[0035] In some embodiments, the software structure of the terminal device 200 may include an application layer, a control logic layer, a system service layer, and a driver layer.

[0036] The application layer is used to enable users to trigger eSIM configuration file downloads and status notifications.

[0037] The control logic layer integrates a fragmentation and reassembly engine, an offline verification module (eUICC identifier (eUICCIdentifier, EID) matching, cyclic redundancy check (CRC), and hash message authentication code (Hash). Based on Message Authentication Code (HMAC) signature verification and Application Protocol Data Unit (APDU) instruction generator, it directly drives eUICC to complete the eSIM configuration file installation.

[0038] The system service layer provides operating system scheduling, scheduled tasks, and secure application programming interfaces (APIs), such as key access and secure boot.

[0039] The driver layer includes the protocol stack driver for the first data channel (such as the SMS protocol stack driver), the eUICC communication interface (such as the Single Wire Protocol (SWP) or the Serial Peripheral Interface (SPI)), and the security chip access interface.

[0040] The aforementioned layers can interact via standard APIs, supporting independent operation in lightweight environments without LPA agents. They are adaptable to different chip platforms (such as using Field-Programmable Gate Arrays (FPGAs) to replace Microcontroller Units (MCUs) or Application-Specific Integrated Circuits (ASICs) for encryption modules). This architecture allows for software-defined download processes within the GSMA SGP.02 / SGP.32 protocol framework, satisfying both hardware implementability and achieving layered decoupling and component replacement.

[0041] It should be noted that, Figure 1 This is merely an illustrative framework diagram. Figure 1 The number of devices included and the names of each device are unlimited. And except... Figure 1 In addition to the devices shown, the eSIM configuration system may also include other nodes or devices.

[0042] The system architecture and business scenarios described in the embodiments of this disclosure are intended to more clearly illustrate the technical solutions of the embodiments of this disclosure and do not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. Those skilled in the art will recognize that, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0043] This disclosure first provides an eSIM configuration method, which can be applied to a terminal device (such as the terminal device 200 described above). Figure 2 This is a flowchart illustrating an eSIM configuration method provided in an embodiment of this disclosure. Figure 2 As shown, the method may include the following steps: S101, Receive control plane messages sent by the configuration server through the first data channel.

[0044] The first data channel is a non-network protocol IP data channel, and the control plane messages include fragments of the embedded user identification module eSIM profile.

[0045] As an example, the first data channel may include at least one of the following: (1) Unstructured Supplementary Service Data (USSD) channel.

[0046] The USSD channel is an interactive data channel based on the signaling channel of a mobile communication network. It enables the establishment of a real-time session connection between the terminal device and the network side without requiring the terminal device to establish an IP data bearer. Correspondingly, control plane messages transmitted through the USSD channel can also be understood as USSD messages. USSD messages can be initiated by the configuration server to the terminal device or by the terminal device to the configuration server. USSD messages can be carried in signaling messages, supporting multiple data interactions within a single session.

[0047] The eSIM configuration method provided in this disclosure can transmit eSIM configuration file fragments using a USSD channel. This leverages the existing USSD service capabilities deployed in mobile communication networks, allowing terminal devices to receive eSIM configuration file fragments without accessing an IP network, thus avoiding reliance on IP bearers. Furthermore, the USSD channel offers real-time interaction, enabling terminal devices to promptly report reception status or request retransmissions to the configuration server. This improves the reliability and real-time performance of eSIM configuration file fragment transmission in weak network or IP-free environments.

[0048] (2) Card Application Toolkit Transmission Protocol Transport Protocol, CAT TP channel.

[0049] The CAT-TP channel is a transmission channel established based on the CAT-TP protocol, which is used to carry data related to card applications. Control plane messages transmitted through the CAT-TP channel can also be understood as CAT-TP messages. CAT-TP messages are messages encapsulated and transmitted using the CAT-TP protocol, and the protocol's acknowledgment and retransmission mechanisms can ensure the reliable arrival of eSIM profile fragments.

[0050] The eSIM configuration method provided in this disclosure can transmit eSIM configuration file fragments via a CAT-TP channel. It leverages the card application toolkit functionality supported by eUICC itself for data transmission, eliminating the need for the terminal device to run a complete operating system or LPA module, thus reducing the requirements for the terminal device's software environment. Furthermore, the data integrity protection and reliable transmission mechanisms provided by the CAT-TP protocol itself help improve the security and integrity of eSIM configuration file fragments during transmission, making it suitable for resource-constrained, operating system-less, or low-power terminal devices.

[0051] (3) Narrowband Internet of Things Internet of Things, NB IoT control plane message channel.

[0052] Among them, NB The IoT control plane message channel refers to a channel established using the control plane transmission mechanism of the NB-IoT network, through the non-access layer (Non-IoT). Access Stratum (NAS) messages or similar control plane signaling carry small data packets, eliminating the need to establish a user plane data bearer. This is achieved through NB-IoT. The control plane messages transmitted through the IoT control plane message channel can also be understood as NB-IoT control plane messages. The message content of NB-IoT control plane messages can be encapsulated in NAS messages or control plane data containers.

[0053] The eSIM configuration method provided in this disclosure can transmit eSIM configuration file fragments using the NB-IoT control plane message channel, fully utilizing the wide coverage, deep coverage, and low power consumption characteristics of the NB-IoT network. After waking up, the terminal device does not need to establish a complete IP data connection; it can receive configuration data solely through control plane signaling, reducing the terminal device's power consumption and signaling overhead. Simultaneously, the NB-IoT control plane transmission channel offers high transmission reliability, making it suitable for low-power IoT terminal devices deployed in weak coverage environments such as underground or remote areas.

[0054] (4) Cell Broadcast Service (CBS) channel.

[0055] The CBS channel is a CBS-based channel that allows the configuration server to simultaneously broadcast the same message to multiple terminal devices within a specified area. Terminal devices only need to be within the cell's coverage area to receive the message. Control plane messages transmitted through the CBS channel can include Short Message Service (SMS) messages broadcast by the configuration server.

[0056] The eSIM configuration method provided in this disclosure can transmit eSIM configuration file fragments via a CBS channel, enabling the configuration server to configure multiple terminal devices in parallel. Terminal devices can receive broadcast eSIM configuration file fragments without uplink requests, which helps reduce power consumption and access signaling burden on terminal devices, making it suitable for large-scale IoT device batch configuration scenarios.

[0057] (5) Short Message Service Point to Point, SMS PP channel.

[0058] The SMS-PP channel is based on SMS-PP, allowing terminal devices to receive SMS messages sent by the configuration server via the mobile communication network. Control plane messages transmitted through the SMS-PP channel can also be understood as SMS messages sent by the configuration server to the terminal device.

[0059] The eSIM configuration method provided in this disclosure can transmit eSIM configuration file fragments via the SMS-PP channel. This leverages the widespread coverage and common terminal support of SMS services in mobile communication networks, allowing terminal devices to receive configuration data without establishing an IP data connection. When the terminal device is temporarily unreachable, SMS messages can be cached and delivered again once the terminal device becomes accessible, improving the reliability of eSIM configuration.

[0060] Based on the understanding of the above embodiments, the types of control plane messages can be understood to include at least one of the following: USSD messages, CAT-TP messages, NB-IoT control plane messages, SMS messages broadcast by the configuration server, and SMS messages sent by the configuration server to the terminal device.

[0061] S102. Obtain the eSIM profile based on the eSIM profile fragment in the control plane message.

[0062] As an example, each control plane message may include one or more eSIM profile fragments. The terminal device can receive multiple control plane messages and combine the eSIM profiles from the multiple control plane messages into an eSIM profile.

[0063] S103. Write the eSIM configuration file to the embedded universal integrated circuit card eUICC to complete the eSIM configuration.

[0064] As an example, step S103 above may specifically include: generating a configuration file writing instruction based on the eSIM configuration file through the underlying firmware of the terminal device's operating system or a trusted execution environment; and sending the configuration file writing instruction to the eUICC through the eUICC interface driver to write the eSIM configuration file to the eUICC.

[0065] The configuration file writing command includes the configuration information of the eSIM configuration file.

[0066] In the eSIM configuration method provided in this disclosure, when writing the eSIM configuration file to the eUICC, the terminal device can generate a configuration file writing instruction based on the configuration file through the underlying firmware of the operating system or a trusted execution environment, and then send it to the eUICC through the eUICC interface driver. Since the generation and issuance of the writing instruction do not depend on the complete LPA module or complex protocol stack in the upper-layer operating system, the requirements for the terminal device's software operating environment are reduced. At the same time, the underlying firmware or trusted execution environment can provide security isolation, protecting the configuration file from being easily stolen or tampered with by ordinary applications during the internal processing of the terminal device. Direct transmission through the eUICC interface driver also adapts to terminals without an operating system or with limited resources, thereby expanding the feasibility and security of the eSIM configuration method on various terminal devices.

[0067] In the eSIM configuration method provided in this disclosure, the terminal device can receive control plane messages sent by the configuration server through a first data channel (non-IP data channel). The control plane messages carry eSIM configuration file fragments, so that the transmission of the eSIM configuration file does not depend on an IP network connection, nor does it require the terminal device to provide an LPA module operating environment. This reduces the processing power and network coverage requirements of the terminal device during eSIM remote configuration. It can also complete eSIM remote configuration in scenarios such as no IP network coverage, weak network, low power consumption, or no operating system, thus expanding the scope of application of the eSIM remote configuration scheme and improving its applicability.

[0068] In some embodiments, in addition to eSIM profile fragments, control plane messages may also carry at least one of the following information: (1) The segment number corresponding to the eSIM configuration file segment.

[0069] The fragment number is used to identify the order or position number of each eSIM profile fragment in the entire eSIM profile.

[0070] As an example, when the configuration server divides a complete eSIM profile into multiple profile fragments, it can assign a unique fragment number to each profile fragment, such as starting from 0 and incrementing or using other numbering methods.

[0071] In the eSIM configuration method provided in this disclosure, the control plane message may also carry the fragment sequence number corresponding to the eSIM configuration file fragment. This allows the terminal device to sort and reassemble the fragments according to their sequence numbers after receiving them, thereby recovering the complete eSIM configuration file. Simultaneously, the fragment sequence number helps the terminal device determine whether there are missing, duplicate, or out-of-order fragment receptions, facilitating the request to the configuration server to retransmit specific missing fragments when necessary. By carrying the fragment sequence number, the orderliness of fragment transmission and the convenience of management can be improved, reducing the error rate of reassembling the eSIM configuration file.

[0072] (2) The total number of eSIM profile segments is divided into eSIM profile segments.

[0073] The total number of eSIM profile segments can be used to inform the terminal device how many segments the complete eSIM profile has been divided into.

[0074] In the eSIM configuration method provided in this disclosure, the control plane message may also carry the total number of eSIM profile fragments into which the eSIM profile is divided. This allows the terminal device to determine whether all eSIM profile fragments have been received by combining the fragment sequence number and the total number of fragments. For example, when the fragment sequence number received by the terminal device covers all sequence numbers from the starting sequence number to the total number of fragments, it can be determined that all eSIM profile fragments have been received, and reassembly can begin. Carrying the total number of fragments allows the terminal device to complete the integrity check without relying on other external information, simplifying the configuration process and avoiding the risk of reassembly failure or writing incorrect profiles due to incomplete fragment reception, thus improving the reliability of the configuration process.

[0075] (3) Authentication information of the sender of the eSIM configuration file fragment.

[0076] The authentication information of the eSIM profile fragment sender can be used to verify whether the source of the eSIM profile fragment is a legitimate configuration server.

[0077] For example, the type of authentication information may include digital signatures, certificate information, HMAC signatures, or other security credentials used to prove the sender's identity. This disclosure does not limit the specific type of authentication information.

[0078] In the eSIM configuration method provided in this disclosure, the control plane message may also carry authentication information of the eSIM profile fragment sender. This allows the terminal device to verify the authentication information upon receiving the eSIM profile fragment, confirming that the eSIM profile fragment indeed originates from a trusted configuration server and is not a forged or tampered third party. By carrying the sender's authentication information, malicious devices can be prevented from sending forged eSIM profile fragments to the terminal device, avoiding the terminal device being configured to an unauthorized network or subjected to third-party attacks, thus improving the security of the eSIM configuration process.

[0079] (4) Integrity verification information of eSIM configuration file.

[0080] The integrity verification information is used to verify the integrity of the reassembled complete eSIM profile to confirm that the eSIM profile has not been tampered with or damaged during fragmentation and reassembly.

[0081] For example, the types of integrity verification information may include the hash value of the eSIM configuration file, digital signature, CRC code, etc. This disclosure does not limit the specific types of integrity verification information.

[0082] In the eSIM configuration method provided in this disclosure, the control plane message can also carry integrity verification information of the eSIM configuration file. In this way, after the terminal device obtains the eSIM configuration file by fragmenting and reassembling the eSIM configuration file, it can calculate the hash value or checksum of the eSIM configuration file and compare it with the integrity verification information carried in the control plane message. If they match, it indicates that the configuration file is complete and error-free. By carrying integrity verification information in the control plane message, the terminal device can detect potential transmission errors or malicious tampering of the eSIM configuration file before writing it to the eUICC, avoiding writing incomplete or tampered configuration files to the eUICC, thereby reducing the risk of configuration failure and subsequent network access anomalies.

[0083] (5) The identity identifier of the target terminal device corresponding to the eSIM configuration file fragment.

[0084] The identity identifier of the target terminal device is used to indicate the receiving object corresponding to the corresponding eSIM profile fragment.

[0085] For example, the identity identifier of the target terminal device may be its International Mobile Equipment Identity (IMEI), device serial number, EID, or user identifier. This disclosure does not limit the specific type of identity identifier for the target terminal device.

[0086] In the eSIM configuration method provided in this disclosure, the control plane message can also carry the identity identifier of the target terminal device corresponding to the eSIM configuration file fragment. In this way, after receiving the eSIM configuration file fragment, the terminal device can determine whether the identity identifier of the target terminal device corresponding to the eSIM configuration file fragment matches its own identity identifier, thereby confirming whether the eSIM configuration file fragment is the configuration data sent to it. By carrying the identity identifier of the target terminal device, the problem of misdelivery or misreception of eSIM configuration file fragments can be avoided in broadcast or when multiple terminals share the same channel. Simultaneously, when the configuration server sends the eSIM configuration file fragment using broadcast, different terminal devices can filter out their own eSIM configuration file fragments from the received fragments based on the identity identifier of the target terminal device, improving the accuracy and specificity of eSIM configuration.

[0087] (6) The validity period of eSIM profile fragments.

[0088] The validity period of the eSIM profile fragment is used to determine the effective period of the eSIM profile fragment. The terminal device can perform subsequent verification and reassembly only on the eSIM profile fragments that are within the validity period.

[0089] For example, the validity period of an eSIM profile fragment can be represented by absolute time, meaning the validity period can be indicated by the start and end times of the validity period; or, the validity period of an eSIM profile fragment can be represented by relative time, meaning the validity period can be indicated by the duration of the validity period. The control plane message can also carry a sending timestamp, and the terminal device can combine the sending timestamp of the control plane message with the duration of the validity period to determine whether it is within the validity period.

[0090] In some embodiments, control plane messages may also carry the transaction identifier of the configuration transaction corresponding to the eSIM profile.

[0091] In the eSIM configuration method provided in this disclosure, the control plane message can also carry the validity period of the eSIM profile fragment. This allows the terminal device, upon receiving an eSIM profile fragment, to determine if it is currently within the validity period of the eSIM profile. If it has expired, the terminal device discards the eSIM profile fragment or requests a retransmission from the configuration server. By carrying validity period information, the terminal device can prevent the use of expired eSIM profile fragments due to transmission delays, network caching, or replay attacks for configuration, avoiding security issues or configuration errors caused by using outdated configuration data. Simultaneously, the validity period facilitates the configuration server's lifecycle management of the eSIM profile fragments, improving the timeliness and security of the configuration process.

[0092] In some embodiments, the step of obtaining the eSIM configuration file based on the eSIM configuration file fragment in the control plane message in S102 may specifically include: performing at least one of the following verification operations: sender identity verification operation, identity identifier consistency verification operation, and validity period verification operation; and obtaining the eSIM configuration file based on the eSIM configuration file fragment in the control plane message after all eSIM configuration file fragments have been received and at least one verification operation has passed, based on the eSIM configuration file fragment in the control plane message.

[0093] As an example, the sender identity verification operation includes: verifying the sender's identity for each eSIM profile fragment based on the sender's identity verification information in each control plane message.

[0094] The sender identity verification operation is used to verify that the eSIM profile fragment in each control plane message does indeed come from a legitimate configuration server, preventing malicious third parties from forging configuration servers and sending forged eSIM profile fragments to terminal devices.

[0095] For example, when a configuration server sends an eSIM profile fragment via control plane messages, it can include the sender's authentication information for that eSIM profile fragment in each control plane message. This authentication information could be a signature value generated by the configuration server digitally signing the eSIM profile fragment content or digest using its private key; a message authentication code generated using a shared key between the terminal device and the configuration server; or the configuration server's certificate information or certificate digest. The terminal device can pre-store the configuration server's public key, shared key, or root certificate. Upon receiving a control plane message, the terminal device can extract the authentication information and verify the digital signature based on the pre-stored public key, or recalculate the message authentication code based on the shared key and compare it with the received message authentication code. If the verification passes, it indicates that the sender of the eSIM profile fragment is legitimate; if the verification fails, the terminal device can discard the fragment.

[0096] As an example, the identity consistency verification operation includes: determining whether the identity identifier of the target terminal device corresponding to the eSIM profile fragment in each control plane message is the same as the identity identifier of the terminal device itself.

[0097] For example, when the configuration server sends a control plane message, it can include the target terminal device's identity identifier. This identifier can be at least one of the terminal device's IMEI, device serial number, EID, ICCID, SUPI, IMSI, or device certificate identifier. After receiving the control plane message, the terminal device can parse the target terminal device's identity identifier from the control plane message and compare it with its own identity identifier. If they match, it means that the eSIM profile fragment carried in the control plane message was sent to this terminal device and can continue to participate in subsequent reassembly; if they do not match, it means that the eSIM profile fragment carried in the control plane message may be a fragment sent to other terminal devices in a broadcast scenario, and the terminal device can discard the fragment.

[0098] As an example, the validity period verification operation includes: determining whether the current time is within the validity period of the eSIM profile fragment in each control plane message.

[0099] For example, when sending each control plane message, the configuration server can include the eSIM profile fragment's validity period information. This validity period information can be expressed as an absolute time, such as the eSIM profile fragment's start and end times; or it can be expressed as a relative time, such as the validity duration calculated from the time the configuration server sends the message. The terminal device can then calculate the fragment's expiration time by combining the control plane message's sending timestamp and the validity duration. Upon receiving the control plane message, the terminal device parses the validity period information and obtains its current system or network time to determine if the current time is within the eSIM profile fragment's validity period. If the current time is within the validity period, the eSIM profile fragment is still valid and can continue to participate in subsequent reassemblies; if the current time has exceeded the validity period, the terminal device can discard the eSIM profile fragment.

[0100] It should be noted that the sender identity verification, identity consistency verification, and validity period verification operations described above can be performed individually or in any combination. The terminal device can perform these verification operations sequentially according to a preset order, or in parallel. For example, the terminal device can first perform the identity consistency verification operation to filter out eSIM profile fragments that are not destined for it, and then perform sender identity verification and validity period verification operations on the remaining eSIM profile fragments. Alternatively, the terminal device can perform all three verification operations simultaneously on each control plane message; only eSIM profile fragments that pass all three verification operations are retained for subsequent reassembly.

[0101] After completing the above verification operations and confirming that all eSIM profile fragments have been received based on the fragment sequence number and the total number of fragments, the terminal device retrieves the eSIM profile based on the verified eSIM profile fragments. Retrieving the eSIM profile may involve sorting all fragments according to their fragment sequence numbers and then sequentially concatenating the contents of each fragment according to the sorting results to reconstruct a complete eSIM profile. If any eSIM profile fragment fails verification or is missing, the terminal device may choose not to perform the reconstruction operation. As an example, after S101 and before S102 above, the method may further include: determining whether all eSIM profile fragments divided from the eSIM profile have been received completely based on the fragment sequence number corresponding to the eSIM profile fragment in the control plane message and the total number of eSIM profile fragments divided from the eSIM profile.

[0102] For example, with a total number of N fragments and fragment numbers starting from 0, the terminal device needs to confirm that it has received all eSIM profile fragments with fragment numbers 0, 1, 2, ..., N-1.

[0103] The eSIM configuration method provided in this disclosure can perform at least one of the following before obtaining the eSIM configuration file: sender identity verification, identity identifier consistency verification, and validity period verification. Furthermore, eSIM configuration file reassembly is only performed if all eSIM configuration file fragments have been received and all verifications have passed, based on the fragment sequence number and total number of fragments. This allows for the identification and exclusion of forged, misdelivered, or expired eSIM configuration file fragments before reassembly, preventing invalid eSIM configuration files from participating in the reassembly. Simultaneously, confirming complete reception based on the fragment sequence number and total number of fragments prevents the generation of incomplete or erroneous eSIM configuration files due to missing fragments, thereby improving the correctness, completeness, and security of the final eUICC configuration file and reducing the risk of configuration failure.

[0104] In some embodiments, if the sender identity verification operation fails M times consecutively, the terminal device may stop receiving control plane messages.

[0105] Where M is a positive integer. For example, M can be set to 3, 4, 5, 6, or 7, etc. The specific value of M is not limited in the embodiments of this disclosure.

[0106] In the eSIM configuration method provided in this disclosure, the terminal device stops receiving control plane messages if the sender identity verification operation fails M consecutive times. This allows for timely interruption of the data reception process when the source of the received eSIM configuration file fragment is found to be continuously untrusted. Since consecutive sender identity verification failures typically indicate that the messages transmitted on the current first data channel (non-IP data channel) are likely not from a legitimate configuration server, but rather forged, replayed, or interfered messages, if the terminal device continues to receive and process these messages, it will continuously consume processing resources, storage space, and power. This could lead to the buffer being filled with invalid fragments, affecting the reception and reassembly of subsequent legitimate fragments, and even causing the battery to be depleted too quickly. By presetting the M value and stopping reception in a timely manner, invalid or malicious data can be prevented from continuously occupying resources.

[0107] In some embodiments, the step of writing the eSIM configuration file to the embedded universal integrated circuit card eUICC in S103 above may specifically include: verifying the integrity of the eSIM configuration file based on the integrity verification information of the eSIM configuration file in the control plane message; and writing the eSIM configuration file to the embedded universal integrated circuit card eUICC if the integrity verification of the eSIM configuration file passes.

[0108] As an example, taking CRC verification, after generating a complete eSIM configuration file, the configuration server can use a CRC algorithm such as CRC-32 to calculate a CRC checksum, which is then carried as integrity verification information in the control plane message and sent to the terminal device. After reassembling the eSIM configuration file, the terminal device can recalculate the CRC checksum using the same CRC algorithm and compare the calculated CRC checksum with the CRC checksum in the received control plane message. If they match, the integrity verification is successful; otherwise, the integrity verification fails.

[0109] As an example, taking hash digest verification, after generating a complete eSIM configuration file, the configuration server can use the SHA-256 algorithm to hash the entire eSIM configuration file, obtaining a 256-bit digest value, which is then sent to the terminal device as integrity verification information in the control plane message. After reassembling the eSIM configuration file, the terminal device can recalculate the hash digest using the same SHA-256 algorithm and compare the calculated digest value bit-by-bit with the received digest value. If they are identical, the integrity verification is successful; otherwise, it fails. The eSIM configuration method provided in this disclosure verifies the integrity of the eSIM configuration file based on integrity verification information carried in the control plane message before writing it to the eUICC. Only after successful verification is the writing operation performed. Since writing to the eUICC is a sensitive and difficult-to-recover operation, directly writing an incomplete or tampered eSIM configuration file may lead to abnormal subscription information, network access failure, or even the need for reconfiguration. This disclosure, by adding an integrity verification step before writing, ensures that only complete and untampered eSIM configuration files are written to the eUICC, thereby improving the eSIM configuration success rate and avoiding device malfunctions caused by data corruption or tampering.

[0110] In some embodiments, the method may further include: sending a first retransmission message to a configuration server if the integrity verification of the eSIM profile fails.

[0111] The first retransmission information is used to request the retransmission of all eSIM profile fragments of the eSIM profile through the first data channel or the IP data channel.

[0112] As an example, the first retransmission information may include the identity identifier of the terminal device or the transaction identifier of the configuration transaction corresponding to the eSIM configuration file.

[0113] As an example, after sending the first retransmission information, the terminal device can enter a waiting state and listen for control plane messages on the retransmission channel (first data channel or IP data channel) agreed upon with the configuration server. If the configuration server retransmits the eSIM profile fragment via the first data channel, the terminal device continues to receive, verify, and reassemble the eSIM profile fragment according to the aforementioned steps; if the configuration server retransmits the eSIM profile via the IP data channel, the terminal device can establish or activate the corresponding IP connection and receive the eSIM profile fragment via the IP channel.

[0114] In the eSIM configuration method provided in this disclosure, when the integrity verification of the eSIM configuration file fails, the terminal device can proactively send a first retransmission message to the configuration server, requesting the retransmission of all eSIM configuration file fragments through the first data channel or the IP data channel. This way, if eSIM configuration file fragments are lost, corrupted, or tampered with during transmission, causing the overall integrity verification to fail, the configuration process will not be directly interrupted; instead, data will be recovered through feedback and retransmission mechanisms. Simultaneously, the retransmission channel can flexibly select either the original first data channel (non-IP channel) or the IP channel, enabling the use of a more suitable channel to complete transmission when network conditions change, thereby improving the fault tolerance capability and configuration success rate of the eSIM configuration process.

[0115] In some embodiments, after S101, the method may further include: if an eSIM profile fragment is parsed from a control plane message, writing the eSIM profile fragment into a circular buffer according to its fragment number. Specifically, S102 may include: determining the eSIM profile based on the eSIM profile fragments stored in the circular buffer.

[0116] The ring buffer is a fixed-size circular buffer that occupies a contiguous or logically contiguous storage space in the terminal device's memory. The ring buffer can be pre-allocated or allocated upon first receiving an eSIM profile fragment based on the total number of fragments or a preset fragment size. The ring buffer is divided into multiple slots, each slot storing data for one eSIM profile fragment. The number of slots can be determined based on the total number of fragments in the eSIM profile or set to a fixed value based on the available memory size of the terminal device. For example, if the eSIM profile is divided into N fragments, the ring buffer can have N slots, each corresponding to a fragment sequence number; alternatively, the ring buffer can have fewer than N slots. This disclosure does not limit the specific size of the ring buffer.

[0117] As an example, the circular buffer may be located in a TEE, SE, or encrypted Flash, and this disclosure does not limit this.

[0118] In some embodiments, the terminal device can also be equipped with a four-level memory protection strategy for the ring buffer. When the cache utilization exceeds 70%, asynchronous verification can be started and HMAC and CRC verification can be suspended. When the cache utilization reaches 90%, the reception of control plane messages can be suspended. When the cache utilization reaches 100%, invalid data can be cleared. In the event of continuous overflow of the ring buffer, a memory overload command is actively sent to the configuration server to request the suspension of the issuance of control plane messages, so as to ensure stable operation on IoT terminals with limited random access memory (RAM) resources.

[0119] It should be understood that during the transmission of eSIM profile fragments through non-IP data channels, because USSD messages, SMS messages, NB-IoT control plane messages, or SMS messages may arrive at the terminal device via different signaling paths, store-and-forward nodes, or scheduling times, the order in which eSIM profile fragments arrive at the terminal device is often inconsistent with the order in which they are sent by the configuration server, i.e., out-of-order arrival occurs.

[0120] The eSIM configuration method provided in this disclosure can write and read eSIM configuration file fragments through a circular buffer, decoupling the writing process and the reading and reassembly process in terms of time and sequence. During writing, the terminal device only needs to place each eSIM configuration file fragment into its corresponding slot according to its fragment sequence number, without needing to write them sequentially according to the fragment sequence number. During reading, the terminal device can wait until all eSIM configuration file fragments have been received, and then read each eSIM configuration file fragment from its corresponding slot in ascending order of fragment sequence number and concatenate them. When reading each eSIM configuration file fragment in the circular buffer, there is no need to consider the actual writing order of the fragments; reading according to the slot index order is sufficient to obtain the correct file content. Thus, even if the eSIM configuration file fragments arrive in disorder during reception, it will not affect the correctness of the final reassembly result. This allows the terminal device to directly write each eSIM configuration file fragment to the correct position and read them out in order for reassembly even when fragments arrive out of order, thereby ensuring the correctness and robustness of the eSIM configuration file fragment reception and reassembly process in non-IP data channel transmission environments.

[0121] In some embodiments, the method may further include: within a preset time period after the eSIM profile fragment is first written into the circular buffer, if it is determined that not all eSIM profile fragments divided from the eSIM profile have been received, based on the fragment sequence number corresponding to the eSIM profile fragment in the control plane message and the total number of eSIM profile fragments divided from the eSIM profile, then based on the total number of fragments and the fragment sequence number of the eSIM profile fragment stored in the circular buffer, determining the fragment sequence number of the unreceived eSIM profile fragment; and sending a second retransmission message to the configuration server.

[0122] The second retransmission information is used to request the retransmission of unreceived eSIM profile fragments via the first data channel or IP data channel. The second retransmission information includes the fragment sequence number of the unreceived eSIM profile fragment. The preset duration can be pre-configured by the terminal device, or it can be sent to the terminal device by the configuration server via control plane messages or configuration trigger response messages. It can also be dynamically adjusted according to the current network environment and channel type of the terminal device. For example, the preset duration can be set to 30 seconds, 1 minute, 3 minutes, or 5 minutes. This embodiment does not limit the specific duration of the preset duration.

[0123] As an example, the terminal device determines the set of complete fragment sequence numbers to be received based on the total number of fragments divided from the eSIM profile. For instance, if the total number of fragments is N and the fragment numbers start from 0, then the complete set of fragment sequence numbers is {0, 1, 2, ..., N-1}. The terminal device reads the fragment sequence numbers corresponding to all currently stored eSIM profile fragments in the circular buffer to obtain the set of received fragment sequence numbers. Then, the terminal device can perform a difference operation between the complete set of fragment sequence numbers and the set of received fragment sequence numbers to determine the fragment sequence numbers of the eSIM profile fragments that have not been received.

[0124] As an example, when the terminal device is not in a power-saving or data-off state, it can generate a Negative Acknowledgement (NACK) request, including the fragment sequence number of the eSIM profile fragment that was not received, to obtain a second retransmission message. This second retransmission information is then sent to the configuration server via a dedicated SMS message format (e.g., RETRY:TID=ABC123;SN=3,7,9,12;SIG=...). Alternatively, when the terminal device is not in a power-saving or data-off state, it can generate a lightweight NACK Protocol Data Unit (PDU) to obtain the second retransmission message.

[0125] In the eSIM configuration method provided in this disclosure, if, within a preset time period after the initial writing of fragments to the circular buffer, it is determined that all eSIM configuration file fragments have not been received, based on the fragment sequence number and the total number of fragments, the terminal device can determine the unreceived eSIM configuration file fragments based on the total number of fragments and the existing fragment sequence numbers in the buffer, and send second retransmission information containing the fragment sequence numbers of the unreceived eSIM configuration file fragments, requesting retransmission of the unreceived eSIM configuration file fragments through the first data channel or the IP data channel. Timeout detection can promptly detect transmission interruptions or partial eSIM configuration file fragment loss. By locating the missing unreceived eSIM configuration file fragments based on the existing fragment sequence numbers and requesting retransmission of only the missing portion, retransmission of all eSIM configuration file fragments can be avoided, reducing redundant transmission and lowering terminal reception and processing overhead. Simultaneously, the circular buffer adapts to resource-constrained terminals, improving the efficiency and reliability of configuration in weak network environments.

[0126] In some embodiments, before receiving control plane messages sent by the configuration server via a non-network protocol IP data channel, the method may further include: sending configuration trigger information to the configuration server in response to detecting a trigger event.

[0127] The configuration trigger information is used to trigger the configuration server to send control plane messages. This configuration trigger information includes the terminal device's identity information. For example, the types of terminal device identity information may include IMEI, device serial number, EID, Integrated Circuit Card Identifier (ICCID), or Subscription Permanent Identifier (SUPI), etc. This disclosure does not limit the specific types of terminal device identity information. The configuration server can authenticate and authorize the terminal device based on this identity information, confirming that the terminal device is entitled to obtain the requested eSIM profile, and can query or generate the eSIM profile corresponding to the terminal device based on the identity information.

[0128] As an example, a triggering event may include at least one of the following: (1) The user's trigger operation was detected.

[0129] User-triggered operations can include operations related to eSIM configuration performed by the user on the terminal device.

[0130] For example, users can click buttons such as "Download eSIM Configuration," "Update Configuration File," or "Switch Carrier" on the eSIM configuration interface of their terminal device, or enter an activation code or plan code provided by the carrier on the terminal device, or scan a QR code or barcode containing configuration information. The terminal device's operating system or underlying firmware can detect the above operations, generate configuration trigger information in response to the operation, and then send it to the configuration server.

[0131] For example, for terminal devices without an operating system or with weak interactive capabilities, user triggering operations can also include pressing physical buttons on the terminal device, switching on / off switches, or writing trigger commands through an external programmer or debugging interface. For instance, an IoT terminal can be equipped with a configuration button. When a user presses this button during installation or maintenance, the IoT terminal detects the triggering operation and initiates a configuration trigger.

[0132] (2) Receive trigger commands sent by other devices.

[0133] The trigger commands sent by other devices can originate from external devices that have a communication connection with the terminal device. These external devices can be, for example, smartphones, tablets, configuration terminals, gateway devices, other IoT terminals, or network-side management platforms. Trigger commands can be sent via short-range or local area communication methods such as Near Field Communication (NFC), Bluetooth, Wireless Fidelity (Wi-Fi) Direct, serial port, infrared, ZigBee, or Long Range (LoRa), or via existing IP connections or SMS. This disclosure does not limit the specific method of sending trigger commands.

[0134] For example, users can configure an eSIM for a smartwatch they are paired with via a smartphone app. The smartphone sends a trigger command to the smartwatch via Bluetooth, and the smartwatch, upon receiving the command, sends configuration trigger information to a configuration server. This method facilitates configuration triggering for terminal devices without screens or input capabilities using existing external devices, improving the convenience and manageability of the configuration process.

[0135] (3) The current time is determined as the time to send the configuration trigger information based on the preset timing strategy.

[0136] As an example, the terminal device can pre-store or have a preset timing policy pre-configured by a configuration server. This preset timing policy can include a fixed information transmission time or a fixed information transmission period. For example, the preset timing policy could include the terminal device sending a configuration trigger message once a day at 2:00 AM, or sending a configuration trigger message every 24 hours.

[0137] In the eSIM configuration method provided in this disclosure, before receiving control plane messages through a non-IP data channel, the terminal device can send configuration trigger information to the configuration server in response to user operations, instructions from other devices, or preset timing policies. This trigger information includes the terminal's identity information. This allows the configuration server to distribute eSIM configuration file fragments only when the terminal actually needs configuration or when the planned configuration time arrives, avoiding blind pushes when the terminal is unreachable or does not require configuration, thus reducing invalid distributions and network resource waste. Simultaneously, the terminal's identity information enables the configuration server to accurately identify the target terminal and select the corresponding configuration file, ensuring the relevance and accuracy of the configuration. This is particularly suitable for scenarios such as low-power device periodic wake-up, user-triggered configuration, or inter-device collaborative configuration.

[0138] In some embodiments, this disclosure also provides a firmware-level conflict detection and automatic handling mechanism for multi-profile management. The terminal device can also parse the provider identifier of the eSIM profile fragment before writing it to the circular buffer. The profile identifier (PPID), version number, and default activation rules are compared with the PPID of the eSIM profile fragment in eUICCC. If it is a cross-carrier addition, it is independently written to the new application security domain (Issuer Security Domain). A, ISD A) If it's a higher version update from the same operator, it enters the Pending-Install state, and after verification, it's temporarily stored for standby switching. If the versions are the same, a hash comparison is performed; if the hashes match, the write operation is skipped to achieve idempotency. When storage space is insufficient, old eSIM configuration files in the DELETE_PENDING state are prioritized for cleanup. If still insufficient, the least recently used (LRU) policy is used to reclaim the least recently used non-default eSIM configuration file. All the above operations can be recorded in the eUICC internal security log, including timestamps, transaction identifiers (TIDs), operation types, and results, supporting remote auditing.

[0139] The foregoing description of the eSIM configuration method provided in this disclosure uses a terminal device as the execution subject. This disclosure further provides another eSIM configuration method, which can be executed by a configuration server. Figure 3 This is a flowchart illustrating another eSIM configuration method provided in an embodiment of this disclosure. Figure 3 As shown, the method may include the following steps: S201. Send control plane messages to the terminal device through the first data channel.

[0140] The first data channel is a non-network protocol IP data channel, and the control plane messages include eSIM profile fragments. Specific details regarding the first data channel and control plane messages can be found in the embodiments described above, and will not be repeated here.

[0141] In some embodiments, prior to S201 described above, the configuration server may further encrypt the control plane message or the eSIM profile fragment within the control plane message using an encryption algorithm. Correspondingly, after receiving the control plane message, the terminal device may decrypt the control plane message or the eSIM profile fragment within the control plane message using the decryption algorithm corresponding to the encryption algorithm to obtain the eSIM profile fragment.

[0142] For example, encryption algorithms can employ Vester. Shamir Adelman (Rivest) Shamir Algorithms include Adleman (RSA), Advanced Encryption Standard (AES), State Cryptography Standard 2 (SM2), and State Cryptography Standard 4 (SM4). This disclosure does not limit the specific type of encryption algorithm used.

[0143] In some embodiments, the configuration server can also dynamically adjust the size of eSIM file fragments.

[0144] For example, the configuration server can use a dynamic adaptation algorithm to adjust the load of a single control plane message within a preset byte range (such as 70 bytes to 140 bytes) based on factors such as the signal strength of the terminal device, operator restrictions, the memory usage of the terminal device, and the historical configuration success rate.

[0145] In some embodiments, the configuration server may also receive fragment size recommendation information sent by the terminal device, which is used to indicate the fragment size of the eSIM profile recommended by the terminal device.

[0146] Based on the understanding of the above embodiments, in the exemplary embodiment, the control plane message is taken as an SMS message sent by the configuration server to the terminal device. Figure 4 This is a flowchart illustrating yet another eSIM configuration method provided in an embodiment of this disclosure. Figure 4 As shown, the method may include the following steps: S301. Configure the server to determine the eSIM configuration file of the terminal device.

[0147] S302. The configuration server divides the eSIM profile into multiple eSIM profile fragments and sends the eSIM profile fragments to the terminal device via SMS messages.

[0148] S303, SMS gateway forwards SMS messages.

[0149] S304. The terminal device receives the SMS message and caches the eSIM profile fragment in the SMS message.

[0150] S305. The terminal device reassembles the eSIM configuration file based on the eSIM configuration file and performs HMAC verification in the TEE.

[0151] S306. The terminal device determines whether the HMAC verification passes.

[0152] If not, proceed to S307; if yes, proceed to S308 through S310.

[0153] S307. The terminal device logs the process and terminates.

[0154] S308: The terminal device generates an APDU write command based on the eSIM configuration file and sends it to the eUICC.

[0155] S309 and eUICC perform the write operation and return a response code.

[0156] S310: The terminal device determines whether the write was successful based on the response code.

[0157] If not, execute S311; if yes, execute S312 and S313.

[0158] S311, Terminal device recording fault.

[0159] S312. The terminal device initiates network attach to the Home Location Register (HLR).

[0160] S313. The terminal device has completed registration, and the process is over.

[0161] Based on the understanding of the above embodiments, in the exemplary embodiment, the control plane message is taken as an SMS message sent by the configuration server to the terminal device. Figure 5 This is a flowchart illustrating yet another eSIM configuration method provided in an embodiment of this disclosure. Figure 5 As shown, the method may include the following steps: S401, Receive SMS messages sent by the configuration server.

[0162] S402. Parse the SMS message using the SMS parsing engine to obtain the eSIM profile fragment from the SMS message.

[0163] S403. Write the eSIM profile fragments to the circular buffer.

[0164] S404. Determine whether all eSIM profile fragments have been received.

[0165] If not, proceed to S405; if yes, proceed to S406 through S408.

[0166] S405, awaiting more eSIM profile fragments.

[0167] S406. The eSIM profile is reassembled into an eSIM profile using the fragmentation and reassembly engine, and the eSIM profile is then subjected to CRC verification.

[0168] S407. The sender's identity is verified by the HMAC verification module running on the TEE for the eSIM configuration file fragments.

[0169] S408. Determine whether the sender's identity verification has passed.

[0170] If not, proceed to S409; if yes, proceed to S410 through S412.

[0171] S409, Output eSIM configuration file discarded alarm.

[0172] S410 generates configuration file writing instructions through the firmware-level APDU constructor.

[0173] S411 sends the configuration file writing command to the eUICC chip through the eUICC interface driver.

[0174] The S412 and eUICC chips respond to the configuration file write command and write the eSIM configuration file.

[0175] Based on the understanding of the above embodiments, in the exemplary embodiments, Figure 6 This is a flowchart illustrating yet another eSIM configuration method provided in an embodiment of this disclosure. Figure 6 As shown, the method may include the following steps: S501, The first SMS message has been received.

[0176] S502. Determine whether the eSIM profile fragment in the SMS message is the first fragment with fragment number 1.

[0177] If yes, then execute S503 and S504 followed by S506; otherwise, execute S505 followed by S506.

[0178] S503. Initialize the circular buffer.

[0179] S504. Record the number of fragments of the received eSIM profile.

[0180] S505, cached eSIM profile fragments.

[0181] S506, Continue receiving eSIM profile fragments.

[0182] S507. Write the eSIM profile fragments into the corresponding positions in the circular buffer according to the fragment sequence number.

[0183] S508: Determine whether all eSIM profile fragments have been received.

[0184] If not, execute S509; if yes, execute S514 to S516.

[0185] S509, Start the timeout timer.

[0186] S510, Determine if a timeout has occurred.

[0187] If not, execute S511; if yes, execute S512 and S513.

[0188] S511, continue waiting to receive eSIM profile fragments.

[0189] S512. Based on the total number of fragments and the fragment sequence number of the eSIM profile fragment stored in the circular buffer, determine the fragment sequence number of the unreceived eSIM profile fragment.

[0190] S513, Send a second retransmission message to the configuration server.

[0191] The second retransmission information is used to request the retransmission of unreceived eSIM profile fragments via the first data channel or the IP data channel.

[0192] S514: Reassemble the eSIM profile fragments into an eSIM profile.

[0193] S515, Perform CRC32 verification on the eSIM configuration file.

[0194] S516. Determine whether the CRC32 check passes.

[0195] If not, execute S517; if yes, execute S518.

[0196] S517. Send the first retransmission information to the configuration server.

[0197] The first retransmission information is used to request the retransmission of all eSIM profile fragments of the eSIM profile through the first data channel or the IP data channel.

[0198] S518, outputs the complete eSIM configuration file.

[0199] Based on the understanding of the above embodiments, in the exemplary embodiments, Figure 7This is a flowchart illustrating the exception handling and retransmission triggering process provided in the embodiments of this disclosure. Figure 7 As shown, the exception handling and retransmission triggering process may include the following steps: S601, Currently in an idle state.

[0200] S602, Receive eSIM profile fragments via control plane messages.

[0201] If the reception times out, execute S603 and then return to S602; if the reception times out before completion, execute S604 to S606; if the reception is complete, execute S608.

[0202] S603, Send a second retransmission message to the configuration server.

[0203] S604. Perform HMAC verification on the eSIM configuration file fragments.

[0204] S605. HMAC verification results are recorded in the log.

[0205] S606. Determine if HMAC verification has failed more than M times consecutively.

[0206] If not, return to S602; if yes, execute S607.

[0207] S607, Stop receiving control plane messages.

[0208] S608. Fragment the eSIM profile and reassemble it into an eSIM profile, and perform CRC verification on the eSIM profile.

[0209] S609. Determine whether the CRC check passes.

[0210] If yes, then end; if no, then execute S610 and return to S602.

[0211] S610, Send the first retransmission message to the configuration server.

[0212] The foregoing primarily describes the solutions provided by the embodiments of this disclosure from a methodological perspective. To achieve the above functions, each device, such as a terminal device or configuration server, includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the algorithmic steps of the examples described in the embodiments disclosed herein, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Experts may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0213] This disclosure embodiment can divide the terminal device or configuration server into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one functional module. The integrated module can be implemented in hardware or software. It should be noted that the module division in this disclosure embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the example of dividing each functional module according to each function.

[0214] In an exemplary embodiment, this disclosure provides an eSIM configuration device that can be applied to a terminal device. Figure 8 This is a schematic diagram illustrating the composition of an eSIM configuration device provided in an embodiment of this disclosure. Figure 8 The eSIM configuration device may include a receiving module 701 and a processing module 702.

[0215] The receiving module 701 is used to receive control plane messages sent by the configuration server through the first data channel; wherein, the first data channel is a non-network protocol IP data channel, and the control plane messages include fragments of the embedded user identification module eSIM configuration file; The processing module 702 is used to obtain the eSIM configuration file based on the eSIM configuration file fragment in the control plane message; and write the eSIM configuration file into the embedded universal integrated circuit card eUICC to complete the eSIM configuration.

[0216] In some embodiments, the processing module 702 is specifically configured to perform at least one of the following verification operations: sender identity verification operation, identity identifier consistency verification operation, and validity period verification operation; wherein, the sender identity verification operation includes: verifying the identity of the sender of each eSIM profile fragment based on the identity verification information of the sender of each eSIM profile fragment in each control plane message; the identity identifier consistency verification operation includes: determining whether the identity identifier of the target terminal device corresponding to each eSIM profile fragment in each control plane message is the same as the identity identifier of the terminal device itself; the validity period verification operation includes: determining whether the current time is within the validity period of each eSIM profile fragment in each control plane message; and when all eSIM profile fragments divided from the eSIM profile are received after determining based on the fragment sequence number and the total number of fragments, and at least one verification operation passes, the eSIM profile is obtained based on the eSIM profile fragment in the control plane message.

[0217] In some embodiments, the processing module 702 is specifically used to perform integrity verification on the eSIM profile based on the integrity verification information of the eSIM profile in the control plane message; if the integrity verification of the eSIM profile passes, the eSIM profile is written into the embedded universal integrated circuit card eUICC.

[0218] In some embodiments, the processing module 702 is further configured to send a first retransmission message to the configuration server if the integrity verification of the eSIM profile fails; the first retransmission message is used to request the retransmission of all eSIM profile fragments of the eSIM profile through a first data channel or an IP data channel.

[0219] In some embodiments, the processing module 702 is further configured to, within a preset time period after the eSIM profile fragment is first written into the circular buffer, if it is determined, based on the fragment sequence number corresponding to the eSIM profile fragment in the control plane message and the total number of eSIM profile fragments divided from the eSIM profile, that not all eSIM profile fragments divided from the eSIM profile have been received, then, based on the total number of fragments and the fragment sequence number of the eSIM profile fragments stored in the circular buffer, determine the fragment sequence number of the unreceived eSIM profile fragment; and send second retransmission information to the configuration server; the second retransmission information is used to request the retransmission of the unreceived eSIM profile fragment through the first data channel or the IP data channel, and the second retransmission information includes the fragment sequence number of the unreceived eSIM profile fragment.

[0220] In some embodiments, the processing module 702 is specifically used to generate a configuration file writing instruction based on the eSIM configuration file, through the underlying firmware of the terminal device's operating system or a trusted execution environment; the configuration file writing instruction includes the configuration information of the eSIM configuration file; and send the configuration file writing instruction to the eUICC through the eUICC interface driver to write the eSIM configuration file to the eUICC.

[0221] In some embodiments, the processing module 702 is further configured to send configuration trigger information to the configuration server in response to detecting a trigger event before the receiving module 701 receives the control plane message sent by the configuration server through a non-network protocol IP data channel; the trigger event includes at least one of the following: detecting a user's trigger operation, receiving a trigger instruction sent by another device, or determining the current time as the time to send the configuration trigger information based on a preset timing strategy; the configuration trigger information is used to trigger the configuration server to send the control plane message, and the configuration trigger information includes the identity information of the terminal device.

[0222] In an exemplary embodiment, this disclosure provides another eSIM configuration device that can be applied to a configuration server. Figure 9 This is a schematic diagram illustrating the composition of another eSIM configuration device provided in an embodiment of this disclosure. (See diagram below.) Figure 9 The eSIM configuration device may include a transmitting module 801.

[0223] The sending module 801 is used to send control plane messages to the terminal device through a first data channel; the first data channel is a non-network protocol IP data channel; the control plane messages include fragments of the embedded user identification module eSIM profile.

[0224] It should be noted that the above Figure 8 or Figure 9 Modules in a module can also be called units; for example, a processing module can be called a processing unit. Additionally, in... Figure 8 or Figure 9 In the embodiments shown, the names of the modules may not be the same as those shown in the figure. For example, the receiving module or the sending module may also be called the acquisition module or the communication module, etc.

[0225] Figure 8 or Figure 9 If the various modules in the present disclosure are implemented as software functional modules and sold or used as independent products, they can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this disclosure, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a mobile phone, personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this disclosure. Storage media for storing computer software products include: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0226] In an exemplary embodiment, this disclosure also provides an electronic device. Figure 10 This is a schematic diagram illustrating the composition of an electronic device provided in an embodiment of this disclosure. For example... Figure 10 As shown, the electronic device includes a processor 902, a communication interface 903, and a bus 904. As an example, the electronic device may also include a memory 901.

[0227] Processor 902 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with this disclosure. Processor 902 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with this disclosure. Processor 902 may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0228] The communication interface 903 is used to connect to other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0229] The memory 901 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0230] In one possible implementation, the memory 901 can exist independently of the processor 902. The memory 901 can be connected to the processor 902 via a bus 904 and is used to store instructions or program code. When the processor 902 calls and executes the instructions or program code stored in the memory 901, it can implement the eSIM configuration method provided in this embodiment of the disclosure.

[0231] In another possible implementation, the memory 901 can also be integrated with the processor 902.

[0232] The 904 bus can be an extended industry standard architecture (EISA) bus, etc. The 904 bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 10 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0233] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the terminal device or configuration server can be divided into different functional modules to complete all or part of the functions described above.

[0234] In exemplary embodiments, this disclosure also provides a computer-readable storage medium, which includes a non-transitory computer-readable storage medium storing computer instructions. When these computer instructions are executed on an electronic device, they cause the electronic device to perform the methods described in the above embodiments. The computer-readable storage medium can also be an external storage device of the electronic device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the electronic device. Further, the computer-readable storage medium can include both internal storage units and external storage devices of the electronic device. The computer-readable storage medium is used to store the software instructions and other programs and data required by the electronic device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0235] In an exemplary embodiment, this disclosure also provides a computer program product including computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the methods described in the above method embodiments.

[0236] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer-executable instructions. When these computer-executable instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer-executable instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer-executable instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, Bluetooth, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape) or an optical medium (e.g., DVD), etc.

[0237] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0238] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

[0239] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An eSIM provisioning method, characterized by, The method is applied to a terminal device; the method includes: The system receives control plane messages sent by the configuration server through a first data channel; wherein, the first data channel is a non-network protocol IP data channel, and the control plane messages include embedded user identification module eSIM profile fragments; Based on the eSIM profile fragment in the control plane message, obtain the eSIM profile; The eSIM configuration file is written to the embedded universal integrated circuit card eUICC to complete the eSIM configuration.

2. The method according to claim 1, characterized in that, The first data channel includes at least one of the following: Unstructured supplemental service data via the USSD channel; Card Application Toolkit Transmission Protocol CAT-TP Channel; Narrowband Internet of Things (NB-IoT) control plane message channel; Community Broadcasting Service (CBS) channel; The point-to-point short message service (SMS-PP) channel; The control plane message types include at least one of the following: USSD News; CAT-TP message; NB-IoT control plane messages; The configuration server broadcasts SMS messages; The configuration server sends an SMS message to the terminal device.

3. The method of claim 1, wherein, The control plane message also carries at least one of the following information: The fragment number corresponding to the eSIM configuration file fragment; The eSIM profile is divided into eSIM profile segments, which determine the total number of segments. eSIM profile fragment sender's authentication information; Integrity verification information for the eSIM configuration file; The identity identifier of the target terminal device corresponding to the eSIM profile fragment; eSIM profile fragment validity period.

4. The method of claim 3, wherein, The process of obtaining the eSIM profile based on the eSIM profile fragment in the control plane message includes: Perform at least one of the following verification operations: sender identity verification, identity identifier consistency verification, and validity period verification; wherein, the sender identity verification operation includes: verifying the sender's identity for each eSIM profile fragment based on the identity verification information of the sender in each control plane message; the identity identifier consistency verification operation includes: determining whether the identity identifier of the target terminal device corresponding to each eSIM profile fragment in each control plane message is the same as the identity identifier of the terminal device itself; the validity period verification operation includes: determining whether the current time is within the validity period of each eSIM profile fragment in each control plane message; If all eSIM profile fragments are received after the eSIM profile is divided based on the fragment sequence number and the total number of fragments, and all at least one verification operation passes, the eSIM profile is obtained based on the eSIM profile fragment in the control plane message.

5. The method of claim 3, wherein, The step of writing the eSIM configuration file into the embedded universal integrated circuit card eUICC includes: The integrity of the eSIM configuration file is verified based on the integrity verification information of the eSIM configuration file in the control plane message. If the integrity verification of the eSIM profile passes, the eSIM profile is written into the embedded universal integrated circuit card eUICC.

6. The method of claim 5, wherein, The method further includes: If the integrity verification of the eSIM profile fails, a first retransmission message is sent to the configuration server; the first retransmission message is used to request the retransmission of all eSIM profile fragments of the eSIM profile through the first data channel or the IP data channel.

7. The method of claim 3, wherein, The method further includes: Within a preset time period after the eSIM profile fragment is first written into the circular buffer, if it is determined that not all eSIM profile fragments divided from the eSIM profile have been received, based on the fragment sequence number corresponding to the eSIM profile fragment in the control plane message and the total number of eSIM profile fragments divided from the eSIM profile, then the fragment sequence number of the unreceived eSIM profile fragment is determined based on the total number of fragments and the fragment sequence number of the eSIM profile fragment stored in the circular buffer. Send a second retransmission message to the configuration server; the second retransmission message is used to request the retransmission of the unreceived eSIM profile fragment through the first data channel or the IP data channel, and the second retransmission message includes the fragment sequence number of the unreceived eSIM profile fragment.

8. The method of claim 1, wherein, The step of writing the eSIM configuration file into the embedded universal integrated circuit card eUICC includes: Based on the eSIM configuration file, a configuration file writing instruction is generated through the underlying firmware or trusted execution environment of the terminal device's operating system; the configuration file writing instruction includes the configuration information of the eSIM configuration file; The configuration file writing instruction is sent to the eUICC via the eUICC interface driver to write the eSIM configuration file to the eUICC.

9. The method of claim 1, wherein, Before receiving control plane messages sent by the configuration server via a non-network protocol IP data channel, the method further includes: In response to the detection of a triggering event, configuration triggering information is sent to the configuration server; the triggering event includes at least one of the following: detecting a user's triggering operation, receiving a triggering instruction sent by another device, or determining the current time as the time to send the configuration triggering information based on a preset timing strategy; the configuration triggering information is used to trigger the configuration server to send the control plane message, and the configuration triggering information includes the identity information of the terminal device.

10. An eSIM provisioning method, comprising: The method is applied to a configuration server; the method includes: Control plane messages are sent to the terminal device through a first data channel; the first data channel is a non-network protocol IP data channel; the control plane messages include fragments of the embedded user identification module eSIM profile.

11. An electronic device, comprising: include: A processor and a memory for storing instructions executable by the processor; When the processor is configured to execute the instructions, the electronic device performs the method as described in any one of claims 1 to 9 or 10.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a non-transitory computer-readable storage medium on which computer instructions are stored, which, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 9 or 10.

13. A computer program product, characterised in that, It includes computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 9 or 10.

14. An eSIM provisioning system, comprising: The system includes: terminal devices and a configuration server; The configuration server is used to send control plane messages to the terminal device through a first data channel; the first data channel is a non-network protocol IP data channel; the control plane message includes an embedded user identification module (eSIM) configuration file fragment. The terminal device is used to obtain the eSIM configuration file based on the eSIM configuration file fragment in the control plane message; and write the eSIM configuration file into the embedded universal integrated circuit card eUICC to complete the eSIM configuration.