Apparatus and method for electronic subscriber identity module (ESIM) installation and interoperation

By implementing eSIM management entities and standardized formatting processing on eUICC, the interoperability problem caused by the MNO-centric eSIM management method is solved, and eSIM management compatibility across different devices and operators is achieved.

CN112566074BActive Publication Date: 2024-11-08APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011446691.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2015-04-10
Filing Date
2016-04-07
Publication Date
2024-11-08
Estimated Expiration
2036-04-07

AI Technical Summary

Technical Problem

In the prior art, the management method of the electronic user identity module (eSIM) is centered on the mobile network operator (MNO), causing different MNOs and eUICCs to use different protocols, hindering the interoperability of eSIM between different mobile devices and eUICCs. sex.

Method used

By implementing an eSIM management entity on an embedded universal integrated circuit card (eUICC), decrypting and formatting using encrypted eSIM packets, using standardized communication protocols and formats, such as ASN.1 DER format, parsing and installing eSIM components to provide local Personalize server features to suit the requirements of different devices and manufacturers.

Benefits of technology

The interoperability of eSIM is realized, making eSIM compatible and managed between different MNOs and eUICCs, improving the flexibility and applicability of eSIM.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112566074B_ABST
    Figure CN112566074B_ABST
Patent Text Reader

Abstract

The present disclosure relates to an apparatus and method for eSIM installation and interoperability. An eSIM management entity of an eUICC in the mobile device obtains an encrypted eSIM package, decrypts the eSIM package to obtain eSIM content that is generally formatted rather than specifically customized for the requirements of the eUICC. In some embodiments, the eSIM content is formatted based on an encoding rule (DER) format distinguished by an abstract syntax notation (ASN). The eSIM management entity parses the formatted eSIM content to retrieve separate eSIM components and installs each eSIM component of the eSIM in an eSIM security domain on the eUICC. In some embodiments, the eSIM management entity acts as a local personalization server to provide a local trusted service manager (TSM) server function for eSIM installation, which converts the "generally formatted" eSIM content into eSIM components that match the specific requirements of the eUICC.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application with application number 201680021016.8, application date April 7, 2016, and invention name “Device and method for installation and interoperation of electronic user identity module (ESIM)”. Technical Field

[0002] The embodiments describe techniques for processing an electronic subscriber identity module (eSIM) and installing the eSIM on an embedded universal integrated circuit card (eUICC) included in a mobile device. Background Art

[0003] Many mobile devices are configured to use a removable universal integrated circuit card (UICC) that enables the mobile device to access services provided by a mobile network operator (MNO). Specifically, each UICC includes at least a microprocessor and a read-only memory (ROM), wherein the ROM is configured to store an MNO profile, which the mobile device can use to register with and interact with the MNO. Typically, the UICC takes the form of a small removable card (commonly referred to as a user identity module (SIM) card) that is configured to be inserted into a UICC receiving base included in the mobile device. However, in recent implementations, the UICC is embedded directly into the system board of the mobile device. These embedded UICCs (eUICCs) can provide several advantages over traditional removable UICCs. For example, some eUICCs include a rewritable memory that can facilitate the installation, modification and / or deletion of one or more eSIMs, which can provide new and / or different services and / or updates for accessing extended functionality provided by the MNO. The eUICC can store multiple MNO profiles (also referred to herein as eSIMs), and can eliminate the need to include a UICC receiving base in the mobile device. Additionally, eSIMs can be provisioned remotely to mobile devices, allowing for greatly increased flexibility when users travel to different countries, migrate their phone numbers to different MNOs, etc.

[0004] Currently, a common method for managing the eSIM of a mobile device is MNO-centric and involves a network device such as a configuration server of the MNO communicating with the eUICC of the mobile device through an over-the-air (OTA) secure channel. By establishing an OTA secure channel between the configuration server and the eUICC of the mobile device, the configuration server can remotely manage the appropriate eSIM of the eUICC contained in the mobile device by sending commands to the eUICC via the OTA secure channel.

[0005] It is worth noting that the above-mentioned MNO-centric provisioning techniques may have a number of disadvantages. For example, one disadvantage is that different MNOs, different servers of the MNOs, and / or different eUICCs may use different sets of proprietary protocols to communicate and manage the eSIM. The format used to communicate eSIM information and / or the specific command sequences used by the server to interact with the eUICC to communicate and manage the eSIM may vary significantly, which hinders the interoperability of eSIM management implemented by multiple MNOs and / or multiple configuration servers across different eUICCs in different mobile devices. Summary of the invention

[0006] Representative embodiments describe techniques for managing the processing of an electronic user identity module (eSIM) at a mobile device. According to some embodiments, an eSIM management entity of an embedded universal integrated circuit card (eUICC) included in a mobile device obtains an encrypted eSIM package. The eSIM management entity on the eUICC may be an application that includes specific security service functions (such as secure communications and encryption / decryption). The eSIM management entity on the eUICC decrypts the encrypted eSIM package to obtain the contents of the eSIM. The contents of the eSIM obtained by decrypting the encrypted eSIM package may be formatted in general, rather than being specifically customized according to the requirements of a particular eUICC or mobile device or the requirements of its manufacturer. In some embodiments, the contents of the eSIM package may be formatted according to a standardized communication protocol or specification, or according to an accepted de facto standard format for the communication industry. The contents of the eSIM package may be formatted so that the same format applies to the eSIM for different configuration servers, MNOs, eUICCs, mobile devices, eUICC vendors, and / or mobile device manufacturers. The contents of the eSIM may be formatted according to an encoding rule (DER) format distinguished by an abstract syntax notation (ASN) (e.g., ASN.1). The eSIM management entity parses the formatted content of the eSIM to retrieve individual eSIM (profile) components. The eSIM package may also provide context information for processing eSIM components. In some embodiments, the eSIM management entity personalizes the parsed eSIM content to be installed on the eUICC. The eSIM management entity installs each eSIM (profile) component of the eSIM within the eSIM security domain. In some embodiments, the eSIM management entity acts as a local personalization server to provide a local trusted service manager (TSM) server function for eSIM installation, which converts the "general formatted" content of the eSIM into a set of individual eSIM components in a specific format that matches the requirements of the eUICC, mobile device, and / or its manufacturer. Representative requirements of the eUICC may include hardware requirements, software requirements, operating system (OS) requirements, or a combination of these, which may at least partially determine the format of the eSIM (or one or more eSIM components) stored on the eUICC and / or be used to manage the eSIM stored on the eUICC.

[0007] The purpose of providing this summary is only to summarize some exemplary embodiments in order to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be recognized that the features described above are only examples and should not be considered to narrow the scope or essence of the subject matter described herein in any way. Other features, aspects and advantages of the subject matter described herein will become apparent from the following detailed description, drawings and claims.

[0008] Other aspects and advantages of the embodiments described herein will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate by way of example the principles of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The included drawings are for illustrative purposes and are merely examples of possible structures and arrangements of the disclosed apparatus and methods of the present invention for providing wireless computing devices. These drawings in no way limit any changes in form and detail that may be made to the embodiments by those skilled in the art without departing from the spirit and scope of the embodiments. The embodiments will be more easily understood through the following detailed description in conjunction with the accompanying drawings, in which like reference numerals represent similar structural elements.

[0010] Figure 1 Shown is a block diagram of different components of a system configured to implement the various techniques described herein, according to some embodiments.

[0011] Figure 2 According to some embodiments, Figure 1 A block diagram of a more detailed view of specific components of the system.

[0012] Figure 3A An eSIM for storage is shown installed in accordance with some embodiments Figure 1 A sequence diagram of the method on the eUICC of a mobile device.

[0013] Figure 3B Representative parsing of a portion of a standard formatted eSIM package into eSIM content for installation on an eUICC is shown in accordance with some embodiments.

[0014] Figure 4 An example of a method for installing an eSIM for storage in a Figure 1 Flowchart of an exemplary method on an eUICC of a mobile device.

[0015] Figure 5 Shown is a detailed view of an exemplary computing device that can be used to implement the various components described herein, according to some embodiments. DETAILED DESCRIPTION

[0016] Representative applications of the apparatus and methods according to the embodiments described in the present invention are provided in this section. These examples are provided only to add context and to help understand the embodiments. It will therefore be apparent to those skilled in the art that the embodiments described in the present invention may be implemented without some or all of these specific details. In other cases, well-known process steps are not described in detail to avoid unnecessarily obscuring the embodiments described in the present invention. Other applications are also possible, so that the following examples should not be considered restrictive.

[0017] According to various embodiments described herein, the terms "wireless communication device", "wireless device", "mobile device", "mobile station", and "user equipment (UE)" may be used interchangeably herein to describe one or more common consumer electronic devices that may be capable of performing the processes associated with various embodiments of the present disclosure. According to various specific implementations, any of these consumer electronic devices may relate to: a cellular phone or smartphone, a tablet computer, a laptop computer, a notebook computer, a personal computer, a netbook computer, a media player device, an e-book device, Devices, wearable computing devices, and any other type of electronic computing device with wireless communication capabilities, which wireless communication capabilities may include communication via one or more wireless communication protocols, which wireless communication protocols, such as protocols used to communicate on the following networks: wireless wide area networks (WWAN), wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), wireless personal area networks (WPAN), near field communication (NFC), cellular wireless networks, fourth generation (4G) long term evolution (LTE), advanced LTE (LTE-A), and / or 5G or other currently or future developed advanced cellular wireless networks.

[0018] In some embodiments, the wireless communication device may also operate as part of a wireless communication system, which may include a group of client devices, which may also be referred to as stations, client wireless devices, or client wireless communication devices, interconnected to an access point (AP), such as part of a WLAN, and / or interconnected to each other, such as part of a WPAN and / or "ad hoc" wireless network. In some embodiments, a client device may be any wireless communication device capable of communicating via WLAN technology (e.g., according to a wireless local area network communication protocol). In some embodiments, the WLAN technology may include a Wi-Fi (or more generally, a WLAN) wireless communication subsystem or radio component, which Wi-Fi radio equipment may implement the Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology, such as one or more of the following: IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other existing or future developed IEEE 802.11 technologies.

[0019] In addition, it should be understood that the UE described herein may be configured as a multi-mode wireless communication device that is also capable of communicating via different third generation (3G) and / or second generation (2G) RATs. In these cases, the multi-mode UE may be configured to prefer attaching to an LTE network that provides a faster data rate throughput over other 3G legacy networks that provide a lower data rate throughput. For example, in some embodiments, the multi-mode UE may be configured to fall back to a 3G legacy network, such as an evolved high speed packet access (HSPA+) network, or a code division multiple access (CDMA) 2000 evolution-data only (EV-DO) network when LTE and LTE-A networks are otherwise unavailable.

[0020] The representative embodiments described herein set forth techniques for managing the processing of an electronic user identity module (eSIM) at a mobile device. Upcoming communications standard protocols, such as those specified in the European Technical Standards Institute (ETSI) Technical Specification (TS) 103.383, require that eSIM interoperability be achieved across different eUICCs. Specifically, the eUICC should support the loading and installation of eSIMs (profiles) that can be generated by different profile provisioning credential holders. The eSIM may use a standardized description format that allows loading and installation on any eUICC that complies with eSIM interoperability, for example, as specified in ETSI TS 103.383 and / or other applicable communications standard protocols and / or in fact communications industry standard formats. The standardized description format for the eSIM may include a number of different standardized items, such as network access application (NAA) parameters, NAA algorithm parameters and keys, "over the air" (OTA) keys, remote applet management (RAM) and remote file management (RFM) parameters, personal identification number (PIN) and personal unlocking key (PUK). In addition, the interface used by the eSIM to be remotely provisioned to the eUICC should conform to a common specified type in terms of file structure and associated metadata. In some embodiments, the format of the eSIM content may be based on Abstract Syntax Notation 1 (ASN.1) Distinguished Encoding Rules (DER). To achieve eSIM interoperability, the architecture of the eUICC and / or the structure of the operating system (OS) may need to be modified to adapt it to the new "standardized" or "universal" eSIM format and / or the eSIM process to manage the formatted content of the eSIM obtained from the "standardized" eSIM package to a set of separate eSIM components in a format compatible with the eUICC and / or specific to the eUICC.

[0021] According to some embodiments, an eSIM management entity of an embedded universal integrated circuit card (eUICC) included in a mobile device obtains an encrypted eSIM package with formatted content. The content of the eSIM package may be formatted according to a communication standard protocol or specification, or may be based on a de facto communication industry standard format. The eSIM management entity on the eUICC may be (1) an issuer security domain (ISD) level application, (2) a server-side application, or (3) a server-side application. The eSIM management entity on the eUICC decrypts the encrypted eSIM package to obtain the contents of the eSIM, wherein the contents are formatted in a "universal" or "standard" format suitable for different eUICCs and / or mobile devices. The same format of the eSIM content can be used for different eUICCs and / or mobile devices (and their manufacturers). Similarly, different configuration servers used by different MNOs can provide eSIM packages with content formatted in a similar manner accordingly. In some embodiments, the contents of the eSIM can be formatted according to a communication standard protocol or specification or a de facto standard format in the communication industry. In some embodiments, the contents of the eSIM are formatted according to an encoding rule (DER) format distinguished by an abstract syntax notation (ASN) (e.g., ASN.1). The eSIM management entity parses the formatted contents of the eSIM to retrieve individual eSIM (profile) components, which may include files (e.g., elementary files (EF) and dedicated files (DF)), applications, security domain settings, eSIM encryption / decryption keys, network access application (NAA) parameters, NAA algorithm parameters and keys, over-the-air (OTA) keys, remote applet management (RAM) and remote file management (RFM) parameters, personal identification number (PIN) and / or personal unlocking key (PUK). The eSIM package may also provide: context information used to process the components of the eSIM, such as implicit file path information used to organize one or more EFs under a common DF path; and / or implicit record padding patterns, such as 'FF', which are used to pad the contents of the various components of the eSIM to the appropriate size after parsing, such as when compressing the contents of the eSIM to reduce the size of the eSIM package used for communication between the configuration server and the eUICC of the mobile device. In some embodiments, the eSIM management entity on the eUICC personalizes the parsed content of the eSIM for installation on the eUICC, such as during installation of the eSIM content on the eUICC, the eUICC uses keys and / or secrets. The eSIM management entity installs the various components of the eSIM (profile) in the eSIM security domain. In some embodiments, the eSIM management entity acts as a local personalization server to provide local TSM server functions for eSIM installation, which converts a generic or "standard formatted" eSIM package into a specific format that matches the eUICC requirements.In some embodiments, the requirements of the eUICC include the format of the eSIM, such as individual eSIM components, and / or the organization of the eSIM components stored on the eUICC. In some embodiments, the requirements of the eUICC include hardware requirements and / or software (such as for the eUICC operating system) requirements that affect the format of the eSIM stored on the eUICC, the organization of the eSIM components on the eUICC, and / or a series of commands for installing, adding, modifying, updating, and / or performing other eSIM management operations on the eUICC for the eSIM. In some embodiments, the eSIM management entity parses different eSIM packages formatted according to standard protocols into different eSIM contents, and installs the different eSIM contents in different security domains according to the hardware, software, and / or OS requirements for the eSIM and / or for the MNO associated with the eSIM. In some embodiments, the post-installation data structure of the eSIM contents stored in the associated security domain of the eUICC is formatted in a manner specific to the eUICC OS used by the eUICC. In some embodiments, an eSIM management entity located external to the eUICC, such as a terminal interface or a remote management server, may interface with a “personalized” eSIM on the eUICC according to one or more standardized communication protocols.

[0022] Therefore, compared to conventional MNO-specific, server-specific, and / or eUICC-specific eSIM management techniques, the eSIM management techniques described herein provide a method for managing eSIMs in an interoperable manner because the eUICC can receive a standardized and / or generally formatted eSIM package and convert the contents of the eSIM package into a format specifically compatible with one or more requirements of the eUICC for managing and / or storing the eSIM on the eUICC. A more detailed discussion of these techniques is shown below and in conjunction with Figures 1 to 5 A description is provided that shows detailed illustrations of systems and methods that can be used to implement these techniques.

[0023] Figure 1 1 is a block diagram of various components of a system 100 configured to implement the various techniques described herein, according to some embodiments. More specifically, Figure 1 A high-level overview of a system 100 is shown, which includes a mobile device 102, a set of base stations 112 managed by different MNOs 114, and a set of configuration servers 116 in communication with the MNOs 114. Figure 1 , mobile device 102 may represent a mobile computing device (e.g., of or ), base stations 112 may represent different radio towers configured to communicate with mobile device 102, and MNO 114 may represent different wireless service providers that provide specific services (e.g., voice and data) to which mobile device 102 may subscribe.

[0024] like Figure 1As shown, the mobile device 102 may include a main processor 104, a memory 106, an eUICC 108, and a baseband component 110. These components work together to enable the mobile device 102 to provide useful features to the user of the mobile device 102, such as local computing, location-based services, and Internet connectivity. As described in more detail below, the eUICC 108 may be configured to store multiple eSIMs for accessing different MNOs 114 through a base station 112. For example, the eUICC 108 may be configured to store and manage one or more eSIMs of one or more MNOs 114 for different users associated with the mobile device 102. In order to access services provided by the MNO, the eSIM is provisioned to the eUICC 108. In addition, the eSIM stored on the eUICC 108 may be updated, modified, activated, deactivated, and / or deleted via communication between the eUICC 108 of the mobile device 102 and an applicable network device such as a configuration server 116 (or other equivalent or similar network-based eSIM management entity). In some embodiments, the eSIM is pre-stored in the eUICC 108 in an inactive state, and during the provisioning process, the eUICC 108 obtains MNO credentials (e.g., keys, etc.), service information (e.g., operator information, subscribed services), and / or other information, and uses this information to activate the eSIM. In some embodiments, the eSIM is not pre-stored in the eUICC 108, and the eUICC 108 obtains one or more eSIMs from one or more associated provisioning servers 116. It should be noted that the provisioning server 116 may be maintained by the manufacturer of the mobile device 102, the MNO 114, a third-party entity, etc. The communication of eSIM data between the provisioning server 116 and the eUICC 108 uses a secure communication channel, through which a series of commands between the provisioning server 116 and the eUICC 108 result in the eSIM being provisioned (or otherwise managed) to the eUICC 108 (or on the eUICC 108). Because different eUICC 108 (or UICC) manufacturers (or mobile device manufacturers) may currently require different "proprietary" protocols to format eSIM data and / or manage the eSIM on the eUICC 108, such as requiring a specific series of commands, different eSIMs provided to the same eUICC 108 from different MNOs and / or different provisioning servers 116 may require different processing, which may hinder interoperability of the eSIMs.As further described herein, the provisioning server 116 may provide a “standardized” or “generic” formatted eSIM package to the eUICC 108 of the mobile device 102, and the eSIM management entity on the eUICC 108 may extract a set of eSIM components from the eSIM package to install, modify, update, or otherwise manage the eSIM on the eUICC. Although. Figure 1 Not shown, the mobile device 102 may also be configured to include a receiving dock for a removable UICC (eg, a SIM card) on which an eSIM may be managed in a similar manner using the techniques described herein.

[0025] Figure 2 It is shown that according to some embodiments, Figure 1 A block diagram of a more detailed view 200 of certain components of the mobile device 102 is shown. Figure 2 As shown, the host processor 104 in conjunction with the memory 106 may implement a host operating system (OS) 202 configured to execute application programs 204 (eg, native OS applications and user applications). Figure 2 As shown, the eUICC 108 may be configured to implement an eUICC OS 206 that is configured to manage the hardware resources of the eUICC 108 (e.g., a processor and memory embedded in the eUICC 108). The eUICC OS 206 may also be configured to manage the eSIM 208 stored by the eUICC 108, for example, by activating, deactivating, modifying, or otherwise performing management of the eSIM 208 within the eUICC 108 and providing access to the eSIM 208 to the baseband component 110 to provide access to wireless services for the mobile device 102. The eUICC 108 operating system may include an eSIM manager 210, which may be an issuer security domain (ISD) level application, a SIM card based on a SIM card, or a SIM card that is configured to communicate with the baseband component 110. The eSIM manager 210 may be a security domain that is associated with one or more eSIMs and calls for additional eUICC OS installation services and / or applications that implement a specific set of security services, such as for establishing and managing secure channels and / or providing encryption / decryption functions. The eSIM manager 210 may perform management functions for various eSIMs as further described herein. Figure 2 As shown, each eSIM 208 may include a plurality of applets 212 that define the manner in which the eSIM 208 operates. For example, one or more of the applets 212, when implemented by the baseband component 110 and the eUICC 108, may be configured to enable the mobile device 102 to communicate with the MNO 114 and provide useful features (e.g., phone calls and the Internet) to a user of the mobile device 102.

[0026] Likewise Figure 2 As shown, the baseband component 110 of the mobile device 102 may include a baseband OS 214 configured to manage the hardware resources (e.g., processor, memory, different radio components, etc.) of the baseband component 110. According to some embodiments, the baseband component 110 may implement a manager 216 configured to interface with the eUICC 108 to implement various techniques described herein, which may include establishing a secure channel with the configuration server 116 and obtaining information (such as eSIM data) from the configuration server 116 for managing the eSIM 208, including but not limited to configuring, loading, installing, adding, modifying, updating, deleting, or performing other management operations for one or more eSIMs 208. Similarly, as shown in FIG. Figure 2 As shown, the manager 216 may be configured to implement services 218, which represent a collection of software modules instantiated with various applets 212 included in the activated eSIMs 208 in the eUICC 108. For example, the services 218 may be configured to manage different connections between the mobile device 102 and the MNO 114 depending on the different eSIMs 208 activated within the eUICC 108.

[0027] Figure 3AA sequence diagram 300 is shown of a set of steps that an eUICC 108 of a mobile device 102 may use to obtain and process a standardized formatted eSIM package from a provisioning server 140. In step 302, the eSIM manager 210 of the eUICC 108 may receive the eSIM package from the provisioning server 140. In some embodiments, the provisioning server 140 "pushes" the eSIM package to the eUICC 108, for example, to install an update to an existing eSIM 208 of the eUICC 108 or to provision an eSIM 208 to the eUICC 108 in response to a request from the mobile device 102 (or via another not shown path). In some embodiments, the eSIM package (and / or the contents of the eSIM 208 contained therein) is formatted according to a standards-based communication protocol or specification (e.g., a specification of 3GPP, ETSI, IEEE, or other wireless standards organization). In some embodiments, the eSIM package and / or its contents are formatted according to a communication industry de facto standard format. In some embodiments, the eSIM package (and / or the eSIM content included therein) is formatted according to an ASN.1 DER encoding format. In some embodiments, the eSIM package received by the eSIM manager 210 from the provisioning server 140 is encrypted, for example, to provide a degree of security protection for the eSIM package. In step 304, the eSIM manager 210 decrypts the encrypted formatted eSIM package to retrieve the eSIM content, which in some embodiments may be ASN.1 DER encoded eSIM content. The content of the eSIM 208 obtained from the eSIM package may be formatted using a format suitable for different eUICCs 108 and / or their manufacturers. The format may be "generic" and not "specific" or "customized" to the requirements of a particular eUICC or its manufacturer. Thus, for example, the same format may be used to provide an eSIM package to different eUICCs 108, and each eUICC 108 may locally customize the "generic" formatted eSIM content at the eUICC 108, for example, via the eSIM manager 210 of the eUICC 108, for installation on the eUICC 108. In step 306, the eSIM manager 210 parses the eSIM content to retrieve a set of individual eSIM components, which may include files, applications, settings, keys, etc. for the eSIM 208. In some embodiments, the eSIM components of the eSIM 208 include elementary files (EF) and dedicated files (DF), such as those defined by 3GPP and / or ETSI. In some embodiments, the eSIM components include a set of applications or applets 212 associated with the eSIM 208.In some embodiments, the eSIM components include a set of security domain settings that can be used to define the operation of an eSIM-specific security domain in which the eSIM 208 can be stored and / or managed. In some embodiments, the eSIM components include a set of eSIM keys, for example, for encryption / decryption and / or network access application (NAA) secrets for authentication and / or authorization and / or protection of eSIM content. In step 308, the eSIM manager 210 installs each eSIM component of the eSIM 208 into an eSIM security domain 310 associated with the eSIM 208. In some embodiments, multiple eSIMs 208 can reside in a common eSIM security domain 310, such as for a particular MNO 114. In some embodiments, each eSIM 208 can reside in its own eSIM security domain 310.

[0028] Figure 3B A diagram 350 is shown of representative parsing of a portion of a standardized formatted eSIM packet by the eSIM manager 210 of the eUICC 108 (which is part of the eUICC OS 206). The eSIM packet (and / or the contents therein) can be formatted in a format that can be parsed by any compatible eUICC OS 206 or eSIM manager 210. In some embodiments, the eSIM packet (and / or the contents therein) is formatted according to the ASN.1 DER encoding format. Figure 3B A representative ASN.1 DER encoded portion of the contents of an eSIM packet shown in a human readable structure is shown. The eSIM manager 210 can parse the ASN.1 formatted eSIM contents of the eSIM packet to generate eSIM components for eSIM installation on the eUICC 108. Specifically, Figure 3BAn elementary file (EF) for an integrated circuit card identifier (ICCID) is shown. After being parsed by the eSIM manager 210, the ASN.1 formatted input becomes a set of eSIM content, namely, file control parameters (FCP) and file data (ICCID value). The FCP may include a data group identifier (DGI) and a type length value (TLV) of the ICCID EF. In some embodiments, the eSIM package parsed by the eSIM manager 210 may include context information that may or may not be included in the eSIM components. For example, the context handling of eSIM content by the eSIM manager 210 may be standardized. A representative context handling example includes implicit file path information, such as when creating an EF sequence under a common DF path (or folder). Another representative context handling example includes an implicit file record padding pattern used when creating eSIM content for installation on the eUICC 108, such as when a fixed length file record of the eSIM 208 is padded with a specific pattern, such as 'FF', resulting in a file record having a specific length value (the 'FF' padding pattern is not included in the encrypted formatted eSIM package to reduce its size). In some embodiments, after parsing, the eSIM manager 210 may "personalize" the eSIM content and / or process the eSIM data in a proprietary manner for installation on the eUICC 108, e.g., the manner in which keys and / or secrets are used at the eUICC 108 during the eSIM installation process may be determined by the eSIM manager and is not subject to interoperability requirements.

[0029] Back to Figure 3AIn step 308, the eSIM manager 210 installs the components of the eSIM 208 in the eSIM security domain 310 associated with the eSIM 208. The eSIM manager 210 may act as a local "personalization" server (of the mobile device 102) during the installation of the eSIM 208, for example, to at least partially implement the functionality provided by the provisioning server 140 (or an equivalent network-based device) to manage the eSIM 208 on the eUICC 108 of the mobile device 102. The functionality provided by the eSIM manager 210 may be comparable to the remote management commands provided by the provisioning server 140 to manage the eSIM 208 on the eUICC 108. For example, commands such as "select path", "create file (EF / DF)", "update record", "load security domain", "install security domain", "load application", and "install application" may be implemented locally on the eUICC 108 of the mobile device 102 by the eSIM manager 210 to manage the eSIM 208. The eSIM manager 210 may receive the eSIM package via a secure connection, and the eSIM manager 210 may install the eSIM 208 on the eUICC 108 without receiving a series of commands from the provisioning server 140 during the installation of the eSIM 208. The eSIM manager 210 may decrypt, parse, personalize, process, load, install, authenticate, and perform other management functions of the eSIM 208 autonomously or with minimal communication with the provisioning server 140. The eSIM manager 210 may notify the provisioning server 140 upon successful installation of the eSIM 208. In some embodiments, the eSIM manager 210 may regenerate a series of commands comparable to the communications between the provisioning server 140 and the "traditional" eUICC OS to achieve at least a portion of the process of installing the eSIM 208 on the eUICC 108. In some embodiments, the eSIM manager uses the "new" series of commands to achieve the same results as those achieved by installing the eSIM 208 on the eUICC 108 through a series of "traditional" commands. In some embodiments, the eUICC 108 stores a set of command scripts that can be executed in whole or in part to perform at least a portion of the installation of the eSIM 208 on the eUICC 108. In some embodiments, when the eSIM 208 is installed on the eUICC 108, the eUICC performs at least some "personalization" functions in a proprietary manner. Representative functions may include personalization of one or more keys and / or NAA secrets or other security measures. In addition, the file format used to store the eSIM 208 on the eUICC 108 can be "personalized" in a proprietary manner, for example based on a vendor personalization facility specific to the SIM card.In some embodiments, the post-installation data structure for storing the eSIM 208 on the eUICC platform may be specific to the eUICC OS; however, the data of the eSIM 208 may be viewed and / or managed via a standard interface of the terminal such as the UICC / eUICC interface. Thus, the eSIM 208 may be stored in a different manner for each eSIM 208, but may be presented in a "unified" manner via a standard interface. For example, eSIM management implemented by an "off-card" entity such as by a remote management server and / or via a terminal interface may conform to a public standardized management interface such as ETSI TS 103.383 and / or TS 103.384. In some embodiments, selection of the eSIM 208 via the interface may be performed according to a conventional interface specification of the UICC, such as specified in the international standard ISO / IEC 7816, which is a standard jointly managed by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC).

[0030] Figure 5 A detailed view of a computing device 500 that can be used to implement the various components described herein according to some embodiments is shown. Specifically, the detailed view shows Figure 1 The various components that may be included in the mobile device 102 are shown. Figure 5 As shown, the computing device 500 may include a processor 502, which represents a microprocessor or controller for controlling the overall operation of the computing device 500. The microprocessor or controller may represent an Figure 1 The computing device 500 may also include a user input device 508 that allows a user of the computing device 500 to interact with the computing device 500. For example, the user input device 508 may take a variety of forms, such as buttons, keypads, dials, touch screens, audio input interfaces, visual / image capture input interfaces, input in the form of sensor data, etc. Further, the computing device 500 may include a display 510 (screen display) that can be controlled by the processor 502 to display information to the user. The data bus 516 may facilitate data transfer between at least the storage device 540, the processor 502, and the controller 513. The controller 513 can be used to interact with and control different devices through the device control bus 514. The computing device 500 may also include a network / bus interface 511 coupled to the data link 512. In the case of a wireless connection, the network / bus interface 511 may include a wireless transceiver.

[0031] The computing device 500 also includes a storage device 540, which may include a single disk or multiple disks (e.g., a hard drive) and a storage management module that manages one or more partitions within the storage device 540. In some embodiments, the storage device 540 may include flash memory, semiconductor (solid-state) memory, etc. The computing device 500 may also include a random access memory (RAM) 520 and a read-only memory (ROM) 522. The ROM 522 may store programs, utilities, or processes to be executed in a non-volatile manner. The RAM 520 may provide volatile data storage and store instructions related to the operation of the computing device 500. The computing device 500 may also include a secure element 550, which may represent a secure element. Figure 1 , Figure 2 and Figure 3A The eUICC 108 is shown in FIG. 1 and described in detail herein.

[0032] The various aspects, embodiments, implementations, or features of the embodiments may be used individually or in any combination. The various aspects of the embodiments may be implemented by software, hardware, or a combination of hardware and software. The embodiments may also be embodied as computer readable code on a computer readable medium. A computer readable medium is any data storage device that can store data, which can then be read by a computer system. Examples of the computer readable medium include read-only memory, random access memory, CD-ROM, DVD, magnetic tape, hard disk drive, solid state drive, and optical data storage device. The computer readable medium may also be distributed in a network coupled computer system so that the computer readable code is stored and executed in a distributed manner.

[0033] For the purpose of explanation, the foregoing description uses specific nomenclature to provide a thorough understanding of the embodiments. However, it will be apparent to those skilled in the art that these specific details are not required to practice the embodiments. Therefore, the foregoing description of specific embodiments is presented for the purpose of illustration and description. These descriptions are not intended to be considered exhaustive or to limit the embodiments to the disclosed precise forms. It will be apparent to those of ordinary skill in the art that many modifications and variations are possible based on the above teachings.

Claims

1. A method for managing an electronic user identity module (eSIM) on an embedded universal integrated circuit card (eUICC) included in a mobile device, the method comprising: By the eUICC: receiving an encrypted eSIM packet from a provisioning server via a secure connection over a wireless network, the eSIM packet comprising: i) general formatted content of the eSIM, and ii) context information or an indication of context information, wherein a format of the general formatted content is not specific to requirements of the eUICC; decrypting the encrypted eSIM package to obtain the generally formatted content of the eSIM; customizing the generic formatted content of the eSIM according to the format requirements of the eUICC or the mobile device using the context information to generate at least a portion of a set of individual components of the eSIM; and installing the set of individual components of the eSIM in an eSIM security domain on a memory of the eUICC, The context information includes implicit file path information and / or implicit record filling mode.

2. The method according to claim 1, wherein the implicit file path information indicates an organization of elementary files (EF) under a common dedicated file (DF) path for the eSIM.

3. The method of claim 1 , wherein the implicit record padding mode indicates padding to be used in order to generate a fixed length value for a file record of the eSIM installed on the eUICC.

4. The method according to claim 1, further comprising: By the eUICC: The at least a portion of the set of individual components of the eSIM is personalized for installation on the eUICC using a key or secret specific to the eUICC.

5. The method of claim 1, wherein the decryption, the customization, and the installation are performed by an eSIM management entity residing on the eUICC while disconnected from the provisioning server.

6. The method of claim 5, wherein the eSIM management entity comprises an Issuer Security Domain (ISD) application. 7 . The method according to claim 5 , wherein the eSIM management entity comprises an application having a specific security service capability, the specific security service capability comprising decryption.

8. The method of claim 1, wherein the set of individual components of the eSIM installed in the eSIM security domain are formatted specifically for an eUICC operating system (OS) of the eUICC.

9. The method of claim 1, wherein the generic formatted content of the eSIM is formatted according to Distinguished Encoding Rules for Abstract Syntax Notation 1 (ASN.1) (DER) format.

10. An embedded universal integrated circuit card (eUICC), configured to manage an electronic user identity module (eSIM) for a mobile device, the eUICC comprising: a memory configured to store at least one eSIM; as well as A processor configured to perform operations including: receiving an encrypted eSIM packet from a provisioning server via a secure connection over a wireless network, the eSIM packet comprising general formatted content of the eSIM and context information or an indication of context information, wherein a format of the general formatted content is not specific to requirements of the eUICC; decrypting the encrypted eSIM package to obtain the generally formatted content of the eSIM; using the context information to customize the generic formatted content of the eSIM according to the format requirements of the eUICC or the mobile device to generate at least a portion of a set of individual components of the eSIM; as well as installing the set of individual components of the eSIM in an eSIM security domain on the memory of the eUICC, The context information includes implicit file path information and / or implicit record filling mode.

11. The eUICC according to claim 10, wherein the implicit file path information indicates an organization of elementary files (EF) under a common dedicated file (DF) path for the eSIM.

12. The eUICC of claim 10, wherein the implicit record padding mode indicates padding to be used in order to generate a fixed length value for a file record of the eSIM installed on the eUICC.

13. The eUICC according to claim 10, wherein the operations performed by the eUICC further comprise: The at least a portion of the set of individual components of the eSIM is personalized for installation on the eUICC using a key or secret specific to the eUICC.

14. The eUICC of claim 10, wherein the decryption, the customization, and the installation are performed by an eSIM management entity residing on the eUICC while disconnected from the provisioning server.

15. The eUICC of claim 14, wherein the eSIM management entity comprises an Issuer Security Domain (ISD) application.

16. The eUICC according to claim 14, wherein the eSIM management entity includes an application having a specific security service capability, the specific security service capability including decryption.

17. The eUICC of claim 10, wherein the set of individual components of the eSIM installed in the eSIM security domain are formatted specifically for an eUICC operating system (OS) of the eUICC.

18. The eUICC of claim 10, wherein the generic formatted content of the eSIM is formatted according to Distinguished Encoding Rules for Abstract Syntax Notation 1 (ASN.1) (DER) format.

19. A mobile device configured to manage an electronic subscriber identity module (eSIM), the mobile device comprising: wireless circuitry including one or more antennas and baseband components; as well as a processor communicatively coupled to the wireless circuit and the embedded universal integrated circuit card eUICC, The eUICC is configured to perform the following operations: receiving an encrypted eSIM packet from a provisioning server via a secure connection over a wireless network, the eSIM packet comprising general formatted content of the eSIM and context information or an indication of context information, wherein a format of the general formatted content is not specific to requirements of the eUICC; decrypting the encrypted eSIM package to obtain the generally formatted content of the eSIM; using the context information to customize the generic formatted content of the eSIM according to the format requirements of the eUICC or the mobile device to generate at least a portion of a set of individual components of the eSIM; as well as installing the set of individual components of the eSIM in an eSIM security domain on a memory of the eUICC, The context information includes implicit file path information and / or implicit record filling mode.

20. The mobile device of claim 19, wherein the implicit file path information indicates an organization of elementary files (EF) under a common dedicated file (DF) path for the eSIM.

21. The mobile device of claim 19, wherein the implicit record padding mode indicates padding to be used in order to generate a fixed length value for a file record of the eSIM installed on the eUICC.

22. The mobile device of claim 19, wherein the operations performed by the eUICC further comprise: The at least a portion of the set of individual components of the eSIM is personalized for installation on the eUICC using a key or secret specific to the eUICC.

23. The mobile device of claim 19, wherein the decryption, the customization, and the installation are performed by an eSIM management entity residing on the eUICC while disconnected from the provisioning server.

24. The mobile device of claim 23, wherein the eSIM management entity comprises an Issuer Security Domain (ISD) application.

25. The mobile device of claim 23, wherein the eSIM management entity comprises an application having specific security service capabilities, the specific security service capabilities comprising decryption.

26. The mobile device of claim 19, wherein the set of individual components of the eSIM installed in the eSIM security domain are formatted specifically for an eUICC operating system (OS) of the eUICC.

27. The mobile device of claim 19, wherein the generic formatted content of the eSIM is formatted according to Distinguished Encoding Rules for Abstract Syntax Notation (ASN.1) (DER) format.