A method, system, and storage medium for configuring network identity in a soft SIM

By allocating seed codes through a code management platform and using near-field communication to automate the initialization of soft SIM terminals, the network access problem without pre-set code data is solved, improving production efficiency and resource utilization.

CN123075409APending Publication Date: 2026-11-10ZHONGRUI COMM PLANNING & DESIGN
View PDF 5 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

Existing soft SIM initialization solutions struggle to automate network access without pre-configured number data, leading to wasted number resources and low production efficiency. Furthermore, their reliance on manual operation makes them unsuitable for batch testing scenarios.

Method used

Seed codes are allocated and seed configuration files are generated through a code management platform. Terminal initialization is achieved using near-field communication, and resource recycling is achieved through timer and working code pool management, reducing reliance on manual operation and network switching.

Benefits of technology

It enables autonomous network access for terminals without pre-set code numbers, reduces waste of code number resources, and improves the automation level and resource utilization efficiency of production line testing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123075409A_ABST
    Figure CN123075409A_ABST
Patent Text Reader

Abstract

This application discloses a method, system, and storage medium for configuring network identity in a soft SIM, relating to the field of communication technology. In this application, a number management platform responds to a configuration file request sent by a mobile terminal via near-field communication. It allocates seed numbers from a seed number pool and generates and sends back a seed configuration file, enabling the mobile terminal to obtain a temporary credential for network access without pre-setting a number. The platform synchronously updates the allocation status and starts a timer to track the status of the issued seed numbers. After the terminal accesses the network using the seed configuration file and receives authentication instructions from the network side, the platform allocates a working number from the working number pool and sends a working configuration file, instructing the terminal to complete the replacement in the soft SIM module. Finally, based on the timer status or the configuration file update information fed back by the terminal, the seed number is returned to the seed number pool. This application completes the initialization and network access of the soft SIM without the soft SIM terminal pre-setting any number data and suppresses the pre-consumption of number resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, system and storage medium for configuring network identity in a soft SIM. Background Technology

[0002] In urban emergency communication support, especially in 6G-oriented application scenarios, numerous operations are involved, including testing of emergency communication equipment, smart terminal production lines, and vehicle-mounted systems. During batch testing, it's typically necessary to manually insert removable physical SIM cards into terminals to enable network connectivity and transmit test anomaly logs in real time. This method is prone to damage to the physical SIM card or slot due to repeated insertion and removal, leading to terminal rework. Furthermore, the reliance on manual operation is cumbersome and impacts production line efficiency. Therefore, soft SIMs are gradually being applied to terminal production line testing and other scenarios to replace physical SIM card solutions. Compared to physical SIM cards, soft SIMs port all the software functions of the physical SIM card to the terminal baseband or module, operating as part of its software and virtually implementing the user identification module's functions.

[0003] When a soft SIM is activated, a proprietary instruction protocol is used to complete the process of downloading a user-specific configuration file from the server side to the device side. The user-specific configuration file contains basic data such as the card serial number, authentication key, algorithm configuration parameters, and derived authentication key, as well as personalized data such as the International Mobile Subscriber Identity Code (IMSI), IC card identification code, personal identification number (PIN), and PIN unlock code. It is the core data for activating the soft SIM.

[0004] In existing technologies, there are two main ways to download and write user-specific configuration files to a soft SIM: First, the user-specific configuration files are written synchronously during the production process of the terminal baseband or module. Since the code number data must be unique when multiple terminals are simultaneously accessing the network, this method requires batch pre-setting of code numbers, which occupies a large amount of valuable code number resources and brings significant additional costs. Second, the user-specific configuration files are obtained through over-the-air (OTA) download or local download during production line testing. If local download relies on a wired connection, the drawbacks are basically the same as those of the physical SIM card solution. However, for OTA download, since the terminal soft SIM does not have any pre-set code number data and cannot independently access the cellular network, how to complete the initial network access and establish a bearer channel becomes a new challenge.

[0005] To address the above problems, existing technologies have proposed several improvement solutions, but all of them have certain limitations: Chinese invention patent CN108616861B (application number 201710001823.X) discloses an over-the-air SIM card writing method and apparatus. This method accesses the network through an emergency call process and establishes a bearer channel with a number management server to obtain and write SIM card data. However, the emergency call process defined in 3GPP TS 23.167 primarily targets voice and SMS calls, and the call recipient is typically a pre-set emergency number (such as 120, 122, 119, etc.). This solution relies on customized extensions of the emergency call access process to support configuration file downloads, involving collaborative modifications to the terminal-side protocol stack and network-side core network element processes. Implementation requires a high degree of cooperation between terminal and network equipment manufacturers, thus limiting its versatility and portability.

[0006] Chinese invention patent CN115022919B (application number 202210625633.6) discloses a testing method, device, and system based on a soft SIM. The soft SIM connection application module of the test terminal establishes communication with a soft SIM cloud server via USB cable or WiFi connection, thereby completing the import, activation, and real-network testing of the soft SIM. However, this solution still relies on manual operations such as wired cable plugging and unplugging or WiFi network configuration, making it difficult to adapt to the batch automation requirements of smart terminal production line testing scenarios that do not rely on manual intervention.

[0007] Chinese invention patent CN117440360B (application number 202311771257.2) discloses a method, system, electronic device, and storage medium for implementing eSIM in a CPE. It establishes initial network connectivity via WiFi, and then switches to a mobile data network for subsequent data interaction after acquiring EUICC information. However, this method relies on manual operation to switch between WiFi and cellular data networks, making it difficult to adapt to the needs of reducing manual intervention and improving automation in smart terminal production line testing scenarios.

[0008] Chinese invention patent application CN117319991A (application number 202311263191.6) discloses a SIM card writing method and system based on AT commands. The method involves a card writing tool reading data from the SIM card and sending a card writing request to an over-the-air (OTA) card writing platform. The OTA platform verifies the card writing permissions, assembles the personalized data into AT commands, and sends them to the communication module via the card writing tool. The baseband chip then parses the commands to complete the card data modification. However, this solution relies on manual operation of the card writing tool and interaction with the OTA card writing platform, making it difficult to adapt to the needs of intelligent terminal production line testing scenarios that require avoiding excessive introduction of new processes and improving automation levels.

[0009] In summary, existing soft SIM initialization solutions have two main inherent shortcomings: First, both pre-setting the code number during the production stage and pre-setting the temporary code number during the production line stage require reserving a unique code number for batch terminals that have not yet been confirmed for final deployment. This can easily lead to the accumulation and waste of code number resources due to situations such as failure to pass testing or failure of the equipment to be finally deployed. Second, the auxiliary means introduced to enable terminals without pre-set codes to access the network either rely on customized extensions of the emergency call access process or on manual switching between wired cables, WiFi and cellular networks, and manual operation of card writing tools. These methods are difficult to adapt to the deployment requirements of batch, automated, and non-excessive introduction of new processes in smart terminal production line testing scenarios.

[0010] Therefore, how to complete the initialization and network access of the soft SIM without any pre-installed number data in the soft SIM terminal, and how to suppress the pre-consumption of number resources, has become an urgent technical problem to be solved. Summary of the Invention

[0011] This application provides a method, system, and storage medium for configuring a soft SIM network identity, which is used to complete the initialization of the soft SIM and network access without pre-setting any code number data in the soft SIM terminal, and to suppress the pre-consumption of code number resources.

[0012] In a first aspect, embodiments of this application provide a method for configuring a soft SIM network identity, applied to a number management platform, the method comprising: In response to a configuration file request sent by a mobile terminal via near-field communication, a seed code number is allocated from a seed code number pool, a seed configuration file is generated based on the seed code number, and the seed configuration file is sent to the mobile terminal via the near-field communication. Update the allocation status of the seed codes in the seed code pool, and start a timer for the seed codes; Based on the authentication command fed back by the network side after the mobile terminal accesses the network according to the seed configuration file, a working code number is allocated from the working code number pool, a working configuration file is generated based on the working code number, and the working configuration file is sent to the mobile terminal so that the mobile terminal replaces the seed configuration file with the working configuration file in the soft SIM module. Based on the timing status of the timer or the configuration file update information fed back by the mobile terminal, the seed code number is recycled back to the seed code number pool.

[0013] In the above embodiments, this application responds to the configuration file request sent by the mobile terminal via near-field communication by the code number management platform, allocates a seed code number from the seed code number pool, generates a seed configuration file and sends it back, so that the mobile terminal can obtain a temporary credential for network access without pre-setting a code number; the platform synchronously updates the allocation status and starts a timer to track the status of the issued seed code numbers; after the terminal accesses the network with the seed configuration file and receives the authentication instruction from the network side, the platform allocates a working code number from the working code number pool and issues a working configuration file, instructing the terminal to complete the replacement in the soft SIM module; finally, according to the timer status or the configuration file update information fed back by the terminal, the seed code number is recycled back to the seed code number pool; this application not only avoids the resource accumulation problem caused by pre-setting a unique code number on the terminal side, but also improves the overall utilization efficiency of code number resources through the recycling mechanism of seed code numbers. At the same time, by using near-field communication to complete the configuration file issuance, the reliance on cable plugging and unplugging and manual network switching is reduced, and the automation level of the production line testing process is improved.

[0014] In some embodiments, the step of recycling the seed code number back to the seed code number pool includes: When the timer's duration is greater than or equal to a preset duration, the seed code number's allocation status in the seed code number pool is set to unallocated, and the timer is cleared.

[0015] In the above embodiments, when the timer's duration reaches or exceeds a preset duration, this application sets the seed code number's allocation status in the seed code number pool to unallocated and clears the timer; this reduces the problem of seed code numbers being occupied for a long time due to terminal abnormalities, enables the seed code number pool to have autonomous recovery capabilities in the absence of feedback, and improves the turnover efficiency of seed code numbers.

[0016] In some embodiments, the step of recycling the seed code number back to the seed code number pool includes: Based on the received configuration file update information, the allocation status of the seed code number in the seed code number pool is set to unallocated, and the timer is cleared. The configuration file update information includes a user identification code, an update status identifier, and a timestamp. The update status identifier is used to characterize the replacement result of the seed configuration file in the soft SIM module.

[0017] In the above embodiments, after receiving the configuration file update information from the terminal, this application immediately sets the allocation status of the corresponding seed code number in the seed code number pool to unallocated and clears the timer. The feedback information is composed of the user identification code, the update status identifier, and the timestamp, so that the platform can accurately identify the recycled seed code number and its replacement result. This shortens the cycle from seed code number issuance to recycling and facilitates the platform to trace the replacement process and verify its status.

[0018] In some embodiments, the authentication command is a command generated by the network side after performing a legality verification based on the device identification code of the mobile terminal; The legality verification is based on the device identification code data table, which includes the device identification code, the number of times the user identification code can be allocated, the number of times the user identification code can be allocated, and the validity period of the obtained code number. When the number of times the user identification code is assigned is less than the number of times the user identification code can be assigned, and the current time is within the validity period of the acquired code number, the device identification code is determined to be valid.

[0019] In the above embodiments, if the terminal identity verification process is lacking during the soft SIM initialization, illegal or unauthorized terminals may fraudulently obtain working numbers by forging configuration files. For example, an unauthorized terminal may repeatedly request configuration files from the platform to occupy number resources. In this application, the network side performs legality verification based on the device identification code carried in the terminal registration request. The device identification code data table used for verification includes fields for allocation count, available allocation count, and validity period of the obtained number. The terminal is deemed legitimate only when the allocation count is lower than the available allocation count and the current time is within the validity period. This not only restricts the repeated application behavior of a single terminal for working numbers but also facilitates differentiated configuration of number application permissions for terminals from different manufacturers and batches.

[0020] In some embodiments, both the seed configuration file and the working configuration file include a card serial number, authentication key, algorithm configuration parameters, derived authentication key, user identification code, and integrated circuit card identification code; The authentication key is updated periodically by the business operation support system and synchronized to the code management platform.

[0021] In the above embodiments, this application clarifies that both the seed configuration file and the working configuration file contain the card serial number, authentication key, algorithm configuration parameters, derived authentication key, user identification code, and integrated circuit card identification code, enabling the configuration file to have complete authentication and identification capabilities. On the other hand, the business operation support system updates the authentication key periodically and synchronizes it to the code management platform. This not only reduces the security exposure risk caused by the key remaining unchanged for a long time, but also eliminates the need for terminal-side intervention in the key update process, improving the convenience of security maintenance on the platform side.

[0022] In some embodiments, the code management platform includes a near end of the code management platform and a far end of the code management platform; The near end of the code management platform is connected to the mobile terminal via near-field communication, the near end of the code management platform is connected to the far end of the code management platform via wired or wireless means, and the far end of the code management platform is connected to the network side via an encrypted transmission protocol.

[0023] In the above embodiments, if the code management platform is deployed in a centralized manner, it needs to simultaneously handle near-field interaction with field terminals and remote communication with the network side. For example, if a production line directly engages in a large number of near-field interactions with a remote code system, it will be limited by the field network conditions and deployment complexity. This application divides the code management platform into two parts: a near end and a far end. The near end handles near-field communication transmission and reception with field terminals, while the far end handles remote encrypted communication with the network side. The two are interconnected via wired or wireless means. This decouples near-field interaction and remote communication in deployment and facilitates flexible configuration of near-end devices in different production line sites without the need for repeated deployment of far-end services.

[0024] Secondly, embodiments of this application provide a soft SIM network identity configuration method, applied to a mobile terminal, including: Based on the detection result that there is no configuration file in its own soft SIM module, the configuration file request is sent to the number management platform via near field communication; Receive the seed configuration file sent by the number management platform through the near-field communication, and write the seed configuration file into the soft SIM module; A registration request is sent to the network side based on the seed configuration file, and the registration request carries the device identification code of the mobile terminal. The module receives the working configuration file issued by the number management platform, replaces the seed configuration file with the working configuration file in the soft SIM module, and sends the configuration file update information back to the number management platform.

[0025] In the above embodiments, existing soft SIM terminals cannot initiate network registration autonomously if they do not have pre-set code number data during the initialization phase. For example, during the testing phase of a terminal production line, a physical SIM card or connecting cable still needs to be manually inserted to complete the configuration file download. In this application, after the mobile terminal detects that there is no configuration file in its own soft SIM module, it actively sends a request to the code number management platform through near-field communication and receives the seed configuration file to write to the soft SIM module. Then, based on the seed configuration file, it initiates a registration request to the network side and carries its own device identification code. In turn, it receives the working configuration file to complete the replacement and feeds back the update information. This application not only enables the terminal to have the ability to autonomously join the network without a pre-set code number, but also eliminates the dependence on physical insertion or manual network switching during the batch testing phase, thereby improving the automation level of the production line.

[0026] In some embodiments, sending a configuration file request to the code management platform via near-field communication includes: Configure the near-field communication to point-to-point mode, and send the configuration file request to the code management platform through the point-to-point mode; The steps of writing the seed configuration file into the soft SIM module and replacing the seed configuration file with the working configuration file in the soft SIM module are both executed by generating AT commands.

[0027] In the above embodiments, since near-field communication has multiple working modes, if not explicitly specified, the configuration file request may fail to be sent due to mode matching issues. Furthermore, since the writing of the soft SIM module needs to be compatible with the existing command interface of the baseband module, for example, a certain module only accepts the writing operation of the standard command interface. This application configures near-field communication as a point-to-point mode to carry bidirectional data exchange with the code management platform, and completes the writing of the seed configuration file and the replacement of the working configuration file by generating AT commands. This makes the near-field interaction between the terminal and the platform more stable, and at the same time makes the configuration file writing process compatible with the standard command interface of the existing baseband module, thus improving the portability of the solution.

[0028] Thirdly, embodiments of this application provide a soft SIM network identity configuration system, including a near end of a number management platform and a far end of a number management platform; The code management platform is configured to send and receive seed configuration files, working configuration files, and configuration file update information with the mobile terminal via near-field communication. The remote configuration of the code management platform is as follows: In response to the configuration file request sent by the mobile terminal via the near end of the code management platform, a seed code number is allocated from the seed code number pool, the seed configuration file is generated based on the seed code number, and the seed configuration file is sent to the mobile terminal via the near end of the code management platform. Start a timer for the seed code number; Based on the authentication command fed back by the network side after the mobile terminal accesses the network, a working code number is allocated from the working code number pool, the working configuration file is generated based on the working code number, and the working configuration file is sent to the mobile terminal via the code number management platform, so that the mobile terminal replaces the seed configuration file with the working configuration file in the soft SIM module. Based on the timing status of the timer or the update information of the configuration file, the seed code number is recycled back to the seed code number pool.

[0029] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method as described in the first aspect and any possible implementation thereof, or implements the method as described in the second aspect and any possible implementation thereof.

[0030] One or more technical solutions provided in the embodiments of this application have at least the following beneficial effects: 1. By maintaining a seed code pool on the code management platform side, seed configuration files are sent to mobile terminals without pre-set codes via near-field communication, enabling the terminals to complete registration and authentication with the network side. Subsequently, the platform allocates working codes from the working code pool and sends working configuration files to complete the replacement. Compared with the method of pre-setting a unique code for each terminal in the production stage, the proportion of code accumulation caused by failed tests or equipment not being finally put into operation is reduced. Compared with the method of relying on wired connections or manual network switching in the production line stage, the automation level of the initialization process is improved. 2. By setting up a dual management mechanism of allocation status and timer for the seed code pool, the seed code is recycled in real time when the terminal reports the update information of the configuration file. On the other hand, it is actively recycled when the timer reaches the preset time, so that the seed code has a dual-path turnover capability of fast recycling with feedback and self-recovery without feedback. 3. By verifying the legitimacy of terminals on the network side based on the device identification code data table, and by restricting the number of times user identification codes can be assigned, the number of times they can be assigned, and the validity period of the obtained code number, the distribution of working codes is restricted to legitimate terminals that are within their validity period. This reduces the possibility of unauthorized terminals fraudulently obtaining working codes and facilitates differentiated permission configuration for terminals from different manufacturers and batches, thereby improving the controllability of resource allocation on the platform side. Attached Figure Description

[0031] Figure 1 This is a schematic diagram illustrating the application of this application's embodiments in a smart terminal production line testing scenario; Figure 2 This is a schematic diagram of the overall technical architecture of an embodiment of this application; Figure 3 This is a flowchart illustrating a soft SIM network identity configuration method according to an embodiment of this application; Figure 4 This is a flowchart illustrating the soft SIM network identity configuration and verification method in an embodiment of this application; Figure 5 This is a multi-subject interaction timing diagram of a soft SIM network identity configuration method according to an embodiment of this application; Figure 6This is another flowchart illustrating a soft SIM network identity configuration method according to an embodiment of this application; Figure 7 This is a schematic diagram of the structure of a soft SIM network identity configuration system according to an embodiment of this application; Figure 8 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0032] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification of this application, the singular expressions “a,” “an,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this application refers to any or all possible combinations including one or more of the listed items.

[0033] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0034] To facilitate understanding, the application scenarios of the embodiments of this application are described below.

[0035] Please see Figure 1 , Figure 1 This is a schematic diagram illustrating the application of this application embodiment in a smart terminal production line testing scenario. In this scenario, mobile terminals move along the production line conveyor belt. The code management platform is deployed near the production line at a specific workstation and establishes a data interaction link with the mobile terminals via Near Field Communication (NFC). The code management platform is deployed far from the equipment room and interconnected with the near end of the code management platform via wired or wireless means. At the same time, it is interconnected with the operator's Business & Operation Support System (BOSS) via an encrypted transmission protocol.

[0036] Please see Figure 2 , Figure 2This is a schematic diagram of the overall technical architecture of an embodiment of this application. The overall architecture includes a mobile terminal, a near-end number management platform, a far-end number management platform, core network elements, and the operator's BOSS system. The core network elements include at least an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), and a Unified Data Management (UDM), used to carry out the forwarding and authentication of registration requests from the mobile terminal.

[0037] In the field of communication technology, soft SIM, as a virtual identification module solution that portes the software functions of a physical Subscriber Identity Module (SIM) card to the terminal baseband or module, is widely used in batch scenarios such as smart terminal production line testing because it eliminates the need for physical card insertion and removal. Related technologies either pre-assign a unique code number to each terminal during the terminal production stage, or rely on methods such as wired cable insertion and removal, and manual switching between WiFi and cellular networks to download the user-specific profile during the production line testing stage. The former results in a large accumulation of code number resources, while the latter is difficult to adapt to the needs of batch automated deployment. This application is mainly applied to batch testing scenarios such as smart terminal production line testing, emergency communication equipment testing, and vehicle-mounted system testing. In these application scenarios, it is necessary to automatically complete the initialization of the soft SIM and network access without any pre-assigned code number data on the terminal, while suppressing the pre-consumption of code number resources.

[0038] To address the aforementioned technical problems, this application provides a method for configuring a soft SIM network identity. The following description, using an embodiment and in conjunction with the accompanying drawings, illustrates such a method.

[0039] Please see Figure 3 , Figure 3 This application provides a flowchart illustrating a method for configuring a soft SIM network identity, which includes the following steps: S301. In response to the Profile request sent by the mobile terminal via NFC, allocate a seed code number from the seed code number pool, generate a seed Profile based on the seed code number, and send the seed Profile to the mobile terminal via NFC.

[0040] The seed number pool refers to the set of International Mobile Subscriber Identity (IMSI) codes that are pre-maintained by the number management platform and used to temporarily issue to mobile terminals that have not pre-installed any number data; the seed number refers to an IMSI that is assigned to a specific mobile terminal from the seed number pool; the seed profile refers to a profile generated based on the seed number that can be written into the soft SIM module of the mobile terminal and used directly to initiate a registration request to the cellular network; NFC refers to a short-range high-frequency wireless communication technology that operates in the 13.56MHz frequency band and supports three modes: inductive card reader, inductive card, and peer-to-peer (P2P) communication.

[0041] Specifically, the system first receives a Profile request from the mobile terminal via NFC from the near end of the code management platform, and forwards the request to the far end of the code management platform through the link between the near end and the far end of the code management platform. Then, the far end of the code management platform selects a seed code (i.e., seed IMSI) that is currently unassigned from the seed code pool and assigns it to the mobile terminal. Next, the far end of the code management platform generates a seed Profile based on the seed IMSI and a preset basic data template. Finally, the far end of the code management platform sends the seed Profile to the mobile terminal via the near end of the code management platform.

[0042] It should be noted that both the seed profile and the subsequently issued working profile include fields such as Card Serial Number (CARDSN), Key Identifier (Ki), Operator Variant Algorithm Configuration (OPC) field, Derived Authentication Key (K1), IMSI, and Integrated Circuit Card Identity (ICCID). For example, a seed profile might consist of the following fields: {CARDSN=8986…, Ki=A1B2…, OPC=C3D4…, K1=E5F6…, IMSI=460001234567890, ICCID=8986011…}. Among them, CARDSN, Ki, OPC, and K1 are basic data maintained by the code management platform; IMSI and ICCID are personalized data generated according to the allocation of seed code or working code; Personal Identification Number (PIN) and Personal Identification Number Unlock Key (PUK) are optional fields that can be added or deleted according to actual deployment needs. Ki is dynamically updated by the BOSS system on a periodic basis (e.g., every 7 days or 30 days) and synchronized to the remote code management platform. The update cycle is configured by the operations personnel based on security risks.

[0043] It should be noted that the code management platform consists of two parts: a near-end and a far-end. The near-end connects to the mobile terminal via NFC; the near-end and far-end connect via wired or wireless means (such as Ethernet, WiFi, etc.), the specific network standard depending on the production line environment; the far-end connects to the BOSS system via an encrypted transmission protocol (such as HTTPS). As a parallel implementation, the code management platform can also be deployed centrally, where a single entity handles both NFC communication with the mobile terminal and encrypted communication with the BOSS system. Both deployment methods functionally achieve the allocation, distribution, and recycling processes for seed and working codes as described in this application, differing only in deployment form and scalability.

[0044] It should be noted that the seed IMSIs in the seed number pool are pre-activated on the operator's side. Their corresponding Ki, OPC, and other basic authentication data are uniformly maintained by the BOSS system and synchronized to the remote number management platform and the network-side UDM. This ensures that registration requests initiated by mobile terminals using the seed profile to the network side can complete the legal authentication process through the standard AKA authentication procedure. When the same seed IMSI is recycled and redistributed to different mobile terminals, its corresponding Ki, OPC, and other basic data on the UDM side remain unchanged. Only the allocation status and occupancy identifier maintained on the number management platform side change. Therefore, it does not affect the AKA authentication success rate of subsequent reused terminals.

[0045] S302. Update the allocation status of the seed IMSI in the seed code pool and start a timer for the seed IMSI.

[0046] The Allocation Status refers to the occupancy flag corresponding to each seed IMSI in the seed number pool. It can be set to "Yes" or "No". "Yes" means that the seed IMSI has been allocated to a mobile terminal and has not been reclaimed. "No" means that the seed IMSI can be reassigned. The Timer is a timing component that is started independently for each allocated seed IMSI and is used to track the continuous occupancy time of the seed IMSI since it was issued.

[0047] Specifically, the system first locates the seed IMSI to be allocated in the seed IMSI pool maintained by the code management platform remotely; then, it updates the Allocation_status field corresponding to the seed IMSI from "no" to "yes"; next, it starts an independent Timer instance for the seed IMSI, with the timing starting when the Allocation_status update is completed; finally, it writes the seed IMSI, along with its Allocation_status and Timer instance, into the runtime status table of the seed code pool for subsequent recycling steps to query and determine.

[0048] It should be noted that the seed code pool contains at least three key fields: IMSI, Allocation_status, and Timer. For example, a partial record in the runtime status table of a certain seed code pool might look like this: {IMSI=460001234567890, Allocation_status=Yes, Timer started and duration = 120 seconds}; {IMSI=460001234567891, Allocation_status=No, Timer not started}. The seed code pool has a maximum capacity of M (M is a positive integer), and the specific value of M is set according to the scale of concurrent testing on the production line. Since the seed IMSI has the ability to be recycled and redistributed, a smaller value of M can support large-scale batch testing needs. In contrast, the working code pool has a maximum capacity of N (N is a positive integer), and in general, N is much larger than M.

[0049] S303. Based on the authentication instruction fed back by the network side after the mobile terminal accesses the network according to the seed profile, the working code number is allocated from the working code number pool, a working profile is generated based on the working code number, and the working profile is sent to the mobile terminal so that the mobile terminal replaces the seed profile with the working profile in the soft SIM module.

[0050] Among them, the working number pool refers to the set of IMSIs that the number management platform maintains in advance for formal allocation to mobile terminals and to support their long-term operation; the working number refers to an IMSI (i.e., a working IMSI) that is allocated to a specific mobile terminal from the working number pool; the working profile refers to the profile generated based on the working IMSI, used to replace the seed profile in the soft SIM module and to support the subsequent normal services of the mobile terminal; and the authentication instruction refers to the instruction information fed back to the number management platform by the network side after authenticating the registration request of the mobile terminal.

[0051] Please refer to the following for details. Figure 4 , Figure 4This is a flowchart illustrating the soft SIM network identity configuration and verification method in this embodiment. First, the AMF in the core network receives the registration request sent by the mobile terminal based on the seed profile and extracts the International Mobile Equipment Identity (IMEI) carried within it. The IMEI is forwarded to the AUSF and UDM for authentication, and the AUSF further sends the IMEI to the BOSS system for legality verification. Then, the BOSS system searches the pre-configured IMEI data table. If the IMEI exists in the data table and meets the legality judgment rules, an authentication command is sent to the remote number management platform; otherwise, an illegal message is sent. Next, after receiving the authentication command, the remote number management platform selects an unassigned working IMSI from the working number pool and assigns it to the mobile terminal. Based on the working IMSI and a preset basic data template, a working profile is generated. Finally, the remote number management platform sends the working profile to the mobile terminal via the near end of the number management platform. Upon receiving the working profile, the mobile terminal generates a corresponding write command, clears the original seed profile in the soft SIM module, and writes the working profile.

[0052] It should be noted that the IMEI data table must contain at least the following key fields: IMEI, IMSI allocation count, available IMSI allocation count, code acquisition validity period, and manufacturer. For example, a portion of a record in a data table could be: {IMEI=8612345678901230, IMSI allocation count=2, available IMSI allocation count=5, code acquisition validity period=2025-01-01 to 2026-12-31, manufacturer=a terminal manufacturer A}. The validity rule is: the IMEI is considered valid if and only if the IMSI allocation count is less than the available IMSI allocation count, and the current time is within the code acquisition validity period. It should be noted that the "authentication command" mentioned in this article refers to the command sent by the network side to the remote code management platform after verifying the legality of the mobile terminal's IMEI. This command is used to trigger the allocation of working code numbers and the issuance of working profiles. Its nature is an authorization decision by the operator regarding terminal access permissions. It is a separate process from the AKA authentication process executed by AMF, AUSF, and UDM based on seed IMSI and Ki in the 3GPP standard, and the two should not be confused. Furthermore, the signaling interactions between AUSF and the BOSS system, and between the BOSS system and the remote code management platform, are all implemented based on the operator's internal private interface and do not involve any modification to the 3GPP standard access and authentication process itself. As a parallel implementation method, the network side can also verify the IMEI solely based on its existence in a pre-configured list of legitimate IMEIs, without introducing allocation counts or validity period constraints. Both verification methods can support the generation of authentication commands; the former enables differentiated permission control for terminals from different manufacturers and batches, while the latter is simpler to deploy and maintain. As a parallel implementation method, considering that the mobile terminal has already registered with the cellular network using the seed profile, the working profile can also be directly sent from the remote end of the code management platform to the mobile terminal via the cellular network, without having to go through the near end of the code management platform and the NFC link for relay; both sending methods can support the replacement process of the working profile, and can be flexibly selected according to the deployment form of the production line and the conveyor belt turnover rate.

[0053] S304. Based on the timing status of the Timer or the Profile update information fed back by the mobile terminal, the seed IMSI is recycled to the seed code pool.

[0054] Among them, Profile update information refers to the information that the mobile terminal sends back to the number management platform after the seed profile is replaced to the working profile in the soft SIM module, which is used to inform the platform that the seed IMSI can be recycled; recycling refers to the operation of setting the Allocation_status of a certain seed IMSI in the seed number pool from "yes" to "no" and clearing its corresponding Timer.

[0055] Specifically, the system first has the remote code management platform continuously monitor the timing status of the Timer and simultaneously monitor the Profile update information forwarded by the near end of the code management platform; then it determines the triggering condition: if the timing duration of the Timer reaches or exceeds the preset duration, a timeout recycling branch is triggered; if Profile update information is received, a feedback recycling branch is triggered; then the recycling action of the corresponding branch is executed, setting the Allocation_status of the seed IMSI in the seed code pool to "No" and clearing its corresponding Timer; finally, the remote code management platform updates the runtime status table of the seed code pool so that the recycled seed IMSI can be reallocated in the subsequent S301 step.

[0056] It should be noted that for timeout branch recycling, the system starts a timer immediately after the seed IMSI is issued. If no Profile update information is received from the mobile terminal within a preset time (e.g., 300 seconds), it is determined that the seed IMSI may be unable to complete the subsequent network access process due to terminal failure, test interruption, or other reasons. The Allocation_status of the seed IMSI in the seed code pool is then set to "No," and its corresponding Timer is cleared. For example, if a seed IMSI = 460001234567890 is issued at time T with a preset time of 300 seconds, and no Profile update information is received by time T+300 seconds, its Allocation_status is reset from "Yes" to "No," and the Timer is cleared, allowing the seed IMSI to be reassigned to the next terminal under test.

[0057] It should be noted that for the feedback recycling branch, the Profile update information includes three fields: IMSI, update status identifier (ACK / NACK), and timestamp (Time_Stamp). The IMSI corresponds to the seed IMSI that has been covered this time; ACK / NACK indicates the replacement result of the seed Profile in the soft SIM module, with ACK indicating that the seed Profile has been successfully covered by the working Profile, and NACK indicating that the seed Profile has not been covered or the coverage failed; Time_Stamp corresponds to the current time when the mobile terminal sent the Profile update information. For example, a feedback message could be {IMSI=460001234567890, ACK / NACK=ACK, Time_Stamp=1766472459}. Based on this, the system locates the seed IMSI with IMSI 460001234567890, sets its Allocation_status to "No", and clears its corresponding Timer. If ACK / NACK is NACK, it indicates that the mobile terminal failed to complete the replacement. In this case, the system does not reclaim the seed IMSI, and the Timer continues to count down until it times out, at which point it is processed according to the timeout recycling branch. As a parallel implementation method, the two recycling branches can be enabled simultaneously or only one of them can be enabled: when only the timeout recycling branch is enabled, the recycling decision depends entirely on the preset duration and does not require feedback from the terminal side; when only the feedback recycling branch is enabled, the recycling decision depends entirely on the replacement result feedback from the terminal side; when both are enabled, a dual-path turnaround can be achieved with fast recycling when there is feedback and self-recovery when there is no feedback, improving the overall circulation efficiency of the seed IMSI.

[0058] In one specific embodiment, such as Figure 5 As shown, Figure 5 This is a multi-subject interaction timing diagram illustrating a soft SIM network identity configuration method provided in an embodiment of this application. It shows the complete signaling interaction timing between the mobile terminal, the near end of the number management platform, the far end of the number management platform, and the BOSS system. It should be noted that... Figure 5 The terms “first IMSI”, “first Profile”, and “first Profile update information” correspond to the aforementioned seed IMSI, seed Profile, and profile update information, respectively. The terms “second IMSI”, “second Profile”, and “second IMSI instruction” correspond to the aforementioned working IMSI, working Profile, and authentication instruction, respectively.

[0059] Specifically, the mobile terminal sends a request to the near end of the IMEI management platform to obtain the first profile (i.e., the seed profile request). The near end of the IMEI management platform forwards this request to the far end of the IMEI management platform. The far end of the IMEI management platform allocates the first IMSI (i.e., the seed IMSI) and generates the first profile data (i.e., the seed profile), which is then sent to the mobile terminal via the near end of the IMEI management platform. Subsequently, the seed number pool allocation status is updated, and a timer is started for the first IMSI. After completing the verification of the legality of the mobile terminal's IMEI, the BOSS system sends a second IMSI instruction to the far end of the IMEI management platform. (i.e., authentication command) Based on this, the remote end of the number management platform allocates a second IMSI (i.e., working IMSI) and generates second profile data (i.e., working profile), which is then sent to the mobile terminal via the near end of the number management platform. The mobile terminal replaces the first profile with the second profile in the soft SIM module. Finally, the mobile terminal sends the first profile update information (i.e., profile update information) back to the near end of the number management platform, which forwards it to the remote end of the number management platform. Based on this, the remote end of the number management platform updates the allocation status of the seed number pool and completes the recycling of the first IMSI.

[0060] It should be noted that in actual deployment, multiple mobile terminals can interact with the number management platform in parallel according to the above timing sequence, and their respective first IMSI allocation, Timer activation and recycling processes do not interfere with each other; if a mobile terminal fails to provide feedback on the first profile update information, the number management platform will actively trigger the first IMSI recycling after the timeout based on the timing status of the corresponding Timer.

[0061] In another embodiment, please refer to Figure 6 , Figure 6 Another flowchart illustrating a soft SIM network identity configuration method provided in this application embodiment includes the following steps: S601, based on the detection result that there is no Profile in its own soft SIM module, sends a Profile request to the number management platform via NFC.

[0062] Among them, the Profile request refers to the signaling message sent by the mobile terminal to the code management platform to apply for obtaining the seed Profile.

[0063] Specifically, the system first automatically runs a detection program after the mobile terminal is powered on to check whether there is Profile data in the soft SIM module. Then, if it is confirmed that there is no Profile in the soft SIM module, the terminal's NFC switch is enabled and configured to P2P mode. Next, when the mobile terminal moves along the production line conveyor belt to the workstation near the code management platform, an NFC handshake is automatically triggered. Finally, the mobile terminal sends a Profile request to the code management platform via NFC. The key fields of the request information include CARDSN, Ki, OPC, K1, IMSI, and ICCID.

[0064] It should be noted that NFC is configured in P2P mode; as a parallel implementation, NFC can also be configured in inductive reader mode or inductive card mode and complete the request transmission with the help of a relay device. All three modes can support the transmission of Profile requests, but P2P mode is more suitable in terms of the stability of bidirectional data exchange, so P2P mode is preferred in this embodiment.

[0065] S602: Receive the seed profile sent by the code management platform via NFC and write the seed profile into the soft SIM module.

[0066] Specifically, the system first has the mobile terminal receive the seed profile via NFC; then it performs an integrity verification on the seed profile; next, the mobile terminal generates the corresponding AT (Attention) command based on the fields of the seed profile; finally, the mobile terminal writes the seed profile into the soft SIM module via the AT command, enabling the mobile terminal to obtain a seed IMSI that can initiate a registration request.

[0067] It should be noted that AT commands are a standard command set used for control and data interaction between terminal devices and communication modules. Using AT commands to write to the soft SIM module maintains compatibility with existing baseband module interfaces. As a parallel implementation, if the mobile terminal's baseband module supports other manufacturers' proprietary command protocols, the seed profile can also be written using the corresponding proprietary commands. Both methods can achieve the writing operation to the soft SIM module as described in this application.

[0068] S603. Send a registration request to the network side based on the seed profile. The registration request carries the IMEI of the mobile terminal.

[0069] The system performs this step after the soft SIM module completes the seed profile writing, which is used to access the cellular network using the temporary code number data carried by the seed profile.

[0070] Specifically, the system first has the mobile terminal read the seed profile written in the soft SIM module; then it constructs a registration request message based on the IMSI, Ki, and other fields in the seed profile; next, it carries the mobile terminal's own IMEI in the registration request message; and finally, the mobile terminal sends a registration request to the AMF of the core network.

[0071] S604: Receive the working profile issued by the number management platform, replace the seed profile with the working profile in the soft SIM module, and report the profile update information to the number management platform.

[0072] Specifically, the system first has the mobile terminal receive the working profile issued by the code management platform via NFC; then the mobile terminal generates the corresponding AT command based on the fields of the working profile; next, the original seed profile in the soft SIM module is cleared and written into the working profile through the AT command; finally, the mobile terminal sends the profile update information back to the code management platform, which includes IMSI, ACK / NACK and Time_Stamp.

[0073] It should be noted that both writing and clearing in the soft SIM module are implemented through AT commands, and both share the same standard command set interface, which facilitates the implementation and porting of the terminal baseband module. For example, the feedback information can be {IMSI=460001234567890, ACK / NACK=ACK, Time_Stamp=1766472459}, where "460001234567890" is the seed IMSI assigned to the mobile terminal, "ACK" indicates that the seed profile has been successfully overwritten by the working profile, and "1766472459" is the current time when the mobile terminal sent the profile update information.

[0074] In some embodiments, please refer to Figure 7 , Figure 7 This is a schematic diagram of the structure of a soft SIM network identity configuration system according to an embodiment of this application. The system includes a near-end of a number management platform and a far-end of a number management platform.

[0075] The near-end of the code management platform includes: a communication module for establishing an NFC P2P connection with the mobile terminal and a wired or wireless connection with the remote end of the code management platform, and for sending and receiving seed profiles, working profiles, and profile update information; a processing module for processing the information sent and received by the communication module; and a storage module for temporarily storing information to be processed.

[0076] The remote part of the code management platform includes: a communication module for establishing wired or wireless connections with the near-end of the code management platform and the BOSS system; a processing module for processing the transmitted and received information, as well as performing judgment, start, and clear operations on the information of the Timer module; a storage module for temporarily storing information to be processed and storing database information such as the seed code pool and the working code pool; and a timer module for starting the timing for the seed IMSI.

[0077] The system implements all the steps of the method in the first embodiment described above. Specific operations such as responding to requests, allocating seed IMSI, starting a Timer, issuing seed Profiles, allocating working IMSIs, issuing working Profiles, and recycling seed IMSIs are all completed through the collaboration between the near end of the code management platform and the far end of the code management platform, which will not be described in detail here.

[0078] In some embodiments, please refer to Figure 8 , Figure 8 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. The electronic device may include a processor and a memory, wherein the memory is used to store a computer program, and the processor calls the computer program stored in the memory to execute the steps of the methods described in the first or second embodiment.

[0079] Optionally, this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the methods described in the first or second embodiment.

[0080] Optionally, this application also provides a program product, such as a computer-readable storage medium, including a program that, when executed by a processor, performs the steps of the aforementioned method embodiments.

[0081] In this embodiment, by employing the technical means of issuing a seed profile via NFC, issuing a working profile based on network-side authentication instructions, and reclaiming the seed IMSI based on the timer timing status or the profile update information fed back by the terminal, soft SIM initialization and network access can be completed without pre-setting any code number data on the terminal side. This alleviates the problem of code number resource accumulation caused by pre-setting code numbers in the prior art and the problem of network access difficulties caused by not pre-setting code numbers. In turn, it realizes the automated deployment of the soft SIM configuration process and the recycling of code number resources in batch testing scenarios such as smart terminal production line testing.

Claims

1. A method for configuring a soft SIM network identity, applied to a number management platform, characterized in that, The method includes: In response to a configuration file request sent by a mobile terminal via near-field communication, a seed code number is allocated from a seed code number pool, a seed configuration file is generated based on the seed code number, and the seed configuration file is sent to the mobile terminal via the near-field communication. Update the allocation status of the seed codes in the seed code pool, and start a timer for the seed codes; Based on the authentication command fed back by the network side after the mobile terminal accesses the network according to the seed configuration file, a working code number is allocated from the working code number pool, a working configuration file is generated based on the working code number, and the working configuration file is sent to the mobile terminal so that the mobile terminal replaces the seed configuration file with the working configuration file in the soft SIM module. Based on the timing status of the timer or the configuration file update information fed back by the mobile terminal, the seed code number is recycled back to the seed code number pool.

2. The method according to claim 1, characterized in that, The step of returning the seed code number to the seed code number pool includes: When the timer's duration is greater than or equal to a preset duration, the seed code number's allocation status in the seed code number pool is set to unallocated, and the timer is cleared.

3. The method according to claim 1, characterized in that, The step of returning the seed code number to the seed code number pool includes: Based on the received configuration file update information, the allocation status of the seed code number in the seed code number pool is set to unallocated, and the timer is cleared. The configuration file update information includes a user identification code, an update status identifier, and a timestamp. The update status identifier is used to characterize the replacement result of the seed configuration file in the soft SIM module.

4. The method according to claim 1, characterized in that, The authentication command is generated by the network side after verifying the legality of the mobile terminal's device identification code; The legality verification is based on the device identification code data table, which includes the device identification code, the number of times the user identification code can be allocated, the number of times the user identification code can be allocated, and the validity period of the obtained code number. When the number of times the user identification code is assigned is less than the number of times the user identification code can be assigned, and the current time is within the validity period of the acquired code number, the device identification code is determined to be valid.

5. The method according to claim 1, characterized in that, Both the seed configuration file and the working configuration file contain the card serial number, authentication key, algorithm configuration parameters, derived authentication key, user identification code, and integrated circuit card identification code; The authentication key is updated periodically by the business operation support system and synchronized to the code management platform.

6. The method according to claim 1, characterized in that, The code management platform includes a near-end code management platform and a far-end code management platform. The near end of the code management platform is connected to the mobile terminal via near-field communication, the near end of the code management platform is connected to the far end of the code management platform via wired or wireless means, and the far end of the code management platform is connected to the network side via an encrypted transmission protocol.

7. A method for configuring a soft SIM network identity, applied to a mobile terminal, characterized in that, include: Based on the detection result that there is no configuration file in its own soft SIM module, the configuration file request is sent to the number management platform through near field communication; Receive the seed configuration file sent by the number management platform through the near-field communication, and write the seed configuration file into the soft SIM module; Based on the seed configuration file, a registration request is sent to the network side, and the registration request carries the device identification code of the mobile terminal. The module receives the working configuration file issued by the number management platform, replaces the seed configuration file with the working configuration file in the soft SIM module, and sends the configuration file update information back to the number management platform.

8. The method according to claim 7, characterized in that, The step of sending a configuration file request to the code management platform via near-field communication includes: Configure the near-field communication to point-to-point mode, and send the configuration file request to the code management platform through the point-to-point mode; The steps of writing the seed configuration file into the soft SIM module and replacing the seed configuration file with the working configuration file in the soft SIM module are both executed by generating AT commands.

9. A soft SIM network identity configuration system, characterized in that, This includes the near end of the code management platform and the far end of the code management platform; The code management platform is configured to send and receive seed configuration files, working configuration files, and configuration file update information with the mobile terminal via near-field communication. The remote configuration of the code management platform is as follows: In response to the configuration file request sent by the mobile terminal via the near end of the code management platform, a seed code number is allocated from the seed code number pool, the seed configuration file is generated based on the seed code number, and the seed configuration file is sent to the mobile terminal via the near end of the code management platform. Start a timer for the seed code number; Based on the authentication command fed back by the network side after the mobile terminal accesses the network, a working code number is allocated from the working code number pool, the working configuration file is generated based on the working code number, and the working configuration file is sent to the mobile terminal via the code number management platform, so that the mobile terminal replaces the seed configuration file with the working configuration file in the soft SIM module. Based on the timing status of the timer or the update information of the configuration file, the seed code number is recycled back to the seed code number pool.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 6, or the method as described in any one of claims 7 to 8.

Citation Information

Patent Citations

  • Over-the-air card writing method and device

    CN108616861A

  • A method and apparatus for writing cards over the air

    CN108616861B

  • Testing method, equipment and system based on soft SIM

    CN115022919B

  • SIM over-the-air card writing method and system based on AT instruction

    CN117319991A

  • CPE eSIM implementation method and system, electronic device, and storage medium

    CN117440360B