DE102018202173A1 - Method and device for authenticating a user of a vehicle - Google Patents

Abstract

A user token (T1) detecting the user's digital identity is issued by an identity provider (IDP) (S1). A user registration for use of the vehicle with a backend device (BE) is carried out by means of the user token (T1) and authorization of the user for use of the vehicle is given by the backend device (2). The user token (T1) issued by the identity provider is stored on the mobile device (M). A token containing data about the user's digital identity (N), which may be the user token (T1) or an access token (T2) retrieved using the user token (T1), is used by wirelessly sent to the mobile device and received by the mobile device (5). The received token is then checked (6) as to whether it identifies a user who is authorized to use the vehicle. In the case of a determined authorization of the user, (7) a release of the use of the vehicle takes place.

Description

The present invention relates to a method for authenticating a user of a vehicle. The present invention further relates to a corresponding apparatus and a vehicle having such apparatus or is adapted to carry out such a method.

Mechanical car keys that are inserted into a lock to close or open a vehicle, as an ignition key to start the engine and for other functions such as the release of a steering wheel lock in order to open this by turning are increasingly supplemented or replaced by remote key, with which the doors can be locked and unlocked by remote control. Furthermore, so-called keyless locking systems allow a vehicle to be unlocked without actively using a car key when the key of the vehicle is detected in the immediate vicinity of the vehicle and to start by merely pressing a start button when the key is in the vehicle. For this purpose, the key has a chip which, for example, with RFID or UWB technology receives a signal from the vehicle and then in turn sends back a signal to the vehicle. If the correct signal is detected in the vehicle, an authentication takes place and the vehicle can be opened and, if necessary, started.

Furthermore, there are first attempts to use mobile phones, so-called smartphones, as a digital car key. These are based on the operation of classic vehicle radio controls, i. the smartphone appropriately retains its knowledge of a vehicle-specific secret (e.g., part of the immobilizer secret), whereupon the vehicle releases the access or grants the driving authorization.

However, solutions based on proof of vehicle secrecy have a number of disadvantages. So they are unattractive for manufacturers of smartphones, because they have to create a way or offer to be able to transfer such vehicle secrets for a variety of vehicle manufacturers on the smartphone. This is technically complex and error-prone, difficult to hedge against attacks and can cause high operating costs. Therefore, such solutions are currently only supported by a few smartphone manufacturers.

Furthermore, secured storage space on the smartphone is limited to the vehicle secrets, so that thereby the number of digital car keys per smartphone is limited. Since the digital vehicle keys are vehicle-specific, thus the number of vehicles is limited. This becomes even more problematic when concepts based on such digital keys are also to be used for other things of daily life, such as opening and closing office doors, front doors, locker lockers, lockers at a bench, wheel locks, etc.

Finally, another problem can occur when the user uses multiple mobile devices, such as a combination of one or more smartphones, smartwatches, and tablets. Since the digital keys are stored device-bound, the user initially only has them available on one of the mobile devices and has to set them up on other devices, for example when purchasing a new device, before use. Furthermore, care must be taken to remove the digital key from a mobile device when it is no longer used by the user and disposed of or sold.

Furthermore, keyless access control and start systems are known which use biometric data for authentication in the vehicle. So revealed the DE 10 2016 104 629 A1 a centralized control platform that manages information about user rights and biometric target data of a user for a vehicle and transmits it to an access control unit in the vehicle. With a mobile communication device, such as a smartphone biometric actual data of the user are detected and also transmitted to the access control unit. The actual biometric data is compared with the target biometric data and granted access to the vehicle based on the result of the comparison.

The GB 2516377 A describes a method for identifying the user of a vehicle, in which a code that includes identification data of the vehicle, such. As a bar code or a QR code is displayed on the display of the vehicle. This code can be scanned and decoded with a mobile terminal to determine the identification data and forward it to a server for identifying the user. User-specific data is then assigned to the user by the server and forwarded to the vehicle to automatically operate or adjust a component of the vehicle based thereon.

Finally, the reveals DE 10 2014 001 038 A1 a method of transmitting data to a vehicle that requires electronic identity matching for successful transmission. As electronic identity, a code is chosen that is generated using a vehicle identification number of the respective vehicle and an identity of the respective user and thereby vehicle and user is assigned. In this case, the transmission can first take place on a mobile telephone of the user, and from there onto the vehicle. The transmitted data is then usable only using the vehicle identification number of the respective vehicle in the respective vehicle.

It is an object of the invention to provide an improved method for authenticating a user of a vehicle, a corresponding device and a corresponding vehicle.

This object is achieved by a method having the features of claim 1, a device according to claim 13 and by a vehicle according to claim 14. Preferred embodiments of the invention are the subject of the dependent claims.

• - ein Token empfangen wird, der Daten über die digitale Identität eines Nutzers enthält und von einem mobilen Gerät des Nutzers an das Fahrzeug gesendet worden ist;
• - der empfangene Token daraufhin überprüft wird, ob dieser einen Nutzer ausweist, der zur Nutzung des Fahrzeugs berechtigt ist; und
• - bei einer ermittelten Berechtigung des Nutzers eine Freigabe der Nutzung des Fahrzeugs erfolgt.

In the inventive method for authenticating a user of a vehicle, wherein

• - Receiving a token containing data about a user's digital identity and sent to the vehicle by a user's mobile device;
• - the received token is checked to see if it identifies a user who is authorized to use the vehicle; and
• - When a determined authorization of the user, a release of the use of the vehicle takes place.

• - ein die digitale Identität des Nutzers nachweisender Nutzer-Token von einem Identitätsprovider ausgestellt;
• - eine Anmeldung des Nutzers für eine Nutzung des Fahrzeugs bei einer Backendeinrichtung mittels des Nutzer-Tokens durchgeführt und eine Berechtigung des Nutzers für eine Nutzung des Fahrzeugs durch die Backendeinrichtung erteilt; und
• - der von dem Identitätsprovider ausgestellte Nutzer-Token auf dem mobilen Gerät gespeichert.

Preferably, this is

• - a user token proving the user's digital identity issued by an identity provider;
• - An application of the user for a use of the vehicle at a backend device carried out by means of the user token and granted authorization of the user for use of the vehicle by the backend device; and
• the user token issued by the identity provider is stored on the mobile device.

• - eine Information über die digitale Identität des Nutzers von der Backendeinrichtung an das Fahrzeug gesendet und im Fahrzeug gespeichert;
• - vor einer Nutzung des Fahrzeugs für eine Überprüfung der Berechtigung des Nutzers der auf dem mobilen Gerät gespeicherte Nutzer-Token an das Fahrzeug gesendet; wobei
• - das Fahrzeug den gesendeten Nutzer-Token empfängt und überprüft, ob der empfangene Nutzer-Token einen Nutzer ausweist, der eine Berechtigung zur Nutzung des Fahrzeugs hat.

According to one embodiment of the invention

• - Information about the digital identity of the user sent from the backend device to the vehicle and stored in the vehicle;
• - sent to the vehicle before using the vehicle for checking the authorization of the user of the user token stored on the mobile device; in which
• - The vehicle receives the sent user token and checks whether the received user token identifies a user who has authorization to use the vehicle.

Advantageously, in this case, a public key of the identity provider is sent from the backend device to the vehicle and stored in the vehicle and used to check the validity of the transferred from the mobile device to the vehicle user token.

• - ist ein Authorisierungs-Server vorgesehen, dem für eine Autorisierung eines Nutzers zur Fahrzeugnutzung die zulässigen Fahrzeugnutzungen für die bei der Backendeinrichtung angemeldeten Nutzer bekannt sind und der aus einem Nutzer-Token ein Zugriffs-Token für eine Fahrzeugnutzung erstellen kann;
• - wird dem mobilen Gerät vom Fahrzeug mitgeteilt, von welchem Authorisierungs-Server es einen Zugriffs-Token akzeptiert;
• - ruft das mobile Gerät mittels des Nutzer-Tokens am angegebenen Authorisierungs-Server einen Zugriffs-Token ab;
• - sendet das mobile Gerät den abgerufenen Zugriffs-Token an das Fahrzeug; und
• - empfängt das Fahrzeug den abgerufenen Zugriffs-Token und überprüft, ob der empfangene Zugriffs-Token einen Nutzer ausweist, der eine Berechtigung zur Nutzung des Fahrzeugs hat.

In a further embodiment of the invention

• an authorization server is provided for which the authorized vehicle usages for the users registered with the backend device are known for authorization of a user for vehicle usage and which can create a vehicle usage access token from a user token;
• the mobile device informs the vehicle from which authorization server it accepts an access token;
• the mobile device uses the user token to retrieve an access token at the specified authorization server;
• the mobile device sends the retrieved access token to the vehicle; and
• the vehicle receives the retrieved access token and checks whether the received access token identifies a user who has authorization to use the vehicle.

In this case, a public key of the authorization server can be stored in the vehicle and used to check the validity of the access token transmitted from the mobile device to the vehicle.

Likewise, an address information of the authorization server can be stored in the vehicle and transmitted to the mobile device.

Furthermore, information about which user data is required in the access token for the desired use of the vehicle can be transmitted to the mobile device.

In addition, the vehicle can then check the retrieved access token whether it is still valid or has already expired, with the use of the vehicle only being released if the access token is still valid.

Furthermore, the mobile device may automatically be prompted for authentication upon detection of imminent vehicle usage.

Also, online functions can be activated with the received token for the user in the vehicle and / or online services can be registered.

Finally, with a confirmed digital identity of the user, an individualized configuration of the vehicle can be made for this user and / or an individualized user greeting of the user can take place.

Accordingly, a device according to the invention for authenticating a user of a vehicle comprises a communication unit for receiving a token which contains data about the digital identity of a user and has been sent to the vehicle by a mobile device of the user and a control unit which then checks the received token whether it identifies a user who is authorized to use the vehicle and, in the case of a determined authorization, releases the use of the vehicle by the user.

The invention also relates to a vehicle in which the method according to the invention or the device according to the invention is used.

• 1 zeigt ein Ablaufdiagramm eines erfindungsgemäßen Verfahrens zur Authentifizierung eines Nutzers eines Fahrzeugs, das mittels eines mobilen Geräts des Nutzers durchgeführt wird;
• 2 zeigt schematisch eine Übersicht für ein Ausführungsbeispiel ohne Internetverbindung des mobilen Geräts und/oder Fahrzeugs zum Zeitpunkt der Authentifizierung;
• 3 zeigt für das Ausführungsbeispiel aus 2 den restlichen Verfahrensablauf nach Detektion einer bevorstehenden Fahrzeugnutzung;
• 4 zeigt schematisch eine Übersicht für ein Ausführungsbeispiel ohne Internetverbindung des mobilen Geräts und/oder Fahrzeugs zum Zeitpunkt der Authentifizierung; und
• 5 zeigt für das Ausführungsbeispiel aus 4 den restlichen Verfahrensablauf nach Detektion einer bevorstehenden Fahrzeugnutzung.

Further features of the present invention will become apparent from the following description and claims taken in conjunction with the figures.

• 1 shows a flowchart of a method according to the invention for authenticating a user of a vehicle, which is performed by means of a mobile device of the user;
• 2 schematically shows an overview for an embodiment without Internet connection of the mobile device and / or vehicle at the time of authentication;
• 3 shows for the embodiment 2 the rest of the procedure after detection of imminent vehicle use;
• 4 schematically shows an overview for an embodiment without Internet connection of the mobile device and / or vehicle at the time of authentication; and
• 5 shows for the embodiment 4 the rest of the procedure after detection of imminent vehicle use.

For a better understanding of the principles of the present invention, embodiments of the invention will be explained in more detail below with reference to the figures. It should be understood that the invention is not limited to these embodiments, and that the features described may also be combined or modified without departing from the scope of the invention as defined in the claims.

1 shows a flowchart of a method according to the invention for authenticating a user of a vehicle.

In a first process step S1 the user registers for himself a digital identity with an identity provider, ie a provider who operates an identity confirmation service and performs an authentication of a user, which can also be used for other service providers. The basis for this is that both the user and the other service providers can accept the digital identity of the user made available by the identity provider or trust in the authentication by the identity provider.

A digital identity can be, for example, a unique name, a unique number or other suitable for a unique identification data with which a user can be identified by a computer system. In addition, the digital identity may also have other features, such as the first and last name, academic degree or gender, an e-mail address or telephone number of the user. Here, a user, unlike in the real world, also have multiple digital identities.

In a second process step S2 The user logs on by means of the digital identity when using electronic services of a vehicle supplier / operator. There, he carries out an action by means of which he obtains authorizations to use a vehicle, for example by ordering or renting a vehicle online, proving possession of a vehicle by suitable means or by authorizing the owner of a vehicle to use it.

In a third process step S3 the vehicle operator / operator ensures that the information required to authenticate a user is known to the vehicle. This is done, depending on which of the following described embodiments, in different ways and is therefore in connection with the descriptions of 2 or. 4 explained in more detail.

In a fourth process step S4 the user now uses the same digital identity on a mobile device, such as a smartphone, for logging on to the operating system of the mobile device or an application program installed on it, a so-called app. Upon successful user login, the identity provider then issues a signed user token ("User Token"). The user token has here in addition to the payload ("payload" or "claims"), which contain at least one unique digital identity at the identity provider and beyond further information, such as may contain expiration dates, also a signature that the validity of the token and generated using the private key of the identity provider. The user token including its signature is then received and stored by the mobile device.

In a fifth process step S5 is wirelessly sent to the vehicle by the user token mobile device or an access token retrieved using the user token. Again, a more detailed explanation in connection with the descriptions of the various embodiments in the following figures. Preferably, this process can be triggered automatically as soon as it is detected that vehicle use is imminent. This can be done, for example, in which the vehicle detects a touch of the door handles, and then requests mobile devices in the area via a wireless channel to identify themselves using one of the identities that have authorization to use this vehicle.

Likewise, however, the authentication sequence can also be initiated in other ways, for example by detecting a vehicle approach of a user by means of suitable sensors such as cameras or IR sensors, or by detecting an RFID transponder near the vehicle.

In a sixth process step S6 the vehicle now checks whether the received token belongs to a user who has authorizations to use the vehicle by comparing the contained user identity with those from his list of authorized users. In addition, it checks whether the signature of the token is valid and, if necessary, further contents of the token, for example, whether the token has not yet expired.

If this test is successful, the vehicle gives in a seventh process step S7 the use of the degree free, as it is permitted for this user.

Finally, optional In an eighth step S8 the vehicle use the token to register the user for the on-line services of the vehicle provider / operator and to provide user satisfaction by, for example, information available through the token or retrievable by means of the token.

The method according to the invention has a number of advantages for the user, the vehicle provider / operator, as well as the manufacturers of mobile devices such as smartphones. Thus, the user does not have to carry out manual key management for his devices, as all locking permissions on the respective device are immediately available through a single login and all devices with the same login, if desired, have the same locking permissions. Also, the user does not have to register with vendor-specific portals for proof of identity, but can have his identity confirmed by any vendors trusted by the vehicle manufacturer, especially those in which he already has a login. For the vehicle provider / operator in turn, for example, has the advantage that it does not have to operate its own identity provider and no distribution infrastructure for digital keys on the smartphones needed and the person identity can also be used for personal functions / services. Among other things, it is advantageous for the manufacturers of smartphones that only a single "key" is required for opening and closing any number of locks of vehicles and other everyday items, so that already limited storage space is sufficient for this and simple implementation low operating costs is possible.

With reference to the 2 and 3 an embodiment of the inventive method is described that an authentication of the user allows without an Internet connection of the mobile device and / or vehicle must be present at the time of authentication.

The user N has a digital identity with an identity provider IDP registered, for example, to various web and mobile applications on his mobile device M safe to use without having to log in each with username and password. This can be done, for example, when you log in to popular electronic services or even with neutral or independent certification authorities and is initially independent of the use of the mobile device in connection with the use of a vehicle by the user.

For example, users can use special protocols such as OAuth (Open Authorization) to allow an application to access its data, which is provided by another service without disclosing any secret details about its access authorization. The identity provider IDP can sign user tokens for this T1 Issue the signature using the private key IDPK2 of the identity provider IDP via the payload of the user token. To further increase security additional cryptographic measures can be taken in this case, such as the use of a so-called "salt", in which a randomly selected string is appended to the user data before the calculation of the signature.

As already mentioned above 1 described the user logs N for the use of a vehicle by means of the digital identity at a backend device BE of the vehicle operator / operator and thus obtains the authorizations to use the vehicle FZ ,

The vehicle provider / operator then sends from the backend device BE information about the digital identity of the user from the signed part of the user token and the public key IDPK1 of the identity provider IDP via a secure channel to the vehicle in which this information is stored. In addition to the information about the digital identity of the user, this may also provide further information such as the user's entitlement to use the vehicle, eg the authorization to open and close and / or drive the vehicle, or the benefit of the digital installed in the vehicle's infotainment system Services are transmitted and stored.

After a login of the user N on the mobile device M gets this from the identity provider IDP a user token T1 , stores this including its signature. The subsequent steps in an intended use of the vehicle are in 3 clarified.

First, in step S51 the intention to use recognized, for example by the touch of a door handle of the vehicle FZ by the user N is recognized. The vehicle then straightens FZ in step S52 an authentication request to the mobile device M the user to obtain information about the identity of the user. The mobile device then transmits, if any, in step S53 that of the identity provider IDP issued user tokens T1 back to the vehicle, preferably via a wireless communication channel such as via Bluetooth, NFC, RFID or WLAN. In the vehicle is then using the obtained user token T1 and the public key IDPK1 of the issuing identity provider IDP in the context of the step S6 the authenticity of the user token is checked whether it comes from an accepted identity provider, whether it is valid or has expired and whether the user is authorized to use the vehicle. If this is the case, in step S7 the user N access to the vehicle or use of the vehicle.

In the 4 and 5 A further exemplary embodiment of the method according to the invention is shown, in which an internet connection of the mobile device must exist for an authentication of the user at the time of the authentication. This results in deviations of the method compared to the first embodiment, which are described below.

The vehicle provider / operator operates in this case in addition to the backend unit BE an authorization server AS which is aware of the permitted vehicle uses of all users registered for vehicle use and the authorized vehicle usage of it from the user token T1 corresponding signed access tokens T2 can create for these vehicle usages. An address information of the authorization server, such as its URL, and the public key of the authorization server ASK1 are known to the vehicle connected to the system and stored in a memory.

Intended now the user N a vehicle FZ to use, so will step in S52 the mobile device M informed by the user of the vehicle from which authorization server AS It's an access token T2 accepted and what claim, ie what must be included in the user data of the access token, so the access token T2 can be used for the desired use of the vehicle. For this example, the vehicle identification number (VIN) of the vehicle can be used or other information about the intended actions on the vehicle ("trunk open", "driving" ...). Unless the smartphone already has a valid such access token T2 is present, it asks in step S54 using the user token on the specified authorization server AS for the required claim such a. The required access token T2 will then step in S55 from the authorization server AS to the mobile device M returned. It can also be provided that only at the first query on the authorization server AS the user token must be used and for later queries old access tokens or dedicated server AS issued update tokens ("refresh tokens").

The smartphone then sends this access token in step S53 back to the vehicle, this checks again in step S6 whether the claim in the access token authorizes the use of the vehicle and, by means of the public key of the authorization server known to it ASK1 whether the signature of the access token is valid, and if so, whether the token is still valid or has expired. If the result of the test is positive then in step S7 the vehicle is released for use to the extent permitted by claim.

Each of the two previously described embodiments has advantages over the other embodiments. So comes the embodiment according to the 2 and 3 without active internet connection of the mobile device, as there is no need to communicate with an authorizing server of the vehicle operator / operator. There is also no danger that a user token sent to the authorization server can be tapped.

On the other hand, the active internet connection embodiment according to FIGS 4 and 5 no potentially vulnerable transmission of information about the authorized users and their authorizations to the vehicle. Furthermore, this method is very flexible, since the permissions of users for vehicles can be easily and quickly adjusted by appropriate configuration of the authorization server. Furthermore, the examination of the access token and issuing authorization server is completely in the hands of the vehicle operator / operator.

Other variants are conceivable in which by means of a user token transmitted to the vehicle, the vehicle itself collects access tokens on the authorization server.

The invention is not limited to the authentication of a user of a vehicle, but can also be used in other areas in which a proof of a user authorization by means of a mobile device, in particular a smartphone, can take place.

LIST OF REFERENCE NUMBERS

S1

first process step

S2

second process step

S3

third process step

S4

fourth process step

S5

fifth process step

S6

sixth process step

S7

seventh process step

S8

eighth process step

S51

Detecting touch door handle

S52

authentication request

S53

Send tokens

S54

Request Token to Authorization Server

S55

Receive tokens from authorization server

N

user

M

mobile device

IDP

identity provider

AS

Remote File Server

BE

Back terminal

FZ

vehicle

IDPK1

public key of the identity provider

IDPK2

private key of the identity provider

ASK1

public key of the authorization server

ASK2

private key of the authorization server

T1

User Token

T2

Access token

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited patent literature

• DE 102016104629 A1 [0007]
• GB 2516377 A [0008]
• DE 102014001038 A1 [0009]

Claims (14)

Method for authenticating a user of a vehicle, in which - receive (5) a token containing data about the digital identity of a user (N) and sent to the vehicle from a mobile device (M) of the user; - the received token is then checked (6) whether it identifies a user who is authorized to use the vehicle (FZ); and - If the user has a determined authorization, a release of the use of the vehicle takes place (7). Method according to Claim 1 in which - a user token (T1) detecting the user's digital identity is issued by an identity provider (IDP); - An application of the user for a use of the vehicle at a backend device (BE) carried out by means of the user token (T1) and granted a permission of the user for use of the vehicle by the backend device (2); and - the user token (T1) issued by the identity provider is stored on the mobile device (M). Method according to Claim 1 or 2 in which - information about the digital identity of the user (N) is sent from the backend device (BE) to the vehicle (FZ) and stored in the vehicle; - before use of the vehicle for a review of the authorization of the user of the stored on the mobile device user token (T1) is sent to the vehicle (SA53); and - the vehicle receives and checks (S6) the transmitted user token (T1) whether the received user token (T1) identifies a user who has authorization to use the vehicle. Method according to Claim 3 in that a public key (IDPK1) of the identity provider (IDP) is sent from the backend device (BE) to the vehicle (FZ) and stored in the vehicle and for checking the validity of the user token transmitted from the mobile device (M) to the vehicle (T1) is used. Method according to Claim 1 or 2 in which - an authorization server (AS) is provided, for which the authorized vehicle uses for the users registered with the back-end device (BE) are known for an authorization of a user (N) for vehicle use and which consists of a user token (T1) can create an access token (T2) for vehicle use; the mobile device (M) is informed by the vehicle (FZ) from which authorization server (AS) it accepts an access token (T2); - The mobile device (M) using the user token (T1) on the specified authorization server (AS) retrieves an access token (T2) (S54, S55); - the mobile device sends the retrieved access token (T2) to the vehicle (S53); and - the vehicle receives the retrieved access token (T2) and checks (S6) whether the received access token (T2) has authorization to use the vehicle. Method according to Claim 5 in which a public key (ASK1) of the authorization server (AS) is stored in the vehicle (FZ) and used to check the validity of the access token (T2) transmitted by the mobile device (M) to the vehicle. Method according to Claim 5 or 6 , wherein an address information of the authorization server (AS) in the vehicle (FZ) is stored and transmitted to the mobile device (M). Method according to Claim 5 . 6 or 7 in which information about which user data is required in the access token for the desired use of the vehicle (FZ) is transmitted to the mobile device (M). Method according to one of Claims 5 to 8th in which the vehicle (FZ) checks the retrieved access token (T2) for whether it is still valid or has already expired and only if the access token (T2) is still valid, a release of the use of the vehicle takes place (7). Method according to one of the preceding claims, wherein the mobile device (M) automatically requested for authentication (S52) upon detection (S51) of imminent vehicle use. Method according to one of the preceding claims, wherein with the received token for the user (N) in the vehicle (FZ) enabled online functions and / or online services registered. Method according to one of the preceding claims, wherein in the case of a confirmed digital identity of the user (N) an individualized configuration of the vehicle (FZ) is undertaken for this user and / or an individualized user greeting of the user takes place. A device for authenticating a user of a vehicle, comprising - a communication unit for receiving a token containing data about the digital identity of a vehicle User (N) and has been sent from a mobile device (M) of the user to the vehicle; and - control unit, which checks the received token to determine whether it identifies a user who is authorized to use the vehicle (FZ) and, in the case of a determined authorization, releases the use of the vehicle by the user. Vehicle that is set up, a method according to one of Claims 1 to 12 to execute or a device according to Claim 13 having.

Images