Method for controlling communication between a vehicle and a back-end device

Abstract

The present invention relates to a method for controlling communication (D) between a vehicle (10) and a back-end device (20) in a vehicle-to-cloud system (100), comprising the following steps: 1) sending a message (m) from the vehicle (10) to the back-end device (20), 2) setting a timer (t) for receiving an acknowledgment (a) from the back-end device (20) at the vehicle (10) that the message (m) is successfully received, and 3) when the acknowledgment (a) from the back-end device (20) is not received at the vehicle (10) or the acknowledgment (a) from the back-end device (20) does not correspond to the message (m) sent in step 1), wherein method step 2) and method step 3) have different schedules (S) according to different settings (A).

Description

Technical Field

[0001] Embodiments of the present invention relate to a method for controlling communication between a vehicle and backend devices in a vehicle-to-cloud system, particularly from the vehicle side of the system. Furthermore, embodiments of the present invention relate to an electronic control unit. Furthermore, embodiments of the present invention relate to a vehicle including a corresponding electronic control unit. Furthermore, embodiments of the present invention relate to a computer program product for use in a corresponding method. Background Art

[0002] Vehicle-to-cloud systems are generally known, for example from patent document DE 10 2015 200422 A1. Electronic control units in vehicles typically have computing units. However, the processing power and storage capacity of these computing units are often limited. Furthermore, access to programming updates or other data can sometimes be complex. Cloud computers, on the other hand, typically offer high computing power, large storage capacities, and easy access to updates and other data. Vehicle-to-cloud systems are used to provide cloud computing applications to enhance vehicle functionality, increasing safety, intelligence, environmental friendliness, and user-friendliness while increasing comfort and pleasant operation. To this end, the electronic control unit can send requests for certain (or specific) applications to be provided in the cloud. Furthermore, modern vehicle-to-cloud systems can provide synchronization between the electronic control unit and the cloud. However, known systems do not consider or provide sufficient flexibility to handle situations where, for example, communication between the vehicle and the cloud is not feasible and / or permitted. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a method for controlling the communication between a vehicle and a back-end device in a vehicle-to-cloud system, especially from the vehicle side of the system, which method has improved and flexible functionality. In particular, a method for controlling the communication between a vehicle and a back-end device in a vehicle-to-cloud system is provided, which method can ensure that messages from the vehicle to the back-end device in the cloud are received, and can provide a flexible retry mechanism for messages that are not received by the back-end device in the cloud. The purpose of the present invention is also to provide a corresponding electronic control unit for a vehicle, a corresponding vehicle, and a related computer program product for the method of the present invention.

[0004] According to a first aspect, the present invention provides a method for controlling the communication between a vehicle and a backend device in a vehicle-to-cloud system, in particular from the vehicle side of the system. According to a second aspect, the present invention provides an electronic control unit. According to a third aspect, the present invention provides a vehicle comprising a corresponding electronic control unit. Furthermore, one aspect of the present invention is a corresponding vehicle-to-cloud system. According to a fourth aspect, the present invention provides a computer program product for a corresponding method. The details and features disclosed in the individual aspects of the present invention also apply to the other aspects of the present invention, and vice versa.

[0005] According to a first aspect, the present invention provides a method for controlling (preferably wireless) communication between a vehicle and backend devices (on the cloud side of the system) in a vehicle-to-cloud system (via a network, such as a mobile phone network), in particular from the vehicle side of the system, preferably using a publish-subscribe environment, such as the MQTT protocol, the method comprising:

[0006] 1) Send messages from the vehicle to the backend device,

[0007] 2) setting a timer for receiving an acknowledgment from the backend device at the vehicle that the message has been successfully received,

[0008] 3) When the vehicle does not receive an acknowledgment from the backend device or the acknowledgment from the backend device does not correspond to the message sent in step 1), the message is resent from the vehicle to the backend device.

[0009] Method step 2) and method step 3) may have different schedules depending on different settings, in particular targeted settings and / or settings determined intentionally, preferably manually and / or automatically.

[0010] The method can be performed in the order given or in a modified order. In some embodiments, the steps of the method according to the present invention can be performed simultaneously and / or repeatedly to achieve a process.

[0011] The different settings may for example be stored in a memory, preferably a volatile memory, of the electronic control unit of the vehicle. The different settings may preferably be set, for example manually by a user of the vehicle and / or automatically by the electronic control unit of the vehicle.

[0012] A backend device in the sense of the present invention is a computer or a group of computers that provides high computing power, large storage capacity and easy access to updates and other data available for the vehicle. A backend device in the sense of the present invention is representative of the cloud.

[0013] The message from the vehicle to the backend device in step 1) can be associated with an application (or application program) in the vehicle and include a unique identifier, a so-called ID. The application in the vehicle can include safety, intelligence, environment and user settings, comfort and / or entertainment operations.

[0014] The timer set in step 2) is used to set the time to wait for receiving the confirmation that the message was successfully received from the back-end device at the vehicle. If the vehicle does not receive the confirmation within the time period defined by the timer, or if the confirmation has an incorrect ID, a retry mechanism is provided in step 3). The timer determines the time to wait for the confirmation from the back-end device. The confirmation can also be referred to as a confirmation of receipt. The confirmation can also include calculation results and / or other information (if requested in the message, including release received, release released or release completed, etc. for some applications).

[0015] In step 3), the following messages will be resent for which no acknowledgement was received from the cloud or no acknowledgement was received with a matching ID.

[0016] In the sense of the present invention, a schedule may also be referred to as a plan. The schedule may include any details about the workflow of the method steps, such as the duration of the steps, the number of discrete items within the steps, the number of repetitions of the steps, etc.

[0017] The inventive concept is to provide flexible confirmation schedules and / or adaptive retry mechanisms for different settings (hereinafter referred to as settings). This may, for example, involve sending a message with a certain ID (including updates and / or data for certain applications) to the cloud and waiting for an acknowledgement message with the same ID. If the ID is different or no acknowledgement message is received, the last known version of the message is resent. As long as the user accepts synchronization with the cloud, this mechanism can have unlimited retries even in poor connectivity. In this case, the setting can be a low level of privacy, where the electronic control unit is online. However, if the user requests not to share information and not synchronize with the cloud, this mechanism can be adjusted. For example, after a 30-second timer of inactivity in step 2), the vehicle can only retry once, for example, in step 3). Thereafter, the vehicle's communication unit can be turned off, thereby turning the electronic control unit offline. These settings can be selected by the vehicle user. Alternatively, settings can be provided automatically, for example, based on the vehicle's current location, the user's calendar data, the vehicle's surroundings, and so on. In this case, the user can be provided with the option to confirm and / or adjust the settings.

[0018] After carrying out the method according to different, in particular targeted and / or intentionally determined settings, the communication unit of the vehicle can be switched off, ie the electronic control unit of the vehicle can be switched offline. Applications associated with the message can also be stopped.

[0019] Thus, due to the flexible acknowledgement scheme and / or the flexible retry mechanism according to the invention, the privacy settings of the user, the environment of the vehicle and / or the authorization level of the user can be taken into account in a better way.

[0020] According to the present invention, the various settings include privacy settings. This allows the user's privacy preferences to be advantageously taken into account, in particular through communication and / or synchronization with the cloud. This allows user data to be handled confidentially.

[0021] In some embodiments, the different settings, in particular privacy settings, include at least one of the following privacy levels:

[0022] a low level of privacy, wherein at the low level of privacy the communication unit of the vehicle for communicating with the back-end device is turned on (ie the electronic control unit of the vehicle is online),

[0023] - a reduced level of privacy,

[0024] - an increased level of privacy, and / or

[0025] A high level of privacy, wherein at the high level of privacy the communication unit of the vehicle for communicating with back-end devices is switched off (ie the electronic control unit of the vehicle is offline).

[0026] In this way, a flexible consideration of different privacy levels can be achieved.

[0027] In some embodiments, the different settings are determined manually by the user of the vehicle, in particular by operating an input device of the vehicle, preferably a display device on the vehicle dashboard, so that the user's preferences can be directly taken into account.

[0028] In some embodiments, the different settings are automatically determined by the electronic control unit of the vehicle, taking into account, inter alia, the current location of the vehicle, the user's calendar data, the user's authorization level (e.g., authorization by a shared vehicle), the vehicle's environment (e.g., airport area, highway, city, etc.), etc. Thus, environmental factors and / or authorization factors can be advantageously taken into account by communicating with a backend device (i.e., the cloud).

[0029] In some embodiments, the vehicle user is provided with the possibility to confirm and / or adjust the automatically determined settings, in particular by operating an input device of the vehicle, such as a display device on the vehicle dashboard. Thus, the user can be provided with the ability to check and review the different settings automatically determined by the electronic control unit.

[0030] In some embodiments, during or before step 1), a verification is performed if transmission is permitted according to various settings, and / or during or before step 1), a verification is performed if transmission is possible, wherein, in particular, a communication test is performed on the backend device. Thus, various, particularly purposeful and / or intentionally determined settings can be considered in a safe and reliable manner.

[0031] In some embodiments, the timer in step 2) has different durations according to different settings. Therefore, different settings can affect how long the vehicle waits for the confirmation of the message in step 2).

[0032] The duration of the timer in step 2) can depend on the privacy level of the different settings. In this way, the privacy level can be taken into account in a corresponding manner in step 2). In addition, it is conceivable that the duration of the timer in step 2) decreases as the privacy level of the different settings increases. In this way, privacy preferences can be quickly taken into account. For example, the duration of the timer according to the high level of privacy of the different settings can be 0.1 seconds to 1 minute, in particular 1 second to 30 seconds, preferably 30 seconds, and / or the duration of the timer according to the low level of privacy of the different settings can be 1 minute to 10 minutes, in particular 1 minute to 5 minutes, preferably 5 minutes.

[0033] In some embodiments, the resending of the message in step 3) has different attempts according to different settings. Therefore, different settings can affect the frequency with which the vehicle retries to resend the message in step 3).

[0034] Most importantly, the number of attempts can depend on the privacy level of the different settings. In this way, the privacy level can be taken into account in a corresponding manner in step 3). In addition, it is conceivable that the number of attempts can increase as the privacy level of the different settings increases. Therefore, when the user's preference is to remain "offline", more attempts to resend the message can be made quickly in order to ensure that the cloud receives the information it needs and that the electronic control unit can be switched offline relatively quickly. In other words, only one attempt to resend the message should be as successful as possible before the electronic control unit will be switched offline. For example, the number of attempts according to the high level of privacy of the different settings can be 2 to 10 times, in particular 4 to 8 times, preferably 6 times, and / or the number of attempts according to the low level of privacy of the different settings can be 1 to 10 times, in particular 2 to 8 times, preferably 4 times.

[0035] In some embodiments, a certain number of repetitions may be performed depending on the applicable settings. In this case, the number of repetitions may depend on the privacy level of the settings. In particular, the number of repetitions may decrease as the privacy level of the settings increases. For example, the number of repetitions for a high level of privacy in the settings may include only one repetition. The number of repetitions for a low level of privacy in the settings may include at least one repetition or any necessary number of repetitions as needed.

[0036] According to a second aspect, embodiments of the present invention provide an electronic control unit comprising: a memory storing program code; and a computing unit, wherein, when the computing unit executes the program code, the method described above is implemented. The electronic control unit can achieve the same advantages as those achieved with the method described above. These advantages are fully incorporated herein by reference.

[0037] According to a third aspect, embodiments of the present invention provide a vehicle comprising a corresponding electronic control unit. The vehicle of the present invention can achieve the same advantages as those achieved with the method described above. Reference is made in full to these advantages in the present case.

[0038] The embodiments of the present invention may be directed to corresponding transportation tools and cloud systems.

[0039] According to a fourth aspect, embodiments of the present invention provide a computer program product comprising program code for implementing the above-described method. The computer program product comprises instructions that, when executed by a computer, cause the computer to implement the above-described method. The computer program product can achieve the same advantages as achieved with the above-described method. These advantages are incorporated herein by reference. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The present invention and its further developments and advantages will be explained in more detail below using the accompanying drawings. These drawings schematically show:

[0041] Figure 1 A schematic diagram of a vehicle-to-cloud system design according to an embodiment of the present invention is shown and

[0042] Figure 2 A schematic flow chart showing a method according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0043] Figure 1 A vehicle-to-cloud system 100 is shown. The vehicle-to-cloud system 100 includes at least one vehicle 10 and a backend device 20 in the cloud. The vehicle 10 may include an electronic control unit (ECU). To increase the functionality of the vehicle 10, the backend device 20 may provide one or more of high computing power, large storage capacity, and easy access to updates and other data. Thus, cloud computing applications may enhance the functionality of the vehicle, such as for greater safety, intelligence, environmental and customer-friendly and comfortable operation, and enjoyable operation. To this end, the electronic control unit (ECU) may send one or more requests for certain applications to be provided by the backend device 20. In addition, synchronization may be provided between the electronic control unit (ECU) and the backend device 20.

[0044] Figure 2 To explain the Figure 1 Schematically shown in FIG is a method for controlling the communication D between the vehicle 10 and the backend device 20 in the vehicle-to-cloud system 100, in particular from the vehicle side of the system 100. The method comprises the following steps:

[0045] 1) Sending a message m from the vehicle 10 to the backend device 20, wherein the message can be described by an identification ID and can be related to an application in the vehicle 10,

[0046] 2) Setting a timer t for receiving an acknowledgment a of successful receipt of the message m from the backend device 20 at the vehicle 10, e.g., the timer t sets a maximum time period for waiting for the acknowledgment to be received,

[0047] 3) When the vehicle 10 does not receive the confirmation a from the backend device 20 at the time set by the timer t or within the time period set by the timer t, or when the confirmation a is received from the backend device 20 at the time set by the timer t or within the time period set by the timer t but the confirmation has an incorrect identification ID, the message m is resent from the vehicle 10 to the backend device 20,

[0048] Method step 2) and method step 3) have different schedules S depending on different settings, in particular targeted settings and / or settings A determined intentionally, preferably manually and / or automatically.

[0049] The different settings A may be stored, for example, in a memory m of an electronic control unit (ECU) of the vehicle 10. The memory m may be a volatile memory m1. The different settings A may be set by a user of the vehicle 10, for example manually, and / or automatically by the electronic control unit (ECU) of the vehicle 10.

[0050] The backend device 20 may include at least one computer or a group of multiple computers in the cloud.

[0051] Applications provided by the backend devices 20 for the vehicle 10 may include safety, intelligence, environmental and customer settings, comfort, and / or entertainment operations.

[0052] The timer t (wait time) set in step 2) is used to determine the time or time period for receiving an acknowledgment a from the backend device 20 at the vehicle 10 indicating that the message m has been successfully received. If the vehicle does not receive the acknowledgment a by the time set by the timer or within the time period set by the timer, or if the acknowledgment received by the time set by the timer or within the time period set by the timer has an incorrect identification ID, a retry mechanism is provided in step 3) to resend the message m. The acknowledgment a may also include a confirmation of receipt of the message m and / or, if requested in the message m, include calculation results for the application.

[0053] In step 3), according to a special retransmission mechanism, the following message m, for which no acknowledgement a or no acknowledgement with a matching ID is received from the backend device 20, will be retransmitted according to the determined setting A.

[0054] The schedule S may include any details about the workflow of method steps 2) and 3), such as the duration of the timer t, the number n of attempts to resend the message m and / or the number r of repetitions of steps 2) and 3).

[0055] The present invention provides a flexible acknowledgment schedule in step 2) and / or an adaptable retry mechanism for different settings A in step 3). In step 1), a message m with a specific ID containing updates and / or data related to certain applications may be sent to the cloud. In step 2), the vehicle 10, specifically the electronic control unit (ECU) of the vehicle 10, may wait for an acknowledgment a with the same ID. If the ID is different or no acknowledgment a is received, the last known version of message m is resent in step 3).

[0056] After carrying out the method according to various settings A, in particular purposeful and / or intentionally determined settings, the communication unit 11 of the vehicle 10 can be switched off, ie the vehicle's electronic control unit ecu can be switched offline. Subsequently, the relevant applications can be stopped.

[0057] like Figure 2 As shown, the different settings A may include a privacy setting P. In other words, the different settings A may include at least one of the following privacy levels Ai:

[0058] A low level of privacy A1 , wherein at the low level of privacy A1 , the communication unit 11 of the vehicle 10 for communicating D with the back-end device 20 is turned on, ie the electronic control unit ecu of the vehicle 10 is online,

[0059] - a reduced privacy level A2, where, for example, some confidential data is not allowed to be shared with the backend device 20,

[0060] - an elevated level of privacy A3, where, for example, some confidential data and / or some user data are not allowed to be shared with the backend device 20, and / or

[0061] A high level of privacy A4 , wherein at the high level of privacy A4 the communication unit 11 of the vehicle 10 for communicating D with the backend device 20 is switched off, ie the electronic control unit of the vehicle is offline.

[0062] The different settings A can be determined, for example manually, by a user of the vehicle 10. For this purpose, an input device 14 of the vehicle 10, preferably a display device on the vehicle dashboard 12, can be provided.

[0063] It is also possible for the electronic control unit (ECU) of the vehicle 10 to automatically determine the different settings A. In this case, the ECU can, for example, take into account one or more parameters selected from the current location of the vehicle 10, user calendar data, user authorization level (e.g., authorized by a shared vehicle 10), and the environment of the vehicle 10 (e.g., airport area, highway, city, etc.). Of course, the ECU can also take other useful information into account for this purpose. In addition, the user of the vehicle 10 can be provided with the possibility to confirm and / or adjust the automatically determined settings A, for example, by operating an input device 14 of the vehicle 10, such as a display device on the vehicle dashboard 12.

[0064] like Figure 2As shown, during or before step 1), if sending is allowed according to different settings A, verification 1a) can be performed. In addition, during or before step 1), if sending is possible, verification 1b) can be performed, wherein in particular a communication test can be performed on the backend device 20.

[0065] like Figure 2 As shown schematically, the timer t in step 2) may have different durations t1, t2, t3, and t4 for different settings A. Preferably, the durations t1, t2, t3, and t4 of the timer t in step 2) may depend on the privacy level Ai of the different settings A. For example, the durations t1, t2, t3, and t4 of the timer t in step 2) may decrease as the privacy level Ai of the different settings A increases. In particular, the duration t4 of the timer t according to the high privacy level A4 of the different settings A may be 30 seconds, whereas the duration t1 of the timer t according to the low privacy level A1 of the different settings A may be 5 minutes.

[0066] like Figure 2 As further shown, in step 3), the maximum number of attempts n1, n2, n3, and n4 for resending the message m varies depending on the different settings A. The number of attempts n may preferably depend on the privacy level Ai of the different settings A. For example, the number of attempts n may increase as the privacy level Ai of the different settings A increases. In particular, the number of attempts n4 for a high privacy level A4 of the different settings A may be 6, whereas the number of attempts n1 for a low privacy level A1 of the different settings A may be 4.

[0067] In addition, for greater simplicity, the number of attempts n for different settings A can be set to be the same.

[0068] like Figure 2 As further shown, step 1a) and / or step 1b), step 2) and step 3) may be repeated a certain number of times r according to the different settings A. In this case, the number of times r of repetitions of step 1a) and / or step 1b), step 2) and step 3) may depend on the privacy level Ai of the different settings A. In particular, the number of times r of repetitions of step 1a) and / or step 1b), step 2) and step 3) may decrease as the privacy level Ai of the different settings A increases. For example, the number of times r4 of repetitions according to a high level A4 of privacy of the different settings A may include only one repetition of step 1a) and / or step 1b), step 2) and step 3), wherein the number of times r1 of repetitions according to a low level A1 of privacy of the different settings A may include any necessary number of times r of repetitions of step 1a) and / or step 1b), step 2) and step 3).

[0069] The electronic control unit ecu comprises a memory m and a computing unit c, wherein a program code is stored in the memory, wherein when the program code is executed by the computing unit c, the method as described above can be implemented, for example, referring to Figure 2 In other words, the electronic control unit ecu may be configured to perform the method as described above.

[0070] The vehicle 10 may include the electronic control unit ecu described above.

[0071] The above methods, such as Figure 2 The embodiments described in the foregoing may be implemented by a computer program product. That is, the computer program product may include instructions that, when executed by a computer, cause the computer to implement the embodiments of the above method.

[0072] The above description of the drawings only describes the present invention within the scope of the exemplary embodiments. Of course, the individual features of these embodiments can be combined with one another as long as it is technically reasonable without departing from the scope of the present invention.

[0073] Reference Signs List

[0074] 100 vehicles to cloud system

[0075] 10. Transportation

[0076] 11 Communication Unit

[0077] 12. Vehicle dashboard

[0078] 14 Input devices

[0079] 20 backend

[0080] ASettings

[0081] Ai Privacy Level

[0082] A1 Low Level

[0083] A2 downgrade

[0084] A3 Upgrade

[0085] A4 High Level

[0086] Privacy Settings

[0087] Plan S

[0088] m-message

[0089] aConfirmation

[0090] ID application identifier

[0091] ecu electronic control unit

[0092] c computing unit

[0093] m-memory

[0094] m1 volatile memory

[0095] tTimer

[0096] t1 duration of the low-level timer according to privacy

[0097] t2 Duration of the timer according to the privacy reduction level

[0098] t3 Duration of the timer according to the privacy level increase

[0099] t4 duration of the timer according to the high level of privacy

[0100] n attempts

[0101] n1 is the number of attempts based on the low level of privacy

[0102] n2 The number of attempts to reduce the privacy level

[0103] n3 The number of attempts based on the privacy level

[0104] n4 Number of attempts based on high level of privacy

[0105] Number of repetitions

[0106] r1 is the number of repetitions based on the low level of privacy

[0107] r2 The number of repetitions according to the reduced level of privacy

[0108] r3 The number of repetitions according to the increasing level of privacy

[0109] r4 The number of repetitions based on the highest level of privacy

Claims

1. A method for controlling communication (D) between a vehicle (10) and a backend device (20) in a vehicle-to-cloud system (100), the method comprising: 1) Sending a message (m) from the vehicle (10) to the backend device (20), 2) setting a timer (t) for receiving an acknowledgement (a) from the backend device (20) at the vehicle (10) that the message (m) has been successfully received, 3) when the vehicle (10) does not receive the confirmation (a) from the back-end device (20) or the confirmation (a) from the back-end device (20) does not correspond to the message (m) sent in step 1), the message (m) is resent from the vehicle (10) to the back-end device (20), Method step 2) and method step 3) have different schedules (S) according to different settings (A). And wherein the different settings (A) include privacy settings (P).

2. The method according to claim 1, characterized in that The different settings (A) include at least one of the following privacy levels (Ai): a low level of privacy (A1), wherein, at the low level of privacy (A1), a communication unit (11) of the vehicle (10) for communicating (D) with a back-end device (20) is switched on; - Reduced level of privacy (A2); - an increased level of privacy (A3); and / or A high level of privacy (A4), wherein at the high level of privacy (A4), the communication unit (11) of the vehicle (10) for communicating (D) with the backend device (20) is switched off.

3. The method according to claim 2, characterized in that The privacy settings (P) include at least one of the following privacy levels (Ai): a low level of privacy (A1), wherein, at the low level of privacy (A1), a communication unit (11) of the vehicle (10) for communicating (D) with a back-end device (20) is switched on; - Reduced level of privacy (A2); - an increased level of privacy (A3); and / or A high level of privacy (A4), wherein at the high level of privacy (A4), the communication unit (11) of the vehicle (10) for communicating (D) with the backend device (20) is switched off.

4. The method according to claim 1, wherein The different settings (A) are determined by a user of the vehicle (10).

5. The method according to claim 4, characterized in that The determination is performed by operating an input device (14) of the vehicle (10).

6. The method according to claim 1, characterized in that The different settings (A) are automatically determined by an electronic control unit (ecu) of the vehicle (10).

7. The method according to claim 6, characterized in that A user of the vehicle (10) is provided with a possibility to confirm and / or adjust the automatically determined settings (A).

8. The method according to claim 7, characterized in that The providing is performed by operating an input device (14) of the vehicle (10).

9. The method according to claim 5 or 8, characterized in that The input device is a display device at a vehicle dashboard (12).

10. The method according to claim 1, characterized in that During or before the sending of the message (m), if the sending is allowed according to the different settings (A), a verification (1a) is performed, and / or during or before sending of the message (m), if sending is possible, performing verification (1b).

11. The method according to claim 10, characterized in that Verification (1b) when transmission is possible includes performing a communication test on the back-end device (20).

12. The method according to claim 1, characterized in that The timer (t) has different durations (t1, t2, t3, t4) according to the different settings (A).

13. The method according to claim 12, characterized in that The duration (t1, t2, t3, t4) of the timer (t) depends on the privacy level (Ai) of the different settings (A), and / or the duration (t1, t2, t3, t4) of the timer (t) decreases as the privacy level (Ai) of the different settings (A) increases, and / or the duration (t4) of the timer (t) of the high level (A4) of privacy according to the different settings (A) is 0.1 seconds to 1 minute, And / or the duration (t1) of the timer (t) of the low level (A1) of privacy according to the different settings (A) is 1 minute to 10 minutes.

14. The method according to claim 13, characterized in that The duration (t4) of the timer (t) of the high level (A4) of privacy according to the different settings (A) is 1 second to 30 seconds.

15. The method according to claim 14, characterized in that The duration (t4) of the timer (t) for the high level (A4) of privacy according to the different settings (A) is 30 seconds.

16. The method according to claim 13, characterized in that The duration (t1) of the timer (t) of the low level (A1) of privacy according to the different settings (A) is 1 minute to 5 minutes.

17. The method according to claim 16, characterized in that The duration (t1) of the timer (t) of the low level (A1) of privacy according to the different setting (A) is 5 minutes.

18. The method according to claim 1, wherein According to the different settings (A), the retransmission of the message (m) has different numbers of attempts (n1, n2, n3, n4).

19. The method according to claim 18, characterized in that The number of attempts (n) depends on the privacy level (Ai) of the different settings (A), and / or the number of attempts (n) increases with the increase of the privacy level (Ai) of the different settings (A), and / or the number of attempts (n4) of the high level (A4) of privacy according to the different settings (A) is 2 to 10, And / or the number of attempts (n1) of the low level (A1) of privacy according to the different settings (A) is 1 to 10.

20. The method according to claim 19, characterized in that The number of attempts (n4) of the high level (A4) of privacy according to the different settings (A) is 4 to 8.

21. The method according to claim 20, characterized in that The number of attempts (n4) for the high level (A4) of privacy according to the different setting (A) is 6.

22. The method according to claim 19, wherein The number of attempts (n1) of the low level (A1) of privacy according to the different settings (A) is 2 to 8.

23. The method according to claim 22, characterized in that The number of attempts (n1) for the low level (A1) of privacy according to the different settings (A) is 4.

24. The method according to claim 1, characterized in that Step 2) and step 3) are repeated a certain number of times (r) according to the different settings (A).

25. The method according to claim 24, characterized in that The number of repetitions (r) of step 2) and / or step 3) depends on the privacy level (Ai) of the different settings (A), and / or the number of repetitions (r) of step 2) and / or step 3) decreases as the privacy level (Ai) of the different settings (A) increases, and / or the number of repetitions (r4) of the high level of privacy (A4) according to said different settings (A) comprises only one repetition of steps 2) and 3), and / or the number of repetitions (r1) of the low level of privacy (A1) according to the different settings (A) includes at least one repetition of step 2) and step 3).

26. An electronic control unit (ECU), comprising: a memory (m), wherein program code is stored in the memory; and A computing unit (c), wherein, when the program code is executed by the computing unit (c), the method according to any one of the preceding claims is carried out.

27. A vehicle (10) comprising an electronic control unit (ecu) according to claim 26.

28. A computer program product comprising instructions which, when the program is executed by a computer, cause the computer to carry out the method according to any one of claims 1 to 25.

Images