PUSH NOTIFICATION MANAGEMENT FOR A RESERVE eSIM CONNECTION

Abstract

This application describes a technique for managing push notifications for a backup electronic subscriber identity (eSIM) connection in a wireless device. The backup eSIM is installed in the wireless device to provide limited connectivity options for basic services, such as device startup, user eSIM deployment, user eSIM transfer, and user subscription account management. When the backup eSIM is active, push notifications for a limited set of push notification topics are allowed to be delivered to the wireless device via the backup eSIM connection.

Description

Technical Field

[0001] The embodiments described herein illustrate techniques for managing push notifications for a backup electronic subscriber identity module (eSIM) connection in a wireless device. The backup eSIM is installed in the wireless device to provide limited connectivity options for basic services, such as device startup, user eSIM deployment, user eSIM transfer, and user subscription account management. When the backup eSIM is active, push notifications for a limited set of push notification topics are allowed to be delivered to the wireless device via the backup eSIM connection. Prior Technology

[0002] Next-generation (5G) cellular wireless networks implementing one or more 3rd Generation Partnership Project (3GPP) standards have been rapidly developed and deployed by mobile network operators (MNOs) worldwide. Furthermore, the 6th generation (6G) standard is under active development. Newer cellular wireless networks offer a range of packet-based services, with 5G (and 6G) ​​technologies providing increased data throughput and reduced connection latency, potentially providing enhanced mobile broadband services for 5G (and 6G) ​​wireless devices. Access to cellular services provided by MNOs may require the use of cellular credentials and / or security processing provided by secure elements (SEs) such as universal integrated circuit cards (UICCs), embedded UICCs (eUICCs), or integrated UICCs (iUICCs) included in the wireless device.

[0003] Generally, wireless devices are configured to use a removable UICC, which includes at least a microprocessor and read-only memory (ROM). The ROM is configured to store an MNO profile (also known as a Subscriber Identity Module (SIM) or SIM profile). The wireless device can use this profile to register with and interact with the MNO to obtain wireless services via a cellular wireless network. The SIM profile contains user information, such as digital identity and one or more encryption keys, to allow the wireless device to communicate with the cellular wireless network. Typically, the UICC takes the form of a small, removable card, commonly referred to as a SIM card or physical SIM (pSIM) card, which can be inserted into the UICC receiver slot of a mobile wireless device. In recent implementations, the UICC is directly embedded into the system board of the wireless device as an eUICC, or integrated as an iUICC with other system components, offering advantages over traditional removable UICCs. The eUICC and / or iUICC may include rewritable memory to facilitate the installation, modification, and / or removal of one or more electronic SIMs (eSIMs) on the eUICC / iUICC, wherein the eSIMs can provide new and / or different services and / or updates for accessing extended functionality provided by the MNO. The eUICC / iUICC can store several MNO profiles (also referred to herein as eSIMs) and can eliminate the need for a UICC receiver slot in the wireless device. The use of multiple SIMs and / or eSIMs is expected to provide flexibility in accessing a variety of services across multiple wireless networks.

[0004] Wireless devices may include a backup eSIM (also known as a boot eSIM, backup eSIM, or deployed eSIM) installed at manufacturing or dynamically provided thereafter. A backup eSIM offers limited connectivity options, allowing the wireless device to connect to a cellular wireless network for basic services, such as upon initial device startup or during device configuration after a factory reset. Other conditions, such as eSIM deployment, eSIM delivery, and user cellular service account management, can benefit from the availability of a backup eSIM. Currently, push notifications are not permitted via backup eSIM connections to prevent applications from using backup eSIM connections for data transmission. Restricting the use of push notifications via backup eSIM connections could interfere with or complicate applications intended to use backup eSIMs. A mechanism is needed to manage the availability of selectable push notification messages via backup eSIM connections. Summary of the Invention

[0005] This application describes a technique for managing push notifications for a backup electronic subscriber identity (eSIM) connection in a wireless device. The backup eSIM is installed in the wireless device to provide limited connectivity options for basic services, such as device startup, user eSIM deployment, user eSIM transfer, and user subscription account management. When the backup eSIM is active, push notifications for a limited set of push notification topics are allowed to be delivered to the wireless device via the backup eSIM connection.

[0006] Wireless devices may include backup eSIMs (also known as boot eSIMs, backup eSIMs, or deployed eSIMs) installed during manufacturing or dynamically provided thereafter. Backup eSIMs offer limited connectivity options to allow wireless devices to connect to cellular wireless networks for a limited set of services, such as: connecting to an original equipment manufacturer (OEM) (e.g., the device manufacturer, a server used for device boot); connecting to a mobile network operator (MNO) server to deploy, download, and install a full-featured user eSIM, or to assist in delivering cellular wireless services for the user eSIM; connecting to an MNO server to manage cellular wireless subscription accounts; or similar. Backup eSIMs may be in an inactive state, which restricts the wireless device from establishing a connection to a cellular wireless network via the backup eSIM until it is booted. Wireless device monitoring indicators can ensure the use of one or more of the conditions for the backup eSIM. Example conditions may include when a user eSIM is installed but not yet activated, when cellular connectivity is unavailable via the installed user eSIM, when cellular connectivity via the user eSIM is only available via roaming, when internet connectivity is unavailable via a non-mobile network, or similar situations. When a wireless device requires a wireless connection and cannot use other wireless or wired connections, the wireless device will reactivate the backup eSIM from an inactive state to an active state. The wireless device establishes a connection to the cellular wireless network via the backup eSIM and initiates a new cellular wireless network operational phase with the device manufacturer's push notification server via the backup eSIM connection, or continues using the previous cellular wireless network operational phase. The wireless device registers with the push notification server to receive push notifications for one or more push notification topics via the backup eSIM connection. The push notification server registers with the application server corresponding to the push notification topic for the wireless device to receive applicable push notification messages via the backup eSIM connection. The push notification server can filter push notifications to ensure that only push notification messages authorized for use via the backup eSIM connection are sent to the wireless device via the backup eSIM connection. The wireless device can implement a time-limiting procedure to manage the time periods during which the backup eSIM connection is active, outside of which the backup eSIM may be inactive.

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

[0008] The content of this invention is provided only for the purpose of summarizing some exemplary embodiments to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be understood that the features described above are merely examples and should not be construed as limiting the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following description of the embodiments, drawings, and claims. Simple Explanation of the Diagram

[0009] This disclosure is more readily understood through the embodiments described in conjunction with the accompanying drawings, wherein similar element symbols refer to similar structural components. [Figure 1] A block diagram illustrating different components of an exemplary system configured to implement the various techniques described herein, according to some embodiments. [Figure 2] is a block diagram illustrating more detailed views of exemplary components of the system of Figure 1 according to some embodiments. [Figure 3] illustrates the startup and network deployment of an exemplary device for a wireless device according to some embodiments. [Figure 4A] illustrates an exemplary state diagram of a standby eSIM according to some embodiments. [Figure 4B] illustrates an exemplary startup process using a standby eSIM according to some embodiments. [Figure 5A] and [Figure 5B] illustrate examples of push notification management via a backup eSIM connection for a wireless device according to some embodiments. [Figure 6] illustrates an exemplary method for managing push notifications via a backup eSIM connection by a wireless device, according to some embodiments. [Figure 7] illustrates an exemplary method for managing push notifications via a backup eSIM connection by a push notification server, according to some embodiments. [Figure 8] A block diagram illustrating exemplary elements of a wireless device according to some embodiments. Implementation

[0010] This section describes representative applications of the methods and apparatus according to this application. 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 can be practiced without some or all of these specific details. In other instances, well-known procedural steps have not been described in detail to avoid unnecessarily obscuring the described embodiments. Other applications are possible, such that the following examples should not be considered limiting.

[0011] In the following embodiments, reference is made to the accompanying drawings, which form part of this specification and illustrate specific embodiments according to the described embodiments by way of illustration. While these embodiments are sufficiently detailed to enable those skilled in the art to practice them, it should be understood that these examples are not limiting; that other embodiments may be used and that variations may be made without departing from the spirit and scope of the described embodiments.

[0012] This application describes a technique for managing push notifications for a backup electronic subscriber identity (eSIM) connection in a wireless device. The backup eSIM is installed in the wireless device to provide limited connectivity options for basic services, such as device startup, user eSIM deployment, user eSIM transfer, and user subscription account management. When the backup eSIM is active, push notifications for a limited set of push notification topics are allowed to be delivered to the wireless device via the backup eSIM connection.

[0013] Wireless devices include backup eSIMs (also known as boot eSIMs, backup eSIMs, or deployed eSIMs) installed during manufacturing or dynamically provided thereafter. Backup eSIMs provide limited connectivity options to allow wireless devices to connect to a cellular wireless network for a limited set of services, such as: i) connecting to an original equipment manufacturer (OEM) (e.g., device manufacturer, server for device boot); ii) connecting to a mobile network operator (MNO) server to deploy, download, and install a full-featured user eSIM, or to assist in delivering cellular wireless services for the user eSIM; iii) connecting to an MNO server to manage cellular wireless subscription accounts; or similar. Backup eSIMs can be in an inactive state, which allows wireless devices to reside on a cellular wireless network with limited communication, but restricts the wireless device from establishing a connection to the cellular wireless network via the backup eSIM until it is booted. Wireless device monitoring indicators can ensure the use of one or more of the backup eSIM's conditions. Example conditions may include when a user eSIM is installed but not yet activated, when cellular connectivity is unavailable via the installed user eSIM, when cellular connectivity via the user eSIM is only available via a roaming network, when internet connectivity is unavailable via a non-mobile network, or similar situations. When a wireless device requires a wireless connection and cannot use other wireless or wired connections, the wireless device will reactivate the backup eSIM from an inactive state to an active state. In some cases, the wireless device may indicate to one or more authorized applications or system resources that the backup eSIM connection is available (or may become available). Activation and use of the backup eSIM connection may occur in the background and may not be directly visible to the user of the wireless device.

[0014] The use of backup eSIM connections is limited due to potential costs associated with their use, such as cellular wireless service fees accrued by device manufacturers providing backup eSIMs on wireless devices. Current practice completely prohibits push notifications via backup eSIM connections; however, such complete restriction could hinder the user experience of certain essential services. As discussed herein, backup eSIM connections can be made available for use by a limited set of applications or system resources that use push notification messages sent to wireless devices. The use of push notifications via backup eSIM connections can provide improved or simplified procedures, such as during device startup or eSIM deployment.

[0015] After a wireless device establishes a connection to a cellular wireless network via a backup eSIM, the wireless device establishes a new (or continues to use the previous) cellular wireless network working phase with the device manufacturer's push notification server via the backup eSIM connection. In some cases, when establishing or continuing a working phase with the device manufacturer's push notification server, the wireless device may indicate that it is using the backup eSIM connection. For example, the header of a device capability (or other applicable) message may indicate the use of the backup eSIM connection to the device manufacturer's push notification server. In some cases, the wireless device connects to the device manufacturer's push notification server via a proxy server. In some cases, the device manufacturer's push notification server identifies the connection to the wireless device as being via a backup eSIM connection based on the connection via a specific proxy server (e.g., a proxy server designated for backup eSIM use). The device manufacturer's push notification server can provide push notifications for various applications or system services to the wireless device. The backup eSIM connection will be restricted to a limited set of push notification topics for the wireless device. Specifically, only certain push notification messages that can be communicated to the wireless device via the user's eSIM cellular wireless connection (or via a non-cellular wireless connection) will be permitted to communicate via the backup eSIM connection. The wireless device will register with a push notification server to receive push notifications for one or more topics that are permitted to be used via the backup eSIM connection. Only push notifications associated with permitted and registered push notification topics will be sent to the wireless device via the backup eSIM connection. Exemplary push notification topics permitted via the backup eSIM connection may include: i) obtaining the user's eSIM from the wireless device when an alternative connection is unavailable; ii) transferring the user's eSIM (or the cellular service associated with user eSIM0) to the wireless device; and iii) initial unpacking or device startup after a factory reset. Currently, the application uses polling of the application server by the wireless device in response to user actions, which may hinder certain processes, such as when the user does not perform a specific action that would poll the application server. In some cases, without push notifications via a backup eSIM connection and without polling based on user actions, a wireless device may be unable to receive information about new cellular plans available for the wireless device or obtain new or updated startup policies for the wireless device. To overcome these limitations, the wireless device will be allowed to register push notifications from a selected set of push notification topics. In some cases, this set of allowed notification topics can be dynamically adjusted, for example, through policies included in the device manufacturer's software or firmware. The push notification server registers with the application server corresponding to the push notification topics for the wireless device to receive applicable push notification messages via the backup eSIM connection.The device manufacturer's push notification server restricts push notifications sent to the wireless device via the backup eSIM connection and may disallow the sending or forwarding of push notification messages that do not belong to the permitted push notification topics to the wireless device via the backup eSIM connection. The device manufacturer's push notification server can appropriately filter push notifications and can update push notification filtering policies at the device manufacturer's push notification server without requiring changes to the wireless device. The wireless device may limit the use of the backup eSIM connection to, for example, a certain number of minutes per hour per day. The wireless device may implement time-limiting procedures to manage the time periods during which the backup eSIM connection is active; the backup eSIM may be inactive outside of these periods.

[0016] These and other embodiments are discussed below with reference to Figures 1 through 8. However, those skilled in the art will understand that the detailed descriptions given herein with reference to these figures are for illustrative purposes only and should not be construed as limiting.

[0017] Figure 1 illustrates a block diagram of the different components of system 100, which includes: i) a wireless device 102, which may also be referred to as a mobile wireless device, a cellular wireless device, a wireless communication device, a mobile device, user equipment (UE), a device, a primary wireless device, a secondary wireless device, an auxiliary wireless device, a wearable device supporting cellular functionality, and the like; ii) a group of base stations 112-1 to 112-N, which may be managed by different mobile network operators (MNOs) 114; and iii) a group of deployed servers 116, which communicate with MNO 114. Wireless device 102 may represent a mobile computing device (e.g., a telephone, tablet, peripheral device, etc.), and base stations 112-1 to 112-N may represent radio access network (RAN) entities, including fourth-generation (4G) Long Term Evolution (LTE) Evolved Node B (eNodeB or eNB), fifth-generation (5G) Node B (gNodeB or gNB), and / or sixth-generation (6G) Node B configured to communicate with wireless device 102. Each of base stations 112-1 to 112-n may be a single entity, a quasi-co-located entity, or separated among multiple units (e.g., Central Unit (CU), Distributed Unit (DU), Remote Unit (RU)). MNO 114 may represent different wireless service providers offering specific services (e.g., voice, data, video, messaging), which users of wireless device 102 may subscribe to for access via wireless device 102. Applications residing on wireless device 102 may advantageously access services provided by the wireless service provider via one or more base stations 112 using 4G LTE, 5G, and / or 6G connections (when available) on the cellular wireless network.

[0018] As shown in Figure 1, the wireless device 102 may include a processing circuitry system (which may include one or more processors 104 and memory 106), an embedded universal integrated circuit card (eUICC) 108, and / or an integrated UICC (iUICC) (not shown), and a wireless circuitry system 110 for transmitting and receiving wireless radio frequency signals. In some embodiments, the wireless device 102 may include one or more universal integrated circuit cards (UICCs) 118 (also referred to as physical SIM cards), in addition to or instead of an eUICC 108 providing one or more electronic SIMs (eSIMs) and / or an iUICC providing one or more eSIMs, each UICC 118 also including a SIM. The wireless device 102 including multiple active (enabled) SIMs and / or eSIMs may be generally referred to herein as a multi-SIM / eSIM wireless device. One or more processors 104 may include one or more wireless processors, such as a cellular baseband component, a wireless local area network processor, a wireless personal area network processor, a near-field communication processor, and one or more system-level application processors. The components of wireless device 102 work together to enable wireless device 102 to provide useful functions to the user of wireless device 102, such as cellular wireless network access, non-cellular wireless network access, localized computing, location-based services, and Internet connectivity. Although the various components (e.g., memory 106, processors 104, eUICC 108, wireless circuit system 110, and UICC 118) are depicted as dissimilar blocks, they can still be configured and combined in any number of ways.

[0019] To access services provided by the MNO, the eSIM can be kept on standby for subsequent download and installation into the eUICC 108. In some embodiments, as part of the device initialization of the wireless device 102 (such as when a new wireless device 102 is purchased), the eUICC 108 obtains one or more eSIMs from one or more associated deployment servers 116. The deployment servers 116 may be maintained by the manufacturer of the wireless device 102, the MNO 114, a third-party entity, and the like. Communication of eSIM data between the MNO deployment server 116 and the eUICC 108 (or between the MNO deployment server 116 and the processing circuitry (e.g., processor 104) of the wireless device 102 outside the eUICC 108) may use a secure communication channel.

[0020] In some cases, wireless device 102 may lack an activated, fully functional cellular wireless eSIM on eUICC 108, and may also not include UICC 118 with an activated physical SIM (pSIM) installed in wireless device 102. Users of wireless device 102 may be required to activate, download, and / or configure a fully functional eSIM from MNO deployment server 116 to access the cellular wireless service of the specific MNO with which the user has established a cellular wireless subscription. Wireless device 102 may include a limited-functionality backup eSIM that can be initially configured to be in an inactive state. When an application authorized to use the backup eSIM requires a wireless network connection, and no cellular wireless network connection is available or cannot be established, wireless device 102 may reactivate the backup eSIM from an inactive state to an active state to allow the establishment of a connection to the cellular wireless network via the backup eSIM. In some cases, a backup eSIM can be activated, and a backup eSIM connection can be established in the background for system resource processing, such as for receiving a limited set of push notification messages that can assist various wireless device programs. In some embodiments, a backup eSIM connection to the device manufacturer's push notification server can be established when push notification messages for basic services cannot be received via other alternative wireless or wired connections.

[0021] Figure 2 is a block diagram illustrating a more detailed view 200 of specific components of the wireless device 102 of Figure 1 according to some embodiments. As shown in Figure 2, processors 104 combined with memory 106 can implement a main operating system (OS) 202 configured to execute applications 204 (e.g., native OS applications and user applications). Also as shown in Figure 2, eUICC 108 can be configured to implement an eUICC OS 206 configured to manage the hardware resources of eUICC 108 (e.g., the processor and memory embedded in eUICC 108). The eUICC OS 206 can also be configured to manage the eSIMs 208 stored in the eUICC 108, for example, by downloading, installing, deleting, enabling, disabling, modifying, or otherwise managing the eSIMs 208 within the eUICC 108, and granting the baseband wireless circuit system 110 access to the eSIMs 208 to provide the wireless device 102 with access to wireless services. The eUICC 108 OS may include an eSIM manager 210 capable of performing various management functions for the eSIMs 208. As illustrated in Figure 2, each eSIM 208 may include several small applications 212 that define the operation of the eSIM 208. For example, when implemented in conjunction with the baseband wireless circuit system 110 and the eUICC 108, one or more small applications 212 may be configured to enable the wireless device 102 to communicate with the MNO 114 and provide useful functions (e.g., telephone calls and internet access) to the user of the wireless device 102.

[0022] As also shown in Figure 2, the baseband wireless circuit system 110 of the wireless device 102 may include a baseband OS 214 configured to manage the hardware resources (e.g., processor, memory, various radio components, etc.) of the baseband wireless circuit system 110. According to some embodiments, the baseband wireless circuit system 110 may implement a baseband manager 216 configured to interface with the eUICC 108 to establish a secure channel with the MNO deployment server 116 and obtain information (such as eSIM data) from the MNO deployment server 116 for the purpose of managing the eSIM 208. The baseband manager 216 may be configured to implement a service 218 representing a collection of software modules, which are individualized by various small applications 212 included in the eUICC 108 and enabled for eSIM 208. For example, service 218 can be configured to manage different connections between wireless device 102 and MNO 114 based on different eSIMs 208 enabled within eUICC 108. For a backup eSIM 208 that provides limited functionality limited to certain data connections when certain conditions are met (e.g., when a cellular wireless connection via the user eSIM 208 or a non-cellular wireless connection with internet access is unavailable), wireless device 102 can suggest the availability of the backup eSIM to one or more authorized applications and / or system resources. For example, in response to an authorized application or system resource requesting network access via the backup eSIM, wireless device 102 can re-enable the backup eSIM 208 from an inactive state to an active state. The application processor of wireless device 102 (e.g., one of processors 104) may include a module for monitoring network conditions that ensure the use of the backup eSIM 208 and dynamically managing the availability of the backup eSIM for one or more applications. When the conditions for using the backup eSIM 208 are met, the backup eSIM 208 can be suggested to one or more authorized applications and / or system resources. When the conditions for using the backup eSIM 208 are not met, the backup eSIM 208 can be reverted from an active state to an inactive state. In some embodiments, a core telephony module residing on the processor 104 of the wireless device (e.g., an application processor) can request a connection to the device manufacturer's push notification server, and one or more device service resident programs on the application processor can determine whether a fully functional cellular eSIM connection or a non-cellular wireless connection can be used to connect to the device manufacturer's push notification server. When no alternative (cellular wireless, non-cellular wireless, or wired) connection is available, the device service resident program can execute a procedure to request a backup eSIM connection to communicate with the device manufacturer's push notification server via that backup eSIM connection.Activating a backup eSIM and connecting to a push notification server via the backup eSIM can occur in the background to support various system procedures, such as device startup, user eSIM deployment, user eSIM transfer, or similar.

[0023] Figure 3 illustrates the components of a communication network involved in device startup and SIM deployment, installation, and activation of wireless device 102. Device startup and SIM deployment (in some cases, including eSIM transfer) may require data connectivity for wireless device 102. In some scenarios, non-cellular access network 304 may be used for wireless device 102 to connect to various servers managed by the device manufacturer and / or by MNO 114 via an intermediary communication network 306. In some scenarios, non-cellular access network 304 may not be available, and wireless device 102 may rely on access to cellular access network 302 to start wireless device 102 and / or perform SIM deployment, for example, communicating with one or more MNO infrastructure servers 312 and / or one or more MNO deployment servers 116, including downloading and installing user eSIM 208 to wireless device 102. In some embodiments, the wireless device 102 includes a limited-function SIM profile, such as a pre-installed limited-function backup eSIM 208, which provides limited access to the cellular access network 302, such as for deploying or transmitting the user eSIM 208 to the wireless device 102, or interacting with the MNO infrastructure server 312 for managing cellular wireless service subscription accounts. In some cases, the wireless device may also communicate with one or more device manufacturer servers 308, 310. The use of the backup eSIM 208 may be based on monitored network conditions and may be recommended for specific applications authorized to use the backup eSIM 208. The OEM manufacturer of the wireless device 102 may maintain multiple network-based servers to assist in the management of the wireless device 102, such as one or more device manufacturer device service servers 308 (which can manage services supplied to the wireless device 102 for the device manufacturer), and one or more device manufacturer MNO service servers 310 (which can provide device manufacturer anchoring for managing services supplied to the wireless device 102). An exemplary device manufacturer device service server 308 may be a device manufacturer push notification server that provides push notification messages to the wireless device 102. An exemplary device manufacturer MNO service server 310 may be a lookup server that provides information about eSIMs available for the wireless device 102 from one or more MNOs 114. MNOs 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 the cellular wireless service of the wireless device 102, and an MNO deployment server 116 from which the wireless device 102 can access the SIM firmware (e.g., eSIM 208, OTA updates for eSIM 208, etc.) with appropriate authentication.

[0024] Figure 4A illustrates an exemplary state of the backup eSIM 208 of the wireless device 102, shown in Figure 400. The backup eSIM 208 may be installed in the wireless device 102 at the manufacturing plant or downloaded to the wireless device 102 after manufacturing. The backup eSIM 208 may be installed on the eUICC 108 of the wireless device 102, and the backup eSIM may be configured to be in a disabled state 402. The backup eSIM 208 cannot be used until it is enabled. The backup eSIM 208 may be reconfigured from the disabled state 402 to an inactive state 404, in which the use of the cellular wireless capabilities of the backup eSIM 208 may be restricted, preventing it from establishing an active cellular wireless connection with a cellular wireless network, for example, to reduce communication and save battery power of the wireless device 102. The inactive state may include: i) cellular flight mode, in which the baseband cellular transceiver is disabled (cellular wireless transmission or reception is not allowed); or ii) limited network search mode, in which the baseband cellular receiver listens for signals from the cellular wireless network to prepare the wireless device 102 for future cellular wireless connections, but does not use the backup eSIM for transmission or connection to the cellular wireless network when in the inactive state. In some cases, the wireless device 102 may use the backup eSIM 208 to reside on the cellular wireless network, but only establish an active data connection with the cellular wireless network when needed. The backup eSIM 208 can be reconfigured from the inactive state 404 to the active state 406, in which a data connection with the cellular wireless network can be established via the backup eSIM 208. Wireless device 102 can put and take off the backup eSIM 208 into an inactive state 404 based on system resource needs and / or requests from applications authorized to use the backup eSIM 208. In some cases, the use of cellular wireless connectivity via the backup eSIM 208 can be restricted to a specific set of permitted actions, such as allowing an internet connection to the device manufacturer's managed server for device startup, establishing a secure connection to the MNO 114 deployment server 116 to download the user eSIM 208, communicating various eSIM deployment operation statuses to the device manufacturer's server or MNO server, obtaining eSIM status from the device manufacturer's MNO service server 310, and receiving a limited set of push notification messages from the device manufacturer's device service server (such as a push notification server).

[0025] The client application or system resources of the wireless device 102 authorized to use the backup eSIM 208 can receive an indication of the availability of the backup eSIM 208. The client application or system resources can determine whether to request network connectivity via the backup eSIM 208 when available, and can, for example, confirm the need to use the backup eSIM 208 with the dynamic backup eSIM management module. When it is no longer needed, the client application or system resources can indicate the completion of the confirmation of using the backup eSIM 208. When no application or system resource authorized to use the backup eSIM 208 needs to use the backup eSIM, the dynamic backup eSIM management module can revert the backup eSIM 208 from an active state to an inactive state. Under certain conditions, the backup eSIM 208 can remain available to authorized client applications and / or authorized system resources. In some cases, the connection via the backup eSIM 208 can be used to register one or more push notification topics, for which push notifications are permitted to be sent to the wireless device 102 via the backup eSIM 208 connection. In some cases, the wireless device 102 may implement a procedure to limit the time availability of the backup eSIM 208 connection for push notifications. In some cases, the wireless device 102 may implement an inactive timer to determine when to stop using the backup eSIM 208 connection, such as for push notifications.

[0026] Figure 4B illustrates an illustrative use of the fallback eSIM 208 installed on the eUICC 108 of the wireless device 102. At 456, a communication module 452, which can execute on the processor 104 of the wireless device 102 (e.g., an application processor or baseband processor), can initialize a fallback agent associated with the fallback eSIM 208. At 458, the communication module 452 can register the fallback agent with the network management module 454, or the network management module can execute on the same processor 104 or another processor 104 of the wireless device 102. At 460, the communication module 452 can initialize a cellular deployment policy to instruct the correct use of the fallback eSIM 208 via the fallback agent. At 462, the communication module 452 can communicate the cellular deployment policy to the network management module. Subsequently, at 464, the communication module 452 can determine the network data connection requirement, for example, based on user input or system resource requirements, and can transmit 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 backup eSIM 208. At 466, the network management module 454 can send a request to initiate an internet data connection to the communication module 452, for example, by establishing a non-cellular or cellular wireless connection based on the user eSIM 208. At 452, the communication module 452 can respond to the network management module 454, indicating that the establishment of the requested network data connection has failed, 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 wireless device 102. At 470, network management module 454 may, for example, supplement the use of backup eSIM 208 according to the cellular deployment strategy previously received from communication module 452 at 462. At 472, network management module 454 may send a message to communication module 452 to establish a network connection using backup eSIM 208. At 474, communication module 452 may respond with an indication that the backup eSIM 208 has successfully established a network connection. At 476, network management module 454 may transmit data via the connection established using backup eSIM 208. In some embodiments, as shown in FIG4B, the ability to deploy eSIM 208 can be used for data connections and as a supplementary connection on demand when no other data connection is available.

[0027] Figures 5A and 5B illustrate examples of managing push notifications via a backup eSIM connection of wireless device 102, Figures 500 and 520. In a first step, the core telephone module 506 and wireless circuit system 110 of wireless device 102 can place the backup eSIM 208 in an inactive state 404, wherein wireless device 102 resides on a cellular wireless network via the backup eSIM 208, but cannot establish a data connection with the cellular wireless network. The core telephone module 506 may be implemented in the application processor and / or baseband processor of wireless device 102. Wireless circuit system 110 may include hardware and software / firmware (including the baseband processor) to enable wireless connectivity for wireless device 102. In a second step, the core telephone module 506 sends a request message to the push notification resident 504 of wireless device 102 to establish a connection for push notification services to the push notification server 508 of the original equipment manufacturer (OEM) (also referred to herein as the device manufacturer). Push notification resident 504 provides services for managing push notifications from device manufacturer push notification server 508. Push notification resident 504 may be one of several device service resident resident on the application processor of wireless device 102. In the third step, push notification resident 504 may determine whether to select a non-cellular wireless connection or a user eSIM cellular wireless connection (when available) for communication with device manufacturer push notification server 508. In the fourth step, when no alternative wireless (e.g., non-cellular or user eSIM) or wired connection is available, push notification resident 504 may determine whether to select a backup eSIM cellular wireless connection for communication with device manufacturer push notification server 508. In the fifth step, push notification resident 504 may send a request to use backup eSIM 208 to core telephone module 506. In the sixth step, the core phone module 506 enables the wireless circuit system 110 to switch the backup eSIM 208 to an active state (if needed) and establish an active data connection via the backup eSIM 208. In the seventh step, the core phone module 506 can respond to the push notification resident 504 by confirming the availability of the backup eSIM connection for use by the push notification resident 504. In the eighth step, the push notification resident 504 establishes a new working phase or continues a previous working phase with the device manufacturer push notification server 508 via the backup eSIM connection. This device manufacturer push notification server may be one of one or more device manufacturer device service servers 308. In some cases, the push notification resident 504 communicates directly with the device manufacturer push notification server 508. In some cases, the push notification resident 504 communicates indirectly with the device manufacturer's push notification server 508 via a proxy server, which may be another of one or more device manufacturer device service servers 308.In some embodiments, the proxy server may be configured to handle communications via a backup eSIM connection. In some embodiments, the push notification resident 504 indicates to the device manufacturer push notification server 508 that a backup eSIM connection is being used (and / or will be used) during the operational phase. In a ninth step, the push notification resident 504 may identify the wireless device 102 to the device manufacturer push notification server 508 and indicate the use of the backup eSIM connection. In some embodiments, the push notification resident 504 indicates to the device manufacturer push notification server 508 that the backup eSIM connection will be used for push notification communications (and associated communications) in the header of the device capability message. In some embodiments, the device manufacturer push notification server 508 determines that the wireless device 102 is using the backup eSIM connection based on receiving communications established or reused during the operational phase via the proxy server, where the proxy server is known to be used for the backup eSIM connection. In a tenth step, the push notification resident 504 may indicate to the core telephone module 506 that a connection to the device manufacturer push notification server 508 is available via the backup eSIM connection.

[0028] Because the backup eSIM connection can be restricted to a subset of push notification messages that can be sent to the wireless device 102, the wireless device 102 can be configured to request push notification messages for specific push notification topics permitted to be delivered via the backup eSIM connection. Example push notification topics include user eSIM deployment, eSIM transfer, and device startup. In step eleven, the core phone module 506 sends a message to the push notification resident 504 to register one or more push notification topics (e.g., A, B, and / or C) to receive push notification messages for the requested push notification topics via the backup eSIM connection. In step twelf, the push notification resident 504 sends a message to the device manufacturer push notification server 508 to register one or more requested push notification topics (e.g., A, B, and / or C). In some embodiments, the core phone module 506 can restrict requests for push notifications to only those permitted via the backup eSIM connection. In some embodiments, push notification resident 504 may filter push notification requests from core telephony module 506 (or other modules) and forward such requests to a set of authorized push notification topics. In some embodiments, when a backup eSIM connection is used for communication between the device manufacturer push notification server 508 and the wireless device 102, the device manufacturer push notification server 508 may filter registration requests for push notification messages to limit them to requests authorized via the backup eSIM connection.

[0029] For the examples in Figures 5A and 5B, we assume that push notification topics A, B, and C are included in a set of permitted push notification topics, and push notification messages for these topics can be transmitted to wireless device 102 via a backup eSIM connection. In step thirteen, device manufacturer push notification server 508 can send a message to application server A 502A to register wireless device 102 to receive push notifications for push notification topic A. In step fourteen, device manufacturer push notification server 508 can send a message to application server B 502B to register wireless device 102 to receive push notifications for push notification topic B. In step fifteen, device manufacturer push notification server 508 can send a message to application server C 502C to register wireless device 102 to receive push notifications for push notification topic C. In some embodiments, individual application servers 502A, 502B, and 502C may be unaware that push notifications will be provided to wireless device 102 via a backup eSIM connection. In some embodiments, the device manufacturer push notification server 508 acts as a gatekeeper to filter push notifications from wireless device 102, limiting them to those permitted to be delivered via the backup eSIM connection. In the sixteenth step, the push notification resident 504 confirms with the core telephony module 506 the registration of wireless device 102 with one or more application servers 502A, 502B, and 502C for push notification topics A, B, and C. Although Figures 5A and 5B indicate individual application servers handling different push notification topics, in some embodiments, application servers may provide push notifications for more than one push notification topic.

[0030] In some embodiments, to limit the availability of the backup eSIM connection used for push notification messages to, for example, a specific time period, such as every Z days, Y hours, and X minutes, in step seventeen, the push notification resident 504 initiates a time-limiting agreement for the use of the backup eSIM connection to the device manufacturer's push notification server. In step eighteen, the device manufacturer's push notification server 508 receives a notification message for push notification topic A from application server A 502A. In step nineteen, the device manufacturer's push notification server 508 allows push notifications only for authorized and registered push notification topics to be sent to the wireless device 102, while the backup eSIM connection is active and used by the wireless device 102 to receive push notifications. When the wireless device 102 registers for push notification topic A authorized via the backup eSIM connection, in step twentieth, the device manufacturer's push notification server 508 may send a push notification for push notification topic A to the push notification resident 504 on the wireless device 102. In step 21, the push notification resident 504 may forward a push notification for push notification topic A to the core telephone module 506 (e.g., when the push notification topic relates to the availability of an eSIM for deployment to wireless device 102). In step 22, the core telephone module 506 and the wireless circuit system 110 (e.g., the baseband processor and / or eUICC 108 of wireless device 102) may communicate with application servers A, 502A via a backup eSIM connection. For example, application server A 502A may be deployment server 116 of MNO 114, and push notification topic A may relate to deploying eSIM 208 to eUICC 108 of wireless device 102. As another example, application server A 502A may be a device manufacturer lookup server, from which wireless device 102 can determine the availability of one or more eSIMs 208 for backup, for example, where push notification topic A may relate to deploying eSIM 208 to wireless device 102 or delivering cellular wireless service associated with eSIM 208 to wireless device. As a further example, application server A 502A may be a device manufacturer startup server, and push notification topic A may relate to startup of wireless device 102. In step twenty-three, the time limit for connecting to the device manufacturer push notification server 508 via the backup eSIM is reached. In step twenty-four, push notification resident 504 sends a message to core telephone module 506 to release the use of the backup eSIM connection.In step twenty-five, when wireless device 102 has no other service or module requiring or able to use the backup eSIM connection, core telephone module 506 and wireless circuit system 110 disconnect the backup eSIM connection to the cellular wireless network, and revert backup eSIM 208 from an active state to an inactive state, wherein wireless device 102 continues to reside on the cellular wireless network via backup eSIM 208. In step twenty-six, core telephone module 506 confirms to push notification resident 504 that the release of the backup eSIM connection has been completed.

[0031] Figure 6 illustrates a flowchart 600 of an exemplary method executed by one or more processors 104 of wireless device 102 to manage push notifications of wireless device 102 via a backup eSIM connection. At 602, one or more processors 104 determine that one or more conditions for using backup eSIM 208 are met. At 604, one or more processors 104 re-enable backup eSIM 208 from an inactive state to an active state. At 606, one or more processors 104 establish a backup eSIM connection to the wireless network via backup eSIM 208. At 608, one or more processors 104 establish an operational phase with push notification server 508 via backup eSIM connection. At 610, one or more processors 104 register wireless device 102 to receive one or more push notifications on push notification topics from push notification server 508 via backup eSIM connection. At 612, one or more processors 104 initiate a time-limited procedure for using backup eSIM connection for push notifications. At point 614, when the push notification time limit is met, one or more processors 104 release the backup eSIM connection to the wireless device 102.

[0032] In some embodiments, the method further includes, when a push notification time limit is met, one or more processors 104 of the wireless device 102 reconfigures the backup eSIM 208 from an active state to an inactive state. In some embodiments, the inactive state includes a dwell-only mode for the wireless device 102 to reduce communication dwell time on the wireless network. In some embodiments, communication between the wireless device 102 and the push notification server 508 via the backup eSIM connection includes communication via a proxy server. In some embodiments, the method further includes one or more processors 104 of the wireless device 102 identifying to the push notification server 508 associated with the establishment of the operational phase that the backup eSIM connection is used for push notification. In some embodiments, the method further includes the wireless device 102 receiving a push notification for a push notification topic from the push notification server 508 via the backup eSIM connection. In some embodiments, the method further includes the wireless device 102, in response to receiving the push notification, communicating via the backup eSIM connection with the application server 502 associated with the push notification topic. In some embodiments, the push notification topic includes deploying the user eSIM 208 to the wireless device 102. In some embodiments, the push notification topic includes transmitting cellular wireless services associated with the SIM or user eSIM 208 of the second wireless device 102 to the wireless device 102. In some embodiments, the application server 502 associated with the push notification topic includes an MNO deployment server 116. In some embodiments, the application server 502 associated with the push notification topic includes a device manufacturer MNO service server 310 configured to provide notifications for the idle user eSIM 208 of the wireless device 102. In some embodiments, the push notification topic includes wireless device startup. In some embodiments, the application server 502 associated with the push notification topic includes a device manufacturer device service server 308 configured for wireless device startup.

[0033] Figure 7 illustrates a flowchart 700 of an exemplary method executed by a push notification server 508 to manage push notifications for a wireless device 102 connected via a backup eSIM. At 702, the push notification server 508 establishes an operational phase with the wireless device 102 via the backup eSIM connection. At 704, the push notification server 508 receives a registration request message from the wireless device 102 via the backup eSIM connection, indicating a push notification topic. At 706, the push notification server 508 sends a registration message to an application server 502 corresponding to the push notification topic to register the wireless device 102 to obtain push notifications associated with that topic. At 708, the push notification server 508 receives a notification message from the application server 502 regarding the push notification topic for the wireless device 102. At 710, when the wireless device 102 allows push notifications for a push notification topic via a backup eSIM connection, the push notification server 508 responds by sending a push notification for the push notification topic to the wireless device 102 via the backup eSIM connection upon receiving the notification message.

[0034] In some embodiments, the push notification server 508 is further configured to receive a second notification message for the second push notification topic for the wireless device 102 from the second application server 502 when the backup eSIM connection to the wireless device 102 is active, and to avoid sending the second push notification to the wireless device 102 when push notifications for the second push notification topic are not permitted via the backup eSIM connection. In some embodiments, the push notification topic includes deploying or transmitting the user eSIM 208 to the wireless device 102, and the application server 502 associated with the push notification topic includes an MNO deployment server 116 or a device manufacturer MNO service server 310 configured to provide notifications of the user eSIM 208 in standby mode on the wireless device 102. In some embodiments, the push notification topic includes wireless device startup, and the application server 502 associated with the push notification topic includes a device manufacturer device service server 308 configured for wireless device startup. [Representative Device]

[0035] Figure 8 illustrates a detailed view of a representative computing device 800 that can be used to implement the various methods described herein, according to some embodiments. Specifically, this detailed view illustrates various components that may be included in the wireless device 102. As shown in Figure 8, the computing device 800 may include a processor 802, which represents a microprocessor or controller for controlling the overall operation of the computing device 800. The computing device 800 may also include a user input device 808 that allows a user of the computing device 800 to interact with it. For example, the user input device 808 may take various forms, such as buttons, keypads, dial pads, touchscreens, audio input interfaces, visual / image capture input interfaces, sensor data input, etc. Furthermore, the computing device 800 may include a display 810 that can be controlled by the processor 802 to display information to a user. A data bus 816 facilitates data transfer between at least a storage device 840, the processor 802, and the controller 813. The controller 813 can be used to connect to and control different devices via a device control bus 814. The computing device 800 may also include a network / bus interface 811 communicatively coupled to the data link 812. In the case of wireless connectivity, the network / bus interface 811 may include a wireless transceiver.

[0036] The computing device 800 also includes a storage device 840, which may comprise a single disk or a plurality of disks (e.g., a hard disk), and includes a storage management module that manages one or more partitions within the storage device 840. In some embodiments, the storage device 840 may include flash memory, semiconductor (solid-state) memory, etc. The computing device 800 may also include random access memory (RAM) 820 and read-only memory (ROM) 822. The ROM 822 may store programs, utilities, or processing programs to be executed in a non-volatile manner. The RAM 820 may provide volatile data storage and store instructions related to the operation of the computing device 800. The computing device 800 may further include a secure element (SE) 824, which may represent secure storage for the wireless device 102 to access the cellular wireless system, such as an eUICC 108 storing one or more eSIMs 208 and / or a UICC 118 storing a pSIM profile. [Wireless Terminology]

[0037] According to the various embodiments described herein, the terms "wireless communication device," "wireless device," "mobile wireless device," "mobile station," and "user equipment (UE)" are used interchangeably herein to describe one or more common consumer electronic devices capable of performing programs associated with the various embodiments of this disclosure. According to various implementations, any of these consumer electronic devices may relate to: cellular phones or smartphones, tablet computers, laptops, notebook computers, personal computers, lightweight notebook computers, media player devices, e-book devices, MiFi® devices, wearable computing devices, and any other type of electronic computing device with wireless communication capabilities, which may include communication via one or more wireless communication protocols such as for communication on: 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 network, fourth generation (4G) Long Term Evolution (LTE), LTE-A, and / or 5G or other currently or future advanced cellular wireless networks.

[0038] In some embodiments, the wireless communication device may also operate as part of a wireless communication system that may include a group of user terminal devices (also referred to as stations, user terminal wireless devices, or user terminal wireless communication devices) interconnected to an access point (AP) for example as part of a WLAN, and / or interconnected with each other for example as part of a WPAN and / or an "ad hoc" wireless network. In some embodiments, the user terminal 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, WLAN technology may include a Wi-Fi (or more generally, WLAN) wireless communication subsystem or radio, and the Wi-Fi radio may implement 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 IEEE 802.11 technologies.

[0039] Furthermore, it should be understood that the UE described herein can be configured as a multi-mode wireless communication device capable of communicating via different third-generation (3G) and / or second-generation (2G) RATs. In these scenarios, the multi-mode UE can be configured to preferentially connect to LTE networks, which offer faster data rates, compared to other 3G legacy networks that provide lower data rates. For example, in some implementations, the multi-mode UE can 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 unavailable.

[0040] The various forms, embodiments, implementations, or features of the described examples may be used separately or in any combination. The various forms of the described examples may be implemented by software, hardware, or a combination of hardware and software. The described examples may also be embodied as computer-readable code on a non-transitory computer-readable medium. A non-transitory computer-readable medium is any data storage device capable of storing data, which can then be read by a computer system. Examples of non-transitory computer-readable media include read-only memory, random access memory, CD-ROM, HDD, DVD, magnetic tape, and optical data storage. Non-transitory computer-readable media may also be distributed across a network-coupled computer system, enabling distributed storage and execution of computer-readable code.

[0041] Regarding this disclosure, the use of personally identifiable information should comply with privacy policies and practices generally recognized as meeting or exceeding industry or governmental requirements for maintaining user privacy. In particular, personally identifiable information should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to the user.

[0042] For the purpose of explanation, specific nomenclature has been used in the foregoing description to provide a thorough understanding of the described embodiments. However, those skilled in the art will understand that specific details are not necessary for the practice of the described embodiments. Therefore, the foregoing description of specific embodiments is for illustrative and explanatory purposes, and is not intended to be exhaustive or to limit the described embodiments to the precise forms disclosed. Those skilled in the art will understand that many modifications and variations are possible in light of the foregoing teachings.

[0043] 100: System 102: Wireless Device 104: Processor 106: Memory 108: Embedded General-Purpose Integrated Circuit Card 110: Wireless Circuit System 112-1~112-N: Base Station 114: Mobile Internet Operator 116: MNO Deployment Server 118: Integrated Universal Circuit Card 200: View 202: Main OS 204: Application 206: eUICC OS 208:eSIM 210: eSIM Manager 212: Small Applications 214: Baseband OS 216: Baseband Manager 218: Service 300: Figure 302: Cellular Access Network 304: Non-cellular access network 306: Communication Networks 308: Device Manufacturer Device Service Server 310: Device manufacturer MNO service server 312: MNO Infrastructure Server 400: Figure 402: Disabled 404: Inactive state 406: In operation 450: Figure 452: Communication Module 454: Network Management Module 456: Steps 458: Steps 460: Steps 462: Steps 464: Steps 466: Steps 470: Steps 472: Steps 474: Steps 476: Steps 500, 520: Figure 502A: Application Server A 502B: Application Server B 502C: Application Server C 504: Push notification persistent program 506: Core Telephone Module 508: Push Notification Server 600: Flowchart 602: Steps 604: Steps 606: Steps 608: Steps 610: Steps 612: Steps 614: Steps 700: Flowchart 702: Steps 704: Steps 706: Steps 708: Steps 710: Steps 800: Computing device 802: Processor 808: User Input Device 810: Monitor 811: Network / Bus Interface 812: Data Link 813: Controller 814: Equipment Control Bus 816: Data Bus 820: Random Access Memory (RAM) 822: Read-only memory (ROM) 824: Safety Components 840: Storage device

Claims

1. A method for managing push notifications of a backup electronic subscriber identity module (eSIM) connection of a wireless device, the method comprising: by means of one or more processors of the wireless device: determining that one or more conditions for using a backup eSIM are met; resetting the backup eSIM from an inactive state to an active state; establishing a backup eSIM connection to a wireless network via the backup eSIM; establishing an operational phase with a push notification server via the backup eSIM connection; registering with the push notification server via the backup eSIM connection to receive one or more push notifications on a push notification subject via the backup eSIM connection; initiating a time-limiting procedure for using the backup eSIM connection for push notifications; and releasing the backup eSIM connection when a push notification time-limit threshold is met. The push notification server only allows push notifications to be delivered to the wireless device via the backup eSIM connection for push notification topics that have been registered for the wireless device; otherwise, push notifications for the wireless device are not allowed to be delivered via the backup eSIM connection.

2. The method of request item 1 further includes: when the push notification time limit is met, resetting the backup eSIM from the active state to the inactive state.

3. The method of claim 1, wherein the inactive state includes a dwell-only mode for the wireless device to reduce the number of communications residing on the wireless network.

4. The method of claim 1, wherein communication between the wireless device and the push notification server via the backup eSIM connection includes communication via a proxy server.

5. The method of claim 1, further comprising: the wireless device identifying to the push notification server associated with the establishment of the working phase that the backup eSIM connection is used for push notification.

6. The method of claim 1, further comprising: receiving a push notification for one of the push notification topics from the push notification server via the backup eSIM connection.

7. The method of claim 6 further includes: in response to receiving the push notification, communicating via the backup eSIM connection with one of the application servers associated with the push notification topic.

8. The method of request item 7, wherein the push notification subject includes deploying a user eSIM to the wireless device.

9. The method of request item 8, wherein the application server associated with the push notification topic includes a mobile network operator (MNO) deployment server.

10. The method of claim 8, wherein the application server associated with the push notification topic includes a device manufacturer MNO service server configured to provide notifications of the user's eSIM in the event of a standby wireless device.

11. The method of request item 7, wherein the push notification subject includes wireless device startup.

12. The method of claim 11, wherein the application server associated with the push notification topic includes a device manufacturer device service server configured for wireless device startup.

13. The method of claim 7, wherein the push notification subject includes transmitting cellular wireless service associated with a SIM or a user eSIM of a second wireless device to the wireless device.

14. The method of request item 13, wherein the application server associated with the push notification topic includes a mobile network operator (MNO) deployment server.

15. The method of claim 13, wherein the application server associated with the push notification topic includes a device manufacturer MNO service server configured to provide notifications of the user's eSIM in the event of a standby wireless device.

16. A method for managing push notifications via a backup electronic subscriber identity module (eSIM) connection of a wireless device, the method comprising: establishing an operational phase with the wireless device via the backup eSIM connection through a push notification server; receiving from the wireless device via the backup eSIM connection a registration request message indicating a push notification topic; sending a registration message to an application server corresponding to the push notification topic to register the wireless device for obtaining push notifications associated with the push notification topic; receiving from the application server a notification message for the push notification topic for the wireless device; and, in response to receiving the notification message, sending a push notification for the push notification topic to the wireless device via the backup eSIM connection when the wireless device allows push notifications for the push notification topic via the backup eSIM connection. The push notification server only allows push notifications to be delivered to the wireless device via the backup eSIM connection for push notification topics that have been registered for the wireless device; otherwise, push notifications for the wireless device are not allowed to be delivered via the backup eSIM connection.

17. The method of claim 16, wherein the push notification server is further configured to: receive a second notification message for the wireless device on a second push notification subject from a second application server when the backup eSIM connection to the wireless device is active; and avoid sending the second push notification to the wireless device when push notifications on a second push notification subject are not permitted via the backup eSIM connection.

18. As in request item 16, wherein: The push notification topic includes the deployment or transmission of a user eSIM to the wireless device; and the application server associated with the push notification topic includes a mobile network operator (MNO) deployment server or a device manufacturer MNO service server configured to provide notifications of a user eSIM in use for the wireless device.

19. As in request item 16, wherein: The push notification topic includes "wireless device startup"; and the application server associated with the push notification topic includes a device manufacturer device service server configured for wireless device startup.

20. One or more processors for managing a backup electronic subscriber identity module (eSIM) connection of a wireless device, wherein the one or more processors are configured to: determine that one or more conditions for using a backup eSIM are met; re-enable the backup eSIM from an inactive state to an active state; establish a backup eSIM connection to a wireless network via the backup eSIM; establish an operational phase with a push notification server via the backup eSIM connection; register with the push notification server via the backup eSIM connection to receive one or more push notifications for a push notification topic via the backup eSIM connection; initiate a time-limiting procedure for using the backup eSIM connection for push notifications; and release the backup eSIM connection when a push notification time-limit threshold is met, wherein the push notification server only allows push notifications to be delivered to the wireless device via the backup eSIM connection for push notification topics already registered for the wireless device, otherwise does not allow push notifications for the wireless device to be delivered via the backup eSIM connection.

Images