ESIM code number configuration method and system, and medium

Abstract

The invention discloses an embedded SIM (Subscriber Identity Module) card eSIM (Embedded Subscriber Identity Module) code number configuration method, an embedded SIM card eSIM code number configuration system and a medium, and relates to the technical field of communication, the method comprises the following steps: a configuration server receives a code number configuration request from user equipment, and the code number configuration request carries user identity information and eSIM code number service qualification information; verifying a user identity and business qualification based on the code number configuration request; after the verification is passed, initiating a configuration request to an eSIM management server to obtain an activation code corresponding to the eSIM service; and sending the activation code to the user equipment, so that the user equipment completes configuration of the eSIM code number. The configuration server directionally applies for the activation code from the eSIM management server and issues the activation code to the user equipment, and the established standardized process adapts to the configuration requirements of different eSIM service scenes, simplifies the configuration link, improves the overall efficiency and reliability of eSIM code number configuration, and assists the large-scale application of the eSIM technology.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and more specifically to an eSIM number configuration method, system, and medium. Background Technology

[0002] eSIM (Embedded-Subscriber Identification Module) technology, a significant innovation in the communications field, integrates the functions of a traditional SIM card into a built-in chip within a device, enabling digital management of user identity information. Essentially, an eSIM is a dedicated chip directly soldered onto the device's motherboard, replacing the traditional pluggable physical SIM card. This allows users to remotely download and switch operator profiles, significantly improving ease of use.

[0003] Currently, eSIM number download and migration primarily rely on two technical solutions: The first is a QR code download mode based on the SM-DP+ system. After user authentication via offline or online channels, the operator's system generates an activation code in QR code form. After scanning the QR code, the device connects to the operator's SM-DP+ server to download and install the corresponding eSIM configuration file. The second is a carrier network configuration file migration solution based on migration tokens. This solution generates a migration token to bind the target configuration file, aiming to simplify the carrier network configuration file migration process between different devices without requiring modifications to the operator's backend system.

[0004] However, existing eSIM technology processes have a low degree of digitalization and rely heavily on manual operations, resulting in low operational efficiency and high costs for operators, while users face cumbersome processes and fragmented experiences. Furthermore, the migration solutions it relies on lack security, making tokens vulnerable to attack. Summary of the Invention

[0005] The main objective of this invention is to provide an eSIM number configuration method, system, and medium that addresses the problems of insufficient security, poor service adaptability, and lack of process standardization in existing eSIM number configuration processes, thereby improving the security, controllability, and efficiency of eSIM number configuration. By having a configuration server uniformly receive configuration requests carrying user identity information and eSIM service qualification information, accurate identification of the configuration initiator can be achieved, preventing invalid configuration requests from unauthorized devices or unqualified users and ensuring the secure management of eSIM number resources. Simultaneously, a dual verification process for user identity and service qualification at the outset ensures the legality and compliance of configuration requests, providing a secure upfront guarantee for subsequent activation code acquisition and number configuration. Furthermore, the configuration server directly requests activation codes from the eSIM management server and distributes them to user devices. This standardized process adapts to the configuration needs of different eSIM service scenarios, simplifies the configuration chain, improves the overall efficiency and reliability of eSIM number configuration, and facilitates the large-scale application of eSIM technology.

[0006] To achieve the above objectives, the embodiments of this application provide the following technical solutions: According to a first aspect of the embodiments of this application, an eSIM number configuration method is provided, the method comprising: The configuration server receives a code number configuration request from the user equipment, the code number configuration request carrying user identity information and eSIM code number service qualification information; The user's identity and business qualifications are verified based on the code number configuration request; After successful verification, a configuration request is sent to the eSIM management server to obtain the activation code corresponding to the eSIM service; The activation code is sent to the user equipment so that the user equipment can complete the configuration of the eSIM number.

[0007] Optionally, the verification of user identity and business qualifications based on the code number configuration request includes: Based on the user's identity information and eSIM number service qualification information, a dynamic password challenge value uniquely bound to the user device is generated and sent to the user device, so that the user device can calculate the dynamic password challenge value based on the key preset in its own security unit, generate a dynamic password response value and provide feedback. The received dynamic password response value is compared with the expected response value calculated by itself to obtain the device verification result; Based on the device verification result, the user's identity and business qualifications are verified for the code number configuration request, and the verification result is output, which includes verification passed or verification failed.

[0008] Optionally, the user equipment is an eSIM device, the eSIM number service eligibility information includes eSIM new number activation eligibility information, and the process of initiating the number configuration request includes: The eSIM device obtains its own eSIM hardware identification information; The eSIM device generates a number configuration request based on the eSIM hardware identification information, the user identity information, and the eSIM new number activation qualification information. The eSIM device establishes a communication connection with the configuration server and sends the code number configuration request to the configuration server.

[0009] Optionally, the user equipment is a companion device carrying a physical SIM card and a target eSIM device, and the eSIM number service eligibility information includes number portability eligibility information; the process of initiating the number configuration request includes: The accompanying device and the target eSIM device complete mutual trust verification based on a dynamic password mechanism; After confirming that the trust verification is successful, the accompanying device will synchronize its associated physical SIM card information to the target eSIM device. The target eSIM device generates a number configuration request based on the user identity information, the physical SIM card information of the accompanying device, the eSIM hardware identification information, and the number portability eligibility information. The target eSIM device sends the code number configuration request and trust verification result to the configuration server.

[0010] Optionally, the user equipment includes a first eSIM device and a second eSIM device, the eSIM number service eligibility information includes device transfer eligibility information, and the number configuration request initiation process includes: The first eSIM device and the second eSIM device complete mutual trust verification based on a dynamic password mechanism; After the first eSIM device confirms that the trust verification is successful, it synchronizes its own eSIM configuration information and original code number association information to the second eSIM device, and at the same time exchanges their respective eSIM hardware identification information. The first eSIM device generates a number configuration request based on the eSIM configuration information, the user identity information, the eSIM hardware identification information of the first eSIM device and the second eSIM device, and the device transfer qualification information; The first eSIM device sends the code number configuration request and the inter-device trust verification result to the configuration server.

[0011] Optionally, before initiating a configuration request to the eSIM management server, the following steps are also included: Based on the eSIM configuration information of the first eSIM device and the original number association information in the number configuration request, a request to cancel the binding relationship between the first device and the original number is sent to the eSIM management server. Receive the successful deregistration confirmation message returned by the eSIM management server; Based on the successful cancellation confirmation message, a configuration request for the second eSIM device is initiated to the eSIM management server.

[0012] Optionally, initiating a configuration request to the eSIM management server to obtain an activation code corresponding to the eSIM service includes: The verification result and the eSIM hardware identification information of the user equipment are encapsulated into the configuration request, and the configuration request is sent to the eSIM management server through an interface conforming to the eSIM standard. The eSIM management server verifies the validity of the verification result in the configuration request and the eSIM hardware identification information. After successful verification, an activation code for an eSIM configuration file uniquely bound to the target device is generated based on the eSIM hardware identification information and the service type corresponding to the code number configuration request. The activation code is sent to the configuration server through the eSIM-compliant interface.

[0013] Optionally, the activation code is sent to the user equipment to enable the user equipment to complete the configuration of the eSIM number, including: The configuration server encrypts the activation code and the eSIM hardware identification information of the user device, generates an encrypted activation code, and sends it to the user device. The user equipment verifies the encrypted activation code based on its own eSIM hardware identification information. After successful verification, it establishes a connection with the eSIM management server through the eSIM-compliant interface. The user equipment sends the encrypted activation code to the eSIM management server so that the eSIM management server can decrypt the encrypted activation code; After decryption, the eSIM management server verifies the consistency of the device based on the eSIM hardware identification information. After successful verification, an eSIM configuration file uniquely associated with the activation code is generated based on the service type corresponding to the activation code and sent to the user equipment. The user equipment receives and installs the eSIM configuration file to complete the eSIM number configuration, and then sends the configuration status information back to the configuration server.

[0014] According to a second aspect of the embodiments of this application, an eSIM number configuration system is provided, the system comprising: The message receiving module is used to configure the server to receive a code number configuration request from the user equipment. The code number configuration request carries user identity information and eSIM code number service qualification information. The verification module is used to verify the user's identity and business qualifications based on the code number configuration request; The message sending module is used to send a configuration request to the eSIM management server after successful verification in order to obtain the activation code corresponding to the eSIM service; The message sending module is also used to send the activation code to the user equipment so that the user equipment can complete the configuration of the eSIM number.

[0015] According to a third aspect of the embodiments of this application, a computer-readable storage medium is provided, on which computer-readable instructions are stored, which can be executed by a processor to implement the method described in the first aspect above.

[0016] In summary, this application provides an eSIM number configuration method, system, and medium. A configuration server receives a number configuration request from a user device, the request carrying user identity information and eSIM number service eligibility information. The user identity and service eligibility are verified based on the configuration request. Upon successful verification, a configuration request is sent to the eSIM management server to obtain an activation code corresponding to the eSIM service. The activation code is then sent to the user device, enabling the user device to complete the eSIM number configuration. By having a configuration server uniformly receive configuration requests carrying user identity information and eSIM service eligibility information, accurate identification of the configuration initiator can be achieved, preventing invalid configuration requests from unauthorized devices or unqualified users, and ensuring the secure management of eSIM number resources. Meanwhile, by conducting a dual verification process for user identity and business qualifications beforehand, the legality and compliance of configuration requests are ensured, providing a secure prerequisite for subsequent activation code acquisition and number configuration. Then, the configuration server requests activation codes from the eSIM management server and distributes them to the user's device. This standardized process not only adapts to the configuration requirements of different eSIM business scenarios but also simplifies the configuration process, improving the overall efficiency and reliability of eSIM number configuration and facilitating the large-scale application of eSIM technology. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0018] The structures, proportions, sizes, etc. illustrated in this specification are only for the purpose of assisting those skilled in the art in understanding and reading the content disclosed herein, and are not intended to limit the conditions under which the present invention can be implemented. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in the proportions, or adjustments to the size, without affecting the effects and objectives that the present invention can produce, should still fall within the scope of the technical content disclosed in the present invention.

[0019] Figure 1 A flowchart of an eSIM number configuration method provided in an embodiment of this application; Figure 2 This is a schematic diagram illustrating the process of porting a SIM card to an eSIM as provided in an embodiment of this application. Figure 3 This is a schematic diagram illustrating the download and transfer of a new eSIM number as provided in an embodiment of this application. Figure 4 The business timing flowchart provided for the embodiments of this application; Figure 5 A schematic diagram of an eSIM number configuration system provided in this application embodiment; Figure 6 This paper shows a structural diagram of an electronic device provided in an embodiment of this application; Figure 7 A diagram of a computer-readable storage medium provided in an embodiment of this application is shown.

[0020] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

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

[0022] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0023] Furthermore, in this invention, descriptions involving "first," "second," etc., are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0024] In this invention, unless otherwise explicitly specified and limited, the terms "connection," "fixed," etc., should be interpreted broadly. For example, "fixed" can mean a fixed connection, a detachable connection, or an integral part; it can mean a mechanical connection or an electrical connection; it can mean a direct connection or an indirect connection through an intermediate medium; it can mean the internal communication of two components or the interaction between two components, unless otherwise explicitly limited. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0025] Furthermore, the technical solutions of the various embodiments of the present invention can be combined with each other, but only if they are feasible for those skilled in the art. If the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such combination of technical solutions does not exist and is not within the scope of protection claimed by the present invention.

[0026] Figure 1 This application illustrates an eSIM number configuration method provided by an embodiment of the present application. The method includes: Step 101: The configuration server receives a code number configuration request from the user equipment, the code number configuration request carrying user identity information and eSIM code number service qualification information; Step 102: Verify the user's identity and business qualifications based on the code number configuration request; Step 103: After successful verification, a configuration request is sent to the eSIM management server to obtain the activation code corresponding to the eSIM service; Step 104: Send the activation code to the user equipment so that the user equipment can complete the configuration of the eSIM number.

[0027] By configuring the server as a unified request receiving and processing hub, connecting user devices and the eSIM management server, centralized control over eSIM number configuration requests can be achieved. Number configuration requests initiated by user devices must carry user identity information and eSIM number service qualification information, filtering invalid or illegal requests at the source, preventing unrelated devices from occupying eSIM number resources, and ensuring the compliance of eSIM number configuration. The pre-emptive user identity and service qualification verification step is a crucial step in ensuring the security of eSIM number configuration. It allows for dual verification of the requesting user's true identity and service application qualifications, ensuring that only users with legitimate identities and corresponding service qualifications can enter the subsequent activation code application process, effectively preventing security risks such as identity theft and unauthorized configuration. After successful verification, the configuration server sends an activation code configuration request to the eSIM management server, enabling precise binding of the activation code to the user device and service type, preventing activation code abuse. The unified distribution of activation codes and the user device's self-configuration process simplify the eSIM number activation operation, adapt to the configuration needs of different types of user devices, and promote the large-scale application of eSIM technology in multi-terminal scenarios.

[0028] In one possible implementation, step 102, verifying the user's identity and business eligibility based on the code number configuration request, includes: Based on the user's identity information and eSIM number service qualification information, a dynamic password challenge value uniquely bound to the user device is generated and sent to the user device. This allows the user device to calculate the dynamic password challenge value based on a pre-set key within its own security unit, generate a dynamic password response value, and provide feedback. The received dynamic password response value is compared with the expected response value calculated by the user device to obtain a device verification result. Based on the device verification result, the user's identity and service qualification are verified for the number configuration request, and a verification result is output, which includes verification success or verification failure.

[0029] This implementation further enhances the security and accuracy of the eSIM number configuration request verification process, addressing the issues of disconnect between device and user identity verification in traditional methods, which are susceptible to unauthorized tampering or impersonation. It constructs a dual verification barrier for both the device and the user. Specifically, the verification process does not directly audit user identity and service eligibility information. Instead, it first generates a dynamic password challenge value uniquely bound to the user device based on this information. A pre-set key within the user device's security unit is used to calculate the response to the challenge value. The device-level identity verification is achieved by comparing the response value with the expected value, ensuring that the requesting device is a registered and legitimate eSIM device, thus blocking configuration requests from unauthorized devices at the hardware level. After obtaining a valid device verification result, a second audit is conducted to verify the legitimacy of the user's identity information and the validity of the eSIM number service eligibility information. Only when both device verification and user eligibility audits pass is a verification pass result output. This layered verification design ensures both the authenticity of the device identity and the compliance of the user's service application, effectively avoiding security risks caused by the failure of a single verification step.

[0030] In one possible implementation, in step 101, the user equipment is an eSIM device, the eSIM number service qualification information includes eSIM new number activation qualification information, and the process of initiating the number configuration request includes: the eSIM device obtaining its own eSIM hardware identification information; the eSIM device generating a number configuration request based on the eSIM hardware identification information, the user identity information, and the eSIM new number activation qualification information; the eSIM device establishing a communication connection with the configuration server and sending the number configuration request to the configuration server.

[0031] This implementation method is adapted to the scenario of activating a new number for a single eSIM device. By clarifying the generation and sending logic of the number configuration request in this scenario, it solves the problems of unclear identity identification and incomplete request information when a single device initiates a new eSIM number configuration, ensuring the accuracy and security of the new number activation request and improving the efficiency of eSIM number configuration in a single-device scenario. Specifically, for the requirement of activating a new number for a single eSIM device, this implementation method first requires the eSIM device to actively collect its own eSIM hardware identification information. This information is the unique identity credential of the eSIM device, which can uniquely identify the main body of the device's eSIM chip. Including it in the number configuration request can achieve precise binding between the request and the device, avoid confusion of configuration requests from different devices, and also provide a basis for device identity verification in the subsequent verification process.

[0032] Based on this, the eSIM device integrates user identity information, its own eSIM hardware identification information, and eSIM new number activation eligibility information to generate a configuration request, ensuring the integrity of the request information: user identity information is used to confirm the legitimacy of the user initiating the application; eSIM new number activation eligibility information, such as whether the user meets the operator's new number application conditions and whether the device is compatible with the target operator's eSIM service, is used to predict the feasibility of the service application. The combination of these three elements allows the configuration server to quickly perform subsequent verification work after receiving the request, reducing the processing cost of invalid requests. Finally, the request is sent through a dedicated communication connection established between the eSIM device and the configuration server, further ensuring the security of the request transmission process and preventing the request information from being tampered with or stolen during transmission.

[0033] In one possible implementation, in step 101, the user equipment comprises a companion device carrying a physical SIM card and a target eSIM device, and the eSIM number service qualification information includes number portability qualification information; the process of initiating the number configuration request includes: the companion device and the target eSIM device completing mutual trust verification based on a dynamic password mechanism; after confirming that the trust verification is successful, the companion device synchronizes its associated physical SIM card information to the target eSIM device; the target eSIM device generates a number configuration request based on the user identity information, the physical SIM card information of the companion device, the eSIM hardware identification information, and the number portability qualification information; and the target eSIM device sends the number configuration request and the trust verification success result to the configuration server.

[0034] This implementation method is adapted to the business scenario of porting a physical SIM card to an eSIM device, solving problems such as lack of trust between devices, insecure information synchronization, and incomplete configuration request information during cross-device number portability, and achieving secure and efficient migration of physical SIM numbers to eSIM devices. Specifically, considering the characteristic of number portability requiring the transmission of sensitive number information between the accompanying device and the target eSIM device, this implementation method first completes two-way trust verification between the two devices through a dynamic password mechanism, ensuring that the information synchronization target is a legitimate device, and avoiding the risk of number information being stolen by unauthorized devices from the source. Only after the trust verification is successful will the accompanying device synchronize its associated physical SIM card information to the target eSIM device, ensuring the security of sensitive number data transmission.

[0035] Based on this, the target eSIM device integrates user identity information, synchronously acquired physical SIM card information, its own eSIM hardware identification information, and number portability eligibility information to generate a configuration request. Simultaneously, it sends the trust verification result between devices to the configuration server. This ensures the completeness of the configuration request information. User identity information is used to confirm the legitimacy of the user entity, physical SIM card information is used to associate with the original number resource, eSIM hardware identification information is used to bind the target device, and number portability eligibility information is used to verify business compliance. Furthermore, it provides the configuration server with pre-existing credentials for inter-device trust, reducing the server's secondary verification costs and thus improving the overall efficiency of eSIM number configuration in number portability scenarios.

[0036] In one possible implementation, in step 101, the user equipment includes a first eSIM device and a second eSIM device, the eSIM number service qualification information includes device transfer qualification information, and the number configuration request initiation process includes: the first eSIM device and the second eSIM device completing mutual trust verification based on a dynamic password mechanism; after confirming that the trust verification is successful, the first eSIM device synchronizes its own eSIM configuration information and original number association information to the second eSIM device, and at the same time exchanges their respective eSIM hardware identification information; the first eSIM device generates a number configuration request based on the eSIM configuration information, the user identity information, the eSIM hardware identification information of the first eSIM device and the second eSIM device, and the device transfer qualification information; the first eSIM device sends the number configuration request and the device trust verification success result to the configuration server.

[0037] This implementation method is adapted to eSIM number transfer scenarios across devices, addressing issues such as insufficient device trust, incomplete information synchronization, and loose binding of configuration requests and dual device identities during number migration between multiple eSIM devices. It achieves secure and accurate eSIM number migration between different devices. Specifically, for the requirement to transfer eSIM numbers from the original device to a new device, this implementation method first requires the first and second eSIM devices to complete two-way trust verification based on a dynamic password mechanism. This ensures that both devices involved in the number transfer are legitimate and registered, preventing the number information from being intercepted or stolen by unauthorized devices. After successful trust verification, the first eSIM device synchronizes its eSIM configuration information and original number association information to the second eSIM device, while simultaneously exchanging eSIM hardware identification information. This ensures complete data transmission required for number migration and achieves dual device identity binding through hardware identification exchange, providing accurate device identity information for subsequent number configuration.

[0038] Based on this, the first eSIM device integrates its own eSIM configuration information, user identity information, eSIM hardware identification information of both devices, and device transfer eligibility information to generate a configuration request, and sends the inter-device trust verification result to the configuration server along with the request. This not only ensures the comprehensiveness of the configuration request information—using the dual device hardware identification to identify the entities transferring the number out and in, the device transfer eligibility information to verify business compliance, and the user identity information to confirm number ownership—but also reduces the verification steps of the configuration server by including the inter-device trust verification result, thus improving the overall efficiency of the cross-device number transfer process.

[0039] In one possible implementation, before initiating a configuration request to the eSIM management server in step 101, the method further includes: sending a request to the eSIM management server to cancel the binding relationship between the first device and the original number based on the eSIM configuration information and original number association information of the first eSIM device in the number configuration request; receiving a cancellation success confirmation message returned by the eSIM management server; and initiating a configuration request for the second eSIM device to the eSIM management server based on the cancellation success confirmation message.

[0040] This implementation improves the entire process logic of eSIM number transfer across devices, resolving issues such as multiple devices using the same number and configuration conflicts caused by the failure to promptly unbind the original device from the first eSIM device to the second eSIM device during the transfer process. It ensures the uniqueness and security of the number transfer, guaranteeing that the new device can successfully complete the number configuration. Specifically, in the eSIM number transfer scenario, the binding relationship between the original number and the first eSIM device is a critical prerequisite affecting the transfer process. If this binding relationship is not broken, directly sending new configuration information to the second eSIM device will result in the same number being associated with two devices simultaneously, causing problems such as number usage conflicts and data transmission chaos.

[0041] Therefore, this implementation adds a step to cancel the original binding relationship before initiating a configuration request for the second eSIM device to the eSIM management server. By extracting the eSIM configuration information of the first eSIM device and the original number association information from the number configuration request, a request to cancel the binding relationship between the first device and the original number is sent to the eSIM management server, accurately locating the entity that needs to be unbound. Only after receiving and confirming the successful cancellation confirmation message returned by the eSIM management server is the configuration request process for the second eSIM device initiated. This ensures the complete removal of the original binding relationship, avoiding duplicate occupation of number resources, and clears obstacles for establishing a new binding relationship between the second eSIM device and the number. This creates a complete closed loop for the cross-device number transfer process: "cancel old binding—confirm cancellation—establish new binding," improving the standardization and reliability of number transfer.

[0042] In one possible implementation, in step 103, initiating a configuration request to the eSIM management server to obtain an activation code corresponding to the eSIM service includes: encapsulating the verification result and the eSIM hardware identification information of the user device into the configuration request, and sending the configuration request to the eSIM management server through an interface conforming to the eSIM standard; the eSIM management server verifies the validity of the verification result and the eSIM hardware identification information in the configuration request; after successful verification, based on the eSIM hardware identification information and the service type corresponding to the code number configuration request, it generates an activation code for an eSIM configuration file uniquely bound to the target device; and sends the activation code to the configuration server through the interface conforming to the eSIM standard.

[0043] This implementation method standardizes the application, generation, and transmission process of eSIM activation codes, resolving issues such as unclear activation code generation criteria, insecure transmission, and inaccurate device or service compatibility. It ensures the uniqueness, security, and specific compatibility of activation codes, building a robust security defense for subsequent eSIM number configuration on user devices. Specifically, in the activation code application stage, this implementation method clarifies that the configuration request must encapsulate the verification result from the configuration server and the user device's eSIM hardware identification information, providing a basis for the eSIM management server's verification work. The verification result proves the legitimacy of the user device and user qualifications, and the eSIM hardware identification information accurately locates the target device, preventing the issuance of activation codes to unauthorized devices or unqualified users. Simultaneously, transmitting configuration requests through an interface compliant with eSIM standards ensures the standardization and security of request data during transmission, reducing the risk of data tampering and interception.

[0044] During the activation code generation process, the eSIM management server first verifies the validity of the verification result and eSIM hardware identification information in the configuration request, further filtering invalid requests to ensure that the subsequently generated activation codes correspond to legitimate entities. After successful verification, an activation code is generated based on the eSIM hardware identification information and the service type corresponding to the number configuration request (e.g., new number activation, number portability, cross-device transfer). This activation code is uniquely bound to the target device, achieving a precise association between "device—service—activation code." This prevents the activation code from being misused or misappropriated to other devices / service scenarios and ensures that the activation code is compatible with the configuration requirements of the target device. Finally, the activation code is still transmitted back to the configuration server through an eSIM-compliant interface, forming a standardized transmission closed loop of "gateway request—management server generation—gateway reception." This ensures the security and traceability of activation code transmission, laying a reliable foundation for the configuration server to subsequently issue activation codes to user devices and advance the number configuration process.

[0045] In one possible implementation, step 104, sending the activation code to the user equipment to enable the user equipment to complete the eSIM number configuration, includes: the configuration server encrypting the activation code based on the user equipment's eSIM hardware identification information to generate an encrypted activation code, and sending it to the user equipment; the user equipment verifying the encrypted activation code based on its own eSIM hardware identification information, and establishing a connection with the eSIM management server through the eSIM standard-compliant interface after successful verification; the user equipment sending the encrypted activation code to the eSIM management server so that the eSIM management server decrypts the encrypted activation code; after decryption, the eSIM management server verifying the device's consistency based on the eSIM hardware identification information; after successful verification, generating an eSIM configuration file uniquely associated with the activation code based on the service type corresponding to the activation code, and sending it to the user equipment; the user equipment receiving and installing the eSIM configuration file to complete the eSIM number configuration, and feeding back configuration status information to the configuration server.

[0046] This implementation method perfects the final step in eSIM number configuration, addressing issues such as the vulnerability of activation codes to theft and tampering during distribution, and mismatches between configuration files and target devices. It constructs a secure closed loop of "activation code encryption - device verification - consistency verification - configuration activation," ensuring that user devices can accurately and securely complete eSIM number configuration. Specifically, before distributing the activation code, the configuration server encrypts the activation code and the user device's eSIM hardware identification information to generate a unique encrypted activation code. This prevents the activation code from being illegally intercepted or stolen during transmission and also pre-binds the activation code to the target device. After receiving the encrypted activation code, the user device first performs local verification based on its own eSIM hardware identification information, filtering out activation codes that do not match, reducing invalid subsequent operations, and improving configuration efficiency.

[0047] After successful verification, the user device establishes a connection with the eSIM management server through an eSIM-compliant interface and submits an encrypted activation code. The eSIM management server decrypts the code and further verifies its consistency with the device's eSIM hardware identification information. This dual verification ensures that only authorized devices can obtain the configuration file, preventing unauthorized configuration by unauthorized devices from the outset. Subsequently, the eSIM management server generates and distributes a uniquely associated eSIM configuration file based on the service type corresponding to the activation code, ensuring that the configuration file accurately matches the user's requested service scenario. Finally, the user device receives and installs the configuration file to complete the eSIM number configuration and simultaneously reports the configuration status information to the configuration server, achieving traceable management throughout the entire process. This series of progressive steps not only ensures the security of eSIM number configuration but also improves the standardization and accuracy of the configuration process.

[0048] The eSIM number configuration method provided in the embodiments of this application will be described in detail below with reference to several accompanying drawings.

[0049] Figure 2 The schematic diagram illustrating the SIM card number portability to eSIM process provided in this application embodiment demonstrates the technical process by which a user transfers the number of their existing physical SIM card (i.e., number portability) to a new eSIM device (such as a smartwatch or other wearable device). Specifically, it includes the following steps: Step 1: Bluetooth pairing and trust verification between devices; Consumers first operate the accompanying device corresponding to the physical SIM card (such as a mobile phone with a physical SIM card installed) to establish a Bluetooth connection with the target eSIM device (such as a wearable device that supports eSIM) to complete pairing. During the pairing process, the two devices complete two-way trust verification based on the Dynamic Password (OTP) mechanism: the accompanying device generates an OTP challenge value and sends it to the target eSIM device, the target eSIM device calculates the response value using a pre-set key in its own security unit and sends it back, and after both parties compare the response values ​​and find that they match, the trust binding between the devices is completed, and the target eSIM device synchronously obtains the basic information of the accompanying device.

[0050] Step 2: Initiate qualification check and information submission to the ODSA gateway; Step 2-1: After completing the trust verification, the target eSIM device initiates a number configuration request to the ODSA gateway (i.e., the configuration server) through the ODSA client. The request carries the user's identity information, the physical SIM card information of the accompanying device (including the original number and operator identifier), the eSIM hardware identifier information of the target eSIM device, and the number portability qualification information.

[0051] Step 2-2: After receiving the request, the ODSA gateway verifies the legitimacy of the user's identity and eligibility to subscribe to the number portability service. At the same time, it collects the subscription information of the physical SIM card of the accompanying device, confirms that the card is currently in normal status and meets the conditions for number portability, and outputs the verification result.

[0052] Step 3: The ODSA gateway requests an activation code from the SM-DP+ system; Step 3-1: After the qualification check is passed, the ODSA gateway calls the service capabilities of its connected SM-DP+ system (i.e., eSIM management server) and initiates a configuration request through an eSIM-compliant interface (such as the GSMA standard ES2+ interface): The request encapsulates the device verification result and the eSIM hardware identification information of the target eSIM device.

[0053] Step 3-2: After the SM-DP+ system verifies the validity of the request information, it generates an eSIM profile activation code uniquely bound to the target eSIM device based on the hardware identification information of the target eSIM device and the service type of number portability. The activation code is then sent back to the ODSA gateway via the ES2+ interface. The ODSA gateway further encrypts and binds the activation code with the hardware identification information of the target eSIM device, generates an encrypted activation code, and sends it to the target eSIM device.

[0054] Step 4: The target eSIM device downloads and installs the eSIM configuration file; Step 4-1: After receiving the encrypted activation code, the target eSIM device completes local verification based on its own eSIM hardware identification information. After successful verification, it establishes a secure connection with the SM-DP+ system through the GSMA-compliant ES9+ interface and submits the encrypted activation code.

[0055] Step 4-2: After decrypting the encrypted activation code, the SM-DP+ system verifies the consistency between the activation code and the target eSIM device's hardware identifier. Upon successful verification, it generates an eSIM configuration file (i.e., a Profile number) uniquely associated with the activation code and sends it to the target eSIM device via the ES9+ interface. The target eSIM device receives and installs the configuration file, completing the eSIM number portability configuration. Simultaneously, it sends a status update to the ODSA gateway, indicating that the configuration is complete. The entire process then ends.

[0056] Figure 3 This is a schematic diagram illustrating the download and transfer of a new eSIM number as provided in this embodiment of the application. This embodiment covers two service scenarios: "downloading a new eSIM number" and "fast transfer of an eSIM number," specifically including: I. eSIM New Number Download Process This scenario addresses the need to activate a new number on a single eSIM device. The specific steps are as follows: Step 1: Device Information Collection When a consumer operates the target eSIM device (such as a mobile phone or smart terminal), they actively collect their own eSIM hardware identification information as the device's unique identity credential.

[0057] Step 2: Eligibility Check and Request Submission The target eSIM device initiates a number configuration request to the ODSA gateway (i.e., the configuration server) via the ODSA client. The request includes the user's identity information, the device's eSIM hardware identification information, and eSIM new number activation eligibility information. Upon receiving the request, the ODSA gateway verifies the user's identity and eligibility for the new number activation, collects the device's basic information, and checks its current subscription status. Once it confirms that the new number activation conditions are met, it outputs a verification success result.

[0058] Step 3: After the activation code application and issuance qualification check is passed, the ODSA gateway invokes the service capabilities of the SM-DP+ system (i.e., the eSIM management server) and initiates a configuration request through the GSMA standard ES2+ interface. The request encapsulates the verification result and the device's eSIM hardware identification information. After verifying the validity of the information, the SM-DP+ system generates a uniquely bound activation code based on the service type activated by the new code number and the device hardware identification, and sends it back to the ODSA gateway through the ES2+ interface. The ODSA gateway then encrypts and binds the activation code with the device hardware identification before issuing it to the target eSIM device.

[0059] Step 4: Profile Number Download and Configuration. After receiving the encrypted activation code, the target eSIM device completes local verification using its own eSIM hardware identifier. Upon successful verification, it establishes a secure connection with the SM-DP+ system via the ES9+ interface and submits the encrypted activation code. The SM-DP+ system decrypts the code and verifies its consistency with the device. Upon successful verification, it generates the corresponding eSIM configuration file (Profile number) and sends it to the device via the ES9+ interface. The device receives and installs the configuration file, completing the new eSIM activation. Simultaneously, it reports the configuration completion status to the ODSA gateway, and the process ends.

[0060] II. eSIM Number Fast Transfer Process This scenario addresses the need to migrate an eSIM number from an old device to a new device. The specific steps are as follows: Step 1: Secure Connection and Trust Verification between Devices. The consumer operates the old eSIM device to collect its own eSIM configuration information, original number association information, and eSIM hardware identifier; at the same time, a secure connection is established with the new eSIM device via Bluetooth / WiFi, and two-way trust verification is completed based on the OTP mechanism (the old device generates a challenge value, the new device calculates the response value through the secure unit key, and the trust binding is completed after the two are compared and matched), and the eSIM hardware identifier information of the two devices is exchanged.

[0061] Step 2: Eligibility Check and Request Submission. The old eSIM device initiates a number configuration request to the ODSA gateway via the ODSA client. The request includes user identity information, eSIM hardware identification information of both the old and new devices, eSIM configuration information of the old device, original number association information, and number transfer eligibility information. The ODSA gateway verifies the user's identity and number transfer subscription eligibility, checks the old device's subscription status, and outputs a verification success result after confirming that the transfer conditions are met.

[0062] Step 3: After the old device binding relationship is cancelled and the activation code application eligibility check is passed, the ODSA gateway sends a request to the SM-DP+ system to cancel the binding relationship between the old eSIM device and the original number. Upon receiving a confirmation message from the SM-DP+ system confirming successful cancellation, a new configuration request is initiated via the ES2+ interface. This request encapsulates the verification result and the new device's eSIM hardware identifier information. The SM-DP+ system generates an activation code based on the number transfer service type and the new device's hardware identifier, and sends it back to the ODSA gateway via the ES2+ interface. The ODSA gateway encrypts the activation code and synchronizes it to the new eSIM device.

[0063] Step 4: New Device Profile Number Download and Configuration. After receiving the encrypted activation code, the new eSIM device verifies its eSIM hardware identifier, then establishes a connection with the SM-DP+ system via the ES9+ interface and submits the activation code. The SM-DP+ system decrypts the code and verifies its consistency with the new device. Upon successful verification, it generates an eSIM configuration file associated with the original number and sends it to the new device via the ES9+ interface. The new device installs the configuration file, completes the number transfer, and simultaneously reports the configuration completion status to the ODSA gateway, ending the process.

[0064] Figure 4 This diagram illustrates the entire service timeline of an eSIM number, from resource preparation to activation. The diagram clarifies the collaborative interactions between the Operator, eSIM Management Server (SM-DP+), Service Gateway (ODSA), and User Equipment (UAE) to achieve automated number configuration. Specifically, it includes the following steps: Step 1: Operator prepares number resources: First, the operator prepares the corresponding eSIM number resource pool in advance according to the card functions and service requirements of the eSIM service, so as to provide basic support for the subsequent number allocation and order placement process.

[0065] Step 2: SM-DP+ system receives number orders: The operator synchronizes the prepared number information to the SM-DP+ system, which then completes the order creation for this batch of numbers, realizing the association and binding of number resources with the eSIM profile generation system.

[0066] Step 3: User completes identity authentication and qualification check: The user operates the target eSIM device (supports single device or multi-device scenarios) and initiates an identity authentication and qualification check request through the function entry in the device: submitting their own identity information, the device's eSIM hardware identification information, and the corresponding eSIM service subscription qualification information (such as new number activation, package upgrade, etc.).

[0067] Step 4: ODSA Gateway performs identity and qualification verification: After receiving the user's authentication request, the ODSA gateway verifies the legitimacy of the user's identity based on the user identity authentication mechanism preset by the Operator; at the same time, it verifies the eSIM number application eligibility of the device, and outputs the verification pass result after confirming that both the user and the device meet the service application conditions.

[0068] Step 5: User completes package and number selection: After identity and qualification verification is passed, the user completes the purchase of eSIM service package on the device, selects the target number from the available number resources, and confirms the service application information.

[0069] Step 6: Millisecond-level automatic order placement and activation code retrieval: After the user confirms the purchase, the ODSA client in the device sends an activation code request to the ODSA gateway; the ODSA gateway simultaneously sends a millisecond-level automatic order placement request to the SM-DP+ system. Based on the user's selected package, code number, and the device's eSIM hardware identification information, the SM-DP+ system generates an activation code uniquely bound to the device (which can be carried in the form of a QR code, etc.), and returns the QR code to the ODSA gateway, which then pushes it to the user's device.

[0070] In the case of a multi-device transfer scenario, the two-way trust verification between the old and new devices must be completed through the OTP mechanism first. After confirming the trust relationship, the activation code is then sent to the target device.

[0071] Step 7: Device parses activation code and prepares configuration: After receiving the QR code corresponding to the activation code, the user device automatically parses the activation code information in the QR code, completes the local verification of the activation code and its own eSIM hardware identifier, and prepares to initiate the download request of the eSIM configuration file after the verification is successful.

[0072] Step 8: Download Profile Code via ES9+ Interface: The device establishes a secure connection with the SM-DP+ system via the GSMA-compliant ES9+ interface and submits the parsed activation code; the SM-DP+ system verifies the validity of the activation code and its consistency with the device. After successful verification, it generates the corresponding eSIM configuration file (Profile Code) and sends the configuration file to the user device via the ES9+ interface.

[0073] Step 9: User completes eSIM activation and local operation: After the user device receives the Profile number, it automatically completes the installation of the configuration file and displays a successful installation status message on the device interface; the user can complete the eSIM number activation operation based on the device's local Profile management function.

[0074] Step 10: Device reports Profile management notification: After the device completes eSIM activation, it automatically reports the local Profile management operation notification to the SM-DP+ system, synchronizing information such as activation progress and configuration status to the SM-DP+ system, realizing full-process status traceability, and the entire business process ends here.

[0075] In summary, the technical solution of this application addresses the following problems existing in the prior art from three dimensions: operator, user experience, and security. 1. For operators, the automated connection between the ODSA gateway and the SM-DP+ system (such as millisecond-level order placement and automatic activation code generation via the ES2+ interface) replaces the manual query and offline distribution process, realizing a fully digital closed loop for eSIM number configuration, improving operational efficiency and reducing labor costs. At the same time, the standardized verification mechanism based on user identity information and device hardware identification replaces the highly subjective manual identity verification, unifies the review standards, and avoids deviations from manual operations.

[0076] 2. For users, the entire process of identity authentication, activation code parsing, and profile download is automatically completed on the device (such as Bluetooth pairing + OTP trust verification, and automatic download via ES9+ interface), eliminating the need for offline verification and simplifying the activation process. At the same time, based on the eSIM standard interface (ES2+, ES9+) and a unified ODSA client process, the operation interface and process of different device manufacturers are standardized, eliminating the problem of fragmented experience. The process of canceling the old device binding relationship and binding the new device activation code when transferring between devices also simplifies the configuration file migration steps.

[0077] 3. In terms of security, the activation code is encrypted and bound to the device hardware identifier, and OTP two-way trust verification replaces the simple migration token, avoiding the risk of token transmission being attacked. At the same time, a step to cancel the binding relationship between the old device and the original code number is added in the cross-device transfer process, and the new device configuration request is only initiated after receiving confirmation of successful cancellation, which completely solves the problem of duplicate numbers and eliminates the security risk of the old and new devices being usable at the same time.

[0078] In summary, this application provides an eSIM number configuration method. A configuration server receives a number configuration request from a user device, the request carrying user identity information and eSIM number service eligibility information. The user identity and service eligibility are verified based on the configuration request. Upon successful verification, a configuration request is sent to the eSIM management server to obtain an activation code corresponding to the eSIM service. The activation code is then sent to the user device, enabling the user device to complete the eSIM number configuration. By having the configuration server uniformly receive configuration requests carrying user identity information and eSIM service eligibility information, accurate identification of the configuration initiator can be achieved, preventing invalid configuration requests from unauthorized devices or unqualified users, and ensuring the secure management of eSIM number resources. Meanwhile, by conducting a dual verification process for user identity and business qualifications beforehand, the legality and compliance of configuration requests are ensured, providing a secure prerequisite for subsequent activation code acquisition and number configuration. Then, the configuration server requests activation codes from the eSIM management server and distributes them to the user's device. This standardized process not only adapts to the configuration requirements of different eSIM business scenarios but also simplifies the configuration process, improving the overall efficiency and reliability of eSIM number configuration and facilitating the large-scale application of eSIM technology.

[0079] Based on the same technical concept, embodiments of this application also provide an eSIM number configuration system, such as... Figure 5 As shown, the system includes: The message receiving module 501 is used to configure the server to receive a code number configuration request from the user equipment, wherein the code number configuration request carries user identity information and eSIM code number service qualification information. Verification module 502 is used to verify the user's identity and business qualifications based on the code number configuration request; The message sending module 503 is used to send a configuration request to the eSIM management server after successful verification in order to obtain the activation code corresponding to the eSIM service; The message sending module 503 is further configured to send the activation code to the user equipment so that the user equipment can complete the configuration of the eSIM number.

[0080] This application also provides an electronic device corresponding to the method provided in the foregoing embodiments. Please refer to... Figure 6The diagram illustrates an electronic device provided by some embodiments of this application. The electronic device 20 may include: a processor 200, a memory 201, a bus 202, and a communication interface 203, wherein the processor 200, the communication interface 203, and the memory 201 are connected via the bus 202; the memory 201 stores a computer program that can run on the processor 200, and when the processor 200 runs the computer program, it executes the method provided by any of the foregoing embodiments of this application.

[0081] The memory 201 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one physical port (which can be wired or wireless), such as the Internet, wide area network, local area network, or metropolitan area network.

[0082] Bus 202 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 201 is used to store programs. After receiving an execution instruction, the processor 200 executes the program. The method disclosed in any of the foregoing embodiments of this application can be applied to the processor 200, or implemented by the processor 200.

[0083] The processor 200 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 200 or by instructions in software form. The processor 200 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 201. The processor 200 reads the information in memory 201 and, in conjunction with its hardware, completes the steps of the above method.

[0084] The electronic devices and methods provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods they employ, operate, or implement.

[0085] This application also provides a computer-readable storage medium corresponding to the method provided in the foregoing embodiments. Please refer to... Figure 7 The computer-readable storage medium shown is an optical disc 30, on which a computer program (i.e., a program product) is stored, which, when run by a processor, executes the methods provided in any of the foregoing embodiments.

[0086] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0087] The computer-readable storage medium provided in the above embodiments of this application and the method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0088] It should be noted that the above embodiments are illustrative of this application and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. This application can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.

[0089] The above description is merely a preferred embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art 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.

[0090] The above description is only a preferred embodiment of the present invention and does not limit the patent scope of the present invention. All equivalent structural transformations made under the concept of the present invention using the contents of the present invention specification and drawings, or direct / indirect applications in other related technical fields, are included within the patent protection scope of the present invention.

Claims

1. An eSIM number configuration method, characterized by, The method includes: The configuration server receives a code number configuration request from the user equipment, the code number configuration request carrying user identity information and eSIM code number service qualification information; The user's identity and business qualifications are verified based on the code number configuration request; After successful verification, a configuration request is sent to the eSIM management server to obtain the activation code corresponding to the eSIM service; The activation code is sent to the user equipment so that the user equipment can complete the configuration of the eSIM number.

2. The method of claim 1, wherein, The verification of user identity and business qualifications based on the code number configuration request includes: Based on the user's identity information and eSIM number service qualification information, a dynamic password challenge value uniquely bound to the user device is generated and sent to the user device, so that the user device can calculate the dynamic password challenge value based on the key preset in its own security unit, generate a dynamic password response value and provide feedback. The received dynamic password response value is compared with the expected response value calculated by itself to obtain the device verification result; Based on the device verification result, the user's identity and business qualifications are verified for the code number configuration request, and the verification result is output, which includes verification passed or verification failed.

3. The method of claim 2, wherein, The user equipment is an eSIM device, and the eSIM number service eligibility information includes eSIM new number activation eligibility information. The process of initiating the number configuration request includes: The eSIM device obtains its own eSIM hardware identification information; The eSIM device generates a number configuration request based on the eSIM hardware identification information, the user identity information, and the eSIM new number activation qualification information. The eSIM device establishes a communication connection with the configuration server and sends the code number configuration request to the configuration server.

4. The method of claim 2, wherein, The user equipment includes a companion device carrying a physical SIM card and a target eSIM device; the eSIM number service eligibility information includes number portability eligibility information; the process of initiating the number configuration request includes: The accompanying device and the target eSIM device complete mutual trust verification based on a dynamic password mechanism; After confirming that the trust verification is successful, the accompanying device will synchronize its associated physical SIM card information to the target eSIM device. The target eSIM device generates a number configuration request based on the user identity information, the physical SIM card information of the accompanying device, the eSIM hardware identification information, and the number portability eligibility information. The target eSIM device sends the code number configuration request and trust verification result to the configuration server.

5. The method of claim 2, wherein, The user equipment includes a first eSIM device and a second eSIM device, the eSIM number service eligibility information includes device transfer eligibility information, and the number configuration request initiation process includes: The first eSIM device and the second eSIM device complete mutual trust verification based on a dynamic password mechanism; After the first eSIM device confirms that the trust verification is successful, it synchronizes its own eSIM configuration information and original code number association information to the second eSIM device, and at the same time exchanges their respective eSIM hardware identification information. The first eSIM device generates a number configuration request based on the eSIM configuration information, the user identity information, the eSIM hardware identification information of the first eSIM device and the second eSIM device, and the device transfer qualification information; The first eSIM device sends the code number configuration request and the inter-device trust verification result to the configuration server.

6. The method of claim 5, wherein, Before sending a configuration request to the eSIM management server, the following steps are also included: Based on the eSIM configuration information of the first eSIM device and the original number association information in the number configuration request, a request to cancel the binding relationship between the first device and the original number is sent to the eSIM management server. Receive the successful deregistration confirmation message returned by the eSIM management server; Based on the successful cancellation confirmation message, a configuration request for the second eSIM device is initiated to the eSIM management server.

7. The method of claim 2, wherein, The step of initiating a configuration request to the eSIM management server to obtain the activation code corresponding to the eSIM service includes: The verification result and the eSIM hardware identification information of the user equipment are encapsulated into the configuration request, and the configuration request is sent to the eSIM management server through an interface conforming to the eSIM standard. The eSIM management server verifies the validity of the verification result in the configuration request and the eSIM hardware identification information. After successful verification, an activation code for an eSIM configuration file uniquely bound to the target device is generated based on the eSIM hardware identification information and the service type corresponding to the code number configuration request. The activation code is sent to the configuration server through the eSIM-compliant interface.

8. The method of claim 7, wherein, Sending the activation code to the user equipment to enable the user equipment to complete the configuration of the eSIM number includes: The configuration server encrypts the activation code and the eSIM hardware identification information of the user device, generates an encrypted activation code, and sends it to the user device. The user equipment verifies the encrypted activation code based on its own eSIM hardware identification information. After successful verification, it establishes a connection with the eSIM management server through the eSIM-compliant interface. The user equipment sends the encrypted activation code to the eSIM management server so that the eSIM management server can decrypt the encrypted activation code; After decryption, the eSIM management server verifies the consistency of the device based on the eSIM hardware identification information. After successful verification, an eSIM configuration file uniquely associated with the activation code is generated based on the service type corresponding to the activation code and sent to the user equipment. The user equipment receives and installs the eSIM configuration file to complete the eSIM number configuration, and then sends the configuration status information back to the configuration server.

9. An eSIM number configuration system, characterized by, The system includes: The message receiving module is used to configure the server to receive a code number configuration request from the user equipment. The code number configuration request carries user identity information and eSIM code number service qualification information. The verification module is used to verify the user's identity and business qualifications based on the code number configuration request; The message sending module is used to send a configuration request to the eSIM management server after successful verification in order to obtain the activation code corresponding to the eSIM service; The message sending module is also used to send the activation code to the user equipment so that the user equipment can complete the configuration of the eSIM number.

10. A computer-readable storage medium, characterized in that, It stores computer-readable instructions that can be executed by a processor to implement the method as described in any one of claims 1-8.

Images