Autonomous driving interaction method, computer device, storage medium and intelligent device

Abstract

The present application relates to the technical field of autonomous driving, and specifically provides an autonomous driving interaction method, a computer device, a storage medium and an intelligent device, aiming to solve the problem of autonomous driving interaction effects. In order to achieve the objective, the method provided in the present application is applied to an autonomous driving interaction engine arranged in a vehicle cockpit domain, and the method comprises: acquiring an interaction event, wherein the interaction event is an interaction event obtained by matching an autonomous driving domain of a vehicle on the basis of an event triggering condition in a preset interaction table; and presenting the interaction event by means of a preset presentation device in the cockpit domain and on the basis of event presentation logic in the preset interaction table, wherein the preset presentation device comprises a display device and / or a voice device, and a local display interface of the display device is set as an autonomous driving interaction area. On the basis of the autonomous driving interaction area, autonomous driving interaction information can be presented in various forms, and the autonomous driving interaction method is independently and flexibly upgraded, meeting the requirement of the autonomous driving interaction method for the upgrading frequency.

Description

Automatic driving interaction method, computer equipment, storage medium and intelligent device

[0001] This application claims priority to Chinese patent application No. 202311745991.1 filed on December 18, 2023, with the invention name “Autonomous driving interaction method, computer equipment, storage medium and intelligent device”. The entire contents of the above Chinese patent application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of autonomous driving technology, and in particular to an autonomous driving interaction method, computer equipment, storage medium, and intelligent device. Background Art

[0003] When a vehicle is under autonomous driving control, interactive information about the autonomous driving process is typically displayed on the instrument panel, allowing passengers to quickly and intuitively understand the vehicle's driving status. For example, if road construction is detected ahead of the vehicle, the vehicle will be controlled to slow down in advance. At this time, a text message "Construction ahead, slowing down in advance" can be displayed on the instrument panel. Passengers can immediately understand the vehicle's deceleration status and the purpose of the deceleration, improving the driving experience.

[0004] Currently, conventional autonomous driving interaction methods primarily overlay or float a new interface on top of the currently displayed interface on the dashboard when autonomous driving interaction information is needed. Because this new interface is overlaid or floats on top of the currently displayed interface, it is typically only suitable for displaying information using simple text and cannot present autonomous driving interaction information in other forms. Furthermore, because this new interface partially obscures the currently displayed interface, the new interface is typically limited in scope and cannot present complex and rich autonomous driving interaction information.

[0005] Furthermore, current conventional autonomous driving interaction methods can only be upgraded during a full vehicle FOTA (Firmware Over-The-Air) update, and cannot be independently and flexibly upgraded dynamically. To maximize the autonomous driving interaction experience, frequent upgrades to autonomous driving interaction methods may be necessary, but the frequency of full vehicle FOTA updates typically cannot meet this requirement, which may affect the autonomous driving interaction experience.

[0006] Accordingly, this field requires a new technical solution to solve the above problems. Summary of the Invention

[0007] In order to overcome the above-mentioned defects, the present application is proposed to provide an autonomous driving interaction method, computer equipment, storage medium and intelligent device that solve or at least partially solve the technical problems of how to use a variety of different expression forms to present autonomous driving interaction information to improve the information presentation effect, and how to enable autonomous driving interaction to be dynamically upgraded.

[0008] In a first aspect, an autonomous driving interaction method is provided. The method is applied to an autonomous driving interaction engine, wherein the autonomous driving interaction engine is disposed in a vehicle cockpit domain. The method comprises:

[0009] Obtaining an interaction event, where the interaction event is an interaction event obtained by matching the autonomous driving domain of the vehicle based on an event trigger condition in a preset interaction table;

[0010] Based on the event presentation logic in the preset interaction table, the interaction event is presented and processed by a presentation device preset in the cockpit domain;

[0011] Among them, the preset presentation device includes a display device and / or a voice device, and the local display interface of the display device is set as an autonomous driving interaction area, and the autonomous driving interaction area is used to display the results of the presentation processing of the interactive event.

[0012] In one technical solution of the above-mentioned autonomous driving interaction method, the presenting logic based on the event in the preset interaction table and the presentation processing of the interaction event by a preset presentation device in the cockpit domain include:

[0013] Treating the interaction event as a new event, determining whether the autonomous driving interaction engine is presenting the event logic based on the preset interaction table, and presenting other interaction events through a preset autonomous driving interaction area;

[0014] If so, compare the priorities of the new event and the other interaction events, and determine whether to present the new event according to the comparison result;

[0015] If not, the newly arrived event is directly presented and processed.

[0016] In one technical solution of the above-mentioned autonomous driving interaction method, the determining whether to present the new event based on the comparison result includes:

[0017] If the priority of the newly arrived event is greater than the priority of the other interactive events, then stop presenting the other events and present the newly arrived event instead;

[0018] If the priority of the new event is less than or equal to the priority of the other interactive events, the new event will no longer be presented.

[0019] In one technical solution of the above-mentioned autonomous driving interaction method, the method further includes: if the priority of the new event is equal to the priority of the other interaction events, replacing the step of no longer presenting the new event with the following method:

[0020] Comparing the IDs of the newly arrived event and other interaction events;

[0021] Determine whether to present the new event according to the comparison result;

[0022] The IDs of the new event and the other interactive events respectively represent the priority order of the new event and the other interactive events in the same priority level.

[0023] In one technical solution of the above-mentioned autonomous driving interaction method, the presenting logic based on the event in the preset interaction table and the presenting processing of the interaction event by a preset presentation device in the cockpit domain further include:

[0024] When presenting the interactive event through the voice device, obtaining a voice broadcast mode that matches the user of the vehicle;

[0025] Based on the event presentation logic in the preset interaction table and in accordance with the voice playback mode, the voice device is controlled to present and process the interaction event.

[0026] In one technical solution of the above-mentioned autonomous driving interaction method, before presenting the interaction event based on the event presentation logic in the preset interaction table and using a preset presentation device in the cockpit domain, the method further includes:

[0027] Obtaining the event data type of the interaction event;

[0028] If the event data type is a data table type, the interaction event is presented based on the event presentation logic in the preset interaction table and through a presentation device preset in the cockpit domain;

[0029] If the event data type is a non-data table type, obtain the preset event presentation logic that matches the event data type, and based on the matching event presentation logic, present the interactive event through the preset presentation device in the cockpit domain.

[0030] In one technical solution of the above-mentioned autonomous driving interaction method, before presenting the interaction event through a presentation device preset in the cockpit domain, the method further includes:

[0031] Taking the interaction event as a new event, determining whether the autonomous driving interaction engine is currently presenting and processing other interaction events, and whether the new event and the other interaction events have different event data types;

[0032] If so, compare the priorities of the new event and the other interaction events, and determine whether to present the new event according to the comparison result;

[0033] If not, the newly arrived event is directly presented and processed.

[0034] In one technical solution of the above-mentioned autonomous driving interaction method, the preset interaction table is stored in the autonomous driving interaction engine and the autonomous driving domain respectively. The method further includes updating the preset interaction table of the autonomous driving interaction engine in the following manner:

[0035] The autonomous driving interaction engine transmits a first version of a preset interaction table stored in the autonomous driving domain to the autonomous driving domain;

[0036] The autonomous driving interaction engine receives an update request transmitted by the autonomous driving domain, where the update request is transmitted by the autonomous driving domain to the autonomous driving interaction engine when the autonomous driving domain detects that a second version of the preset interaction table stored in the autonomous driving domain is inconsistent with the first version;

[0037] The autonomous driving interaction engine obtains and stores the preset interaction table stored in the autonomous driving domain according to the update request to complete the update of the preset interaction table stored in itself.

[0038] In one technical solution of the above-mentioned autonomous driving interaction method, the autonomous driving interaction engine obtains and stores a preset interaction table stored in the autonomous driving domain according to the update request, including:

[0039] The autonomous driving interaction engine obtains verification information of the latest version of the preset interaction table stored in the cloud server according to the update request,

[0040] and, after obtaining the verification information, sending an update response message to the autonomous driving domain, so that the autonomous driving domain can transmit the preset interaction table stored in itself to the autonomous driving interaction engine according to the update response message;

[0041] The autonomous driving interaction engine receives the preset interaction table transmitted by the autonomous driving domain, and verifies the transmitted preset interaction table according to the verification information to determine whether the transmitted preset interaction table is the latest version of the preset interaction table; if so, stores the transmitted preset interaction table; if not, does not store the transmitted preset interaction table;

[0042] Among them, the preset interaction table stored in the autonomous driving domain is the same as the latest version of the preset interaction table stored in the cloud server, and is synchronously updated following the update of the latest version of the preset interaction table.

[0043] In one technical solution of the above-mentioned autonomous driving interaction method, the receiving of the preset interaction table transmitted by the autonomous driving domain includes:

[0044] Receive serialized data formed after the autonomous driving domain serializes the preset interaction table stored in the autonomous driving domain.

[0045] In one technical solution of the above-mentioned autonomous driving interaction method, the preset interaction table is stored in the autonomous driving interaction engine and the autonomous driving domain respectively. The method further includes updating the preset interaction table of the autonomous driving interaction engine in the following manner:

[0046] The autonomous driving interaction engine obtains the latest version of the preset interaction table and its verification information stored in the cloud server;

[0047] The autonomous driving interaction engine verifies the preset interaction table stored in the autonomous driving domain according to the verification information to determine whether the preset interaction table stored in the autonomous driving domain is the latest version of the preset interaction table; if so, stores the latest version of the preset interaction table obtained from the cloud server to complete the update of the preset interaction table stored in the autonomous driving domain; if not, does not store the latest version of the preset interaction table obtained from the cloud server;

[0048] Among them, the preset interaction table stored in the autonomous driving domain is the same as the latest version of the preset interaction table stored in the cloud server, and is synchronously updated following the update of the latest version of the preset interaction table.

[0049] In one technical solution of the above-mentioned autonomous driving interaction method, the preset interaction table is stored in the autonomous driving interaction engine and the autonomous driving domain respectively. The method further includes performing fault handling in the following manner:

[0050] After a failure occurs in the autonomous driving interaction engine, the preset interaction table currently being run is switched to a preset default version of the interaction table.

[0051] And send information to the autonomous driving domain, so that the autonomous driving domain can switch its currently running preset interaction table to the preset default version of the interaction table according to the information.

[0052] In one technical solution of the above-mentioned autonomous driving interaction method, the preset interaction table is stored in the autonomous driving interaction engine and the autonomous driving domain respectively. The method further includes performing fault handling in the following manner:

[0053] The autonomous driving interaction engine receives a version switching request transmitted by the autonomous driving domain;

[0054] The autonomous driving interaction engine switches the preset interaction table currently running on the autonomous driving interaction engine to an interaction table of a preset default version according to the version switching request;

[0055] The autonomous driving domain can transmit a version switching request to the autonomous driving domain after a failure occurs in the autonomous driving domain and the preset interaction table currently running in the autonomous driving domain is switched to an interaction table of a preset default version.

[0056] In a technical solution of the above-mentioned autonomous driving interaction method, the method also includes: the autonomous driving interaction engine communicates with the autonomous driving domain based on the SOME / IP communication protocol, wherein the autonomous driving interaction engine is a server based on the SOME / IP communication protocol, and the autonomous driving domain is a client based on the SOME / IP communication protocol.

[0057] In a second aspect, a computer device is provided, which includes a processor and a storage device, wherein the storage device is suitable for storing multiple program codes, and the program codes are suitable for being loaded and run by the processor to execute the method described in any one of the technical solutions of the above-mentioned autonomous driving interaction method.

[0058] In a third aspect, a computer-readable storage medium is provided, which stores a plurality of program codes, wherein the program codes are suitable for being loaded and run by a processor to execute the method described in any one of the technical solutions of the above-mentioned autonomous driving interaction method.

[0059] In a fourth aspect, an intelligent device is provided, comprising at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program, and when the computer program is executed by the at least one processor, the method described in any one of the technical solutions of the above-mentioned autonomous driving interaction method is implemented.

[0060] The above one or more technical solutions of this application have at least one or more of the following beneficial effects:

[0061] In one technical solution for implementing the autonomous driving interaction method provided herein, the method is applied to an autonomous driving interaction engine located in a vehicle's cockpit domain. The autonomous driving interaction engine can obtain interaction events and, based on event presentation logic in a preset interaction table, present and process the interaction events via a preset presentation device within the cockpit domain. The interaction events are obtained by the vehicle's autonomous driving domain based on event trigger conditions in a preset interaction table. The preset presentation devices include a display device and / or a voice device. A local display interface of the display device is configured as an autonomous driving interaction zone, which is used to display the results of the presentation processing of the interaction events.

[0062] Because a portion of the display device's interface is designated as a separate autonomous driving interaction zone, rather than overlaying or floating a new interface on top of the original display, this separate area can display a variety of autonomous driving interaction information, including text, icons, and animations. Furthermore, since the information on the original display interface is not obscured, a larger area can be created, allowing for more complex and richer autonomous driving interaction information. Furthermore, because event trigger conditions and event presentation logic are stored in a preset interaction table, the autonomous driving interaction method can be upgraded simply by updating the preset interaction table. Updating the preset interaction table is simple and convenient. For example, replacing it with a new interaction table eliminates the need for a subsequent update during a FOTA (Function Over-The-Air) upgrade of the entire vehicle. This allows for independent and flexible upgrades of the autonomous driving interaction method, meeting the frequent upgrade requirements of the autonomous driving interaction method and improving the autonomous driving interaction experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] The disclosure of this application will become more easily understood with reference to the accompanying drawings. Those skilled in the art will readily appreciate that these drawings are for illustrative purposes only and are not intended to limit the scope of protection of this application. Among them:

[0064] FIG1 is a schematic flow chart of the main steps of an autonomous driving interaction method according to an embodiment of the present application;

[0065] FIG2 is a flow chart showing the main steps of a method for resolving conflicts that occur when presenting interactive events according to an embodiment of the present application;

[0066] 3 is a flowchart illustrating the main steps of a method for controlling a voice device to present an interactive event in different voice broadcast modes according to an embodiment of the present application;

[0067] FIG4 is a flow chart showing the main steps of a method for resolving conflicts that occur when presenting interactive events according to another embodiment of the present application;

[0068] FIG5 is a flowchart illustrating the main steps of a method for updating a preset interaction table stored in an autonomous driving interaction engine according to one embodiment of the present application;

[0069] FIG6 is a flowchart illustrating the main steps of a method for updating a preset interaction table stored in an autonomous driving interaction engine according to another embodiment of the present application;

[0070] FIG7 is a flowchart showing the main steps of a fault handling method according to an embodiment of the present application;

[0071] FIG8 is a flowchart showing the main steps of a fault handling method according to another embodiment of the present application;

[0072] FIG9 is a schematic diagram of the structural relationship between the autonomous driving interaction engine and external modules according to one embodiment of the present application;

[0073] FIG10 is a schematic diagram of internal modules of an autonomous driving interaction engine according to one embodiment of the present application;

[0074] FIG11 is a schematic diagram of the upgrade process, event triggering process, and default version switching process of the autonomous driving interaction engine structure shown in FIG9 and FIG10;

[0075] FIG12 is a schematic diagram of an event triggering process according to an embodiment of the present application;

[0076] FIG13 is a schematic diagram of an event triggering process according to another embodiment of the present application;

[0077] FIG14 is a schematic diagram of the main process of voice broadcasting based on the interactive table processing in the process shown in FIG12;

[0078] FIG15 is a schematic diagram of a default version switching process according to an embodiment of the present application;

[0079] FIG16 is a schematic diagram of an autonomous driving interaction area provided in the upper left area of ​​an instrument panel according to one embodiment of the present application;

[0080] FIG17 is a schematic diagram of an autonomous driving interaction area provided in the bottom area of ​​a dashboard according to one embodiment of the present application;

[0081] FIG18 is a schematic diagram of the main structure of a computer device according to an embodiment of the present application.

[0082] FIG19 is a schematic diagram of the main structure of a smart device according to an embodiment of the present application.

[0083] List of reference numerals:

[0084] 11: Storage device; 12: Processor; 21: Memory; 22: Processor. DETAILED DESCRIPTION

[0085] Some embodiments of the present application are described below with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are only used to explain the technical principles of the present application and are not intended to limit the scope of protection of the present application.

[0086] In the description of this application, a "processor" may include hardware, software, or a combination of the two. A processor may be a central processing unit, a microprocessor, an image processor, a digital signal processor, or any other suitable processor. A processor has data and / or signal processing capabilities. A processor may be implemented in software, hardware, or a combination of the two. Computer-readable storage media include any suitable medium capable of storing program code, such as a magnetic disk, a hard disk, an optical disk, flash memory, read-only memory, random access memory, and the like.

[0087] The relevant user personal information that may be involved in the various embodiments of this application is strictly in accordance with the requirements of laws and regulations, following the principles of legality, legitimacy and necessity, and based on the reasonable purposes of business scenarios, to process the personal information that users actively provide during the use of products / services or generated due to the use of products / services, as well as the personal information obtained with the user's authorization.

[0088] The user personal information processed by this application will vary depending on the specific product / service scenario and must be based on the specific scenario in which the user uses the product / service. This may involve the user's account information, device information, driving information, vehicle information, or other related information. This application will treat the user's personal information and its processing with a high degree of diligence.

[0089] This application attaches great importance to the security of user personal information and has taken reasonable and feasible security protection measures that comply with industry standards to protect user information and prevent personal information from being accessed, disclosed, used, modified, damaged or lost without authorization.

[0090] The following describes an embodiment of the autonomous driving interaction method provided in this application.

[0091] The autonomous driving interaction method of the embodiment of the present application can be applied to an autonomous driving interaction engine set in the vehicle cockpit domain. The vehicle is also provided with an autonomous driving domain. A preset interaction table is stored in both the autonomous driving interaction engine and the autonomous driving domain, and autonomous driving interaction can be performed based on this preset interaction table. This preset interaction table includes event triggering conditions and event presentation logic. Different interaction events correspond to different event triggering conditions and also correspond to different event presentation logic. According to the event triggering conditions, it is possible to obtain which interaction events have occurred, and according to the event presentation logic, the interaction events can be presented, so that the vehicle user can understand the autonomous driving status of the vehicle in a timely and intuitive manner.

[0092] Specifically, referring to FIG1 , FIG1 is a schematic flow chart of the main steps of the autonomous driving interaction method according to an embodiment of the present application. As shown in FIG1 , the autonomous driving interaction method in the embodiment of the present application mainly includes the following steps S101 to S102.

[0093] Step S101: Obtain an interaction event, where the interaction event is an interaction event obtained by matching the vehicle's automatic driving domain with event triggering conditions in a preset interaction table.

[0094] The autonomous driving domain can match event trigger conditions based on information from the vehicle's autonomous driving process. If certain information successfully matches the event trigger conditions of a specific interaction event, this indicates that the interaction event has occurred. Each time the autonomous driving domain matches an interaction event, it can transmit this interaction event to the autonomous driving interaction engine, allowing the autonomous driving interaction engine to present and process the interaction event in a timely manner. For example, if the autonomous driving domain determines from information during the autonomous driving process that there is road construction ahead of the vehicle and that the vehicle is slowing down, matching the event trigger conditions based on these two pieces of information can determine that an interaction event has occurred, indicating that the vehicle has slowed down due to the construction, and immediately transmit this interaction event to the autonomous driving interaction engine.

[0095] Step S102: Based on the event presentation logic in the preset interaction table, the interaction event is presented and processed through the preset presentation device in the cockpit domain.

[0096] The preset presentation device may include a display device and / or a voice device. The display device has a display interface, and a local area of ​​this display interface (i.e., a local display interface) is designated as an autonomous driving interaction zone. The autonomous driving interaction zone may be used to display the results of the presentation processing of the interactive event. One or more local display interfaces may be configured for the same display device. This embodiment does not specifically limit the number or location of these local display interfaces.

[0097] In addition, the preset presentation device may include a separate display device and a separate voice device, or may include a device that integrates both display and voice functions.

[0098] When the interactive event is presented and processed through a preset presentation device, the interactive event can be displayed in the form of text, icons, animations, etc. through the display device, or the interactive event can be output in the form of voice playback through the voice device.

[0099] It should be noted that those skilled in the art can flexibly set the specific content of the event triggering conditions corresponding to different interactive events and the specific content of the event presentation logic corresponding to different interactive events according to actual needs. This embodiment does not specifically limit the above content.

[0100] In the method based on steps S101 to S102 above, the autonomous driving interaction zone is not a new interface superimposed or floating on the existing display interface of the display device. Therefore, this separate autonomous driving interaction zone can display a variety of autonomous driving interaction information, such as text, icons, and animations. Furthermore, because the information on the existing display interface is not obscured, a larger autonomous driving interaction zone can be set, thereby presenting more complex and rich autonomous driving interaction information. Furthermore, the preset interaction table stores event triggering conditions and event presentation logic. Therefore, the autonomous driving interaction method can be upgraded simply by updating the preset interaction table. Updating the preset interaction table is simple and convenient. For example, replacing it with a new interaction table eliminates the need for updating it during a FOTA (Function Over-The-Air) upgrade of the entire vehicle. This allows for independent and flexible upgrades of the autonomous driving interaction method, meeting the upgrade frequency requirements of the autonomous driving interaction method and improving the autonomous driving interaction experience.

[0101] In one application scenario according to an embodiment of the present application, the autonomous driving interaction method according to an embodiment of the present application can be configured on a vehicle, for example, by installing a device capable of executing the method. During the vehicle's autonomous driving process, the method can intuitively, promptly, and accurately present autonomous driving interaction information, allowing the vehicle user to promptly understand the vehicle's driving status. In particular, if the user needs to take over the vehicle, the user can do so promptly after viewing the presented information, ensuring the safety and reliability of the vehicle's driving.

[0102] The above step S102 is further explained below.

[0103] In some implementations of step S102, when presenting and processing interactive events based on the event presentation logic in the preset interaction table and through the preset presentation device in the cockpit domain, it may be encountered that the autonomous driving interaction engine is presenting and processing other interactive events, thereby causing a conflict. In this case, this conflict can be arbitrated through the following steps S201 to S204 shown in Figure 2.

[0104] Step S201: Treat the interaction event as a new event.

[0105] For each interaction event obtained from the autonomous driving domain, each interaction event is sequentially treated as a new event and arbitrated through subsequent steps S202 to S204.

[0106] Step S202: Determine whether the autonomous driving interaction engine is currently presenting other interaction events based on the event presentation logic in the preset interaction table and using the preset autonomous driving interaction zone. If so, a conflict exists, and the process proceeds to step S203. If not, a conflict does not exist, and the process proceeds to step S204.

[0107] Step S203: comparing the priorities of the new event and the other interactive events, and determining whether to perform presentation processing on the new event based on the comparison result.

[0108] A higher priority indicates a higher level of importance or urgency, and thus requires preferential presentation processing. In this embodiment, based on the comparison results, an event with a higher priority can be obtained and presented. It should be noted that those skilled in the art can flexibly set the priorities of different interactive events based on actual needs, and this embodiment does not specifically limit this.

[0109] Step S204: Directly present the newly arrived event.

[0110] Based on the method described in steps S201 to S204 above, when the autonomous driving interaction engine is presenting and processing other interaction events and a conflict occurs, the priority of the interaction events is used to select interaction events that are more important or urgent for vehicle driving to be presented.

[0111] The above step S203 is further explained below.

[0112] In some implementations of the above step S203, when determining whether to present and process the new event based on the result of the priority comparison, if it is determined that the priority of the new event is greater than the priority of other interactive events, it indicates that the new event is more important or urgent to the vehicle's travel, so the presentation and processing of other events can be stopped, and the new event can be presented and processed; if it is determined that the priority of the new event is less than or equal to the priority of other interactive events, it indicates that the other events currently being processed are still more important or urgent to the vehicle's travel and need to continue to be processed, and the new event can be discarded, so the new event can no longer be presented and processed. Based on the above implementation, interactive events that are more important or urgent to the vehicle's travel can be selected for presentation based on the size of the priority.

[0113] In other embodiments of the above-mentioned step S203, when judging whether to present and process the new event according to the result of the priority comparison, the processing method when the priority of the new event is greater than the priority of other interactive events, and the processing method when the priority of the new event is less than the priority of other interactive events are respectively the same as the methods in the aforementioned embodiments, and the main difference lies in the processing method when the priorities are equal. Among them, the processing method when the priorities are equal may include: obtaining the IDs of the new event and other interactive events, and these two IDs respectively represent the priority order of the new event and other interactive events in the same priority level. Then, the IDs of the new event and other interactive events are compared, and whether to present and process the new event is judged according to the result of the comparison. Based on this, autonomous driving interaction can still be reliably completed when the priority levels are equal.

[0114] In some embodiments, a larger ID indicates a higher priority. If the ID of a new event is larger than the IDs of other interactive events, then the presentation processing of other events can be stopped, and the presentation processing of the new event can be performed; if the ID of the new event is smaller than the IDs of other interactive events, then the presentation processing of the new event can be stopped. Similarly, a smaller ID indicates a higher priority. If the ID of a new event is smaller than the IDs of other interactive events, then the presentation processing of other events can be stopped, and the presentation processing of the new event can be performed; if the ID of a new event is larger than the IDs of other interactive events, then the presentation processing of the new event can be stopped.

[0115] It should be noted that those skilled in the art can flexibly set the IDs of different interaction events in the same priority level according to actual needs, and this embodiment does not specifically limit this.

[0116] In some implementations of step S102, when the interactive event is presented and processed through a voice device, the interactive event can be presented and processed using different voice playback methods according to different vehicle users through the following steps S301 to S302 shown in Figure 3.

[0117] Step S301: When presenting an interactive event through a voice device, a voice broadcast method that matches the user of the vehicle is obtained.

[0118] The vehicle's cockpit domain can be pre-set with a voice broadcast mode that matches the current vehicle user, and the autonomous driving interaction engine can directly obtain the voice broadcast mode from the cockpit domain.

[0119] In addition, the vehicle's cockpit area can be pre-configured with multiple voice announcement modes for users to choose from. Users can select a voice announcement mode that matches the vehicle's user. For example, the voice announcement modes can include a novice announcement mode and an experienced announcement mode. The novice announcement mode can be more detailed when announcing interactive events, while the experienced announcement mode can be more concise when announcing interactive events.

[0120] Step S302: Based on the event presentation logic in the preset interaction table and in accordance with the voice playback mode, the voice device is controlled to present and process the interaction event.

[0121] Based on the method described in steps S301 to S302 above, different voice broadcasting methods can be used to broadcast interaction events for different vehicle users, which helps to improve the experience of autonomous driving interaction.

[0122] In some implementations of step S102 , interactive events with different event data types can be compatibly processed through the following steps S401 to S403 shown in FIG. 4 .

[0123] Step S401: Acquire the event data type of the interaction event.

[0124] Event data types can include data table types and non-data table types. A data table type refers to an interactive event using a data table structure, while a non-data table type refers to an interactive event using a data structure other than a data table structure. Persons skilled in the art can flexibly determine the data structure of a non-data table type based on actual needs, and this embodiment does not impose any specific limitations thereon.

[0125] If the type of the current interaction event is a data table type, go to step S402; if the type of the current interaction event is a non-data table type, go to step S403.

[0126] Step S402: Based on the event presentation logic in the preset interaction table, the interaction event is presented and processed through the preset presentation device in the cockpit domain.

[0127] The event triggering conditions and event presentation logic in the preset interaction table also adopt the data table structure. Therefore, when the type of the current interaction event is a data table type, presentation processing can be performed normally based on the preset interaction table.

[0128] Step S403: Obtain preset event presentation logic that matches the event data type, and present the interactive event based on the matching event presentation logic and through a preset presentation device in the cockpit domain.

[0129] If the current interaction event type is not a data table type, it will not be rendered normally based on the preset interaction table. To solve this problem, you can pre-set event rendering logic that matches this non-data table type and then directly call this event rendering logic for rendering.

[0130] In some implementations, because the preset interaction table offers high update flexibility and independence, interaction events that require frequent presentation updates can be configured as data table-type events, while interaction events that do not require frequent presentation updates can be configured as non-data table-type events. This embodiment does not specifically limit how to categorize update frequencies; as long as it can distinguish whether frequent updates are required, it is sufficient.

[0131] Based on the method described in steps S401 to S403 above, not only can data table type interaction events be presented and processed based on the preset interaction table, but non-data table types can also be compatible, thereby increasing the application scope of autonomous driving interaction and helping to improve the experience of autonomous driving interaction.

[0132] In some implementations of the above steps S402 and S403, when presenting interactive events through a preset presentation device in the cockpit domain, it may be encountered that the autonomous driving interactive engine is presenting and processing interactive events of other event data types, thereby causing a conflict. In this case, this conflict can be arbitrated through the following steps 11 to 14.

[0133] Step 11: Treat the interaction event as a new arrival event.

[0134] For each interaction event obtained from the autonomous driving domain, each interaction event is sequentially treated as a new event and arbitrated through subsequent steps 12 to 14.

[0135] Step 12: Determine whether the autonomous driving interaction engine is presenting and processing other interaction events, and whether the event data type of the new event is different from that of other interaction events; if so, go to step 13; if not, go to step 14.

[0136] Step 13: Compare the priorities of the new event and other interactive events, and determine whether to present the new event based on the comparison result.

[0137] A higher priority indicates a higher level of importance or urgency, and thus requires preferential presentation processing. In this embodiment, based on the comparison results, an event with a higher priority can be obtained and presented. It should be noted that those skilled in the art can flexibly set the priorities of different interactive events based on actual needs, and this embodiment does not specifically limit this.

[0138] When the event data type only includes data table type and non-data table type, the two types can be set to different priorities, and there is no situation where the priorities are the same.

[0139] Step 14: Directly process the newly arrived event.

[0140] Based on the method described in steps 11 to 14 above, when the autonomous driving interaction engine is presenting and processing other interaction events and a conflict occurs, the priority of the interaction events is used to select interaction events that are more important or urgent for vehicle driving to be presented.

[0141] The following describes a method for updating the preset interaction table in an embodiment of the present application.

[0142] In the autonomous driving interaction method according to an embodiment of the present application, preset interaction tables are respectively stored in the autonomous driving interaction engine and the autonomous driving domain.

[0143] In some embodiments, the preset interaction table of the autonomous driving interaction engine can be updated through the following steps S501 to S503 shown in Figure 5.

[0144] Step S501: The autonomous driving interaction engine transmits the first version of the preset interaction table stored in itself to the autonomous driving domain.

[0145] Step S502: The autonomous driving interaction engine receives an update request transmitted by the autonomous driving domain. The update request is transmitted to the autonomous driving interaction engine when the autonomous driving domain detects that the second version of the preset interaction table stored in itself is inconsistent with the first version.

[0146] If the versions of the preset interaction table in the autonomous driving domain and the preset interaction table in the autonomous driving interaction engine are inconsistent, it indicates that the preset interaction table in the autonomous driving interaction engine needs to be updated. Therefore, when the first and second versions are inconsistent, the autonomous driving domain will send an update request to the autonomous driving interaction engine, allowing the autonomous driving interaction engine to update its own preset interaction table.

[0147] Step S503: The autonomous driving interaction engine obtains and stores the preset interaction table stored in the autonomous driving domain according to the update request to complete the update of the preset interaction table stored in itself.

[0148] In this embodiment, the preset interaction table for the autonomous driving domain can be used as the latest version of the interaction table, and the autonomous driving interaction engine can be updated based on the preset interaction table for the autonomous driving domain. After the autonomous driving interaction engine stores the preset interaction table for the autonomous driving domain, if the vehicle is currently operating or in autonomous driving mode, it can temporarily disable this preset interaction table and re-enable it after the vehicle next operates or exits autonomous driving mode.

[0149] Based on the method described in steps S501 to S503 above, the preset interaction table stored in the autonomous driving domain can be used to update the preset interaction table of the autonomous driving interaction engine, thereby improving the convenience of updating.

[0150] The above step S503 is further explained below.

[0151] In some implementations of the above-mentioned step S503, the preset interaction table stored in the autonomous driving domain can be obtained and stored through the following steps S5031 to S5033.

[0152] Step S5031: The autonomous driving interaction engine obtains the verification information of the latest version of the preset interaction table stored in the cloud server based on the update request.

[0153] The verification information may be MD5 verification information obtained by processing the latest version of the preset interaction table using an MD5 Message Digest Algorithm.

[0154] In addition, in this embodiment, other conventional verification information setting methods may also be used to set the verification information of the latest version of the preset interaction table, as long as it is possible to determine whether a preset interaction table is the current latest version of the preset interaction table based on the verification information.

[0155] Step S5032: After obtaining the verification information, the autonomous driving interaction engine sends an update response message to the autonomous driving domain, so that the autonomous driving domain can transmit the preset interaction table stored in itself to the autonomous driving interaction engine according to the update response information.

[0156] When the autonomous driving domain receives the update response information, it indicates that the autonomous driving interaction engine is ready to update the preset interaction table. Therefore, the autonomous driving domain can transmit the preset interaction table stored in the autonomous driving domain to the autonomous driving interaction engine.

[0157] The preset interaction table stored in the autonomous driving domain is identical to the latest version of the preset interaction table stored in the cloud server and is updated synchronously with updates to the latest version of the preset interaction table. In other words, the preset interaction table in the autonomous driving domain is dynamically updated with the cloud server, and its version is almost always the latest or maintained at the latest version.

[0158] Step S5033: The autonomous driving interaction engine receives the preset interaction table transmitted by the autonomous driving domain, and verifies the transmitted preset interaction table according to the verification information to determine whether the transmitted preset interaction table is the latest version of the preset interaction table.

[0159] If so, it indicates that the preset interaction table transmitted from the autonomous driving domain is indeed the latest version. Therefore, the transmitted preset interaction table can be stored to ensure that both the autonomous driving domain and the autonomous driving engine store the latest version of the preset interaction table.

[0160] If not, this indicates that the preset interaction table transmitted by the autonomous driving domain is not the latest version and needs to be updated. Therefore, the transmitted preset interaction table is not stored. Furthermore, since the autonomous driving domain dynamically updates with the cloud server, after the autonomous driving domain is updated, it and the autonomous driving interaction engine can still update the preset interaction table of the autonomous driving interaction engine through steps S501 to S503.

[0161] In some embodiments, the autonomous driving domain may receive serialized data generated by serializing a preset interaction table stored in the domain. This serialization process can compress the data volume of the preset interaction table, reducing the burden of transmitting the preset interaction table. After receiving the serialized data, the autonomous driving interaction engine may deserialize it to obtain the preset interaction table. In some embodiments, a FlatBuffer-based serialization and deserialization method may be employed. Furthermore, other conventional serialization and deserialization methods may also be employed in this embodiment, and this embodiment does not specifically limit these methods.

[0162] Based on the method described in steps S5031 to S5033 above, it can be ensured that the preset interaction table after the autonomous driving engine is updated is consistent with the preset interaction table of the autonomous driving domain, and both are the latest versions.

[0163] In some embodiments, the preset interaction table of the autonomous driving interaction engine may also be updated through the following steps S601 to S603 shown in FIG6 .

[0164] Step S601: The autonomous driving interaction engine obtains the latest version of the preset interaction table and its verification information stored in the cloud server. The verification information is the same as the verification information in step S5031.

[0165] Step S602: The autonomous driving interaction engine verifies the preset interaction table stored in the autonomous driving domain according to the verification information to determine whether the preset interaction table stored in the autonomous driving domain is the latest version of the preset interaction table.

[0166] The preset interaction table stored in the autonomous driving domain is the same as the latest version of the preset interaction table stored in the cloud server, and is updated synchronously with the update of the latest version of the preset interaction table.

[0167] This step is similar to the related method of the aforementioned step S5033 and will not be repeated here.

[0168] Step S603: Update according to the verification result.

[0169] If the preset interaction table stored in the autonomous driving domain is the latest version of the preset interaction table, the latest version of the preset interaction table obtained from the cloud server is stored to complete the update of the preset interaction table stored in itself; otherwise, the latest version of the preset interaction table obtained from the cloud server is not stored.

[0170] Based on the method described in steps S601 to S603 above, it can also be ensured that the preset interaction table after the autonomous driving engine is updated is consistent with the preset interaction table of the autonomous driving domain, and both are the latest versions.

[0171] The following describes a method for handling a fault that occurs in an embodiment of the present application.

[0172] In some embodiments, if a fault occurs in the autonomous driving interaction engine, the fault can be handled through the following steps S701 to S702 shown in Figure 7.

[0173] Step S701: After a failure occurs in the autonomous driving interaction engine, the autonomous driving interaction engine switches the preset interaction table it is running to a preset default version of the interaction table.

[0174] Those skilled in the art can flexibly select a version as the preset default version according to actual needs. This embodiment does not specifically limit the preset default version.

[0175] The preset interaction table for the autonomous driving interaction engine is stored in a preset area. When performing autonomous driving interactions based on the preset interaction table, the autonomous driving interaction engine retrieves or reads information from this preset interaction table. Possible failures of the autonomous driving interaction engine include failures to read information from the preset interaction table. Other possible failures include crashes and restarts of the autonomous driving interaction engine or the cockpit domain.

[0176] Step S702: The autonomous driving interaction engine sends information to the autonomous driving domain, so that the autonomous driving domain can also switch its currently running preset interaction table to a preset default version of the interaction table based on the information.

[0177] After receiving information from the autonomous driving interaction engine, the autonomous driving domain can determine that the autonomous driving interaction engine has switched to the preset interaction table. Because the autonomous driving domain and the autonomous driving interaction engine respectively complete autonomous driving interactions based on the event triggering conditions and event presentation logic in the preset interaction table, the preset interaction tables in the autonomous driving domain and the autonomous driving interaction engine must be consistent. If the autonomous driving interaction engine switches the preset interaction table, the autonomous driving domain must also switch the preset interaction table synchronously.

[0178] Based on the method described in steps S701 to S702 above, it can be ensured that autonomous driving interaction can still be performed reliably after a failure of the autonomous driving interaction engine occurs.

[0179] In some implementations, if a fault occurs in the autonomous driving domain, the fault may be handled through the following steps S801 to S802 shown in FIG8 .

[0180] Step S801: The autonomous driving interaction engine receives a version switching request transmitted by the autonomous driving domain.

[0181] After a fault occurs in the autonomous driving domain, it switches its currently running preset interaction table to a preset default version of the interaction table and transmits a version switch request to the autonomous driving domain. Those skilled in the art can flexibly select a version as the preset default version based on actual needs; this embodiment does not specifically limit the preset default version. The preset interaction table for the autonomous driving domain is stored in a preset area. When autonomous driving interactions are performed based on the preset interaction table, the autonomous driving domain obtains or reads information from this preset area. Possible faults in the autonomous driving domain include failures to read information from the preset interaction table. Possible faults may also include crashes and restarts of the autonomous driving domain.

[0182] Step S802: The autonomous driving interaction engine switches its currently running preset interaction table to an interaction table of a preset default version according to the version switching request.

[0183] Because the autonomous driving domain and the autonomous driving interaction engine complete autonomous driving interactions based on the event triggering conditions and event presentation logic in the preset interaction table, the preset interaction table of the autonomous driving domain and the autonomous driving interaction engine must be consistent. If the autonomous driving domain changes the preset interaction table, the autonomous driving engine must also change the preset interaction table synchronously.

[0184] Based on the method described in steps S801 to S802 above, it can be ensured that autonomous driving interaction can be performed reliably even after a failure occurs in the autonomous driving domain.

[0185] The following describes the communication method between the autonomous driving interaction engine and the autonomous driving domain in the embodiment of the present application.

[0186] In some embodiments, the autonomous driving interaction engine can communicate with the autonomous driving domain based on the SOME / IP communication protocol, where the autonomous driving interaction engine serves as a server based on the SOME / IP communication protocol, and the autonomous driving domain serves as a client based on the SOME / IP communication protocol. The SOME / IP communication protocol is a conventional communication protocol in the field of communications technology, and this embodiment does not elaborate on its content or the communication process between the autonomous driving interaction engine and the autonomous driving domain.

[0187] The following is a brief description of the autonomous driving interaction method of the embodiment of the present application in conjunction with Figures 9 to 17.

[0188] First, refer to Figures 9 and 10. Figure 9 illustrates the connection relationship between the autonomous driving interaction engine and external modules, while Figure 10 illustrates the main structural diagram of the internal modules of the autonomous driving interaction engine. As shown in Figure 9, the vehicle cockpit domain utilizes a combined architecture of the QNX and Android operating systems, with the autonomous driving interaction engine located in the QNX. The autonomous driving interaction engine can connect to the IC module, HUD module, and Audio module, all located in the QNX. The autonomous driving interaction engine also communicates with the hypervisor using the SOME / IP and CAN communication protocols, respectively. The hypervisor communicates with the firmware in the cockpit domain using the SOME / IP communication protocol. QNX also includes a WTI service module, which can control a display device to overlay or float a new interface on its display interface, displaying information through this new interface. Android includes the NasCore module, the Thor module, and the smart device service module. The autonomous driving interaction engine connects to the NasCore module, which in turn connects to the TSP module. The smart device service can control the display and / or broadcast of information on a device that integrates both display and voice capabilities.

[0189] As shown in Figure 10, the autonomous driving interaction engine may include a data executor, a data arbitrator, a SOME / IP parser, an initialization processor, a data persistence manager, and an MD5 checksum processor. The data executor can control the presentation device to present interaction events, the data arbitrator can be used to execute the methods for arbitrating conflicts described in the aforementioned method embodiments, the SOME / IP parser can obtain data communicated based on the SOME / IP communication protocol, the initialization processor can initialize the autonomous driving interaction engine, the data persistence manager can persistently store a preset interaction table, and the MD5 checksum processor can obtain MD5 checksum information and verify the preset interaction table transmitted from the autonomous driving domain based on the MD5 checksum information.

[0190] Continuing with Figure 11, Figure 11 illustrates the upgrade process, event triggering process, and default version switching process involved in autonomous driving interaction based on the aforementioned autonomous driving interaction engine. The following briefly describes each of these three processes.

[0191] 1. Upgrade process

[0192] As shown in Figure 11, the autonomous driving interaction engine, located in QNX, broadcasts the first version of its preset interaction table to the autonomous driving domain (AD) using the SOME / IP communication protocol. Upon detecting that the second version of its preset interaction table is inconsistent with the first version, the AD requests an update from the autonomous driving interaction engine. Since the autonomous driving interaction engine resides in QNX, it obtains verification information for the latest version of the interaction table from the PLM system via QNX and then Android. Upon receiving this verification information, it responds to the AD, indicating that the autonomous driving interaction engine is ready for the update. Upon receiving the response, the AD transmits the serialized interaction table, resulting from serializing the preset interaction table, to the autonomous driving interaction engine. The autonomous driving interaction engine deserializes the serialized interaction table to obtain the preset interaction table, verifies the preset interaction table based on the verification information, persistently stores the verified preset interaction table, and then responds to the AD, indicating that the autonomous driving interaction engine has completed the storage. The next time the vehicle starts running, the autonomous driving interaction engine activates this preset interaction table.

[0193] 2. Event triggering process

[0194] Referring again to FIG. 11 , the AD transmits an interaction event to the autonomous driving interaction engine. The autonomous driving interaction engine determines whether other interaction events are currently running. If so, it performs arbitration and controls the presentation device in the cockpit domain to perform presentation processing based on the result of the arbitration.

[0195] Further, referring to FIG12, FIG12 exemplifies a method flow for arbitrating conflicts when presenting interactive events based on a preset interactive table. As shown in FIG12, the autonomous driving interactive engine receives a newly arrived interactive event (i.e., a new event), queries the preset interactive table, and determines whether other interactive events are running. When other interactive events are running, it is determined whether the priority of the new event is equal to that of the other interactive event. If the priorities are equal, it is determined whether the ID of the new event (i.e., the trigger ID in FIG12) is greater than the ID of the other interactive event (i.e., the running ID in FIG12). If the trigger ID is greater than the running ID, the signal data is parsed based on the interactive table, and text information and image / time information are obtained according to the parsing results. These information are transmitted to the HMI for presentation, completing the presentation of the new event. If the trigger ID is less than the running ID, the new event is discarded and no presentation processing is performed on the new event. If the priorities are not equal, determine whether the priority of the new event is greater than the priority of the other interactive events (i.e., determine whether the trigger priority is greater than the running priority in Figure 12); if so, parse the signal data based on the interactive table, obtain text information and image / time information based on the analysis results, and transmit this information to the HMI for presentation, completing the presentation processing of the new event; otherwise, discard the new event and do not present it. If no other interactive events are running, parse the signal data based on the interactive table, obtain text information and image / time information based on the analysis results, and transmit this information to the HMI for presentation, completing the presentation processing of the new event.

[0196] Further, referring to Figure 13, Figure 13 illustrates a method flow for presenting and processing interaction events of different event data types. As shown in Figure 13, the autonomous driving interaction engine receives interaction events transmitted from the AD based on the SOME / IP communication protocol. The main logic processor in the autonomous driving interaction engine processes this interaction event, which includes multiple event segments. n in Figure 12 represents the sequence number of the event segments. The main logic processor first sets n = 0, then copies the interaction event, obtains the field representing the event data type in the nth event segment, and uses this field to determine whether the event data type is a data table type. If it is a data table type, the table arbitration processor in the autonomous driving interaction engine presents and processes this event segment based on a preset interaction table. If it is not a data table type, the HMI arbitration processor in the autonomous driving interaction engine presents and processes this event segment. The processing methods of the table arbitration processor and the HMI arbitration processor can refer to the processing methods for interaction events of data table type and non-data table type in the aforementioned method embodiments. After the table arbitration processor or HMI arbitration processor completes the presentation processing of the nth event segment, set n=n+1 and determine whether the updated n is less than the maximum number of event segments contained in the interactive event size; if so, end the presentation processing of this interactive event; if not, re-acquire the field representing the event data type in the updated nth event segment and the subsequent steps until n <size。

[0197] Further, referring to Figure 14, Figure 14 illustrates a method flow for presenting interactive events using different voice playback methods for different vehicle users. As shown in Figure 14, the autonomous driving interaction engine receives the interaction event ID, parses the signal data based on the interaction table, obtains the voice information based on the parsed result, and sends it to the NasCore module located on Android. The NasCore module then transmits it to the Thor module (i.e., the Thor app in Figure 14). The Thor module obtains the voice broadcast method that matches the vehicle user from the settings app, transmits the voice information and voice broadcast method to the TTS engine for voice broadcast, completing the broadcast of this interactive event.

[0198] 3. Default version switching process

[0199] Referring again to Figure 11, the autonomous driving interaction engine and the autonomous driving domain each run two different versions of the preset interaction table: one version for normal use and the other (the default version) as a backup. If a failure occurs in the autonomous driving interaction engine or the autonomous driving domain, the normal version is switched to the backup version. As shown in Figure 11, after a failure occurs, the autonomous driving domain switches from the normal version to the backup version and simultaneously sends a version switch request to the autonomous driving interaction engine. The autonomous driving interaction engine, in response to this request, also switches the preset interaction table version to the backup version and responds to the autonomous driving domain after the switch.

[0200] Further, referring to Figure 15, FIG15 illustrates an exemplary state diagram of the autonomous driving interaction engine when switching between preset interaction tables. As shown in FIG15, upon startup and initialization, the autonomous driving interaction engine sets its state to normal. If the autonomous driving interaction engine switches between preset interaction table versions, it sets its state to abnormal, and then returns to normal after the switch is complete. In abnormal state, the autonomous driving interaction engine cannot present or process interaction events.

[0201] 16 and 17 , FIG16 exemplarily shows an autonomous driving interaction area set on the display interface in the upper left area of ​​the instrument panel, and FIG17 exemplarily shows an autonomous driving interaction area set on the bottom display interface on the instrument panel. Through the method in the aforementioned embodiment, autonomous driving interaction information in various situations such as text, icons, and progress bars can be displayed in these two autonomous driving interaction areas, so that vehicle users can intuitively understand the autonomous driving status of the vehicle.

[0202] It should be pointed out that although the various steps in the above embodiments are described in a specific order, those skilled in the art will understand that in order to achieve the effect of the present application, different steps do not have to be performed in such an order. They can be performed simultaneously (in parallel) or in other orders. These adjusted solutions are equivalent to the technical solutions described in this application, and therefore will also fall within the scope of protection of this application.

[0203] It will be understood by those skilled in the art that all or part of the processes in the method for implementing the above embodiment of the present application can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it can implement the steps of each of the above method embodiments. The computer program includes computer program code, which can be in source code form, object code form, executable file or some intermediate form. The computer-readable storage medium can include: any entity or device, medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory, random access memory, electric carrier signal, telecommunication signal and software distribution medium that can carry the computer program code. It should be noted that the content contained in the computer-readable storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable storage media do not include electric carrier signals and telecommunication signals.

[0204] Another aspect of the present application provides a computer device.

[0205] In an embodiment of a computer device according to the present application, the computer device primarily includes a storage device and a processor. The storage device may be configured to store a program for executing the autonomous driving interaction method of the aforementioned method embodiment, and the processor may be configured to execute the program in the storage device, including but not limited to a program for executing the autonomous driving interaction method of the aforementioned method embodiment. Referring to FIG. 18 , FIG. 18 exemplarily illustrates a storage device 11 and a processor 12 communicating via a bus. For ease of illustration, only the portions relevant to this embodiment are shown. For specific technical details not disclosed, please refer to the method section of the present application embodiment.

[0206] In some possible implementations, a computer device may include multiple storage devices and multiple processors. The multiple processors may be processors deployed on the same device. For example, the computer device may be a high-performance device composed of multiple processors, and the multiple processors may be processors configured on the high-performance device. Furthermore, the multiple processors may be processors deployed on different devices. For example, the computer device may be a server cluster, and the multiple processors may be processors on different servers in the server cluster.

[0207] Another aspect of the present application provides a computer-readable storage medium.

[0208] In an embodiment of a computer-readable storage medium according to the present application, the computer-readable storage medium can be configured to store a program for executing the autonomous driving interaction method of the above-mentioned method embodiment. The program can be loaded and executed by a processor to implement the above-mentioned autonomous driving interaction method. For ease of explanation, only the parts related to the embodiment of the present application are shown. For specific technical details not disclosed, please refer to the method section of the embodiment of the present application. The computer-readable storage medium can be a storage device formed by various electronic devices. Optionally, the computer-readable storage medium in the embodiment of the present application is a non-transitory computer-readable storage medium.

[0209] Another aspect of the present application provides a smart device.

[0210] In an embodiment of an intelligent device according to the present application, the intelligent device may include at least one processor; and a memory communicatively connected to the at least one processor; wherein a computer program is stored in the memory, and when the computer program is executed by the at least one processor, the method described in any of the above embodiments is implemented. The intelligent device described in the present application may include driving devices, smart cars, robots and other devices. Referring to Figure 19, Figure 19 exemplarily shows that the memory 21 and the processor 22 are communicatively connected via a bus. In some embodiments of the present application, the intelligent device may also include at least one sensor, which is used to perceive information. The sensor is communicatively connected to any type of processor mentioned in the present application. Optionally, the intelligent device may also include an autonomous driving system, which is used to guide the intelligent device to drive independently or assist in driving. The processor communicates with the sensor and / or the autonomous driving system to complete the method described in any of the above embodiments.

[0211] Thus far, the technical solution of the present application has been described in conjunction with an embodiment shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of the present application is obviously not limited to these specific embodiments. Without departing from the principles of the present application, those skilled in the art may make equivalent changes or substitutions to the relevant technical features, and the technical solutions after such changes or substitutions will fall within the scope of protection of the present application.

Claims

1. An autonomous driving interaction method, characterized in that: The method is applied to an autonomous driving interaction engine, and the autonomous driving interaction engine is arranged in a cockpit domain of a vehicle. The method comprises: Obtaining an interaction event, where the interaction event is an interaction event obtained by matching the automatic driving domain of the vehicle based on an event trigger condition in a preset interaction table; Based on the event presentation logic in the preset interaction table, the interaction event is presented and processed by a presentation device preset in the cockpit domain; Among them, the preset presentation device includes a display device and / or a voice device, and the local display interface of the display device is set as an autonomous driving interaction area, and the autonomous driving interaction area is used to display the results of presentation processing of the interactive event.

2. The method according to claim 1, characterized in that The presenting logic based on the event in the preset interaction table and presenting the interaction event through a preset presentation device in the cockpit domain includes: Taking the interaction event as a new event, determining whether the autonomous driving interaction engine is presenting logic based on the event in the preset interaction table, and presenting other interaction events through a preset autonomous driving interaction area; If yes, compare the priorities of the new event and the other interactive events, and determine whether to present the new event according to the comparison result; If not, the newly arrived event is directly presented and processed.

3. The method according to claim 2, characterized in that The step of judging whether to present the new event according to the comparison result includes: If the priority of the newly arrived event is greater than the priority of the other interactive events, then stop presenting the other events and present the newly arrived event; If the priority of the newly arrived event is less than or equal to the priority of the other interactive events, the newly arrived event will no longer be presented.

4. The method according to claim 3, characterized in that The method further includes: if the priority of the new event is equal to the priority of the other interactive events, replacing the no longer presenting the new event with the following manner: Compare the IDs of the newly arrived event and other interaction events; Determine whether to present the new event according to the comparison result; The IDs of the new event and the other interactive events respectively represent the priority order of the new event and the other interactive events in the same priority level.

5. The method according to claim 1, characterized in that The method of presenting the interactive event based on the event presentation logic in the preset interaction table and using a presentation device preset in the cockpit domain further includes: When presenting the interactive event through the voice device, obtaining a voice broadcast mode that matches the user of the vehicle; Based on the event presentation logic in the preset interaction table and in accordance with the voice playback mode, the voice device is controlled to present and process the interaction event.

6. The method according to any one of claims 1 to 5, characterized in that Before presenting the interaction event based on the event presentation logic in the preset interaction table and through a presentation device preset in the cockpit domain, the method further includes: Obtaining the event data type of the interaction event; If the event data type is a data table type, based on the event presentation logic in the preset interaction table, the interaction event is presented and processed through a presentation device preset in the cockpit domain; If the event data type is a non-data table type, obtain the preset event presentation logic that matches the event data type, and based on the matching event presentation logic, present the interactive event through a preset presentation device in the cockpit domain.

7. The method according to claim 6, characterized in that Before presenting the interactive event through a presentation device preset in the cockpit domain, the method further includes: Taking the interaction event as a new event, determining whether the autonomous driving interaction engine is presenting and processing other interaction events, and whether the event data types of the new event and the other interaction events are different; If yes, compare the priorities of the new event and the other interactive events, and determine whether to present the new event according to the comparison result; If not, the newly arrived event is directly presented and processed.

8. The method according to any one of claims 1 to 5, characterized in that The preset interaction table is stored in the autonomous driving interaction engine and the autonomous driving domain respectively, and the method further includes updating the preset interaction table of the autonomous driving interaction engine in the following manner: The autonomous driving interaction engine transmits a first version of a preset interaction table stored in the autonomous driving domain to the autonomous driving domain; The autonomous driving interaction engine receives an update request transmitted by the autonomous driving domain, where the update request is transmitted by the autonomous driving domain to the autonomous driving interaction engine when the autonomous driving domain detects that a second version of a preset interaction table stored in the autonomous driving domain is inconsistent with the first version; The autonomous driving interaction engine obtains and stores the preset interaction table stored in the autonomous driving domain according to the update request to complete the update of the preset interaction table stored in the autonomous driving domain.

9. The method according to claim 8, characterized in that The autonomous driving interaction engine obtains and stores a preset interaction table stored in the autonomous driving domain according to the update request, including: The autonomous driving interaction engine obtains verification information of the latest version of the preset interaction table stored in the cloud server according to the update request, and after acquiring the verification information, sending update response information to the autonomous driving domain, so that the autonomous driving domain can transmit the preset interaction table stored in itself to the autonomous driving interaction engine according to the update response information; The autonomous driving interaction engine receives the preset interaction table transmitted by the autonomous driving domain, and verifies the transmitted preset interaction table according to the verification information to determine whether the transmitted preset interaction table is the latest version of the preset interaction table; if so, stores the transmitted preset interaction table; if not, does not store the transmitted preset interaction table; Among them, the preset interaction table stored in the autonomous driving domain is the same as the latest version of the preset interaction table stored in the cloud server, and is updated synchronously with the update of the latest version of the preset interaction table.

10. The method according to claim 9, characterized in that The receiving of the preset interaction table transmitted by the autonomous driving domain includes: Receive serialized data formed after the autonomous driving domain serializes the preset interaction table stored in the autonomous driving domain.

11. The method according to any one of claims 1 to 5, characterized in that The preset interaction table is stored in the autonomous driving interaction engine and the autonomous driving domain respectively, and the method further includes updating the preset interaction table of the autonomous driving interaction engine in the following manner: The autonomous driving interaction engine obtains the latest version of the preset interaction table and its verification information stored in the cloud server; The autonomous driving interaction engine verifies the preset interaction table stored in the autonomous driving domain according to the verification information to determine whether the preset interaction table stored in the autonomous driving domain is the latest version of the preset interaction table; If yes, store the latest version of the preset interaction table obtained from the cloud server to complete the update of the preset interaction table stored in itself; If not, the latest version of the preset interaction table obtained from the cloud server is not stored; Among them, the preset interaction table stored in the autonomous driving domain is the same as the latest version of the preset interaction table stored in the cloud server, and is updated synchronously with the update of the latest version of the preset interaction table.

12. The method according to any one of claims 1 to 5, characterized in that The preset interaction table is stored in the autonomous driving interaction engine and the autonomous driving domain respectively, and the method further includes performing fault handling in the following manner: After the autonomous driving interaction engine fails, it switches the preset interaction table that it is running to a preset default version of the interaction table. And send information to the autonomous driving domain, so that the autonomous driving domain can switch its currently running preset interaction table to the preset default version of the interaction table according to the information.

13. The method according to any one of claims 1 to 5, characterized in that The preset interaction table is stored in the autonomous driving interaction engine and the autonomous driving domain respectively, and the method further includes performing fault handling in the following manner: The autonomous driving interaction engine receives a version switching request transmitted by the autonomous driving domain; The autonomous driving interaction engine switches the preset interaction table currently running in the autonomous driving interaction engine to an interaction table of a preset default version according to the version switching request; The autonomous driving domain can transmit a version switching request to the autonomous driving domain after a failure occurs in the autonomous driving domain and the preset interaction table currently being run by the autonomous driving domain is switched to an interaction table of a preset default version.

14. The method according to claim 1, characterized in that The method further comprises: The autonomous driving interaction engine communicates with the autonomous driving domain based on the SOME / IP communication protocol, wherein the autonomous driving interaction engine is a server based on the SOME / IP communication protocol, and the autonomous driving domain is a client based on the SOME / IP communication protocol.

15. A computer device comprising a processor and a storage device, wherein the storage device is suitable for storing a plurality of program codes, characterized in that: The program code is suitable for being loaded and run by the processor to execute the autonomous driving interaction method according to any one of claims 1 to 14.

16. A computer-readable storage medium storing a plurality of program codes, characterized in that: The program code is suitable for being loaded and run by a processor to execute the autonomous driving interaction method according to any one of claims 1 to 14.

17. A smart device, characterized in that: include: at least one processor; and, a memory communicatively coupled to the at least one processor; Wherein, a computer program is stored in the memory, and when the computer program is executed by the at least one processor, the automatic driving interaction method described in any one of claims 1 to 14 is implemented.

Images