Cellular service type for bootstrap selection

Abstract

An apparatus is configured to: determine that an operation is to be performed, wherein the operation is related to a service type; determining that the current network connection does not support operation; generating a request for a temporary bootstrap profile for performing an operation for transmission to a bootstrap server, where the request includes an indication of a service type; processing the temporary bootstrap profile; and performing an operation using the temporary bootstrap profile.

Description

[0001] Priority / Citation

[0002] This application claims priority to U.S. Provisional Application Serial No. 63 / 488,850, filed on March 7, 2023, the entire contents of which are incorporated herein by reference. Background Technology

[0003] User equipment (UE) may include universal integrated circuit cards (UICCs) that enable the UE to access services provided by mobile network operators (MNOs), also known as carriers. The UICC may be configured to store an MNO profile (also known as a subscriber identity module (SIM) or SIM profile), which the UE can use to register with and interact with the carrier to obtain wireless services via the cellular network. In some cases, the UICC may be embedded directly into the UE's system board as an embedded UICC (eUICC), which may store multiple different MNO profiles (also known as eSIMs or eSIM profiles) from different operators. Summary of the Invention

[0004] Some example implementations relate to an apparatus having processing circuitry configured to: determine an operation to be performed, wherein the operation is related to a service type; determine that the current network connection does not support the operation; generate a request for a temporary bootstrap profile for performing the operation to be sent to a bootstrap server, wherein the request includes an indication of the service type; process the temporary bootstrap profile; and use the temporary bootstrap profile to perform the operation.

[0005] Other example implementations relate to an apparatus having processing circuitry configured to: process a request for a temporary bootstrap profile based on a signal received from a user equipment (UE), wherein the request includes an indication of a service type; select the temporary bootstrap profile from a pool of temporary bootstrap profiles based at least on the service type; assign the temporary bootstrap profile to the UE, wherein when the temporary bootstrap profile is assigned to the UE, the temporary bootstrap profile is not available for use by other UEs; and generate a message including the temporary bootstrap profile for transmission to the UE. Attached Figure Description

[0006] Figure 1 Example network layouts based on various example implementation schemes are shown.

[0007] Figure 2 Example user equipment (UE) based on various example implementation schemes is shown.

[0008] Figure 3 Example methods for obtaining and using bootstrap IMSI (b-IMSI) are shown according to various example implementation schemes.

[0009] Figure 4 Example user actions for initiating an emergency call service are illustrated according to various example implementation schemes.

[0010] Figure 5 Example user actions for initiating a multiplayer game are illustrated according to various example implementation schemes.

[0011] Figure 6 An example bootstrap server based on various example implementations is shown. Detailed Implementation

[0012] The example implementation can be further understood by referring to the following description and related figures, in which similar elements have the same reference numerals. The example implementation relates to a mechanism performed at the user equipment (UE) to obtain and utilize a bootstrap profile for specific user operations. As will be described in detail below, some cellular service types may require specific bootstrap profiles that may not be available at the UE.

[0013] The example implementation is described with reference to a UE. However, reference to the UE is provided for illustrative purposes only. The example implementation can be used with any electronic component capable of establishing a connection to a network and configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE as described herein is used to represent any suitable type of electronic component.

[0014] An example implementation is also described with reference to a bootstrap server (also known as a configuration server). The UE communicates with the bootstrap server via a cellular wireless network. The bootstrap server can be controlled by any entity (e.g., a cellular provider, the UE manufacturer, a third party, etc.). Furthermore, in the example implementation, the bootstrap server is shown as a component separate from the cellular network. This is not mandatory; the bootstrap server can be a component of the cellular network. Moreover, the depiction of a single bootstrap server is also illustrative; the operations described below with respect to a bootstrap server can be performed by more than one bootstrap server. Finally, the use of the term "bootstrap server" is illustrative; different entities may use different names to refer to the components or functions that perform the example operations described below.

[0015] The UE may include a bootstrap MNO profile, which provides limited connectivity options to allow the UE to connect to the cellular network for certain user operations within the network. In the current configuration, the bootstrap profile can be uniquely generated and assigned to the UE individually. However, the bootstrap profile may only provide certain types of services, such as data services. Therefore, if the UE requires a type of service not provided by the installed bootstrap profile (e.g., voice service for emergency calls), the UE will not be able to perform the desired operations.

[0016] In an example implementation, the UE provides a bootstrap server with information indicating that the UE may be seeking temporary access to a radio connection. Based on this information, the bootstrap server can perform operations to select a temporary bootstrap International Mobile Subscriber Identity (IMSI) (b-IMSI) value specifically for temporary use by the UE. The UE can use the b-IMSI value obtained from the bootstrap server to reconfigure its bootstrap profile on the eUICC and use credentials from the bootstrap profile configured with the b-IMSI value to establish a new cellular radio connection, performing the intended action indicated in the information provided to the bootstrap server. The bootstrap server can restrict the UE's use of the b-IMSI value based on any factor (e.g., based on a timer). Therefore, after the timer expires or in response to a deletion notification message for the b-IMSI value received from the UE, the bootstrap server can return the b-IMSI value to a pool of available b-IMSI values ​​for allocation to other UEs.

[0017] The example implementation introduces a mechanism for a UE to obtain a temporary bootstrap profile in order to perform specific user actions on that UE. These user actions may involve, but are not limited to, initiating an emergency call service on the UE, participating in a multiplayer game, etc. While references can be made to emergency call and multiplayer game scenarios, these are merely examples. The example implementation can be applied to other user actions that can utilize temporary bootstrap profiles. The example techniques introduced herein can be used independently of each other, in combination with other currently implemented mechanisms for obtaining temporary bootstrap profiles, in combination with future specific implementations of mechanisms for obtaining temporary bootstrap profiles, or independently of other mechanisms related to obtaining temporary bootstrap profiles.

[0018] Figure 1An example network arrangement 100 according to various example implementations is shown. Example network arrangement 100 includes a UE 110. UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet computer, desktop computer, smartphone, phablet, embedded device, wearable device (e.g., head-mounted display (HMD), AR glasses, etc.), Internet of Things (IoT) device, etc. A real network arrangement may include any number of UEs used by any number of users. Therefore, the example of a single UE 110 is provided for illustrative purposes only.

[0019] UE 110 can be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 can wirelessly communicate is the 5G NR radio access network (RAN) 120. However, UE 110 can also communicate with other types of networks (e.g., 5G cloud RAN, next-generation RAN (NG-RAN), LTE RAN, legacy cellular networks, wireless local area networks (WLANs), etc.), and UE 110 can also communicate with the network via a wired connection. Referring to the example implementation, UE 110 can establish a connection with at least 5G NR RAN 120. Therefore, UE 110 may have a 5G NR chipset to communicate with NR RAN 120.

[0020] The 5G NR RAN 120 can be part of a cellular network that can be deployed by network operators (e.g., Verizon, AT&T, T-Mobile, etc.). The 5G NR RAN 120 may include, for example, cells or base stations (Node B, eNodeB, HeNB, eNB, gNB, gNodeB, macro cells, micro cells, small cells, femtocells, etc.) configured to transmit and receive services from UEs equipped with appropriate cellular chipsets.

[0021] In network deployment 100, UE 110 can connect to 5G NR-RAN 120 via gNB 120A. Any association procedure can be performed to connect UE 110 to 5G NR-RAN 120. For example, as described above, 5G NR-RAN 120 can be associated with a specific cellular provider where UE 110 and / or its user have protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UE 110 can send the corresponding credential information to associate with 5G NR-RAN 120. More specifically, UE 110 can be associated with a specific base station (e.g., gNB 120A). However, as described above, the reference to 5G NR-RAN 120 is for illustrative purposes only, and any suitable type of RAN can be used.

[0022] Network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, a network service backbone 160, and a bootstrap server 170. The cellular core network 130 can be viewed as an interconnected set of components that manage the operation and services of the cellular network. The cellular core network 130 also manages the services flowing between the cellular network and the Internet 140. The bootstrap server 170 communicates with the UE 110 via the cellular core network 130 to exchange bootstrap data. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can generally be described as a collection of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 in communicating with various networks.

[0023] As described above, bootstrap server 170 may be a component that stores temporary bootstrap profiles and can assign one or more temporary bootstrap profiles from the temporary bootstrap profiles to UE 110 to perform specific user operations. Example operations performed by the bootstrap server are described in more detail below.

[0024] Figure 2 Example UE 110 is shown according to various example implementations. UE 110 will refer to Figure 1The network layout 100 is described below. UE 110 may include a processor 205, a memory layout 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, other components 230, an eUICC 235, and a UICC 240. Other components 230 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, and ports for electrically connecting UE 110 to other electronic devices.

[0025] Processor 205 may be configured to execute multiple engines of UE 110. For example, these engines may include bootstrap service engine 245. Bootstrap service engine 245 may perform various operations for bootstrap service and other related techniques described herein. These operations may include, but are not limited to, enabling bootstrap service for user operations by selecting an initial IMSI (i-IMSI) value from a pool of available values, requesting a temporary bootstrap profile (b-IMSI), replacing the i-IMSI value with the temporary bootstrap profile, and using the b-IMSI value for user operations.

[0026] The engine 245 referenced above, as an application (e.g., a program) executed by processor 205, is provided merely for illustrative purposes. The functionality associated with engine 245 may also be represented as a separate, integrated component of UE 110, or as a modular component coupled to UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine may also be embodied as one or more separate applications. Furthermore, in some UEs, the functionality described for processor 205 is split between two or more processors (such as a baseband processor and an application processor). Example implementations may be implemented according to any of these or other configurations of the UE.

[0027] Memory arrangement 210 may be a hardware component configured to store data related to operations performed by UE 110. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling the user to input data. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen).

[0028] Transceiver 225 may be a hardware component configured to establish a connection with 5G NR-RAN 120 and / or any other suitable type of network. Therefore, transceiver 225 may operate on a variety of different frequencies or channels (e.g., a set of consecutive frequencies). Transceiver 225 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded using information used to implement any of the methods described herein. Processor 205 may be operatively coupled to transceiver 225 and configured to receive signals from and / or transmit signals to transceiver 225. Processor 205 may be configured to encode and / or decode signals (e.g., signaling from a base station in the network) for use in implementing any of the methods described herein.

[0029] eUICC 235 can be a hardware component embedded in UE 110, configured to store multiple operator profiles. UICC 240 can be a small hardware component configured to be inserted into UE 110 to enable UE 110 to access services provided by the operator.

[0030] Figure 3 Example methods for obtaining and using bootstrap international mobile subscriber identity (b-IMSI) for specific user services are shown, according to various example implementation schemes. References will be made to... Figure 1 Network layout 100 and Figure 2 UE 110 to describe Figure 3 As will be described by way of example, UE 110 may use b-IMSI to facilitate a specific cellular service that is not supported by an installed bootstrap profile available for use at UE 110. Method 300 is a general method that can be implemented to obtain any type of b-IMSI from a bootstrap server. Emergency calls are described below. Figure 4 (call process) and multiplayer games ( Figure 5 Specific use cases for the call flow. However, as referenced Figure 3 The examples and descriptions provided are merely illustrative, and method 300 can be used with any type of bootstrap profile.

[0031] In case 305, a user initiates a specific user action on UE 110 (e.g., an emergency call in an area where UE 110 does not have voice service based on the user's subscription, a multiplayer game session not supported by the user's subscription, or an attempt to download a new eSIM profile using a QR code while traveling internationally without data roaming enabled). However, as the example illustrates, the user's subscription does not support the selected action.

[0032] Therefore, in 310, UE 110 may attempt to perform user operations using a bootstrap profile. Specifically, UE 110 may select an initial IMSI (i-IMSI) profile pre-installed on UE 110 to allow UE 110 to connect to any available network. In this example, it can be assumed that the i-IMSI profile also does not support the selected operation, and therefore UE 110 still cannot perform the selected user operation.

[0033] In section 315, UE 110 may request a bootstrap IMSI (b-IMSI) from bootstrap server 170. The request transmitted by UE 110 may include a service type. For example, if the selected operation is an emergency call, UE 110 may include an emergency service type in its request for the b-IMSI. In this way, bootstrap server 170 will understand what type of b-IMSI to provide to UE 110 so that UE 110 can complete the selected user operation. Each b-IMSI profile may have one or more defined service types. Service types may be jointly defined between UE 110 and bootstrap server 170, for example, through definitions in standard documents (e.g., 3GPP standards), through specific implementation agreements between operators, UE manufacturers, and third parties, etc.

[0034] In 320, bootstrap server 170 can allocate available b-IMSIs from a pool of available bootstrap IMSIs for specific user operations. As described above, bootstrap server 170 may include a pool of bootstrap IMSI profiles. These b-IMSI profiles may include one or more defined service types supported by the b-IMSI profile and the current status of the b-IMSI profile, such as available or currently assigned to another UE. Based on the information received in the request (e.g., service type), bootstrap server 170 will allocate one of the selected b-IMSI profiles to UE 110.

[0035] In addition to the requested service type, there may be other factors that the bootstrap server 170 may use to assign a b-IMSI profile to the UE 110. For example, the bootstrap server 170 may also select a specific b-IMSI based on, for example, the type of the UE, the UE's home PLMN, the UE's subscription type, etc.

[0036] In 325, the bootstrap server 170 may reserve available b-IMSIs for UE 110. Reserving a b-IMSI may include marking or otherwise indicating that the selected b-IMSI is no longer available for use by other UEs, and setting conditions for returning the b-IMSI to the pool after it has been used by UE 110. These conditions may be, for example, the expiration of a timer, the end of a session in which UE 110 used the b-IMSI, etc.

[0037] In 330, the bootstrap server 170 transmits the selected b-IMSI to the UE 110. In 335, once the UE 110 receives the selected b-IMSI, the UE 110 can enable the b-IMSI and perform the selected user action.

[0038] As described above, UE 110 can utilize a temporary bootstrap profile to perform specific user actions during limited cellular service at UE 110. Example call flows for two example use cases are provided below, where the user action is an emergency call ( Figure 4 Or start a multiplayer game. Figure 5 However, these user actions are merely examples, and other user actions using bootstrap IMSI (b-IMSI) may also exist.

[0039] Figure 4 Example user actions for initiating an emergency call service are illustrated according to various example implementation schemes. (Refer to...) Figure 1 Network setup 100 Figure 2 UE 110 and Figure 3 Methods to describe Figure 4 . Figure 4 An example is shown as a signaling diagram between UE110, cellular core network 130, and bootstrap server 170. Specifically, in this example, cellular core network 130 is the Mobility Management Entity (MME) and Home Subscription Service (HSS) of the local network (e.g., the network to which UE110 can communicate).

[0040] In scenario 405, a user initiates an emergency call service on UE 110. However, as shown in scenario 410, in this example, UE 110 does not have a service to perform the emergency call when the user initiates the emergency call service. There could be many reasons why UE 110 does not have a service to perform the emergency call, for example, the user's home network may not provide voice service at the user's current location. The specific reason why UE 110 does not have a service to perform the selected operation is irrelevant to the example implementation. UE 110 may alert the user to the lack of available cellular service based on the user's subscription used to perform the emergency call. However, UE 110 is not required to notify the user.

[0041] In step 415, UE 110 can set its cellular service mode to emergency service mode. In step 420, UE 110 can then attempt to make an emergency call using a bootstrap profile. Therefore, in step 425, UE 110 can select an initial IMSI (i-IMSI) pre-installed on UE 110. However, in this example, the bootstrap profile pre-installed on UE 110 may only provide data service to UE 110. Emergency call service may require voice service. For example, assigning a phone number for voice service to each bootstrap profile on each UE may not be an ideal or cost-effective practice. Therefore, UE 110 will not be able to complete an emergency call using the i-IMSI.

[0042] The example implementation introduces a mechanism that allows UE 110 to initiate emergency call service even if its original subscription and pre-installed i-IMSI do not support emergency call service. As described above, this mechanism allows UE 110 to retrieve an additional bootstrap profile that supports emergency call service.

[0043] Therefore, in 430, UE 110 transmits a request for b-IMSI to bootstrap server 170 via the established connection between UE 110 and core cellular network 130. For example, as described above, UE 110 can use the i-IMSI to establish a data-only connection to the local cellular network. UE 110 can use this data-only connection to communicate with the local cellular network to transmit the request for b-IMSI to bootstrap server 170. The request for b-IMSI may include a unique device identifier (ID) and a service type value indicating the reason why UE 110 is requesting the allocation of a b-IMSI value. Therefore, in this example implementation, the use case may indicate that a user intends to initiate an emergency call service on UE 110, for example, an emergency service type.

[0044] In 435, the bootstrap server 170 allocates a b-IMSI value to the UE 110 from a pool of available b-IMSI values. In this example, the bootstrap server 170 determines the available b-IMSI values ​​from a pool of b-IMSI values ​​that support the service type "Emergency".

[0045] In 440, the selected b-IMSI value can be retained and associated with UE 110 (in Figure 4 (This is indicated as profile 0001). In an example implementation, the bootstrap server 170 may be configured to retain and assign b-IMSI values ​​over a set time period (e.g., 24 hours).

[0046] In 445, the bootstrap server 170 can return the selected b-IMSI value (associated with bootstrap profile 0001) to the UE 110. Once the UE 110 receives the b-IMSI value, the bootstrap server 170 can initialize the expiration timer associated with the b-IMSI value.

[0047] In 450, UE 110 can be configured to enable a bootstrap profile using a selected b-IMSI value and associated profile parameters. After enabling the bootstrap profile using the selected b-IMSI value, UE 110 can continue to initiate an emergency call via the established connection between UE 110 and the cellular core network 130, as shown in 455. That is, in the example implementation, UE 110 can use credentials of the bootstrap profile configured with the b-IMSI value to establish a connection with the network.

[0048] In 460, the core network can establish a connection that allows UE 110 to receive callbacks in emergency mode. For example, in an emergency, a user may need to receive a callback after making an emergency call. Therefore, when a user makes an emergency call using the b-IMSI (profile 0001) value, the network can access the callback number associated with the b-IMSI value (profile 0001), which allows for easy callbacks in emergency mode.

[0049] In section 465, the user can terminate the emergency mode on UE 110. For example, the user can terminate the emergency call after the emergency call service is completed or after the user determines that UE 110 does not need to be in emergency mode. Therefore, in section 470, the network can clear the resources allocated to the b-IMSI (profile 0001) value. However, as previously mentioned, bootstrap server 170 can associate an expiration timer (e.g., 24 hours) with the b-IMSI allocated to UE 110. Therefore, when the timer associated with the b-IMSI (profile 0001) value expires, bootstrap server 170 can send an indication to the network after the set time (24 hours in this case) has elapsed, as shown in section 475.

[0050] Therefore, in 480, the bootstrap server 170 can return the b-IMSI (profile 0001) value to a pool of b-IMSI values ​​that can be assigned to UE110.

[0051] Therefore, the example implementation allows UE 110 to attach to other networks not registered as pre-existing subscriptions on UE 110 to perform certain user actions. For example, a user may be subscribed to a network operator's service (e.g., T-Mobile) but may be roaming in areas with different network coverage (e.g., AT&T, Verizon, etc.), so the user's network subscription may not be available to the user. Therefore, the bootstrapping service mechanism configured on UE 110 allows the user to obtain the correct credentials for user actions, regardless of the network subscription status on UE 110.

[0052] Therefore, the example implementation allows a user to access network services from any location, regardless of whether the UE 110 is connected to a subscribed network. Additionally, the user can dynamically obtain parameters (e.g., phone number) for certain user actions based on their needs.

[0053] As previously mentioned, in other example implementations, user actions can be described in terms of a user initiating a multiplayer game.

[0054] Figure 5 Example user actions for initiating a multiplayer game are illustrated according to various example implementation schemes. (Refer to...) Figure 1 Network setup 100 Figure 2 UE 110 and Figure 3 Methods to describe Figure 5 . Figure 5 An example is shown as a signaling diagram between UE 110, cellular core network 130, and bootstrap server 170.

[0055] In 505, a user can initiate multiplayer gaming services on UE 110. Multiplayer gaming services may require a low-latency network. For example, the latency a user may require may be close to that available on a Wi-Fi connection. However, when a user initiates a multiplayer gaming service (e.g., Fortnite), UE 110 may connect to a cellular network that may not consistently provide sufficient Quality of Service (QoS) to meet the gaming requirements.

[0056] 5G NR networks can use network features such as network slicing to provide defined QoS. However, this feature may only be applicable to specific use cases within the network. For example, UE 110 may be configured to dedicate a portion of a network slice to specific use cases, such as low latency (e.g., near-Wi-Fi), for certain use cases such as gaming, virtual reality, etc. A user playing a multiplayer game on UE 110 subscribed to a specific cellular service may lack the QoS associated with that service. Therefore, when a user initiates a multiplayer game on UE 110, the user can request a low-latency bootstrap profile that has been pre-allocated and pre-activated on the service to obtain dedicated low latency for the time period during which the user can participate in the game. Thus, in the example implementation, the user can obtain and utilize a temporary bootstrap profile with dedicated low latency for multiplayer gaming to participate in the game.

[0057] return Figure 5 In 510, when a user initiates a game service, UE 110 can use the bootstrap service for multiplayer gaming because the user's subscription does not support the low-latency connection required for the game service. In 515, the UE can choose a pre-installed i-IMSI profile. However, in this example, it can be assumed that the pre-installed i-IMSI profile may lack the low latency required for participating in multiplayer gaming services.

[0058] Therefore, in step 520, UE 110 can transmit a request to bootstrap server 170 via the established connection to request a temporary b-IMSI. The request for the b-IMSI may include a unique device ID and a service type value, which indicates the reason why UE 110 is requesting the allocation of a b-IMSI value. Thus, in this example implementation, the use case may indicate a user's intention to participate in a multiplayer game session using UE 110, for example, the game's service type.

[0059] In 525, bootstrap server 170 allocates b-IMSI values ​​to UE 110 from a pool of available b-IMSI values. In this example, bootstrap server 170 determines available b-IMSI values ​​from a pool of b-IMSI values ​​that support the service type "Games".

[0060] In 530, the selected b-IMSI value can be associated with UE 110 (in Figure 5 (This is indicated as profile 0002). Additionally, the bootstrap server 170 may be configured to retain the b-IMSI value for user actions at the UE 110. In an example implementation, the bootstrap server 170 may be configured to retain the b-IMSI value until predetermined conditions are met, such as the user closing the game session.

[0061] In 535, bootstrapping server 170 can return the selected b-IMSI value (associated with bootstrapping profile 0002) to UE 110. In 540, UE 110 can be configured to enable the bootstrapping profile using the selected b-IMSI value and associated profile parameters. After enabling the bootstrapping profile using the selected b-IMSI value, UE 110 can continue to initiate multiplayer games using the low-latency cellular network through the established connection between UE 110 and core cellular network 130, as shown in 545. That is, in the example implementation, UE 110 can use credentials from the bootstrapping profile configured with the b-IMSI value (which the user can use to participate in multiplayer games) to establish a connection with the network.

[0062] In 550, after a user finishes participating in a game, the user can end or close the game on UE 110. Therefore, in 555, UE 110 can be configured to release the b-IMSI value after the user transmits an indication that the game has ended or closed.

[0063] Therefore, in 555, the cellular core network 130 can be configured to clear any resources used for the b-IMSI (profile 0002) value associated with the bootstrap profile of UE 110. Therefore, in 560, the bootstrap server 314 makes the b-IMSI (profile 0002) value available in a pool of b-IMSI values ​​that can be assigned to other UEs.

[0064] Therefore, in this example implementation, the user can optimize the resources allocated to UE 110. For example, in some cases, low latency from other network subscriptions can be provided to the user based on the user's location when the user can request a temporary bootstrap profile.

[0065] Figure 6 An example bootstrap server 600 according to various example implementations is shown. (Refer to...) Figure 1 The bootstrap server 600 is described using a network layout 100. The bootstrap server 600 may include a processor 605, a memory layout 610, input / output (I / O) devices 620, network interface circuitry 625, and other components 630. Other components 630 may include, for example, a power supply, data acquisition devices, ports for electrically connecting the bootstrap server 600 to other electronic devices, etc.

[0066] Processor 605 may be configured to execute multiple engines of bootstrap server 600. For example, these engines may include bootstrap service engine 645. Bootstrap service engine 645 may perform various operations for bootstrap services and other related technologies described herein. These operations may include, but are not limited to, assigning one or more temporary bootstrap profiles from a temporary bootstrap profile to UE 110 to perform specific user operations.

[0067] The engine 645 referenced above, as an application (e.g., a program) executed by processor 605, is provided merely for illustrative purposes. The functionality associated with engine 645 may also be represented as a separate integrated component of bootstrap server 600, or as a modular component coupled to bootstrap server 600, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine may also be embodied as one application or multiple separate applications. Example implementations may be implemented according to any of these or other configurations of the bootstrap server.

[0068] The memory arrangement 610 may be a hardware component configured to store data (e.g., temporary bootstrap profiles) related to operations performed by the bootstrap server 600.

[0069] Network interface circuitry 625 may be a hardware component configured to establish a connection with cellular core network 130 and / or any other suitable type of network. Network interface circuitry 625 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded with information used to implement any of the methods described herein. Processor 605 may be operatively coupled to network interface circuitry 625 and configured to receive signals from and / or transmit signals to network interface circuitry 625. Processor 605 may be configured to encode and / or decode signals for use in implementing any of the methods described herein.

[0070] In the examples above, the described operation or action is user-initiated. However, in some examples, there may be system-initiated actions that might result from using a bootstrap profile. For example, the system (e.g., the UE, the UE's operating system (OS), etc.) may determine that a software update is needed. To facilitate the end user, the download of the software update package can utilize a high-throughput bootstrap profile with zero cost to the end user; for example, no user data is consumed by this maintenance operation occurring in the background.

[0071] For example, in the case of an in-vehicle telematics system, a user eSIM may exist for hotspots and / or other user-facing features (real-time map updates, service data, etc.). Background operations (such as vehicle data or software updates) may exist that utilize a bootstrap profile for this purpose, but these operations are not user-initiated. Therefore, the example implementation is not limited to user-initiated operations.

[0072] Example

[0073] In a first embodiment, a method includes: determining to initiate an operation, wherein the operation is related to a service type; determining that a current network connection does not support the operation; transmitting a request to a bootstrap server for a temporary bootstrap profile for performing the operation, wherein the request includes an indication of the service type; receiving the temporary bootstrap profile from the bootstrap server; and using the temporary bootstrap profile to perform the operation.

[0074] In a second embodiment, according to the method of the first embodiment, the method further includes: attempting to perform the operation using a bootstrap profile pre-installed on the user equipment (UE) before transmitting the request.

[0075] In a third embodiment, according to the method of the first embodiment, the temporary bootstrap profile includes an International Mobile Subscriber Identity (IMSI) value.

[0076] In the fourth embodiment, according to the method of the first embodiment, the temporary bootstrap profile is assigned a profile identifier.

[0077] In a fifth embodiment, according to the method of the first embodiment, the request further includes a unique identifier of the user equipment (UE).

[0078] In the sixth embodiment, according to the method of the first embodiment, the temporary bootstrap profile is enabled for user equipment (UE) until predetermined conditions are met.

[0079] In the seventh embodiment, according to the method of the sixth embodiment, the predetermined condition includes the expiration of a time duration or the termination of the user of the application associated with the operation.

[0080] In the eighth embodiment, according to the method of the first embodiment, receiving the temporary bootstrap profile from the bootstrap server includes: storing the temporary bootstrap profile on the embedded universal integrated circuit card (eUICC) of the user equipment (UE).

[0081] In the ninth embodiment, according to the method of the first embodiment, the method further includes: transmitting a message to the bootstrap server indicating that the UE is releasing the temporary bootstrap profile.

[0082] In the tenth embodiment, according to the method of the first embodiment, releasing the temporary bootstrap profile includes: deleting the temporary bootstrap profile from the embedded universal integrated circuit card (eUICC) of the user equipment (UE).

[0083] In the eleventh embodiment, according to the method of the first embodiment, wherein the operation is associated with an emergency call service, and the service type is associated with the emergency call service.

[0084] In the twelfth embodiment, according to the method of the first embodiment, wherein the operation is associated with a multiplayer game service, and the service type is associated with the multiplayer game service.

[0085] In a thirteenth embodiment, a processor is configured to perform any one of the methods described according to the first to twelfth embodiments.

[0086] In a fourteenth embodiment, a user equipment (UE) includes: a transceiver circuit configured to communicate with a network; and a processor communicatively coupled to the transceiver circuit and configured to perform any of the methods described according to the first to twelfth embodiments.

[0087] In a fifteenth embodiment, a method includes: receiving a request for a temporary bootstrap profile from a user equipment (UE), wherein the request includes an indication of a service type; selecting the temporary bootstrap profile from a pool of temporary bootstrap profiles based at least on the service type; assigning the temporary bootstrap profile to the UE, wherein when the temporary bootstrap profile is assigned to the UE, the temporary bootstrap profile is not available for use by other UEs; and transmitting the temporary bootstrap profile to the UE.

[0088] In the sixteenth embodiment, according to the method of the fifteenth embodiment, the temporary bootstrap profile includes an International Mobile Subscriber Identity (IMSI) value.

[0089] In the seventeenth embodiment, according to the method of the fifteenth embodiment, the method further includes: assigning a profile identifier to the temporary bootstrap profile.

[0090] In the eighteenth embodiment, according to the method of the fifteenth embodiment, the request further includes a unique identifier of the UE.

[0091] In the nineteenth embodiment, according to the method of the fifteenth embodiment, the method further includes: enabling the temporary bootstrap profile for the UE until a predetermined condition is met.

[0092] In the twentieth embodiment, according to the method of the nineteenth embodiment, the predetermined condition includes the expiration of a time duration or the termination of the user of the application associated with the operation.

[0093] In the twenty-first embodiment, according to the method of the fifteenth embodiment, the method further includes: receiving from the UE a message indicating that the UE is releasing the temporary bootstrap profile.

[0094] In the twenty-second embodiment, according to the method of the twenty-first embodiment, the method further includes: releasing the temporary bootstrap profile from the UE, wherein the release makes the temporary bootstrap profile available in the pool of temporary bootstrap profiles.

[0095] In the twenty-third embodiment, the method described in the fifteenth embodiment is wherein the service type is related to an emergency call service.

[0096] In the twenty-fourth embodiment, the method described in the fifteenth embodiment is used, wherein the service type is related to a multiplayer game service.

[0097] In the twenty-fifth embodiment, a processor is configured to perform any of the methods described according to the fifteenth to twenty-fourth embodiments.

[0098] In the twenty-sixth embodiment, a bootstrap server includes: a network interface circuit configured to communicate with a user equipment (UE); and a processor communicatively coupled to the network interface circuit and configured to perform any of the embodiments according to the fifteenth to twenty-fourth embodiments.

[0099] Those skilled in the art will understand that the example embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Example hardware platforms for implementing the example embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. Example embodiments of the methods described above may be embodied as programs containing lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0100] Although this application describes various embodiments that have different features in various combinations, those skilled in the art will understand that any feature of one embodiment can be combined with features of other embodiments in any way that is not expressly denied or that is not functionally or logically inconsistent with the operation of the device or the specified function of the disclosed embodiment.

[0101] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting 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 authorized use should be clearly explained to users.

[0102] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover modifications and variations thereof, provided they fall within the scope of the appended claims and their equivalents.

Claims

1. An apparatus comprising a processing circuit configured to: Determine the operation to be performed, wherein the operation is related to the service type; It has been determined that the current network connection does not support the operation. A request is generated for a temporary bootstrap profile to be sent to the bootstrap server, wherein the request includes an indication of the service type. Process the temporary bootstrap profile; as well as The operation is performed using the temporary bootstrap profile.

2. The apparatus of claim 1, wherein the processing circuit is further configured to: Before generating the request, attempt to perform the operation using a bootstrap profile pre-installed on the device.

3. The apparatus of claim 1, wherein the temporary bootstrap profile includes an International Mobile Subscriber Identity (IMSI) value.

4. The apparatus of claim 1, wherein the temporary bootstrap profile is assigned a profile identifier.

5. The apparatus of claim 1, wherein the request further includes a unique identifier of the apparatus.

6. The apparatus of claim 1, wherein the temporary bootstrap profile is enabled for the apparatus until predetermined conditions are met, wherein the predetermined conditions include the expiration of a time period or termination of the user of the application associated with the operation.

7. The apparatus of claim 1, wherein the apparatus further comprises an embedded universal integrated circuit card (eUICC), wherein the temporary bootstrap profile is stored in the eUICC.

8. The apparatus of claim 1, wherein the processing circuit is further configured to: Generate a message indicating that the device is releasing the temporary bootstrap profile for sending to the bootstrap server, wherein releasing the temporary bootstrap profile includes: Remove the temporary bootstrap profile from the embedded universal integrated circuit card (eUICC).

9. The apparatus of claim 1, wherein the operation is associated with an emergency call service, and the service type is associated with the emergency call service.

10. The apparatus of claim 1, wherein the operation is associated with a multiplayer game service, and the service type is associated with the multiplayer game service.

11. The apparatus of claim 1, wherein the processing circuitry determines the operation to be performed based on user input or system-initiated input.

12. An apparatus comprising a processing circuit configured to: The request for a temporary bootstrap profile is processed based on signals received from the user equipment (UE), wherein the request includes an indication of the type of service. The temporary bootstrap profile is selected from the pool of temporary bootstrap profiles based at least on the service type. The temporary bootstrap profile is assigned to the UE, wherein when the temporary bootstrap profile is assigned to the UE, the temporary bootstrap profile cannot be used by other UEs; as well as A message including the temporary bootstrap profile is generated for sending to the UE.

13. The apparatus of claim 12, wherein the temporary bootstrap profile includes an International Mobile Subscriber Identity (IMSI) value.

14. The apparatus of claim 12, wherein the processing circuit is further configured to: Assign a profile identifier to the temporary bootstrap profile.

15. The apparatus of claim 12, wherein the request further includes a unique identifier of the UE.

16. The apparatus of claim 12, wherein the processing circuit is further configured to: The temporary bootstrap profile is enabled for the UE until predetermined conditions are met.

17. The apparatus of claim 16, wherein the predetermined condition includes the expiration of a time period or the termination of the user of the application associated with the operation.

18. The apparatus of claim 12, wherein the processing circuit is further configured to: The message indicating that the UE is releasing the temporary bootstrap profile is processed based on the signal received from the UE.

19. The apparatus of claim 18, wherein the processing circuit is further configured to: The temporary bootstrap profile is released from the UE, wherein the release makes the temporary bootstrap profile available in the pool of temporary bootstrap profiles.

20. The apparatus of claim 11, wherein the service type is related to an emergency call service or a multiplayer gaming service.

Images