User equipment comprising an embedded universal integrated circuit card and method of controlling same

Abstract

Describe a UE and a UE peripheral device. The UE is capable of: receiving an alert (AT) command from a UE peripheral device via a Local Portfolio Assistant (LPA) and a Local Portfolio Management Interface; determining that the AT command is directed to an Embedded Universal Integrated Circuit Card (eUICC) of the UE, the eUICC being configured to support a plurality of eSIM profiles; providing a request to the eUICC according to the AT command; obtaining an indication of a status of the request from the eUICC responding to the request; and providing an AT command response to the UE peripheral device via the Local Portfolio Management Interface, the AT command response being at least partially based on the indication of the status.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems, including systems, devices, and methods for profile activation and selection triggering for embedded universal integrated circuit cards. Prior Art

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between network devices (e.g., base stations, radio heads, etc.) and wireless communication devices. Wireless communication system standards and protocols include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for wireless local area networks (WLANs), commonly referred to by industry groups as Wi-Fi®.

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols may utilize various radio access networks (RANs) for communications between RAN network devices (sometimes also commonly referred to as RAN nodes, network nodes, or simply nodes) and wireless communication devices, known as UEs. 3GPP RANs may include, for example, the Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next-Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) to facilitate communications between network devices and UEs. For example, GERAN implements GSM and / or EDGE RATs, UTRAN implements the Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT (sometimes referred to herein as LTE), and NG-RAN implements the NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). In some deployments, E-UTRAN may also implement the NR RAT. In some deployments, NG-RAN may also implement the LTE RAT.

[0005] A network device used by a RAN may correspond to the RAN. An example of an E-UTRAN network device is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (often also referred to as an evolved Node B, enhanced Node B, eNode B, or eNB). An example of an NG-RAN network device is a next-generation Node B (sometimes also referred to as a gNode B or gNB).

[0006] The RAN provides communication services to external entities through its connection to the core network (CN). For example, E-UTRAN can utilize the Evolved Packet Core (EPC), while NG-RAN can utilize the 5G Core Network (5GC). Summary of the Invention

[0007] none Simple diagram description

[0008] To facilitate identification of the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the figure number in which the element is first introduced. [ FIG. 1 ] shows an example wireless communication system according to embodiments described herein. [ FIG. 2 ] illustrates an example signal flow according to one or more aspects described herein. [ FIG. 3 ] illustrates an example signal flow according to one or more aspects described herein. [ FIG. 4 ] illustrates an example signal flow according to one or more aspects described herein. [ FIG. 5 ] illustrates an example signal flow according to one or more aspects described herein. [ FIG. 6 ] illustrates an example signal flow according to one or more aspects described herein. [ FIG. 7 ] illustrates an example signal flow according to one or more aspects described herein. [ FIG. 8 ] illustrates an example signal flow according to one or more aspects described herein. [ FIG. 9 ] illustrates an example signal flow according to one or more aspects described herein. [ FIG. 10 ] illustrates an example signal flow according to one or more aspects described herein. [ FIG. 11 ] illustrates an example method for wireless communication by a UE according to one or more aspects described herein. [ FIG. 12 ] illustrates an example method for wireless communication via UE peripheral devices according to one or more aspects described herein. [Figure 13] illustrates an example architecture of a wireless communication system according to the embodiments described herein. [ FIG. 14 ] illustrates an example system for performing communication between a wireless device and UE peripheral devices according to embodiments described herein. Implementation Method

[0009] Various embodiments are described with respect to user equipment (UE). However, reference to UE is provided for illustrative purposes only. Example embodiments may be used with any electronic component capable of establishing a connection to a network and configured with hardware, software, and / or firmware to exchange information and data with the network. Therefore, as described herein, UE is intended to represent any suitable electronic device.

[0010] UEs or other mobile devices may use a subscriber identity module (SIM) card to store information related to the UE's user. A SIM card is typically a small, portable memory chip that stores user-related information. For example, a SIM card typically contains a 17-digit number that specifies the country of origin, the carrier (e.g., mobile network operator (MNO)), and the user's ID. Unlike physical cards that need to be replaced or installed for different deployments, eSIMs (embedded SIMs) are non-removable cards that can be embedded directly into UEs (such as smartphones or IoT (Internet of Things) devices). As used herein, the term eSIM generally refers to remote SIM activation according to the Global System for Mobile Communications Association (GSMA). eSIMs are designed, in part, to replace traditional physical SIM cards. One advantage of eSIM technology is its flexibility, as it allows users to remotely activate and manage their mobile subscriptions without having to replace a physical SIM card. This capability can be particularly beneficial for devices with limited physical space, such as smartwatches or connected IoT devices.

[0011] In some cases, an embedded universal integrated circuit card (eUICC) may be used. An eUICC is an embedded component that combines the functionality of a traditional SIM card with an additional layer of programmability for managing multiple mobile subscriptions. An eUICC can be removable or non-removable and can manage profiles remotely and / or locally in a secure manner. An eUICC can contain multiple "eSIM profiles," which are also referred to herein as "profiles." An eUICC can make it easier and more convenient for customers and device manufacturers to activate a SIM card with a new carrier profile, for example, over the air.

[0012] Modern UEs typically have multiple eSIM profiles activated and enabled by default. UE users can switch between several eSIM profiles. While defined methods exist for provisioning, activating, and switching eSIM profiles, the UE may lack a defined interface between the user and the baseband for performing this provisioning, activation, and switching of eSIM profiles. In many cases, the lack of such an interface can result in control or testing being blocked or otherwise unsupported, such as during compliance or lab testing when support from access points (APs) or other network devices is unavailable or unavailable, or when configuring lightweight IoT devices with limited user interfaces (UIs).

[0013] Attention (AT) commands are communication commands used to control and configure mobile devices, including UEs and their associated modems and modules. AT commands are transmitted to the UE as a series of characters prefixed with "AT." AT commands can be used to initiate various operations, such as establishing a connection on the UE, querying device information, or configuring parameters. Therefore, AT commands facilitate interaction between external applications or devices and the UE, facilitating the management and customization of communication settings. For example, for eUICC devices, how to enable, disable, and / or delete profiles is left to the UE implementation. Having a standardized method is helpful, for example, for testing non-removable UICC (nrUICC) devices (e.g., according to 3GPP CT6 and 3GPP RAN5 test specifications).

[0014] Therefore, this document describes one or more AT commands that facilitate aspects of eSIM profile activation and selection triggering. In some instances, such AT commands may be used to test at least an eSIM device with an eSIM profile. AT commands for an eUICC include AT commands for: downloading and installing a profile (e.g., via a boot code process); activating or deactivating an installed profile; deleting a profile; adding and / or updating a profile nickname; querying profile metadata; resetting the eUICC's memory; editing the default subscription manager data preparation platform (SM-DP+) address; listing, sending, and / or deleting pending notifications; or obtaining the eUICC identifier (EID). One or more of these AT commands may be incorporated into or provide a basis for developing test specifications for eUICCs (including nrUICC devices), such as those associated with 3GPP TS 31.117 and / or 3GPP TS 31.127. One or more of these AT commands may be incorporated into or provide the basis for developing test specifications for IoT devices (e.g., IoT devices that do not have a UI or standard interface for testing), such as those associated with the GSMA SGP.26 test specification. One or more of these AT commands may be incorporated into or provide the basis for one or more of 3GPP Global Certification Forum (GCF) or Personal Communications Services (PCS) Type Certification Review Board (PTCRB) testing, operator testing, or vendor and third-party lab testing, where test execution is automated via AT commands.

[0015] FIG1 illustrates an example wireless communication system 100 according to one or more aspects described herein. As further described herein, in one or more embodiments, the wireless communication system 100 supports one or more aspects of profile activation and selection triggering of an eUICC.

[0016] Wireless communication system 100 includes a UE 102 and a UE peripheral device 108. In one or more embodiments, UE 102 has not yet established a connection 120 with a network device 104, for example, because UE 102 is being tested prior to deployment, use, or configuration in a network including network device 104. In one or more embodiments, UE 102 is associated with a universal SIM (USIM), such as an eUICC 116. The combination of UE 102 and eUICC 116 is a mobile station (MS) 112. As used herein, components of UE 112 are also components of MS 112.

[0017] In one or more embodiments, MS 112 includes profile manager circuitry, such as a local profile assistant (LPA) 114 coupled to eUICC 116. In some embodiments, LPA 114 is part of eUICC 116 (e.g., LPA 114-b). In some embodiments, LPA 114 is a separate component from eUICC 116 (e.g., LPA 114-a). In either configuration, LPA 114 is coupled to eUICC 116 for communication.

[0018] In one or more embodiments, the eUICC 116 is configured to support a plurality of eSIM profiles, such as a first eSIM profile 122, a second eSIM profile 124, and a third eSIM profile 126. Although three eSIM profiles are shown, any number of eSIM profiles may be supported, configured, or used in the eUICC 116.

[0019] In one or more embodiments, UE peripheral device 108 may be, for example, a UE test device or a UE extension device that enhances the UI. UE peripheral device 108 is coupled to MS 112 via a local management interface 118. UE peripheral device 108 connects to UE 102 using a universal port. Therefore, UE peripheral device 108 interacts with eUICC 116 via a logical interface. In one or more embodiments, local management interface 118 includes circuitry from UE 102, MS 112, or both that supports communication with UE peripheral device 108, and circuitry from UE peripheral device 108 that supports communication with UE 102, MS 112, LPA, or a combination thereof.

[0020] In one or more embodiments, the eUICC 116 may allow a user (e.g., a user of UE 102) to select between multiple MNO profiles. In some embodiments, the eUICC 116 may be, for example, a discrete chip or integrated circuit component mounted on a printed circuit board of the UE 102. In other embodiments, the eUICC 116 may be incorporated into an integrated circuit chip, module, or assembly with other components or circuits of the UE 102 (such as a modem or baseband).

[0021] In one or more embodiments, the LPA 114 is a functional element that provides services for eUICC operations. In some embodiments, the LPA 114 is implemented as part of a standalone or discrete chip or integrated circuit device, for example, mounted on a printed circuit board of the UE 102. In some embodiments, the LPA 114 is implemented as part of the application processor, modem, baseband, or other components of the MS 112. In some embodiments, the LPA 114 is part of the eUICC 116, for example, circuitry that is part of the same chip or integrated circuit as the eUICC 116.

[0022] The LPA 114 is typically a set of functions within the UE 102 that provides the ability to download encrypted profiles to the eUICC 116. The LPA 114 may also present a local management interface 118 (which may also be referred to as the local management interface 118) to the end user (e.g., the UE peripheral device 108), allowing the end user to manage the status of profiles (e.g., one or more of the first eSIM profile 122, the second eSIM profile 124, and the third eSIM profile 126) on the eUICC 116. As described herein, one or more of the functions of the LPA 114 may be implemented within the eUICC 116.

[0023] LPA 114 includes one or more sets of circuitry responsible for different services or otherwise performing different tasks of LPA 114. Therefore, LPA 114 has one or more sets of functionality responsible for different services or tasks. For example, LPA 114 may include one or more of the following: a local discovery service (LDS) that interfaces with, for example, a subscription manager discovery service (SM-DS) external to UE 102; a local profile download (LPD) that interfaces with, for example, a subscription manager data provisioning (SM-DP+) external to UE 102; and a local user interface (LUI) that interfaces with one or more of UE 102's device applications, a high-resolution icon (HRI) server, or an end user (e.g., UE peripheral device 108).

[0024] In one or more embodiments, the SM-DS facilitates the abstraction of eUICC functionality from the operational connection. The SM-DS can allow the SM-DP+ to post alerts to a security bulletin board and for devices to retrieve. The SM-DS can be used to notify the LPA 114 when profile (e.g., eSIM profile) data is available for download to the eUICC 116. The LPA 114 can poll the SM-DS for notifications, for example, when requested by the UE 102.

[0025] In one or more embodiments, the SM-DP+ is responsible for the creation, downloading, remote management (e.g., activation, deactivation, update, deletion), and protection of operator credentials (e.g., configuration files).

[0026] In one or more embodiments, the UE peripheral device 108 may transmit or otherwise provide AT commands to the UE 102, and the UE 102 may receive or otherwise obtain the AT commands from the UE peripheral device 108. In response to such AT commands, the UE 102 may transmit or otherwise provide results (e.g., AT command results) to the UE peripheral device 108, and the UE peripheral device 108 may receive or otherwise obtain the results from the UE 102. In one or more embodiments, as further described herein, such AT commands (and results associated with such AT commands) include one or more AT commands to: download and install a profile (e.g., via a boot code process); enable or disable an installed profile; delete a profile; add and / or update a nickname for a profile; query profile metadata; reset the eUICC's memory; edit the default subscription manager data preparation platform (SM-DP+) address; list, send, and / or delete pending notifications; or obtain an EID.

[0027] In the context of 3GPP technology and mobile communication devices (e.g., UEs, including their modems and cellular modules), AT commands are used to control and configure the devices. AT commands can be issued via a communication interface, such as a serial interface (e.g., Universal Asynchronous Receiver-Transmitter (UART) or Universal Serial Bus (USB)). In some embodiments, AT commands are ASCII strings and begin with the prefix "AT." In some embodiments, AT commands are sent from UE peripheral device 108 to UE 102 using a selected interface (e.g., local management interface 118). AT commands can be programmatically sent via software running on UE peripheral device 108, which can be a computer or microcontroller including a processor and memory that can be configured or programmed for UE testing.

[0028] In some embodiments, AT commands have a specific syntax, such as an "AT" prefix followed by a specific command and optional parameters, as discussed further below. A response to an AT command (e.g., an AT command response or AT command result) may include information or confirmation. This response may include the results of the command or information regarding the current state of the UE (e.g., a modem or eUICC 116). In some embodiments, such a response takes the form of a programmatically interpretable text string. In some cases, an AT command may return an error, for example, if a problem occurs with the AT command or if the UE (e.g., eUICC 116) is unable to execute the AT command. In some embodiments, an error response begins with "ERROR." As further described herein, AT commands for profile activation and selection triggering of the eUICC 116 may be defined as a separate set of AT commands that are shared across compliant devices (such as UE 102) to ensure interoperability.

[0029] In one or more embodiments, the AT command and AT command response for eUICC configuration file download + CEUICCPD may have the syntax shown in Table 1 below.

[0030] FIG2 illustrates an example signal flow 200 according to one or more aspects described herein. As further described herein, in one or more embodiments, signal flow 200 supports one or more aspects of profile activation and selection triggering for an eUICC. Signal flow 200 generally relates to a successful profile download.

[0031] FIG3 illustrates an example signal flow 300 according to one or more aspects described herein. As further described herein, in one or more embodiments, signal flow 300 supports one or more aspects of profile activation and selection triggering for an eUICC. Signal flow 300 generally relates to an unsuccessful profile download, for example, when one or more errors are returned by the eUICC 116.

[0032] Signal flow 200 and signal flow 300 each illustrate communications between UE peripheral device 108, mobile station 112, LPA 114, and eUICC 116. In one or more embodiments, LPA 114 and eUICC 116 are part of mobile station 112. Mobile station 112 may be referred to as UE 102 or an instance of a UE. In some embodiments, mobile station 112 may include at least a portion of a local management interface, such as circuitry associated with local management interface 118. Additionally or alternatively, in some embodiments, UE peripheral device 108 may include at least a portion of the local management interface. [Order] [Possible Response(s)] +CEUICCPD= <mode>,<matching_ID> / <confirmation_code>[,<smdp_address>] +CME ERROR: <err> +CEUICCPD=? [surface] [1] [:] [+CEUICCPD] [Parameter command syntax]

[0033] Table 1 illustrates the syntax of the +CEUICCPD command (e.g., for eSIM profile download) including parameters associated with signal flows 200 and 300. The configuration command invokes the LPA 114 (residing in the eUICC 116 and / or MS 112) to trigger a request to download and install the profile in the eUICC via a boot code procedure. If the default SM-DP+ address already exists in the eUICC 116 and / or MS 112, the same SM-DP+ address can be used and the user can skip providing it.

[0034] The command is returned with a response depending on whether the request was successfully sent to the LPA. Once the boot process is complete, the actual result of the download and installation is determined by the unsolicited result code: +CEUICCPDU: <result> [,[ <iccid>][,<cause_source>[, <cause>]]] show.

[0035] Optionally, if the activation code token indicates that a confirmation code is also required, the user is prompted via the +CEUICCPDU to enter the confirmation code provided to them by the issuing MSP. The set command can be used to respond with a confirmation code.

[0036] Defined values:

[0037] <mode>:Integer Type: 0 Send start code 1 Send confirmation code

[0038] <confirmation_code> : String type, indicating the confirmation code that will be used to download and install the configuration file from the SM-DP+. This is obtained from the Mobile Service Provider (MSP) when subscribing through external means. <mode>= 1, required<confirmation_code> .

[0039] <matching_ID> : String type, indicating the matching ID that will be used to download and install the configuration file from SM-DP+. <mode>= 0, required<matching_ID> .

[0040] <smdp_address> : String type, indicating the address of the SM-DP+ (Subscription Manager Data Preparation +). The LPA uses it to identify the SM-DP+ where the configuration file is stored and available for download.

[0041] <result>: Integer type; indicates the final result of downloading and installing the configuration file. 0 Downloaded and installed successfully. 1 Failed to download and install. 2 Confirmation code required. 3 Download successful but PIN locked. Refer to +CPIN to unlock.

[0042] <iccid>: string type; specifies a unique number to identify a configuration profile in the eUICC.

[0043] <cause_source> : Integer type, indicating the function that returns the error reason when downloading and installing the configuration file. These functions are associated with specific eUICC interfaces, for example, ES9+ is used to provide secure transport for delivering configuration files between SM-DP+ and LPA, and LPA uses ES10b to transfer the configuration files to the eUICC. <result>=1,<cause_source> Will exist, refer to GSMA SGP.22. 0 Unknown 1 General error in ES10b interface. 2. Function: Perform RSP server authentication (AuthenticateServer, ES10b) via eUICC 3. Function 3 initiates download of the binding profile package (PrepareDownload, ES10b) after successful authentication with the SM-DP+. 4. Function: Transfer the binding profile package to the eUICC (LoadBoundProfilePackage, ES10b) 5. Function Request SM-DP+ Authentication (InitiateAuthentication, ES9+) Function 6 is called by the LPA to request authentication of the eUICC by the SM-DP+ (AuthenticateClient, ES9+) 7 Function is called to request the delivery and binding profile package to the eUICC (GetBoundProfilePackage, ES9+) 8 General Errors in ES9+ Interfaces

[0044] <cause>: Integer type, indicating the error reason due to which the process of downloading and installing the configuration file has been terminated. <result>=1, <cause>Will exist, refer to GSMA SGP.22: 0 Undefined Error 1 Invalid Credentials 2 Invalid signature 3 Curves not supported 4 No session context 5 Invalid OID 6 eUICC Challenges Mismatch 7 CI PK unknown 8 Invalid transaction id 9 Incorrect input value 10 Unsupported CRT value 11 Unsupported remote operation type 12 Unsupported profile types 13 SCP03t Structural Error 14 SCP03t Security Error 15 Installation failed because the iccid already exists on the eUICC 16 Installation failed due to insufficient memory for configuration files 17 Installation failed due to interruption 18 Installation failed due to PE processing error 19 Installation failed due to data mismatch. 20 Test profile installation failed due to invalid NAA key 21 PPR not allowed 22 Incorrect value in command data 23 References not found 24 The conditions for use are not met 25 Invalid SM-DP+ address 26 eUICC specification version is not supported by SM-DP+. 27 Security configuration not supported 28 CI PK Id is not supported 29 EUM certificate is invalid 30 EUM certificate expires 31 The eUICC certificate is invalid. 32 eUICC certificate expires 33 eUICC signature is invalid 34 Insufficient eUICC memory 35 CI PK unknown 36 Unauthorized profile 37 Transaction ID unknown 38 matchingId rejected 39 EID mismatch 40 Exceeded the maximum number of retries for downloading orders 41 Download order expiration time 42 BPP rebinding rejected 43 Confirmation code lost 44 Confirmation code rejected 45 Exceeded the maximum number of confirmation code retries

[0045] Referring to signal flow 200, at 202, an AT command indicating a start code is sent to UE 102. In one or more embodiments, the AT command is AT+CEUICCPD=0, "matching_ID", "smdp_address".

[0046] At 204, a message is sent from mobile station 112 to LPA 114 instructing LPA 114 to perform a boot code procedure based on one or more boot code parameters. In some embodiments, 204 includes UE operation to receive an AT command from UE peripheral device 108 via a local management interface. In some embodiments, the UE may determine that the AT command includes a request to perform a boot code procedure to download and install an eSIM profile in eUICC 116, wherein the request provided to eUICC 116 includes an instruction to initiate the boot code download procedure. In one or more embodiments, the message at 204 may identify one or more parameters associated with the boot code, as further described herein.

[0047] At 206 , the MS 112 may send an acknowledgement (“OK”) to the UE peripheral 108 .

[0048] For example, if a confirmation code is required, optional messaging 240 may be performed. At 208, LPA 114 sends a confirmation code request to MS 112, which sends an unsolicited response 210 (e.g., +CEUICCPD:2) indicating the confirmation code request to UE peripheral 108. UE peripheral 108 returns an AT command indicating a confirmation code response 212 (e.g., AT+CEUICCPD=1 "confirmation code"), and MS 112 sends a confirmation code response 214 to LPA 114.

[0049] At 216, a request is provided to the eUICC 116 based on the AT command received at 202. The LPA 114 sends a message to the eUICC 116 indicating the start of the activation code download procedure. At 218, a secure download of the activation code is performed from the eUICC 116 to the MS 112. At 220, the LPA 114 performs profile verification, and in one or more embodiments, the verification can be determined to be successful.

[0050] For example, if the profile requests or requires a PIN, optional messaging 250 may be performed. At 222, the LPA 114 sends an indication that a PIN is required to the MS 112, which sends an AT command response 224 (e.g., +CEUICCPD:3) indicating a request for a PIN to the UE peripheral 108. At 226, the UE peripheral 108 returns an AT command indicating a PIN (e.g., AT+CPIN= <pin>), and the MS 112 sends the PIN code to the LPA 114 at 228, and the LPA 114 sends the PIN code (e.g., for the eSIM profile) to the eUICC 116 at 230. At 232, a confirmation may be sent from the MS 112 to the UE peripheral device 108.

[0051] At 234, the profile is installed and may be successfully installed (e.g., optionally without or with a PIN). In some embodiments, 234 is an example of obtaining an indication of the status of the request from the eUICC 116 responding to the request.

[0052] At 236, an AT command response indicating the profile identifier (ID) of the installed profile is sent to the UE peripheral device 108. In some embodiments, 236 is an example of an AT command response provided by the UE peripheral device via the local management interface, the AT command response being based at least in part on the indication of the status.

[0053] Referring to signal flow 300, 302 may be an example of 202, 304 may be an example of 204, and 306 may be an example of 206. However, the eUICC 116 may return one or more errors in response to 304, so that when <result>=1,<cause_source> Response to AT command exists (for example, <result>For example, if a general error of the ES10B interface occurs at 308, this results in an AT command response at 310 (e.g., <result>=1, and +CEUICCPDU: 1,,1,22). In another example, if the function performs authentication with a remote SIM provisioning (RSP) server via the eUICC at 312, this results in an AT command response at 314 (e.g., <result>=2, and +CEUICCPDU: 1,,2,1). In another example, if the function initiates BPP download at 316 after successful authentication of SM-DP+, this results in an AT command response at 318 (e.g., <result>=3, and +CEUICCPDU: 1,,3,2). In another example, if the function transfers the bound profile package (BPP) to the eUICC at 320, this results in an AT command response at 322 (e.g., <result>=4, and +CEUICCPDU: 1,,4,9). In another example, if the function requests SM-DP+ authentication at 324, this results in an AT command response at 326 (e.g., <result>=5, and +CEUICCPDU: 1,,5,25). In another example, if at 328, the function is called by the LPA to request authentication of the eUICC by the SM-DP+, this results in an AT command response at 330 (e.g., <result>=6, and +CEUICCPDU: 1,,6,29). In another example, if the function is called at 332 to request the delivery and binding of the profile packet, this results in an AT command response at 330 (e.g., <result>=7, and +CEUICCPDU: 1,,7,43). In another example, if a general error of the ES9+ interface occurs at 336, this results in an AT command response at 338 (e.g., <result>= 8, and +CEUICCPDU: 1,,8,0). In some embodiments, although multiple return errors are shown in signal flow 300, in the case of a return error, in some instances, a single one of 308, 312, 316, 320, 324, 328, 332, or 336 may occur, resulting in one of 310, 314, 318, 322, 326, 330, 334, or 338, respectively.

[0054] FIG4 illustrates an example signal flow 400 according to one or more aspects described herein. As further described herein, in one or more embodiments, signal flow 400 supports one or more aspects of profile activation and selection triggering for an eUICC. Signal flow 400 generally relates to activating a profile.

[0055] FIG5 illustrates an example signal flow 500 according to one or more aspects described herein. As further described herein, in one or more embodiments, signal flow 500 supports one or more aspects of profile activation and selection triggering for an eUICC. Signal flow 500 generally relates to deactivating a profile.

[0056] FIG6 illustrates an example signal flow 600 according to one or more aspects described herein. As further described herein, in one or more embodiments, signal flow 600 supports one or more aspects of profile activation and selection triggering for an eUICC. Signal flow 600 generally relates to deleting a profile.

[0057] Signal flow 400, signal flow 500, and signal flow 600 each illustrate communications between UE peripheral device 108, mobile station 112, LPA 114, and eUICC 116. In one or more embodiments, LPA 114 and eUICC 116 are part of mobile station 112. Mobile station 112 may be referred to as UE 102 or an instance of a UE. In some embodiments, mobile station 112 may include at least a portion of a local management interface, such as circuitry associated with local management interface 118. Additionally or alternatively, in some embodiments, UE peripheral device 108 may include at least a portion of a local management interface. In one or more embodiments, communications with eUICC 116 may more specifically be communications with issuer security domain root (ISD-R) 432, which may be part or a component of eUICC 116. [Order] [Possible Response(s)] +CEUICCPM= <operation> , <iccid> +CME ERROR: <err> +CEUICCPM? [+CEUICCPM: <iccid1> , <state> [, <iccid2> , <state> […]]] +CEUICCPM=? +CEUICCPM:(Supported <iccid>Range), supported ( <operation>) list [surface] [2] [:] [+CEUICCPM] [Parameter command syntax]

[0058] Table 2 illustrates the syntax of the +CEUICCPM command (e.g., for eSIM profile management) associated with signal flow 400, signal flow 500, and signal flow 600. The Set command activates, deactivates, or deletes a profile in the eUICC. In some embodiments, the Set command applies to eUICC 116-capable devices that have profile(s) installed in the eUICC 116. For devices supporting two simultaneous device cellular connections, two profiles can be activated simultaneously. In some embodiments, to delete a profile, the profile must be deactivated.

[0059] The command is returned in response depending on whether the request was successfully sent to the LPA 114. Once the procedure is completed, the actual result of the operation will be indicated by the unsolicited result code +CEUICCPMU: <result> [,[ <iccid> ],[ <state> ][, <cause>]]]show.

[0060] If verification of the user's intent regarding the action being performed is required, prompt the user to respond. See command +CEUICCUIV.

[0061] The read command returns the current settings of each installed configuration file.

[0062] Test command return <iccid>A list of installed configuration files and the ones that should be triggered <operation>.

[0063] Defined values:

[0064] <operation>: Integer type, indicating the operation to be completed for the profile management of the profile installed in the eUICC. 0 Disable profile 1 Enable the profile 2 Delete the configuration file

[0065] <iccid>: string type; specifies a unique number to identify a configuration profile in the eUICC.

[0066] <state>: Integer type, indicating the current status of the configuration file. 0 Deactivated 1 Enabled 2 Deleted

[0067] <result>: Integer type; indicates the final result of the action triggered by the user. 0 Successfully enabled / disabled / deleted profile. 1 Failed to complete enabling / disabling / deleting profile.

[0068] <cause>: Integer type, indicating the error reason due to which the process of enabling / disabling / deleting the profile has terminated. <result>=1, <cause>Will exist, refer to GSMA SGP.22. 0 Unknown 1 ICCID or AID not found 2 The profile is not disabled 3 The profile is not active 4 Policy not allowed 5. Wrong profile reactivation 6 Busy (ongoing active session on target port)

[0069] Referring to the signal flow 400, at 402, an AT command indicating profile activation is sent to the UE 102. In one or more embodiments, the AT command is AT+CEUICCPM=1, "iccid2".

[0070] At 404, a message indicating a profile activation request is sent from the mobile station 112 to the LPA 114. At 406, the MS 112 may send an acknowledgment ("OK") to the UE peripheral 108, and the LPA 114 sends a profile activation signal to the ISD-R 432 at 408.

[0071] For example, if the first profile (e.g., iccid1) is already enabled and multiple enabled profiles are not supported, optional communication 420 may be performed. At 410, a profile policy rule conflict notification is sent to LPA 114, and ISD-R 432 deactivates the profile (e.g., profile "iccid1," which is different from the profile iccid2 requested for activation) at 412. At 414, LPA 114 sends a profile policy rule conflict notification to MS 112. At 418, an AT command response (e.g., +CEUICCPMU:0, "iccid1") indicates deactivation of the conflicting profile (e.g., "iccid1"). At 416, UE peripheral device 108 deactivates the conflicting profile (e.g., "iccid1") or identifies the conflicting profile as deactivated.

[0072] At 422, the profile is requested to be enabled in ISD-R 432. At 424, a confirmation of the profile enabling is sent to LPA 114 and, at 426, to MS 112. At 218, an AT command response (e.g., +CEUICCPMU:0, "iccid2", 1) indicates that the requested profile (e.g., "iccid2") is enabled. At 430, UE peripheral 108 enables the requested profile (e.g., "iccid2") or identifies the requested profile as enabled.

[0073] Referring to the signal flow 500, at 502, an AT command indicating profile deactivation is sent to the UE 102. In one or more embodiments, the AT command is AT+CEUICCPM=0, "iccid1".

[0074] At 504, a message indicating a profile deactivation request is sent from the mobile station 112 to the LPA 114. At 506, the LPA 114 sends a profile deactivation signal to the ISD-R 432.

[0075] For example, if profile deactivation is not permitted (e.g., for iccid1, or generally), optional communication 518 may be performed. At 508, the request may be aborted, and at 510, a profile policy rule conflict notification may be sent to LPA 114. At 512, LPA 114 sends the profile policy rule conflict notification to MS 112. At 516, an AT command response (e.g., +CEUICCPMU:1, "iccid1", 1) indicates that the profile is enabled. At 514, UE peripheral device 108 continues to enable the profile (e.g., "iccid1") or continues to identify the profile as enabled.

[0076] For example, if profile deactivation is allowed (e.g., for iccid1, or generally), optional communication 528 may be performed. At 518, the requested profile may be deactivated, and at 520, a profile deactivation confirmation may be sent to LPA 114. At 522, LPA 114 sends the profile deactivation confirmation to MS 112. At 526, an AT command response (e.g., +CEUICCPMU:0, "iccid1", 0) indicates that the profile (e.g., "iccid1") is deactivated. At 524, UE peripheral device 108 deactivates the profile (e.g., "iccid1") or identifies the profile as deactivated.

[0077] Referring to signal flow 600, at 602, an AT command instructing profile deletion is sent to UE 102. In one or more embodiments, the AT command is AT+CEUICCPM=2, "iccid1".

[0078] At 604, a message indicating a profile deletion request is sent from the mobile station 112 to the LPA 114. At 606, the MS 112 may send an acknowledgment ("OK") to the UE peripheral 108, and the LPA 114 may send a profile deletion signal to the ISD-R 432 at 608.

[0079] For example, if profile deletion is not permitted (e.g., for iccid1, or generally), optional messaging 620 may be performed. At 610, the request may be aborted, and at 612, a profile policy rule conflict notification may be sent to LPA 114. At 614, LPA 114 sends the profile policy rule conflict notification to MS 112. At 618, an AT command response (e.g., +CEUICCPMU:1, "iccid1", 1, 2) may be sent to UE peripheral 108, and UE peripheral 108 may proceed to enable the profile (e.g., "iccid1") or identify the profile as enabled, e.g., because the profile cannot be deleted because it is not in a disabled state.

[0080] For example, if profile deletion is allowed (e.g., for iccid1, or generally), optional messaging 632 may be performed. At 622, the requested profile may be deleted, and at 624, a profile deletion confirmation may be sent to LPA 114. At 626, LPA 114 sends the profile deletion confirmation to MS 112. At 630, an AT command response (e.g., +CEUICCPMU:0, "iccid1", 2) indicates the deletion of the profile (e.g., "iccid1"). At 628, UE peripheral 108 deactivates the profile (e.g., "iccid1") or identifies the profile as deactivated.

[0081] FIG7 illustrates an example signal flow 700 according to one or more aspects described herein. As further described herein, in one or more embodiments, signal flow 700 supports one or more aspects of profile activation and selection triggering for an eUICC. Signal flow 700 generally relates to updating the nickname of an eSIM profile.

[0082] FIG8 illustrates an example signal flow 800 according to one or more aspects described herein. As further described herein, in one or more embodiments, signal flow 800 supports one or more aspects of profile activation and selection triggering for an eUICC. Signal flow 800 generally relates to reading metadata from an eSIM profile.

[0083] Signal flow 700 and signal flow 800 each illustrate communications between UE peripheral device 108, mobile station 112, LPA 114, and eUICC 116. In one or more embodiments, LPA 114 and eUICC 116 are part of mobile station 112. Mobile station 112 may be referred to as UE 102 or an instance of such a UE. In some embodiments, mobile station 112 may include at least a portion of a local management interface, such as circuitry associated with local management interface 118. Additionally or alternatively, in some embodiments, UE peripheral device 108 may include at least a portion of the local management interface. [Order] [Possible Response(s)] +CEUICCPMETAI[= <operation> [, <iccid> [, <nickname>]]] [+CEUICCPMETAI: <iccid> , <state>,<profile_metadata> [ <cr> <lf>+CEUICCPMETAI: <iccid> , <state>,<profile_metadata> […]]] +CME ERROR: <err> +CEUICCPMETAI=? +CEUICCPMETAI:(Supported <operation>range) [surface] [3] [:] [+CEUICCPMETAI] [Parameter command syntax]

[0084] Table 3 illustrates the syntax of the +CEUICCPMETAI command (e.g., for eSIM profile metadata) including parameters associated with signal flows 700 and 800. The configuration command allows a user (e.g., UE peripheral device 108) to read and display profile metadata for all profiles installed in the eUICC, regardless of their status. The command also allows the user to assign nicknames to profiles, for example, for ease of use. In some embodiments, adding or changing a nickname does not affect any other information or other profile metadata associated with the profile.

[0085] The test command returns the triggered <operation>.

[0086] Defined values:

[0087] <operation>: Integer type, indicating the operation to be completed for the profile management of the profile installed in the eUICC. 0 Read all profile metadata (default) 1 Read by <iccid>The profile metadata of the identified profile. In this case, you need to provide <iccid>. 2 Add / update a profile-specific nickname in the profile metadata. In this case, you need to provide <iccid>and <nickname>

[0088] <iccid>: string type; specifies a unique number to identify a configuration profile in the eUICC.

[0089] <nickname>: string type, indicating that it needs to be <iccid>Nicknames added / updated in the identified profile.

[0090] <state>: Integer type, indicating the current status of the configuration file. 0 Deactivated 1 Enabled

[0091] <profile_metadata> : A string type indicating the configuration file's configuration file metadata information, including the information listed below. In some embodiments, the list of information displayed by this command may be implementation-specific. - MSP Name -ICCID - User nickname for the profile. - A short description of the profile as defined by the operator or MSP. - Profile Policy Rules - Type of profile operation, activation, or test profile - Manage the list of (multiple) SM-DP+ - Estimated installation dimensions of the profile (optional) - Device change configuration of profile (optional) - Additional exclusive information (optional)

[0092] Referring to signal flow 700, at 702, an AT command indicating a request to update a nickname is sent to UE 102. In one or more embodiments, the AT command is AT+CEUICCPMETAI=2, "iccid", "nickname".

[0093] At 704, the mobile station 112 sends a message indicating a request to update the nickname of the profile to the LPA 114. At 706, the LPA 114 sends an instruction to update the nickname to the eUICC 116.

[0094] At 708, a message indicating confirmation of the updated nickname is sent from the eUICC 116 to the LPA 114. At 710, the LPA 114 sends a response indicating the updated nickname of the profile to the MS 112 (e.g., a response indicating success or failure in updating the nickname). At 712, the MS 112 may send a confirmation ("OK") indicating a successful nickname update or an error to the UE peripheral device 108, as further described herein.

[0095] Referring to signal flow 800, at 802, an AT command indicates a request for metadata information (eg, metadata query) to UE 102. In one or more embodiments, the AT command is AT+CEUICCPMETAI=1, "iccid".

[0096] At 804, a message indicating a metadata query is sent from the mobile station 112 to the LPA 114. At 806, the LPA 114 sends an indication for metadata query (which may also be referred to as a request to read profile metadata) to the eUICC 116.

[0097] At 808, a message indicating the profile metadata for display is sent from the eUICC 116 to the LPA 114. At 810, the LPA 114 sends a response indicating the requested metadata to the MS 112. At 812, the MS 112 may send an AT command response indicating the requested metadata (e.g., +CEUICCPMETAI: "iccid", "state", "profile_metadata") to the UE peripheral 108, as further described herein. When multiple metadata queries have been received or indicated via the AT command at 802, one or more of 804, 806, 808, 810, and / or 812 may, for example, be repeated for each of the multiple metadata queries.

[0098] At 816, MS 112 may send an acknowledgment ("OK") to UE peripheral device 108 indicating successful provision of the requested profile metadata information, as further described herein.

[0099] FIG9 illustrates an example signal flow 900 according to one or more aspects described herein. As further described herein, in one or more embodiments, signal flow 900 supports one or more aspects of profile activation and selection triggering of an eUICC. Signal flow 900 generally relates to resetting the memory of the eUICC 116.

[0100] Signal flow 900 illustrates communications between UE peripheral device 108, mobile station 112, LPA 114, and eUICC 116. In one or more embodiments, LPA 114 and eUICC 116 are part of mobile station 112. Mobile station 112 may be referred to as UE 102 or an instance of a UE. In some embodiments, mobile station 112 may include at least a portion of a local management interface, such as circuitry associated with local management interface 118. Additionally or alternatively, in some embodiments, UE peripheral device 108 may include at least a portion of the local management interface. [Order] [Possible Response(s)] +CEUICCMEMRESET +CME ERROR: <err> +CEUICCMEMRESET=? [surface] [4] [:] [+CEUICCMEMRESET] [Parameter command syntax]

[0101] Table 4 illustrates the command syntax (e.g., for eUICC memory reset) including the +CEUICCMEMRESET parameter associated with signal flow 900. In one or more embodiments, the AT command triggers an eUICC-capable UE to request the LPA 114 to perform an eUICC memory reset, including associated profile metadata. In some embodiments, this requires user authentication, triggering a notification from the LPA 114 to the user (e.g., the UE peripheral 108) regarding the authentication, followed by a prompt for the user to respond. See command +CEUICCUIV.

[0102] The AT command is returned in response depending on whether the request was successfully sent to the LPA 114. Once the procedure is completed, the actual result of the memory reset will be indicated by the unsolicited result code +CEUICCMEMRESETU: <result> [, <cause>]show.

[0103] Defined values:

[0104] <result>: Integer type; indicates the final result of eUICC memory reset. 0 Successfully deleted the profile and associated profile metadata. 1 Failed to reset the eUICC memory.

[0105] <cause>: Integer type, indicating the error reason due to which the procedure of resetting the eUICC has been terminated. <result>=1, <cause>Will exist, refer to GSMA SGP.22. 0 Unknown 1 No content to delete 2 Busy

[0106] Referring to signal flow 900, at 902, an AT command indicating a request to perform an eUICC memory reset is sent to UE 102. In one or more embodiments, the AT command is AT+CEUICCMEMRESET.

[0107] At 904, a message indicating a request to reset the eUICC memory is sent from the mobile station 112 to the LPA 114. At 906, an acknowledgement ("OK") indicates receipt of the AT command indicating a request to perform the eUICC memory reset.

[0108] At 908 , in one or more embodiments, the LPA 114 may obtain confirmation from the UE peripheral device 108 of the consequences of performing the eUICC memory reset.

[0109] At 910, the LPA 114 sends an instruction to reset the eUICC memory to the eUICC 116. The eUICC 116 then sends a response indicating that the memory reset operation is complete (e.g., after the eUICC 116 memory reset is complete). At 914, the LPA 114 sends a response confirming the memory reset to the MS 112. At 916, the MS 112 may send an AT command response confirming the memory reset (e.g., +CEUICCPMEMRESETU:0) to the UE peripheral device 108, as further described herein.

[0110] FIG10 illustrates an example signal flow 1000 according to one or more aspects described herein. As further described herein, in one or more embodiments, signal flow 1000 supports one or more aspects of profile activation and selection triggering for an eUICC. Signal flow 1000 generally relates to editing an SM-DP+ address (e.g., a default SM-DP+ address) on an eUICC (e.g., eUICC 116) or a device (e.g., UE 102, such as a modem or baseband of UE 102).

[0111] Signal flow 1000 illustrates communications between UE peripheral device 108, mobile station 112, LPA 114, and LPA service 1016 or device 1018. In one or more embodiments, LPA 114, LPA service 1016, and device 1018 are part of mobile station 112. Mobile station 112 may be referred to as UE 102 or an instance of a UE. In some embodiments, mobile station 112 may include at least a portion of a local management interface, such as circuitry associated with local management interface 118. Additionally or alternatively, in some embodiments, UE peripheral device 108 may include at least a portion of a local management interface. [Order] [Possible Response(s)] +CEUICCUSMDPA=<smdp_address> +CME ERROR: <err> +CEUICCUSMDPA=? [surface] [5] [:] [+CEUICCUSMDPA] [Parameter command syntax]

[0112] Table 5 illustrates the syntax of the +CEUICCUSMDPA command (e.g., for updating the default SM-DP+ address) associated with signal flow 1000. In one or more embodiments, this AT command allows a user to edit the default SM-DP+ address on an eUICC (e.g., eUICC 116) or a device (e.g., UE 102, such as UE 102's modem or baseband). In some embodiments, this requires verification of the user's intent, triggering a notification from LPA 114 to the user regarding the verification, followed by a prompt for the user to respond. See command +CEUICCUIV.

[0113] The AT command is returned in response depending on whether the request is successfully sent to the LPA 114. Once the procedure is completed, the actual result of updating the SM-DP+ address will be sent via the unsolicited result code +CEUICCUSMDPAU: <result>show.

[0114] Defined value

[0115] <smdp_address> : String type, indicating the SM-DP+ address that will replace the default SM-DP+ address present in the eUICC / Device.

[0116] <result>: Integer type; indicates the final result of eUICC memory reset. 0 Successfully updated the SM-DP+ address. 1 Failed to update SM-DP+ address.

[0117] Referring to the signal flow 1000, at 1002, the UE peripheral device 108 sends an AT command indicating an address update request to the UE 102. In one or more embodiments, the AT command is AT+CEUICCUSMDPA=“smdp_address”.

[0118] At 1004, a message indicating a request to edit the SM-DP+ address is sent from the mobile station 112 to the LPA 114. At 1006, the MS 112 may send an acknowledgment ("OK") indicating successful receipt of the AT command to the UE peripheral device 108.

[0119] After 1006, one of two address updates may be performed. In some embodiments, the SM-DP+ address is stored in the eUICC 116, and the SM-DP+ address update is performed between the LPA 114 and the LPA service 1016. In some embodiments, the SM-DP+ address is stored in another component of the device 1018 (e.g., UE 102), such as in the device's modem or baseband, and the SM-DP+ address update is performed between the LPA 114 and the device 1018.

[0120] At 1012, LPA 114 sends a response providing confirmation of the edit of the SM-DP+ address to MS 112. At 1014, MS 112 may send an AT command response (e.g., +CEUICCUSMDPAU:0) confirming the edit of the SM-DP+ address to UE peripheral device 108, as further described herein.

[0121] Additional AT commands and AT command responses may request the eUICC's ID (e.g., EID), manage pending notifications generated when a profile management operation has succeeded, enable or disable notifications via unsolicited responses, or any combination thereof, as discussed further below.

[0122] The first example includes eUICC User Intent Verification (e.g., +CEUICCUIV). [Order] [Possible Response(s)] +CEUICCUIV= <action>[,<user_response>[, <iccid>]] +CME ERROR: <err> +CEUICCUIV=? +CEUICCUIV:(Supported <action>range) [surface] [6] [:] [+CEUICCUIV] [Parameter command syntax]

[0123] Set the command to allow unsolicited response +CEUICCUIV: <operation>,<op_state>[, <iccid>] Enables or disables notification to the user (e.g., UE peripheral device 108) to verify the intention of the triggered action. This command also allows responding to the verification prompt.

[0124] The test command returns the triggered <action>.

[0125] Defined values:

[0126] <action>: integer type. 0 Disable unsolicited responses +CEUICCUIV: <operation>,<op_state>[, <iccid>] 1 Enable unsolicited responses + CEUICCUIV: <operation>,<op_state>[, <iccid>] 2. When verifying the triggered action, respond with the user's intent

[0127] <user_response> : Integer type, indicating the response to the user's intent verification. 0 The user does not intend to verify this action 1 The user intends to verify the action

[0128] <iccid>: string type; specifies a unique number to identify a configuration profile in the eUICC.

[0129] <operation>: Integer type, indicating the operation that requires verification of the user's intention. 0 Unknown 1 Download and install the configuration file 2 Enable the profile 3 Disable profile 4 Delete the configuration file 5 eUICC memory reset 6 Update SM-DP+ address

[0130] <op_state> : Integer type, indicating the status of verifying the user's intention for a specific operation. 0 No verification required 1 Verification required

[0131] The second example includes obtaining the eUICC ID (e.g., +CGEUICCID) [Order] [Possible Response(s)] +CGEUICCID +CGEUICCID: <eid> +CME ERROR: <err> +CGEUICCID=? [surface] [7] [:] [+CGEUICCID] [Parameter command syntax]

[0132] The setup command triggers an eUICC-capable UE to request the eUICC ID (EID) for the eUICC present in the device. Users can use this function (e.g., at any time) to obtain the EID via LPA.

[0133] Defined value

[0134] <eid>: string type; indicates the eUICC identifier consisting of 32 digits, where each digit is represented by a character in the set [0123456789]

[0135] Instances with valid EIDs are: 8900 1012 0123 4123 4012 3456 7890 1224 8900 1567 01020304 0506 0708 0910 1152 8904 4011 1122 3344 1122 3344 1122 3321 0090 9231 2229 9992 3581 2903 6544 3008

[0136] The third example includes eSIM profile notification management (e.g., +CEUICCPNM) [Order] [Possible Response(s)] +CEUICCPNM= <operation>[,<seq_no> ] like <operation>=0 [+CEUICCPNM: <seq_no1>,<profile_event>[, <iccid> ] [ <cr> <lf>+CEUICCPNM: <seq_no2>,<profile_event>[, <iccid>] […]]] +CME ERROR: <err> +CEUICCPNM=? +CEUICCPM:(Supported <operation>range) [surface] [8] [:] [+CEUICCPNM] [Parameter command syntax]

[0137] The Set Command will manage pending notifications that are generated when a profile management operation has been successfully performed on the eUICC or when such an operation is in progress. <operation>= 0, the command returns a list of sequence numbers, each of which represents a pending notification. <operation>= 1, this command triggers the LPA 114 to send all pending notifications to the SM-DP+. <operation>= 2, this command triggers LPA 114 to use <operation>=0 The extracted sequence number deletes the specific pending information.

[0138] Test command return <operation>.

[0139] Defined values:

[0140] <operation>: Integer type, indicating the operation to be completed for the notification management of the profile installed in the eUICC. 0 List pending notifications 1 Send all hold notifications to SM-DP+ 2. Delete notification

[0141] <iccid>: string type; specifies a unique number to identify a configuration profile in the eUICC.

[0142] <seq_no> : Integer type, indicating the sequence number representing the hold notification.

[0143] <profile_event> : Integer type, indicating the profile event of the notification generated by the eUICC. 0 Notice about installation 1 Notification about activation of this terminal 2. Notice about the deactivation of this terminal 3. Notice of deletion from this site 4 Notice about Rpm activation 5. Notice on the deactivation of Rpm 6 Notice about Rpm deletion 7 Loading Rpm package results

[0144] Various specific AT command names are used herein, including at least +CEUICCPD, +CEUICCPM, +CEUICCPMETAI, +CEUICCMEMRESET, +CEUICCUSMDPA, +CEUICCUIV, +CGEUICCID, and +CEUICCPNM. Each of these AT command names is exemplary only, and additional, fewer, or different AT commands, which may have different names, may be used consistent with the disclosure herein.

[0145] FIG11 illustrates an example method 1100 for wireless communication by a UE according to one or more aspects described herein. As further described herein, in one or more embodiments, method 1100 supports one or more aspects of profile activation and selection triggering of an eUICC. In some cases, the UE may be UE 102, wireless device 1402, or any other UE described herein. Method 1100 may be performed by a processor, transceiver (or primary radio), or other component of the UE.

[0146] At 1102, method 1100 includes receiving, at a UE's LPA and via a local management interface, an AT command from a UE peripheral device.

[0147] At 1104, method 1100 includes determining that the AT command is for an eUICC of the UE, the eUICC configured to support a plurality of eSIM profiles.

[0148] At 1106, method 1100 includes providing a request to the eUICC according to the AT command.

[0149] At 1108, method 1100 includes obtaining an indication of the status of the request from the eUICC that responded to the request.

[0150] At 1110, method 1100 includes providing an AT command response to the UE peripheral device via the local management interface, the AT command response being based at least in part on the indication of the status.

[0151] In one or more embodiments, the method further includes determining that the AT command includes a request to perform a boot code procedure to download and install the eSIM configuration file in the eUICC, wherein the request provided to the eUICC includes an indication to initiate the boot code download procedure.

[0152] In one or more embodiments, the method further includes providing an AT command response indicating a confirmation code request to the UE peripheral device via the local management interface and in response to the request to execute the startup code program, wherein the AT command includes a first AT command; and receiving a second AT command identifying the confirmation code from the UE peripheral device in response to the confirmation code request.

[0153] In one or more embodiments, the method further includes providing, via the local management interface and in response to verifying the eSIM profile, a request for a PIN from the UE peripheral device, wherein the AT command includes a first AT command; and receiving, in response to the request for the PIN, a second AT command identifying the PIN from the UE peripheral device.

[0154] In one or more embodiments, the method further includes identifying a failure associated with downloading or installing the eSIM profile; and providing, via the local management interface and in response to identifying the failure, an AT command response identifying the type of the failure.

[0155] In one or more embodiments, the method further includes determining that the AT command includes a request to activate an eSIM profile in an eUICC, wherein the request provided to the eUICC includes the request to activate the eSIM profile, and the AT command response indicates success or failure of activating the eSIM profile, wherein the eSIM profile is a first eSIM profile.

[0156] In one or more embodiments, the method further includes determining that the second eSIM profile has an enabled status based at least in part on the request to enable the first eSIM profile, wherein the AT command response indicates a failure to enable the first eSIM profile.

[0157] In one or more embodiments, the method further includes determining that the AT command includes a request to deactivate or delete an eSIM profile in an eUICC, wherein the request provided to the eUICC includes the request to deactivate or delete the eSIM profile, and the AT command response indicates success or failure of deactivating or deleting the eSIM profile.

[0158] In one or more embodiments, the method further includes determining, based at least in part on the request to deactivate or delete the eSIM profile, that a profile policy does not permit deactivation or deletion of the eSIM profile, wherein the AT command response indicates a failure to deactivate or delete the eSIM profile.

[0159] In one or more embodiments, the method further includes determining that the eSIM profile has been deactivated or deleted based at least in part on a request to deactivate or delete the eSIM profile, wherein the AT command response indicates success in deactivating or deleting the eSIM profile.

[0160] In one or more embodiments, the method further includes determining that the AT command includes one or more of a request to add or update a nickname of an eSIM profile among a plurality of eSIM profiles, read metadata of the eSIM profile, perform a memory reset of the eUICC, or update a subscription manager address (e.g., an SM-DP+ address, which may be an SM-DP+ address), wherein the AT command response includes an acknowledgment of one or more of the requests to add or update the nickname of the eSIM profile, read metadata of the eSIM profile, perform a memory reset, or update the subscription manager address.

[0161] In one or more embodiments, the method further includes determining that the AT command includes a notification management command, wherein the request provided to the eUICC includes at least one of a request for a list of sequence numbers associated with one or more on-hold notifications, a request to send the one or more on-hold notifications to the SM-DP+, or a request to delete the one or more on-hold notifications.

[0162] In one or more embodiments, the method further includes determining that the AT command includes a request to provide an EID from an eUICC, wherein the request provided to the eUICC includes a request to provide the EID.

[0163] In some embodiments, the eUICC includes an LPA. In some embodiments, the UE's modem or baseband includes an LPA.

[0164] Method 1100 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this specification.

[0165] FIG12 illustrates an example method 1200 for wireless communication via a UE peripheral device according to one or more aspects described herein. As further described herein, in one or more embodiments, method 1200 supports one or more aspects of profile activation and selection triggering of an eUICC. In some cases, the UE peripheral device may be UE peripheral device 108, UE peripheral device 1420, or any other user device or UE peripheral device described herein. Method 1200 may be performed using a processor, transceiver, or other component of the UE peripheral device.

[0166] At 1202 , method 1200 includes selecting, from a set of AT commands for eUICC testing, an AT command for an eUICC of a UE configured to support a plurality of eSIM profiles.

[0167] At 1204, the method 1200 includes providing an AT command to the UE via the local management interface, the AT command being for an eUICC of the UE configured to support a plurality of eSIM profiles.

[0168] At 1206, method 1200 includes receiving an AT command response from the UE via the local management interface in response to the AT command.

[0169] In some embodiments, the AT command includes a request to execute a boot code procedure to download and install the eSIM configuration file in the eUICC.

[0170] In one or more embodiments, the method further includes receiving, via a local management interface and in response to a request to execute a boot code program, an AT command response indicating a confirmation code request, wherein the AT command includes a first AT command; determining a confirmation code in response to the confirmation code request; and transmitting, via the local management interface and in response to the confirmation code request, a second AT command identifying the confirmation code.

[0171] In one or more embodiments, the method further includes receiving a request for a PIN via the local management interface in response to the request to execute the boot code program, wherein the AT command includes a first AT command; and transmitting a second AT command identifying the PIN via the local management interface in response to the request for the PIN.

[0172] In some embodiments, the AT command includes a request to activate, deactivate, or delete a first eSIM profile; and the AT command response indicates success or failure in activating, deactivating, or deleting the first eSIM profile.

[0173] In one or more embodiments, the method further includes determining that the second eSIM profile has an enabled status based at least in part on the AT command response, wherein the AT command response indicates a failure to enable the first eSIM profile.

[0174] In some embodiments, the AT command includes one or more of a request to update the nickname of the eSIM profile, read metadata of the eSIM profile, perform a memory reset of the eUICC, or update the address of the subscription manager, wherein the AT command response includes an acknowledgment of one or more of the requests to update the nickname of the eSIM profile, read metadata of the eSIM profile, perform a memory reset, or update the address of the subscription manager.

[0175] Method 1200 may be variously embodied, expanded, or adapted, as described in the following paragraphs and elsewhere in this specification.

[0176] Embodiments contemplated herein include one or more non-transitory computer-readable media storing instructions for causing an electronic device to perform one or more elements of method 1100 or 1200 after the instructions are executed by one or more processors of the electronic device. In the context of method 1100, the non-transitory computer-readable medium may be, for example, a memory of a UE (such as memory 1406 of wireless device 1402, which is a UE, as described herein). In the context of method 1200, the non-transitory computer-readable medium may be, for example, a memory of a UE peripheral device (such as memory 1424 of UE peripheral device 1420, as described herein).

[0177] Embodiments contemplated herein include an apparatus having logic, modules, or circuitry for performing one or more elements of method 1100 or 1200. In the context of method 1100, the apparatus may be, for example, an apparatus of a UE (such as wireless device 1402 that is a UE). In the context of method 1200, the apparatus may be, for example, an apparatus of a UE peripheral device (such as UE peripheral device 1420, as described herein).

[0178] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media that use or store instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 1100 or 1200. In the context of method 1100, the apparatus may be, for example, an apparatus of a UE (such as wireless device 1402 that is a UE, as described herein). In the context of method 1200, the apparatus may be, for example, an apparatus of a UE peripheral device (such as UE peripheral device 1420, as described herein).

[0179] Embodiments contemplated herein include signals as described in or associated with one or more elements of method 1100 or 1200 .

[0180] Embodiments contemplated herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of method 1100 or 1200. In the context of method 1100, the processor may be a processor of a UE (such as processor(s) 1404 of wireless device 1402 of a UE, as described herein), and the instructions may, for example, be located in the processor and / or in a memory of the UE (such as memory 1406 of wireless device 1402 of a UE, as described herein). In the context of method 1200, the processor may be a processor of a UE peripheral device (such as processor(s) 1422 of UE peripheral device 1420, as described herein), and the instructions may, for example, be located in the processor and / or in a memory of the UE peripheral device (such as memory 1424 of UE peripheral device 1420, as described herein).

[0181] FIG13 illustrates an example architecture of a wireless communication system according to embodiments described herein. The following description is provided for an example wireless communication system 1300 operating in conjunction with LTE system standards or specifications and / or 5G or NR system standards or specifications as provided by 3GPP technical specifications.

[0182] As shown, wireless communication system 1300 includes UE 1302 and UE 1304 (although any number of UEs may be used). In this example, UE 1302 and UE 1304 are depicted as smartphones (e.g., handheld touch-screen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0183] UE 1302 and UE 1304 may be configured to be communicatively coupled to RAN 1306. In one embodiment, RAN 1306 may be NG-RAN, E-UTRAN, or the like. UE 1302 and UE 1304 utilize a connection (or tunnel) (shown as connection 1308 and connection 1310, respectively) with RAN 1306. Each of these UEs includes a physical communication interface. RAN 1306 may include one or more network devices, such as base stations 1312 and 1314, that enable connections 1308 and 1310.

[0184] In this example, connection 1308 and connection 1310 are air interfaces to facilitate such communicative coupling and may conform to the RAT(s) used by RAN 1306 (such as, for example, LTE and / or NR).

[0185] In some embodiments, UE 1302 and UE 1304 can also directly exchange communication data via sidelink interface 1316. UE 1304 is shown as being configured to access an access point (shown as AP 1318) via connection 1320. For example, connection 1320 may include a local wireless connection, such as one conforming to any IEEE 802.11 protocol, where AP 1318 may include a Wi-Fi® router. In this example, AP 1318 can connect to another network (e.g., the Internet) without going through CN 1324.

[0186] In an embodiment, UE 1302 and UE 1304 may be configured to communicate with each other using orthogonal frequency division multiplexing (OFDM) communication signals or with base station 1312 and / or base station 1314 via multi-carrier communication channels according to various communication techniques, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. OFDM signals may include a plurality of orthogonal subcarriers.

[0187] In some embodiments, all or part of base station 1312 or base station 1314 may be implemented as one or more software entities running on a server computer as part of a virtual network. Additionally, or in other embodiments, base station 1312 or base station 1314 may be configured to communicate with each other via interface 1322. In embodiments where wireless communication system 1300 is an LTE system (e.g., when CN 1324 is an EPC), interface 1322 may be an X2 interface. The X2 interface may be defined between two or more network devices (e.g., two or more eNBs and the like) connected to an EPC in a RAN and / or between two eNBs connected to an EPC. In embodiments where wireless communication system 1300 is an NR system (e.g., when CN 1324 is a 5GC), interface 1322 may be an Xn interface. The Xn interface is defined between two or more network devices (e.g., two or more gNBs or the like) connected to 5GC in the RAN, between a base station 1312 (e.g., a gNB) and an eNB connected to the 5GC, and / or between two eNBs (e.g., CN 1324) connected to the 5GC.

[0188] RAN 1306 is shown as being communicatively coupled to CN 1324. CN 1324 may include one or more network elements 1326 configured to provide various data and telecommunication services to customers / subscribers (e.g., UE 1302 and users of UE 1304) connected to CN 1324 via RAN 1306. Components of CN 1324 may be implemented in one physical device or in separate physical devices including components that read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0189] In an embodiment, CN 1324 may be an EPC, and RAN 1306 may be connected to CN 1324 via an S1 interface 1328. In an embodiment, S1 interface 1328 may be divided into two parts: an S1-user plane (S1-U) interface, which carries traffic data between base station 1312 or base station 1314 and a serving gateway (S-GW), and an S1-MME interface, which is a messaging interface between base station 1312 or base station 1314 and a mobility management entity (MME).

[0190] In an embodiment, CN 1324 may be a 5GC, and RAN 1306 may be connected to CN 1324 via an NG interface 1328. In an embodiment, NG interface 1328 may be divided into two parts: an NG user plane (NG-U) interface, which carries traffic data between base station 1312 or base station 1314 and a user plane function (UPF), and an S1 control plane (NG-C) interface, which is a messaging interface between base station 1312 or base station 1314 and an access and mobility function (AMF).

[0191] Generally speaking, application server 1330 may be a component that provides applications (e.g., packet-switched data services) that utilize Internet Protocol (IP) bearer resources with CN 1324. Application server 1330 may also be configured to support one or more communication services (e.g., VoIP sessions, group messaging sessions, etc.) between UE 1302 and UE 1304 via CN 1324. Application server 1330 may communicate with CN 1324 via IP communication interface 1332.

[0192] FIG14 illustrates an example system 1400 for performing communication 1438 between a wireless device 1402 and a UE peripheral device 1420 according to embodiments described herein. System 1400 can be part of a wireless communication system as described herein. Wireless device 1402 can be, for example, a UE of the wireless communication system. UE peripheral device 1420 can be, for example, a user device used during or shortly after manufacturing in conjunction with conformance testing or other testing to determine the correct operation of wireless device 1402.

[0193] Wireless device 1402 may include one or more processors 1404. Processor(s) 1404 may execute instructions to cause various operations of wireless device 1402 to be performed, as described herein. Processor(s) 1404 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a controller, a field-programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0194] Wireless device 1402 may include memory 1406. Memory 1406 may be a non-transitory, computer-readable storage medium that stores instructions 1408 (which may include, for example, instructions being executed by processor(s) 1404). Instructions 1408 may also be referred to as program code or a computer program. Memory 1406 may also store data used by processor(s) 1404 and the results of operations performed.

[0195] The wireless device 1402 may include one or more transceiver(s) 1410 (also collectively referred to as transceivers 1410), which may include radio frequency (RF) transmitter and / or receiver circuitry using antenna(s) 1412 of the wireless device 1402 to facilitate communication (e.g., communication 1438) from the wireless device 1402 to and / or from other devices (e.g., UE peripheral devices 1420) according to a corresponding RAT.

[0196] Wireless device 1402 may include one or more antennas 1412 (e.g., one, two, four, eight, or more). For embodiments with multiple antennas 1412, wireless device 1402 may exploit the spatial diversity of such multiple antennas 1412 to transmit and / or receive multiple different data streams over the same time and frequency resources. This behavior may be referred to as, for example, MIMO behavior (referring to the use of multiple antennas at each of the transmitting and receiving devices that facilitate this behavior). MIMO transmission by wireless device 1402 may be accomplished based on precoding (or digital beamforming) applied to wireless device 1402. This multiplexes the data streams across antenna(s) 1412 based on known or assumed channel characteristics, such that each data stream is received with appropriate signal strength relative to the other streams and at a desired location in the spatial domain (e.g., at the location of the receiver associated with that data stream). Some embodiments may utilize single-user MIMO (SU-MIMO) methods (where all data streams are directed to a single receiver) and / or multi-user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers at different locations in the spatial domain).

[0197] In some embodiments with multiple antennas, the wireless device 1402 may implement analog beamforming techniques to relatively adjust the phases of the signals transmitted by the antenna(s) 1412 so that the (joint) transmissions of the antenna(s) 1412 can be steered (this is sometimes referred to as beam steering).

[0198] Wireless device 1402 may include one or more interface(s) 1416. Interface(s) 1416 may be used to provide input to or output from wireless device 1402. For example, wireless device 1402, which is a UE, may include interface(s) 1416, such as a microphone, speaker, touchscreen, buttons, and the like, to allow a user of the UE to provide input and / or output to the UE. Other interfaces of such a UE may include transmitters, receivers, and other circuitry (e.g., in addition to the transceiver(s) 1410 / antenna(s) 1412 already described) that allow communication between the UE and other devices and operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0199] Wireless device 1402 may include a profile manager 1418. Profile manager 1418 may be implemented via hardware, software, or a combination thereof. For example, profile manager 1418 may be implemented as a processor, circuitry, and / or instructions 1408 stored in memory 1406 and executed by processor(s) 1404. In some examples, profile manager 1418 may be integrated within processor(s) 1404 and / or transceiver(s) 1410. For example, profile manager 1418 may be implemented by a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor(s) 1404 or transceiver(s) 1410.

[0200] From the perspective of a wireless device or UE, the profile manager 1418 may be used in various aspects of the present disclosure, such as the aspects of Figures 1 to 14. The profile manager 1418 may be configured to, for example, receive an AT command from a UE peripheral device at a UE's LPA and via a local management interface; determine that the AT command is directed to the UE's eUICC, which is configured to support multiple eSIM profiles; provide a request to the eUICC based on the AT command; obtain an indication of a status of the request from the eUICC in response to the request; and provide an AT command response to the UE peripheral device via the local management interface, the AT command response being based at least in part on the indication of the status.

[0201] The UE peripheral device 1420 may include one or more processors 1422. The processor(s) 1422 may execute instructions to cause various operations of the UE peripheral device 1420 to be performed, as described herein. The processor(s) 1422 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0202] UE peripheral device 1420 may include memory 1424. Memory 1424 may be a non-transitory computer-readable storage medium that stores instructions 1426 (which may include, for example, instructions being executed by processor(s) 1422). Instructions 1426 may also be referred to as program code or computer programs. Memory 1424 may also store data used by processor(s) 1422 and the results of operations performed.

[0203] The UE peripheral device 1420 may include one or more transceiver(s) 1428 (also collectively referred to as transceivers 1428), which may include RF transmitter and / or receiver circuitry using the UE peripheral device 1420's antenna(s) 1430 to facilitate communication (e.g., communication 1416) from the UE peripheral device 1420 to and / or from other devices (e.g., wireless device 1402) according to a corresponding RAT.

[0204] The UE peripheral device 1420 may include one or more antennas 1430 (e.g., one, two, four, or more). As described above, in embodiments with multiple antennas 1430, the UE peripheral device 1420 may perform MIMO, digital beamforming, analog beamforming, beam steering, and the like.

[0205] The UE peripheral device 1420 may include one or more interface(s) 1432. The interface(s) 1432 may be used to provide input to the UE peripheral device 1420 or output from the wireless device. For example, a UE peripheral device 1420 of a RAN (e.g., a base station, a radio head, etc.) may include interface(s) 1432 comprised of transmitters, receivers, and other circuitry (e.g., in addition to the transceiver(s) 1428 / antenna(s) 1430 already described). The interface(s) enable the UE peripheral device 1420 to communicate with other devices in the network and / or enable the UE peripheral device 1420 to communicate with external networks, computers, databases, and the like for the purpose of operating, managing, and maintaining the UE peripheral device 1420 or other devices operatively connected thereto.

[0206] UE peripheral device 1420 may include at least one of the profile managers 1434. Profile manager 1434 may be implemented via hardware, software, or a combination thereof. For example, profile manager 1434 may be implemented as a processor, circuitry, and / or instructions 1426 stored in memory 1424 and executed by processor(s) 1422. In some examples, profile manager 1434 may be integrated within processor(s) 1422 and / or transceiver(s) 1428. For example, profile manager 1434 may be implemented by a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor(s) 1422 or transceiver(s) 1428.

[0207] From the perspective of UE peripherals, profile manager 1434 may be used in various aspects of the present disclosure, such as the aspects of Figures 1 through 14. Profile manager 1434 may be configured to select, from a set of AT commands for eUICC testing, an AT command for a UE's eUICC configured to support multiple eSIM profiles; provide the AT command to the UE via a local management interface, the AT command being targeted at the eUICC of the UE; and receive an AT command response from the UE via the local management interface in response to the AT command.

[0208] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more operations, techniques, procedures, and / or methods as described herein. For example, a baseband processor (or processors) as described herein in conjunction with one or more of the preceding figures may be configured to operate according to one or more of the examples described herein. As another example, circuitry associated with a UE, UE peripherals, network elements, etc., as described above in conjunction with one or more of the preceding figures, may be configured to operate according to one or more of the examples described herein.

[0209] Unless expressly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more embodiments provides illustration and description but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form described. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0210] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic for performing the operations, or may include a combination of hardware, software, and / or firmware.

[0211] The systems described herein are provided with respect to specific embodiments, but are provided as examples. These embodiments may be combined into a single system, partially combined into other systems, separated into multiple systems, or otherwise divided or combined. Furthermore, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be utilized in another embodiment. For clarity, parameters, attributes, aspects, etc. are described only in relation to one or more embodiments, and unless specifically denied herein, it should be understood that such parameters, attributes, aspects, etc. may be combined with or substituted for those of another embodiment.

[0212] Although the foregoing has been described in some detail for the purposes of clarity, it should be understood that changes and modifications can be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the procedures and the apparatus described herein. Therefore, the present embodiments are to be considered as illustrative and not restrictive, and the description is not to be limited to the details provided herein, but may be modified within the scope and scope of equivalents of the appended claims.

[0213] 100: Wireless communication system 102:UE 104: Network device 108:UE peripheral devices 112: Mobile Station (MS); MS; Mobile Station 114: Local Profile Assistant (LPA); LPA 114-a:LPA 114-b:LPA 116:eUICC 118: Local management interface 120:Connect 122: First eSIM profile 124: Second eSIM profile 126: Third eSIM profile 200:Signal Flow 202: Steps 204: Steps 206: Steps 208: Steps 210: Unsolicited response 212: Confirmation code response 214: Confirmation code response 216: Steps 218: Steps 220: Steps 222: Steps 224: AT command response 226: Steps 228: Steps 230: Steps 232: Steps 234: Steps 236: Steps 240: Submission 250: Submission 300:Signal Flow 302: Steps 304: Steps 306: Steps 308: Steps 310: Steps 312: Steps 314: Steps 316: Steps 318: Steps 320: Steps 322: Steps 324: Steps 326: Steps 328: Steps 330: Steps 332: Steps 336: Steps 338: Steps 400:Signal Flow 402: Steps 404: Steps 406: Steps 408: Steps 410: Steps 412: Steps 414: Steps 416: Steps 418: Steps 420: Submission 422: Steps 424: Steps 426: Steps 430: Steps 432: Issuer Security Domain – Root (ISD-R); ISD-R 500:Signal Flow 502: Steps 504: Steps 506: Steps 508: Steps 510: Steps 512: Steps 514: Steps 516: Steps 518: Submission; Steps 520: Steps 522: Steps 524: Steps 526: Steps 528: Submission 600:Signal Flow 602: Step 604: Steps 606: Steps 608: Steps 610: Steps 612: Steps 614: Steps 618: Steps 620: Submission 622: Steps 624: Steps 626: Steps 628: Steps 630: Steps 632: Submission 700:Signal Flow 702: Steps 704: Steps 706: Steps 708: Steps 710: Steps 712: Steps 800:Signal Flow 802: Step 804: Steps 806: Steps 808: Steps 810: Steps 812: Steps 816: Steps 900:Signal Flow 902: Steps 904: Steps 906: Steps 908: Steps 910: Steps 914: Steps 916: Steps 1000:Signal Flow 1002: Step 1004: Step 1006: Steps 1012: Steps 1014: Steps 1016:LPA Service 1018: Device 1100: Method 1102: Steps 1104: Steps 1106: Steps 1108: Steps 1110: Steps 1200: Method 1202: Steps 1204: Steps 1206: Steps 1300: Wireless Communication System 1302:UE 1304:UE 1306:RAN 1308:Connect 1310:Connect 1312:Base station 1314:Base station 1316: Side Link Interface 1318:AP 1320:Connect 1322: Interface 1324:CN 1326: Network Components 1328: S1 interface; NG interface 1330: Application Server 1332:IP communication interface 1400: System 1402: Wireless device 1404:Processor 1406:Memory 1408: Instructions 1410: Transceiver 1412: Antenna 1416: Interface 1418:Configuration Manager 1420:UE peripheral devices 1422: Processor 1424:Memory 1426: Instructions 1428: Transceiver 1430: Antenna 1432: Interface 1434:Configuration Manager 1438: Submission< / iccid> < / operation> < / operation> < / operation> < / operation> < / operation> < / operation> < / operation> < / err> < / iccid> < / lf> < / cr> < / iccid> < / operation> < / operation> < / eid> < / err> < / eid> < / operation> < / iccid> < / iccid> < / operation> < / iccid> < / operation> < / action> < / action> < / iccid> < / operation> < / action> < / err> < / iccid> < / action> < / result> < / result> < / err> < / cause> < / result> < / cause> < / result> < / cause> < / result> < / err> < / state> < / iccid> < / nickname> < / iccid> < / nickname> < / iccid> < / iccid> < / iccid> < / operation> < / operation> < / operation> < / err> < / state> < / iccid> < / lf> < / cr> < / state> < / iccid> < / nickname> < / iccid> < / operation> < / cause> < / result> < / cause> < / result> < / state> < / iccid> < / operation> < / operation> < / iccid> < / cause> < / state> < / iccid> < / result> < / operation> < / iccid> < / state> < / iccid2> < / state> < / iccid1> < / err> < / iccid> < / operation> < / result> < / result> < / result> < / result> < / result> < / result> < / result> < / result> < / result> < / result> < / pin> < / cause> < / result> < / cause> < / result> < / iccid> < / result> < / mode> < / mode> < / mode> < / cause> < / iccid> < / result> < / err> < / mode>

Claims

1. A user equipment (UE) comprising: an embedded universal integrated circuit card (eUICC); a local profile assistant (LPA) coupled to the eUICC, the LPA being configured to support a local management interface for a user; and a processor configured to enable the UE to receive an attention (AT) command from a UE test device or a UE extension device of an enhanced user interface (UI) via the local management interface without establishing a connection with a network device; determining that the AT command is directed to the eUICC, the eUICC being configured to support a plurality of embedded user identity module (eSIM) profiles; and providing a request to the eUICC according to the AT command. The system obtains an indication of the status of the request from the eUICC responding to the request; and provides an AT command response to the UE test device or the UE extension device of the enhanced UI via the local management interface, the AT command response being at least in part based on the indication of the status.

2. The UE of request item 1, wherein the processor is further configured to cause the UE to: determine that the AT command contains a request to execute a startup code procedure to download and install an eSIM profile in the eUICC, wherein the request provided to the eUICC contains an instruction to initiate a startup code download procedure.

3. The UE as requested in item 2, wherein the processor is further configured such that the UE: provides an AT command response indicating an acknowledgment code request to the UE peripheral device via the local management interface and in response to the request to execute the activation code procedure, wherein the AT command includes a first AT command; and receives a second AT command identifying an acknowledgment code from the UE peripheral device in response to the acknowledgment code request.

4. The UE as requested in item 2, wherein the processor is further configured to enable the UE to: provide a request for a personal identification number (PIN) from the UE peripheral device via the local management interface and in response to verifying the eSIM profile, wherein the AT command includes a first AT command; and receive a second AT command from the UE peripheral device to identify the PIN in response to the request for the PIN.

5. The UE as requested in item 2, wherein the processor is further configured to enable the UE to: identify a failure associated with the download or installation of the eSIM profile; and, via the local management interface and in response to the identification of the failure, provide an AT command response of a type that identifies the failure.

6. The UE of request item 1, wherein the processor is further configured to enable the UE to: determine that the AT command contains a request to enable an eSIM profile in the eUICC, wherein the request provided to the eUICC contains the request to enable the eSIM profile, and the AT command response indicates either a success or a failure in enabling the eSIM profile.

7. The UE of request item 1, wherein the processor is further configured to cause the UE to: determine that the AT command contains a request to disable an eSIM profile in the eUICC, wherein the request provided to the eUICC contains the request to disable the eSIM profile, and the AT command responds with an indication of success or failure in disabling the eSIM profile.

8. The UE of request item 7, wherein the processor is further configured such that the UE: determines, at least in part, based on the request to disable the eSIM profile, that a profile policy does not allow the disabling of the eSIM profile, wherein the AT command responds to the failure indicating the disabling of the eSIM profile.

9. The UE of request item 7, wherein the processor is further configured such that the UE: determines that the eSIM profile has been disabled at least in part based on the request to disable the eSIM profile, wherein the AT command response indicates the success of disabling the eSIM profile.

10. The UE of request item 1, wherein the processor is further configured to cause the UE to: determine that the AT command contains a request to delete an eSIM profile in the eUICC, wherein the request provided to the eUICC contains the request to delete the eSIM profile, and the AT command response indicates a success or a failure in deleting the eSIM profile.

11. The UE of request item 10, wherein the processor is further configured such that the UE: determines, at least in part, based on the request to delete the eSIM profile, that a profile policy does not allow the deletion of the eSIM profile, wherein the AT command response indicates the failure to delete the eSIM profile.

12. The UE of request item 1, wherein the processor is further configured to cause the UE to: determine that the AT command includes one or more of the following: adding or updating a nickname of an eSIM profile among the plurality of eSIM profiles, reading the post-processing data of the eSIM profile, performing a memory reset of the eUICC, or updating a default Subscription Manager Data Preparation Platform (SM-DP+) address, wherein the AT command responds to an acknowledgment of the one or more of the requests including adding or updating the nickname of the eSIM profile, reading the post-processing data of the eSIM profile, performing the memory reset, or updating the default SM-DP+ address.

13. The UE of request item 1, wherein the processor is further configured to cause the UE to: determine that the AT command includes a notification management command, wherein the request provided to the eUICC includes a request for a list of serial numbers associated with one or more shelved notifications, a request to send the one or more shelved notifications to a subscription manager data preparation platform (SM-DP+), or a request to delete at least one of the one or more shelved notifications.

14. The UE of request item 1, wherein the processor is further configured such that the UE: determines that the AT command contains a request to provide an eUICC identifier (EID) from the eUICC, wherein the request to the eUICC contains the request to provide the EID.

15. For the UE in request item 1, the eUICC contains the LPA, or a modem of the UE contains the LPA.

16. A user equipment (UE) peripheral device comprising: a local management interface configured to communicate with a UE via a serial interface; and a processor configured to enable the UE peripheral device to select, from a set of alert (AT) commands for testing an embedded universal integrated circuit card (eUICC), an AT command for a UE configured to support a plurality of embedded user identity module (eSIM) profiles; provide the AT command to the UE via the serial interface of the local management interface, the AT command being directed to the eUICC of the UE; and receive, via the local management interface, an AT command response from the UE in response to the AT command.

17. The UE peripheral device as requested in Request 16, wherein the AT command includes a request to execute a startup code procedure to download and install an eSIM profile in the eUICC.

18. As in request item 16, the UE peripheral device, wherein: The AT command includes a request to enable, disable, or delete an eSIM profile; and the AT command responds with a success or failure indicating whether to enable, disable, or delete the eSIM profile.

19. The UE peripheral device as requested in Request 16, wherein the AT command includes one or more requests to update a nickname in an eSIM profile, read the post-processing data of the eSIM profile, perform a memory reset of the eUICC, or update a subscription manager address, wherein the AT command responds with an acknowledgment including the one or more of the requests to update the nickname in the eSIM profile, read the post-processing data of the eSIM profile, perform the memory reset, or update the subscription manager address.

20. A method of controlling a user equipment (UE), comprising: receiving an alert (AT) command from a UE peripheral device via a local management interface; determining that the AT command is directed to an embedded universal integrated circuit card (eUICC) and that the AT command includes a notification management command, the eUICC being configured to support a plurality of embedded user identity modules (eSIM) profiles; providing a request to the eUICC according to the AT command, the request to the eUICC including a request for a list of serial numbers associated with one or more shelved notifications, a request to send the one or more shelved notifications to a subscription manager data preparation platform (SM-DP+), or a request to delete at least one of the one or more shelved notifications; obtaining an indication of a status of the request from the eUICC responding to the request; and providing an AT command response to the UE peripheral device via the local management interface, the AT command response being at least partially based on the indication of the status.

21. A user equipment (UE) comprising: an embedded universal integrated circuit card (eUICC); a local profile assistant (LPA) coupled to the eUICC, the LPA being configured to support a local management interface toward a user; and a processor configured to enable the UE to receive an alert (AT) command from a UE peripheral device via the local management interface; determining that the AT command is directed to the eUICC and that the AT command includes a request to delete an eSIM profile, the eUICC being configured to support a plurality of embedded user identity module (eSIM) profiles; and providing a request to the eUICC according to the AT command, the request to the eUICC including the request to delete the eSIM profile; The system obtains an indication of the status of the request from the eUICC responding to the request; and provides an AT command response to the UE peripheral device via the local management interface, the AT command response being at least in part based on the indication of the status and indicating that a profile policy does not allow the deletion of the eSIM profile.

22. A user equipment (UE) comprising: an embedded universal integrated circuit card (eUICC); a local profile assistant (LPA) coupled to the eUICC, the LPA being configured to support a local management interface toward a user; and a processor configured to enable the UE to receive an alert (AT) command from a UE peripheral device via the local management interface; determining that the AT command is directed to the eUICC and that the AT command includes a notification management command, the eUICC being configured to support a plurality of embedded user identity module (eSIM) profiles; and providing a request to the eUICC according to the AT command, the request to the eUICC including a request for a list of serial numbers associated with one or more shelved notifications, a request to send the one or more shelved notifications to a subscription manager data preparation platform (SM-DP+), or a request to delete at least one of the one or more shelved notifications; The system obtains an indication of the status of the request from the eUICC responding to the request; and provides an AT command response to the UE peripheral device via the local management interface, the AT command response being at least in part based on the indication of the status.

Images