DE102016216336B4 - Method for automatically provisioning a terminal device with an embedded subscriber identification module (eSIM) - Google Patents

Abstract

A method for supporting automatic provisioning of a terminal (50) with an embedded subscriber identification module, the method comprising the following steps: - wireless transmission of a readiness message (103) by the terminal (50), - wireless reception of the readiness message (103) by a reading device (10), - wireless request for an identifier linked to the embedded subscriber identification module by the reading device (10), - release of a transmission of the identifier by means of the terminal (50), - reading of the identifier from the embedded subscriber identification module, - wireless transmission of the identifier and a Device identifier of the terminal (50) after the release from the terminal (50) to the readout device (10), - transmission of the identifier and the device identifier from the readout device (10) to an authentication unit, - verification of the identifier using the device identifier by the authentication unit, - wireless transmission a user profile uniquely assigned to the identifier to the terminal (50), - installation of the user profile in the embedded subscriber identification module.

Description

field of invention

The invention relates to a method for automatically provisioning a terminal device with an electronic subscriber identification module (eSIM). The invention also relates to a correspondingly set up terminal. Finally, the invention relates to a system that has a correspondingly set up terminal and readout device. The invention also relates to an associated computer program product.

Background of the Invention

With the introduction of the eSIM, a mobile network operator (MNO) can no longer provide its customers with a physical SIM card. The installation and activation of an eSIM profile, which contains all the necessary data for dialing into the mobile network, on an end device to be connected can be a challenge for the user if the end device is not sold by the mobile network provider.

Summary of the Invention

It is an object of the present invention to provide a method for supporting automatic provisioning of a terminal device with an electronic subscriber identification module (eSIM) that allows a simple installation and activation of an eSIM profile by a user.

The invention is claimed in the independent claims. Preferred embodiments can be found in the dependent claims.

• - kabelloses Senden einer Bereitschaftsmitteilung durch das Endgerät,
• - kabelloses Empfangen der Bereitschaftsmitteilung durch ein Auslesegerät,
• - kabelloses Anfordern eines mit dem elektronischen Teilnehmeridentifizierungsmodul verknüpften Identifizierers durch das Auslesegerät,
• - Freigabe einer Übermittlung des Identifizierers mittels des Endgerätes,
• - Auslesen des Identifizierers aus dem elektronischen Teilnehmeridentifizierungsmodul,
• - kabellose Übermittlung des Identifizierers und einer Gerätekennung des Endgerätes nach der Freigabe vom Endgerät zum Auslesegerät
• - Übermitteln des Identifizierers und der Gerätekennung vom Auslesegerät an eine Authentisierungseinheit,
• - Verifizierung des Identifizierers mittels der Gerätekennung durch die Authentisierungseinheit,
• - kabelloses Übermitteln eines dem Identfizierer eindeutig zugeordneten Nutzerprofils an das Endgerät,
• - Installation des Nutzerprofils in dem eingebetteten Teilnehmeridentifizierungsmodul.

This object is achieved by a method for supporting automatic provisioning of a terminal device with an embedded subscriber identification module. The procedure includes the following steps:

• - wireless sending of a ready message by the terminal device,
• - wireless receipt of the readiness message by a reading device,
• - wireless request for an identifier linked to the electronic subscriber identification module by the reading device,
• - release of a transmission of the identifier by means of the end device,
• - reading the identifier from the electronic subscriber identification module,
• - wireless transmission of the identifier and a device identifier of the terminal device after release from the terminal device to the reading device
• - Transmission of the identifier and the device ID from the reading device to an authentication unit,
• - verification of the identifier using the device ID by the authentication unit,
• - wireless transmission of a user profile uniquely assigned to the identifier to the end device,
• - Installation of the user profile in the embedded subscriber identification module.

With the introduction of the electronic subscriber identification module (embedded UICC), the so-called eSIM (embedded Subscriber Identity Module), a mobile network operator (MNO) no longer provides its customers with a physical SIM card, but transmits them an eSIM profile. The eSIM profile contains all the necessary data for dialing into the mobile network for installation and activation on the device to be connected. The prerequisite for this is that the mobile communications provider can identify the customer as a unique identifier using an identifier assigned to or linked to the eSIM, the so-called eID (eUICCID) of the eSIM of the end device.

In this context, it is possible that the majority of devices used in the future, especially in the context of the "Internet of Things" (IoT), will not be acquired via MNO channels. In such a case, the MNO usually does not know the eID. This can pose a problem because the deployment or Provisioning of an eSIM profile without prior provision of the eID in the backend of the MNO is not possible. The method shown allows the user of the device with eSIM to easily display and read the eID and to transfer it to another device (readout device). In particular, the method allows wireless transmission of the eID between two devices. The reading device does not have to have an eSIM.

For this purpose, a user's terminal sends a ready message via a radio interface of the terminal. The radio interface can, for example, comprise a Bluetooth interface, a Wi-Fi interface, an NFC interface or the like. The readiness notification can, for example, signal the connection readiness of the terminal device by means of the respective wireless connection technology. A reader receives this readiness message. The reading device can be, for example, a computer, a smartphone or any other device that can directly or indirectly (e.g. through a forwarding unit) receive the ready notification. The readout device can thus, for example, communicate directly with the terminal device using the respective connection technology or indirectly via one or more forwarding units. The readout device can, for example, have a list of known end devices. Such a list can enable the reader to determine whether the terminal has already been provisioned. If the end device has not yet been provisioned, the reading device could request the transmission of an eID in order to initiate provisioning, i.e. the provision of an eSIM profile, if necessary. Alternatively, the reader could also have a program in the form of an application, which application, when active, contacts each terminal, for example regardless of the connection technology, that sends a ready message. The wireless request for the eID is preferably carried out using the same connection technology as is used to send the notification of readiness. However, if alternative, possibly more secure transmission paths are available, alternative connection technologies could also be used. The identifier or the eID is only transmitted if there is a release that explicitly or implicitly confirms that the eID may be transmitted. After confirmation that the eID can be read, the eID is read from a memory area of the end device assigned to the eSIM and transmitted wirelessly to the reading device. The reading device could then be used to forward the eID to an MNO and thus initiate the provisioning of the end device. The method thus enables the user to easily read out the eID without an unauthorized person gaining direct access to the eID.

The readiness message preferably signals a readiness to transmit the identifier associated with the electronic subscriber identity module. The readiness notification can, for example, signal that the end device has an eID.

The release of the transmission of the identifier preferably includes an activation of a readiness for transmission for the transmission of the identifier. The readiness for transmission can be activated in advance by the user switching on the end device. Alternatively, the readiness for transmission could also be activated after the request for the eID. For example, the end device could indicate the receipt of the request visually or acoustically and ask the user to grant the release by means of an activation signal. The activation signal can include, for example, an acoustic or key input on the terminal. The key input can be done, for example, by means of a simple button or by means of a user interface.

The readiness to transmit is automatically deactivated, preferably after a predetermined period of time, in particular after the activation or release of the readiness to transmit by switching on the terminal device. The automatic deactivation of the readiness for transmission can prevent the user from unintentionally activating the readiness for transmission for an undefined period of time without wanting to initiate the provisioning of the terminal device. This could make it easier for unauthorized persons to read the eID.

Alternatively, readiness for transmission can be terminated after activation by a deactivation signal. This can be done again by pressing a button on the end device or by a corresponding electronic signal. The electronic signal can preferably be sent automatically by the reading device, for example, after the eID has been transmitted and, if necessary, has been checked, for example, for formal criteria that allow it to be determined that it is an eID.

The step of enabling the transmission of the identifier preferably includes the additional step of authenticating the reading device. For example, access to the eID can be restricted to certain reading devices. Furthermore, access to the eID can be linked to entering a code. This code can be entered, for example, using a user interface of the terminal or can be entered using the readout device and transmitted to the terminal.

The provisioning of the end device is started by means of the readout device. The reading device can, for example, forward the eID to an MNO, optionally with additional information that enables the terminal device to be contacted. The MNO then transmits a user profile to the terminal device, which is preferably installed in the electronic subscriber identification module (eSIM) with the consent (explicit or implicit) of the user of the terminal device. The transmission of the eSIM profile does not necessarily have to take place via the reading device, but can also take place via another communication channel. In this case, the reading device has transmitted the eID to a central authority of a mobile network operator, for example. The user profile is then provided by a mobile operator's server and transmitted to the end device.

The procedure is designed in such a way that the correctness of the identifier (eID) is authenticated. The eID is transmitted from the reading device to an authentication unit and is then verified by this authentication unit using the device identifier. The authentication unit can, for example, belong to an independent organization to which the manufacturer communicates the eIDs, for example in combination with the device type/serial number. The authentication unit then checks whether a corresponding electronic identification number has been assigned for the corresponding device or end device. In this case, a device ID is sent to the authentication unit together with the eID. Authenticating the eID using the authentication unit can prevent an eSIM profile from being transmitted to a device or end device with a counterfeit eID.

The identifier is preferably read out and transmitted using the Bluetooth protocol. For example, a Bluetooth service can be created/adapted to transmit an eID. For example, another field/category (so-called characteristic) could be introduced in the already existing "Device Information Service" (DIS) [BT.DIS]. The DIS is based on the "Generic Attribute Profile" (GATT) [BT.GATT] of the Bluetooth specification and can be used both over BR/EDR (Basic Rate/Enhanced Data Rate) and over Low Energy links. GATT specifies a number of attributes specific to sensors and application services. The profile defines which data can be retrieved from a device, how this data is specifically structured and what properties it has. GATT distinguishes between two roles, server and client. The server is the device that provides the data (typically a peripheral device). So-called services are available on the server, which offer the data. A service can contain several data bundles, so-called characteristics. A characteristic is in turn a bundle of a data value (value), the properties (properties) of this value (data type, length) and an optional description (descriptor). A profile can consist of several services and the services can build on each other (include). A list of all services, their dependencies and all built-in characteristics can be found under [DevBtServices]. The DIS is a service that operates as a set of characteristics to perform a specific function. The characteristics include, for example, the hardware revision string, the serial number string, the model number string, the manufacturer name string, the firmware revision string, the software revision string, the system ID and the IEEE 11073-20601 regulatory certification data list.

In order to meet the needs of the IoT market and to be able to provide all relevant information about a device to the user, the following characteristics could be added, for example: Surname qualifiers Mandatory Properties Optional properties Security Permissions oath 0 Read user consent

The eID can therefore only be read if the user has given their consent. As an existing service is being changed, according to the Bluetooth specification, new characteristics may only be added as "optional". The characteristic is of the "UTF8 String" type and is read using the GATT function Characteristic Value Read. In order for it to be read, it must be assigned a universally unique identifier (UUID) by the Bluetooth SIG. For devices with a user interface, consent of the user, for example, at the moment when the value is accessed for reading. With loT devices, for example, the user gives their consent by switching on the transmission mode.

A terminal is set up to wirelessly transmit a readiness message to a readout device. The terminal is also set up to read an identifier (eID) linked to the electronic subscriber identification module from the electronic subscriber identification module and to wirelessly transmit the identifier and a device identifier of the terminal to the readout device after the release. The end device includes one or more data memories in which, for example, the data of the eSIM is stored. The terminal also includes one or more processors or microprocessors in order to carry out the data exchange and, if necessary, to be able to process further functions.

It is a further object of the present invention to provide a system, the system having an authentication unit, a read-out device and the terminal device described above. The readout device is set up to wirelessly request an identifier (eID) linked to the electronic subscriber identification module from the terminal device. The readout device is also set up to transmit the identifier and the device identifier to the authentication unit. The authentication unit is set up to identify the identifier using the device identifier. The system is also set up, after the identifier has been verified, to wirelessly transmit a user profile that is uniquely associated with the identifier to the terminal device. The terminal is set up to install the user profile in the embedded subscriber identification module. For this purpose, the readout device, like the end device, has corresponding data storage processors or microprocessors.

The invention also relates to one or more computer program products. The computer program product(s) includes code means that are stored on one or more data memories of the terminal device or the readout device. The code means are designed in such a way that the method steps of claims 1 - 10 can be executed on one or more processors of the terminal or the readout device.

character list

• 1 zeigt eine schematische Darstellung eines ersten Systems
• 2 zeigt eine schematische Darstellung eines ersten Verfahrens
• 3 zeigt eine schematische Darstellung eines zweiten Systems
• 4 zeigt eine schematische Darstellung eines zweiten Verfahrens

These and other aspects of the invention are shown in detail in the figures as follows.

• 1 shows a schematic representation of a first system
• 2 shows a schematic representation of a first method
• 3 shows a schematic representation of a second system
• 4 shows a schematic representation of a second method

Detailed description of the exemplary embodiments

1. 1. Auf dem Auslesegerät 10 wird eine App zum Empfang der eID gestartet
2. 2. Die App veranlasst das Betriebssystem aktiv nach Endgeräten 50 zu scannen, die elDs übertragen können
   1. a. Das Auslesegerät 10 nutzt die Eigenschaften der Funktechnologie, um Endgeräte 50 zu finden, die angeben, eine eID übertragen zu können. Dies erfolgt mit den Methoden der „Service Discovery“ der Funktechnologie.
3. 3. In der App werden die gefundenen Endgeräte 50 mittels einer Anzeigevorrichtung 20 des Auslesegerätes 10 angezeigt
4. 4. Der Nutzer 1 wählt aus einer Liste 30 mit Endgeräten 50 eines der gefundenen Geräte 31, 32, 33 aus
5. 5. Das Auslesegerät 10 sendet eine Anfrage 119 zur Übertragung der eID an das ausgewählte Endgerät 50
6. 6. das ausgewählte Endgerät 50 empfängt diese Anfrage und zeigt dem Nutzer die oben beschriebene Sicherheitsabfrage an
   1. a. Der Nutzer 1 erlaubt mittels Betätigung eines Bestätigungsfeldes 71 einer Anzeigevorrichtung 60 des Endgerätes 50 die Übertragung der eID,
   2. b. Der Nutzer 1 verweigert mittels eines Ablehnungsfeldes 72 die Übertragung der eID.
      1. i. Das Endgerät 50 antwortet mit einem Fehlercode
      2. ii. Das Endgerät 50 zeigt eine Nachricht über den Misserfolg mit dem Fehlercode und/oder einer entsprechenden Fehlermeldung an
7. 7. Das Endgerät 50 überträgt in Schritt 119 einen Statuscode (der den Erfolg oder Misserfolg der Operation angibt) und, abhängig vom Statuscode, die eID an das Auslesegerät 10
8. 8. Das Auslesegerät 10 reicht die empfangene eID an die App weiter
9. 9. Die App verarbeitet die eID

1 shows a schematic representation of a first system with a terminal 50 and a reading device 10. In this first system, the reading of the eID on a terminal 50 with eSIM with a user interface (UI) is discussed. In this method, the eID is transmitted to a second device, the reading device 10, via short-range radio technology. The transmission takes place explicitly at the instruction of a user. An application (app) is installed on the reading device 10, which receives and further processes the transmitted eID. This app can come from a mobile network operator (MNO), for example. A prerequisite is that the selected radio technology (Bluetooth or NFC) is available and switched on at the readout device 10 . The recipient scans the environment for terminals 50 that can transmit the eID. The end devices 50 found are displayed in a list from which the user selects the device from which he would like to read the eID. Terminal 50 and reader 10 now establish a connection and transmit the eID. If the end device 50 can interact with the user, the user is prompted to allow the transmission of the eID on the transmitter. The logical sequence is as follows:

1. 1. An app for receiving the eID is started on the reading device 10
2. 2. The app prompts the operating system to actively scan for end devices 50 that can transmit elDs
   1. a. The readout device 10 uses the properties of radio technology to find end devices 50 that indicate that they can transmit an eID. This is done using the “service discovery” methods of radio technology.
3. 3. The end devices 50 found are displayed in the app by means of a display device 20 of the readout device 10
4. 4. The user 1 selects one of the devices 31, 32, 33 found from a list 30 with terminals 50
5. 5. The reading device 10 sends a request 119 to transmit the eID to the selected end device 50
6. 6. The selected terminal 50 receives this request and displays the security query described above to the user
   1. a. The user 1 allows the transmission of the eID by actuating a confirmation field 71 of a display device 60 of the end device 50,
   2. b. The user 1 refuses the transmission of the eID by means of a rejection field 72 .
      1. i. The terminal 50 responds with an error code
      2. ii. The terminal 50 displays a message about the failure with the error code and/or a corresponding error message
7. 7. In step 119, the end device 50 transmits a status code (indicating the success or failure of the operation) and, depending on the status code, the eID to the readout device 10
8. 8. The reader 10 forwards the received eID to the app
9. 9. The app processes the eID

2 shows a schematic representation of a first method. The term reader 10 refers to the device that has an app for finding devices with eSIM. The term terminal device 50 defines the device that includes an eSIM from which the eID is to be read. The terminal 50 is permanently in the Bluetooth LE “General Discoverable Mode”, ie it can be found by other devices at any time provided the Bluetooth module is switched on. It thus sends a readiness message 103. Using an app on the readout device 10, the user 1 starts a scan for Bluetooth LE devices in the area in step 105. To do this, the app prompts the Bluetooth module of the readout device 10 to search for end devices 50 in step 107 using the “General Discovery Procedure” described in the BLUETOOTH SPECIFICATION Version 4.2 Chapter 9.2.6 Vol 3, Part C in [BT.Core]. The respective end device 50 then registers with the readout device 10 in step 109 as part of this search. This registration can take place, for example, in that the read-out device 10 receives a readiness message 103 . Every end device 50 found is now asked in step 111 whether it supports the above-mentioned characteristic for reading out the eID. This is done using the "Discover Characteristics by UUID" function, which is specified in the BLUETOOTH SPECIFICATION Version 4.2 Chapter 4.6.2 in Vol 3, Part G in [BT.Core]. If at least one service that supports this characteristic is found on a found terminal device 50, this terminal device 50 is displayed after a response 113 (FindCharacteristicsResponse) from the terminal device 50 in step 115 in the user interface of the app of the reading device 10. In addition, the handle that is required to read the characteristic is saved. If the user 1 selects one of the end devices 50 found from the list in step 117, the app causes the eID to be read out by sending a read request in step 119 with the handle of the characteristic to the end device 50 in question. The corresponding handle was determined in the previous step. How the Read Request works is described in the BLUETOOTH SPECIFICATION Version 4.2 Chapter 4.8.1 in Vol 3, Part G in [BT.Core]. If the terminal 50 receives the read request, the function ESc10.GetEID of the local profile assistant (Local Profile Assistant—LPA) 80 is called in step 121 to read out the eID. The functionality of the LPA is described for example in chapters 4.8 and 4.10 in [SGP.21 - RSP Architecture Version 1.0, 23 December 2015]. The consensus of the user 1 is obtained by means of a release request 123. If the user allows access with a release 125, the LPA 80 transmits a confirmation response 127 to the terminal 50. The eID is then read from the memory of the terminal 50 assigned to the eSIM. If user 1 denies access, the function returns an error code. The result of this query is sent to readout device 10 as response 129 to the read request. If the response is an eID, it is passed to the app for processing. Otherwise the error message is displayed in a form that the user 1 can understand.

1. 1. Der Nutzer schaltet die Übertragungsbereitschaft am Endgerät 50 über eine Taste am IoT-Gerät ein
2. 2. Das Modul der gewählten Funktechnologie wird eingeschaltet und in einen Modus zur Kopplung/Übertragung der eID versetzt
3. 3. Auf dem Auslesegerät 10 wird eine App zum Empfang der eID gestartet
4. 4. Die App veranlasst das Betriebssystem aktiv nach Endgeräten 50 zu scannen, die sich über Bluetooth verbinden können und elDs übertragen können
   1. a. Das Auslesegerät 10 nutzt die Eigenschaften der Funktechnologie, um Endgeräte 50 zu finden, die angeben, eine eID übertragen zu können. Dies erfolgt mit den Methoden der „Service Discovery“ der Funktechnologie.
5. 5. Die App zeigt die gefundenen Endgeräte 50 an
6. 6. Der Nutzer 1 wählt eines der gefundenen Endgeräte 50 aus
7. 7. Das Auslesegerät 10 sendet eine Anfrage 119 zur Übertragung der eID an das ausgewählte Endgerät 50
8. 8. Das ausgewählte Endgerät 50 empfängt die Anfrage 119 und antwortet mit einem Statuscode (der über den Erfolg oder Misserfolg der Operation informiert) sowie, im Erfolgsfall, mit der eID
9. 9. Das Auslesegerät 10 empfängt die Antwort in Schritt 129 und leitet die eID an die App weiter
10. 10. Die App verarbeitet die eID

3 shows a schematic representation of a second system. In this second system, a readout device 10 is coupled to a terminal 50 that does not have a complex user interface. Such a terminal device 50 is an IoT device, for example, which has, for example, one or more memory devices 52 and one or more processor devices 54 for processing stored software commands. Such IoT devices may, for example, have a hardware button that turns on readiness for pairing for a limited period of time. This function is expanded to include the willingness to transfer an eID. This condition is normally indicated visually by means of a signal indicator. The eID is transmitted as follows, for example:

1. 1. The user switches on the readiness for transmission on the end device 50 via a button on the IoT device
2. 2. The module of the selected radio technology is switched on and put into a mode for pairing/transmission of the eID
3. 3. An app for receiving the eID is started on the reading device 10
4. 4. The app prompts the operating system to actively scan for end devices 50 that can connect via Bluetooth and transmit elDs
   1. a. The readout device 10 uses the properties of radio technology to find end devices 50 that indicate that they can transmit an eID. This is done using the “service discovery” methods of radio technology.
5. 5. The app displays the 50 end devices found
6. 6. The user 1 selects one of the terminals 50 found
7. 7. The reading device 10 sends a request 119 to transmit the eID to the selected end device 50
8. 8. The selected terminal 50 receives the request 119 and replies with a status code (which informs about the success or failure of the operation) and, if successful, with the eID
9. 9. The reader 10 receives the response in step 129 and forwards the eID to the app
10. 10. The app processes the eID

4 shows a detailed representation of a second method as it can be carried out in connection with the previously described IoT device. This procedure differs from that in 2 shown by the fact that the user 1 must explicitly switch on the "visibility" of the loT device in step 101 and through this process implicitly agrees to access the eID via the LPA. The visibility of the loT device is automatically terminated in step 133 after a time specified by the manufacturer. With the end of visibility, user 1's permission to access the eID ends automatically. Since user 1 has already given his consent to the transmission of the eID by switching on visibility, the 2 discussed steps 123 (release request) and 125 (release). It should be noted that the scan for new terminals 50 can also be performed permanently. It is therefore not necessary for the scan to be started manually in step 105. The first notification of readiness 103 can thus already trigger the following process, which leads to the transmission of the eID.

Although the invention has been described in detail in the drawings and the foregoing representation, the representations are to be understood as illustrative and exemplary and not restrictive. The invention is not limited to the exemplary embodiments explained.

Further variants of the invention and their implementation result from the above disclosure, the figures and the patent claims for the person skilled in the art.

Terms used in the claims such as “comprise”, “have”, “include”, “contain” and the like do not exclude further elements or steps. The use of the indefinite article does not exclude a plural. A single device can perform the functions of several units or devices mentioned in the claims. Reference signs given in the patent claims are not to be regarded as limitations on the means and steps used.

Reference List

1

user

10

reading device

20

Display device of the readout device

30

List of devices

31

first device

32

second device

33

third device

50

Device with eSIM

52

storage facility

54

processor device

60

Display device of the end device with eSIM

70

confirmation display

71

confirmation field

72

rejection field

80

Local Profile Assistant

101

Turn on visibility

103

notice of readiness

105

start scan

107

scan for devices

109

Registration of the transmitter

111

Query eID characteristics

113

Response eID characteristic

115

Lists of devices

117

Selection of a device

119

eID requirement

121

Confirmation request eID

123

release request

125

Release

127

Confirmation response eID

129

Response to read request eID

131

eID transfer

133

Turn off visibility

Claims (10)

A method for supporting automatic provisioning of a terminal (50) with an embedded subscriber identification module, the method comprising the following steps: - wireless transmission of a readiness message (103) by the terminal (50), - wireless reception of the readiness message (103) by a reading device (10), - wireless request for an identifier linked to the embedded subscriber identification module by the reading device (10), - release of a transmission of the identifier by means of the terminal (50), - reading of the identifier from the embedded subscriber identification module, - wireless transmission of the identifier and a Device identifier of the terminal (50) after the release from the terminal (50) to the readout device (10), - Transmission of the identifier and the device identifier from the readout device (10) to an authentication unit, - verification of the identifier using the device identifier by the authentication unit, - wireless transmission of a user profile uniquely assigned to the identifier to the terminal (50), - installation of the user profile in the embedded subscriber identification module. The procedure according to claim 1 wherein the readiness message signals a readiness to transmit the identifier associated with the embedded subscriber identity module. The procedure according to claim 1 or 2 , wherein the step of enabling the transmission of the identifier comprises the step of: - activating a readiness for transmission for the transmission of the identifier. The procedure according to claim 3 , wherein the readiness to transmit is activated by switching on the terminal (50). The procedure according to claim 3 , wherein the readiness to transmit is activated by an activation signal. The method according to one of claims 2 until 5 , the readiness for transmission being automatically deactivated after activation after a predetermined period of time. The method according to one of claims 2 until 5 , the readiness to transmit being terminated after activation by a deactivation signal. The method of any preceding claim, wherein the step of enabling transmission of the identifier includes the additional step of: - automatic authentication of the readout device (10). The method according to any one of the preceding claims, wherein the identifier is read out and transmitted using the Bluetooth protocol. A system comprising an authentication unit, a readout device (10) and a terminal (50) with an embedded subscriber identification module, the terminal (50) being set up to wirelessly transmit a readiness message (103) to the readout device (10), the readout device (10 ) is set up to request an identifier associated with the embedded subscriber identity module wirelessly from the terminal (50), the terminal (50) being set up to read the identifier from the embedded subscriber identity module, the terminal being set up to read the identifier and a device identifier of the terminal to transmit wirelessly to the readout device (10) after a release, the readout device (10) being set up to transmit the identifier and the device ID to the authentication unit, the authentication unit being set up to identify the identifier using the device ID, the system is further set up, after verification of the identifier, to wirelessly transmit a user profile uniquely associated with the identifier to the terminal (50), and the terminal (50) is set up to install the user profile in the embedded subscriber identification module.

Images