Method for setting a terminal device associated to a user

Abstract

The invention relates to a method for user-dependent settings of a terminal (10) connected to a background system (30), the terminal (10) being connected to a data exchange 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 at least one network operator (40) operating the data exchange network (46). An authorization token (BT) for providing a telecommunications profile (TP) belonging to the authorization token (BT) is stored in the service platform (50), the authorization token (BT) being linked to the joint identifier (VK). The service platform (50) receives a joint identifier (VK) or a profile request specifying the joint identifier (VK) from the background system (30) and determines an authorization token (BT) linked with the joint identifier (VK). The service platform (50) loads a telecommunications profile (TP) associated with an authorization token (BT) into a secure element (18) contained in the terminal (10) by means of the authorization token (BT) by means of the network operator (40), and then the terminal (10) is arranged to be connected to the data exchange network (46).

Description

Technical Field

[0001] The present invention relates to a method for making user-related settings for a user terminal device connected to a backend system, and a management system service platform for making user-related settings for a terminal device. In particular, the present invention relates to the connection of a vehicle to a mobile radio network and the configuration of services provided by the vehicle. Background Art

[0002] A method for introducing communication functions into a terminal device is known from WO 2021 / 170506 A1, according to which a user generates an initialization message, in response to which the terminal device sends a request to a management server to implement a communication profile. Based on the request, the management server conducts the data exchange with the network operator. Finally, the network operator sends an activation message for implementing the communication profile to the terminal device. In order to identify the user in the dialogue between the management server and the network operator, the network operator generates a universal network token.

[0003] From US10735944 B2 an eSIM management system is known, which connects mobile radio network operators, terminal devices of different participants and different eSIM providers to one another. The management system allows the best profile to be immediately provided to the terminal device in a request-driven manner based on personalized terminal device attributes, which describe the technical and functional characteristics of the terminal device. The terminal device sends a profile request and the attributes to the management system, which selects the best possible profile based on the attributes by accessing a database and then entrusts the eSIM provider to generate and provide the corresponding profile. This known solution makes it possible to provide optimized profiles to terminal devices newly connected to the management system without having to make special arrangements as to who provides the profiles.

[0004] US2016 / 0020802 A1 discloses an eSIM provision method, which enables a configuration file to be quickly downloaded to a terminal device. To this end, an image file is transmitted from a configuration file management server, and a configuration file is set based on the image file.

[0005] EP 3065431 describes a method for introducing a configuration file into an eUICC, in which a download certificate and addressing information are transmitted to a data preparer, by means of which the configuration file is called from the data preparer and transmitted to the eUICC. A relevant application in practice is to use an existing telecommunication configuration file set for a first terminal device for another terminal device. The technical problem to be solved by the present invention is to provide a management system that is particularly suitable for such an application case. Summary of the invention

[0006] This object is achieved by a method having the features of claim 1. The method according to the invention uses a joint identifier which advantageously allows a joint identifier assigned to a first terminal to also be used for setting up a second or multiple further terminals.

[0007] Advantageously, a service platform is provided for this purpose, which is connected to the network operator on the one hand and to a backend system associated with the terminal device on the other hand. Control data linked to the joint identifier are stored in the service platform. After the control data are transmitted, the control data enable the terminal device to provide a telecommunication profile through the network operator and also configure the services provided by the terminal device.

[0008] The solution according to the invention is particularly advantageous for vehicles. In this case, the technical development is to use the vehicle windows for additional purposes and to provide them with materials that can counteract the transmission of mobile radio signals. By providing the function of a mobile radio participant in the vehicle and using a device on the vehicle side for connecting to a mobile radio network, a mobile radio connection can be provided to the user regardless of whether his own mobile phone is capable of carrying out a mobile radio connection or whether the user has his own mobile phone ready at all.

[0009] Another advantage of the solution according to the invention is that the operator of the backend system only has to adapt his system to the service platform once, in order to be able to realize the possibility of connecting the terminal equipment associated with the backend system to multiple network operators. Likewise, the network operators only have to adapt their respective data exchange networks to the service platform once, in order to be able to subsequently provide access to their data exchange networks via multiple backend systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The embodiments of the present invention are further described below in conjunction with the accompanying drawings. In the accompanying drawings:

[0011] Figure 1 A management system supported by a platform for managing multiple terminal devices is shown;

[0012] Figure 2 A portion of a storage device of a service platform is shown;

[0013] Figure 3 A registration routine for setting up a federated identifier on a service platform is shown;

[0014] Figure 4 It shows the user-related settings made to the terminal device by the associated background system when the joint identifier has been stored in the background system;

[0015] Figure 5It shows the user-related settings made to the second terminal device by the associated background system when a joint identifier has not been stored for the user in the background system, but a federation account has been set up as a user account on the service platform. DETAILED DESCRIPTION

[0016] Figure 1 A management system supported by a platform for managing a plurality of terminal devices 10 is shown. Each terminal device 10 is connected to an associated background system 30 via a data connection 20. Each terminal device 10 can also be connected to a data exchange network 46 provided by a different network operator 40 via an additional data connection 22 according to the user's choice. Each background system 30 and each network operator 40 are connected to a service platform 50 via an additional data connection 24 or 26, respectively.

[0017] The terminal device 10 is a user terminal device, which can be, for example, a vehicle connected to a manufacturer management system. Here, the manufacturer management system constitutes a background system 30. The terminal device 10 has a user interface 12, and according to the user's selection, can be connected to a network operator 40 through a first data connection 22, and connected to a manufacturer management system 30 through a second data connection 20.

[0018] The network operator 40 is typically a mobile radio provider and implements the data connection 22 in a mobile radio network 46, which is provided by the network operator 40. The network operator 40 provides communication and other digital services via the data connection 22 in a known manner.

[0019] Data connection 20 and data connections 24, 26 to manufacturer management system 30 may also be designed as mobile radio connections in mobile radio network 46 and provided by one or more network operators 40. However, other types of data connections and data or telecommunication networks may also be used.

[0020] All data connections 20, 22, 24, 26 are suitably encrypted and secured to prevent access by unauthorized persons.

[0021] Each backend system 30 is usually associated with a specific set of terminal devices 10. It provides customized services for the corresponding terminal devices 10 via the data connection 20. User accounts 32 are managed in the backend system 30. Each user account 32 is associated with one or more terminal devices 10. An identifier and, if necessary, personalized terminal device data are stored for each user in the user account 32. The identifier can also be associated with the user's authentication device 60.

[0022] For example, the backend system 30 may be operated by a vehicle manufacturer or a car rental company and provide additional services for the vehicles of the manufacturer or the car rental company.

[0023] The service platform 50 coordinates the connection between the terminal device 10 and the corresponding network operator 40, and performs user-related settings on the terminal device 10. It is designed to receive, process and forward messages from the background system 30 to the corresponding network operator 40, and receive, process and forward messages from the network operator 40 to the corresponding background system 30. The service platform 50 is preferably operated by a provider independent of the network operator 40 and the operator of the background system 30.

[0024] The backend system 30, the service platform 50 and the network operator 40 are designed in the form of data processing devices, on which programs for implementing the described functions are executed. The terminal device 10 also has a data processing unit, on which the described functions are executed by executing corresponding programs.

[0025] The proposed solution is not limited to vehicles or cars. It is suitable for all terminal devices 10, which are connected to the background system 30 on the one hand and are designed to be connected to the network operator 40 according to the user's choice on the other hand.

[0026] The following description is based on the exemplary embodiment in which the terminal device 10 is a car from a different manufacturer and the network operator 40 is a mobile radio provider. For the background system 30, it is assumed that it is designed as a management system of the car manufacturer.

[0027] The terminal device 10, i.e., for example, a motor vehicle, has a management interface 12 to an associated management system 30. The management interface 12 is usually permanently arranged. It is based on a data connection 20 which is suitably established via a mobile radio network 46. For example, it can be implemented by means of a first secure element 16 in the form of an eUICC or iUICC implemented in the motor vehicle via a subscriber identity module. Authentication data for a network operator 40, which is specified, for example, by a motor vehicle manufacturer or a vehicle operator, are stored on the secure element 16, by means of which the terminal device 10 is connected to a data exchange network 46 of the network operator 40 and thus to the management system 30.

[0028] In a variant, the data connection can also be established via other radio network technologies, such as WIFI or satellite communication.

[0029] The terminal device 10, i.e., for example, a car, also has a user interface 14 for receiving data from a user and outputting data to the user. The user interface 14 can include components for the user to manually input data individually, such as a touch-sensitive display, a keyboard, a sensor or a camera. It can also include components for inputting data in a device-based manner, such as a reading device for reading a storage element or an interface for exchanging data with a mobile phone.

[0030] The terminal device 10 also has a second security element 18, which can access the mobile radio network 46 via a second data connection 22 with the network operator 40. For example, the second security element 18 can also be designed as an eSIM on an eUICC or iUICC, or by a function that allows multiple parallel accesses to the mobile radio network to be managed on the security element, for example by setting MEP (Multiple Enabled Profiles). In principle, the two security elements 16, 18 can be activated simultaneously and can be operated according to the DSDA (Dual SIM Dual Active) principle or the DSDS (Dual SIM Dual Standby) principle. With the help of the security element 18, the terminal device 10 can establish a connection with the mobile radio network 46 in a manner known per se.

[0031] In a variant, only a single secure element can also be provided, which provides a first basic connection (bootstrap connectivity) at the beginning of use, which is replaced by the user-related end-client connection after the configuration file has been loaded for the first time and the user-related end-client connection has been set up. The first basic connection can also be established via other radio network technologies, such as WIFI or satellite communication.

[0032] The service platform 50 has a defined interface with each connected management system 30. The service platform 50 also has a defined network operator interface with each connected network operator 40. The service platform 50 also has a control unit and a storage device 52.

[0033] In the storage device 52, for each user who has set up the terminal device 10 through the service platform 50, data defining the alliance identity in the management system is stored. Figure 2The structure of the data is shown in , which shows a part of the storage device 52 of the service platform 50. The data generally includes a personalized joint identifier VK, one or more terminal devices 10, i.e., a terminal device identifier EK of a car, and correspondingly associated control data KD for setting the service configuration in the terminal device 10. The data also includes an authorization token BT issued by the network operator 40. The data also includes status information about the completed activation of the telecommunication profile. The data is suitably stored in a federation account 54 managed on the service platform 50, wherein each federation account 54 is identified by a unique joint identifier VK and is associated with the user via the joint identifier VK.

[0034] The network operator 40 operates a data switching network 46 and provides communication services in a known manner for the terminal device 10. In the following, it is assumed that the network operator 40 is a mobile radio provider and the data switching network 46 is a mobile radio network.

[0035] Each mobile radio provider 40 has a profile data output unit 42 , usually in the form of an SM-DP+, by means of which a telecommunications profile is output, in particular, to the terminal 10 , and a server 44 for storing customer-specific profile data and user data.

[0036] The connection of the terminal 10 to the mobile radio provider 40 in the mobile radio network 46 takes place via a communication service provided by the mobile radio provider 46. The mobile radio provider 46 usually uses standardized methods such as are described in the GSMA standard SGP.22, for example.

[0037] Authentication and proof of access authorization are prerequisites for using communication services. The proof of access authorization is carried out with the help of a secure element 18 stored on the terminal device 10, usually in the form of an eSIM. The authorization data is usually stored on the secure element 18 in the form of a telecommunications profile TP. The telecommunications profile TP (which is also referred to as profile in the following) contains the information required to enable calls and actions in the mobile radio network 46. The profile TP belongs to the corresponding mobile radio provider 40 and is provided by it. The profile TP usually contains at least a network access authorization, usually an IMSI, a profile management key and authentication parameters.

[0038] Figure 1 The arrangement shown enables a user to establish network access at a first terminal 10 and to also provide network access with the same functionality as that available to the user at the first terminal 10 at another terminal 10 .

[0039] To this end, during a registration routine, the user sets a joint identifier VK on the service platform 50 . Figure 3The process of setting up the joint identifier VK on the service platform 50 for the first time by a user who has not stored the joint identifier VK on the service platform 50 is shown.

[0040] In a first step 100, the user authenticates in the terminal device 10. The authentication is suitably 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 fixedly connected to the terminal device 10, for example in the form of an input unit, a biometric sensor or a camera.

[0041] Then, in step 102, the user authenticates with respect to the backend system 30 associated with the terminal device 10. The second authentication can be performed in the same manner as the first authentication. It may require the presentation of additional authentication proof, such as in the form of a password. The two authentication steps 100, 102 can also be combined, so that authentication is performed with respect to the terminal device 10 and the backend system 30 at the same time.

[0042] After the authentication is complete, the backend system 30 determines whether the user wants to set a joint identifier VK. If this is the case, the backend system 30 sends a request to the service platform 50 in the next step 104.

[0043] Subsequently, the service platform 50 transmits a list of selectable network operators 40 to the background system 30 , and in step 106 , the background system 30 forwards the list to the user via the terminal device 10 .

[0044] The user selects a network operator 40 with an associated data exchange network 46 , step 108 , and transmits it to the background system 30 via the terminal device 10 , and the background system 30 forwards the notification to the service platform 50 .

[0045] In the following step 110 , the service platform 50 transmits a request to the selected network operator 40 for providing an authorization token BT.

[0046] The network operator 40 receives the request and then starts an authentication routine 112, in which the user proves that he is authorized to use the selected network 46. To this end, the network operator 40 sends a notification to the user to present authorization data directly or through the service platform 50, the backend system 30 and the terminal device 10. The user then presents his authorization data. For example, the authorization data can be authentication data for logging the user's mobile radio device (e.g., a smartphone) into the mobile radio network.

[0047] The network operator 40 checks the authorization data. If the check result is positive, the network operator 40 calculates an authorization token BT in a subsequent step 114, which authorizes the entity that subsequently submits the authorization token BT to request the telecommunication profile TP belonging to the authorization token BT. The authorization token BT is a data set and must be created so that it is unique for the background system 30 and the specific network operator 40. This means that there is no ambiguity at the network operator 40.

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

[0049] The network operator 40 then updates the user profile stored in the server 44 , step 118 .

[0050] Subsequently, the service platform 50 creates a federation account 54 for the user in the service platform 50 (if it has not already been created when the request is received). To this end, in step 120, the service platform 50 forms a federation identifier VK specific to the federation account 54. In addition, the service platform 50 generates access data ZD in order to be able to access the federation account 54 and the associated calculated federation identifier VK. The access data ZD is or contains a secret, usually 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 the authorization token BT in the federation account 54, step 122.

[0051] In a subsequent step 124 , the service platform 50 transmits the joint identifier VK to the backend system 30 . The backend system 30 updates the user account 32 managed there, step 126 .

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

[0053] Then, the service platform 50 is set up for the user. An alliance account 54 is set up, which the user can access by submitting access data ZD.

[0054] Figure 4 It shows the user-related settings made to the terminal device 10 by the associated background system 30 when a joint identifier VK has been stored for the user in the background system 30 .

[0055] In a first step 200, the user authenticates in the terminal device 10. The authentication is suitably 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 fixedly connected to the terminal device 10, for example in the form of an input unit, a biometric sensor or a camera.

[0056] The user then authenticates with respect to the backend system 30 associated with the terminal device 10, step 202. The second authentication can be performed in the same way as the first authentication. It may require the presentation of an additional authentication proof, for example in the form of a password. It is also possible to combine the two authentication steps 200, 202 so that authentication is performed simultaneously with respect to the terminal device 10 and the backend system 30. During the full authentication process, the terminal device identifier EK is transmitted to the backend system 30.

[0057] After successful authentication, the backend system 30 checks whether the joint identifier VK is stored for the terminal device 10 in the backend system 30 and whether the alliance account 54 is set up in the service platform 50, step 204.

[0058] If this is the case, the backend system 30 sends a request for a profile to the service platform 50, step 206. The profile request contains data that uniquely specifies the alliance account 54, the federation identifier VK or the user. In particular, the data can be the federation identifier VK itself. In a variant, an authorization token BT may 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 user's alliance account 54 and determines the authorization token BT stored therein and 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 agreed, the network operator 40 provides the user with a telecommunication profile TP, step 210; in addition, it calculates download information DI for the profile TP. The network operator 40 stores the determined telecommunication profile TP in the network operator's server 44, which transmits the download information DI to the service platform 50, step 212. If the terminal device 10 is configured according to the SGP.22 standard, the download information DI is usually an activation code according to the standard SGP.22.

[0061] After receiving the download information DI, the service platform 50 updates the alliance account 54 it manages, step 214. In addition, the service platform 50 determines the control data KD possibly stored in the alliance account 54, which is used to set the service configuration, i.e., to set customer-specific settings and services in the terminal device 10.

[0062] When 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, for example to enable the use of audio data or to carry out payment transactions. In other terminal devices 10, the control data KD can be used to set up, for example, a 5G router, a 5G modem of a laptop or a 5G modem in a mobile device. The configuration of the control data KD or the service is expediently defined by the user during regular operation of the terminal device 10 and transmitted from the terminal device 10 to the corresponding background system 30. The participating background system 30 further transmits the new or modified control data KD to the service platform 50 accordingly.

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

[0064] The backend system 30 updates the user account it manages, step 218. The backend system 30 further transmits the download information DI and the control data KD for setting the service configuration to the terminal device 10, step 220.

[0065] After receiving the download information DI, the terminal device 10 establishes a direct connection with the network operator 40 belonging to the download information DI via the data connection 22, and uses the download information DI to request the network operator 40 to transmit the telecommunication profile TP in step 222.

[0066] The network operator 40 checks the request and, if it agrees, sends a configuration file TP provided for this purpose to the terminal 10 via the data connection 22 , step 224 .

[0067] The terminal device 10 sets the telecommunication profile TP and activates the telecommunication profile TP, step 226. The request for the profile TP and the activation in the terminal device 10 are performed, for example, according to the GSMA standard, for example according to the GSMA standard SGP.22.

[0068] In addition to setting the telecommunication profile TP, the terminal device 10 also configures the services provided by the terminal device 10 based on the received control data KD. After activation and setting of the services are completed, the terminal device 10 sends a confirmation message to the background system 30, step 228.

[0069] Subsequently, the background system 30 updates the user account 32 , step 230 , and also sends the setting information to the service platform 50 , step 232 .

[0070] The service platform 50 then updates the alliance account 54 it manages, step 234 . Here, the service platform 50 stores the activation of the transmitted telecommunication profile TP as the new state of the terminal device 10 .

[0071] Furthermore, in a step 240 which is performed independently thereof, the network operator 40 updates the customer-specific data stored in the server 44 after the transmission of the telecommunication profile TP and also stores the activation of the transmitted telecommunication profile TP.

[0072] Figure 5 It shows the user-related settings made to the second terminal device 10 by the associated background system 30 when the joint identifier VK has not been stored for the user in the background system 30 , but the alliance account 54 has been set up for the user in the service platform 50 .

[0073] In a first step 300, the user first authenticates in the second terminal device 10. The authentication is preferably 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 also be fixedly connected to the terminal device, for example in the form of an input unit, a biometric sensor or a camera.

[0074] Then, the second terminal device 10 registers the user in the background system 30 associated with the second terminal device 10, step 302. During the registration process, the second terminal device 10 transmits its terminal device identifier EK to the background system 30. In addition, the terminal device 10 determines the user's joint identifier VK. This can be done by outputting a corresponding input prompt via the interface 14, or if the user uses an authentication device 60 in the form of an electronic key, an IC card or a mobile phone, this can be done automatically.

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

[0076] If this is not the case, as in Figure 5 As is based on the embodiment of , the background system 30 sends the joint identifier VK to the service platform 50. The background system 30 transmits the identifier EK of the terminal device 10 together with the joint identifier VK, step 306.

[0077] 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 is assumed in the present embodiment, the service platform 50 requires the user to authenticate.

[0078] Suitably, for this purpose, the service platform 50 sends a message to the second terminal device 10 via the background system 30, with which the user is asked to log in to the alliance account 54, step 310. If, as is assumed in the present example, a simple authentication is provided for the login, the user presents a secret for this purpose in order to authenticate with respect to the service platform 50. For example, the secret is a password or a PIN belonging to the alliance account 54. This is transmitted to the service platform 50 via the second terminal device 10 and the background system 30, step 312.

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

[0080] The service platform 50 checks the received login data. If the login data is correct, the service platform 50 determines the authorization token BT from the federation account 54 specified by the federation identifier VK and links it to the second terminal device 10, step 314. To this end, the service platform 50 links the federation account 54 and therefore the authorization token BT to the identifier EK of the second terminal device 10.

[0081] The service platform 50 then updates the alliance account 54, step 316, and adds the previously created link with the second terminal device 10. This can be done by storing the known terminal device identifier EK of the second terminal device 10 in the alliance account 54. Now, there is at least one link with the second terminal device 10 that performs the current settings and a link with the terminal device 10 that stored the link at an earlier point in time in the alliance account 54.

[0082] In the next step, the service platform 50 sends the authorization token BT to the determined network operator 40, step 318. In addition, the service platform 50 sends information about the updated joint identifier VK to the background system 30, step 320. After receiving it, the background system 30 updates the user account 32, step 322.

[0083] If the joint identifier VK has been stored for the user in the background system 30, the following steps correspond to Figure 4 The described steps are to perform user-related settings on the terminal device 10 through the associated background system 30.

[0084] The network operator 40 checks the received authorization token BT. If approved, the network operator 40 provides the user with a telecommunications profile TP, step 324; this profile TP is identical to the profile of the terminal device 10, for which a link has been stored in the alliance account 54 at an earlier point in time; these two profiles usually form the basis of the same customer contract.

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

[0086] After receiving the download information DI, the service platform 50 updates the alliance account 54 it manages, step 328. In addition, the service platform 50 determines the control data KD stored in the alliance account 54, the control data KD being used to set the service configuration on the terminal device 10.

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

[0088] The background system 30 updates the user account it manages, step 332. In addition, the background system 30 transmits the download information DI and the control data KD for setting the service configuration to the second terminal device 10, step 334.

[0089] After receiving the download information DI, the terminal device 10 establishes a direct connection with the network operator 40 belonging to the download information via the data connection 22 and uses the download information DI to request the network operator 40 to transmit the telecommunication profile TP in step 336 .

[0090] The network operator 40 examines the request, determines the profile TP provided for this purpose, and sends it to the second terminal device 10 via the data connection 22 , step 338 .

[0091] The second terminal device 10 sets the telecom profile TP and activates the telecom profile TP, step 342. The request for the telecom profile TP and the activation in the second terminal device 10 are performed, for example, according to the GSMA standard, for example according to the GSMA standard SGP.22.

[0092] In addition to setting the telecommunication profile TP, the second terminal device 10 also configures the service provided by the second terminal device 10 based on the received control data KD, step 344. After activation and setting of the service is completed, the second terminal device 10 sends a confirmation message to the background system 30, step 346.

[0093] Subsequently, the background system 30 updates the user account 32 , step 348 , and also sends the setting information to the service platform 50 , step 350 .

[0094] After receipt, the service platform 50 updates the alliance account 54 it manages, step 352. Here, the service platform 50 stores the activation of the transmitted telecommunication profile TP as the new state of the terminal device 10.

[0095] Furthermore, in a step 340 which is performed independently thereof, the network operator 40 updates the customer-specific profile data stored in the server 44 after the transmission of the telecommunication profile TP and also stores the activation of the transmitted telecommunication profile TP.

[0096] The second terminal device 10 is then set up to establish a connection to the data exchange network 46 specified by the telecommunication profile TP using the same telecommunication profile TP as was initially provided for the other terminal device 10. Furthermore, the services that the user had defined at an earlier point in time are configured on the terminal device 10. The user's joint identifier VK is also stored in the user account 32 belonging to the terminal device 10. Thus, the user can also subsequently quickly set up other terminal devices 10 associated with the same backend system 30.

[0097] While retaining the basic idea, the solution described above allows a large number of designs and variants that are not described separately. In particular, this also applies to the design and structure of the data processing components. In addition, the structures and elements of the embodiments described in the description based on the drawings should not be understood as correspondingly and ultimately forming the only possible implementation exactly according to the described arrangement. On the contrary, individual elements and processes can be combined and modified where reasonable and possible.

[0098] Reference numerals list

[0099] 10 User terminal equipment

[0100] 12 Interface

[0101] 14 User Interface

[0102] 16 Security Element

[0103] 18 Security Element

[0104] 20 Data Connection

[0105] 22 Data Connection

[0106] 24 Data Connections

[0107] 26 Data Connection

[0108] 30 Backend System

[0109] 32 user accounts

[0110] 40 Network Operators

[0111] 42 Configuration file data output unit

[0112] 44 Server

[0113] 46 Data Exchange Network

[0114] 50 Service Platform

[0115] 52 Storage Devices

[0116] 54 Affiliate Accounts

[0117] 60 Authentication equipment

[0118] VK Joint Identifier

[0119] EK Endpoint Device Identifier

[0120] BT Authorization Token

[0121] DI Download Information

[0122] TP Telecom Profile

[0123] KD Control data used to set service configuration

[0124] ZD Access Data

Claims

1. A method for performing user-related settings on a terminal device (10) connected to a background system (30), wherein: connecting the terminal device (10) to a data exchange network (46) by means of a telecommunication profile (TP) stored in a secure element (18), A service platform (50) is provided, the service platform is connected to the background system (30) and to at least one network operator (40), the network operator operates a data exchange network (46), Wherein, an authorization token (BT) is stored in the service platform (50), and the authorization token is used to provide a telecommunication profile (TP) belonging to the authorization token (BT). wherein the authorization token (BT) is linked to the joint identifier (VK), wherein the joint identifier (VK) or a configuration file request specifying the joint identifier (VK) is transmitted (206) from the backend system (30) to the service platform (50), wherein, upon receiving a federated identifier (VK) or a profile request specifying a federated identifier (VK), the service platform (50) determines (208) an authorization token (BT) linked to the federated identifier (VK), The service platform (50) uses the determined authorization token (BT) to load (224) a telecommunication profile (TP) belonging to the authorization token (BT) into a security element (18) contained in the terminal device (10) through a network operator (40), and then the terminal device (10) is set to connect to a data exchange network (46).

2. The method according to claim 1, characterized in that The service platform (50) is arranged to request a secret from a user after receiving a federated identifier (VK) or a profile request specifying a federated identifier (VK) in order to authenticate (310, 312) the user relative to the service platform (50).

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

4. The method according to any one of the preceding claims, characterized in that The service platform (50) is configured to establish a connection with a network operator (40) and prompt the network operator to generate a telecommunication configuration file (TP) and send back (210, 212, 318, 326) corresponding download information (DI).

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

6. The method according to any one of the preceding claims, characterized in that The service platform (50) generates access data (ZD) with respect to the joint identifier (VK), the access data being or containing a secret, and transmits (128) the access data (ZD) to the user.

7. The method according to any one of the preceding claims, characterized in that In the service platform (50), control data (KD) for setting service configuration is also stored in relation to the joint identifier (VK), the control data is transmitted (216) to the background system (30), and then the stored service is set (228) on the terminal device (10) with the aid of the control data (KD).

8. The method according to claim 7, characterized in that The service configuration is the setting of the infotainment system of the vehicle or the setting of customer-specific settings and services in a device equipped with a mobile radio unit, for example a computer or a 5G router.

9. The method according to any one of the preceding claims, characterized in that A user is authenticated (200, 300) with respect to a terminal device (10).

10. The method according to claim 9, characterized in that The authentication of the user to the terminal (10) is performed by means of an authentication device (60).

11. The method according to any one of the preceding claims, characterized in that The joint identifier (VK) is transmitted by means of the authentication device (60).

12. The method according to any one of the preceding claims, characterized in that The service platform (50) generates (124, 128) a federation identifier (VK) and a secret for authentication during a registration routine in which a user identifies a data exchange network (46) for which a telecommunication profile (TP) is to be provided (108).

13. The method according to any 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) determined by a user, and upon receipt, calculate (120) a joint identifier (VK) and link (122) the joint identifier with the authorization token (BT).

14. The method according to any one of the preceding claims, characterized in that The terminal (10) is a vehicle or a device having a mobile radio unit.

15. A service platform (50) for a management system, used for performing user-related settings on a terminal device (10), wherein: The service platform (50) is connected to at least one network operator (40) and to at least one backend system (30), wherein at least one backend system (30) is connected to the terminal device (10), and the terminal device (10) is connected to a data exchange network (46) by means of a telecommunication profile (TP) stored in a secure element (18), wherein the service platform (50) is configured to perform the following steps: receiving, processing and forwarding messages from 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), storing in said federation account (54) an authorization token (BT) for providing a telecommunication profile (TP), receiving a joint identifier (VK) and an end device identifier (EK) through a background system (30), checking whether a federation account (54) with a delegation token (BT) has already been created for the received federation identifier (VK), If a federation account has been created (54), a secret is requested from the user, Upon successful transfer of the secret, linking the end device identifier (EK) with the federation account (54), A telecommunication profile (TP) is provided by a network operator (40) with the aid of an authorization token (BT) stored in a federation account (54) for an end device (10) specified by an end device identifier (EK).

Images