System, method and computer program for transferring subscriber identity module (SIM) information for SIM card or ESIM activation

By receiving activation requests, accessing SIM card and eSIM information, and performing corresponding actions, the system solves the information transfer and compatibility issues of mobile devices from traditional SIM cards to eSIMs, achieving automated conversion and seamless network access between devices.

CN114467320BInactive Publication Date: 2024-11-22AMDOCS DEV LTD
View PDF 12 Cites 0 Cited by

Patent Information

Application Number
CN202080063261.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-09-12
Filing Date
2020-09-11
Publication Date
2024-11-22
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

In existing technologies, there are information transfer and compatibility issues in the process of mobile devices transitioning from traditional SIM cards to eSIMs, and there is a lack of automated activation and configuration mechanisms.

Method used

A system and method are provided that receive an activation request, access information about the SIM card and eSIM, and perform actions based on this information to achieve transfer and compatibility verification from the SIM card to the eSIM, including information migration, configuration file download, and device compatibility correction.

Benefits of technology

It enables automated conversion from SIM card to eSIM, ensuring no data loss and improving compatibility between devices and smooth network access.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114467320B_ABST
    Figure CN114467320B_ABST
Patent Text Reader

Abstract

Systems, methods, and computer programs for activating an eSIM from a SIM card or another eSIM are provided. In one implementation, a request to activate an eSIM from a SIM card or another eSIM is received. In addition, in response to the request, first information associated with the SIM card or another eSIM and second information associated with the eSIM are accessed. Further, at least one action for activating the eSIM from the SIM card or another eSIM is performed, wherein the at least one action is based on the first information and the second information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to Subscriber Identity Module (SIM) 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 then 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 can be remotely provided and is rewritable. For example, the eSIM can be digitally integrated with a mobile device, such as as a computer code, software application, or chip installed on the mobile device or installed on a physical card connected to the mobile device. In some embodiments, 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 different subscriber account can be activated at any given time.

[0004] Due to the newly available eSIM technology, a process is needed to allow mobile device users to transfer from the use of a traditional SIM card to the use of an eSIM, and therefore allow the activation of an eSIM from a SIM card. Other embodiments involving the transfer of SIM information may also be desired, such as activating a traditional SIM card from an eSIM, activating an eSIM from another eSIM, or even transferring SIM information between SIM cards.

[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, according to one embodiment, a system, method, and computer program for activating an eSIM are provided. In use, a request to activate an eSIM from a SIM card or another eSIM is received. In addition, in response to the request, first information associated with the SIM card or another eSIM and second information associated with the eSIM are accessed. Further, at least one action for activating the eSIM from the SIM card or another eSIM is performed, wherein the at least one action is based on the first information and the second information.

[0007] According to another embodiment, a system, method and computer program for activating a SIM card are provided. In use, a request to activate a SIM card from an eSIM is received. In addition, in response to the request, first information associated with the eSIM and second information associated with the SIM card are accessed. Further, at least one action for activating the SIM card from the eSIM is performed, wherein the at least one action is based on the first information and the second information. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 A method for activating an eSIM from a SIM card according to one embodiment is shown.

[0009] Figure 2 A system flow diagram for activating an eSIM from a SIM card according to one embodiment is shown.

[0010] Figure 3 A flow chart of a system for moving information from a SIM card to an eSIM according to one embodiment is shown.

[0011] Figure 4 A flow chart of a system for verifying compatibility between a SIM card and an eSIM according to one embodiment is shown.

[0012] Figure 5 A flow chart of a system for verifying compatibility of a target mobile device with an eSIM profile according to one embodiment is shown.

[0013] Figure 6 A flow chart of a system for verifying the compatibility of an eSIM profile with a target device according to one embodiment is shown.

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

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

[0016] Figure 1 A method 100 for activating an eSIM from a SIM card according to one embodiment is shown. The method 100 may be performed on any computer system such as Figure 8 The method 100 is implemented in the context of an exemplary system 800 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.

[0017] As shown, in operation 102, a request to activate an eSIM from a SIM card is received. In the context of this specification, a SIM card is a physical device that can be physically connected and disconnected (removed) from a mobile device. The SIM card securely stores information that can be used to identify and authenticate a subscriber of the mobile device (e.g., to a provider network), and the SIM card may not be rewritable. Therefore, when the SIM card is connected to the mobile device, the SIM card is used (e.g., by the provider network) to identify and authenticate the subscriber of the mobile device to the provider network.

[0018] Also in the context of this specification, an eSIM is an electronic (digital) SIM used similarly to a SIM card, such as for storing information that can be used to identify and authenticate a subscriber of a mobile device to a provider network, but the eSIM can be remotely provided and is rewritable. For example, the 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 the eSIM can also store the aforementioned information of one or more different subscribers of a mobile device to one or more different provider networks. In one embodiment, the eSIM can be a computer code (e.g., a software application) or a chip, such as which can be installed on a mobile device or installed on a physical card connected to the mobile device.

[0019] Once activated, the eSIM will operate such that when the 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.

[0020] As described above, in operation 102, a request to activate an eSIM from a SIM card is received. With respect to this operation, activating an eSIM from a SIM card may include configuring the eSIM for use by the mobile device based on the SIM card. Thus, the request may be to transfer the functionality of the SIM card to the eSIM so that the eSIM may be used as a replacement for the SIM card or as an additional instance of the SIM card. To this end, the eSIM may not necessarily exist or may not be configured for operation before receiving the request in operation 102.

[0021] It should be noted that the request to activate the eSIM from the SIM card may include various information. For example, the request may include the identification of the SIM card and / or the mobile device to which the SIM card is connected. As another example, the request may include the identification of the mobile device for which use of the eSIM is intended once the eSIM is activated.

[0022] In one embodiment, the request may be received as a result of user input to a mobile device (or other computer system). For example, the user input may be provided through a user interface, an application running on the mobile device, a web application accessed through a browser of the mobile device, etc. Optionally, eSIM activation may be requested for the same mobile device through which the request is received. As another option, the mobile device through which the request is received may be different from the mobile device for which eSIM activation is requested. As a further option, the SIM card may be connected to the mobile device through which the request is received and / or for which eSIM activation is requested.

[0023] In another embodiment, the request may be received as part of an automated operation to activate an eSIM from a SIM card. The automated operation may optionally be a batch operation to activate eSIMs from any number of different SIM cards for any number of different mobile devices.

[0024] In addition, in response to the request, first information associated with the SIM card and second information associated with the eSIM are accessed in operation 104. For example, the first information may describe the SIM card. Similarly, the second information may describe the eSIM.

[0025] In one embodiment, the first information associated with the SIM card may include data stored on the SIM card. The data may be personal information of at least one subscriber, such as (one or more) contacts of the subscriber. The data may also be configuration information of the provider network, such as a roaming priority list. In addition, the data may include identification and authentication information for the subscriber. In another embodiment, the first information associated with the SIM card may include the version and / or manufacturer of the SIM card. Further, in one embodiment, the second information associated with the eSIM may include the version and / or developer / provider of the eSIM.

[0026] It should be noted that the first information and the second information may be accessed from one or more channels (e.g., sources). The channels may include a connected mobile device, an original equipment manufacturer (OEM) mobile application and / or store and / or website, an operator (network provider) store and / or mobile application and / or information technology (IT) (such as a business support system (BSS) and / or an operation support system (OSS)), a third-party store, a subscription manager data preparation (SM-DP) optionally with an eSIM database, etc., from which the request is received.

[0027] Further, in operation 106, at least one action for activating the eSIM from the SIM card is caused to be performed, wherein the at least one action is based on the first information and the second information. In the context of this operation, causing at least one action to be performed to activate the eSIM from the SIM card may include initiating any operation flow with the intended purpose of activating the eSIM from the SIM card. Activation of the eSIM may be provided by downloading a configuration file (e.g., configuration, data, application, etc.) to a mobile device of the eSIM so that network access is provided to the mobile device using the eSIM. For example, a network provider may enable network access based on the configuration file.

[0028] It should be noted that the operation flow may be selected in any manner based on the first information and the second information, such as based on a rule specifying a particular operation flow to be performed for activating an eSIM with associated first information from a SIM card with associated second information. In one embodiment, the action(s) may include moving information from the SIM card to the eSIM, such as transferring data stored by the SIM card to the eSIM. In another embodiment, the action(s) may include verifying compatibility between the SIM card and the eSIM.

[0029] In yet another embodiment, the action(s) may include verifying compatibility of the target mobile device with a profile of the eSIM. In a further embodiment, the action(s) may include verifying compatibility of the eSIM profile with the target device. In yet another embodiment, the action(s) may include correcting errors resulting from any of the above verifications to allow activation of the eSIM from the SIM card. In a further embodiment, the action(s) may include providing the eSIM to the target mobile device for use, such as by downloading the eSIM to the target mobile device or installing the eSIM on the mobile device (e.g., as a computer code or software application).

[0030] To this end, method 100 can enable activation of an eSIM from a SIM card for use by a mobile device in connecting to a provider network. The method 100 can be implemented to automatically convert a user's mobile device from using a SIM card to using an eSIM, or can be implemented to newly configure an eSIM-compatible device based on an already configured SIM card without requiring a user or another entity to manually configure the eSIM.

[0031] More illustrative information about various optional architectures and uses will now be set forth, wherein the aforementioned 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.

[0032] Similar to Figure 1 In the method 100 of activating an eSIM from another eSIM, another embodiment is contemplated, wherein the eSIM is activated from another eSIM. The eSIM and the other eSIM may be located on different mobile devices. The embodiment may include: receiving a request to activate an eSIM from another eSIM; in response to the request, accessing first information associated with the other eSIM and second information associated with the eSIM to be activated; and causing at least one action to be performed to activate the eSIM from the other eSIM, wherein the at least one action is based on the first information and the second information. The request, first / second information, and actions may be the same as described above, but in the context of activating an eSIM from another eSIM.

[0033] In yet another embodiment, the Figure 1 Method 100 of activating a SIM card from an eSIM. This embodiment may include: receiving a request to activate a SIM card from an eSIM; in response to the request, accessing first information associated with the eSIM and second information associated with the SIM card to be activated; and causing at least one action to be performed to activate the SIM card from the eSIM, wherein the at least one action is based on the first information and the second information. The request, first / second information, and actions may be the same as described above, but in the context of activating a SIM card from an eSIM.

[0034] Figure 2 A system flow diagram for activating an eSIM from a SIM card according to one 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.

[0035] As shown, a user obtains an eSIM-enabled device 202 through one of a number of possible communication channels. This may include purchasing a new eSIM-enabled device or upgrading an already owned device to be eSIM compatible / supported. The device may be any device capable of connecting to a network for sending and / or receiving communications, such as a mobile phone, tablet, laptop, etc.

[0036] The user then requests activation of the eSIM from the SIM card. The request may be made through the eSIM support device 202 and / or through another communication channel. The various communication channels through which the user may make the request may be a website, an application installed on the device or another device, a retail (physical) store, etc. Optionally, the communication channels may be separately capable of being used to request activation of the eSIM from the SIM card and may be managed by the network provider or by a third party platform 204 separate from the network provider. Of course, in other embodiments, the request may not necessarily be made by the user, but may be made by another user, entity, automated process, etc.

[0037] As shown, the request is received by a third-party platform 204, which can be used to activate the eSIM from the SIM card. The platform 204 may include a combination of hardware (e.g., server) and software (e.g., application) that communicates with the device 202 and additional communication channels described below.

[0038] The platform 204 may be connected to each channel where the user performs actions related to their existing or new device 202. For example, a channel may include a store from which the user has purchased a new eSIM-enabled device, such as a network operator store or a third-party store. The platform 204 may also (or may not) be part of the device upgrade or purchase process. Examples of channels that the platform 204 interacts with are: OEM store, operator store, third-party store (electronics store), operator mobile application, OEM website, OEM mobile application, etc. Examples of information that the platform 204 may obtain include: information related to user purchases of new devices, user upgrades of existing devices to new devices, user returns of devices, etc.

[0039] Once the request is received, the platform 204 collects the information required to activate the eSIM from the SIM. Specifically, the platform 204 accesses at least the first information associated with the SIM card, and the platform 204 accesses the additional second information associated with the eSIM. In this embodiment, the platform 204 is connected to each channel that has information or participates in the request or need to activate the eSIM from the SIM card, which may include obtaining the eSIM from the device 202 (e.g., digitally transferring the SIM card function to the eSIM). The platform 204 obtains all the information required for activation, such as personal information that the user has on the SIM (e.g., contact information), general information (e.g., SIM card version, operating system version, operator application details), etc. The platform 204 also obtains information from the new device 202 including the eSIM information on it. Examples of channels that the platform interacts with to retrieve information are: OEM store, operator store, third-party store, network operator mobile application, OEM website, OEM mobile application, operator IT (with BSS / OSS) 206, SM-DP (with eSIM database) 208, etc. Examples of retrieved information include: contact information, SIM version, eSIM version, network operator applications, etc.

[0040] When the platform 204 receives the information, it runs an algorithm that detects / determines the action(s) to be taken to activate the eSIM from the SIM card. The action(s) may be actions that provide a smooth experience where the user will not lose any information when transferring from the use of the SIM card to the eSIM. The algorithm detects which technical and / or experience process can be taken to perform the best transfer use case. An example is that a user may have personal information (e.g., contacts) on his plastic SIM card that he may wish to transfer to his eSIM-supported device 202 (either on the eSIM itself or directly to the device 202).

[0041] Depending on the use case, the platform 204 causes the relevant technical actions to be performed. It may involve any or all relevant entities, such as the device 202, the eSIM provider 208, the operator IT network 206, etc. For example, in the contacts embodiment, the platform 204 may retrieve the contacts on the SIM card, store them on the platform 204, and then install / download these contacts in the eSIM or the device 202 itself.

[0042] The following is for Figure 3-6 Describes about Figure 2 Details of each use of this system process. It should be noted that Figure 3-6 The embodiments disclosed in the present invention may be implemented individually or in combination with each other.

[0043] Figure 3A system flow diagram for moving information from a SIM card to an eSIM according to one 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.

[0044] 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 the actions that the platform 204 causes to be performed to activate an eSIM from a SIM card.

[0045] SIM cards typically store both personal and non-personal information. Examples of personal information may be phone numbers and details of contacts. Examples of non-personal information may be any operator configuration information (e.g. roaming priority list).

[0046] The platform 204 will retrieve the information as needed (e.g., from the SIM card, device 202, carrier 206, or another system) and install / download that information in the eSIM or device 202 itself. The platform can do this in many ways, such as by keeping the information on the cloud, having a client on the plastic SIM that will manage it, etc. For example: the platform 204 will retrieve the contacts on the SIM card by communicating directly with the device 202, and the device 202 will obtain, then store it on the cloud, and then download it to the eSIM by binding that information as part of a new profile to be downloaded to the new eSIM.

[0047] Figure 4 A system flow chart for verifying compatibility between a SIM card and an eSIM according to one embodiment is shown. As an option, the system flow chart can be implemented in the context of the details of the previous figure and / or any subsequent figure. However, of course, the flow chart can be implemented in the context of any desired environment.

[0048] Figure 4 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 the actions that the platform 204 causes to be performed to activate an eSIM from a SIM card.

[0049] A SIM card typically stores personal information and SIM applications. An example of personal information may be a contact's phone number and details. An example of a SIM application is an operator application that changes the preferred roaming operation of the device 202 on the fly.

[0050] Once the platform 204 will receive the request to move from the use of the SIM card to the eSIM, it will run an algorithm that will obtain information as needed (e.g., from the SIM card, device 202, operator 206, or another system, etc.). The platform 204 will further verify that the eSIM is compatible to maintain personal information and SIM applications. If the eSIM is compatible, it will verify that the profile to be downloaded for the eSIM has the same personal information and SIM applications that currently exist on the SIM card.

[0051] Once the platform 204 completes the verification, it will update the user in any channel. For example, via the device 202 operating system (OS), dedicated application (OEM, operator), short message service (SMS), call or any other channel.

[0052] Figure 5 A system flow diagram for verifying compatibility of a target mobile device with an eSIM profile according to one 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.

[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 the actions that the platform 204 causes to be performed to activate an eSIM from a SIM card.

[0054] SIM cards are typically movable from one type of device to another. Examples include from one version of a mobile phone to another version of a mobile phone, from one device manufactured by a first company to another device manufactured by a second company, from one type of device to another type of device (e.g., a smartwatch to a mobile phone), or any other combination.

[0055] Once the platform 204 will receive a request to activate an eSIM from a SIM card, it will run an algorithm that will obtain information as needed (e.g., from the SIM card, device 202, operator, or another system) and verify that the device 202 that should get the new profile of the eSIM is compatible with that profile.

[0056] For example, both may be compatible, but only the feature of saving contacts cannot be saved on a new profile on a new device. This means that even if the eSIM can hold a profile with contact information, the new device cannot read contacts from the eSIM with the profile.

[0057] The platform 204 will also verify which other devices are suitable for the new profile in general. It will also verify which parts of the SIM card profile are suitable on the new device and which are not. It can also notify the user of the results of the verification.

[0058] In an embodiment, if compatibility does not exist, the platform 204 may initiate a repair of the eSIM or of the profile in a manner that will enable the profile to be downloaded to the device 202 .

[0059] In an example where all are compatible, but only the feature of saving contacts cannot be saved on a new profile on a new device, then the platform 204 may download additional software to the device 202 to enable the device 202 to read the contacts, or the platform 204 may update the profile that will enable the device 202 to read the contacts in another manner.

[0060] Figure 6 A system flow diagram for verifying compatibility of an eSIM profile with a target device according to one 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.

[0061] 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 the actions that the platform 204 causes to be performed to activate an eSIM from a SIM card.

[0062] SIM cards are typically movable from one type of device to another. Examples include from one version of a mobile phone to another version of a mobile phone, from one device manufactured by a first company to another device manufactured by a second company, from one type of device to another type of device (e.g., a smartwatch to a mobile phone), or any other combination.

[0063] Once the platform 204 will receive the request to activate the eSIM from the SIM card, it will run an algorithm that will obtain information as needed (e.g., from the SIM card, the device 202, the operator, or another system) and verify that the profile that should be moved to the new device 202 is compatible for the device 202. It will also verify which profiles are appropriate for the new device 202.

[0064] In an embodiment, if compatibility does not exist, the platform 204 may initiate a repair of the eSIM or of the profile in a manner that will enable the profile to be downloaded to the device 202. For example, it may be that the profile intended to be downloaded is incompatible with the device 202, however another profile is compatible, and the platform 205 will detect the compatible profile and may provide the other compatible profile to the user.

[0065] 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.

[0066] Coupled to the network 702 are a plurality 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.

[0067] 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.

[0068] 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.

[0069] 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.

[0070] 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.

[0071] 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, through various possible standard or proprietary communication protocols (e.g., via Bluetooth, near field communication (NFC), cellular communication, etc.).

[0072] 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 extract) the instructions from the computer-readable medium and execute the instructions to perform 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; and optical storage devices. BLU-RAY disk; etc.

[0073] 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.

[0074] 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 described figures. Furthermore, 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.

[0075] 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. In addition, some or all of these other components may be combined, some components may be omitted entirely, and additional components may be added while still implementing 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.

[0076] In the above description, unless otherwise indicated, the subject matter is described with reference to the actions and symbolic representations of the operations performed by one or more devices. As such, 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 a processor. This manipulation converts data or keeps it in a position in the memory system of a 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 may also be implemented in hardware.

[0077] In order to facilitate understanding of the subject matter described herein, many aspects are described with respect to 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 each action can be performed by a dedicated circuit or circuit system, by a program instruction 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 executing 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.

[0078] 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.

[0079] 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.

[0080] Although various embodiments have been described above, it should be understood that they are 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 activating an eSIM, the method include: receiving a request to activate an eSIM of a target mobile device from a SIM card or another eSIM of a source mobile device; In response to the request, access data stored on the SIM card or the other eSIM and information associated with the eSIM; as well as causing activation of the eSIM from the SIM card or the other eSIM, the activation being based on data stored on the SIM card or the other eSIM and the information associated with the eSIM, and comprising at least: verifying whether the eSIM is compatible with the data stored on the SIM card or the other eSIM, In response to verifying that the eSIM is compatible to preserve the data stored on the SIM card or the other eSIM, transferring the data stored on the SIM card or the other eSIM to the eSIM, After transferring the data, the eSIM is enabled for use by the target mobile device. 2 . The non-transitory computer-readable medium of claim 1 , wherein the method is performed by the target mobile device. 3 . The non-transitory computer-readable medium of claim 1 , wherein the method is performed by a platform running on a server separate from the target mobile device. 4 . The non-transitory computer-readable medium of claim 1 , wherein the request is received as a result of user input to the target mobile device.

5. The non-transitory computer readable medium of claim 1, wherein the eSIM is computer code. The non-transitory computer readable medium of claim 5 , wherein the computer code is a software application. 7 . The non-transitory computer-readable medium of claim 1 , wherein the data is transferred to the eSIM as a profile of the eSIM.

8. The non-transitory computer-readable medium of claim 1, wherein the data stored on the SIM card or the other eSIM includes identity information and authentication information for at least one subscriber of a provider network.

9. The non-transitory computer-readable medium of claim 1 , wherein causing the eSIM to be activated from the SIM card or the other eSIM is also include: Additional software is downloaded to the target mobile device to achieve compatibility between the target mobile device and the data.

10. The non-transitory computer-readable medium of claim 1, wherein the data stored on the SIM card or the other eSIM includes personal information of at least one subscriber and configuration information of a provider network.

11. The non-transitory computer readable medium of claim 1 , further comprising: include: In response to the request, a version of the SIM card or the other eSIM is accessed, wherein the activation is based on the version of the SIM card or the other eSIM.

12. The non-transitory computer-readable medium of claim 1, wherein the information associated with the eSIM comprises a version of the eSIM.

13. The non-transitory computer-readable medium of claim 1, wherein enabling the eSIM to be used by the target mobile device comprises providing the eSIM to a target mobile device for use thereby.

14. A method for activating an eSIM, include: receiving a request to activate an eSIM of a target mobile device from a SIM card or another eSIM of a source mobile device; In response to the request, access data stored on the SIM card or the other eSIM and information associated with the eSIM; as well as causing activation of the eSIM from the SIM card or the other eSIM, the activation being based on data stored on the SIM card or the other eSIM and the information associated with the eSIM, and comprising at least: verifying that the eSIM is compatible with the data stored on the SIM card or the other eSIM, In response to verifying that the eSIM is compatible to preserve the data stored on the SIM card or the other eSIM, transferring the data stored on the SIM card or the other eSIM to the eSIM, After transferring the data, the eSIM is enabled for use by the target mobile device.

15. A system for activating an eSIM, include: memory, which stores computer instructions; as well as at least one computer processor configured to execute the computer instructions, the computer instructions being configured to perform a method comprising: receiving a request to activate an eSIM of a target mobile device from a SIM card or another eSIM of a source mobile device; In response to the request, access data stored on the SIM card or the other eSIM and information associated with the SIM card; and causing activation of the eSIM from the SIM card or the other eSIM, the activation being based on data stored on the SIM card or the other eSIM and the information associated with the eSIM, and comprising at least: verifying whether the eSIM is compatible with the data stored on the SIM card or the other eSIM, In response to verifying that the eSIM is compatible to preserve the data stored on the SIM card or the other eSIM, transferring the data stored on the SIM card or the other eSIM to the eSIM, After transferring the data, the eSIM is enabled for use by the target mobile device.

Citation Information

Patent Citations

  • Method and apparatus for selectively activating multiple subscriber identity modules

    CN104012067A

  • Facilitating multiple subscriber identity support in a wireless device

    CN104982050A

  • Data processing method and device and terminal

    CN105792179A

  • SIM card-to-eSIM card data migration method and device

    CN107734498A

  • Managing multiple active subscriber identity module profiles

    CN107925867A