JP6231044B2 - Handling of application identification information of electronic subscriber identification module (eSIM) - Google Patents

Description

  The present application relates to an embedded universal integrated circuit card (eUICC) and an electronic subscriber identity module (eSIM). In particular, it relates to enabling mobile devices to access eSIM content in multiple eSIM environments.

  Most mobile devices are configured to receive and operate a removable universal integrated circuit card (UICC) that enables the mobile device to access services provided by a mobile operator (MNO). In particular, each UICC includes at least a microprocessor and a read only memory (ROM). The ROM is configured to store different applets and authentication data that a mobile device can use to register with the MNO and interact with the MNO. Typically, a UICC is configured to store a single MNO profile and is in the form of a small removable card (eg, a SIM card) that is inserted into a UICC receptacle provided on a mobile device. In more recent implementations, the UICC is built directly into the mobile device system board and is configured to store multiple MNO profiles. This is called an electronic SIM (eSIM). For example, an embedded UICC (eUICC) can store one eSIM for a local MNO and another SIM for an international MNO. These eUICCs have a number of advantages over conventional removable UICCs. For example, some eUICCs have rewritable memory that facilitates eSIM updates to access extended functionality provided by the MNO. eUICC eliminates the need for mobile devices to have a UICC receptacle. The implementation of eUICC not only increases the flexibility of the mobile device, but also simplifies the design and frees up space for other components.

  Although eUICC offers many benefits over traditional removable UICC, implementing eUICC proposes a new challenge on how mobile devices access eSIM content. For example, MNOs share many of the same properties with each other. As a result, the eSIM can include applications with the same application identification information. As a result, a mobile device having an eUICC that includes two or more eSIMs that share the same may not be successful in selecting and accessing a particular application of the two or more eSIMs. Specifically, existing protocols for accessing applications involve referencing only AIDs. This is not sufficient for a mobile device to access a particular eSIM application because AID alone cannot uniquely identify a particular eSIM application, including the application. Accordingly, there is a need to allow mobile devices, particularly processors included in mobile devices, to access specific eSIM content, such as specific eSIM applications, in a multiple eSIM environment.

  An eUICC can store multiple eSIMs, and each eSIM can store its own content (eg, application and file structure). With the configuration of multiple eSIMs on an eUICC, the problem arises of how to identify and access different eSIM content stored in the same eUICC. For example, when a mobile device sends a read command (command) to a file identified by file identification information (FID) using an existing interface, a conflict occurs because the same FID may exist in a plurality of eSIMs. sell. As a result, the eUICC will not be able to access the file for a particular eSIM using only the FID. Embodiments will now clarify that this problem is addressed by introducing special commands that can be sent from the mobile device to the eUICC. In particular, the special command includes identification information that uniquely identifies the eSIM for selection, and the special command instructs the eUICC to activate or deactivate the content contained in the eSIM. To do. After selecting an eSIM, the mobile device can view the eSIM content (eg, application and file structure). In this way, the mobile device can access the content of a particular eSIM stored in the eUICC even though something similar exists across other eSIMs stored in the eUICC.

  Furthermore, when attempting to access an application based solely on application identification information (AID) associated with the application, a conflict may occur in the eUICC. In order to remedy this defect, a logical channel can be used to distinguish how eUICC accesses the eSIM. Logical channels are defined in existing standards so that mobile devices can open multiple logical channels to access different applications in the eSIM. Specifically, existing standards indicate that an eSIM application must first be selected on a logical channel before the application can be accessed. Therefore, the operating system (OS) running on eUICC has prior knowledge of eSIM selected on the logical channel. Embodiments will now be described that extend this functionality to allow different eSIM selections (for the application itself) on different logical channels. Subsequently, each application is uniquely identified by a SELECT (eSIM, AID) command. A terminal (eg, a baseband processor) of a mobile device that exchanges information with the eUICC can know different eSIMs managed by the eUICC, for example, by managing various eSIM IDs. In this way, the mobile device processor can simultaneously access a particular application across multiple eSIMs in the eUICC.

  This summary is provided only for the purpose of summarizing some exemplary embodiments in order to provide a basic understanding of some aspects of the subject matter described herein. Thus, it will be understood that the functions described are exemplary only and should not be construed as narrowing the scope or spirit of the described subject matter in any way. Other features, aspects, and subject advantages will be apparent from the detailed description, drawings, and claims.

The drawings are for illustrative purposes and provide exemplary configurations and arrangements for the apparatus and method according to the disclosed invention provided to wireless computing devices. These drawings do not limit any formal and detailed changes made to the embodiments by those skilled in the art without departing from the spirit and scope of the embodiments. Embodiments will be readily understood by the following detailed description of the invention in conjunction with the accompanying drawings. The same reference numbers indicate similar components.
1 is a block diagram illustrating different components of a wireless system including an MNO, a base station, and a mobile device configured to perform various techniques according to embodiments. FIG. 2 is a more detailed block diagram of a particular configuration of the system of FIG. 1 according to an embodiment. The block diagram of eSIM which concerns on embodiment. The block diagram of eUICC which memorize | stores several eSIM which concerns on embodiment. FIG. 3 is a detailed diagram of a file structure of an application according to the embodiment. 5 is a timing chart showing selection of a specific eSIM application included in the eUICC according to the embodiment. 4 is a timing chart showing selecting and accessing one eSIM application among a plurality of eSIMs including the application according to the embodiment. The frame structure which supports the timing chart of FIG. 5A which concerns on embodiment. 6 is a flowchart illustrating a method related to FIGS. 5A and 5B according to the embodiment. FIG. 3 is a block diagram of an eUICC that stores a plurality of eSIMs from a plurality of eSIM providers according to an embodiment. FIG. 3 is a block diagram of an eUICC that stores a plurality of eSIMs selected by a terminal using a logical channel according to an embodiment. FIG. 6B is a flowchart of a method related to FIGS. 6A and 6B according to the embodiment. FIG. 2 is a detailed view of a computing device capable of executing various components according to an embodiment.

  Exemplary applications of the apparatus and method according to the embodiments described below are provided in this section. These examples are provided merely to add background and help in understanding the described embodiments. It will be apparent to those skilled in the art that the embodiments described herein may be practiced without some or all of these specific details. In other instances, well-known processing steps have not been described in detail in order to avoid unnecessarily obscuring the description of the embodiments. Other applications are possible, not limited to the following examples.

  UICC is a smart card used in mobile terminals for cellular networks including Universal Mobile Telecommunication System (UMTS) and Long Term Evolution (LTE). In particular, the UICC authenticates the subscriber to the cellular network while ensuring the subscriber's personal data completely and securely. UICC stores applications for MNOs and end users for use in the correct deployment of mobile services. UICC is a common multi-application platform that hosts several applications simultaneously.

  UICC is an integration that securely stores international mobile subscriber identity (IMSI) and associated keys used to identify and authenticate subscribers in mobile phone devices (such as mobile phones). It has a SIM which is a circuit. In early implementations, the SIM circuit is incorporated into a removable plastic card. This plastic card is called a SIM card and can be moved between different mobile devices. The SIM card is a unique serial number, integrated circuit card ID (ICCID), international mobile device subscriber identification information (IMSI), security authentication information and encryption information, temporary information about the local network, a list of services accessed by the user , Have authentication information (eg password).

  Over time, the role of UICC has evolved to become the only network owned MNO that is under the control of the subscriber. Thus, UICC is a useful tool for MNOs to securely provide services to subscribers. And because of the portability and ability to operate on many mobile handsets, UICC allows MNO to provide network specific services and to customize regardless of the mobile phone being used. The uniqueness of UICC provides all MNOs and subscribers with a variety of improved functions.

  As described above, the UICC is integrated directly into the mobile device system board (ie, eUICC), eg, multiple electronic SIMs (such as one eSIM for a local MNO and another eSIM for an international MNO). eSIM). These eUICCs offer a number of advantages over conventional removable UICCs. For example, some eUICCs have rewritable memory that facilitates eSIM updates to access extended functionality provided by the MNO. In particular, each eSIM can have its own file structure and application. The problem to be solved is how to identify multiple eSIMs on the same eUICC and access their content. For example, if a mobile device sends a read command to a file identified by an FID using an existing interface, the same FID may exist in other eSIMs and may be related to other eSIMs Conflict may occur. As a result, eUICC will not know how to access the particular file identified by the FID.

  Other considerations include: The standard for UICC implementation specifies that AID is used to identify applications implemented in the SIM. The AID has an application provider ID of 5 bytes and an individual usage AID of 11 bytes (or less). The AID is determined while the card is prepared, such as during manufacture by a vendor. A problem with the eUICC implementation relates to the ambiguity of AID in multiple eSIM environments. As already revealed, an eUICC can have multiple eSIMs. In particular, these eSIMs may come from different, uncoordinated sources such as AT & T and T-Mobile. Since the uniqueness of AID is not preserved across different eSIMs, in some cases, different sources can use the same AID. Thus, a conflict occurs when an application has multiple eSIMs that share the same AID.

  Because of the foregoing problems, the embodiments describe techniques by which a mobile device can send a special command to an eUICC with identification information that uniquely identifies an eSIM managed by the eUICC. In particular, this special command can instruct the eUICC to activate or deactivate the content that the eSIM has. When an eSIM is selected, the eSIM file structure and application are made accessible by the mobile device using existing commands (eg, read commands). The mobile device can select a different eSIM by deactivating the active eSIM and then operating a different eSIM. The foregoing techniques provide compatibility benefits in that an eUICC with an active eSIM can be implemented in a legacy device and can work well on the legacy device. Such a function requires the eUICC to store the last selected eSIM, and when the legacy device is launched, the eUICC automatically selects the previously selected eSIM.

  As previously mentioned, logical channels are defined in the existing standards that allow mobile devices to open different logical channels to access different applications within the eSIM. In the present embodiment, it will be described that the function is extended to select different eSIMs (for applications) in different logical channels. This feature allows a mobile device to access multiple eSIMs and associated content simultaneously. With regard to accessing the same application in multiple eSIM environments, the solution can be defined using standard external entity coordination principles. The principle is: 1) AID within the same eSIM is unique. I.e. guaranteed by eSIM vendors (similar to existing UICC standards), 2) AIDs from different eSIM vendors may overlap with eUICC.

  By operating the eUICC OS, the mobile device can open multiple logical channels to the eUICC, avoiding AID conflicts. That is, an application's associated eSIM is first associated with a given logical channel before the application is selected. In this way, the eUICC OS can know that the eSIM is associated with an AID on a given logical channel. Each application is uniquely identified by a SELECT (eSIM ID, AID) command. The terminal (ie baseband processor) knows the different eSIMs managed by the eUICC, for example by managing various eSIM IDs. This answer can be implemented without major changes to the interface.

  Thus, the foregoing approach provides a technique for the system to identify different eSIMs in the eUICC and access their content. A more detailed description will become apparent below in connection with FIGS. 1, 2, 3A, 3B, 3C, 4, 5A, 5B, 5C, 6A, 6B, 6C and 7. These figures represent detailed views of systems and methods in which these techniques are implemented and used.

Terms related to the embodiments are described next.
AID-Application identification information for identifying an application in UICC. The AID has registered application provider identification information (RID) of 5 bytes and individual use application extended identification information (PIX) of up to 11 bytes. The AID of the application can be unique in a given UICC. The AID is determined while the card is prepared, for example, during the manufacturing process by the vendor.
APDU-Application Protocol Data Unit-EUM-eUICC Manufacturer-ICCID-Integrated Circuit Card ID-A unique number to identify the eSIM in the eUICC.
IMSI—International mobile device subscriber identification information. IMSI is unique identification information owned and issued by an MNO that identifies users and makes mobile devices belong to networks and user services.
-MCC-Mobile country code-MNO-Mobile operator. An entity that provides access capabilities and communication services to customers through a mobile network infrastructure.
OTA platform—over the air platform. An MNO based platform that is used for UICC remote management and enables eUICC eSIM.
SIM-subscriber identity module eSIM-electronic SIM. eSIM is a software-based SIM, or “soft SIM”. The eSIM can be a combination of file structure, data, and applications that are supplied or exist in the eUICC.
-SM-SR-Subscription Manager-secure manager secure routing
-UICC-Universal integrated circuit card-eUICC-Embedded UICC
USIM—Universal subscriber identification module. USIM is a network access application (NAA) for UMTS. The USIM on the UICC may contain information that identifies the subscriber.

  In accordance with various embodiments described herein, the terms “wireless communication device”, “wireless device”, “mobile device”, “mobile station”, and “user terminal (UE)” relate to the embodiments disclosed herein. It can be used interchangeably to describe one or more common consumer electronics devices that can perform the processing procedure. According to various embodiments, any one of these consumer electronic devices can be a wireless wide area network (WWAN), a wireless metro area network (WMAN), a wireless local area network (WLAN), a wireless personal area. Communicate over network (WPAN), near field communication (NFC), cellular wireless network, 4th generation (4G) LTE, LTE advance (LTE-A), 5G or other current or future developed cellular wireless networks Cellular phones or smartphones, tablet computers, laptop computers, notebook computers, personal computers, netbook computers capable of wireless communication using one or more wireless communication protocols Related to computers, media player devices, electronic books, MiFi® devices, wearable computing devices, and other types of computing devices as well.

  In some embodiments, a wireless communication device includes a set of client devices called a station, a client wireless device, a client communication device, and can operate as part of a wireless communication system, e.g., part of a WLAN, It is connected to a part of WPAN or an access point (AP) such as an ad hoc wireless network. In some embodiments, the client device is a wireless communication device capable of communicating via WLAN technology according to a wireless local area network communication protocol. In some embodiments, the WLAN technology includes a Wi-Fi (or more generally WLAN) wireless communication subsystem or radio. A Wi-Fi radio is one or more of IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11-2007, IEEE 802.11n, IEEE 802.11-2012, IEEE 802.11ac, or current or future developed The Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology, such as 802.11 technology, can be implemented.

  Further, the UE described herein may be configured in a multi-mode communication device capable of communicating with different third generation (3G) or second generation (2G) RATs. In these scenarios, multi-mode UEs can prefer to connect to LTE that offers faster data rate throughput compared to conventional 3G with lower data rate throughput. For example, in some embodiments, a multi-mode UE may use an evolved high-speed packet access (HSPA +) network, code division multiple access (CDMA) 2000, evolution when an LTE or LTE-A network is not available. ) It may be configured to fall back to a conventional 3G network such as a data only (EV-DO) network.

  FIG. 1 depicts a block diagram of different components of a system 100 that is configured to implement the various described techniques according to some embodiments. Specifically, FIG. 1 represents a high level appearance of the system 100 and shows the mobile device 102, including one or more base stations 112, one or more MNOs 114. According to one embodiment, mobile device 102 represents a wireless communication device (eg, smartphone, tablet, laptop, etc.) that can communicate with at least one MNO 114 via at least one base station 112. As shown in FIG. 1, the mobile device 102 can include a processor 104, a memory 106, an eUICC 108, and a baseband processor 110. The eUICC 108 is a hardware element that is, for example, incorporated into the system board of the mobile device 102 and configured to provide a more flexible environment than a conventional removable UICC. As described in more detail below, eUICC 108 may have various hardware and software components that allow eUICC 108 to manage eSIMs according to the techniques described herein.

  FIG. 2 is a detailed diagram 200 of the mobile device 102 of FIG. 1 according to one embodiment. As shown in FIG. 2, the mobile device OS 202 and one or more applications 204 can be executed on the mobile device 102 by the processor 104 and the memory 106. FIG. 2 shows the various hardware and software components that the eUICC 108 has. More specifically, the eUICC 108 includes a processor 210 and memory 212 that allow the eUICC OS 214 to execute on the eUICC 108 and manage one or more eSIMs 216. With this configuration, the processor 104, the processor 210, and the baseband processor 110 operate in concert to allow the mobile device 102 to access services provided by the at least one MNO 104.

  FIG. 3A represents a block diagram 300 of an eSIM 302 having a first application 306 and a second application 308 and an application file structure 304. As shown in FIG. 3A, the first application 306 and the second application 308 are identified by application identification information, a first AID 307 and a second AID 309, respectively. First application 306 and second application 309 represent different applications provided by the MNO associated with eSIM 302. With the application identification information, the first AID 307 and the second AID 309, the mobile device 102 can uniquely access either the first application 306 or the second application 308. This access capability allows the mobile device 102 to properly access the application file structure 304, as described in detail below with respect to FIG. 3C.

  FIG. 3B is a diagram representing a block 350 of eUICC 352 that stores a plurality of eSIMs 216 represented as a first eSIM 354 and a second eSIM 356. In this embodiment, applications associated with the first eSIM 354 and the second eSIM 356 (not shown in FIG. 2B) are identified by the same application identification information, the first AID 307. Accordingly, the first eSIM 354 and the second eSIM 356 application may be the same application. And applications can be provided by different MNOs. Referring to FIG. 3B, the ICCID is the same for the first eSIM 354 and the second eSIM 356. When the baseband processor 110 reads the ICCID, there may be a conflict because the unique application identification information (and thus the application) cannot be identified. Therefore, the application file structure will not be properly identified.

FIG. 3C is a diagram illustrating details 370 of the application file structure 304 for the eSIM 302 of FIG. 3A. File identification information (FID) is used to identify and identify a particular file. The file types included in FIG. 3C are as follows.
Individual file (DF): Includes basic files (elementary file (EF)) or other individual files with access conditions and options. The DF is referenced by the FID.
Application individual file (ADF): entry point to the application. Application DF (ADF) is a specific DF that includes all DFs and EFs of the application.
Basic file (EF): A valid IMSI value must be present by default in the IMSI basic file (EF IMSI) in the SIM when the SIM card is manufactured.
・ Master file (MF)

The application is uniquely identified by the AID and obtained from the EF _DIR . AID is used to select an application. EF _DIR , EF _PL and EF _ICCID are mandatory and are directly under MF. DF _TELECOM is optional and, if present, is under MF. DF _TELECOM may contain application independent information.

  FIG. 4 depicts a timing chart 400 for selecting a particular eSIM application included within the eUICC. The process begins with the baseband processor 110 of the mobile device 102 requesting a channel for communication. eUICC responds, for example, by selecting channel 1. Baseband processor 110 sends a SELECT (AID) command to request access to the application associated with the specified AID. The baseband processor 110 can repeat this process to access other applications. Thus, two parallel sessions can be active. This method works well for selecting an appropriate application within the eSIM of the structure described in FIG. 3A. However, if there are multiple eSIMs in the eUICC (eg, FIG. 3B), a conflict may occur because the applications may be the same. Applications are published by different MNOs, and eSIMs can have the same ICCID. As a result, for example, the application identification information can be the same as in the first AID 307, so the method of FIG. 4 may not identify an appropriate application file structure.

  FIG. 5A is a timing chart showing selecting and accessing one eSIM application from among a plurality of eSIMs having applications. Initially, the baseband processor 110 sends a SELECT (eSIM ID) command to the eUICC identifying the eSIM and requesting access to the eSIM. The eUICC sends an acknowledgment message (eg, OK) indicating the active state as a response. If the mobile device 102 is inactive, the baseband processor 110 cannot access the eSIM. Based on MNO regulations, only one eSIM can operate at a time. The SELECT (eSIM ID) can select a specific eSIM, such as a first eSIM 354 or a second eSIM 356, for example. P1 and P2 described in FIG. 5B are described in more detail below, but can have values that specify the type of SELECT command, eg, eSIM selection. To switch between the first eSIM 354 and the second eSIM 356, the baseband processor 110 can issue a “non-select” command and make a new selection. For example, SELECT (P1, P2) indicates deselecting the first eSIM, and SELECT (P3, P4) indicates selecting the second eSIM.

  When the eSIM is running, the baseband processor 110 can respond with a SELECT (first AID 307) command that represents a request for a particular application (and application file structure). After an acknowledgment from the eUICC, the baseband processor 110 can send a SELECT (ICCID) to select a specific application. After an acknowledgment from the eUICC, the baseband processor 110 can send a READ BINARY command to the eUICC. The READ BINARY response message may include EF content having a transparent structure. In addition, the eSIM can have a subsidy lock that prevents the eUICC from being programmed to select a particular MNO. An auxiliary lock can limit MCC / MNC selection.

  FIG. 5B is a frame structure 550 that supports the timing chart 500. As shown in FIG. 5B, the frame structure 550 has an APDU header and an eSIM ID. The APDU header includes the following frames: SELECT CLASS, INS (instruction code), P1 / P2, LEN (length). The APDU header is included in the standard for eUICC operation. The same INS code included in the standard is used in the timing chart 500. In order to provide unique identification information for applications, P1 / P2 frames are assigned special values not included in the standard. By the programming of P1 / P2, the baseband processor 110 can execute the communication method shown in the timing chart 500. In this way, the baseband processor 110 can select and access the application of interest. As described above, an eSIM ID is a combination of file structure, data and application that is present or provided in eUICC, and when enabled, allows access to a specific mobile network infrastructure.

FIG. 5C is a flowchart 570 representing the method associated with FIGS. 5A and 5B. The steps in the flowchart are executed by the baseband processor 110 and are executed as follows.
1. Send a SELECT (eSIM ID) command to the eUICC to identify the eSIM 572. -572
2. After receiving the reception confirmation, a SELECT (first AID) command is transmitted to the eUICC in order to select an application related to the identification information “first AID”. -574
3. After receiving the receipt confirmation, a SELECT (ICCID) command is sent to confirm the ICCID and select an eSIM having a file structure (eg, application file structure 304). -576
4). After receiving the reception confirmation, a READ BINARY command designating a specific file is transmitted. -578
5. Receive a specific file. -580

  In particular, this method is backward compatible with standard designed eUICC. That is, the eUICC OS can store the last selected eSIM. Here, eSIM ID selects eSIM. P1 / P2 coding determines a particular type of SELECT command, such as a select command for selecting an eSIM.

  FIG. 6A is a block diagram 600 of an eUICC 602 having a first eSIM 604 and a second eSIM 606. As shown in FIG. 6A, the first eSIM 604 and the second eSIM 606 have an application whose AID is “n”, which indicates a problem that may occur when eUICC is executed. In particular, different eSIMs may come from different unregulated sources, where these sources are denoted as eSIM provider # 1 (eg AT & T) and eSIM provider # 2 (eg T-Mobile). Different sources can use the same AID for applications included in the eSIM. This can cause a conflict when accessing a specific application by AID. Thus, a conflict can occur if the eUICC has multiple eSIMs with the same application sourced from different sources.

  The answer to the above problem is illustrated in block diagram 650 of FIG. 6B. As shown in FIG. 6B, block diagram 650 includes an eUICC 672 having a first eSIM 674 and a second eSIM 676. Each of these eSIMs supports the same application and AID. That is, in FIG. 6B, APP and AID = n. Here, the eUICC 678 is configured to coordinate the transmission of application information to the terminal 680 (ie, the baseband processor 110 of FIG. 1) based on eSIM identification information (eg, eSIM ID) and application identification information (AID). ing. More specifically, eUICC OS 678 is configured to establish a logical channel using (eSIM ID, AID). These logical channels eliminate the described possible conflicts that may occur.

  The embodiment of block diagram 650 supports several functions. AIDs within the same eSIM are unique. That is, it is guaranteed by the eSIM vendor as in the conventional UICC. However, AIDs from different eSIMs may overlap in eUICC between different eSIMs. AID conflicts can be avoided by operating eUICC OS678. For an application, its associated eSIM must first be selected on a given logical channel before the application is selected. Thus, eUICC OS 678 can know which eSIM is associated with this AID on a given logical channel. Each application is uniquely identified by a command (eSIM ID, AID). The terminal knows the different eSIMs on the eUICC by eSIM ID. In other embodiments, multiple eSIMs can operate on eUICC using multiple logical channels. Each logical channel can select a different MNO simultaneously. Accordingly, the mobile device 102 can access two or more MNOs simultaneously.

FIG. 6C shows a flowchart 670 for the method associated with FIGS. 6A and 6B. The method includes the following steps, which are performed by the eUICC OS 678 of FIG. 6B.
1. Associate an eSIM with a specific logical channel. -672
2. Associate AID with eSIM. -674
3. A mobile terminal (eg, mobile terminal 680 in FIG. 6B) is instructed to access the AID via the logical channel using the {eSIM ID, AID} command described herein. Terminal 680 may correspond to baseband processor 110 shown in FIG. 1 and described in more detail. -676

  FIG. 7 is a detailed view of a computing device 700 that is used to implement various components described herein and in accordance with embodiments. In particular, this detailed view illustrates various components that may be included in the mobile device 102 shown in FIG. According to FIG. 7, the computing device 700 may have a processor 702 that corresponds to a microprocessor or controller for controlling the overall operation of the computing device 700. The computing device 700 can include a user input device 708 for a user of the computing device to interact with the computing device 700. For example, the user input device 708 may take various forms such as buttons, keypads, dials, touch screens, voice input interfaces, optical / image input interfaces, sensor data type input, and the like. Further, the computing device 700 can include a display 710 (screen display) that is controlled by the processor 702 to display information to the user. The data bus 716 can facilitate data transmission between at least the storage device 740, the processor 702, and the controller 713. The control device 713 can interface with the device control bus 714, and can control different devices through the device control bus. The computing device 700 can have a network / bus interface 711 that connects to the data link 712. In the case of wireless connection, the network / bus interface 711 can include a wireless transmission / reception device.

  The computing device 700 can comprise a single storage device or multiple storage devices and can have a storage device 740 that includes a storage management module for managing one or more partitions of the storage device 740. In some embodiments, the storage device 740 may include flash memory, semiconductor (solid state) memory, or the like. The computing device 700 may also include random access memory (RAM) 720 and read only memory (ROM) 722. The ROM 722 can store programs, utilities, and processes in a nonvolatile manner. The RAM 720 provides volatile data storage and can store instructions related to software processing operations different from those described herein. The computing device 700 may further include a secure element 750 that may be represented in eUICC as described and illustrated in FIGS.

  Various aspects, embodiments, implementations or features of the described embodiments can be used separately or in combination. Various aspects of the embodiments may be implemented by software, hardware or a combination of hardware and software. Embodiments can also be implemented as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of computer readable media include read only memory, random access memory, CDROM, DVD, magnetic tape, hard disk drive, solid state drive, optical data storage device. The computer readable medium can be distributed over a networked computer system so that the computer readable code is stored and executed in a distributed fashion.

  The descriptions above are for illustrative purposes, and specific terminology is used for all understanding of the description of the embodiments. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the described embodiments. The foregoing description of specific embodiments exists for purposes of explanation and illustration. They are not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Many modifications and variations will occur to those skilled in the art in view of the above teachings.

Claims (20)

A method for accessing an electronic subscriber identity module (eSIM) application managed by an embedded universal integrated circuit card (eUICC) comprising:
In the eUICC,
Receiving the command to select a first eSIM corresponding to the eSIM identification information (eSIM ID) included in the command from the baseband processor via the logical channel;
Associating the logical channel with the first eSIM;
A request to access the first eSIM application managed by the EUICC, said method comprising the steps of receiving from the baseband processor via a logical channel, the application is shared by the second eSIM Applications associated with the application identification information (AID), the step,
Enabling the baseband processor to access the application associated with the AID of the first eSIM via the logical channel in response to the request.   The method of claim 1, wherein each application of the first eSIM is associated with a unique AID.   The method of claim 2, wherein each eSIM managed by the eUICC is associated with a unique eSIM ID. The request to access the application of the first eSIM includes a SELECT (eSIM ID, AID) command having an application protocol data unit (APDU) header, and the APDU header determines the type of the SELECT command P1 The method of claim 1, comprising: and P2 fields, wherein the values of the P1 and P2 fields represent eSIM selection.   The method of claim 1, wherein at least two eSIMs are simultaneously active in the eUICC.   The method of claim 1, wherein the baseband processor simultaneously accesses different active eSIM applications in the eUICC using different logical channels. A mobile device,
An embedded universal integrated circuit card (eUICC) that manages an electronic subscriber identity module (eSIM);
A baseband processor;
And at least one memory,
The at least one memory is executed by the baseband processor to the baseband processor,
Sending a first command for selecting the first ESIM, to the eUICC via a first logical channel,
Sending a second command for selecting a second eSIM to the eUICC via a second logical channel, wherein each of the first eSIM and the second eSIM has the same application identification comprising the application associated with the information (AID), the step,
Issuing a third command to the eUICC that includes both the eSIM identification information (eSIM ID) associated with the first eSIM and the AID via the first logical channel ;
Accessing the application included in the first eSIM using the first logical channel;
A mobile device configured to store an instruction to execute.   The mobile device of claim 7, wherein the AID is unique among other AIDs associated with different applications of the first eSIM and the second eSIM, respectively.   The mobile device of claim 7, wherein each eSIM managed by the eUICC is associated with a unique eSIM ID. The mobile device according to claim 7, wherein the third command includes a SELECT (eSIM ID, AID) command.   The SELECT (eSIM ID, AID) command includes an application protocol data unit (APDU) header including P1 and P2 fields for determining the type of the SELECT command, and the values of the P1 and P2 fields represent eSIM selection. The mobile device according to claim 10.   The mobile device of claim 7, wherein at least two eSIMs are active in the eUICC simultaneously.   The mobile device of claim 7, wherein the baseband processor simultaneously accesses different active eSIM applications in the eUICC using different logical channels. When executed by a baseband processor of a mobile device, executing a step causes a command issued by the baseband processor to be sent to a specific electronic device managed by the mobile device embedded universal integrated circuit card (eUICC) A computer program comprising instructions for sending to an active subscriber identity module (eSIM), said step comprising:
Sending a first command for selecting the first ESIM, to the eUICC via a first logical channel,
Sending a second command for selecting a second eSIM to the eUICC via a second logical channel, wherein each of the first eSIM and the second eSIM has the same application identification Including an application associated with the information (AID);
Issuing a third command to the eUICC that includes both the eSIM identification information (eSIM ID) associated with the first eSIM and the AID via the first logical channel ;
Accessing the application included in the first eSIM using the first logical channel;
A computer program comprising:   15. The computer program product of claim 14, wherein the AID is unique among other AIDs associated with different applications of the first eSIM and the second eSIM.   The computer program product of claim 14, wherein each eSIM managed by the eUICC is associated with a unique eSIM ID. 15. The computer program according to claim 14, wherein the third command includes a SELECT (eSIM ID, AID) command.   The SELECT (eSIM ID, AID) command includes an application protocol data unit (APDU) header including P1 and P2 fields for determining a type of the SELECT command, and the values of the P1 and P2 fields represent eSIM selection. The computer program according to claim 17.   The computer program product of claim 14, wherein at least two eSIMs are simultaneously active in the eUICC.   15. The computer program product of claim 14, wherein the baseband processor accesses different eSIM applications simultaneously using different logical channels.

Images