Method for managing an application for electronic identification of a user

Abstract

The invention relates to a method (100) for managing an application for electronic identification of a user of a mobile terminal (2) having a subscriber identity module (1) in a mobile network. The method (100) comprises the following method steps: - sending (103) a request to create a subscription profile with the application to a subscription manager data preparation (SM-DP+) server of the mobile network; - creating (104) a subscription profile with the application for electronic identification of the user, wherein the creation of the subscription profile comprises creating a private asymmetric personalisation key associated with the subscription profile, and creating a public asymmetric personalisation key associated with the subscription profile for the application; - sending (106) the public asymmetric personalisation key to a server of the mobile network operator (MNO) or to an identification provider server; - encrypting (107) identity data of the user by means of the public asymmetric personalisation key; and - distributing (109) the subscription profile with the application, and the private asymmetric personalisation key to the mobile terminal (2).

Description

[0001] Method for managing an application for electronic identification of a user

[0002] TECHNICAL FIELD OF THE INVENTION

[0003] The invention relates to a method for managing an application for electronically identifying a user of a mobile terminal having a subscriber identity module in a mobile radio network.

[0004] To use the services of a communications network, a terminal device, such as a mobile phone or a machine-to-machine device (M2M device for short), or a device for using Internet of Things (IoT) technologies, contains a subscriber identity module. The term "subscriber identity module" is used in this description as a synonym for the terms "UICC", "eUICC", "chip card", "iUICC", "integrated eUICC", "integrated secure element", "embedded secure element", "secure element" or "SIM". The subscriber identity module typically comprises one or more subscription profiles designed to authenticate the subscriber identity module or a device in which the subscriber identity module is operated, such as a mobile terminal, to the mobile network.

[0005] The application for electronic identification can be implemented, for example, as a computer program, particularly as an applet. Electronic identification refers to digital proof of identity of citizens or organizations. Electronic identification is also referred to as eID. Electronic identification can include, among other things, an eID registration number, a last name, a first name, a date of birth, a gender, a place of birth, a nationality, and / or a facial image of the person to be identified. In the present method, the person to be identified corresponds to the user of the terminal device.

[0006] From US 20210342462 A1, a subscriber identity module is known with an embedded universal integrated circuit card which receives and decrypts an encrypted profile and is configured to generate random numbers using memory noise in order to derive private and public keys therefrom, which are then securely stored on the card.

[0007] TECHNICAL BACKGROUND

[0008] When a user of a terminal device concludes a mobile phone contract, the user's identity data is usually collected by the mobile network operator (MNO) or by an identification service commissioned by the mobile network operator. The user's identity data is available to the mobile network operator (MNO) or the identification service at the time the data is collected. Governments need to provide their users with a simple and secure application for electronic identification of the user, such as an eID applet, which can be executed on the user's terminal device. The data for the application should be provided using the identity data available to the mobile network operator or the identification service. Such an eID applet can serve as an electronic ID card.

[0009] SUMMARY OF THE INVENTION

[0010] The invention is based on the object of creating a method with which it is possible to provide an application for the electronic identification of the user in a simple and secure manner.

[0011] It is a further object of the present invention to provide the user with a simple and data protection-compliant possibility for personalizing the application.

[0012] This object is achieved by the features described in the independent patent claims. Advantageous embodiments of the invention are specified in the dependent claims.

[0013] The method according to the invention for managing an application for electronic identification of a user of a mobile terminal having a subscriber identity module in a mobile network comprises the following method steps:

[0014] - Sending a request to create a subscription profile using the application for electronic identification of the user to a Subscription Manager Data Preparation (SM-DP+) server of the mobile network;

[0015] - Creating a subscription profile with the application for electronic identification of the user, wherein creating the subscription profile comprises creating a private asymmetric personalization key associated with the subscription profile and a public asymmetric personalization key associated with the subscription profile for the application for electronic identification of the user;

[0016] - Sending the public asymmetric personalisation key to a server of the mobile network operator (MNO) or to a server of an identification provider;

[0017] - Encrypting the user's identity data using the public asymmetric personalization key;

[0018] - Distributing the subscription profile with the application for electronic identification of the user and the private asymmetric personalisation key to the mobile device; and

[0019] - Distributing the application for electronic user identification to the mobile device (2) via a Subscription Manager Data Preparation (SM-DP+) server of the mobile network or a trusted service. A subscription profile is a storage area (container, slot) allocated in the subscriber identity module. The subscription profile stores, among other things, subscription data (authorization data, network access data, network access credential data, credentials) that allow a user (subscriber) to use services, such as voice and / or data services, of a mobile network. Use of these services is enabled after successful registration with the mobile network.

[0020] To log into a mobile network, subscription data of a subscription profile is used to uniquely identify and / or authenticate a user (subscriber) of a terminal device in which the subscriber identity module is installed and ready for use, on the mobile network.

[0021] The subscription management system can be a Root Issuer Security Domain (ISD-R). It is particularly preferred that the subscription management system be a Root Issuer Security Domain (ISD-R) in accordance with the GSM SGP.22 specification, in particular in accordance with the GSM SGP.22 specification in version 2.3 dated June 30, 2021.

[0022] Such an application for electronic identification of the user can, for example, be part of the subscription profile.

[0023] The Subscription Manager Data Preparation (SM-DP+) Server may in particular be a Subscription Manager Data Preparation (SM-DP+) Server in accordance with the GSM SGP.22 specification, in particular in accordance with the GSM SGP.22 specification in version 2.3 of 30 June 2021.

[0024] The subscriber identity module, for example, has a file system as described in 3GPP TS 11.11 or 3GPP TS 11.14. The file system has files, e.g., elementary files (EF). An EF contains header data and main data and comes in three types: transparent EF, linear fixed EF, and cyclic EF. The file system of the subscriber identity module, for example, includes dedicated files (DF), which contain header data with a hierarchical structure of elementary files (EF) on the subscriber identity module. DFs do not contain their own data. A DF can be thought of as a directory structure. The file system of the subscriber identity module has at least one master file (MF), which represents the master file in the UICC file system.

[0025] A subscriber identity module within the meaning of the invention is, for example, an electronic module with reduced size and resource requirements, which has a control unit (microcontroller) and at least one interface (data interface) for communication with the device. This communication preferably takes place via a connection protocol, in particular a protocol according to the ETSI TS 102221 or ISO 7816 standard.

[0026] For subscriber identity module designs implemented as a so-called system on a chip (SoC), such as the "iUICC," the "Integrated eUICC," the Plugin eUICC, the "Integrated SE," or the "Integrated TRE," communication takes place via an SoC-internal bus. The subscriber identity module has an internal or external secure non-volatile memory area in which subscriber identity data and authentication data are securely stored to prevent attempts at manipulation and / or misuse during identification and / or authentication on the network.

[0027] In one embodiment, the subscriber identity module can be operated by means of a device, wherein the subscriber identity module in this embodiment is self-sufficient except for supply signals such as supply voltage, clock, reset, etc.

[0028] The term subscriber identity module is synonymous with the terms “UICC,” “eUICC,” “chip card,” “iUICC,” “integrated eUICC,” “integrated secure element,” “embedded secure element,” “secure element,” or “SIM.” A UICC can be, for example, a chip card, a SIM card, or a subscriber identity module. The subscriber identity module is used to identify a subscriber in a communications network using machine-readable subscriber identity data stored in the secure, non-volatile memory area and to authenticate them for the use of services. Subscriber identity modules also include USIM, TSIM, ISIM, CSIM, or R-UIM. For example, a UICC is defined as a USIM application in ETSI TS 131 102. For example, a UICC is defined as a SIM application in ETSI TS 151 011. For example, a UICC is defined as a TSIM application according to ETSI TS 100 812.For example, a UICC is defined as an ISIM application according to ETSI TS 131 103. For example, a UICC is defined as a CSIM application according to 3GPP2 C.S0065-B. For example, a UICC is defined as an R-UIM application according to 3GPP2 C.S0023-D.

[0029] The subscriber identity module can be an integral component within the device, for example, a hard-wired electronic component. Such subscriber identity modules are also referred to as eUICCs. In this form, these subscriber identity modules are not designed to be removed from the device and, in principle, cannot be easily replaced. Such subscriber identity modules can also be designed as embedded secure elements and are a secure hardware component within the device.

[0030] The subscriber identity module can also be a software component in a trusted part of the device's operating system, a so-called Trusted Execution Environment (TEE). The subscriber identity module is implemented, for example, within a secure runtime environment in the form of programs running within it, so-called "trustlets."

[0031] The subscriber identity module can also be an integral component of a larger integrated circuit, such as a modem or application processor. Such UICCs are referred to as "integrated UICCs," "integrated TREs," "integrated eUICCs," or "integrated SEs." Such UICCs are permanently integrated into an SoC as an integrated processor block and can be connected via an on-chip bus.

[0032] The subscriber identity module can be used for remote monitoring, control, and maintenance of devices such as machines, plants, and systems. It can be used for metering units such as electricity meters, hot water meters, etc. The subscriber identity module is, for example, a component of IoT technology.

[0033] The term "end device" is preferred here, although in communications technology, the end device can primarily be a "terminal." This does not preclude the possibility that a "end device" can be a "device" in a different technology. The terms "end device" and "device" are used synonymously.

[0034] A terminal device within the meaning of the invention is essentially a device or device component with means for communicating with a communications network, for using services of the communications network, or for using services of a server via a gateway of the communications network. For example, a mobile device such as a smartphone, a tablet PC, a notebook, or a PDA falls under this term. Multimedia devices such as digital photo frames, audio devices, televisions, and e-book readers, which also have means for communicating with the communications network, can also be understood as devices.

[0035] In particular, the device is installed in a machine, a vending machine and / or a vehicle. If the device is installed in a motor vehicle, it typically has an integrated UICC as a subscriber identity module. The UICC can establish a data connection to a server via the communications network via the device, e.g. using a modem on the device. The device can, for example, contact a server of the device manufacturer in order to address control units, e.g. ECUs (ECU = Electronic Control Unit) for the device's functionalities. A server in the background system of the mobile network operator, MNO, can be contacted via the UICC, e.g. a server to load updates for the UICC's software, firmware and / or operating system into the UICC.

[0036] A command is an instruction, command, or instruction sent by the device. The command is preferably a command according to ETSI TS 102 221 or ISO / IEC 7816. It can have a command header and a command body.

[0037] Preferably, the subscriber identity module comprises an operating system that is stored executably in the data memory and is configured to carry out the steps of the control unit.

[0038] The subscriber identity module, for example, is configured to establish a logical data connection to a server in the mobile network in order to use the server's or another server's services and exchange data. Establishing such a data connection from a subscriber identity module to a server requires connection parameters, such as a unique server address and the data connection protocol to be used. A card application toolkit (CAT) of the subscriber identity module, in accordance with ETSI Standard TS 102 223, is used to establish, terminate, and operate a data connection.

[0039] A mobile communications network is a technical facility over which signals are transmitted with identification and / or authentication of the subscriber. The mobile communications network offers its own services (own voice and data services) and / or enables the use of services from external entities. Device-to-device communication under the supervision of the mobile communications network is possible. In particular, a mobile communications network, for example the "Global System for Mobile Communications", or GSM for short, represents the second generation, or the "General Packet Radio Service", or GPRS for short or "Universal Mobile Telecommunications System", or UMTS for short, represents the third generation, or the "Long Term Evolution", or LTE for short, represents the fourth generation, is understood as a mobile communications network, or a 5th generation mobile communications network with the current working title "5G" is understood as a communications network.Communication in the communication network can take place via a secure channel, for example as defined in the technical standards ETSI TS 102 225 and / or ETSI TS 102226, for example SCP80, SCP81 or a transport layer security, TLS.

[0040] A server can be an instance physically remote from the end device. The server can be part of the mobile network. Alternatively or additionally, the server can be an external instance (i.e., not an instance of the mobile network). The Subscription Manager Data Preparation (SM-DP+) server can be an instance physically remote from the end device but part of the mobile network.

[0041] Subscriber identity data (=subscription data), as stored, for example, in the non-volatile memory area of ​​the subscriber identity module, is data that uniquely identifies a subscriber (a person or a device) in the mobile network. This includes, for example, a subscriber identifier, such as the International Mobile Subscriber Identity (IMSI) or Subscription Permanent Identifier (SUPI), and / or subscriber-specific data. The IMSI / SUPI is the unique subscriber identity file in a mobile communications network. Subscriber identity data also includes, for example, parameters and / or data that enable a subscriber to uniquely authenticate themselves in the communications network, such as an authentication algorithm, specific algorithm parameters, a cryptographic authentication key (Ki), and / or a cryptographic over-the-air (OTA) key.In addition, subscriber identity data includes data that uniquely authenticates a subscriber to a service, such as a unique identifier or signature. A service is, in particular, a voice service or a data service of a server used to transmit information and / or data over the communications network.

[0042] The subscriber identity module can be integrated into the terminal device in a ready-to-use state. Communication between the subscriber identity module and the terminal device is based on a connection protocol. The terminal device can also be configured to independently establish a data connection to the remote server in order to also use its services and exchange data with this server.

[0043] According to a preferred embodiment of the method, the public asymmetric personalization key and the private asymmetric personalization key are generated by means of a hardware security module, HSM.

[0044] Preferably, after encrypting the user's identity data, the encrypted identity data is stored on a server. This server is preferably different from the SM-DP+ server.

[0045] According to a preferred embodiment, a reference to the encrypted identity data, in particular to the encrypted identity data stored on the server, is transmitted to the user in the form of a URL or a QR code. Such a reference can also be referred to as a URL, link, or hyperlink.

[0046] According to a preferred embodiment of the method, the user initiates a personalization of the user's identity data based on the application for electronic identification of the user and the reference to the encrypted identity data.

[0047] Preferably, before sending the request to generate the subscription profile, the user's identity data is collected by the mobile network operator (MNO) or the identification provider and stored on a server of the mobile network operator (MNO) or the identification provider.

[0048] According to a preferred embodiment, the user's identity data is read from the user's electronic identification document. According to a preferred embodiment of the method, the identity data is deleted from the server of the mobile network operator (MNO) or the identification provider after the request to generate the subscription profile has been sent.

[0049] SHORT DESCRIPTION OF THE CHARACTERS

[0050] The invention and further embodiments and advantages of the invention are explained in more detail below with reference to figures, wherein the figures merely describe exemplary embodiments of the invention. Identical components in the figures are provided with the same reference numerals. The figures are not to be considered to scale; in particular, individual elements of the figures may be exaggeratedly large or oversimplified.

[0051] Fig. 1 shows an embodiment of a system comprising a mobile radio network, a terminal and a subscriber identity module;

[0052] Fig. 2 shows an embodiment of a subscriber identity module;

[0053] Fig. 3 shows a further embodiment of a subscriber identity module; and

[0054] Fig. 4 shows an embodiment of a flowchart of a method according to the invention.

[0055] DETAILED DESCRIPTION OF EMBODIMENTS

[0056] Fig. 1 shows an embodiment of a system with a mobile radio network, a terminal 2 and an exemplary subscriber identity module 1 with a memory 17. Applets, a Card Application Toolkit (CAT), authentication data records 172, an authentication data management 171 and at least one subscription profile 173a-c, in particular a plurality of subscription profiles 173a-c, can be stored in the memory 17.

[0057] The subscription profile(s) 173a-c of the subscriber identity module 1 are typically installed in an application bundle. The application bundle can be a (virtual) runtime environment, in particular a Java Card Runtime Environment, JCRE (according to the Java Card Classic Edition standard).

[0058] Subscriber Identity Module 1 can comprise multiple application bundles. These application bundles should be strictly separated from each other according to the GSMA standard and should contain "shielded" applications. An application bundle can be designed in such a way that it does not expose any of its own elements to another application bundle. In addition to the subscription profile, the application bundle can also include, for example, a GSM applet with a file system and events, a remote file management (RFM) applet, and other applets.

[0059] Application bundles can be pre-installed as empty application bundles on Subscriber Identity Module 1 or generated dynamically by calling a system programming interface (System API). A System API is preferably understood to be an API of Subscriber Identity Module 1.

[0060] The subscriber identity module 1 is inserted into the terminal 2 in a ready-to-use state and is supplied by the terminal 2 with a supply voltage Vcc and a clock pulse CLK. The subscriber identity module 1 is shown in more detail in Fig. 2. Fig. 1 indicates that the subscriber identity module 1 has the memory 17. Applets, the Card Application Toolkit (CAT), authentication data records 172, and the authentication data management 171 can be stored in this memory 17. Various APDU commands 11 can be exchanged between the UICC 1 and the terminal 2 using the applets, the CAT, and the operating system (not shown).

[0061] The terminal device 2 includes, for example—but not necessarily—a modem 3. The modem 3 can be regarded as a logical unit for converting data between the subscriber identity module 1 and a server 40 of a network 4. The terminal device 2 can establish a communication connection 12 to the subscriber identity module 1 via the modem 3. The communication 12 between the terminal device 2 and the subscriber identity module 1 takes place in accordance with the protocols defined in the international standards ISO / IEC 7816-3 and ISO / IEC 7816-4, to which reference is hereby expressly made.

[0062] All data exchange between the subscriber identity module 1 and the terminal device 2 preferably takes place using so-called APDUs (application protocol data units) in accordance with the ISO / IEC 7816-4 standard. An APDU represents an application-layer data unit, i.e., a type of container used to transmit commands and / or data to the subscriber identity module 1. A distinction is made between command APDUs, which are sent from a terminal device 2 to the subscriber identity module 1, and response APDUs, which are sent by the subscriber identity module 1 to the terminal device 2 in response to a command APDU.

[0063] The modem 3 is a communication unit of the terminal device 2, also for exchanging data from the terminal device 2 or the subscriber identity module 1 with the communication network 4 and the server 40 located therein. The data exchanged between the subscriber identity module 1 and the modem 3 can be converted into an IP-based connection protocol in the modem 3. Fig. 2 shows a block diagram of an exemplary subscriber identity module 1, preferably a hard-wired eUICC. Alternatively, the subscriber identity module 1 is a portable data carrier with a different design. The subscriber identity module 1 has an operating system 15. The operating system 15 is, for example, a native operating system. It is also conceivable that the operating system 15 is configured to run a Javacard runtime environment, JCRE, 16, which is then stored in the memory 17 together with the operating system 17.

[0064] The subscriber identity module 1 is designed to exchange data with the terminal 2 according to Fig. 3. For data transmission or communication between the subscriber identity module 1 and the terminal 2, both the subscriber identity module 1 and the terminal 2 each have suitable communication interfaces 12. The interfaces can, for example, be designed such that communication between them or between the subscriber identity module 1 and the terminal 2 is established galvanically, i.e., by contact. The contact assignment is defined in ISO / IEC 7816. In an embodiment not shown, the communication interface is contactless, for example, according to an RFID, NFC, or WLAN standard.

[0065] The subscriber identity module 1 also has a central processor or control unit, CPU 19, which is in communication with the interface 12. The primary tasks of the CPU 19 include executing arithmetic and logical functions and reading and writing data elements, as defined by program code executed by the CPU 19. The CPU 19 is also connected to a volatile main memory, RAM 18, and a non-volatile rewritable memory 17. Preferably, the non-volatile memory 17 is a flash memory (flash EEPROM). This can be, for example, a flash memory with a NAND or NOR architecture.

[0066] In the preferred embodiment shown in Fig. 2, the program code that can be executed by the CPU 19 is stored in the non-volatile memory 17. In particular, the program code of the chip card operating system, OS, 15, the Java Card runtime environment, JCRE, 16 (consisting of Java Card Virtual Machine, JCVM and Java Card Application Programming Interfaces, JCAPI), an application 13 for authentication data management, and at least two authentication data records 172a, 172b can be stored in the non-volatile memory 17. An application is preferably in the form of Java Card™ applets. In addition, a CAT (not shown) according to ETSI TS 102 223 can be incorporated. Instead of an application, a program element written in native code, for example in C or assembler, can also be provided.

[0067] Fig. 3 shows a further embodiment of a subscriber identity module 1, more precisely a memory area 17 of a subscriber identity module 1. The memory area 17 is a non-volatile memory, but can also be a volatile memory (RAM). The memory area 17 can be an exclusively assigned memory area 17 that is part of a larger memory unit. The memory area 17 can be a remote memory area. The memory area 17 of the subscriber identity module 1 describes a memory area to which the subscriber identity module 1 or the control unit 19 of the subscriber identity module 1 has exclusive access. The access rights to the memory area 17, i.e., reading, writing, and overwriting, can be defined in a security domain (SD), so that different subunits of the subscriber identity module 1 have or do not have access to different areas of the file system 175.

[0068] The memory area 17 of Fig. 3 has, for example (but not necessarily), a subscription management 174 (ISD-R), which can manage various subscription profiles 173a-c. A subscription profile 173ac can be managed by means of OTA communication between servers 40 of the communication network, for example, subscription server SM-SR or data provision server SM-DP, SM-DP+ according to the GSMA specifications SGP.02 and SGP.22, using, for example, SMS, CAT TP, or HTTPS for over-the-air, OTA, communication with the subscriber identity module 1. This profile management—which is not part of this description—includes "creating," "loading," "activating," "deactivating," "deleting," and "updating." For details, reference is made to the aforementioned GSMA specifications.

[0069] A subscription profile 173a-c includes profile data. For example, one of the following components can be present as a profile file for each subscription profile 173a-c: an MNO security domain (MNO-SD) with the OTA key sets from OTA servers; at least one authentication parameter (Ki, OP, RAND, SGN) or at least one reference 176 (pointer or address) to a corresponding entry 172 in the file system 175 of the subscriber identity module 1; a network access application, policy rules; a profile-specific file system containing DFs, EFs for the respective subscription profile 173a-c; a supplementary security domain (Supplementary Security Domain, SSD for short) for storing connection parameters of the profile and additional keys; an area with applications, such as applets; a subscriber identifier (IMSI), a subscriber identity module identifier (ICCID), and, if applicable, profile updates.

[0070] The subscriber identity module 1 further includes an authentication data management system 171. This can be stored in the form of a Java applet (see Fig. 1) in the memory area 17 of the subscriber identity module 1. The data management system 171 can also be stored in the memory area 17 of the subscriber identity module 1 as native program code. The control unit 19 executes the authentication data management system 171 as needed.

[0071] Furthermore, authentication data records 172 are stored in the memory 17 of the subscriber identity module 1. Two authentication data records 172a and 172b are shown as examples, but the number is not limited. An authentication data record 172 can comprise various authentication data. This is illustrated in Fig. 2 using the first authentication data record 172a as an example. It has an authentication algorithm (Milenage, TUAK) with corresponding authentication parameters, one or more authentication keys (CK, IK, Ki), if necessary, sequence parameters (counters SGN-MS, SGN-HE, other counters), and authentication updates, etc. In addition to the above, an authentication data record 172 can contain further authentication data. The authentication data is preferably stored in a structured manner in the file system 175, as indicated in Fig. 3. However, proprietary files can also be created to store the authentication data records 172.

[0072] Using a reference 176, the authentication data records 172 can be assigned to a respective subscription profile 173. For this purpose, in one embodiment of the invention, an area is defined in the file system 175 in which the activated authentication data is stored. A subscription profile 173 then accesses this area to authenticate the subscriber identity module 1 with the server 40 of the communication network 4.

[0073] In another embodiment, the authentication data is written to the respective storage area of ​​the file system.

[0074] Implementation details are described in detail in the technical reports TR 33.834 and TR 133.935, and reference is made here to the implementations, particularly the updates according to solutions 4b and 5. When updates are received, they are stored in a memory area of ​​the UICC using the authentication data management 171. For this purpose, either a new file or a new file structure is created in the file system 175, or a corresponding authentication data record 172 is updated, e.g., overwritten or extended. In addition, a reference 176 to the authentication data can be updated, for example, by updating a memory address, updating a pointer, or copying the updated authentication data into the corresponding area of ​​the profile.Only one authentication data record can be activated at a time, so that the subscriber identity module 1 provides unique authentication to the communication network.

[0075] The data records are stored, for example, in EF files of the subscriber identity module 1. Alternatively or additionally, the authentication data can be stored in data objects, for example, in data objects of the subscriber identity module 1. Alternatively or additionally, the authentication data can be stored in reserved memory areas of the operating system (OS) of the subscriber identity module 1. These different storage locations may require a change in the structure of the data records.

[0076] The data records can therefore be stored in differently structured data records 172a, 172b depending on their storage location. The authentication data management system 171 is configured, in particular, to restructure and adapt the stored authentication data, in particular the authentication data records 172a, 172b, accordingly, in order to be able to use them for intended authentication on the one hand, and to store them in the desired storage location on the other.

[0077] Fig. 4 shows an exemplary embodiment of a flowchart of a method according to the invention. The method 100 for managing an application for electronically identifying a user of a mobile terminal 2 having a subscriber identity module 1 in a mobile network according to the exemplary embodiment comprises the following method steps:

[0078] - Collecting 101 of a user's identity data;

[0079] - storing 102 the collected identity data of a user on a first server;

[0080] - Sending 103 a request to generate a subscription profile 173a-c to a Subscription Manager Data Preparation (SM-DP+) server of the mobile network;

[0081] - generating 104 a subscription profile 173a-c, wherein generating the subscription profile 173a-c comprises generating a private asymmetric personalization key associated with the subscription profile 173a-c and a public asymmetric personalization key associated with the subscription profile 173a-c for an application for electronic identification of the user;

[0082] - Providing 105 an application for electronic identification of the user by a Subscription Manager Data Preparation (SM-DP+) server of the mobile network or a trusted service;

[0083] - sending 106 the public asymmetric personalization key to a second server, namely a server of the mobile network operator (MNO) or a server of an identification provider;

[0084] - Encryption of the user's identity data using the public asymmetric personalization key;

[0085] - Deleting 108 the collected identity data of a user;

[0086] - Distributing 109 the subscription profile 173a-c with the private asymmetric personalization key to the mobile terminal 2;

[0087] - Distributing 110 the application for electronic identification of the user to the mobile terminal (2) by a Subscription Manager Data Preparation (SM-DP+) server of the mobile network or a trusted service;

[0088] - Importing 111 of the identity data into the application for electronic identification of the user and decryption by the application for electronic identification of the user.

[0089] The Subscription Manager Data Preparation (SM-DP+) server is typically a server that is part of the mobile network and communicates with other entities in the mobile network. The Subscription Manager Data Preparation (SM-DP+) server typically prepares subscription profiles 173a-c, secures them with a profile protection key, securely stores the profile protection keys and the protected subscription profiles 173a-c in a profile package repository, and maps the protected profile packages to specific identifiers of the Subscriber Identity Module 1 (EIDs).

[0090] The SM-DP+ server typically binds protected subscription profiles 173a-c to the respective EID and securely downloads these bound profile packages to the LP A of the respective Subscriber Identity Module 1 (eUICC).

[0091] The Subscription Manager Data Preparation (SM-DP+) Server may in particular be a Subscription Manager Data Preparation (SM-DP+) Server in accordance with the GSM SGP.22 specification, in particular in accordance with the GSM SGP.22 specification in version 2.3 of 30 June 2021.

[0092] The generated public and corresponding private asymmetric personalization keys are conveniently stored in the additional security domain (SSD) of subscription profile 173a-c. The generation of the public asymmetric personalization key and a corresponding private asymmetric personalization key is generally based on an asymmetric cryptosystem, in particular a public-key encryption method.

[0093] The application for electronic identification of the user can, for example, be an electronic identification applet (eID applet), which can be executed in particular on the user's terminal device 2. The electronic identification applet can be linked to the subscription profile 173a-c, be a component thereof, or be a component of an application bundle of the subscription profile 173a-c.

[0094] The application for electronic identification can be created or provided by the Subscription Manager Data Preparation (SM-DP+) server or a trusted service, such as a Trusted Service Manager (TSM). If provision is performed by a trusted service, the Subscription Manager Data Preparation (SM-DP+) server and the trusted service expediently exchange master keys or certificates before distributing an application for electronic identification. The trusted service then expediently has a key or credential available with which the trusted service can identify itself to a subscription profile 173a-c. For example, the trusted service can receive a key that uniquely corresponds to a key stored in the supplementary security domain (SSD) of the subscription profile 173a-c.

[0095] Preferably, the application for electronic identification is written into the applications area of ​​the subscription profile 173a-c.

[0096] The terminal device 2 can, in particular, be a mobile phone of the user. Encrypting 107 the user's identity data using the public asymmetric personalization key ensures that the identity data can only be imported into the application for electronic identification of the user that belongs to the subscription profile 173a-c intended for the user, since only this application can decrypt the encrypted identity data. The method 100 complies with current data protection regulations, in particular the General Data Protection Regulation (GDPR).

[0097] Preferably, the generation 104 of the public asymmetric personalization key and the private asymmetric personalization key takes place by means of a hardware security module.

[0098] According to a preferred embodiment of the method 100, before sending 103 the request to generate the subscription profile 173a-c, the user's identity data is captured 101 by the mobile network operator (MNO) or the identification provider and stored 102 on a first server, namely a server of the mobile network operator (MNO) or the identification provider. The user's identity data can be read from an electronic identification document of the user, such as an electronic passport or identity card. Such an electronic identification document is usually provided with a readable chip and can be in the form of a so-called smart card. By reading the user's electronic identification document, a high degree of accuracy of the obtained identity data can be ensured.

[0099] The user can be identified, for example, by the mobile network operator upon conclusion of a mobile phone contract. When concluding a mobile phone contract, the user's identity data must be collected anyway. Alternatively, the mobile network operator can commission an identification service and / or use its services to identify the user.

[0100] The generation 104 of the public asymmetric personalization key and the private asymmetric personalization key can be done by means of a hardware security module.

[0101] After encrypting 107 the user's identity data, the encrypted identity data can be stored on a server, such as the second server.

[0102] After the encrypted identity data has been stored on the second server, the originally recorded identity data can be deleted 104. The encrypted identity data can be decrypted using an electronic identification application integrated into a subscription profile 173a-c, which includes the corresponding private asymmetric personalization key. Preferably, the encrypted identity data can be decrypted exclusively by a subscription profile 173a-c, which includes the application for electronic identification of the user.

[0103] A reference to the encrypted identity data, in particular to the encrypted identity data stored on the server, can be transmitted to the user in the form of a URL or a QR code. Such a reference can also be referred to as a link, hyperlink, or URL.

[0104] The user can initiate personalization of their identity data using the application for electronic user identification and the reference to the encrypted identity data. Using the application, the user can supplement their identity data or correct any errors.

[0105] Using method 100, operators of a mobile network, in particular operators of a Subscription Manager Data Preparation (SM-DP+) server, are enabled to generate such an application (eID applet) and distribute it to the users' end devices 2. The application can then be personalized by the user.

[0106] The subscriber identity module 1 can comprise a register. Data can be stored in this register, allowing all entities to be uniquely referenced. This data includes an identifier of the corresponding application bundle and an identifier of the corresponding subscription profile 173a-c (according to ISO / IEC 7816). According to this embodiment, starting from the active application bundle, the entities can be filtered out that correspond to the identifier of the active application bundle and the subscription management 174. Furthermore, a non-UICC application bundle can be created that has the same interface but is not managed by the subscription management 174.

[0107] Within the scope of the invention, all described and / or drawn and / or claimed elements can be combined with one another as desired. LIST OF REFERENCE SYMBOLS Subscriber identity module, SIM, UICC

[0108] 11 Command, APDU

[0109] 12 Interface

[0110] 15 Operating system, OS

[0111] 16 Java Runtime Environment, JCRE

[0112] 17 Non-volatile memory

[0113] 171 Authentication data management

[0114] 172 Authentication record

[0115] 173a Subscription profile

[0116] 173b Subscription profile

[0117] 173c Subscription profile

[0118] 174 Subscription management

[0119] 175 File system

[0120] 176 Reference

[0121] 18 Volatile memory

[0122] 19 Control unit, CPU terminal device modem between terminal device and UICC communication network

[0123] 40 servers over-the-air communication

Claims

PATENT CLAIMS 1. A procedure for managing an application for the electronic identification of a user of a mobile terminal equipment (2) having a subscriber identification module (1) in a mobile network, comprising the following procedural steps: - Sending (103) a request to generate a subscription profile (173a-c) to a Subscription Manager Data Preparation (SM-DP+) server of the mobile network; - Generating (104) a subscription profile (173a-c), wherein generating the subscription profile (173a-c) includes generating a private asymmetric personalization key associated with the subscription profile (173a-c) and a public asymmetric personalization key associated with the subscription profile (173a-c) for the application for electronic identification of the user; - Sending (106) the public asymmetric personalization key to a server of the mobile network operator (MNO) or to a server of an identification provider; - Encrypting (107) user identity data using the public asymmetric personalization key; and - Distributing (109) the subscription profile (173a-c) with the private asymmetric personalization key to the mobile device (2) - Distributing (110) the application for electronic identification of the user to the mobile device (2) by a Subscription Manager Data Preparation (SM-DP+) server of the mobile network or a trusted service (TSM).

2. Method according to claim 1, characterized in that the encrypted identity data of the user is fed into the application for electronic identification of the user and decrypted by it.

3. Method according to claim 1 or 2, characterized in that the trusted service exchanges master keys or certificates with the Subscription Manager Data Preparation (SM-DP+) server of the mobile network.

4. Method according to one of the preceding claims, characterized in that the generation (104) of the public asymmetric personalization key and the private asymmetric personalization key is carried out using a hardware security module.

5. Method according to one of the preceding claims, characterized in that after encrypting (107) the user's identity data, the encrypted identity data is stored on a server.

6. Method according to one of the preceding claims, characterized in that a reference to the encrypted identity data, in particular to the encrypted identity data stored on the server, is transmitted to the user in the form of a URL or a QR code.

7. Method according to claim 6, characterized in that the user initiates a personalization of the user's identity data based on the application for electronic identification of the user and the reference to the encrypted identity data.

8. Method according to one of the preceding claims, characterized in that, prior to sending (103) the request to generate the subscription profile (173a-c), the user's identity data is recorded by the mobile network operator (MNO) or the identification provider (101) and stored on a server of the mobile network operator (MNO) or the identification provider (102).

9. Method according to claim 8, characterized in that the user's identity data is read from an electronic identification document of the user.

10. Method according to one of claims 8 or 8, characterized in that the recorded identity data is deleted after encryption and storage on a server (108).

Images