Vehicle information output control method and vehicle

Abstract

The application provides a vehicle information output control method and a vehicle, and relates to the technical field of intelligent driving. The method comprises the following steps: obtaining vehicle running information during vehicle running; determining at least one corresponding event according to the vehicle running information; processing the at least one event based on a preset rule to obtain a target output event; the preset rule comprises an event mutual exclusion rule and / or an event redundancy rule; the event mutual exclusion rule is used for retaining at most one event among events having a mutual exclusion relationship; the event redundancy rule is used for filtering out redundant events in the at least one event; and corresponding prompt information is output based on the target output event. According to the embodiment, only one event is retained among events having a mutual exclusion relationship, and / or redundant events in the at least one event are removed, so that the accuracy of information output is improved, a user can clearly and accurately know the change condition during vehicle running, the user experience is improved, and driving safety is ensured.

Description

Technical Field

[0001] This application relates to the field of intelligent driving technology, and in particular to a vehicle information output control method and a vehicle. Background Technology

[0002] With the continuous development of intelligent driving technology, the level of intelligence in vehicle information output control is increasing. Taking parking function as an example, Home Area Valet Parking (HAVP) has become a core parking assistance function of intelligent vehicles. It can automatically cruise, turn, change routes and park at the destination by memorizing the route within the parking lot, greatly improving the convenience of parking for users.

[0003] During the operation of the HAVP function, it is necessary to provide users with real-time feedback on events such as changes in vehicle status and scene transitions to ensure that users are aware of the vehicle's operating status in real time and to ensure parking safety.

[0004] However, when multiple events are triggered simultaneously during vehicle operation, users may not be able to accurately perceive the vehicle's operating status, affecting the user experience. Summary of the Invention

[0005] This application provides a vehicle information output control method and a vehicle to solve the problem in related technologies where, when multiple events are triggered simultaneously during vehicle operation, users cannot accurately perceive the vehicle's operating status, thus affecting user experience.

[0006] In a first aspect, embodiments of this application provide a vehicle information output control method, including: During vehicle operation, acquire vehicle operation information; Based on the vehicle operation information, determine at least one corresponding event; Based on preset rules, at least one event is processed to obtain the target output event; the preset rules include event mutual exclusion rules and / or event redundancy rules; the event mutual exclusion rules are used to retain at most one event among events that have a mutual exclusion relationship; the event redundancy rules are used to filter out redundant events in at least one event. Based on the target output event, output the corresponding prompt message.

[0007] Based on the above technical content, this application embodiment obtains vehicle operation information and determines at least one triggered event based on the vehicle operation information. On this basis, the at least one event is processed according to preset rules to obtain a target output event. The preset rules include event mutual exclusion rules and / or event redundancy rules. If at least one event is processed based on event mutual exclusion rules, since the event mutual exclusion rules are used to retain at most one event among mutually exclusive events, multiple mutually exclusive events will not be simultaneously determined as the target output event, thereby avoiding the simultaneous output of conflicting prompts and preventing users from experiencing cognitive confusion due to receiving multiple conflicting prompts. This allows users to accurately perceive the current state of the vehicle, improving the user experience. If redundant events are filtered out from at least one event using event redundancy rules to obtain the target output event, since redundant events are filtered out, the same prompts will not be repeatedly output when the same event is triggered multiple times in a short period of time. This protects users from continuous interference from redundant event prompts. Simultaneously, because redundant events are effectively filtered, newly triggered key events will not be overwhelmed by duplicate information, allowing users to promptly perceive changes in the vehicle's state, which helps ensure the accuracy of the user's perception of the vehicle's current state. If at least one event is processed based on both event mutual exclusion rules and event redundancy rules, the final output target event will be neither conflicting nor redundant. Users can not only clearly and accurately know the changes in the vehicle's operation, but also avoid the continuous interference of redundant event prompts, thus improving the accuracy of information output and user experience, and ensuring driving safety.

[0008] In one possible implementation, the preset rules include event mutual exclusion rules and event redundancy rules; Based on preset rules, at least one event is processed to obtain the target output event, including: Based on the event mutual exclusion rule, at least one event is mutually excluded to obtain candidate output events; mutual exclusion filtering is a filtering operation used to retain at most one event from events that have a mutual exclusion relationship. Based on the event redundancy rule, redundant events in the candidate output events are filtered out, and the remaining events after filtering are determined as the target output events.

[0009] In this embodiment of the application, the dual filtering mechanism of mutual exclusion filtering and redundancy filtering ensures that the final output target event is neither conflicting nor redundant. Users can not only avoid receiving multiple conflicting prompts and causing cognitive confusion, but also clearly and accurately understand the changes in the vehicle operation process. At the same time, they can also avoid being continuously interfered with by redundant event prompts, further improving the accuracy of information output and user experience, and ensuring driving safety.

[0010] In one possible implementation, based on an event mutual exclusion rule, at least one event is mutually excluded to obtain candidate output events, including: If at least one event includes multiple events, then based on the event mutual exclusion rule, determine whether there is a mutual exclusion relationship between the multiple events; If there is no mutual exclusion relationship between multiple events, then each event is treated as a candidate output event; If there is a mutual exclusion relationship between multiple events, then select one event to be retained from the mutually exclusive events, and use the retained event and the events that are not mutually exclusive as candidate output events.

[0011] In this embodiment, when there is no mutual exclusion relationship between multiple events, each event is treated as a candidate output event to avoid omitting the output of prompts for valid events. When there is a mutual exclusion relationship between multiple events, one event is selected from the mutually exclusive events to be retained. This effectively avoids the problem of user confusion caused by outputting prompts for multiple mutually exclusive events, and helps ensure that users accurately understand the current state of the vehicle.

[0012] In one possible implementation, a reserved event is determined from events that are mutually exclusive, including: Based on preset event priority rules, determine the priority of events that have a mutual exclusion relationship; Based on the priority of events with mutual exclusion relationships, the event with the highest priority is determined from the mutually exclusive events and reserved as the event.

[0013] Here, among mutually exclusive events, the event with the highest priority is reserved based on the priority of each event, ensuring that critical and urgent prompts can be delivered to the user, thus improving driving safety.

[0014] In one possible implementation, after outputting the corresponding prompt message based on the target output event, the following is also included: If an event switch is detected, determine whether there is a mutual exclusion relationship between the event before the switch and the event after the switch; If there is a mutual exclusion relationship between the event before and the event after the switch, the output of the prompt message corresponding to the event before the switch is interrupted, and the event after the switch is determined to be the target output event according to the preset event redundancy rule. If the event after the switch is the target output event, the prompt message corresponding to the event after the switch is output. If the events before and after the switch are not mutually exclusive, the prompt information corresponding to the event after the switch is output after the prompt information corresponding to the event before the switch is output and after a first preset time interval has elapsed.

[0015] Specifically, when an event switch is detected, if there is a mutual exclusion relationship between the event before and after the switch, the output of the prompt information for the event before the switch is immediately interrupted. Redundancy filtering is performed on the event after the switch, and the corresponding prompt information is output first. This ensures that the user can obtain the latest information and understand the vehicle's current status in a timely manner when the vehicle's state changes abruptly. If there is no mutual exclusion relationship between the event before and after the switch, the prompt information for the event after the switch is output, after a first preset time interval. This ensures that the prompt information is output sequentially and avoids output overlap due to too rapid a transition, allowing the user to clearly and accurately receive the prompt information.

[0016] In one possible implementation, the event redundancy rule includes a redundancy exemption condition and a preset redundancy duration; the redundancy exemption condition is used to determine whether a candidate output event is not subject to the preset redundancy duration limit. Based on the event redundancy rule, redundant events are filtered out from the candidate output events, and the remaining events after filtering are determined as the target output events, including: Based on the redundancy exemption condition, it is determined whether the candidate output event is an exemption event; the exemption event is an event that allows repeated output of prompt information within a preset redundancy duration. If the candidate output event is an exemption event, then the candidate output event will be determined as the target output event; If the candidate output event is a non-exempt event, then the historical output events within the preset redundancy period are obtained, and based on the historical output events, redundant events in the candidate output events are filtered out, and the events remaining after filtering are determined as the target output events.

[0017] This application first determines whether a candidate output event is an exempt event based on redundancy exemption conditions. If it is an exempt event, it is determined as the target output event to ensure that emergency information is not delayed or filtered, thus protecting driving safety. If it is not an exempt event, redundant events in the candidate output events are filtered out based on historical output events within a preset redundancy period. This effectively avoids the repeated output of the same event's prompt information within the preset redundancy period, protecting the user from continuous interference from redundant information.

[0018] In one possible implementation, redundant events are filtered out from candidate output events based on historical output events, and the remaining events after filtering are determined as target output events, including: Obtain the first event information of the candidate output event and the second event information of the historical output event; Based on the information of the first event and the information of the second event, determine whether the candidate output event and the historical output event are the same event; If a candidate output event is the same as a historical output event, the candidate output event is determined to be a redundant event and filtered out. If the candidate output event is not the same as the historical output event, then the candidate output event is determined to be the target output event.

[0019] Based on the above technical content, by comparing the first event information of the candidate output event and the second event information of the historical output event, it is determined whether the two are the same event. If they are the same event, they are judged as redundant events and filtered out; otherwise, they are taken as the target output event. This embodiment determines redundant events based on event information, effectively avoiding the problems of false filtering or missed filtering caused by relying solely on a single trigger time, and improving the accuracy of redundant filtering.

[0020] In one possible implementation, based on the target output event, corresponding prompt information is output, including: If there are multiple target output events, the multiple target output events are sorted according to the preset event priority rules to determine the event output order; Based on the event output order and preset output rules, prompt messages corresponding to multiple target output events are output sequentially; among them, the output rules include that the time interval between two adjacent prompt messages is greater than a second preset duration.

[0021] In this embodiment, multiple target output events are sorted according to event priority rules to obtain the event output order. Then, the corresponding prompts are output sequentially according to the event output order, ensuring that prompts for events with higher importance are output first. At the same time, the time interval between two adjacent prompts is greater than a second preset duration, enabling users to clearly distinguish and receive each prompt, avoiding information overlap or confusion caused by short time intervals, and improving information recognition in multi-event output scenarios.

[0022] In one possible implementation, multiple target output events are sorted based on a preset event priority rule to determine the event output order, including: Based on event priority rules, multiple target output events are sorted. If there are target output events with the same priority, the trigger time of the target output events with the same priority is obtained, and the target output events with the same priority are sorted according to the trigger time to obtain the event output order.

[0023] In this embodiment of the application, for events with the same priority, the events with the same priority are further sorted according to the trigger time. Through the above two-level sorting mechanism of priority first and trigger time second, it is ensured that the prompt information corresponding to the events with higher importance is output first, and that events with the same priority are output in sequence. This allows users to perceive the order of changes in vehicle status according to the order of prompt information and to more intuitively judge the current operating status of the vehicle.

[0024] In one possible implementation, at least one corresponding event is determined based on vehicle operation information, including: Obtain the preset driving route, and determine at least one corresponding event to be verified based on the vehicle operation information and driving route; Based on preset validity criteria, at least one event to be verified is validated, and the events that pass the validity verification are identified as at least one event.

[0025] Here, the validity of the events to be verified is checked, and false events caused by momentary jitter, environmental interference, etc. are filtered out to improve the accuracy of event recognition. At the same time, false events are prevented from entering subsequent mutual exclusion filtering, redundancy filtering and other processes, thus reducing the computational consumption of the system.

[0026] Secondly, embodiments of this application provide a vehicle information output control device, including: The acquisition module is used to acquire vehicle operation information during vehicle operation; The processing module is used to determine at least one corresponding event based on the vehicle operation information; The processing module is also used to process at least one event based on preset rules to obtain a target output event; the preset rules include event mutual exclusion rules and / or event redundancy rules; the event mutual exclusion rules are used to retain at most one event among events with mutual exclusion relationships; the event redundancy rules are used to filter out redundant events in at least one event; The output module is used to output corresponding prompt information based on the target output event.

[0027] Thirdly, embodiments of this application provide a vehicle, including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the computer program, it implements the vehicle information output control method as described in any of the first aspects.

[0028] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the vehicle information output control method as described in any of the first aspects.

[0029] It is understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here.

[0030] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this specification. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0032] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of this application; Figure 2 This is a schematic flowchart of a vehicle information output control method provided in an embodiment of this application; Figure 3 This is a schematic flowchart of a vehicle information output control method provided in another embodiment of this application; Figure 4 This is a schematic diagram of the structure of a vehicle information output control device provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a vehicle provided in one embodiment of this application. Detailed Implementation

[0033] The present application will be described more clearly below with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the function of the present application, but do not limit the present application in any way. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of the present application. These all fall within the protection scope of the present application.

[0034] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0035] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0036] In the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0037] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0038] Furthermore, the term "multiple" mentioned in the embodiments of this application should be interpreted as two or more.

[0039] As the vehicle travels along the preset path, the system will provide real-time feedback to the user through various information output modules, providing alerts on vehicle status changes, scene transitions, and driving decisions. This ensures that the user is aware of the vehicle's operating status in real time, guaranteeing driving and parking safety. Scenarios where the vehicle travels along the preset path include, but are not limited to, HAVP, memory driving, and Navigate on Autopilot (NOA) scenarios.

[0040] However, during actual vehicle operation, abnormal output of event prompts frequently occurs, impacting user experience and parking safety. Taking the HAVP scenario as an example, when multiple events such as cruise control turning and route changes are triggered simultaneously or switched consecutively, the voice prompts may become disjointed and overlapping. For instance, simultaneously broadcasting "Caution: Turning" and "Route changed" prompts can cause auditory interference, making it difficult for users to clearly understand the information and resulting in a poor user experience. Furthermore, because users cannot clearly understand the prompts, they are prone to misjudging the vehicle's current operating status, affecting driving safety.

[0041] Furthermore, for the same event occurring within the same time period and along the same path, related technologies often repeatedly broadcast the same prompts, leading to broadcast redundancy. This not only inconveniences users but also increases system resource consumption. For example, when approaching the destination, the system might repeatedly broadcast "Destination near, please prepare to park" every second, severely impacting the user experience. Redundant broadcasts can also prevent users from promptly capturing critical emergency information, posing a security risk.

[0042] The applicant has found that, in order to enable users to clearly and accurately obtain prompts and improve user experience and driving safety, it is necessary to consider a new method for controlling the output of vehicle information.

[0043] To enhance user experience, in the embodiments of this application, after determining at least one triggered event, the at least one event can be mutually excluded. At most one event is retained from the mutually exclusive events, thereby avoiding the simultaneous output of conflicting prompts. This prevents user confusion caused by receiving multiple conflicting prompts, allowing the user to accurately perceive the vehicle's current status, thus improving user experience and ensuring driving safety. And / or, to protect the user from continuous interference from redundant event prompts, redundant events can be filtered out from the at least one event. This prevents the same prompt from being repeatedly output when the same event is triggered multiple times in a short period, reducing interference from redundant information. Simultaneously, because redundant events are effectively filtered, newly triggered key events are not overwhelmed by duplicate information, allowing the user to promptly perceive changes in the vehicle's status, ensuring the accuracy of the user's perception of the vehicle's current status, improving user experience, and ensuring driving safety.

[0044] First refer to Figure 1 , Figure 1 The illustration shows an application scenario diagram provided according to an embodiment of this application. The devices involved in the application scenario include sensors, processors, vehicle speakers, instruments, and vehicle head unit (HUT) displays.

[0045] The sensors are used to collect vehicle operation information and send it to the processor.

[0046] The processor can identify one or more triggered events based on vehicle operating information, and perform mutual exclusion filtering on the events to obtain candidate output events, thus avoiding the output of prompts incorrectly. Then, it performs redundancy filtering on the candidate output events to obtain the target output event, thereby avoiding the repeated output of the same event prompt. Next, it prioritizes the target output events to determine the output order. Finally, it determines whether the target output event meets the synchronization triggering conditions of the vehicle speakers, instrument panel, and vehicle infotainment display. If it does, it generates a synchronization trigger command and sends it to the vehicle speakers, instrument panel, and vehicle infotainment display.

[0047] The vehicle's speakers can broadcast voice prompts for the target output event, the instrument panel can display corresponding text prompts, and the vehicle's infotainment display can display corresponding icons and text prompts.

[0048] The following is combined Figure 1 Application scenarios, refer to Figures 2-3 This application describes a vehicle information output control method according to exemplary embodiments thereof. It should be noted that the above application scenarios are shown only to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited in any way. Rather, the embodiments of this application can be applied to any applicable scenario.

[0049] It should be noted that the embodiments of this application can be applied to vehicles, and the vehicle can be a server or a host computer of the vehicle, that is, the vehicle information output control method provided by the exemplary embodiments of this application can be executed on the server or the host computer of the vehicle.

[0050] The server can be a monolithic server or a distributed server spanning multiple computers or computer data centers. Servers can also be of various categories, such as, but not limited to, web servers, application servers, database servers, or proxy servers.

[0051] Optionally, a server may include hardware, software, or embedded logic components for performing suitable functions supported or implemented by the server, or a combination of two or more such components. For example, a server may be a blade server, a cloud server, or a server group consisting of multiple servers, which may include one or more of the above-mentioned categories of servers, etc.

[0052] It should be noted that the vehicle information output control method provided according to the exemplary embodiments of this application can be executed on the same device or on different devices.

[0053] refer to Figure 2 , Figure 2 This is a schematic flowchart of a vehicle information output control method provided in an embodiment of this application. Figure 2 As shown, the method in the embodiments of this application may include: Step 201: During vehicle operation, obtain vehicle operation information.

[0054] Taking the HAVP scenario as an example, if the HAVP function is activated during vehicle operation, the vehicle will perform operations such as cruise, turning, route change, destination approach reminder, and destination parking according to the memorized path, and output vehicle operation commands in real time to control vehicle operation. Vehicle operation commands include, but are not limited to, turning commands and route adjustment commands.

[0055] Vehicle operation information refers to multi-dimensional data collected by devices such as cameras, lidar, and vehicle sensors mounted on the vehicle. This multi-dimensional data includes scene data and vehicle status data.

[0056] Taking the HAVP scenario as an example, scenario data includes, but is not limited to, the turning angle and position corresponding to cruise turns, the direction and distance of route changes, as well as information such as vehicle position, distance from the destination, and parking space status at the destination. Vehicle status data includes, but is not limited to, vehicle gear status data and vehicle stationary data. Gear status data includes gear shifting information and gear anomaly information, while vehicle stationary data includes the reason for stationary status and duration of stationary status.

[0057] In one implementation scenario, multidimensional data can also include environmental data. Environmental data includes, but is not limited to, information on the status of surrounding obstacles and road boundary information. Environmental data can be used to optimize the output prompts. For example, if environmental data determines that the vehicle is in an open parking lot with no obstructions, the output of prompts can be simplified to reduce redundancy in non-emergency situations.

[0058] Optionally, the acquisition frequency of multidimensional data can be kept consistent with the HAVP operating frequency to ensure that each frame of vehicle operation information is synchronized with the vehicle operation command, avoiding problems such as data loss or timing deviation caused by inconsistency between the acquisition frequency and the operating frequency. Under normal circumstances, the acquisition frequency is not lower than 10Hz.

[0059] Step 202: Based on the vehicle operation information, determine at least one corresponding event.

[0060] An event refers to a specific state change or operation node that occurs during vehicle operation and requires the output of prompt information to the user. Taking the HAVP scenario as an example, events include, but are not limited to, cruise turning, route change, approaching the destination, gear status, and vehicle stationary.

[0061] In some embodiments, after acquiring vehicle operation information, the information can be preprocessed to remove abnormal data and improve data quality. Abnormal data may include state transition data. State transition data refers to abrupt changes in vehicle operation parameters that do not conform to the vehicle's physical motion characteristics at adjacent sampling times; for example, the vehicle speed may jump instantaneously from 10 km / h to 60 km / h between two adjacent frames. Optionally, the change in each parameter in the vehicle operation information between two adjacent frames can be calculated. If the change exceeds a preset threshold, the data in the corresponding frame is determined to be state transition data and removed.

[0062] In one possible implementation, a preset driving route can be obtained, and at least one corresponding event can be determined based on the driving route and vehicle operation information.

[0063] Step 203: Based on preset rules, process at least one event to obtain the target output event; the preset rules include event mutual exclusion rules and / or event redundancy rules; the event mutual exclusion rules are used to retain at most one event among events with mutual exclusion relationships; the event redundancy rules are used to filter out redundant events in at least one event.

[0064] Among them, event mutual exclusion rules refer to a predefined set of logical judgment conditions used to describe whether there is a semantic or perceptual mutual exclusion relationship between different events. A mutual exclusion relationship means that when the prompts corresponding to two or more events are output at the same time, it will cause cognitive confusion for the user, making it impossible to accurately understand the vehicle's current state. For example, when the prompts corresponding to the events of cruise turning and route change are output at the same time, the user cannot determine whether the vehicle is turning along the original memorized route or has deviated from the original memorized route to change lanes. Therefore, cruise turning and route change can be defined as mutually exclusive events. Similarly, vehicle stationary and multiple events such as cruise turning, route change, and approaching the destination are mutually exclusive.

[0065] The target output event is the event that requires a prompt to be displayed to the user. In one possible implementation, at least one event can be processed based on event mutual exclusion rules to obtain the target output event. Specifically, if the at least one event includes only one event, that event can be directly used as the target output event. If the at least one event includes multiple events, it is necessary to further determine whether there is a mutual exclusion relationship between the events based on the event mutual exclusion rules. If some of the triggered at least one event has a mutual exclusion relationship, since at most one event can be retained from the mutually exclusive events, only that event is retained as the target output event. Therefore, prompts from all of the aforementioned events will not be output simultaneously, effectively avoiding the problem of cognitive confusion for the user when receiving prompts from multiple mutually exclusive events, and helping to ensure that the user accurately understands the current state of the vehicle.

[0066] In another implementation scenario, if there is no mutual exclusion relationship between multiple events, it means that the prompts corresponding to all triggered events will not cause cognitive confusion for the user. Therefore, each event can be used as the target output event to ensure that the user has a comprehensive understanding of the vehicle status.

[0067] Event redundancy rules are used to manage the repeated triggering of the same event within a preset redundancy period, thus preventing the frequent output of identical prompts within a short time. In one possible implementation, at least one event can be processed based on the event redundancy rules to determine the target output event. Specifically, if the current event is the same as a historical output event already output within the preset redundancy period, the current event is identified as a redundant event and filtered out. The remaining event is then used as the target output event, reducing information output redundancy, avoiding user interference, and lowering system resource consumption.

[0068] The preset redundancy duration refers to the output interval threshold set for the same event. It defines how long the same event can be repeatedly triggered within which it is considered redundant. The specific setting can be determined according to actual needs, such as 3 seconds.

[0069] In addition, event redundancy rules can also include redundancy exemption conditions for events. These conditions determine whether an event is not subject to a preset redundancy duration. Events that meet the redundancy exemption conditions are not considered redundant events, even if they are the same as historical output events within the preset redundancy duration. These events are still used as target output events, and corresponding prompts are output immediately. This ensures timely notification of emergency events such as security warnings while avoiding information redundancy, thus guaranteeing security.

[0070] In another possible implementation, at least one event can be processed based on event mutual exclusion rules and event redundancy rules to determine the target output event. For example, first, the event mutual exclusion rule can be used to filter out events without mutual exclusion from at least one event, and one event can be retained from the events with mutual exclusion. Then, the event redundancy rule can be used to filter out redundant events from the events without mutual exclusion and the retained event, and the remaining event after filtering can be used as the target output event. Alternatively, the event redundancy rule can be used first to filter out redundant events from at least one event, and then the event mutual exclusion rule can be used to filter out events without mutual exclusion from the remaining events after filtering out redundant events, and one event can be retained from the events with mutual exclusion. The events without mutual exclusion and the retained event can then be used as the target output event.

[0071] Step 204: Based on the target output event, output the corresponding prompt information.

[0072] The number of target output events can be one or more. When there are multiple target output events, the priority of the multiple target output events can be determined, and the prompt information of the multiple target output events can be output in sequence.

[0073] In one possible implementation, the prompt information corresponding to the target output event can be output through one or more of the voice broadcast module, the classical Chinese prompt module, and the HUT display module. Specifically, after determining the target output event, a synchronization trigger command can be generated and sent to the voice broadcast module, the classical Chinese prompt module, and the HUT display module respectively to achieve multimodal output.

[0074] The voice broadcast module, upon receiving a synchronization trigger command, can broadcast prompts according to a preset speech rate and tone, such as "The route has changed, please pay attention to the surrounding environment," ensuring clear and uninterrupted speech that meets the acoustic requirements of in-vehicle voice broadcasting and has sufficient penetration in noisy environments.

[0075] Upon receiving a synchronization trigger command, the Chinese language display module can display a Chinese prompt on the instrument that matches the voice broadcast content, such as "Route changed." The displayed font must be clear and the color prominent. Optionally, white font on a black background can be used for display, and red font can be used for emergency events to provide a warning.

[0076] After receiving the synchronization trigger command, the HUT display module can display icons and text prompts on the HUT interface that are consistent with the voice broadcast content and the classical Chinese prompt content. For example, it can display a path change icon and the text "Path has changed". The display duration is consistent with the voice broadcast duration to avoid premature disappearance or delayed display.

[0077] In some embodiments, the consistency and synchronization of the outputs of the voice broadcast module, the classical Chinese prompt module, and the HUT display module can be checked every third preset duration. If inconsistencies in the output content or a time difference in outputs exceeds a fourth preset duration, such as 0.2 seconds, appropriate adjustments are made immediately to ensure the synchronization of multimodal output prompts, avoid user confusion, and improve the human-computer interaction experience.

[0078] It should be noted that the consistency of the output content in this embodiment means that the core information conveyed by the voice broadcast module, the classical Chinese prompt module, and the HUT display module is the same, not that the three modules have completely identical forms of expression.

[0079] In this embodiment, vehicle operation information is acquired, and at least one triggered event is determined based on this information. Then, the at least one event is processed according to preset rules to obtain a target output event. These preset rules include event mutual exclusion rules and / or event redundancy rules. If the at least one event is processed based on the event mutual exclusion rule, since the event mutual exclusion rule retains at most one event among mutually exclusive events, multiple mutually exclusive events will not be simultaneously identified as the target output event. This avoids simultaneously outputting conflicting prompts, preventing user confusion due to receiving multiple conflicting prompts, and enabling users to accurately perceive the vehicle's current state. If the event redundancy rule is used to filter out redundant events from the at least one event to obtain the target output event, the redundant events are filtered out. Because redundant events are filtered out, the same prompts will not be repeatedly output when the same event is triggered multiple times in a short period, protecting users from continuous interference from redundant event prompts. Simultaneously, because redundant events are effectively filtered, newly triggered key events will not be overwhelmed by duplicate information, allowing users to promptly perceive changes in the vehicle's state, thus ensuring the accuracy of the user's perception of the vehicle's current state. If at least one event is processed based on both event mutual exclusion rules and event redundancy rules, the final output target event will be neither conflicting nor redundant. Users can not only clearly and accurately know the changes in the vehicle's operation, but also avoid the continuous interference of redundant event prompts, thus improving the accuracy of information output and user experience, and ensuring driving safety.

[0080] In addition, when outputting prompts for target output events, this application embodiment also needs to consider how to connect the prompts when the events switch continuously, so as to avoid the prompts being displayed incorrectly or overlapping, so that the user can accurately receive the prompts and understand the changes in the vehicle's status. At the same time, it also needs to consider how to ensure the synchronization of the prompts output by the voice broadcast module, the text prompt module and the HUT display module, so as to improve the human-computer interaction experience. Figure 3 This is a flowchart illustrating a vehicle information output control method according to another embodiment of this application, as shown below. Figure 3 As shown, the method includes: Step 301: During vehicle operation, obtain vehicle operation information.

[0081] Here, for the implementation of step 301, please refer to [link / reference]. Figure 2 The relevant descriptions in the embodiments will not be repeated here.

[0082] Step 302: Obtain the preset driving route; determine at least one event to be verified based on the vehicle operation information and driving route; perform validity verification on at least one event to be verified based on the preset validity judgment conditions, and determine the event to be verified that passes the validity verification as at least one event.

[0083] A driving route refers to the pre-defined path a vehicle follows during operation. In the HAVP scenario, this route is a memory route learned by the vehicle, containing the path's geometry, key nodes and their corresponding positions, as well as the vehicle's baseline operating information. Geometric features include path curvature, turning angles, and path length; key nodes include turning points, gear shift points, endpoint proximity points, and the endpoint itself; and the vehicle's baseline operating information includes the baseline gear status data for each position.

[0084] As can be seen from the above embodiments, vehicle operation information includes scene data such as the turning angle and turning position corresponding to cruise turning, the direction and distance of path change, vehicle position, distance of vehicle from destination, and status of destination parking space, as well as vehicle status data such as vehicle gear status and vehicle stationary data.

[0085] In one implementation scenario, vehicle operation information and driving route can be matched to determine the triggered event to be verified. For example, if the vehicle's current position reaches a turning point in the driving route, and the difference between the turning angle and the turning angle at that turning point in the driving route is less than a first preset angle threshold, then the triggered event to be verified is determined to be a cruise turning event. If the vehicle's current driving direction is inconsistent with the direction of the corresponding position in the driving route, then the triggered event to be verified is determined to be a path change event. If the vehicle's current position reaches a point near the destination in the driving route, then the triggered event to be verified is determined to be a destination proximity event. For gear position status events, if the vehicle's current position coincides with the position of a gear shift point in the driving route, then the triggered event to be verified is determined to be a gear position status event. If the vehicle's current position reaches the destination, then the triggered event to be verified is determined to be a destination proximity event.

[0086] After identifying the events to be validated, validity checks can be performed on them based on validity criteria. If an event meets the validity criteria, it passes the validation and can be identified as at least one event. If an event does not meet the validity criteria, it fails the validation, and subsequent steps such as mutual exclusion filtering, redundancy removal, and outputting prompts are unnecessary.

[0087] The validity criteria include multiple conditions such as recognition accuracy, triggering conditions, and time stability. Among these, meeting the recognition accuracy requirement requires the event recognition accuracy to be greater than a preset accuracy threshold. Event recognition accuracy can be used as recognition confidence to ensure the reliability of the current recognition result and exclude invalid events caused by perceptual misidentification or false detection. Recognition confidence can be obtained based on a deep learning model.

[0088] The trigger condition is that the current vehicle operating information meets the trigger threshold corresponding to the event. Different events have different trigger thresholds. For the endpoint proximity event, the trigger threshold is a preset distance threshold, and the trigger condition is that the distance between the vehicle and the endpoint is less than or equal to the preset distance threshold. For the cruise turning event, the trigger threshold is a second preset angle threshold and a preset curvature threshold, and the trigger condition is that the current turning angle is greater than the second preset angle threshold and the path curvature is greater than the preset curvature threshold. For the path change event, the trigger threshold is a preset deviation threshold, and the trigger condition is that the lateral deviation of the vehicle's current position from the driving route is greater than the preset deviation threshold. For the gear status event, the trigger condition is that the vehicle chassis signal undergoes a valid switch or the gear abnormality is triggered. For the vehicle stationary event, the trigger threshold is a preset vehicle speed threshold, and the trigger condition is that the vehicle speed is continuously less than or equal to the preset vehicle speed threshold and the braking system is activated.

[0089] The time stability condition is met when the same event is identified based on vehicle operation information from multiple consecutive frames, and the event remains stable within these frames without any jumps or instantaneous disappearances. This avoids false triggers caused by single-point noise or instantaneous jitter and improves the reliability of event triggering.

[0090] The preset accuracy threshold, trigger threshold, etc. mentioned above can all be set based on actual needs. For example, the preset accuracy threshold is 98%, the preset distance threshold is 5m, and the preset vehicle speed threshold is 0.

[0091] In another possible implementation, at least one event can be determined based on the triggering conditions. In this case, there is no need to perform validity verification on the event based on the triggering conditions; validity verification can be performed only based on recognition accuracy and time stability.

[0092] Here, the validity of the events to be verified is checked, and false events caused by momentary jitter, environmental interference, etc. are filtered out to improve the accuracy of event recognition. At the same time, false events are prevented from entering subsequent mutual exclusion filtering, redundancy filtering and other processes, thus reducing the computational consumption of the system.

[0093] Step 303: Based on the event mutual exclusion rule, perform mutual exclusion filtering on at least one event to obtain candidate output events; mutual exclusion filtering is a filtering operation used to retain at most one event from events that have a mutual exclusion relationship.

[0094] Candidate output events refer to a set of events that are logically non-conflicting. This set may contain all triggered events or only some triggered events, depending on whether there are mutual exclusion relationships between the events.

[0095] In one implementation scenario, if at least one event consists of only one event, since there is no mutually exclusive event, this event can be directly used as a candidate output event.

[0096] In another implementation scenario, if at least one event includes multiple events, then based on the event mutual exclusion rule, it is determined whether there is a mutual exclusion relationship between the multiple events; if there is no mutual exclusion relationship between the multiple events, then each event is taken as a candidate output event; if there is a mutual exclusion relationship between the multiple events, then one event is determined from the events with mutual exclusion relationship, and the reserved event and the event without mutual exclusion relationship are taken as candidate output events.

[0097] As shown in the above embodiments, event mutual exclusion rules are used to determine whether there is a mutual exclusion relationship between different events. Taking the HAVP scenario as an example, its events include cruise turning, route change, approaching the destination, gear position, and vehicle stationary. Event mutual exclusion rules define the mutual exclusion relationship between events. For example, cruise turning and route change are mutually exclusive, and vehicle stationary is mutually exclusive with multiple events such as cruise turning, route change, and approaching the destination. In addition, event mutual exclusion rules also define the compatibility relationship between events. For example, gear position is compatible with other events.

[0098] In one possible implementation, each event can be iterated based on an event mutual exclusion rule to determine whether at least one event contains an event that is mutually exclusive with it. If multiple events are not mutually exclusive, that is, each event has no mutually exclusive events, such as when the gear position is close to the finish line, then each event can be considered a candidate output event.

[0099] In some embodiments, if there is a mutual exclusion relationship among multiple events, it is necessary to further identify the mutually exclusive events and then determine a reserved event from among them. In one possible implementation, the priority of the mutually exclusive events can be determined based on a preset event priority rule; based on the priority of the mutually exclusive events, the event with the highest priority can be determined from among the mutually exclusive events and selected as the reserved event.

[0100] Event priority rules are preset levels of importance for different events. In an implementation scenario, when setting priority rules, they can be set in the order of emergency > scenario status > auxiliary prompts to ensure that emergency information is output first, avoid emergency information being overridden by non-emergency information, and improve parking safety.

[0101] For example, in the HAVP scenario, the priorities of the included events, from highest to lowest, are as follows: gear position > vehicle stationary > route change > cruise turn > destination approaching. Among these, gear position is given the highest priority because it is related to the vehicle's power transmission and direction of travel; abnormal gear shifts may cause unexpected acceleration or reversing, posing a serious safety risk. Vehicle stationary is the next highest priority; a sudden stop could indicate a system malfunction or collision, requiring immediate notification to the user. Route changes involve alterations to the vehicle's trajectory, potentially confusing the user about the vehicle's intentions, thus also requiring timely alerts. Cruise turns and destination approaching are expected events during normal driving and fall under the category of auxiliary prompts; therefore, their priority is relatively low.

[0102] It should be noted that the event priority rule also follows the principle of "driver's instructions take precedence". If the driver triggers a manual operation instruction, the output of the current prompt information will be paused and the manual operation feedback information will be output first.

[0103] For events that are mutually exclusive, the priority of each event can be determined by combining event priority rules. Then, the priorities of each event can be compared to determine the event with the highest priority, and this event is reserved.

[0104] Taking the HAVP scenario as an example, if two mutually exclusive events, namely cruise turning and route change, are triggered simultaneously during HAVP cruise, and the priority of route change is higher than that of cruise turning, then route change can be reserved as the event.

[0105] In one implementation scenario, for mutually exclusive events, after determining which events to retain, other events can be temporarily stored. After the prompt message corresponding to the current target output event is output, the temporarily stored events can be backtested. If the event is still in a triggered state, it can be re-selected for mutual exclusion and redundancy filtering to determine whether to output the prompt message for that event.

[0106] Here, among mutually exclusive events, the event with the highest priority is reserved based on the priority of each event, ensuring that critical and urgent prompts can be delivered to the user, thus improving driving safety.

[0107] In this embodiment, when there is no mutual exclusion relationship between multiple events, each event is treated as a candidate output event to avoid omitting the output of prompts for valid events. When there is a mutual exclusion relationship between multiple events, one event is selected from the mutually exclusive events to be retained. This effectively avoids the problem of user confusion caused by outputting prompts for multiple mutually exclusive events, and helps ensure that users accurately understand the current state of the vehicle.

[0108] Step 304: According to the event redundancy rule, filter out redundant events in the candidate output events, and determine the remaining events after filtering as the target output events.

[0109] In one possible implementation, the event redundancy rule includes a redundancy exemption condition and a preset redundancy duration; the redundancy exemption condition is used to determine whether a candidate output event is not subject to the preset redundancy duration limit. Optionally, according to the event redundancy rule, redundant events in the candidate output events are filtered out, and the events remaining after filtering are determined as target output events, including: determining whether a candidate output event is an exempted event based on the redundancy exemption condition; an exempted event is an event that allows repeated output of prompt information within the preset redundancy duration; if the candidate output event is an exempted event, then the candidate output event is determined as the target output event; if the candidate output event is not an exempted event, then historical output events within the preset redundancy duration are obtained, and based on the historical output events, redundant events in the candidate output events are filtered out, and the events remaining after filtering are determined as target output events.

[0110] Redundancy exemption conditions are used to determine whether a candidate output event is not subject to a preset redundancy duration limit. For example, redundancy exemption conditions can be implemented based on a preset set of exemption events, which typically includes safety-related emergency events, such as abnormal gear shifting or sudden vehicle stoppage.

[0111] When a candidate output event is included in the set of exempt events, it is determined to be an exempt event. Exempt events are events for which repeated output of prompts is permitted within a preset redundancy period; they are not limited by the preset redundancy period. Therefore, exempt events can be directly identified as target output events, and corresponding prompts can be output to promptly remind users and improve driving safety.

[0112] If the candidate output event is not included in the set of exempted events, it is determined to be a non-exempt event. Further redundancy determination is required based on historical output events within the preset redundancy period to filter out redundant events. This ensures that the same event triggered repeatedly within the preset redundancy period will only output the corresponding prompt information once.

[0113] This application first determines whether a candidate output event is an exempt event based on redundancy exemption conditions. If it is an exempt event, it is determined as the target output event to ensure that emergency information is not delayed or filtered, thus protecting driving safety. If it is not an exempt event, redundant events in the candidate output events are filtered out based on historical output events within a preset redundancy period. This effectively avoids the repeated output of the same event's prompt information within the preset redundancy period, protecting the user from continuous interference from redundant information.

[0114] In one possible implementation, redundant events are filtered out from candidate output events based on historical output events, and the remaining events after filtering are determined as target output events. This includes: obtaining first event information of candidate output events and second event information of historical output events; determining whether candidate output events and historical output events are the same event based on the first event information and the second event information; if candidate output events and historical output events are the same event, then candidate output events are determined as redundant events and filtered out; if candidate output events and historical output events are not the same event, then candidate output events are determined as target output events.

[0115] The first event information is a set of attribute information related to the candidate output event, including at least the event type, triggering condition, and triggering location of the candidate output event. The second event information is a set of attribute information related to historical output events, including at least the event type, triggering condition, and triggering location of the historical output events.

[0116] If the candidate output event has the same event type, the same triggering condition, and the triggering location is within the same path range as the historical output event, then the candidate output event and the historical output event are determined to be the same event; otherwise, the candidate output event and the historical output event are determined to be different events.

[0117] Here, "event type" refers to the category to which the event belongs. Taking the HAVP scenario as an example, the event types are those mentioned above, such as cruise turning, route change, approaching the destination, gear status, and vehicle stationary. For example, both the candidate output event and the historical output event are "approaching the destination" events.

[0118] As can be seen from the above, the triggering condition is that the vehicle operation information meets the triggering threshold corresponding to the event. For example, both endpoint proximity events are triggered by "the distance between the vehicle and the endpoint is less than or equal to the preset distance threshold", and the triggering conditions are the same. Both route change events are triggered by "the lateral offset of the vehicle's current position from the driving route is greater than the preset deviation threshold", and the triggering conditions are the same.

[0119] The trigger position refers to the spatial location of the vehicle when the event is triggered, used to determine whether two events occur within the same path segment. In one possible implementation, if the longitudinal deviation between the trigger position corresponding to the candidate output event and the trigger position corresponding to the historical output event is less than a first distance threshold, and the lateral deviation is less than a second distance threshold, then the candidate output event and the historical output event are determined to be events within the same path segment; otherwise, the candidate output event and the historical output event are determined to be events within different path segments.

[0120] Taking the HAVP scenario as an example, when the HAVP cruise is nearing its destination, the destination proximity event will be detected continuously when the vehicle is 5m, 4.5m and 4m away from the destination, with an interval of 0.5s. The event type, triggering condition and triggering location of the above three destination proximity events are within the same path range. The three events can be judged as the same event. Only when the destination proximity is detected for the first time, the corresponding prompt information will be output. The subsequent two events will be judged as redundant events and filtered out, thereby avoiding the repeated output of the same prompt information every 0.5s.

[0121] Based on the above technical content, by comparing the first event information of the candidate output event and the second event information of the historical output event, it is determined whether the two are the same event. If they are the same event, they are judged as redundant events and filtered out; otherwise, they are taken as the target output event. This embodiment determines redundant events based on event information, effectively avoiding the problems of false filtering or missed filtering caused by relying solely on a single trigger time, and improving the accuracy of redundant filtering.

[0122] In this embodiment of the application, the dual filtering mechanism of mutual exclusion filtering and redundancy filtering ensures that the final output target event is neither conflicting nor redundant. Users can not only avoid receiving multiple conflicting prompts and causing cognitive confusion, but also clearly and accurately understand the changes in the vehicle operation process. At the same time, they can also avoid being continuously interfered with by redundant event prompts, further improving the accuracy of information output and user experience, and ensuring driving safety.

[0123] Step 305: If there are multiple target output events, sort the multiple target output events according to the preset event priority rules to determine the event output order; according to the event output order and the preset output rules, output the prompt information corresponding to the multiple target output events in sequence; wherein, the output rules include that the time interval between two adjacent prompt information is greater than a second preset duration.

[0124] Optionally, based on a preset event priority rule, multiple target output events are sorted to determine the event output order, including: sorting multiple target output events based on the event priority rule; if there are target output events with the same priority, the trigger time of the target output events with the same priority is obtained, and the target output events with the same priority are sorted according to the trigger time to obtain the event output order.

[0125] To ensure users receive timely notifications for more important events, multiple target output events can be arbitrated based on event priority rules. These events are initially sorted from highest to lowest priority. If the priorities of multiple target output events are all different, the initial sorting result becomes the event output order, which is also the order in which the corresponding notification messages for each target output event are output. For example, if two target output events, "normal gear shift" and "endpoint approaching," are triggered simultaneously, "normal gear shift" belongs to the gear status event, which has a higher priority than "endpoint approaching." Therefore, the event output order would be "gear shift" followed by "endpoint approaching."

[0126] In one possible implementation, the event output order can be further adjusted based on the urgency of the target output events, in addition to the event priority rules. For example, if the target output events include normal gear shifting and sudden vehicle stoppage, the preset event priority is gear position > vehicle stoppage. If the two are sorted according to the event priority rules, the event output order would be normal gear shifting, then sudden vehicle stoppage. However, since normal gear shifting is a routine operation, while sudden vehicle stoppage may indicate a system malfunction or collision, posing a more direct threat to driving safety, although gear position has a higher priority than vehicle stoppage, if both normal gear shifting and sudden vehicle stoppage are triggered simultaneously, the event output order can be adjusted to sudden vehicle stoppage, then normal gear shifting.

[0127] Trigger time refers to the moment when the event is confirmed to have occurred. For target output events with the same priority, they can be sorted according to the order of their trigger times, so that the target output event that was triggered earlier is output first.

[0128] In another implementation scenario, if there are target output events with the same priority and the same trigger time, the prompt information of the target output event that provides stronger guidance for the user's operation will be output first. For example, if the two events "Near the End" and "Normal Gear Shift" have the same priority and the same trigger time, the prompt information of "Near the End" can be output first because the "Near the End" event has a more direct guiding significance for the user's immediate operation, such as preparing to park or observing the surrounding environment.

[0129] In this embodiment of the application, for events with the same priority, the events with the same priority are further sorted according to the trigger time. Through the above two-level sorting mechanism of priority first and trigger time second, it is ensured that the prompt information corresponding to the events with higher importance is output first, and that events with the same priority are output in sequence. This allows users to perceive the order of changes in vehicle status according to the order of prompt information and to more intuitively judge the current operating status of the vehicle.

[0130] After determining the event output order, multiple target output events can be sequentially output with corresponding prompts based on preset output rules. The output rules are the constraints that must be followed when outputting prompts for each target output event. These include ensuring that the time interval between two adjacent prompts is greater than a second preset duration. This ensures sufficient time between prompts, allowing users to clearly distinguish and receive each prompt, avoiding auditory overlap or information confusion caused by excessively short intervals. The second preset duration can be set according to actual needs, for example, it can be 0.5 seconds.

[0131] Taking gear shifting and approaching the destination as two target output events as examples, based on the determined event output order, the prompt information corresponding to gear shifting is output first, such as "gear has been shifted to D gear". After a second preset time, the prompt information corresponding to approaching the destination is output, such as "the destination is approaching, please prepare to park".

[0132] In another implementation scenario, if there is only one target output event, then the prompt message for that target output event can be output directly.

[0133] As can be seen from the above embodiments, after determining the target output event, a synchronization trigger instruction can be generated and sent to the voice broadcast module, the classical Chinese prompt module and the HUT display module respectively to achieve multimodal output.

[0134] In one possible implementation, before generating the synchronization trigger instruction, the target output event can be verified based on preset synchronization trigger conditions. For example, the synchronization trigger conditions may include one or more of the following conditions: the target output event is still valid, no higher priority event is currently triggered, the target output event is a non-repeating event, and there is no mutual exclusion relationship between the target output event and the event identified in the current frame.

[0135] It should be noted that although the target output event has undergone mutual exclusion filtering, redundancy removal, and priority arbitration in steps 303 to 305, there is a small time window between the determination of the target output event and the output of the prompt message. Within this time window, the vehicle's operating status may change, such as the sudden occurrence of a higher priority event, or the identification of a new event that is mutually exclusive with the target output event. Therefore, before outputting the prompt message for the target output event, it can be determined whether it meets the synchronization triggering conditions.

[0136] If the synchronization triggering conditions are met, a corresponding synchronization triggering command is generated and simultaneously sent to the voice broadcast module, text prompt module, and HUT display module, achieving multimodal synchronous output. This synchronization triggering mechanism effectively avoids inconsistencies in the content of voice broadcasts, text prompts, and HUT displays due to different triggering conditions. It ensures that the prompting information corresponding to the same target output event is triggered simultaneously in the three output modalities of voice, text, and graphics, and that the semantics of the output content are consistent, eliminating the cognitive burden and misjudgment of the user caused by multimodal information conflicts. Furthermore, it ensures that the final output prompting information is consistent with the latest vehicle status, avoiding outdated or invalid information due to status changes, further improving the timeliness and reliability of information output.

[0137] In this embodiment, multiple target output events are sorted according to event priority rules to obtain the event output order. Then, the corresponding prompts are output sequentially according to the event output order, ensuring that prompts for events with higher importance are output first. At the same time, the time interval between two adjacent prompts is greater than a second preset duration, enabling users to clearly distinguish and receive each prompt, avoiding information overlap or confusion caused by short time intervals, and improving information recognition in multi-event output scenarios.

[0138] Step 306: If an event switch is detected, determine whether there is a mutual exclusion relationship between the event before the switch and the event after the switch. If there is a mutual exclusion relationship between the event before the switch and the event after the switch, interrupt the output of the prompt information corresponding to the event before the switch, and determine whether the event after the switch is the target output event according to the preset event redundancy rule. If the event after the switch is the target output event, output the prompt information corresponding to the event after the switch. If there is no mutual exclusion relationship between the event before the switch and the event after the switch, output the prompt information corresponding to the event after the switch after the switch is output after the output of the prompt information corresponding to the event before the switch is completed and after an interval of the first preset time.

[0139] The pre-switching and post-switching events are determined based on vehicle operation information from different frames. If the target output event identified in the current frame is different from the target output event in the previous frame, an event switch is determined to have occurred. In this case, the event in the previous frame is the pre-switching event, and the event in the current frame is the post-switching event.

[0140] Based on preset event mutual exclusion rules, it can be determined whether there is a mutual exclusion relationship between events before and after the switch. For details, please refer to the above content, which will not be repeated here.

[0141] In one implementation scenario, if there is a mutual exclusion relationship between the pre-switch event and the post-switch event, such as cruise turning and route change, if the corresponding prompt information for the pre-switch event is not fully output, the output is immediately interrupted, triggering redundancy filtering of the post-switch event. If the post-switch event is determined to be the target output event, its prompt information is output. If the post-switch event is determined to be a redundant event, it is filtered out, and the corresponding prompt information is not output.

[0142] In another implementation scenario, if there is no mutual exclusion between the pre-switch event and the post-switch event, i.e. they are compatible, the pre-switch event prompt information can be output first, and then the post-switch event prompt information can be output.

[0143] In one possible implementation, to ensure the orderly connection of prompts during event switching and to avoid the overlap of prompts for the pre-switching and post-switching events due to too rapid a transition, which could cause auditory or visual interference to the user, the prompts for the post-switching events can be output after a first preset time interval following the completion of the prompts for the pre-switching scene. This avoids information overlap and ensures that the information output is orderly and clear.

[0144] Furthermore, if the event after the switch is the same as the event before the switch, and the event after the switch is a continuation of the event before the switch in consecutive frames (e.g., the endpoint proximity event continues from 5m to 3m from the endpoint), and the time interval between the event before and after the switch is less than the preset deduplication time, based on the preset event redundancy rules, the event after the switch and the event before the switch will be determined as the same event. To allow users to intuitively perceive the continuous change in the vehicle's position, the voice broadcast and text prompts will not be repeated; only the distance or progress information in the HUT interface will be updated.

[0145] Here, upon detecting an event transition, if there is a mutual exclusion relationship between the event before and after the transition, the output of the prompt information for the event before the transition is immediately interrupted. Redundancy filtering is performed on the event after the transition, and the corresponding prompt information is output first. This ensures that when the vehicle's state changes abruptly, the user can promptly obtain the latest information and understand the vehicle's current status. If there is no mutual exclusion relationship between the event before and after the transition, the prompt information for the event after the transition is completed, and after a first preset time interval, is output. This ensures that the prompt information is sequentially connected, avoiding output overlap due to excessively rapid transitions, and allowing the user to clearly and accurately receive the prompt information.

[0146] In one possible implementation, for HAVP scenarios, after the HAVP function is started, before obtaining vehicle operation information, system initialization can be performed first, loading the aforementioned event mutual exclusion rules, event redundancy rules, event priority rules, and multimodal prompt synchronization trigger conditions, etc., to provide a foundation for subsequent mutual exclusion filtering, redundancy filtering, etc.

[0147] Specifically, the acquisition accuracy and frequency of the equipment collecting vehicle operation information can be initialized to ensure the accuracy of the information. The acquisition frequency must reach at least 10Hz. Additionally, the data storage module can be initialized to provide storage support for subsequent data recording. This module stores information output logs, rule parameters, and anomaly records. Optionally, the data storage period can be no less than a fifth preset duration, such as 12 months, to support data traceability and strategy iteration. Furthermore, the voice broadcast module, text prompt module, and HUT display module can be initialized to ensure the consistency and synchronization of their output information. The initial latency of the voice broadcast module should be controlled within 300 milliseconds to meet the real-time requirements of in-vehicle voice interaction.

[0148] The information output log may include various information such as vehicle operation information, output records, redundancy filtering records, priority arbitration records, multimodal synchronization records, and user feedback records. In some embodiments, the information output log can be periodically summarized. Every time a preset number of valid vehicle operation cycles are accumulated, such as 100 HAVP parking cycles, the event mutual exclusion rules, event redundancy rules, event priority rules, and multimodal prompt synchronization trigger conditions can be iteratively optimized.

[0149] For example, iterative optimization may include: adjusting the mutual exclusion and compatibility relationships between events defined in the event mutual exclusion rules to adapt to new vehicle operation scenarios, such as mobile parking scenarios; adjusting the preset redundancy duration of different events based on user feedback records, for example, adjusting the preset redundancy duration of the endpoint proximity event from 3s to 2s to optimize the preset redundancy duration; adjusting the priority order of the event priority rules based on emergency events in actual testing, for example, adding a sudden obstacle intrusion event, whose priority is higher than the gear position event, to update and iterate the event priority rules; optimizing the multimodal synchronous triggering conditions, shortening the output time difference between voice broadcast, text prompts, and HUT display, for example, from 0.2s to 0.1s, to further improve the consistency of multimodal output; and optimizing the information content library, which stores prompt information templates corresponding to various events, including voice broadcast scripts, text prompts, and HUT display icons. For example, the broadcast scripts may be optimized based on user habits to make them more concise and easy to understand, while enriching the broadcast tone to meet the needs of different users.

[0150] In this embodiment, vehicle operation information is acquired during vehicle operation. Based on the vehicle operation information and driving route, at least one event to be verified is identified. Based on preset validity judgment conditions, the validity of the at least one event to be verified is verified, and the events that pass the validity verification are determined as at least one event. This improves the accuracy of event identification and also prevents false events from entering subsequent mutual exclusion filtering and redundancy filtering processes, reducing the system's computational consumption. Subsequently, mutual exclusion filtering can be performed on the at least one event based on event mutual exclusion rules, determining only one retained event from mutually exclusive events. This effectively avoids outputting prompts corresponding to multiple mutually exclusive events, preventing user confusion and ensuring users accurately understand the vehicle's current status. Then, based on redundancy exemption conditions, it is determined whether the candidate output event is an exempt event. If it is an exempt event, it is determined as the target output event to ensure that emergency information is not delayed or filtered, ensuring driving safety. If it is not an exempt event, based on historical output events within a preset redundancy period, redundant events in the candidate output events are filtered out to determine the target output event. This effectively avoids repeated output of prompts for the same event within the preset redundancy period, protecting users from continuous interference from redundant information. Furthermore, if there are multiple target output events, they are sorted according to event priority rules to ensure that prompts for events with higher importance are output first. Additionally, when outputting prompts in the order of event output, the time interval between two adjacent prompts is greater than a second preset duration, allowing users to clearly distinguish and receive each prompt, avoiding information overlap or confusion due to short time intervals, and improving information recognition in multi-event output scenarios. Finally, when an event switch is detected, the output of prompts is flexibly connected based on whether there is a mutual exclusion relationship between the events before and after the switch, ensuring that users can receive prompts promptly and accurately when switching scenarios. Furthermore, this embodiment unifies the synchronization triggering conditions of the voice broadcast module, the written prompt module, and the HUT display module, achieving accurate, orderly, and synchronized information output.

[0151] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0152] Figure 4 This is a schematic diagram of the structure of a vehicle information output control device provided in one embodiment of this application. Figure 4 As shown, the vehicle information output control device provided in this embodiment may include: an acquisition module 401, a processing module 402, and an output module 403.

[0153] The acquisition module 401 is used to acquire vehicle operation information during vehicle operation. The processing module 402 is used to determine at least one corresponding event based on the vehicle operation information; The processing module 402 is further configured to process at least one event based on preset rules to obtain a target output event; the preset rules include event mutual exclusion rules and / or event redundancy rules; the event mutual exclusion rules are used to retain at most one event among events with mutual exclusion relationships; the event redundancy rules are used to filter out redundant events in at least one event; The output module 403 is used to output corresponding prompt information based on the target output event.

[0154] In one possible implementation, the preset rules include event mutual exclusion rules and event redundancy rules; Processing module 402 is specifically used for: Based on the event mutual exclusion rule, at least one event is mutually excluded to obtain candidate output events; mutual exclusion filtering is a filtering operation used to retain at most one event from events that have a mutual exclusion relationship. Based on the event redundancy rule, redundant events in the candidate output events are filtered out, and the remaining events after filtering are determined as the target output events.

[0155] In one possible implementation, processing module 402 is specifically used for: If at least one event includes multiple events, then based on the event mutual exclusion rule, determine whether there is a mutual exclusion relationship between the multiple events; If there is no mutual exclusion relationship between multiple events, then each event is treated as a candidate output event; If there is a mutual exclusion relationship between multiple events, then select one event to be retained from the mutually exclusive events, and use the retained event and the events that are not mutually exclusive as candidate output events.

[0156] In one possible implementation, processing module 402 is specifically used for: Based on preset event priority rules, determine the priority of events that have a mutual exclusion relationship; Based on the priority of events with mutual exclusion relationships, the event with the highest priority is determined from the mutually exclusive events and reserved as the event.

[0157] In one possible implementation, processing module 402 is further configured to: If an event switch is detected, determine whether there is a mutual exclusion relationship between the event before the switch and the event after the switch; If there is a mutual exclusion relationship between the event before and the event after the switch, the output of the prompt message corresponding to the event before the switch is interrupted, and the event after the switch is determined to be the target output event according to the preset event redundancy rule. If the event after the switch is the target output event, the prompt message corresponding to the event after the switch is output. If the events before and after the switch are not mutually exclusive, the prompt information corresponding to the event after the switch is output after the prompt information corresponding to the event before the switch is output and after a first preset time interval has elapsed.

[0158] In one possible implementation, the event redundancy rule includes a redundancy exemption condition and a preset redundancy duration; the redundancy exemption condition is used to determine whether a candidate output event is not subject to the preset redundancy duration limit. Processing module 402 is specifically used for: Based on the redundancy exemption condition, it is determined whether the candidate output event is an exemption event; the exemption event is an event that allows repeated output of prompt information within a preset redundancy duration. If the candidate output event is an exemption event, then the candidate output event will be determined as the target output event; If the candidate output event is a non-exempt event, then the historical output events within the preset redundancy period are obtained, and based on the historical output events, redundant events in the candidate output events are filtered out, and the events remaining after filtering are determined as the target output events.

[0159] In one possible implementation, processing module 402 is specifically used for: Obtain the first event information of the candidate output event and the second event information of the historical output event; Based on the information of the first event and the information of the second event, determine whether the candidate output event and the historical output event are the same event; If a candidate output event is the same as a historical output event, the candidate output event is determined to be a redundant event and filtered out. If the candidate output event is not the same as the historical output event, then the candidate output event is determined to be the target output event.

[0160] In one possible implementation, output module 403 is specifically used for: If there are multiple target output events, the multiple target output events are sorted according to the preset event priority rules to determine the event output order; Based on the event output order and preset output rules, prompt messages corresponding to multiple target output events are output sequentially; among them, the output rules include that the time interval between two adjacent prompt messages is greater than a second preset duration.

[0161] In one possible implementation, output module 403 is specifically used for: Based on event priority rules, multiple target output events are sorted. If there are target output events with the same priority, the trigger time of the target output events with the same priority is obtained, and the target output events with the same priority are sorted according to the trigger time to obtain the event output order.

[0162] In one possible implementation, processing module 402 is specifically used for: Obtain the preset driving route, and determine at least one corresponding event to be verified based on the vehicle operation information and driving route; Based on preset validity criteria, at least one event to be verified is validated, and the events that pass the validity verification are identified as at least one event.

[0163] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0164] Figure 5 This is a schematic diagram of the structure of a vehicle provided in one embodiment of this application. Figure 5 As shown, the vehicle 500 in this embodiment includes a processor 510 and a memory 520, wherein the memory 520 stores a computer program 521 that can run on the processor 510. When the processor 510 executes the computer program 521, it implements the steps in any of the above method embodiments, for example... Figure 2 Steps 201 to 204 are shown. Alternatively, when processor 510 executes computer program 521, it implements the functions of each module / unit in the above-described device embodiments, for example... Figure 4 The functions of modules 401 to 403 are shown.

[0165] For example, computer program 521 may be divided into one or more modules / units, one or more of which are stored in memory 520 and executed by processor 510 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of computer program 521 in vehicle 500.

[0166] Those skilled in the art will understand that Figure 5 This is merely an example of a vehicle and does not constitute a limitation on the vehicle. It may include more or fewer components than shown, or combinations of certain components, or different components, such as input / output devices, network access devices, buses, etc.

[0167] The processor 510 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0168] The memory 520 can be an internal storage unit of the vehicle, such as a hard drive or memory, or an external storage device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc. The memory 520 can also include both internal and external storage devices. The memory 520 is used to store computer programs and other programs and data required by the vehicle. The memory 520 can also be used to temporarily store data that has been output or will be output.

[0169] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0170] An embodiment of this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described vehicle information output control method.

[0171] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0172] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0173] In the embodiments provided in this application, it should be understood that the disclosed devices / vehicles and methods can be implemented in other ways. For example, the device / vehicle embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0174] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0175] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0176] If the integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0177] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A vehicle information output control method, characterized in that, include: During vehicle operation, acquire vehicle operation information; Based on the vehicle operation information, at least one corresponding event is determined; Based on preset rules, the at least one event is processed to obtain the target output event; The preset rules include event mutual exclusion rules and / or event redundancy rules; the event mutual exclusion rules are used to retain at most one event among events that have a mutual exclusion relationship; the event redundancy rules are used to filter out redundant events in the at least one event; Based on the target output event, output the corresponding prompt message.

2. The vehicle information output control method according to claim 1, characterized in that, The preset rules include event mutual exclusion rules and event redundancy rules; The process of processing the at least one event based on preset rules to obtain the target output event includes: Based on the event mutual exclusion rule, mutual exclusion filtering is performed on the at least one event to obtain candidate output events; the mutual exclusion filtering is a filtering operation used to retain at most one event from events that have a mutual exclusion relationship; According to the event redundancy rule, redundant events in the candidate output events are filtered out, and the remaining events after filtering are determined as the target output events.

3. The vehicle information output control method according to claim 2, characterized in that, The step of performing mutual exclusion filtering on at least one event based on the event mutual exclusion rule to obtain candidate output events includes: If the at least one event includes multiple events, then based on the event mutual exclusion rule, it is determined whether there is a mutual exclusion relationship among the multiple events; If there is no mutual exclusion relationship among the multiple events, then each event is taken as a candidate output event; If there is a mutual exclusion relationship among the multiple events, then one event is selected from the mutually exclusive events and reserved, and the reserved event and the events that do not have a mutual exclusion relationship are selected as candidate output events.

4. The vehicle information output control method according to claim 3, characterized in that, The step of determining a reserved event from mutually exclusive events includes: Based on preset event priority rules, determine the priority of events that have a mutual exclusion relationship; Based on the priority of events with mutual exclusion relationships, the event with the highest priority is determined from the mutually exclusive events, and the event with the highest priority is selected as the reserved event.

5. The vehicle information output control method according to any one of claims 1 to 4, characterized in that, After outputting the corresponding prompt information based on the target output event, the method further includes: If an event switch is detected, determine whether there is a mutual exclusion relationship between the event before the switch and the event after the switch; If there is a mutual exclusion relationship between the pre-switching event and the post-switching event, the output of the prompt information corresponding to the pre-switching event is interrupted, and the post-switching event is determined to be the target output event according to the preset event redundancy rule. If the post-switching event is the target output event, the prompt information corresponding to the post-switching event is output. If the pre-switching event and the post-switching event are not mutually exclusive, then after the prompt information corresponding to the pre-switching event is output and after a first preset time interval, the prompt information corresponding to the post-switching event is output.

6. The vehicle information output control method according to any one of claims 2 to 4, characterized in that, The event redundancy rule includes redundancy exemption conditions and a preset redundancy duration; the redundancy exemption conditions are used to determine whether the candidate output event is not subject to the preset redundancy duration limit. The step of filtering out redundant events from the candidate output events according to the event redundancy rule, and determining the remaining events after filtering as the target output events, includes: Based on the redundancy exemption conditions, it is determined whether the candidate output event is an exemption event; the exemption event is an event in which repeated output of prompt information is allowed within the preset redundancy duration. If the candidate output event is an exemption event, then the candidate output event is determined to be the target output event; If the candidate output event is a non-exempt event, then the historical output events within a preset redundancy period are obtained, and based on the historical output events, redundant events in the candidate output events are filtered out, and the events remaining after filtering are determined as the target output events.

7. The vehicle information output control method according to claim 6, characterized in that, The step of filtering out redundant events from the candidate output events based on the historical output events, and determining the remaining events after filtering as the target output events, includes: Obtain the first event information of the candidate output event and the second event information of the historical output event; Based on the first event information and the second event information, determine whether the candidate output event and the historical output event are the same event; If the candidate output event is the same as the historical output event, then the candidate output event is determined to be a redundant event and filtered out. If the candidate output event is not the same as the historical output event, then the candidate output event is determined to be the target output event.

8. The vehicle information output control method according to any one of claims 1 to 4, characterized in that, The step of outputting corresponding prompt information based on the target output event includes: If there are multiple target output events, the multiple target output events are sorted according to a preset event priority rule to determine the event output order; According to the event output order and preset output rules, prompt information corresponding to multiple target output events is output sequentially; wherein, the output rules include that the time interval between two adjacent prompt information is greater than a second preset duration.

9. The vehicle information output control method according to claim 8, characterized in that, The process of sorting multiple target output events based on preset event priority rules to determine the event output order includes: Based on the event priority rules, the multiple target output events are sorted. If there are target output events with the same priority, the trigger time of the target output events with the same priority is obtained, and the target output events with the same priority are sorted according to the trigger time to obtain the event output order.

10. A vehicle comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the computer program, it implements the vehicle information output control method as described in any one of claims 1 to 9.

Images