Operating subscription profile download

Abstract

A method for operating subscription profile downloading and installation is implemented by a subscriber module (1200) in a communication device (180). The method comprises: obtaining (S102) download information for the operation subscription profile from an eSIM server (1400) and over an initial cellular connectivity connection for the communication device, where the subscriber module authenticates the eSIM server using subscription data during cellular network access authentication to establish the initial cellular connectivity connection; preparing an entity (150) from enhanced subscription manager data and downloading (S104) the operational subscription profile according to the download information, where the operational subscription profile is downloaded over the initial cellular connectivity connection for the communication device; and installing (S106) the operation subscription profile in the subscriber module. A communication device, an eSIM server, a subscription module, a computer program, a computer program product and further methods are also disclosed.

Description

Technical Field

[0001] The invention presented herein relates to a method, a subscriber module, a communication device, a computer program and a computer program product for operating a subscription profile download and installation. The invention also relates to a method, an embedded subscriber identity module (eSIM) server, a computer program and a computer program product for implementing the operation of downloading and installing a subscription profile to a subscriber module. Background Art

[0002] The Global System for Mobile Communications Alliance (GSMA) has specified how to provide subscribers with a 3rd Generation Partnership Project (3GPP) subscription profile, commonly referred to as a Subscriber Identity Module (SIM) subscription profile, hereinafter referred to as a subscription profile. Such a subscription profile can be remotely downloaded to the physical hardware in the communication device, called an embedded UICC / embedded universal integrated circuit card (eUICC) or an integrated UICC / universal integrated circuit card (iUICC) or an integrated embedded UICC / universal integrated circuit card (ieUICC), via the Internet. The Remote SIM Provisioning Protocol (RSP) is followed to remotely deliver the subscription profile to the communication device from a provisioning server (such as an enhanced subscription manager data preparation (SM-DP+) server; hereinafter referred to as an SM-DP+ entity). Remote SIM provisioning for consumer devices is described in the documents "SGP.21-RSP Architecture Specification v2.4" and "SGP.22-RSP Technical Specification v2.4".

[0003] The communication device downloads the subscription profile from the SM-DP+ entity. When the mobile network operator (MNO) orders a subscription profile from the SM-DP+ entity, the SM-DP+ entity will prepare the subscription profile that will be available for download for the communication device. During the subscription profile subscription phase, the MNO also implements the necessary network provisioning operations. In particular, in order to obtain initial cellular-based connectivity when the communication device is first started, it is necessary to install a suitable SIM subscription profile for the location of the communication device into the communication device at the time of manufacturing. This SIM subscription profile is hereinafter referred to as a bootstrap subscription profile or a provisioning subscription profile. When the eUICC / module / device is manufactured, it is generally not known what a particular communication device will end up like. Therefore, a provisioning subscription profile of an MNO with a global roaming agreement is desired.

[0004] Generally, eSIM services are available for communication devices in the form of Internet of Things (IoT) devices, where knowledge of a pre-negotiated agreement with the MNO, IoT device information, etc. based on the geographic location of the IoT device is used as input to a localization process that is implemented to determine the correct MNO, provisioning server, and subscription profile for a particular IoT device. The download of the operational subscription profile is then triggered. Such eSIM services may be provided by an eSIM server and may be triggered, for example, when the IoT device is first powered on.

[0005] Since IoT devices generally do not have a user interface, IoT devices may not be able to establish user consent for operations related to subscription profiles. In the provisioning technology for IoT devices under consideration, the IoT device is configured to accept subscription profile download trigger operations and subscription profile management operations (such as enabling, disabling and deleting subscription profiles) sent to the IoT device from an authorized (remote) server (hereinafter referred to as a management entity) through an established secure communication channel without seeking any user confirmation through some local or remote user interface. This allows automatic subscription profile processing for a batch (such as hundreds or thousands) of IoT devices. The management entity may be called an eSIM IoT Remote Manager (eIM). According to the document "SGP.31-eSIM IoT Architecture and Requirements v1.0" published by GSMA, its purpose is to be based on the eSIM consumer variant so that the IoT eSIM variant can utilize the existing SM-DP+ and Subscription Manager Discovery Service (SM-DS) infrastructure. Therefore, the IoT eSIM variant supports the same three methods as in the eSIM consumer variant (as summarized below) to provide the communication device with information that the subscription profile is waiting to be downloaded. For secure subscription profile management in IoT devices, secure communication must be established between IoT devices and management entities, which relies on key materials available at IoT devices and management entities. For example, a pre-shared key can be used, or a private public key pair and certificate for two entities can be used. In the GSMA eSIM IoT architecture (SGP.31), a secure communication channel between an IoT device and a device management server acting as a management entity can be used to ensure secure triggering of subscription profile download and subscription profile management operations. Establishing key materials on both sides is not within the scope of the solution proposed by GSMA. For example, it may rely on the boot process of the IoT device to set the key material. The GSMA eSIM IoT architecture for low-power IoT devices is aimed at storage and / or power-constrained IoT devices and IoT devices connected via a low-power wide area (LPWA) network. Such devices are generally unable to support Hypertext Transfer Protocol Secure (HTTPS) communication with SM-DP+ entities as required by SGP.22. For these devices, secure communication between the IoT device and the management entity is utilized to implement subscription profile download (and notification processing) to the SM-DP+ entity via the management entity, and the management entity handles HTTPS communication with the SM-DP+ entity.

[0006] There are currently three options, denoted below as Option 1, Option 2 and Option 3, defined for providing information to the communication device that a subscription profile is awaiting download.

[0007] Option 1: During the subscription profile subscription phase, the MNO receives an activation code (AC) from the SM-DP+ (via the ES2+ interface), or the MNO generates an AC based on data received from the SM-DP+. The MNO then distributes the AC to the customer, for example in the form of a Quick Response (QR) code, which can be read by the communication device and used by the communication device to contact the SM-DP+. The customer triggers the download of the subscription profile by providing the AC to the communication device, and then, based on the information from the AC, the communication device is able to connect to the appropriate SM-DP+ to download the subscription profile.

[0008] Option 2: The communication device is configured with or at least has access to a default SM-DP+ address that defines the SM-DP+ for downloading subscription profiles. For example, at first power-up during commissioning of the communication device, or based on some other defined trigger, the communication device connects to the default SM-DP+ to download the subscription profile.

[0009] Option 3: During the subscription profile subscription phase, the MNO requests the SM-DP+ to register information about available subscription profiles for a specific communication device at a discovery service (such as SM-DS). Then, an event is created at the SM-DS for the specific communication device, instructing the communication device to connect to the SM-DP+ to download the subscription profile. The communication device is configured to contact the SM-DS, for example, at the first power-on during commissioning of the communication device, to check for pending subscription profile download events. Upon a successful download event from the SM-DS, the communication device connects to the SM-DP+ given by the event to download the subscription profile. The GSMA has currently specified a root SM-DS, which is common to all communication devices. However, there may be secondary SM-DS servers and vendor-specific discovery services, and therefore there are multiple SM-DS servers.

[0010] According to Option 2 and Option 3, the MNO provides the eUICC identifier (EID) of the communication device, and the subscription profile package to be downloaded is bound to the EID in the SM-DP+. According to Option 1, the MNO (or SM-DP+) does not need to know the EID when subscribing to the subscription profile. In Option 1, the communication device receives the matching ID (MID) via the AC, and the communication device presents the matching ID (MID) to the SM-DP+ during the download of the subscription profile to identify the correctly prepared subscription profile package.

[0011] In the GSMA eSIM IoT architecture specified in the above-mentioned document "SGP.31-eSIM IoT Architecture and Requirements v1.0", in addition to the secure channel between the communication device and the management entity, an additional layer of protection is added between the management entity and the subscriber module to prevent potential malware in the communication device. According to the architecture, the management entity must use its private key to sign all commands / operations for the subscriber module related to subscription profile state management operations, and before accepting subscription profile state management operations (PSMO) such as subscription profile activation, subscription profile disabling and subscription profile deletion, the subscriber module must verify the signature using the management entity public key that has been securely configured in the subscriber module. This is to ensure that malware cannot (download, install and) enable a fraudulent (rogue) subscription profile into the subscriber module, or that malware cannot disable or delete an installed subscription profile, resulting in a connection interruption and the need to reinstall the subscription profile. The signed PSMO protects management operations, data that uniquely identifies the subscription profile (e.g., integrated circuit card ID; ICCID), and data for replay protection (e.g., counter or random).

[0012] The configuration of the management entity public key in the subscriber module can be implemented at different stages, such as subscriber module production, communication device production, and on-site when the communication device is put into use. Currently, subscription profile state management is only possible when the management entity public key has been configured in the subscriber module. In addition, in the case of downloading the subscription profile from the default SM-DP+ entity (as in option 2) or from the SM-DP+ entity obtained via the SM-DS entity (as in option 3), it is allowed to automatically enable the subscription profile without a signed PSMO.

[0013] Although the GSMA eSIM IoT architecture prevents malware in a communication device from modifying the state of a subscription profile, it does not prevent malware from orchestrating the download and installation of a new subscription profile. The architecture also does not prevent someone who knows the EID of a particular communication device from subscribing to an unwanted subscription profile for that particular communication device and preparing the download, for example, via an SM-DP+ entity whose information is obtained via the same SM-DS entity that the communication device uses to check for subscription profiles to download. Summary of the invention

[0014] It is an object of embodiments herein to address at least one of the above mentioned problems and / or to achieve security improvements in the process of operating subscription profiles.

[0015] According to a first aspect, a method for downloading and installing an operation subscription profile is proposed. The method is implemented by a subscriber module. The subscriber module is provided in a communication device. The subscriber module is provided with subscription data for establishing initial cellular connectivity. The method comprises: obtaining download information for the operation subscription profile from an eSIM server and through an initial cellular connectivity connection for the communication device. When it is determined that the subscription profile download is authorized to the subscriber module, the download information is used by the subscriber module. During cellular network access authentication to establish the initial cellular connectivity connection, the subscriber module authenticates the eSIM server using the subscription data. The method comprises: downloading the operation subscription profile from an SM-DP+ entity and according to the download information. The operation subscription profile is downloaded through the initial cellular connectivity connection for the communication device. The method comprises: installing the operation subscription profile in the subscriber module.

[0016] According to a second aspect, a subscriber module for downloading and installing an operation subscription profile is proposed. The subscriber module is provided in a communication device. The subscriber module is provided with subscription data for establishing initial cellular connectivity. The subscriber module includes a processing circuit. The processing circuit is configured to enable the subscriber module to obtain download information for the operation subscription profile from an eSIM server and through an initial cellular connectivity connection for the communication device. When it is determined that the subscription profile download is authorized to the subscriber module, the download information is used by the subscriber module. During cellular network access authentication to establish the initial cellular connectivity connection, the subscriber module authenticates the eSIM server using the subscription data. The processing circuit is configured to enable the subscriber module to download the operation subscription profile from an SM-DP+ entity and according to the download information. The operation subscription profile is downloaded through the initial cellular connectivity connection for the communication device. The processing circuit is configured to enable the subscriber module to install the operation subscription profile in the subscriber module.

[0017] According to a third aspect, a subscriber module for downloading and installing an operation subscription profile is proposed. The subscriber module is provided in a communication device. The subscriber module is provided with subscription data for establishing initial cellular connectivity. The subscriber module includes an acquisition module configured to acquire download information for the operation subscription profile from an eSIM server and through an initial cellular connectivity connection for the communication device. When it is determined that the subscription profile download is authorized to the subscriber module, the download information is used by the subscriber module. During cellular network access authentication to establish the initial cellular connectivity connection, the subscriber module authenticates the eSIM server using the subscription data. The subscriber module includes a download module configured to download the operation subscription profile from an SM-DP+ entity and according to the download information. The operation subscription profile is downloaded through the initial cellular connectivity connection for the communication device. The subscriber module includes an installation module configured to install the operation subscription profile in the subscriber module.

[0018] According to a fourth aspect, a computer program for downloading and installing an operational subscription profile is proposed. A subscriber module is provided in a communication device. The subscriber module is provided with subscription data for establishing initial cellular connectivity. The computer program includes computer program code, which, when running on a processing circuit of the subscriber module, causes the subscriber module to obtain download information for the operational subscription profile from an eSIM server and through an initial cellular connectivity connection for the communication device. When it is determined that the subscription profile download is authorized to the subscriber module, the download information is used by the subscriber module. During cellular network access authentication to establish the initial cellular connectivity connection, the subscriber module authenticates the eSIM server using the subscription data. The computer program includes computer program code, which, when running on a processing circuit of the subscriber module, causes the subscriber module to download the operational subscription profile from an SM-DP+ entity and according to the download information. The operational subscription profile is downloaded through the initial cellular connectivity connection for the communication device. The computer program comprises computer program code which, when executed on processing circuitry of the subscriber module, causes the subscriber module to install the operational subscription profile in the subscriber module.

[0019] According to a fifth aspect, a method for enabling downloading and installing an operational subscription profile to a subscriber module is provided. The method is implemented by an eSIM server. The method comprises: obtaining a trigger for downloading the operational subscription profile to the subscriber module. The method comprises: providing download information for the operational subscription profile to the subscriber module and over an initial cellular connectivity connection for a communication device in which the subscriber module is provided. The download information is designated for the subscriber module to determine that subscription profile download is authorized to the subscriber module. The eSIM server provides authentication data to the subscriber module for the subscriber module to authenticate the eSIM server during cellular network access authentication to establish the initial cellular connectivity connection.

[0020] According to a sixth aspect, an eSIM server is provided for implementing downloading and installing an operational subscription profile to a subscriber module. The eSIM server comprises a processing circuit. The processing circuit is configured to cause the eSIM server to obtain a trigger for downloading the operational subscription profile to the subscriber module. The processing circuit is configured to cause the eSIM server to provide download information for the operational subscription profile to the subscriber module and through an initial cellular connectivity connection for a communication device in which the subscriber module is provided. The download information is designated for the subscriber module to determine that the subscription profile download is authorized to the subscriber module. The eSIM server provides authentication data to the subscriber module for the subscriber module to authenticate the eSIM server during cellular network access authentication to establish the initial cellular connectivity connection.

[0021] According to a seventh aspect, an eSIM server is provided for implementing downloading and installing an operational subscription profile to a subscriber module. The eSIM server comprises an acquisition module configured to acquire a trigger for downloading an operational subscription profile to the subscriber module. The eSIM server comprises a provision module configured to provide download information for the operational subscription profile to the subscriber module and over an initial cellular connectivity connection for a communication device in which the subscriber module is provided. The download information is designated for the subscriber module to determine that subscription profile download is authorized to the subscriber module. The eSIM server provides authentication data to the subscriber module for the subscriber module to authenticate the eSIM server during cellular network access authentication to establish the initial cellular connectivity connection.

[0022] According to an eighth aspect, a computer program for implementing downloading and installing an operational subscription profile to a subscriber module is provided. The computer program comprises computer program code. When executed on a processing circuit of an eSIM server, the computer program code causes the eSIM server to obtain a trigger for downloading the operational subscription profile to the subscriber module. When executed on a processing circuit of the eSIM server, the computer program code causes the eSIM server to provide download information for the operational subscription profile to the subscriber module and over an initial cellular connectivity connection for a communication device in which the subscriber module is provided. The download information is designated for the subscriber module to determine that subscription profile download is authorized to the subscriber module. The eSIM server provides authentication data to the subscriber module for the subscriber module to authenticate the eSIM server during cellular network access authentication to establish the initial cellular connectivity connection.

[0023] According to a ninth aspect, there is provided a computer program product comprising a computer program according to at least one of the fourth and eighth aspects and a computer readable storage medium storing the computer program thereon. The computer readable storage medium may be a non-transitory computer readable storage medium.

[0024] A tenth aspect relates to a communication device, comprising the subscriber module according to the second aspect or the third aspect.

[0025] Advantageously, these aspects provide a secure process for downloading and installing a subscription profile in a communication device, thereby avoiding the above-mentioned problems.

[0026] Advantageously, these aspects mitigate the risk of fraudulent subscription profiles being downloaded to and installed in a subscriber module of a communication device.

[0027] Advantageously, these aspects enable automatic processing of download information without requiring involvement of a device owner or user, thereby enabling automatic provisioning of operational subscription profiles.

[0028] Advantageously, these aspects enable automatic later / subsequent configuration of information in the subscriber module for subscription profile download using the above disclosed options 2 and 3. Such information includes SM-DP+ / SM-DS object identifier (OID) and address.

[0029] Other objects, features and advantages of the accompanying embodiments will become apparent from the following detailed disclosure, claims and drawings.

[0030] Generally, unless otherwise clearly defined herein, all terms used in the embodiments and claims should be interpreted according to their ordinary meanings in the technical field. Unless otherwise clearly stated, all references to "an / an / the element, device, component, member, module, step, etc." should be openly interpreted as referring to at least one instance of an element, device, component, member, module, step, etc. Unless explicitly stated, the steps of any method disclosed herein are not necessarily implemented in the exact order disclosed. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The inventive concept will now be described by way of example with reference to the accompanying drawings, in which:

[0032] Figure 1 is a schematic diagram showing a communication network according to an embodiment;

[0033] Figure 2 and Figure 3 is a flow chart of a method according to an embodiment;

[0034] Figures 4 to 11 is a sequence diagram according to an embodiment;

[0035] Fig.12 is a schematic diagram showing functional units of a subscriber module according to an embodiment;

[0036] Fig.13 is a schematic diagram showing functional modules of a subscriber module according to an embodiment;

[0037] Fig.14 is a schematic diagram showing functional units of an eSIM server according to an embodiment;

[0038] Fig.15 is a schematic diagram showing functional modules of an eSIM server according to an embodiment; and

[0039] Fig.16 An example of a computer program product including computer readable means according to an embodiment is shown. DETAILED DESCRIPTION

[0040] The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which specific embodiments of the inventive concept are shown. However, the inventive concept may be embodied in many different forms and should not be construed as limited to the embodiments described herein; rather, these embodiments are provided by way of example so that this disclosure will be comprehensive and complete and will fully convey the scope of the inventive concept to those skilled in the art. The same numbers throughout this specification represent the same elements. Any steps or features indicated by dashed lines should be considered optional.

[0041] The wording that a particular data item or piece of information is obtained by a first device should be interpreted as the data item or piece of information being retrieved, retrieved, received or otherwise made available to the first device. For example, the data item or piece of information may be pushed to the first device from the second device, or may be pulled from the second device by the first device. In addition, in order for the first device to obtain the data item or piece of information, the first device may be configured to perform a series of operations, which may include interaction with the second device. Such operations or interactions may involve message exchanges, including any of the following: a request message for the data item or piece of information, a response message including the data item or piece of information, and a confirmation message for the data item or piece of information. If the first device neither explicitly nor implicitly requests the data item or piece of information, the request message may be omitted.

[0042] The wording that a particular data item or piece of information is provided by a first device to a second device should be interpreted as sending the data item or piece of information to the second device by the first device or otherwise making it available to the second device. For example, the data item or piece of information may be pushed from the first device to the second device, or may be pulled from the second device by the second device. In addition, 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 may be configured to implement a series of operations in order to interact with each other. Such operations or interactions may involve message exchanges, including any one of the following: a request message for the data item or piece of information, a response message including the data item or piece of information, and a confirmation message for the data item or piece of information. If the second device neither explicitly nor implicitly requests the data item or piece of information, the request message may be omitted.

[0043] Figure 1 is a schematic diagram illustrating a communication network 100 in which embodiments presented herein may be applied.

[0044] The communication device 180 is a device to which an operational subscription profile is to be downloaded. The communication device 180 may be a mobile phone, a notebook computer, a computer tablet, or a user equipment (UE). It may also be an IoT device. The communication device 180 includes a subscriber module 1200, such as an iUICC or an eUICC or an ieUICC (as exemplified by the eUICC in the figure), supporting remote provisioning of subscription profiles according to GSMA consumer variants, including signature subscription profile state management operations according to the GSMA eSIM IoT architecture (as specified in the above document "SGP.31-eSIM IoT Architecture and Requirements v1.0"). The communication device 180 supports secure subscription profile downloading, installation, and activation, wherein authorization secrets are utilized, or download and installation data are used. The subscriber module 1200 stores credentials for secure interaction with a provisioning server (such as an SM-DP+ entity 150) and a discovery server (such as an SM-DS entity 160). The credentials include an elliptic curve (EC) private key and a subscriber module 1200 certificate containing a corresponding public key. The subscriber module 1200 certificate also contains a subscriber module 1200 identifier, such as an EID. The subscriber module 1200 is provisioned with a first profile in the form of a provisioning subscription profile at the time of manufacturing, or personalization or module / device manufacturing. The provisioning subscription profile provides initial cellular connectivity to allow downloading of an operating subscription profile. Optionally, if the subscription profile is not installed in the subscriber module 1200, the subscriber module 1200 operating system (OS) may act as a provisioning subscription profile in the initial cellular connectivity establishment. The communication device 180 may be manufactured by an original equipment manufacturer (OEM), and the subscriber module 120 may be manufactured by an eUICC manufacturer (EUM), both of which are represented by a manufacturer entity 130.

[0045] Management of subscription profiles on the subscriber module 1200 (e.g., enabling, disabling, and deleting subscriber subscription profiles) is handled remotely by the management entity 210. The management entity 210 may also handle device and data management for the communication device 180. When the communication device 180 is first powered on, information may not yet be configured to connect to the management entity 210. Such information may be obtained by the communication device 180, for example, via operating the subscription profile or via an application layer bootstrapping process.

[0046] The communication device 180 includes a cellular modem configured to connect to a mobile network based on an active subscription profile. For the first startup of the communication device 180, the provisioning subscription profile is the active subscription profile and provides initial cellular connectivity. The initial cellular connectivity is established using the first mobile network (MNO1 120). Using eSIM remote SIM provisioning, a second profile in the form of an operational subscription profile can then be provisioned to the subscriber module 1200 from the second mobile network (MNO2 200). Note here that MNO1 120 and MNO2 200 can be the same network, but can be different networks in other embodiments. In some instances, the terms MNO1, MNO2, and MNO3 can also be used interchangeably in the following description for mobile network operators and their corresponding mobile networks. After the operational subscription profile has been activated, the operational subscription profile is used to provide network connectivity for the communication device 180. In other words, the operational subscription profile is intended to be used for connectivity services for the communication device 180 for a longer period of time (than the provisioning subscription profile). In an embodiment, the operational subscription profile includes MNO data and applications for the purpose of providing services by the MNO. In an embodiment, the operational subscription profile supports subscription with the MNO and allows connection to a mobile network, which in the above figure is typically MNO2 200. The operational subscription profile may also include one or more applications for non-telecom services. In an embodiment, the provisioning subscription profile includes a combination of MNO data and applications, the purpose of which is to enable connectivity with MNO1 120 only for the purpose of provisioning the operational subscription profile on the subscriber module 1200. Therefore, the provisioning subscription profile contains information / applications that are not present in the operational subscription profile, such as information on how to download the operational subscription profile.

[0047] The communication device 180 typically includes an IoT subscription profile assistant (IPA) 170 as part of the modem, which assists in subscription profile download and subscription profile management operations. The IPA 170 interacts with the provisioning server for subscription profile download and notification processing, and interacts with the management entity for subscription profile management operations. The IPA 170 may be configured to interact with the discovery service to check for pending subscription profile download events. In the case where the communication device 180 is subject to network constraints, energy constraints, and / or storage constraints, the interaction with the SM-DP+ entity 150 and the SM-DS entity 160 may be via the management entity 210.

[0048] When the communication device 180 connects to the first mobile network (i.e., the visiting / serving mobile network) during its first startup to obtain initial cellular connectivity, the eSIM server 1400 acts as the home mobile network. The eSIM server 1400 provides a provisioning subscription profile that is installed during the manufacture or personalization of the subscriber module 1200. This can be a subscription profile common to all communication devices 180 using the service. Optionally, a separate subscription profile is used for each communication device 180. The provider of the eSIM server 1400 can be, for example, a mobile network operator, a communication service provider (CSP), a mobile virtual network operator (MVNO), or a mobile network provider. The provider of the eSIM server 1400 can have an agreement with the MNO (shown as the mobile network MNO3110) to use a set of international mobile subscriber identities (IMSIs) for its eSIM server 1400, so that the communication device (such as the communication device 180) can be routed to the eSIM server 1400 during the initial cellular connectivity establishment.

[0049] The MNO (or CSP) provides cellular connectivity for the communication device and potentially also a localized server 140 for remote subscription profile download. The eSIM server 1400 provider, in the case of an MVNO, has roaming agreements with a set of MNOs (represented in the figure as mobile network MNO1 120) that use the eSIM server 1400 to assist in providing initial cellular connectivity for the communication device 180.

[0050] An enterprise, IoT service provider, device owner or end user using the eSIM server 1400 subscribes to a subscription profile for its communication device 180 from an MNO (shown as mobile network MNO2 200). The MNO interacts with a provisioning server to prepare the operational subscription profile for remote download. Upon successful download and activation of the operational subscription profile into the communication device 180, the MNO provides cellular connectivity to the communication device 180. Note that MNO2 200 may be one of the MNO1 120 operators that provided the initial cellular connectivity.

[0051] The SM-DP+ entity 150 handles the download of subscription profiles to IoT devices according to the GSMA eSIM consumer variant. The SM-DP+ entity 150 is operated by the MNO (shown as the mobile network MNO2 200 in the figure) that provides the operational subscription profile to be downloaded or by a third party trusted by the MNO. The SM-DP+ entity 150 is verified and has obtained a certificate, allowing it to become part of the eSIM ecosystem. The SM-DP+ certificate for authentication and the certificate for subscription profile download contain the SM-DP+ OID. The OID is used to ensure communication with the intended SM-DP+ entity 150.

[0052] The SM-DS entity 160 provides discovery services for use by the communication device 180 in accordance with the above-mentioned documents "SGP.21-RSP Architecture Specification v2.4" and "SGP.22-RSP Technical Specification v2.4". GSMA currently specifies the root SM-DS for the eSIM ecosystem. However, there may be auxiliary SM-DS entities and vendor-specific SM-DS entities. The SM-DS entity 160 is authenticated and has obtained one or more certificates, allowing it to become part of the eSIM ecosystem. The SM-DS certificate used for authentication contains the SM-DS OID. The OID is used to ensure communication with the intended SM-DS entity 160.

[0053] As part of providing initial cellular connectivity, the localization server 140 may determine the appropriate MNO / MNO device to provide an operational subscription profile for a particular communication device 180. This is referred to as a localization process, which may be more or less complex depending on the scenario being targeted. For example, the appropriate MNO, provisioning server, and operational subscription profile to use may be determined based on the geographic location of the communication device 180, knowledge of a pre-negotiated agreement with the MNO, communication device 180 information, etc. This localization may be provided as a service by the localization server 140 provider to an enterprise or communication service provider 190.

[0054] There may be different ways in how the localization server 140 is provided and how it is connected to the eSIM server 1400. In a first option, the localization server 140 manages connectivity for a group of MNOs and handles interactions with the provisioning server on behalf of the MNO (the provisioning server may even be provided by the localization server 140 provider), and also updates / controls the home subscriber server (HSS) or similar (such as the unified data management (UDM) in the 5G core network (5GC) of the MNO). In a second option, the localization server 140 simply implements localization based on input data, and the enterprise itself handles the interaction with the MNO. Other options are also possible. The eSIM server 1400 may be closely connected to the localization server 140 (or part of it), for example in the first option, or it may have no relationship and only use the localization application programming interface (API) to trigger localization and receive information about the selected operational subscription profile. Such interaction may also be via the enterprise.

[0055] The management entity 210 manages one or more subscription profiles on the subscriber module 1200 of the communication device 180. The management entity 210 may also facilitate subscription profile download interactions between the communication device 180 and the SM-DS entity 160. The management entity 210 supports signed subscription profile state management operations (PSMOs) using a management entity 210 private key (such as an EC private key), the corresponding public key of which (such as an EC public key) is configured into each subscriber module 1200 managed by the management entity 210. The management entity 210 is configured with a list of subscriber modules 1200 or subscriber module 1200 identifiers (such as EIDs) of the communication device 180 managed by the management entity 210. The device owner / end user / enterprise / service provider or other actor may interact with the management entity 210 to configure it using management operations. Such information may include, for example, the ICCID of the subscription profile of a particular subscriber module 1200 for which a particular subscription profile management operation should be performed, or may include an activation code (AC) with information about where a particular communication device 180 should download the subscription profile from.

[0056] Embodiments disclosed herein relate to techniques for operating subscription profile download and installation to a subscriber module 1200. To achieve such techniques, a subscriber module 1200, a method implemented by the subscriber module 1200, and a computer program product are provided, the computer program product including code, such as in the form of a computer program, which when executed on a processing circuit of the subscriber module 1200, causes the subscriber module 1200 to implement the method. To achieve such techniques, an eSIM server 1400, a method implemented by the eSIM server 400, and a computer program product are provided, the computer program product including code, such as in the form of a computer program, which when executed on a processing circuit of the eSIM server 140, causes the eSIM server 1400 to implement the method.

[0057] Reference now Figure 2 , which shows a method implemented by a subscriber module 1200 for operating subscription profile download and installation according to an embodiment. The subscriber module 1200 is provided in the communication device 180. The subscriber module 1200 is provided with subscription data for establishing initial cellular connectivity.

[0058] S102: The subscriber module 1200 obtains download information for operating a subscription profile from the eSIM server 1400. The download information is obtained through an initial cellular connectivity connection for the communication device 180. When it is determined that the subscription profile download is authorized to the subscriber module 1200, the download information is used by the subscriber module 1200. During cellular network access authentication to establish an initial cellular connectivity connection, the subscriber module 1200 authenticates the eSIM server 1400 using subscription data.

[0059] S104: The subscriber module 1200 downloads the operational subscription profile from the SM-DP+ entity 150 and according to the download information. The operational subscription profile is downloaded through the initial cellular connectivity connection for the communication device 180.

[0060] S106 : The subscriber module 1200 installs the operation subscription profile in the subscriber module 1200 .

[0061] Embodiments relating to further details of operational subscription profile download and installation as implemented by subscriber module 1200 will now be disclosed.

[0062] In some embodiments, after S106, the operational subscription profile is enabled when it has been downloaded and installed (and stored). Thus, in some embodiments, the subscriber module 1200 is configured to implement (optional) step S108.

[0063] S108: The subscriber module 1200 activates the operation subscription profile in the subscriber module 1200 when the operation subscription profile has been installed.

[0064] Network access authentication may rely on a shared secret between the eSIM server 1400 and a provisioning profile (as accessed by the subscriber module 1200). The shared secret may be a preconfigured part of the provisioning profile, or may be derived from data contained in the provisioning profile. Thus, in some examples, authentication of the eSIM server 140 is performed using a secret shared with the eSIM server 1400 that is contained in or derivable from subscription data. In some examples, the subscription data is contained in a provisioning subscription profile installed in the subscriber module 1200. In some examples, the subscription data is contained as part of the subscriber module 1200 operating system. Then, when the subscription profile is not installed in the subscriber module 1200, the subscriber module 1200 uses the subscription data to treat the communication device 180 as if the provisioning profile was present in the subscriber module 1200. In some examples, the secret shared with the eSIM server 1400 for ensuring secure transmission of download information from the eSIM server 140 to the subscriber module 1200 over the initial cellular connectivity connection for the communication device 180 is contained in the subscription data or can be derived from the subscription data. In some examples, the secret shared with the eSIM server 140 can be derived from the subscription data based on a private key of a private key-public key pair of the subscriber module 1200 and a public key of a private key-public key pair of the eSIM server 1400. The public key of the private key-public key pair of the eSIM server 1400 is part of the subscription data.

[0065] In some examples, the download information is securely transmitted from the eSIM server 1400 to the subscriber module 1200 using a SIM over-the-air (OTA) procedure. The operational subscription profile may be downloaded from a default SM-DP+ entity 150 or an SM-DP+ entity 150 given by an SM-DS entity 160. If the SM-DS entity 160 is used, the SM-DP+ information of where the operational subscription profile is to be downloaded from is first securely obtained from the SM-DS. The authorization secret is used to ensure that the operational subscription profile download is authorized to the subscriber module 1200. Thus, in some examples, the download information specifies an authorization secret that is used by the subscriber module 1200 to determine that downloading the operational subscription profile from the SM-DP+ entity is authorized, and / or to determine that downloading the SM-DP+ information from the SM-DS that specifies the SM-DP+ entity 150 from which the operational subscription profile is to be downloaded is authorized. Determining that the download is authorized is then based on the subscriber module 1200 obtaining proof of the SM-DP+ / SM-DS knowledge of the authorization secret as obtained during profile download preparation for the operational subscription profile.

[0066] In some examples, secure downloading of the operational subscription profile is ensured by utilizing SM-DS or SM-DP + information (such as addresses and OIDs) in the subscriber module 1200. The SM-DS or SM-DP + information is used by the subscriber module 1200 to verify the information obtained from the SM-DP + and SM-DS (if used) during the operational profile download to determine that the profile download is authorized. The SM-DS or SM-DP + information is selected by the communication device 180 using unsigned download and installation data pointing to the SM-DS or SM-DP + information. Therefore, in some examples, the download information identifies the OID of the SM-DS entity 160 and / or the SM-DP + entity 150 for use by the subscriber module 1200 when downloading and installing the operational subscription profile. In some examples, the SM-DP + entity 150 from which the operation subscription profile is downloaded is given by the OID when the OID identified by the download information is the OID of the SM-DP + entity 150, or is given by the event record received by the subscriber module 1200 from the SM-DS entity 160 when the OID identified by the download information is the OID of the SM-DS entity 160. Then, the SM-DS entity 160 is given by the OID identified by the download information.

[0067] An authentication and key agreement (AKA) protocol (such as a protocol enabled by UMTS-AKA, IMS-AKA, 5G AKA, or Extensible Authentication Protocol-AKA', such as that running between the subscriber module 1200 and the eSIM server 1400 for authenticating the communication device 180 to obtain initial cellular connectivity) may be used to securely transmit the download information. Thus, in some examples, the AKA protocol is used to obtain the download information as part of performing network access authentication when establishing an initial cellular connectivity connection.

[0068] Reference now Figure 3 , which shows a method for implementing operation subscription profile download and installation to a subscriber module 1200, for example, implemented by an eSIM server 1400, according to an implementation.

[0069] S202 : The eSIM server obtains a trigger for downloading an operation subscription profile to the subscriber module 1200 .

[0070] S206: The eSIM server 1400 provides download information for operating a subscription profile to the subscriber module 1200 and through an initial cellular connectivity connection for the communication device 180 in which the subscriber module 1200 is provided. The download information is designated for the subscriber module 1200 to determine that the subscription profile download is authorized to the subscriber module 1200. The eSIM server 1400 provides authentication data to the subscriber module 1200 for the subscriber module 1200 to authenticate the eSIM server 1400 during cellular network access authentication to establish an initial cellular connectivity connection.

[0071] Embodiments relating to further details of enabling operations for downloading and installing subscription profiles to the subscriber module 1200 as performed by the eSIM server 1400 will now be disclosed.

[0072] The trigger obtained in S202 may be in the form of a network access authentication triggered at the eSIM server 1400. This in turn is triggered by a subscription identifier (such as an IMSI or a Network Access Identifier (NAI)) provided / received from the subscriber module 1200 to the eSIM server 1400 via the communication device 180 and the service network.

[0073] In some aspects, the download information is generated or determined by the eSIM service when the profile download is prepared. Thus, in some embodiments, the eSIM server 1400 is configured to implement (optional) step S204.

[0074] S204: The eSIM server 1400 determines download information during profile download preparation for operating a subscription profile.

[0075] Note that step S204 may be performed after step S202 (e.g. Figure 3 As shown) or implemented before step S202, that is, implemented after or before the trigger in S202 has been obtained.

[0076] As described above, in some examples, the authentication data provided by the eSIM server 1400 to the subscriber module 1200 is derived using a secret shared with the subscriber module 1200 (and therefore a shared secret). As disclosed above, in some examples, the secret shared with the subscriber module 1200 is used to ensure that the download information is securely transmitted from the eSIM server 1400 to the subscriber module 1200 over the initial cellular connectivity connection for the communication device 180. As disclosed above, in some examples, the secret shared with the subscriber module 1200 is based on a public key of a private key-public key pair of the subscriber module 1200 and a private key of a private key-public key pair of the eSIM server 1400. As disclosed above, in some examples, the download information is securely transmitted from the eSIM server 1400 to the subscriber module 1200 using a SIM OTA procedure.

[0077] As disclosed above, in some examples, the download information specifies an authorization secret for use by the subscriber module 1200 to determine that downloading the operational subscription profile from the SM-DP+ entity is authorized, and / or for determining that downloading from the SM-DS the SM-DP+ information specifying the SM-DP+ entity 150 from which the operational subscription profile is to be downloaded is authorized. Determining that the download is authorized is based on the subscriber module 1200 obtaining proof of SM-DP+ / SM-DS knowledge of the authorization secret as obtained during profile download preparation for the operational subscription profile.

[0078] As disclosed above, in some examples, the download information identifies the OID of the SM-DS entity 160 and / or the SM-DP + entity 150 for use by the subscriber module 1200 when downloading and installing the operational subscription profile. As disclosed above, in some examples, the SM-DP + entity 150 from which the operational subscription profile is downloaded is given by the OID when the OID identified by the download information is the OID of the SM-DP + entity 150, or is given by the event record received by the subscriber module 1200 from the SM-DS entity 160 when the OID identified by the download information is the OID of the SM-DS entity 160. The SM-DS entity 160 is given by the OID identified by the download information.

[0079] As disclosed above, in some examples, the download information is provided as part of performing network access authentication using the AKA protocol when establishing an initial cellular connectivity connection. In some examples, the download information is provided in the form of an authentication vector.

[0080] In the following examples, for non-limiting and illustrative purposes, the subscriber module 1200 will be represented by an eUICC. However, the following examples are also applicable to other types of subscriber modules 1200 already mentioned in the present disclosure.

[0081] In the following examples, for non-limiting and illustrative purposes, the communication device 180 will be represented by an IoT device. However, the following examples are also applicable to other types of communication devices 180 that have been mentioned in this disclosure. A communication device in the form of an IoT device can be a device used in one or more application domains, including but not limited to: home, city, wearable technology, extended reality, industrial applications, and healthcare. Examples of IoT devices for a home, office, building, or infrastructure may be a baking scale, coffee maker, grill, refrigerator, freezer, freezer, microwave, oven, toaster, faucet, water heater, water boiler, sauna, vacuum cleaner, washing machine, dryer, dishwasher, door, window, curtain, blinds, furniture, light bulb, fan, air conditioner, cooler, air purifier, humidifier, speaker, television, laptop, personal computer, game console, remote control, vent, iron, steamer, pressure cooker, stove, electric stove, hair dryer, curling iron, mirror, printer, scanner, copier, projector, holographic projector, 3D printer, drill, hand dryer, alarm, clock, security camera, smoke alarm, fire alarm, connected doorbell, electronic door lock, lawn mower, thermostat, plug, irrigation control equipment, flood sensor, humidity sensor, motion detector, weather station, electricity meter, water meter, and gas meter.

[0082] By further example, IoT devices for use in a city, urban area, or suburbia may be connected street lighting, connected traffic lights, traffic cameras, connected road signs, air controls / monitors, noise level detectors, traffic congestion monitoring equipment, traffic control equipment, automatic toll payment devices, parking payment devices, sensors for monitoring parking usage, traffic management equipment, digital kiosks, trash bins, air quality monitoring sensors, bridge condition monitoring sensors, fire hydrants, manhole sensors, asphalt pavement sensors, fountain sensors, connected CCTV, scooters, hoverboards, ticket machines, ticket barriers, subway tracks, subway station equipment, passenger information panels, on-board cameras, and other connected devices on public transportation vehicles.

[0083] As a further example, the communication IoT device may be a wearable device, or may be a device related to extended reality, wherein the device related to extended reality may be a device related to augmented reality, virtual reality, merged reality, or mixed reality. Examples of such IoT devices may be smart bracelets, activity trackers, haptic gloves, haptic suits, smart watches, clothing, glasses, head-mounted displays, earbuds, activity monitors, fitness monitors, heart rate monitors, rings, key trackers, blood glucose meters, and pressure gauges.

[0084] As a further example, the IoT device may be an industrial application device, where the industrial application device may be an industrial drone, an intelligent industrial robot, a vehicle assembly robot, and an automated guided vehicle.

[0085] As a further example, the IoT device can be a transportation vehicle, where the transportation vehicle can be a bicycle, motorcycle, scooter, moped, auto rickshaw, rail transportation, train, tram, bus, car, truck, airplane, ship, boat, skis, snowboard, snowmobile, hoverboard, skateboard, roller skates, freight vehicle, drone, robot, stratospheric aircraft, aircraft, helicopter and hovercraft.

[0086] As a further example, IoT devices may be health or fitness devices, where the health or fitness devices may be surgical robots, implantable medical devices, non-invasive medical devices, and fixed medical devices, where the fixed medical devices may be: in vitro diagnostic devices, radiology devices, diagnostic imaging devices, and x-ray devices.

[0087] Next, we will refer to Figure 4 The sequence diagram discloses general aspects of a subscription profile securely downloading operation using download information acquired by an eUICC using an eSIM server.

[0088] refer to Figure 4 , which describes a process for an IoT device to acquire initial cellular connectivity and for the IoT device to download a first operational subscription profile. During a subscription profile download preparation phase, download information required for secure download of the operational subscription profile (e.g., in the presence of malware) is determined or generated, and the download information is provided to the eUICC using an eSIM server that is part of providing initial cellular connectivity to the IoT device.

[0089] Assume (step 0) that the database of the eSIM server is populated with the EID for each IoT device using the eSIM server. The eUICC of each IoT device is configured with a provisioned subscription profile from the eSIM server. This subscription profile is the currently active subscription profile of the eUICC. The IoT device wakes up (e.g., for the first time) and connects to MNO1 using the provisioned subscription profile of the eUICC, performs network access authentication and obtains initial cellular connectivity (step 1a). Typically, roaming is used and the eSIM server acts as the home operator and handles the network access authentication. MNO1 determines the eSIM server based on the IMSI provided by the IoT device (or MNO3 if the eSIM server has an agreement with MNO3 to use a specific IMSI range).

[0090] The network access authentication performed as part of step 1a relies on a shared secret shared between the eSIM server and the provisioning subscription profile. In order to select the correct shared secret and trigger localization in step 2, the eSIM server determines the EID of the eUICC in step 1b. This can be done based on the received IMSI, for example, the mapping between IMSI and EID is saved in the eSIM server, or the EID can be transmitted from the eUICC to the eSIM server during the network access authentication (step 1b is implemented in conjunction with step 1a).

[0091] In order to prepare for downloading a suitable operational subscription profile for the IoT device, the eSIM server requests (in step 2) localization implemented by the localization server. The EID of the eUICC of the IoT device is provided, and optionally the MCC (+MNC) of MNO1 (the country / region where the IoT device is located) for localization. The eSIM server does not necessarily interact directly with the entity implementing the localization as shown here. The localization mechanism is implemented in step 3 and the MNO providing the operational subscription profile is determined, represented as MNO2 in the figure. The operational subscription profile from MNO2 is prepared in advance for download (step 4a), for example for a whole batch of IoT devices, or the localization server interacts directly with the SM-DP+ (step 4b), or prepares the subscription profile for download via the MNO / CSP. If SM-DS is to be used, an event will be registered at the SM-DS.

[0092] When the operational subscription profile is determined and ready for download, the download information required to securely download the subscription profile is securely provided from the localization server to the eSIM server and further to the eUICC (step 1c) (step 5). Depending on the method used to securely transmit the download information, the transmission occurs either as part of obtaining initial cellular connectivity (in conjunction with step 1a) or after obtaining initial cellular connectivity (using this connectivity to transmit the download information). In the first case, steps 2-5 are implemented when the initial cellular connectivity establishment is performed, while in the other case, these steps are typically implemented after the initial cellular connectivity has been established.

[0093] After receiving the download information, the eUICC stores (step 6) the download information in the ISD-R security domain with the help of the eUICC OS command for use during the download of the operational subscription profile. In step 7, with the help of the acquired download information and the eUICC, the modem securely downloads the operational subscription profile from the SM-DP+ given by the information in the eUICC and / or IoT device. If SM-DS is used, the SM-DP+ information from where to download the subscription profile is first securely obtained from the SM-DS. Upon successful download, the subscription profile is installed and automatically enabled. The provisioning subscription profile then uses a refresh command (step 8), which triggers the modem to detach from the current network and discard all cached information related to the network. The modem then uses the newly installed and enabled operational subscription profile to attach the MNO2 network and obtain connectivity (step 9).

[0094] Next, we will refer to Figure 5 An example is described with a sequence diagram of FIG. 1 , in which an authorization secret is used to ensure secure download of a first operation subscription profile. The authorization secret is generated by a localization server during subscription profile download preparation and provided to the eUICC using the eSIM server using the SIM OTA procedure.

[0095] Step 0: Bootstrapping connectivity service with eSIM server, whose database is populated with EID for each IoT device. The eUICC of each IoT device using the service is configured with a provisioned subscription profile from the eSIM server. This subscription profile is the currently active subscription profile of the eUICC. The eUICC is provisioned with a default SM-DP+ address and / or SM-DS address.

[0096] Step 1: Using the provisioning subscription profile of the eUICC, the IoT device connects to MNO1, performs network access authentication and obtains initial cellular connectivity. Roaming may be used, with the eSIM server acting as the home operator and handling network access authentication. Based on the IMSI provided by the IoT device, MNO1 determines the eSIM server (or MNO3 if the eSIM server and MNO3 have an agreement to use a specific IMSI range). Network access authentication relies on a shared secret shared between the eSIM server and the provisioning subscription profile. This shared secret may be pre-configured as part of the provisioning subscription profile, or may be derived by the subscription module (and the eSIM server) based on the eUICC private key-public key pair and the eSIM server private key-public key pair, where the eSIM server's public key is part of the provisioning subscription profile. In the latter case, the provisioning subscription profile is configured with / includes the eSIM server public key, and the eSIM server database contains the EID and public key of each IoT device using the eSIM server (e.g., the eSIM server database contains an eUICC certificate, which includes the eUICC public key). As is known in the art, an eUICC certificate is a certificate issued by the EUM for a specific eUICC. In order to select the correct key and trigger localization in step 2, the eSIM server determines the EID of the eUICC. This can be done based on the IMSI, for example, the mapping between the IMSI and the EID is saved in the eSIM server. If the IMSI is randomly selected from a range of IMSIs, the EID can be transmitted from the eUICC to the eSIM server during AKA authentication, as described in further detail below. In another example, the EID is encoded into the IMSI. For example, in the case of 5G, the EID can be sent (in encrypted form) as part of or together with the Subscription Hidden Identifier (SUCI).

[0097] Step 2: The eSIM server requests the implementation of localization. The EID of the IoT device's eUICC and optionally the Mobile Country Code (MCC) of MNO1 (the country where the IoT device is located) are provided as input. The eSIM server does not necessarily interact directly with the entity implementing localization as shown here.

[0098] Step 3: Implement the localization mechanism and identify the MNO that provides the operational subscription profile, denoted as MNO2 in the figure.

[0099] Step 4: The operation subscription profile from the selected MNO needs to be prepared for download in step 4. The authorization secret for the operation subscription profile download preparation is randomly generated by the localization server.

[0100] Step 5: The localization server interacts with the SM-DP+ directly or via the MNO / CSP to prepare the subscription profile for download. The authorization secret is provided to the SM-DP+ along with the EID. If SM-DS is to be used, an event is registered at the SM-DS, including the authorization secret, EID, SM-DP+ information such as address and matching ID. The SM-DS here is the same as the SM-DS configured in the eUICC. If SM-DS is not used, the SM-DP+ here is the same as the default SM-DP+ configured in the IoT device.

[0101] Step 6: The localization server provides the authorization secret to the eSIM server.

[0102] Step 7: Using the SIM OTA procedure, the eSIM server provides the authorization secret to the eUICC's provisioning subscription profile. The shared secret between the eSIM server and the provisioning subscription profile for protecting the SIM OTA procedure may be pre-configured as part of the provisioning subscription profile, or may be derived by the provisioning subscription profile (and the eSIM server) based on the eUICC private key-public key and the eSIM server private key-public key pair.

[0103] Step 8: With the help of the eUICC OS command, the eUICC stores the authorization secret into the ISD-R security domain for use during the download of the operational subscription profile.

[0104] Step 9: The modem determines that the eUICC is ready for subscription profile download.

[0105] Step 10: The modem downloads the subscription profile from the default SM-DP+ with the help of the eUICC, where the eUICC determines that the download is authorized using the authorization secret as explained previously. If SM-DS is used, the SM-DP+ information from where to download the subscription profile is first securely obtained from the SM-DS, where the eUICC determines that the download of the SM-DP+ information obtained from the SM-DS is authorized using the authorization secret. Upon successful authentication, the subscription profile is installed and automatically activated.

[0106] Step 11: The eUICC uses a Refresh command which triggers the modem to detach from the current network and discard all cached information related to that network.

[0107] Step 12: The modem attaches the MNO2 network and gains connectivity using the newly installed and enabled operational subscription profile.

[0108] In step 0, the SM-DP + address and / or SM-DS address may be configured in the IoT device during device (or modem module) manufacturing, for example, in the modem, rather than in the eUICC during eUICC manufacturing or personalization. This allows for later configuration of the SM-DP + / SM-DS to be used during the first subscription profile download. The SM-DP + / SM-DS address to be used in step 7 may also be provided together with the authorization secret.

[0109] As a variation of this example, the IoT device may belong to a batch of IoT devices, and when the IoT device first connects, a set of subscription profiles has been prepared for it to download. Figure 6 A sequence diagram in is provided to illustrate this variant and where the authorization secret is used.

[0110] Figure 6 The steps in the sequence diagram are the same as Figure 5 The steps for the sequence diagram in are the same except for the following.

[0111] Step 1: The localization server generates authorization secrets for a batch of IoT devices and stores the authorization secrets in the database.

[0112] Step 2: This step is the same as Figure 5 Same as step 5 of the sequence diagram in .

[0113] Step 3: See Figure 5 Step 1 of the sequence diagram.

[0114] Step 4: The eSIM server requests the localization server for the authorization secret for the EID obtained in step 3.

[0115] Step 5: The localization server obtains the authorization secret for the specific EID from its database.

[0116] Next, we will refer to Figure 7 An example is described in a sequence diagram of , wherein during the operation subscription profile download, the SM-DP+ / SM-DS information in the eUICC is used to verify the information obtained from the SM-DP+ and SM-DS (if used) to determine that the operation subscription profile download is authorized as described above, ensuring the secure download of the first operation subscription profile. The SM-DP+ / SM-DS information is selected by the communication device using the unsigned download and installation data in the device pointing to the SM-DS or SM-DP+ information in the eUICC. The SM-DS / SM-DP+ information defines the download information and is determined by the localization server during the subscription profile download preparation and provided to the eUICC using the eSIM server using the SIM OTA process. In the case of providing SM-DP+ information, the information may also include a matching ID.

[0117] Figure 7 The steps in the sequence diagram are the same as Figure 5 The steps in the sequence diagram are the same as in , except for the following.

[0118] Step 0: The database of the eSIM server is populated with the EID of each IoT device using the eSIM server. The eUICC of each IoT device using the service is configured with a provisioned subscription profile from the eSIM server provider. This subscription profile is the currently active subscription profile of the eUICC.

[0119] Step 4: Figure 7 Not implemented in the sequence diagram Figure 5 Step 4 of the sequence diagram.

[0120] Step 6: The localization server returns SM-DP+ information or SM-DS information to the eSIM server. The information includes the SM-DP+ / SM-DS OID and may also include an address. In the case of providing SM-DP+ information, the information may also include a matching ID that identifies the subscription profile for download at the SM-DP+. Optionally, the ICCID may be used to uniquely identify the subscription profile.

[0121] Step 7: Using the SIM OTA procedure, the eSIM server provides the SM-DP + / SM-DS information to the provisioning subscription profile of the eUICC. The shared secret between the eSIM server and the provisioning subscription profile for protecting the SIM OTA procedure may be pre-configured as part of the provisioning subscription profile, or may be derived by the provisioning subscription profile (and the eSIM server) based on the eUICC private key-public key and the eSIM server private key-public key pair.

[0122] Step 8: With the help of the eUICC OS command, the eUICC stores the SM-DP+ / SM-DS information into the ISD-R security domain for use during the download operation subscription profile.

[0123] Step 10: The modem downloads the subscription profile from the SM-DP+ with the help of the eUICC, where the eUICC uses the SM-DP+ / SM-DS information in the eUICC to verify the information obtained from the SM-DP+ / SM-DS during the subscription profile download operation. If SM-DS is used, the SM-DP+ information from where to download the subscription profile is first securely obtained from the SM-DS. The SM-DP+ information is used by the eUICC to verify the information obtained from the SM-DP+ and from the IoT device to prevent fraudulent subscription profile download, installation and activation. For example, the SM-DP+ OID, address and matching identifier provided to the eUICC are checked according to the information obtained in step 7. Upon successful matching, the subscription profile is downloaded, installed and automatically activated.

[0124] Figure 6 A variant in which the IoT device belongs to a batch of IoT devices and a set of operational subscription profiles has been prepared for it for download when the IoT device is connected for the first time is also applicable to the case where the SM-DP+ / SM-DS information stored in the eUICC is used to ensure the security of the subscription profile download and to verify the information obtained from the SM-DP+ / SM-DS during the operational subscription profile download, where the SM-DP+ / SM-DS information is obtained by the eUICC via the SIM OTA process.

[0125] Next, we will refer to Figure 8 An example is described with a sequence diagram of a first operation subscription profile secure download is ensured using an authorization secret to determine that the operation subscription profile download is authorized as described above, and wherein the authorization secret is generated by a localization server during subscription profile download preparation and provided to the eUICC using an eSIM server. In this example, the authorization secret is delivered as part of running the AKA protocol.

[0126] The transfer of the authorization secret to the eUICC is performed as part of establishing initial cellular connectivity for the IoT device.

[0127] Step 0: With Figure 5 Same as step 0 in the sequence diagram in .

[0128] Step 1: To attach to the network when the IoT device wakes up for the first time, the device’s modem reads the IMSI from the eUICC.

[0129] Step 2: The eUICC's provisioning subscription profile provides the modem with the IMSI. The provisioning subscription profile may be unique for each IoT device and is configured with a unique IMSI returned. Optionally, a provisioning subscription profile that is common to a large group of IoT devices is used. The subscription profile may contain one or more IMSI ranges from which the provisioning subscription profile randomly selects the IMSI to use. In another alternative, the provisioning subscription profile uses an IMSI range in which the MCC+MNC digits and possibly a few more digits are fixed (preconfigured in the provisioning subscription profile) and the remaining IMSI digits are derived from the eUICC's EID. For example, the remaining digits are assigned as a truncated SHA-256 hash of the EID. The EID is obtained through the subscription profile using the eUICCOS function.

[0130] Step 3: The modem scans for available networks to attach to. Using the MCC+MNC from the IMSI, the modem analyzes the available networks and determines that MNO1 is a suitable network. The modem then requests to attach to the selected network.

[0131] Step 4: Provide the identity request from the network.

[0132] Step 5: The modem provides the IMSI in response.

[0133] Step 6: MNO1 analyzes the IMSI to determine the home mobile network.

[0134] Step 7: Roaming request is made to the home network. The home network is the eSIM server acting as an MVNO or the home network is another mobile network operator MNO3, where the IMSI range to which the IMSI belongs is handled by the eSIM server. The eSIM server then controls the HSS or similar entity.

[0135] Step 8: The eSIM server determines the EID of the eUICC of the IoT device. In one alternative, this is implemented based on the received IMSI using a preconfigured mapping between IMSI and EID stored in the eSIM server database. For example, such a database can be used when a unique IMSI for each provisioning subscription profile is used, or when the provisioning subscription profile encodes the EID into the IMSI. When the EID is encoded into the IMSI, there may be several EIDs encoded into the same IMSI, resulting in several entries in the database being valid. The frequency with which such conflicts occur depends on the size of the IMSI range and the number of IoT devices currently using the service. In the event of a conflict, the complete EID value must be provided to the eSIM server from the provisioning subscription profile. This can be implemented via the AKA protocol and is further described below. In addition, if in step 2, the IMSI is randomly selected from the IMSI range by the provisioning subscription profile, the EID is transmitted from / to the eSIM server via the AKA protocol.

[0136] Step 9: With Figure 5 Same as step 2 in the sequence diagram in .

[0137] Step 10: With Figure 5 Same as step 3 in the sequence diagram in .

[0138] Step 11: With Figure 5 Same as step 4 in the sequence diagram in .

[0139] Step 12: With Figure 5 Same as step 5 in the sequence diagram in .

[0140] Step 13: With Figure 5 Same as step 6 in the sequence diagram in .

[0141] Step 14: Network access authentication is performed using AV and following the AKA procedure based on the cellular technology used (with small variations depending on the generation of the 3GPP cellular network). The eSIM server's HSS and the eUICC's provisioning subscription profile use behaviors modified according to the following description, but the behavior is transparent to the visited network (MNO1) and the data and message formats follow the cellular standard used. As part of the network access authentication, the eUICC's provisioning subscription profile obtains the authorization secret.

[0142] Step 14: With Figure 5 Same as step 8 in the sequence diagram in .

[0143] Step 15: With Figure 5 Same as step 9 in the sequence diagram in .

[0144] Step 16: With Figure 5 Same as step 10 in the sequence diagram in .

[0145] Step 17: With Figure 5 Same as step 11 in the sequence diagram in .

[0146] Step 18: With Figure 5 Same as step 12 in the sequence diagram in .

[0147] Reference below Fig. 9 The sequence diagram of , will disclose an example for transferring the authorization secret from the eSIM server to the provisioning protocol using the AKA protocol. This example is based on Figure 8 Follow step 14 in the

[0148] The authorization secret is transmitted as part of the authentication vector prepared by the eSIM server. The authorization secret is both encrypted and intact during transmission. The keys used for encryption and integrity protection are derived from the shared secret between the provisioning subscription profile and the eSIM server. Preferably, the shared secret is an ECDH shared secret derived from the eSIM server private key-public key pair and the eUICC private key-public key pair for use with the eSIM. The eSIM server's HSS stores the eSIM server private key and retrieves the key from the key stored in its database that matches the eSIM server's private key. Figure 8 The eUICC public key required for calculating the shared secret is obtained from the eUICC certificate corresponding to the EID determined in step 8. The eUICC stores the eSIM server public key and uses the eUICC OS function to derive the shared secret, using the eUICC private key and the stored eSIM server public key. Optionally, the provisioning subscription profile saves a global secret, and the EID can be used to derive a shared secret specific to the eUICC from the global secret.

[0149] In order to make the encryption keys and MAC keys session-related, these keys are derived from a shared secret (ECDH or derived from a global secret) and a seed. As a seed, a random value can be used or a challenge delivered as a RAND value as part of the authentication vector. RAND can be concatenated with a string, for example, "NAA" (see below) for separating key derivations for different purposes. For example, the ANSI-16.63-KDF algorithm can be used for key derivation. The encryption algorithm and MAC algorithm used for encryption and integrity protection of the IMSI can be, for example, the AES and HMAC-SHA-256 algorithms, respectively. The MAC algorithm can be replaced by the Milenage f1 function, in which the IMSI and the flag replace the SQN and AMF fields given as input. The following substeps of step 14 are implemented, in which the authentication vector is first created and then the AKA protocol is implemented.

[0150] Step 14a: The HSS of the eSIM server generates a random value RAND for authentication.

[0151] Step 14b: The eSIM server uses RAND and a shared secret (ECDH or a secret derived from a global secret) to derive encryption keys K_enc and K_mac according to the above description. In addition, temporary values ​​of Ki and OPc are derived (derived using the same key), denoted as Ki_tmp and OPc_tmp, for network access authentication. In other words, the shared secret can be derived using the eUICC public key and the eSIM bootstrapping connectivity service private key.

[0152] Step 14c: Encrypt the authorization secret using K_enc and protect integrity by computing a MAC using K_mac on the encrypted data. The concatenation of the encrypted data and the MAC forms the AUTN value of the authentication vector. AUTN = (encrypted data | MAC).

[0153] Step 14d: Using RAND, Ki_tmp and OPc_tmp as input, calculate the XRES, CK and IK values ​​according to the normal network access authentication algorithm.

[0154] Step 14e: Deliver the authentication vectors (RAND, AUTN, XRES, CK, IK) from the eSIM server to the visited mobile network (ie MNO1).

[0155] Step 14f: The access network sends RAND and AUTN to the IoT device’s modem as an authentication challenge.

[0156] Step 14g: The modem invokes the eUICC Authenticate command, providing RAND and AUTN.

[0157] Step 14h: The eUICC derives the shared secret according to the above, and derives K_enc, K_mac, Ki_tmp and OPc_tmp according to the above description.

[0158] Step 14i: The eUICC extracts the MAC from the AUTN and verifies the MAC using K_mac. If the MAC verification succeeds, the encrypted data of the AUTN is extracted and decrypted to obtain the authorization secret.

[0159] Step 14j: Using RAND, Ki_tmp and OPc_tmp as input, the eUICC calculates RES, CK and IK according to the normal network access authentication algorithm.

[0160] Step 14k: Provide RES, CK, and IK as a response to the Authenticate command.

[0161] Step 141: The modem returns a RES to the visited network as a response to the authentication challenge.

[0162] Step 14m: The visited network verifies that RES is equal to XRES, and if this is the case, the authentication is successful.

[0163] The size of the authorization secret may vary, for example, 64 bits. The size of the AUTN parameter may be 128 bits. For example, the encryption may be implemented using the AES encryption algorithm as follows: by first encrypting a string (e.g., "AUTN") using K_enc, truncating the result to the size of the data to be encrypted (e.g., 64 bits), and then applying a logical exclusive OR (XOR) between the truncated result and the data to be encrypted to obtain the encrypted data. In pseudocode, this may be represented as follows (where the final size is 64 bits):

[0164] E(Authorization Secret) = (Authorization Secret) XOR E("AUTN")_trunc

[0165] The MAC portion of the AUTN may be represented by 64 bits, for example, based on HMAC-SHA-256 using K_mac, and truncated to 64 bits. For example, the full 128-bit AUTN may then be a 64-bit encrypted authorization secret followed by a 64-bit MAC.

[0166] In case a larger authorization secret (e.g. 128 bits) is used, the first half can be sent in the first AUTN, and the provisioning subscription profile (even if it successfully receives the first part) signals a synchronization error, and a new authentication is performed using a new authentication vector (with a new RAND), where the second half of the authorization secret is communicated to the provisioning subscription profile. This principle can be generated to accommodate even larger authorization secrets.

[0167] Next, we will refer to Fig.10 An example is described with a sequence diagram of FIG. 1 , where an IMSI is randomly selected according to a provisioning subscription profile and the EID is transmitted to the eSIM server via the AKA protocol. Fig.10 Describes this special case in detail Figure 8 Follow step 8 in the

[0168] Step 8a: The HSS of the eSIM server generates a random value RAND for the AKA protocol.

[0169] Step 8b: The eSIM server uses RAND and the global secret shared with the provisioning subscription profile to derive the encryption key K_enc. In addition, temporary values ​​of Ki (subscriber key) and OPc (key derived with Ki and operator code as input) are derived (using the same key), denoted as Ki_tmp and OPc_tmp, for network access authentication.

[0170] Step 8c: Using RAND, Ki_tmp and OPc_tmp as input, the values ​​of the authentication token (AUTN), expected response (XRES), cryptographic key (CK) and integrity key (IK) are calculated according to the normal network access authentication algorithm.

[0171] Step 8d: Deliver the authentication vectors (RAND, AUTN, XRES, CK, IK) from the eSIM server to the visited mobile network (MNO1).

[0172] Step 8e: The access network sends RAND and AUTN to the IoT device’s modem as an authentication challenge.

[0173] Step 8f: The modem invokes the eUICC Authenticate command, providing RAND and AUTN.

[0174] Step 8g: The provisioning subscription profile uses RAND and the shared secret to derive K_enc, Ki_tmp and OPc_tmp.

[0175] Step 8h: The provisioning subscription profile verifies AUTN using RAND, Ki_tmp and OPc_tmp.

[0176] Step 8i: Upon successful authentication, the EID is encrypted using K_enc and the encrypted data is formatted into an AUTS message.

[0177] Step 8j: Provisioning the subscription profile enables the eUICC to signal a synchronization error and provide AUTS as a response to the request in step 8f.

[0178] Step 8k: The modem responds with a Sync Error to the access network and provides AUTS.

[0179] Step 81: The visited network responds to the eSIM server with a synchronization error and provides AUTS.

[0180] Step 8m: The eSIM server decrypts the encrypted part of AUTS using K_enc derived in step 8b to obtain the EID.

[0181] In other words, AUTS is used here to transmit / obtain EID rather than to indicate a true synchronization error, even though step 8j mentioned above signaling a synchronization error.

[0182] The EID can be represented by 32 digits. In order to encode the EID, one possible method is to combine 3 digits together and encode them as a number between 0-999 represented by 10 bits. Then, the 32-digit EID can be represented by 110 digits, but since the last 2 digits of the EID are check digits, 30 digits (100 bits) are sufficient. The size of the AUTS parameter can be 112 bits. For example, the encryption can be implemented as follows using the AES encryption algorithm: by first encrypting the string (e.g., "AUTS" of the EID) using K_enc, truncating the result to the size of the data to be encrypted, and then implementing an XOR operation between the truncated result and the number to be encrypted to obtain the encrypted data.

[0183] In pseudocode this can be represented as follows (where the final size is 100 bits):

[0184] E(EID)=EID XOR E("AUTS")_trunc

[0185] For example, a complete 112-bit AUTS may be a 100-bit encrypted EID followed by 12 random bits.

[0186] The shared secret used to derive K_enc may be a static global secret between the provisioning subscription profile and the eSIM server. Even if RAND is used to derive K_enc so that they are session specific, it may be desirable to derive the shared secret using session specific keys. In the case of 5G cellular connectivity and the use of SUCI, the eSIM server private-public key pair and the ephemeral key pair generated by the eUICC for SUCI protection may be used to establish an ECDH shared secret from which K_enc may be derived.

[0187] Next, some aspects of IMSI conflicts will be disclosed. Fig. 9 The MAC verification in step 14i of may fail for different reasons. One reason is that there is a conflict of IMSIs in the case where the EID is encoded into the IMSI, although this should rarely happen. Having an IMSI conflict means that there is at least one EID in the eSIM server database that has the same IMSI as the EID. Figure 8The eSIM server HSS may have selected the same IMSI as the one determined by the eUICC in step 8 of the MAC verification and the wrong entry in the database (i.e. the wrong EID) has been selected by the eSIM server HSS. This results in the wrong shared secret being derived and the MAC verification failing. The provisioning subscription profile then needs to send its EID to the eSIM server. Another reason for a MAC failure is that the AUTN value has been modified in some way during transmission. The provisioning server cannot distinguish between these two cases and will therefore always provide the EID in case of a MAC failure.

[0188] The eSIM server will know when there is an IMSI conflict and there is a risk of selecting the wrong EID. In the case of an IMSI conflict, there is more than one entry in the eSIM server database that matches Figure 8 The localization process can help select the correct EID (i.e. the correct entry). The localization rule can be such that a given EID range belongs to IoT devices from a specific enterprise for which, based on a pre-negotiated MNO contract, a specific set of countries are valid where the IoT device may be deployed. For example, assume that the IoT device connects via an access network in a specific country and from the IMSI it is inferred that there are two possible EIDs. However, according to the localization rule, only one EID is in the EID range from the enterprise (where localization is possible for the MNO in the specific country in question), which means that this EID should be selected.

[0189] Depending on the relationship between the eSIM server and the localization server, localization can be utilized when selecting an EID. Fig.10 A sequence diagram of , where a conflict occurs.

[0190] Step 8: There is more than one entry in the database (ie more than one EID) matching the received IMSI.

[0191] Step 9: Provide the entire list of possible EIDs to the localization server in a localization request.

[0192] Step 10: The localization server performs localization to determine the MNO.

[0193] Step 11: The localization server selects a suitable EID from the list and generates an authorization secret for it.

[0194] Steps 12a, 12b: Prepare an operational subscription profile for the selected EID (denoted as EID1) for downloading.

[0195] Step 13: Provide the authorization secret from the localization server to the eSIM server.

[0196] Step 14: The eSIM server executes the AKA protocol (according to Figure 8 14a-14h) in which the authorization secret is transmitted to the provisioning subscription profile. Fig. 9 14i), and the EID is returned in an AUTS formatted message (in encrypted form) to the eSIM server (where the same Fig. 9 Request re-localization from the localization server. Repeat steps 9 to 13 using the new EID received from the eUICC (referred to as EID2), and generate a new authorization secret and return it to the eSIM server. Then, according to step 14 (as shown in Figure 8 As shown) and step 15, the authorization secret is delivered to the provisioning subscription profile and stored in ISD-R. A new authentication vector with a new RAND is generated.

[0197] Using the SIM OTA procedure to securely transfer information to the eUICC allows more information to be provided than when the AKA protocol is used. Figure 5 and Figure 6 In the disclosed example, the eUICC may not need to be provisioned with a default SM-DP+ address. The address to the SM-DP+ (or to the SM-DS, if this option is used) may be provided to the eUICC along with the authorization secret using the SIM OTA procedure.

[0198] The size of the SM-DP+ / SM-DS OID is typically small enough to be provided using the AKA protocol. For example, the SM-DS OID can be securely provided to the eUICC using the AKA protocol. As long as the SM-DS address is configured for use by the IPA, such as configured in the IoT device during device production, a secure subscription profile download can be implemented, where the eUICC uses the SM-DS information in the eUICC to verify the information obtained from the SM-DS during the operational subscription profile download. Similarly, the combination of the SM-DP+ OID and, for example, the ICCID can be provided to the eUICC via the AKA protocol. As long as the SM-DP+ address is configured for use by the IPA, a secure operational subscription profile download can be implemented by verifying the information obtained from the SM-DP+ during the profile download.

[0199] As already mentioned above, the SIM OTA procedure is less restricted in terms of the size of information that can be transmitted from the eSIM server to the eUICC than using the AKA protocol. On the other hand, the SIM OTA procedure relies on the use of Short Message Service (SMS) messages or HTTPS as a bearer for the information, which means that the SIM OTA procedure may not be suitable for low-power IoT devices connected via LPWA networks such as narrowband (NB) IoT networks. The AKA protocol can be used for the transmission of information for all IoT devices that support the required protocol. In addition, in addition to HTTPS over the Transmission Control Protocol (TCP), the Constrained Application Protocol (CoAP) over Datagram Transport Layer Security (DTLS) over the User Datagram Protocol (UDP) can also be used for low-power IoT devices, allowing the SIM OTA procedure to be used for low-power IoT devices as well.

[0200] Fig.12 The components of the subscriber module 1200 according to an embodiment are schematically shown in the form of a plurality of functional units. Using a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc. (which is capable of executing the program stored in the computer program product 1610a (such as Fig.16 The processing circuit 1210 may be provided as any combination of one or more of the software instructions in the storage medium 1230 (e.g., as shown in FIG. 1 ) or the like. The processing circuit 1210 may also be provided as at least one application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0201] In particular, the processing circuit 1210 is configured to cause the subscriber module 1200 to implement a set of operations or steps as disclosed above. For example, the storage medium 1230 may store the set of operations, and the processing circuit 1210 may be configured to retrieve the set of operations from the storage medium 1230 to cause the subscriber module 1200 to implement the set of operations. The set of operations may be provided as a set of executable instructions. Therefore, the processing circuit 1210 is thereby arranged to perform the method disclosed herein.

[0202] The storage medium 1230 may also include a persistent memory, for example, which may be any single one or a combination of magnetic memory, optical memory, solid-state memory, or even a remotely mounted memory.

[0203] The subscriber module 1200 may also include a communication interface 1220 for communicating with other entities, functions, nodes and devices, such as Figure 1 As such, communication interface 1220 may include one or more transmitters and receivers, including analog and digital components.

[0204] The processing circuit 1210 controls the general operation of the subscriber module 1200, for example, by sending data and control signals to the communication interface 1220 and the storage medium 1230, by receiving data and reports from the communication interface 1220, and by retrieving data and instructions from the storage medium 1230. Other components of the subscriber module 1200 and related functions are omitted in order not to obscure the concepts presented herein.

[0205] Fig.13 The components of the subscriber module 1200 according to an embodiment are schematically shown in the form of a plurality of functional modules. Fig.13 The subscriber module 1200 includes multiple functional modules; the acquisition module 1210a is configured to implement step S102, the download module 1210b is configured to implement step S104, and the installation module 1210c is configured to implement step S106. Fig.13 The subscriber module 1200 may also include a plurality of optional functional modules, such as an enabling module 1210d configured to implement step S108. In general, each functional module 1210a: 1210d may be implemented in hardware or software. Preferably, one or more or all functional modules 1210a: 1210d may be implemented by the processing circuit 1210, possibly in cooperation with the communication interface 1220 and / or the storage medium 1230. Therefore, the processing circuit 1210 may be arranged to retrieve instructions provided by the functional modules 1210a: 1210d from the storage medium 1230 and execute these instructions, thereby implementing any steps of the subscriber module 1200 disclosed herein.

[0206] Fig.14 The components of the eSIM server 1400 according to an embodiment are schematically shown in the form of a plurality of functional units. Using a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc. (which is capable of executing the program stored in the computer program product 1610b (such as Fig.16 The processing circuit 1410 may be provided as any combination of one or more of software instructions in the form of a storage medium 1430 (e.g., as shown in FIG. 14 ) (e.g., in the form of software instructions in the storage medium 1430). The processing circuit 1410 may also be provided as at least one application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0207] In particular, the processing circuit 1410 is configured to cause the eSIM server 1400 to implement a set of operations or steps as disclosed above. For example, the storage medium 1430 may store the set of operations, and the processing circuit 1410 may be configured to retrieve the set of operations from the storage medium 1430 to cause the eSIM server 1400 to implement the set of operations. The set of operations may be provided as a set of executable instructions. Therefore, the processing circuit 1410 is thereby arranged to perform the method disclosed herein.

[0208] The storage medium 1430 may also include a persistent memory, for example, which may be any single one or a combination of magnetic memory, optical memory, solid-state memory, or even a remotely mounted memory.

[0209] The eSIM server 1400 may also include a communication interface 1420 for communicating with other entities, functions, nodes and devices, such as Figure 1 As such, communication interface 1420 may include one or more transmitters and receivers, including analog and digital components.

[0210] The processing circuit 1410 controls the general operation of the eSIM server 1400, for example, by sending data and control signals to the communication interface 1420 and the storage medium 1430, by receiving data and reports from the communication interface 1420, and by retrieving data and instructions from the storage medium 1430. In order not to obscure the concepts presented herein, other components of the eSIM server 1400 and related functions are omitted.

[0211] Fig.15 The components of the eSIM server 1400 according to the embodiment are schematically illustrated in the form of a plurality of functional modules. Fig.15 The eSIM server 1400 includes multiple functional modules; the acquisition module 1410a is configured to implement step S202, and the providing module 1410c is configured to implement step S206. Fig.15 The eSIM server 1400 may also include a plurality of optional functional modules, such as a determination module 1410b configured to implement step S204. In general, each functional module 1410a: 1410c may be implemented in hardware or software. Preferably, one or more or all functional modules 1410a: 1410c may be implemented by the processing circuit 1410, possibly in cooperation with the communication interface 1420 and / or the storage medium 1430. Therefore, the processing circuit 1410 may be arranged to retrieve instructions provided by the functional modules 1410a: 1410c from the storage medium 1430 and execute these instructions, thereby implementing any steps of the eSIM server 1400 disclosed herein.

[0212] Fig.16An example of a computer program product 1610a, 1610b including a computer readable component 1630 is shown. On the computer readable component 1630, a computer program 1620a may be stored, which may cause the processing circuit 1210 and its operably coupled entities and devices (such as the communication interface 1220 and the storage medium 1230) to perform a method according to the embodiments described herein. Therefore, the computer program 1620a and / or the computer program product 1610a may provide a component for implementing any steps of the subscriber module 1200 disclosed herein. On the computer readable component 1630, a computer program 1620b may be stored, which may cause the processing circuit 1410 and its operably coupled entities and devices (such as the communication interface 1420 and the storage medium 1430) to perform a method according to the embodiments described herein. Therefore, the computer program 1620b and / or the computer program product 1610b may provide a component for implementing any steps of the eSIM server 1400 disclosed herein.

[0213] exist Fig.16 In the example of , the computer program products 1610a, 1610b are shown as optical disks, such as CD (Compact Disk) or DVD (Digital Versatile Disk) or Blu-ray disks. The computer program products 1610a, 1610b may 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, may be embodied 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. Thus, although the computer programs 1620a, 1620b are schematically shown here as tracks on the depicted optical disks, the computer programs 1620a, 1620b may be stored in any manner suitable for the computer program products 1610a, 1610b.

[0214] The inventive concept has mainly been described above with reference to a few embodiments. However, as readily appreciated by a person skilled in the art, other embodiments than those disclosed above are equally possible within the scope of the inventive concept as defined by the claims.

Claims

1. A method for operating subscription profile download and installation, the method being implemented by a subscriber module (1200) provided in a communication device (180), the subscriber module being provided with subscription data for establishing initial cellular connectivity, the method comprising: obtaining (S102) download information for the operational subscription profile from an eSIM server (1400) and over an initial cellular connectivity connection for the communication device (180), wherein the download information is used by the subscriber module when it is determined that subscription profile download is authorized to the subscriber module, and wherein the subscriber module authenticates the eSIM server using the subscription data during cellular network access authentication to establish the initial cellular connectivity connection; preparing an SM-DP+ entity (150) from an enhanced subscription manager data and downloading (S104) the operational subscription profile according to the download information, wherein the operational subscription profile is downloaded via the initial cellular connectivity connection for the communication device (180); and The operational subscription profile is installed (S106) in the subscriber module (1200).

2. The method according to claim 1, wherein: The method further comprises: When the operational subscription profile has been installed, the operational subscription profile is enabled (S108) in the subscriber module (1200).

3. The method according to claim 1, wherein: The authentication of the eSIM server (1400) is performed using a secret contained in the subscription data or derivable from the subscription data that is shared with the eSIM server.

4. The method according to claim 3, wherein: The subscription data is contained in a provisioning subscription profile installed in the subscriber module (1200).

5. The method according to claim 3, wherein: The subscription data is included as part of a subscriber module operating system, and wherein, when no subscription profile is installed in the subscriber module, the subscriber module (1200) treats the communication device (180) as if a provisioning profile exists using the subscription data.

6. The method according to claim 1, wherein: A secret shared with the eSIM server (1400) is contained in or derivable from the subscription data, the secret being used to ensure that the download information is securely transmitted from the eSIM server to the subscriber module (1200) over the initial cellular connectivity connection for the communication device (180).

7. The method according to claim 3 or claim 6, wherein: Based on a private key of a private key-public key pair of the subscriber module (1200) and a public key of a private key-public key pair of the eSIM server, a secret shared with the eSIM server (1400) can be derived from the subscription data, wherein the public key of the private key-public key pair of the eSIM server is part of the subscription data.

8. The method according to claim 1, wherein: The download information is securely transmitted from the eSIM server (1400) to the subscriber module (1200) using a SIM OTA procedure.

9. The method according to claim 1, wherein: The download information specifies an authorization secret used by the subscriber module (1200) for determining that downloading of the operational subscription profile from the SM-DP+ entity (150) is authorized to the subscriber module, and / or determining that downloading of SM-DP+ information specifying the SM-DD+ entity from which the operational subscription profile is to be downloaded from a subscription manager discovery service SM-DS entity (160) is authorized, and wherein determining that the download is authorized is based on the subscriber module obtaining proof of SM-DP+ / SM-DS knowledge of the authorization secret as obtained during profile download preparation of the operational subscription profile.

10. The method according to claim 1, wherein: The download information identifies an object identifier OID of the SM-DS entity (160) and / or the SM-DP+ entity (150) for use by the subscriber module (1200) when downloading and installing the operational subscription profile.

11. The method according to claim 10, wherein: The SM-DP+ entity (150) from which the operational subscription profile is downloaded is given by the OID when the OID identified by the download information is the OID of the SM-DP+ entity, or is given by the event record received by the subscriber module (1200) from the SM-DS entity (160) when the OID identified by the download information is the OID of the SM-DS entity, and wherein the SM-DS entity is given by the OID identified by the download information.

12. The method according to claim 1, wherein: The download information is obtained using the AKA protocol as part of performing network access authentication when establishing the initial cellular connectivity connection.

13. A method for implementing downloading and installing an operation subscription profile to a subscriber module (1200), the method being implemented by an eSIM server (1400), the method comprising: Obtaining (S202) a trigger for downloading the operation subscription profile to the subscriber module; Download information for the operational subscription profile is provided (S206) to the subscriber module and through an initial cellular connectivity connection for a communication device (180) in which the subscriber module is provided, wherein the download information is destined for the subscriber module to determine that subscription profile download is authorized to the subscriber module, and wherein, during cellular network access authentication to establish the initial cellular connectivity connection, the eSIM server (1400) provides authentication data to the subscriber module (1200) for the subscriber module to authenticate the eSIM server.

14. The method according to claim 13, wherein: The method further comprises: The download information is determined (S204) during profile download preparation of the operational subscription profile.

15. The method according to claim 13, wherein: The authentication data provided by the eSIM server (1400) to the subscriber module is derived using a secret shared with the subscriber module.

16. The method according to claim 13, wherein: The download information is securely communicated from the eSIM server (1400) to the subscriber module (1200) over the initial cellular connectivity connection for the communication device (180) using a secret shared with the subscriber module.

17. The method according to claim 15 or 16, wherein: The secret shared with the subscriber module is based on a public key of a private key-public key pair of the subscriber module (1200) and a private key of a private key-public key pair of the eSIM server (1400).

18. The method according to claim 13, wherein: The download information is securely transmitted from the eSIM server (1400) to the subscriber module (1200) using a SIM OTA procedure.

19. The method according to claim 13, wherein: The download information specifies an authorization secret for use by the subscriber module (1200) to verify that downloading the operational subscription profile from an enhanced subscription manager data preparation SM-DP+ entity (150) is authorized to the subscriber module, and / or to verify that SM-DP+ information obtained by the subscriber module from a subscription manager discovery service SM-DS entity (160) specifying the SM-DP+ entity from which the operational subscription profile is to be downloaded is authorized, and wherein the verification is based on the SM-DP+ entity and / or the SM-DS entity proving to the subscriber module knowledge of the authorization secret as obtained during profile download preparation of the operational subscription profile.

20. The method according to claim 13, wherein: The download information identifies an object identifier OID of the SM-DS entity (160) and / or the SM-DP+ entity (150) for use by the subscriber module (1200) when downloading and installing the operational subscription profile.

21. The method according to claim 20, wherein: The SM-DP+ entity (150) from which the operational subscription profile is downloaded is given by the OID when the OID identified by the download information is the OID of the SM-DD+ entity, or is given by the event record received by the subscriber module (1200) from the SM-DS entity (160) when the OID identified by the download information is the OID of the SM-DS entity, and wherein the SM-DS entity is given by the OID identified by the download information.

22. The method according to claim 13, wherein: The download information is provided as part of performing network access authentication using the AKA protocol when establishing the initial cellular connectivity connection.

23. The method according to claim 22, wherein: The download information is provided in an authentication vector.

24. A subscriber module (1200) for operating subscription profile download and installation, the subscriber module being provided in a communication device (180), the subscriber module being provided with subscription data for establishing initial cellular connectivity, the subscriber module comprising a processing circuit (1210) configured to cause the subscriber module to: obtaining download information for the operational subscription profile from an eSIM server (1400) and through an initial cellular connectivity connection for the communication device, wherein: the download information being used by the subscriber module when it is determined that subscription profile download is authorized to the subscriber module, and wherein the subscriber module authenticates the eSIM server using the subscription data during cellular network access authentication to establish the initial cellular connectivity connection; preparing an SM-DP+ entity (150) from an enhanced subscription manager data and downloading the operational subscription profile according to the download information, wherein the operational subscription profile is downloaded over the initial cellular connectivity connection for the communication device (180); and The operational subscription profile is installed in the subscriber module.

25. A subscriber module (1200) for operating subscription profile download and installation, said subscriber module being provided in a communication device (180), said subscriber module being provided with subscription data for establishing initial cellular connectivity, said subscriber module comprising: an acquisition module (1210a) configured to acquire download information for the operational subscription profile from an eSIM server (1400) and over an initial cellular connectivity connection for the communication device (180), wherein the download information is used by the subscriber module when it is determined that subscription profile download is authorized to the subscriber module, and wherein the subscriber module authenticates the eSIM server using the subscription data during cellular network access authentication to establish the initial cellular connectivity connection; a download module (1210b) configured to prepare an SM-DP+ entity (150) from enhanced subscription manager data and download the operational subscription profile according to the download information, wherein the operational subscription profile is downloaded through the initial cellular connectivity connection for the communication device; and An installation module (1210c) configured to install the operational subscription profile in the subscriber module.

26. The subscriber module (1200) according to claim 24 or 25, further configured to implement the method according to any one of claims 2 to 12.

27. An eSIM server (1400) for implementing download and installation of an operational subscription profile to a subscriber module (1200), the eSIM server comprising a processing circuit (1410) configured to cause the eSIM server to: obtaining a trigger for downloading the operational subscription profile to the subscriber module; and providing download information for the operational subscription profile to the subscriber module and through an initial cellular connectivity connection for a communication device (180) in which the subscriber module is provided, wherein The download information is destined for the subscriber module to determine that subscription profile download is authorized to the subscriber module, and wherein, during cellular network access authentication to establish the initial cellular connectivity connection, the eSIM server provides authentication data to the subscriber module for the subscriber module to authenticate the eSIM server.

28. An eSIM server (1400) for implementing downloading and installing an operation subscription profile to a subscriber module (1200), the eSIM server comprising: an acquisition module (1410a) configured to acquire a trigger for downloading the operational subscription profile to the subscriber module; A providing module (1410c) configured to provide download information for the operational subscription profile to the subscriber module and through an initial cellular connectivity connection for a communication device (180) in which the subscriber module is provided, wherein the download information is destined for the subscriber module to determine that subscription profile download is authorized to the subscriber module, and wherein, during cellular network access authentication to establish the initial cellular connectivity connection, the eSIM server provides authentication data to the subscriber module for the subscriber module to authenticate the eSIM server.

29. The eSIM server (1400) according to claim 27 or 28, further configured to implement the method according to any one of claims 14 to 23.

30. A computer program (1620a) for operating subscription profile download and installation, the computer program comprising computer code, providing a subscriber module in a communication device (180), the subscriber module being provided with subscription data for establishing initial cellular connectivity, the computer code when executed on processing circuitry of the subscriber module (1200) causing the subscriber module to: obtaining download information for the operational subscription profile from an eSIM server (1400) and through an initial cellular connectivity connection for the communication device, wherein: the download information being used by the subscriber module when it is determined that subscription profile download is authorized to the subscriber module, and wherein the subscriber module authenticates the eSIM server using the subscription data during cellular network access authentication to establish the initial cellular connectivity connection; preparing an SM-DP+ entity (150) from an enhanced subscription manager data and downloading the operational subscription profile according to the download information, wherein the operational subscription profile is downloaded over the initial cellular connectivity connection for the communication device; and The operational subscription profile is installed in the subscriber module.

31. A computer program (1620b) for implementing the operation of downloading and installing a subscription profile to a subscriber module (1200), the computer program comprising computer code which, when executed on a processing circuit of an eSIM server (1400), causes the eSIM server to: obtaining a trigger for downloading the operational subscription profile to the subscriber module; and providing download information for the operational subscription profile to the subscriber module and through an initial cellular connectivity connection for a communication device (180) in which the subscriber module is provided, wherein The download information is destined for the subscriber module to determine that subscription profile download is authorized to the subscriber module, and wherein, during cellular network access authentication to establish the initial cellular connectivity connection, the eSIM server provides authentication data to the subscriber module for the subscriber module to authenticate the eSIM server.

32. A computer program product (1610a, 1610b) comprising a computer program (1620a, 1620b) according to at least one of claims 30 and 31 and a computer-readable storage medium on which the computer program is stored.

33. A communication device (180) comprising a subscriber module (1200) according to any one of claims 24-26.

34. The communication device (180) according to claim 33, which is an IoT device.

Images