Configuration file management method and device, equipment and storage medium

Abstract

The embodiment of the invention relates to a configuration file management method and device, equipment and a storage medium, and the method comprises the steps: under the condition that a target eSE instruction is received through a target eSE physical interface, the target eSE instruction is routed to an eSE configuration file through a target eSE LSI mapped by the target eSE physical interface, so as to execute the target eSE instruction through the eSE configuration file; and under the condition that a target eSIM instruction is received through the target eSIM physical interface, determining a target eSIM configuration file pointed by the target eSIM instruction, and routing the target eSIM instruction to the target eSIM configuration file through a target eSIM LSI associated with the target eSIM configuration file so as to execute the target eSIM instruction through the target eSIM configuration file. According to the embodiment of the invention, the code reuse rate, hardware resource sharing and efficient configuration file management can be improved.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of smart card chip technology, and in particular to a configuration file management method, apparatus, device, and storage medium. Background Art

[0002] With the development of smart card chips, the integration of embedded Secure Element (eSE) and embedded Subscriber Identity (eSIM) has become a general trend. Currently, one integration solution is to use two independent chips to handle eSE functions and eSIM functions respectively and package the two independent chips through sealing technology, but this will lead to hardware redundancy and increased costs. In view of this, another integration solution has emerged, which integrates eSE functions and eSIM functions into a single chip. However, due to the incompatibility between the eSIM architecture and the eSE architecture, eSIM and eSE need to independently maintain their own Java Card platforms, resulting in low code reuse rate and the inability to share hardware resources, resulting in waste of area and power consumption. Summary of the Invention

[0003] In order to solve the above technical problems or at least partially solve the above technical problems, embodiments of the present disclosure provide a configuration file management method, apparatus, device, and storage medium.

[0004] A first aspect of an embodiment of the present disclosure provides a configuration file management method, which is applied to a combo chip integrating an eSE and an eSIM. The combo chip is deployed with a configuration file management platform, an eSE physical interface, and an eSIM physical interface. The configuration file management platform is deployed with multiple configuration files, including an eSE configuration file and an eSIM configuration file. Each eSE physical interface is mapped to an eSE LSI, each eSIM physical interface is mapped to at least one eSIM LSI, each eSE LSI is associated with the eSE configuration file, and each eSIM LSI is associated with an eSIM configuration file. The method includes:

[0005] In a case where a target eSE instruction is received through a target eSE physical interface, routing the target eSE instruction to the eSE profile via a target eSE LSI mapped to the target eSE physical interface, so as to execute the target eSE instruction through the eSE profile;

[0006] In a case where a target eSIM instruction is received through a target eSIM physical interface, a target eSIM profile to which the target eSIM instruction points is determined, and the target eSIM instruction is routed to the target eSIM profile via a target eSIM LSI associated with the target eSIM profile, so as to execute the target eSIM instruction through the target eSIM profile.

[0007] A second aspect of an embodiment of the present disclosure provides a configuration file management device, which is applied to a combo chip integrating an eSE and an eSIM. The combo chip is deployed with a configuration file management platform, an eSE physical interface, and an eSIM physical interface. The configuration file management platform is deployed with multiple configuration files, including an eSE configuration file and an eSIM configuration file. Each eSE physical interface is mapped to an eSE LSI, and each eSIM physical interface is mapped to at least one eSIM LSI. The eSE LSIs are associated with the eSE configuration file, and each eSIM LSI is associated with an eSIM configuration file. The device includes:

[0008] a first routing module, configured to, when receiving a target eSE instruction through a target eSE physical interface, route the target eSE instruction to the eSE configuration file via a target eSE LSI mapped to the target eSE physical interface, so as to execute the target eSE instruction through the eSE configuration file;

[0009] a second routing module configured to, upon receiving a target eSIM instruction through a target eSIM physical interface, determine a target eSIM profile to which the target eSIM instruction points, and route the target eSIM instruction to the target eSIM profile via a target eSIM LSI associated with the target eSIM profile, so as to execute the target eSIM instruction through the target eSIM profile.

[0010] A third aspect of an embodiment of the present disclosure provides an electronic device, comprising: a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the method of the first aspect above.

[0011] A fourth aspect of an embodiment of the present disclosure provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method of the first aspect described above can be implemented.

[0012] The technical solution provided by the embodiments of the present disclosure has the following advantages over the prior art:

[0013] An embodiment of the present disclosure is applied to a combination chip integrating an eSE and an eSIM. The combination chip is deployed with a profile management platform, an eSE physical interface, and an eSIM physical interface. Multiple profiles are deployed on the profile management platform, including an eSE profile and an eSIM profile. Each eSE physical interface is mapped to an eSE LSI, each eSIM physical interface is mapped to at least one eSIM LSI, each eSE LSI is associated with an eSE profile, and each eSIM LSI is associated with an eSIM profile. The method includes: upon receiving a target eSE instruction through a target eSE physical interface, routing the target eSE instruction to the eSE profile via a target eSE LSI mapped to the target eSE physical interface, so as to execute the target eSE instruction through the eSE profile; and upon receiving a target eSIM instruction through a target eSIM physical interface, determining a target eSIM profile to which the target eSIM instruction points, routing the target eSIM instruction to the target eSIM profile via a target eSIM LSI associated with the target eSIM profile, so as to execute the target eSIM instruction through the target eSIM profile. It can be seen that the above technical solution can be used as a special profile (i.e., eSE profile) in the eSIM architecture, so that eSIM and eSE use the same profile management platform, and through a unified LSI (i.e., Logical Security element interface) mechanism, multiple profiles (eSE profile and multiple eSIM profiles) deployed on the profile management platform can be efficiently managed, thereby improving code reuse, hardware resource sharing and efficient profile management. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0015] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0016] Figure 1 is a flow chart of a configuration file management method provided by an embodiment of the present disclosure;

[0017] Figure 2 This is a schematic diagram of the architecture of a combination chip provided by an embodiment of the present disclosure;

[0018] Figure 3is a schematic diagram of the architecture of another combination chip provided by an embodiment of the present disclosure;

[0019] Figure 4 This is a schematic diagram of the architecture of another combination chip provided by an embodiment of the present disclosure;

[0020] Figure 5 This is a logical diagram of configuration file switching provided by an embodiment of the present disclosure;

[0021] Figure 6 is another logical diagram of configuration file switching provided by an embodiment of the present disclosure;

[0022] Figure 7 This is another logical diagram of configuration file switching provided by an embodiment of the present disclosure;

[0023] Figure 8 This is a logical diagram of another configuration file switching provided by an embodiment of the present disclosure;

[0024] Figure 9 1 is a schematic diagram of the structure of a configuration file management device provided by an embodiment of the present disclosure;

[0025] Figure 10 It is a structural diagram of an electronic device in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0026] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features therein can be combined with each other in the absence of conflict.

[0027] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0028] Figure 1 This is a flowchart of a configuration file management method provided by an embodiment of the present disclosure. The method can be applied to a combination chip integrating eSE and eSIM. A configuration file management platform, an eSE physical interface, and an eSIM physical interface are deployed on the combination chip. Multiple configuration files are deployed on the configuration file management platform. The multiple configuration files include eSE configuration files and eSIM configuration files. Each eSE physical interface maps to an eSE LSI, each eSIM physical interface maps to at least one eSIM LSI, each eSE LSI is associated with an eSE configuration file, and each eSIM LSI is associated with an eSIM configuration file.

[0029] Specifically, the combo chip integrates the eSE function and the eSIM function. In other words, the eSE and the eSIM are integrated into the same chip (ie, the combo chip).

[0030] Specifically, the eSE physical interface is a physical interface used by the eSE. Optionally, the eSE physical interface includes an SPI interface, an I2C interface, and / or a UART interface, but is not limited thereto.

[0031] Specifically, the eSIM physical interface is a physical interface used by the eSIM. Optionally, the eSIM physical interface includes a 7816 interface, etc., but is not limited thereto.

[0032] Specifically, the profile management platform allows for the simultaneous deployment of multiple profiles. In other words, the profile management platform acts as a container for multiple profiles. Furthermore, the profile management platform can dynamically switch between different profiles based on instructions received by the combo chip. Optionally, the profile management platform includes, but is not limited to, a Java Card platform.

[0033] Specifically, a profile is an independent runtime environment, including resources such as the application registry, package registry, and file system. Each profile is self-contained, with its own set of applications and settings, ensuring that resources between profiles are not shared and are isolated from each other. This provides a foundation for security: even if two profiles contain applications with the same AID (Application Identifier), they remain completely independent and will not interfere with each other.

[0034] The eSE configuration file is a configuration file that implements the eSE function, and the eSIM configuration file is a configuration file that implements the eSIM function.

[0035] Specifically, the LSI is responsible for managing the system context of the interface operation, including the UICC platform context (including operations and data processing related to the UICC), the VM operation context (including the operating environment of the virtual machine (such as the Java Card VM), including its status, memory allocation, etc.), and the profile management platform (such as the Java Card platform) context (including the executing application and its status), etc., but is not limited to these.

[0036] A single LSI can only correspond to one profile at a time, but a profile can have multiple LSIs pointing to it. Specifically, all eSE LSIs mapped to an eSE physical interface point to an eSE profile; an eSIM physical interface can be divided into multiple eSIM LSIs, and different eSIM LSIs point to different eSIM profiles.

[0037] For example, Figure 2 is a schematic diagram of the architecture of a combination chip provided by an embodiment of the present disclosure. Figure 3 is a schematic diagram of the architecture of another combination chip provided by an embodiment of the present disclosure, such as Figure 2 and Figure 3 As shown, the physical interface in the combination chip is mapped to the LSI, and the LSI points to the configuration file (ie Profile). Specifically, eSE is deployed as a special configuration file in the configuration file management platform. Each eSE physical interface (such as SPI interface and I2C interface, etc.) can correspond to an LSI (ie eSELSI), and are all configured to correspond to the eSE configuration file. And. Each eSIM physical interface (such as 7816 interface, etc.) corresponds to multiple LSIs (ie eSIM LSI), and the eSIM LSI can dynamically bind different eSIM configuration files. In this way, eSE and eSIM can share the same configuration file management platform (such as Java Card platform), and the firewall mechanism can be used to isolate different configuration files, thereby effectively realizing the isolated coexistence of eSE and eSIM. Further exemplary, Figure 4 This is a schematic diagram of the architecture of another combination chip provided by an embodiment of the present disclosure, such as Figure 3 and Figure 4 As shown in the figure, the physical interfaces include the 7816 interface, SPI interface, and I2C interface. The 7816 interface is divided into two LSIs, LSI0 and LSI1. The SPI interface is mapped to one LSI (i.e., LSI2), and the I2C interface is mapped to one LSI (i.e., LSI3). LSI0 points to an eSIM profile (i.e., eSIM Profile0), LSI1 points to an eSIM profile (i.e., eSIM Profile1), and both LSI2 and LSI3 point to an eSE profile (i.e., eSEProfile).

[0038] Specifically, the combination chip can be integrated into an electronic device, which can be exemplarily understood as a smart device such as a mobile phone, a tablet computer, a wearable device, etc.

[0039] like Figure 1 As shown, the method provided in this embodiment includes the following steps:

[0040] S110 . When a target eSE instruction is received through the target eSE physical interface, the target eSE instruction is routed to the eSE configuration file via the target eSE LSI mapped to the target eSE physical interface, so as to execute the target eSE instruction through the eSE configuration file.

[0041] Specifically, the target eSE instruction is an eSE instruction received by the combination chip, wherein the eSE instruction is an instruction for implementing an eSE function.

[0042] Specifically, the target eSE physical interface is the eSE physical interface that receives the target eSE instruction, and the target eSE LSI is the eSE LSI mapped to the target eSE physical interface.

[0043] Specifically, if the combination chip receives a target eSE instruction through the target eSE physical interface, it switches the current profile (i.e., the profile currently executing the instruction) to the eSE profile and switches the current LSI (i.e., the LSI currently routing the instruction) to the target eSE LSI, so that the target eSE LSI routes the target eSE instruction to the eSE profile and executes the target eSE instruction through the eSE profile.

[0044] In some embodiments, if the current configuration file of the currently executed instruction is the current eSIM configuration file and the current context information currently used is the context information recorded by the current eSIM LSI, the current eSIM LSI is used to route the instruction to the current eSIM configuration file and execute the target eSE instruction through the eSE configuration file, including:

[0045] Switch the current profile from the current eSIM profile to the eSE profile, and switch the current context information from the context information recorded by the current eSIM LSI to the context information recorded by the target eSE LSI;

[0046] Execute target eSE instructions through eSE configuration files.

[0047] Specifically, the current eSIM configuration file is the eSIM configuration file that is currently executing the instruction.

[0048] Specifically, the current context information is the context information used by the currently executed instruction.

[0049] Specifically, the current eSIM LSI is the eSIM LSI associated with the current eSIM configuration file.

[0050] For example, Figure 5 This is a logical diagram of a configuration file switching provided by an embodiment of the present disclosure, such as Figure 4 and Figure 5 As shown, the current profile is eSIM Profile0 ( Figure 4In the example, the current LSI is LSI0, the current context information is the context information recorded by LSI0, and eSIM Profile0 executes the eSIM instructions routed from LSI0 by 7816 interface. If the combination chip receives the target eSE instruction through the SPI interface (i.e., the target eSE physical interface) at this time, the current profile is switched to eSE Profile, the current LSI is switched to LSI2, and the current context information is switched to the context information recorded by LSI2, and the target eSE instruction routed from LSI2 by SPI interface is executed through the eSE Profile.

[0051] In some embodiments, an eSE configuration file includes multiple eSE interfaces, where different eSE interfaces correspond to different applications. If the current interface for executing a current instruction is the current eSE interface and the current context information currently used is the context information recorded by the current eSELSI, the current eSE LSI is used to route the instruction to the current eSE interface, and executing the target eSE instruction through the eSE configuration file includes:

[0052] Switch the current interface from the current eSE interface to the target eSE interface, and switch the current context information from the context information recorded by the current eSELSI to the context information recorded by the target eSE LSI;

[0053] Execute target eSE instructions through the target eSE interface.

[0054] Specifically, the current eSE interface is the eSE interface that is currently executing an instruction.

[0055] Specifically, the current eSE LSI is the eSE LSI associated with the current eSE interface.

[0056] Specifically, the target eSE interface is an eSE interface associated with the target eSE physical interface and used to execute the target eSE instruction.

[0057] For example, Figure 6 This is another logical diagram of configuration file switching provided by an embodiment of the present disclosure, such as Figure 4 and Figure 6As shown, the current profile is eSE Profile, the current eSE interface is the eSE interface associated with LSI2 and used to execute the current eSE instruction, the current LSI is LSI2, the current context information is the context information recorded by LSI2, and the current eSE interface executes the eSE instruction routed from the SPI interface by LSI2. If the combination chip receives the target eSE instruction through the I2C interface (i.e., the target eSE physical interface) at this time, the current eSE interface is switched to the eSE interface associated with LSI3 and used to execute the target eSE instruction (i.e., the target eSE interface), the current LSI is switched to LSI3, and the current context information is switched to the context information recorded by LSI3, and the target eSE instruction routed from the I2C interface by LSI3 is executed through the target eSE interface.

[0058] It is understood that by configuring the combo chip to automatically route instructions to the eSE profile (i.e., eSE Profile) for processing via the target LSI when receiving instructions via the target eSE physical interface, the profile management platform can automatically complete instruction routing and profile switching based on the type of physical interface receiving the instructions. Furthermore, by configuring the eSE profile to include multiple eSE interfaces, when the combo chip receives instructions via the target eSE physical interface, the instructions are automatically routed to the target eSE interface for processing via the target LSI, enabling support for multiple eSE physical interfaces to operate simultaneously (i.e., parallel processing of multiple eSE physical interfaces).

[0059] S120: When a target eSIM instruction is received through the target eSIM physical interface, determine a target eSIM profile to which the target eSIM instruction points, and route the target eSIM instruction to the target eSIM profile via the target eSIM LSI associated with the target eSIM profile, so as to execute the target eSIM instruction through the target eSIM profile.

[0060] Specifically, the target eSIM instruction is an eSIM instruction received by the combination chip, wherein the eSIM instruction is an instruction for implementing an eSIM function.

[0061] Specifically, the target eSIM physical interface is an eSIM physical interface that receives the target eSIM instruction.

[0062] Specifically, the target eSIM profile is an eSIM profile used to execute the target eSIM instruction, and the target eSIM LSI is an eSIM LSI associated with the target eSIM profile.

[0063] Specifically, if the combination chip receives a target eSIM instruction through the target eSIM physical interface, the current profile currently running is switched to the target eSIM profile and the current LSI is switched to the target eSIM LSI, so that the target eSIM LSI routes the target eSIM instruction to the target eSIM profile and executes the target eSIM instruction through the target eSIM profile.

[0064] Optionally, the eSIM instruction includes a MANAGE LSI instruction and a non-MANAGE LSI instruction, wherein determining the target eSIM configuration file pointed to by the target eSIM instruction includes:

[0065] If the target eSIM command is a MANAGE LSI command, the eSIM configuration file specified by the target eSIM command is used as the target eSIM configuration file;

[0066] If the target eSIM command is not a MANAGE LSI command, the eSIM profile specified by the last received MANAGE LSI command is used as the target eSIM profile.

[0067] Specifically, eSIM instructions are divided into MANAGE LSI instructions and non-MANAGE LSI instructions (i.e., eSIM instructions other than MANAGE LSI instructions). MANAGE LSI instructions are used to indicate which eSIM profile will execute the next non-MANAGE LSI instruction (i.e., the non-MANAGE LSI instruction received before the next MANAGE LSI instruction is received).

[0068] Specifically, when a MANAGE LSI command is received through the target eSIM physical interface, the current profile is switched to the eSIM profile specified by the MANAGE LSI command (i.e., the target eSIM profile); when a non-MANAGE LSI command is received through the target eSIM physical interface, it is automatically routed to the most recently switched eSIM profile for processing.

[0069] It is understandable that by setting the MANAGE LSI command to dynamically switch to the target eSIM profile, flexible and simple switching of the eSIM profile can be achieved.

[0070] In some embodiments, the eSE configuration file includes multiple eSE interfaces. If the current interface for executing the instruction is the current eSE interface and the current context information currently used is the context information recorded by the current eSE LSI, the current eSELSI is used to route the instruction to the current eSE interface, and the target eSIM instruction is executed through the target eSIM configuration file, including:

[0071] Switch the current profile from the eSE profile to the target eSIM profile, and switch the current context information from the context information recorded by the current eSE LSI to the context information recorded by the target eSIM LSI;

[0072] Execute target eSIM commands via target eSIM profile.

[0073] For example, Figure 7 This is a logical diagram of a configuration file switching provided by an embodiment of the present disclosure, such as Figure 4 and Figure 7 As shown, the current profile is eSE Profile, the current LSI is LSI2, and the eSE Profile executes the eSE instructions routed from the SPI interface by LSI2. If the combination chip receives the target eSIM instruction through the 7816 interface (i.e., the target eSIM physical interface), then after determining that the target eSIM profile is eSIM Profile0 ( Figure 4 After that, the current profile is switched to eSIM Profile0, the current LSI is switched to LSI0, and the current context information is switched to the context information recorded by LSI0, and the target eSIM instruction routed from LSI0 from the 7816 interface is executed through eSIM Profile0.

[0074] In some embodiments, if the current configuration file for the currently executed instruction is the current eSIM configuration file and the current context information currently used is the context information recorded by the current eSIM LSI, the current eSIM LSI is configured to route the instruction to the current eSIM configuration file and execute the target eSIM instruction through the target eSIM configuration file, including:

[0075] Switch the current profile from the current eSIM profile to the target eSIM profile, and switch the current context information from the context information recorded by the current eSIM LSI to the context information recorded by the target eSIM eSIM;

[0076] Execute target eSIM commands via target eSIM profile.

[0077] For example, Figure 8 This is another logical diagram of configuration file switching provided by an embodiment of the present disclosure, such as Figure 4 and Figure 8 As shown, the current profile is eSIM Profile0 ( Figure 4The current LSI is LSI0, the current context information is the context information recorded by LSI0, and eSIM Profile0 executes the eSIM instruction routed from LSI0 via the 7816 interface. If the combination chip receives the target eSE instruction through the 7816 interface (i.e., the target eSIM physical interface) and determines that the target eSIM profile is eSIM Profile1 ( Figure 4 After that, the current profile is switched to eSIM Profile1, the current LSI is switched to LSI1, and the current context information is switched to the upper and lower information recorded by LSI1, and the target eSIM instruction routed from LSI0 from the 7816 interface is executed through eSIM Profile1.

[0078] It can be understood that by setting the combination chip to automatically route the instruction to the target eSIM profile processing through the target LSI when receiving the instruction through the target eSIM physical interface, the profile management platform can automatically complete the instruction routing and profile switching based on the type of physical interface that receives the instruction and the type of instruction.

[0079] The disclosed embodiments can use eSE as a special profile (i.e., eSE profile) in the eSIM architecture, allowing eSIM and eSE to use the same profile management platform. Furthermore, a unified LSI mechanism is used to efficiently manage multiple profiles (eSE profile and multiple eSIM profiles) deployed on the profile management platform, thereby achieving code reuse, hardware resource sharing, and efficient profile management.

[0080] To sum up, the embodiment of the present disclosure incorporates eSE as a special Profile into the MEP management system of eSIM, and makes the eSE LSIs mapped to all eSE physical interfaces of eSE point to the same Profile (i.e., eSE Profile), and the eSIM LSIs mapped to the eSIM physical interfaces of eSIM can be dynamically switched. In this way, unified management of eSE Profile and eSIM Profile can be achieved through the LSI mechanism. The configuration file management platform automatically completes instruction routing and Profile switching based on the type of physical interface, realizes seamless switching between eUICC and eSE instructions, and supports parallel processing of multiple physical interfaces of eSE, significantly improves code reuse rate, reduces development cost, optimizes hardware resource utilization, reduces chip area, and realizes efficient collaboration between eSIM and eSE, maintaining security isolation between profiles.

[0081] Figure 9This is a schematic diagram of the structure of a configuration file management device provided by an embodiment of the present disclosure. The configuration file management device can be understood as the above-mentioned combination chip or some functional modules in the above-mentioned combination chip. Figure 9 As shown, the configuration file management device includes:

[0082] a first routing module 910 configured to, when receiving a target eSE instruction through a target eSE physical interface, route the target eSE instruction to the eSE configuration file via a target eSE LSI mapped to the target eSE physical interface, so as to execute the target eSE instruction through the eSE configuration file;

[0083] The second routing module 920 is configured to, upon receiving a target eSIM instruction through the target eSIM physical interface, determine a target eSIM profile to which the target eSIM instruction points, and route the target eSIM instruction to the target eSIM profile via the target eSIM LSI associated with the target eSIM profile, so as to execute the target eSIM instruction through the target eSIM profile.

[0084] Optionally, the eSIM instruction includes a MANAGE LSI instruction and a non-MANAGE LSI instruction, wherein the second routing module 920 includes a first determining submodule, the first determining submodule being configured to determine a target eSIM profile pointed to by the target eSIM instruction, wherein the first determining submodule is specifically configured to, if the target eSIM instruction is the MANAGE LSI instruction, use the eSIM profile specified by the target eSIM instruction as the target eSIM profile;

[0085] If the target eSIM command is the non-MANAGE LSI command, the eSIM configuration file specified by the last received MANAGE LSI command is used as the target eSIM configuration file.

[0086] Optionally, the first routing module 910 includes a first execution submodule, the first execution submodule being configured to execute the target eSE instruction through the eSE configuration file, wherein the first execution submodule is specifically configured to, if the current configuration file of the currently executed instruction is the current eSIM configuration file and the current context information currently used is the context information recorded by the current eSIM LSI, the current eSIM LSI being configured to route the instruction to the current eSIM configuration file, and executing the target eSE instruction through the eSE configuration file includes:

[0087] Switching the current profile from the current eSIM profile to the eSE profile, and switching the current context information from the context information recorded by the current eSIM LSI to the context information recorded by the target eSE LSI;

[0088] The target eSE instruction is executed through the eSE configuration file.

[0089] Optionally, the eSE configuration file includes multiple eSE interfaces, wherein the first routing module 910 includes a second execution submodule, the second execution submodule being configured to execute the target eSE instruction through the eSE configuration file, wherein the second execution submodule is specifically configured to, if the current interface for currently executing the instruction is the current eSE interface and the current context information currently used is the context information recorded by the current eSE LSI, the current eSE LSI being configured to route the instruction to the current eSE interface, and executing the target eSE instruction through the eSE configuration file includes:

[0090] Switching the current interface from the current eSE interface to the target eSE interface, and switching the current context information from the context information recorded in the current eSE LSI to the context information recorded in the target eSE LSI;

[0091] The target eSE instruction is executed through the target eSE interface.

[0092] Optionally, the eSE configuration file includes multiple eSE interfaces, and the second routing module 920 includes a third execution submodule, the third execution submodule being configured to execute the target eSIM instruction through the target eSIM configuration file. The third execution submodule is specifically configured to, if the current interface for currently executing the instruction is the current eSE interface and the current context information currently used is the context information recorded by the current eSE LSI, route the instruction to the current eSE interface. Executing the target eSIM instruction through the target eSIM configuration file includes:

[0093] Switching the current profile from the eSE profile to the target eSIM profile, and switching the current context information from the context information recorded by the current eSE LSI to the context information recorded by the target eSIM LSI;

[0094] The target eSIM command is executed through the target eSIM profile.

[0095] Optionally, the second routing module 920 includes a fourth execution submodule, the fourth execution submodule being configured to execute the target eSIM instruction through the target eSIM configuration file. Specifically, if the current configuration file for the currently executed instruction is the current eSIM configuration file and the current context information currently used is the context information recorded by the current eSIM LSI, the current eSIM LSI being configured to route the instruction to the current eSIM configuration file. The execution of the target eSIM instruction through the target eSIM configuration file includes:

[0096] Switching the current profile from the current eSIM profile to the target eSIM profile, and switching the current context information from the context information recorded by the current eSIM LSI to the context information recorded by the target eSIM;

[0097] The target eSIM command is executed through the target eSIM profile.

[0098] Optionally, the configuration file management platform includes a Java Card platform;

[0099] The eSE physical interface includes an SPI interface, an I2C interface and / or a UART interface;

[0100] The eSIM physical interface includes a 7816 interface.

[0101] The device provided in this embodiment can execute the method of any of the above embodiments, and its execution method and beneficial effects are similar, which will not be repeated here.

[0102] An embodiment of the present disclosure further provides an electronic device, comprising: a memory storing a computer program; and a processor for executing the computer program. When the computer program is executed by the processor, the method of any of the above embodiments can be implemented.

[0103] For example, Figure 10 This is a schematic diagram of the structure of an electronic device in the embodiment of the present disclosure. Figure 10 , which shows a schematic structural diagram of an electronic device 1000 suitable for implementing the embodiments of the present disclosure. The electronic device 1000 in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 10The electronic device shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0104] like Figure 10 As shown, the electronic device 1000 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1008 into a random access memory (RAM) 1003. Various programs and data required for the operation of the electronic device 1000 are also stored in the RAM 1003. The processing device 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0105] Typically, the following devices may be connected to the I / O interface 1005: an input device 1006 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 1007 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1008 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 may allow the electronic device 1000 to communicate with other devices wirelessly or by wire to exchange data. Figure 10 The electronic device 1000 is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0106] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 1009, or installed from the storage device 1008, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0107] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0108] In some embodiments, the client and server can communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0109] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0110] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the method described in any one of the above embodiments.

[0111] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0112] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0113] The units involved in the embodiments described in this disclosure may be implemented in software or hardware, wherein the name of a unit does not necessarily limit the unit itself.

[0114] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0115] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0116] The embodiments of the present disclosure further provide a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method of any of the above embodiments can be implemented. The execution method and beneficial effects are similar and will not be repeated here.

[0117] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0118] The foregoing description is intended only to provide specific embodiments of the present disclosure, intended to enable those skilled in the art to understand and implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the embodiments described herein, but rather to be construed in the broadest manner consistent with the principles and novel features disclosed herein.

Claims

1. A configuration file management method, characterized in that: The method is applied to a combination chip integrating an eSE and an eSIM, wherein a profile management platform, an eSE physical interface, and an eSIM physical interface are deployed on the combination chip, multiple profiles are deployed on the profile management platform, and the multiple profiles include an eSE profile and an eSIM profile. Each of the eSE physical interfaces is mapped to an eSE LSI, and each of the eSIM physical interfaces is mapped to at least one eSIM LSI. The eSE LSIs are associated with the eSE profiles, and each of the eSIM LSIs is associated with an eSIM profile. In a case where a target eSE instruction is received through a target eSE physical interface, routing the target eSE instruction to the eSE profile via a target eSE LSI mapped to the target eSE physical interface, so as to execute the target eSE instruction through the eSE profile; In a case where a target eSIM instruction is received through a target eSIM physical interface, a target eSIM profile to which the target eSIM instruction points is determined, and the target eSIM instruction is routed to the target eSIM profile via a target eSIM LSI associated with the target eSIM profile, so as to execute the target eSIM instruction through the target eSIM profile.

2. The method according to claim 1, characterized in that The eSIM command includes a MANAGE LSI command and a non-MANAGE LSI command, wherein determining the target eSIM configuration file pointed to by the target eSIM command includes: If the target eSIM instruction is the MANAGE LSI instruction, using the eSIM configuration file specified by the target eSIM instruction as the target eSIM configuration file; If the target eSIM command is the non-MANAGE LSI command, the eSIM configuration file specified by the last received MANAGE LSI command is used as the target eSIM configuration file.

3. The method according to claim 1, characterized in that If the current configuration file for the currently executed instruction is the current eSIM configuration file and the current context information currently used is the context information recorded by the current eSIMLSI, the current eSIMLSI is used to route the instruction to the current eSIM configuration file, and executing the target eSE instruction by using the eSE configuration file includes: Switching the current profile from the current eSIM profile to the eSE profile, and switching the current context information from the context information recorded by the current eSIM LSI to the context information recorded by the target eSE LSI; The target eSE instruction is executed through the eSE configuration file.

4. The method according to claim 1, wherein The eSE configuration file includes multiple eSE interfaces. If the current interface for currently executing an instruction is the current eSE interface and the current context information currently used is the context information recorded by the current eSELSI, the current eSELSI is used to route the instruction to the current eSE interface. Executing the target eSE instruction using the eSE configuration file includes: Switching the current interface from the current eSE interface to the target eSE interface, and switching the current context information from the context information of the current eSELSI record to the context information of the target eSELSI record; The target eSE instruction is executed through the target eSE interface.

5. The method according to claim 1, wherein The eSE configuration file includes multiple eSE interfaces. If the current interface for currently executing the instruction is the current eSE interface and the current context information currently used is the context information recorded by the current eSELSI, the current eSELSI is used to route the instruction to the current eSE interface. Executing the target eSIM instruction using the target eSIM configuration file includes: Switching the current profile from the eSE profile to the target eSIM profile, and switching the current context information from the context information recorded by the current eSELSI to the context information recorded by the target eSIMLSI; The target eSIM command is executed through the target eSIM profile.

6. The method according to claim 1, characterized in that If the current configuration file for the currently executed instruction is the current eSIM configuration file and the current context information currently used is the context information recorded by the current eSIMLSI, the current eSIMLSI is used to route the instruction to the current eSIM configuration file, and executing the target eSIM instruction using the target eSIM configuration file includes: Switching the current profile from the current eSIM profile to the target eSIM profile, and switching the current context information from the context information recorded by the current eSIMLSI to the context information recorded by the target eSIM; The target eSIM command is executed through the target eSIM profile.

7. The method according to any one of claims 1 to 6, characterized in that The configuration file management platform includes a JavaCard platform; The eSE physical interface includes an SPI interface, an I2C interface and / or a UART interface; The eSIM physical interface includes a 7816 interface.

8. A configuration file management device, characterized in that: Applicable to a combination chip integrating eSE and eSIM, wherein a profile management platform, an eSE physical interface, and an eSIM physical interface are deployed on the combination chip, multiple profiles are deployed on the profile management platform, and the multiple profiles include an eSE profile and an eSIM profile. Each of the eSE physical interfaces is mapped to an eSE LSI, and each of the eSIM physical interfaces is mapped to at least one eSIM LSI. The eSE LSIs are associated with the eSE profiles, and each of the eSIM LSIs is associated with one of the eSIM profiles. The apparatus includes: a first routing module, configured to, when receiving a target eSE instruction through a target eSE physical interface, route the target eSE instruction to the eSE configuration file via a target eSE LSI mapped to the target eSE physical interface, so as to execute the target eSE instruction through the eSE configuration file; a second routing module configured to, upon receiving a target eSIM instruction through a target eSIM physical interface, determine a target eSIM profile to which the target eSIM instruction points, and route the target eSIM instruction to the target eSIM profile via a target eSIM LSI associated with the target eSIM profile, so as to execute the target eSIM instruction through the target eSIM profile.

9. An electronic device, characterized in that: include: A processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor performs the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images