Methods and systems for determining eSIM profile presence for reactivation

A service provider may receive a user device that includes an embedded subscriber identity module (eSIM) associated with an equipment identifier (eID) with a previously provisioned service. The previously provisioned service may be provided by an eSIM profile (identified by an Integrated Circuit Card Identifier or ICCID) and the eSIM may contain more than one ICCID. The service provider may re-provision one of the existing ICCIDs to provide service based on the eID and historical data. The device and the carrier provisioning system may determine whether one of the profiles (ICCIDs) installed in the eSIM matches an already known eSIM profile (ICCD) and re-provision the eSIM profile (ICCD) for new wireless service. The service provider may then activate the user device for communication via the new wireless service in response to re-provisioning of the applicable eSIM profile (ICCID).

BACKGROUND

Mobile devices with embedded subscriber identity modules (eSIM) have become more popular due to many advantages over traditional SIMs (non-eSIMs). While eSIM technology has brought many advantages, it has also introduced some disadvantages. In order to reactivate a device using eSIM technology, a new eSIM profile must be downloaded to the device. If a device has been reactivated numerous times, attempting to download a new eSIM profile to the eSIM may waste resources or may result in profile download failure due to lack of available memory on the eSIM.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Mobile devices with eSIMs have many advantages over mobile devices with traditional SIMs (non-eSIMs). For example, mobile devices with eSIMs may be more compact in size due to the lack of need for a SIM slot on the mobile device. In addition, mobile devices with eSIM technology may provide a flexibility of switching cellular network services among different service providers. Furthermore, eSIM technology may provide better customer experience because customers do not need to insert a physical SIM card into the mobile device or remove the physical SIM card from the mobile device when, for example, activating a device or changing service providers.

A disadvantage of eSIM technology may involve cellular service reactivation with a previously active eSIM device or cellular service activation with a previously inactive device. For example, a customer may switch cellular network providers and may need to reactivate an eSIM device that was previously activated on a different cellular network. As another example, a customer may purchase an eSIM device from an original equipment manufacturer (OEM) or from another source and may need to activate the eSIM device with a cellular network service provider.

In order to reactivate an eSIM device, a wireless network service provider may provision a network service using a new eSIM profile, which is downloaded to the eSIM device via a remote SIM provisioning (RSP) platform. A wireless network service provider, however, may not reactivate existing eSIM profiles because the wireless network service provider may not be aware of which eSIM profiles remain on an eSIM. For example, a customer may erase an eSIM profile locally and a wireless network service provider may not be aware that the erased eSIM profile no longer exists on the eSIM.

Due to the restricted storage allocated to eSIM, an eSIM may also be able to store only a limited number of eSIM profiles. Each time an eSIM device is reactivated, a new eSIM profile is downloaded to and stored on the eSIM. If an eSIM device is reactivated several times, the eSIM may become full. If the eSIM becomes full, a new eSIM profile may not be able to be downloaded to the eSIM when the eSIM device is being reactivated. A full eSIM may result in a reactivation failure for an eSIM mobile device.

Systems and methods described herein may detect eSIM profiles previously stored on an eSIM that may be re-provisioned for service. In this way, the overall profile inventory management and customer experience may be improved. For example, because new eSIM profiles may be used only after verification that old eSIM profiles are not available for re-provisioning, profile inventory management may be improved and the speed of reactivating a device may be increased.

In addition, implementations described herein may allow a service provider to determine if an eligible eSIM profile exists for reactivation on an eSIM with minimal user interaction. For example, a service provider may determine whether an eligible eSIM profile exists for reactivation without the installation of a service provider application on the eSIM device. In this way, an OEM may not be required to preload a carrier-specific application or a carrier-specific entitlement server address on the eSIM device. Additionally, a customer may not be required to download a carrier-specific application to the eSIM device to begin using the device. Therefore, implementations described herein may be scalable for multiple wireless network service providers. Additionally, if a service provider does not need to download a new eSIM profile it may save network bandwidth and other network resources.

FIG. 1is a diagram of an exemplary environment100in which the systems and/or methods, described herein, may be implemented. As shown inFIG. 1, environment100may include user equipment (UE) device110, a remote SIM Provisioning Platform (RSP)120, a carrier provisioning system130, a network140, and a point-of-sale (POS) device170. The elements shown within dotted area180(i.e., RSP120and carrier provisioning system (CPS)130) may be associated with a wireless service provider that provides wireless services to UE110. The elements shown within dotted area180may also be interconnected via an internal company network, such as a local area network or wide area network, that includes wired, wireless and/or optical connections between the elements illustrated inFIG. 1. In other implementations, the devices illustrated within dotted area180may be directly coupled or indirectly coupled to each other via an external network, such as the Internet.

UE110may include any device with long-range (e.g., cellular or mobile wireless network) wireless communication functionality. For example, UE110may include a handheld wireless communication device (e.g., a mobile phone, a smart phone, a tablet device, etc.); a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, etc.); a laptop computer, a tablet computer, or another type of portable computer; a desktop computer; a customer premises equipment (CPE) device, such as a set-top box or a digital media player (e.g., Apple TV, Google Chromecast, Amazon Fire TV, etc.), a WiFi access point, a smart television, etc.; a portable gaming system; a global positioning system (GPS) device; a home appliance device; a home monitoring device; and/or any other type of computer device with wireless communication capabilities and a user interface. UE110may include capabilities for voice communication, mobile broadband services (e.g., video streaming, real-time gaming, premium Internet access etc.), best effort data traffic, and/or other types of applications. UE110may also be referred to herein as a user device, a mobile device, or an eSIM device.

UE110may include an eSIM card150(also referred to herein as eSIM150). eSIM150may be implemented as an embedded universal integrated circuit card (eUICC) that allows UE110to access a wireless network. eSIM150may be directly embedded into UE110. eSIM150may store Integrated Circuit Card Identifiers (ICCIDs). ICCIDs may also be referred to as eSIM profiles or SIM profiles. An ICCID may store a user's subscription and network settings and allow the user to connect to the wireless network.

UE110may include a local profile assistant (LPA)160. LPA160may include logic associated with interfacing with eSIM150to activate UE110. LPA160may interface with RSP120to activate existing ICCIDs or download and activate a new ICCID to eSIM150.

RSP120may include one or more computing devices or systems that provide for remote provisioning of ICCIDs to user devices110. For example, RSP120may include a subscription manager—data preparation (SM-DP) device that acts as an eSIM subscription management server associated with a wireless carrier network. RSP120may act as an interface between LPA160on UE110and CPS130to re-provision an ICCID with a new service or download an ICCID to eSIM150.

Carrier provisioning system130may include one or more computing devices or systems that act as a backend for a wireless network to facilitate operations of the wireless network. For example, carrier provisioning system130may include billing-related systems/databases, an electronic telephone number inventory (ETNI), a mobile terminating access service (MTAS), a home subscriber server (HSS), a unified data management (UDM) function, etc. Carrier provisioning system130may store historical records of eSIM profiles associated with UEs110. Carrier provisioning system130may interact with RSP120to facilitate activation of UE110, as described in detail below.

Network140may include one or more wired, wireless and/or optical networks that are capable of receiving and transmitting data, voice and/or video signals. For example, network140may include one or more public switched telephone networks (PSTNs) or other type of switched network. Network140may also include one or more wireless networks and may include a number of transmission towers for receiving wireless signals and forwarding the wireless signals toward the intended destination. Network140may further include one or more satellite networks, one or more packet switched networks, such as an Internet protocol (IP) based network, a local area network (LAN), a wide area network (WAN), a personal area network (PAN), a WiFi network, a Bluetooth network, an intranet, the Internet, or another type of network that is capable of transmitting data. Network140provides wireless packet-switched services and wireless Internet protocol (IP) connectivity to UEs110to provide, for example, data, voice, and/or multimedia services.

POS device170(also referred to as POS170) may include an interface for interacting with a customer for activating UE110. In one implementation, POS170may be located at a store where the customer has purchased UE110and subscribed to cellular network service for UE110. In another implementation, POS170may include an application associated with a wireless service provider or a website associated with the wireless service provider. POS170may display instructions for activating UE110. In addition, POS170may display additional information needed to activate UE110.

As used herein, the term “user” is intended to be broadly interpreted to include UE110and/or a person using UE110. Also, the terms “user,” “owner,” “consumer,” “subscriber,” and/or “customer” are intended to be used interchangeably.

The number of devices and/or networks, illustrated inFIG. 1, is provided for explanatory purposes only. In practice, additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those illustrated inFIG. 1may be used. Also, in some implementations, one or more of the components or networks may perform one or more functions described as being performed by another one or more of the other components or networks. The components and networks shown inFIG. 1may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

FIG. 2is a diagram of exemplary components of a device200that may correspond to one of the components of UE110, RSP120, carrier provisioning system130, POS170, and/or network140. As illustrated, device200may include a bus210, a processing unit220, a memory230, an input component240, an output component250, and a communication interface260.

Bus210may permit communication among the components of device200. Processing unit220may include one or more processors or microprocessors that interpret and execute instructions. Additionally or alternatively, processing unit220may be implemented as or include one or more application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or the like.

Memory230may include a random access memory (RAM) or another type of dynamic storage device that stores information and instructions for execution by processing unit220, a read only memory (ROM) or another type of static storage device that stores static information and instructions for the processing unit220, and/or some other type of magnetic or optical recording medium and its corresponding drive for storing information and/or instructions.

Input component240may include a device that permits an operator to input information to device200, such as a button, a switch, a keyboard, a keypad, a mouse, a microphone or the like. Output component250may include a device that outputs information to the operator, such as a display (e.g., a liquid crystal display), a printer, a speaker, a light emitting diode (LED), etc.

Communication interface260may include one or more transceivers that enables device200to communicate with other devices and/or systems. For example, communication interface260may include one or more radio frequency (RF) receivers, transmitters, and/or transceivers and or more antennas for transmitting and receiving data. Communication interface260may also include a modem or Ethernet interface to a LAN or other mechanism for communicating with other devices.

AlthoughFIG. 2shows exemplary components of device200, in other implementations, device200may contain fewer components, different components, differently arranged components, or additional components than depicted inFIG. 2. Alternatively, or additionally, one or more components of device200may perform one or more tasks described as being performed by one or more other components of device200.

FIG. 3illustrates an exemplary method300for reactivating an eSIM device when an eligible eSIM profile exists. Method300may be performed by components of UE110, RSP120, and/or carrier provisioning system130.

Method300may begin when RSP120receives an equipment identifier (eID) from UE110(block302). A customer may sign up to access a wireless network service using UE110and may be prompted to check whether UE110is eligible to be enabled for the wireless network service. In one implementation, POS170may provide instructions to the customer for determining the eligibility of UE110. For example, POS170may instruct the customer to check the device eligibility by accessing the “Settings” menu and choosing an “Add Service Provider” option via UE110. In addition, POS170may present a Quick Response (QR) code and may provide instructions to the customer to scan the QR code. The QR code may contain a fully qualified domain name (FQDN) of RSP120via UE110. When the QR code has been scanned, LPA160may send the eID associated with UE110to RSP120.

Processing may continue with RSP120forwarding the eID of UE110to carrier provisioning system130(block304). In one implementation, RSP120may additionally forward any notifications received for the eID (e.g., notifications indicating profile management actions, etc.) to carrier provisioning system130. In response to receiving the eID of UE110, carrier provisioning system130may locate any records of ICCIDs associated with eSIM150of UE110and may determine whether any ICCIDs are eligible for service re-provisioning (block306). For example, carrier provisioning system130may locate historical records of all ICCIDs previously associated with eSIM150and may determine whether any of the ICCIDs have been removed or de-activated. In one implementation, carrier provisioning system130may determine whether any of the ICCIDs have been removed or de-activated by determining whether any Delete Notifications have previously been received by RSP120for any ICCIDs associated with the eSIM150.

When an ICCID that is eligible for re-provisioning has been identified, carrier provisioning system130may send the ICCID to RSP120to determine whether eSIM150stores a matching ICCID (block308). In one implementation, if more than one eligible ICCID has been identified, carrier provisioning system130may send the most recently assigned ICCID to RSP120. For example, carrier provisioning system130may determine which ICCID has been most recently provisioned for use and may send the most recently provisioned ICCID to RSP120. In response, RSP120may send a notification to LPA160to determine whether eSIM150stores a matching ICCID (block310). In addition, RSP130may send LPA160a request for an enabled/disabled state associated with the ICCID if the matching ICCID is present on eSIM150.

If a matching ICCID is installed on eSIM150(block310—yes), UE110may send RSP120a “yes” indication that the matching ICCID is installed on eSIM150along with the enabled/disabled status of the ICCID and RSP120may send the “yes” indication and the enabled/disabled status to carrier provisioning system130(block312). In response to receiving the indication that eSIM150stores the matching ICCID, carrier provisioning system130may re-provision the ICCID with a new service and may transmit instructions to the customer for activating the eSIM profile (block314). In one implementation, carrier provisioning system130may transmit the activation instructions to POS170for the customer to view. For example, carrier provisioning system130may transmit instructions for enabling the ICCID if the ICCID is not enabled, such as instructions for performing a power cycle to enable to ICCID, etc. When the customer has completed/performed the actions corresponding to the instructions, UE110may be activated with cellular service.

If a matching ICCID is not stored on eSIM150(block310—no), UE110may send RSP120a “no” indication that no matching ICCID is stored on eSIM150and RSP120may transmit the “no” indication to carrier provisioning system130(block316). Carrier provisioning system130may determine whether additional ICCIDs are available for re-provisioning (block318). For example, carrier provisioning system130may determine whether more than one eligible ICCID was identified in block306. If additional ICCIDs are available for re-provisioning (block318—yes), carrier provisioning system130may determine which ICCID of the additional ICCIDs has been most recently provisioned for use (block320). When the most recently provisioned ICCID has been identified, carrier provisioning system130may send the ICCID to RSP120and on to LPA160to determine whether eSIM150stores a matching ICCID in the manner described above (blocks308and310).

If carrier provisioning system130determines that no additional ICCIDs are available for re-provisioning (block318—no), carrier provisioning system130may select a new ICCID for activation (block322). For example, carrier provisioning system130may identify an ICCID that is not being used from the inventory and may provision the ICCID for activation.

When no additional ICCIDs are available for re-provisioning and carrier provisioning system130has selected a new ICCID for activation, carrier provisioning system130may notify RSP120to pair the new ICCID to the eID associated with eSIM150and may provide instructions for activating the service on UE110(block324). For example, carrier provisioning system130may forward the new ICCID to RSP120with instructions to pair the new ICCID with the eID. In addition, carrier provisioning system130may provide instructions to the customer via POS170and/or UE110on the next steps to take to activate the service on UE110. When the customer has followed the steps to activate UE110, RSP120may receive a request from UE110for an eSIM profile and RSP120may forward the new eSIM profile with corresponding ICCID to UE110(block326). In one implementation, LPA160may receive the new ICCID and may install the new eSIM profile on eSIM150. When the eSIM profile is installed and enabled, cellular service may be activated on UE110.

FIG. 4is a diagram illustrating exemplary communications between devices in network environment100. Communications inFIG. 4represent communications for re-provisioning an eSIM profile.

Referring toFIG. 4, when a customer wishes to activate UE110, POS170may present a QR code that contains a FQDN of RSP120(402) and UE110may scan the QR code (404). In response to scanning the QR code, UE110may forward a message to RSP120that includes an eID associated with UE110and a request that service be activated for UE110(406). RSP120may forward the message to carrier provisioning system130(408).

After receiving the eID and the request, carrier provisioning device130may search for ICCIDs associated with the eID that are eligible for re-provisioning (410). For example, carrier provisioning device130may search historical records of ICCIDs associated with the eID and may determine if any ICCIDs exist that do not include “Delete Notifications” indicating that the ICCIDs have been deleted or de-activated. If carrier provisioning device130locates more than one ICCID that is ready for re-provisioning, carrier provisioning device130may identify the most recently provisioned ICCID (412).

When carrier provisioning system130identifies an ICCID or the most recently provisioned ICCID, carrier provisioning system130may forward the ICCID to RSP120with instructions to check whether a matching ICCID exists on eSIM150(414). RSP120may send a message to UE110inquiring whether the ICCID is stored on eSIM150(416). LPA160may determine that a matching ICCID is stored on eSIM150and may forward an indication to RSP120that the matching ICCID is stored on eSIM150(418). RSP120may forward the indication that the matching ICCID exists on eSIM150to carrier provisioning system130(420).

Although not shown inFIG. 4, if a matching ICCID is not stored on eSIM150and more than one eligible ICCID has been identified by carrier provisioning system130, carrier provisioning system130may identify the next most recently provisioned ICCID and send instructions to RSP120to determine whether a matching ICCID is stored on eSIM150. Carrier provisioning system130may continue to locate the next most recently provisioned ICCID associated with the eID until a matching ICCID is identified on eSIM150. If no matching ICCIDs are stored on eSIM150, the process may continue as discussed below with respect toFIG. 5.

When carrier provisioning system130receives the indication that the matching ICCID exists on eSIM150, carrier provisioning system130may provision network service on the ICCID (422). In addition, carrier provisioning system130may send activation instructions to POS170(424). For example, carrier provisioning system130may send instructions to allow the customer to activate the eSIM profile in order to activate UE110. In one implementation, carrier provisioning system130may send instructions to power cycle UE110, enable the SIM profile if the eSIM profile is disabled, etc. POS170may display the instructions to activate the eSIM profile (426). After the customer has followed the instructions to activate the eSIM profile, UE110may be activated with a wireless network service (428).

FIG. 5is a diagram illustrating exemplary communications between devices in network environment100. Communications inFIG. 5represent communications for provisioning an eSIM profile when an eSIM is not available for re-provisioning.

Referring toFIG. 5, when a customer wishes to activate UE110, POS170may present a QR code that contains a FQDN of RSP120(502) and UE110may scan the QR code (504). In response to scanning the QR code, UE110may forward a message to RSP120that includes an eID associated with UE110and a request that network service be activated for UE110(506). RSP120may forward the message to carrier provisioning system130(508).

After receiving the eID and the request, carrier provisioning device130may search historical ICCIDs associated with the eID (510) and may identify an ICCID that is ready for re-provisioning (512). When carrier provisioning system130identifies an ICCID to be re-provisioned, carrier provisioning system130may forward the ICCID to RSP120with instructions to check whether a matching ICCID exists on eSIM150(514). RSP120may send a message to UE110inquiring whether the ICCID is stored on eSIM150(516).

LPA160may determine that a matching ICCID is not stored on eSIM150and may forward an indication to RSP120that no matching ICCID is stored on eSIM150(518). RSP120may forward the indication that there is no matching ICCID on eSIM150to carrier provisioning system130(520) and carrier provisioning system130may determine a new ICCID for provisioning (522). For example, carrier provisioning system130may identify an ICCID that is not currently being used from an inventory of available ICCIDs.

Carrier provisioning system130may send instructions to RSP120to pair the new ICCID with the eID associated with UE110and to prepare to download the eSIM profile to UE110when UE110requests the eSIM profile (524). In addition, carrier provisioning system130may transmit instructions to POS170for activating the eSIM profile (526). For example, carrier provisioning system130may transmit instructions for the customer to follow to activate the eSIM profile on UE110. In one implementation, the instructions may indicate that the customer should scan the QR code again in order to activate the eSIM profile. POS170may display the instructions for the customer to follow (528).

UE110may perform functions associated with activating the eSIM profile based on customer input (530) and may send the eID along with a request for the eSIM profile to RSP120(532). For example, the customer may follow the instructions displayed on POS170and, when the instructions are completed, UE110may send the eID and the request to RSP120. UE110may then download the eSIM profile from RSP120(534). For example, LPA160may download the eSIM profile and install the eSIM profile on eSIM150. When the eSIM profile is downloaded, the eSIM profile may be installed and enabled (536). At this point, the eSIM profile may be activated and UE110may be activated with the wireless network service.

If UE110was not previously activated with a carrier's service, UE110may be activated for the first time. In this case, carrier provisioning system130may have no historical activation record associated with eSIM150or UE110. A new activation for UE110may follow the steps described above with respect toFIG. 5in order to install the eSIM profile on eSIM150and activate UE110with the wireless network service. Therefore, the implementation described above may be used for a new eSIM device activation in addition to re-activation of an eSIM device when an eSIM is not available for re-provisioning.

For example, while a series of blocks have been described with respect toFIG. 3, and a series of signal flows/messages have been described with respect toFIGS. 4 and 5, the order of the blocks and/or signal flows may be modified in other implementations. Further, non-dependent blocks may be performed in parallel.

The term “logic,” as used herein, may refer to a combination of one or more processors configured to execute instructions stored in one or more memory devices, may refer to hardwired circuitry, and/or may refer to a combination thereof. Furthermore, a logic may be included in a single device or may be distributed across multiple, and possibly remote, devices.