Dynamic management of deployed eSIM for wireless devices

Abstract

Techniques for dynamically managing a deployed electronic subscriber identity module (eSIM) of a wireless device are described. A provisioning eSIM is installed in the wireless device to provide finite function connection options for basic services such as device activation and user eSIM provisioning. To reduce signaling loading on the network and conserve wireless device battery power, the deploying eSIM is dynamically reconfigured between an inactive state and an active state based on user actions and system requirements.

Description

Technical Field

[0001] The described embodiments set forth techniques for dynamically managing a provisioning electronic subscriber identity module (eSIM) of a wireless device. The provisioning eSIM is installed in the wireless device to provide limited functionality connectivity options for basic services such as device activation and user eSIM provisioning. To reduce signaling load on the network and save wireless device battery power, the provisioning eSIM is dynamically reconfigured between an inactive state and an active state based on user actions and system requirements. Background Art

[0002] Many mobile wireless devices are configured to use a removable Universal Integrated Circuit Card (UICC) that enables the mobile wireless device to access services provided by a mobile network operator (MNO). Specifically, each UICC includes at least a microprocessor and a read-only memory (ROM), wherein the ROM is configured to store an MNO profile, which the wireless device can use to register and interact with the MNO to obtain wireless services via a cellular wireless network. The profile may also be referred to as a subscriber identity module (SIM). Typically, the UICC takes the form of a small removable card (often referred to as a SIM card) that is inserted into the UICC receiving area of ​​the mobile wireless device. In recent implementations, the UICC is directly embedded into the system board of the wireless device as an embedded UICC (eUICC), which may provide advantages over traditional removable UICCs. The eUICC may include a rewritable memory that may facilitate the installation, modification and / or deletion of one or more electronic SIMs (eSIMs) on the eUICC, wherein the eSIM may provide new and / or different services and / or updates for accessing extended features provided by the MNO. The eUICC may store several MNO profiles (also referred to herein as eSIMs) and may eliminate the need to include a UICC receiving area in the wireless device.

[0003] A wireless device may include a provisioning eSIM (also referred to as a bootstrap eSIM) that is installed at the time of manufacturing or dynamically installed to the wireless device after manufacturing. The provisioning eSIM provides limited functionality connectivity options to allow the wireless device to connect to a cellular wireless network for basic services, such as for device activation, user eSIM installation, etc. Currently, the provisioning eSIM may initiate network search and network attachment when the wireless device boots up to provide a ready connection when needed. In some cases, such as during a new product launch, a large number of wireless devices may be connected to a cellular wireless network at the same time, which poses a challenge to the mobile network operator (MNO) infrastructure due to the high signaling load. A mechanism is needed to dynamically manage the mode / state of the provisioning eSIM to limit its use to only basic activities and offload active connections to reduce network signaling load. Summary of the invention

[0004] This application describes a technology for dynamically managing a provisioning electronic subscriber identity module (eSIM) of a wireless device. The provisioning eSIM is installed in the wireless device to provide limited functionality connectivity options for basic services such as device activation and user eSIM provisioning. To reduce signaling load on the network and save wireless device battery power, the provisioning eSIM is dynamically reconfigured between an inactive state and an active state based on user actions and system requirements.

[0005] The wireless device includes a provisioning eSIM (also referred to as a bootstrap eSIM) installed at the time of manufacture or dynamically installed to the wireless device after manufacture. The provisioning eSIM provides limited functionality connectivity options to allow the wireless device to connect to a cellular wireless network for basic services, such as connecting to an original equipment manufacturer (OEM) server for device activation, connecting to a mobile network operator (MNO) server to provision, download, and install a full-function user eSIM, etc. In order to reduce the signaling load on the cellular wireless network used by the provisioning eSIM and save battery power, the wireless device configures the provisioning eSIM to initially enter an inactive state after activation, wherein the inactive state restricts the wireless device from establishing a connection with the cellular wireless network. The inactive state may include: a cellular airplane mode in which baseband cellular wireless transceiver functionality is disabled; or a limited network search mode in which baseband cellular wireless transceiver functionality listens for signals from a cellular wireless network to prepare the wireless device for future cellular wireless connections, but does not use the provisioning eSIM to transmit or connect to the cellular wireless network while in the inactive state. In response to a user action or system requirement to establish a cellular wireless network connection, the wireless device reconfigures the provisioning eSIM from the inactive state to the active state. A client service of the wireless device requiring a provisioned eSIM cellular wireless connection may indicate a requirement to use the provisioned eSIM and release the provisioned eSIM when no longer needed. After satisfying the current network use of the provisioned eSIM, the wireless device waits for a backoff period governed by a backoff timer to allow the provisioned eSIM cellular wireless network attachment to be reused for subsequent network use when needed. The wireless device reconfigures the provisioned eSIM from an active state to an inactive state after the backoff timer expires to reduce the signaling load on the cellular wireless network associated with the provisioned eSIM and save battery power of the wireless device.

[0006] Other aspects and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate by way of example the principles of the described embodiments.

[0007] The present disclosure is provided for the purpose of summarizing some example embodiments only, so as to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be understood that the above-mentioned features are only examples and should not be construed as narrowing the scope or essence of the subject matter described herein in any way. Other features, aspects and advantages of the subject matter described herein will become apparent through the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The present disclosure will be more readily understood through the following detailed description taken in conjunction with the accompanying drawings, in which like reference numerals designate like structural elements.

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

[0010] Figure 2 Illustrated according to some embodiments Figure 1 A block diagram of a more detailed view of exemplary components of a system.

[0011] Figure 3 An exemplary device activation and provisioning network for mobile wireless devices according to some embodiments is illustrated.

[0012] Figure 4A An example state diagram for provisioning an eSIM is illustrated according to some embodiments.

[0013] Figure 4B An example activation flow for provisioning an eSIM according to some embodiments is illustrated.

[0014] Figure 5 An example of a state change of a provisioned eSIM triggered by a user action according to some embodiments is illustrated.

[0015] Fig. 6A and Figure 6B An example wireless device activation flow with provisioning eSIM state changes for a wireless device without a cellular wireless service plan is illustrated in accordance with some embodiments.

[0016] Fig. 7A , Figure 7B , Figure 7C , Fig.7D and Fig. 7E Examples of wireless device activation and adding a cellular wireless service plan to a wireless device are illustrated, wherein an eSIM state change is provisioned, according to some embodiments.

[0017] Figure 8 An example of a provisioning eSIM state change to allow emergency services connectivity is illustrated in accordance with some embodiments.

[0018] Fig. 9 An example method for dynamically managing a provisioned eSIM installed on an eUICC of a wireless device is illustrated in accordance with some embodiments.

[0019] Fig.10 An example method for dynamically managing provisioning of an eSIM for emergency services connectivity is illustrated in accordance with some embodiments.

[0020] Fig.11 A block diagram illustrating exemplary elements of a wireless device according to some embodiments is illustrated. DETAILED DESCRIPTION

[0021] Representative applications of the methods and apparatus according to the present application are described in this section. These examples are provided only to add context and aid in understanding the described embodiments. Therefore, it will be apparent to those skilled in the art that the described embodiments may be practiced without some or all of these specific details. In other cases, in order to avoid unnecessarily obscuring the described embodiments, well-known processing steps are not described in detail. Other applications are possible, so that the following examples should not be considered limiting.

[0022] In the following detailed description, reference is made to the accompanying drawings which form a part of the specification and in which are shown by way of illustration specific embodiments in accordance with the described embodiments. Although these embodiments are described in sufficient detail to enable those skilled in the art to practice the described embodiments, it is to be understood that these examples are not limiting; other embodiments may be used and modifications may be made without departing from the spirit and scope of the described embodiments.

[0023] This application describes a technology for dynamically managing a provisioning electronic subscriber identity module (eSIM) of a wireless device. The provisioning eSIM is installed in the wireless device to provide limited functionality connectivity options for basic services such as device activation and user eSIM provisioning. To reduce signaling load on the network and save wireless device battery power, the provisioning eSIM is dynamically reconfigured between an inactive state and an active state based on user actions and system requirements.

[0024] The wireless device includes a provisioning eSIM (also known as a bootstrap eSIM) installed at the time of manufacture or dynamically installed to the wireless device after manufacture. The provisioning eSIM provides limited functional connection options to allow the wireless device to connect to a cellular wireless network for basic services, such as connecting to an original equipment manufacturer (OEM) server for device activation, connecting to a mobile network operator (MNO) server to provision, download and install a full-function user eSIM, etc. The provisioning eSIM can be used to establish a cellular wireless network connection when a non-cellular wireless connection or a user eSIM cellular wireless connection is not available or cannot be established. In some cases, the provisioning eSIM may be limited to only limited-use data connections and no voice connections are allowed. In some cases, the provisioning eSIM may be limited to only connecting to certain network endpoints to allow certain management operations, such as device initialization, cellular wireless service subscription, and user eSIM download. Currently, the provisioning eSIM is enabled and configured to an active state to initiate a network search and attach to a cellular wireless network associated with the provisioning eSIM so that it is available for use when needed. However, due to the large number of wireless devices connecting to the cellular wireless network at the same time, this immediate attachment may pose a challenge to the cellular wireless network load. The cellular wireless network associated with the provisioning eSIM may be different from the cellular wireless network associated with the user eSIM that is subsequently downloaded and used for regular cellular wireless service. The bootstrap eSIM may be used as a default connection option when other wireless connections are unavailable.

[0025] As further described herein, in order to reduce the signaling load on the cellular wireless network used by the provisioning eSIM and to save battery power, the wireless device configures the provisioning eSIM to initially enter an inactive state after being enabled, wherein the inactive state restricts the wireless device from establishing a connection with the cellular wireless network. The inactive state may include i) a cellular airplane mode in which the baseband cellular wireless transceiver is disabled (not allowing cellular wireless transmission or reception); or ii) a limited network search mode in which the baseband cellular wireless receiver listens for signals from the cellular wireless network to prepare the wireless device for future cellular wireless connections, but does not use the provisioning eSIM to transmit or connect to the cellular wireless network while in the inactive state. In response to a user action or system requirement to establish a cellular wireless network connection, the wireless device reconfigures the provisioning eSIM from the inactive state to the active state. A client service of the wireless device that requires the provisioning eSIM cellular wireless connection may indicate a requirement to use the provisioning eSIM, for example, an application or system resource executed on an application processor may assert a requirement for the provisioning eSIM connection. The application or system resource may maintain the assertion until the cellular wireless network connection requirement has been completed, and then release the provisioning eSIM assertion when no longer needed. After satisfying the current network usage of the provisioning eSIM, the wireless device waits for a backoff period governed by a backoff timer. The backoff period allows the existing provisioning eSIM cellular wireless network attachment to be reused for subsequent network usage when needed, and avoids switching the provisioning eSIM back and forth between an inactive state and an active state for a series of separate network usages. After the backoff timer expires, the wireless device reconfigures the provisioning eSIM from an active state to an inactive state to reduce the signaling load on the cellular wireless network associated with the provisioning eSIM and save battery power of the wireless device.

[0026] These and other embodiments are referred to below. Figures 1 to 11 Discussion is made; however, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for illustrative purposes only and should not be construed as limiting.

[0027] Figure 1 1 illustrates a block diagram of various components of a system 100 configured to implement the various techniques described herein, according to some embodiments. More specifically, Figure 1A brief overview of a system 100 is illustrated, which includes a mobile wireless device 102 (also referred to as a wireless device, wireless device, mobile device, user equipment (UE) or the like), a set of base stations 112-1 through 112-N managed by different mobile network operators (MNOs) 114, and a set of deployment servers 116 in communication with the MNOs 114. Additional MNO infrastructure servers such as those used for account management and billing are not shown. The mobile wireless device 102 may represent a mobile computing device (e.g., of or ), base stations 112-1 to 112-n may represent cellular wireless network entities configured to communicate with mobile wireless device 102, including evolved NodeBs (eNodeBs or eNBs) and / or next generation NodeBs (gNodeBs or gNBs), and MNO 114 may represent different wireless service providers that provide specific cellular wireless services (e.g., voice and data) to which mobile wireless device 102 may subscribe, such as via a subscription account of a user of mobile wireless device 102.

[0028] like Figure 1As shown, the mobile wireless device 102 may include processing circuitry (which may include one or more processors 104 and memory 106), an embedded universal integrated circuit card (eUICC) 108, and baseband radio circuitry 110 for sending and receiving cellular wireless radio frequency signals. The baseband radio circuitry 110 may include analog hardware components, such as antennas and amplifiers, and digital processing components, such as signal processors (and / or general / limited purpose processors) and associated memory. In some embodiments, in addition to or in lieu of the eUICC 108, the mobile wireless device 102 includes one or more physical UICCs 118 (also referred to as subscriber identity modules (SIM) cards). The components of the mobile wireless device 102 work together to enable the mobile wireless device 102 to provide useful features to the user of the mobile wireless device 102, such as cellular wireless network access, non-cellular wireless network access, localized computing, location-based services, and Internet connectivity. The eUICC 108 may be configured to store multiple electronic SIMs (eSIMs) for accessing cellular wireless services provided by different MNOs 114 via connections to their respective cellular wireless networks through the base stations 112-1 to 112-N. For example, the eUICC 108 may be configured to store and manage one or more eSIMs of one or more MNOs 114 for different subscriptions associated with the mobile wireless device 102. To enable access to services provided by the MNOs, the eSIMs are retained for subsequent download and installation to the eUICC 108. In some embodiments, the eUICC 108 obtains the one or more eSIMs from one or more associated provisioning servers 116 as part of device initialization of the mobile wireless device 102 (such as when a new mobile wireless device 102 is purchased). The provisioning servers 116 may be maintained by the manufacturer of the mobile wireless device 102, the MNO 114, a third-party entity, etc. eSIM data communications between the MNO provisioning server 116 and the eUICC 108 (or between the MNO provisioning server 116 and processing circuitry (eg, processor 104) of the mobile wireless device 102 external to the eUICC 108) may use a secure communication channel.

[0029] When a user initially acquires the mobile wireless device 102, an activated full-function cellular wireless eSIM may be absent from the eUICC 108, and the mobile wireless device may also not include a UICC 118 with an activated physical SIM (pSIM) installed in the mobile wireless device 102. A user of the mobile wireless device 102 may need to download a full-function eSIM from the MNO provisioning server 116 to access the cellular wireless services of a particular MNO with which the user has established a cellular wireless subscription. After booting, the mobile wireless device 102 may enable a limited-function provisioning eSIM and configure the provisioning eSIM to be in an inactive state. When a user action or system resources indicate that a wireless network connection via the provisioning eSIM is required, and no non-cellular wireless network connection or cellular wireless connection using the user's eSIM is available or can be established, the mobile wireless device 102 reconfigures the provisioning eSIM from the inactive state to the active state to allow a connection to be established to the cellular wireless network associated with the provisioning eSIM.

[0030] Figure 2 Illustrated according to some embodiments Figure 1 A block diagram of a more detailed view 200 of certain components of a mobile wireless device 102 is shown. Figure 2 As shown, the processor 104 in conjunction with the memory 106 may implement a main operating system (OS) 202 configured to execute applications 204 (eg, native OS applications and user applications). Figure 2 As shown, the eUICC 108 may be configured to implement an eUICC OS 206 that is configured to manage the hardware resources of the eUICC 108 (e.g., a processor and memory embedded in the eUICC 108). The eUICC OS 206 may also be configured to manage the eSIM 208 stored by the eUICC 108, for example, by downloading, installing, deleting, enabling, disabling, modifying, or otherwise performing management of the eSIM 208 within the eUICC 108 and providing access to the eSIM 208 to the baseband radio circuit 110 to provide access to wireless services to the mobile wireless device 102. The eUICC 108 OS may include an eSIM manager 210 that may perform management functions for various eSIMs 208. Figure 2 In the illustrated example, each eSIM 208 may include a number of applets 212 that define the manner in which the eSIM 208 operates. For example, one or more of the applets 212, when implemented in conjunction with the baseband radio circuitry 110 and the eUICC 108, may be configured to enable the mobile wireless device 102 to communicate with the MNO 114 and provide useful features (e.g., phone calls and Internet access) to the user of the mobile wireless device 102.

[0031] Likewise Figure 2 As shown, the baseband radio circuit 110 of the mobile wireless device 102 may include a baseband OS 214 configured to manage the hardware resources (e.g., processor, memory, different radio components, etc.) of the baseband radio circuit 110. According to some embodiments, the baseband radio circuit 110 may implement a baseband manager 216 configured to interface with the eUICC 108 to establish a secure channel with the MNO provisioning server 116 and obtain information (such as eSIM data) from the MNO provisioning server 116 for managing the eSIM 208. The baseband manager 216 may be configured to implement services 218, which represent a collection of software modules that are instantiated by various applets 212 of enabled eSIMs 208 included in the eUICC 108. For example, the services 218 may be configured to manage different connections between the mobile wireless device 102 and the MNO 114 depending on the different eSIMs 208 enabled within the eUICC 108. For a provisioning eSIM 208 that provides limited functionality limited to certain data connections when a cellular wireless connection or a non-cellular wireless connection via the user eSIM 208 is not available, the mobile wireless device 102 enables the provisioning eSIM 208, but also places the provisioning eSIM in an inactive state ready for use, but unable to establish a connection with a cellular wireless network until it is reconfigured to an active state, for example, in response to a user action or system resource requirement.

[0032] Figure 3A diagram 300 of elements of a communication network involved in device activation and SIM provisioning, installation, and activation of a mobile wireless device 102 is illustrated. Device activation and SIM provisioning may require a data connection for the mobile wireless device 102. In some scenarios, a non-cellular access network 304 may be used for the mobile wireless device 102 to connect to various device manufacturer-managed servers and / or servers managed by the MNO 114 via an intermediate communication network 306. In some scenarios, the non-cellular access network 304 may not be available, and the mobile wireless device 102 may rely on access to the cellular access network 302 to activate the mobile wireless device 102 and perform SIM provisioning on the mobile wireless device 102, e.g., downloading and installing the eSIM 208. In some embodiments, the mobile wireless device 102 includes a limited functionality SIM profile (e.g., a pre-installed limited functionality bootstrap eSIM or a pre-installed limited functionality pSIM) that can provide limited access to a cellular access network 302 for provisioning an eSIM 208, for example, when access to a non-cellular access network 304 that can interconnect to a required server is not available. The OEM manufacturer of the mobile wireless device 102 can maintain multiple network-based servers to assist in the management of the mobile wireless device 102, for example, a device manufacturer-managed device services server 308 that can provide management of device manufacturer-provided services to the mobile wireless device 102, and a device manufacturer-managed MNO services server 310 that can provide a device manufacturer anchor for managing MNO-provided services to the mobile wireless device 102. The MNO 114 may also provide their own set of servers, including various MNO infrastructure servers 312 for managing cellular access, authentication, authorization, subscription, billing and other associated management functions for cellular wireless services for the mobile wireless device 102, and MNO provisioning servers 116, through which the mobile wireless device 102 can access SIM firmware, such as eSIM 208, OTA updates of eSIM 208 or pSIM, etc., using appropriate authentication.

[0033] Figure 4AA diagram 400 of exemplary states of a provisioning eSIM 208 for a mobile wireless device 102 is illustrated. The provisioning eSIM 208 may be installed in the mobile wireless device 102 at a manufacturing facility or downloaded to the mobile wireless device 102 after manufacturing. The provisioning eSIM 208 may be installed on the eUICC 108 of the mobile wireless device 102 and may be configured in a disabled state 402. The provisioning eSIM 208 cannot be used until it is enabled. The provisioning eSIM 208 may be reconfigured from the disabled state 402 to an inactive state 404, in which the cellular wireless capabilities of the provisioning eSIM 208 may be limited to establishing a connection with a cellular wireless network, e.g., to reduce the signaling load on the cellular wireless network associated with the provisioning eSIM 208 and save battery power of the mobile wireless device 102. The inactive state 404 of the provisioning eSIM 208 may also be referred to as a signaling reduction mode / state. The inactive state may include i) a cellular airplane mode in which the baseband cellular radio transceiver is disabled (no cellular radio transmission or reception is permitted); or ii) a limited network search mode in which the baseband cellular radio receiver listens for signals from a cellular wireless network to prepare the wireless device for future cellular wireless connections, but does not use the provisioning eSIM to transmit or connect to a cellular wireless network while in the inactive state. The provisioning eSIM 208 may be enabled while in the inactive state 404, but may not establish a cellular wireless connection with a cellular wireless network associated with the provisioning eSIM 208 while in the inactive state 404. The provisioning eSIM 208 may be reconfigured from the inactive state 404 to an active state 406 in which a data connection may be established with a cellular wireless network associated with the provisioning eSIM 208. The mobile wireless device 102 may cause the provisioning eSIM 208 to enter and exit the inactive state 404 as needed, for example, in response to user actions or system resource requirements indicating a need for cellular wireless connectivity, such as to allow an Internet connection to a server managed by the device manufacturer for device activation, enable a secure connection to the MNO 114 provisioning server 116 to download the user eSIM 208, communicate the status of various eSIM provisioning operations to the device manufacturer server or the MNO server, etc. A client service of the wireless device requiring provisioning eSIM cellular wireless connectivity may indicate a requirement to use the provisioning eSIM, for example, an application executing on an application processor or a system resource may assert a requirement for the provisioning eSIM connection. The application or system resource may maintain the assertion until the cellular wireless network connectivity requirement has been completed, and then release the provisioning eSIM assertion when no longer needed. After satisfying the current network use of the provisioning eSIM, the wireless device waits for a backoff period governed by a backoff timer.The backoff period allows the existing provisioning eSIM cellular wireless network attachment to be reused for subsequent network usage when needed, and avoids switching the provisioning eSIM back and forth between the inactive state and the active state for a series of separate network usages. In some cases, such as after successfully installing and enabling a full-function user eSIM 208 that provides access to a cellular wireless network connection, the mobile wireless device 102 may also directly transition the provisioning eSIM 208 from the active state 406 to the disabled state 402.

[0034] Figure 4B A diagram 450 of an exemplary activation flow for a provisioning eSIM 208 installed on an eUICC 108 of a mobile wireless device 102 is illustrated. At 456, a communication module 452, which may be executed on a processor 104 (such as an application processor or a baseband processor) of the mobile wireless device 102, may initialize a provisioning fallback agent associated with the provisioning eSIM 208. At 458, the communication module 452 may register the provisioning fallback agent with a network management module 454, which may also be executed on the same processor 104 or another processor 104 of the mobile wireless device 102. At 460, the communication module 452 may initialize a cellular provisioning policy to indicate proper use of the provisioning eSIM 208 via the provisioning fallback agent. At 462, the communication module 452 may communicate the cellular provisioning policy to the network management module. Subsequently, at 464, the communication module 452 may determine a requirement for a network data connection, for example, based on a user input action or system resource requirements, and may communicate the network data connection request to the network management module 454. In some embodiments, the network management module 454 may be unaware of the inactive state 404 of the provisioning eSIM 208. At 466, the network management module 454 may transmit to the communication module 452 a request to initiate an internet data connection, for example, by establishing a non-cellular wireless connection or a cellular wireless connection based on the user eSIM 208. At 452, the communication module 452 may respond to the network management module 454 indicating a failure to establish the requested internet data connection, which may occur when a non-cellular wireless connection cannot be established and the user eSIM 208 is not installed and enabled on the eUICC 108 of the mobile wireless device 102. At 470, the network management module 454 may fall back to the use of the provisioning eSIM 208, for example, based on the cellular provisioning policy previously received from the communication module 452 at 462. At 472, the network management module 454 may transmit a message to the communication module 452 to establish a network connection using the provisioning eSIM 208. At 474, the communication module 452 may respond with an indication that the network connection was successfully established using the provisioning eSIM 208. At 476, the network management module 454 may communicate data via the connection established using the provisioning eSIM 208. In some embodiments, such as Figure 4B As illustrated, the provisioning eSIM 208 capabilities are available for data connections when no other data connections are available, and used as a fallback connection as needed.

[0035] Figure 5 Diagram 500 illustrates an example of a state change of a provisioning eSIM 208 triggered by a user action at a mobile wireless device 102 . Figure 5The example of illustrates a state change of the provisioning eSIM 208 triggered by a user during an initialization process of the mobile wireless device 102, which may occur when the mobile wireless device 102 is initially powered on or after a factory reset. As part of the initialization process, the mobile wireless device 102 may require a data connection to communicate with one or more network-based servers of the device manufacturer during device activation, or with one or more network-based servers of the MNO 114 to manage cellular wireless services. Initially, a user interface (UI) screen is presented to request selection of a non-cellular wireless network (e.g., a Wi-Fi network) with which to establish a data connection. The user of the mobile wireless device 102 may select an option to continue the device activation process without connecting to a Wi-Fi network, and the user may be asked to confirm the selection to continue without establishing a Wi-Fi connection. When the user of the mobile wireless device 102 is presented with and selects the option to exit the non-cellular wireless connection, the provisioning eSIM 208 of the mobile wireless device may be in an inactive state 404. Since no non-cellular wireless connection is available or established, and a network connection is required to continue the device activation process, the mobile wireless device 102 may change the state of the provisioning eSIM 208 from the inactive state 404 to the active state 406. The credentials of the provisioning eSIM 208 may be used to establish a limited functionality cellular wireless connection, and the user is presented with an option to establish cellular wireless service for the mobile wireless device 102, such as by transfer from another wireless device 102 or by scanning a quick response (QR) code provided by the MNO 114. After the full-function user eSIM 208 is downloaded, installed, and enabled on the eUICC 108 of the mobile wireless device 102, the provisioning eSIM 208 may no longer be required (because the user eSIM 208 can provide cellular wireless connectivity). The mobile wireless device 102 may change the state of the provisioning eSIM 208 from the active state 406 to the disabled state 402. In some embodiments, the mobile wireless device 102 transitions the state of the provisioning eSIM 208 from the active state 406 to the inactive state 404 before further transitioning the provisioning eSIM 208 to the disabled state 402. In some embodiments, the mobile wireless device 102 disables the provisioning eSIM 208 by directly transitioning the provisioning eSIM 208 from the active state 406 to the disabled state 402. In some embodiments, when the user eSIM 208 is not successfully downloaded, installed, or enabled on the eUICC 108 of the mobile wireless device 102, the mobile wireless device 102 transitions the provisioning eSIM 208 from the active state 406 to the inactive state 404 to allow the provisioning eSIM 208 to be subsequently used for wireless connections when needed and when no other wireless connections are available.

[0036] Fig. 6A and Figure 6BDiagrams 600, 650 of an exemplary wireless device activation flow with a change in state of a provisioning eSIM 208 of a mobile wireless device 102 without a cellular wireless service plan are illustrated. Initially, the mobile wireless device 102 is manufactured with a provisioning eSIM 208 installed on the eUICC 108 of the mobile wireless device 102 at a factory 606 or downloaded to the eUICC 108 thereafter. A user 602 purchases the mobile wireless device 102 and initiates the device activation process (e.g., after unboxing and booting the mobile wireless device 102). An application processor 604 of the mobile wireless device 102 transmits a message to the eUICC 108 identifying an available eSIM 208 on the eUICC 108. The eUICC 108 responds with an indication that the eUICC 108 is configured with only the provisioning eSIM 208 and does not have any installed or enabled user eSIM 208. The provisioning eSIM 208 may be initially installed on the eUICC 108 in a disabled state 402. The application processor 604 transmits a message to the eUICC 108 to enable the provisioning eSIM 208 on the eUICC 108. The application processor 604 then transmits a message to the eUICC 108 to place the provisioning eSIM 208 in an inactive state 404. In some embodiments, the application processor 604 transmits a single message to enable the provisioning eSIM and place the provisioning eSIM from the disabled state 402 in the inactive state 404. Subsequently, as part of a device activation process for the mobile wireless device 102, the application processor 604 detects a specific requirement for a network connection, such as connecting to a device activation server 610 managed by a device manufacturer of the mobile wireless device 102. The application processor 604 communicates with the wireless circuit 110 to establish the required network connection. The application processor 604, together with the wireless circuit 110, may determine that no network connection (e.g., a non-cellular wireless connection or a user SIM / eSIM 208 wireless connection) is available. The application processor 604 may increase the usage count of the provisioning eSIM 208 and transmit a message to the wireless circuit 110 to transition the provisioning eSIM 208 on the eUICC 108 from the inactive state 404 to the active state 406. The wireless circuit 110 may use the credentials of the provisioning eSIM 208 to attach to the access portion of the cellular wireless network and indicate to the application processor 604 when the attachment to the cellular wireless network using the provisioning eSIM 208 is successful. The mobile wireless device 102 establishes a transport layer security (TLS) tunnel to the device activation server 610 via the secure proxy server 608. Connecting via the secure proxy server 608 provides an additional level of security and privacy compared to connecting directly to the device activation server 610. The application processor 604 then requests activation of the mobile wireless device 102 via the secure TLS tunnel and subsequently receives an indication of successful device activation from the device activation server 610.The application processor 604 then closes the secure TLS tunnel with the device activation server 610 after successfully completing the device activation. The application processor 604 detects that the use of the network connection has completed and decrements the use count of the provisioning eSIM 208. When the value of the use count reaches a null value, for example, when no other request for network connection is pending, the application processor 604 starts a backoff timer to wait for a backoff period in which the provisioning eSIM 208 is in the active state 406. The backoff period allows for detection of subsequent requests for network connection and provides hysteresis to avoid switching the state of the provisioning eSIM 208 back and forth between the active state 406 and the inactive state 404 during a series of different non-overlapping requests for network connection using the provisioning eSIM 208. The application processor 604 (and the wireless circuitry 110 of the mobile wireless device 102) remains attached to the cellular wireless network associated with the provisioning eSIM during the backoff period. After the backoff timer expires, when no additional request for network connection is received, the application processor 604 transmits a message to the eUICC 108 to change the state of the provisioning eSIM 208 from the active state 406 to the inactive state 404. An indication of device activation completion may then be provided to the user 602, for example, via a user interface of the mobile wireless device 102.

[0037] Fig. 7A , Figure 7B , Figure 7C , Fig.7D and Fig. 7EDiagrams 700, 720, 740, 760, and 780, respectively, illustrate examples of activating a mobile wireless device 102, including adding a cellular wireless service plan to the mobile wireless device 102, accompanied by a change of state of the provisioning eSIM 208 during device activation utilizing a cellular plan provisioning process. Initially, the mobile wireless device 102 is manufactured with the provisioning eSIM 208 installed on the eUICC 108 of the mobile wireless device 102 at the factory 606 or downloaded thereafter to the eUICC 108. The user 602 purchases the mobile wireless device 102 and subscribes to a cellular wireless service plan, which requires provisioning by one or more network-based servers (e.g., infrastructure server 704 and SM-DP+ server 706, the latter being the provisioning server 116) of the MNO 114 associated with the cellular wireless service plan. The infrastructure server 704 initiates the establishment of an eSIM profile 208 associated with the cellular wireless service plan subscribed by the user 602 on the SM-DP+ server 706 for subsequent download to the eUICC 108 of the mobile wireless device 102. The eSIM profile 208 may also be referred to as a user eSIM 208, and provides access to the cellular wireless services of the MNO 114. The infrastructure server 704 provides detailed information about the eSIM profile 208 to a device discovery server 702 managed by the device manufacturer of the mobile wireless device 102. Subsequently, for example, after unboxing and booting the mobile wireless device 102, the user 602 initiates a device activation process for the mobile wireless device 102.

[0038] The application processor 604 of the mobile wireless device 102 transmits a message to the eUICC 108 that determines the available eSIMs 208 on the eUICC 108. The eUICC 108 responds with an indication that the eUICC 108 is configured with only the provisioning eSIM 208 without any installed or enabled user eSIMs 208. The provisioning eSIM 208 may initially be installed on the eUICC 108 in a disabled state 402. The application processor 604 transmits a message to the eUICC 108 that enables the provisioning eSIM 208 on the eUICC 108. Then, the application processor 604 transmits a message to the eUICC 108 that places the provisioning eSIM 208 in an inactive state 404. In some embodiments, the application processor 604 transmits a single message that enables the provisioning eSIM and places the provisioning eSIM from the disabled state 402 in the inactive state 404. Subsequently, as part of the device activation process of the mobile wireless device 102, the application processor 604 detects a specific requirement for a network connection, for example, to connect to a device activation server 610 managed by the device manufacturer of the mobile wireless device 102. The application processor 604 communicates with the wireless circuit 110 to establish the required network connection. The application processor 604, together with the wireless circuit 110, can determine that no network connection (e.g., a non-cellular wireless connection or a user SIM / eSIM 208 wireless connection) is available. The application processor 604 can increase the usage count of the provisioning eSIM 208 and transmit a message to the wireless circuit 110 to transition the provisioning eSIM 208 on the eUICC 108 from the inactive state 404 to the active state 406. The wireless circuit 110 can use the credentials of the provisioning eSIM 208 to attach to the access portion of the cellular wireless network and indicate to the application processor 604 when the attachment to the cellular wireless network using the provisioning eSIM 208 is successful. The mobile wireless device 102 establishes a transport layer security (TLS) tunnel to the device activation server 610 via the secure proxy server 608. Connecting via the secure proxy server 608 provides an additional level of security and privacy compared to connecting directly to the device activation server 610. The application processor 604 then requests activation of the mobile wireless device 102 via the secure TLS tunnel, and subsequently receives an indication of successful device activation from the device activation server 610. The application processor 604 then closes the secure TLS tunnel with the device activation server 610 after successfully completing the device activation. The application processor 604 detects that the use of the network connection has been completed and decrements the use count of the provisioning eSIM 208. When the value of the use count reaches a null value, for example, when no other request for network connection is pending, the application processor 604 starts a backoff timer to wait for a backoff period of time, in which the provisioning eSIM 208 is in the active state 406.The backoff period allows for detection of subsequent requirements for network connectivity and provides hysteresis to avoid switching the state of the provisioning eSIM 208 back and forth between the active state 406 and the inactive state 404 during a series of different, non-overlapping requirements for network connectivity using the provisioning eSIM 208. The application processor 604 (and the wireless circuitry 110 of the mobile wireless device 102) remains attached to the cellular wireless network associated with the provisioning eSIM during the backoff period.

[0039] The application processor 604 initiates installation of a cellular wireless service plan prior to the expiration of the back-off timer, resulting in a new requirement for network connectivity by the mobile wireless device 102. As part of the cellular wireless service plan installation process, the application processor 604 detects a specific requirement for network connectivity, e.g., connects to the device discovery server 702 to determine an available eSIM profile 208 for the mobile wireless device 102. The application processor 604 communicates with the wireless circuit 110 to establish the required network connectivity. The application processor 604, together with the wireless circuit 110, may determine that no network connectivity (e.g., a non-cellular wireless connection or a user SIM / eSIM 208 wireless connection) is available. The application processor 604 may reset the back-off timer and increment the usage count of the provisioning eSIM 208. When the back-off timer is running but has not expired prior to being reset due to detection of an additional requirement for network connectivity, the application processor 604 does not need to change the state of the provisioning eSIM 208, which remains in the active state 406, wherein the cellular wireless network is attached via the provisioning eSIM 208. The mobile wireless device 102 establishes a transport layer security (TLS) tunnel to the device discovery server 702 via the secure proxy server 608. Connecting via the secure proxy server 608 provides an additional level of security and privacy compared to connecting directly to the device discovery server 702. The application processor 604 queries the device discovery server 702 via the secure TLS tunnel for available eSIM profiles 208 specified for the mobile wireless device 102, and in response receives information about the available eSIM profiles 208 from the device discovery server 702. The information may include a network address, such as a uniform resource locator (URL) or a fully qualified domain name (FQDN), of the SM-DP+ server 706 from which the eSIM profile 208 of the mobile wireless device 102 is obtained. The application processor 604 then closes the secure TLS tunnel with the device discovery server 702 after receiving the eSIM profile 208 information. The application processor 604 detects that the use of the network connection has been completed and decrements the usage count of the provisioning eSIM 208. If the value of the usage count has reached a null value, e.g., when no other requests for network connectivity are pending, the application processor 604 starts a backoff timer to wait for a backoff period in which the provisioning eSIM 208 is in the active state 406. The application processor 604 (and the wireless circuitry 110 of the mobile wireless device 102) remains attached to the cellular wireless network associated with the provisioning eSIM during the backoff period.

[0040] The application processor 604 detects a requirement for a new network connection, such as by obtaining an eSIM profile 208 from the SM-DP+ server 706 to continue the cellular service plan installation. The application processor 604 communicates with the wireless circuit 110 to establish the required network connection. The application processor 604, together with the wireless circuit 110, can determine that no network connection (e.g., a non-cellular wireless connection or a user SIM / eSIM 208 wireless connection) is available. The application processor 604 resets the back-off timer and increases the usage count of the provisioning eSIM 208. When the back-off timer is running but has not expired before being reset due to the detection of an additional requirement for a network connection, the application processor 604 does not need to change the state of the provisioning eSIM 208, which remains in the active state 406, wherein the cellular wireless network is attached via the provisioning eSIM 208. The mobile wireless device 102 establishes a transport layer security (TLS) tunnel to the SM-DP+ server 706 via the secure proxy server 608. Connecting via the secure proxy server 608 provides an additional level of security and privacy compared to connecting directly to the SM-DP+ server 706. The mobile wireless device 102 downloads one or more eSIM profiles 208 from the SM-DP+ server 706 to the eUICC 108 via the application processor 604 using a secure TLS tunnel. The application processor 604 transmits a notification message to the SM-DP+ server 706 via the secure TLS tunnel, indicating the successful download and installation of the eSIM profile 208 on the eUICC 108 of the mobile wireless device 102. The application processor 604 then closes the secure TLS tunnel with the SM-DP+ server 706 after transmitting the successful eSIM installation notification message to the SM-DP+ server 706. The application processor 604 detects that the use of the network connection has been completed and decrements the use count of the provisioning eSIM 208. If the value of the use count has reached a null value, for example, when no other requirements for network connection are pending, the application processor 604 starts a backoff timer to wait for a backoff period of time, in which the provisioning eSIM 208 is in the active state 406. The application processor 604 (and the wireless circuitry 110 of the mobile wireless device 102 ) remains attached to the cellular wireless network associated with the provisioning eSIM during the backoff period.

[0041] The application processor 604 detects a requirement for a new network connection, such as completing a cellular service plan installation by confirming a successful eSIM installation to the device discovery server 702. The application processor 604 communicates with the wireless circuit 110 to establish the required network connection. The application processor 604, together with the wireless circuit 110, can determine that no network connection (e.g., a non-cellular wireless connection or a user SIM / eSIM 208 wireless connection) is available. The application processor 604 resets the back-off timer and increases the usage count of the provisioning eSIM 208. When the back-off timer is running but has not expired before being reset due to detecting an additional requirement for a network connection, the application processor 604 does not need to change the state of the provisioning eSIM 208, which remains in the active state 406, wherein the cellular wireless network is attached via the provisioning eSIM 208. The mobile wireless device 102 establishes a transport layer security (TLS) tunnel to the device discovery server 702 via the secure proxy server 608. The application processor 604 transmits a notification message to the device discovery server 702 via the secure TLS tunnel, the notification message indicating successful download and installation of the eSIM profile 208 on the eUICC 108 of the mobile wireless device 102. The application processor 604 then closes the secure TLS tunnel with the device discovery server 702 after transmitting the successful eSIM installation notification message to the device discovery server 702. The application processor 604 detects that the use of the network connection has completed and decrements the use count of the provisioning eSIM 208. If the value of the use count has reached a null value, for example, when no other requirements for network connectivity are pending, the application processor 604 starts a backoff timer to wait for a backoff period in which the provisioning eSIM 208 is in the active state 406. The application processor 604 (and the wireless circuitry 110 of the mobile wireless device 102) remains attached to the cellular wireless network associated with the provisioning eSIM during the backoff period.

[0042] After one or more fully functional user eSIM profiles 208 are successfully installed on the mobile wireless device 102, the provisioning eSIM profiles 208 may no longer be needed because at least one of the user eSIM profiles 208 should be able to be used to establish a cellular wireless network connection. The application processor 604 transmits a message to the eUICC 108 to disable the provisioning eSIM 208, thereby changing the state of the provisioning eSIM 208 from the active state 406 to the disabled state 402. The application processor 604 also resets a back-off timer that is no longer needed to monitor for a network connection that requires the use of the provisioning eSIM 208. The provisioning eSIM 208 may remain on the eUICC 108 of the mobile wireless device 102 to be reused in the future when needed (e.g., after a factory reset of the mobile wireless device 102 or when a non-cellular wireless connection and a cellular wireless connection using the user eSIM profile 208 are not available or cannot be established). The provisioning eSIM profile 208 may be used to download and install another user eSIM profile 208 or communicate with one or more network-based servers of the MNO 114 or device manufacturer. However, the provisioning eSIM 208 may be limited to a limited set of basic services and may not be used for voice connections or unrestricted data connections.

[0043] Figure 8Diagram 800 illustrates an example of a state change of a provisioning eSIM 208 that allows a mobile wireless device 102 to establish an emergency services connection. In some embodiments, the mobile wireless device 102 does not include an available (installed and enabled) user SIM or eSIM 208 for emergency services connections. In some embodiments, the mobile wireless device 102 does not include a user SIM or eSIM 208 installed therein. The provisioning eSIM 208 is installed on the eUICC 108 of the mobile wireless device 102 and may initially be in an inactive state 404 or an active state 406. The provisioning eSIM profile 208 may be limited to limited function data connections only and cannot be used by the mobile wireless device 102 for voice connections. The user 602 may access the emergency services mode of the mobile wireless device 102, for example, by selecting an emergency services icon via a user interface display or performing an action indicating a requirement to access the emergency services mode. The application processor 604 may provide the set of current device / country bundles to the wireless circuitry 110 and / or eUICC 108 of the mobile wireless device 102. The wireless circuit 110 and / or the eUICC 108 of the mobile wireless device 102 may return a set of currently applicable emergency call numbers that can be used at the current location of the mobile wireless device 102. The application processor 604 may detect that an emergency service connection is needed, for example, to connect to a police station, fire department, hospital, emergency dispatch center, etc. Since the provisioning eSIM 208 is currently in the inactive state 404 or the active state 406 and cannot be used to provide the requested emergency service connection, the application processor 604 transmits a message to the wireless circuit 110 and / or the eUICC 108 of the mobile wireless device 102 to disable the provisioning eSIM 208, thereby changing the state of the provisioning eSIM 208 from the inactive state or the active state 406 to the disabled state 402. Any running back-off timer may also be reset. The application processor 604 may then transmit a request to the wireless circuit 110 to attach to a cellular wireless network and initiate an emergency service connection via the cellular wireless network. The wireless circuit 110 may establish an emergency services connection with the cellular wireless network without using the credentials of the provisioning eSIM 208 or any other SIM or eSIM 208 of the mobile wireless device 102. The wireless circuit 110 may acknowledge to the application processor 604 when the emergency services connection is successfully established. Subsequently, the emergency services connection may no longer be needed, and the application processor 604 transmits a message to the wireless circuit 110 to terminate (complete) the emergency services connection with the cellular wireless network. The application processor 604 may detect the successful completion of the emergency services connection, and may transmit a message to the wireless circuit 110 and the eUICC 108 to re-enable the provisioning eSIM 208 and then transition the state of the provisioning eSIM 208 from the disabled state 402 to the inactive state 404.To allow establishment of an emergency services connection to a cellular wireless network, the provisioning eSIM 208 is disabled, and when the emergency services connection to the cellular wireless network is no longer required, the provisioning eSIM 208 is re-enabled and placed in an inactive state 404 to allow credentials to be prepared for use with the provisioning eSIM 208 to attach and connect to a cellular wireless network later when needed.

[0044] Fig. 9 A flow chart 900 of an exemplary method for dynamically managing a provisioning eSIM 208 installed on an eUICC 108 of a wireless device 102 is illustrated. At 902, the wireless device 102 determines that a user eSIM 208 is not installed on the eUICC 108 of the wireless device 102. At 904, the wireless device 102 reconfigures the provisioning eSIM 208 from a disabled state 402 to an inactive state 404. At 906, the wireless device 102 detects that the wireless device 102 requires a network connection. At 908, the wireless device 102 reconfigures the provisioning eSIM 208 from the inactive state 404 to an active state 406. At 910, the wireless device 102 attaches to a cellular wireless network using the credentials of the provisioning eSIM 208. At 912, the wireless device 102 establishes the required network connection via the cellular wireless network. At 914, the wireless device 102 detects that the use of the network connection is complete. At 916, the wireless device 102 reconfigures the provisioning eSIM 208 from the active state 406 to the inactive state 404 after the backoff timer expires. The provisioning eSIM 208 is enabled while in the inactive state 404 and is restricted from attaching the wireless device 102 to a cellular wireless network.

[0045] In some embodiments, the method further includes: the wireless device 102 determines that no non-cellular wireless connection is available for the desired network connection before reconfiguring the provisioning eSIM 208 from the inactive state 404 to the active state 406. In some embodiments, the method further includes the wireless device 102: i) increasing a usage count of the provisioning eSIM 208 before reconfiguring the provisioning eSIM 208 to the active state 406, and ii) decreasing the usage count of the provisioning eSIM 208 after detecting that the use of the network connection is complete. In some embodiments, the method further includes: the wireless device 102 starting a back-off timer in response to the usage count being equal to a null value. In some embodiments, the method further includes: the wireless device 102 maintaining attachment to the cellular wireless network via the credentials of the provisioning eSIM 208 after starting and until the back-off timer expires. In some embodiments, the wireless device 102 determines that there is no user eSIM 208 installed on the eUICC 108 by at least: i) querying the eUICC 108 for available user eSIMs 208, and ii) receiving an indication from the eUICC 108 indicating that the provisioning eSIM 208 is the only eSIM 208 installed on the eUICC 108. In some embodiments, the network connection includes a transport layer security (TLS) tunnel connection via a secure proxy server. In some embodiments, the wireless device detects completion of use of the network connection by at least detecting closing of the TLS tunnel connection.

[0046] In some embodiments, the wireless device 102 requires a network connection for device activation, and the method further includes the wireless device 102: i) requesting activation of the wireless device 102 via a TLS tunnel connection to a device activation server 610 managed by a device manufacturer of the wireless device 102, and ii) receiving an indication of successful device activation from the device activation server 610 via the TLS tunnel connection. In some embodiments, the wireless device 102 requires a network connection to determine an available user eSIM 208, and the method further includes the wireless device 102: i) checking for an available user eSIM 208 via a TLS tunnel connection to a device discovery server 702 managed by a device manufacturer of the wireless device 102, and ii) receiving an indication of an available user eSIM 208 from the device discovery server 702 via the TLS tunnel connection. In some embodiments, the wireless device 102 requires a network connection to download the user eSIM 208, and the method further includes the wireless device 102: i) downloading the user eSIM 208 from a provisioning server 116 managed by a mobile network operator (MNO) 114 associated with the user eSIM 208 via a TLS tunnel connection, and ii) providing an indication of a successful user eSIM 208 installation to the provisioning server 116 via the TLS tunnel connection. In some embodiments, the method further includes the wireless device: i) disabling the provisioning eSIM 208 after successfully installing the user eSIM 208, and ii) enabling the user eSIM 208 on the eUICC 108 of the wireless device 102, wherein the provisioning eSIM 208 provides limited cellular wireless network connectivity limited to certain endpoints, and the user eSIM 208 provides full cellular wireless network connectivity to access services of the MNO 114 based on a cellular wireless subscription associated with the user eSIM 208.

[0047] Fig.10A flow chart 1000 is illustrated of an exemplary method for dynamically managing a provisioning eSIM 208 installed on an eUICC 108 of a wireless device 102 to allow the wireless device 102 to make an emergency services connection. At 1002, the wireless device 102 detects a user input accessing an emergency services mode of the wireless device 102. At 1004, the wireless device 102 obtains one or more emergency services phone numbers from the eUICC. At 1006, the wireless device 102 detects that the wireless device 102 requires an emergency services connection. At 1008, the wireless device 102 disables the provisioning eSIM 208 installed on the eUICC 108 of the wireless device 102. At 1010, the wireless device 102 establishes an emergency services connection without using the provisioning eSIM 208 or any user SIM or user eSIM 208 installed in the wireless device 102. At 1012, the wireless device 102 enables the provisioning eSIM 208 and configures the provisioning eSIM to an inactive state after detecting completion of the emergency services connection. In some embodiments, the wireless device 102 is configured without any enabled user SIM or user eSIM 208. In some embodiments, the provisioning eSIM 208 is enabled when in an inactive state and is restricted for use in attaching the wireless device 102 to a cellular wireless network.

[0048] Representative equipment

[0049] Fig.11 1 illustrates a detailed view of a representative computing device 1100 that can be used to implement the various methods described herein according to some embodiments. In particular, the detailed view illustrates various components that can be included in the mobile wireless device 102. Fig.11As shown, the computing device 1100 may include a processor 1102, which represents a microprocessor or controller for controlling the overall operation of the computing device 1100. The computing device 1100 may also include a user input device 1108 that allows a user of the computing device 1100 to interact with the computing device 1100. For example, the user input device 1108 may take a variety of forms, such as buttons, keypads, dials, touch screens, audio input interfaces, visual / image capture input interfaces, input in the form of sensor data, etc. Further, the computing device 1100 may include a display 1110 that can be controlled by the processor 1102 to display information to the user. The data bus 1116 can facilitate data transfer between at least the storage device 1140, the processor 1102, and the controller 1113. The controller 1113 can be used to interface with and control different devices through the device control bus 1114. The computing device 1100 may also include a network / bus interface 1111 that can be communicatively coupled to the data link 1112. In the case of a wireless connection, the network / bus interface 1111 may include a wireless transceiver.

[0050] The computing device 1100 also includes a storage device 1140 (which may include a single disk or multiple disks, such as a hard drive), and includes a storage management module that manages one or more partitions within the storage device 1140. In some embodiments, the storage device 1140 may include flash memory, semiconductor (solid-state) memory, etc. The computing device 1100 may also include a random access memory (RAM) 1120 and a read-only memory (ROM) 1122. The ROM 1122 may store programs, utilities, or processes to be executed in a non-volatile manner. The RAM 1120 may provide volatile data storage and store instructions related to the operation of the computing device 1100. The computing device 1100 may also include a secure element (SE) 1124, which may represent a secure storage for the mobile wireless device 102 to access a cellular wireless system, such as an eUICC 108 on which one or more eSIMs 208 are stored and / or a UICC 118 on which a pSIM profile is stored.

[0051] Wireless Terminology

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

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

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

[0055] The various aspects, embodiments, specific implementations or features of the described embodiments may be used individually or in any combination. Various aspects of the described embodiments may be implemented by software, hardware, or a combination of hardware and software. The described embodiments may also be implemented as computer-readable code on a non-transient computer-readable medium. A non-transient computer-readable medium is any data storage device that can store data, which can then be read by a computer system. Examples of non-transient computer-readable media include read-only memory, random access memory, CD-ROM, HDD, DVD, magnetic tape, and optical data storage devices. Non-transient computer-readable media may also be distributed on network-coupled computer systems so that the computer-readable code is stored and executed in a distributed manner.

[0056] In connection with this disclosure, it is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

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

Claims

1. A method for dynamically managing a provisioned electronic subscriber identity module (eSIM) installed on an embedded universal integrated circuit card (eUICC) of a wireless device, the method comprising: By the wireless device: Determining that no user eSIM is installed on the eUICC; reconfiguring the provisioned eSIM from a disabled state to an inactive state; detecting that the wireless device requires a network connection; reconfiguring the provisioning eSIM from the inactive state to an active state; attaching the wireless device to a cellular wireless network using the credentials of the provisioned eSIM; establishing the network connection via the cellular wireless network; detecting completion of use of the network connection; as well as reconfiguring the provisioning eSIM from the active state to the inactive state after expiration of a backoff timer, Wherein the provisioning eSIM is enabled and restricted for use in attaching the wireless device to the cellular wireless network when in the inactive state.

2. The method according to claim 1, further comprising: By the wireless device: No non-cellular wireless connection is available prior to reconfiguring the provisioning eSIM from the inactive state to the active state.

3. The method according to claim 1, further comprising: By the wireless device: Prior to reconfiguring the provisioned eSIM to the active state, incrementing a usage count of the provisioned eSIM; as well as After detecting completion of the use of the network connection, the usage count of the provisioned eSIM is decremented.

4. The method according to claim 1, further comprising: By the wireless device: The backoff timer is started in response to the use count being equal to a null value.

5. The method according to claim 3, further comprising: By the wireless device: After activation and until expiration of the back-off timer, attachment to the cellular wireless network is maintained via the credentials of the provisioning eSIM.

6. The method of claim 1 , wherein determining that a user eSIM is not installed on the eUICC comprises: Query the eUICC for available user eSIMs; as well as An indication is received from the eUICC indicating that the provisioning eSIM is the only eSIM installed on the eUICC.

7. The method according to claim 1, wherein: The network connection includes a Transport Layer Security (TLS) tunnel connection via a secure proxy server.

8. The method of claim 7, wherein detecting completion of use of the network connection comprises: The closing of the TLS tunnel connection was detected.

9. The method according to claim 7, wherein: The wireless device requires the network connection for device activation; and The method also includes the wireless device performing the following operations: requesting activation of the wireless device via the TLS tunnel connection to a device activation server managed by a device manufacturer of the wireless device; as well as An indication of successful device activation is received from the device activation server via the TLS tunnel connection.

10. The method according to claim 7, wherein: The wireless device requires the network connection to determine an available user eSIM; and The method also includes the wireless device performing the following operations: checking for an available user eSIM via the TLS tunnel connection to a device discovery server managed by a device manufacturer of the wireless device; as well as An indication of the available user eSIM is received from the device discovery server via the TLS tunnel connection.

11. The method according to claim 7, wherein: The wireless device requires the network connection to download the user's eSIM; and The method also includes the wireless device performing the following operations: downloading the user eSIM from a provisioning server managed by a mobile network operator (MNO) associated with the user eSIM via the TLS tunnel connection; and An indication of a successful user eSIM installation is provided to the provisioning server via the TLS tunnel connection.

12. The method according to claim 11, further comprising: By the wireless device: disabling the provisioning eSIM after successfully installing the user eSIM; as well as enabling the user eSIM on the eUICC of the wireless device, in: The provisioning eSIM provides limited cellular wireless network connectivity limited to certain endpoints; and The user eSIM provides a full cellular wireless network connection to access services of the MNO based on a cellular wireless subscription associated with the user eSIM.

13. A wireless device, comprising: wireless circuitry including one or more antennas and an embedded universal integrated circuit card (eUICC); and one or more processors communicatively coupled to the wireless circuitry and to a memory storing instructions that, when executed by the one or more processors, configure the wireless device to: determining that a user electronic subscriber identity module (eSIM) is not installed on the eUICC; reconfiguring the provisioning eSIM on the eUICC from a disabled state to an inactive state; detecting that the wireless device requires a network connection; reconfiguring the provisioning eSIM from the inactive state to an active state; attaching the wireless device to a cellular wireless network using the credentials of the provisioned eSIM; establishing the network connection via the cellular wireless network; detecting completion of use of the network connection; as well as reconfiguring the provisioning eSIM from the active state to the inactive state after expiration of a backoff timer, Wherein the provisioning eSIM is enabled and restricted for use in attaching the wireless device to the cellular wireless network when in the inactive state.

14. The wireless device of claim 13, wherein the wireless device determining that a user eSIM is not installed on the eUICC comprises: Query the eUICC for available user eSIMs; as well as An indication is received from the eUICC indicating that the provisioning eSIM is the only eSIM installed on the eUICC.

15. The wireless device of claim 13, wherein: The network connection includes a Transport Layer Security (TLS) tunnel connection via a secure proxy server.

16. The wireless device of claim 15, wherein: The wireless device requires the network connection for device activation; and The wireless device is further configured to: requesting activation of the wireless device via the TLS tunnel connection to a device activation server managed by a device manufacturer of the wireless device; and An indication of successful device activation is received from the device activation server via the TLS tunnel connection.

17. The wireless device of claim 15, wherein: The wireless device requires the network connection to determine an available user eSIM; and The wireless device is further configured to: checking for an available user eSIM via the TLS tunnel connection to a device discovery server managed by a device manufacturer of the wireless device; and An indication of the available user eSIM is received from the device discovery server via the TLS tunnel connection.

18. The wireless device of claim 15, wherein: The wireless device requires the network connection to download the user's eSIM; and The wireless device is further configured to: downloading the user eSIM from a provisioning server managed by a mobile network operator (MNO) associated with the user eSIM via the TLS tunnel connection; and An indication of a successful user eSIM installation is provided to the provisioning server via the TLS tunnel connection.

19. The wireless device of claim 18, wherein the wireless device is further configured to: disabling the provisioning eSIM after successful installation of the user eSIM; and enabling the user eSIM on the eUICC of the wireless device, in: The provisioning eSIM provides limited cellular wireless network connectivity limited to certain endpoints; and The user eSIM provides a full cellular wireless network connection to access services of the MNO based on a cellular wireless subscription associated with the user eSIM.

20. A method for dynamically managing a provisioned electronic subscriber identity module (eSIM) installed on an embedded universal integrated circuit card (eUICC) of a wireless device, the method comprising: By the wireless device: detecting user input for accessing an emergency services mode of the wireless device; obtaining one or more emergency service telephone numbers from the eUICC; detecting that the wireless device requires an emergency services connection; disabling the provisioning eSIM installed on the eUICC of the wireless device; establishing the emergency services connection without using the provisioning eSIM or any user SIM or user eSIM installed in the wireless device; as well as After detecting completion of the emergency services connection, enabling the provisioning eSIM and configuring the provisioning eSIM to an inactive state, in: The wireless device is configured without any enabled user SIM or user eSIM; and The provisioning eSIM is enabled and restricted from use in attaching the wireless device to a cellular wireless network when in the inactive state.

Images