Method for registering a user to a vehicle, computer-readable medium, system, and vehicle

Abstract

The invention relates to a method for registering a user to a vehicle. Said method comprises the following steps: detecting a mobile terminal of the user, wherein the mobile terminal of the user is identified using a first wireless communication protocol; determining a seating location of the user in the vehicle, wherein the seating location of the user in the vehicle is determined using a second wireless communication protocol; and registering the user to the determined seating location of the vehicle by the vehicle.

Description

[0001] Method for logging a user onto a vehicle, computer-readable medium, system, and vehicle

[0002] The invention relates to a method for registering a user to a vehicle. The method further relates to a computer-readable medium for registering a user to a vehicle, a system for registering a user to a vehicle, and a vehicle comprising the system for registering a user to the vehicle.

[0003] In current vehicles, a vehicle user can enter their login credentials via the vehicle's display to log in. It is also known to enable a user to log in to a vehicle by scanning a QR code displayed on the vehicle's display with a mobile device's camera. In the current state of the art, user interaction with the vehicle's display is always necessary for the user to log in to the vehicle.

[0004] It is therefore an object of the invention to efficiently simplify the registration of a user in a vehicle. In particular, an object of the invention is to enable simpler and more precise registration for all users, especially all occupants, of a vehicle. In particular, a further object of the invention is to efficiently automate the registration of a user in a vehicle.

[0005] This object is achieved by the features of the independent claims. Advantageous embodiments and further developments of the invention emerge from the dependent claims.

[0006] According to a first aspect, the invention is characterized by a method for logging in a user to a vehicle. The method can be a computer-implemented method and / or a control unit-implemented method. The user can be an occupant, a driver, a front passenger, and / or a rear passenger of the vehicle. The method can execute the user login without the user interacting with a display of the vehicle. In other words, the method for logging in the user to the vehicle can be executed independently of the user interacting with a display of the vehicle. The user can execute the login in the vehicle using a mobile device brought into the vehicle by the user. The mobile device can be a smartphone, a smartwatch, smart glasses, a tablet, and / or another mobile device of the user. The vehicle can be a motor vehicle.

[0007] The method detects a user's mobile device, wherein the user's mobile device is detected using a first wireless communication protocol. The method further determines a seat location of the user in the vehicle, wherein the user's seat location in the vehicle is determined using a second wireless communication protocol. The first wireless communication protocol and the second wireless communication protocol are preferably different wireless communication protocols. Finally, the method can have the vehicle register the user at the determined seat location in the vehicle.

[0008] Advantageously, a user can log in to the vehicle, and in particular to a specific seat of the vehicle, without interacting with a display device of the vehicle, in particular with a display control device of the vehicle. The mobile device and the seat of the vehicle where the mobile device and the user are located can be determined automatically using two wireless communication protocols. Thus, the method can efficiently simplify the login of a user in the vehicle. A user can efficiently log in to a seat of the vehicle using the mobile device, even if this seat does not have a display device or a display control device.

[0009] According to an advantageous embodiment, the registration of the user at the determined seat of the vehicle by the vehicle can comprise providing a message for registration of the user at the determined seat of the vehicle from the vehicle to the user's mobile device, receiving a confirmation message for registration of the user at the determined seat from the user by the mobile device, transmitting the received confirmation message from the mobile device to the vehicle, and registration of the user at the determined seat of the vehicle by the vehicle after receiving the confirmation message. This can increase the security when the user registers at a seat of the vehicle. The user is only registered at the vehicle seat if the user initiates registration at the vehicle with the confirmation message.

[0010] According to an advantageous embodiment of the invention, the message for logging the user into the identified seat can comprise a single button on a graphical interface of the mobile device, with which the user can log into the identified seat of the vehicle. This can efficiently simplify the user login process.

[0011] According to a further advantageous embodiment of the invention, the confirmation message can include a single user interaction with the single button on the graphical interface of the mobile device. This can efficiently simplify the user's login.

[0012] According to a further advantageous embodiment of the invention, the method may further comprise configuring the determined vehicle seat after the user has logged in to the determined seat based on a user-specific profile. This allows the user to flexibly specify the seat at which they wish to log in.

[0013] According to a further advantageous embodiment of the invention, the first wireless communication protocol can be Bluetooth Low Energy, and / or the second wireless communication protocol can be Ultra Wide Band. This allows the mobile device to be efficiently detected and located.

[0014] According to a further advantageous embodiment of the invention, the user can log in to the determined seat in the vehicle, authenticate, and authorize the user using a standardized authentication and / or authorization protocol, and / or the user can be authenticated and / or authorized based on an oauth 2.0 protocol, and / or a user code and / or a verification URI of the oauth 2.0 protocol can be transmitted from the vehicle to the user's mobile device using the Bluetooth Low Energy protocol. User authentication can be performed, for example, using OpenID Connect. OpenID Connect can verify the user's identity based on the oauth 2.0 protocol and thus authenticate the user. User authorization can be performed using oauth 2.0. This allows the vehicle user to be automatically authenticated and / or authorized.The security of the user login can thus be efficiently increased.

[0015] According to a further aspect, the invention is characterized by a computer-readable medium for registering a user with a vehicle, wherein the computer-readable medium comprises instructions which, when executed on a computer and / or a control unit, carry out the method described above.

[0016] According to a further aspect, the invention is characterized by a system for registering a user to a vehicle, wherein the system is designed to carry out the method described above.

[0017] According to a further aspect, the invention is characterized by a vehicle comprising the above-described system for registering a user to a vehicle.

[0018] Further features of the invention emerge from the claims, the figures, and the description of the figures. All features and combinations of features mentioned above in the description, as well as the features and combinations of features mentioned below in the description of the figures and / or shown alone in the figures, can be used not only in the respective specified combination, but also in other combinations or even on their own.

[0019] A preferred embodiment of the invention is described below with reference to the accompanying drawings. Further details, preferred embodiments, and developments of the invention will emerge from these. In detail, schematically

[0020] Fig. 1 shows an exemplary method for registering a user to a vehicle,

[0021] Fig. 2 shows an exemplary method for detecting a user’s mobile device,

[0022] Fig. 3 shows an exemplary method for determining a seat location of the user in the vehicle, and

[0023] Fig. 4 shows an exemplary method for logging the user into the determined seat of the vehicle.

[0024] In detail, Fig. 1 shows an exemplary method 100 for logging a user into a vehicle. A user can get into a vehicle using a mobile device and take a seat inside the vehicle. At the seat, the user can log in using the mobile device and thus use and / or control one or more functions of the vehicle seat and / or one or more functions of the vehicle. For example, using and / or controlling a function can include automated personalization of the function to user-specific requirements. Functions of the vehicle can be, for example, a seat position, an air conditioning function, a light color, a configuration of a digital media service of the vehicle, and / or a navigation function. The user can log in to the seat with a single user input.For example, the operating input can be a gesture, a touch input, and / or an input via a mechanical control element of the mobile device.

[0025] The method 100 can detect 102 a mobile device of the user. An exemplary method for detecting 102 a mobile device of the user is shown in Fig. 2. Furthermore, the method 100 can determine 104 a seat of the user in the vehicle. An exemplary method for determining 104 a seat of the user in the vehicle is shown in Fig. 3. The detection 102 of the user's mobile device and the determination 104 of the user's seat can be carried out sequentially or in parallel. Preferably, the detection 102 of the mobile device is carried out in parallel with the determination 104 of the seat. Alternatively, the mobile device can already be detected outside the vehicle. Further alternatively, the mobile device is only detected when the user occupies a seat in the vehicle.

[0026] The method 100 may provide a message for logging the user into the identified vehicle seat from the vehicle to the user's mobile device. For example, the message for logging the user into the vehicle seat may be provided in an app or widget on the mobile device. The message may include a button or other interface for logging the user into the vehicle seat. A confirmation message for logging the user into the identified seat may be received from the user by the mobile device. For example, the confirmation message may include pressing the button or other interaction with another interface displayed to the user on the mobile device. The received confirmation message may be transmitted from the mobile device to the vehicle. The method 100 may have the vehicle logging the user into the identified vehicle seat 106.An exemplary method for logging the user into the identified seat is shown in Fig. 4. For example, after receiving the confirmation message, the user can be logged into the identified seat of the vehicle by the vehicle. After logging in 106 the user, the vehicle can provide personalized functions and / or services to the logged-in user, particularly at the user's seat in the vehicle.

[0027] The method 100 can store the logged-in user on the vehicle. If the mobile device of the stored user is recognized by the vehicle, the user can be automatically logged in to the seat without the user interacting with the mobile device. Alternatively, the method 100 can automatically log the user out when the user leaves the vehicle seat and exits the vehicle.

[0028] In detail, Fig. 2 shows an exemplary method 200 for recognizing 102 a user's mobile device 202. The mobile device 202 can execute a mobile application, also referred to as an app below, which carries out the recognition of the mobile device in communication with a vehicle 204 and / or a backend server 206. The mobile application can be executed in the background on the mobile device. Preferably, the mobile application is an application of the vehicle manufacturer that enables the use and / or control of vehicle functions and vehicle-specific backend functions. The communication between the mobile device 202 and the vehicle 204 can take place via a first wireless communication interface, preferably Bluetooth and / or Bluetooth Low Energy.The communication between the mobile terminal 202 and the backend server 206, as well as between the vehicle 204 and the backend server 206, can take place, for example, via a mobile radio communication interface.

[0029] The mobile terminal 202 can scan 208 for a predefined registration service. The scanning 208 can be performed continuously by the mobile terminal 202. The vehicle 204 can offer the predefined registration service 210. The mobile terminal 202 can recognize the offered registration service 212 and connect to the vehicle 214. The vehicle can offer parameters to the mobile terminal 216. The mobile terminal can use the offered parameters to request data from the vehicle and to transmit data from the mobile terminal to the vehicle.

[0030] For example, the vehicle can offer the following parameters to the mobile device:

[0031] Table 1 : exemplary parameters offered by the vehicle to the mobile device in order to transmit data from the mobile device to the vehicle from the vehicle to the mobile device.

[0032] Steps 218 to 220 can optionally be performed to increase the security during recognition 102 of the mobile terminal. In step 218, the vehicle 204 can generate a public vehicle identifier and transmit it to the backend server 206. The public vehicle identifier can be generated by the vehicle if the vehicle offers the login service to a mobile terminal. Furthermore, the vehicle can regenerate the public vehicle identifier if the login service is offered to a mobile terminal again. This can prevent tracking of offered login services and improve the privacy of the method 200. In addition, the mobile terminal can be prevented from communicating with unknown devices, for example unknown vehicles, that offer a login service that does not correspond to the login service of the vehicle in which the user is seated.

[0033] In step 220, the mobile device 202 can request the public vehicle identifier from the vehicle. The mobile device can then have the public vehicle identifier verified 222 by the backend server 206. The backend server 206 can transmit the verification result to the mobile device. If the verification result is that the public vehicle identifier is valid, the mobile device can establish a preferably secure connection to the vehicle, and in particular to the vehicle's registration service. If the verification result is that the public vehicle identifier is invalid, the mobile device can abort the process with the registration service and scan for another registration service.

[0034] Furthermore, steps 218 to 220 can be used to query vehicle-specific information as additional login information. For example, a vehicle type, a number of seats, a vehicle color, a vehicle seat color, and / or other vehicle interior-specific details can be queried. Steps 224 and 226 are optional and represent a first possibility for establishing a secure communication connection between the mobile device and the vehicle. Using steps 224 and 226, a secure indirect communication connection between the mobile device and the vehicle can be established. For this purpose, a secure communication connection between the mobile device 202 and the backend server 206 can be established 224, and a secure communication connection between the backend server and the vehicle can be expanded 226.Communication between the mobile device and the vehicle can only occur indirectly via the backend server. For example, an existing secure communication connection between an app on the mobile device and the backend server can be used for this purpose. The secure indirect communication connection has the advantage of preventing attacks on the wireless interface between the mobile device and the vehicle. For example, local BLE attacks can be prevented by the secure indirect communication connection.

[0035] Steps 228 and 230 are optional and provide a second way to establish a secure connection between the mobile device and the vehicle. Steps 228 and 230 enable a secure direct communication connection between the mobile device and the vehicle. In step 228, the vehicle exchanges security data, such as cryptographic keys and / or security certificates, with the mobile device via the backend server in order to establish a secure direct communication channel. In step 230, the mobile device exchanges security data, such as cryptographic keys and / or security certificates, with the vehicle via the backend server in order to establish a secure direct communication channel. For example, the security data exchanged via the backend server can be used to establish a secure BLE communication channel between the mobile device and the vehicle.

[0036] In detail, Fig. 3 shows an exemplary method 300 for determining 104 a user's seat location in the vehicle. The exemplary method 300 shown in Fig. 3 can determine a user's seat location using ultra-wideband (UWB)-based mobile device detection. The mobile terminal 202 can request 302 a UWB token from the backend server 206. The backend server 206 can generate 304 the UWB token and transmit it 306 to the mobile terminal 202. Furthermore, the backend server 206 can transmit 308 the generated UWB token to the vehicle 204. For example, the backend server can transmit 308 the UWB token to the vehicle 204 via a push message. The vehicle 204 can determine 310 a position of the mobile terminal using UWB. For example, the vehicle can continuously determine the position of the mobile terminal using UWB in order to be able to detect a change in the position of the mobile terminal.Furthermore, the vehicle 204 can generate 312 a suggested seating position based on the position of the mobile device. The generated suggested seating position can be transmitted 314 from the vehicle to the mobile device. For example, the generated suggested seating position of the user can be transmitted 314 from the vehicle to the mobile device using the "Suggested seating position" parameter. The mobile device 202 can provide 316 the suggested seating position to a user 315. For example, the suggested seating position can be displayed to the user in an app on the mobile device. Optionally, the user can manually change the suggested seating position 318. The changed seating position can be transmitted 320 from the mobile device 202 to the vehicle. For example, the changed seating position can be transmitted 320 from the mobile device to the vehicle using the "Selected seating position" parameter.

[0037] To generate a seating position suggestion using the UWB protocol, various input parameters can be used:

[0038] UWB device localization

[0039] Seat occupancy, door opening status, belt status and / or camera-based person detection in the vehicle interior

[0040] In addition to the suggested seat position, the vehicle can also provide the accuracy of the estimated suggestion as an output parameter. Statistical state estimation algorithms can be used as the algorithm for determining the seat position. For example, an extended Kalman filter can be used, in which a separate state estimator is used for each seat in the vehicle, and the state estimator of a seat with the highest accuracy is suggested as the user's seat position. Alternatively, a particle filter can be used, which creates seat clusters for each seat in the vehicle. The seat cluster containing the most mobile device positions is suggested as the user's seat position.Alternatively, a predefined machine learning method can be used to generate the seating position suggestion, which adapts itself to a vehicle and its seating.

[0041] In detail, Fig. 4 shows an exemplary method 400 for logging 106 the user into the determined seat of the vehicle. The method 400 can log the user into the vehicle after determining the user's seating position. To log the user into the vehicle, the mobile device can provide the user with a notification message 402 for logging the user into the determined seat of the vehicle. The notification message can include a login suggestion and / or a suggested seat of the vehicle. The user can confirm 404 the notification message for logging the user into the determined seat of the vehicle. Steps 402 and 404 are optional and can increase the security of the method 400 by requiring the user to confirm the login process. Alternatively, the user can log in to the determined seat automatically without confirmation from the user.If the user logs in automatically, steps 402 and 404 are not executed. The vehicle can log the user in using a standardized authentication and authorization process. For example, the vehicle can log the user in using the oAuth 2.0 Device Authorization Grant Standard.

[0042] In step 406, the mobile device 202 can transmit 406 a message to the vehicle for registering the user code and / or URI parameters. By registering the user code and / or URI parameters by the mobile device, the mobile device can automatically receive the user code and / or URI from the vehicle. In step 408, the vehicle 204 can transmit a client identifier of the vehicle to the backend server 206. By transmitting the client identifier from the vehicle 204 to the backend server 206, the vehicle 204 can request access from the backend server. In response to transmitting 408 the client identifier, the backend server 206 may transmit 410 a device code, the user code, and the URI, in particular a URI for verification by the user, to the vehicle. Steps 408 and 410 may be performed analogously to steps (A) and (B) of the oauth 2.0 Device Authorization Grant standard.The oauth 2.0 Device Authorization Grant Standard is published as RFC 8628. The process flow of the oauth 2.0 Device Authorization Grant Standard is shown in Figure 1 of RFC 8628. Additionally, the message may include the confirmation login request parameter, which triggers the user login process at the vehicle. In step 412, the user code and the URI may be transmitted from the vehicle 204 to the mobile device 202. Step 412 may be performed analogously to step (C) of the oauth 2.0 Device Authorization Grant Standard. In contrast to step (D) of the oauth 2.0 Device Authorization Grant Standard, in step 412, the user code and the URI may be transmitted automatically from the vehicle 204 to the mobile device 202 using the user code and URI parameters. Preferably, the parameters are transmitted from the vehicle 204 to the mobile device 202 using the first wireless communication protocol.For example, the first wireless communication protocol is Bluetooth Low Energy. Alternatively, only the user code can be transmitted from the vehicle 204 to the mobile device 202 in step 412, and the URI can be transmitted from the backend server 206 to the mobile device. For example, the URI can be transmitted from the backend server to the mobile device via a cellular communication protocol. This can increase the security of the transmission of the user code and the URI.

[0043] Furthermore, in contrast to step (D) of the oauth 2.0 Device Authorization Grant Standard, in step 412, a user with a web browser can be omitted. An app can be run on the mobile device that automates the user with a web browser. Likewise, a QR code scan for transmitting the user code and URI can be omitted. This data can be transmitted automatically, as described above, from the vehicle to the mobile device, and in particular to the mobile device's app, via the first wireless communication protocol and by registering the user code and URI parameters of the login service.

[0044] In step 414, the vehicle 204 can transmit the device code and the client identifier from the backend server 206 to the backend server at cyclic intervals to query whether the user has confirmed logging in to the vehicle. Step 414 can be performed analogously to step (E) of the oauth 2.0 Device Authorization Grant Standard.

[0045] Additionally, the mobile device may provide a confirmation message to the mobile device user 416 to confirm the registration request and receive a response message to the confirmation message from the mobile device user 417. As described above, the confirmation message may include the user's seat location determined in step 104. With the response to the confirmation request, the user may confirm the user's registration and the user's seat location in the vehicle.

[0046] The mobile device can automatically respond 418 to the login request received in step 412. Step 418 can be performed analogously to step (D) of the oauth 2.0 Device Authorization Grant standard. Unlike step (D) of the oauth 2.0 Device Authorization Grant standard, user confirmation is optional. The mobile device can automatically authorize the login request. Furthermore, the mobile device can automatically confirm the seat location. Thus, the user can be logged into the vehicle seat completely automatically.

[0047] In step 420, the backend server 206 can validate the vehicle's device code and transmit it 420 with an access token to the vehicle if the mobile device or the user of the mobile device has confirmed access. If the mobile device or the user of the mobile device has not confirmed access, the backend server can transmit an error message to the vehicle and / or a message to the vehicle to continue the cyclic query 414. Step 420 can be performed analogously to step (F) of the oauth 2.0 Device Authorization Grant standard.

[0048] Advantageously, the method 100 can perform automatic registration in a vehicle. Furthermore, the method 100 can provide an automatic registration suggestion for a vehicle seat on a mobile device without requiring manual initiation of the registration process. The vehicle user can be automatically registered in the vehicle or only needs to perform a single user interaction to register in a vehicle seat. The user's registration information does not need to be stored on the vehicle. Scanning a QR code is also no longer necessary to register the user in the vehicle. The user can also efficiently register in vehicle seats that do not have a display. Furthermore, the method allows multiple vehicle users to register in parallel at their respective seats without requiring a display at each seat.

[0049] 100 procedures

[0050] 102 Detecting a mobile device

[0051] 104 Finding a seat

[0052] 106 Registering a user

[0053] 200 procedures

[0054] 202 mobile devices

[0055] 204 vehicles

[0056] 206 backend servers

[0057] 208 Scanning a login service

[0058] 210 Offer registration service

[0059] 212 Detect Login Service

[0060] 214 Connect to vehicle

[0061] 216 Offer Parameters

[0062] 218 Generation and transmission of public vehicle identifiers

[0063] 220 queries of the public vehicle identifier

[0064] 222 Checking the public vehicle identifier

[0065] 224 Establishing a secure communication connection

[0066] 226 Expanding a secure communication connection

[0067] 228 Exchange of security data

[0068] 230 Exchange of security data

[0069] 232 Establishing a secure communication connection

[0070] 300 procedures

[0071] 302 UWB token requests

[0072] 304 Generate UWB token

[0073] 306 Transmit UWB token

[0074] 308 Transmit UWB token

[0075] 310 Determining the position of the mobile device

[0076] 312 Generating a suggested seating position

[0077] 314 Sending the proposal to the mobile device

[0078] 315 users

[0079] 316 Providing the suggested seating position

[0080] 318 Manually changing the seat position Transmitting the changed seat position

[0081] Proceedings

[0082] Providing a registration suggestion

[0083] Confirm the registration suggestion

[0084] Registering parameters

[0085] Transmit client identifier

[0086] Transmit device code, user code, and URI

[0087] Transfer user code and URI

[0088] Transmit device code and client identifier

[0089] Provide confirmation message

[0090] Receive reply message

[0091] Answer registration request

[0092] Submitting an access token

Claims

Patent claims 1. Procedure for registering a user with a vehicle, the procedure comprising: Detecting a user's mobile device, where the mobile device of the User is recognized using an initial wireless communication protocol; Determining the user's seat location in the vehicle, wherein the user's seat location in the vehicle is determined using a second wireless communication protocol; and The vehicle logs the user into the determined seat of the vehicle.

2. Method according to claim 1, wherein the vehicle comprises registering the user at the determined seat of the vehicle: Providing a message to log the user into the identified seat of the vehicle from the vehicle to the user's mobile device; Receiving a confirmation message from the user via the mobile device to log in to the determined seat; Transmitting the received confirmation message from the mobile device to the vehicle; and The vehicle logs the user into the identified seat after receiving the confirmation message.

3. Method according to one of the preceding claims, wherein the message for registering the user at the identified seat comprises a single button of a graphical interface of the mobile device with which the user can register at the identified seat of the vehicle.

4. Method according to one of the preceding claims, wherein the confirmation message comprises a single interaction of the user with the single button of the graphical interface of the mobile device.

5. A method according to any of the preceding claims, further comprising: Configuring the detected seat in the vehicle after the user logs in to the detected seat, depending on a user-specific profile.

6. A method according to any of the preceding claims, wherein the first wireless communication protocol is Bluetooth Low Energy; and / or wherein the second wireless communication protocol is Ultra Wide Band.

7. A method according to any of the preceding claims, wherein the user's login to the identified seat in the vehicle is accompanied by authentication and authorization of the user using a standardized authentication and / or authorization protocol; and / or wherein the user is authenticated on the basis of OpenID Connect and / or authorized using an OAuth 2.0 protocol; and / or wherein a user code and / or a verification URI of the OAuth 2.0 protocol is transmitted from the vehicle to the user's mobile device using the Bluetooth Low Energy protocol.

8. Computer-readable medium for registering a user to a vehicle, wherein the computer-readable medium comprises instructions which, when executed on a computer and / or a control unit, execute the method according to any one of claims 1 to 7.

9. System for registering a user to a vehicle, wherein the system is configured to perform the method according to any one of claims 1 to 7.

10. Vehicle comprising the system for registering a user to a vehicle according to claim 9.

Images