Private device triggering for IOT

Abstract

A universal integrated circuit card (UICC) is configured to provide a list to a communication device that indicates i) available profiles of a plurality of profiles that allow the communication device to access a respective wireless network, and ii) a currently enabled public network profile of the plurality of profiles, the available configuration file at least comprises a private network configuration file with a specified fallback attribute. The UICC receives a trigger from the communication device indicating a network event, such as a loss of connection. In response to the trigger, the UICC identifies the appropriate profile as a fallback / anchor profile; forbidding the currently enabled network configuration file; enabling the newly identified network configuration file; and sending the refresh command to the communication device.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and, more particularly, to methods and apparatus for prioritizing and selecting between wireless network profiles. Background Art

[0002] GSMA has defined specifications SGP.01 and SGP.02, which provide embedded SIM (eSIM) management functions for the Machine-to-Machine (M2M) / Internet of Things (IoT) segment. In this approach, all eSIM management functions are triggered remotely via the Subscription Manager for Data Preparation (SM-DP) and Subscription Manager for Secure Routing (SM-SR) functions. Local switching of profiles is explicitly not allowed within the specification, except for emergency and test profiles. Among other things, the standard defines two events that can switch eSIMs locally within the embedded Universal Integrated Circuit Card (eUICC): (i) "Fallback", which switches from the currently enabled profile to the so-called "fallback" profile, and (ii) "Switchback", which switches from the fallback profile to the previously enabled profile. The GSMA standard does not define how the fallback and switchback functions are triggered. Therefore, the practice within the industry is to have an application within the eUICC that triggers these functions. The implementation varies, but generally these events are inside the eUICC.

[0003] When these GSMA standards were originally defined, few eSIM operations were expected, except, for example, during the initial activation of a connected device or when certain events (e.g., relocation, change of service provider, etc.) occurred. Recently, private mobile networks have become available in the industry, which has changed the outlook for mobile networks. Typically, private networks are only available in specific locations (e.g., warehouses, production sites, campuses, stores, EV charging stations, etc.) and usually have limited range. Many device manufacturers want to benefit from offloading services from public mobile networks to private mobile networks (and vice versa) because such networks are available. However, these device manufacturers want to ensure that devices are continuously connected by using public mobile networks in all locations where no private networks are available. Both private and public networks require SIM profiles for network identification and authentication. This means that using SGP.01 / 02 requires more frequent eSIM operations to switch between private and public networks. The transition from one network to another should be as fast as possible to have continuous connectivity for the device. Since private networks have limited range or may be available in locations where no public networks are available, remote operations according to SGP.01 / 02 cannot usually be performed as they require an active network connection. Unfortunately, the eUICC itself has no visibility on the networks available within the reach of the device, it can only detect lost connectivity. Therefore, eUICC-based mechanisms will be too slow to achieve continuous connectivity. Summary of the invention

[0004] The following introduces a selection of concepts in a simplified form in order to provide a basic understanding of some aspects of the present disclosure. The following is not a broad overview of the present disclosure and is not intended to identify key or important elements of the present disclosure or to describe the scope of the present disclosure. The following only presents some concepts of the present disclosure as a preface to the more detailed description provided thereafter.

[0005] In one aspect, the present disclosure relates to a non-transitory computer-readable storage medium configured to be attached to a communication device for wireless communication, the storage medium comprising: a memory storing a plurality of profiles, each of the plurality of profiles comprising data allowing the communication device to access a corresponding wireless network; and instructions implementing a universal integrated circuit card (UICC), the instructions being executable by one or more processors so that the one or more processors: provide a list to the communication device, the list indicating i) available profiles from the plurality of profiles, and ii) currently enabled public network profiles from the plurality of profiles, wherein the available profiles include at least a private network profile specified with a fallback attribute; receive a fallback trigger from the communication device to enable the fallback profile corresponding to the fallback attribute; and in response to the fallback trigger: identify the private network profile as the fallback profile corresponding to the fallback attribute; disable the public network profile; enable the private network profile; and send a refresh command to the communication device, wherein the refresh command is used to cause the communication device to authenticate to the private wireless network corresponding to the private network profile.

[0006] In another aspect, the present disclosure relates to a non-transitory computer-readable storage medium configured to be attached to a communication device for wireless communication, the storage medium comprising: a memory storing a plurality of profiles, each of the plurality of profiles comprising data allowing the communication device to access a corresponding wireless network; and instructions implementing a universal integrated circuit card (UICC), the instructions being executable by one or more processors so that the one or more processors: provide a list to the communication device, the list indicating i) available profiles from the plurality of profiles, and ii) currently enabled private network profiles from the plurality of profiles, wherein the available profiles include at least a public network profile specified with a fallback attribute; receive a fallback trigger from the communication device to enable the fallback profile corresponding to the fallback attribute; and in response to the fallback trigger: identify the public network profile as the fallback profile corresponding to the fallback attribute; disable the private network profile; enable the public network profile; and send a refresh command to the communication device, wherein the refresh command is used to cause the communication device to authenticate to the public wireless network corresponding to the public network profile.

[0007] In yet another aspect, the present disclosure relates to a method implemented by a universal integrated circuit card (UICC) installed in a communication device, the method comprising: providing a list to the communication device, the list indicating i) available profiles from a plurality of profiles that allow the communication device to access a corresponding wireless network, and ii) a currently enabled public network profile from a plurality of profiles, wherein the available profiles include at least a private network profile specified with a fallback attribute; receiving a fallback trigger from the communication device to enable a fallback profile corresponding to the fallback attribute; and in response to receiving the fallback trigger: identifying the private network profile as a fallback profile corresponding to the fallback attribute; disabling the public network profile; enabling the private network profile; and sending a refresh command to the communication device, wherein the refresh command is used to cause the communication device to authenticate to the private wireless network corresponding to the private network profile.

[0008] Further applicability of the apparatus and method of the present disclosure will become apparent from the more detailed description given below. However, it should be understood that the following detailed description and specific examples, although indicating embodiments of the apparatus and method, are given by way of illustration only, as various changes and modifications within the spirit and scope of the concepts disclosed herein will become apparent to those skilled in the art from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] These and / or other aspects will become apparent and more readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0010] Figure 1 is a block diagram illustrating an example operating environment for one or more embodiments described herein.

[0011] Figure 2 is a block diagram illustrating an example universal integrated circuit card according to one or more embodiments described herein.

[0012] Figure 3 is a diagram illustrating example data flows, states, and operations for converting a fallback network profile according to one or more embodiments described herein.

[0013] Figure 4 is a diagram illustrating example data flows, states, and operations for transitioning a switchback network profile according to one or more embodiments described herein.

[0014] Figure 5 is a flow chart illustrating an example method for converting a fallback private network profile according to one or more embodiments described herein.

[0015] Figure 6is a flow chart illustrating an example method for converting a fallback public network profile according to one or more embodiments described herein.

[0016] The headings provided herein are for convenience only and do not necessarily affect the scope or meaning of what is claimed in the disclosure.

[0017] Embodiments of the present disclosure and their advantages may be best understood by reference to the detailed description below. It should be understood that the same reference numerals are used to identify the same elements shown in one or more of the accompanying drawings, wherein the illustrations are for the purpose of illustrating the embodiments of the present disclosure, rather than for the purpose of limiting the embodiments of the present disclosure. DETAILED DESCRIPTION

[0018] Various examples and embodiments of the present disclosure will now be described. The following description provides specific details for a thorough understanding and implementation of the description of these examples. However, it will be appreciated by those of ordinary skill in the relevant art that one or more embodiments described herein may be practiced without many of these details. Similarly, it will be appreciated by those of ordinary skill in the relevant art that one or more embodiments of the present disclosure may include other features and / or functions not described in detail herein. In addition, some well-known structures or functions may not be shown or described in detail below to avoid unnecessarily obscuring the relevant description.

[0019] Embodiments of the present disclosure relate to methods, systems, and devices for selecting or switching between wireless network profiles. In one example, a communication device for wireless communication (e.g., an IoT device) may be configured to trigger one or more functions that cause a UICC (e.g., an eUICC, an integrated UICC (iUICC), etc.) installed in the communication device to switch or convert from a currently enabled network profile to another network profile corresponding to a different wireless network available to the device without requiring backend operations (e.g., without requiring operations of a remote server).

[0020] It should be noted that while one or more embodiments described herein refer to implementation in an eUICC, aspects of the present disclosure may alternatively be applied to a physical UICC chip and / or an iUICC. An iUICC is a tamper-proof element within a system-on-chip (SoC). Also known as an integrated SIM (iSIM), an iUICC is an isolated hardware component that is combined with a baseband chipset to create a single connected module.

[0021] In one embodiment, a function may be provided to notify the communication device of available networks from which it can choose. Such a function allows instantaneous switching of network profiles without the need for backend operations. In one example, the communication device may be able to detect the signal strength of the available networks. With this capability, combined with the network information provided by the eUICC, the communication device will be able to determine which network to use in a significantly faster manner than the mechanism used by the eUICC. It should be understood that the communication device and the eUICC do not explicitly select a network. Instead, in one embodiment, the conversion function described herein may enable the communication device to trigger an event (sometimes referred to herein as a "fallback trigger") that will cause the eUICC to switch (or "fall back") from the currently enabled public network profile to the private network profile. In addition, the conversion function described herein may enable the communication device to trigger an event (sometimes referred to herein as a "fallback trigger") that will cause the eUICC to switch (or "switched back") from the currently enabled private network profile to the previously enabled public network profile (sometimes referred to as an "anchor" profile).

[0022] As will be described in more detail herein, in one or more embodiments, the eUICC is configured to provide a plurality of different functions that can be invoked or triggered by a communication device. In one example, the communication device can trigger a fallback function within the eUICC. If the fallback function is triggered within the eUICC, the eUICC will switch from a currently enabled network profile to a fallback network profile. For example, in one embodiment, if the fallback function is triggered within the eUICC, the eUICC will switch from a currently enabled public network profile to a private network profile. The private network profile (which may be considered a "fallback network profile" in this scenario) corresponds to a private network currently available to the communication device. In another embodiment, if the fallback function is triggered within the eUICC, the eUICC will switch from a currently enabled private network profile to a public network profile. The public network profile, which may be considered a "fallback network profile" in this example, corresponds to a public network currently available to the communication device.

[0023] It should be understood that according to at least one embodiment, the fallback trigger and the switchback trigger may be the same instruction to the eUICC. For example, the eUICC may be configured to determine whether the received instruction triggers the fallback function or the switchback function based on the current configuration of the eUICC. In one example, if the fallback network profile is currently enabled, the eUICC regards the received instruction as a switchback trigger. In another example, if a public network profile (which is not a fallback network profile) is currently enabled, the instruction received by the eUICC may be interpreted as a fallback trigger in this context.

[0024] In one example, at a certain time point after the fallback function in the eUICC is triggered, the communication device may trigger the switchback function in the eUICC. If the switchback function is triggered in the eUICC, the eUICC will switch from the currently enabled network profile back to the previously enabled network profile. For example, in one embodiment, if the switchback function is triggered in the eUICC, the eUICC will switch from the currently enabled private network profile back to the previously enabled public network profile. The public network profile that may be considered as a "switchback network profile" or "anchor network profile" in this scenario corresponds to a public network that may have been previously available to the communication device and is now currently available to the communication device. In another embodiment, if the switchback function is triggered in the eUICC, the eUICC will switch from the currently enabled public network profile to the previously enabled private network profile. The private network profile (which may be considered as a "switchback network profile" or "anchor network profile" in this example) corresponds to a private network that may have been previously available to the communication device and is now currently available to the communication device. It should be noted that although either a private network or a public network can be used as a fallback network, in at least some embodiments, having a private network as the fallback network is preferred because it allows for easier provisioning of a new public network.

[0025] In one embodiment, the eUICC is configured to provide a list of available profiles to the communication device. For example, the communication device may trigger a profile list function within the eUICC. If the communication device triggers the profile list function in the eUICC (e.g., by sending a "GetProfileList" request to the eUICC), the eUICC will provide the communication device with a list of all network profiles available on the eUICC. In one example, the network profile list provided by the eUICC to the communication device includes at least a fallback network profile and a switchback network profile. Depending on the implementation, other network profiles available on the eUICC may or may not be masked. In one embodiment, in the profile list provided by the eUICC to the communication device, the fallback network profile and / or the switchback network profile may be marked or otherwise identified to inform the communication device about which network profiles the communication device can convert locally using the above functions (e.g., fallback and switchback functions). In one example, the profile list provided by the eUICC may include a mobile country code and / or a mobile network code for each network corresponding to the network profile in the list. In one example, the profile list may also include extended information about one or more private network profiles in the list of available profiles.

[0026] In at least one embodiment, the profile list provided by the eUICC to the communication device may include information related to the last network profile switch that occurred. For example, the profile list may include information indicating whether the last network profile switch that occurred in the eUICC was triggered via a function of the communication device or via a backend (e.g., a remote server). In an embodiment, the profile list maintained by the eUICC may be updated by the eUICC in response to an operation performed by a network backend (e.g., a remote server). As an example, the backend may cause the eUICC to download and enable a new network profile. After such an operation, the eUICC may update the profile list to include the newly enabled network profile. In such an example, the newly enabled network profile may become a new anchor network profile.

[0027] In one embodiment, in addition to or instead of the above functions, the eUICC may also provide one or more other functions. For example, the eUICC may provide information about a preferred subscription list. The preferred subscription list may contain information such as a roaming list, which informs the communication device which subscription to use in which network (region). Such a list may include a list of subscriptions that are available and mapped to their mobile country codes that should be used. For private networks, additional location information may also be included in the list.

[0028] Figure 1 An example operating environment 100 for one or more embodiments described herein is shown. The example environment 100 includes multiple networks, including a public LTE network 130, a private LTE network 140, and a WiFi network 150. In an embodiment, a motor vehicle 120 (e.g., a truck, a car, etc.) can travel within and between various wireless networks. The vehicle 120 can have a communication device 110 (e.g., an IoT device) installed therein for wireless communication, the communication device 110 including a radio transceiver 112 and a profile manager 114. The profile manager 114 can be, for example, an eUICC.

[0029] Figure 2An example eUICC according to one or more embodiments described herein is shown. In one embodiment, the eUICC 230 is configured to communicate with the radio transceiver 212 via an application programming interface (API) 216. The eUICC 230 may include an eUICC operating system (OS) 220, an issuer security domain root (ISD-R) 232, and multiple network profiles (e.g., fallback profiles and / or fallback / anchor profiles). Each network profile may include an issuer security domain profile (ISD-P) 234 / 236 / 238, a security domain (such as a private LTE security domain or a public mobile network operator security domain (MNO SD) 242 / 244 / 246), and various applets, rules, and storage. In one example, a network profile is a combination of file structures, data, and applications to be assigned to or present on the eUICC 230, and which, when enabled, allows access to a specific mobile network infrastructure.

[0030] GSMA specification SGP.22RSP Technical Specification Version 2.2.2 June 5, 2020 (or SGP.22 for short) describes remote SIM provisioning by downloading a profile to an embedded universal integrated circuit card eUICC hosted in a device. The device is understood to be a mobile device or mobile terminal, such as, for example, a device or terminal having the ability to communicate in a mobile network (e.g., a wireless network). At the time of subscription by a terminal user at a mobile network operator (operator or MNO, which is an entity that provides access capabilities and communication services to its customers through a mobile network infrastructure), a ready-made profile already stored at a profile provisioning server (e.g., SM-DP+) is reserved. Thereafter, a mutual authentication process between the profile provisioning server SM-DP+ and the eUICC is performed. Thereafter, the reserved profile is downloaded to the eUICC via the device and installed in the eUICC.

[0031] Within the eUICC 230, each profile is contained in a separate Issuer Security Domain Profile (ISD-P) 234 / 236 / 238. Each ISD-P 234 / 236 / 238 contains one profile. The profile has the main technical service task of authenticating the eUICC 230 and / or its device and / or its end user to the mobile network associated with the profile. The ISD-P234 / 236 / 238 or profile may contain additional elements such as applets and applications. The applets and applications may have service purposes beyond authentication to the mobile network, such as payment services or ticketing services. In particular, near field communication NFC payment services may be implemented by NFC payment applets or applications in the profile or ISD-P. Currently, the applets and applications provided for downloading to the ISD-P are also static and ready-made. The profile (or general content) to be downloaded to the eUICC 230 in the case of a remote SIM assignment session is downloaded to the eUICC 230 in the form of a binding profile package BPP. The Binding Profile Package contains a Tag Length Value (TLV) sequence, commands for installing in the following order: (1) ISD-P with ISD-P configuration, (2) metadata, (3) Profile Protection Keys, (4) the actual profile payload in the form of a Protected Profile Package, all within the eUICC.

[0032] Figure 3 Example data flows, states, and operations for converting a fallback network profile according to an embodiment are shown. Figure 3 In the example shown, data flows occur between the communication device 310, the eUICC 320, and the subscription manager secure routing (SM-SR) device 330, and operations are performed by the communication device 310, the eUICC 320, and the subscription manager secure routing (SM-SR) device 330. In one embodiment, the communication device 310 may be similar to Figure 1 The communication device 110 shown and described above, and the eUICC 320 may be similar to Figure 2 The eUICC 230 is shown and described in detail above.

[0033] In an example, a public network profile may be currently enabled (340) in the eUICC 320. Because the public network profile is the currently enabled network profile, the communication device 310 (e.g., a modem in the communication device 310) may attempt to authenticate using the public network profile (342). The public network profile may correspond to a public wireless network that is available or unavailable (344) to the communication device 310. The communication device 310 may send a request for available network profiles to the eUICC 320 (346). In an example, the communication device 310 may send a "GetProfileList" request to the eUICC 320. In response to receiving the request for available network profiles (346) from the communication device 310, the eUICC 320 may provide the communication device 310 with a list of all network profiles available on the eUICC (348). In an example, the list of available network profiles provided by the eUICC 320 may include an indication that the public network profile is the currently enabled network profile. In another example, the list of available network profiles provided by the eUICC 320 to the communication device 310 includes at least the currently enabled public network profile and at least the private network profile with the fallback attribute specified. In another example, the list of available network profiles provided by the eUICC 320 to the communication device 310 includes at least the fallback network profile and the currently enabled public network profile (which is the "switching back network profile" in this example), and the fallback network profile and / or the switching back network profile may be marked or otherwise identified to inform the communication device 310 which network profiles it can locally switch to using the fallback and switching back functions, which has been described in detail above.

[0034] The communication device 310 may be configured to scan for available wireless networks, and may detect an available private wireless network (350). In one example, the communication device 310 may periodically check whether the private wireless network is available, or whether another wireless network preferred based on the location of the communication device 310 is available. In one example, the private wireless network may be prioritized over the public wireless network. In another example, the public wireless network may be prioritized over the private wireless network. If the communication device 310 determines that the detected private wireless network should be used, the communication device 310 may send a fallback trigger (352) to the eUICC 320 to trigger the fallback function and cause the eUICC 320 to switch to the private network profile. In one example, the communication device 310 may determine whether the detected private wireless network should be used based on information provided by the eUICC 320 (e.g., a preferred network list and / or a profile list). In one example, the fallback trigger (352) may be sent to the eUICC 320 to trigger the fallback function to enable the fallback network profile corresponding to the fallback attribute. In response to receiving the fallback trigger (352) from the communication device 310, the eUICC 320 may identify the private network profile (corresponding to the private wireless network detected by the communication device 310) as the fallback network profile corresponding to the fallback attribute, disable the currently enabled public network profile, and enable the private network profile (354). Once the eUICC 320 has enabled the fallback network profile (private network profile), the eUICC 320 may send a refresh command (356) to the communication device 310. In an example, the refresh command (356) sent by the eUICC 320 to the communication device 310 is configured to cause the communication device 310 to authenticate to the private wireless network corresponding to the fallback network profile (private network profile) (358).

[0035] In one embodiment, after the communication device 310 has authenticated to the private wireless network (358), the eUICC 320 may perform a fallback notification procedure (360) with the SM-SR device 330. In one example, the notification procedure may be performed in accordance with GSMA SGP.02.

[0036] Figure 4 Figure 2 shows example data flows, states, and operations for converting a switchback network profile according to an embodiment. Figure 4 In the example shown, data flows occur between the communication device 410, the eUICC 420, and the subscription manager secure routing (SM-SR) device 430, and operations are performed by the communication device 410, the eUICC 420, and the subscription manager secure routing (SM-SR) device 430. In one embodiment, the communication device 410 may be similar to Figure 1 and Figure 3 The communication device 110 and / or 310 shown in FIG. 1 and described in detail above. The eUICC 420 may be similar to Figure 2 and Figure 3 The eUICC 230 and / or 320 shown in FIG. 1 and described in detail above.

[0037] like Figure 4 As shown, a private network profile may now be enabled (440) in the eUICC 420. In one example, the private network profile may be Figure 3 For example, the currently enabled private network profile may correspond to the fallback network profile configured by Figure 3 The communication device 310 in the embodiment of the present invention detects a private wireless network of (350). Because the private network profile is a currently enabled network profile, the communication device 410 (e.g., a modem in the communication device 410) may attempt to authenticate using the private network profile (442). The private network profile may correspond to a private wireless network that is currently available or unavailable to the communication device 410 (e.g., 444). The communication device 410 may send a request for available network profiles to the eUICC 420 (446). In an example, the communication device 410 may send a "GetProfileList" request to the eUICC 420. In another example, the "GetProfileList" may be cached within the communication device 410. In response to receiving the request for available network profiles (446) from the communication device 410, the eUICC 420 may provide the communication device 410 with a list of all network profiles available on the eUICC (448). In one example, the list of available network profiles provided by the eUICC 420 may include an indication that the private network profile is a currently enabled network profile. In another example, the available network profile list provided by the eUICC 420 to the communication device 410 includes at least a currently enabled private network profile and at least a previously enabled public network profile (in this example, a “switchback network profile”).

[0038] The communication device 410 may detect a loss of connection with the private wireless network (450). In one example, the communication device 410 may scan for any other private wireless networks that are available, or check whether a preferred private wireless network is available based on the location of the communication device 410. If the communication device 410 cannot detect another available private wireless network, the communication device 410 may send a switchback trigger (452) to the eUICC 420 to trigger the switchback function and cause the eUICC 420 to switch back to the previously enabled public network profile. It should be noted that while in one or more embodiments, the switchback function may be separated from the fallback function, in one or more other embodiments, the switchback function and the fallback function may be combined. In this case, the communication device 410 will simply trigger the "lost network" function, which will then trigger a switch or fallback based on the current state in the eUICC 420.

[0039] In response to receiving a switchback trigger (452) from the communication device 410, the eUICC 420 may switch the previously enabled public network profile (e.g., Figure 3 The eUICC 420 may identify the currently enabled public network profile (340) in the communication device 410 as the fallback network profile, disable the currently enabled private network profile, and enable the fallback public network profile (454). Once the eUICC 420 has enabled the fallback network profile (public network profile), the eUICC 420 may send a refresh command (456) to the communication device 410. In an example, the refresh command (456) sent by the eUICC 420 to the communication device 410 is configured to cause the communication device 410 to authenticate to the public wireless network corresponding to the fallback network profile (public network profile) (458).

[0040] In one embodiment, after the communication device 410 has authenticated to the public wireless network (458), the eUICC 420 may perform a switchback notification procedure (460) with the SM-SR device 430. In one example, the notification procedure may be performed according to GSMA SGP.02.

[0041] Figure 5 An example process 500 for converting a fallback private network profile according to an embodiment is shown. In one example, the process 500 may be performed by an eUICC installed in a communication device (e.g., an IoT device). For example, in one embodiment, the process 500 may be performed by Figures 2 to 4 The eUICC 230, 320 or 420 shown in FIG. 1 is executed, and the eUICC may be installed in a communication device (e.g., Figure 1 , Figure 3 and Figure 4In one example, the eUICC may store (e.g., in a memory) one or more network profiles, each of which includes data that allows the communication device to access a corresponding wireless network. In another embodiment, the example process 500 may be performed by another component of the communication device for wireless communication.

[0042] At step 502, a list of available network profiles from among a plurality of network profiles that may be stored is provided to the communication device. In an example, the list of available network profiles may include an indication of a currently enabled public network profile from among the plurality of profiles. In an example, the list of available network profiles may include at least a private network profile that specifies a fallback attribute and a currently enabled public network profile.

[0043] In one embodiment, in response to receiving a request for available profiles from the communication device, a list of available network profiles may be provided at step 502. In one example, a request for available network profiles may be received from the communication device when the communication device is connected to a public wireless network corresponding to a public network profile.

[0044] At step 504, a fallback trigger (or loss of connectivity trigger) may be received from the communication device. In an example, the fallback trigger is used to enable a fallback network profile corresponding to the fallback attribute. At step 506, in response to receiving the fallback trigger at step 504, a private network profile may be identified as the fallback profile corresponding to the fallback attribute. At step 508, the public network profile may be disabled, and at step 510, the private network profile may be enabled.

[0045] At step 512, a refresh command may be sent to the communication device. In one example, the refresh command is used to cause the communication device to authenticate to the private wireless network corresponding to the private network profile.

[0046] In one embodiment, after the communication device is authenticated with the private wireless network, a notification process may be performed using a Subscription Manager Secure Routing (SM-SR) device.

[0047] Figure 6 An example process 600 for converting a fallback public network profile according to an embodiment is shown. In one embodiment, the process 600 can be substantially similar to that described above and in Figure 55. However, when the public network profile is a fallback profile, there is a difference in how the new profile is assigned. For example, if a new public network profile is downloaded and enabled, the fallback attributes also need to be set for the new profile to make it a fallback profile. This is an additional step that is not required when the private network profile is a fallback profile.

[0048] In one example, process 600 may be performed by an eUICC installed in a communication device (e.g., an IoT device). Figures 2 to 4 The eUICC 230, 320 or 420 shown in FIG. 1 is executed, and the eUICC may be installed in a communication device (e.g., Figure 1 , Figure 3 and Figure 4 In one example, the eUICC may store (e.g., in a memory) one or more network profiles, each of which includes data that allows the communication device to access a corresponding wireless network. In another embodiment, the example process 600 may be performed by another component of the communication device for wireless communication.

[0049] At step 602, a list of available network profiles from among a plurality of network profiles that may be stored is provided to the communication device. In an example, the list of available network profiles may include an indication of a currently enabled private network profile from among the plurality of profiles. In an example, the list of available network profiles may include at least a public network profile that specifies a fallback attribute and a currently enabled private network profile.

[0050] In one embodiment, the list of available network profiles may be provided in response to receiving a request for available profiles from the communication device at step 602. In one example, the request for available network profiles may be received from the communication device when the communication device is connected to a private wireless network corresponding to a private network profile.

[0051] At step 604, a fallback trigger may be received from the communication device. In an example, the fallback trigger is used to enable a fallback network profile corresponding to the fallback attribute. At step 606, in response to receiving the fallback trigger at step 604, a public network profile may be identified as the fallback profile corresponding to the fallback attribute. At step 608, the private network profile may be disabled, and at step 610, the public network profile may be enabled.

[0052] At step 612, a refresh command may be sent to the communication device. In one example, the refresh command is used to cause the communication device to authenticate to a public wireless network corresponding to a public network profile.

[0053] In one embodiment, after the communication device is authenticated with the private wireless network, a notification process may be performed using a Subscription Manager Secure Routing (SM-SR) device.

[0054] At least some of the various blocks, operations, and techniques described above may be implemented using hardware, a processor executing firmware instructions, a processor executing software instructions, or any combination thereof. When implemented using a processor executing software or firmware instructions, the software or firmware instructions may be stored in any non-transitory computer-readable memory, such as on a disk, optical disk, or other storage medium, in RAM or ROM or flash memory, a processor, a hard drive, an optical drive, a tape drive, etc. The software or firmware instructions may include machine-readable instructions that, when executed by one or more processors, cause the one or more processors to perform various actions such as those described above.

[0055] When implemented in hardware, the hardware may include one or more of discrete components, integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), and the like.

[0056] All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.

[0057] In order to promote the understanding of the principles of the present invention, reference has been made to the embodiments shown in the accompanying drawings, and specific language has been used to describe these embodiments. However, this specific language is not intended to limit the scope of the present invention, and the present invention should be interpreted as covering all embodiments that a person of ordinary skill in the art would normally think of. Unless otherwise stated, the description of the features or aspects in each embodiment should generally be considered to be applicable to other similar features or aspects in other embodiments. The terms used herein are for the purpose of describing specific embodiments, and are not intended to limit exemplary embodiments of the present invention. In the description of the embodiments, when it is believed that some detailed explanations of the related art may unnecessarily obscure the essence of the present invention, some detailed explanations of the related art are omitted.

[0058] Unless otherwise stated, the use of any and all examples or exemplary language (e.g., "such as") provided herein is intended only to better illustrate the present invention and does not limit the scope of the present invention. Many modifications and adaptations will be apparent to those of ordinary skill in the art without departing from the scope of the present invention as defined by the appended claims. Therefore, the scope of the present invention is defined not by the detailed description of the present invention, but by the appended claims, and all differences within the scope will be construed as included in the present invention.

[0059] Unless an element is specifically described as "essential" or "critical", no item or component is essential for the practice of the present invention. It will also be recognized that the terms "comprises", "comprising", "includes", "including", "has" and "having" as used herein are specifically intended to be interpreted as open technical terms. Unless the context clearly indicates otherwise, the use of the terms "one" and "a kind of" and "the" and similar indicators in the context of describing the present invention (particularly in the context of the appended claims) should be interpreted as covering the singular and plural. In addition, it should be understood that although the terms "first", "second", etc. can be used herein to describe various elements, these elements should not be limited by these terms, which are only used to distinguish one element from another. In addition, unless otherwise specified herein, the description of the numerical range herein is only intended to be used as a shorthand method for individually referring to each individual value falling within the range, and each individual value is incorporated into this specification as if it were individually described herein.

Claims

1. A non-transitory computer-readable storage medium configured to be attached to a communication device for wireless communication, the storage medium comprising: a memory storing a plurality of configuration files, each of the plurality of configuration files comprising data allowing access to a corresponding wireless network by the communication device; as well as Instructions for implementing a universal integrated circuit card (UICC), the instructions being executable by one or more processors to cause the one or more processors to: providing a list to the communication device, the list indicating i) available profiles from the plurality of profiles, and ii) currently enabled public network profiles from the plurality of profiles, wherein the available profiles include at least a private network profile that specifies a fallback attribute; receiving a fallback trigger from the communication device to enable a fallback profile corresponding to the fallback attribute; In response to the fallback trigger: identifying the private network profile as the fallback profile corresponding to the fallback attribute; disabling said public network profile; activating the private network configuration file; and A refresh command is sent to the communication device, wherein the refresh command is used to enable the communication device to authenticate the private wireless network corresponding to the private network profile.

2. The computer-readable storage medium according to claim 1, wherein: The instructions further cause the one or more processors to: When the communication device is connected to a public wireless network corresponding to the public network profile, a request for the available profile is received.

3. The computer-readable storage medium according to claim 2, wherein: The instructions further cause the one or more processors to: receiving a switchback trigger from the communication device for re-enabling the public network profile; In response to the switchback trigger: Identifying the public network profile as a switchback network profile; disabling the private network profile; enabling the public network profile; as well as Another refresh command is sent to the communication device, wherein the another refresh command is used to cause the communication device to authenticate to the public wireless network corresponding to the public network profile.

4. The computer-readable storage medium according to claim 3, wherein: The switchback trigger corresponds to a connection loss between the communication device and the private wireless network.

5. The computer-readable storage medium according to claim 1, wherein: The UICC is one of: (i) an embedded UICC (eUICC), and (ii) an integrated UICC (iUICC).

6. The computer-readable storage medium according to claim 3, wherein: The instructions further cause the one or more processors to: After authentication by the communication device to the public wireless network, a notification procedure is performed with a Subscription Manager Secure Routing (SM-SR) device.

7. The computer-readable storage medium of claim 3, wherein: The public network profile is a first public network profile; and The instructions further cause the one or more processors to: The Subscription Manager Secure Routing (SM-SR) device performs the download and enablement process, including: receiving a second public network profile from the SM-SR device; storing the second public network configuration file as one of the plurality of configuration files in the memory; disabling the first public network profile; enabling the second public network profile; and The refresh command is sent to the communication device, wherein the refresh command is used to enable the communication device to authenticate to a second wireless network corresponding to the second public network profile.

8. The computer-readable storage medium of claim 1, wherein: The instructions further cause the one or more processors to: After the communication device is authenticated to the private wireless network, a notification process is performed with a subscription manager secure routing (SM-SR) device.

9. A non-transitory computer-readable storage medium configured to be attached to a communication device for wireless communication, the storage medium comprising: a memory storing a plurality of configuration files, each of the plurality of configuration files comprising data allowing access to a corresponding wireless network by the communication device; as well as Instructions for implementing a universal integrated circuit card (UICC), the instructions being executable by one or more processors to cause the one or more processors to: providing a list to the communication device, the list indicating i) available profiles from the plurality of profiles, and ii) currently enabled private network profiles from the plurality of profiles, wherein the available profiles include at least a public network profile that specifies a fallback attribute; receiving a fallback trigger from the communication device to enable a fallback profile corresponding to the fallback attribute; In response to the fallback trigger: identifying the public network profile as the fallback profile corresponding to the fallback attribute; disabling the private network profile; enabling the public network profile; and A refresh command is sent to the communication device, wherein the refresh command is used to enable the communication device to authenticate to the public wireless network corresponding to the public network profile.

10. The computer-readable storage medium of claim 9, wherein: The instructions further cause the one or more processors to: When the communication device is connected to a private wireless network corresponding to the private network profile, a request for the available profile is received.

11. The computer-readable storage medium of claim 10, wherein: The instructions further cause the one or more processors to: receiving a switchback trigger for re-enabling the private network profile from the communication device; In response to the switchback trigger: Identify the private network configuration file as a switchback network configuration file; disabling said public network profile; Activate the private network configuration file; as well as Another refresh command is sent to the communication device, wherein the another refresh command is used to enable the communication device to authenticate to the private wireless network corresponding to the private network profile.

12. The computer-readable storage medium of claim 11, wherein: The switchback trigger corresponds to a connection loss between the communication device and the public wireless network.

13. The computer-readable storage medium of claim 9, wherein: The UICC is one of: (i) an embedded UICC (eUICC), and (ii) an integrated UICC (iUICC).

14. The computer-readable storage medium of claim 11, wherein: The instructions further cause the one or more processors to: After the communication device is authenticated to the private wireless network, a notification process is performed with a subscription manager secure routing (SM-SR) device.

15. The computer-readable storage medium of claim 11, wherein: The private network configuration file is a first private network configuration file; and The instructions further cause the one or more processors to: The Subscription Manager Secure Routing (SM-SR) device performs the download and enablement process, including: receiving a second private network configuration file from the SM-SR device; storing the second private network configuration file in the memory as one of the plurality of configuration files; disabling the first private network configuration file; activating the second private network profile; and The refresh command is sent to the communication device, wherein the refresh command is used to enable the communication device to authenticate to a second wireless network corresponding to the second private network profile.

16. The computer-readable storage medium of claim 9, wherein: The instructions further cause the one or more processors to: After authentication by the communication device to the public wireless network, a notification procedure is performed with a Subscription Manager Secure Routing (SM-SR) device.

17. A method implemented by a universal integrated circuit card (UICC) installed in a communication device, the method comprising: providing a list to the communication device, the list indicating i) available profiles from a plurality of profiles that allow access to a corresponding wireless network by the communication device, and ii) currently enabled public network profiles from the plurality of profiles, wherein the available profiles include at least a private network profile that specifies a fallback attribute; receiving a fallback trigger from the communication device to enable a fallback profile corresponding to the fallback attribute; In response to receiving the fallback trigger: identifying the private network profile as the fallback profile corresponding to the fallback attribute; disabling said public network profile; activating the private network configuration file; and A refresh command is sent to the communication device, wherein the refresh command is used to enable the communication device to authenticate the private wireless network corresponding to the private network profile.

18. The method according to claim 17, further comprising: A request for the available profile is received from the communication device, wherein the request for the available profile is received while the communication device is connected to a public wireless network corresponding to the public network profile.

19. The method according to claim 18, further comprising: receiving a switchback trigger from the communication device for re-enabling the public network profile; In response to receiving the switchback trigger: Identifying the public network profile as a switchback network profile; disabling the private network profile; enabling the public network profile; as well as Another refresh command is sent to the communication device, wherein the another refresh command is used to cause the communication device to authenticate to the public wireless network corresponding to the public network profile.

20. The method according to claim 19, wherein: The UICC is one of (i) an embedded UICC (eUICC) and (ii) an integrated UICC (iUICC).

Images