Vehicle reminder method, device, vehicle, storage medium and computer program

Abstract

This application relates to the field of vehicle technology, and in particular to a vehicle reminder method, device, vehicle, storage medium, and computer program. The method includes: acquiring vehicle driving information; determining the driving scenario corresponding to the driving information and acquiring the usage frequency of the voice broadcast function; determining a target reminder method based on the driving scenario and usage frequency, so that the vehicle provides reminders according to the target reminder method. This solves the problems in related technologies where vehicle voice reminder methods are limited, failing to meet the needs of different users, and resulting in a poor intelligent driving experience.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a vehicle reminder method, device, vehicle, storage medium, and computer program. Background Technology

[0002] With the development of vehicle technology, consumers are no longer solely focused on the vehicle's performance, but are increasingly emphasizing the human-vehicle interaction experience during driving. Currently, the cumbersome and differentiated activation methods of intelligent driving assistance functions create a significant learning curve for users, and the voice prompts are indistinguishable between new and experienced users. The complexity of the voice control process diminishes the user's experience with intelligent driving. Furthermore, many intelligent driving functions offer weak or indistinguishable voice prompts, leaving users uncertain whether a function is active or has been deactivated, and without timely information, they cannot execute further actions via voice. Summary of the Invention

[0003] This application provides a vehicle reminder method, device, vehicle, storage medium, and computer program to solve the problems in related technologies where the vehicle's voice reminder method is singular, cannot meet the needs of different users, and has a poor intelligent driving experience.

[0004] The first aspect of this application provides a vehicle reminder method, including the following steps: obtaining vehicle driving information; determining the driving scenario corresponding to the driving information and obtaining the usage frequency of the voice broadcast function; determining a target reminder method based on the driving scenario and usage frequency, so that the vehicle provides reminders according to the target reminder method.

[0005] Optionally, determining the driving scenario corresponding to the driving information includes: comparing the driving information with the vehicle's preset standard state; if the driving information is different from the preset standard state, then the driving scenario is determined to be a warning scenario, otherwise the driving scenario is determined to be a normal scenario; when the driving scenario is a normal scenario, if a user's voice command is received, then the driving scenario is determined to be an interactive scenario.

[0006] Optionally, the reminder method corresponding to the user's voice command is determined based on the driving scenario and usage frequency, including: if the driving scenario is an interactive scenario, the reminder method is determined to be voice broadcast; if the driving scenario is a warning scenario and the usage frequency is greater than a preset threshold, the reminder method is determined to be a prompt tone; otherwise, the reminder method is both voice broadcast and prompt tone.

[0007] Optionally, the vehicle alert method also includes: while the vehicle is alerting according to the target alert method, displaying alarm prompt information corresponding to the driving scenario on the user interface of the vehicle terminal.

[0008] Optionally, obtaining the usage frequency of the voice broadcast function includes: obtaining a user identifier; determining the user's historical usage history of the voice broadcast function based on the user identifier; and determining the usage frequency of the voice broadcast function based on the historical usage history.

[0009] A second aspect of this application provides a vehicle reminder device, comprising: an acquisition module for acquiring vehicle driving information; a determination module for determining a driving scenario corresponding to the driving information and acquiring the usage frequency of the voice broadcast function; and a reminder module for determining a target reminder method based on the driving scenario and usage frequency, so that the vehicle provides reminders according to the target reminder method.

[0010] Optionally, the determination module is further used to compare the driving information with the vehicle's preset standard state; if the driving information is different from the preset standard state, the driving scenario is determined to be a warning scenario, otherwise the driving scenario is determined to be a normal scenario; when the driving scenario is a normal scenario, if a user's voice command is received, the driving scenario is determined to be an interactive scenario.

[0011] Optionally, the reminder module is further configured to determine that the reminder method is voice broadcast if the driving scenario is an interactive scenario; and to determine that the reminder method is a prompt tone if the driving scenario is a warning scenario and the frequency of use is greater than a preset threshold; otherwise, the reminder method is both voice broadcast and prompt tone.

[0012] Optionally, the vehicle alert device further includes a display module, used to display alarm prompts corresponding to the driving scenario on the user interface of the vehicle terminal while the vehicle is alerting according to the target alert method.

[0013] Optionally, the determining module is further used to obtain a user identifier; determine the user's historical usage history of the voice broadcast function based on the user identifier; and determine the usage frequency of the voice broadcast function based on the historical usage history.

[0014] A third aspect of this application provides a vehicle, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle reminder method as described in the above embodiments.

[0015] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which is executed by a processor to implement the vehicle alerting method as described in the above embodiments.

[0016] A fifth aspect of this application provides a computer program product having a computer program or instructions stored thereon, which, when executed, implement the vehicle alerting method as described in any of the above embodiments.

[0017] Therefore, this application has at least the following beneficial effects:

[0018] This system can determine the target reminder method based on the vehicle's driving scenario and the frequency of voice broadcast usage. The diverse reminder methods not only effectively deliver information to the user but also reduce the learning curve for users learning about the vehicle's intelligent driving functions, thereby improving the user's driving experience. This solves the problems of related technologies where vehicle voice reminders are limited, failing to meet the needs of different users and resulting in a poor intelligent driving experience.

[0019] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0020] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0021] Figure 1 This is a flowchart of a vehicle alert method provided according to an embodiment of this application;

[0022] Figure 2 This is a block diagram of a vehicle reminder device provided according to an embodiment of this application;

[0023] Figure 3 This is an example diagram of a memory parking voice interaction provided according to an embodiment of this application;

[0024] Figure 4 This is a structural schematic diagram of a vehicle according to an embodiment of this application. Detailed Implementation

[0025] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0026] The vehicle reminder method, apparatus, vehicle, storage medium, and computer program according to embodiments of this application are described below with reference to the accompanying drawings. Addressing the problems mentioned in the background section, this application provides a vehicle reminder method. In this method, the target reminder method can be determined based on the vehicle's driving scenario and the frequency of use of the voice broadcast function. The reminder methods are diversified, achieving the desired information delivery effect for the user while reducing the learning cost for the user of the vehicle's intelligent driving functions, thereby improving the user's driving experience. This solves the problems in related technologies where the vehicle's voice reminder method is singular, failing to meet the needs of different users and resulting in a poor intelligent driving experience.

[0027] Specifically, Figure 1 This is a schematic flowchart illustrating a vehicle alert method provided in an embodiment of this application.

[0028] like Figure 1 As shown, the vehicle alert method includes the following steps:

[0029] In step S101, the vehicle's driving information is obtained.

[0030] In this embodiment, vehicle driving information can be collected through various devices or apparatuses built into the vehicle. Driving information may include: vehicle speed, engine speed, coolant temperature, door status, gear status, brake status, seatbelt status, accumulated mileage, total mileage, fuel consumption, steering wheel angle, etc.

[0031] In step S102, the driving scenario corresponding to the driving information is determined, and the usage frequency of the voice broadcast function is obtained.

[0032] Understandably, many current intelligent driving functions offer weak or indistinguishable voice prompts. When it's unclear whether a function is enabled or disabled, the lack of timely information prevents users from taking further action via voice. This application's embodiment addresses this issue by delivering information to the user based on current vehicle driving information and the frequency of voice prompt usage, even when the voice prompt function is disabled or its activation / deactivation is uncertain. This reduces the learning curve for users regarding the vehicle's intelligent driving functions.

[0033] In one embodiment of this application, determining the driving scenario corresponding to driving information includes: comparing the driving information with a preset standard threshold of the vehicle; if the driving information is different from the preset standard threshold, the driving scenario is determined to be a warning scenario, otherwise the driving scenario is determined to be a normal scenario; when the driving scenario is a normal scenario, if a user's voice command is received, the driving scenario is determined to be an interactive scenario.

[0034] The preset standard threshold can be set according to actual conditions, mainly divided into preset standard thresholds during vehicle movement and preset standard thresholds when the vehicle is stationary. No specific limitations are imposed.

[0035] This application embodiment compares vehicle driving information with pre-configured standard thresholds to determine the vehicle driving scenario. For example, when the vehicle is stationary or moving, this application embodiment may compare the acquired fuel level with a pre-configured fuel level standard value. If the acquired fuel level is less than the preset standard threshold value, it is determined that the vehicle is in a warning scenario; otherwise, it is determined that the vehicle is in a normal scenario. Alternatively, it may be determined directly from the vehicle driving information, such as seat belt information indicating that the vehicle is not wearing a seat belt, thereby determining the corresponding vehicle driving scenario as a warning scenario.

[0036] In one embodiment of this application, obtaining the usage frequency of the voice broadcast function includes: obtaining a user identifier; determining the user's historical usage history of the voice broadcast function based on the user identifier; and determining the usage frequency of the voice broadcast function based on the historical usage history.

[0037] In this embodiment, the user's identifier is unique, and the user's historical usage history of the voice broadcast function can be bound to the user's identifier. In actual operation, the vehicle intelligent controller can identify the user's identity and create a unique identifier for each user. When a user enters the vehicle, the vehicle intelligent controller will identify the user's identity and find the corresponding historical usage history of the voice broadcast function based on the user's identifier.

[0038] Furthermore, in this embodiment of the application, the usage frequency can be determined by the historical records of the voice broadcast function. If a user uses it frequently, it indicates that the usage frequency is high and the user is familiar with the voice broadcast function. If a user uses it infrequently or has never used it, it indicates that the usage frequency is low and the user uses the voice broadcast function less often.

[0039] As another possible implementation method, the embodiments of this application may include a selection of the level of voice broadcast in the function settings of high-end product models, which users can choose according to the actual situation, such as familiar or unfamiliar.

[0040] In step S103, the target reminder method is determined based on the driving scenario and usage frequency, so that the vehicle provides reminders according to the target reminder method.

[0041] In one embodiment of this application, determining the reminder method corresponding to the user's voice command based on the driving scenario and usage frequency includes: if the driving scenario is an interactive scenario, then determining the reminder method as voice broadcast; if the driving scenario is a warning scenario and the usage frequency is greater than a preset threshold, then determining the reminder method as a prompt tone; otherwise, the reminder method is both voice broadcast and prompt tone.

[0042] Based on the above embodiments, if the current driving scenario of the vehicle is a normal scenario and the user's voice command is received, it is necessary to transmit some information to the user. In this embodiment, regardless of whether the vehicle is stationary, driving at low speed, or driving at high speed, the user can be responded to by voice broadcast. Voice broadcast replaces the need to pay attention to the instrument function icons or central control text prompts, thereby reducing driving risks and bringing a more intelligent operating experience to the user.

[0043] In actual operation, after waking up the voice assistant and issuing voice commands related to intelligent driving, the vehicle needs to determine the execution conditions and then give the corresponding command execution and voice response. If the conditions are not met, a corresponding voice response should also be given, so that every voice command of the driver has a corresponding voice response.

[0044] 1) Here, voice commands need to be executed after the vehicle's voice assistant is woken up. On the one hand, users have varying levels of understanding of the intelligent driving function, resulting in a large number of generalized voice commands. This leads to a higher probability of false wake-up for the all-time wake-up-free system, which can easily reduce the driver's voice experience.

[0045] 2) However, in the case of continuous dialogue commands and the in-vehicle voice assistant being activated in the background, if the driver issues further continuous voice commands without activating the voice assistant, the in-vehicle system should also directly respond and execute the commands.

[0046] The following embodiment of this application will be described in detail with an example of a memory parking voice interaction. The scenario is that the vehicle is not in a parking-related interface, and the user, after waking up the vehicle's voice assistant, wants to directly create a parking route by voice command. During this process, the vehicle will provide different responses based on whether its own conditions and the environment meet the relevant requirements, such as... Figure 2 The process is shown below.

[0047] User: "I want to create a docking station"

[0048] Scenario 1: Parking settings are not enabled;

[0049] The vehicle's app replied: "Memory parking is not enabled. Please enable it in the settings."

[0050] Scenario 2: Parking settings are enabled, and vehicle collision is activated;

[0051] The vehicle responded: "A collision has occurred, I cannot perform this operation."

[0052] Scenario 3: Parking settings are enabled, vehicle collision is not activated, and the intelligent driving system malfunctions;

[0053] The vehicle responded: "The intelligent driving system is malfunctioning, and I cannot perform this operation."

[0054] Scenario 4: Parking settings are enabled, vehicle collision is not activated, intelligent driving system is normal, but associated systems are abnormal;

[0055] The vehicle responded: "The associated system is abnormal, and I cannot perform this operation."

[0056] Scenario 5: Parking settings are enabled, vehicle-side collision is not activated, intelligent driving system is normal, associated systems are normal, and other intelligent driving functions are activated;

[0057] The car's app replied: "You are already using other driver assistance features. Try turning them off."

[0058] Scenario 6: Parking settings are enabled, vehicle-side collision is not activated, intelligent driving system is normal, associated systems are normal, other intelligent driving functions are activated, and vehicle speed exceeds the range;

[0059] The vehicle responded: "The speed is too fast, try again after slowing down."

[0060] Scenario 7: Parking settings are enabled, vehicle collision is not activated, intelligent driving system is normal, associated systems are normal, other intelligent driving functions are activated, vehicle speed does not exceed the range, and the recommended route conditions are met.

[0061] The vehicle opens the route management interface (and a pop-up window prompts whether to overwrite existing routes).

[0062] Scenario 8: Parking settings are enabled, vehicle-side collision is not activated, intelligent driving system is normal, associated systems are normal, other intelligent driving functions are activated, vehicle speed is within the range, and the recommended route conditions are not met.

[0063] The vehicle-side system can be activated to learn parking routes.

[0064] As another possible implementation, this application embodiment can also classify the prompt sounds according to functional requirements, categorizing the intelligent driving function according to different prompt requirements, such as function activation, function exit, function failure, function pause, function completion, etc., and classifying the Chime prompt sounds according to different prompt requirement types. If the current driving scenario of the vehicle is a normal scenario and a user's voice command is received, it indicates that some information needs to be conveyed to the user (e.g., the function is activated). This application embodiment can obtain the prompt sound type corresponding to the function being activated and respond to the user through the prompt sound, further improving the user's driving experience.

[0065] If the current driving scenario is a warning scenario, this application embodiment can provide complete voice prompts for users who are new to the voice broadcast function; for users who are already familiar with the function and want to avoid lengthy prompts, a concise broadcast format is provided. This concise broadcast format typically only retains the prompt sound (such as a beep) for some function prompts, eliminating the need for a full voice broadcast. While providing safety reminders during driving, the diverse prompt sounds also add to the driving experience.

[0066] While the vehicle provides reminders according to the target reminder method, this embodiment of the application can display corresponding prompt information for the driving scenario on the user interface of the in-vehicle terminal.

[0067] The vehicle reminder method proposed in this application can determine the target reminder method based on the vehicle's driving scenario and the frequency of use of the voice broadcast function. This diversification of reminder methods not only achieves the desired information delivery for the user but also reduces the learning cost for the user regarding the vehicle's intelligent driving functions, thereby improving the user's driving experience. This solves the problems in related technologies where the vehicle's voice reminder method is singular, failing to meet the needs of different users and resulting in a poor intelligent driving experience.

[0068] Next, the vehicle reminder device proposed according to the embodiments of this application is described with reference to the accompanying drawings.

[0069] Figure 3 This is a block diagram of a vehicle reminder device according to an embodiment of this application.

[0070] like Figure 3 As shown, the vehicle reminder device 10 includes: an acquisition module 100, a determination module 200, and a reminder module 300.

[0071] The acquisition module 100 is used to acquire the vehicle's driving information; the determination module 200 is used to determine the driving scenario corresponding to the driving information and acquire the usage frequency of the voice broadcast function; the reminder module 300 is used to determine the target reminder method based on the driving scenario and usage frequency, so that the vehicle can remind the user according to the target reminder method.

[0072] In one embodiment of this application, the determining module 200 is further configured to compare the driving information with a preset standard threshold of the vehicle; if the driving information is different from the preset standard threshold, the driving scenario is determined to be a warning scenario, otherwise the driving scenario is determined to be a normal scenario; when the driving scenario is a normal scenario, if a user's voice command is received, the driving scenario is determined to be an interactive scenario.

[0073] In one embodiment of this application, the reminder module 300 is further configured to determine that the reminder method is voice broadcast if the driving scenario is an interactive scenario; if the driving scenario is a warning scenario and the frequency of use is greater than a preset threshold, determine that the reminder method is a prompt sound; otherwise, the reminder method is both voice broadcast and prompt sound.

[0074] In one embodiment of this application, the vehicle reminder device 10 further includes a display module, which is used to display prompt information corresponding to the driving scenario on the user interface of the vehicle terminal while the vehicle is reminding the user according to the target reminder method.

[0075] In one embodiment of this application, the determining module 200 is further configured to obtain a user identifier; determine the user's historical usage history of the voice broadcast function based on the user identifier; and determine the usage frequency of the voice broadcast function based on the historical usage history.

[0076] It should be noted that the foregoing explanation of the vehicle reminder method embodiment also applies to the vehicle reminder device of this embodiment, and will not be repeated here.

[0077] The vehicle reminder device proposed in this application can determine the target reminder method based on the vehicle's driving scenario and the frequency of use of the voice broadcast function. The diverse reminder methods not only achieve the desired information delivery for the user but also reduce the learning cost for the user regarding the vehicle's intelligent driving functions, thereby improving the user's driving experience. This solves the problems in related technologies where the vehicle's voice reminder methods are limited, failing to meet the needs of different users and resulting in a poor intelligent driving experience.

[0078] Figure 4 A schematic diagram of the structure of a vehicle provided in an embodiment of this application. The vehicle may include:

[0079] The memory 401, the processor 402, and the computer program stored on the memory 401 and capable of running on the processor 402.

[0080] When the processor 402 executes the program, it implements the vehicle reminder method provided in the above embodiments.

[0081] Furthermore, the vehicle also includes:

[0082] Communication interface 403 is used for communication between memory 401 and processor 402.

[0083] The memory 401 is used to store computer programs that can run on the processor 402.

[0084] The memory 401 may include high-speed RAM (Random Access Memory) memory, and may also include non-volatile memory, such as at least one disk storage.

[0085] If the memory 401, processor 402, and communication interface 403 are implemented independently, then the communication interface 403, memory 401, and processor 402 can be interconnected via a bus to complete communication between them. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0086] Optionally, in a specific implementation, if the memory 401, processor 402, and communication interface 403 are integrated on a single chip, then the memory 401, processor 402, and communication interface 403 can communicate with each other through an internal interface.

[0087] Processor 402 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of this application.

[0088] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the vehicle reminder method described above.

[0089] This application also provides a computer program product that stores a computer program or instructions thereon. When the computer program or instructions are executed, they implement the vehicle reminder method as described in any of the above embodiments.

[0090] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0091] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0092] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0093] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (FPGAs), field-programmable gate arrays (FPGAs), etc.

[0094] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0095] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A vehicle alert method, characterized in that, Includes the following steps: Obtain vehicle driving information; Determine the driving scenario corresponding to the driving information and obtain the usage frequency of the voice broadcast function; The target reminder method is determined based on the driving scenario and the usage frequency, so that the vehicle reminds the user according to the target reminder method; The step of determining the driving scenario corresponding to the driving information includes: comparing the driving information with the vehicle's preset standard state; if the driving information is different from the preset standard state, then the driving scenario is determined to be a warning scenario, otherwise the driving scenario is determined to be a normal scenario; when the driving scenario is a normal scenario, if a user's voice command is received, then the driving scenario is determined to be an interactive scenario. The step of determining the reminder method corresponding to the user's voice command based on the driving scenario and the usage frequency includes: if the driving scenario is an interactive scenario, then the reminder method is determined to be a voice broadcast; if the driving scenario is a warning scenario and the usage frequency is greater than a preset threshold, then the reminder method is determined to be a prompt tone; otherwise, the reminder method is a combination of voice broadcast and prompt tone.

2. The vehicle reminder method according to claim 1, characterized in that, Also includes: While the vehicle is issuing the warning according to the target reminder method, the corresponding alarm prompt information for the driving scenario is displayed on the user interface of the vehicle terminal.

3. The vehicle reminder method according to claim 1, characterized in that, The frequency of use of the voice broadcast function is obtained, including: Obtain user identifier; Based on the user identifier, determine the user's historical usage history of the voice broadcast function; The frequency of use of the voice broadcast function is determined based on the historical records.

4. A vehicle warning device, characterized in that, include: The acquisition module is used to acquire the vehicle's driving information; The determination module is used to determine the driving scenario corresponding to the driving information and to obtain the usage frequency of the voice broadcast function; The reminder module is used to determine the target reminder method based on the driving scenario and the usage frequency, so that the vehicle can provide reminders according to the target reminder method; The determining module is further configured to: compare the driving information with the preset standard state of the vehicle; if the driving information is different from the preset standard state, determine that the driving scenario is a warning scenario, otherwise determine that the driving scenario is a normal scenario; when the driving scenario is a normal scenario, if a user's voice command is received, determine that the driving scenario is an interactive scenario. The reminder module is further configured to: if the driving scenario is an interactive scenario, determine that the reminder method is voice broadcast; if the driving scenario is a warning scenario and the usage frequency is greater than a preset threshold, determine that the reminder method is a prompt sound; otherwise, the reminder method is both voice broadcast and prompt sound.

5. A vehicle, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the vehicle alerting method as described in any one of claims 1-3.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the vehicle alert method as described in any one of claims 1-3.

7. A computer program product having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they implement the vehicle alert method according to any one of claims 1-3.

Images