Method and control unit for enabling a remote control service for a vehicle

The method and control unit system facilitate secure remote control of vehicle functions by allowing a service provider to authorize and execute remote control services beyond the digital key device's proximity, addressing the limitations of existing systems by using cryptographic authentication and context-based authorization for enhanced vehicle functionality.

WO2024235572A1PCT designated stage expired Publication Date: 2024-11-21BAYERISCHE MOTOREN WERKE AG
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2024/060877
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-15
Filing Date
2024-04-22
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Existing vehicle remote control systems require the digital key device to be in close proximity to the vehicle, limiting the ability of a service provider to remotely control vehicle functions, such as automated parking, without the user's device being present.

Method used

A method and control unit system allowing remote control of vehicle functions via a long-distance communication connection, where a user's digital key device can hand over authorization to a remote control service, specifying context information for spatial and temporal boundaries, and using cryptographic session signatures for secure authentication and key data generation to enable remote control services without the key device's local presence.

Benefits of technology

Enables secure and efficient remote control of vehicle functions by a service provider, including the release of the immobilizer, without the need for the digital key device to be near the vehicle, enhancing the capability for driverless operations like automated valet parking.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024060877_21112024_PF_FP_ABST
    Figure EP2024060877_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The invention relates to a method for enabling a remote control service for a vehicle. The method comprises receiving a handover request for handing over control of the motor vehicle to a control unit of the remote control service, the handover request comprising context information regarding the permissible context of the remote control service. The method also comprises receiving a mission request for a remote control service mission, and checking the validity of the mission request based on the context information. Furthermore, the method comprises, depending on the checking step, triggering the vehicle to execute the remote control service mission initiated by the control unit.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Method and control unit for enabling a remote control service for a vehicle

[0002] The invention relates to a method and a corresponding control unit for enabling a remote control service for a (motor) vehicle.

[0003] A vehicle may have one or more functions that can be remotely controlled by a user of the vehicle using an electronic device, such as a smartphone. An example vehicle function is opening and / or closing a door or hatch of the vehicle and / or performing an automated parking process. The remote control of the one or more vehicle functions typically occurs via a wireless communication connection between the vehicle and the electronic (key) device, while the electronic device is arranged near the vehicle. A user of a vehicle may wish to enable another entity (e.g. a service provider) to perform one or more vehicle functions of the vehicle, in particular an automated parking maneuver, without the user's electronic device having to be arranged near the vehicle.

[0004] This document deals with the technical task of enabling a vehicle-external unit to remotely control a vehicle function, in particular the release of the vehicle's immobilizer, in a secure manner, even without the spatial and / or temporal presence of a key device.

[0005] The problem is solved by each of the independent claims. Advantageous embodiments are described, among other things, in the dependent claims. It should be noted that additional features of a patent claim dependent on an independent patent claim can form a separate invention, independent of the combination of all features of the independent patent claim, without the features of the independent patent claim or only in combination with a subset of the features of the independent patent claim, which invention can be made the subject of an independent claim, a divisional application, or a subsequent application. This applies equally to technical teachings described in the description, which can form an invention independent of the features of the independent patent claims.

[0006] According to one aspect, a method for enabling a remote control service for a (motor) vehicle (e.g., for a passenger car, a truck, a bus, and / or a motorcycle), in particular for remotely controlling a vehicle, is described. The method can be carried out by a control unit of a system, wherein the system further comprises the vehicle and a control unit for controlling the remote control service. The control unit and the control unit are separate units that are designed to communicate via a communication connection (in particular a remote communication connection, such as a wide area network, WAN). The control unit and the control units are typically operated by different (legal and / or organizational) entities. The control unit can be operated by a manufacturer of the vehicle. The control unit can be operated by a service provider of the remote control service.The control unit and the control unit are typically spatially separated, e.g., with a distance of 10km or more.

[0007] The system typically further comprises an electronic key device (in particular a mobile user device, such as a smartphone) of a user of the vehicle. The key device can have a digital key. The digital key can be designed according to the Car Connectivity Consortium (CCC) key standard, in particular according to CCC Release 3. The digital key can be designed to enable the key device to control one or more vehicle functions of the vehicle. Example vehicle functions are opening and / or closing a vehicle door and / or starting and / or stopping the vehicle's drive engine and / or automated and / or remote-controlled parking of the vehicle.

[0008] The method comprises receiving a handover request sent by the key device for handing over the motor vehicle to the remote control service, in particular to the control unit of the remote control service. The handover request can be directed to handing over the authorization to remotely control one or more vehicle functions of the motor vehicle to a remote control service, in particular to the control unit of a remote control service. The handover request can include context information relating to the permissible context for the remote control service. The context information can specify: • the permissible spatial area for one or more missions of the remote control service;

[0009] • the permitted period for one or more remote control service missions; and / or

[0010] • one or more vehicle functions of the vehicle that may be remotely controlled by the control unit as part of a remote control service mission.

[0011] The context information can thus describe and / or define the framework (defined by the user of the key device) for the implementation of the remote control service.

[0012] The method further comprises receiving a mission request for a mission (e.g., for a specific trip) of the remote control service, sent by the remote control service, in particular by the control unit of the remote control service. A mission of the remote control service can include, in particular, an action, a process, a deployment, and / or an order of the remote control service. A mission of the remote control service can, in particular, alternatively be referred to as an action, process, deployment, and / or order of the remote control service.

[0013] The mission request for the remote control service mission may specify

[0014] • the geographical area of ​​the mission;

[0015] • the duration of the mission; and / or

[0016] • the one or more vehicle functions of the vehicle that are to be remotely controlled by the control unit as part of the mission.

[0017] The request for transmission and / or the mission request can be sent by the respective sender (i.e., the key device or the control unit) and received directly or indirectly (e.g., via one or more intermediate communication stages) by the control unit. Furthermore, the method includes checking the admissibility of the mission request based on the context information. In particular, it can be checked whether the requested mission falls within the context for the remote control service defined by the context information.

[0018] Depending on the check, the vehicle can then be prompted (or not prompted if the check fails) to execute the remote control service mission (initiated and / or requested by the control unit). If the requested mission lies within the defined context, the vehicle can be prompted to execute the remote control service mission. On the other hand, the execution of the remote control service mission can be prevented if it is detected that the requested mission lies outside the defined context. In particular, the vehicle can be prompted (if the check is successful) to release the vehicle's electronic immobilizer in order to execute or be able to execute the remote control service mission. The actual remote control of the vehicle to execute the mission can be carried out by the remote control service control unit.

[0019] This allows for the provision of a central (vehicle-external) control unit that enables the secure execution of one or more remote control service missions even without the physical and / or temporal presence of the key device. In particular, no further communication between the key device and the vehicle may be required to execute the remote control service mission.

[0020] The method may include receiving a cryptographic session signature of the key device along with the handover request. The session signature may be based on the key device's digital key. Verifying the handover request and / or the context information, in particular the authenticity of the handover request and / or the context information, can then be performed in a particularly reliable manner based on the cryptographic session signature. The handover request and / or the context information may only be considered by the control unit if the handover request and / or the context information has been successfully authenticated.

[0021] The method may include receiving a request (sent by the key device) to create key data to enable the vehicle for remote control services. Key data may then be generated in response to the request. A first portion of the key data may be stored in a (secure) key storage module of the control unit. Furthermore, a second portion of the key data (in particular the key pair) may be sent to the vehicle (and stored there). By generating key data, a particularly secure and robust enablement of remote control services for the vehicle can be achieved.In particular, it can be effected that the first part of the key data for enabling the vehicle for remote control services, stored in the key storage module of the control unit, is sent to the vehicle in order to cause the vehicle to carry out the mission of the remote control service (in particular releasing the immobilizer).

[0022] The method may include receiving authentication data for authenticating the key device along with the aforementioned request. The authentication data may be based on the digital key of the key device. The request may then be authenticated based on the authentication data, and the key data for enabling the vehicle for remote control services may be provided (only) after the request has been (successfully) authenticated. This allows for particularly secure enabling of the vehicle for remote control services.

[0023] The method may include receiving availability data sent by the remote control service, in particular by the control unit of the remote control service, indicating that the remote control service, in particular the control unit of the remote control service, is available to provide the remote control service. Availability information relating to the received availability data may then be sent to the key device. Receiving the handover request may occur (possibly only) in response to the transmission of the availability information. This further increases the robustness of the provision of a remote control service.

[0024] According to another aspect, a software (SW) program is described. The SW program can be configured to be executed on a processor and thereby to carry out the method described in this document.

[0025] According to a further aspect, a storage medium is described. The storage medium can comprise a software program configured to be executed on a processor and thereby to carry out the method described in this document.

[0026] According to a further aspect, a control unit (e.g., with one or more computing units, such as servers) for enabling a remote control service to remotely control a motor vehicle is described. The control unit is configured to receive a handover request, sent by a key device, for handing over the motor vehicle to the remote control service, in particular to a control unit of the remote control service, wherein the handover request comprises context information relating to the permissible context of the remote control service or for the remote control service. The control unit is further configured to receive a mission request, sent by the remote control service, in particular by the control unit of the remote control service, for a mission of the remote control service to remotely control the motor vehicle, and to check the admissibility of the mission request based on the context information.In addition, the control unit is configured to cause the vehicle to execute the remote control service mission (initiated and / or requested by the control unit) depending on the check.

[0027] According to a further aspect, a key device of a user of a motor vehicle (e.g., a mobile user device, such as a smartphone) is described. Furthermore, a method corresponding to the key device is described. The key device is configured to send a handover request to hand over the motor vehicle to a remote control service (in particular to hand over the motor vehicle to the control unit of a remote control service). The handover request can include context information relating to the permissible context for the remote control service. The key device and / or the corresponding method can have (any) one or more of the features described in this document in connection with a key device.

[0028] According to a further aspect, a control unit for providing a remote control service for remotely controlling a motor vehicle is described. Furthermore, a method corresponding to the control unit is described. The control unit is configured to send a mission request for a mission of the remote control service for remotely controlling the motor vehicle to a control unit for enabling the remote control service. The control unit can be designed as a backend of the motor vehicle. The control unit and / or the corresponding method can have (any) one or more of the features described in this document in connection with a control unit. According to a further aspect, a motor vehicle is described which comprises one or more vehicle functions that can be remotely controlled. Furthermore, a method corresponding to the motor vehicle is described.The motor vehicle is configured to be initiated by a vehicle-external control unit to execute a remote control service mission for remotely controlling the motor vehicle (where the remote control service mission was requested by a separate, vehicle-external control unit). The motor vehicle and / or the corresponding method may have (any) one or more of the features described in this document in connection with a vehicle.

[0029] According to a further aspect, a system and a corresponding method are described. The system comprises a control unit, a control unit, at least one key device, and at least one vehicle, each configured as described in this document.

[0030] It should be noted that the methods, devices, and systems described in this document can be used both alone and in combination with other methods, devices, and systems described in this document. Furthermore, any aspects of the methods, devices, and systems described in this document can be combined in a variety of ways. In particular, the features of the claims can be combined in a variety of ways. Furthermore, features listed in parentheses are to be understood as optional features.

[0031] The invention will be described in more detail below using exemplary embodiments.

[0032] Figure 1a shows an exemplary digital access system of a vehicle;

[0033] Figure 1b shows an example usage situation for a digital access system; Figure 2 shows example messages between a vehicle and a digital key device;

[0034] Fig. 3 shows an exemplary system for remotely controlling a vehicle function of a vehicle;

[0035] Figures 4a, 4b and 4c are flowcharts of exemplary methods for storing key data for a remote control service;

[0036] Figures 5a, 5b, and 5c show flowcharts of exemplary methods for transferring the vehicle to the control unit of a remote control service provider; Figures 6a, 6b, and 6c show flowcharts of exemplary methods for enabling a remote control mission of the remote control service; and Figure 7 shows a flowchart of an exemplary method for enabling a remote control service for a vehicle.

[0037] As stated at the outset, this document deals with the secure capability of a remote control service provider to remotely control a vehicle function of a vehicle 100 without using a digital key device 110.

[0038] Fig. 1a shows an exemplary (access) system 150 comprising at least one vehicle 100 and a digital key device 110. The digital key device 110 is typically a portable electronic device, such as a smartphone or a tablet PC, with a digital key 111 stored on the portable electronic device. The digital key 111 can be stored in a protected storage area, in particular in a so-called "secure element," of the portable electronic device (e.g., the user device).

[0039] The digital key device 110 is configured to communicate with a communication unit 102 of the vehicle 102 via one or more different wireless communication connections 112. The different communication connections 112 can be used for different purposes. In particular, a Bluetooth Low Energy (BLE) communication connection 112 can be used to

[0040] • to determine the distance and / or relative position between the digital key device 110 and the vehicle 100 (in particular based on the signal strength, in particular the RSSI (Received Signal Strength Indicator), of the radio signals exchanged between the vehicle 100 and the device 110; and / or using BLE Channel Sounding (mode 2 / phase-based measurements)); and / or

[0041] • To exchange data between the digital key device 110 and the vehicle 100 (e.g., a control command for controlling a vehicle function 103, such as unlocking a door and / or opening or closing a window and / or activating or deactivating a heating function and / or activating or deactivating the drive motor of the vehicle 100).

[0042] Alternatively or additionally, an ultrawideband (UWB) communication link 112 may be used to determine the position of the device 110 relative to the vehicle 100 with a relatively high degree of accuracy. Determining the position of the device 110 using the UWB communication link 112 may be referred to as UWB ranging.

[0043] A (control) device 101 of the vehicle 100 can be configured to control at least one vehicle function 103 of the vehicle 100 depending on the communication between the device 110 and the vehicle 100, as shown by way of example in Fig. 1b. In this context, the digital key 111 of the device 110 can be verified, in particular authenticated. Furthermore, after successful authentication, one or more vehicle functions 103 can be controlled, in particular depending on

[0044] • the distance between the device 110 and the vehicle 100; the position of the device 110 relative to the vehicle 100; and / or a control command sent from the device 110 to the vehicle 100 via a communication link 112.

[0045] In an exemplary system 150, a BLE communication connection 112 may be established between the device 110 and the vehicle 100 as soon as the distance between the device 110 and the vehicle 100 is equal to or less than a first distance threshold 121. This enables the user to remotely control one or more vehicle functions 103 using the device 110. Typically, the vehicle 100 repeatedly indicates, e.g., at a certain frequency, the availability of a BLE communication connection 112. Starting at the first distance threshold 121, the device 110 (which may also be referred to as "user equipment" (UE)) receives the indication message from the vehicle 100, and the BLE communication connection 112 may then be established between the device 110 and the vehicle 100.The first distance threshold 121 may depend on the communication capabilities of the device 110, the environment of the vehicle 100 and / or the device 110, and / or the position of the device 110 relative to the vehicle 100.

[0046] Furthermore, a UWB communication connection 112 can be established between the device 110 and the vehicle 100 as soon as the distance between the device 110 and the vehicle 100 is equal to or less than a second distance threshold 122 (which can be less than the first distance threshold 121 and / or which can depend on the communication capabilities of the device 110). Based on the UWB communication connection 112, the location of the device 110 can be determined with relatively high accuracy. One or more further vehicle functions 103 can optionally be controlled via the UWB communication connection 112 (in addition to the one or more functions 103 that can be controlled via the BLE communication connection 112). Fig. 2 illustrates this (optionally.repeated, in particular periodic) transmission of an indication message 201 by the vehicle 100 to indicate that a (BLE) communication connection 112 can be established with the vehicle 100. Fig. 2 further shows a response message 202 that is sent from the device 110 to the vehicle 100 in response to the receipt of an indication message 201 in order to establish the communication connection 112. Following the establishment of the (BLE) communication connection 112, messages 203, 204 can be exchanged between the vehicle 100 and the device 110 via the communication connection 112, e.g., to remotely control a vehicle function 103.

[0047] As explained above, the user of a vehicle 100 may wish to enable a service provider to remotely control a vehicle function 103 of the vehicle 100, e.g., to effect an automated (driverless) parking process of the vehicle 100, without having to hand over his electronic key device 110 to the service provider.

[0048] Fig. 3 shows an exemplary system 300 for remotely controlling one or more vehicle functions 103 of a vehicle 100. The system 300 comprises at least one control unit 330 (e.g., with one or more computing units, such as servers) of a remote control service provider for remotely controlling at least one vehicle function 103 of the vehicle 100. Furthermore, the system 300 comprises at least one monitoring unit 320 (e.g., with one or more computing units, such as servers) of a monitoring authority (e.g., a manufacturer of the vehicle 100). The control unit 330 and the monitoring unit 320 can be configured to communicate with one another via a communication connection 343 (e.g., a wired and / or wireless communication connection).The control unit 320 can be configured to communicate with the vehicle 100 via a (wireless) communication connection 342 and / or with the key device 110 of the user 310 via a (wireless) communication connection 344. The control unit 330 can be configured to communicate with the vehicle 100 via a (wireless) communication connection 345. The individual communication connections 342, 344, 345 can each be configured for long-distance communication (over a distance of 500 meters or more, in particular 1 km or more, in particular 10 km or more). The individual communication connections 342, 344, 345 can each be composed of several sections of different partial communication connections (e.g., wireless or wired).

[0049] As vehicle function 103, for example, the release of an electronic immobilizer of vehicle 100 can be effected. In this context, the steering of vehicle 100 can be released (e.g., by releasing a steering lock). Alternatively or additionally, the engine control of a drive motor of vehicle 100 can be enabled.

[0050] The secure release of the electronic immobilizer typically requires that a correspondingly valid key 111 is located on a terminal device 110 (e.g., ID transmitter, smartphone) in the immediate vicinity of or in the vehicle 100 to be released. From the spatial and temporal presence of the key 111 on or in the vehicle 100, the intention of the user 310 to move the secured vehicle 100 can be inferred. A secure release of the immobilizer is usually only possible if a correspondingly valid key 111, and thus also the user 310, is located temporally and spatially immediately on or in the vehicle 100 before a journey is to be undertaken. This prerequisite is usually not met with a driverless driving function, especially when operated by a service provider. Furthermore, the user 310 and / or the terminal device 110 are usually not available for further releases of individual journeys (i.e., individual missions) of the vehicle 100 (e.g.,because the user 310 has left the vehicle 100 at a parking lot and is in an airplane). To provide a driverless driving function by a service provider, it is typically necessary that the electronic immobilizer securing the vehicle 100 can be released for driving even without the immediate spatial and temporal presence of the correspondingly authorized key(s) 111, in a previously agreed spatial, temporal and / or application-related context. For this purpose, the will of the user 310 to transfer the ability to release the immobilizer of the vehicle 100 for a specific period of time and / or for a defined purpose to an authenticated and integrity-based entity 330 (in particular to the control unit 330) can be stored centrally in a digitally and cryptographically secured manner (e.g., on the control unit 320).

[0051] The user identity, the period of use, the purpose of use, the affected vehicle 100, and / or the identification of the automated driving system can be cryptographically stored in a session token or session signature, which is managed in trust in a central control unit 320 (e.g., in a system provided by the vehicle manufacturer, such as a vehicle backend). Upon request (e.g., by the vehicle 100), the context can be verified, and if the verification is successful, the linked key part can be transferred to the vehicle 100 so that the immobilizer can be released by the vehicle 100.

[0052] The measures described in this document can be used, for example, within the framework of an Automated Valet Parking (AVP) function 103. In this case, the user 310 hands over the previously enabled vehicle 100 in an AVP-enabled parking garage to the AVP parking system (i.e., to the control unit 330). The operator of the AVP parking system (i.e., the service provider) may wish to drive the vehicle 100 or have it driven automatically while it is in the parking garage (e.g., for parking, re-parking, trips to the charging station, car wash, etc.). The one or more individual trips (i.e., missions) should take place without further authorization from the user 310 (e.g., because the user 310 is unavailable).

[0053] The user 310 has a terminal device 110 that supports the secure storage, management and processing of cryptographic key material 111. As part of a secure pairing process between the terminal device

[0054] A cryptographic key pair can be generated between the terminal 110 and the vehicle 100, which enables the activation of a vehicle function 103 (in particular, the activation of the electronic immobilizer). Part of the key pair 111 remains in the secure management of the terminal 110, and part is transferred to the secure key management of the vehicle 100.

[0055] The key device 110 of the user 310 and the vehicle 100 can thus each have a key 111 that enables the user 310 to remotely control one or more vehicle functions 103 using the key device 110 (as explained in connection with Figures 1a, 1b, and 2). These keys 111 can be used to enable a service provider (i.e., the control unit 330 of a service provider) to remotely control a vehicle function 103 without the spatial and / or temporal presence of the key device 110. For this purpose, key data for enabling remote control services can be generated and stored in an enabling phase.

[0056] During the enabling phase, the user 310 can send a request (via the communication link 344) from the key device 110 to the control unit 330 to cause the control unit 320 to generate key data for a remote control service. The request can be generated by a software application 311 of the device 110. Furthermore, the request can be sent to a service module 321 of the control unit 320 and received by the service module 321. The request can be based on the key

[0057] 111 of the device are cryptographically signed so that a management module 322 of the control unit 320 (for managing key data) can check and confirm the authenticity of the request.

[0058] Upon confirmation, new cryptographic key material (i.e., key data for the remote control service) is generated by the control unit 320, in particular by the management module 322. A first portion remains in a secure storage module 323 of the control unit 320, and a second portion is transferred to a secure storage module 302 of the vehicle 100 via a cryptographically secured data connection (via the communication connection 342).

[0059] Fig. 4a shows an exemplary (possibly computer-implemented) method 400 for enabling a remote control service. The method 400 can be executed by the key device 110. Within the scope of the method 400, it can be determined (e.g., based on a user input) (step 401) that the user 310 wishes to enable a remote control service. In response, the key device 110 sends a (signed) request to create key data for a remote control service (together with authentication data) to the control unit 320.

[0060] Fig. 4b shows an exemplary (possibly computer-implemented) method 410 for enabling a remote control service. The method 410 can be executed by the control unit 320. In a step 411, the request to create the key data for a remote control service can be received by the control unit 320. The request can be authenticated based on the authentication data (in particular based on the signature) (step 412). After authentication has been completed, the key data can be generated (step 413), and a first part of the key data can be stored in the key storage module 323 of the control unit 320 (step 414), and a second part of the key data can be sent to the vehicle 100 (step 415). Fig. 4c shows an exemplary (possibly computer-implemented) method 420 for enabling a remote control service.Method 420 may be performed by vehicle 100. The second portion of the key data may be received (via communication link 342) from vehicle 100 (step 421) and stored in a key storage module 302 of vehicle 100 (step 422).

[0061] Following the basic qualification for a remote control service, the vehicle 100 can be handed over to a remote control service provider, in particular to the control unit 330 of the remote control service provider.

[0062] For example, the control unit 330 can detect that the vehicle 100 is located in a spatial area (such as a parking lot) in which a remote control service can be provided. The control unit 330 can

[0063] Control unit 320 may indicate (through an availability message) that control unit 330 is available to provide a remote control service.

[0064] Alternatively or additionally, a transfer request for transferring the vehicle 100 to the control unit 330 of the remote control service provider can be sent from the key device 110 to the control unit 320, in particular to the service module 321 of the control unit 320 (via the communication link 344). The transfer request can include authentication data (e.g., a session signature). Furthermore, the transfer request can specify context information with one or more constraints for the remote control service. Example constraints are:

[0065] • a spatial area in which the remote control service can be carried out;

[0066] • a period of time during which the remote control service can be performed; and / or • one or more vehicle functions 103 that may be remotely controlled as part of the remote control service.

[0067] The permissible context of the remote control service can therefore be determined within the framework of the handover request.

[0068] Immediately before the transfer of authority over the vehicle 100 from the user 310 to the control unit 330, the user 310 can be requested at the terminal 110 to confirm the transfer to the control unit 330 for the remote control service (e.g., for one or more subsequent trips). A session signature can be generated in the key management of the terminal 110 using the stored key 111 and transmitted to the control unit 320. The session signature represents an application-related, context-related (location, time), cryptographically secured declaration of intent by the user 310 to release the immobilizer in the previously confirmed context. The control unit 320 serves as a trustee for the user 310.

[0069] Fig. 5a shows an exemplary (possibly computer-implemented) method 500 for handing over the vehicle 100 to the control unit 330 of a remote control service. The method 500 can be carried out by the key device 110. The key device 110 can determine (step 501) that the handover of the vehicle 100 to the control unit 330 should be effected to carry out a remote control service. For example, the key device 110 can have been informed by the control unit 320 that the control unit 330 is available for the remote control service. A handover request with authentication data, in particular with a session signature, can then be sent to the control unit 320 (step 502). The handover request can specify one or more boundary conditions (i.e., the context) of the remote control service (in the form of context information). Fig. 5b shows an exemplary (possibly computer-implemented)Computer-implemented method 510 for transferring the vehicle 100 to the control unit 330 of a remote control service. The method 510 can be executed by the control unit 320. It can be determined that the control unit 330 is available to perform the remote control service (step 511). This can be detected based on availability data received from the control unit 330 (via the communication link 343). The key device 110 can then be informed of the availability of the control unit 330.

[0070] The method 510 further includes receiving 512 the handover request with the authentication data (in particular with the session signature) sent by the encryption device 110. Based on the received handover request, in particular based on the session signature, the permissibility of the execution of the remote control service by the control unit 330 can then be checked (step 513).

[0071] Fig. 5c shows an exemplary (possibly computer-implemented) method 530 for handing over the vehicle 100 to the control unit 330 of a remote control service. The method 530 can be executed by the control unit 330. It can be detected (step 531) that a remote control service is to be provided for a vehicle 100 (e.g., because the vehicle 100 is located in a specific spatial area, such as a parking lot). Availability data relating to the availability of the control unit 330 to perform the remote control service can then be sent to the control unit 330 associated with the vehicle 100 (step 532).

[0072] Following the handover of the vehicle 100 to a control unit 330 for a remote control service, one or more missions (e.g., trips) for remote control of the vehicle 100 can be released. For this purpose, the control unit 330 can report a planned trip (generally a mission) to the control unit 320 (e.g., by sending a mission request). If the mission request corresponds to the context previously stored in the session signature (and thus fulfills one or more specified boundary conditions), the control unit 320 can inform the vehicle 100 that a valid mission exists. The vehicle 100 can confirm the mission and can request the transmission of the second key part, which is necessary to release the remotely controlled vehicle function 103 (in particular, to release the immobilizer).

[0073] The session signature can be transferred to the key management module 322, which, after a successful integrity and authenticity check, transmits the vehicle-specific key portion to the vehicle 100, allowing remote control of the vehicle function 103, in particular the release of the immobilizer. This process can be repeated (for a large number of missions) within the validity of the session signature.

[0074] Fig. 6a shows an exemplary (possibly computer-implemented) method 610 for enabling a remote control service mission. Method 510 can be executed by control unit 320. Method 510 includes receiving 511 a mission request to execute a remote control service mission. The mission request can be verified taking into account the stored context for the remote control service (step 612). After successful verification, the second part of the key data can be sent to vehicle 100 to enable the remote control service mission (step 613).

[0075] Fig. 6b shows an exemplary (possibly computer-implemented) method 620 for enabling a remote control service mission. Method 620 can be executed by vehicle 100. Within the scope of method 620, the second part of the key data can be received by vehicle 100 (step 621). This can be interpreted as enabling the remote control service mission. The mission can then be executed, in particular enabling the electronic immobilizer. Furthermore, one or more control commands can be received from control unit 330 (step 622). Vehicle function 103 can be controlled depending on the one or more control commands.

[0076] Fig. 6c shows an exemplary (possibly computer-implemented) method 630 for enabling a remote control service mission. Method 630 can be executed by control unit 330. Method 630 includes sending 631 a mission request for a remote control service mission to control unit 320. Method 630 can further include sending 632 one or more control commands to vehicle 100 to execute the mission.

[0077] The release of the remote control service can be terminated upon expiration of the (temporal) validity of the session signature. Alternatively or additionally, the release can be terminated in response to a termination request from vehicle 100 and / or control unit 320 and / or key device 110. The session signature can then be marked as invalid (within memory module 323).

[0078] Fig. 7 shows an exemplary (possibly computer-implemented) method 700 for enabling a remote control service for a motor vehicle 100 or for remotely controlling a motor vehicle 100. The method 700 can be executed by the control unit 320. The method 700 can include one or more (arbitrary) steps from the methods 410, 510, and / or 610.

[0079] The method 700 includes receiving 701, 512 a handover request sent by the key device 110 to hand over the motor vehicle 100 to the remote control service, in particular to the control unit 330 of the remote control service (to enable and / or effect remote control of the motor vehicle 100 by the remote control service). The handover request may include context information regarding the permissible context of the remote control service (such as the permissible spatial area and / or the permissible time period).

[0080] The method 700 further comprises receiving 702, 611 a mission request sent by the remote control service, in particular by the control unit 330 of the remote control service, for a mission of the remote control service for remotely controlling the motor vehicle 100, and checking 703, 612 the admissibility of the mission request on the basis of the context information.

[0081] Furthermore, depending on the verification 703, 612, the method 700 includes initiating 704, 613 the vehicle 100 to execute the remote control service mission (initiated and / or requested by the control unit 330). In particular, upon successful verification of the mission request, the second part of the key data can be sent to the vehicle 100 to enable the execution of the remote control service mission (in particular by releasing the electronic immobilizer of the vehicle 100).

[0082] The measures described in this document enable efficient, reliable and secure remote control of one or more vehicle functions 103 by a remote control service provider (without the local presence of a digital key device 110).

[0083] The present invention is not limited to the embodiments shown. In particular, it should be noted that the description and figures are intended only to illustrate the principle of the proposed methods, devices, and systems by way of example.

Claims

Claims 1) A method (700) for enabling a remote control service to remotely control a motor vehicle (100); the method (700) comprising - receiving (701) a handover request sent by a key device (110) for handing over the motor vehicle (100) to a remote control service; wherein the handover request comprises context information relating to a permissible context for the remote control service; - receiving (702) a mission request sent by the remote control service for a mission of the remote control service for remotely controlling the motor vehicle (100); - checking (703) the admissibility of the mission request based on the context information; and - depending on the checking (703), causing (704) the vehicle (100) to carry out the mission of the remote control service. 2) Method (700) according to claim 1, wherein the method (700) comprises - receiving a cryptographic session signature of the key device (110) together with the handover request; and - Verifying the resulting request and / or the context information, in particular the authenticity of the transfer request and / or the context information, based on the cryptographic session signature. 3) Method (700) according to claim 2, wherein - the session signature is based on a digital key (111) of the key device (110); and - the digital key (111) in particular according to a Car Connectivity Consortium, CCC, key standard, in particular according to CCC Release 3. 4) Method (700) according to one of the preceding claims, wherein the context information indicates - an authorised spatial area for one or more remote control service missions; - a permissible period for one or more remote control missions; and / or - one or more vehicle functions (103) of the vehicle (100) which may be remotely controlled by the control unit (330) as part of a remote control service mission. 5) Method (700) according to one of the preceding claims, wherein the mission request for the mission of the remote control service indicates - a spatial area of ​​the mission; - a period of the mission; and / or - one or more vehicle functions (103) of the vehicle (100) which are to be remotely controlled by the control unit (330) as part of the mission. 6) Method (700) according to one of the preceding claims, wherein the method (700) comprises - receiving a request to create key data to enable the vehicle (100) for remote control services; - Generating key data; - storing a first part of the key data in a key storage module (323) of a control unit (320); and - Sending a second part of the key data to the vehicle (100). 7) Method (700) according to claim 6, wherein the method (700) comprises - Receiving authentication data for authenticating the key device (110) together with the request; wherein the authentication data is based in particular on a digital key (111) of the key device (110); - Authenticating the request based on the authentication data; and - After authenticating the request, generate the key data. 8) Method (700) according to one of the preceding claims, wherein the method (700) comprises sending a first part of key data for enabling the vehicle (100) for remote control services, stored in a key storage module (323) of a control unit (320), to the vehicle (100) in order to cause the vehicle (100) to carry out the mission of the remote control service. 9) Method (700) according to one of the preceding claims, wherein the method (700) comprises, in dependence on the checking (703), causing (704) the vehicle (100) to release an electronic immobilizer of the vehicle (100) in order to carry out the mission of the remote control service. 10) Method (700) according to one of the preceding claims, wherein the method (700) comprises - receiving availability data sent by the remote control service indicating that a control unit (330) is available to provide the remote control service; - sending availability information relating to the received availability data to the key device (110); and Receiving (701) the handover request in response to sending the availability information. 11) Control unit (320) for enabling a remote control service to remotely control a motor vehicle (100); wherein the control unit (320) is configured - to receive a handover request sent by a key device (110) for handing over the motor vehicle (100) to a remote control service; wherein the handover request comprises context information relating to a permissible context for the remote control service; - to receive a mission request sent by the remote control service for a mission of the remote control service for remotely controlling the motor vehicle (100); - to check the admissibility of the mission request based on the context information; and - depending on the checking, to cause the vehicle (100) to carry out the mission of the remote control service. 12) Key device (110) of a user of a motor vehicle (100); wherein the key device (110) is configured - to send a handover request for handing over the motor vehicle (100) to a remote control service; wherein the handover request comprises context information relating to a permissible context for the remote control service. 13) Control unit (330) for providing a remote control service for remotely controlling a motor vehicle (100); wherein the control unit (330) is configured - a mission request for a mission of the remote control service for remote control of the motor vehicle (100) to a control unit (320) to enable the remote control service. 14) Motor vehicle (100) comprising one or more vehicle functions (103) that can be remotely controlled; wherein the motor vehicle (100) is designed, - to be prompted by a vehicle-external control unit (320) to carry out a mission of a remote control service for remotely controlling the motor vehicle (100).

Citation Information

Patent Citations

  • System access using a mobile device

    EP3590225A1

  • Device and method for updating immobilizer token in digital key sharing system

    US20220131687A1

  • Electronic device and method for controlling vehicle based on driver authentication

    US20230147516A1