Method for the user-related setup of a terminal device

Abstract

The invention relates to a method for the user-related setup of a terminal device (10) which is connected to a background system (30), wherein the terminal device (10) is connected to a data interchange network (46) by means of a telecommunications profile (TP) stored in a secure element (18). A service platform (50) is provided, which is connected to the background system (30) and to at least one network operator (40) that operates a data interchange network (46). Stored in the service platform (50) is an authorisation token (BT) for providing a telecommunications profile (TP) belonging to the authorisation token (BT). The authorisation token (BT) is linked to a group identifier (VK). The service platform (50) receives a group identifier (VK) or a profile requirement designating a group identifier (VK) from a background system (30) and determines an authorisation token (BT) linked to the group identifier (VK). With the aid of the authorisation token (BT), the service platform (50) effects, via a network operator (40), the loading of a telecommunications profile (TP) belonging to the authorisation token (BT) into the secure element (18) contained in the terminal device (18), whereupon the terminal device (10) is set up to be connected to the data interchange network (46).

Description

[0001] Procedure for user-specific setup of a terminal device

[0002] The invention relates to a method for user-specific configuration of a user terminal connected to a backend system, as well as to a service platform for a management system for user-specific configuration of a terminal. In particular, the invention relates to the connection of a vehicle to a mobile radio network and the configuration of services provided via the vehicle.

[0003] WO2021 / 170506 A1 discloses a method for integrating a communication function into a terminal device. According to this method, a user generates an initialization message, which then sends a request from the terminal device to a management server to implement a communication profile. Based on this request, the management server exchanges data with a network operator. The network operator then sends an activation message to the terminal device to implement a communication profile. To identify the user in the dialogue between the management server and the network operator, the network operator generates a universal network token.

[0004] US 10735944 B2 discloses an eSIM management system that connects mobile network operators, devices of different subscribers, and different eSIM providers. The management system allows for the request-driven, immediate provision of an optimal profile for a device based on individual device attributes that describe the device's technical and functional properties. The device sends a profile request and attributes to the management system, which, accessing a database, selects the best possible profile based on the attributes and then commissions an eSIM provider to generate and deliver a corresponding profile. This known solution makes it possible to provide an optimized profile to a device newly connected to the management system without having to take special precautions regarding who provides the profile.

[0005] US 2016 / 0020802 A1 discloses an eSIM provisioning method that enables the rapid download of a profile to a device. A profile management server transfers an image file, based on which a profile is created.

[0006] EP 3065431 describes a method for incorporating a profile into an eUICC. A download certificate and addressing information are presented to a data processor, which then retrieves a profile from the data processor and transmits it to the eUICC. A relevant practical application involves using an existing telecommunications profile configured for a first terminal for another terminal. The object of the invention is to provide a management system particularly suitable for this application.

[0007] The object is achieved by a method having the features of claim 1. The method according to the invention uses a network identifier which advantageously allows a network identifier assigned to a first terminal to also be used to set up a second or a plurality of further terminals.

[0008] For this purpose, a service platform is advantageously provided, which is connected to network operators on the one hand and to the background systems assigned to the terminal devices on the other. Control data linked to a network identifier is stored in the service platform. Once transmitted, the control data enables a terminal device to initiate the provision of a telecommunications profile via a network operator and also the configuration of services provided by the terminal device.

[0009] The inventive solution is particularly advantageous for vehicles. Here, a technical development is moving toward using vehicle windows for additional purposes and equipping them with materials that counteract the transmission of mobile phone signals. By configuring the functionality of a mobile phone subscriber in the vehicle and using the vehicle's equipment for connection to a mobile phone network, a user has access to a mobile phone connection regardless of whether their own mobile phone could provide this service or whether they even have their own mobile phone.

[0010] A further advantage of the inventive solution is that operators of backend systems only need to adapt their system to a service platform once in order to enable the connection of a terminal device assigned to the backend system to a multitude of network operators. Similarly, network operators only need to adapt their respective data exchange network to a service platform once in order to subsequently offer access to their data exchange network via a multitude of backend systems.

[0011] Exemplary embodiments of the invention are explained in more detail below with reference to the drawings. They show:

[0012] Fig. 1 shows a platform-based management system for managing a plurality of terminal devices;

[0013] Fig. 2 shows part of a storage device of a service platform;

[0014] Fig. 3 shows a login routine for setting up a federated identifier on a service platform;

[0015] Fig. 4 the user-related setup of a terminal device via an assigned background system if a network identifier is already stored in the background system;

[0016] Fig. 5 the user-related setup of a second terminal device via an assigned background system, if no federation identifier has yet been stored for the user in the background system but a federation account has already been set up as a user account on the service platform.

[0017] Fig. 1 shows a platform-based management system for managing a plurality of terminal devices 10. Each terminal device 10 is connected to an associated backend system 30 via a data connection 20. Each terminal device 10 is also capable of connecting, at the user's discretion, to a data exchange network 46 provided by different network operators 40 via a further data connection 22. Each backend system 30 and each network operator 40 are each connected to a service platform 50 via a further data connection 24 and 26, respectively.

[0018] The terminal 10 is a user terminal and can, for example, be a vehicle connected to a manufacturer management system. The manufacturer management system forms the background system 30. The terminal 10 has a user interface 12 and can be connected to a network operator 40 via a first data connection 22 at the user's discretion, and to the manufacturer management system 30 via a second data connection 20.

[0019] The network operators 40 are typically mobile network providers, and the data connections 22 are implemented in a mobile network 46 provided by a network operator 40. The network operators 40 provide communication and other digital services via the data connections 22 in a known manner.

[0020] The data connections 20 to the manufacturer management system 30, as well as the data connections 24, 26, can also be implemented as a mobile radio connection in a mobile radio network 46 and provided by one or more network operators 40. However, other types of data connections and data or telecommunications networks are also possible.

[0021] All data connections 20, 22, 24, 2.6 are appropriately encrypted and secured against unauthorized access.

[0022] Each background system 30 is generally assigned to a set of specific end devices 10. It provides services tailored to the respective end devices 10 via the data connection 20. A user account 32 is maintained in the background system 30. Each user account 32 is assigned one or more end devices 10. An identifier and, if applicable, individual end device data are stored for each user in the user account 32. The identifier can also be assigned to an authentication device 60 of the user.

[0023] A background system 30 may, for example, be operated by a vehicle manufacturer or a car rental company and provide additional services for vehicles of that manufacturer or car rental company.

[0024] The service platform 50 coordinates the connection of the terminal devices 10 to the respective network operators 40 and implements the user-specific configuration of the terminal devices 10. It is configured to receive, process, and forward messages from the background systems 30 to a corresponding network operator 40, as well as messages from a network operator 40 to a corresponding background system 30. The service platform 50 is expediently operated by a provider that is independent of the network operators 40 and the operators of the background systems 30.

[0025] Background systems 30, service platform 50, and network operator 40 are implemented as data processing devices on which programs are executed that implement the described functions. Likewise, terminal device 10 has a data processing unit on which the described functions are executed by executing corresponding programs.

[0026] The proposed solution is not limited to vehicles or cars. It is suitable for all terminal devices 10 that are connected to a backend system 30 and configured to connect to a network operator 40 at the user's discretion.

[0027] The following description is based on the example where the end devices 10 are cars from different manufacturers and the network operators 40 are mobile phone providers. The background systems 30 are assumed to be implemented as management systems of car manufacturers.

[0028] The terminal device 10, such as a car, has a management interface 12 to an associated management system 30. The management interface 12 is generally permanently configured. It is based on a data connection 20, which is expediently established via a mobile radio network 46. It is implemented, for example, via a subscriber identity module using a first secure element 16 implemented in the car in the form of an ellillCC or iU ICC. Authentication data for a network operator 40, specified, for example, by a car manufacturer or a vehicle operator, is stored on the secure element 16. The authentication data connects the terminal device 10 to the data exchange network 46 of the network operator 40 and, via this, to the management system 30.

[0029] In some variants, the data connection can also be established via another wireless network technology, e.g. WIFI or satellite communication.

[0030] The terminal device 10, e.g., the car, further comprises a user interface 14 for receiving and outputting data to and from a user. The user interface 14 may comprise means for manual, individual data input by a user, such as touch-sensitive displays, keyboards, sensors, or cameras. It may also comprise means for device-based data input, such as readers for reading memory elements or an interface for exchanging data with a mobile phone.

[0031] The terminal device 10 further has a second secure element 18, which allows access to a mobile network 46 via a second data connection 22 to a network operator 40. The second secure element 18 can, for example, also be embodied as an eSIM on an eLJICC or iUICC or by a functionality that allows multiple parallel accesses to a mobile network to be managed on a secure element, e.g., by setting up M1EP - Multiple Enabled Profiles. Both secure elements 16, 18 can, in principle, be active simultaneously and operated according to the DSDA (Dual SIM Dual Active) principle or the DSDS (Dual SIM Dual Standby) principle. Using the secure element 18, a terminal device 10 can establish a connection to a mobile network 46 in a manner known per se.

[0032] In one variant, only a single secure element can be provided, which provides an initial basic connection (bootstrap connectivity) at the start of use, which is replaced by this after the initial loading of a profile and the establishment of a user-specific end-customer connection. This initial basic connection can also be established via another wireless network technology, such as Wi-Fi or satellite communication.

[0033] The service platform 50 has a defined interface to each connected management system 30. It also has a defined network operator interface to each of the connected network operators 40. It also has a control unit and a storage device 52.

[0034] For each user for whom a terminal device 10 has been configured via the service platform 50, data defining a federation identity within the management system is stored in the storage device 52. The structure of this data is illustrated in Fig. 2, which shows part of a storage device 52 of a service platform 50. The data typically includes an individual federation identifier VK, the terminal identifiers EK of one or more terminal devices 10, such as cars, as well as associated control data KD for setting up a service configuration in a terminal device 10. The data also includes authorization tokens BT, which are issued by network operators 40. Furthermore, the data includes status information about completed activations of telecommunications profiles.The data are conveniently stored in federation accounts 54 maintained on the service platform 50, wherein each federation account 54 is identified by a unique federation identifier VK and is thereby assigned to a user.

[0035] Network operators 40 operate data exchange networks 46 and provide communication services for terminal devices 10 in a known manner. In the following, it is assumed that network operators 40 are mobile network providers and data exchange networks 46 are mobile networks.

[0036] Each mobile radio provider 40 has a profile data output unit 42, typically in the form of an SM-DP+, via which telecommunication profiles in particular are output to terminal devices 10, as well as a server 44 for storing customer-specific profile and subscriber data.

[0037] The connection between terminal device 10 and mobile network provider 40 in a mobile network 46 is established via a communications service provided by the mobile network provider 46. This service typically uses standardized methods, such as those described in the GSMA standard SGP.22.

[0038] Prerequisites for using the communication services are authentication and proof of access authorization. Proof of access authorization is provided using a secure element 18 stored on the terminal device 10, typically in the form of an eSIM. Authorization data, typically in the form of telecommunications profiles (TP), is stored on the secure element 18. The telecommunications profiles (TP), also referred to below as profiles, contain information necessary to make calls and operate in a mobile network 46. TP profiles belong to the respective mobile network provider 40 and are provided by them. They generally contain at least one network access authorization, typically an MSI, profile management key, and authentication parameters.

[0039] The arrangement shown in Fig. 1 enables a user to establish network access on a first terminal 10 and to provide network access with the same functionality available to a user on a first terminal 10 on a further terminal 10.

[0040] In a registration routine, the user sets up a composite identifier VK on a service platform 50. Fig. 3 shows the initial setup of a composite identifier VK on a service platform 50 by a user for whom no composite identifier VK has yet been stored on the service platform 50.

[0041] In a first step 100, the user authenticates himself with the terminal 10. Authentication is expediently performed electronically using an authentication device 60. This can be, for example, a portable device in the form of an electronic key, an IC card, or a mobile phone. Alternatively, the authentication device 60 can be permanently connected to the terminal 10, for example, in the form of an input unit, a biometric sensor, or a camera.

[0042] Then, in a step 102, the user authenticates himself to the background system 30 associated with the terminal device 10. The second authentication can be performed in the same way as the first authentication. It may require the presentation of additional authentication credentials, such as a PIN. The two authentication steps 100, 102 can also be combined, so that authentication to the terminal device 10 and the background system 30 occurs simultaneously.

[0043] After authentication, the backend system 30 determines whether the user wishes to set up a federated identifier (VK). If so, the backend system 30 sends a request to the service platform 50 in the following step 104.

[0044] The service platform 50 then transmits to the background system 30, step 106, a list of selectable network operators 40, which is forwarded by the background system 30 to the user via the terminal 10.

[0045] The user selects a network operator 40 with an associated data exchange network 46, step 108, and communicates this via the terminal 10 to the background system 30, which forwards the message to the service platform 50.

[0046] In the next step 110, the service platform 50 transmits a request for the provision of an authorization token BT to the selected network operator 40.

[0047] The network operator 40 receives the request and then starts an authentication routine 112, in which the user verifies their authorization to use the selected network 46. The network operator 40 sends a message to the user, either directly or via the service platform 50, the background system 30, and the terminal 10, presenting the authorization data. The user then presents their authorization data. The authorization data can, for example, be authentication data for logging a user's mobile device, such as a smartphone, into a mobile network.

[0048] The network operator 40 checks the authorization data. If the check is positive, it calculates an authorization token BT in the following step 114, which authorizes an entity subsequently presenting the authorization token BT to request a telecommunications profile TP associated with the authorization token BT. The authorization token BT is a data set and must be created in such a way that it is unique for a background system 30 and a specific network operator 40. This means that there must be no ambiguity at the network operator 40.

[0049] The network operator 40 transmits the authorization token BT to the service platform 50, step 116.

[0050] Subsequently, the network operator 40 updates the user's profile stored in the server 44, step 118.

[0051] The service platform 50 then creates a federation account 54 for the user at the service platform 50, unless this has already been done upon receipt of the request. To this end, in step 120, the service platform 50 creates a federation identifier VK that is specific to the federation account 54. Furthermore, the service platform 50 generates access data ZD to access the federation account 54 and the associated calculated federation identifier VK. The access data ZD is or contains a secret, typically a password or a PIN. The federation identifier VK links the service platform 50 to the federation account 54 and, through it, to the authorization token BT. It stores the link and authorization token BT in the federation account 54 (step 122). In the subsequent step 124, the service platform 50 transmits the federation identifier VK to the background system 30. This updates the user account 32 maintained there (step 126).

[0052] In a further subsequent step 128, the service platform 50 transmits the network identifier VK and the access data ZD for the network identifier VK to the user via the background system 30 and the terminal 10.

[0053] The service platform 50 is then set up for the user. A federation account 54 is set up, which the user can access by presenting the access data ZD.

[0054] Fig. 4 shows the user-related setup of a terminal device 10 via an assigned background system 30, if a network identifier VK is already stored for the user in the background system 30.

[0055] In a first step 200, the user authenticates himself with the terminal 10. Authentication is expediently performed electronically using an authentication device 60. This can be, for example, a portable device in the form of an electronic key, an IC card, or a mobile phone. Alternatively, the authentication device 60 can be permanently connected to the terminal 10, for example, in the form of an input unit, a biometric sensor, or a camera.

[0056] The user then authenticates (step 202) to the background system 30 associated with the terminal device 10. The second authentication can be performed in the same way as the first authentication. It may require the presentation of additional authentication credentials, such as a PIN. The two authentication steps 200, 202 can also be combined, so that authentication occurs simultaneously with the terminal device 10 and the background system 30. During the authentication, the terminal identifier EK is transmitted to the background system 30.

[0057] After successful authentication, the background system 30 checks, in step 204, whether a federation identifier VK is stored for the terminal device 10 in the background system 30 and whether a federation account 54 has been set up on the service platform 50.

[0058] If this is the case, the backend system 30 sends a request for a profile to the service platform 50 in step 206. The profile request contains a date that uniquely identifies the federation account 54, the federation identifier VK, or the user. The date can, in particular, be the federation identifier VK itself. In one variant, an authorization token BT can already be stored for the user in the backend system 30. If this is the case, the request can also be made by the backend system 30 sending the authorization token BT to the service platform 50.

[0059] Based on the request, the service platform 50 determines the federation account 54 for the user and determines the authorization token BT stored there as well as the associated network operator 40 (step 208). The service platform 50 transmits the authorization token to the determined network operator 40 (step 209).

[0060] The network operator 40 checks the received authorization token BT. If the authorization token is valid, it provides the user with a telecommunications profile TP (step 210); it also calculates download information DI for the profile TP. The network operator 40 stores the determined telecommunications profile TP on a server 44 of the network operator and transmits the download information DI to the service platform 50 (step 212). The download information DI is typically an activation code according to the SGP.22 standard, provided that the terminal device 10 is configured according to the SGP.22 standard.

[0061] After receiving the download information DI, the service platform 50 updates the federation account 54 maintained by it, step 214. Furthermore, the service platform 50 determines any control data KD stored in the federation account 54 for setting up a service configuration, i.e., for setting up customer-specific settings and services in a terminal device 10.

[0062] If the terminal device is a vehicle 10, the control data KD can be used, for example, to set up customer-specific, terminal-independent value-added services on the vehicle's infotainment system, e.g., to use audio data or execute payment transactions. In other terminal devices 10, they can be used, for example, to set up a 5G router, an SG modem of a portable computer, or a 5G modem in a mobile device. The control data KD or the configuration of the services are expediently defined by the user during regular operation of a terminal device 10 and transmitted from the terminal device 10 to the respective background system 30. The involved background system 30 then transmits new or changed control data KD to the service platform 50.

[0063] In the following step 216, the service platform 50 transmits the download information DI together with the control data KD to the background system 30 for setting up a service configuration.

[0064] The background system 30 updates the user account maintained by it, step 218. Furthermore, the background system 30 transmits the download information DI and the control data KD for setting up a service configuration to the terminal device 10, step 220.

[0065] After receiving the download information DI, the terminal 10 establishes a direct connection to the network operator 40 associated with the download information DI via the data connection 22 and requests the transmission of a telecommunications profile TP from the network operator 40 in a step 222 using the download information DI.

[0066] The network operator 40 checks the request and, if it is valid, sends the provided profile TP via the data connection 22 to the terminal device 10, step 224.

[0067] The terminal device 10 sets up the telecommunications profile TP and activates it, step 226. The request for the profile TP and its activation in the terminal device 10 are carried out, for example, according to GSMA standards, e.g., according to the GSMA standard SGP.22.

[0068] In addition to setting up the telecommunications profile TP, the terminal 10 configures the services provided by the terminal 10 based on the received control data KD. After the services have been activated and configured, the terminal 10 sends confirmation information to the background system 30, step 228.

[0069] The background system 30 then updates the user account 32, step 230, and in turn sends setup information to the service platform 50, step 232.

[0070] The service platform 50 then updates the federation account 54 maintained by it, step 234. In doing so, it stores the activation of the transmitted telecommunications profile TP as the new status of the terminal device 10. In a step 240 executed independently of this, the network operator 40 further updates the customer-specific data stored in the server 44 after transmitting the telecommunications profile TP and also stores the activation of the transmitted telecommunications profile TP.

[0071] Fig. 5 shows the user-related setup of a second terminal 10 via an assigned background system 30, if no association identifier VK is yet stored for the user in the background system 30, but a federation account 54 has already been set up for the user on the service platform 50.

[0072] In a first step 300, the user first authenticates himself with the second terminal 10. Authentication is expediently performed electronically using an authentication device 60. This can be, for example, a portable device in the form of an electronic key, an IC card, or a mobile phone. Alternatively, the authentication device 60 can be permanently connected to the terminal, for example, in the form of an input unit, a biometric sensor, or a camera.

[0073] The second terminal 10 then registers the user with the background system 30, which is assigned to the second terminal 10, in step 302. During the registration process, the second terminal 10 transmits its terminal identifier EK to the background system 30. Furthermore, the terminal 10 determines the user's network identifier VK. This can be done automatically by issuing a corresponding input request via the interface 14 or, if the user uses an authentication device 60, for example, in the form of an electronic key, an IC card, or a mobile phone.

[0074] After receiving the association identifier VK, the background system 30 determines whether a link with the association identifier VK is already stored in the user account 32, step 304.

[0075] If this is not the case, as assumed in the embodiment of Fig. 5, the background system 30 sends the association identifier VK to the service platform 50. Together with the association identifier VK, it transmits the identifier EK for the terminal 10, step 306.

[0076] After receiving the federation identifier VK, the service platform 50 checks whether a federation account 54 has already been created for it, step 308. If this is the case, as assumed in the exemplary embodiment, the service platform 50 requests the user to authenticate himself.

[0077] For this purpose, the service platform 50 expediently sends a message to the second terminal 10 via the background system 30, requesting the user to log in to the federated account 54 (step 310). If, as assumed in the example, simple authentication is provided for the login, the user then presents a secret to authenticate themselves to the service platform 50. The secret is, for example, the password or PIN associated with the federated account 54. It is transmitted to the service platform 50 via the second terminal 10 and background system 30 (step 312).

[0078] As an alternative to simple authentication, advanced security mechanisms, such as two-factor authentication, can also be used. The process is then adapted accordingly.

[0079] The service platform 50 checks the received login data. If they are correct, the

[0080] Service platform 50 derives the authorization token BT from the federation account 54 designated by the association identifier VK and links it to the second terminal 10, step 314. To do this, service platform 50 links the federation account 54 and thus the authorization token BT with the identifier EK of the second terminal 10.

[0081] The service platform 50 then updates the federation account 54 (step 316) and adds the previously created link to the second terminal 10. This can be done by storing the terminal identifier EK of the second terminal 10 as known in the federation account 54. The federation account 54 now contains at least one link to the second terminal 10 performing the current setup, as well as one link to a terminal 10 for which a link was saved at an earlier time.

[0082] In a next step, the service platform 50 sends the authorization token BT to the determined network operator 40 (step 318). Furthermore, the service platform 50 sends information about the updated association identifier VK to the background system 30 (step 320). Upon receipt, the background system 30 updates the user account 32 (step 322).

[0083] The following steps correspond to the steps described with reference to Fig. 4 for the user-related setup of a terminal device 10 via an assigned background system 30, if a network identifier VK is already stored for the user in the background system 30.

[0084] The network operator 40 checks the received authorization token BT. If the authorization token is valid, it provides the user with a telecommunications profile TP (step 324). This profile TP is equivalent to the profile for the terminal device 10, for which a link was previously stored in the federation account 54. Both profiles are typically based on the same customer contract.

[0085] It then calculates download information DI for the profile TP. The network operator 40 stores the determined telecommunications profile TP on a server of the network operator 40. It transmits the download information DI to the service platform 50, step 326. The download information DI is typically an activation code according to SGP.22, provided the terminal device 10 is configured according to the SGP.22 standard.

[0086] After receiving the download information DI, the service platform 50 updates the federation account 54 maintained by it (step 328). Furthermore, the service platform 50 determines control data KD stored in the federation account 54 for setting up a service configuration on the terminal device 10. In the following step 330, the service platform 50 transmits the download information Di together with the control data KD for setting up a service configuration to the background system 30.

[0087] The background system 30 updates the user account maintained by it, step 332. Furthermore, the background system 30 transmits the download information DI and the control data KD for setting up a service configuration to the second terminal 10, step 334.

[0088] After receiving the download information DI, the terminal 10 establishes a direct connection to the network operator 40 associated with the download information via the data connection 22 and requests the transmission of a telecommunications profile TP from the network operator 40 in a step 336 using the download information DI.

[0089] The network operator 40 checks the request, determines the profile TP provided for this purpose and sends it to the second terminal 10 via the data connection 22, step 338. The second terminal 10 sets up the telecommunications profile TP and activates it, step 342. The request for the telecommunications profile TP and the activation in the second terminal 10 are carried out, for example, according to a GSMA standard, e.g., according to the GSMA standard SGP.2.2.

[0090] In addition to setting up the telecommunications profile TP, the second terminal 10 configures the services provided by the second terminal 10 based on the received control data KD, step 344. After activation and setup of the services, the second terminal 10 sends confirmation information to the background system 30, step 346.

[0091] The background system 30 then updates the user account 32, step 348, and in turn sends setup information to the service platform 50, step 350.

[0092] Upon receipt, the service platform 50 updates the federation account 54 maintained by it, step 352. It stores the activation of the transmitted telecommunications profile TP as the new status of the second terminal device 10.

[0093] In a step 340 executed independently, the network operator 40 further updates the customer-specific profile data stored in the server 44 after transmission of the telecommunications profile TP and also stores the activation of the transmitted telecommunications profile TP.

[0094] The second terminal 10 is then configured to establish a connection to the data exchange network 46 designated by the telecommunications profile TP using an equivalent telecommunications profile TP, as was initially provided for another terminal 10. Furthermore, services that a user had previously defined are configured on the terminal 10. The user's network identifier VK is also stored in the user account 32 associated with the terminal 10. The user can then quickly set up additional terminals 10 assigned to the same background system 30.

[0095] While maintaining the basic idea, the prescribed solution allows for a multitude of configurations and variants that are not described individually. This applies, among other things, to the design and structure of the data processing components. Furthermore, the structures underlying the description and the elements of the exemplary embodiments described with reference to the figures are not to be understood as constituting the only possible embodiments in the exact arrangement described. Rather, combinations and modifications of the elements and processes are possible where appropriate and feasible.

[0096] List of reference symbols

[0097] 10 user terminal

[0098] 12 Interface

[0099] 14 User interface

[0100] 16 Safe element

[0101] 18 Safe element

[0102] 20 Data connection

[0103] 22 Data connection

[0104] 24 Data connection

[0105] 26 Data connection

[0106] 30 background system

[0107] 32 User account

[0108] 40 network operators

[0109] 42 Profile data output unit

[0110] 44 servers

[0111] 46 Data exchange network

[0112] 50 service platform

[0113] 52 Storage device

[0114] 54 Federation Account

[0115] 60 authentication devices

[0116] VK network identifier

[0117] EK terminal device identification

[0118] BT authorization token

[0119] DI download information

[0120] TP Telecommunications Profile

[0121] KD control data for setting up a service configuration

[0122] ZD access data

Claims

Patent claims 1. A method for user-specific setup of an end device (10) connected to a background system (30), wherein the end device (10) is connected to a data exchange network (46) by means of a telecommunications profile (TP) stored in a secure element (18), wherein a service platform (50) is provided which is connected to the background system (30) and to at least one network operator (40) operating a data exchange network (46), wherein the service platform (50) contains an authorization token (BT) for providing a telecommunications profile (TP) belonging to the authorization token (BT), wherein the authorization token (BT) is linked to a federation identifier (VK), and wherein a background system (30) transmits a federation identifier (VK) or a profile request designating a federation identifier (VK) to the service platform (50) (206).wherein the service platform (50), upon receiving a federation identifier (VK) or a profile request designating a federation identifier (VK), determines an authorization token (BT) associated with the federation identifier (VK) (208), wherein the service platform (50), using the determined authorization token (BT), causes a telecommunications profile (TP) belonging to the authorization token (BT) to be loaded into the secure element (18) contained in the terminal device (10) via a network operator (40) (224), whereupon the terminal device (10) is configured to connect to the data exchange network (46).

2. Method according to claim 1, characterized in that the service platform (50) is configured to request a secret from a user after receiving a federation identifier (VK) or a profile request designating a federation identifier (VK) in order to authenticate the user to the service platform (50) (310, 312).

3. Method according to one of the preceding claims, characterized in that the service platform (50) is configured to link an authorization token (BT) stored on the service platform (50) for a federation identifier (VK) with a further terminal device (10) (314).

4. Method according to one of the preceding claims, characterized in that the service platform (50) is configured to establish a connection to a network operator (40) and to cause the latter to generate a telecommunications profile (TP) and to send back an associated download information (DI) (210, 212, 318, 326).

5. Method according to claim 4, characterized in that the service platform (50) transfers the download information (DI) to the background system (30) (216, 330).

6. Method according to one of the preceding claims, characterized in that the service platform (50) generates access data (ZD) to a federated identifier (VK) which is or contains a secret, and the access data (ZD) are transmitted to the user (128).

7. Method according to one of the preceding claims, characterized in that the service platform (50) contains control data (KD) for setting up a service configuration for a federation identifier (VK), which are transmitted to the background system (30) (216), whereupon the stored services are set up on the terminal device (10) using the control data (KD) (228).

8. Method according to claim 7, characterized in that the service configuration is the setup of an infotainment system of a vehicle or the setup of customer-specific settings and services in a device equipped with a mobile communication unit, such as a computer or a 5G router.

9. Method according to one of the preceding claims, characterized in that authentication of a user to the terminal device (10) takes place (200, 300).

10. Method according to claim 9, characterized in that the authentication of the user to the terminal device (10) is carried out using an authentication device (60).

11. Method according to one of the preceding claims, characterized in that the compound identifier (VK) is transmitted using an authentication device (60).

12. Method according to one of the preceding claims, characterized in that the network identifier (VK) and the secret for authentication are generated by the service platform (50) in a login routine (124, 128) in which a user determines a data exchange network (46) for which a telecommunications profile (TP) is to be provided (108).

13. Method according to one of the preceding claims, characterized in that the service platform (50) is configured to request (110) an authorization token (BT) from a data exchange network (46) specified by a user and, upon receipt, to calculate (120) a federation identifier (VK) and to link (122) this to the authorization token (BT).

14. Method according to one of the preceding claims, characterized in that the terminal device (10) is a vehicle or a device with a mobile communication unit.

15. Service platform (50) for a management system for user-related setup of an end device (10), wherein the service platform (50) is connected to at least one network operator (40) and to at least one background system (30), wherein at least one background system (30) is connected to the end device (10) and the end device (10) is connected to a telecommunications profile (TP) stored in a secure element (18) is connected to a data exchange network (46), the service platform (50) being set up to perform the following steps: Receiving, processing and forwarding messages from the at least one background system (30) to a network operator (40). Receiving, processing and forwarding messages from at least one network operator (40) to a background system (30), Setting up a federation account (54) linked to a federation identifier (VK), Depositing an authorization token (BT) to provide a telecommunications profile (TP) in the federation account (54), Receiving a network identifier (VK) and an endpoint identifier (EK) via a background system (30), Check if a federation account (54) with an authorization token (BT) has already been created for the received federation identifier (VK), Requesting a secret from a user when a Federation Account (54) has already been created, Linking the terminal identifier (DC) to the federation account (54) upon successful transmission of the secret, Enabling the provision of a telecommunications profile (TP) for the terminal device (10) identified by the terminal device identifier (EK) via a network operator (40) using the authorization token (BT) stored in the federation account (54).

Images