Patent Description:
Wireless mobile network operators (MNOs) continue to upgrade wireless networks to support newer wireless communication standards, including fourth generation (<NUM>) Long Term Evolution (LTE) and Long Term Evolution Advanced (LTE-A) technologies as well as fifth generation (<NUM>) technologies. Wireless devices continue to evolve to incorporate newer, configurable wireless credentials, such as eSIMs that can be loaded to and subsequently activated on an electronic universal integrated circuit card (eUICC) of a wireless device. To support newer <NUM> wireless communication standards, specifications for eSIMs for <NUM> enabled wireless devices are being developed. Rather than a universal eSIM that can be loaded to a <NUM>-capable wireless device or to a non-<NUM>-capable wireless device, standards are proposed for <NUM> eSIMs and non-<NUM> eSIMs. As such, MNOs need to determine a proper eSIM type to load to a wireless device based on the wireless device's wireless communication capabilities. As these capabilities may be unknown when an eSIM is assigned to a wireless device, there exists a need for flexible eSIM assignment and deployment that accounts for different wireless device capabilities.

<CIT> discloses a device comprising a chip storing a first subscription relating to the first mobile network operator in a home country. The chip stores a second subscription relating to a second mobile network operator and associated with a preferred communication technology. The chip receives location information and analyses whether an extended cell identity value is present within the location information. The chip detects, based upon the analysis, a currently available communication technology relating to a second mobile network. The chip compares the currently available communication technology to at least one preferred communication technology. If the currently available communication technology matches at least one preferred communication technology, then the chip switches to a second subscription associated with the preferred communication technology. The chip sends to the device at least one identifier relating to the second subscription related to the second mobile network.

<CIT> discloses to determine if an electronic subscriber identity module (eSIM) associated with a requested service can be installed in a secure element (SE) housed in a wireless device. Before requesting deployment of an eSIM suitable for the requested service from an eSIM delivery server, a carrier server asks that an original equipment manufacturer (OEM) server validate that an eSIM corresponding to a customer request should be deployed. The OEM server obtains information about the wireless device and information about the SE. When the carrier server requests validation, the OEM server evaluates the wireless device information and/or the SE information. If the OEM server indicates that deployment of the eSIM should proceed, the OEM server also indicates the eSIM type that is compatible with the wireless device and with the SE housed in the device.

GSM Association: "RSP Technical Specification Version <NUM>" discloses the GSMA's remote SIM Provisioning Architecture for consumer devices.

GSM Association: "Embedded SIM Remote Provisioning Architecture" discloses an architecture approach for the remote provisioning and subscription management of devices, while at the same time maintaining at least the same level of security both for network operators and subscribers.

<CIT> discloses techniques for provisioning device configuration files and electronic Subscriber Identity Modules (eSIMs) to mobile devices.

Preferred advantageous embodiments thereof are defined by the sub-features of the dependent claims.

Representative embodiments set forth techniques for flexible electronic subscriber identity module (eSIM) deployment to a wireless device by a wireless network entity, including generation of multiple eSIMs using an identical eSIM identifier and a set of common eSIM configuration data, such as ciphering keys, integrity keys, applets, elementary files, and/or dedicated files, and subsequent selection of an eSIM from the multiple eSIMs based on capabilities of the wireless device. Capabilities to support different wireless communication standards of a wireless device may be unknown when assignment of an eSIM to a wireless device (or generation of an eSIM for future assignment) occurs. To account for different capabilities, multiple eSIMs that correspond to different sets of wireless device capabilities can be generated without knowledge of the wireless communication standards that a wireless device supports. In some embodiments, responsive to an order from an MNO back-end server, a wireless network entity, e.g., a provisioning server, can generate multiple eSIMs for a wireless device. In some embodiments, a specific wireless device is specified in the order. In some embodiments, the order includes a hardware identifier value for the wireless device, such as an eUICC identifier (EID) value. In some embodiments, the provisioning server selects a unique eSIM identifier value, such as an integrated circuit card identifier (ICCID) value to associate with an eSIM, and uses the identical unique eSIM identifier value to generate multiple eSIMs, where each eSIM corresponds to a different wireless communication standard capability for a wireless device. Subsequently, the provisioning server can select one of the multiple eSIMs to download to a wireless device based on information obtained regarding wireless communication capabilities of the wireless device. In some embodiments, the multiple eSIMs include a first eSIM that includes <NUM> information and a second eSIM that excludes <NUM> information. In some embodiments, the <NUM> information includes file structures and/or applets specific to <NUM> wireless communication protocols. In some embodiments, the provisioning server selects an eSIM from the multiple eSIMs based at least in part on whether the wireless device is <NUM> capable. After selection of an eSIM that uses an ICCID value and a binding of a profile package that includes the eSIM for a wireless device, the provisioning server deletes remaining eSIMs of the multiple eSIMs that use the identical ICCID value.

This Summary is provided merely for purposes of summarizing some example embodiments so as to provide a basic understanding of some aspects of the subject matter described herein. Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein in any way.

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

The included drawings are for illustrative purposes and serve only to provide examples of possible structures and arrangements for the disclosed inventive apparatuses and methods for providing wireless computing devices. These drawings in no way limit any changes in form and detail that may be made to the embodiments by one skilled in the art without departing from the spirit and scope of the embodiments. The embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements.

Representative applications of apparatuses and methods according to the presently described embodiments are provided in this section. These examples are being provided solely to add context and aid in the understanding of the described embodiments. It will thus be apparent to one skilled in the art that the presently described embodiments can be practiced without some or all of these specific details. In other instances, well known process steps have not been described in detail in order to avoid unnecessarily obscuring the presently described embodiments. Other applications are possible, such that the following examples should not be taken as limiting.

Representative embodiments set forth techniques for flexible electronic subscriber identity module (eSIM) deployment for a wireless device by a wireless network entity, including generation of multiple eSIMs using an identical eSIM identifier and a set of common eSIM configuration data, such as ciphering keys, integrity keys, applets, elementary files, and/or dedicated files, and subsequent selection of an eSIM based on capabilities of the wireless device. Wireless communication standards continue to evolve including newer, fifth generation (<NUM>) wireless protocols. New versions of wireless protocols may specify features that may be incompatible with previous generation wireless communication devices. Some wireless communication devices may support <NUM> capabilities, some wireless communication devices may require particular software versions to support <NUM> capabilities, and some wireless communication devices may not support <NUM> capabilities. Capabilities of a wireless device to support different wireless communication standards, however, may be unknown when assignment of an eSIM to a wireless device occurs. An MNO may need to select a proper eSIM type for a target wireless device to forestall compatibility issues, such as to avoid an installation failure or a post-installation malfunction. Instead, different eSIM types may be generated and loaded to wireless devices based on their capabilities.

To account for different capabilities of different wireless devices, multiple eSIMs that correspond to different sets of wireless device capabilities can be generated for a wireless device without knowledge of the wireless communication standards that the wireless device supports. In some embodiments, responsive to an order from an MNO back-end server, a wireless network entity, e.g., a provisioning server, generates multiple eSIMs for a wireless device. In some embodiments, the multiple eSIMs are specific to a wireless device identified in the order. In some embodiments, the order includes a hardware identifier value for the wireless device, such as an eUICC identifier (EID) value. In some embodiments, the order includes a unique eSIM identifier value to be associated with the eSIM and with which to identify the eSIM. In some embodiments, the order includes an eSIM profile type to be generated. In some embodiments, the provisioning server selects a unique eSIM identifier value, such as an integrated circuit card identifier (ICCID) value, and uses the identical unique eSIM identifier value to generate the multiple eSIMs, where each eSIM corresponds to a different wireless communication standard capability for a wireless device. In some embodiments, each eSIM of the multiple eSIMs include a set of common eSIM configuration data, such as one or more of: ciphering keys, integrity keys, applets, elementary files, and/or dedicated files. In some embodiments, capability of a wireless device to support a particular wireless communication protocol, such as a <NUM> protocol, is not available when the multiple eSIMs are generated. Subsequently, the provisioning server can select one of the multiple eSIMs to download to a wireless device based on information obtained regarding wireless communication capabilities of the wireless device. In some embodiments, the multiple eSIMs include a first eSIM that includes <NUM> information and a second eSIM that excludes <NUM> information. In some embodiments, the <NUM> information includes file structures and/or applets specific to <NUM> wireless communication protocols. In some embodiments, the provisioning server selects an eSIM from the multiple eSIMs based on whether the wireless device is <NUM> capable. The provisioning server can select an eSIM that includes <NUM> information when the wireless device is <NUM> capable and can select an eSIM that excludes <NUM> information when the wireless device is not <NUM> capable. After selection of an eSIM that uses an ICCID value and a binding of a profile package that includes the eSIM for the wireless device, the provisioning server deletes remaining eSIMs of the multiple eSIMs that use the identical ICCID value.

These and other embodiments are discussed below with reference to <FIG>; however, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes only and should not be construed as limiting.

<FIG> illustrates a block diagram of different components of a system <NUM> that is configured to implement the various techniques described herein, according to some embodiments. More specifically, <FIG> illustrates a high-level overview of the system <NUM>, which, as shown, includes a user equipment (UE) <NUM>, a group of base stations <NUM>-<NUM> to <NUM>-n that are managed by different Mobile Network Operators (MNOs) <NUM>, and a set of provisioning servers <NUM> that are in communication with the MNOs <NUM>. The UE <NUM> can represent a mobile computing device (e.g., an iPhone® or an iPad® by Apple®), the base stations <NUM>-<NUM> to <NUM>-n can represent cellular wireless network entities including evolved NodeBs (eNBs) and/or next generation NodeBs (gNBs or gNB) that are configured to communicate with the UE <NUM>, and the MNOs <NUM> can represent different wireless service providers that provide specific services (e.g., voice and data) to which the UE <NUM> can be subscribed. The UE <NUM> may also be referred to as a wireless device, a mobile device, a mobile wireless device, or the like.

As shown in <FIG>, the UE <NUM> can include processing circuitry, which can include one or more processors <NUM> and memory <NUM>, an embedded Universal Integrated Circuit Card (eUICC) <NUM>, and a baseband component <NUM>. In some embodiments, the UE <NUM> includes one or more physical UICC cards, also referred to as Subscriber Identity Module (SIM) cards (not shown), in addition to or substituting for the eUICC. The components of the UE <NUM> work in conjunction to enable the UE <NUM> to provide useful features to a user of the UE <NUM>, such as localized computing, location-based services, and Internet connectivity. The eUICC <NUM> can be configured to store multiple electronic SIMs (eSIMs) for accessing different services offered by one or more MNOs <NUM> through base stations <NUM>-<NUM> to <NUM>-n. For example, the eUICC <NUM> can be configured to store and manage one or more eSIMs for one or more MNOs <NUM> for different subscriptions to which the UE <NUM> has been associated. To be able to access services provided by the MNOs, an eSIM can be provisioned to the eUICC <NUM>. In some embodiments, the eUICC <NUM> obtains one or more eSIMs (or updates for one or more eSIMs) from one or more associated provisioning servers <NUM>. It is noted that provisioning servers <NUM> can be maintained by a manufacturer of the UE <NUM>, the MNOs <NUM>, third party entities, and the like. Communication of eSIM data between a provisioning server <NUM> and the eUICC <NUM> (or between the provisioning server <NUM> and processing circuitry of the UE <NUM> external to the eUICC <NUM>, e.g., the processor <NUM>) can use a secure communication channel. In some embodiments, the UE <NUM> provides information about communication capability of the UE <NUM> to the provisioning server <NUM>, which provides one or more eSIMs to the UE <NUM> that are selected based at least in part on the communication capability of the UE <NUM>.

<FIG> illustrates a block diagram of a more detailed view <NUM> of particular components of the UE <NUM> of <FIG>, according to some embodiments. As shown in <FIG>, the processor(s) <NUM>, in conjunction with the memory <NUM>, can implement a main operating system (OS) <NUM> that is configured to execute applications <NUM> (e.g., native OS applications and user applications). As also shown in <FIG>, the eUICC <NUM> can be configured to implement an eUICC OS <NUM> that is configured to manage the hardware resources of the eUICC <NUM> (e.g., a processor and a memory embedded in the eUICC <NUM>). The eUICC OS <NUM> can also be configured to manage eSIMs <NUM> that are stored by the eUICC <NUM>, e.g., by installing, enabling, disabling, modifying, or otherwise performing management of the eSIMs <NUM> within the eUICC <NUM> and providing the baseband component <NUM> with access to the eSIMs <NUM> to provide access to wireless services for the UE <NUM>. The eUICC <NUM> OS can include an eSIM manager <NUM>, which can perform management functions for various eSIMs. According to the illustration shown in <FIG>, each eSIM <NUM> can include a number of applets <NUM> that define the manner in which the eSIM <NUM> operates. For example, one or more of the applets <NUM>, when implemented by the baseband component <NUM> and the eUICC <NUM>, can be configured to enable the UE <NUM> to communicate with an MNO <NUM> and provide useful features (e.g., voice connections, messaging services, internet access and the like) to a user of the UE <NUM>.

As also shown in <FIG>, the baseband component <NUM> of the UE <NUM> can include a baseband OS <NUM> that is configured to manage hardware resources of the baseband component <NUM> (e.g., a processor, a memory, different radio components, etc.). According to some embodiments, the baseband component <NUM> can implement a baseband manager <NUM> that is configured to interface with the eUICC <NUM> to establish a secure channel with a provisioning server <NUM> and obtaining information (such as eSIM data) from the provisioning server <NUM> for purposes of managing eSIMs <NUM>. The baseband manager <NUM> can be configured to implement services <NUM>, which represents a collection of software modules that are instantiated by way of the various applets <NUM> of enabled eSIMs <NUM> that are included in the eUICC <NUM>. For example, services <NUM> can be configured to manage different connections between the UE <NUM> and MNOs <NUM> according to the different eSIMs <NUM> that are enabled within the eUICC <NUM>.

<FIG> illustrates a block diagram <NUM> of an exemplary message exchange to provision an eSIM to the UE <NUM> in accordance with an established Global System for Mobile Communications (GSM) Association (GSMA) protocol, e.g., an SGP. <NUM> Remote Service Provisioning (RSP) Technical Specification. At <NUM>, a local profile assistant (LPA) <NUM> operational on the UE <NUM> and external to the eUICC <NUM> initiates an eSIM download by sending a GetEUICCInfo message to an eUICC <NUM> of the UE <NUM> to obtain information from the eUICC <NUM>, e.g., eUICCinfo1 returned at <NUM>, to perform a mutual authentication procedure with a network entity, e.g., with a subscription manager data preparation (SM-DP+) server <NUM>. At <NUM>, the LPA <NUM> sends a GetEUICCChallenge message to the eUICC <NUM> to obtain an eUICCChallenge from the eUICC <NUM> to use for authentication with the SM-DP+ server <NUM>. At <NUM>, the LPA <NUM> of the UE <NUM> sends, via a secure connection to the SM-DP+ server <NUM>, an InitiateAuthentication message that includes the eUICCinfo1 and eUICCChallenge to initiate authentication with the SM-DP+ server <NUM>. Upon successful verification of the eUICCinfo1 by the SM-DP+ server <NUM>, the LPA <NUM> receives in response, at <NUM>, information to authenticate the SM-DP+ server <NUM>, where the information (and/or further parameters derived based on the received information) to the eUICC <NUM> to verify authenticity of the SM-DP+ server <NUM>. Upon successful verification of the information by the eUICC <NUM>, at <NUM>, the eUICC <NUM> provides additional information, e.g., signed certificates and/or signatures, to the LPA <NUM> to send to the SM-DP+, at <NUM>, to authenticate the eUICC <NUM> of the UE <NUM> with the SM-DP+ server <NUM>, and confirmation of successful authentication of the eUICC <NUM> by the SM-DP+ server <NUM> can be provided at <NUM>. Following mutual authentication, the UE <NUM> and SM-DP+ server <NUM> perform a profile download procedure to obtain an eSIM from the SM-DP+ server <NUM> to load into the eUICC <NUM> of the UE <NUM>. The LPA <NUM> initiates the download procedure by sending a PrepareDownload command at <NUM> to the eUICC <NUM>, which verifies information provided in the PrepareDownload command and returns, at <NUM>, signed information to the LPA <NUM>, which communicates the signed information in a GetBoundProfilePackage command at <NUM> to the SM-DP+ server <NUM>. Following successful verification of the signed information, the SM-DP+ server <NUM> returns, at <NUM>, a bound profile package that includes an eSIM (profile) for loading to the eUICC <NUM>. The LPA <NUM>, at <NUM>, forwards the bound profile package to the eUICC <NUM> for loading the eSIM, and the eUICC <NUM> provides confirmation of successful loading of the eSIM at <NUM> to the LPA <NUM>. In order to accommodate different wireless communication capabilities of the UE <NUM>, and to allow for different eSIMs corresponding to different wireless communication capabilities, the procedure illustrated in <FIG> can be modified as further described in the procedure illustrated in <FIG> and <FIG>.

<FIG> illustrates a diagram <NUM> of exemplary message exchange for flexible eSIM deployment to a UE <NUM>. At <NUM>, an MNO network entity, e.g., a backend server <NUM>, initiates a download procedure for an eSIM (profile) by sending a DownloadOrder message to the SM-DP+ server <NUM>. The DownloadOrder message can include a unique hardware identifier value, e.g., an eUICC <NUM> identifier (EID) value, for the UE <NUM> to which eSIM will be downloaded. In some embodiments, the DownloadOrder message does not include an EID value, as the EID value for the UE <NUM> may be unknown at the time of the submission of the DownloadOrder message to the SM-DP+ <NUM>. In some embodiments, the DownloadOrder message includes an eSIM identifier value, e.g., an ICCID value for the eSIM to the be downloaded to the UE <NUM>. In some embodiments, the DownloadOrder message does not include an ICCID value, and the SM-DP+ <NUM> selects an ICCID value to associate with a set of eSIMs for the UE <NUM>. The DownloadOrder message includes an eSIM type value that indicates that multiple eSIMs should be generated for the UE <NUM>. In some embodiments, the eSIM type value indicates that at least one eSIM of the multiple eSIMs should be compatible with a <NUM> capable UE <NUM>. At <NUM>, the SM-DP+ server <NUM> prepares multiple eSIMs, each eSIM using an identical ICCID value. The multiple eSIMs can correspond to different wireless communication capabilities of the UE <NUM>. The multiple eSIMs can include a set of common eSIM configuration data, such as one or more of ciphering keys, integrity keys, applets, elementary files, and/or dedicated files, for each of the eSIMs. In some embodiments, the multiple eSIMs include a first eSIM for a UE <NUM> that supports a <NUM> wireless communication protocol and a second eSIM for a UE <NUM> that does not support a <NUM> wireless communication protocol. In some embodiments, capability of the UE <NUM> to support a particular wireless communication protocol, such as a <NUM> protocol, is not available when the multiple eSIMs are generated by the SM-DP+ server <NUM>. In some embodiments, the multiple eSIMs include a first eSIM that includes <NUM> information and a second eSIM that excludes <NUM> information. In some embodiments, the <NUM> information includes file structures and/or applets specific to <NUM> wireless communication protocols. At <NUM>, the SM-DP+ server <NUM> provides a status message regarding the generation of the multiple eSIMs to the backend server <NUM>. At <NUM>, the backend server <NUM> requests confirmation of the previously requested download order for the eSIMs, which the SM-DP+ <NUM> confirms at <NUM>. Preparation of multiple eSIMs that each correspond to an identical ICCID value for future download to a wireless device, e.g., to UE <NUM>, can occur separate in time from the download process.

As previously illustrated in <FIG>, an eSIM download procedure begins with an authentication procedure between the eUICC <NUM> of the UE <NUM> and the SM-DP+ <NUM> facilitated by LPA <NUM> at <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>. The authentication procedure includes the LPA <NUM> providing eUICC information, e.g., eUICCInfo1obtained at <NUM>, to the SM-DP+ <NUM>, e.g., in the InitiateAuthentication message at <NUM>. The SM-DP+ server <NUM>, in some embodiments, can use the eUICC information, e.g., eUICCinfo1, at <NUM> to select an eSIM from the multiple eSIMs previously generated. In some embodiments, the eUICC information, e.g., eUICCinfo1, includes a specification version number (Svn) that can be used to indicate support for one or more wireless communication protocols. In some embodiments, the SM-DP+ server <NUM> can select an eSIM that supports <NUM> wireless communication protocols based on the eUICC information including an Svn value (or falling within a range of Svn values) that indicates (directly or indirectly) support for <NUM>. In some embodiments, the SM-DP+ server <NUM> selects an eSIM based on the eUICC information according to whether the UE <NUM> supports or does not support <NUM> wireless communication protocols. After selection of the eSIM based on the eUICC information, e.g., based on the Svn value in eUICCInfo1 at <NUM>, the SM-DP+ server <NUM>, at <NUM>, can discard the non-selected eSIMs that correspond to the identical ICCID value for the selected eSIM. In some embodiments, the SM-DP+ server <NUM> discards the non-selected eSIMs, at <NUM>, after the bound profile package that includes the selected eSIM for downloading to the UE <NUM> has been prepared. The download procedure continues as in <FIG> including authentication of the SM-DP+ server <NUM> by the UE <NUM>, authentication of the eUICC <NUM> by the SM-DP+ server <NUM>, preparation for download of the eSIM, and downloading of the eSIM in a bound profile package from the SM-DP+ server <NUM> to the eUICC <NUM> of the UE <NUM>.

<FIG> illustrates a diagram <NUM> of another exemplary message exchange for flexible eSIM deployment to a UE <NUM>. The procedure illustrated in <FIG> differs from that shown in <FIG> in that selection of the SIM from the multiple eSIMs occurs after (and/or during) authentication of the eUICC <NUM>. At <NUM>, the SM-DP+ server <NUM> selects an eSIM for download to the eUICC <NUM> of the UE <NUM> based on eUICC and device capability information reported in the AuthenticateClient message received at <NUM>, such as in eUICCinfo2 including in the AuthenticateClient message. In some embodiments, the eUICCinfo2 includes an Svn value that can indicate support for one or more wireless communication protocols. In some embodiments, the SM-DP+ server <NUM> can select an eSIM that supports <NUM> wireless communication protocols based on the eUICC information including an Svn value (or falling within a range of Svn values) that indicates (directly or indirectly) support for <NUM>. In some embodiments, the SM-DP+ server <NUM> selects an eSIM based on the eUICC information, eUICCinfo2, according to whether the UE <NUM> supports or does not support <NUM> wireless communication protocols. After selection of the eSIM based on the eUICC information, e.g., based on the Svn value in eUICCInfo2, the SM-DP+ server <NUM> discards non-selected eSIMs, e.g., at <NUM> after selection or at <NUM> after a bound profile package that includes the selected eSIM is prepared. The non-selected eSIMs can be discarded for security to protect against eSIM cloning.

<FIG> illustrates a flowchart <NUM> of an exemplary sequence of actions by a UE <NUM> for flexible provisioning of an eSIM to the UE <NUM>. At <NUM>, the UE <NUM> sends an authentication request to an MNO network-based server, e.g., SM-DP+ server <NUM>, where the authentication request includes one or more identifiers and/or capabilities of the UE <NUM>. In some embodiments, the authentication request includes a message to initiate mutual authentication between the UE <NUM> and the MNO network-based server. In some embodiments, the message includes information obtained from the eUICC <NUM> of the UE <NUM>. In some embodiments, the information includes a specification version number (Svn) indicating supported capabilities of the eUICC <NUM> and/or the UE <NUM>. In some embodiments, the authentication request includes a message to authenticate the UE <NUM> and/or eUICC <NUM> thereof with the MNO network-based server. In some embodiments, the message includes eUICC <NUM> capabilities and/or device capabilities information, e.g., specification version number (Svn) values and/or wireless communication protocol types supported by the UE <NUM> and/or by the eUICC <NUM>. In some embodiments, the message includes information to indicate whether the UE <NUM> and/or the eUICC <NUM> support a <NUM> wireless communication protocol. At <NUM>, the UE <NUM> receives from the MNO network-based server an eSIM selected from multiple eSIMs generated by the MNO network-based server based on an identical eSIM identifier value, where selection is based at least in part on the one or more identifiers and/or capabilities included in the authentication request. In some embodiments, each of the multiple eSIMs is generated based on an identical ICCID value. In some embodiments, each of the multiple eSIMs include a set of common eSIM configuration data, such as one or more of: such as ciphering keys, integrity keys, applets, elementary files, and/or dedicated files. In some embodiments, the multiple eSIMs include a first eSIM that supports a <NUM> wireless communication protocol and a second eSIM that does not support <NUM> wireless communication protocols. At <NUM>, the UE <NUM> loads the eSIM into the eUICC <NUM> of the UE <NUM>.

<FIG> illustrates a flowchart <NUM> of an exemplary sequence of actions by an MNO network-based server for flexible provisioning of an eSIM to a UE <NUM>. At <NUM>, the MNO network-based server, e.g., SM-DP+ server <NUM>, receives from an MNO backend server, e.g., an entitlement server, a message initiating a download order for an eSIM for a UE <NUM>. In some embodiments, the message includes a unique hardware identifier value for the UE <NUM>, e.g., an eUICC <NUM> identifier (EID) value. In some embodiments, the message excludes identifier values for a UE <NUM> and does not specify a particular UE <NUM>. In some embodiments, the message includes a unique eSIM identifier value, e.g., an ICCID value. In some embodiments, the message includes an eSIM type indication, e.g., a value for an eSIM type supported by the UE <NUM>. In some embodiments, the eSIM type indication includes a value that indicates whether the UE <NUM> supports a particular wireless communication protocol or range of wireless communication protocols. In some embodiments, the eSIM type indication includes a value that indicates whether the UE <NUM> supports a <NUM> wireless communication protocol. In some embodiments, the eSIM type indication includes a value that indicates multiple eSIMs should be generated for the UE <NUM>. At <NUM>, the MNO network-based server generates multiple eSIMs for the UE <NUM>, where the multiple eSIMs are based on an identical ICCID value, included in the download order message received from the backend server or generated separately by the MNO network-based server. In some embodiments, the multiple eSIMs each include a set of common eSIM configuration data, such as one or more of: ciphering keys, integrity keys, applets, elementary files, and/or dedicated files. In some embodiments, the multiple eSIMs include a first eSIM that supports a <NUM> wireless communication protocol and a second eSIM that does not support <NUM> wireless communication protocols. At <NUM>, the MNO network-based server receives from the UE <NUM> an authentication request that includes one or more identifiers and/or capabilities of the UE <NUM>. In some embodiments, the authentication request includes a message to initiate mutual authentication between the UE <NUM> and the MNO network-based server. In some embodiments, the message includes information from the eUICC <NUM> of the UE <NUM>. In some embodiments, the information includes a specification version number (Svn) indicating supported capabilities of the eUICC <NUM> and/or the UE <NUM>. In some embodiments, the authentication request includes a message to authenticate the UE <NUM> and/or eUICC <NUM> thereof with the MNO network-based server. In some embodiments, the message includes eUICC <NUM> capabilities and/or device capabilities information, e.g., specification version number (Svn) values and/or wireless communication protocol types supported by the UE <NUM> and/or by the eUICC <NUM>. In some embodiments, the message includes information to indicate whether the UE <NUM> and/or the eUICC <NUM> supports a <NUM> wireless communication protocol. At <NUM>, the MNO network-based server sends to the UE <NUM> an eSIM selected from the multiple eSIMs, where selection is based at least in part on the identifiers and/or capabilities for the UE <NUM> included in the authentication request. In some embodiments, the eSIM selected supports a <NUM> wireless communication protocol based on an indication from the UE <NUM> that the UE <NUM> supports the <NUM> wireless communication protocol. In some embodiments, the eSIM selected does not support a <NUM> wireless communication protocol based on an indication from the UE <NUM> that the UE <NUM> does not support the <NUM> wireless communication protocol. At <NUM>, the MNO network-based server discards non-selected eSIMs previously generated for the UE <NUM>. In some embodiments, the MNO network-based server discards the non-selected eSIMs after a bound profile package that includes the selected eSIM is generated.

<FIG> illustrates a detailed view of a representative computing device <NUM> that can be used to implement various methods described herein, according to some embodiments. In particular, the detailed view illustrates various components that can be included in the UE <NUM> illustrated in <FIG>. As shown in <FIG>, the computing device <NUM> can include a processor <NUM> that represents a microprocessor or controller for controlling the overall operation of computing device <NUM>. The computing device <NUM> can also include a user input device <NUM> that allows a user of the computing device <NUM> to interact with the computing device <NUM>. For example, the user input device <NUM> can take a variety of forms, such as a button, keypad, dial, touch screen, audio input interface, visual/image capture input interface, input in the form of sensor data, etc. Still further, the computing device <NUM> can include a display <NUM> that can be controlled by the processor <NUM> to display information to the user. A data bus <NUM> can facilitate data transfer between at least a storage device <NUM>, the processor <NUM>, and a controller <NUM>. The controller <NUM> can be used to interface with and control different equipment through and equipment control bus <NUM>. The computing device <NUM> can also include a network/bus interface <NUM> that couples to a data link <NUM>. In the case of a wireless connection, the network/bus interface <NUM> can include a wireless transceiver.

The computing device <NUM> also includes a storage device <NUM>, which can comprise a single disk or a plurality of disks (e.g., hard drives), and includes a storage management module that manages one or more partitions within the storage device <NUM>. In some embodiments, storage device <NUM> can include flash memory, semiconductor (solid state) memory or the like. The computing device <NUM> can also include a Random Access Memory (RAM) <NUM> and a Read-Only Memory (ROM) <NUM>. The ROM <NUM> can store programs, utilities or processes to be executed in a non-volatile manner. The RAM <NUM> can provide volatile data storage, and stores instructions related to the operation of the computing device <NUM>. The computing device <NUM> can further include a secure element (SE) <NUM>, which can represent an eUICC <NUM> of the UE <NUM>.

In some embodiments, a method for flexible deployment of eSIMs <NUM> to a wireless device, e.g., UE <NUM>, includes the wireless device: i) sending, to an MNO network-based server, e.g., SM-DP+ <NUM> server, an authentication request including one or more identifiers and/or capabilities of the wireless device; ii) receiving, from the MNO network-based server, an eSIM <NUM> selected from multiple eSIMs <NUM> based on the one or more identifiers and/or capabilities of the wireless device, wherein the multiple eSIMs <NUM> are generated by the MNO network-based server based on an identical eSIM identifier value and include a set of common eSIM configuration data; and iii) loading the eSIM <NUM> into an eUICC <NUM> of the wireless device.

In some embodiments, the authentication request includes a message to initiate mutual authentication between the wireless device and the MNO network-based server. In some embodiments, the message includes information obtained from the eUICC <NUM> of the wireless device. In some embodiments, the information includes a specification version number (Svn) indicating supported capabilities of the eUICC <NUM> and/or the wireless device. In some embodiments, the authentication request includes a second message to authenticate the wireless device and/or the eUICC <NUM> with the MNO network-based server. In some embodiments, the second message includes eUICC <NUM> and/or wireless device capabilities information that specifies one or more wireless communication protocols and/or protocol types supported by the eUICC <NUM> and/or wireless device. In some embodiments, the authentication request includes information to indicate whether the wireless device and/or the eUICC <NUM> support a <NUM> wireless communication protocol. In some embodiments, selection of the eSIM <NUM> is based at least in part on whether the wireless device and/or the eUICC <NUM> support the <NUM> wireless communication protocol. In some embodiments, the identical eSIM <NUM> identifier value includes an ICCID value. In some embodiments, the multiple eSIMs <NUM> include a first eSIM208 that supports a <NUM> wireless communication protocol and a second eSIM <NUM> that does not support <NUM> wireless communication protocols. In some embodiments, the MNO network-based server includes an SM-DP+ <NUM> server. In some embodiments, the set of common eSIM <NUM> configuration data includes one or more of: ciphering keys, integrity keys, applets, elementary files, and/or dedicated files.

In some embodiments, a method for flexible deployment of eSIMs <NUM> to a wireless device, e.g., UE <NUM>, includes an MNO network-based server, e.g., SM-DP+ <NUM>: i) receiving, from a backend server <NUM>, a message to initiate a download order for an eSIM <NUM> for a wireless device; ii) generating, for the wireless device, multiple eSIMs <NUM> based on an identical eSIM <NUM> identifier value, wherein the multiple eSIMs <NUM> each include a set of common eSIM <NUM> configuration data; iii) receiving, from the wireless device, an authentication request including one or more identifiers and/or capabilities of the wireless device; iv) sending, to the wireless device, an eSIM <NUM> selected from the multiple eSIMs <NUM> based on the one or more identifiers and/or capabilities of the wireless device; and v) discarding remaining non-selected eSIMs <NUM> of multiple eSIMs <NUM> generated for the wireless device.

In some embodiments, the message includes one or more of: a unique hardware identifier value for the wireless device, a unique eSIM <NUM> identifier value, or an eSIM <NUM> type indication. In some embodiments, the unique hardware identifier value includes an EID value of the wireless device. In some embodiments, the unique eSIM <NUM> identifier value includes an ICCID value. In some embodiments, the eSIM <NUM> type indication includes a value that indicates whether the wireless device supports a particular wireless communication protocol. In some embodiments, the particular wireless communication protocol includes a <NUM> wireless communication protocol. In some embodiments, the eSIM <NUM> type indication includes a value that indicates the multiple eSIMs <NUM> for the wireless device should be generated. In some embodiments, the identical eSIM <NUM> identifier value includes an ICCID value included in the message received from the backend server <NUM>. In some embodiments, the identical eSIM <NUM> identifier value includes an ICCID value generated by the MNO network-based server. In some embodiments, the multiple eSIMs <NUM> comprise a first eSIM <NUM> that supports a <NUM> wireless communication protocol and a second eSIM <NUM> that does not support <NUM> wireless communication protocols. In some embodiments, the authentication request includes a message to initiate mutual authentication between the wireless device and the MNO network-based server. In some embodiments, the message includes a specification version number (Svn) indicating supported capabilities of an eUICC <NUM> of the wireless device and/or supported capabilities of the wireless device. In some embodiments, the authentication request includes a second message to authenticate the wireless device and/or the eUICC <NUM> with the MNO network-based server. In some embodiments, the second message includes eUICC <NUM> and/or wireless device capability information that specifies one or more wireless communication protocols and/or protocol types supported by the eUICC <NUM> and/or wireless device. In some embodiments, the authentication request includes information to indicate whether the wireless device and/or the eUICC <NUM> support a <NUM> wireless communication protocol. In some embodiments, selection of the eSIM <NUM> is based at least in part on whether the wireless device and/or the eUICC <NUM> support the <NUM> wireless communication protocol. In some embodiments, the MNO network-based server includes an SM-DP+ <NUM> server. In some embodiments, the set of common eSIM configuration data includes one or more of: ciphering keys, integrity keys, applets, elementary files, and/or dedicated files.

In some embodiments, a wireless device, e.g., UE <NUM>, includes one or more antennas, and at least one processor communicatively coupled to the one or more antennas and to a memory storing instructions that, when executed by the at least one processor, cause the wireless device to perform a method as described herein.

In some embodiments, an apparatus configured for operation in a wireless device, e.g., UE <NUM>, includes at least one processor communicatively coupled to a memory storing instructions that, when executed by the at least one processor, cause the wireless device to perform a method as described herein.

In some embodiments, an MNO network-based server configured for flexible deployment of eSIMs <NUM> to a wireless device, e.g., UE <NUM>, includes at least one communication interface for communicating with the wireless device; and at least one processor communicatively coupled to a memory storing instructions that, when executed by the at least one processor, cause the MNO network-based server to perform a method as described herein.

In accordance with various embodiments described herein, the terms "wireless communication device," "wireless device," "mobile device," "mobile station," and "user equipment" (UE) may be used interchangeably herein to describe one, or any number of, common consumer electronic device(s) that may be capable of performing procedures associated various embodiments the disclosure. In accordance with various implementations, any one of these consumer electronic devices may relate to: a cellular phone or a smart phone, a tablet computer, a laptop computer or a netbook computer, a media player device, an electronic book device, a MiFi® device, a wearable computing device, as well as any other type of electronic computing device having fourth generation (<NUM>) Long Term Evolution (LTE) and LTE Advanced (LTE-A), fifth generation (<NUM>) new radio (NR), or similar "later generation" cellular wireless access communication capabilities.

Additionally, it should be understood that the UEs described herein may be configured as multi-mode wireless devices that are also capable of communicating via legacy third generation (<NUM>) and/or second generation (<NUM>) RATs in addition to communicating with <NUM> wireless networks, as well as communicating using one or more different wireless local area networks. Multi-mode UEs can include support for communication in accordance with one or more different wireless communication protocols developed by standards bodies, e.g., 3GPP's Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), LTE, LTE-A, and <NUM> NR standards or 3GPP2's CDMA2000 (1xRTT, 2xEV-DO, HRPD, eHRPD) standards. Multi-mode UEs can also support communication using wireless local area networking protocols, e.g., the Institute of Electrical and Electronics Engineers (IEEE) <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), and wireless personal area networking protocols, e.g., Bluetooth®. Multiple wireless communication protocols can provide complementary functions and/or different services for a multi-mode UE.

The various aspects, embodiments, implementations or features of the described embodiments can be used separately or in any combination. Further, some aspects of the described embodiments may be implemented by software, hardware, or by a combination of hardware and software. The described embodiments can also be embodied as computer program code stored on a non-transitory computer-readable medium. The computer readable-medium may be associated with any data storage device that can store data, which can thereafter be read by a computer or a computer system. Examples of the computer-readable medium include read-only memory, random-access memory, CD-ROMs, Solid-State Disks (SSD or Flash), HDDs, DVDs, magnetic tape, and optical data storage devices. The computer-readable medium can also be distributed over network-coupled computer systems so that the computer program code may be executed in a distributed fashion.

Claim 1:
A mobile network operator, MNO, network-based server configured for flexible deployment of electronic subscriber identity modules, eSIMs (<NUM>), to a wireless device, the MNO network-based server comprising:
at least one communication interface for communicating with the wireless device; and
at least one processor communicatively coupled to a memory storing instructions that, when executed by the at least one processor, cause the MNO network-based server to perform a method that includes:
receiving, from a backend server (<NUM>), a message to initiate a download order for an eSIM (<NUM>) for the wireless device, the message including an eSIM type value indicating multiple eSIMs (<NUM>) are to be generated for the wireless device;
generating, for the wireless device, multiple eSIMs (<NUM>), wherein:
each eSIM (<NUM>) of the multiple eSIMs (<NUM>) includes an identical eSIM identifier value and a set of common eSIM configuration data;
at least one eSIM of the multiple eSIMs (<NUM>) supports a fifth generation, <NUM>, wireless communication protocol; and
at least one eSIM of the multiple eSIMs (<NUM>) does not support a <NUM> wireless communication protocol;
receiving, from the wireless device, an authentication request including one or more identifiers and/or capabilities of the wireless device;
sending, to the wireless device, an eSIM selected from the multiple eSIMs (<NUM>) based on the one or more identifiers and/or capabilities of the wireless device; and
discarding remaining non-selected eSIMs of multiple eSIMs (<NUM>) generated for the wireless device.