A cloud card resource multiplexing method and device based on an eSIM plug-in card

Abstract

This invention discloses a method and apparatus for cloud card resource reuse based on an eSIM plug-in card. The method involves reading multiple card configuration files on the eSIM plug-in card to obtain the mapping relationship between each configuration file and the eSIM plug-in card; sending the multiple configuration files to a cloud server so that the cloud server allocates each configuration file as an independent cloud card resource to a cloud card device; responding to an authentication request from the cloud card device, reading the card identification code, and determining the target configuration file and its activation status from the mapping relationship; if the target configuration file is inactive, activating it using LPA (Limited Application Processing) for authentication; if the target configuration file is active, calculating authentication response parameters; and sending the authentication calculation result to the cloud card device to complete authentication. This invention quickly determines the activity status of a profile file through the mapping relationship, enabling multiple profile files in the eSIM plug-in card to be used effectively simultaneously, significantly improving the efficiency of cloud card resource reuse.

Description

Technical Field

[0001] This invention belongs to the field of wireless communication technology, specifically relating to a cloud card resource reuse method and apparatus based on eSIM plug-in cards. Background Technology

[0002] With the development of mobile communication technology, the form and function of SIM cards have been continuously enriched. Traditional physical SIM cards store a fixed set of card information, including the International Mobile Subscriber Identity (IMSI), Integrated Circuit Card Identifier (ICCID), Authentication Key (KI), and Operator Key (OPC). This set of card information uniquely corresponds to a mobile user number and subscription relationship. Users can access the operator's network by inserting the SIM card into their terminal device.

[0003] Embedded SIM cards (eSIMs) allow multiple operator profiles to be written into the card. For example, removable eSIM cards support multiple configuration storage and have the ability to store multiple profiles. However, their operating mechanism follows the GSMA specification's definition of eSIM activation status, which states that only one profile can be active at a time. This means that although the physical storage space of an eSIM card can store multiple sets of card information, logically only one set is currently active; the other profiles are inactive and cannot participate in network authentication and communication simultaneously, greatly limiting the resource utilization of the eSIM card.

[0004] Based on the above problems, the applicant proposes the technical solution of this application. Summary of the Invention

[0005] To achieve the above objectives, this invention discloses a cloud card resource reuse method based on an eSIM plug-in card, comprising the following steps: Read multiple card configuration files stored on the eSIM plug-in card, obtain the mapping relationship between each card configuration file and the eSIM plug-in card, the mapping relationship includes the card identifier code corresponding to the card configuration file and its corresponding eSIM plug-in card, as well as the status of the card configuration file; Send multiple card profiles stored on the eSIM plug-in card to the cloud server so that the cloud server allocates each card profile as an independent cloud card resource to the cloud card device; In response to the authentication request forwarded by the cloud server from the cloud card device, the card identification code contained in the authentication request is read, and the target card configuration file and its status are determined from the mapping relationship based on the card identification code; If the target card configuration file is not activated, the local configuration file assistant (LPA) is used to activate the target card configuration file for authentication. Authentication response parameters are calculated using the target card configuration file that is in an active state. The authentication calculation result is sent to the cloud card device so that the cloud card device can complete the authentication.

[0006] In some embodiments, a predetermined duration is used as a response time window. When authentication requests from multiple cloud card devices are received within the response time window, the target card configuration file and its status are determined from the mapping relationship based on the card identifier code in each authentication request. The cloud card authentication strategy is determined according to the receiving order of each authentication request and the status of each card configuration file.

[0007] In some embodiments, when multiple card identifiers corresponding to multiple cloud card device authentication requests belong to the same eSIM card, the cloud card authentication strategy is determined through the following steps: The first card configuration file that is active in the mapping relationship is selected as the target card configuration file for calculating authentication response parameters. After waiting for the first card configuration file to send the authentication calculation result to the corresponding cloud card device, the second card configuration file is selected as the target card configuration file according to the access order of the authentication request. The second card configuration file is activated, and the second card configuration file in the activated state is used as the target card configuration file to calculate the authentication response parameters. After the second card configuration file sends the authentication calculation result to the corresponding cloud card device, the third card configuration file is selected as the target card configuration file to calculate the authentication response parameters until the current response time window ends.

[0008] In some embodiments, before activating the second card configuration file, the first card configuration file is deactivated, so that the first card configuration file is in an inactive state, and the activation state of the first card configuration file in the mapping relationship is modified to an inactive state.

[0009] In some embodiments, when multiple card identifiers corresponding to multiple cloud card device authentication requests do not belong to the same eSIM card, the cloud card authentication strategy is determined through the following steps: Select multiple target card configuration files from the mapping relationship, calculate the authentication response parameters for the target card configuration files that are in an active state, and activate the target card configuration files that are in an inactive state in sequence before calculating the authentication response parameters.

[0010] In some embodiments, the maximum value of the predetermined duration is set to 6 seconds.

[0011] In some embodiments, the maximum number of card profiles stored on each eSIM card is 20.

[0012] In some embodiments, after the local configuration file assistant LPA changes the state of the target card configuration file, the state of the target card configuration file is modified in the real-time mapping relationship.

[0013] In some embodiments, if the target card configuration file determined from the mapping relationship is in an inactive state, the target card configuration file is activated using the Local Configuration File Assistant (LPA) for authentication.

[0014] This invention also discloses a cloud card resource reuse device based on an eSIM pluggable card, comprising the following modules: The network module is used to maintain a communication connection with the cloud server; The main control module is used to read multiple card configuration files stored on the eSIM plug-in card, obtain the mapping relationship between each card configuration file and the eSIM plug-in card, the mapping relationship includes the card identifier code corresponding to the card configuration file and its corresponding eSIM plug-in card, as well as the activation status of the card configuration file; send the multiple card configuration files stored on the eSIM plug-in card to the cloud server, so that the cloud server allocates each card configuration file as an independent cloud card resource to the cloud card device; respond to the authentication request forwarded by the cloud server from the cloud card device, read the card identification code contained in the authentication request, and determine the target card configuration file and its activation status from the mapping relationship based on the card identification code; if the target card configuration file is inactive, activate the target card configuration file using the local configuration file assistant LPA before using it for authentication; if the target card configuration file is active, calculate the authentication response parameters; and send the authentication calculation result to the cloud card device so that the cloud card device can complete the authentication. The LPA module is used to activate and deactivate the card information configuration file using the Local Configuration File Assistant (LPA). The smart card resource module provides multiple card slots for inserting eSIM cards.

[0015] In some embodiments, the main control module is further configured to, with a predetermined duration as a response time window, when authentication requests from multiple cloud card devices are received within the response time window, determine the target card configuration file and its activation status from the mapping relationship based on the card identifier code in each authentication request, and determine the cloud card authentication strategy according to the receiving order of each authentication request and the activation status of each card configuration file.

[0016] In some embodiments, the main control module is further configured to determine the cloud card authentication strategy through the following steps when multiple card identifier codes corresponding to multiple cloud card device authentication requests belong to the same eSIM card: The first card configuration file that is active in the mapping relationship is selected as the target card configuration file for calculating authentication response parameters. After waiting for the first card configuration file to send the authentication calculation result to the corresponding cloud card device, the second card configuration file is selected as the target card configuration file according to the access order of the authentication request. The second card configuration file is activated so that the activated second card configuration file is used as the target card configuration file for calculating authentication response parameters. After the second card configuration file sends the authentication calculation result to the corresponding cloud card device, another card configuration file is selected as the target card configuration file to calculate the authentication response parameters until the current response time window ends.

[0017] This invention also discloses a method for using resources in a terminal device, comprising the following steps: Obtain cloud card resources sent by the server. The cloud card resources are card configuration files stored on the eSIM pluggable card. The card configuration files are allocated to the terminal device by the server as cloud card resources. An authentication request for network authentication is sent to the server, so that the server forwards the authentication request to the smart card management device. The smart card management device reads the card identification code contained in the authentication request, determines the target card configuration file and its status from the mapping relationship stored in the smart card management device based on the card identification code, and calculates the authentication response parameters using the target card configuration file in the active state. The mapping relationship includes the card identification code corresponding to the card configuration file and its corresponding eSIM card, as well as the activation status of the card configuration file. Receive the authentication response parameters sent by the server to complete the authentication process.

[0018] The present invention also discloses a terminal device, comprising the following modules: The acquisition module is used to receive cloud card resources sent by the server. The cloud card resources are card configuration files stored on the eSIM plug-in card. The server allocates the card configuration files as cloud card resources to the terminal device. The module sends an authentication request for network authentication to the server. The server forwards the authentication request to the smart card management device. The smart card management device reads the card identification code contained in the authentication request, determines the target card configuration file and its status from the mapping relationship stored in the smart card management device based on the card identification code, and calculates the authentication response parameters using the target card configuration file in the active state. The mapping relationship includes the card identification code corresponding to the card configuration file and its corresponding eSIM plug-in card, as well as the active state of the card configuration file. The authentication module is used to receive authentication response parameters sent by the server in order to complete the authentication process.

[0019] The present invention also discloses a communication device, including at least one processor and a memory, wherein the memory stores a computer program, and the at least one processor executes the computer program stored in the memory, causing the at least one processor to execute the cloud card resource reuse method based on the eSIM plug-in card as described above.

[0020] Compared with the prior art, the present invention has the following beneficial effects: This invention significantly improves the reuse efficiency of profile file resources by establishing a mapping table locally on the smart card management device, reading all profile file information from the card, uploading it to a cloud server, and allocating it to cloud card devices. When responding to authentication requests, the smart card management device first quickly retrieves the target profile file and its activation status from the mapping relationship, and then dynamically activates it on demand using LPA based on its activation status. This allows multiple profile files in the eSIM card to be used effectively simultaneously, greatly improving the reuse efficiency of cloud card resources.

[0021] The following will further explain the concept, specific structure, and technical effects of the present invention in conjunction with the accompanying drawings, so as to fully understand the purpose, features, and effects of the present invention. Attached Figure Description

[0022] Figure 1 This refers to the network connection relationship between the cloud server, cloud card device, and smart card management device in this invention.

[0023] Figure 2 This is a flowchart illustrating the cloud card resource reuse method based on eSIM plug-in card in this invention.

[0024] Figure 3 This is a schematic diagram of the process of the smart card management device collecting profile information in this invention.

[0025] Figure 4 This is a schematic diagram of the process of activating Profile information by the smart card management device in this invention.

[0026] Figure 5 This is a schematic diagram of the cloud card resource reuse device based on eSIM plug-in card in this invention. Detailed Implementation

[0027] To make the technical means, inventive features, objectives, and effects of the invention readily understandable, the invention is further illustrated below with reference to specific figures. However, the invention is not limited to the embodiments described below.

[0028] It should be noted that the structures, proportions, sizes, etc., illustrated in the accompanying drawings of this specification are only used to complement the content disclosed in the specification for those skilled in the art to understand and read, 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.

[0029] The terminology used in this manual is explained below: Cloud SIM: A virtual SIM card technology implemented through software. The card itself does not contain security-related data or sensitive information; this information is stored on a cloud server. When authentication or other operations are required, a data channel must be established through another local SIM card (seed card, ignition card) to retrieve data from the server. (Authorization cannot be completed locally.) eSIM (embedded SIM card): This type of SIM card is directly embedded into the device's circuit board, unlike a traditional SIM card which exists as a separate card. Like a traditional SIM card, an eSIM card stores the user's identity information, authentication data, and relevant carrier configuration files to enable the device to connect and communicate with mobile communication networks. However, unlike a traditional SIM card, an eSIM card can switch between different carrier networks by remotely downloading and updating its configuration files. Users can change carriers or plans without replacing their physical SIM card. (Authorization can be completed locally.) eSIM plug-in card: A physical SIM card that can write or delete eSIM profiles. The eSIM profile (the card's configuration file, including information such as IMSI, ICCID, PLMN, and authentication parameters KI OPC; one profile is equivalent to one card's information) is written to the plug-in card, and it can be used as a normal physical card. An eSIM plug-in card can store multiple profiles, but only one profile can be activated at a time. For example, when activating a certain profile, all other profiles need to be deactivated first.

[0030] LPA: Short for Local Profile Assistant. It is a software interface used to download, activate, deactivate, and delete eSIM profiles from the SM DP+ platform. It allows management of profiles on removable eSIM cards.

[0031] Cloud server: A platform that manages cloud card information and is responsible for distributing cloud cards to cloud card terminal devices.

[0032] In applications such as the Internet of Things (IoT), cross-border communications, and remote SIM card banks, smart card management devices (such as remote SIM card servers and SIM card pool gateways) have been introduced to centrally manage and remotely allocate a large number of SIM card resources. These devices insert multiple physical SIM cards (including traditional SIM cards and eSIM pluggable cards), and use virtualization technology to map card information to "cloud cards," dynamically allocating them to remote terminal devices. Each inserted physical SIM card can only provide a single set of valid card information for a single terminal at any given time; that is, one physical card can only form one cloud card at a time. As the number of connected devices increases, the number of physical card slots on the smart card management device becomes a bottleneck, limiting the efficiency of cloud card resource generation and making it difficult to fully utilize the potential multiple identity capabilities of each SIM card. In existing technical solutions, each physical SIM card inserted into the smart card management device, regardless of how many configuration files it stores, can only form one valid cloud card for use by one remote device at any given time.

[0033] As the demand for cloud cards increases, smart card management devices are limited by the number of physical card slots, and the maximum concurrent cloud card resources they can generate are equal to the number of inserted physical cards. Even with the use of eSIM plug-in cards, this physical bottleneck cannot be overcome due to their "single card, single activation" mechanism. Under the current mechanism, an eSIM plug-in card with multiple configuration storage capabilities cannot simultaneously convert the multiple sets of card information it stores into multiple concurrent cloud card resources, resulting in low card slot utilization and insufficient cloud card resource generation efficiency.

[0034] like Figure 1 As shown, the network connection relationship between the cloud server, cloud card device, and smart card management device is illustrated. The smart card management device communicates with the cloud server via the network, and the cloud card device communicates with the cloud server via the seed card.

[0035] The cloud server manages cloud SIM card resources, allocates suitable card resources to cloud SIM card devices, and assists the cloud SIM card devices in completing remote authentication. The cloud SIM card device downloads the cloud SIM card from the cloud server via seed card traffic, registers and authenticates with the network (base station), and completes remote authentication. Once successful, it can access the network normally, allowing other network devices of the user to connect to the cloud SIM card device via Wi-Fi to access the internet. The smart card management device has multiple card slots for inserting removable eSIM cards. The smart card management device integrates LPA software, which manages the profile information in the removable eSIM cards. The smart card management device reports the collected profile information to the cloud server to form a cloud SIM card and dynamically switches the profile in the card to assist the cloud SIM card device in completing remote authentication.

[0036] The first embodiment of the present invention provides a cloud card resource reuse method based on eSIM plug-in card. Based on the hardware characteristics of eSIM plug-in card, the authentication control method of smart card management device is improved, breaking the limitation that only one set of card information can be activated at the same time, and improving the cloud card resource reuse efficiency of a single card slot.

[0037] like Figure 2 As shown, the cloud card resource reuse method based on eSIM plug-in card includes the following steps: Step S1: Read the multiple card configuration files stored on the eSIM plug-in card and obtain the mapping relationship between each card configuration file and the eSIM plug-in card.

[0038] Specifically, the local configuration file assistant (LPA) sequentially reads multiple card information entries from multiple eSIM plug-in cards. Each card information entry includes at least a card information configuration file and a card identifier code. The card identifier code corresponding to each card configuration file, its associated eSIM plug-in card, and the status of the associated card configuration file are stored locally as a mapping relationship. When cloud card device authentication is required, the card identification code included in the authentication request can be mapped to the card identifier code in the card configuration file, thus enabling the location of the card configuration file for authentication.

[0039] Step S2: Send the multiple card configuration files stored on the eSIM plug-in card to the cloud server so that the cloud server allocates each card configuration file as an independent cloud card resource to the cloud card device.

[0040] Specifically, such as Figure 3 As shown, the smart card management device uses LPA to read information from the eSIM card, extracting all the profile information from the card and recording the card corresponding to each profile. Then, it sends the IMSI and ICCID of each profile to the cloud server. Thus, each profile is essentially an independent cloud card. When the cloud card device authenticates with the server, the cloud server sends the packaged cloud card information (such as IMSI and ICCID) to the cloud card device.

[0041] Step S3: In response to the authentication request forwarded by the cloud server from the cloud card device, read the card identification code contained in the authentication request, and determine the target card configuration file and its status from the mapping relationship based on the card identification code.

[0042] If the target card configuration file is inactive, proceed to step S4, where the target card configuration file is activated using the Local Configuration File Assistant (LPA) for authentication.

[0043] If the target card configuration file is active, proceed to step S5 to calculate the authentication response parameters.

[0044] After step S5 is completed, proceed to step S6, where the authentication calculation result is sent to the cloud card device so that the cloud card device can complete the authentication.

[0045] Specifically, the mapping table locally set up by the smart card management device represents the mapping relationship of Profile files, acting as a local real-time database to record the activity status of each Profile file on each eSIM card in real time. The mapping table includes the card slot location of each eSIM card, the card identifier code corresponding to the card information in the Profile file, and the status of the corresponding card information configuration file, including active and inactive states. According to eSIM technical specifications and mobile network security mechanisms, the Profile file must be active during the authentication process of the cloud card device. Only when the Profile file is active will the card management device calculate the authentication response parameters using the authentication key KI and operation key OPC from the card information, and the network authentication parameter RAND, combined with the authentication algorithm. The authentication response parameters are then uploaded to the cloud server and the cloud card device, ensuring that the cloud card device can initiate an authentication request to the network only after successful authentication. If the Profile is inactive, the baseband cannot access the necessary security credentials, and the network cannot verify the user's identity. Multiple Profile files can be stored in an eSIM card, but only one Profile file can be active on each card at any given time. When a profile file changes from active to inactive, or vice versa, the mapping table is updated accordingly. In other words, when the target card's profile file is activated or deactivated using the Local Profile Assistant (LPA), the mapping table is updated in real-time to reflect the target card's profile file's status.

[0046] The smart card management device uploads the profile file read from the eSIM card to the cloud server. At this point, one profile file is equivalent to one cloud card. The cloud server assigns cloud cards to the cloud card device, encrypts the card information, and sends it to the cloud card device. The cloud card device writes the received card information into the modem's virtual card application. The modem treats the virtual card application as the physical SIM card in the device.

[0047] When a cloud SIM card device uses a cloud SIM card to access the internet, the cloud SIM card lacks an authentication key (KI) and an operation key (OPC). During network authentication, an authentication request is sent. Since authentication cannot be completed locally, the network authentication parameter RAND needs to be sent to the cloud server via the seed card network. The cloud server then retrieves the authentication response parameters from the smart card management device (specifying the eSIM insertion / removal card) and returns them to the cloud SIM card device. The cloud SIM card device uses the response value to complete authentication, and after successful verification, the cloud SIM card device accesses the network.

[0048] When a cloud SIM card device requests authentication, it uses the seed SIM card network to send the cloud SIM card network authentication parameters to the smart card management device. The smart card management device parses the authentication request packet, which includes the International Mobile Subscriber Identity (IMSI), the Card Identifier Code (ICCID), and the network authentication parameter RAND. Since the mapping table stores the status of the Profile file, the status of the Profile file and the card slot location can be quickly found from the mapping table based on the Card Identifier Code, which can significantly improve the efficiency of cloud SIM card resource reuse.

[0049] Because the smart card management device has multiple card slots, each slot can accommodate an eSIM card, and each eSIM card can store multiple profile files, allowing multiple authentication requests to complete the authentication process. For example... Figure 4 As shown, upon receiving the authentication random number from the cloud server, the system matches the corresponding Profile file to determine which eSIM card the Profile file is located in. If the Profile file is inactive, it is activated first; only activated Profile files can complete authentication successfully. When multiple authentication requests are received simultaneously, the system switches between Profile files sequentially within a limited time to complete subsequent authentications.

[0050] In this embodiment, a predetermined duration is used as a response time window. When authentication requests from multiple cloud SIM card devices are received within the response time window, the target card configuration file and its status are determined from the mapping relationship based on the card identifier code in each authentication request. The cloud SIM card authentication strategy is determined according to the receiving order of each authentication request and the status of each card configuration file. The maximum value of the predetermined duration is set to 6 seconds, and the maximum number of card configuration files stored on each eSIM card is 20. This ensures that the cloud SIM card resource reuse efficiency increases several times within each response time window.

[0051] The cloud card authentication strategy includes a single authentication request for a single profile file and multiple authentication requests for multiple profile files. In scenarios with multiple authentication requests, there are authentication requests for multiple profile files within the same plug-in SIM card, as well as authentication requests for multiple profile files across different plug-in SIM cards.

[0052] For authentication requests from a single cloud SIM card device, if the card information configuration file is active, the configuration file is located based on the SIM card slot location, and subsequent authentication is performed directly. If the configuration file is inactive, it is located based on the SIM card slot location, and the local configuration file assistant (LPA) is used to activate the configuration file. The activated configuration file is then used as the target configuration file for authentication.

[0053] For multiple authentication requests from multiple cloud SIM card devices, it is necessary to distinguish whether the multiple card identifiers are located in the same eSIM card, and determine the cloud SIM card authentication strategy based on the judgment result.

[0054] When multiple card identifiers corresponding to multiple cloud card device authentication requests belong to the same eSIM card, the cloud card authentication strategy is determined through the following steps: The first card configuration file that is active in the mapping relationship is selected as the target card configuration file for calculating authentication response parameters. After waiting for the first card configuration file to send the authentication calculation result to the corresponding cloud card device, the second card configuration file is selected as the target card configuration file according to the access order of the authentication request. The second card configuration file is activated, and the second card configuration file in the activated state is used as the target card configuration file to calculate the authentication response parameters. After the second card configuration file sends the authentication calculation result to the corresponding cloud card device, the third card configuration file is selected as the target card configuration file to calculate the authentication response parameters until the current response time window ends.

[0055] It should be noted that the aforementioned third card configuration file refers to card configuration files other than the first and second card configuration files.

[0056] In the cloud card authentication strategy, authentication calculations are first performed on activated profile files. Then, the first and second authentication requests are determined based on the response order of multiple authentication requests, with the first authentication request responding before the second. For the first authentication request, the card information configuration file is first ensured to be in an active state, and the corresponding card information is uploaded to the cloud server, enabling the first authentication request to complete the authentication response parameter calculation. Then, the card information configuration file is deactivated, making its active state inactive. Next, the card information configuration file corresponding to the second authentication request is activated, and the authentication response parameters from the corresponding card information are uploaded to the cloud server to complete the authentication for the second authentication request.

[0057] Specifically, when multiple profile files are involved in the simultaneous authentication of the same eSIM card, they must be authenticated sequentially. That is, a subsequent profile file can only begin authentication after the first profile file has completed all authentication steps. For example, when the first profile file 'a' and the second profile file 'b' are authenticated simultaneously, the activity status of the two files in the mapping table can be one of two things: file a is active and file b is inactive; or both file a and file b are inactive. In the first case, file a can be authenticated immediately. After file a completes its authentication process, file a is deactivated, then file b is activated, and finally, file b's authentication process is completed. In the second case, file a is activated first, and after it completes its authentication process, it is deactivated, then file b is activated, and finally, file b's authentication process is completed.

[0058] When multiple card identifiers in multiple cloud card device authentication requests do not belong to the same eSIM card, multiple target card configuration files are selected from the mapping relationship. The authentication response parameters are calculated for the active target card configuration files, and the inactive target card configuration files are activated sequentially before the authentication response parameters are calculated.

[0059] Specifically, if multiple card identifiers are located in different eSIM cards, the first authentication request and the second authentication request are processed concurrently based on the activity status of each card information configuration file.

[0060] When multiple profile files are involved in simultaneous authentication across different eSIM cards, concurrent authentication can be performed. The authentication processes for multiple profile files run in parallel without waiting for each other. In this case, the first authentication request and the second authentication request are distinguished. For each authentication request, the corresponding activity status and SIM card slot position of the profile file are looked up in the mapping table, and authentication is completed quickly. Taking simultaneous authentication of first profile file 'a' and second profile file 'b' as an example, the activity status of the two files in the mapping table can be one of three cases: file 'a' is active and file 'b' is inactive; both file 'a' and file 'b' are active; and both file 'a' and file 'b' are inactive. In the first case, file 'a' can be authenticated immediately, while file 'b' needs to be activated before authentication. In the second case, since both files are active, they can both be authenticated immediately without affecting each other. In the third scenario, since both files are inactive, they need to be activated before authentication. Following the order of requests, file a is activated first, followed by file b. After file a is activated, there is no need to wait for file a to complete authentication before activating and authenticating file b, allowing for parallel processing.

[0061] During the authentication process of the cloud SIM card device, the device downloads cloud SIM card information from the cloud server via the seed card network, writes this information into the modem's virtual card application, activates the cloud SIM card, and initiates registration with the network. Upon receiving the authentication packet from the network, the cloud SIM card device switches its current data channel to the seed card slot and sends the authentication packet to the cloud server. The cloud server then forwards the received authentication packet to the corresponding smart card management device. The smart card management device forwards the received authentication packet to the designated eSIM card, calculates the authentication response value within the eSIM card, and transmits it to the cloud SIM card device via the reverse path. The cloud SIM card device transmits the authentication response value to the network. After successful authentication, it switches the data card slot to the cloud SIM card slot, enabling normal internet access. When facing concurrent authentication requests from multiple cloud SIM card devices, the smart card management device uploads the authentication response parameters corresponding to the target card information configuration file to the cloud server. Then, according to the cloud SIM card authentication strategy, it switches to other target card information configuration files, ultimately completing the concurrent authentication of all cloud SIM card devices.

[0062] This embodiment leverages the characteristic that a single eSIM card can store multiple profile files, but only one profile file can be used at a time. A mapping table is established locally on the smart card management device, and all profile file information from the card is read and uploaded to the cloud server for allocation to cloud card devices. This significantly improves the reuse efficiency of profile file resources. Since authentication can only be completed when a profile file is active, upon responding to an authentication request, the smart card management device first uses the mapping table to quickly query the profile file's activity status and card slot location, and then uses LPA to dynamically switch activation. This allows multiple profile files in the eSIM card to be used effectively simultaneously, greatly improving the reuse efficiency of cloud card resources.

[0063] A second embodiment of the present invention provides a cloud card resource multiplexing device based on an eSIM pluggable card, such as... Figure 5 As shown, the device includes a network module, a main control module, a power supply module, an LPA module, and a smart card resource module.

[0064] The network module is used to maintain a communication connection with the cloud server.

[0065] The main control module is used to read multiple card configuration files stored on the eSIM plug-in card, obtain the mapping relationship between each card configuration file and the eSIM plug-in card, the mapping relationship includes the card identifier code corresponding to the card configuration file and its corresponding eSIM plug-in card, as well as the activation status of the card configuration file; send the multiple card configuration files stored on the eSIM plug-in card to the cloud server, so that the cloud server allocates each card configuration file as an independent cloud card resource to the cloud card device; respond to the authentication request forwarded by the cloud server from the cloud card device, read the card identification code contained in the authentication request, and determine the target card configuration file and its activation status from the mapping relationship based on the card identification code; if the target card configuration file is inactive, activate the target card configuration file using the local configuration file assistant LPA before using it for authentication; if the target card configuration file is active, calculate the authentication response parameters; and send the authentication calculation result to the cloud card device so that the cloud card device can complete the authentication.

[0066] The LPA module is used to activate and deactivate the card information configuration file using the Local Configuration File Assistant (LPA).

[0067] The smart card resource module provides multiple card slots for inserting eSIM cards, and the power module provides power to the device.

[0068] In one example, the main control module is also used to use a predetermined duration as a response time window. When authentication requests from multiple cloud card devices are received within the response time window, the target card configuration file and its activation status are determined from the mapping relationship based on the card identifier code in each authentication request. The cloud card authentication strategy is determined according to the receiving order of each authentication request and the activation status of each card configuration file.

[0069] In one example, the main control module is also used to determine the cloud card authentication strategy through the following steps when multiple card identifier codes corresponding to multiple cloud card device authentication requests belong to the same eSIM card: The first card configuration file that is active in the mapping relationship is selected as the target card configuration file for calculating authentication response parameters. After waiting for the first card configuration file to send the authentication calculation result to the corresponding cloud card device, the second card configuration file is selected as the target card configuration file according to the access order of the authentication request. The second card configuration file is activated so that the activated second card configuration file is used as the target card configuration file for calculating authentication response parameters. After the second card configuration file sends the authentication calculation result to the corresponding cloud card device, another card configuration file is selected as the target card configuration file to calculate the authentication response parameters until the current response time window ends.

[0070] Since the first embodiment corresponds to this embodiment, this embodiment can be implemented in conjunction with the first embodiment. The relevant technical details mentioned in the first embodiment remain valid in this embodiment, and the technical effects achievable in the first embodiment can also be achieved in this embodiment. To reduce repetition, they will not be repeated here. Correspondingly, the relevant technical details mentioned in this embodiment can also be applied to the first embodiment.

[0071] A third embodiment of the present invention provides a method for using resources in a terminal device, comprising the following steps: Obtain cloud card resources sent by the server. The cloud card resources are card configuration files stored on the eSIM pluggable card. The card configuration files are allocated to the terminal device by the server as cloud card resources. An authentication request for network authentication is sent to the server, so that the server forwards the authentication request to the smart card management device. The smart card management device reads the card identification code contained in the authentication request, determines the target card configuration file and its status from the mapping relationship stored in the smart card management device based on the card identification code, and calculates the authentication response parameters using the target card configuration file in the active state. The mapping relationship includes the card identification code corresponding to the card configuration file and its corresponding eSIM card, as well as the activation status of the card configuration file. Receive the authentication response parameters sent by the server to complete the authentication process.

[0072] The terminal device in this embodiment is a cloud card device. The authentication process of the cloud card device is similar to that in the first embodiment, and will not be described again here.

[0073] The fourth embodiment of the present invention provides a terminal device, including the following acquisition module and authentication module.

[0074] The acquisition module receives cloud card resources sent by the server. These cloud card resources are card configuration files stored on the eSIM plug-in card. The server allocates these card configuration files as cloud card resources to the terminal device. The acquisition module sends an authentication request for network authentication to the server. The server forwards the authentication request to the smart card management device. The smart card management device reads the card identification code contained in the authentication request and determines the target card configuration file and its status from a mapping relationship stored within the smart card management device based on the card identification code. It then calculates the authentication response parameters using the active target card configuration file. The mapping relationship includes the card identifier code corresponding to the card configuration file, its associated eSIM plug-in card, and the activation status of the card configuration file. The authentication module receives the authentication response parameters sent by the server to complete the authentication process.

[0075] The fifth embodiment of the present invention provides a communication terminal, including at least one processor and a memory, wherein the memory stores a computer program, and the at least one processor executes the computer program stored in the memory, causing the at least one processor to execute the cloud card resource reuse method based on eSIM plug-in card as described in the first embodiment.

[0076] A fourth embodiment of the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, is used to implement the cloud card resource reuse method based on eSIM plug-in card as described in the first embodiment.

[0077] The preferred embodiments of the present invention have been described in detail above. It should be understood that those skilled in the art can make numerous modifications and variations based on the concept of the present invention without creative effort. Therefore, all technical solutions that can be obtained by those skilled in the art based on the concept of the present invention through logical analysis, reasoning, or limited experimentation on the basis of existing technology should be within the scope of protection defined by the claims.

Claims

1. A method for reusing eSIM plug-in card-based cloud card resources, characterized in that, Includes the following steps: Read multiple card configuration files stored on the eSIM plug-in card, obtain the mapping relationship between each card configuration file and the eSIM plug-in card, the mapping relationship includes the card identifier code corresponding to the card configuration file and its corresponding eSIM plug-in card, as well as the status of the card configuration file; Send multiple card profiles stored on the eSIM plug-in card to the cloud server so that the cloud server allocates each card profile as an independent cloud card resource to the cloud card device; In response to the authentication request forwarded by the cloud server from the cloud card device, the card identification code contained in the authentication request is read, and the target card configuration file and its status are determined from the mapping relationship based on the card identification code; If the target card configuration file is active, the authentication response parameters are calculated using the configuration file. The authentication calculation result is sent to the cloud card device so that the cloud card device can complete the authentication. 2.The eSIM plug card based cloud card resource multiplexing method according to claim 1, characterized in that, A predetermined duration is used as a response time window. When authentication requests from multiple cloud card devices are received within the response time window, the target card configuration file and its status are determined from the mapping relationship based on the card identifier code in each authentication request. The cloud card authentication strategy is determined according to the receiving order of each authentication request and the status of each card configuration file. 3.The eSIM plug card based cloud card resource multiplexing method of claim 2, wherein, When multiple card identifiers corresponding to multiple cloud card device authentication requests belong to the same eSIM card, the cloud card authentication strategy is determined through the following steps: The first card configuration file that is active in the mapping relationship is selected as the target card configuration file for calculating authentication response parameters. After waiting for the first card configuration file to send the authentication calculation result to the corresponding cloud card device, the second card configuration file is selected as the target card configuration file according to the access order of the authentication request. The second card configuration file is activated, and the second card configuration file in the activated state is used as the target card configuration file to calculate the authentication response parameters. After the second card configuration file sends the authentication calculation result to the corresponding cloud card device, the third card configuration file is selected as the target card configuration file to calculate the authentication response parameters until the current response time window ends.

4. The cloud card resource reuse method based on eSIM plug-in card according to claim 3, characterized in that, Before activating the second card configuration file, the first card configuration file is deactivated, making it inactive, and the activation state of the first card configuration file in the mapping relationship is changed to inactive.

5. The cloud card resource reuse method based on eSIM plug-in card according to claim 2, characterized in that, When multiple card identifiers corresponding to multiple cloud card device authentication requests do not belong to the same eSIM card, the cloud card authentication strategy is determined through the following steps: Select multiple target card configuration files from the mapping relationship, calculate the authentication response parameters for the target card configuration files that are in an active state, and activate the target card configuration files that are in an inactive state in sequence before calculating the authentication response parameters.

6. The cloud card resource reuse method based on eSIM plug-in card according to claim 1, characterized in that, After the local configuration file assistant LPA changes the status of the target card configuration file, the status of the target card configuration file in the mapping relationship is modified in real time.

7. The cloud card resource reuse method based on eSIM plug-in card according to claim 1, characterized in that, If the target card configuration file determined from the mapping relationship is inactive, the target card configuration file is activated using the Local Configuration File Assistant (LPA) for authentication.

8. A cloud card resource reuse device based on an eSIM pluggable card, characterized in that, Includes the following modules: The network module is used to maintain a communication connection with the cloud server; The main control module is used to read multiple card configuration files stored on the eSIM plug-in card, obtain the mapping relationship between each card configuration file and the eSIM plug-in card, the mapping relationship includes the card identifier code corresponding to the card configuration file and its corresponding eSIM plug-in card, as well as the status of the card configuration file; send the multiple card configuration files stored on the eSIM plug-in card to the cloud server, so that the cloud server allocates each card configuration file as an independent cloud card resource to the cloud card device; respond to the authentication request forwarded by the cloud server from the cloud card device, read the card identification code contained in the authentication request, and determine the target card configuration file and its status from the mapping relationship based on the card identification code; if the target card configuration file is in an inactive state, activate the target card configuration file using the local configuration file assistant LPA before using it for authentication; if the target card configuration file is in an active state, calculate the authentication response parameters; and send the authentication calculation result to the cloud card device so that the cloud card device can complete the authentication. The LPA module is used to activate and deactivate the card configuration file using the Local Configuration File Assistant (LPA). The smart card resource module provides multiple card slots for inserting eSIM cards.

9. The cloud card resource multiplexing device based on eSIM pluggable card according to claim 8, characterized in that, The main control module is also used to, with a predetermined duration as a response time window, when authentication requests from multiple cloud card devices are received within the response time window, determine the target card configuration file and its status from the mapping relationship based on the card identifier code in each authentication request, and determine the cloud card authentication strategy according to the receiving order of each authentication request and the status of each card configuration file.

10. The cloud card resource multiplexing device based on eSIM pluggable card according to claim 9, characterized in that, The main control module is also used to determine the cloud card authentication strategy through the following steps when multiple card identifier codes corresponding to multiple cloud card device authentication requests belong to the same eSIM card: The first card configuration file that is active in the mapping relationship is selected as the target card configuration file for calculating authentication response parameters. After waiting for the first card configuration file to send the authentication calculation result to the corresponding cloud card device, the second card configuration file is selected as the target card configuration file according to the access order of the authentication request. The second card configuration file is activated, and the second card configuration file in the activated state is used as the target card configuration file to calculate the authentication response parameters. After the second card configuration file sends the authentication calculation result to the corresponding cloud card device, the third card configuration file is selected as the target card configuration file to calculate the authentication response parameters until the current response time window ends.

11. A method for using resources in a terminal device, characterized in that, Includes the following steps: Obtain cloud card resources sent by the server. The cloud card resources are card configuration files stored on the eSIM pluggable card. The card configuration files are allocated to the terminal device by the server as cloud card resources. An authentication request for network authentication is sent to the server, so that the server forwards the authentication request to the smart card management device. The smart card management device reads the card identification code contained in the authentication request, determines the target card configuration file and its status from the mapping relationship stored in the smart card management device based on the card identification code, and calculates the authentication response parameters using the target card configuration file in the active state. The mapping relationship includes the card identification code corresponding to the card configuration file and its corresponding eSIM card, as well as the activation status of the card configuration file. Receive the authentication response parameters sent by the server to complete the authentication process.

12. A terminal device, characterized in that, Includes the following modules: The acquisition module is used to receive cloud card resources sent by the server. The cloud card resources are card configuration files stored on the eSIM plug-in card. The server allocates the card configuration files as cloud card resources to the terminal device. The module sends an authentication request for network authentication to the server. The server forwards the authentication request to the smart card management device. The smart card management device reads the card identification code contained in the authentication request, determines the target card configuration file and its status from the mapping relationship stored in the smart card management device based on the card identification code, and calculates the authentication response parameters using the target card configuration file in the active state. The mapping relationship includes the card identification code corresponding to the card configuration file and its corresponding eSIM plug-in card, as well as the active state of the card configuration file. The authentication module is used to receive authentication response parameters sent by the server in order to complete the authentication process.

13. A communication device, characterized in that, It includes at least one processor and a memory, the memory storing a computer program, the at least one processor executing the computer program stored in the memory, causing the at least one processor to perform the cloud card resource reuse method based on an eSIM plug-in card as described in any one of claims 1 to 7.

Images