Patent Description:
Remote SIM provisioning (RSP; where SIM is short for subscriber identity module) for consumer devices is described in "<NPL>. According to this document, firstly, the subscriber makes a contract with a mobile network operator (MNO). Secondly, the MNO orders a profile for the subscriber entity from a server (enhanced Subscription Manager Data Preparation (SM-DP+) server), and the SM-DP+ creates the profile and returns to the MNO a pointer to the profile. Thirdly, the MNO delivers the pointer for download initialization of the profile to the subscriber. Fourthly, the profile is downloaded from the SM-DP+ to the embedded universal integrated circuit card (eUICC) in the communication device to be provisioned. Section <NUM> of the aforementioned document describes the profile download initiation process. It indicates how the user orders a subscription from the MNO. Request/response methods are used for the MNO to request the SM-DP+ to create a SIM profile. The profile is then stored securely in the SM-DP+. After profile creation, the subscriber entity can download the created profile by contacting the SM-DP+ using the communication device.

In general terms, the profile is a data package that contains MNO specific parameters and credentials that allow the communication device to access the network of the MNO after download of the profile. The structure of the data package may follow either a standardized or a proprietary format. The profile is prepared and created for an eUICC upon the SM-DP+ receives the profile order from the MNO. The MNO may know the capabilities of the eUICC at the profile order time or the MNO may order the SM-DP+ to create a generic profile without having access to information of the eUICC capabilities. The latter could represent a scenario where a batch of profiles is ordered for prepaid subscriptions, where the target communication devices are not be known in advance.

An MNO without knowing the capabilities of the eUICC may thereby order an incompatible profile from the SM-DP+. The capabilities of an eUICC may differ from one eUICC to another eUICC. For example, there are different versions of the GSMA specifications, there are different versions of the eUICC, and there are different versions of the specified profile package formats. All of these factors may impact the profile content. Thus, one profile type may not be suitable for all communication devices. The same applies not only to prepaid subscriptions, but for all subscriptions. When an MNO sells a subscription, the MNO will need to ask from the subscriber the make, model, age of the communication device in order to allocate the correct profile type. This manual process is error prone, and subscribers might provide incorrect information to the MNO by accident or by purpose.

<CIT> discloses a method of adaptive generation of a profile package, said profile package being constructed to, when being downloaded to an eUICC and installed in the eUICC, install a profile in the eUICC.

<CIT> discloses a technique for operating an RSP node, which is configured for remote subscriber identity module, SIM, provisioning.

Hence, there is still a need for improved handling of subscription profiles for eUICCs and other types of subscriber entities.

An object of embodiments herein is to provide less complex creation of subscription profiles that in turn enables efficient handling of subscription profiles for eUICCs and other types of subscriber entities.

According to a first aspect there is presented a method for creating a subscription profile for a subscriber entity, according to claim <NUM>. The method is performed by a subscription provisioning server. The method comprises obtaining, from the subscriber entity, a request for download of the subscription profile. The request comprises capability information of the subscriber entity. The method comprises creating the subscription profile based on the capability information as obtained from the subscriber entity. According to a second aspect there is presented a subscription provisioning server for creating a subscription profile for a subscriber entity, according to the independent claim <NUM>. The subscription provisioning server comprises processing circuitry. The processing circuitry is configured to cause the subscription provisioning server to obtain, from the subscriber entity, a request for download of the subscription profile. The request comprises capability information of the subscriber entity. The processing circuitry is configured to cause the subscription provisioning server to create the subscription profile based on the capability information of the subscriber entity.

Advantageously, these aspects enable efficient handling of subscription profiles for eUICCs and other types of subscriber entities.

Advantageously, these aspects alleviate the need for the mobile network operator to order a specific type of a profile, or batch of profiles, for subscriber entities in devices that are not necessarily known yet (e.g. having prepaid subscriptions). Instead, the mobile network operator might define rules based on which the subscription provisioning server could automatically select the best suited profile type based on the information directly provided by the subscriber entities.

Advantageously, these aspects eliminate errors occurring when the profile type is allocated for a specific type of subscriber entities.

Advantageously, these aspects enable automatic profile selection for a batch of subscriber entities. This is especially advantageous when the subscriber entities are part of, integrated in, or provided in, Internet of Things devices, such as narrowband Internet of Things devices.

The wording that a certain data item or piece of information is obtained by a first device should be construed as that data item or piece of information being retrieved, fetched, received, or otherwise made available to the first device. For example, the data item or piece of information might either be pushed to the first device from a second device or pulled by the first device from a second device. Further, in order for the first device to obtain the data item or piece of information, the first device might be configured to perform a series of operations, possible including interaction with the second device. Such operations, or interactions, might involve a message exchange comprising any of a request message for the data item or piece of information, a response message comprising the data item or piece of information, and an acknowledge message of the data item or piece of information. The request message might be omitted if the data item or piece of information is neither explicitly nor implicitly requested by the first device.

The wording that a certain data item or piece of information is provided by a first device to a second device should be construed as that data item or piece of information being sent or otherwise made available to the second device by the first device. For example, the data item or piece of information might either be pushed to the second device from the first device or pulled by the second device from the second device. Further, in order for the first device to provide the data item or piece of information to the second device, the first device and the second device might be configured to perform a series of operations in order to interact with each other. Such operations, or interaction, might involve a message exchange comprising any of a request message for the data item or piece of information, a response message comprising the data item or piece of information, and an acknowledge message of the data item or piece of information. The request message might be omitted if the data item or piece of information is neither explicitly nor implicitly requested by the second device.

<FIG> is a schematic diagram illustrating a communication network <NUM> where embodiments presented herein can be applied. The communication network <NUM> comprises a radio access network <NUM>, and a combined core and service network <NUM>. In turn, the radio access network <NUM> comprises a radio access network node <NUM> and the combined core and service network <NUM> comprises a subscription provisioning server <NUM> and an MNO entity <NUM>. In some examples the subscription provisioning server <NUM> is an SM-DP+ entity (or just SM-DP+ for short). The radio access network node <NUM> is configured to provide network access to, and thus to serve, wireless terminal devices <NUM>, such as a user equipment (UE), network equipped vehicle, network equipped sensor, a so-called Internet of Things (IoT) device, or the like. Each wireless terminal device <NUM> comprises a respective subscriber entity <NUM>. In some examples the subscriber entity <NUM> is an eUICC entity (or just eUICC for short), an integrated Universal Integrated Circuit Card (iUICC) entity (or just iUICC for short), a European Telecommunications Standards Institute Smart Secure Platform (ETSI SSP). Thus, although the eUICC will be used below to represent the subscriber entity <NUM>, the eUICC might be an iUICC or an ETSI SSP.

As the skilled person understands, the radio access network <NUM> as well as the combined core and service network <NUM> might comprise a plurality of functions, nodes, devices, and entities for facilitating communication between the wireless terminal devices <NUM> and the combined core and service network <NUM>. Functions, nodes, devices, and entities not relevant for the herein disclosed embodiments have been omitted for brevity.

As noted above, there is still a need for improved handling of subscription profiles for eUICCs <NUM> and other types of subscriber entities.

In particular, the SM-DP+ <NUM> performs an eligibility check of the eUICC <NUM> at the time download of the subscription profile is requested by the eUICC <NUM>, whilst the subscription profile is prepared and created already at the subscription profile order time. To further illustrate this, reference is now made to <FIG> is a signalling diagram of a method for subscription profiler order and eligibility check according to state of the art.

S301: The user orders a subscription from the MNO entity <NUM>.

S302: The MNO entity <NUM> sends an order for a subscription profile in an ES2+. downloadOrder message for the SM-DP+ <NUM> to prepare a subscription profile and defines the subscription profile type in standard way.

S303: The SM-DP+ <NUM> generates, stores and returns Authentication Vector (AV) data to the MNO entity <NUM> in an ES2+ downloadOrderResp message, and also creates the subscription profile. The AV data might comprise e.g. international mobile subscriber identity (IMSI), Integrated Circuit Card Identifier (ICCID; i.e., an identifier of the eUICC <NUM>), individual subscriber authentication key (Ki), and/or other subscriber specific data elements.

S304: The MNO entity <NUM> responds with an ES2+ confirmOrderReq message to the SM-DP+ <NUM>, where the message according to the aforementioned SGP. <NUM> specification. This message can use any of the mechanisms supported by the SGP. <NUM> specification, for example use MatchingID, or register the event based on the requestor's EID to a subscription server, such as a Subscription Manager - Discovery Server (SM-DS).

S305: The SM-DP+ <NUM> responds with an ES2+ confirmOrderResp message to the MNO entity <NUM>, where the message comprises a pointer to the created subscription profile, according to the aforementioned SGP. <NUM> specification.

S306: The MNO entity <NUM> delivers the pointer for download initialization of the subscription profile to the user, or the subscriber entity connects to the subscription server or a default-SM-DP+ <NUM>.

S307: The subscriber entity request download of the subscription profile by providing the pointer and eligibility check information to the SM-DP+ <NUM> in an ES9+ getBoundSubscription profilePackage message. When the SM-DP+ <NUM> receives this message the SM-DP+ <NUM> will perform an eligibility check and only allow download of the created subscription profile if the eligibility check is successful.

S308: The SM-DP+ <NUM> enables download of the created subscription profile to the subscriber entity in a bounded subscription profile package.

When the eUICC <NUM> triggers download of the subscription profile from the SM-DP+ <NUM>, the eUICC <NUM> and the SM-DP+ <NUM> both establish a secure, mutually authenticated, communication channel and the subscription profile is delivered to the eUICC <NUM> over this communication channel. During the download procedure for the subscription profile, the eUICC <NUM> delivers the capabilities of the eUICC <NUM> to the SM-DP+ <NUM>. These capabilities include a set of supported features of the eUICC <NUM>, e.g., supported Remote SIM Provisioning (RSP; where SIM is short for subscriber identity module or subscriber identification module) version, supported subscription profile type, supported network type, International Mobile Equipment Identity (IMEI) and supported subscription profile size. The SM-DP+ <NUM> uses the capabilities information to perform an eligibility check i.e., whether the eUICC <NUM> will support the subscription profile prepared for this eUICC <NUM>. If the eUICC <NUM> does not support the prepared subscription profile, the SM-DP+ <NUM> may reject the download of the subscription profile. This may result in a bad user experience.

The embodiments disclosed herein therefore relate to mechanisms for creating a subscription profile for a subscriber entity <NUM> and ordering a subscription profile for a subscriber entity <NUM>. In order to obtain such mechanisms there is provided a subscription provisioning server <NUM>, a method performed by the subscription provisioning server <NUM>, a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the subscription provisioning server <NUM>, causes the subscription provisioning server <NUM> to perform the method. In order to obtain such mechanisms there is further provided a mobile network operator entity <NUM>, a method performed by the mobile network operator entity <NUM>, and a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the mobile network operator entity <NUM>, causes the mobile network operator entity <NUM> to perform the method.

Reference is now made to <FIG> illustrating a method for creating a subscription profile for a subscriber entity <NUM> as performed by the subscription provisioning server <NUM> according to an embodiment.

It is assumed that a subscription profile is to be created for the subscriber entity <NUM>. The creation is triggered by the subscription provisioning server <NUM> obtaining a request for download of the subscription profile from the subscriber entity <NUM>. Hence, the subscription provisioning server is configured to perform step S106:
S106: The subscription provisioning server <NUM> obtains, from the subscriber entity <NUM>, a request for download of the subscription profile. The request comprises capability information of the subscriber entity <NUM>.

According to the herein disclosed embodiments, the subscription profile is created at the eligibility check time. Hence, the subscription provisioning server <NUM> is configured to perform step S112:
S112: The subscription provisioning server <NUM> creates the subscription profile based on the capability information as obtained from the subscriber entity <NUM>.

This method enables the number of rejected subscription profiles due to mismatch between prepared subscription profiles and eligibility check information of the subscriber entity to be reduced. This in turn will reduce network resource usage and also improve the user experience.

Embodiments relating to further details of creating a subscription profile for a subscriber entity <NUM> as performed by the subscription provisioning server <NUM> will now be disclosed.

In some aspects, the request for download of the subscription profile is preceded by an order for creating the subscription profile from the mobile network operator entity <NUM>. Hence, in some embodiments, the subscription provisioning server <NUM> is configured to perform (optional) step S102:
S102: The subscription provisioning server <NUM> obtains, from a mobile network operator entity <NUM>, an order for creating the subscription profile for the subscriber entity <NUM>.

The order in step S102 is received before the request in step S108 is received.

The order might either pertain to only one single subscription profile to be created for only one single subscriber entity <NUM> or pertain to a batch of subscription profiles to be created for a batch of subscriber entities <NUM>.

In some aspects, reception of the order for creating the subscription profile triggers the subscription provisioning server <NUM> to create provisioning data for the subscription profile. Hence, in some embodiments, the subscription provisioning server <NUM> is configured to perform (optional) step S104:
S104: The subscription provisioning server <NUM> creates provisioning data for the subscription profile only upon having obtained the order for creating the subscription profile for the subscriber entity <NUM>.

In other aspects, the provisioning data for the subscription profile is by the subscription provisioning server <NUM> created offline an in advance of receiving the order for creating the subscription profile for the subscriber entity <NUM>. In any case, the provisioning data can then be used for creating the subscription profile, for example by inserting the provisioning data to an appropriate subscription profile template.

There could be different ways in which the subscription provisioning server <NUM> creates the subscription profile. In some aspects, how the subscription profile is dependent on what information is provided in the order as received from the mobile network operator entity <NUM> in step S102.

According to some aspects, the subscription profile is created according to a subscription profile type specified in the order. That is, in some embodiments, the order comprises a subscription profile type, and the subscription profile is created in accordance with the subscription profile type. In other aspects, the subscription profile is created according to a rule set or an indication to such a rule set. In particular, in some embodiments, the order comprises a set of rules, or an indication to the set of rules, where the set of rules pertains to according to which subscription profile type the subscription profile is to be created for the subscriber entity <NUM>. The subscription profile is then created in accordance with the capability information of the subscriber entity <NUM> (and the provisioning data) in combination with either the set of rules or the indication to the set of rules.

In some embodiments, the subscription profile, prior to being created, is selected in accordance with the capability information of the subscriber entity <NUM> in combination with either the set of rules or the indication to the set of rules. According to some aspects, the subscription profile is selected from one or more available subscription profile types. There might be different ways to select the subscription profile from these one or more available subscription profile types. In some embodiments, the subscription profile type is selected from a set of subscription profile templates in accordance with the set of rules, or the indication to the set of rules. In some embodiments, the subscription profile type further is selected based on information obtained from the mobile network operator entity <NUM> in the order. In some embodiments, the subscription profile type is selected by the subscription provisioning server <NUM> providing data to a subscription profile selection entity and receiving a subscription profile specification in return from the subscription profile selection entity, and where the subscription profile is created according to the subscription profile specification.

In some aspects, the mobile network operator entity <NUM> is notified about the subscription type selected for creating the subscription profile. In particular, in some embodiments, the subscription provisioning server <NUM> is configured to perform (optional) step S110:
S110: The subscription provisioning server <NUM> provides an indication to the mobile network operator entity <NUM>, the indication specifying a subscription type according to which the subscription profile was selected.

Step S110 is performed before, or in conjunction with, the creation of the subscription profile in step S112. Further details of how the subscription provisioning server <NUM> might provide the indication to the mobile network operator entity <NUM> will be disclosed below with reference to <FIG>.

In further embodiments, the order specifies how the subscription profile type is to be selected. Step S110 needs then not to be performed. Neither does step S110 needs to be performed in case the subscription profile selection entity is operated, or controlled by, the mobile network operator entity <NUM>.

In some aspects, a verification is made that it indeed is possible to create a subscription profile for the subscriber entity <NUM>. In particular, in some embodiments, the subscription provisioning server <NUM> is configured to perform step S108:
S108: The subscription provisioning server <NUM> verifies that the subscriber entity <NUM> passes an eligibility check before, or as part of, creating the subscription profile. The eligibility check is based on the capability information of the subscriber entity <NUM>. The eligibility test pertains to whether the subscriber entity <NUM> will support the subscription profile or not.

Step S108 is performed before, or in conjunction with, step S112. Further aspects of how the subscription provisioning server <NUM> might verify that the subscriber entity <NUM> passes the eligibility check will be disclosed below with reference to <FIG>.

Once the subscription profile has been created (and has been successfully passed the eligibility check) the subscription profile can be downloaded to the subscriber entity <NUM>. Hence, in some embodiments, the subscription provisioning server <NUM> is configured to perform (optional) step S114:
S114: The subscription provisioning server <NUM> enables download of the created subscription profile to the subscriber entity <NUM>.

Reference is now made to <FIG> illustrating a method for ordering a subscription profile for a subscriber entity <NUM> as performed by the mobile network operator entity <NUM> according to an example useful for understanding the invention.

As disclosed above, the subscription provisioning server <NUM> might receive an order from the mobile network operator entity <NUM> for creating the subscription profile for the subscriber entity <NUM>. In particular, the mobile network operator entity <NUM> is configured to perform step S202.

S202: The mobile network operator entity <NUM> provides, to the subscription provisioning server <NUM>, an order for creating the subscription profile for the subscriber entity <NUM>. The order comprises a set of rules, or an indication to the set of rules. The set of rules pertains to which types of subscription profile is to be created for the subscriber entity <NUM>.

Embodiments relating to further details of ordering a subscription profile for a subscriber entity <NUM> as performed by the mobile network operator entity <NUM> will now be disclosed.

As disclosed above, the order might either pertain to only one single subscription profile to be created for only one single subscriber entity <NUM> or pertain to a batch of subscription profiles to be created for a batch of subscriber entities <NUM>.

As disclosed above, in some aspects, the mobile network operator entity <NUM> is notified about the subscription type selected for creating the subscription profile. In particular, in some embodiments, the mobile network operator entity <NUM> is configured to perform (optional) step S204:
S204: The mobile network operator entity <NUM> obtains an indication from a subscription provisioning server <NUM>, the indication specifying a subscription type according to which the subscription profile was created by the subscription provisioning server <NUM>.

A first particular embodiment for ordering a subscription profile for a subscriber entity <NUM> and for creating a subscription profile for the subscriber entity <NUM> based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram <FIG>.

S401: The user orders a subscription from the MNO entity <NUM>.

S402: The MNO entity <NUM> sends an order for a subscription profile in an ES2+. downloadOrder message for the SM-DP+ <NUM> to prepare a subscription profile and has the choice to either define the subscription profile type in standard way or indicate to the SM-DP+ <NUM> to select the subscription profile (either by the SM-DP+ <NUM> itself or by a separate selection function). In the latter case, the MNO entity <NUM> might either provide an indication to a set of rules, which (previously defined) ruleset will be used for subscription profile selection, or provide the set of rules (i.e. including the actual rules, based on which the subscription profile selection is automatically performed).

S403, S404: The SM-DP+ <NUM> generates, stores and returns AV data to the MNO entity <NUM> in an ES2+ downloadOrderResp message, but does not yet create the subscription profile. The AV data might comprise e.g. IMSI, ICCID, Ki, and/or other subscriber specific data elements.

S405: The MNO entity <NUM> responds with an ES2+ confirmOrderReq message to the SM-DP+ <NUM>, where the ES2+ confirmOrderReq message is defined as in the aforementioned SGP. <NUM> specification.

S406: The SM-DP+ <NUM> responds with an ES2+ confirmOrderResp message to the MNO entity <NUM>, where the message comprises a pointer to the yet not created subscription profile and otherwise is defined as in the aforementioned SGP. <NUM> specification.

S407: The MNO entity <NUM> delivers the pointer for download initialization of the subscription profile to the user.

S408, S409: The subscriber entity requests download of the subscription profile by providing the pointer and eligibility check information to the SM-DP+ <NUM> in an ES9+ getBoundSubscription profilePackage message. When the SM-DP+ <NUM> receives this message the SM-DP+ <NUM> will perform an eligibility check and only proceed with creating the actual subscription profile if the eligibility check is successful. The SM-DP+ <NUM> will then, if the subscription profile type was defined in the download order, create and provide the subscription profile to the eUICC <NUM>. If the subscription profile type was not defined, but either the set of rules or an indication to the set of rules was provided in step S402, the SM-DP+ <NUM> interprets the eligibility check information as subscription profile property requirements, and processes the rules, as will be more disclosed in detail below. By processing the rules, the SM-DP+ <NUM> selects the correct subscription profile type and creates the subscription profile. If no match for the rules is found in the subscription profile type inventory, the SM-DP+ <NUM> might try to use a default subscription profile type as template when creating the subscription profile.

S410: Optionally, for example when either the set of rules or an indication to the set of rules was provided in step S402, the SM-DP+ <NUM> provides information of the thus created subscription profile to the MNO entity <NUM> in an ES2+ notify subscription profile type message.

S411: The SM-DP+ <NUM> enables download of the thus created subscription profile to the subscriber entity in a bounded subscription profile package.

A second particular embodiment for ordering a subscription profile for a subscriber entity <NUM> and for creating a subscription profile for the subscriber entity <NUM> based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram of <FIG>. In comparison to <FIG>, there is in <FIG> an alternative location for the subscription profile type selection. In the example of <FIG>, this function is run by the MNO, which would receive the eligibility check information from the SM-DP+ <NUM> and based on that return information of which subscription profile to select, or whether to deny subscription profile download on e.g. EIR or other blacklisting mechanism.

S501: The user orders a subscription from the MNO entity <NUM>.

S502: The MNO entity <NUM> sends an order for a subscription profile in an ES2+. downloadOrder message for the SM-DP+ <NUM> to prepare a subscription profile and has the choice to either define the subscription profile type in standard way or indicate to the SM-DP+ <NUM> to select the subscription profile (either by the SM-DP+ <NUM> itself or by a separate selection function). In the latter case, the MNO entity <NUM> might either provide an indication to a set of rules, which (previously defined) ruleset will be used for subscription profile selection, or provide the set of rules (i.e. including the actual rules, based on which the subscription profile selection is automatically performed).

S503: The SM-DP+ <NUM> generates, stores and returns AV data to the MNO entity <NUM> in an ES2+ downloadOrderResp message, but does not yet create the subscription profile. The AV data might comprise e.g. IMSI, ICCID, Ki, and/or other subscriber specific data elements.

S504: The MNO entity <NUM> responds with an ES2+ confirmOrderReq message to the SM-DP+ <NUM>, where the message is defined as in the aforementioned SGP. <NUM> specification.

S505: The SM-DP+ <NUM> responds with an ES2+ confirmOrderResp message to the MNO entity <NUM>, where the message comprises a pointer to the yet not created subscription profile and otherwise is defined as in the aforementioned SGP. <NUM> specification.

S506: The MNO entity <NUM> delivers the pointer for download initialization of the subscription profile to the user.

S507: The subscriber entity request download of the subscription profile by providing the pointer and eligibility check information to the SM-DP+ <NUM> in an ES9+ getBoundSubscription profilePackage message. When the SM-DP+ <NUM> receives this message the SM-DP+ <NUM> will perform an eligibility check and only proceed with creating the actual subscription profile if the eligibility check is successful.

Assume that either the set of rules or an indication to the set of rules was provided in step S502. The SM-DP+ <NUM> interprets the eligibility check information as subscription profile property requirements, and processes the rules, as will be more disclosed in detail below. By processing the rules, the SM-DP+ <NUM> selects the correct subscription profile type and creates the subscription profile. If no match for the rules is found in the subscription profile type inventory, the SM-DP+ <NUM> might try to use a default subscription profile type as template when creating the subscription profile.

S508: The SM-DP+ <NUM> provides the eligibility check information to a subscription profile selection entity, which then selects a subscription profile type by interpreting the eligibility check information as subscription profile property requirements. The eligibility check information might be provided in an ES2+ Parsed Eligibility Info message.

S509: The SM-DP+ <NUM> obtains the thus selected subscription profile type from the subscription profile selection entity. The subscription profile type might be obtained in an ES2+ Define Subscription profile Type message.

S510: The SM-DP+ <NUM> creates the subscription profile based on the obtained subscription profile type and any other available information.

S511: The SM-DP+ <NUM> enables download of the thus created subscription profile to the subscriber entity in a bounded subscription profile package.

Reference is now made to the flowchart of <FIG> that shows an example of subscription profile selection according to embodiments disclosed herein.

S601: The SM-DP+ <NUM> obtain an order for a subscription profile from the MNO entity <NUM>.

S602: The SM-DP+ <NUM> checks whether the subscriber entity for which the subscription profile is ordered is any of blacklisted or incompatible, or not. Step S603 is entered when the subscriber entity is neither blacklisted nor incompatible. Step S611 is entered when the subscriber entity is blacklisted and/or incompatible.

S603: The SM-DP+ <NUM> checks whether the subscription profile type is explicitly set in the order or not. Step S609 is entered when the subscription profile type is explicitly set in the order. Step S604 is entered when the subscription profile type is not explicitly set in the order.

S604: The SM-DP+ <NUM> checks whether the subscription profile type can be selected using a TAC value or not. Step S609 is entered when the subscription profile type can be selected using a TAC value. Step S605 is entered when the subscription profile type cannot be selected using a TAC value.

S605: The SM-DP+ <NUM> interprets the eUICC information as subscription profile property requirements.

S606: The SM-DP+ <NUM> checks whether the subscription profile property requirements match any subscription profile template in an inventory of template subscription profile types or not. Step S609 is entered when the subscription profile property requirements match a subscription profile template. Step S607 is entered when the subscription profile property requirements do not match a subscription profile template.

S607: The SM-DP+ <NUM> checks whether it is possible to use a default template to create the subscription profile or not. Step S609 is entered it is possible to use a default template to create the subscription profile. Step S608 is entered when it is not possible to use a default template to create the subscription profile.

S608: The eligibility check for the subscriber entity has failed since no compatible subscription profile type can be found. The SM-DP+ <NUM> can thus not create any subscription profile for the subscriber entity.

S609: The SM-DP+ <NUM> creates a subscription profile for the subscriber entity based on the selected subscription profile type.

S610: The SM-DP+ <NUM> allows download of the thus created subscription profile to the subscriber entity.

S611: The eligibility check for the subscriber entity has failed since the subscriber entity is blacklisted and/or incompatible. The SM-DP+ <NUM> can thus not create any subscription profile for the subscriber entity.

As noted above, the SM-DP+ <NUM> receives information from the subscriber entity when subscription profile download is requested. The information could be device information (as specified in aforementioned document "SGP. <NUM> - RSP Technical Specification" and in document "SGP. <NUM> - eSIM Architecture Specification", Version <NUM>, <NUM> September <NUM>, published by the GSM Association) and eUICC <NUM> information (eUICC <NUM> Info1 + Info2) (as specified in aforementioned documents "SGP. <NUM> - RSP Technical Specification" and "SGP. <NUM> - eSIM Architecture Specification"). Examples of device information are: type allocation code (TAC), device capabilities, IMEI (optional), preferred languages (optional), indication for enterprise capable device, device test mode, and RSP functions supported. Examples of device capabilities are: radio access technologies (including release), contactless (the single wire protocol (SWP) and human computer interaction (HCI) interfaces as well as the associated application programming interfaces (APIs)), RSP central revocation list subversion (CRL SVN), local subscription profile assistant subversion (LPA SVN), card application toolkit support, and eUICC <NUM> form factor type.

The subscription profile can then be created based on these rules and the eligibility data received from the eUICC <NUM>.

Table <NUM> gives an example of how the TAC could be used for selecting the profile type. It is noted that there could be any number of these rules and that each rule could point to one or more profile types.

Table <NUM> gives an example of how the eUICC information and the device information provided by the eUICC to the SM-DP+ is interpreted in view of profile property requirements.

Table <NUM> gives an example of how each profile template has a set of profile properties defined. If the profile property requirements from the eUICC match a profile template in the inventory, that profile template is selected. If not, either a default profile template is selected, or no profile template is selected (in case not even the default template can be used).

<FIG> schematically illustrates, in terms of a number of functional units, the components of a subscription provisioning server <NUM> according to an embodiment.

Processing circuitry <NUM> is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 1210a (as in <FIG>), e.g. in the form of a storage medium <NUM>. The processing circuitry <NUM> may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

Particularly, the processing circuitry <NUM> is configured to cause the subscription provisioning server <NUM> to perform a set of operations, or steps, as disclosed above. For example, the storage medium <NUM> may store the set of operations, and the processing circuitry <NUM> may be configured to retrieve the set of operations from the storage medium <NUM> to cause the subscription provisioning server <NUM> to perform the set of operations. Thus the processing circuitry <NUM> is thereby arranged to execute methods as herein disclosed.

The subscription provisioning server <NUM> may further comprise a communications interface <NUM> for communications with other entities, functions, nodes, and devices of the communication network <NUM>. As such the communications interface <NUM> may comprise one or more transmitters and receivers, comprising analogue and digital components.

The processing circuitry <NUM> controls the general operation of the subscription provisioning server <NUM> e.g. by sending data and control signals to the communications interface <NUM> and the storage medium <NUM>, by receiving data and reports from the communications interface <NUM>, and by retrieving data and instructions from the storage medium <NUM>. Other components, as well as the related functionality, of the subscription provisioning server <NUM> are omitted in order not to obscure the concepts presented herein.

<FIG> schematically illustrates, in terms of a number of functional modules, the components of a subscription provisioning server <NUM> according to an embodiment.

The subscription provisioning server <NUM> of <FIG> comprises a number of functional modules; an obtain module 110c configured to perform step S106, and a create module 110f configured to perform step S112. The subscription provisioning server <NUM> of <FIG> may further comprise a number of optional functional modules, such as any of an obtain module 110a configured to perform step S102, a create module 110b configured to perform step S104, a verify module 110d configured to perform step S108, a provide module 110e configured to perform step S110, and an enable module <NUM> configured to perform step S114. In general terms, each functional module 110a-<NUM> may be implemented in hardware or in software. Preferably, one or more or all functional modules 110a-<NUM> may be implemented by the processing circuitry <NUM>, possibly in cooperation with the communications interface <NUM> and/or the storage medium <NUM>. The processing circuitry <NUM> may thus be arranged to from the storage medium <NUM> fetch instructions as provided by a functional module 110a-<NUM> and to execute these instructions, thereby performing any steps of the subscription provisioning server <NUM> as disclosed herein.

<FIG> schematically illustrates, in terms of a number of functional units, the components of a mobile network operator entity <NUM> according to an embodiment. Processing circuitry <NUM> is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 1210b (as in <FIG>), e.g. in the form of a storage medium <NUM>. The processing circuitry <NUM> may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

Particularly, the processing circuitry <NUM> is configured to cause the mobile network operator entity <NUM> to perform a set of operations, or steps, as disclosed above. For example, the storage medium <NUM> may store the set of operations, and the processing circuitry <NUM> may be configured to retrieve the set of operations from the storage medium <NUM> to cause the mobile network operator entity <NUM> to perform the set of operations. Thus the processing circuitry <NUM> is thereby arranged to execute methods as herein disclosed.

The mobile network operator entity <NUM> may further comprise a communications interface <NUM> for communications with other entities, functions, nodes, and devices of the communication network <NUM>. As such the communications interface <NUM> may comprise one or more transmitters and receivers, comprising analogue and digital components.

The processing circuitry <NUM> controls the general operation of the mobile network operator entity <NUM> e.g. by sending data and control signals to the communications interface <NUM> and the storage medium <NUM>, by receiving data and reports from the communications interface <NUM>, and by retrieving data and instructions from the storage medium <NUM>. Other components, as well as the related functionality, of the mobile network operator entity <NUM> are omitted in order not to obscure the concepts presented herein.

<FIG> schematically illustrates, in terms of a number of functional modules, the components of a mobile network operator entity <NUM> according to an embodiment. The mobile network operator entity <NUM> of <FIG> comprises a provide module 210a configured to perform step S210a. The mobile network operator entity <NUM> of <FIG> may further comprise a number of optional functional modules, such as an obtain module 210b configured to perform step S204. In general terms, each functional module 210a-210b may be implemented in hardware or in software. Preferably, one or more or all functional modules 210a-210b may be implemented by the processing circuitry <NUM>, possibly in cooperation with the communications interface <NUM> and/or the storage medium <NUM>. The processing circuitry <NUM> may thus be arranged to from the storage medium <NUM> fetch instructions as provided by a functional module 210a-210b and to execute these instructions, thereby performing any steps of the mobile network operator entity <NUM> as disclosed herein.

<FIG> shows one example of a computer program product 1210a, 1210b comprising computer readable means <NUM>. On this computer readable means <NUM>, a computer program 1220a can be stored, which computer program 1220a can cause the processing circuitry <NUM> and thereto operatively coupled entities and devices, such as the communications interface <NUM> and the storage medium <NUM>, to execute methods according to embodiments described herein. The computer program 1220a and/or computer program product 1210a may thus provide means for performing any steps of the subscription provisioning server <NUM> as herein disclosed. On this computer readable means <NUM>, a computer program 1220b can be stored, which computer program 1220b can cause the processing circuitry <NUM> and thereto operatively coupled entities and devices, such as the communications interface <NUM> and the storage medium <NUM>, to execute methods according to embodiments described herein. The computer program 1220b and/or computer program product 1210b may thus provide means for performing any steps of the mobile network operator entity <NUM> as herein disclosed.

In the example of <FIG>, the computer program product 1210a, 1210b is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc. The computer program product 1210a, 1210b could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory. Thus, while the computer program 1220a, 1220b is here schematically shown as a track on the depicted optical disk, the computer program 1220a, 1220b can be stored in any way which is suitable for the computer program product 1210a, 1210b.

Claim 1:
A method for creating a subscription profile for a subscriber entity (<NUM>), the method being performed by a subscription provisioning server (<NUM>), the method comprising:
obtaining (S106), from the subscriber entity (<NUM>), a request for download of the subscription profile, the request comprising capability information of the subscriber entity (<NUM>);
creating (S112) the subscription profile based on the capability information as obtained from the subscriber entity (<NUM>); and characterized in that the method further comprises:
verifying (S108) that the subscriber entity (<NUM>) passes an eligibility check before, or as part of, creating the profile, wherein the eligibility check is based on the capability information of the subscriber entity (<NUM>) and pertains to whether the subscriber entity (<NUM>) will support the subscription profile or not.