Techniques for concurrently managing different contexts for an electronic subscriber identity module

Abstract

This application sets forth techniques for managing both a consumer context and an IoT context with respect to utilizing at least one consumer-related electronic Subscriber Identity Module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively. According to some embodiments, the method can be implemented by a wireless device and includes providing a terminal capability command to an embedded Universal Integrated Circuit Card (eUICC) included in the wireless device that indicates that both the consumer context and the IoT context should be managed. In turn, the wireless device can provide a function call to the eUICC, where the function call is accompanied by context information to indicate the context (i.e., consumer or IoT) under which the function call should be handled. Additionally, the wireless device can provide a context switch (i.e., consumer or IoT) command to the eUICC to cause the eUICC to utilize a particular context when handling the function call (prior to receiving a further notification).

Description

Technical Field

[0001] The described implementation scheme illustrates techniques for concurrently managing different contexts for an electronic subscriber identity module (eSIM). Specifically, these techniques include managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively. Background Technology

[0002] Many wireless devices are configured to use a removable Universal Integrated Circuit Card (UICC), which enables the wireless device to access services provided by a Mobile Network Operator (MNO). Specifically, each UICC includes at least a microprocessor and a read-only memory (ROM) configured to store an MNO profile, which the wireless device can use to register and interact with the MNO to obtain wireless services via a cellular network. The MNO profile may also be referred to as a Subscriber Identity Module (SIM). Typically, the UICC takes the form of a small, removable card (often called a SIM card) inserted into the UICC receiver area of ​​the wireless device. In more recent implementations, the UICC is embedded directly into the system board of the wireless device as an embedded UICC (eUICC), which offers advantages over traditional removable UICCs. The eUICC may include rewritable memory that facilitates the installation, modification, and / or removal of one or more electronic SIMs (eSIMs) on the eUICC, which can provide new and / or different services and / or updates for accessing extended features provided by the MNO. eUICC can store several MNO profiles (also referred to as eSIM in this document) and eliminates the need to include the UICC receive area in the wireless device. Recently, integrated SIM (iSIM) has been proposed as a type of SIM that is directly integrated into the device hardware (e.g., the device processor and / or attached memory and / or system-on-chip (SoC) components) without using a separate eUICC to store the iSIM.

[0003] In some cases, it may be desirable for certain devices (such as vehicles) to provide both consumer-related eSIM functionality (e.g., phone calls, internet access) and Internet of Things (IoT)-related eSIM functionality (e.g., diagnostic reports, location services). Unfortunately, with current methods, a given eUICC can only manage a single context (i.e., a consumer context or an IoT context) during operation, thus limiting the eUICC to providing only consumer-related or IoT-related functionality at a time. Furthermore, transitions between different contexts require a complete reset of the eUICC, leading to operational inefficiencies, communication interruptions, etc. Therefore, there is a need to improve how the eUICC manages different contexts so that consumer-related / IoT-related eSIM functionality can be accessed efficiently. Summary of the Invention

[0004] The described implementation scheme illustrates techniques for concurrently managing different contexts for an electronic subscriber identity module (eSIM). Specifically, these techniques include managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively.

[0005] One embodiment describes a method for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively. According to some embodiments, the method can be implemented by a wireless device and includes the steps of: (1) providing an embedded universal integrated circuit card (eUICC) included in the wireless device with terminal capability commands instructing that both the consumer context and the IoT context should be managed; (2) providing the eUICC with at least one first function call instructing the consumer context, wherein the consumer context causes the eUICC, based on the consumer context and at least one consumer-related eSIM, to: (i) process at least one first function call, and (ii) provide at least one first response to at least one first function call; and (3) providing the eUICC with at least one second function call instructing the IoT context, wherein the IoT context causes the eUICC, based on the IoT context and at least one IoT-related eSIM, to: (i) process at least one second function call, and (ii) provide at least one second response to at least one second function call.

[0006] Another implementation describes a method for managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively. According to some implementations, the method can be implemented by a wireless device and includes the following steps: (1) providing an embedded universal integrated circuit card (eUICC) included in the wireless device with a terminal capability command indicating that both the consumer context and the IoT context should be managed; (2) identifying at least one first condition, under which at least one first condition is invoked at least one first function related to the consumer context; (3) providing the eUICC with a consumer context switching command that causes the eUICC, based on the consumer context and at least one consumer-related eSIM, to: (i) process a specific function call including the first function call, and (ii) provide a first response to the specific function call before receiving further notification; (4) identifying at least one second condition, under which at least one second condition is invoked at least one second function related to the IoT context; (5) providing the eUICC with an IoT context switching command that causes the eUICC, based on the IoT context and at least one IoT-related eSIM, to: (i) process a specific function call including the second function call, and (ii) provide a second response to the specific function call before receiving further notification.

[0007] Another embodiment describes a method for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively. According to some embodiments, the method can be implemented by an embedded universal integrated circuit card (eUICC) and includes the steps of: (1) receiving from a wireless device a terminal capability command indicating that both the consumer context and the IoT context should be managed; (2) receiving from the wireless device at least one first function call indicating the consumer context; (3) based on the consumer context and at least one consumer-related eSIM: (i) processing at least one first function call, and (ii) providing the wireless device with at least one first response to the at least one first function call; (4) receiving from the wireless device at least one second function call indicating the IoT context; and (5) based on the IoT context and at least one IoT-related eSIM: (i) processing at least one second function call, and (ii) providing the wireless device with at least one second response to the at least one second function call.

[0008] Another implementation describes a method for managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively. According to some implementations, the method can be implemented by an embedded universal integrated circuit card (eUICC) and includes the following steps: (1) receiving from a wireless device a terminal capability command indicating that both the consumer context and the IoT context should be managed; (2) receiving from the wireless device a consumer context switching command, wherein the consumer context switching command is provided in response to the wireless device identifying at least one first condition, under which at least one first function related to the consumer context is invoked; (3) based on the consumer context and at least one consumer-related eSIM, and before receiving further notification: (i) processing a specific function call including the first function call, and (ii) providing a first response to the specific function call; (4) receiving from the wireless device an IoT context switching command, wherein the IoT context switching command is provided in response to the wireless device identifying at least one second condition, under which at least one second function related to the IoT context is invoked; (5) based on the IoT context and at least one IoT-related eSIM, and before receiving further notification: (i) processing a specific function call including the second function call, and (ii) providing a second response to the specific function call.

[0009] Other embodiments include a non-transitory computer-readable storage medium configured to store instructions that, when executed by a processor included in a computing device, cause the computing device to perform various steps of any of the methods described above. Further embodiments include a computing device configured to perform various steps of any of the methods described above.

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

[0011] The content of this invention is provided merely to outline some exemplary embodiments in order to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be understood that the features described above are merely illustrative and should not be construed as narrowing the scope or substance of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0012] This disclosure will be more readily understood through the following detailed description taken in conjunction with the accompanying drawings, wherein the same reference numerals denote the same structural elements.

[0013] Figure 1 Block diagrams illustrating different components of exemplary systems configured to implement the various technologies described herein, according to some implementation schemes.

[0014] Figure 2A Examples are given based on some implementation schemes. Figure 1 A block diagram showing a more detailed view of exemplary components of the system.

[0015] Figure 2B Conceptual diagram 250 illustrates an exemplary system according to some implementations, which may include any combination of different types of wireless devices that can support cellular wireless connectivity with the support of various network-based servers to provide eSIM for wireless devices to access cellular wireless services.

[0016] Figure 3 A conceptual diagram illustrating example means for configuring eUICC based on consumer terminal capabilities, IoT terminal capabilities, or a hybrid terminal capability including both consumer terminal capabilities and IoT terminal capabilities, according to some implementation schemes.

[0017] Figure 4 A sequence diagram illustrating techniques for managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, according to some implementation schemes, is provided.

[0018] Figure 5 Examples of methods for managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, according to some implementation schemes, are illustrated.

[0019] Figure 6 An alternative method is illustrated, according to some implementation schemes, for managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively.

[0020] Figure 7 An alternative method is illustrated, according to some implementation schemes, for managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively.

[0021] Figure 8Another method is illustrated, according to some implementations, for managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively.

[0022] Figure 9 Detailed views of representative computing devices that can be used to implement the various methods described herein, according to some implementation schemes, are shown. Detailed Implementation

[0023] This section describes representative applications of the methods and apparatus according to this application. These examples are provided only to add context and aid in understanding the described embodiments. Therefore, it will be apparent to those skilled in the art that the described embodiments can be practiced without some or all of these specific details. In other instances, well-known processing steps have not been described in detail to avoid unnecessarily obscuring the described embodiments. Other applications are possible, such that the following examples should not be considered limiting.

[0024] In the following detailed description, reference is made to the accompanying drawings, which form part of this specification, and specific embodiments according to the described embodiments are illustrated by way of example in the drawings. While these embodiments are described in sufficient detail to enable those skilled in the art to practice the described embodiments, it should be understood that these examples are not limiting; other embodiments are permitted for use, and modifications may be made without departing from the spirit and scope of the described embodiments.

[0025] The described implementation scheme illustrates techniques for concurrently managing different contexts for an electronic subscriber identity module (eSIM). Specifically, these techniques include managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, respectively.

[0026] The following is for reference. Figures 1 to 9 These and other implementation schemes will be discussed here. However, those skilled in the art will readily understand that the detailed descriptions given herein with respect to the accompanying drawings are for illustrative purposes only and should not be construed as limiting.

[0027] Figure 1 Block diagrams illustrating different components of a system 100 configured to implement the various technologies described herein, according to some implementation schemes. More specifically, Figure 1This illustrates a high-level overview of system 100, which, as shown, includes a wireless device 102 (which may also be referred to as a device, mobile wireless device, mobile device, user equipment (UE), etc.), a set of base stations 112-1 to 112-N managed by different mobile network operators (MNOs) 114, and a set of eSIM dispatch servers 116 communicating with the MNOs 114. Additional MNO infrastructure servers, such as those used for account management and billing, are not shown. Wireless device 102 may represent, for example, a cellular-capable computing device (e.g., Apple). ® iPhone ® or iPad ® Cellular wearable devices (e.g., Apple Watch), cellular vehicles, etc. Base stations 112-1 to 112-n may represent cellular wireless network entities, including evolved Node Bs (eNodeBs or eNBs) for fourth-generation (4G) Long Term Evolution (LTE) wireless networks and / or next-generation Node Bs (gNodeBs or gNBs) for fifth-generation (5G) wireless networks (or comparable nodes for future-generation wireless networks), wherein the cellular wireless network entities are configured to communicate with wireless device 102, and MNO 114 may represent different wireless service providers offering specific cellular wireless services (e.g., voice and data) that wireless device 102 may subscribe to.

[0028] like Figure 1As shown, wireless device 102 may include: processing circuitry, which may include one or more processors 104 and memory 106; and wireless circuitry 110 for transmitting and receiving cellular radio frequency signals. Wireless circuitry 110 may include analog hardware components, such as antennas and amplifiers, and digital processing components, such as signal processors (and / or general-purpose / limited-purpose processors) and associated memory. In some embodiments, wireless device 102 includes an embedded universal integrated circuit card (eUICC) 108 for storing one or more electronic SIMs (eSIMs). In some embodiments, wireless device 102 includes (or is capable of including) one or more integrated SIMs (iSIMs) securely stored in the hardware of wireless device 102 (e.g., in the processor (104), in the memory (106), or in a system-on-a-chip (SoC) component). In some embodiments, as a complement or alternative to one or more eSIMs on the eUICC 108 or one or more iSIMs stored in the hardware of wireless device 102, wireless device 102 includes one or more physical UICCs 118, also referred to as subscriber identity module (SIM) cards. The components of wireless device 102 work together to enable wireless device 102 to provide users of wireless device 102 with useful features such as cellular wireless network access, non-cellular wireless network access, localized computing, location-based services, and Internet connectivity.

[0029] According to some implementations, the eUICC 108 can be configured to store multiple electronic SIMs (eSIMs) for accessing cellular radio services provided by different MNOs 114 via base station 112 (or via multiple base stations 112, such as one or more of the illustrated base stations 112-1 to 112-N). For example, the eUICC 108 can be configured to store and manage one or more eSIMs from one or more MNOs 114 subscribed to different cellular radio services for wireless device 102. To access the cellular radio services provided by the MNOs 114, eSIMs can be retained for downloading and installation into the eUICC 108. The eUICC 108 can store one or more eSIMs obtained from one or more associated eSIM assignment servers 116. The eSIM assignment servers 116 can be maintained by the manufacturer of wireless device 102, by the MNOs 114, by a third-party entity, etc. Communication of eSIM data between eSIM dispatch server 116 and eUICC 108 (or between eSIM dispatch server 116 and processing circuitry (e.g., processor 104) of wireless device 102 outside eUICC 108) may use a secure communication channel. Similarly, one or more iSIMs may be securely stored in the hardware of wireless device 102 to enable access to cellular wireless services.

[0030] Figure 2A Examples are given based on some implementation schemes. Figure 1 A more detailed view of the specific components of the wireless device 102 is shown in Figure 2. As illustrated in Figure 2, the processor 104, combined with memory 106, can implement a main operating system (OS) 204 configured to execute applications 202 (e.g., local OS applications and user applications). Similarly... Figure 2AAs shown, eUICC 108 can be configured to implement eUICC OS 210, which is configured to manage the hardware resources of eUICC 108 (e.g., the processor and memory embedded in eUICC 108). eUICC OS 210 can also be configured to manage consumer-related eSIMs 206 / IoT-related eSIMs 208 stored by eUICC 108 in ways such as downloading, installing, deleting, enabling, disabling, modifying, or otherwise managing these eSIMs within eUICC 108, and providing access to eSIMs 206 / 208 to wireless circuit 110 to provide access to cellular wireless services for wireless device 102. eUICC 108 OS may include eSIM manager 212, which performs management functions for eSIMs 206 / 208. According to some implementations, each eSIM 206 / 208 may include multiple applets ( Figure 2A (Not illustrated in the text) These applets define how eSIM 206 / 208 operates. For example, one or more applets, when implemented in conjunction with wireless circuit 110 and eUICC 108, can be configured to enable wireless device 102 to communicate with MNO 114 and provide wireless device 102 with useful features (e.g., telephone calling and internet access).

[0031] Similarly, Figure 2A As shown, the wireless circuitry 110 of the wireless device 102 may include a baseband OS 222, which is configured to manage the hardware resources of the wireless circuitry 110 (e.g., processor, memory, various radio components, etc.). According to some embodiments, the wireless circuitry 110 may implement a baseband manager 214, which is configured to interface with the eUICC 108 to establish a secure channel with the eSIM provisioning server 116 and obtain information (such as eSIM 206 / 208) from the eSIM provisioning server 116. Figure 2A As shown, the eSIM provisioning server 116 may include (e.g., configured to provide consumer-related eSIMs) a subscription manager data preparation plus (SM-DP+) server 224, (e.g., configured to perform eSIM management functions) a subscription manager discovery service (SM-DS) server 226, and (configured to provide IoT-related eSIMs) an eSIM IoT remote manager (eIM) server 228.

[0032] According to some implementations, baseband manager 214 may be configured to implement service 216, which represents a collection of software modules instantiated through various applets of enabled eSIM 206 / 208 included in eUICC 108 within wireless device 102. For example, service 216 may be configured to manage different connections between wireless device 102 and MNO 114 based on the different eSIM 206 / 208 enabled within eUICC 108. According to some implementations, baseband manager 214 / eSIM manager 212 may also be configured to manage operating mode 218, which reflects whether (only) the consumer context is active (for managing consumer-related eSIM 206), (only) the IoT context is active (for managing IoT-related eSIM 208), or whether both the consumer context and the IoT context are concurrently active (referred to herein as a hybrid terminal capability / operating mode). It should be noted that operating mode 218 is not limited to the consumer context and IoT context described herein. Conversely, in accordance with the scope of this disclosure, the baseband manager 214 may be configured to manage any number of contexts (and the different types of eSIMs corresponding to these contexts).

[0033] Additionally, for one or more iSIMs directly embedded in the hardware of the wireless device 102 (e.g., in the processor 104, memory 106, or SoC (not illustrated)), the one or more iSIMs may include modules that provide functionality similar to those illustrated for eSIMs 206 / 208, and the software / firmware supporting the eSIM (such as eSIM manager 212 and eUICC OS 210) may be provided by similar software / firmware elements in the hardware of the wireless device 102 in which one or more iSIMs are stored.

[0034] Figure 2BA conceptual diagram 250 illustrates an exemplary system according to some embodiments, which may include any combination of different types of wireless devices 102, which may support cellular wireless connectivity with the support of various network-based servers to provide eSIM for accessing cellular wireless services to the wireless devices 102. The different types of wireless devices 102 may include a cellular-capable mobile phone 102A, a cellular-capable wearable device 102B, a cellular-capable tablet computer 102C, and a cellular-capable vehicle 102D. It should be noted that the foregoing examples are not intended to be limiting, and where consistent with the scope of this disclosure, wireless device 102 may represent any physical entity, may be included in any physical entity, etc. Cellular capability for wireless devices 102A–102D may be based on a SIM card (UICC 118), an eSIM 208 included on an eUICC 108, an iSIM, etc.

[0035] In some cases, wireless devices 102A, 102B, 102C, and 102D can each communicate with a public user account (e.g., a cloud-based service account, such as iCloud). ® The account, the iCloud ® An account is associated with wireless device 102 via an internet data connection to one or more cloud service servers 256 (enabling network access). Data for wireless devices 102A, 102B, 102C, and 102D can be securely stored in a cloud-based service account on one or more cloud service servers 256. In some cases, this cloud-based service account can be used to transfer information between different wireless devices 102. For example, a user may replace an older wireless device 102 with a newer one and seek to transfer various information, settings, preferences, etc., from the older wireless device 102 to the newer one. Additionally, habitual device usage characteristics compiled and determined by the older wireless device 102 can be transferred to the newer wireless device 102 directly in peer-to-peer transfers or via backup and restore through local storage or via remote storage on one or more cloud service servers 256. Habitual device usage characteristics can be encrypted before being transferred via remote storage, thereby protecting user privacy before being loaded onto the newer wireless device 102.

[0036] MNO 114 can provide cellular wireless services to a group of wireless devices 102 and can manage access to the cellular wireless network for access to cellular wireless services provided by MNO 114 for a specific cellular wireless service subscription (or for a group of cellular wireless service subscriptions) via one or more MNO servers 258. MNO server 258 may include one or more dispatch servers 116 for providing eSIM 208 (and / or iSIM) to wireless devices 102. One or more SIMs (e.g., eSIM 208 and / or iSIM) may be provided to wireless device 102 based on several factors. For example, when wireless device 102A represents a user's smartphone, providing a single SIM to wireless device 102A to enable the user to access wireless services through wireless device 102A may be sufficient. For example, when the wireless device 102D represents a user’s vehicle, it may be appropriate to provide the vehicle with the following: (1) a consumer-related SIM to enable the user to make phone calls, access the Internet, etc. through the vehicle, and (2) an IoT-related SIM to enable the vehicle to interface with a management entity (e.g., the vehicle’s manufacturer) to provide diagnostics, receive software updates, etc.

[0037] Figure 3 A conceptual diagram 300 illustrates an example means for configuring an eUICC 108 based on consumer terminal capabilities, IoT terminal capabilities, or a hybrid terminal capability including both consumer terminal capabilities and IoT terminal capabilities, according to some embodiments. According to some embodiments, wireless circuit 110 / wireless device 102 may transmit terminal capability commands to the eUICC 108 in association with power-on, reset, etc., to cause the eUICC 108 to enter the aforementioned combined... Figure 2A The described operating mode 218 is one of the operating modes. According to some embodiments, the terminal capability commands described herein may be terminal capability commands as described in ETSI TS 102 221. According to some embodiments, and as described in more detail below, the terminal capability commands may include information such as, accompanied by, indications of the appropriate operating mode 218, attributes that should be applied to operating mode 218, etc.

[0038] like Figure 3 As shown, one example means for enabling the eUICC 108 to configure itself according to the capabilities of the consumer terminal may involve the wireless device 102 sending a tag-length-value (TLV) encapsulation to the eUICC 108, the tag-length-value (TLV) encapsulation including a tag 302 (indicating the value "83"), a length 304 (indicating one byte), and a first byte 306 (indicating detailed attributes related to the capabilities of the consumer terminal). Also as... Figure 3As shown, an example means for enabling the eUICC 108 to configure itself according to the IoT terminal capabilities may involve the wireless device 102 sending a TLV encapsulation to the eUICC 108, the TLV encapsulation including a tag 308 (indicating the value "83"), a length 310 (indicating two bytes), a first byte 312 (i.e., empty (e.g., all values ​​are set to zero)) and a second byte 314 (indicating detailed attributes related to the IoT terminal capabilities).

[0039] in addition, Figure 3 Two example means are illustrated for enabling the eUICC 108 to configure itself according to hybrid terminal capabilities. Specifically, the first means 315 may involve the wireless device 102 sending a TLV encapsulation to the eUICC 108, the TLV encapsulation including a tag 316 (indicating value "83"), a length 318 (indicating two bytes), a first byte 320 (indicating detailed attributes related to consumer terminal capabilities), and a second byte 322 (indicating detailed attributes related to IoT terminal capabilities). The second means 323 may involve the wireless device 102 sending to the eUICC 108 a first TLV encapsulation including a tag 324 (indicating value "83"), a length 326 (indicating one byte), and a first byte 328 (indicating detailed attributes related to consumer terminal capabilities), and a second TLV encapsulation including a tag 330 (indicating value "84"), a length 332 (indicating one byte), and a first byte 334 (indicating detailed attributes related to IoT terminal capabilities). It should be noted that the foregoing examples are not intended to be limiting, and that, within the scope of this disclosure, the wireless device 102 / eUICC 108 may be configured to convey information of any quantity, type, form, etc., to effectively transmit the operating mode 218 to be utilized, configuration aspects of the operating mode 218, etc.

[0040] Figure 4 Sequence diagram 400 illustrates techniques for managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, according to some embodiments. Figure 4 As shown, in step 402, the wireless device 102 is powered on and undergoes a reset process, etc.

[0041] At step 404, eUICC 108 indicates to wireless circuit 110 that eUICC 108 supports eUICC functionality. According to some embodiments, eUICC 108 may use a Reset Response (ATR) global interface byte as defined in ETSI TS 102 221 to indicate that the eUICC supports eUICC functionality. It should be understood that, within the scope of this disclosure, additional / alternative means may be used to effectively enable eUICC 108 to indicate that the eUICC supports eUICC functionality.

[0042] At step 406, wireless circuit 110 (to eUICC 108) instructs to select a hybrid terminal capability from consumer terminal (CT) capability, Internet of Things (IoT) capability, or a hybrid terminal capability reflecting both CT and IoT capabilities. According to some embodiments, wireless circuit 110 may use a combination of the above descriptions. Figure 3 The first method described, 315, uses the above in combination. Figure 3 The second means 323 described herein, or any other means that effectively enables the wireless circuit 110 to instruct the eUICC 108 to implement hybrid terminal capabilities, to provide instruction to the eUICC 108.

[0043] At step 408, the eUICC 108 provides confirmation of the hybrid terminal capability to the wireless circuit 110. According to some embodiments, the confirmation may be provided in the form of a status word (SW), where the status byte is set to the value "90 00" to effectively indicate that the hybrid terminal capability has been confirmed by the eUICC 108. It should be understood that, consistent with the scope of this disclosure, additional / alternative means may be used to effectively enable the eUICC 108 to provide confirmation of the hybrid terminal capability to the wireless circuit 110.

[0044] At step 410, wireless circuit 110 provides eUICC 108 with a command to select the Issuing Authority Security Domain – Root (ISD-R). According to some embodiments, the command can be transmitted via a logical channel established between wireless circuit 110 and eUICC 108 using management channel commands defined in the Global Platform Card Specification. According to some embodiments, the command can be established, formatted, etc., using selection commands defined in the Global Platform Card Specification. It should be understood that, consistent with the scope of this disclosure, additional / alternative means can be used to effectively enable wireless circuit 110 to provide the eUICC 108 with the command to select the ISD-R.

[0045] At step 412, wireless circuit 110 provides a Document Control Information (FCI) template indicating hybrid terminal capabilities. According to some embodiments, the FCI template may include labels “A0” and “A1” to indicate hybrid terminal capabilities, where “A0” corresponds to consumer-related capabilities and “A1” corresponds to IoT-related capabilities. It should be understood that additional / alternative means (e.g., additional / alternative templates, commands, labels, etc.) can be used to effectively enable wireless circuit 110 to provide indications of hybrid terminal capabilities to eUICC 108.

[0046] At the end of step 412, wireless circuit 110 and eUICC 108 are configured according to the hybrid operating mode described herein. In this respect, wireless circuit 110 and eUICC 108 can effectively manage consumer context and IoT context when utilizing consumer-related eSIM and IoT-related eSIM respectively. Depending on some implementations, different means can be used to manage these contexts. Specifically, the following describes... Figure 4 The first operational means described (including steps 414-420) involves accompanying function calls with a label indicating whether a consumer context or an IoT context should be applied when processing the function call. The following section combines... Figure 4 The second operational means described (including steps 422-436) relates to providing a context switching command whenever a transition from an application consumer context to an application IoT context (or vice versa) is required. It should be understood that, consistent with the scope of this disclosure, additional / alternative means may be utilized to effectively enable the wireless circuit 110 / eUICC 108 to select, identify, apply, etc., the appropriate context when processing function calls.

[0047] In the first approach, at step 414, wireless circuit 110 issues a function call with an indication to operate in a consumer context. The function call may represent, for example, an ES10 function call defined in the GSMA RSP specification, eSIM IoT specification, etc. It should be noted that the foregoing examples are not intended to be limiting, and that, consistent with the scope of this disclosure, function calls can include function calls of any type, form, etc., at any granularity. According to some embodiments, each function call may include, be accompanied by, a corresponding label identifying the context to be applied when processing the function call (e.g., the label "A0" (where "A0" corresponds to the consumer context)). It should be understood that, consistent with the scope of this disclosure, additional / alternative means may be used to effectively enable wireless circuit 110 to instruct eUICC 108 to apply the consumer context when processing the function call.

[0048] At step 416, wireless circuit 110 provides a consumer context response (in response to the function call provided in step 414). According to some embodiments, each consumer context response may optionally include, accompanied by, the label "A0", to confirm the application of the consumer context when processing the consumer context response, to instruct wireless circuit 110 to apply the consumer context when processing the consumer context response, etc. In any case, wireless circuit 110 may appropriately process the consumer context response.

[0049] At step 418, wireless circuit 110 issues a function call with an indication of operation within an IoT context. As described herein, the function call may represent an ES10 function call as defined, for example, in the GSMA RSP specification, eSIM IoT specification, etc. According to some embodiments, each function call may include, be accompanied by, a corresponding label identifying the context to be applied when processing the function call (e.g., label “A1” (where “A1” corresponds to the IoT context)). It should be understood that, consistent with the scope of this disclosure, additional / alternative means may be used to effectively enable wireless circuit 110 to instruct eUICC 108 to apply the IoT context when processing the function call.

[0050] At step 420, wireless circuit 110 provides an IoT context response. As described herein, each IoT context response may optionally include, accompanied by, a label such as "A1," to confirm that an IoT context is applied when processing the IoT context response, to instruct wireless circuit 110 to apply an IoT context when processing the IoT context response, etc. In any case, wireless circuit 110 may appropriately process the IoT context response.

[0051] In the second approach, as an alternative to (or supplement to) the aforementioned approach, which involves accompanying a function call with a label identifying the appropriate context to be applied when processing the function call, using a context switching command. Specifically, and according to some embodiments, a given context switching command may include a label identifying the context to be applied to the function call before receiving further notification—that is, before receiving a subsequent context switching command specifying a different context. For example, when one or more function calls (to be processed) are associated with a consumer context, wireless circuit 110 may provide a context switching command including, accompanied by, the label "A0" to deliver the consumer context to be applied before receiving further notification. Similarly, when one or more function calls (to be processed) are associated with an IoT context, wireless circuit 110 may provide a context switching command including, accompanied by, the label "A1" to deliver the consumer context to be applied before receiving further notification. It should be understood that, consistent with the scope of this disclosure, additional / alternative means may be used to effectively enable wireless circuit 110 to indicate to eUICC 108 that a particular context should be applied to subsequent function calls before receiving further notification.

[0052] To illustrate the second approach, at step 422, wireless circuit 110 provides eUICC 108 with a context switching command to operate in a consumer context. The context switching command may be provided, for example, in response to wireless circuit 110 identifying needs, conditions, etc., to issue one or more function calls related to the consumer context. Similarly, the function calls may represent ES10 function calls defined, for example, in the GSMA RSP specification, eSIM IoT specification, etc. At step 424, wireless circuit 110 provides an acknowledgment of the context switch (e.g., according to the technique described above in conjunction with step 408). This acknowledgment may indicate to wireless circuit 110 that eUICC 108 has been correctly configured and is ready to use the consumer context to process function calls. Subsequently, at step 426, wireless circuit 110 issues a function call to eUICC 108, and at step 428, eUICC 108 provides a consumer context response to wireless circuit 110.

[0053] Additionally, to illustrate the second means, at step 430, wireless circuit 110 provides a context switching command for operation within the IoT context. The context switching command may be provided, for example, in response to wireless circuit 110 identifying needs, conditions, etc., to issue one or more function calls related to the IoT context. At step 432, wireless circuit 110 provides confirmation of the context switch (e.g., according to the technique described above in conjunction with steps 408 and 424). This confirmation may indicate to wireless circuit 110 that eUICC 108 has been correctly configured and is ready to use the IoT context to process function calls. Subsequently, at step 434, wireless circuit 110 issues a function call to eUICC 108, and at step 436, eUICC 108 provides an IoT context response to wireless circuit 110.

[0054] therefore, Figure 4 The first approach described is more efficient (compared to the second approach) when function calls with different (i.e., changing) contexts are frequently interleaved—frequent interleaving of function calls in the second approach would require frequent context switching commands, leading to jitter. Conversely, Figure 4 The second approach described herein is more efficient (compared to the first approach) when function calls related to different contexts are not frequently interleaved—function calls not being frequently interleaved would involve function calls being accompanied by label information that is not actually necessary under the first approach (e.g., when most / a set of function calls are for the consumer context and a few / a set of function calls are for the IoT context, or vice versa).

[0055] To mitigate the aforementioned drawbacks, wireless circuit 110 can be configured to monitor and analyze the manner in which function calls are being issued or will be issued, the context in which these function calls are applied, etc., to identify when using the first operating means is most advantageous and when using the second operating means is most advantageous. In this regard, wireless circuit 110 can be configured to issue an operating mode switching command to eUICC 108. Figure 4 (not illustrated in the text) to effectively enable eUICC 108 to reconfigure itself to handle function calls according to either the first or second means. Alternatively, when using the second means, wireless circuit 110 can be configured to group pending (i.e., unprocessed) function calls corresponding to the same context, and then issue a context switching command before issuing subsequent / different grouped function calls to be processed.

[0056] It should be understood that additional means may be used to apply the appropriate context associated with processing function calls. For example, the wireless circuit 110 / eUICC 108 may be configured to assume that function calls that do not specifically reference a context (e.g., using a tag) should be processed using a consumer context, while function calls that specifically reference an IoT context (e.g., using a tag corresponding to an IoT context) should be processed using an IoT context (or vice versa). Again, these means are exemplary, and any means that effectively enable the wireless circuit 110 / eUICC 108 to apply the appropriate context when processing function calls may be implemented, within the scope of this disclosure.

[0057] Figure 5 Examples of methods 500 for managing both consumer context and IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, according to some embodiments, are illustrated. In some embodiments, method 500 is performed by a wireless device 102, by one or more elements of the wireless device 102 (such as one or more hardware components and / or one or more software / firmware modules), or by means configurable (or configured) for operation in the wireless device 102. In some embodiments, method 500 is performed by the application processor and / or baseband processor of the wireless device 102. Figure 5 As shown, at step 502, method 500 includes interfacing with an embedded universal integrated circuit card (eUICC) 108, wherein the eUICC 108 manages at least one consumer-related eSIM and at least one IoT-related eSIM. In some embodiments, the eUICC 108 is included in a wireless device 102. At step 504, method 500 includes providing the eUICC 108 with terminal capability commands instructing both the consumer context and the IoT context to be managed.

[0058] At step 506, the method includes providing at least one first function call to the eUICC 108 indicating a consumer context, wherein the consumer context causes the eUICC 108 to process the at least one first function call based on the consumer context and at least one consumer-related eSIM: (i) process the at least one first function call, and (ii) provide at least one first response to the at least one first function call.

[0059] At step 508, the method includes providing at least one second function call to the eUICC 108 indicating an IoT context, wherein the IoT context causes the eUICC 108 to process the at least one second function call based on the IoT context and at least one IoT-related eSIM: (i) processing the at least one second function call, and (ii) providing at least one second response to the at least one second function call.

[0060] In some embodiments, method 500 further includes receiving an indication from eUICC 108 that eUICC 108 supports eUICC 108 functionality before providing a terminal capability command. In some embodiments, the terminal capability command is provided in response to a reset response (ATR) triggered by a power-on event or a reset event. In some embodiments, method 500 further includes receiving confirmation from eUICC 108 that eUICC 108 is managing both a consumer context and an IoT context in response to the terminal capability command. In some embodiments, method 500 further includes: i) providing an issuer security domain-root (ISD-R) selection command to eUICC 108, and ii) receiving a File Control Information (FCI) template from eUICC 108 indicating both the consumer context and the IoT context. In some embodiments, the terminal capability command includes a tag-length-value (TLV) encapsulation, and the TLV encapsulation includes a first byte and a second byte respectively identifying at least one consumer-related functionality and at least one IoT-related functionality. In some embodiments, the terminal capability command includes a first TLV package and a second TLV package. The first TLV package includes a byte identifying at least one consumer-related functionality implemented by the wireless device 102, and the second TLV package includes a byte identifying at least one IoT-related functionality. In some embodiments, the at least one consumer-related functionality and the at least one IoT-related functionality are implemented by the wireless device 102, by one or more elements of the wireless device 102 (such as one or more hardware components and / or one or more software / firmware modules), or by means configurable (or configured) for operation in the wireless device 102.

[0061] Figure 6 A method 600, according to some embodiments, for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, is illustrated. In some embodiments, method 600 is performed by a wireless device 102, by one or more elements of the wireless device 102 (such as one or more hardware components and / or one or more software / firmware modules), or by means configurable (or configured) for operation in the wireless device 102. In some embodiments, method 600 is performed by the application processor and / or baseband processor of the wireless device 102. Figure 6As shown, at step 602, method 600 includes interfacing with an embedded universal integrated circuit card (eUICC) 108, wherein the eUICC 108 manages at least one consumer-related eSIM and at least one IoT-related eSIM. In some embodiments, the eUICC 108 is included in a wireless device 102. At step 604, method 600 includes providing the eUICC 108 with terminal capability commands instructing both the consumer context and the IoT context to be managed.

[0062] At step 606, the method includes identifying at least one first condition under which at least one first function related to a consumer context is invoked. At step 608, the method includes providing a consumer context switching command to the eUICC 108, the consumer context switching command causing the eUICC 108, based on the consumer context and at least one consumer-related eSIM, and prior to receiving further notification: (i) processing a specific function call including the first function call, and (ii) providing a first response to the specific function call.

[0063] At step 610, the method includes identifying at least one second condition under which at least one second function related to the IoT context is invoked. At step 612, the method includes providing an IoT context switching command to the eUICC 108, the IoT context switching command causing the eUICC 108, based on the IoT context and at least one IoT-related eSIM, and prior to receiving further notification: (i) processing a specific function call including the second function call, and (ii) providing a second response to the specific function call.

[0064] In some embodiments, the actions of steps 606 and 610 may be combined, for example, i) identifying at least one first condition, under which at least one first function related to the consumer context is invoked, and / or ii) identifying at least one second condition, under which at least one second function related to the IoT context is invoked. Additionally, in some embodiments, the actions of steps 608 and 612 may be combined, for example, i) providing a consumer context switching command to the eUICC 108, which causes the eUICC 108, based on the consumer context and at least one consumer-related eSIM, and before receiving further notification: (a) processing a specific function call including the first function call, and (b) providing a first response to the specific function call; and / or ii) providing an IoT context switching command to the eUICC 108, which causes the eUICC 108, based on the IoT context and at least one IoT-related eSIM, and before receiving further notification: (a) processing a specific function call including a second function call, and (b) providing a second response to the specific function call.

[0065] In some embodiments, method 600 further includes receiving an indication from eUICC 108 that eUICC 108 supports eUICC 108 functionality before providing a terminal capability command. In some embodiments, the terminal capability command is provided in response to an ATR triggered by a power-on event or a reset event. In some embodiments, method 600 further includes receiving an acknowledgment from eUICC 108 in response to the terminal capability command that eUICC 108 is managing both a consumer context and an IoT context. In some embodiments, method 600 further includes: i) providing an ISD-R select command to eUICC 108; and ii) receiving an FCI template from eUICC 108 indicating both the consumer context and the IoT context. In some embodiments, the terminal capability command includes a TLV encapsulation, and the TLV encapsulation includes a first byte and a second byte respectively identifying at least one consumer-related functionality and at least one IoT-related functionality. In some embodiments, the terminal capability command includes a first TLV encapsulation and a second TLV encapsulation, the first TLV encapsulation including a byte identifying at least one consumer-related functionality and the second TLV encapsulation including a byte identifying at least one IoT-related functionality. In some implementations, at least one consumer-related function and at least one IoT-related function are implemented by the wireless device 102, by one or more elements of the wireless device 102 (such as one or more hardware components and / or one or more software / firmware modules), or by means configurable (or configured) for operation in the wireless device 102.

[0066] Figure 7 An example of a method 700, according to some embodiments, for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, is illustrated. In some embodiments, method 700 is performed by an eUICC 108 that communicates with one or more elements of wireless device 102 (e.g., hardware components and / or software / firmware modules and / or means configurable (or configured to operate in wireless device 102). In some embodiments, eUICC 108 communicates with the application processor and / or baseband processor of wireless device 102. Figure 7 As shown, method 700 begins at step 702, where eUICC 108 manages at least one consumer-related eSIM and at least one IoT-related eSIM. At step 704, eUICC 108 receives a terminal capability command instructing that both the consumer context and the IoT context should be managed.

[0067] At step 706, the eUICC 108 receives at least one first function call indicating a consumer context. At step 708, the eUICC 108, based on the consumer context and at least one consumer-related eSIM, (i) processes the at least one first function call, and (ii) provides at least one first response to the at least one first function call.

[0068] At step 710, the eUICC 108 receives at least one second function call indicating an IoT context. At step 712, based on the IoT context and at least one IoT-related eSIM, the eUICC 108: (i) processes at least one second function call, and (ii) provides at least one second response to at least one second function call.

[0069] In some embodiments, method 700 further includes eUICC 108 providing an indication that eUICC 108 supports eUICC functionality before receiving a terminal capability command. In some embodiments, the terminal capability command is communicated by at least one of an application processor or a baseband processor, and the application processor is provided in response to an ATR triggered by a power-on event or a reset event. In some embodiments, method 700 further includes eUICC 108 providing confirmation that both the consumer context and the IoT context are being managed in response to the terminal capability command. In some embodiments, method 700 further includes eUICC 108: i) receiving an ISD-R select command; and ii) providing an FCI template indicating both the consumer context and the IoT context. In some embodiments, the terminal capability command includes a TLV encapsulation, and the TLV encapsulation includes a first byte and a second byte respectively identifying at least one consumer-related function and at least one IoT-related function. In some embodiments, the terminal capability command includes a first TLV encapsulation and a second TLV encapsulation, the first TLV encapsulation including a byte identifying at least one consumer-related function and the second TLV encapsulation including a byte identifying at least one IoT-related function. In some implementations, at least one consumer-related function and at least one IoT-related function are implemented by the wireless device 102, by one or more elements of the wireless device 102 (such as one or more hardware components and / or one or more software / firmware modules), or by means configurable (or configured) for operation in the wireless device 102.

[0070] Figure 8 An example of a method 800 for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, according to some embodiments, is illustrated. In some embodiments, method 800 is performed by an eUICC 108 that communicates with one or more elements of a wireless device 102 (e.g., hardware components and / or software / firmware modules and / or means configurable (or configured to operate in the wireless device 102). In some embodiments, the eUICC 108 communicates with the application processor and / or baseband processor of the wireless device 102. Figure 8 As shown, method 800 begins at step 802, where eUICC 108 manages at least one consumer-related eSIM and at least one IoT-related eSIM. At step 804, eUICC 108 receives a terminal capability command instructing that both the consumer context and the IoT context should be managed.

[0071] At step 806, eUICC 108 receives a consumer context switching command, wherein the consumer context switching command is provided in response to an identifier of at least one first condition under which at least one first function related to the consumer context is invoked. In some embodiments, the identifier of at least one first condition under which at least one first function related to the consumer context is invoked is executed by one or more elements of wireless device 102 (e.g., hardware components and / or software / firmware modules and / or means configurable (or configured to operate in wireless device 102). In some embodiments, the identifier of at least one first condition under which at least one first function related to the consumer context is invoked is executed by one or more of an application processor or a baseband processor. At step 808, eUICC 108, based on the consumer context and at least one consumer-related eSIM, and before receiving further notification: (i) processes a specific function call including the first function call, and (ii) provides a first response to the specific function call.

[0072] At step 810, the eUICC 108 receives an IoT context switching command, which is provided in response to an identifier of at least one second condition under which at least one second function related to the IoT context is invoked. In some embodiments, the identifier of the at least one second condition under which at least one second function related to the IoT context is invoked is executed by one or more elements of the wireless device 102 (e.g., hardware components and / or software / firmware modules and / or means configurable (or configured to operate in the wireless device 102). In some embodiments, the identifier of the at least one second condition under which at least one second function related to the IoT context is invoked is executed by one or more of an application processor or a baseband processor. At step 812, based on the IoT context and at least one IoT-related eSIM, and before receiving further notification, the eUICC 108: (i) processes a specific function call including the second function call, and (ii) provides a second response to the specific function call.

[0073] In some embodiments, method 800 further includes eUICC 108 providing an indication that eUICC 108 supports eUICC 108 functionality before receiving a terminal capability command. In some embodiments, the terminal capability command is communicated by at least one of an application processor or a baseband processor, and the application processor is provided in response to an ATR triggered by a power-on event or a reset event. In some embodiments, method 800 further includes eUICC 108 providing confirmation that both the consumer context and the IoT context are being managed in response to the terminal capability command. In some embodiments, method 800 further includes eUICC 108: i) receiving an ISD-R select command, and ii) providing an FCI template indicating both the consumer context and the IoT context. In some embodiments, the terminal capability command includes a TLV encapsulation, and the TLV encapsulation includes a first byte and a second byte respectively identifying at least one consumer-related function and at least one IoT-related function. In some embodiments, the terminal capability command includes a first TLV encapsulation and a second TLV encapsulation, the first TLV encapsulation including a byte identifying at least one consumer-related function, and the second TLV encapsulation including a byte identifying at least one IoT-related function. In some implementations, at least one consumer-related function and at least one IoT-related function are implemented by the wireless device 102, by one or more elements of the wireless device 102 (such as one or more hardware components and / or one or more software / firmware modules), or by means configurable (or configured) for operation in the wireless device 102.

[0074] Figure 9 Detailed views of a representative computing device 900, according to some embodiments, that can be used to implement the various methods described herein are illustrated. Specifically, these detailed views illustrate various components that may be included in any of wireless devices 102, 102A, 102B, 102C, and 102D, or any other wireless device, as discussed herein. Figure 9As shown, computing device 900 may include processor 902, which represents a microprocessor or controller for controlling the overall operation of computing device 900. Computing device 900 may also include user input device 908, which allows a user of computing device 900 to interact with computing device 900. For example, user input device 908 may take various forms, such as buttons, keypad, dial pad, touchscreen, audio input interface, visual / image capture input interface, sensor data input, etc. Furthermore, computing device 900 may include display 910, which can be controlled by processor 902 to display information to a user. Data bus 916 facilitates data transfer between at least storage device 940, processor 902, and controller 913. Controller 913 can be used to interface with and control different devices via equipment control bus 914. Computing device 900 may also include network / bus interface 911 communicatively coupled to data link 912. In the case of wireless connectivity, network / bus interface 911 may include a wireless transceiver.

[0075] The computing device 900 also includes a storage device 940, which may include a single disk or multiple disks (e.g., a hard disk drive), and the computing device includes a storage management module that manages one or more partitions within the storage device 940. In some embodiments, the storage device 940 may include flash memory, semiconductor (solid-state) memory, etc. The computing device 900 may also include random access memory (RAM) 920 and read-only memory (ROM) 922. ROM 922 may store programs, utilities, or procedures that will be executed in a non-volatile manner. RAM 920 may provide volatile data storage and store instructions related to the operation of the computing device 900. The computing device 900 may also include a secure element (SE) 924, which may represent secure storage of credentials for cellular wireless system access performed by the computing device 900. The secure element 924 may include an eUICC storing one or more eSIMs (e.g., one or more eUICCs 108), one or more UICCs 118 storing SIM or eSIM credentials (profiles), and / or a processor and / or chip component in a system-on-a-chip (SoC) module storing iSIM credentials (profiles).

[0076] Wireless terminology According to the various embodiments described herein, the terms "wireless communication device," "wireless device," "mobile wireless device," "mobile station," and "user equipment (UE)" are used interchangeably herein to describe one or more general consumer electronic devices capable of performing processes associated with the various embodiments of this disclosure. According to various specific embodiments, any of these consumer electronic devices may relate to: cellular phones or smartphones, tablet computers, laptop computers, notebook computers, personal computers, netbook computers, media player devices, e-book devices, MiFi devices, etc. ® Devices, wearable computing devices, and any other type of electronic computing device with wireless communication capabilities, which may include communication via one or more wireless communication protocols, such as protocols for communicating on networks including: Wireless Wide Area Network (WWAN), Wireless Metropolitan Area Network (WMAN), Wireless Local Area Network (WLAN), Wireless Personal Area Network (WPAN), Near Field Communication (NFC), Cellular Wireless Network, Fourth Generation (4G) Long Term Evolution (LTE), LTE-Advanced (LTE-A), and / or 5G or other currently or future advanced cellular wireless networks.

[0077] In some implementations, the wireless communication devices may also operate as part of a wireless communication system that may include a group of client devices, also referred to as stations, client wireless devices, or client wireless communication devices, interconnected to an access point (AP) (e.g., as part of a WLAN), and / or interconnected with each other (e.g., as part of a WPAN and / or a “self-organizing” wireless network). In some implementations, the client devices may be any wireless communication device capable of communicating via WLAN technology (e.g., according to a wireless LAN communication protocol). In some implementations, WLAN technology may include a Wi-Fi (or more generally, WLAN) wireless communication subsystem or radio component that implements IEEE 802.11 technology, such as one or more of the following: IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other currently or future IEEE 802.11 technologies.

[0078] Furthermore, it should be understood that the UE described herein can be configured as a multi-mode wireless communication device capable of communicating via different third-generation (3G) and / or second-generation (2G) RATs. In these scenarios, the multi-mode UE can be configured to prefer attaching to LTE networks that offer faster data rate throughput compared to other 3G legacy networks that offer lower data rate throughput. For example, in some specific implementations, the multi-mode UE can be configured to fall back to a 3G legacy network, such as an evolved High-Speed ​​Packet Access (HSPA+) network or a Code Division Multiple Access (CDMA) 2000 Evolution-Data-Only (EV-DO) network, when LTE and LTE-A networks are otherwise unavailable.

[0079] Cellular access credentials used to provide access to cellular wireless services from cellular wireless service providers can be installed in various forms in wireless devices, including but not limited to universal integrated circuit cards (UICCs) storing a subscriber identity module (SIM), embedded UICCs (eUICCs) storing an electronic SIM (eSIM), or processors in hardware such as system-on-chip (SoC) modules storing an integrated SIM (iSIM). The implementations described herein can be applied to all these types of specific implementations. A UICC storing a SIM can also be referred to as a SIM card. A SIM, eSIM, or iSIM can also be referred to as a SIM profile, eSIM profile, or iSIM profile, or simply a profile.

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

[0081] Regarding this disclosure, it is widely known that the use of personally identifiable information should comply with privacy policies and practices that are generally recognized as meeting or exceeding 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 the permitted use should be clearly explained to the user.

[0082] For illustrative purposes, the foregoing description uses specific names to provide a thorough understanding of the described embodiments. However, it will be apparent to those skilled in the art that specific details are not required to practice the described embodiments. Therefore, the foregoing description of specific embodiments is presented for illustrative and descriptive purposes. The foregoing description is not intended to be exhaustive or to limit the described embodiments to the precise forms disclosed. It will be apparent to those skilled in the art that many modifications and variations are possible in light of the teachings above.

Claims

1. A method for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the method comprising: Provide the embedded universal integrated circuit card (eUICC) with terminal capability commands that indicate whether both the consumer context and the IoT context should be managed; Provide the eUICC with at least one first function call indicative of the consumer context, wherein the consumer context causes the eUICC to base itself on the consumer context and the eSIM associated with the at least one consumer: Process the at least one first function call, and Provide at least one first response to the at least one first function call; and / or Provide the eUICC with at least one second function call indicating the IoT context, wherein the IoT context causes the eUICC to be based on the IoT context and the at least one IoT-related eSIM: Process the at least one second function call, and Provide at least one second response to the at least one second function call.

2. The method according to claim 1, further comprising: Before providing the terminal capability commands: Receive an indication from the eUICC that the eUICC supports eUICC functionality.

3. The method of claim 1, wherein the terminal capability command is provided in response to a reset response (ATR) triggered by a power-on event or a reset event.

4. The method according to claim 1, further comprising: In response to the terminal capability command, receive confirmation from the eUICC that the eUICC is managing both the consumer context and the IoT context.

5. The method according to claim 1, further comprising: Provide the eUICC with an issuer security domain-root (ISD-R) selection command; as well as Receive a File Control Information (FCI) template from the eUICC that indicates both the Consumer Context and the IoT Context.

6. The method according to claim 1, wherein: The terminal capability commands include tag-length-value (TLV) encapsulation; and The TLV package includes a first byte and a second byte that respectively identify at least one consumer-related function and at least one IoT-related function.

7. The method according to claim 1, wherein: The terminal capability commands include a first TLV package and a second TLV package. The first TLV encapsulation includes a byte identifying at least one consumer-related functionality; and The second TLV package includes a byte that identifies at least one IoT-related functionality.

8. A method for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the method comprising: Provide the embedded universal integrated circuit card (eUICC) with terminal capability commands that indicate whether both the consumer context and the IoT context should be managed; Identify at least one first condition and / or at least one second condition, under the at least one first condition, invoke at least one first function related to the consumer context, and under the at least one second condition, invoke at least one second function related to the IoT context; Provide the eUICC with a consumer context switching command, the consumer context switching command causing the eUICC, based on the consumer context and the eSIM associated with the at least one consumer, and prior to receiving further notification, to: (i) process a specific function call including the first function call, and (ii) provide a first response to the specific function call; and / or An IoT context switching command is provided to the eUICC, which causes the eUICC, based on the IoT context and the at least one IoT-related eSIM, to: (i) process the specific function call including the second function call, and (ii) provide a second response to the specific function call before receiving further notification.

9. The method according to claim 8, further comprising: Before providing the terminal capability commands: Receive an indication from the eUICC that the eUICC supports eUICC functionality.

10. The method of claim 8, wherein the terminal capability command is provided in response to a reset response (ATR) triggered by a power-on event or a reset event.

11. The method according to claim 8, further comprising: In response to the terminal capability command, receive confirmation from the eUICC that the eUICC is managing both the consumer context and the IoT context.

12. The method according to claim 8, further comprising: Provide the eUICC with an issuer security domain-root (ISD-R) selection command; as well as Receive a File Control Information (FCI) template from the eUICC that indicates both the Consumer Context and the IoT Context.

13. The method of claim 8, wherein: The terminal capability commands include tag-length-value (TLV) encapsulation; as well as The TLV package includes a first byte and a second byte that respectively identify at least one consumer-related function and at least one IoT-related function.

14. The method according to claim 8, wherein: The terminal capability commands include a first TLV package and a second TLV package. The first TLV package includes a byte identifying at least one consumer-related functionality; and The second TLV package includes a byte that identifies at least one IoT-related functionality.

15. A method for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the method comprising using an embedded universal integrated circuit card (eUICC): Receive terminal capability commands instructing that both the consumer context and the IoT context should be managed; Receive at least one first function call indicating the consumer context; as well as Based on the consumer context and the eSIM associated with the at least one consumer: (i) process the at least one first function call, and (ii) provide at least one first response to the at least one first function call; And / or Receive at least one second function call indicating the IoT context; as well as Based on the IoT context and the at least one IoT-related eSIM: (i) process the at least one second function call, and (ii) provide at least one second response to the at least one second function call.

16. The method according to claim 15, further comprising: Before receiving the terminal capability command: Provides indications of eUICC support for eUICC functionality.

17. The method of claim 15, wherein: The terminal capability commands are conveyed by at least one of the application processor or the baseband processor; and The terminal capability command is provided in response to a reset response (ATR) triggered by a power-on event or a reset event.

18. The method according to claim 15, further comprising: In response to the terminal capability command, confirmation is provided that both the consumer context and the IoT context are being managed.

19. The method of claim 15, further comprising: Receive the issuer security domain-root (ISD-R) selection command; as well as Provide a File Control Information (FCI) template that indicates both the consumer context and the IoT context.

20. The method of claim 15, wherein: The terminal capability commands include tag-length-value (TLV) encapsulation; as well as The TLV package includes a first byte and a second byte that respectively identify at least one consumer-related function and at least one IoT-related function.

21. The method of claim 15, wherein: The terminal capability commands include a first TLV package and a second TLV package. The first TLV package includes a byte identifying at least one consumer-related functionality; and The second TLV package includes a byte that identifies at least one IoT-related functionality.

22. A method for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the method comprising using an embedded universal integrated circuit card (eUICC): Receive terminal capability commands instructing that both the consumer context and the IoT context should be managed; Receive a consumer context switching command, wherein the consumer context switching command is provided in response to an identifier of at least one first condition, and under the at least one first condition, invoke at least one first function related to the consumer context; Based on the consumer context and the eSIM associated with the at least one consumer, and prior to receiving further notification: (i) process a specific function call including the first function call, and (ii) provide a first response to the specific function call; Receive an IoT context switching command, wherein the IoT context switching command is provided in response to an identifier of at least one second condition, and under the at least one second condition, invoke at least one second function related to the IoT context; and Based on the IoT context and the at least one IoT-related eSIM, and prior to receiving further notification: (i) process the specific function call including the second function call, and (ii) provide a second response to the specific function call.

23. The method according to claim 22, further comprising: Before receiving the terminal capability command: Provides indications of eUICC support for eUICC functionality.

24. The method of claim 22, wherein the terminal capability command is provided in response to a reset response (ATR) triggered by a power-on event or a reset event.

25. The method according to claim 22, further comprising: In response to the terminal capability command, confirmation is provided that both the consumer context and the IoT context are being managed.

26. The method of claim 22, further comprising: Receive the issuer security domain-root (ISD-R) selection command; as well as Provide a File Control Information (FCI) template that indicates both the consumer context and the IoT context.

27. The method of claim 22, wherein: The terminal capability commands include tag-length-value (TLV) encapsulation; as well as The TLV package includes a first byte and a second byte that respectively identify at least one consumer-related function and at least one IoT-related function.

28. The method according to claim 22, wherein: The terminal capability commands include a first TLV package and a second TLV package. The first TLV package includes a byte identifying at least one consumer-related functionality; and The second TLV package includes a byte that identifies at least one IoT-related functionality.

29. An apparatus configured to manage both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the apparatus comprising: One or more processors, the processors being communicatively coupled to a memory storing instructions for performing the method according to any one of claims 1 to 7.

30. The apparatus of claim 29, wherein the one or more processors include an application processor and / or a baseband processor.

31. A wireless device configured to manage both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the wireless device comprising: One or more antennas; Embedded Universal Integrated Circuit Card (eUICC); and One or more processors communicatively coupled to one or more antennas, the eUICC, and a memory storing instructions for performing the method according to any one of claims 1 to 7.

32. The wireless device of claim 31, wherein the one or more processors include an application processor and / or a baseband processor.

33. A non-transitory computer-readable medium storing instructions for managing both a consumer context and an IoT context with respect to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the instructions including instructions for performing the method according to any one of claims 1 to 7.

34. An apparatus configured to manage both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the apparatus comprising: One or more processors, the processors being communicatively coupled to a memory storing instructions for performing the method according to any one of claims 8 to 14.

35. The apparatus of claim 34, wherein the one or more processors include an application processor and / or a baseband processor.

36. A wireless device configured to manage both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the wireless device comprising: One or more antennas; Embedded Universal Integrated Circuit Card (eUICC); and One or more processors communicatively coupled to one or more antennas, the eUICC, and a memory storing instructions for performing the method according to any one of claims 8 to 14.

37. The wireless device of claim 36, wherein the one or more processors include an application processor and / or a baseband processor.

38. A non-transitory computer-readable medium storing instructions for managing both a consumer context and an IoT context with respect to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the instructions including instructions for performing the method according to any one of claims 8 to 14.

39. An embedded universal integrated circuit card (eUICC) configured to manage both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the eUICC comprising: One or more processors, the processors being communicatively coupled to a memory storing instructions for performing the method according to any one of claims 15 to 21.

40. A non-transitory computer-readable medium storing instructions for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the instructions including instructions for performing the method according to any one of claims 15 to 21.

41. An embedded universal integrated circuit card (eUICC) configured to manage both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the eUICC comprising: One or more processors, the processors being communicatively coupled to a memory storing instructions for performing the method according to any one of claims 22 to 28.

42. A non-transitory computer-readable medium storing instructions for managing both a consumer context and an IoT context relative to at least one consumer-related electronic subscriber identity module (eSIM) and at least one Internet of Things (IoT)-related eSIM, the instructions including instructions for performing the method according to any one of claims 22 to 28.

Images