Systems, methods and computer programs for preventing unintentional removal of an ESIM from a mobile device

Abstract

Systems, methods, and computer programs are provided for preventing unintentional removal of an eSIM from a mobile device. In use, a removal of an eSIM from a mobile device is detected. Additionally, definitions of predefined scenarios indicative of unintentional removal of an eSIM are accessed. Further, the detected removal is analyzed using these definitions to determine that the detected removal is unintentional. Also, a proactive maintenance action is performed to address the unintentional removal of the eSIM from the mobile device.

Description

Technical Field

[0001] The present invention relates to SIM technology, and more particularly to eSIM technology. Background Art

[0002] Traditionally, a Subscriber Identity Module (SIM) card has been integrated with a mobile device for identifying and authenticating a subscriber of the mobile device (e.g., to a provider network). Specifically, a SIM card securely stores information that identifies and authenticates a subscriber. In the past, a SIM card was a physical device with an integrated circuit and could be physically connected and disconnected from a mobile device. Thus, losing or misplacing a SIM card was not possible because it would require physically removing the SIM card from the mobile device and subsequently losing / misplacing the SIM card.

[0003] Recently, electronic SIM (eSIM) technology has been introduced to replace traditional SIM cards. The eSIM is used for similar purposes as a traditional SIM card, but is digitally integrated with a mobile device, e.g., as a computer code or software application installed on the mobile device. The eSIM does not need to be removed from the mobile device because it can support multiple different subscriber accounts (e.g., for different provider networks) and any of the different subscriber accounts can be activated at any given time.

[0004] However, due to the digital nature of eSIM technology, there is a risk that the eSIM may be unintentionally (e.g., accidentally) removed from a mobile device. For example, an eSIM may be unintentionally removed from a mobile device by deleting a software application representing the eSIM from the mobile device. Because the connection identity of a mobile device user is valuable for enabling network connectivity for the mobile device, protection is needed to prevent the eSIM from being unintentionally removed from the mobile device.

[0005] Therefore, there is a need to address these and / or other problems associated with the prior art. Summary of the invention

[0006] As described herein, systems, methods, and computer programs are provided for preventing unintentional removal of an eSIM from a mobile device. In use, a removal of an eSIM from a mobile device is detected. Additionally, definitions of predefined scenarios indicative of unintentional removal of an eSIM are accessed. Further, the detected removal is analyzed using these definitions to determine that the detected removal is unintentional. Also, a proactive maintenance action is performed to address the unintentional removal of the eSIM from the mobile device. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 A method for preventing unintentional removal of an eSIM from a mobile device according to an embodiment is shown.

[0008] Figure 2 A flow chart of a system for preventing unintentional removal of an eSIM from a mobile device according to an embodiment is shown.

[0009] Figure 3 A flow diagram of a system for preventing unintentional deletion of an eSIM from a mobile device by downloading a copy of the unintentionally deleted eSIM to the mobile device is shown in accordance with an embodiment.

[0010] Figure 4 A system flow diagram is shown for preventing unintentional removal of an eSIM from a mobile device by providing an alert on the mobile device and an option for a user of the mobile device to download a copy of the unintentionally removed eSIM to the mobile device in accordance with an embodiment.

[0011] Figure 5 A flow diagram of a system for preventing unintentional deletion of an eSIM from a mobile device by providing an alert on the mobile device and preventing the eSIM from being removed from the mobile device is shown in accordance with an embodiment.

[0012] Figure 6 A flow diagram of a system for preventing inadvertent removal of an eSIM from a mobile device by providing an alert via a channel separate from the mobile device is shown in accordance with an embodiment.

[0013] Figure 7 A network architecture according to one possible embodiment is shown.

[0014] Figure 8 An exemplary system according to one embodiment is shown. DETAILED DESCRIPTION

[0015] Figure 1 A method 100 for preventing unintentional removal of an eSIM from a mobile device according to one embodiment is shown. The method 100 may be implemented in any computer system such as Figure 7 The method 100 is implemented in the context of an exemplary system 700 of FIG. 100 . In one embodiment, the method 100 may be performed by a mobile device. The mobile device may be a mobile phone, a tablet computer, a laptop computer, or any other mobile user device. In another embodiment, the method 100 may be performed by a platform that runs independently of the mobile device, such as a platform running on a cloud server that communicates with the mobile device via one or more communication networks.

[0016] As shown, in operation 102, the removal of an eSIM from a mobile device is detected. In the context of the present specification, an eSIM is an electronic (digital) SIM that stores information that can be used to identify and authenticate a subscriber of a mobile device to a provider network. For example, an eSIM can securely store identity and authentication information for a subscriber to a provider network, such as an identifier of a subscription account of a subscriber to the provider network. It should be noted that an eSIM can similarly store the aforementioned information of one or more different subscribers of a mobile device to one or more different provider networks.

[0017] When a mobile device attempts to connect or otherwise communicate via a provider network, the provider network may access the eSIM to identify and authenticate the mobile device's subscription to the provider network as a prerequisite to authorizing the connection / communication. As described above, if the eSIM stores identification and authentication information for multiple different subscribers, the provider network may check the identification and authentication information for each subscriber to ensure that at least one of the subscribers is authorized to access the provider network.

[0018] In one embodiment, the eSIM may be installed on the mobile device as computer code, such as a software application installed on the mobile device. Thus, the eSIM may be susceptible to unintentional deletion by a user of the mobile device. In the context of this specification, unintentional means accidental, unintentional, or otherwise undesirable.

[0019] Optionally, the deletion of the eSIM from the mobile device may be detected before or after the eSIM is actually removed from the mobile device, depending on the configuration of the method 100. For example, in one embodiment, the deletion of the eSIM from the mobile device may be detected based on a command to delete the eSIM from the mobile device. The command may be a user request to delete the eSIM from the mobile device, such as a user selecting an icon representing the eSIM in combination with the user selecting a delete key on the mobile device. In another embodiment, the deletion of the eSIM from the mobile device may be detected from an event indicating the removal of the eSIM from the mobile device. The removal may refer to removing the eSIM from the memory of the mobile device. Optionally, the removal may be caused by the above-mentioned command to delete the eSIM from the mobile device.

[0020] In embodiments where method 100 is performed by a mobile device, the deletion may be detected directly by the mobile device. In embodiments where method 100 is performed by a third party platform, the deletion may be detected from information provided by the mobile device to the platform indicating the deletion.

[0021] Further, as an option, detecting the removal of the eSIM from the mobile device may include identifying information describing the removal of the eSIM from the mobile device. The information describing the removal may include the time of the removal, the user causing the removal, the event occurring on the mobile device causing the removal, the location of the mobile device at the time of the removal, and / or the fees paid for the eSIM. It should be noted that the information may be retrieved from different channels storing the information, such as an original equipment manufacturer (OEM) mobile application, any device, device local profile assistance (LPA), a store, an operator information technology (IT) such as a business support system (BSS) and / or an operation support system (OSS), a subscription manager data preparation (SM-DP), and / or an eSIM database.

[0022] As yet another option, detecting removal of an eSIM from a mobile device may include identifying registration information for the eSIM. Of course, it should be noted that in other embodiments, the registration information may be identified independently of detecting removal of an eSIM from a mobile device, such as at a point in time prior to detecting removal of the eSIM from the mobile device. The registration information may be retrieved, obtained, or otherwise identified from an OEM mobile application, any device, a device LPA, a store, an operator IT (such as a BSS and / or OSS), an SM-DP, and / or an eSIM database. According to various examples, the registration information may include the time at which the eSIM was activated on the mobile device, the subscription plan for each account associated with the eSIM, and / or the location of the mobile device during activation of the eSIM on the mobile device.

[0023] Next, as shown in operation 104, definitions of predefined scenarios indicating unintentional removal of an eSIM are accessed. The predefined scenarios may be defined manually (e.g., by a developer of method 100) or may be defined automatically, such as by using artificial intelligence applied to historical data related to unintentional removal of an eSIM of a mobile device. In any case, the definition of each predefined scenario may include any information, criteria, parameters, etc. indicating unintentional removal of an eSIM.

[0024] In one embodiment, the one or more predefined scenarios may be time-dependent. For example, the definition of the one or more predefined scenarios may indicate that when the removal of the eSIM occurs within a specified time after the eSIM is activated, the removal is unintentional. In another embodiment, the one or more predefined scenarios may be location-dependent. For example, the definition of the one or more predefined scenarios may indicate that when the removal of the eSIM occurs within a specified time after the mobile device is taken out of a particular store (e.g., the store where the mobile device was purchased), the removal is unintentional.

[0025] In yet another embodiment, the one or more predefined scenarios may be user-dependent. For example, the definition of the one or more predefined scenarios may indicate that the removal is unintentional when the user of the mobile device at the time of eSIM removal is identified as a child (i.e., within a specified age range). In yet another embodiment, the one or more predefined scenarios may be pattern-dependent. For example, the definition of the one or more predefined scenarios may indicate that the removal of the eSIM is unintentional when the usage pattern of the device is predetermined to be associated with unintentional removal of the eSIM.

[0026] In another embodiment, one or more predefined scenarios may be experience-related. For example, the definition of one or more predefined scenarios may indicate that the deletion of the eSIM is unintentional when it occurs after an experience (i.e., a series of actions) of a user of a mobile device that is predetermined to be associated with the unintentional deletion of the eSIM. The experience may be a complex process, such as signing up for a credit card. In another embodiment, one or more predefined scenarios may be financially related. For example, the definition of one or more predefined scenarios may indicate that the deletion of the eSIM is unintentional when the eSIM is installed on the mobile device without charge. For example, it may be predetermined that when a user obtains the eSIM without charge (free of charge), the user may have no reason to delete the eSIM.

[0027] It should be noted that these embodiments are not mutually exclusive, but can be used in combination to define scenarios having a plurality of different parameters indicating unintentional removal of an eSIM, etc. As described above, in operation 104, definitions of predefined scenarios are accessed. In one embodiment, these definitions may be stored locally and thus accessed locally (e.g., in a local memory). In another embodiment, these definitions may be stored remotely and thus accessed remotely (e.g., over a network). In addition, the definitions may be accessed in response to operation 102 (i.e., detecting removal of an eSIM from a mobile device).

[0028] Further, the detected deletion is analyzed using these definitions to determine that the detected deletion is unintentional, as shown in operation 106. For example, the analysis may include determining that the detected deletion satisfies, matches, etc. at least one of the definitions indicative of unintentional deletion of an eSIM, thereby determining that the detected deletion is unintentional.

[0029] In one embodiment, the analysis may also consider information describing the removal of the eSIM from the mobile device. For example, analyzing the detected removal using the definition to determine that the detected removal was unintentional may include determining that the information describing the removal of the eSIM from the mobile device is related to one or more of the definitions. In another embodiment, the analysis may similarly consider registration information of the eSIM.

[0030] Still, as shown in operation 108, a proactive maintenance action is caused to be performed to address the unintentional removal of the eSIM from the mobile device. In embodiments where the method 100 is performed by a mobile device, the proactive maintenance action may be performed by the mobile device alone or in combination with other devices / systems. In embodiments where the method 100 is performed by a platform, the platform may cause the proactive maintenance action to be performed by the mobile device alone or in combination with other devices / systems.

[0031] As described above, deletion of an eSIM from a mobile device may be detected before or after the eSIM is actually removed from the mobile device, depending on the configuration of method 100. Thus, the proactive maintenance actions performed may depend on whether method 100 is configured to detect a command to delete an eSIM from a mobile device or is configured to detect an event indicating removal of an eSIM from a mobile device.

[0032] For example, when detecting that the eSIM is deleted from the mobile device includes detecting a command to delete the eSIM from the mobile device, then the proactive maintenance action may include at least temporarily preventing the eSIM from being deleted from the mobile device. In this example, the proactive maintenance action may include providing a notification on the mobile device regarding the commanded deletion, and optionally requiring the user to confirm the deletion through additional input (e.g., an additional button click) before the eSIM is removed from the device. Alternatively, in this example, the proactive maintenance action may include providing a notification regarding the commanded deletion through a channel separate from the mobile device (e.g., to another mobile device), and optionally requiring the user to confirm the deletion through additional input (e.g., an additional button click) before the eSIM is removed from the device. As yet another option, the proactive maintenance action may include returning an error and preventing the eSIM from being removed from the mobile device regardless of further user input.

[0033] As another example, when detecting that the eSIM is deleted from the mobile device includes detecting an event indicating removal of the eSIM from the mobile device, then the proactive maintenance action may include downloading a copy of the eSIM to the mobile device. The download may occur automatically without user intervention. Alternatively, the download may occur in response to notifying a user of the mobile device of the deletion (e.g., via the mobile device or via a channel separate from the mobile device) and receiving input from the user to download a copy of the eSIM.

[0034] To this end, the method 100 can implement proactive maintenance actions to provide protection against unintentional removal of an eSIM from a mobile device. The method 100 can help ensure that the eSIM continues to be available to the mobile device for its intended purpose (i.e., network connection). The method 100 can further prevent the mobile device user from having to initiate maintenance actions themselves (e.g., calling the provider network's customer service).

[0035] More illustrative information about various optional architectures and uses will now be set forth, wherein the foregoing methods may or may not be implemented depending on the user's desires. It should be strongly noted that the following information is set forth for illustrative purposes and should not be construed as limiting in any way. Any of the following features may be optionally combined with or without excluding the other features described.

[0036] Figure 2 A system flow diagram for preventing unintentional deletion of an eSIM from a mobile device according to an embodiment is shown. As an option, the system flow diagram can be implemented in the context of the details of the previous figure and / or any subsequent figure. However, of course, the flow diagram can be implemented in the context of any desired environment.

[0037] As shown, a user registers (e.g., activates) an eSIM for a mobile device 202 through one of a number of possible communication channels. Registering an eSIM may include requesting an eSIM from a network provider, completing an authorization process for the user (e.g., creating a user account at the network provider, verifying an existing account at the network provider, etc.), and receiving the eSIM from the network provider at the mobile device 202 for accessing the network of the network provider. The registration process may be performed at the network provider or at a third-party platform 204 that can be used to prevent unintentional removal of the eSIM from the mobile device 202. The third-party platform 204 may include a combination of hardware (e.g., a server) and software (e.g., an application) that communicates with the mobile device 202 and other communication channels described below.

[0038] It should be noted that possible communication channels can each register an eSIM for mobile device 202 and can be managed by a network provider or by platform 204. In various examples, possible communication channels can include a website, an application installed on a mobile device, a retail (physical) store, etc.

[0039] Once registered, registration information is sent from the mobile device 202 (or optionally the communication channel used to register the eSIM) to the platform 204. The registration information may include an identifier of the mobile device 202, an identifier of the eSIM registered for the mobile device 202, and the like. The platform 204 also retrieves additional registration information from other channels, such as an OEM mobile application (not shown), any device (not shown), a device LPA (not shown), a store (not shown), an operator IT (with BSS / OSS) 206, an SM-DP (with an eSIM database) 208, and the like. According to various examples, the registration information may include the time the eSIM was registered on the mobile device 202, the subscription plan of each account associated with the eSIM, and / or the location of the mobile device 202 during the registration of the eSIM for the mobile device.

[0040] At some point in time after the eSIM is registered for the mobile device 202, a removal of the eSIM from the mobile device 202 is detected. In one embodiment, the removal may be detected by software running on the mobile device 202. The removal may simply include a request or command to remove the eSIM from the mobile device 202, or may be the actual removal of the eSIM from the mobile device 202. Alternatively, the software may be an application installed on the mobile device 202 (e.g., by the platform 204), optionally as part of registering the eSIM for the mobile device 202.

[0041] As shown, in response to detecting the removal of the eSIM from the mobile device 202, removal information is sent from the mobile device 202 to the platform 204. The software used to detect the removal can similarly be used to send the removal information to the platform 204. Thus, the software can be configured to interface with the platform 204. The removal information can include any information describing the removal, such as the time of the removal, the user logged in or otherwise determined to be using the mobile device 202 at the time of the removal, the location of the mobile device 202 at the time of the removal, the use of the mobile device 202 that led to the removal (i.e., the user's actions), and the experience of the user of the mobile device 202 before the removal (i.e., a series of actions).

[0042] Further, additional removal information is also identified by the platform 204 from other channels (e.g., operator IT (with BSS / OSS) 206, SM-DP (with eSIM database) 208, etc.). The additional removal information may include the price paid for the eSIM, the identity of the user who registered the eSIM for the mobile device 202, or any other category of information predefined by the platform 204 for subsequent analysis to determine whether the removal was unintentional.

[0043] Therefore, once the platform 204 obtains the deletion information and the additional deletion information, the platform 204 analyzes them to determine whether the deletion is unintentional. The analysis may be performed using the definition of predefined scenarios indicating unintentional deletion of an eSIM, and optionally also using the registration information and the additional registration information. For example, if the deletion information and the additional deletion information meet any of the defined criteria, it may be determined that the deletion is unintentional.

[0044] In the embodiment shown, the deletion is determined by the platform 204 to be unintentional. In response, the platform 204 causes proactive maintenance actions to be performed on the mobile device 202. The proactive maintenance actions may include any actions that prevent unintentional deletion of the eSIM on the mobile device 202, as described below in the remaining Figure 3-5The proactive maintenance actions may be performed solely by the mobile device 202 (e.g., software running on the mobile device), or may be performed by the mobile device 202 with assistance from other channels (e.g., operator IT (with BSS / OSS) 206, SM-DP (with eSIM database) 208, etc.), again as described in the remaining sections below. Figure 3-5 Described in more detail in .

[0045] Figure 3 A system flow diagram for preventing unintentional deletion of an eSIM from a mobile device by downloading a copy of the unintentionally deleted eSIM to the mobile device according to an embodiment is shown. As an option, the system flow diagram can be implemented in the context of the details of the previous figure and / or any subsequent figure. However, of course, the flow diagram can be implemented in the context of any desired environment.

[0046] Figure 3 The system flow chart follows the same as above. Figure 2 The same sequence of events is described, with a more specific use case of a proactive maintenance action performed by the mobile device 202. As shown, the platform 204 causes the mobile device 202 to download a copy of the inadvertently deleted eSIM.

[0047] Specifically, in response to a determination that the deletion (i.e., actual removal in this case) of the eSIM from the mobile device 202 was unintentional, the platform 204 instructs the SM-DP (with an eSIM database) 208 to prepare a copy of the eSIM for the mobile device 202. The platform 204 then requests the mobile device 202 to download a copy of the eSIM from the SM-DP (with an eSIM database) 208. In response to the request, the mobile device 202 downloads a copy of the eSIM from the SM-DP (with an eSIM database) 208. The download may be performed automatically (e.g., by software) without user intervention.

[0048] Figure 4 A system flow diagram for preventing unintentional deletion of an eSIM from a mobile device by providing an alert on the mobile device and an option for a user of the mobile device to download a copy of the unintentionally deleted eSIM to the mobile device according to an embodiment is shown. As an option, the system flow diagram may be implemented in the context of the details of the previous figure and / or any subsequent figure. However, of course, the flow diagram may be implemented in the context of any desired environment.

[0049] Figure 4 The system flow chart follows the same as above. Figure 2The same sequence of events described, with a more specific use case of a proactive maintenance action performed by mobile device 202. As shown, platform 204 causes mobile device 202 to issue an alert and provides the user of mobile device 202 with the option to download a copy of the unintentionally deleted eSIM to mobile device 202.

[0050] Specifically, in response to a determination that the deletion (i.e., actual removal in this case) of the eSIM from the mobile device 202 was unintentional, the platform 204 instructs the mobile device 202 to display an alert (i.e., indicating the removal of the eSIM) and an option for a user of the mobile device 202 to download a copy of the unintentionally deleted eSIM to the mobile device 202. The option can be a selectable button displayed on the mobile device 202. Thus, the user can verify that the deletion was unintentional by not selecting the option and closing the alert, or can verify that the deletion was unintentional by selecting the option.

[0051] In response to the user selecting this option, the platform 204 instructs the SM-DP (with eSIM database) 208 to prepare a copy of the eSIM for the mobile device 202. The platform 204 then requests the mobile device 202 to download a copy of the eSIM from the SM-DP (with eSIM database) 208. In response to the request, the mobile device 202 downloads a copy of the eSIM from the SM-DP (with eSIM database) 208. Thus, the download may be performed only in response to user intervention.

[0052] Figure 5 A system flow diagram for preventing unintentional deletion of an eSIM from a mobile device by providing an alert on the mobile device and preventing the eSIM from being removed from the mobile device according to an embodiment is shown. As an option, the system flow diagram can be implemented in the context of the details of the previous figure and / or any subsequent figure. However, of course, the flow diagram can be implemented in the context of any desired environment.

[0053] Figure 5 The system flow chart follows the same as above. Figure 2 The same sequence of events is described, with a more specific use case of a proactive maintenance action performed by the mobile device 202. As shown, the platform 204 causes the mobile device 202 to sound an alarm and prevent the eSIM from being removed from the mobile device.

[0054] Specifically, in response to a determination that the deletion of the eSIM from the mobile device 202 (i.e., in this case a requested removal, not an actual removal) was unintentional, the platform 204 instructs the mobile device 202 to display an alert (e.g., indicating a requested eSIM removal, an error indicating a requested removal, etc.). The platform 204 also instructs the mobile device 202 to lock the wipe function for the eSIM so that the eSIM cannot be removed from the mobile device 202.

[0055] Figure 6 A system flow diagram for preventing unintentional removal of an eSIM from a mobile device by providing an alert via a channel separate from the mobile device according to an embodiment is shown. As an option, the system flow diagram can be implemented in the context of the details of the previous figure and / or any subsequent figure. However, of course, the flow diagram can be implemented in the context of any desired environment.

[0056] Figure 6 The system flow chart follows the same as above. Figure 2 The same sequence of events is described, with a more specific use case of a proactive maintenance action performed by a mobile device 202. As shown, the platform 204 causes the mobile device 202 to issue an alert, which is provided through a channel separate from the mobile device 202.

[0057] Specifically, in response to a determination that the deletion of the eSIM from the mobile device 202 (i.e., in this case a requested removal, not an actual removal) was unintentional, the platform 204 instructs a channel separate from the mobile device 202 to issue an alert (e.g., indicating a requested eSIM removal, an error indicating a requested removal, etc.). For example, the platform 204 may instruct another mobile device of the user to display an alert, may instruct a short message service (SMS) message to be provided to the user, may instruct a call to a network provider call center, etc. Optionally, the platform 204 may also instruct the mobile device 202 to lock the erase function for the eSIM so that the eSIM cannot be removed from the mobile device 202.

[0058] Figure 7 A network architecture 700 according to one possible embodiment is shown. As shown, at least one network 702 is provided. In the context of the present network architecture 700, the network 702 may take any form, including but not limited to a telecommunications network, a local area network (LAN), a wireless network, a wide area network (WAN) (such as the Internet), a peer-to-peer network, a cable network, etc. Although only one network is shown, it should be understood that two or more similar or different networks 702 may be provided.

[0059] Coupled to the network 702 are a number of devices. For example, a server computer 704 and an end-user computer 706 may be coupled to the network 702 for communication purposes. Such end-user computers 706 may include desktop computers, laptop computers, and / or any other type of logic. In addition, various other devices may be coupled to the network 702, including a personal digital assistant (PDA) device 708, a mobile phone device 710, a television 712, and the like.

[0060] Figure 8 An exemplary system 800 according to one embodiment is shown. As an option, the system 800 may be implemented in Figure 7 The system 800 may be implemented in the context of any device of the network architecture 700. Of course, the system 800 may be implemented in any desired environment.

[0061] As shown, a system 800 is provided, which includes at least one central processor 801 connected to a communication bus 802. The system 800 also includes a main memory 804 [eg, random access memory (RAM) etc.]. The system 800 also includes a graphics processor 806 and a display 808.

[0062] The system 800 may also include an auxiliary storage device 810. The auxiliary storage device 810 includes, for example, a hard disk drive and / or a removable storage drive, which represents a floppy disk drive, a tape drive, a compact disk drive, etc. The removable storage drive reads from and / or writes to a removable storage unit in a well-known manner.

[0063] In this regard, a computer program or computer control logic algorithm may be stored in the main memory 804, the secondary storage device 810, and / or any other memory. Such a computer program, when executed, enables the system 800 to perform various functions (e.g., as described above). The memory 804, the storage device 810, and / or any other storage device are possible examples of non-transitory computer readable media.

[0064] The system 800 may also include one or more communication modules 812. The communication module 812 may be used to facilitate communication between the system 800 and one or more networks, and / or to communicate with one or more devices via various possible standard or proprietary communication protocols (e.g., via Bluetooth, near field communication (NFC), cellular communication, etc.).

[0065] As used herein, "computer-readable medium" includes one or more of any suitable media for storing executable instructions of a computer program, such that an instruction execution machine, system, apparatus, or device can read (or retrieve) the instructions from the computer-readable medium and execute the instructions for performing the described method. Suitable storage formats include one or more of electronic, magnetic, optical, and electromagnetic formats. A non-exhaustive list of conventional exemplary computer-readable media includes: portable computer disks; RAM; ROM; erasable programmable read-only memory (EPROM or flash memory); optical storage devices, including portable compact disks (CDs), portable digital video disks (DVDs), high-definition DVDs; BLU-RAY disk; etc.

[0066] It should be understood that the arrangement of components shown in the described figures is exemplary and other arrangements are possible. It should also be understood that the various system components (and devices) defined by the claims described below and illustrated in the various block diagrams represent logical components in some systems configured according to the subject matter disclosed herein.

[0067] For example, one or more of these system components (and devices) may be implemented in whole or in part by at least some of these components shown in the arrangements shown in the figures. In addition, while at least one of these components is at least partially implemented as an electronic hardware component and thus constitutes a machine, other components may be implemented in software, which, when included in an execution environment, constitutes a machine, hardware, or a combination of software and hardware.

[0068] More specifically, at least one component defined by the claims is implemented at least in part as an electronic hardware component, such as an instruction execution machine (e.g., a processor-based or processor-containing machine) and / or a dedicated circuit or circuit system (e.g., discrete logic gates interconnected to perform a dedicated function). Other components may be implemented in software, hardware, or a combination of software and hardware. Furthermore, some or all of these other components may be combined, some components may be omitted entirely, and additional components may be added while still achieving the functionality described herein. Thus, the subject matter described herein may be embodied in many different variations, and all of these variations are contemplated to be within the claimed scope.

[0069] In the above description, unless otherwise specified, the subject matter is described with reference to the actions and symbolic representations of the operations performed by one or more devices. Therefore, it will be understood that such actions and operations sometimes referred to as computer execution include the manipulation of data in a structured form by the processor. This manipulation converts data or keeps it in a position in the memory system of the computer, which reconfigures or otherwise changes the operation of the device in a manner well known to those skilled in the art. The data is maintained at the physical location of the memory as a data structure with specific attributes defined by the format of the data. However, although the subject matter is described in the aforementioned context, it is not meant to be restrictive, because those skilled in the art will understand that several actions and operations described below can also be implemented in hardware.

[0070] In order to facilitate understanding of the subject matter described herein, many aspects are described in terms of action sequences. At least one of these aspects defined by the claims is performed by an electronic hardware component. For example, it will be appreciated that various actions can be performed by a dedicated circuit or circuit system, by program instructions executed by one or more processors, or by a combination of the two. The description of any action sequence herein is not intended to imply that the specific order described for performing the sequence must be followed. Unless otherwise indicated herein or the context otherwise clearly conflicts, all methods described herein can be performed in any suitable order.

[0071] In the context of describing the subject matter (especially in the context of the following claims), the use of the terms "a" and "an" and "the" and similar indicators should be interpreted as covering both the singular and the plural, unless otherwise indicated herein or clearly contradicted by the context. Unless otherwise indicated herein, the enumeration of numerical ranges herein is intended only to be used as a shorthand method of individually referring to each individual value falling within the range, and each individual value is incorporated into the specification as if it were individually enumerated herein. In addition, the foregoing description is for illustrative purposes only, not for limiting purposes, because the scope of protection sought is defined by the claims set forth below and any equivalents to which they are entitled. The use of any and all examples or exemplary language (e.g., "such as") provided herein is intended only to better illustrate the subject matter and does not limit the scope of the subject matter, unless otherwise required. The use of the term "based on" and other similar phrases representing conditions for producing a result in the claims and written description is not intended to exclude any other conditions for producing the result. The language in the specification should not be interpreted as indicating that any unclaimed element is essential to the practice of the claimed invention.

[0072] The embodiments described herein include one or more modes known to the inventor for implementing the claimed subject matter. Of course, after reading the above description, the changes of those embodiments will become apparent to those of ordinary skill in the art. The inventor expects those skilled in the art to adopt such changes as appropriate, and the inventor intends to implement the claimed subject matter in a manner other than the specific description herein. Therefore, as permitted by applicable law, the claimed subject matter includes all modifications and equivalents of the subject matter recited in the appended claims. In addition, unless otherwise indicated herein or the context is clearly contradictory, any combination of the above-mentioned elements in all possible variations is included.

[0073] Although various embodiments have been described above, it should be understood that they have been presented by way of example only and not limitation.Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

1. A non-transitory computer readable medium storing computer code executable by a processor to perform a method for preventing unintentional removal of an eSIM from a mobile device, the method comprising: Detect removal of an eSIM from a mobile device; accessing a definition of a predefined scenario indicative of unintentional removal of an eSIM, wherein the predefined scenario is automatically defined using artificial intelligence applied to historical data related to unintentional removal of an eSIM of a mobile device; analyzing the detected deletion using the definition to determine that the detected deletion was unintentional; and A proactive maintenance action is caused to be performed to address the unintentional removal of the eSIM from the mobile device. 2 . The non-transitory computer-readable medium of claim 1 , wherein the method is performed by the mobile device. 3 . The non-transitory computer-readable medium of claim 1 , wherein the method is performed by a platform that operates separately from the mobile device. 4 . The non-transitory computer-readable medium of claim 1 , wherein the eSIM is installed on the mobile device as computer code. 5 . The non-transitory computer-readable medium of claim 1 , wherein the eSIM securely stores identity and authentication information of at least one subscriber to a provider network.

6. The non-transitory computer-readable medium of claim 1 , wherein detecting removal of the eSIM from the mobile device comprises: A command to delete the eSIM from the mobile device is detected, or an event indicating that the eSIM is removed from the mobile device is detected.

7. The non-transitory computer-readable medium of claim 1 , wherein detecting removal of the eSIM from the mobile device comprises: Information describing removal of the eSIM from the mobile device is identified.

8. The non-transitory computer-readable medium of claim 7, wherein the information describing the deletion of the eSIM from the mobile device comprises at least one of: a time of the deletion, a user causing the deletion, an event occurring on the mobile device causing the deletion, a location of the mobile device at the time of the deletion, or a fee paid for the eSIM.

9. The non-transitory computer readable medium of claim 7, wherein analyzing the detected deletion using the definition to determine that the detected deletion was unintentional comprises: A determination is made that the information describing the removal of the eSIM from the mobile device is associated with one or more of the definitions.

10. The non-transitory computer readable medium of claim 1, wherein the definition is stored locally.

11. The non-transitory computer-readable medium of claim 1 , wherein detecting that the eSIM is removed from the mobile device comprises: Identify registration information of the eSIM.

12. The non-transitory computer-readable medium of claim 11, wherein the registration information comprises at least one of: a time when the eSIM was activated on the mobile device, a subscription plan for each account associated with the eSIM, or a location of the mobile device during activation of the eSIM on the mobile device. The non-transitory computer readable medium of claim 12 , wherein the analyzing is further directed to the registration information.

14. The non-transitory computer-readable medium of claim 1, wherein when detecting the removal of the eSIM from the mobile device comprises detecting a command to delete the eSIM from the mobile device, then the proactive maintenance action comprises at least temporarily preventing the removal of the eSIM from the mobile device.

15. The non-transitory computer-readable medium of claim 1, wherein when detecting deletion of the eSIM from the mobile device comprises detecting an event indicative of removal of the eSIM from the mobile device, then the proactive maintenance action comprises automatically downloading a copy of the eSIM to the mobile device without user intervention.

16. A method for preventing unintentional removal of an eSIM from a mobile device, comprising: Detection by the system of removal of the eSIM from the mobile device; accessing, by the system, a definition of a predefined scenario indicative of unintentional removal of an eSIM, wherein the predefined scenario is automatically defined using artificial intelligence applied to historical data related to unintentional removal of an eSIM of a mobile device; analyzing, by the system, the detected deletion using the definition to determine that the detected deletion was unintentional; and A proactive maintenance action is caused by the system to be performed to address the unintentional removal of the eSIM from the mobile device.

17. A system for preventing unintentional removal of an eSIM from a mobile device, comprising: a non-transitory memory storing instructions; as well as one or more processors in communication with the non-transitory memory, the one or more processors executing the instructions to perform a method for preventing unintentional removal of an eSIM from a mobile device, the method comprising: Detect removal of an eSIM from a mobile device; accessing a definition of a predefined scenario indicative of unintentional removal of an eSIM, wherein the predefined scenario is automatically defined using artificial intelligence applied to historical data related to unintentional removal of an eSIM of a mobile device; analyzing the detected deletion using the definition to determine that the detected deletion was unintentional; and A proactive maintenance action is caused to be performed to address the unintentional removal of the eSIM from the mobile device.

18. The non-transitory computer-readable medium of claim 1, wherein at least one of the definitions of the predefined scenarios indicates that removal of an eSIM on a mobile device is unintentional when the removal occurs within a specified time after the eSIM is activated.

19. The non-transitory computer-readable medium of claim 1, wherein at least one of the definitions of the predefined scenarios indicates that when an eSIM is deleted on a mobile device, the deletion is unintentional when a user of the mobile device is identified as being within a specified age range.

20. The non-transitory computer-readable medium of claim 1, wherein at least one of the definitions of the predefined scenarios indicates that when an eSIM installed on a mobile device is free, deleting an eSIM from the mobile device is unintentional.

Images