Techniques for managing communications with wireless devices tagged for specific activity

Abstract

Techniques for managing communications with wireless devices that have been tagged due to a particular activity are set forth. In particular, these techniques effectively eliminate unnecessary interactions and enable enhanced user feedback when a tagged wireless device is attempting to interact with a mobile network operator (MNO). These techniques may be implemented by a variety of entities to achieve different and efficient results in a variety of scenarios. Such entities may include, for example: i) equipment identification registries that track unique identifiers of wireless devices that have been tagged due to a particular activity; ii) an MNO server, such as a SM-DP + server; and iii) a wireless device. Additionally, various components within the wireless devices may implement the techniques in different ways, including using an issuer security domain root (ISD-R) component, a local profile assistant (LPA), an electronic subscriber identity module (eSIM) component, and / or a baseband component included in the wireless devices.

Description

Technical Field

[0001] The described embodiments set forth techniques for managing communications with wireless devices that have been tagged for specific activities. Specifically, these techniques effectively eliminate unnecessary interactions and enable enhanced user feedback when wireless devices that have been tagged for specific activities are attempting to interact with a mobile network operator (MNO). Background Art

[0002] Many wireless devices are configured to use a removable universal integrated circuit card (UICC) that 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), wherein the ROM is configured to store an MNO profile that the wireless device can use to register and interact with the MNO to obtain wireless services via a cellular wireless network. The profile may also be referred to as a subscriber identity module (SIM). Typically, the UICC takes the form of a small removable card (often referred to as a SIM card) that is inserted into a UICC receiving area of ​​a mobile wireless device. In recent implementations, the UICC is embedded directly into the system board of the wireless device as an embedded UICC (eUICC), which may provide advantages over traditional removable UICCs. The eUICC may include a rewritable memory that may facilitate the installation, modification and / or deletion of one or more electronic SIM (eSIM) profiles on the eUICC, wherein the eSIM profile may provide new and / or different services and / or updates for accessing extended features provided by the MNO. In this regard, the eUICC may beneficially eliminate the need to include a UICC reception area in a wireless device.

[0003] In some cases, when interacting with a wireless device, the MNO may determine that the wireless device has been marked due to a specific activity. Exemplary specific activities may include, for example: the MNO identifies that two or more devices share a unique identifier and have attempted to interact with the MNO; the MNO receives (e.g., from a customer or other entity) a notification that a specific wireless device has been lost or stolen, etc. When the MNO determines that it is communicating with a marked wireless device, the MNO typically abandons the interaction with the wireless device. Unfortunately, before such abandonment occurs, the communication has been well underway, which causes a series of disadvantages. For example, provisioning an eSIM profile to a wireless device includes multiple stages to be completed, including operations occurring at the wireless device where the eSIM profile is to be installed, operations occurring at the manufacturer's server that manages the wireless device, and operations occurring at the MNO server from which the eSIM profile is downloaded and activated for service. In this regard, abandoning a partially completed eSIM profile provisioning process may waste power and network bandwidth consumption. In addition, the MNO has no mechanism to notify the wireless device that it has been marked, making it impossible for the wireless device to determine why further communication with the MNO is denied. This can be frustrating for innocent, unsuspecting users of tagged wireless devices that do not reveal the nature of the problem.

[0004] In view of the above considerations, a technique is needed that effectively eliminates unnecessary interactions and enables enhanced user feedback when a wireless device that has been tagged for a particular activity is attempting to communicate with an MNO. Summary of the invention

[0005] The present application describes techniques for managing communications with wireless devices that have been tagged for specific activities. Specifically, these techniques effectively eliminate unnecessary interactions and enable enhanced user feedback when the tagged wireless device is attempting to interact with a mobile network operator (MNO).

[0006] One embodiment describes a method for interacting with a wireless device that has been tagged for a specific activity. According to some embodiments, the method is primarily implemented by a provisioning server (e.g., a subscription manager-data preparation (SM-DP+) server) and includes: (1) receiving a client authentication request from a local profile assistant (LPA) of the wireless device, wherein the client authentication request includes at least one unique identifier associated with the wireless device; (2) providing the at least one unique identifier to an equipment identification registry, wherein the equipment identification registry manages unique identifiers of devices that have been tagged for a specific activity; (3) receiving a status of the wireless device from the equipment identification registry, wherein the status indicates that the wireless device has been tagged for a specific activity; and (4) providing the status of the wireless device to the LPA.

[0007] Another embodiment describes a method for interacting with a wireless device that has been tagged for a particular activity. According to some embodiments, the method is primarily implemented by a local profile assistant (LPA) of the wireless device and includes: (1) obtaining at least one unique identifier associated with the wireless device; (2) providing the at least one unique identifier to an equipment identification registry, wherein the equipment identification registry manages unique identifiers of devices that have been tagged for a particular activity; and (3) in response to receiving a status of the wireless device from the equipment identification registry, wherein the status indicates that the wireless device has been tagged for a particular activity, updating a configuration of the wireless device such that the wireless device is prohibited from performing at least one form of cellular network activity.

[0008] Yet another embodiment describes a method for interacting with a wireless device that has been flagged for a particular activity. According to some embodiments, the method is primarily implemented by an embedded universal integrated circuit card (eUICC) of the wireless device and includes: (1) receiving a network attachment failure notification from a baseband component of the wireless device; (2) providing a request to an issuer security domain root (ISD-R) component of the wireless device to suspend profile-related activities on the wireless device; and (3) updating a configuration of the wireless device such that the wireless device is prohibited from performing the profile-related activities.

[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 implement the methods and techniques described in the present disclosure. Still other embodiments include a hardware computing device that includes a processor that can be configured to cause the hardware computing device to implement the methods and techniques described in the present disclosure.

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

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

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

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

[0014] Figure 2 Illustrated according to some embodiments Figure 1 A block diagram of a more detailed view of certain components of a wireless device illustrated in FIG.

[0015] Figure 3 A sequence diagram illustrating a first (SM-DP+ centric) technique for interacting with a wireless device that has been tagged for a particular activity according to some embodiments.

[0016] Figure 4 Illustrated is a sequence diagram of a second (Local Profile Assistance (LPA) centric) technique for interacting with a wireless device that has been tagged for a particular activity in accordance with some embodiments.

[0017] Figure 5 A sequence diagram illustrating a third (embedded Universal Integrated Circuit Card (eUICC) centric) technique for interacting with a wireless device that has been tagged for a particular activity in accordance with some embodiments.

[0018] Figure 6 A conceptual diagram illustrating an exemplary user interface that may be displayed by a wireless device that has been tagged for a particular activity in accordance with some embodiments.

[0019] Figure 7 A block diagram illustrating exemplary elements of a mobile wireless device according to some embodiments is illustrated. DETAILED DESCRIPTION

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

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

[0022] The described embodiments describe techniques for interacting with wireless devices that have been tagged for specific activities. Specifically, these techniques effectively eliminate unnecessary interactions and enable enhanced user feedback when the tagged wireless device is attempting to interact with a mobile network operator (MNO).

[0023] The first technique may be implemented primarily by a mobile network operator (MNO) deployment server (e.g., SM-DP+ server) that interacts with a wireless device and an equipment identity registry. According to some embodiments, the equipment identity registry is an entity that manages a database of identifiers associated with wireless devices that have been marked due to specific activities. Additionally, entities within the wireless device may be involved in the technique, including a local profile assistant (LPA) and an issuer security domain root (ISD-R) configured to interface with the SM-DP+ server.

[0024] Under the first technique, the initial step may involve a triggering operation occurring on the wireless device, such as powering on the wireless device, a user attempting to cause the wireless device to perform an electronic subscriber identity module (eSIM) profile-related activity, and the like. The LPA may then collect wireless device information (e.g., one or more unique identifiers) associated with the wireless device and provide such information to the ISD-R. Next, the ISD-R may digitally sign the wireless device information and provide it to the LPA. The LPA may then issue a client authentication request to the SM-DP+ server, wherein the request includes the signed wireless device information. According to some embodiments, communication between the LPA and the SM-DP+ server may be performed using the ES9+ interface defined by the GSM Association (GSMA), which may be used to provide a secure communication channel between the SM-DP+ server and the LPA. However, any method may be used to enable the LPA and SM-DP+ to transmit information between each other without departing from the scope of the present disclosure.

[0025] Next, the SM-DP+ server issues a query to the Equipment Identity Registry, where the query includes the wireless device information received by the SM-DP+ server from the LPA. The query issued by the SM-DP+ server may include any additional information that may assist the Equipment Identity Registry in determining whether it should report back that the wireless device has been marked as a device of interest. The Equipment Identity Registry then uses the information received from the SM-DP+ server to determine whether the wireless device has been marked as a device of interest, and then issues a Client Authentication Response to the LPA. The Client Authentication may include any information that effectively informs the LPA whether the wireless device has been identified as a device of interest.

[0026] Next, when the wireless device has been flagged for a particular activity, the wireless device may provide feedback, for example, via a display device communicatively attached to the wireless device. According to some embodiments, the wireless device may display information indicating the nature of the reason why the wireless device is prohibited from further interacting with the SM-DP + server.

[0027] The second technique may be implemented primarily by a wireless device (particularly an LPA included in the wireless device). Under this approach, the LPA may interact with a baseband component instead of the ISD-R discussed above in conjunction with the first technique. In addition, the LPA may interact with an equipment identity registry instead of interfacing with an SM-DP+ server. In this regard, and in accordance with some embodiments, the LPA may communicate with the equipment identity registry (and vice versa) using any conceivable connection technology (e.g., using a Wi-Fi connection that can access the Internet, using a cellular data connection provided by an MNO, etc.).

[0028] According to some embodiments, the second technique may be initiated when some form of activity occurs at the wireless device. For example, the activity may include initial power-up of the wireless device (and by extension, initial power-up of the LPA and baseband). In another example, the activity may include the wireless device transitioning out of airplane mode (or an equivalent mode), causing components within the wireless device to reinitialize into an operational state. Subsequently, depending on device capabilities, program preferences, etc., two different sub-methods may be implemented.

[0029] According to some embodiments, the first sub-method involves the LPA sending wireless device information associated with the wireless device to an equipment identification registry. As discussed above, such information may include any conceivable information that effectively enables the equipment identification registry to determine whether the wireless device (or some component thereof) has been marked due to a particular activity. The equipment identification registry may then identify whether the wireless device (or some component thereof) has been marked due to a particular activity based on the information. Under any method used, the equipment identification registry ultimately returns a status message to the LPA that indicates whether the wireless device is a device of interest based on at least the equipment identification registry.

[0030] Alternatively, the second sub-method involves the baseband experiencing a network attachment failure. This may occur, for example, when the MNO to which the wireless device is attempting to attach determines that the wireless device has been tagged and refuses to allow the attachment to proceed. This scenario typically involves the MNO receiving an attachment request from the baseband, where the request includes at least one identifier associated with the wireless device. The MNO may then effectively determine whether the wireless device has been tagged for a particular activity, for example, by referencing its own internal management system, by interfacing with an equipment identification registry, and so on. In any case, in response to detecting a network attachment failure, the baseband may notify the LPA that the wireless device has been tagged for a particular activity.

[0031] Thus (and regardless of the sub-method utilized), the LPA is ultimately notified that the MNO (to which the wireless device is attempting to dock) has identified that the wireless device has been tagged and therefore will not be permitted to access wireless services provided by the MNO.

[0032] The LPA may then update any configuration of the wireless device to effectively prevent the wireless device from attempting to perform any number of activities that would be wasteful if the wireless device had been flagged. For example, the wireless device may be configured to not make any additional attempts to attach to the MNO, prohibit activities based on the eSIM profile, etc.

[0033] Next, when a triggering action is detected by the LPA (occurring when an activity occurs on the wireless device that violates the configuration update that occurred), the wireless device may provide feedback, for example, via a display device that is communicatively attached to the wireless device. In some cases, the feedback method may provide one or more options that permit the user to effectively bypass the configuration update implemented by the wireless device, which may be particularly useful in situations where the user believes that the flagged state of the wireless device has been deleted.

[0034] The third technique may be implemented primarily by a wireless device (particularly an eUICC included in the wireless device, which may include an ISD-R and an eSIM profile). Under this method, the eUICC may interact with the baseband component and the LPA of the wireless device. As with the above techniques, the third technique may be invoked in response to some form of activity occurring at the wireless device. Subsequently, depending on device capabilities, program preferences, etc., two different sub-methods may be implemented.

[0035] According to some embodiments, the first sub-method involves the eSIM profile issuing a request to the baseband to receive one or more notifications when the baseband experiences a network attachment failure (as described above, this may occur when the wireless device is prohibited from accessing wireless services provided by the MNO while identifying that the wireless device has been flagged due to a particular activity). Then, if / when the baseband detects a network attachment failure, the baseband provides a notification of the network attachment failure to the eSIM profile. At this point, the eSIM profile is aware that a network attachment failure has occurred (and that the wireless device has been flagged). Therefore, the eSIM profile interfaces with the ISD-R to cause the ISD-R to perform a configuration update that effectively prevents the wireless device from attempting to perform any number of activities that would be wasteful if the wireless device had been flagged. For example, this may include a request to suspend profile-related activities on the wireless device until at least one condition is met.

[0036] Alternatively, the second sub-method omits eSIM profile registration to receive a network attachment failure notification from the baseband (as described above in the first sub-method). Alternatively, the baseband may be (e.g., pre-) configured to notify the ISD-R of any network attachment failure experienced by the baseband. For example, this approach may be useful when the wireless device does not possess any eSIM profiles and is attempting to interface with the MNO (or other entity) to download an eSIM profile to access wireless services. In any case, when the baseband realizes that a network attachment failure has occurred (and the wireless device has been flagged), the baseband may interface with the ISD-R. Specifically, the baseband may cause the ISD-R to perform the same or similar configuration update described above in conjunction with the first sub-method.

[0037] Thus (and regardless of the sub-method utilized), the ISD-R is ultimately notified that the MNO (to which the wireless device is attempting to dock) has identified that the wireless device has been tagged and will therefore deny wireless service to the wireless device. The ISD-R may then update any configuration of the wireless device to effectively prevent the wireless device from attempting to perform any number of activities (such as those described herein) that would be wasteful if the wireless device had been tagged. Additionally, it is noted that other entities included within the wireless device (other than the ISD-R) may perform configuration updates without departing from the scope of this disclosure.

[0038] Next, one or more triggering operations may occur at the wireless device that attempt to violate the aforementioned configuration updates, such as those described above in conjunction with the first and second techniques. In response, the LPA may issue a request to the ISD-R for information associated with the eUICC and / or a challenge-based response from the eUICC. According to some embodiments, the ES10b function defined by the GSM Association (GSMA) may be used to facilitate the request for information associated with the eUICC, but it should be noted that any protocol may be utilized to enable the LPA and the ISD-R to communicate with each other without departing from the scope of the present disclosure. Subsequently, the ISD-R may indicate to the LPA that the configuration update has achieved a suspension of profile-related activities on the wireless device until at least one condition is met. Finally, according to the techniques described herein, the wireless device may provide feedback, for example, via a display device that is communicatively attached to the wireless device.

[0039] It is noted that the first, second, and third techniques discussed above need not be implemented in isolation. Rather, any number of these methods (partially or fully, and individually or in combination) may be implemented to achieve the desired result (regarding the management of wireless devices that have been equipped with an identification registry tag) without departing from the scope of the present disclosure. Additionally, it is noted that once applied, the configuration updates discussed herein may be modified (or revoked) when one or more conditions are met, details of which will be described in more detail below.

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

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

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

[0043] Additionally and as Figure 1As shown, the system 100 may include at least one equipment identification registry 120. According to some embodiments, the equipment identification registry 120 represents an entity that manages a database of identifiers associated with wireless devices 102 (e.g., an International Mobile Equipment Identity (IMEI) identifier of the wireless device 102, an identifier (EID) of an eUICC 108 included in the wireless device 102, an identifier of a physical SIM card that can be inserted into the wireless device 102, etc.), which have been marked due to specific activities. Such activities may include, for example, the MNO 114 identifying that two or more wireless devices 102 sharing an identifier are attempting to access the MNO 114, indicating that at least one of the two or more wireless devices 102 is attempting to spoof the identifier of another wireless device of the two or more wireless devices 102. In another example, the MNO 114 (or some other entity) may report a theft event of the wireless device 102 to the equipment identification registry 120.

[0044] It is noted that the equipment identification registry 120 is not limited to managing only information regarding malicious activity associated with wireless devices 102. Rather, the equipment identification registry 120 may track wireless devices 102 based on other points of interest, including wireless devices 102 that have been reported as lost, wireless devices 102 that have exhibited suspicious behavior, wireless devices 102 associated with flagged or delinquent service accounts, etc. It is again noted that the foregoing examples are not meant to represent an exhaustive list, and the equipment identification registry 120 may track any wireless device 102 for any reason without departing from the scope of the present disclosure.

[0045] Additionally, it is noted that in addition to the identifier of the wireless device 102, the equipment identification registry 120 may also store any additional information that indicates the nature of the reason why the equipment identification registry 120 is tracking the wireless device 102. For example, for a given wireless device 102, the equipment identification registry 120 may store indications of one or more underlying reasons why the equipment identification registry 120 is tracking the wireless device 102. Such indications may include, for example, values ​​indicating why the wireless device 102 was first reported to the equipment identification registry 120 (or identified by the equipment identification registry 120) (e.g., one or more of the reasons discussed above), the amount of time that the wireless device 102 was tracked by the equipment identification registry 120, the number of times that the equipment identification registry 120 tracked the wireless device 102, and the like. Such information may beneficially enable the equipment identification registry 120 to make an informed decision as to whether and when to no longer track the wireless device 102, particularly in the absence of instructions from the MNO 114 or in the absence of knowledge of how to proceed after the wireless device 102 was initially reported to the equipment identification registry 120. Again, note that the foregoing examples are not intended to represent an exhaustive list, and the equipment identification registry 120 may store any additional information related to the identifier of the wireless device 102 without departing from the scope of the present disclosure.

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

[0047] Likewise Figure 2 As shown, the baseband radio circuit 110 of the wireless device 102 may include a baseband OS 214 configured to manage the hardware resources (e.g., processor, memory, different radio components, etc.) of the baseband radio circuit 110. According to some embodiments, the baseband radio circuit 110 may implement a baseband manager 216 configured to interface with the eUICC 108 to establish a secure channel with the MNO provisioning server 116 and obtain information (such as eSIM profile data) from the MNO provisioning server 116 for managing the eSIM profiles 208. The baseband manager 216 may be configured to implement services 218, which represent a collection of software modules instantiated by various applets 212 included in the eUICC 108 for enabling eSIM profiles 208. For example, the services 218 may be configured to manage different connections between the wireless device 102 and the MNO 114 according to different eSIM profiles 208 enabled within the eUICC 108.

[0048] Figure 3 A sequence diagram 300 is illustrated of a first technique for interacting with a wireless device 102 that has been tagged for a particular activity in accordance with some embodiments. Figure 3 As shown, the technology can be mainly implemented by the SM-DP+ server 304, which can represent, for example, Figure 1 In this approach, the SM-DP+ server 304 can interact with the wireless device 102 and the equipment identity registry 302 to perform the techniques described in more detail below.

[0049] like Figure 3 As shown, the SM-DP+ server 304 may be configured to interact with the equipment identification registry 302, which may be represented in Figure 1 An equipment identification registry in the equipment identification registry 120 illustrated in and described herein. Additionally, Figure 3Entities within the wireless device 102 may be involved in the techniques illustrated in . Specifically, these entities may include a local profile assistant (LPA) 306, which may be configured to interface with the SM-DP+ server 304. According to some embodiments, the LPA 306 represents a functional element that provides local profile download functionality, local discovery service functionality, and local user interface features. Additionally, these entities may include an issuer security domain root (ISD-R) 308 configured to manage eSIM profiles on the wireless device 102, which may include, for example, an initial profile that can be used to establish a network connection with the SM-DP+ server 304. The ISD-R 308 may also provide authentication techniques, such as those discussed in more detail below in conjunction with step 356.

[0050] like Figure 3 As shown, the initial step 352 may involve any device activity occurring on the wireless device 102 that causes the sequence diagram 300 to be invoked. For example, the device activity may represent an end user powering on the wireless device 102. In another example, the device activity may represent the wireless device 102 attempting to attach to an MNO in order to download an eSIM profile, access wireless services using an existing eSIM profile, etc. It is noted that the foregoing examples are not intended to represent an exhaustive list, and any activity occurring on the wireless device 102 may constitute an example of a wireless device 102 that is not intended to be an exhaustive list. Figure 3 The device activities illustrated in the figure may be performed without departing from the scope of the present disclosure.

[0051] Next, at step 354, LPA 306 may collect wireless device information associated with wireless device 102 and provide such information to ISD-R 308. Figure 3 As shown, the wireless device information may include, but is not limited to, one or more identifiers associated with the wireless device 102 itself (e.g., an International Mobile Equipment Identity (IMEI)), one or more identifiers associated with components of the wireless device 102 (e.g., an identifier (EID) of the eUICC 108 included in the wireless device 102, an identifier of a physical SIM card inserted into the wireless device 102, etc.), etc. It should be noted that the foregoing examples are not intended to represent an exhaustive list, and any identifier associated with the wireless device 102 may be collected and provided without departing from the scope of the present disclosure.

[0052] Next, at step 356, the ISD-R 308 digitally signs the wireless device information. For example, this may involve the ISD-R 308 accessing one or more cryptographic keys known to the ISD-R 308 and utilizing these keys to establish a digital signature based on (i.e., linked to) the wireless device information. According to some embodiments, the cryptographic scheme utilized may enable the SM-DP+ server 304 to reliably determine that the ISD-R 308 (and, by extension, the wireless device 102) is authentic and known to the SM-DP+ server 304. For example, if the ISD-R 308 establishes a digital signature using a private key that is unique and accessible to the ISD-R 308, the SM-DP+ server 304 may utilize a corresponding public key that is accessible (and known) to the SM-DP+ server 304 to verify the digital signature. Note that the foregoing examples are not intended to represent an exhaustive list, and any cryptographic scheme (or other authentication scheme) may be utilized to enable the SM-DP+ server 304 to effectively identify the wireless device 102 as authentic and known to the SM-DP+ server 304.

[0053] At step 358, LPA 306 issues a client authentication request to SM-DP+ server 304, wherein the request includes the signed wireless device information. According to some embodiments, communication between LPA 306 and SM-DP+ server 304 may be performed using the ES9+ interface defined by the GSM Association (GSMA), which may be used to provide a secure communication channel between SM-DP+ server 304 and LPA 306. When using this protocol, Figure 3 The client authentication request illustrated in the example may represent the ES9+.AuthenticateClient function. It should be noted that utilizing ES9+ in step 358 and step 364 discussed below is an example method that may be utilized and is not meant to be limiting. Instead, any method may be utilized to enable the SM-DP+ server 304 and the LPA 306 to communicate information between each other without departing from the scope of the present disclosure.

[0054] At step 360, the SM-DP+ server 304 issues a query to the equipment identification registry 302, wherein the query includes the wireless device information received by the SM-DP+ server 304 from the LPA 306. According to some embodiments, the equipment identification registry 302 may represent the above-mentioned Figure 1 One of the discussed equipment identification registries 120. As discussed herein, the query issued by the SM-DP+ server 304 may include any additional information that may assist the equipment identification registry 302 in determining whether it should report back that the wireless device 102 has been marked as a device of interest.

[0055] At step 362, the equipment identification registry 302 uses the information received from the SM-DP+ server 304 to determine whether the wireless device 102 has been marked as a device of interest. According to some embodiments, and under a simple approach, the equipment identification registry 302 may return a Boolean value indicating whether an entry for the wireless device 102 exists in a database accessible to the equipment identification registry 302 (thereby inherently indicating that the wireless device 102 is a device of interest). Under a more complex approach, the equipment identification registry 302 may analyze any information it has on the wireless device 102 (or any additional information it may access through other entities known to the wireless device 102) to effectively determine whether the wireless device 102 is a device of interest. Under any approach used, the equipment identification registry 302 ultimately returns a status message to the SM-DP+ server 304 indicating whether the wireless device 102 is a device of interest.

[0056] At step 364, the SM-DP+ server 304 issues a client authentication response to the LPA 306. According to some embodiments, and as described above, the communication between the SM-DP+ server 304 and the LPA 306 may be performed using the ES9+ interface defined by the GSM Association (GSMA), which may be used to provide a secure communication channel between the SM-DP+ server 304 and the LPA 306. When using this protocol, Figure 3 The client authentication response illustrated in the example may represent the ES9+.AuthenticateClient function. It should be noted again that utilizing ES9+ in steps 358 and 364 is an example method that may be utilized and is not meant to be limiting. Instead, any method may be utilized to enable the SM-DP+ server 304 and the LPA 306 to communicate with each other without departing from the scope of the present disclosure.

[0057] In any case, the client authentication response issued by the SM-DP+ server 304 may include any information that effectively informs the LPA 306 whether the wireless device 102 has been identified as a device of interest. Currently, the GMSA standard is deficient in status codes that can be used to communicate the various reasons why the wireless device 102 is designated as a device of interest (e.g., duplicate identifier, stolen, lost, business reasons, time reasons, etc.). Therefore, this deficiency can be remedied by supplementing the GMSA standard with a certain number of status codes that are commensurate with the desired level of granularity that represents the aforementioned additional information and should be reported to the LPA 306. It should be noted that the aforementioned examples are not intended to be limiting, and the SM-DP+ server 304 and the LPA 306 may implement any reasonable method to effectively communicate whether the wireless device 102 is a device of interest without departing from the scope of the present disclosure, including methods that do not rely on the GMSA standard.

[0058] Additionally, it is noted that the SM-DP+ server 304 may be configured to provide any number of status codes required to accurately convey the nature of the problem (if any) to the wireless device 102. For example, one or more status codes may be utilized to indicate that the IMEI of the wireless device 102 is valid, but its EID has been marked by the equipment identification registry 302. In another example, one or more status codes may be utilized to indicate that one or more aspects of a wireless device 102 having two or more IMEIs / EIDs, etc. (e.g., a dual SIM device) have been marked. For example, the status code may indicate that one of the IMEIs / EIDs / etc. is valid, but the others are invalid. It is noted that the foregoing examples are not intended to be limiting, and any information in any format may be transmitted between the SM-DP+ server 304 and the wireless device 102 in a manner that enables the wireless device 102 to understand the nature of the problem in detail.

[0059] At step 366, the wireless device 102 may provide feedback, for example, via a display device communicatively attached to the wireless device 102. According to some embodiments, the wireless device 102 may display information indicating the nature of why the wireless device 102 is prohibited from further interacting with the SM-DP + server 304. It is noted that any method may be utilized to best help the user understand the nature of the problem. For example, this may include the wireless device 102 displaying suggestive information on how to remedy the problem. This may be particularly useful for unsuspecting / innocent individuals in possession of the credentials, effectively removing the wireless device 102 from the list of devices of interest from the perspective of the equipment identification registry 302. This may also alert malicious users that their behavior has been identified and that the wireless device 102 will not be able to attach to the network, which may beneficially cause such users to abandon the wireless device 102. Additionally, in certain scenarios (such as a spoofed device or a device reported as stolen), the wireless device 102 may alert the user that additional information has been reported to the relevant authorities and that the wireless device should be returned to an authorized location immediately. It should be noted that the foregoing examples do not represent an exhaustive list, and the wireless device 102 may take any conceivable course of action upon receiving information from the SM-DP+ server 304 without departing from the scope of the present disclosure.

[0060] therefore, Figure 3 A SM-DP+ server-centric approach is described for eliminating unnecessary interactions and enabling enhanced user feedback when a tagged wireless device is attempting to interact with an MNO.

[0061] Figure 4 A sequence diagram 400 is illustrated of a second technique for interacting with a wireless device 102 that has been tagged for a particular activity in accordance with some embodiments. Figure 4As shown, these techniques may be primarily implemented by the wireless device 102, and in particular, a local profile assistant (LPA) 404 included in the wireless device 102. Under this approach, the LPA 404 may communicate with a baseband 406 (e.g., Figure 2 The baseband radio circuit 110) interacts with the baseband radio circuit 110, rather than in conjunction with the above Figure 3 In addition, LPA 404 can interact with equipment identification registry 402 (e.g., Figure 1 The device identification registry 120) is used to interact with the SM-DP+ server (such as the one described above in conjunction with Figure 3 In this regard, and in accordance with some embodiments, the LPA 404 may communicate with the equipment identity registry 402 (and vice versa) using any conceivable connection technology (e.g., using a Wi-Fi connection that can access the Internet, using a cellular data connection provided by the MNO, etc.).

[0062] like Figure 4 As shown, the sequence diagram 400 begins at step 452, which may involve some form of activity occurring at the wireless device 102. For example, the activity may include initial power-up of the wireless device 102 (and, by extension, initial power-up of the LPA 404 and baseband 406). In another example, the activity may include the wireless device 102 transitioning out of airplane mode (or an equivalent mode) such that components within the wireless device 102 are reinitialized into an operational state. In yet another example, the activity may include the wireless device 102 processing a software update that causes one or more components of the wireless device 102 (or the wireless device 102 itself) to restart. It is noted that the foregoing examples are not intended to be limiting, and step 452 may represent any activity on the wireless device 102 without departing from the scope of the present disclosure. Furthermore, it is noted that step 452 may be optional. For example, the remaining steps of the sequence diagram 400 may be performed on a periodic basis, upon direct request (e.g., from a user or other entity), and so forth. Next, as the sequence 400 proceeds, two different methods (method 454 or method 460) may be used.

[0063] like Figure 4As shown, method 454 involves step 456, in which LPA 404 sends wireless device information associated with wireless device 102 to equipment identification registry 402. As discussed above, such information may include any conceivable information that effectively enables equipment identification registry 402 to determine whether wireless device 102 (or some component thereof) has been marked due to a particular activity. Such information may include, for example, the IMEI of wireless device 102, the EID of eUICC 108 included in wireless device 102, and the like. Then, at step 458, equipment identification registry 402 may utilize the above in conjunction with the wireless device identification registry 402 to send wireless device information associated with wireless device 102. Figure 3 The same technique (or similar technique) described in step 362 of FIG. 4 is used to identify whether the wireless device 102 (or a component thereof) has been marked for a particular activity. Under any method used, the equipment identification registry 402 ultimately returns a status message to the LPA 404, which indicates whether the wireless device 102 is a device of interest based on at least the equipment identification registry 402.

[0064] Alternatively, the method 460 involves the baseband 406 experiencing a network attachment failure at step 462. This may occur, for example, when the MNO to which the wireless device 102 is attempting to attach determines that the wireless device 102 has been tagged and refuses to allow the attachment to proceed. This scenario typically involves the MNO receiving an attachment request from the baseband 406, where the request includes at least one identifier associated with the wireless device 102. The MNO may then effectively determine whether the wireless device 102 has been tagged for a particular activity, such as by referencing its own internal management system, by interfacing with the equipment identification registry 120, and so on. In any case, at step 464, the baseband 406 may notify the LPA 404 that a connection failure has occurred, which communicates to the LPA 404 that the wireless device has been tagged for a particular activity.

[0065] Thus, regardless of whether method 454 or 460 is utilized, LPA 404 is ultimately notified that the MNO (to which wireless device 102 is attempting to dock) has identified that wireless device 102 has been tagged and therefore will not be permitted to access wireless services provided by the MNO.

[0066] Then, at step 468, the LPA 404 may update any configuration of the wireless device 102 to effectively prevent the wireless device 102 from attempting to perform any number of activities that would be wasteful if the wireless device 102 had been flagged. For example, the configuration of the wireless device 102 may be updated so that the wireless device 102 will not make any additional attempts to attach to the MNO. The configuration of the wireless device 102 may also be updated so that the wireless device 102 will prohibit activities based on the eSIM profile, such as downloading a new profile, modifying an existing profile, deleting an existing profile, etc. It is noted that the aforementioned activities are exemplary and are not meant to represent an exhaustive list. Instead, the configuration updates discussed herein may be for any activity that is desired to be modified / prohibited on the wireless device 102 when the wireless device 102 is identified as a device of interest by the equipment identification registry 120.

[0067] Additionally, it is noted that once applied, the configuration updates discussed herein may be modified (or revoked) when one or more conditions are met. For example, a given condition may be met when a particular "cooling off" period of time has passed. In another example, a given condition may be met when the wireless device 102 (or a component thereof) is power cycled. In yet another example, a given condition may be met when a physical SIM card is removed from and / or inserted into the wireless device 102 or an eSIM profile is switched (i.e., disabled and enabled). In another example, a given condition may be met when the wireless device 102 receives a notification that it is no longer marked as a device of interest. It is noted that the foregoing conditions are not meant to represent an exhaustive list, and any condition and any combination of conditions may be implemented to effectively determine when to modify / revoke the configuration updates discussed herein.

[0068] Step 470 occurs when a triggering operation is detected, which indicates that the LPA 404 detected (or was notified of) an activity occurring on the wireless device 102 that violated the configuration update that occurred at step 468. For example, the triggering operation may indicate that the wireless device 102 attempted to download an eSIM profile to the wireless device 102, the wireless device 102 reattempted to attach to the MNO despite being marked as a device of interest, or other similar operations. In response, at step 472, the wireless device 102 may provide feedback, for example, via a display device that is communicatively attached to the wireless device 102. As described above in conjunction with Figure 3 As discussed in step 366 of step 470, the wireless device 102 may display information indicating the nature of the reason why the wireless device 102 is prohibited from performing the operation detected at step 470. Again, it is noted that any method may be utilized to best assist the user in understanding the nature of the problem, including displaying detailed information about the problem itself, detailed suggestions on how to remedy the problem, etc.

[0069] Additionally, it is noted that in some embodiments, the feedback method may provide an option to permit the user to effectively bypass the configuration update performed by the wireless device 102 at step 468. For example, when the triggering operation at step 470 involves a user request to download and / or install a new eSIM profile, the wireless device 102 may inform the user that if the wireless device 102 has been marked as a device of interest, the operation may not result in the wireless device 102 successfully attaching to the MNO. In another example, when the triggering operation at step 470 involves a user request to attach to the MNO (e.g., using an existing SIM / eSIM profile), the wireless device 102 may warn of multiple failed attachment attempts that have occurred due to the wireless device being marked as a device of interest, but at the same time enable the user to have the wireless device 102 attempt to reattach to the MNO anyway. It is noted that the above examples are not meant to be exhaustive, and the feedback at step 472 may enable the user to perform any number of operations related to the configuration update and triggering operations of steps 468 and 470, respectively.

[0070] therefore, Figure 4 An LPA-centric approach is described for eliminating unnecessary interactions and enabling enhanced user feedback when a tagged wireless device is attempting to interact with an MNO.

[0071] Figure 5 A sequence diagram 500 is illustrated of a second technique for interacting with a wireless device 102 that has been tagged for a particular activity in accordance with some embodiments. Figure 5 As shown, the technology can be mainly implemented by the wireless device 102 (particularly the eUICC 108 included in the wireless device 102, which can include the ISD-R 504 and the eSIM profile 506). Under this method, the eUICC 108 can communicate with the baseband 508 (e.g., Figure 2 10) and LPA 502. These various entities may communicate with each other using any conceivable connection technology.

[0072] In brief (although Figure 5500 ), it is noted that the sequence diagram 500 may begin with some form of activity occurring at the wireless device 102. For example, the activity may include initial power-up of the wireless device 102 (and, by extension, initial power-up of the LPA 502, the eUICC 108, and the baseband 508). In another example, the activity may include the wireless device 102 transitioning out of airplane mode (or an equivalent mode) such that components within the wireless device 102 are reinitialized into an operational state. In yet another example, the activity may include the wireless device 102 loading an eSIM profile 506 for accessing wireless services provided by a given MNO. For example, the eSIM profile 506 may represent a bootstrap eSIM profile that permits the wireless device 102 to access limited wireless services in order to connect to the MNO and download other eSIM profiles to access extended / enhanced wireless services. It is noted that the foregoing examples are not intended to be limiting, and any activity on the wireless device 102 may occur prior to the sequence diagram 500 without departing from the scope of the present disclosure.

[0073] like Figure 5 As shown, when sequence 500 is executed, two different methods (method 550 or method 560) may be utilized. According to some embodiments, method 550 may involve step 552, where when baseband 508 experiences a network attachment failure, eSIM profile 506 issues a request to baseband 508 to receive one or more notifications. As described herein, a network attachment failure may occur when wireless device 102 is prohibited from accessing wireless services provided by an MNO while identifying that wireless device 102 has been flagged due to a specific activity. For example, this prohibition may be implemented using MNO-centric techniques and / or any of the techniques described herein for identifying scenarios in which wireless device 102 has been flagged due to a specific activity.

[0074] Next, in method 550, the baseband 508 detects a network attachment failure at step 554 (which again indicates that the wireless device 102 has been flagged due to a particular activity). In response (and because the eSIM profile 506 is registered to receive notifications of such events via step 552), the baseband 508 provides notification of the network attachment failure to the eSIM profile 506 at step 556. At this point, the eSIM profile 506 is aware that a network attachment failure has occurred (and that the wireless device 102 has been flagged). Therefore, at step 558, the eSIM profile 506 interfaces with the ISD-R 504 to cause the ISD-R 504 to perform a configuration update that effectively prevents the wireless device 102 from attempting to perform any number of activities that would be wasteful if the wireless device 102 had been flagged. For example, this may include a request to suspend profile-related activities on the wireless device 102 until at least one condition is satisfied. Such a configuration update occurs at step 568, which will be discussed in more detail below.

[0075] Alternatively, method 560 omits eSIM profile 506 registration to receive network attachment failure notifications from baseband 508 (as described above in connection with step 552 under method 550). Alternatively, baseband 508 may be configured (e.g., in advance) to notify ISD-R 504 of any network attachment failures experienced by baseband 508. This approach may be useful, for example, when wireless device 102 does not possess any eSIM profiles and is attempting to interface with an MNO (or other entity) to download an eSIM profile to access wireless services. In any case, baseband 508 is aware that a network attachment failure has occurred (and wireless device 102 has been tagged). Therefore, at step 564, baseband 508 interfaces with ISD-R 504 to cause ISD-R 504 to perform a configuration update that effectively prevents wireless device 102 from attempting to perform any number of activities that would be wasteful if wireless device 102 had been tagged. Again, this may include a request to suspend profile-related activities on wireless device 102 until at least one condition is satisfied. This configuration update occurs at step 568, which will be discussed in more detail below.

[0076] At step 568, the ISD-R 504 may update any configuration of the wireless device 102 to effectively prevent the wireless device 102 from attempting to perform any number of activities that would be wasteful if the wireless device 102 had been tagged. For example, the configuration of the wireless device 102 may be updated so that the wireless device 102 will not make any additional attempts to attach to the MNO. The configuration of the wireless device 102 may also be updated so that the wireless device 102 will prohibit activities based on the eSIM profile, such as downloading a new profile, modifying an existing profile, deleting an existing profile, etc. It is noted that the aforementioned activities are exemplary and are not meant to represent an exhaustive list. Rather, when the equipment identification registry 120 is tracking the wireless device 102, the configuration updates discussed herein may be for any activities on the wireless device 102 that are desired to be modified / prohibited.

[0077] Note that although the sequence diagram 500 relates to the ISD-R 504 performing the configuration update, other entities included within the wireless device 102 may perform the configuration update without departing from the scope of the present disclosure. For example, the ISD-R 504 may interface with the LPA 502 to perform some or all of the configuration update that occurs at step 568 (e.g., as described above in conjunction with Figure 4 Additionally, and as previously described herein, the applied configuration update may be modified (or revoked) by the ISD-R 504, LPA 502, or any other appropriate / capable entity within the wireless device 102 when one or more conditions are met.

[0078] Step 570 occurs when a triggering operation is detected, which indicates that the LPA 502 detects (or is notified of) activities occurring on the wireless device 102 that, if permitted, would violate the configuration update implemented at step 568. The triggering operation may include, for example, the above-mentioned respective combinations of Figure 3 and Figure 4 Those triggering operations described in steps 352 and 470.

[0079] In response, at step 572, the LPA 502 issues a request to the ISD-R 504 for information associated with the eUICC 108 and / or a challenge-based response from the eUICC 108. According to some embodiments, the request for information associated with the eUICC 108 may be facilitated using the ES10b "GetEUICCChallenge" function defined by the GSM Association (GSMA), while the request for a challenge-based response from the eUICC 108 may be facilitated using the ES10b "GetUICCInfo" function also defined by the GSMA. It is noted that the use of the aforementioned ES10b functions at step 572 constitutes an example method and is not meant to be limiting. Instead, any method may be used to enable the LPA 502 and the ISD-R 504 to communicate information between each other without departing from the scope of the present disclosure.

[0080] In any case, at step 574, the ISD-R 504 may indicate to the LPA 502 that the configuration update that occurred in conjunction with step 568 enables a suspension of profile-related activities on the wireless device 102 until at least one condition is satisfied.

[0081] At step 576, the wireless device 102 may provide feedback, for example, via a display device that is communicatively attached to the wireless device 102. Figure 3 and Figure 4 As discussed in steps 366 and 472 of , the wireless device 102 may display information indicating the nature of the reason why the wireless device 102 is prohibited from performing the operation detected at step 570. Again, it is noted that any method may be utilized to best assist the user in understanding the nature of the problem, including displaying detailed information about the problem itself, detailed suggestions on how to remedy the problem, etc. In addition, and as previously described herein, the feedback method may provide an option to permit the user to effectively bypass the configuration update implemented by the wireless device 102 at step 568.

[0082] therefore, Figure 5 An eUICC-centric approach is described for eliminating unnecessary interactions and enabling enhanced user feedback when a branded wireless device is attempting to interact with an MNO.

[0083] Please note that the above is combined with Figure 3 , Figure 4 and Figure 5 The sequence diagrams 300, 400, and 500 discussed need not be implemented in isolation. Rather, any number of these methods (partially or fully, and individually or in combination) may be implemented to achieve the desired results (regarding managing wireless devices 102 that have been tagged by the equipment identification registry 120) without departing from the scope of the present disclosure.

[0084] Figure 6 A conceptual diagram 600 illustrates an exemplary user interface that may be displayed by a wireless device 102 that has been tagged for a particular activity in accordance with some embodiments. Figure 6 As shown, the wireless device 102 may display a user interface 602, which may constitute, for example, a lock screen or a welcome screen of the wireless device 102. Specifically, the wireless device 102 may execute Figure 3 , Figure 4 and / or Figure 5 After one or more steps of , the user interface 602 is displayed, wherein the wireless device 102 effectively identifies / determines that it has been tagged due to a particular activity. For example, the wireless device 102 may execute Figure 3 Steps 352-364, Figure 4 Steps 452-470 and / or Figure 5 After steps 550-574, user interface 602 is displayed. Figure 6 As shown, user interface 602 may indicate established connectivity, such as a bar indicating the overall strength of a cellular network connection (if any), a Wi-Fi icon indicating a Wi-Fi connection (if any), etc. Figure 6 In the example illustrated in , the user interface 602 shows an empty cellular network connection bar because the wireless device 102 has identified / determined that it has been flagged due to a particular activity and is therefore not permitted to access wireless services provided by the MNO.

[0085] The next user interface 604 may be displayed in response to, for example, a user providing appropriate input to advance to the next user interface 604. Figure 6 As shown, the user interface 604 can convey to the user of the wireless device 102 that the wireless device 102 has been flagged for a particular activity and is therefore prohibited from participating in cellular network activities. In this regard, the user interface 604 can represent, for example, the above-mentioned respective combinations of Figure 3 , Figure 4 and Figure 5 Described feedback steps 366, 472, and 576. Additionally, and as previously described herein, the user may be presented with one or more options to select in response to the notification.

[0086] The next user interface 606 may be displayed in response to the user selecting to continue after receiving the notification displayed in the user interface 604. Figure 6As shown, user interface 606 may enable a user to select from a variety of options that constitute a cellular network activity desired by the user. Such activities may include, for example, downloading an eSIM profile to the wireless device 102, performing management operations on an existing eSIM profile installed on the wireless device 102, attempting to connect to one or more MNOs using an existing eSIM profile installed on the wireless device 102, and the like. It is noted that the foregoing activities do not constitute an exhaustive list of options, and any number of user interfaces may be provided to permit a user to attempt to invoke any form of cellular network (or other) activity without departing from the scope of the present disclosure.

[0087] In any case, when the user selects the option, the wireless device 102 may display a user interface 608 that warns the user that the operation may fail because the wireless device 102 has been flagged for a particular activity (e.g., as described above in connection with Figure 4 If the user chooses to attempt the operation, an additional user interface 610 may be displayed to inform the user of the result of the attempt. Figure 6 As shown, user interface 610 may notify the user of the operation failure and provide a recommended course of action for remediating the problem. Figure 6 ), user interface 610 may notify the user that the operation was successful. For example, if wireless device 102 has been excluded as a device of interest before attempting to perform the operation, such a result may occur, in which case the operation will have a chance to succeed.

[0088] Please note that Figure 6 The user interfaces illustrated in (and described herein) are exemplary only and are not meant to be limiting in any way. Rather, any number of user interfaces may be implemented to effectively inform users of the various issues and processes described throughout this disclosure without departing from its scope.

[0089] Figure 7 1 shows a detailed view of a representative computing device 700 that can be used to implement the various methods described herein according to some embodiments. In particular, the detailed view shows various components that can be included in the wireless device 102. Figure 7As shown, the computing device 700 may include a processor 702 representing a microprocessor or a controller for controlling the overall operation of the computing device 700. The computing device 700 may also include a user input device 708 that allows a user of the computing device 700 to interact with the computing device 700. For example, the user input device 708 can take a variety of forms, such as buttons, keypads, dials, touch screens, audio input interfaces, visual / image capture input interfaces, inputs in the form of sensor data, etc. Further, the computing device 700 can include a display 710 that can be controlled by the processor 702 to display information to the user. The data bus 716 can facilitate data transmission between at least the storage device 740, the processor 702, and the controller 713. The controller 713 can be used to interact with and control different equipment through the equipment control bus 714. The computing device 700 may also include a network / bus interface 711 that is communicatively coupled to the data link 712. In the case of a wireless connection, the network / bus interface 711 may include a wireless transceiver.

[0090] The computing device 700 also includes a storage device 740, which may include a single disk or multiple disks (e.g., a hard drive), and includes a storage management module that manages one or more partitions within the storage device 740. In some embodiments, the storage device 740 may include flash memory, semiconductor (solid-state) memory, etc. The computing device 700 may also include a random access memory (RAM) 720 and a read-only memory (ROM) 722. The ROM 722 may store programs, utilities, or processes to be executed in a non-volatile manner. The RAM 720 may provide volatile data storage and store instructions related to the operation of the computing device 700. The computing device 700 may also include a secure element (SE) 724, such as an eUICC 108, a UICC 118, or another secure storage for cellular wireless system access by the wireless device 102.

[0091] Wireless Terminology

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

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

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

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

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

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

Claims

1. A method for interacting with a wireless device that has been marked for a particular activity, the method comprising, at an SM-DP+ server: receiving a client authentication request from a local profile assistant (LPA) of the wireless device, wherein the client authentication request includes at least one unique identifier associated with the wireless device; providing the at least one unique identifier to an equipment identification registry, wherein the equipment identification registry manages unique identifiers of devices that have been tagged for a particular activity; receiving a status of the wireless device from the equipment identification registry, wherein the status indicates that the wireless device has been tagged for a particular activity; as well as The status of the wireless device is provided to the LPA.

2. The method of claim 1, wherein the client authentication request is provided by the LPA in response to the LPA receiving the at least one unique identifier from an Issuer Security Domain Root (ISD-R) entity of the wireless device.

3. The method according to claim 2, wherein: The ISD-R generates a digital signature based on the at least one unique identifier before providing the at least one unique identifier to the LPA, and The LPA authenticates the digital signature before providing the at least one unique identifier to the SM-DP+ server. 4 . The method of claim 1 , wherein the status of the wireless device comprises at least one status code indicating that the wireless device has been flagged for a particular activity.

5. The method of claim 4, wherein the at least one status code corresponds to an International Mobile Equipment Identity (IMEI) of the wireless device or an identifier (EID) of an embedded Universal Integrated Circuit Card (eUICC) of the wireless device.

6. The method of claim 1, wherein providing the status of the wireless device causes the wireless device to update its configuration such that the wireless device is prohibited from performing at least one form of cellular network activity.

7. The method of claim 1, wherein prior to providing the client authentication request, the LPA identifies a triggering operation that causes the wireless device to require an indication of whether the wireless device has been flagged for a particular activity.

8. The method according to claim 7, wherein the triggering operation comprises: Powering on of the wireless device, a first request to download an electronic subscriber identity module (eSIM) profile to the wireless device, a second request to perform at least one management operation on at least one eSIM profile managed by the wireless device, and / or A third request to connect to a mobile network operator (MNO) using at least one eSIM profile managed by the wireless device.

9. The method according to claim 1, wherein the specific activity comprises any combination of: the at least one unique identifier is shared by separate and distinct wireless devices that have attempted to interact with the MNO, or The wireless device is reported as lost or stolen.

10. A method for interacting with a wireless device that has been tagged for a particular activity, the method comprising, at a local profile assistant (LPA) of the wireless device: obtaining at least one unique identifier associated with the wireless device; providing the at least one unique identifier to an equipment identification registry, wherein the equipment identification registry manages unique identifiers of devices that have been tagged for a particular activity; as well as In response to receiving a status of the wireless device from the equipment identification registry, wherein the status indicates that the wireless device has been tagged for a particular activity: The configuration of the wireless device is updated such that the wireless device is prohibited from performing at least one form of cellular network activity.

11. The method of claim 10, further comprising, after updating the configuration: Detecting a triggering operation, the triggering operation comprising an activity selected from one or more of the following: a first request to download an electronic subscriber identity module (eSIM) profile to the wireless device, a second request to perform at least one management operation on at least one eSIM profile managed by the wireless device, and / or A third request to connect to a mobile network operator (MNO) using at least one eSIM profile managed by the wireless device.

12. The method according to claim 11, further comprising, in response to the triggering operation: The activities described are prohibited.

13. The method of claim 11, further comprising, prior to obtaining the at least one unique identifier, identifying device activity at the wireless device, wherein the device activity comprises: Powering on the wireless device; Exit airplane mode on the wireless device.

14. The method according to claim 11, further comprising: A user interface is displayed that communicates that the wireless device has been tagged for a particular activity.

15. The method of claim 11, further comprising, after updating the configuration: receiving an indication that the wireless device is no longer tagged, and The update to the configuration is restored.

16. A method for interacting with a wireless device that has been tagged for a particular activity, the method comprising, at an embedded universal integrated circuit card (eUICC) of the wireless device: receiving a network attachment failure notification from a baseband component of the wireless device; providing a request to an Issuer Security Domain Root (ISD-R) component of the wireless device to suspend profile-related activities on the wireless device; The configuration of the wireless device is updated so that the wireless device is prohibited from performing the profile-related activities.

17. The method of claim 16, further comprising, at a local profile assistant (LPA) included in the wireless device, detecting a trigger operation at the wireless device, wherein the trigger operation comprises: a first request to download an electronic subscriber identity module (eSIM) profile to the wireless device, a second request to perform at least one management operation on at least one eSIM profile managed by the wireless device, and / or A third request to connect to a mobile network operator (MNO) using at least one eSIM profile managed by the wireless device.

18. The method of claim 17, further comprising, at the LPA, and in response to detecting the triggering operation: issuing a fourth request to the ISD-R for information associated with the eUICC and / or a challenge-based response from the eUICC; and Receiving from the eUICC an indication that the updated configuration prohibits the wireless device from performing profile-related activities.

19. The method according to claim 18, further comprising: A user interface is displayed that communicates that the wireless device has been tagged for a particular activity.

20. The method of claim 16, further comprising, before receiving the network attachment failure notification: A second request is provided to the baseband component to receive a notification from the baseband component whenever the baseband component experiences a network attachment failure.

Images