Authorization procedure and authorization system for operating a vehicle

Abstract

Authorisation procedure for operating a vehicle (V1) using a mobile device (M) and a backend (B), in which (a) Access data (10), comprising an access element through which backend (B) is generated, (b) the access data (10) is provided to the vehicle (V1) by the backend (B), (c) the access data (10) is provided to the mobile device (M) by the backend (B) after successful authentication of a user, wherein the authentication of the user in step (c) includes validation of the user's name and password and / or biometric data, (d) the vehicle (V1) is sent an operating request (20) by the mobile device (M) comprising the access data (10) received from the backend (B), (e) depending on the operating request (20), an authorization request (30) of the vehicle (V1) is transmitted to the backend (B) by the vehicle (V1), wherein the authorization request in step (e) is transmitted with the access element received by the backend (B) after successful validation of the access element received by the mobile device (M), (f) depending on the authorization request (30), an authorization response (40) is transmitted to the vehicle (V1) by the backend (B), (g) depending on the authorization response (40) an interaction of the user of the mobile device (M) with the vehicle (V1) is authorized by the backend (B).

Description

[0001] The invention relates to an authorization method and system for operating a vehicle.

[0002] Traditionally, every car has a physical car key to lock and unlock the doors and trunk. The same key is usually used to start the engine and thus operate the car. To improve convenience and user-friendliness, today's car keys are composed of two modules, including both a physical key and a wireless key radio module. With the wireless key, it is possible to remotely unlock the car within a certain distance of the car. Furthermore, it is no longer necessary to insert a physical key into a vehicle keyhole to start the engine. Instead, the vehicle key only needs to be recognized as being inside the car.

[0003] Since these systems still require the car owner or anyone wanting to access the car to be in possession of the vehicle key, automakers have begun creating apps installed on a smartphone that allow the car to be locked and unlocked from close proximity.

[0004] Currently, a pre-set device is required in the immediate vicinity of the vehicle to enable unlocking, locking, and starting the engine. The vehicle user requires either a vehicle key or a smartphone with pre-installed software that is pre-authorized for access to the vehicle. Without these devices, authorization is not possible. This represents a major inconvenience for the vehicle user in a variety of situations. For example, if the vehicle user has lost the vehicle key and does not have the corresponding app installed on their smartphone, which was previously paired with the vehicle, there is no easy way to lock or unlock the car and start the engine.

[0005] DE 10 2016 218 071 A1 discloses an authentication system for a motor vehicle. The authentication system comprises an access module that can receive and verify access authorization data from an external device. The access module can control a door lock for the motor vehicle. Furthermore, the authentication system comprises a drive authorization module that can receive and verify drive authorization data from the external device. The drive authorization module can control a drive authorization for the motor vehicle.

[0006] DE 10 2016 116 042 A1 discloses a method and system for opening and / or using at least one vehicle.

[0007] US 2016 / 0 368 456 A1 discloses a system and a method for wireless duty scheduling of a motor vehicle.

[0008] DE 10 2016 222 100 A1 discloses a method and a system for proving the owner of a vehicle.

[0009] US 2017 / 0 267 214 A1 discloses a motor vehicle and cloud system for temporarily assigning e-keys to control the use of a vehicle.

[0010] The object underlying the invention is to create a secure method and corresponding system for operating a vehicle, which makes it possible to reliably authorize or refuse authorization of control functions of the vehicle such as locking, unlocking or engine start, even without an authorization device pre-coupled to the vehicle.

[0011] The problem is solved by the independent patent claims. Advantageous embodiments are characterized in the subclaims.

[0012] According to a first aspect, the invention relates to an authorization method for operating a vehicle using a mobile radio device and a backend. In the method, (a) access data generated by the backend, (b) the access data is provided to the vehicle via the backend, (c) the access data is provided to the mobile device by the backend after successful authentication of a user, (d) the mobile device transmits an operating request to the vehicle comprising the access data received from the backend, (e) the vehicle transmits an authorization request from the vehicle to the backend depending on the operation request, (f) the backend sends an authorization response to the vehicle depending on the authorization request, and (g) depending on the authorization response, an interaction of the user of the mobile device with the vehicle is authorized by the backend.

[0013] The authorization method according to the invention advantageously enables access to the vehicle even if the vehicle owner neither has the physical or wireless key of the vehicle nor his or her own mobile device. In particular, the method thus contributes to enabling access to the vehicle via any smart device, preferably via any internet-enabled device, including third-party devices. The method can also advantageously be used to implement novel use cases with high security aspects, such as remote access to a vehicle for temporary use, in particular trunk delivery or car sharing.

[0014] In comparison to previous approaches, the authorization method according to the invention does not require a pre-installed app or the user to manually link the vehicle with the app; rather, a user account linked to the vehicle is sufficient.

[0015] The mobile radio device is in particular a so-called “smart device”, i.e. a portable electronic device which is equipped with one or more communication interfaces to other devices such as a Bluetooth, near field communication (NFC), Wi-Fi or mobile radio interface according to 3GPP such as GSM, UMTS or LTE.

[0016] For example, the mobile device can be a “smartphone,” “phablet,” “tablet,” a “smartwatch,” a “smart band,” or a “smart key chain.”

[0017] The access data includes an access element, which can also be referred to as an "access token" or "trusted element." The access element can be, for example, a JSON Web Token (JWT), or another generic identifier such as a hash, ID, or token.

[0018] The access data or the access element can be regenerated periodically. After a predetermined period of time has elapsed, the newly generated access element is then provided to the vehicle and / or the mobile device. The predetermined period of time after which the access element is regenerated is, for example, between 1 second and 60 minutes, in particular between 10 seconds and 5 minutes, preferably 60 seconds. The length of time for which a respective access element is valid can depend in particular on the associated security certificate architecture. In other embodiments, certificates or access elements can also be valid for one day, so that costs associated with the process can be kept low.

[0019] The operation request in step (d) is particularly representative of stimulating the vehicle to transmit its identifier to the backend.

[0020] The authorization request in step (e) is particularly representative of informing the backend about the mobile device located nearby.

[0021] The authorization response in step (f) is particularly representative of informing the vehicle about the mobile device located nearby, in particular its identifier and the access authorization of the corresponding user with regard to the vehicle.

[0022] According to the first aspect, the authentication of the user in step (c) comprises a validation of the user's name and password and / or biometric data. In particular, the authentication in step (c) - an optional authentication request is sent to the mobile device via the backend, - depending on the authentication request, an authentication response from the user of the mobile device is transmitted to the backend by the mobile device, and - the user's authentication response is validated by the backend.

[0023] If the backend validates the user's authentication response, the access data is provided to the mobile device via the backend. Validation of the user's authentication response includes, for example, comparing the authentication response with the user's user account.

[0024] Communication between the mobile device and the backend can, for example, take place via a website or an app. The mobile device does not have to be already paired with the vehicle, for example by linking a device-specific identification number of the mobile device and a device-specific identification number of the vehicle. Rather, the aforementioned app or website can be downloaded or opened spontaneously. The only prerequisite for this is that the user of the mobile device is assigned a user account to which access authorizations for one or more vehicles are assigned. For example, the user account of a vehicle owner includes full access authorization for their vehicle. The user account of a parcel delivery person, for example, is assigned temporary access authorizations from one or more vehicle owners for the one-time locking and unlocking of the trunk.

[0025] According to the first aspect, the authorization request is transmitted in step (e) after successful validation of the access element received from the mobile device with the access element received from the backend.

[0026] The vehicle's authorization request transmitted to the backend is particularly representative of the fact that the mobile device is in the vicinity of the vehicle.

[0027] The authorization request includes, in particular, an identifier for the vehicle. This identifier is, for example, a media access control (MAC) address of the vehicle. Alternatively or additionally, the authorization request includes, for example, an identifier for the mobile device, thus facilitating the assignment of the operating request.

[0028] In an advantageous embodiment according to the first aspect, the authorization response in step (f) includes an identifier of the mobile device. The identifier is, for example, a media access control address of the mobile device. In particular, the authorization response in step (f) can include a so-called "unique identifier" (UID) of a communication interface of the mobile device.

[0029] In an advantageous embodiment according to the first aspect, the vehicle is assigned to a predefined vehicle fleet. Furthermore, in step (b), the backend provides the access data to all vehicles in the vehicle fleet.

[0030] In an advantageous embodiment according to the first aspect, in step (d) an operating request is transmitted by the mobile device to all vehicles of the vehicle fleet within a predetermined distance from the mobile device.

[0031] The specified distance to the mobile device can be limited, for example, by the mobile device's transmission power. For example, communication between the mobile device and the vehicles in the fleet takes place via Bluetooth, Bluetooth Low Energy (BLE), ultra-wideband (UWB) technology, or a wireless local area network (WLAN).

[0032] In an advantageous embodiment according to the first aspect, in step (e) an identifier is transmitted to the backend (B) by all vehicles of the vehicle fleet within the specified distance from the mobile device.

[0033] In an advantageous embodiment according to the first aspect, in step (e) - the backend sends a list of all vehicles in the fleet within the specified distance to the mobile device, - a vehicle selection is transmitted to the backend by the mobile device, which is representative of a vehicle selected by the user of the mobile device from the list and intended for interaction. Furthermore, in step (f) - Depending on the vehicle selection, the authorization response is sent to the selected vehicle from the vehicle fleet via the backend.

[0034] In an advantageous embodiment according to the first aspect, in step (g) - the vehicle checks whether the mobile device is within a specified maximum distance from the vehicle and / or whether a specified interaction between the user of the mobile device and the vehicle has been recorded.

[0035] In case the mobile device is within the specified maximum distance to the vehicle and / or the specified interaction of the user of the mobile device with the vehicle has been recorded, - the vehicle sends a security request to the backend, and - Depending on the security request and after successful secondary authentication of the mobile device user, an authorization message is provided to the vehicle via the backend, which represents the authorization of an interaction with the vehicle by the mobile device user. The authorization message can, for example, be a cryptographic key that authorizes access to the vehicle.

[0036] The specified maximum distance of the mobile device to an outer wall of the vehicle is, for example, between 1 cm and 100 m, in particular between 50 cm and 50 m, preferably between 1 m and 10 m.

[0037] In an advantageous embodiment according to the first aspect, in step (g) the second authentication is carried out depending on the security request, wherein in the second authentication - an authentication request is sent to the mobile device by the backend, - depending on the authentication request, an authentication response from the user of the mobile device is transmitted to the backend by the mobile device, and - the user's authentication response is validated by the backend.

[0038] If the backend validates the user's authentication response, the backend provides the vehicle with the authorization response. Validating the user's authentication response includes, for example, comparing the authentication response with a predefined sequence of numbers.

[0039] In an advantageous embodiment according to the first aspect, in a step (h) following step (g), the vehicle checks whether the mobile device is within a predetermined maximum distance from the vehicle. Furthermore, the vehicle provides the backend with a status message based on the check result.

[0040] The check to determine whether the mobile device is within a specified maximum distance from the vehicle can, in particular, be carried out periodically. After a specified time interval has elapsed, a newly determined status message can then be provided to the backend. The status message can, in particular, also be periodically re-determined and provided to the backend by the vehicle. The specified time interval after which the check is carried out again is, for example, between 1 second and 60 minutes, in particular between 10 seconds and 5 minutes, preferably 60 seconds. A time interval for determining and providing the status message is, for example, the same as the specified time interval of the check, but can also differ from it.

[0041] To authorize the vehicle's engine operation, in particular the engine start, the specified maximum distance of the mobile device from the vehicle is selected, for example, such that the mobile device is located entirely within the driver's cab. In this case, the specified maximum distance of the mobile device from the center of the vehicle's driver's cab is, for example, between 1 cm and 10 m, in particular between 50 cm and 5 m, preferably between 1 m and 2 m.

[0042] In an advantageous embodiment according to the first aspect, depending on the status message, the backend extends or revokes the authorization for the user of the mobile device to interact with the vehicle. For example, if the mobile device is outside the specified maximum distance from the vehicle, the backend revokes the authorization for the user of the mobile device to interact with the vehicle. The authorization for the interaction with the vehicle is revoked, for example, by the backend sending a message to the vehicle that the mobile device is no longer authorized. In an advantageous embodiment according to the first aspect, the authorization response in step (f) comprises an identifier of the mobile device and an access authorization of the associated user with respect to the vehicle.

[0043] For example, access authorization could be authorization to operate the vehicle, i.e., opening / closing all access openings of the vehicle, including starting / stopping the engine. Alternatively, access authorization could only include opening / closing the trunk, for example, to enable innovative services such as parcel delivery in private vehicles.

[0044] According to a second aspect, the invention relates to an authorization system for operating a vehicle. The authorization system comprises a mobile radio device and a backend. The vehicle, the mobile radio device, and the backend are each signal-coupled to one another and configured to carry out a method according to the first aspect.

[0045] According to a third aspect, the invention relates to a computer program for operating a vehicle, wherein the computer program is designed to carry out a method according to the first aspect when executed on a data processing device.

[0046] According to a fourth aspect, the invention relates to a computer program product comprising executable program code, wherein the program code, when executed by a data processing device, carries out the method according to the first aspect.

[0047] Embodiments of the invention are explained in more detail below with reference to the schematic drawings.

[0048] They show: Fig. 1 is a schematic representation of an exemplary authorization system for operating a vehicle; and Fig. 2 a flowchart of an exemplary authorization procedure for operating the vehicle according to Fig. 1.

[0049] Elements of the same construction or function are provided with the same reference symbols throughout the figures.

[0050] Fig. 1 shows an authorization system S with a vehicle fleet V comprising vehicles V1, V2, V3, e.g., vehicles belonging to different vehicle owners. The vehicles V1...V3 of the vehicle fleet V are assigned to a backend B of the authorization system S and are signal-linked to it, e.g., via the Internet. A user of a mobile device M of the authorization system S, e.g., a smartphone, is within radio range of the vehicles V1 and V2. The mobile device M is also signal-linked to the backend B, e.g., via the Internet. The signal-linking of the mobile device M and the vehicles V1, V2 takes place, e.g., via BLE, UWB, or WIFI.

[0051] The mobile device M is, for example, any internet-enabled device on which, in particular, neither a cryptographic access key to one of the vehicles V1, V2 needs to be stored, nor a coupling with one of the vehicles V1, V2 needs to exist.

[0052] The user of the mobile device M only needs a user account, which is assigned to the user in backend B and to which access authorizations for one or more vehicles V1...V3 are assigned. In particular, attributes related to a role / rights model are assigned to the user account. For example, the "Owner" role has all rights, while the "Parcel Carrier" role only has the rights to open / close the trunk once, but no rights to start the engine.

[0053] The mobile device M, the backend B and the vehicles V1, V2 each comprise a data processing device with a data and program memory in which a program is stored, which is described below using the flow chart of the Fig. 2. The program implements an authorization procedure intended to authorize interaction between the user of the mobile device M and the vehicle V1. In particular, this allows the user to lock or unlock the vehicle V1 and start its engine.

[0054] In step a, backend B first generates access data 10 with a limited time validity. This is, for example, a JSON Web Token. Step a is executed periodically and / or event-based.

[0055] Each time new access data 10 is generated, it is distributed to all vehicles V1, V2, V3 of the vehicle fleet V in a subsequent step b. If an authorized user of the vehicle V1 does not have a key for the vehicle V1 at hand or only has a mobile device M without a special pre-installed application, they can send a request 11 to an app store B' or a website in a step b' and download a special application 12 that facilitates communication between the mobile device M and the backend B. Alternatively, the communication between the mobile device M and the backend B can also take place via a website that is linked to the backend B.

[0056] In a subsequent step c', the user of the mobile device M is authenticated. For example, the user's biometric data is captured by a sensor. Alternatively, the user's name and password are requested, for example. An authentication response 13, which is representative of the captured or queried data, is transmitted to the backend B and validated by the backend B in a step c''. For example, the data is compared with the user's user account. If validation is successful, the access data 10 is also transmitted to the mobile device M in a subsequent step c. Authentication can take place both via the app and via the accessed website. The access data 10 is then shared with the mobile device M via the app or website.

[0057] In a subsequent step d, the access data 10 contained in an operation request 20 received by the mobile device M is used to "ping" all vehicles V1, V2 of the vehicle fleet V in the vicinity, for example, within radio range. In other words, in step d, the operation request 20 is sent to the vehicles V1, V2 to trigger them to contact the backend B.

[0058] In a subsequent step e, the vehicles V1, V2 each evaluate the operation request 20. In this context, the vehicles V1, V2 each validate, in particular, the access data 10 received from the backend B and the access data 10 contained in the operation request 20. If the validation is successful, the vehicles V1, V2 each inform the backend B with an authorization request 30 that the mobile device M wishes to communicate with them, i.e., that the mobile device M is nearby. The authorization request 30 includes, in particular, an identifier such as a MAC address of the respective vehicle V1, V2.

[0059] In the event that multiple vehicles V1, V2 are located near the mobile device M and / or the user of the mobile device M is assigned access authorizations for multiple vehicles V1...V3, the backend B determines, in a step e', a list 31 of all these vehicles V1...V3 or the intersection of the vehicles V1, V2 based on the authorization request 30 of the vehicles V1, V2 and the role / rights model. The list 31 is then transmitted to the mobile device M. In this case, the user can select which vehicle V1, V2 they wish to access. In a step e'', the user's vehicle selection 32 is determined and transmitted to the backend B.

[0060] In a subsequent step f, an authorization response 40 is sent by the backend B to the selected vehicle V1. The authorization response 40 can include, in particular, the MAC address of the mobile device M and / or the UID of the wireless communication interface of the mobile device M, as well as the access authorizations stored in the backend B and, if applicable, further details of the corresponding user.

[0061] In a subsequent step g, a check is made to determine whether a predefined event has occurred that indicates user access to vehicle V1. For example, in this context, a check is made to determine whether the mobile device M has fallen below a predefined maximum distance from vehicle V1 or whether the door handle has been operated a predefined number of times within a defined period of time. As soon as the check reveals that the user wishes to access or interact with vehicle V1, for example, open vehicle V1 or start the engine, vehicle V1 sends a security request 50. The security request is particularly representative of a desired two-factor authentication that is to be initialized by backend B.

[0062] In a subsequent step g', a second authentication of the user of the mobile device M takes place. For example, in this context, the backend B first sends an authentication request 51 to the mobile device M, in which the user is requested to confirm access to the vehicle V1, for example by entering a predefined sequence of numbers. An authentication response 52, which is representative of the user's confirmation, is transmitted to the backend B in a step g'' and validated by the backend B in a step g'''. If validation is successful, an authorization message 60 is finally transmitted to the mobile device M, which is representative of an authorization of the interaction of the user of the mobile device M with the vehicle V1. In particular, the vehicle V1 thus enables access or the engine start and reports the corresponding status to the backend B if necessary.

[0063] Optionally, in a subsequent step h, the vehicle V1 periodically checks whether the mobile device M is within a specified maximum distance from the vehicle V1. For this purpose, the vehicle V1 sends, for example, a status query 70 to the mobile device M and waits for its response 71. Depending on the test result, a status message 72 is then periodically sent to the backend B in a step h'.

[0064] In use cases where temporary usage rights are (or must be) granted to third parties, it is conceivable to use the authorization system or procedure to inform an authorized party, such as a vehicle owner, that a third party wishes to access the vehicle. The access authorization can be granted at least temporarily and stored in backend B, so that the third party can gain access to vehicle V1 using the authorization system or procedure. List of reference symbols: M mobile device V Vehicle fleet V1...V3 vehicle B Backend 10 Access data 20 Operational inquiry 30 Authorization request 40 Authorization response 50 Security request ah program steps

Claims

[1] Authorization method for operating a vehicle (V1) by means of a mobile radio device (M) and a backend (B), in which (a) access data (10), comprising an access element, are generated by the backend (B), (b) the access data (10) are provided to the vehicle (V1) by the backend (B), (c) the access data (10) are provided to the mobile device (M) by the backend (B) after successful authentication of a user, wherein the authentication of the user in step (c) comprises a validation of the name and password and / or biometric data of the user, (d) an operating request (20) comprising the access data (10) received from the backend (B) is transmitted to the vehicle (V1) by the mobile device (M), (e) an authorization request (30) of the vehicle (V1) is transmitted to the backend (B) by the vehicle (V1) depending on the operating request (20), wherein the authorization request is transmitted in step (e) after successful validation of the access element received from the mobile device (M) with the access element received from the backend (B), (f) an authorization response (40) is transmitted to the vehicle (V1) by the backend (B) depending on the authorization request (30), (g) depending on the authorization response (40), an interaction of the user of the mobile device (M) with the vehicle (V1) is authorized by the backend (B). [2] Authorization method according to claim 1, wherein the vehicle (V1) is assigned to a predetermined vehicle fleet (V), and in step (b) - all vehicles (V1, V2, V3) of the vehicle fleet (V) are provided with the access data (10) by the backend (B). [3] Authorization method according to claim 2, wherein in step (d) - an operating request (20) is transmitted by the mobile radio device (M) to all vehicles (V1, V2) of the vehicle fleet (V) within a predetermined distance from the mobile radio device (M). [4] Authorization method according to claim 3, wherein in step (e) - an authorization request (30) is transmitted to the backend (B) by all vehicles (V1, V2) of the vehicle fleet (V) within the specified distance from the mobile device (M). [5] Authorization method according to claim 4, wherein in step (e) - a list of all vehicles (V1, V2) of the vehicle fleet (V) within the specified distance from the mobile device (M) is transmitted to the mobile device (M) by the backend (B), - a vehicle selection is transmitted to the backend (B) by the mobile device (M), which is representative of a vehicle (V1) selected by the user of the mobile device (M) from the list and intended for interaction, and in step (f) - depending on the vehicle selection, the authorization response (40) is transmitted to the selected vehicle (V1) from the vehicle fleet (V) by the backend (B). [6] Authorization method according to one of the preceding claims, in which in step (g) - the vehicle (V1) checks whether the mobile device (M) is within a predetermined maximum distance from the vehicle (V1) and / or a predetermined interaction of the user of the mobile device (M) with the vehicle (V1) has been detected, and in the event that the mobile device (M) is within a predetermined maximum distance from the vehicle (V1) and / or a predetermined interaction of the user of the mobile device (M) with the vehicle (V1) has been detected - a security request (50) is transmitted to the backend (B) by the vehicle (V1), - depending on the security request (50) and after successful secondary authentication of the user of the mobile device (M), an authorization message (60) is provided to the vehicle (V1) by the backend (B), which is representative of an authorization of an interaction of the user of the mobile device (M) with the vehicle (V1). [7] Authorization method according to one of the preceding claims, in which in a step following step (g) (h) the vehicle (V1) checks whether the mobile device (M) is within a predetermined maximum distance from the vehicle (V1), and the backend (B) is provided with a status message by the vehicle (V1) depending on the check result. [8] Authorization method according to one of the preceding claims, wherein the authorization response (40) in step (f) comprises an identifier of the mobile radio device (M) and / or an access authorization of the associated user with respect to the vehicle (V1). [9] Authorization system (S) for operating a vehicle (V1), comprising a mobile radio device (M) and a backend (B), wherein the vehicle (V1), the mobile radio device (M) and the backend (B) are each coupled to one another by signal technology and are configured to carry out a method according to one of the preceding claims 1 to 8. [10] Computer program for operating a vehicle (V1), wherein the computer program is designed to carry out a method according to one of claims 1 to 8 when executed on a data processing device. [11] A computer program product comprising executable program code, wherein the program code, when executed by a data processing device, carries out the method according to any one of claims 1 to 8.

Images