WO2025038918A1

WO2025038918A1 - Globalization of contactless applet information

Info

Publication number: WO2025038918A1
Application number: PCT/US2024/042645
Authority: WO
Inventors: Li Li; Aurelien P RABOISSON; Jean-Marc Padova; Ngabin S NG
Original assignee: Apple Inc.
Priority date: 2023-08-16
Filing date: 2024-08-16
Publication date: 2025-02-20

Abstract

An apparatus configured to generate, for transmission to a network component associated with a mobile network operator (MNO), a user equipment (UE) state comprising information related to one or more embedded subscriber identity module (eSIM) profiles, wherein the information comprises whether a UE currently has one or more eSIM profiles associated with the MNO and process, based on signals received from the network component, an eSIM profile.

Description

Globalization of Contactless Applet Information

Inventors: Li Li, Aurelien P Raboisson, Jean-Marc Padova and Ngabin S Ng

PRIORITY/ INCORPORATION BY REFERENCE

[0001] This application claims priority to U.S. Provisional Application Serial No. 63/519,882 filed on August 16, 2023, and entitled "Globalization of Contactless Applet Information," the entirety of which is incorporated by reference herein.

BACKGROUND

[0002] Existing embedded subscriber identity modules (eSIMs) profiles typically contain data only related to telecommunications capabilities. The storage capabilities of existing eSIMs is typically small, on the order of tens to hundreds of kilobytes. Expansion of eSIM capabilities to support contactless functionality (such as payment, transit, access, identification, and lock/key security) is needed. eSIM storage capability is expected to increase substantially in the future but Embedded Universal Integrated Circuit Card (eUICC) chipsets may lack sufficient storage to facilitate the aforementioned use cases. Operations and logic are needed to facilitate enhanced eSIM profile functionality.

Summary

[0003] Some example embodiments are related to an apparatus having processing circuitry configured to generate, for transmission to a network component associated with a mobile network operator (MNO) , a user equipment (UE) state comprising information related to one or more embedded subscriber identity module (eSIM) profiles, wherein the information comprises whether a UE currently has one or more eSIM profiles associated with the MNO and process, based on signals received from the network component, an eSIM profile.

[0004] Othe r example embodiments are related to an apparatus having processing circuitry configured to store a first embedded subscriber identity module (eSIM) profile associated with a mobile network operator (MNO) , wherein the first eSIM profile comprises contactless application information allowing a user equipment (UE) to complete contactless transactions based on the contactless application information, store a second eSIM profile associated with the MNO, wherein the second eSIM profile comprises only telecom information allowing the UE to perform telecommunications related operations, disable the first eSIM profile and, when the second eSIM profile is enabled, perform a contactless transaction using the contactless application information of the first eSIM profile.

[0005] Still further example embodiments are related to an apparatus having processing circuitry configured to process, based on signals received from a user equipment (UE) , a UE state comprising information related to one or more embedded subscriber identity modules (eSIM) profiles installed on the UE, select an eSIM profile to assign to the UE based on the UE state and prepare, for transmission to the UE, the eSIM profile.

Brief Description of the Drawings

[0006] Fig. 1 shows an example network arrangement according to various example embodiments. [0007] Fig. 2 shows an example user equipment (UE) according to various example embodiments.

[0008] Fig. 3 shows an example subscription manager data preparation+ (SM-DP+) according to various example embodiments.

[0009] Fig. 4 shows an example embedded Universal Integrated Circuit Card (eUICC) arrangement according to various example embodiments .

[0010] Fig. 5 shows an example method of a SM-DP+ assigning eSIM profiles to a UE according to various example embodiments.

[0011] Fig. 6 shows an example method for a UE to manage eSIM profiles according to various example embodiments.

Detailed Description

[0012] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments relate to operations and logic for eSIM profile customization based on user equipment (UE) device states via a subscription manager data preparation+ (SM-DP+) which is a network element (typically a server) that prepares, stores, and protects carrier profiles (including operator credentials) . Additional embodiments relate to operations and logic for eSIM profile customization in dual SIM dual standby (DSDS) scenarios. Still further embodiments relate to near field communications (NFC) as applied to the aforementioned eSIM customized profiles. [0013] The example embodiments are described with regard to a user equipment (UE) . However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may include an eSIM (e.g., eUICC) and that may establish a connection to a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any electronic component.

[0014] The example embodiments are also described with reference to a 5G New Radio (NR) network. However, the example embodiments may also be implemented in other types of networks, including but not limited to LTE networks, future evolutions of the cellular protocol (e.g., 5G advanced, 6G, etc.) , or any other type of network. In the examples, it will be considered that the example UE receives eSIM profiles and other information using the 5G network. However, the UE may receive the eSIM profiles and other information via any wired or wireless network .

[0015] The example embodiments are also described with reference to contactless services that may be a service that removes physical contact from transactions or other interactions but may use electronic interactions between a user device (e.g., a UE) and other electronic systems. The electronic interactions may include the exchange of information via wireless communications such as WiFi communications, Bluetooth communications, near-field communications (NFC) , etc. Nonlimiting examples of contactless services include self-checkout and contactless payments (e.g., a user can scan a code on their device or bring their device near a payment terminal or transit gate to complete a transaction) .

[0016] The example embodiments are also described with reference to a subscription manager data preparation+ (SM-DP+) service that is a network element (typically a server) that prepares, stores, and protects carrier profiles (including operator credentials) . However, the nomenclature SM-DP+ is only example and other entities may refer to a device, component or function performing the functionality of the SM-DP+ as described herein using different terminology.

[0017] The example embodiments describe various operations and logic for SM-DP+ customization of eSIM profiles based on a state of the user equipment (UE) . Additional operations and logic are disclosed for eSIM profile customization as applied to DSDS and NFC.

[0018] Fig. 1 shows an example network arrangement 100 according to various example embodiments. The example network arrangement 100 includes a UE 110. The UE 110 may be any type of electronic component that is configured to communicate via a network, e.g. , mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (loT) devices (including connected vehicles) , etc. An actual network arrangement may include any number of UEs being used by any number of users. Thus, the example of one UE 110 is merely provided for illustrative purposes.

[0019] The UE 110 may be configured to communicate with one or more networks. In the example of the network configuration 100, the network with which the UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120. The UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, a next generation RAN (NG-RAN) , a legacy cellular network, etc. ) and the UE 110 may also communicate with networks over a wired connection. With regard to the example embodiments, the UE 110 may establish a connection with the 5G NR RAN 120. Therefore, the UE 110 may have a 5G NR chipset to communicate with the NR RAN 120.

[0020] The 5G NR RAN 120 may be portions of a cellular network that may be deployed by a network carrier (e.g., Verizon, AT&T, T-Mobile, etc. ) . The RAN 120 may include cells or base stations that are configured to send and receive traffic from UEs that are equipped with the appropriate cellular chip set. In this example, the 5G NR RAN 120 includes the gNB 120A. However, reference to a gNB is merely provided for illustrative purposes, any appropriate base station or cell may be deployed (e.g., Node Bs, eNodeBs, HeNBs, eNBs, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc. ) .

[0021] Any association procedure may be performed for the UE 110 to connect to the 5G NR RAN 120. For example, as discussed above, the 5G NR RAN 120 may be associated with a particular network carrier where the UE 110 and/or the user thereof has a contract and credential information (e.g. , stored on a SIM card) . Upon detecting the presence of the 5G NR RAN 120, the UE 110 may transmit the corresponding credential information to associate with the 5G NR RAN 120. More specifically, the UE 110 may associate with a specific cell (e.g. , gNB 120A) . [0022] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 manages the traffic that flows between the cellular network and the Internet 140. The IMS 150 may be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide the multimedia services to the UE 110. The network services backbone 160 is in communication either directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a suite of services that may be used to extend the functionalities of the UE 110 in communication with the various networks.

[0023] In some example embodiments, the SM-DP+ may be included as part of the network services backbone 160. The SM- DP+ may be a network element (typically a server) that prepares, stores, and protects carrier profiles (including operator credentials) . The SM-DP+ being included in the network services backbone 160 is only example and the SM-DP+ may be included as part of other network services or as a third party service that is connected to the network.

[0024] Fig. 2 shows an example UE 110 according to various example embodiments. The UE 110 will be described with regard to the network arrangement 100 of Fig. 1. The UE 110 may represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input/output (I/O) device 220, a transceiver 225, and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a battery that provides a limited power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, sensors to detect conditions of the UE 110, etc. The UE 110 may include an eUICC 240, which may be a hardware component embedded into the UE 110 and configured to store a number of carrier profiles, e.g., eSIM profiles.

[0025] The processor 205 may be configured to execute a plurality of engines for the UE 110. For example, the engines may include an eSIM profile customization engine 235 for performing operations related to determining a UE state and applying an eSIM profile received from an SM-DP+ based on the determined UE state.

[0026] The above referenced engine being an application (e.g., a program) executed by the processor 205 is only an example. The functionality associated with the engines may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications. In addition, in some UEs, the functionality described for the processor 205 is split among two or more processors such as a baseband processor and an applications processor. The example embodiments may be implemented in any of these or other configurations of a UE . [0027] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to show data to a user while the I/O device 220 may be a hardware component that enables the user to enter inputs. The display device 215 and the I/O device 220 may be separate components or integrated together such as a touchscreen.

[0028] The transceiver 225 may be a hardware component configured to establish a connection with the 5G-NR RAN 120. Accordingly, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies) . The transceiver 225 includes circuitry configured to transmit and/or receive signals (e.g. , control signals, data signals) . Such signals may be encoded with information implementing any one of the methods described herein. The processor 205 may be operably coupled to the transceiver 225 and configured to receive from and/or transmit signals to the transceiver 225. The processor 205 may be configured to encode and/or decode signals (e.g., signaling from a base station of a network) for implementing any one of the methods described herein .

[0029] Fig. 3 shows an example SM-DP+ 300 according to various example embodiments. The SM-DP+ 300 may represent a network element that prepares, stores, and protects carrier profiles (including operator credentials) . In some examples, the SM-DP+ 300 may be implemented in a server device such as illustrated in the example of Fig. 3. In other examples, the SM- DP+ 300 may be implemented in a distributed manner such as in a cloud computing implementation or as a network function.

[0030] The SM-DP+ 300 may include a processor 305, a memory arrangement 310, an input/output (I/O) device 315, a transceiver 320, and other components 325. The other components 325 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports to electrically connect the SM-DP+ 300 to other electronic devices and/or power sources, etc.

[0031] The processor 305 may be configured to execute a plurality of engines for the SM-DP+ 300. For example, the engines may include an eSIM profile customization engine 330 for performing operations related to receiving a UE device state and transmitting an eSIM profile to the UE based on the received device state.

[0032] The memory 310 may be a hardware component configured to store data related to operations performed by the SM-DP+ 300. The I/O device 315 may be a hardware component or ports that enable a user to interact with the SM-DP+ 300.

[0033] The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the network arrangement 100 either directly or indirectly. Because the SM-DP+ 300 is typically resident within the network, the transceiver 320 includes a wired network interface such as an Ethernet or other wired type network interface. In some examples, the transceiver 320 may include a wireless interface and operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies) . Therefore, the transceiver 320 may include one or more components (e.g., radios) to enable the data exchange with the various networks and UEs. The transceiver 320 includes circuitry configured to transmit and/or receive signals (e.g., control signals, data signals) . Such signals may be encoded with information implementing any one of the methods described herein. The processor 305 may be operably coupled to the transceiver 320 and configured to receive from and/or transmit signals to the transceiver 320. The processor 305 may be configured to encode and/or decode signals (e.g., signaling from a UE) for implementing any one of the methods described herein.

[0034] In a first aspect of the example embodiments, SM-DP+ customization of eSIM content is disclosed. For example, different versions of an eSIM profile may be assigned to a UE depending on a state of the UE (e.g. , does the UE already have an eSIM profile from a carrier) . The first aspect will be described with reference to the method 500 of Fig. 5.

[0035] Fig. 5 shows an example method 500 of a SM-DP+ assigning eSIM profiles to a UE according to various example embodiments. The method 500 is described from the standpoint of actions performed by the SM-DP+ 300 when interacting with the UE 110.

[0036] In 510, the SM-DP+ 300 stores variants of eSIM profile inventory. For example, the SM-DP+ 300 may store a telecom eSIM profile. The telecom eSIM profile may store data related to typical telecommunications information such as phone number information and user credential information. Throughout this description, this type of eSIM profile variant will be described as a "telecom eSIM profile." The telecom eSIM profile allows the UE to perform telecommunications related operations such as connecting to networks, making phone calls, etc. The SM-DP+ 300 may also store a contactless eSIM profile that may include both telecommunications information and contactless application information related to contactless services. Contactless application information may include information such as payment information (e.g. , credit card information, debit card information, etc. ) , transit information (e.g. , credentials to access a transit system) , and other types of information associated with contactless services. Throughout this description, this type of eSIM profile variant will be described as a "contactless eSIM profile." The contactless eSIM profile allows the UE to complete contactless transactions associated with the corresponding contactless service (e.g., a banking service, a transit service, a payment service, an identification service, a lock service, a key service, etc. ) .

[0037] In 520, the SM-DP+ 300 performs a handshake operation with the UE 110 for an eSIM operation (e.g., for provisioning the UE 110 with one or more eSIM profiles) . In one example, the handshake operation may be an SGP.22 protocol handshake operation. During the handshake operation, the UE 110 may report the status of installed eSIM profile (s) to the SM-DP+ 300. The SGP.22 Technical Specification describes the Global System for Mobile Communications Association (GSMA) protocol for "Remote SIM Provisioning (RSP) Architecture for Consumer Devices." While the example embodiments are described with reference to using the GSMA protocol and corresponding handshake for remote SIMs, the example embodiments are not limited to using this protocol and/or type of handshake.

[0038] In 530, the SM-DP+ 300 determines a device state of the UE 110 with respect to the eSIM profiles currently included in the UE 110 as indicated during the handshake operation. For example, SM-DP+ 300 may determine whether the UE 110 has an eSIM profile from the carrier, e.g. , mobile network operator (MNO) . The SM-DP+ 300 may have a variety of logical flows enabled to determine an eSIM profile to be assigned to the the UE 110 following the handshake operation.

[0039] For example, when the SM-DP+ 300 determines that the UE 110 has an installed eSIM profile from the MNO, in 540, the SM-DP+ 300 may assign a telecom eSIM profile to the UE 110. In another example, when the SM-DP+ 300 determines that the UE 110 does not have an installed eSIM profile from the MNO, in 550, the SM-DP+ 300 may assign a contactless eSIM profile to the UE 110.

[0040] As described above, there is a limited amount of storage on the eUICC 240 of the UE 110 for storing eSIM profiles. As can be seen from the above description, the contactless eSIM profile will typically include more data and correspondingly will use more storage than a telecom eSIM profile. Thus, if the UE 110 already has a contactless eSIM profile stored for the carrier, the UE 110 does not have to restore the information related to the contactless services but may only store the telecommunications information as included in the telecom eSIM profile. As will be described in greater detail below, the example embodiments allow the UE 110 to use the contactless information that is included in the contactless eSIM profile when using the telecom eSIM profile.

[0041] In a second aspect of the example embodiments, operations and logic for dual SIM dual standby (DSDS) for enhanced eSIM profiles is described. For example, it may be considered that the SM-DP+ 300 has performed the operations of Fig. 4 and provisioned the UE 110 with a first eSIM profile (e.g., eSIM 1 profile) that is a contactless eSIM profile from a carrier and a second eSIM profile (e.g., eSIM 2 profile) that is a telecom eSIM profile from the same carrier. The provisioning of the two eSIM profiles onto UE 110 is not required to be performed in accordance with the operations of Fig. 4. This is only provided as one example of how the UE 110 may be provisioned with two eSIM profiles for the same carrier. The example embodiments may be extended to more than two eSIM profiles based on the principles described herein.

[0042] Under the above scenario, when the user is using the UE 110 with the eSIM 1 profile active (e.g., the contactless eSIM profile) and the user accesses a contactless service (e.g. , a tap-to-pay service) , the UE 110 will use the contactless information from the eSIM 1 profile to complete the transaction related to the contactless service.

[0043] On the other hand, if the user is currently using the UE with the eSIM 2 profile active (e.g., the telecom eSIM profile) that does not have the contactless information, the example embodiments still allow the UE 110 to perform contactless services. For example, the contactless capability of the eSIM 1 profile (e.g. , the contactless information) may be offered as a common service shared with the eSIM 2 profile. This means that when the user disables the eSIM 1 profile (e.g., switches to eSIM 2 profile in the DSDS scenario) , the contactless service may remain available to the user utilizing the active eSIM 2 profile.

[0044] These actions may be transparent to the user. For example, the user may have already provided information to activate various contactless services for the carrier (e.g., the user may have provided credit card information for use with contactless services) . The user may expect this information to be available for all eSIM profiles for the carrier. The example embodiments allow this contactless information to be available for all the eSIM profiles but does not require the UE 110 to individually store the contactless information in the eUICC 240 for each eSIM profile.

[0045] Continuing with the second aspect, if the user deletes the eSIM 1 profile, the user may be presented with the option to upgrade the eSIM 2 profile with contactless functionality via the UE 110 contacting the SM-DP+ 300. For example, when the user deletes the eSIM 1 profile, the eSIM customization profile engine 235 of the UE 110 may determine that the contactless information for the carrier is included in the to be deleted eSIM 1 profile. This may cause the UE 110 to present a user interface (UI) message to the user indicating that the contactless services for the carrier will be lost unless the user upgrades the eSIM2 profile (e.g., the current telecom eSIM profile) to a contactless eSIM profile. If the user agrees to this upgrade, the UE 110 may contact the SM-DP+ 300 to receive a new eSIM 2 profile that includes the contactless information so the user has continued access to the contactless services. If the user does not agree, the user may continue to use the UE 110 without access to contactless services.

[0046] In the above example, when it is described that the eSIM 2 profile is upgraded to a contactless eSIM profile, this typically means a new eSIM profile is provisioned to the UE 110 (e.g., an eSIM profile with a different Integrated Circuit Card ID (ICCID) ) . This new eSIM profile includes the telecom information that was included in the eSIM 2 profile and some or all of the contactless information that was included in the eSIM 1 profile. For example, the user may be presented with the option of upgrading the eSIM 2 profile with all of the contactless information from the eSIM 1 profile or only some of the contactless information from the eSIM 1 profile.

[0047] In other examples, when the user deletes the eSIM 1 profile, only the telecom portion (e.g., the telecom information of the eSIM 1 profile may be deleted) . Since the contactless portion of the eSIM 1 profile remains, the user may still have access to the contactless services when using the UE 110 with the eSIM 2 profile active.

[0048] The following provides example details for implementing the second aspect, e.g., allowing the UE 110 to access contactless information even when the UE 110 has an active eSIM profile that only includes telecom information. As will be described in greater detail below with reference to Fig. 4, these example details are related globalizing the contactless information such that it is available to multiple eSIM profiles. This globalization allows for decreased storage use on the eUICC

240 and improved installation times for additional profiles.

[0049] Applications may be explicitly labeled as "global" during installation of an eSIM profile. A global application may be linked to a profile owner and be accessible when at least one profile from the corresponding profile owner is enabled. Global applications may be disabled if all profiles from the corresponding owner are disabled. Global applications may be deleted when a last profile from the corresponding profile owner is deleted.

[0050] Fig. 4 shows an eUICC arrangement 400. The eUICC arrangement 400 features a variety of domains and domain management systems. The eUICC arrangement 400 may be a more detailed description of the subcomponents and subsystems of an eUICC, such as the eUICC 240. The eUICC arrangement 400 features a physical interface 410 which may be the protocols and physical requirements for interface between the UE 110 and the eUICC 240. The eUICC arrangement 400 features a contactless interface 420, which may be the protocols and physical requirements for interface between the eUICC 240 (and associated eSIM) with a contactless service, such as a tap-to-pay interface. Also shown is the eUICC OS + runtime environments 420. The eUICC OS + runtime environments 420 may provide operating-system level functionality and application programming interfaces (APIs) for the eUICC 240.

[0051] Also shown in the eUICC arrangement 400 is a domain manager 422, which may provide eSIM profile installation capabilities and firewall capabilities for eSIM profiles. Still further shown in the eUICC arrangement 400 are system applications 430, such as an eUICC Controlling Authority Security Domain (ECASD) , eSIM manager, and issuer security domain - root (ISD-R) .

[0052] Also shown is secured applications for mobile (SAM) domain 440, which enables secured applets within the eUICC 240. Such applets may be managed by one or more service providers. Shown in the SAM domain 440 are two sub-domains (SDs) bound to the root security domain (i.e. , the SAM domain 440) . Each of the sub-domains may be equivalent to an embedded secure element.

The SAM domain 440 may be isolated from certain functions of the eUICC. An eUICC may contain one or more SAM domains, with substantially similar functionalities as shown in the SAM domain 440. The SAM domain 440 may lack a file system, telecom resources, and global platform architectures (such as the owner shared domain in the eUICC domain 450) .

[0053] Also shown in the eUICC arrangement 400 is an eUICC domain 450. The eUICC domain 450 features an app provider #1 service 452 and an app provider #2 service 454 (henceforth service 452 and service 454) . The services 452 and 454 may be a variety of different contactless services associated with applications (shown as AP #1 app and AP #2 app, respectively) . As an example, the service 452 may be associated with a tap to pay service associated with a first credit card, and the service 454 may be associated with a second credit card. The services 452 and 454 may be any number of different contactless services, such as peer-to-peer file exchange services or transportation services . [0054] The services 452 and 454 are associated with an owner shared domain. The owner shared domain is associated with a specific user (typically associated with an active user account on the UE 110) . The owner-shared domain may also be a globalized domain .

[0055] Also shown in the eUICC domain 450 is a trusted connectivity alliance (TCA) profile #3 460. The TCA profile #3 460 features an issuer security domain profile (ISD-P) which may serve as a container for an eSIM profile. Further shown in the TCA profile #3 460 is a network access application (NAA) , file system, and remote management application (RMA) . Still further shown in the TCA profile #3 460 is a mobile network operator security domain (MNO-SD) , application security domain (AP SD) , Controlling Authority Security Domain (CASD) , and two non-shared applications which may be owned by the TCA profile #3 460 and are not shared with other profiles.

[0056] Also shown in the eUICC domain 450 is a TCA profile #1 from owner (henceforth profile #1) and a TCA profile #2 from owner (henceforth profile #2) , which each contain an NAA, file system, RMA, MNO SD, AP SD, and non-shared apps, which are substantially similar to those described with respect to the TCA profile #3 460. It should be noted that each MNO SD shown has a security key managed by a mobile network operator. Unlike the TCA profile #3 460, the profile #1 and the profile #2 lack a CASD, instead utilizing a Global-CASD (G-CASD) , to be described in further detail below.

[0057] The owner shared domain is accessible by both the profile #1 and the profile #2. The owner shared domain featured a global security domain (G-SD) , a global CASD (G-CASD) , the two shown contactless services 452 and 454, and an additional application .

[0058] The application shown in the owner shared domain may represent one or more global applications which may be management applications deployed by an MNO. These MNO-deployed management applications may manage all contactless services for the UE 110.

[0059] The G-SD may act as the root for all security operations occurring with respect to the owner shared domain. The G-CASD may create and securely provision one or more security keys for any AP SDs utilizing the owner shared domain. For example, the G-CASD may provision the security keys for the AP SDs of the services 452 and 454. The G-CASD may provide cryptographic services for confidential key loading for one or more AP-SDs in the owner shared domain.

[0060] The globalized owner shared domain allows the services 452 and 454 to be accessible to both the profile #1 and the profile #2, regardless of which of the two profiles is currently enabled at the UE 110. In some embodiments, additionally added profiles (e.g., a profile #4 not shown) may be added to the owner shared domain by default. These additional profiles may also access the globalized services 452 and 454. To prevent newly added profiles from accessing the owner shared domain, an indication or flag in the profile may be used to indicate to the eUICC to place the newly added profile into the SAM domain 440 instead of the eUICC domain 450. The use of globalized contactless services reduces storage use on the eUICC because each profile utilizing globalized contactless services does not need to duplicate the resources associated with each contactless services (such as the services 452 and 454) .

[0061] The owner shared domain offers several benefits.

Contactless services utilizing the owner shared domain may be explicitly managed by an MNO, and such contactless services may be commonly shared across different profiles operating in the owner shared domain.

[0062] Fig. 6 shows an example method 600 for a UE to manage eSIM profiles according to various example embodiments. The method 600 describes operations that may be performed by the UE 110 in implementing the first and second aspects of the example embodiments as described above. In addition, the operations may also be implemented with respect to the example eUICC 400 as described with reference to Fig. 4. However, the example embodiments are not limited to the implementation of the eUICC 400 nor do the example embodiments require that both the first and second aspects be implemented together, e.g., the first aspect and/or the second aspect may be implemented separately.

[0063] In 602, the UE 110 transmits a UE state to an SM-DP+ (e.g., the SM-DP+ 300) associated with an MNO. The UE state may include information on any installed eSIM profiles on the UE 110 (such as telecom eSIM profiles or contactless eSIM profiles) .

[0064] In 604, the UE 110 receives an eSIM profile from the SM-DP+ 300 based on the UE state. The SM-DP+ 300 may follow a predetermined logic for what type of eSIM profile to transmit to the UE 110 based on the received UE state. For example, if the UE state indicates that the UE 110 does not have any eSIM profiles associated with the MNO, the SM-DP+ 300 may transmit a contactless eSIM profile to the UE 110.

[0065] In 606, the UE 110 configures the eSIM profile with one or more globalized contactless services. For example, the UE 110 may have a globalized tap-to-pay service in an owner-shared domain. Such a tap-to-pay service would become accessible to the newly received eSIM profile, without needing to duplicate associated contactless resources for each additional eSIM profile utilizing contactless services. Should multiple eSIM profiles from a same MNO be installed, the UE 110 may preserve contactless functionality in a telecom eSIM profile should a contactless eSIM profile be disabled, and offer to upgrade the telecom eSIM profile should the contactless eSIM profile be deleted .

Examples

[0066] In a first example, a method, comprising generating, for transmission to a network component associated with a mobile network operator (MNO) , a user equipment (UE) state comprising information related to one or more embedded subscriber identity module (eSIM) profiles, wherein the information comprises whether a UE currently has one or more eSIM profiles associated with the MNO, and processing, based on signals received from the network component, an eSIM profile.

[0067] In a second example, the method of the first example, wherein the information comprises the UE does not currently have any eSIM profiles associated with the MNO and the eSIM profile comprises telecom information and contactless application information, wherein the telecom information allows the UE to perform telecommunications related operations and the contactless application information allows the UE to complete contactless transactions.

[0068] In a third example, the method of the first example, wherein the information comprises the UE currently has one or more eSIM profiles associated with the MNO and the eSIM profile comprises only telecom information allowing the UE to perform telecommunications related operations.

[0069] In a fourth example, a processor configured to perform any of the methods of the first through third examples.

[0070] In a fifth example, a user equipment (UE) configured to perform any of the methods of the first through third examples .

[0071] In a sixth example, a method, comprising, storing a first embedded subscriber identity module (eSIM) profile associated with a mobile network operator (MNO) , wherein the first eSIM profile comprises contactless application information allowing a user equipment (UE) to complete contactless transactions based on the contactless application information, storing a second eSIM profile associated with the MNO, wherein the second eSIM profile comprises only telecom information allowing the UE to perform telecommunications related operations, disabling the first eSIM profile and, when the second eSIM profile is enabled, performing a contactless transaction using the contactless application information of the first eSIM profile. [0072] In a seventh example, the method of the sixth example, further comprising deleting the first eSIM profile, in response to deletion of the first eSIM profile, presenting a user interface (UI) to a user of the UE to query whether the eSIM 2 profile is to be upgraded to include the contactless application information of the first eSIM profile.

[0073] In an eighth example, the method of the seventh example, further comprising, in response to the user indicating the second eSIM profile is to be upgraded, generating, for transmission to a network, a request to upgrade the second eSIM profile to include the contactless application information of the first eSIM profile, processing, based on signaling received from the network component, an upgraded second eSIM profile including the contactless application information of the first eSIM profile.

[0074] In a ninth example, the method of the eighth example, wherein the upgraded second eSIM profile comprises a different Integrated Circuit Card ID (ICCID) than the second eSIM profile.

[0075] In a tenth example, the method of the sixth example, further comprising deleting the first eSIM profile, wherein the contactless application information of the first eSIM profile is retained when the first eSIM profile is deleted such that the second eSIM profile continues to have access to the contactless application information of the first eSIM profile.

[0076] In an eleventh example, the method of the sixth example, wherein the UE is operating in a dual SIM dual standby (DSDS) mode. [0077] In a twelfth example, the method of the sixth example, wherein the contactless application information is globalized by associating the contactless application information with a global security domain (G-SD) and a global controlling authority security domain (G-CASD) , wherein the globalized contactless application information allows the first eSIM profile and the second eSIM profile to access the contactless application information .

[0078] In a thirteenth example, the method of the twelfth example, wherein the G-SD, the G-CASD, and the globalized contactless application information operate in a shared domain associated with a user.

[0079] In a fourteenth example, the method of the twelfth example, further comprising deleting the first eSIM profile and the second eSIM profile such that the UE no longer has any stored eSIM profiles associated with the MNO and deleting the globalized contactless application information in response to the UE no longer having any stored eSIM profiles associated with the MNO.

[0080] In a fifteenth example, the method of the sixth example, wherein the contactless application information comprises information related to a contactless service, wherein the contactless service comprises a banking service, a transit service, a payment service, an identification service, a lock service, or a key service. [0081] In a sixteenth example, a processor configured to perform any of the methods of the sixth through fifteenth examples .

[0082] In a seventeenth example, a user equipment (UE) configured to perform any of the methods of the sixth through fifteenth examples.

[0083] In an eighteenth example, a method, comprising processing, based on signals received from a user equipment (UE) , a UE state comprising information related to one or more embedded subscriber identity modules (eSIM) profiles installed on the UE, selecting an eSIM profile to assign to the UE based on the UE state and preparing, for transmission to the UE, the eSIM profile.

[0084] In a nineteenth example, the method of the eighteenth example, wherein, when the information indicates the UE does not currently have any eSIM profiles associated with a mobile network operator (MNO) , the eSIM profile comprises telecom information and contactless application information, wherein the telecom information allows the UE to perform telecommunications related operations and the contactless application information allows the UE to complete contactless transactions.

[0085] In a twentieth example, the method of the eighteenth example, wherein, when the information indicates the UE currently has one or more eSIM profiles associated with the MNO, the eSIM profile comprises only telecom information allowing the UE to perform telecommunications related operations. [ 0086] In a twenty first example , a processor configured to perform any of the methods of the eighteenth through twentieth examples .

[ 0087 ] In a twenty second example , a network component configured to perform any of the methods of the eighteenth through twentieth examples .

[ 0088 ] In a twenty third example , the network component of the twenty second example , wherein the network component is a subscription manager data preparation+ ( SM-DP+ ) server .

[ 0089] Those skilled in the art will understand that the above-described example embodiments may be implemented in any suitable software or hardware configuration or combination thereof . An example hardware platform for implementing the example embodiments may include , for example, an Intel x86 based platform with compatible operating system, a Windows OS , a Mac platform and MAC OS , a mobile device having an operating system such as iOS , Android, etc . The example embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that , when compiled, may be executed on a processor or microprocessor .

[ 0090 ] Although this application described various embodiments each having different features in various combinations , those skilled in the art will understand that any of the features of one embodiment may be combined with the features of the other embodiments in any manner not speci fically disclaimed or which is not functionally or logically inconsistent with the operation of the device or the stated functions of the disclosed embodiments .

[ 0091 ] It is well understood that the use of personally identi fiable information should follow privacy policies and practices that are generally recogni zed as meeting or exceeding industry or governmental requirements for maintaining the privacy of users . In particular, personally identifiable information data should be managed and handled so as to minimi ze risks of unintentional or unauthori zed access or use , and the nature of authori zed use should be clearly indicated to users .

[ 0092 ] It will be apparent to those skilled in the art that various modi fications may be made in the present disclosure , without departing from the spirit or the scope of the disclosure . Thus , it is intended that the present disclosure cover modifications and variations of this disclosure provided they come within the scope of the appended claims and their equivalent .

Claims

What is claimed :

1 . An apparatus comprising processing circuitry configured to : generate , for transmission to a network component associated with a mobile network operator (MNO) , a user eguipment (UE ) state comprising information related to one or more embedded subscriber identity module ( eSIM) profiles , wherein the information comprises whether a UE currently has one or more eSIM profiles associated with the MNO; and process , based on signals received from the network component , an eSIM profile .

2 . The apparatus of claim 1 , wherein the information comprises the UE does not currently have any eS IM profiles associated with the MNO and the eS IM profile comprises telecom information and contactless application information, wherein the telecom information allows the UE to perform telecommunications related operations and the contactless application information allows the UE to complete contactless transactions .

3 . The apparatus of claim 1 , wherein the information comprises the UE currently has one or more eS IM profiles associated with the MNO and the eS IM profile comprises only telecom information allowing the UE to perform telecommunications related operations .

4 . An apparatus comprising processing circuitry configured to : store a first embedded subscriber identity module ( eS IM) profile associated with a mobile network operator (MNO) , wherein the first eS IM profile comprises contactless application information allowing a user eguipment (UE ) to complete contactless transactions based on the contactless application information; store a second eSIM profile associated with the MNO, wherein the second eSIM profile comprises only telecom information allowing the UE to perform telecommunications related operations ; disable the first eS IM profile ; and when the second eS IM profile is enabled, perform a contactless transaction using the contactless application information of the first eSIM profile .

5 . The apparatus of claim 4 , wherein the processing circuitry is further configured to : delete the first eS IM profile ; in response to deletion of the first eSIM profile , present a user interface (UI ) to a user of the UE to query whether the eS IM 2 profile is to be upgraded to include the contactless application information of the first eSIM profile .

6 . The apparatus of claim 5 , wherein the processing circuitry is further configured to : in response to the user indicating the second eS IM profile is to be upgraded, generate, for transmission to a network, a request to upgrade the second eSIM profile to include the contactless application information of the first eS IM profile ; and process , based on signaling received from the network component , an upgraded second eSIM profile including the contactless application information of the first eS IM profile .

7. The apparatus of claim 6, wherein the upgraded second eSIM profile comprises a different Integrated Circuit Card ID (ICCID) than the second eSIM profile.

8. The apparatus of claim 4, wherein the processing circuitry is further configured to: delete the first eSIM profile, wherein the contactless application information of the first eSIM profile is retained when the first eSIM profile is deleted such that the second eSIM profile continues to have access to the contactless application information of the first eSIM profile.

9. The apparatus of claim 4, wherein the UE is operating in a dual SIM dual standby (DSDS) mode.

10. The apparatus of claim 4, wherein the contactless application information is globalized by associating the contactless application information with a global security domain (G-SD) and a global controlling authority security domain (G-CASD) , wherein the globalized contactless application information allows the first eSIM profile and the second eSIM profile to access the contactless application information.

11. The apparatus of claim 10, wherein the G-SD, the G-CASD, and the globalized contactless application information operate in a shared domain associated with a user.

12. The apparatus of claim 10, wherein the processing circuitry is further configured to: delete the first eSIM profile and the second eSIM profile such that the UE no longer has any stored eSIM profiles associated with the MNO; and delete the globalized contactless application information in response to the UE no longer having any stored eSIM profiles associated with the MNO.

13. The apparatus of claim 4, wherein the contactless application information comprises information related to a contactless service, wherein the contactless service comprises a banking service, a transit service, a payment service, an identification service, a lock service, or a key service.

14. An apparatus comprising processing circuitry configured to: process, based on signals received from a user equipment

(UE) , a UE state comprising information related to one or more embedded subscriber identity modules (eSIM) profiles installed on the UE ; select an eSIM profile to assign to the UE based on the UE state; and prepare, for transmission to the UE, the eSIM profile.

15. The apparatus of claim 14, wherein, when the information indicates the UE does not currently have any eSIM profiles associated with a mobile network operator (MNO) , the eSIM profile comprises telecom information and contactless application information, wherein the telecom information allows the UE to perform telecommunications related operations and the contactless application information allows the UE to complete contactless transactions.

16. The apparatus of claim 14, wherein, when the information indicates the UE currently has one or more eSIM profiles associated with a mobile network operator (MNO) , the eSIM profile comprises only telecom information allowing the UE to perform telecommunications related operations.

17. The apparatus of claim 14, wherein the apparatus comprises a subscription manager data preparation+ (SM-DP+) server.