ESE and eSIM combined device, system operation method, device and equipment

Abstract

The embodiment of the invention relates to an eSE and eSIM combined device and a system operation method, device and equipment, the eSE and eSIM combined device comprises an NFC Frontend and an SE which are integrated in the same chip, the SE comprises a Flash and an RAM, a software system architecture in the SE comprises an S core and an NS core, and the S core comprises a Main OS; the NS core comprises an eSE XOS and an eSIM XOS; the eSE XOS comprises an eSECODE and an eSEAsset, and the eSECODE comprises an eSE virtual machine, an eSE stack resource and an eSEeSEEntry module; the eSIM XOS comprises an eSIMCODE and an eSIMAsset, and the eSIMCODE comprises an eSIM virtual machine, an eSIM stack resource and an eSIM Entry module. According to the embodiment of the invention, physical isolation of the eSE and the eSIM is realized, and the problem of data leakage risk caused by poor data isolation due to all-in-one of NFC and eSIM service participants can be improved.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of security chip technology, and more particularly to an eSE and eSIM combination device, a system operation method, a device, and a device. Background Art

[0002] At present, mobile phones, bracelets and other wearable devices and IoT terminal devices have put forward strong demands for NFC, eSIM and other chips with higher integration, smaller size, lower cost and lower energy consumption. In response to this demand, all-in-one SE has gradually become a trend. At present, NFC+SE is a mature matching model, that is, NFC is responsible for connection and communication, and SE is responsible for the implementation of security services. For the convenience of description, eSE is usually used in this field to represent NFC SE.

[0003] The underlying platform implementations of eSIM and eSE are cross-industry solutions based on javacard+globalplatform technology. Such all-in-one products span multiple industries, and different participants may worry that a failure in another industry's solution will cause a chain reaction. Therefore, the isolation of the corresponding systems of each industry is the key technology to achieve all-in-one, and has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] In order to solve the above technical problems or at least partially solve the above technical problems, the embodiments of the present disclosure provide an eSE and eSIM combination device, a system operation method, an apparatus and a device.

[0005] A first aspect of an embodiment of the present disclosure provides an eSE and eSIM combination device, including: an NFC Frontend and a SE integrated in the same chip, the SE including Flash and RAM, and the software system architecture in the SE including:

[0006] An S core, wherein the S core includes a Main OS, and the Main OS is stored in the Flash and protected by an MPU mechanism;

[0007] NS core, the NS core including eSE XOS and eSIM XOS;

[0008] The eSE XOS includes eSECODE and eSEAsset, the eSECODE is stored in the Flash and protected by the MPU mechanism, the eSEAsset is stored in the RAM and the Flash and protected by the MPU mechanism, the eSECODE includes an eSE virtual machine, eSE stack resources and an eSEeSEEntry module, and the eSE virtual machine schedules the Main OS through the eSEEntry module system;

[0009] The eSIM XOS includes eSIMCODE and eSIMAsset, the eSIM CODE is stored in the Flash and protected by the MPU mechanism, the eSIM Asset is stored in the RAM and the Flash and protected by the MPU mechanism, the eSIMCODE includes an eSIM virtual machine, eSIM stack resources and an eSIM Entry module, and the eSIM virtual machine schedules the Main OS through the eSIM Entry module system.

[0010] A second aspect of an embodiment of the present disclosure provides a system operation method, which is applied to the eSE and eSIM combination device described in the first aspect, wherein the eSE XOS and the eSIM XOS share the same static code of JavaCard and GlobalPlatform, and the method includes:

[0011] An eSE operating domain context is allocated to the eSE XOS and an eSIM operating domain context is allocated to the eSIM XOS, wherein the operating domain context includes: dedicated XOS code, dedicated NVM storage space, dedicated RAM storage space and dedicated global variables.

[0012] A second aspect of an embodiment of the present disclosure provides a system operation device, which is applied to the eSE and eSIM combination device described in the first aspect, wherein the eSE XOS and the eSIM XOS share the same static code of JavaCard and GlobalPlatform, and the device includes:

[0013] The allocation module is used to allocate an eSE context to the eSE XOS and an eSIM context to the eSIM XOS, wherein the context includes: dedicated XOS code, dedicated NVM storage space, dedicated RAM storage space and dedicated global variables.

[0014] A fourth aspect of an embodiment of the present disclosure provides an electronic device, which includes the eSE and eSIM combination device described in the first aspect.

[0015] Compared with the prior art, the technical solution provided by the embodiments of the present disclosure has the following advantages:

[0016] In an embodiment of the present disclosure, an eSE and eSIM combination device includes: an NFC Frontend and a SE integrated in the same chip, the SE includes Flash and RAM, and the software system architecture in the SE includes: an S core, the S core includes a Main OS, and the Main OS is stored in the Flash and protected by an MPU mechanism; an NS core, the NS core includes an eSE XOS and an eSIM XOS; the eSE XOS includes an eSE CODE and an eSE Asset, the eSE CODE is stored in the Flash and protected by an MPU mechanism, the eSE Asset is stored in the RAM and the Flash and protected by the MPU mechanism, the eSE CODE includes an eSE virtual machine, an eSE stack resource, and an eSE eSE Entry module, and the eSE virtual machine schedules the Main OS through the eSE Entry module system; the eSIM XOS includes an eSIM CODE and an eSIM Asset, the eSIM CODE is stored in the Flash and protected by an MPU mechanism, the eSIM Asset is stored in the RAM and the Flash and protected by the MPU mechanism, the eSIM CODE includes an eSIM virtual machine, an eSIM stack resource, and an eSIM Entry module, and the eSIM virtual machine schedules the Main OS through the eSIMEntry module system. It can be seen that the above technical solution is adopted to realize that eSE (i.e. NFC SE) and eSIM are located in the same SE chip, and the eSE and eSIM are physically isolated through TrustZone-M, MPU, Mapping and other mechanisms, which is conducive to the solutions (i.e. services) of different industries to run safely in the same SE chip, thereby achieving the integration of eSE and eSIM to meet the requirements of smaller physical size, and helping to improve the risk of data leakage caused by poor data isolation due to the integration of NFC and eSIM service participants. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] 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.

[0018] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0019] Figure 1 is a structural schematic diagram of an eSE and eSIM combination device provided by an embodiment of the present disclosure;

[0020] Figure 2 is a schematic diagram of a software system architecture in a SE provided by an embodiment of the present disclosure;

[0021] Figure 3 is a flow chart of a system operation method provided by an embodiment of the present disclosure;

[0022] Figure 4 It is a schematic diagram of the code structure and calling relationship of eSEXOS, eSIM XOS and Main OS provided by an embodiment of the present disclosure;

[0023] Figure 5 It is a schematic diagram of an isolation design of a BASE PKG, an eSEPKG, and an eUICC PKG provided in an embodiment of the present disclosure;

[0024] Figure 6 It is a schematic diagram of the structure of a dedicated NVM storage space corresponding to an eSE XOS and an eSIM XOS respectively provided in an embodiment of the present disclosure;

[0025] Figure 7 It is a switching logic diagram of a dedicated global variable provided by an embodiment of the present disclosure;

[0026] Figure 8 is a schematic diagram of domain state switching provided by an embodiment of the present disclosure;

[0027] Fig. 9 is a switching flow chart of an eSIM task switching to an eSE task provided by an embodiment of the present disclosure;

[0028] Fig.10 is a schematic diagram of resetting a software system in a SE provided by an embodiment of the present disclosure;

[0029] Fig.11 It is a structural diagram of a system operation device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] 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 in the embodiments can be combined with each other without conflict.

[0031] 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.

[0032] First, the eSE and eSIM combination device provided by the embodiment of the present disclosure is described in detail.

[0033] The embodiment of the present disclosure provides an eSE and eSIM combination device, including: an NFCFrontend and an SE integrated in the same chip, the SE including Flash and RAM, and the software system architecture in the SE including:

[0034] S core, the S core includes the Main OS, which is stored in Flash and protected by the MPU mechanism;

[0035] NS core, NS core includes eSE XOS and eSIM XOS;

[0036] eSE XOS includes eSECODE and eSEAsset. eSECODE is stored in Flash and protected by MPU mechanism. eSEAsset is stored in RAM and Flash and protected by MPU mechanism. eSECODE includes eSE virtual machine, eSE stack resources and eSEeSEEntry module. eSE virtual machine schedules Main OS through eSE Entry module system.

[0037] eSIM XOS includes eSIMCODE and eSIMAsset. eSIM CODE is stored in Flash and protected by MPU mechanism. eSIM Asset is stored in RAM and Flash and protected by MPU mechanism. eSIM CODE includes eSIM virtual machine, eSIM stack resources and eSIM Entry module. The eSIM virtual machine schedules Main OS through the eSIM Entry module system.

[0038] For example, Figure 1 is a schematic diagram of the structure of an eSE and eSIM combination device provided by an embodiment of the present disclosure. Figure 1 , the eSE and eSIM combination device includes an NFC Frontend ( Figure 1 The yellow area in the figure) and SE( Figure 1 The purple area in the figure). The NFC Frontend is responsible for radio frequency communication. The SE chip is responsible for two cross-industry solutions: eSE and eSIM.

[0039] Specifically, NFC Frontend is the NFC front-end module, which is responsible for processing the physical layer and link layer functions of NFC communication.

[0040] Specifically, SE includes Flash and RAM, where Flash is a non-volatile memory, Flash is physically separated into Flash0 and Flash1, RAM is a volatile memory, RAM is physically separated into RAM0 and RAM1, eSE domain includes Flash0 and RAM0, eSE domain is a logical area in SE, used to store and process eSE service data, eSEXOS is located in the eSE domain, eSIM includes Flash1 and RAM1, eSIM domain is a logical area in SE, used to store and process eSIM service data, eSIMXOS is located in the eSIM domain. It should be noted that each SIM corresponds to an eSIM domain and eSIMXOS.

[0041] Of course, continue to see Figure 1 , the eSE and eSIM combination device may also include Shared, ROM, PKE and / or CPU, but is not limited to this. Among them, Shared is a shared storage area. ROM is a non-volatile memory. RKE is a remote keyless entry system (Remote Keyless Entry), which is used for remote control of equipment such as automobiles. CPU is a central processing unit, which is responsible for executing instructions and processing data.

[0042] Of course, continue to see Figure 1 , eSE and eSIM combination devices can also have the following functions: DWP, SPI For OMAIIC / SPI For UWB, ISO7816_T0, I2C / SPI Host Interface. Among them, DWP is a digital wallet platform (Digital Wallet Platform) used to manage and process digital payments and identity authentication. SPI For OMA IIC uses the SPI (Serial Peripheral Interface) protocol to implement OMA (Open Mobile Alliance) IIC (Inter-Integrated Circuit) communication. SPI For UWB uses the SPI protocol to implement UWB (Ultra-Wideband) communication. ISO7816_T0 is a transmission protocol defined in the ISO / IEC 7816 standard. I2C HostInterface uses the I2C (Inter-Integrated Circuit) protocol to implement communication between the host and the slave. SPI Host Interface uses the SPI (Serial Peripheral Interface) protocol to implement communication between the host and the slave.

[0043] Specifically, TrustZone-M, MPU, Mapping and other mechanisms are used to achieve physical-level segmentation and isolation of SE resources. For example, the continuous Flash space and RAM space in SE are divided into two independent spaces corresponding to eSE XOS and eSIM XOS, respectively, to form a physical firewall. In this way, when eSEXOS and eSIM XOS try to access quota resources that do not belong to them, including static code, RAM required for dynamic operation, CPU registers involved in the entry and exit process of interrupt processing, etc., the physical firewall will intercept them immediately, so that the physical isolation of eSE and eSIM can be achieved.

[0044] Specifically, the S core is a secure world divided by the TrustZone-M mechanism. The S core mainly includes a Main OS (i.e., main operating system), which is used to implement basic public services, such as managing the resources and task scheduling of the entire system, and providing basic system services, which are not related to specific businesses.

[0045] Specifically, the NS core is a normal world (Non-Secure World) divided by the TrustZone-M mechanism. The NS core mainly includes two XOS subsystems, namely eSE XOS and eSIM XOS. The two XOS subsystems are software systems for specific business implementations. eSE XOS generally refers to the eSE software system, and eSIM XOS generally refers to the SIM software system.

[0046] Specifically, eSE CODE is a code or application in eSEXOS, eSE virtual machine is a virtual machine corresponding to eSE, eSE stack resources are stack resources corresponding to eSE, and eSE is an Entry module corresponding to eSE.

[0047] Specifically, eSE Asset is a resource or data corresponding to eSE.

[0048] Specifically, eSIM CODE is a code or application in eSIMXOS. eSIM virtual machine is a virtual machine corresponding to eSIM, eSIM stack resources are stack resources corresponding to eSIM, and eSIM is an Entry module corresponding to eSIM.

[0049] Specifically, eSIM Asset is the resources or data corresponding to the eSIM.

[0050] Optionally, the physical address of the eSE Entry module is fixed and located at the lowest address part or the highest address part of the memory address space corresponding to the eSE CODE; the physical address of the eSIM Entry module is fixed and located at the lowest address part or the highest address part of the memory address space corresponding to the eSIMCODE.

[0051] Specifically, the physical address of the eSE Entry module is fixed, which means that the location of the eSE Entry module in the memory space corresponding to the eSE XOS is predetermined and will not change. The fixed physical address helps to simplify the eSE XOS startup process. The eSIMEntry module is similar and will not be repeated here.

[0052] Specifically, the eSE Entry module is located in the lowest address part of the memory address space corresponding to the eSE CODE, which means that the code of the eSE Entry module is placed at the very beginning of the eSE CODE code segment, that is, the lowest memory address. The eSEEntry module is located in the highest address part of the memory address space corresponding to the eSE CODE, which means that the code of the eSE Entry module is placed at the very end of the eSE CODE code segment, that is, the highest memory address. The eSIMEntry module is similar and will not be repeated here.

[0053] For example, Figure 2 Schematic diagram of a software system architecture in a SE provided by an embodiment of the present disclosure. Figure 2 , the software system architecture in SE includes: S core and NS core, the S core mainly includes 1 Main OS, the NS core mainly includes 2 XOS subsystems, namely eSE XOS and eSIM XOS, both eSE XOS and eSIM XOS contain independent javacard virtual machines (i.e. eSE virtual machine and eSIM virtual machine) and stack resources (i.e. eSE stack resources and eSIM stack resources), and the javacard virtual machine schedules the system for Main OS through the Entry module (i.e. eSEEntry module and eSIMEntry module). The eSE Entry module is a fixed physical address, located at the bottom of the eSE CODE, and the eSIM Entry module is a fixed physical address, located at the bottom of the eSIM CODE.

[0054] Of course, continue to see Figure 2, Main OS may include RTOS, VMTask, NVM MGR, OSU / ROOT, TxDebug, JC IMPL, and / or GP IMPL. Among them, RTOS refers to the real-time operating system (Real-Time Operating System), which is used for the management and scheduling of real-time tasks to ensure that the tasks are completed within the specified time. VM Task refers to the virtual machine task (Virtual Machine Task), which is used for tasks running in a virtual machine environment. NVM MGR refers to the non-volatile memory manager (Non-Volatile Memory Manager). OSU / ROOT refers to the operating system update / root directory (Operating System Update / ROOT), OSU is used to manage the update process of the operating system to ensure that the system is upgraded safely, and ROOT is used to store the core files and directories of the system. TxDebug refers to (Transaction Debug) transaction debugging, which is used to debug the transaction processing process and help developers find and fix errors in transactions. JC IMPL refers to JavaCard implementation (Java Card Implementation). GP IMPL (GlobalPlatform Implementation) implements the GlobalPlatform standard and is used to manage and protect applications and data on secure elements.

[0055] Of course, continue to see Figure 2 , eSE stack resources may include ISD, CRS, PPSE and / or CASD, but are not limited to them. Among them, ISD refers to the Initial Security Domain on the eSE, which is used to store and manage basic security data and applications. CRS refers to the Contactless Reader System, which is commonly found in payment terminals, access control systems, etc. PPSE refers to the Proximity Payment System Environment, which is used to manage and support multiple payment applications. It acts as the entry point for payment applications to ensure that the correct payment application is selected and executed. CASD is the Card Application Selection Data, which is used to select and start a specific payment application in the PPSE. It contains information for identifying and selecting applications.

[0056] Of course, continue to see Figure 2, eSIM stack resources may include ISD-R, ECASD, ISD-P, and / or SIM / SIM / UICC, but are not limited to them. Among them, ISD-R refers to the Initial Security Domain for Remote SIM Provisioning on the eSIM, which is used to manage and execute the download and activation of remote SIM profiles. ECASD refers to Extended Card Application Selection Data, and ECASD is an extended version of CASD, which contains more information and functions for more complex card application selection and management. ISD-P refers to the Initial Security Domain for Personalization, which is specifically used to manage and execute device personalization settings, such as user identity information, keys, etc. SIM is a user identification module, which is used to store the user's IMSI and Ki, identify and authenticate the user, and connect to the mobile network. ISIM is an IP Multimedia Service Identity Module, which is used to store the user's IMPU and IMPI, identify and authenticate the user's identity in the IMS network, and support IP Multimedia Services. UICC is a universal integrated circuit card that can support multiple application modules at the same time.

[0057] Optionally, in the memory address space corresponding to the eSEAsset, an eSEPA area, an eSEstaticinit data area, an eSE user data area, and an eSE backup data area are sequentially arranged from the lowest address part to the highest address part;

[0058] In the memory address space corresponding to the eSIM Asset, the eSIM PA area, eSIM staticinit data area, eSIM user data area and eSIM backup data area are arranged in sequence from the lowest address part to the highest address part.

[0059] Specifically, the eSEPA area refers to the PA area corresponding to the eSE, and the eSIMPA area refers to the PA area corresponding to the eSIM. The PA area refers to the personalization area, which is used to store data related to user personalized settings, such as user identity information, preference settings, etc.

[0060] Specifically, the eSEstaticinit data area refers to the staticinit data area corresponding to the eSE, and the eSIMstaticinit data area refers to the staticinit data area corresponding to the eSIM. The staticinit data area includes initialized static data structures or variables to ensure that these data are ready when the system starts.

[0061] Specifically, the eSE user data area may include TSF Data and at least one Applet. TSF Data refers to Trust Service Framework data, which stores data related to trust services, such as trust roots, certificate chains, signatures, etc. Applet refers to a small program or application that is used to perform specific security tasks, such as encryption, decryption, and identity authentication.

[0062] Specifically, the eSIM user data area may include at least one Profile, where Profile refers to a configuration file of the SIM, which contains necessary information for connecting to a specific operator's network, such as operator identification, keys, certificates, APN (Access Point Name), etc.

[0063] Specifically, the eSE backup data area refers to the backup data area corresponding to the eSE, which is used to save a copy of the data in the eSE so that it can be restored in case of data loss or damage. The eSIM backup data area refers to the backup data area corresponding to the eSIM, which is used to save a copy of the data in the eSIM so that it can be restored in case of data loss or damage. Of course, the eSE backup data area and the eSIM backup data area can also include FreeTable, where FreeTable refers to a free table, which is used to manage free storage space and record which storage areas are available.

[0064] For example, see Figure 2, eSE XOS and eSIM XOS both contain their own Asset area (i.e., eSE Asset and eSIM Asset). The PA area (i.e., eSEPA area) is stored at the bottom of the eSE Asset area, followed by the staticinit data area (i.e., eSEstaticinit data area), and then the user data area (i.e., eSE user data area), which stores Applet and system data, and the backup data area (i.e., eSE backup data area) is at the top; the eSIM Asset area is similar, except that the user data area in the middle (i.e., eSIM user data area) stores profile data. Except for the user data area, the rest of the Asset area is a fixed virtual EEPROM address and is dynamically protected by the MPU (when eSE is working, eSIMAsset will be set to an inaccessible feature by the MPU; when eSIM is working, eSE Asset will be set to an inaccessible feature by the MPU).

[0065] Optionally, the SE further includes a ROM, wherein the S core further includes: an NSC, a ROMCOS and a BOOTOS, wherein the ROMCOS is stored in the ROM and is protected by the MPU, and the BOOTOS is stored in the ROM and is protected by the MPU.

[0066] Specifically, NSC refers to Non-Secure Component. ROM COS refers to Read-Only Memory Card Operating System, which is used to provide basic card management functions. WM LIB refers to Window Manager Library, which is used to create and manage user interfaces. LIB is a library that provides a set of precompiled functions and data structures to implement specific functions. DRV refers to Driver, which is used to manage the underlying operations of hardware devices and provide an interface for interacting with hardware. HAL refers to Hardware Abstraction Layer, which is used to hide the specific implementation details of the hardware so that the upper-level software can be independent of hardware changes. BOOST OS refers to Boost Operating System, which provides enhanced system services and functions, and is usually used to improve system performance and reliability. ROM COS (Read-Only Memory Card Operating System) is a card operating system (COS) embedded in a read-only memory (ROM).

[0067] Figure 31 is a flowchart of a system operation method provided by an embodiment of the present disclosure, and the method can be executed by an electronic device. The electronic device includes the eSE and eSIM combination device described in any of the above embodiments, and the eSE XOS and the eSIM XOS in the eSE and eSIM combination device share the same static code of JavaCard and GlobalPlatform. The electronic device can be exemplarily understood as a device such as a mobile phone, a bracelet, etc. Figure 3 As shown, the method provided in this embodiment includes the following steps:

[0068] S310. Allocate an eSE operating domain context to the eSE XOS and allocate an eSIM operating domain context to the eSIM XOS, wherein the operating domain context includes: dedicated XOS code, dedicated NVM storage space, dedicated RAM storage space, and dedicated global variables.

[0069] Specifically, the eSE operation domain context is the operation domain context corresponding to the eSE, which refers to all state information and resource configurations required by the eSE during operation. The eSIM operation domain context is the operation domain context corresponding to the eSE, which refers to all state information and resource configurations required by the eSIM during operation.

[0070] Specifically, the eSE and eSIM software systems share the same static code implementation of JavaCard and GlobalPlatform. In order for eSE and eSIM to run independently, a running domain context must be allocated to each instance, called a "DCB" (Domain Context Block). Each DCB contains the following: dedicated XOS code, dedicated NVM storage space, dedicated RAM storage space, and dedicated global variables.

[0071] Optionally, the dedicated XOS code includes Entry, CODE, and PATCH, CODE includes C code implementation, Mask code, Native method table and Static MAP table, wherein the Mask codes corresponding to eSE XOS and eSIM XOS include BASE PKG, eSE PKG and eSIM PKG, and BASE PKG, eSE PKG and eSIM PKG are respectively located in different Masks.

[0072] Specifically, dedicated XOS code refers to code specific to the operating system that is used to manage and schedule tasks. Dedicated XOS code in the eSE runtime domain context ensures that the eSE software system can independently manage and schedule tasks for the instance. Dedicated XOS code in the eSIM runtime domain context ensures that the eSIM software system can independently manage and schedule tasks for the instance.

[0073] Specifically, PATCH is used for code updates that fix bugs in the system or add new features, allowing modifications and enhancements to be made without completely rewriting the system.

[0074] Specifically, CODE is the main function implementation part of the system, including various business logics, data processing, communication protocols, etc.

[0075] Specifically, the C code implementation in the eSE-specific XOS code refers to the program code written in C language, which implements the various functions of eSEXOS; similarly, the C code implementation in the eSIM-specific XOS code refers to the program code written in C language, which implements the various functions of eSIMXOS.

[0076] Specifically, a mask code refers to a bit mask used to control access rights or resource allocation. The mask code is usually used to implement fine-grained access control and resource management.

[0077] Specifically, the Native method table is a mapping table used to associate native methods in the Java virtual machine with functions written in the C language.

[0078] Specifically, the Static MAP table is a static mapping table used to statically map resources, functions, data structures, etc. in the system.

[0079] Specifically, Entry is the first execution point when the system starts, which is responsible for initializing the system and starting the main tasks. Exemplarily, Entry includes XOS_RESET_FUNC, XOS_Process_FUNC and / or XOS_API_FUNC. Among them, XOS_RESET_FUNC refers to the operating system reset function, which is used to reset the operating system and return it to its initial state. XOS_Process_FUNC refers to the operating system process handling function, which is used to manage and schedule processes or tasks in the system. XOS_API_FUNC refers to the operating system API function, which provides an operating system-level API for application calls.

[0080] For example, Figure 4 Schematic diagram of the code structure and calling relationship of eSEXOS, eSIM XOS and Main OS provided by the embodiment of the present disclosure. Figure 4, eSEXOS and eSIM XOS codes both contain their own independent Entry (eSEEntry and eSIMEntry), CODE (eSECODE and eSIMCODE), and PATCH. Among them, Entry is a list of external functions, fixed at the starting address, and provided to the Main OS for calling. The purpose of this design is to facilitate the Main OS call location to remain unchanged after the eSE or eIM is upgraded separately. CODE is the static code implementation of XOS, which includes the following: C code implementation, Mask code, Native method table and Static MAP table, among which Mask code, eSE and eSIM have a public part (BASE PKG) and a proprietary part (ie, eSEPKG and eUICC PKG). Exemplary, Figure 5 Schematic diagram of isolation design of BASE PKG, eSEPKG and eUICC PKG provided by an embodiment of the present disclosure. Figure 5 , the isolation of BASE PKG, eSEPKG and eUICC PKG has three evolutions in design. Figure 5 The leftmost design shows that the eSEPKG and eUICC PKG are not isolated. They use the same Mask and create two staticinits for runtime isolation, but cannot meet the requirements of independent OSU upgrades. Figure 5 The intermediate design means generating two masks and two independent staticinits, which can produce an isolation effect and can be upgraded independently, but will waste more BASE PKG (preliminary evaluation can be controlled to <100K). Figure 5 The design on the far right has the best effect, generating 3 masks with no waste and the best isolation effect.

[0081] Optionally, the dedicated NVM storage spaces corresponding to the eSE XOS and the eSIM XOS respectively have the following characteristics: they are independent of each other, have independent recycling mechanisms and heap management, and share the same set of static codes.

[0082] Specifically, although the dedicated NVM storage spaces corresponding to the eSE XOS and the eSIM XOS are independent, they share the same set of static codes.

[0083] For example, Figure 6 is a schematic diagram of the structure of a dedicated NVM storage space corresponding to an eSE XOS and an eSIM XOS respectively provided in an embodiment of the present disclosure. Figure 6In order to ensure the service isolation of eSE and eSIM, the NVM storage spaces of the two devices are less likely to interfere with each other, such as when both devices load packages at the same time, or when eSIM downloads profiles and eSE deletes packages for garbage collection. Therefore, the disclosed embodiment proposes that both eSE XOS and eSIM XOS have their own independent dedicated NVM storage spaces, but the static codes implemented are the same. Each dedicated NVM storage space has independent GC (garbage collection mechanism) and Heap management. In order to distinguish it from the concept of NVM, the NVM storage space used by eSE XOS and eSIM XOS is abstracted as the EEPROM concept (abbreviated as E2P).

[0084] It can be understood that by setting dedicated NVM storage spaces corresponding to eSE XOS and eSIM XOS respectively, the eSE service and eSIM service have their own independent dedicated NVM storage space, ensuring the independence and security of data, avoiding conflicts or data damage between eSE and eSIM services, thus ensuring that the eSE and eSIM services do not interfere with each other, thereby improving the security and stability of the system.

[0085] Optionally, the dedicated RAM storage spaces corresponding to the eSE XOS and the eSIM XOS respectively include a Java Stack, a DTR and an RTR, and the sizes of the Java Stack, the DTR and the RTR are determined by the maximum call stack depth.

[0086] Specifically, Java Stack refers to the stack in the Java virtual machine, which is used to store local variables, operands, and return addresses during method calls.

[0087] Specifically, DTR (Dynamic Transient RAM) is a dynamic temporary RAM used to store temporary data, which will be cleared after the transaction is completed.

[0088] Specifically, RTR (Revert Transient RAM) is a rollback temporary RAM used to store data that may be modified in a transaction. If the transaction fails, the data can be rolled back to the state at the beginning of the transaction.

[0089] Specifically, the call stack depth refers to the maximum number of method call layers that can be nested in a method call chain.

[0090] Specifically, there are two Java Stacks in JavaCard, and the size of each stack is determined by its corresponding maximum call stack depth. This means that eSE and eSIM have their own independent stacks, and the size of the stack depends on their respective maximum call stack depths. In addition to the Java Stack, there are DTR and RTR spaces in JavaCard, and the size of these spaces is also determined by the maximum call stack depth. This means that eSE and eSIM have their own independent DTR and RTR spaces, and the size of the space depends on their respective maximum call stack depths.

[0091] It can be understood that the eSE runtime domain context includes a RAM storage space dedicated to eSE, and the eSE runtime domain context includes a RAM storage space dedicated to eSIM, which can ensure the independence and efficient access of eSE and eSIM runtime data.

[0092] Optionally, in a single COS scenario, the target virtual machine corresponding to the single COS scenario has exclusive dedicated global variables, where the target virtual machine is one of the eSE virtual machine and the eSIM virtual machine. In a dual COS scenario, a backup method is used to implement it, and the currently activated dedicated global variables are replaced with the backup dedicated global variables when the COS is switched.

[0093] Specifically, the dedicated global variables may include global variables such as JPC, SP, TOP, JCVM, and other modules, but are not limited thereto.

[0094] Specifically, in a single COS scenario, the JavaCard virtual machine has only one instance (i.e., the target virtual machine), and all global variables (such as JPC, SP, TOP, etc.) are exclusive and do not need to be backed up. In a dual COS scenario, the JavaCard virtual machine has two instances: the eSE virtual machine and the eSIM virtual machine. At this time, the dedicated global variables of eSEXOS have a backup (eSE's backup). The dedicated global variables of eSEXOS have a backup (eSIM's backup). In this way, when the COS is switched, the currently activated dedicated global variables can be replaced with the dedicated global variables in the backup using fast copy technology to ensure the efficiency and consistency of the switching process.

[0095] For example, Figure 7This is a switching logic diagram of a dedicated global variable provided by an embodiment of the present disclosure. In a single COS scenario, a single virtual machine exclusively uses global variables. In a dual COS scenario, a backup method is used to implement it. When the COS is switched, the currently activated global variables are replaced with the global variables in the backup by the Fast RAM Copy method to complete the switch. For example, the initial state: eSE is activated: the dedicated global variables of eSE are in RAM. eSIM backup: the dedicated global variables of eSIM are in the backup. Switching to eSIM: save the dedicated global variables of eSE to the backup, and load the dedicated global variables of the backup of eSIM into RAM.

[0096] It is understandable that if all module global variables are implemented in a multi-instance manner, the required changes are too large. However, the embodiment of the present disclosure only needs to compile all global variables that require multi-instances to a specified RAM location as a method for early rapid evolution.

[0097] Optionally, the method further includes: when the Main OS receives the APDU, dispatching the APDU to a corresponding target domain according to source channel information of the APDU, and setting a state of the target domain to a running state, wherein the target domain is one of the eSE domain and the eSIM domain;

[0098] When the target domain completes processing of the APDU or the duration of processing the APDU exceeds a preset duration, the state of the target domain is returned to the ready state.

[0099] Specifically, the source channel information is used to indicate whether the APDU comes from the eSE channel or the eSIM channel. If the APDU comes from the eSE channel, it needs to be processed by the eSE domain; if the APDU comes from the eSIM channel, it needs to be processed by the eSIM domain.

[0100] Specifically, the main states of the eSE domain and the eSIM domain are defined as follows: (1) New: Initial state, no domain instance is created; (2) Ready: After the instance is created, waiting for Main OS scheduling; (3) Running: Running services. It should be noted that the preset durations corresponding to the eSE domain and the eSIM domain can be the same or different.

[0101] For example, Figure 8 Schematic diagram of domain state switching provided by an embodiment of the present disclosure. Figure 8After receiving a valid APDU, the Main OS dispatches it to the specified domain for execution according to the APDU source channel information, and starts a timeout timer. If the domain execution time exceeds the threshold, such as 15S, each domain can configure the threshold separately to avoid the problem that the eSE (or eSIM) malicious application is in an infinite loop and the eSIM (or eSE) cannot be run. When the domain completes the normal processing and returns or throws an exception, it returns to the ready state normally.

[0102] Optionally, the method further includes: when the current task is a first task and triggers a second task, suspending the first task by the RTOS in the MainOS, wherein the first task is an eSIM task and the second task is an eSE task, or the first task is an eSE task and the second task is an eSIM task;

[0103] Using the MPU mechanism, the memory space corresponding to the first task is locked into an inaccessible state;

[0104] switching from a dedicated NVM storage space corresponding to the first task to a dedicated NVM storage space corresponding to the first task;

[0105] Switching from the dedicated global variable corresponding to the first task to the dedicated global variable corresponding to the second task, so as to switch from the virtual machine corresponding to the first task to the virtual machine corresponding to the second task;

[0106] Enable the MPU setting of the memory space corresponding to the second task;

[0107] Check whether the target domain corresponding to the second task has the running conditions;

[0108] When the target domain meets the operating conditions, the current task is switched to the second task.

[0109] Specifically, the trigger condition may be receiving an external command corresponding to the second task or timing out of the first task, but is not limited thereto.

[0110] Specifically, if the first task is an eSE task and the second task is an eSIM task, the eSE domain is set to an inaccessible feature by using the MPU mechanism, which can avoid accidentally accessing the eSE domain when the second task is subsequently executed. Similarly, if the first task is an eSIM task and the second task is an eSE task, the eSIM domain is set to an inaccessible feature by using the MPU mechanism, which can avoid accidentally accessing the eSIM domain when the second task is subsequently executed.

[0111] Specifically, if the first task is an eSE task and the second task is an eSIM task, the access to the eSE dedicated NVM storage space is switched to the eSIM dedicated NVM storage space; similarly, if the first task is an eSIM task and the second task is an eSE task, the access to the eSIM dedicated NVM storage space is switched to the eSE dedicated NVM storage space.

[0112] Specifically, if the first task is an eSE task and the second task is an eSIM task, the currently activated eSE-specific global variables can be replaced with the eSIM-specific global variables in the backup by using the fast copy technology. Similarly, if the first task is an eSIM task and the second task is an eSE task, the currently activated eSIM-specific global variables can be replaced with the eSE-specific global variables in the backup by using the fast copy technology.

[0113] Specifically, if the first task is an eSE task and the second task is an eSIM task, the MPU mechanism is used to set eSIMAsset as an accessible feature. Similarly, if the first task is an eSIM task and the second task is an eSE task, the MPU mechanism is used to set eSE Asset as an accessible feature so that the second task can be executed smoothly afterwards.

[0114] Specifically, if the second task is an eSE task, the target domain is the eSE domain; if the second task is an eSIM task, the target domain is the eSIM domain.

[0115] Specifically, the domain status of the target domain and a security check on the target domain may be performed to determine whether the target domain has the operating conditions, etc., but the present invention is not limited thereto.

[0116] For example, Fig. 9 is a switching flow chart of switching from an eSIM task to an eSE task provided by an embodiment of the present disclosure. Fig. 9,STEP1: The current task is eSIM, and the eSE task needs to be triggered. The triggering condition may be receiving an external command from the eSE end or the eSIM task timeout. The chip will enter privileged mode, and the eSIM task will be suspended by the RTOS; STEP2: Use the MPU to lock the eSIM resources (such as code data / heap data, etc.) to an inaccessible state to prevent accidental access to eSIM resources during eSE operation and cause security risks; STEP3: Switch the HEAP in the EEPROM; STEP4: Switch DCB resources, including the PC, SP, STACK, shared buffer, etc. of the Java virtual machine, to complete the switching of the virtual machine; STEP5: Enable the MPU setting of eSE so that the eSE task has access rights to the corresponding resources (eSE code execution, eSE data access); STEP6: Check the status and security status of the eSE domain to determine whether the operating conditions are met; STEP7: Switch tasks and switch the CPU security state (NS / S). It should be noted that, Fig. 9 The process of switching from eSIM task to eSE task is described above. The same applies to switching from eSE task to eSIM task, so it will not be repeated here.

[0117] Optionally, the method further includes: in the case of resetting the eSE domain alone, resetting the eSE domain using an OMA reset instruction;

[0118] When resetting the eSIM domain separately, the eSIM domain is reset by hot reset;

[0119] When resetting the entire SE, a reset command is sent to the SE via the NFC Frontend using a signal line connected between the NFC Frontend and the SE, so as to reset the entire SE.

[0120] For example, Fig.10 Schematic diagram of resetting a software system in a SE provided by an embodiment of the present disclosure. Fig.10, the eSE and eSIM combination device is powered by the VBAT of the electronic device such as the mobile phone / watch in which it is located. The CLF (i.e. NFC Fronten) and SE inside the eSE and eSIM combination device are two independent power supply systems, among which NCI RST is the NFC controller interface reset signal, SCL is the serial clock line, 7816REST1 is reset signal 1, which complies with the ISO / IEC 7816 standard, and 7816REST2 is reset signal 2, which complies with the ISO / IEC 7816 standard. When only resetting the eSIM domain, the host side performs a hot reset by pulling RST, which only resets the eSIM domain, and the eSE domain is not affected. For example, changing 7816REST1 from a high level to a low level can reset the eSIM domain of SIM1, and changing 7816REST2 from a high level to a low level can reset the eSIM domain of SIM2. If the RST reset fails after 3 attempts, the SE needs to be reset as a whole, and the eSE service will be interrupted. The host side ensures the continuity of the eSE service. When only the eSE domain is reset, it is implemented through the OMA reset command, which will only reset the eSE domain and the eSIM domain will not be affected. When resetting the entire SE, it is implemented through the CLF and the RST pin inside the SE, and the CLF actively triggers or the CLF receives a host command and then triggers.

[0121] In summary, the disclosed embodiment describes the implementation method of the eSIM and eSE all-in-one system, focusing on the solution of core isolation technical problems, including power-on and reset, physical isolation, operating domain context isolation, domain state switching, task switching and other parts, to provide system-level security. Among them, the whole machine reset and the separate reset mechanism for each service make it possible to add no additional external pins. The domain state switching adopts a timer method, and the state is automatically switched when the timeout is reached so as not to affect the normal operation of another system service. In this way, the requirements of electronic devices for chips such as NFC, eSIM, and eSE with high integration, small size, low cost and low energy consumption can be met.

[0122] Fig.11 1 is a schematic diagram of the structure of a system operation device provided by an embodiment of the present disclosure. The system operation device can be understood as the above-mentioned electronic device or some functional modules in the above-mentioned electronic device. Fig.11 As shown, the system operation device is applied to the eSE and eSIM combination device of any of the above embodiments, and the eSE XOS and the eSIM XOS share the same static code of JavaCard and GlobalPlatform. The device includes:

[0123] The allocation module is used to allocate an eSE context to the eSE XOS and an eSIM context to the eSIM XOS, wherein the context includes: a dedicated XOS code, a dedicated NVM storage space, a dedicated RAM storage space, and dedicated global variables.

[0124] Optionally, the dedicated XOS code includes Entry, CODE, and PATCH, the CODE includes C code implementation, Mask code, Native method table and Static MAP table, wherein the Mask codes corresponding to the eSE XOS and the eSIM XOS include BASE PKG, eSE PKG and eSIM PKG, and the BASE PKG, the eSE PKG and the eSIM PKG are respectively located in different Masks;

[0125] The dedicated NVM storage spaces corresponding to the eSE XOS and the eSIM XOS respectively have the following characteristics: they are independent of each other, have independent recycling mechanisms and heap management, and share the same set of static codes;

[0126] The dedicated RAM storage spaces corresponding to the eSE XOS and the eSIM XOS respectively include JavaStack, DTR and RTR, and the sizes of the Java Stack, the DTR and the RTR are determined by the maximum call stack depth;

[0127] In a single COS scenario, the target virtual machine corresponding to the single COS scenario exclusively uses the dedicated global variables, wherein the target virtual machine is one of the eSE virtual machine and the eSIM virtual machine. In a dual COS scenario, a backup method is adopted to replace the currently activated dedicated global variables with the backup dedicated global variables when the COS is switched.

[0128] Optionally, the device further includes: a domain state switching module, configured to dispatch the APDU to a corresponding target domain according to source channel information of the APDU when the Main OS receives the APDU, and set the state of the target domain to a running state, wherein the target domain is one of the eSE domain and the eSIM domain;

[0129] When the target domain completes processing of the APDU or the duration of processing the APDU exceeds a preset duration, the state of the target domain is returned to the ready state.

[0130] Optionally, the device further includes: a task switching module, configured to suspend the first task by the RTOS in the Main OS when the current task is the first task and triggers the second task, wherein the first task is the eSIM task and the second task is the eSE task, or the first task is the eSE task and the second task is the eSIM task;

[0131] Using the MPU mechanism to lock the memory space corresponding to the first task into an inaccessible state;

[0132] switching from the dedicated NVM storage space corresponding to the first task to the dedicated NVM storage space corresponding to the first task;

[0133] Switching from the dedicated global variable corresponding to the first task to the dedicated global variable corresponding to the second task, so as to switch from the virtual machine corresponding to the first task to the virtual machine corresponding to the second task;

[0134] Enabling MPU settings of the memory space corresponding to the second task;

[0135] Checking whether the target domain corresponding to the second task meets the running conditions;

[0136] When the target domain meets the operating conditions, the current task is switched to the second task.

[0137] Optionally, the device further includes: a reset module, configured to reset the eSE domain using an OMA reset instruction when resetting the eSE domain alone;

[0138] In the case of resetting the eSIM domain alone, resetting the eSIM domain by hot resetting;

[0139] When resetting the entire SE, the NFC Frontend sends a reset instruction to the SE via a signal line connected between the NFC Frontend and the SE, so as to reset the entire SE.

[0140] 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.

[0141] An embodiment of the present disclosure further provides an electronic device, which includes: an eSE and eSIM combination device according to any of the above embodiments.

[0142] Specifically, the electronic device can be exemplarily understood as a mobile phone, a bracelet, etc., but is not limited thereto.

[0143] The electronic device provided in this embodiment includes the eSE and eSIM combination device of any of the above embodiments, and therefore has similar beneficial effects as the eSE and eSIM combination device, which will not be described in detail here.

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

[0145] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be 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 will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An eSE and eSIM combination device, characterized in that: include: The NFC Frontend and SE are integrated in the same chip, wherein the SE includes Flash and RAM, and the software system architecture in the SE includes: An S core, wherein the S core includes a Main OS, and the Main OS is stored in the Flash and protected by an MPU mechanism; NS core, the NS core including eSE XOS and eSIM XOS; The eSE XOS includes eSECODE and eSEAsset, the eSECODE is stored in the Flash and protected by the MPU mechanism, the eSEAsset is stored in the RAM and the Flash and protected by the MPU mechanism, the eSECODE includes an eSE virtual machine, eSE stack resources and an eSEeSEEntry module, and the eSE virtual machine schedules the Main OS through the eSEEntry module system; The eSIM XOS includes eSIMCODE and eSIMAsset, the eSIM CODE is stored in the Flash and protected by the MPU mechanism, the eSIM Asset is stored in the RAM and the Flash and protected by the MPU mechanism, the eSIMCODE includes an eSIM virtual machine, eSIM stack resources and an eSIM Entry module, and the eSIM virtual machine schedules the Main OS through the eSIM Entry module system.

2. The eSE and eSIM combination device according to claim 1, characterized in that: The physical address of the eSEEntry module is fixed and is located in the lowest address part or the highest address part of the memory address space corresponding to the eSE CODE; The physical address of the eSIM Entry module is fixed and is located in the lowest address part or the highest address part of the memory address space corresponding to the eSIM CODE; In the memory address space corresponding to the eSEAsset, the eSEPA area, the eSEstaticinit data area, the eSE user data area and the eSE backup data area are sequentially arranged from the lowest address part to the highest address part; In the memory address space corresponding to the eSIM Asset, the eSIM PA area, the eSIM staticinit data area, the eSE user data area and the eSIM backup data area are sequentially arranged from the lowest address part to the highest address part.

3. The eSE and eSIM combination device according to claim 1, characterized in that: The SE further includes a ROM, wherein the S core further includes: an NSC, a ROMCOS and a BOOTOS, the ROMCOS being stored in the ROM and being protected by the MPU, and the BOOTOS being stored in the ROM and being protected by the MPU.

4. A system operation method, characterized in that: Applied to the eSE and eSIM combination device according to any one of claims 1 to 3, the eSE XOS and the eSIM XOS share the same static code of JavaCard and GlobalPlatform, and the method comprises: An eSE operating domain context is allocated to the eSE XOS and an eSIM operating domain context is allocated to the eSIM XOS, wherein the operating domain context includes: dedicated XOS code, dedicated NVM storage space, dedicated RAM storage space and dedicated global variables.

5. The method according to claim 4, characterized in that The dedicated XOS code includes Entry, CODE, and PATCH, the CODE includes C code implementation, Mask code, Native method table and Static MAP table, wherein the Mask codes corresponding to the eSEXOS and the eSIM XOS include BASE PKG, eSE PKG and eSIM PKG, and the BASE PKG, the eSE PKG and the eSIM PKG are respectively located in different Masks; The dedicated NVM storage spaces corresponding to the eSE XOS and the eSIM XOS respectively have the following characteristics: they are independent of each other, have independent recycling mechanisms and heap management, and share the same set of static codes; The dedicated RAM storage spaces corresponding to the eSE XOS and the eSIM XOS respectively include a Java Stack, a DTR and an RTR, and the sizes of the Java Stack, the DTR and the RTR are determined by the maximum call stack depth; In a single COS scenario, the target virtual machine corresponding to the single COS scenario exclusively uses the dedicated global variables, wherein the target virtual machine is one of the eSE virtual machine and the eSIM virtual machine. In a dual COS scenario, a backup method is adopted to replace the currently activated dedicated global variables with the backup dedicated global variables when the COS is switched.

6. The method according to claim 4, characterized in that Also includes: When the Main OS receives the APDU, according to the source channel information of the APDU, the APDU is dispatched to the corresponding target domain, and the state of the target domain is set to the running state, wherein the target domain is one of the eSE domain and the eSIM domain; When the target domain completes processing of the APDU or the duration of processing the APDU exceeds a preset duration, the state of the target domain is returned to the ready state.

7. The method according to claim 4, characterized in that Also includes: In a case where the current task is a first task and triggers a second task, the RTOS in the Main OS suspends the first task, wherein the first task is an eSIM task and the second task is an eSE task, or the first task is an eSE task and the second task is an eSIM task; Using the MPU mechanism to lock the memory space corresponding to the first task into an inaccessible state; switching from the dedicated NVM storage space corresponding to the first task to the dedicated NVM storage space corresponding to the first task; Switching from the dedicated global variable corresponding to the first task to the dedicated global variable corresponding to the second task, so as to switch from the virtual machine corresponding to the first task to the virtual machine corresponding to the second task; Enabling MPU settings of the memory space corresponding to the second task; Checking whether the target domain corresponding to the second task meets the running conditions; When the target domain meets the operating conditions, the current task is switched to the second task.

8. The method according to claim 4, characterized in that Also includes: In the case of resetting the eSE domain alone, the eSE domain is reset using an OMA reset instruction; In the case of resetting the eSIM domain alone, resetting the eSIM domain by hot resetting; When resetting the entire SE, the NFC Frontend sends a reset instruction to the SE via a signal line connected between the NFC Frontend and the SE, so as to reset the entire SE.

9. A system operation device, characterized in that: Applicable to the eSE and eSIM combination device according to any one of claims 1 to 3, the eSE XOS and the eSIM XOS share the same static code of JavaCard and GlobalPlatform, and the device comprises: The allocation module is used to allocate an eSE context to the eSE XOS and an eSIM context to the eSIM XOS, wherein the context includes: dedicated XOS code, dedicated NVM storage space, dedicated RAM storage space and dedicated global variables.

10. An electronic device, characterized in that: include: The eSE and eSIM combination device as claimed in any one of claims 1 to 3.

Images