Method and device for activating a vehicle application
An event-driven activation mechanism for vehicle control applications on user devices addresses power consumption issues by using BLE communication and pass-through messages, ensuring efficient operation and user notification without battery drain.
Patent Information
- Application Number
- DE102024103473
- Authority / Receiving Office
- DE · DE
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-08
- Publication Date
- 2025-08-14
AI Technical Summary
The operation of vehicle control applications on user devices, such as smartphones, consumes significant power, reducing battery life due to persistent activation, even when not in use.
Implementing an event-driven activation mechanism for vehicle control applications on user devices, utilizing Bluetooth Low Energy (BLE) communication to receive notification messages, allowing the application to be automatically activated upon detection of specific vehicle events, such as open doors or left occupants, and using a pass-through message to minimize power consumption.
Enables efficient battery usage by automatically activating the application only when necessary, maintaining functionality without compromising user notification and control quality.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[0001] The invention relates to a method and a corresponding device for activating a vehicle application on a user device for controlling one or more functions of a (motor) vehicle.
[0002] A vehicle may have one or more functions that can be controlled by a vehicle user using an electronic user device, such as a smartphone. The electronic user device has a digital key that is verified by the vehicle to authenticate the user device and, following authentication of the user device, to enable control of one or more vehicle functions.
[0003] Examples of vehicle functions include opening or unlocking and / or closing or locking a vehicle door or tailgate, and / or starting the vehicle's engine. Authentication of the digital key and / or control of one or more vehicle functions typically occurs via a wireless communication connection, in particular via a BLE (Bluetooth Low Energy) communication connection and / or via a Near Field Communication (NFC) communication connection, between the vehicle and the electronic (key) device.
[0004] The control of one or more vehicle functions is typically carried out using a vehicle application running on the key device. Running the vehicle application on the key device consumes energy, which reduces the battery life of the key device.
[0005] This document deals with the technical task of enabling particularly energy-efficient operation of a key device for controlling one or more vehicle functions.
[0006] 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.
[0007] According to one aspect, a device for a key device is described. The key device can be a (mobile and / or electronic and / or handheld) user device, such as a smartphone. The device can be configured to provide the operating system of the key device.
[0008] The key device comprises a digital key for controlling one or more vehicle functions of a (motor) vehicle. The digital key is typically stored in a secure memory area (in particular, in a secure element) of the key device. The digital key can be configured according to the Car Connectivity Consortium, CCC, standard (CCC TS-101), in particular according to CCC Release 3. Alternatively or additionally, the digital key can be configured according to a specific (in particular, asymmetric) cryptosystem or cryptographic method, in particular, elliptic curve cryptography (ECC).
[0009] Examples of vehicle functions include: unlocking or locking a door or hatch; starting the vehicle's engine; adjusting a vehicle setting; etc.
[0010] The device is configured to receive a notification message relating to a notification situation present in the vehicle via a (BLE) communication connection. The notification situation may include, for example, an open window or an open door of the vehicle. Alternatively or additionally, the notification situation may concern a passenger (such as a child) left behind in the vehicle's interior. Alternatively or additionally, the notification situation may concern an adjustment of the control of one or more vehicle functions.
[0011] The notification message may be a pass-through message according to the Car Connectivity Consortium, CCC, standard, in particular according to CCC Release 3.
[0012] The communication connection can be a Bluetooth Low Energy (BLE) communication connection, and the device can be configured to receive the notification message via a Logical Link Control and Adaptation Layer Protocol (L2CAP) channel of the BLE communication connection. Alternatively or additionally, the device can be configured to receive the notification message via the same channel of the BLE communication connection that is also used for data communication relating to the digital key between the vehicle and the key device. Alternatively or additionally, the device can be configured to receive the notification message via a pass-through channel of the BLE communication connection.
[0013] The device can thus detect that a notification message is received (via a specific channel of the BLE communication connection).
[0014] As already explained above, the key device can comprise a secure storage unit, in particular a secure element. An (executable) key applet (i.e., a software program) can be stored in the secure storage unit. The digital key can be stored in the same secure storage unit. The key applet can be configured to perform one or more actions with respect to the digital key (e.g., encrypting or decrypting messages with the digital key). The device can be configured to receive the notification message from the key applet.
[0015] A vehicle application (i.e., a software application) is located on the key device, which can be executed by the operating system of the key device. The vehicle application can be configured to enable a user to control one or more vehicle functions. The vehicle application can provide a user interface for the user via which a control instruction for controlling a vehicle function can be selected. The selected control instruction can be sent from the key device to the vehicle (and executed by the vehicle) via the (BLE) communication connection.
[0016] The device can be configured to detect that the vehicle application has not been used for a certain period of time (e.g., 10 minutes). In response to the detection, the device can cause the vehicle application to be automatically deactivated. This can reduce the power consumption of the key device.
[0017] The device is configured to (re)activate the vehicle application for controlling one or more vehicle functions in response to receiving the notification message.
[0018] In particular, the device can be configured to detect that the notification message is a pass-through message and / or that the notification message was received via a pass-through channel of the communication connection. The vehicle application can then be activated in response to the detection.
[0019] Receiving a notification message thus (preferably always) automatically activates the (inactive) vehicle application. This allows for event-dependent activation of the vehicle application. This allows for particularly energy-efficient and reliable control of one or more vehicle functions.
[0020] The device can further be configured to provide an (acoustic, optical, and / or visual) output to the user of the key device, based on the activated vehicle application, regarding the notification situation. This output can be, for example, a push notification (via the user interface of the key device). Alternatively or additionally, a (lock screen) widget for controlling one or more vehicle functions can be adapted as an output. This allows for particularly convenient and energy-efficient control of one or more vehicle functions.
[0021] The device (in particular the operating system of the key device) can be configured to operate one or more additional software applications in addition to the vehicle application. The vehicle application and the one or more additional software applications can be automatically deactivated if the respective application has not been used for a specific (respective) non-use period. The non-use period used for the vehicle application can be shorter than the non-use period used for the one or more additional software applications. This can be enabled, in particular, by event-dependent activation of the vehicle application. This can further increase the energy efficiency of the control of the one or more vehicle functions.
[0022] According to a further aspect, a (mobile and / or portable) user device (e.g., a smart device and / or a smartphone) is described that includes the device described in this document. The user device can be configured as a key device with a digital key.
[0023] According to a further aspect, a method for operating a key device is described, which comprises a digital key for controlling one or more vehicle functions of a (motor) vehicle. The method comprises receiving, via a communication connection, a notification message relating to a notification situation present at the vehicle. Furthermore, the method comprises, in response to receiving the notification message, activating a vehicle application for controlling the one or more vehicle functions. The method further comprises causing, based on the activated vehicle application, an output relating to the notification situation to a user of the key device.
[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] 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.
[0027] The invention will be described in more detail below using exemplary embodiments. Fig. 1a an exemplary digital access system of a vehicle; Fig. 1b an exemplary key device; Fig. 2 an exemplary transmission of a notification message from a vehicle to a key device; and Fig. 3 a flowchart of an exemplary method for activating a vehicle application.
[0028] As stated at the beginning, this document deals with the energy-efficient operation of a vehicle application for controlling one or more vehicle functions on a mobile user device. In this context, 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 (user) 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.
[0029] The digital key device 110 is configured to communicate with a communication unit 102, 105 of the vehicle 102 via one or more different wireless communication connections 112, 115. Exemplary communication connections 112, 115 are a Bluetooth Low Energy (BLE) communication connection 112 and / or a Near Field Communication (NFC) communication connection 115. Within the context of a (BLE) communication connection 112, one of the two communication partners (typically the device 110) has the status of a so-called "Central," and the other communication partner (typically the vehicle 100) has the status of a so-called "Peripheral."
[0030] The system 150 further comprises a central unit 140, e.g. a backend unit or a backend server, which is configured to communicate with the digital key device 110 and / or with the vehicle 100 (in particular with a communication unit 106 of the vehicle 100) via a respective wireless communication connection 131 (e.g. via a 3G, 4G, 5G communication connection).
[0031] 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. 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 • 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 connection 112, 115.
[0032] The scope of the one or more vehicle functions 103 that can be controlled by the key device 110 may depend on one or more properties of the digital key 111. In particular, it may be possible to enable one or more vehicle functions 103 and / or block one or more vehicle functions 103 using the digital key 111.
[0033] Fig. Figure 1b shows details of the electronic (key) device 110. In particular, Fig. 1b the secure storage area 116, in particular the so-called "secure element", in which the digital key 111 of the key device 110 and, if applicable, an attestation of this digital key 121 are stored. A software application 120 can be stored in the secure storage area 116, which is also executed in the secure storage area 116. The software application 120 can be designed to perform one or more functions related to the digital key 111, such as encrypting and / or decrypting data with the digital key 111 (in particular with the private key part of the digital key 111). The software application 120 for providing one or more key-related functions is also referred to as a key applet in this document.
[0034] The memory area 116 can be read by the operating system and / or by a control device 117 of the device 120 via a (secure) data interface 119. In particular, an interaction between the control device (in particular the operating system) 117 of the key device 110 and the key applet 120 can be enabled via a data interface 119, e.g., to enable the control device 117 to cause the key applet 120 to encrypt (e.g., sign) or decrypt data with the digital key 111.
[0035] Furthermore, the control device (in particular the operating system) 117 can be configured to interact with a software application 118 of the vehicle manufacturer via a further data interface 114, e.g., to forward data from the memory area 116, such as the digital key 121 and / or the attestation. The software application 118 of the manufacturer of the vehicle 100 can be configured to interact (directly) with the central unit 140 (of the manufacturer of the vehicle 100) (via the communication connection 131). If necessary, the central unit 140 can be enabled to interact directly (without integrating the software application 118) with the control device 117 of the key device 120 and / or with the secure memory area 116. The software application 118 of the vehicle manufacturer (which is provided, e.g., by an OEM (Original Equipment Manufacturer)) is also referred to in this document as the vehicle application 118.One or more additional software applications 128 can be executed on the key device 110.
[0036] The key device 110 typically comprises at least one communication unit 125 configured to establish a communication connection 112, 115 with a communication unit 102, 105 of the vehicle 100 (e.g., a BLE communication connection 112 and / or an NFC communication connection 115). The data to be transmitted can be provided directly by the key applet 120 and / or directly by the control device 117 to the communication unit 125.
[0037] The continuous operation of the vehicle application 118 on the key device 110 is typically associated with a certain amount of energy consumption. To increase the battery life of the key device 110, the control device (in particular the operating system) 117 of the key device 110 can cause the vehicle application 118 to be automatically deactivated after a certain period of non-use. Deactivating the vehicle application 118 results in the vehicle application 118 no longer being able to issue notifications (i.e., alerts) to the user of the key device 110, thereby impairing the quality of the remote control of one or more vehicle functions 103.
[0038] Fig. 2 shows an exemplary transmission of a notification message 201 from the vehicle 100 to the key device 110. The notification message 201 is transmitted via the BLE communication connection 112 between the vehicle 100 and the key device 110, whereby the BLE communication connection 112 can exist even if the vehicle application 118 has been deactivated. For example, the key device 110 can be located in the user's home, while the vehicle 100 is parked directly next to the home (within range of the BLE communication connection 112).
[0039] The (control) device 101 of the vehicle 100 can detect that a specific notification situation exists on the vehicle 100, about which the user of the vehicle 100 should be informed. Examples of notification situations are: • the fact that a window and / or a door of the vehicle 100 is open; • the fact that there is still an occupant (e.g. a child) in the vehicle 100, e.g. although the vehicle 100 has already been locked; and / or • the fact that a setting relating to the remote control of a vehicle function 103 should be adjusted.
[0040] If it is detected that a notification situation exists, the communication unit 102 of the vehicle 100 can be prompted by the (control) device 101 of the vehicle 100 to send a notification message 201 relating to the detected notification situation to the key device 110 via the existing BLE communication connection 112. Preferably, a specific pass-through channel, in particular a specific L2CAP (Logical Link Control and Adaptation Layer Protocol) channel, of the BLE communication connection 112 is used. Multiple notification messages 201 can each be sent (one after the other) via the same channel. Alternatively or additionally, the notification message 201 can be sent as a pass-through message (of the CCC-Ts-101 R.3 standard).
[0041] The notification message 201 is received by the communication unit 125 of the key device 110. Furthermore, the received notification message 201 can be evaluated, in particular verified, by the key applet 120. Furthermore, the (verified) notification message 201 can be forwarded to the (control) device 117 of the key device 110.
[0042] The (control) device 117 can detect that the notification message 201 is intended for the vehicle application 118. The (control) device 117 can then cause the vehicle application 118 to be activated automatically, i.e., without user intervention. The notification message 201 can then be passed to the activated vehicle application 118. Furthermore, the notification message 201 can be processed by the vehicle application 118, and the vehicle application 118 can, for example, cause an (optical, haptic, and / or acoustic) output relating to the notification situation to be output via the user interface of the key device 110.
[0043] Sending a notification message 201, particularly in the form of a pass-through message, thus enables interaction between the vehicle 100 and the user of the key device 110 even when the vehicle application 118 is deactivated. In particular, sending a notification message 201 can trigger an event-based activation of the vehicle application 118. This allows the vehicle application 118 to be automatically deactivated, even when the vehicle application 118 is not used for a relatively short period of time, in order to reduce the energy consumption of the remote control of one or more vehicle functions 103, without compromising the quality and / or convenience of the remote control.
[0044] The pass-through message defined in CCC-TS-101 R3 can thus be used to trigger an event-driven activation of the vehicle application 118 on a key device 110. By default, the pass-through message can be used by the vehicle application 118 and / or the vehicle 100 to exchange messages over the same L2CAP channel of the BLE communication link 112 that is also used in the Digital Key Service. By default, pass-through messages can only be sent and / or received when the vehicle application 118 is active (in the foreground or in the background of the key device 110).
[0045] The CCC Digital Key Rel. 3 standard allows a user to control certain vehicle functions 103 without having to use the vehicle application 118. As already explained above, the operating system 117 of the key device 110 can be configured such that the vehicle application 118 is automatically deactivated after the vehicle application 118 has been in the background for a certain period of non-use (e.g., 10 minutes).
[0046] It may be advantageous for the user to be informed of one or more events even when the vehicle application 118 is deactivated. Automatically waking up the vehicle application 118 when a BLE communication connection 112 is established (e.g., in response to the key device 110 approaching the vehicle 100) is often not sufficient, since the BLE communication connection 112 may be permanently active if the vehicle 100 is parked in the immediate vicinity of the home (and thus to the position of the key device 110). In such a scenario, the probability that the vehicle application 118 has been automatically deactivated (due to non-use) is relatively high, so that the vehicle 100 cannot send messages to the vehicle application 118, e.g., to trigger push notifications.
[0047] The measures described in this document make it possible to send a pass-through message even when the vehicle application 118 is inactive, thereby causing the automatic activation of the vehicle application 118.
[0048] As described in this document, the key device 110 can be configured in particular such that any activity on the pass-through channel, in particular any pass-through message 201 sent from the vehicle 100 to the key device 110, triggers the waking (i.e., activation) of the vehicle application 118. The waking occurs in an event-specific manner, so that the vehicle application 118 can be automatically terminated or deactivated relatively quickly (i.e., after a relatively short period of non-use), in particular faster than another software application 128 of the key device 110.
[0049] In one example, the vehicle 100 may detect that the window has been left open. This may be communicated to the user of the key device 110 via a push notification as the user walks away from the vehicle 100. In another example, the user may be informed via a push notification that a child has been left in the vehicle 100. In a further escalation level, a vehicle alarm may be triggered.
[0050] The vehicle application 118 can be configured to provide a lock screen widget for controlling one or more vehicle functions 103 on the screen of the key device 110. The lock screen widget, in particular the one or more vehicle functions 103 that can be controlled with the widget, can be adapted depending on the position of the key device 110 relative to the vehicle 100. For example, control of a specific vehicle door or the trunk can be enabled depending on whether the key device 110 is located near the specific vehicle door or near the trunk. The adaptation of the lock screen widget, or the set of one or more vehicle functions 103, can be effected by sending a notification message 201, in particular a pass-through message.
[0051] The vehicle 100 can detect that potentially unnecessary and / or repeated welcome orchestrations of the vehicle 100 are being performed, e.g., while the user is storing items in the vehicle 100 or mowing the lawn, and is therefore repeatedly located in the immediate vicinity of the vehicle 100. A notification message 201, in particular a pass-through message, can then be sent to the key device 110 to trigger the issuance of a push notification, prompting the user to disable the execution of welcome orchestrations of the vehicle 100, at least temporarily and / or at the current location.
[0052] Fig.3 shows a flowchart of an exemplary (possibly computer-implemented) method 300 for operating a key device 110, which includes a digital key 111 for controlling one or more vehicle functions 103 of a (motor) vehicle 100. The key device 110 can be a mobile and / or electronic and / or portable user device, such as a smartphone. The method 300 can be executed by a (control) device 117 of the user device or key device 110. An operating system of the device can be provided by the (control) device 117 of the user device or key device 110.
[0053] The method 300 includes receiving 301, via a (BLE) communication connection 112, a notification message 201 relating to a notification situation present at the vehicle 100. The notification situation can relate to an event detected at the vehicle 100 that led to the sending of the notification message 201. The notification message 201 can, in particular, be a so-called pass-through message, which is designed, for example, according to the CCC TS-101 Release 3 standard.
[0054] The method 300 includes, in response to receiving 301 the notification message 201, activating 302 the vehicle application 118 to control the one or more vehicle functions 103. The vehicle application 118 may be a software program executed by the operating system of the key device 110. The software program may have been deactivated (possibly due to non-use). Receiving the notification message 201 may result in the vehicle application 118 being activated automatically (without any action by the user of the key device 110).
[0055] Furthermore, the method 300 comprises causing 303, based on the activated vehicle application 118, an (acoustic, haptic and / or optical) output relating to the notification situation to the user of the key device 110. In particular, a push notification can be issued to the user.
[0056] The measures described in this document enable particularly energy-efficient operation of a vehicle application 118 on a key device 110 without impairing the quality of the remote control of one or more vehicle functions 103.
[0057] 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
[1] Device (117) for a key device (110) comprising a digital key (111) for controlling one or more vehicle functions (103) of a vehicle (100); wherein the device (117) is configured - to receive a notification message (201) relating to a notification situation present on the vehicle (100) via a communication connection (112); - in response to receiving the notification message (201), activate a vehicle application (118) for controlling the one or more vehicle functions (103); and - to cause an output relating to the notification situation to a user of the key device (110) based on the activated vehicle application (118). [2] Device (117) according to claim 1, wherein the notification message (201) is a pass-through message according to the Car Connectivity Consortium, CCC, standard, in particular according to CCC Release 3. [3] Device (117) according to one of the preceding claims, wherein - the communication connection (112) is a Bluetooth Low Energy, BLE, communication connection; and - the device (117) is configured to receive the notification message (201) via a Logical Link Control and Adaptation Layer Protocol (L2CAP) channel of the BLE communication connection. [4] Device (117) according to claim 3, wherein the device (117) is arranged to receive the notification message (201) via the same channel of the BLE communication link that is also used for data communication relating to the digital key (111) between the vehicle (100) and the key device (111). [5] Device (117) according to one of claims 3 to 4, wherein the device (117) is configured to receive the notification message (201) via a pass-through channel of the BLE communication connection. [6] Device (117) according to one of the preceding claims, wherein - the key device (110) comprises a secure storage unit (116), in particular a secure element, with a key applet (120); - the digital key (111) is stored in the secure storage unit (116); and - the device (117) is arranged to receive the notification message (201) from the key applet (120). [7] Device (117) according to one of the preceding claims, wherein the device (117) is arranged - to detect that the vehicle application (118) has not been used for a certain non-use period; and - in response to the detection, to deactivate the vehicle application (118). [8] Device (117) according to one of the preceding claims, wherein the device (117) is arranged - to operate one or more additional software applications (128) in addition to the vehicle application (118); and - to cause the vehicle application (118) and the one or more further software applications (128) to be automatically deactivated if the respective application (118, 128) has not been used for a certain non-use period; wherein the non-use period used for the vehicle application (118) is shorter than the non-use period used for the one or more further software applications (128). [9] Device (117) according to one of the preceding claims, wherein the device (117) is arranged to cause - a push notification is issued as output; and / or - a widget, in particular a lock screen widget, is adapted as output for controlling the one or more vehicle functions (103). [10] Device (117) according to one of the preceding claims, wherein the device (117) is arranged - to recognize that the notification message (103) is a pass-through message and / or was received via a pass-through channel of the communication connection (112); and - in response to the detection, to cause the vehicle application (118) to be activated. [11] Method (300) for operating a key device (110) comprising a digital key (111) for controlling one or more vehicle functions (103) of a vehicle (100); the method (300) comprising - receiving (301), via a communication connection (112), a notification message (201) relating to a notification situation present on the vehicle (100); - in response to receiving (302) the notification message (201), activating (302) a vehicle application (118) for controlling the one or more vehicle functions (103); and - effecting (303), based on the activated vehicle application (118), an output relating to the notification situation to a user of the key device (110).
Citation Information
Patent Citations
Arrangement and procedure for operating a remote application
DE102019203236A1
System and method for the interactive control of vehicle functions
DE102022109633A1