Human-computer interaction method and device, electronic equipment, moving tool and readable medium
By detecting the startup conditions of the autonomous driving system and broadcasting driving data in real time, the problem of untimely interaction between the autonomous driving system and the driver is solved, and the driver's response speed and vehicle safety are improved.
Patent Information
- Application Number
- CN202310563397.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-18
- Publication Date
- 2024-11-22
AI Technical Summary
In the autonomous driving system, it is difficult for the driver to receive interactive information in a timely manner, resulting in the inability to take over the vehicle in a timely manner in an emergency, increasing the risk of safety accidents.
By detecting whether the autonomous driving system meets the startup conditions, and displays prompt information when the conditions are met, obtaining driving data to generate takeover and auxiliary prompt information, and broadcasting it to the driver in real time, so as to achieve timely interaction between the autonomous driving system and the driver.
Ensure that the driver can follow up on the driving process in a timely manner, solve the problem of untimely interaction between the autonomous driving system and the driver, and improve the driver's response speed and vehicle safety.
Smart Images

Figure CN118991808A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of autonomous driving technology, and in particular to a human-computer interaction method, device, electronic device, mobile tool and readable medium. Background Art
[0002] At present, autonomous driving technology is gradually maturing, but there are still risks that require takeover. In the L3 autonomous driving specified by SAE, the driver needs to stay focused in the autonomous driving mode and be ready to take over the vehicle at any time to deal with working conditions that the autonomous driving system cannot handle. It can be seen that human-computer interaction in the autonomous driving process is particularly important. Most of the existing human-computer interactions are carried out through HMI (Human Machine Interface), but it is difficult for the driver to always stare at the HMI to receive interactive information. As a result, in the event of an emergency, the driver often cannot immediately know the current obstacle information, resulting in untimely takeover, which is easy to cause safety accidents.
[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention
[0004] The present application provides a human-computer interaction method, device, electronic device, mobile tool and readable medium to solve the technical problem of the above-mentioned untimely interaction between the autonomous driving system and the driver.
[0005] According to one aspect of an embodiment of the present application, the present application provides a human-computer interaction method, including: detecting whether the automatic driving system of a vehicle meets the startup conditions, and displaying a first prompt message when the automatic driving system meets the startup conditions; starting the automatic driving mode when receiving an automatic driving instruction sent by a target object; obtaining driving data when the vehicle is in automatic driving mode; generating a second prompt message based on the driving data, and broadcasting the second prompt message to achieve human-computer interaction between the automatic driving system and the target object, wherein the second prompt message includes takeover prompt information for instructing the target object to take over the vehicle, and auxiliary prompt information for reminding the target object of the driving operation that the vehicle is about to perform.
[0006] Optionally, detecting whether the vehicle's automatic driving system meets the startup conditions specifically includes: when it is detected that the automatic driving system is powered on, obtaining the initialization status of the automatic driving system, and broadcasting a third prompt message corresponding to the initialization status; when the third prompt message indicates that the automatic driving system has been successfully initialized, detecting whether a driving task has been received; when the driving task is received, generating a driving plan according to the driving task; when the driving trajectory in the driving plan is a smooth trajectory, obtaining the current speed of the vehicle; when the current speed is less than the preset speed, determining that the automatic driving system meets the startup conditions, otherwise, determining that the automatic driving system does not meet the startup conditions.
[0007] Optionally, the autonomous driving system is initialized successfully, specifically including: multiple modules in the autonomous driving system are initialized successfully, wherein the multiple modules include a perception module, a positioning module, a prediction module, a decision planning module, a business module, a map engine module and a Canbus module; and the vehicle is not in a faulty state.
[0008] Optionally, a second prompt message is generated based on the driving data, specifically including at least one of the following methods: when the position data in the driving data indicates that the vehicle contour of the vehicle exceeds a preset map boundary, a takeover prompt message is generated; when the braking data in the driving data indicates that the emergency braking device of the vehicle is triggered and the expected acceleration is less than a preset acceleration, an auxiliary prompt message is generated; when the status data in the driving data indicates that there is a fault in the vehicle, a takeover prompt message is generated; when the operating data in the driving data indicates that the vehicle is in an abnormally stationary state, a takeover prompt message is generated.
[0009] Optionally, determining whether the vehicle is in an abnormally stationary state specifically includes: obtaining the vehicle's stationary time and task execution status based on operating data; when the stationary time is greater than a preset time and the task execution status is executing, detecting a driving trajectory output by a decision-making planning module in the automatic driving system; when the driving trajectory is a parking trajectory, detecting whether the vehicle has a passing condition; if it is detected that the vehicle does not have a passing condition, determining that the vehicle is in an abnormally stationary state.
[0010] Optionally, detecting whether the vehicle has the conditions for passing specifically includes: detecting road parameters of the vehicle's current road, wherein the road parameters include road width and road curvature; when the road width is less than a width threshold and / or the road curvature is greater than a curvature threshold, obtaining real-time traffic data of the current road; determining whether the current road is in a congested state through real-time traffic data; when the current road is not in a congested state, detecting obstacles in front of the vehicle; and when the obstacle is a stationary obstacle, determining that the vehicle does not have the conditions for passing, wherein a stationary obstacle is an obstacle that does not move within a preset time period.
[0011] According to another aspect of an embodiment of the present application, the present application provides a human-computer interaction device, including: a detection module, used to detect whether the automatic driving system of a vehicle meets the startup conditions, and display a first prompt message when the automatic driving system meets the startup conditions; a startup module, used to start the automatic driving mode when receiving an automatic driving instruction sent by a target object; an acquisition module, used to acquire driving data when the vehicle is in automatic driving mode; an interaction module, used to generate a second prompt message based on the driving data, and broadcast the second prompt message to achieve human-computer interaction between the automatic driving system and the target object, wherein the second prompt message includes takeover prompt information for instructing the target object to take over the vehicle, and auxiliary prompt information for reminding the target object of the driving operation that the vehicle is about to perform.
[0012] According to another aspect of an embodiment of the present application, the present application provides an electronic device, including a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, the memory and the processor communicate through the communication bus and the communication interface, and the steps of the above method are implemented when the processor executes the computer program.
[0013] According to another aspect of an embodiment of the present application, the present application provides a mobile tool, including the above-mentioned electronic device.
[0014] According to another aspect of an embodiment of the present application, the present application also provides a computer-readable medium having a non-volatile program code executable by a processor, and the program code enables the processor to execute the above method.
[0015] The above technical solution provided by the embodiment of the present application has the following advantages compared with the related art:
[0016] The present application adopts a human-computer interaction method, including: detecting whether the automatic driving system of a vehicle meets the start-up conditions, and displaying a first prompt message when the automatic driving system meets the start-up conditions; starting the automatic driving mode when receiving the automatic driving instruction sent by the target object; obtaining the driving data of the vehicle when it is in the automatic driving mode; generating a second prompt message according to the driving data, and broadcasting the second prompt message to realize the human-computer interaction between the automatic driving system and the target object, wherein the second prompt message includes a takeover prompt message for instructing the target object to take over the vehicle, and an auxiliary prompt message for reminding the target object of the driving operation that the vehicle is about to perform. By broadcasting the driving process in the automatic driving process in real time, the driver can follow up the driving process in time, solving the problem of untimely interaction between the automatic driving system and the driver. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0019] Figure 1 A flowchart of an optional human-computer interaction method provided according to an embodiment of the present application;
[0020] Figure 2 A flowchart of another optional human-computer interaction method provided according to an embodiment of the present application;
[0021] Figure 3 A flowchart of an optional method for determining a ready state of autonomous driving provided according to an embodiment of the present application;
[0022] Figure 4 A flowchart of an optional method for determining an abnormal static state according to an embodiment of the present application;
[0023] Figure 5 A block diagram of an optional human-computer interaction device provided according to an embodiment of the present application;
[0024] Figure 6 A schematic diagram of an optional electronic device structure provided in an embodiment of the present application. DETAILED DESCRIPTION
[0025] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.
[0026] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application and have no specific meaning. Therefore, "module" and "component" can be used interchangeably.
[0027] At present, autonomous driving technology is gradually maturing, but there are still risks that need to be taken over. In the L3 autonomous driving specified by SAE, the driver needs to stay focused in the autonomous driving mode and be ready to take over the vehicle to deal with working conditions that the autonomous driving system cannot handle and reduce the occurrence of risks. Most of the existing human-computer interaction technologies use HMI for display, but the people on the car cannot always focus on the HMI. For emergency situations that require takeover, it cannot directly serve as a warning. Using voice reminders to remind the safety officer at critical moments through sound signals can improve the driver's response speed. Moreover, the current human-computer interaction method for autonomous driving does not involve the design of the logic of entering / exiting the autonomous driving mode and the voice reminder of the reason why the autonomous driving process cannot be carried out. The recognition of the scene where the driver needs to take over and the voice reminder of the critical status of the vehicle are not comprehensive enough, and there are safety risks.
[0028] In order to solve the problems mentioned in the background technology, according to one aspect of the embodiments of the present application, an embodiment of a human-computer interaction method is provided, such as Figure 1 As shown, including:
[0029] Step 101, detecting whether the automatic driving system of the vehicle meets the start-up conditions, and displaying a first prompt message when the automatic driving system meets the start-up conditions;
[0030] Step 103, when receiving the automatic driving instruction sent by the target object, starting the automatic driving mode;
[0031] Step 105, obtaining driving data when the vehicle is in the automatic driving mode;
[0032] Step 107, generating a second prompt message based on the driving data, and broadcasting the second prompt message to achieve human-computer interaction between the automatic driving system and the target object, wherein the second prompt message includes takeover prompt information for instructing the target object to take over the vehicle, and auxiliary prompt information for reminding the target object of the driving operation that the vehicle is about to perform.
[0033] This application is applied to human-computer interaction scenarios in the field of autonomous driving, reminding the target object to take over the vehicle when necessary, where the target object can be the driver or other safety personnel who control the vehicle. In order to improve vehicle safety and comfort, the vehicle is allowed to enter autonomous driving only when the vehicle and environmental conditions meet certain conditions. The human-computer interaction method provided by this application can prompt the driver whether the conditions for entering autonomous driving are met, and when it is impossible to enter autonomous driving, remind the driver of the reason for the failure to enter autonomous driving.
[0034] Figure 2 A flowchart of another optional human-computer interaction method provided for this application.
[0035] It should be noted that the present application does not limit the specific expression of the prompt information, but only limits the meaning represented by the prompt information. Therefore, the specific content of each prompt information in the present application is for reference only.
[0036] As an optional embodiment, detecting whether the vehicle's automatic driving system meets the startup conditions specifically includes: when detecting that the automatic driving system is powered on, obtaining the initialization status of the automatic driving system, and broadcasting a third prompt message corresponding to the initialization status; when the third prompt message indicates that the automatic driving system has been successfully initialized, detecting whether a driving task has been received; when the driving task is received, generating a driving plan according to the driving task; when the driving trajectory in the driving plan is a smooth trajectory, obtaining the current speed of the vehicle; when the current speed is less than the preset speed, determining that the automatic driving system meets the startup conditions, otherwise, determining that the automatic driving system does not meet the startup conditions.
[0037] Preferably, the embodiment provided in the present application defines the conditions for entering the automatic driving, and reminds the target object whether it meets the conditions for entering the automatic driving before entering the automatic driving, and reminds the safety officer of the reason why the automatic driving cannot be entered if the conditions are not met.
[0038] Optionally, the third prompt information is used to indicate whether the automatic driving system initialization is successful.
[0039] For example, if the system initialization fails, the voice broadcast will say "System initialization failed, please wait", and then the system initialization status will be checked again at a fixed time, and the initialization reminder will be made again until the initialization is successful; if the system initialization is successful, the voice reminder will say "System initialization successful".
[0040] After the system prompts that the initialization is successful, the target object can issue the target site task through the terminal (such as a mobile phone APP). After the target object issues the task, the autonomous driving system begins real-time planning, and then uses the autonomous driving ready status light to indicate the ready status of each upper-level module, that is, whether the conditions for triggering the autonomous driving function are met and the vehicle can enter the autonomous driving mode. If the target object does not trigger the autonomous driving function, the vehicle will not enter the autonomous driving mode.
[0041] Optionally, when the system initialization fails, the target object needs to wait for the broadcast of successful system initialization before operating. If the initialization failure is broadcast multiple times, the vehicle can be driven into an open and high-precision map area, and the autonomous driving system can be powered on again. After the system initializes successfully and broadcasts the voice of "System initialization successful", the initialization status voice will no longer be broadcast.
[0042] Specifically, if all the following conditions are met at the current moment, the vehicle will output a light signal indicating that it is ready for autonomous driving: the vehicle has no faults; the driving task is received; the autonomous driving system produces a smooth trajectory that can reach the destination; the current vehicle speed is less than the preset speed (i.e., the maximum speed threshold for autonomous driving). Otherwise, a light signal indicating that autonomous driving is not ready is output.
[0043] Among them, judging the smooth trajectory that can reach the destination must meet the following requirements at the same time: the planned trajectory can reach the destination; it is a non-stop trajectory; the planned trajectory meets the comfort requirements, that is, the maximum value of the lateral acceleration is less than the acceleration threshold, and the specific acceleration threshold can be set according to actual conditions.
[0044] Preferably, the present application provides an autonomous driving ready light as the first prompt information. The target object can know whether the conditions for entering automatic operation are met according to the lighting status of the autonomous driving ready light, and thus take corresponding actions. When the autonomous driving system meets the startup conditions, the autonomous driving ready light is on; when the autonomous driving system does not meet the startup conditions, the autonomous driving ready light is off.
[0045] Optionally, when the autonomous driving ready light is not on, if it is detected that the target object presses the "Auto" button, the vehicle will not enter the autonomous driving mode, but will detect the reason why the autonomous driving mode cannot be entered, and broadcast the reason why the autonomous driving mode cannot be entered through the voice module, so that the target object can know the reason why the autonomous driving cannot be entered in a timely manner.
[0046] Figure 3 A flowchart of an optional method for determining the ready state of autonomous driving provided in this application.
[0047] As an optional embodiment, the autonomous driving system is successfully initialized, specifically including: multiple modules in the autonomous driving system are successfully initialized, wherein the multiple modules include a perception module, a positioning module, a prediction module, a decision planning module, a business module, a map engine module and a Canbus module; and the vehicle is not in a fault state.
[0048] Specifically, the Canbus module is used to feedback the current status of the vehicle (heading, angle, speed, etc.).
[0049] It is necessary to ensure that each module in the autonomous driving system is initialized successfully before the entire automated driving system can be determined to be initialized successfully.
[0050] Specifically, vehicle failures include but are not limited to the following: hardware failures, module output data timeout failures, control-by-wire platform response failures, and positioning output abnormality failures. In fact, detecting whether the vehicle has a fault runs through the entire autonomous driving process, and manual takeover is required once the vehicle fails.
[0051] As an optional embodiment, the second prompt information is generated based on the driving data, specifically including at least one of the following methods: when the position data in the driving data indicates that the vehicle contour of the vehicle exceeds the preset map boundary, a takeover prompt information is generated; when the braking data in the driving data indicates that the emergency braking device of the vehicle is triggered and the expected acceleration is less than the preset acceleration, an auxiliary prompt information is generated; when the status data in the driving data indicates that there is a fault in the vehicle, a takeover prompt information is generated; when the operating data in the driving data indicates that the vehicle is in an abnormally stationary state, a takeover prompt information is generated.
[0052] The embodiments provided in this application will acquire driving information during the driving process in real time, and then promptly give reminders or takeover instructions to the target object to avoid serious consequences.
[0053] Specifically, when the position data in the driving data indicates that the vehicle outline of the vehicle exceeds the preset map boundary, a takeover prompt message is generated, including: when the vehicle exits the electronic fence during the automatic driving process, the voice module continuously broadcasts the takeover prompt message at a certain frequency (such as "Automatic driving out of the map, please take over") until the safety officer takes over or the vehicle autonomously enters the electronic fence. When the voice broadcasts the event, the safety officer should take over the vehicle immediately. The electronic fence can be understood as the "map boundary of the vehicle's automatic driving", with the outline of the vehicle represented by a rectangle. If any corner point of the rectangle is not within the vehicle boundary, it is judged that the vehicle has exited the electronic fence.
[0054] Specifically, when the braking data in the driving data indicates that the vehicle's emergency brake device is triggered and the expected acceleration is less than the preset acceleration, an auxiliary prompt message is generated. During the automatic driving process, a voice reminder will be given in advance of the impending emergency brake, so that passengers and safety officers can be mentally prepared for the emergency brake in advance and pay attention to safety. Emergency braking is the emergency response of the automatic driving system to nearby obstacles. There is no need for the safety officer to take over, and it only serves as a reminder. When the control module triggers AEB (Autonomous Emergency Braking) and the output expected acceleration is less than the preset acceleration, a voice reminder of emergency braking will be given. The specific preset acceleration can be set according to the actual situation.
[0055] Specifically, the status data in the driving data indicates that the vehicle has a fault, and a takeover prompt message is generated. If a vehicle fault occurs during the autonomous driving process, the voice module will continue to broadcast "Vehicle fault, please take over by the safety officer" at a certain frequency until the fault disappears or the safety officer takes over. The type of vehicle fault is consistent with the vehicle fault used in the autonomous driving readiness state judgment. When the voice broadcasts the event, the safety officer should take over the vehicle immediately.
[0056] Optionally, the driving mode of the autonomous driving vehicle is divided into an autonomous driving mode and a manual driving mode. When switching from the manual driving mode to the autonomous driving mode, the voice module broadcasts "entering the autonomous driving mode"; when switching from the autonomous driving mode to the manual driving mode, the voice module broadcasts "entering the manual driving mode".
[0057] In addition, in order to deal with the unmanageable scenarios that may be encountered during the autonomous driving process (such as the vehicle being "stuck"), this application also broadcasts takeover prompts when the vehicle is in an abnormally stationary state. The voice broadcast "The vehicle cannot pass, please take over" is broadcast at a certain frequency until the safety officer takes over or the unmanageable state becomes manageable. When the voice broadcasts the event, the safety officer should take over the vehicle immediately.
[0058] As an optional embodiment, determining whether the vehicle is in an abnormally stationary state specifically includes: obtaining the vehicle's stationary time and task execution status based on operating data; when the stationary time is greater than a preset time and the task execution status is executing, detecting a driving trajectory output by a decision-making planning module in the automatic driving system; when the driving trajectory is a parking trajectory, detecting whether the vehicle has a passing condition; if it is detected that the vehicle does not have a passing condition, determining that the vehicle is in an abnormally stationary state.
[0059] This application divides the abnormal static state into two situations: unhandled and handleable. When it is unhandled, manual takeover is required, and when it is handleable, manual takeover is not required. This application describes the abnormal static state that requires manual takeover.
[0060] Figure 4 This is a flow chart of the method for determining an abnormal static state provided in the present application.
[0061] For example, the abnormal static state that cannot be handled is: the road curvature and road width do not meet the vehicle's passing conditions; the vehicle is stationary for longer than the preset time in the automatic driving mode; the decision-making planning module outputs a parking trajectory; the vehicle is not in the pause task state. The above conditions include the scenario where the vehicle is stuck because the road curvature and width do not meet the vehicle's passing conditions. In this scenario, a voice reminder of "the vehicle cannot pass, please take over" is required to prompt the safety officer to take over.
[0062] As an optional embodiment, detecting whether a vehicle has the conditions for passing specifically includes: detecting road parameters of the vehicle's current road, wherein the road parameters include road width and road curvature; when the road width is less than a width threshold and / or the road curvature is greater than a curvature threshold, obtaining real-time traffic data of the current road; determining whether the current road is in a congested state through real-time traffic data; when the current road is not in a congested state, detecting obstacles in front of the vehicle; and determining that the vehicle does not have the conditions for passing when the obstacle is a stationary obstacle, wherein a stationary obstacle is an obstacle that does not move within a preset time period.
[0063] The conditions for not meeting traffic conditions include: the road curvature and road width do not meet the vehicle traffic conditions; the vehicle is not in a congested queue; and the current obstacles cannot be passed.
[0064] For example, during a forced lane change, the autonomous driving system is affected by a static / dynamic obstacle and is stuck for a long time and unable to change lanes. This is also a scenario that cannot be handled. During a non-forced lane change, when there is a static obstacle (stationary vehicle, construction sign, etc.) ahead and the road does not meet the lane change requirements, the system is stuck for a long time and is not in a congested queue state, this is also a scenario that cannot be handled.
[0065] The human-computer interaction method for autonomous driving proposed in this application is embodied in two aspects. On the one hand, the safety officer interacts according to the state of the autonomous driving ready light, and on the other hand, the safety officer can interact according to the content of the voice reminder. The autonomous driving ready state limits the conditions for the safety officer to enter automatic mode, avoiding the situation where the vehicle safety and comfort are reduced due to automatic mode under unreasonable vehicle and road conditions. The safety officer can obtain the reason why the vehicle cannot enter automatic mode based on the voice reminder and adjust the vehicle status according to the prompt. During the autonomous driving process, the voice reminder module can remind the critical status of the vehicle, so that the safety officer can understand the critical driving status of the vehicle. By setting reasonable trigger conditions in combination with the driving status of the vehicle, the safety officer can be reminded to take over when a fault occurs, the vehicle drives out of the electronic fence, or cannot be handled, so as to avoid the occurrence of dangerous situations and improve travel safety.
[0066] It should be noted that this application does not make specific limitations on the stationary time threshold required for judging the state that cannot be handled, the congestion queue state identification method required for judging the state that cannot be handled, the vehicle fault duration threshold required for judging the autonomous driving ready state, the frequency of system initialization status check, the autonomous driving maximum vehicle speed threshold required for judging the autonomous driving ready state, and the frequency of the voice reminders that cannot be handled, the voice reminders of vehicle failures, and the voice reminders of driving out of the electronic fence.
[0067] The present application adopts a human-computer interaction method, including: detecting whether the automatic driving system of a vehicle meets the start-up conditions, and displaying a first prompt message when the automatic driving system meets the start-up conditions; starting the automatic driving mode when receiving the automatic driving instruction sent by the target object; obtaining the driving data of the vehicle when it is in the automatic driving mode; generating a second prompt message according to the driving data, and broadcasting the second prompt message to realize the human-computer interaction between the automatic driving system and the target object, wherein the second prompt message includes a takeover prompt message for instructing the target object to take over the vehicle, and an auxiliary prompt message for reminding the target object of the driving operation that the vehicle is about to perform. By broadcasting the driving process in the automatic driving process in real time, the driver can follow up the driving process in time, solving the problem of untimely interaction between the automatic driving system and the driver.
[0068] According to another aspect of the embodiment of the present application, the present application provides a human-computer interaction device, such as Figure 5 As shown, including:
[0069] A detection module 502, used to detect whether the automatic driving system of the vehicle meets the start-up conditions, and display a first prompt message when the automatic driving system meets the start-up conditions;
[0070] A starting module 504 is used to start the automatic driving mode when receiving the automatic driving instruction sent by the target object;
[0071] An acquisition module 506 is used to acquire driving data when the vehicle is in an automatic driving mode;
[0072] Interaction module 508, used to generate second prompt information according to driving data, and broadcast the second prompt information to achieve human-computer interaction between the automatic driving system and the target object, wherein the second prompt information includes takeover prompt information for instructing the target object to take over the vehicle, and auxiliary prompt information for reminding the target object of the driving operation that the vehicle is about to perform
[0073] It should be noted that the detection module 502 in this embodiment can be used to execute step 101 in the embodiment of the present application, the startup module 504 in this embodiment can be used to execute step 103 in the embodiment of the present application, the acquisition module 506 in this embodiment can be used to execute step 105 in the embodiment of the present application, and the digital interaction module 508 in this embodiment can be used to execute step 107 in the embodiment of the present application.
[0074] Optionally, the detection module 502 specifically includes:
[0075] An acquisition submodule, used to acquire the initialization state of the automatic driving system when detecting that the automatic driving system is powered on, and broadcast third prompt information corresponding to the initialization state;
[0076] A detection submodule, configured to detect whether a driving task is received when the third prompt information indicates that the automatic driving system has been initialized successfully;
[0077] The first generating submodule is used to generate a driving plan according to the driving task when receiving the driving task; when the driving trajectory in the driving plan is a smooth trajectory, obtain the current speed of the vehicle;
[0078] The determination submodule is used to determine whether the automatic driving system meets the start-up conditions when the current vehicle speed is less than the preset vehicle speed, otherwise, determine whether the automatic driving system does not meet the start-up conditions.
[0079] Optionally, the detection submodule is also used to determine whether the autonomous driving system has been successfully initialized in the following manner: multiple modules in the autonomous driving system have been successfully initialized, wherein the multiple modules include a perception module, a positioning module, a prediction module, a decision planning module, a business module, a map engine module and a Canbus module; and the vehicle is not in a faulty state.
[0080] Optionally, the interaction module 508 specifically includes at least one of the following:
[0081] A second generating submodule is used to generate takeover prompt information when the position data in the driving data indicates that the vehicle outline of the vehicle exceeds the preset map boundary;
[0082] A third generating submodule is used to generate auxiliary prompt information when the braking data in the driving data indicates that the emergency brake device of the vehicle is triggered and the expected acceleration is less than the preset acceleration;
[0083] A fourth generating submodule, for generating takeover prompt information when the status data in the driving data indicates that the vehicle has a fault;
[0084] The fifth submodule is used to generate takeover prompt information when the operating data in the driving data indicates that the vehicle is in an abnormal stationary state.
[0085] Optionally, the fifth submodule is also used to determine whether the vehicle is in an abnormally stationary state in the following manner: obtain the vehicle's stationary time and task execution status based on operating data; when the stationary time is greater than a preset time and the task execution status is executing, detect the driving trajectory output by the decision-making planning module in the automatic driving system; when the driving trajectory is a parking trajectory, detect whether the vehicle has the conditions for passing; if it is detected that the vehicle does not have the conditions for passing, it is determined that the vehicle is in an abnormally stationary state.
[0086] Optionally, the fifth submodule is also used to detect whether the vehicle has the conditions for passing in the following manner: detecting road parameters of the vehicle's current road, wherein the road parameters include road width and road curvature; when the road width is less than a width threshold and / or the road curvature is greater than a curvature threshold, obtaining real-time traffic data of the current road; determining whether the current road is in a congested state through real-time traffic data; when the current road is not in a congested state, detecting obstacles in front of the vehicle; when the obstacle is a stationary obstacle, determining that the vehicle does not have the conditions for passing, wherein a stationary obstacle is an obstacle that does not move within a preset time period.
[0087] It should be noted here that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments.
[0088] According to another aspect of the embodiments of the present application, the present application provides an electronic device, such as Figure 6 As shown, it includes a memory 601, a processor 603, a communication interface 605 and a communication bus 607. The memory 601 stores a computer program that can be run on the processor 603. The memory 601 and the processor 603 communicate through the communication interface 605 and the communication bus 607. When the processor 603 executes the computer program, the steps of the above method are implemented.
[0089] The memory and processor in the above electronic device communicate via a communication bus and a communication interface. The communication bus may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus may be divided into an address bus, a data bus, a control bus, etc.
[0090] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.
[0091] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
[0092] According to another aspect of the embodiments of the present application, a mobile tool is provided, including the above-mentioned electronic device.
[0093] The mobile tools of the present application can be all devices with mobile capabilities, including vehicles with automatic driving or intelligent driving (including vehicles with passenger functions (such as cars, buses, large buses, minibuses, etc.), vehicles with cargo functions (such as ordinary trucks, vans, trailers, closed trucks, tank trucks, flatbed trucks, container trucks, dump trucks, special structure trucks), special vehicles (such as logistics distribution vehicles, automatic guided transport vehicles AGV, patrol cars, cranes, cranes, excavators, bulldozers, forklifts, rollers, loaders, off-road engineering vehicles, armored engineering vehicles, sewage treatment vehicles, sanitation vehicles, vacuum trucks, floor washing vehicles, sprinkler trucks, sweeping robots, food delivery robots, shopping guide robots, lawn mowers, golf carts, etc.), vehicles with entertainment functions (such as entertainment vehicles, amusement park automatic driving devices, balance cars, etc.), rescue vehicles (such as fire trucks, ambulances, power repair vehicles, engineering rescue vehicles, etc.)) and robots (such as sweeping robots, food delivery robots, etc.), etc.
[0094] According to another aspect of the embodiments of the present application, a computer-readable medium having a non-volatile program code executable by a processor is provided.
[0095] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.
[0096] When the embodiments of the present application are specifically implemented, reference may be made to the above-mentioned embodiments, which have corresponding technical effects.
[0097] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application, or a combination thereof.
[0098] For software implementation, the technology described herein can be implemented by a unit that performs the functions described herein. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.
[0099] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0100] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0101] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
[0102] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0103] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0104] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk. It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the term "include", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such a process, method, article or device. Without more constraints, an element defined by the phrase "comprising a..." does not exclude the existence of other identical elements in the process, method, article or apparatus comprising the element.
[0105] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.
Claims
1. A human-computer interaction method, It is characterized in that include: Detecting whether the automatic driving system of the vehicle meets the start-up condition, and displaying a first prompt message when the automatic driving system meets the start-up condition; Upon receiving an autonomous driving instruction sent by a target object, starting the autonomous driving mode; Acquiring driving data of the vehicle when it is in the automatic driving mode; Generate second prompt information based on the driving data, and broadcast the second prompt information to achieve human-computer interaction between the automatic driving system and the target object, wherein the second prompt information includes takeover prompt information for instructing the target object to take over the vehicle, and auxiliary prompt information for reminding the target object of the driving operation that the vehicle is about to perform.
2. The method according to claim 1, It is characterized in that The detecting whether the automatic driving system of the vehicle meets the start-up conditions specifically includes: When detecting that the automatic driving system is powered on, obtaining an initialization state of the automatic driving system, and broadcasting third prompt information corresponding to the initialization state; When the third prompt information indicates that the automatic driving system is successfully initialized, detecting whether a driving task is received; Upon receiving the driving task, generating a driving plan according to the driving task; When the driving trajectory in the driving plan is a smooth trajectory, obtaining the current speed of the vehicle; When the current vehicle speed is less than a preset vehicle speed, it is determined that the automatic driving system meets the start-up condition; otherwise, it is determined that the automatic driving system does not meet the start-up condition.
3. The method according to claim 2, It is characterized in that The automatic driving system is successfully initialized, specifically including: Multiple modules in the autonomous driving system are successfully initialized, wherein the multiple modules include a perception module, a positioning module, a prediction module, a decision-making planning module, a business module, a map engine module and a Canbus module; and, The vehicle is not in a faulty state.
4. The method according to claim 1, It is characterized in that The generating of the second prompt information according to the driving data specifically includes at least one of the following methods: When the position data in the driving data indicates that the vehicle outline of the vehicle exceeds a preset map boundary, generating the takeover prompt information; When the braking data in the driving data indicates that the emergency braking device of the vehicle is triggered and the expected acceleration is less than the preset acceleration, generating the auxiliary prompt information; The status data in the driving data indicates that the vehicle has a fault, and generates the takeover prompt information; The takeover prompt information is generated when the operating data in the driving data indicates that the vehicle is in an abnormal stationary state.
5. The method according to claim 4, It is characterized in that Determining whether the vehicle is in the abnormal stationary state specifically includes: Acquire the stationary time and task execution status of the vehicle according to the operation data; When the stationary time is longer than a preset time and the task execution state is being executed, detecting a driving trajectory output by a decision-making planning module in the automatic driving system; When the driving trajectory is a parking trajectory, detecting whether the vehicle has a passing condition; If it is detected that the vehicle does not meet the traffic conditions, it is determined that the vehicle is in the abnormal stationary state.
6. The method according to claim 5, It is characterized in that The detecting whether the vehicle meets the traffic conditions specifically includes: Detecting road parameters of the current road of the vehicle, wherein the road parameters include road width and road curvature; When the road width is less than a width threshold and / or the road curvature is greater than a curvature threshold, acquiring real-time traffic data of the current road; Determine whether the current road is in a congested state by using the real-time traffic data; When the current road is not in the congested state, detecting an obstacle in front of the vehicle; When the obstacle is a stationary obstacle, it is determined that the vehicle does not meet the passage condition, wherein the stationary obstacle is an obstacle that does not move within a preset time period.
7. A human-computer interaction device, It is characterized in that include: A detection module, used to detect whether the automatic driving system of the vehicle meets the start-up condition, and display a first prompt message when the automatic driving system meets the start-up condition; A starting module, used to start the automatic driving mode upon receiving an automatic driving instruction sent by the target object; An acquisition module, used to acquire driving data when the vehicle is in the automatic driving mode; An interaction module is used to generate second prompt information based on the driving data and broadcast the second prompt information to achieve human-computer interaction between the automatic driving system and the target object, wherein the second prompt information includes takeover prompt information for instructing the target object to take over the vehicle, and auxiliary prompt information for reminding the target object of the driving operation that the vehicle is about to perform.
8. An electronic device comprising a memory, a processor, a communication interface and a communication bus, wherein the memory stores a computer program that can be run on the processor, and the memory and the processor communicate through the communication bus and the communication interface. It is characterized in that When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A mobile tool, It is characterized in that Comprising the electronic device as claimed in claim 8.
10. A computer readable medium having a non-volatile program code executable by a processor, It is characterized in that The program code enables the processor to execute the method according to any one of claims 1 to 6.
