Automatic driving starting method and device, electronic equipment and storage medium

Abstract

The invention discloses an automatic driving starting method and device, electronic equipment and a storage medium. The method comprises the steps that state information in modules participating in a vehicle automatic driving function is collected; fault information, collected by the fault management module, of the modules participating in the vehicle automatic driving function is received; judging whether the current system supports automatic driving or not according to the state information and the fault information; and if automatic driving is not supported, abnormal information is uploaded to the cockpit, so that response is limited before the cockpit starts the automatic driving function. According to the method, on one hand, automatic driving condition preorder collection can be performed on the automatic driving domain, on the other hand, the situation of abnormal failure in execution after traditional command response is reduced, and meanwhile, the starting success rate of automatic driving is increased.

Description

Technical Field

[0001] This application relates to the field of autonomous driving technology, and in particular, to a method and device for starting autonomous driving, an electronic device, and a storage medium. Background Art

[0002] The startup process of autonomous driving is a complex process involving multiple participating modules, and a single failure in autonomous driving may involve multiple operations. That is, the failure of each module in the autonomous driving system will cause the failure of the startup of the current autonomous driving.

[0003] The failure of the self-driving system to start self-driving is an indication of insufficient foundation of the autonomous driving function, which also affects the user experience and is more likely to lead to the loss of customer trust. Summary of the Invention

[0004] Embodiments of this application provide a method and device for starting autonomous driving, an electronic device, and a storage medium to improve the success rate of starting autonomous driving.

[0005] Embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, embodiments of this application provide a method for starting autonomous driving, which is applied to a system status management module. The startup method includes:

[0007] Collect status information in modules participating in the vehicle's autonomous driving function;

[0008] Receive fault information of modules participating in the vehicle's autonomous driving function collected by a fault management module;

[0009] Based on the status information and the fault information, determine whether the current system supports autonomous driving;

[0010] If autonomous driving is not supported, upload abnormal information to the cockpit to restrict the response before starting the autonomous driving function in the cockpit.

[0011] In some embodiments, the determining whether the current system supports autonomous driving based on the status information and the fault information includes:

[0012] Generate status summary information of the current system based on the status information in each module;

[0013] Generate fault summary information based on the fault information in multiple modules;

[0014] Generate an autonomous driving flag based on the status summary information of the current system and / or the fault summary information;

[0015] Based on the autonomous driving flag, determine whether the current system supports autonomous driving.

[0016] In some embodiments, collecting the status information of the modules participating in the vehicle's autonomous driving function includes:

[0017] Receiving the status information on multiple nodes obtained according to the autonomous driving conditions of the modules participating in the vehicle's autonomous driving function itself;

[0018] Summarizing the operating status of the nodes in multiple said modules to serve as the basis for whether the current system status supports autonomous driving.

[0019] In some embodiments, receiving the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module includes:

[0020] Receiving the fault information reported when each said module is abnormal;

[0021] Summarizing the fault information in multiple said modules to serve as the basis for whether the current system status supports autonomous driving.

[0022] In some embodiments, if autonomous driving is not supported, uploading the abnormal information to the cockpit to restrict the response before starting the autonomous driving function in the cockpit includes:

[0023] In the case where it is determined according to the autonomous driving flag bit that the current system does not support autonomous driving, uploading the abnormal information to the cockpit to display the abnormality and restrict the function of starting autonomous driving on the user operation interface of the cockpit;

[0024] In the case where it is determined according to the autonomous driving flag bit that the current system supports autonomous driving, displaying normal on the user operation interface of the cockpit and responding to the function of starting autonomous driving.

[0025] In some embodiments, the method further includes:

[0026] Receiving the scheduling instruction for starting the autonomous driving function issued by the cockpit;

[0027] Issuing the scheduling instruction for starting the autonomous driving function to the modules participating in the vehicle's autonomous driving function.

[0028] In some embodiments, the method further includes:

[0029] If autonomous driving is not supported, uploading the abnormal information to the cockpit to start the degraded operation before starting the autonomous driving function in the cockpit.

[0030] In a second aspect, an embodiment of the present application further provides an autonomous driving start device, which is applied to a system status management module, and the start device includes:

[0031] A collection module for collecting status information in modules participating in the vehicle's autonomous driving function;

[0032] A receiving module for receiving fault information of modules participating in the vehicle's autonomous driving function collected by the fault management module;

[0033] A judgment module for judging whether the current system supports autonomous driving according to the status information and the fault information;

[0034] An upload module for uploading abnormal information to the cockpit if autonomous driving is not supported, so as to restrict the response before the autonomous driving function is started in the cockpit.

[0035] In a third aspect, an embodiment of the present application further provides an electronic device, including: a processor; and a memory arranged to store computer-executable instructions, where the executable instructions, when executed, cause the processor to execute the above method.

[0036] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and when the one or more programs are executed by an electronic device including a plurality of application programs, the electronic device is caused to execute the above method.

[0037] At least one of the technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: collecting status information in modules participating in the vehicle's autonomous driving function; at the same time, receiving fault information of modules participating in the vehicle's autonomous driving function collected by the fault management module. And, judging whether the current system supports autonomous driving according to the status information and the fault information; if autonomous driving is not supported, uploading abnormal information to the cockpit to restrict the response before the autonomous driving function is started in the cockpit. Through the above method, the preconditions for autonomous driving in the autonomous driving domain can be collected, reducing the abnormal failure situation in the traditional command response and execution, thereby improving the startup success rate of autonomous driving. Description of the Drawings

[0038] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments and descriptions thereof of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the drawings:

[0039] Figure 1 It is a flowchart of the autonomous driving startup method in the embodiment of the present application;

[0040] Figure 2 It is a structural diagram of the autonomous driving startup device in the embodiment of the present application;

[0041] Figure 3Schematic diagram of the system architecture of the automatic driving start method in the embodiments of the present application;

[0042] Figure 4 Schematic diagram of the structure of an electronic device in the embodiments of the present application. Detailed implementation manners

[0043] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without making creative efforts shall fall within the protection scope of the present application.

[0044] Common solutions for starting automatic driving are as follows:

[0045] (1) The operator clicks on "self-driving" through the driver's screen to start the activation of the automatic driving function.

[0046] (2) After the vehicle terminal receives the automatic driving command, the command is forwarded to the automatic driving participating module. For example, in the system status management (SSM) module, the operation health of the automatic driving node is judged, and in the fault management (FM) module, it is judged whether there is a fault on the automatic driving domain controller. For example, the map engine judges whether the current trajectory calculation is feasible.

[0047] (3) Each module on the automatic driving domain controller finds an abnormality and reports an abnormal event indicating that self-driving is not possible.

[0048] (4) The SSM module collects the vehicle status and, after receiving the self-driving command, replies to the cockpit with the reason for the failure of automatic driving.

[0049] The deficiencies of the above common solutions for starting automatic driving are as follows:

[0050] First of all, after clicking on "self-driving" in the cockpit, the instruction reaches each module before the self-driving ability is judged. Inevitably, there will be a failure to start self-driving due to insufficient conditions.

[0051] Secondly, problems with the operator's operation will lead to an increase in self-driving failures. For example, during the self-driving startup process, the "self-driving" button is clicked multiple times.

[0052] Finally, there are trajectory download failures or timeouts caused by network abnormalities, resulting in abnormal self-driving and startup failures.

[0053] In view of the above deficiencies, the embodiments of the present application provide an autonomous driving startup method. Different from the failure trigger situation where the reason for abnormal reporting occurs, the core of the autonomous driving startup method in the embodiments of the present application is to check potential problems before autonomous driving execution, fully evaluate and judge the startup risk, and improve the success rate of autonomous driving startup by degrading operation or restricting startup.

[0054] The following will describe in detail the technical solutions provided by each embodiment of the present application with reference to the accompanying drawings.

[0055] As Figure 3 shown, the method in the embodiments of the present application is based on the following system architecture, including a cockpit, an sSM system status control module, an FM fault management module, and a set of autonomous driving function participation modules. The upper layer is the cockpit human-machine interface, which is the starting point for operating autonomous driving and makes the autonomous driving function externally presented. The middle layer is the management layer of SSM and FM, which is used to identify whether nodes can operate normally and to collect whether there are serious faults in each autonomous driving module. The bottom layer is a set of participation modules for each autonomous driving function, and these modules are deployed on multiple domain controllers. The autonomous driving command of the cockpit is sent to the SSM system status control module, and the autonomous driving instruction is scheduled to the participation modules 1, 2,..., n of the set of autonomous driving function participation modules through the SSM system status control module. The abnormal fault collection of the modules in the set of autonomous driving function participation modules will be synchronized to the FM fault management module. The operation status collection of the modules in the set of autonomous driving function participation modules will be synchronized to the SSM system status control module. The FM fault management module will summarize the anomalies to the SSM system status control module, and the SSM system status control module will report the vehicle-end abnormal information in real time.

[0056] The embodiments of the present application provide an autonomous driving startup method. As Figure 1 shown, a schematic flowchart of the autonomous driving startup method in the embodiments of the present application is provided. This method is applied to the system status management (SSM) module, and the method at least includes the following steps S110 to S140:

[0057] Step S110, collect the status information in the modules participating in the vehicle's autonomous driving function.

[0058] The system status management module continuously collects the status information in the modules participating in the vehicle's autonomous driving function. By collecting the autonomous driving operation status or conditions in real time, the module status of autonomous driving can be obtained. Each module sends its own autonomous driving conditions to the SSM system status management module in the form of status messages. The SSM system status management module summarizes the operation status of each module and summarizes whether the current system status supports autonomous driving.

[0059] Step S120: Receive the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module.

[0060] The System Status Management Module (SSM) also collects abnormal faults affecting the autonomous driving function of each module in real time. Each participating module in the autonomous driving function sorts out its own module abnormalities and reports faults. The FM (Fault Management) fault management module collects the faults of each module, summarizes multiple faults into a result of whether it affects autonomous driving, and gives it to the System Status Management Module (SSM). The System Status Management Module (SSM) integrates the fault results collected from the FM fault management module and summarizes them into whether the current system status supports autonomous driving.

[0061] Step S130: Based on the status information and the fault information, determine whether the current system supports autonomous driving.

[0062] Based on the status information in the modules participating in the vehicle's autonomous driving function and the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module, after summarization, it is used as the basis for determining whether the current system supports autonomous driving.

[0063] It should be noted that the status information includes, but is not limited to, changes in the status information caused by problems within the module, network problems, and other reasons. The fault information includes, but is not limited to, the fault information reported after the module obtains the fault level. That is to say, the status information records various states and conditions of the module, and the fault information records the information of the module's faults.

[0064] Step S140: If autonomous driving is not supported, upload the abnormal information to the cockpit to restrict the response before starting the autonomous driving function in the cockpit.

[0065] The System Status Management Module (SSM) reports whether the current system status supports autonomous driving and the current vehicle abnormalities to the cockpit in real time. At the same time, the cockpit makes a judgment on the autonomous driving status, prompts problems and operation instructions to complete the human-machine interaction.

[0066] Furthermore, if autonomous driving is not supported, the abnormal information will be uploaded to the cockpit, thereby restricting its response before attempting to start the autonomous driving function in the cockpit.

[0067] Through the above method, the success rate of the system starting autonomous driving can be improved, while reducing the failure of autonomous driving startup caused by human operation and accidental abnormalities of the network or sensors. And ensure that the modules participating in autonomous driving operate normally without serious faults.

[0068] By the above method, the status information in the modules participating in the vehicle's autonomous driving function is collected; the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module is received; based on the status information and the fault information, it is determined whether the current system supports autonomous driving. A complete set of inspection processes for autonomous driving startup conditions is established. Through the management layer of the System Status Management Module (SSM) + Fault Management Module (FM), the status and faults of all modules participating in autonomous driving are collected, and a summary identifier for simple judgment by the upper layer is generated, and the cause of the abnormality is carried, without the need to investigate the cause again after the problem occurs.

[0069] By the above method, based on the status information and the fault information, it is determined whether the current system supports autonomous driving; if it does not support autonomous driving, the abnormal information is uploaded to the cockpit to limit the response before starting the autonomous driving function in the cockpit. This is different from the traditional solution of echoing the abnormality by checking the feasibility after clicking the autonomous driving start. The core function of autonomous driving is made into a normal active inspection item and reported in combination with the vehicle status and faults, which fundamentally improves the safety and controllability of vehicle operation.

[0070] Different from the related art, it is easy to cause the increase of self-driving failures or the failure of trajectory download caused by network anomalies, resulting in the ultimate abnormality of autonomous driving. Through the method in the embodiment of the present application, the response is limited before starting the autonomous driving function in the cockpit. In this way, if there is an abnormality, personnel are not allowed to click, and there is no way to click multiple times. Whether there is an abnormality is displayed in the cockpit, so that fixed-frequency messages are reported during the download link, avoiding the failure of trajectory download caused by network anomalies.

[0071] In an embodiment of the present application, the determining whether the current system supports autonomous driving based on the status information and the fault information includes: generating status summary information of the current system according to the status information in each module; generating fault summary information according to the fault information in multiple modules; generating an autonomous driving flag bit according to the status summary information of the current system and / or the fault summary information; and determining whether the current system supports autonomous driving according to the autonomous driving flag bit.

[0072] Collect the status information in each of the said modules, and generate the status summary information of the current system. Meanwhile, generate the fault summary information according to the fault information in multiple said modules. Based on the status summary information of the current system and / or the fault summary information, generate an autonomous driving flag bit. That is to say, the system status management module SSM summarizes the operation of nodes and the abnormal summary results of the FM fault management module, and generates a flag indicating whether autonomous driving is supported for the cockpit. When this flag bit changes, report it immediately to ensure the real-time nature of the status. When this flag bit does not change, report it at a fixed frequency to ensure the real-time nature of the status. Optionally, the reporting frequency is 5hz.

[0073] In an embodiment of the present application, the collection of the status information in the modules participating in the vehicle's autonomous driving function includes: receiving the status information on multiple nodes obtained according to the autonomous driving conditions of the modules participating in the vehicle's autonomous driving function themselves; summarizing the operating status of the nodes in multiple said modules as the basis for whether the current system status supports autonomous driving.

[0074] When the system status management module collects the status information in the modules participating in the vehicle's autonomous driving function, it not only collects the status information on multiple nodes (modules participating in the autonomous driving function), but also summarizes the operating status of the nodes in multiple modules as the basis for whether the current system status supports autonomous driving.

[0075] It should be noted that the status information will change continuously during the autonomous driving process.

[0076] In an embodiment of the present application, the reception of the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module includes: receiving the fault information reported when each of the said modules is abnormal; summarizing the fault information in multiple said modules as the basis for whether the current system status supports autonomous driving.

[0077] As a parallel solution to the system status management module collecting the status information in the modules participating in the vehicle's autonomous driving function, when the system status management module receives the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module, it not only receives the fault information reported when the module itself is abnormal, but also summarizes the fault information in multiple said modules as the basis for whether the current system status supports autonomous driving.

[0078] It should be noted that "receiving the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module" and "collecting the status information in the modules participating in the vehicle's autonomous driving function" can both be used as the basis for whether the current system status supports autonomous driving, without distinction in priority or execution order.

[0079] In an embodiment of the present application, if autonomous driving is not supported, uploading abnormal information to the cockpit to restrict responses before the autonomous driving function is activated in the cockpit includes: when it is determined according to the autonomous driving flag bit that the current system does not support autonomous driving, uploading abnormal information to the cockpit to display abnormalities on the user operation interface of the cockpit and restrict the function of activating autonomous driving in response; when it is determined according to the autonomous driving flag bit that the current system supports autonomous driving, displaying normal conditions on the user operation interface of the cockpit and responding to the function of activating autonomous driving.

[0080] If the cockpit receives a flag indicating that autonomous driving is not supported, the cockpit will display the reasons for the current vehicle abnormalities. Prompt the operators to perform standardized operations and repair the abnormalities reasonably. If the cockpit receives a flag indicating that autonomous driving is not supported, restrict the response of the autonomous driving start button, thereby avoiding ineffective activation of autonomous driving and further causing the failure of autonomous driving activation. If the current state of the cockpit supports autonomous driving operation, it means that the vehicle-end autonomous driving system is normal and the autonomous driving can be clicked.

[0081] In an embodiment of the present application, the method further includes: receiving a scheduling instruction for activating the autonomous driving function sent by the cockpit; sending the scheduling instruction for activating the autonomous driving function to the modules participating in the vehicle's autonomous driving function.

[0082] The system status management module SSM receives the scheduling instruction for activating the autonomous driving function sent by the cockpit, and then sends the scheduling instruction for activating the autonomous driving function to the modules participating in the vehicle's autonomous driving function. In addition, the system status management module SSM collects the fault information uploaded by the FM fault management module and the status and condition information in the modules participating in the vehicle's autonomous driving function.

[0083] In an embodiment of the present application, the method further includes: if autonomous driving is not supported, uploading abnormal information to the cockpit to start degraded operation before the autonomous driving function is activated in the cockpit.

[0084] Check potential problems before autonomous driving execution, fully evaluate and judge the start-up risks. If autonomous driving is not supported, upload abnormal information to the cockpit. Improve the success rate of autonomous driving start-up by degraded operation or restricted start, and realize some functions of autonomous driving.

[0085] The embodiment of the present application also provides an autonomous driving start-up device 200, as Figure 2 shown, which provides a schematic structural diagram of the autonomous driving start-up device in the embodiment of the present application. The autonomous driving start-up device 200 at least includes: a collection module 210, a receiving module 220, a judgment module 230, and an uploading module 240, where:

[0086] In an embodiment of the present application, the collection module 210 is specifically configured to: collect the status information in the modules participating in the vehicle's autonomous driving function.

[0087] The system status management module continuously collects the status information in the modules participating in the vehicle's autonomous driving function. By collecting the autonomous driving operation status or conditions in real time, the module status of autonomous driving can be obtained. Each module will send its status to the SSM system status management module in the form of a status message according to its own autonomous driving conditions. The system status management module SSM summarizes the operation status of each module and determines whether the current system status supports autonomous driving.

[0088] In an embodiment of the present application, the receiving module 220 is specifically configured to: receive the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module.

[0089] The system status management module SSM also simultaneously collects the abnormal faults affecting the autonomous driving function of each module in real time. Each module participating in the autonomous driving function will sort out its own module abnormalities and report faults. The FM (fault management) fault management module collects the faults of each module and summarizes multiple faults into a result indicating whether it affects autonomous driving and gives it to the system status management module SSM. The system status management module SSM integrates the fault results collected from the FM fault management module and simultaneously summarizes whether the current system status supports autonomous driving.

[0090] In an embodiment of the present application, the judgment module 230 is specifically configured to: judge whether the current system supports autonomous driving according to the status information and the fault information.

[0091] According to the status information in the modules participating in the vehicle's autonomous driving function and the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module, after summarization, it is used as the basis for judging whether the current system supports autonomous driving.

[0092] It should be noted that the status information includes, but is not limited to, changes in the status information caused by problems within the module, network problems, and other reasons. The fault information includes, but is not limited to, the fault information reported after the module obtains the fault degree. That is to say, the status information records various states and conditions of the module, and the fault information records the information about the module's faults.

[0093] In an embodiment of the present application, the uploading module 240 is specifically configured to: if autonomous driving is not supported, upload the abnormal information to the cockpit to restrict the response before the autonomous driving function is started in the cockpit.

[0094] The System Status Management Module (SSM) reports to the cockpit in real time whether the current system status supports autonomous driving and any current vehicle anomalies. At the same time, it makes a judgment on the autonomous driving status in the cockpit, gives problem prompts and operation instructions to complete the human-machine interaction.

[0095] Furthermore, if autonomous driving is not supported, the anomaly information will be uploaded to the cockpit to restrict the response before attempting to activate the autonomous driving function in the cockpit.

[0096] In an embodiment of the present application, the judgment module 230 is further configured to

[0097] generate a status summary information of the current system according to the status information in each of the modules;

[0098] generate a fault summary information according to the fault information in multiple of the modules;

[0099] generate an autonomous driving flag bit according to the status summary information of the current system and / or the fault summary information;

[0100] judge whether the current system supports autonomous driving according to the autonomous driving flag bit.

[0101] In an embodiment of the present application, the collection module 210 is further configured to

[0102] receive status information on multiple nodes obtained according to the autonomous driving conditions of the modules themselves participating in the vehicle's autonomous driving function;

[0103] summarize the operating status of the nodes in multiple of the modules as a basis for whether the current system status supports autonomous driving.

[0104] In an embodiment of the present application, the receiving module 220 is further configured to

[0105] receive fault information reported when each of the modules is abnormal;

[0106] summarize the fault information in multiple of the modules as a basis for whether the current system status supports autonomous driving.

[0107] In an embodiment of the present application, the uploading module 240 is further configured to

[0108] in the case where it is judged according to the autonomous driving flag bit that the current system does not support autonomous driving, upload the anomaly information to the cockpit to display the anomaly on the user operation interface of the cockpit and restrict the function of responding to start autonomous driving;

[0109] When it is determined according to the automatic driving flag bit that the current system supports automatic driving, the function of starting automatic driving is displayed on the user operation interface of the cockpit and responds to the start.

[0110] In an embodiment of the present application, it further includes: a scheduling module for

[0111] receiving a scheduling instruction for starting the automatic driving function sent by the cockpit;

[0112] sending the scheduling instruction for starting the automatic driving function to the modules participating in the vehicle automatic driving function.

[0113] In an embodiment of the present application, it further includes: an execution module for

[0114] If automatic driving is not supported, uploading abnormal information to the cockpit to start degraded operation before starting the automatic driving function in the cockpit.

[0115] It can be understood that the above automatic driving start device can implement each step of the automatic driving start method provided in the foregoing embodiment. The relevant explanations about the automatic driving start method are all applicable to the automatic driving start device, and will not be elaborated here.

[0116] Figure 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application. Please refer to Figure 4 , at the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. Among them, the memory may include a memory, such as a high-speed random access memory (Random-Access Memory, RAM), and may also include a non-volatile memory, such as at least one disk memory, etc. Of course, the electronic device may also include other hardware required for other services.

[0117] The processor, network interface, and memory can be interconnected through an internal bus, and the internal bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 4 only a bidirectional arrow is used in

[0118] A memory for storing programs. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory may include a memory and a non-volatile memory, and provide instructions and data to the processor.

[0119] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming an automatic driving start device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0120] Collect the status information in the modules participating in the vehicle's automatic driving function;

[0121] Receive the fault information of the modules participating in the vehicle's automatic driving function collected by the fault management module;

[0122] Judge whether the current system supports automatic driving according to the status information and the fault information;

[0123] If automatic driving is not supported, upload the abnormal information to the cockpit to limit the response before starting the automatic driving function in the cockpit.

[0124] The above as in this application Figure 1The method executed by the automatic driving start-up device disclosed in the illustrated embodiment can be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor or the instructions in the form of software. The above-mentioned processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may 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. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0125] The electronic device can also execute Figure 1 the method executed by the automatic driving start-up device in Figure 1 the illustrated embodiment and implement the functions of the automatic driving start-up device in

[0126] Embodiments of the present application also propose a computer-readable storage medium. The computer-readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by an electronic device including multiple application programs, can enable the electronic device to execute Figure 1 the method executed by the automatic driving start-up device in the illustrated embodiment, and specifically used to execute:

[0127] Collect the status information in the modules participating in the vehicle's automatic driving function;

[0128] Receive the fault information of the modules participating in the vehicle's automatic driving function collected by the fault management module;

[0129] Judge whether the current system supports autonomous driving according to the state information and the fault information;

[0130] If autonomous driving is not supported, upload the abnormal information to the cockpit to restrict the response before the autonomous driving function is activated in the cockpit.

[0131] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0132] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram can be implemented by computer program instructions, and the combination of processes and / or blocks in the flowchart and / or block diagram can also be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for realizing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0133] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured product including an instruction device, and the instruction device realizes the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0134] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Therefore, the instructions executed on the computer or other programmable device provide steps for realizing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0135] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and a memory.

[0136] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0137] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0138] It should also be noted that the terms "include", "comprising" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of further restrictions, an element defined by the sentence "comprising a ..." does not exclude the presence of other identical elements in the process, method, commodity or device comprising the element.

[0139] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0140] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various modifications and changes can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. An automatic driving start method, wherein, Applied to the system status management module, the startup method includes: Collect status information in the modules participating in the vehicle's autonomous driving function; Receive the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module; Judge whether the current system supports autonomous driving according to the status information and the fault information; If autonomous driving is not supported, upload the abnormal information to the cockpit to restrict the response before starting the autonomous driving function in the cockpit.

2. The method according to claim 1, wherein The judging whether the current system supports autonomous driving according to the status information and the fault information includes: Generate a status summary information of the current system according to the status information in each of the modules; Generate a fault summary information according to the fault information in multiple of the modules; Generate an autonomous driving flag bit according to the status summary information of the current system and / or the fault summary information; Judge whether the current system supports autonomous driving according to the autonomous driving flag bit.

3. The method according to claim 2, wherein The collecting the status information in the modules participating in the vehicle's autonomous driving function includes: Receive the status information on multiple nodes obtained according to the autonomous driving conditions of the modules participating in the vehicle's autonomous driving function itself; Summarize the running status of the nodes in multiple of the modules as the basis for whether the current system status supports autonomous driving.

4. The method according to claim 2, wherein, The receiving the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module includes: Receive the fault information reported when each of the modules is abnormal; Summarize the fault information in multiple of the modules as the basis for whether the current system status supports autonomous driving.

5. The method according to claim 2, wherein The if autonomous driving is not supported, upload the abnormal information to the cockpit to restrict the response before starting the autonomous driving function in the cockpit includes: In the case that it is judged according to the autonomous driving flag bit that the current system does not support autonomous driving, upload the abnormal information to the cockpit to display the abnormality on the user operation interface of the cockpit and restrict the function of starting the autonomous driving in response; In the case that it is judged according to the autonomous driving flag bit that the current system supports autonomous driving, display normal on the user operation interface of the cockpit and respond to the function of starting the autonomous driving.

6. The method according to claim 1, the method further includes: Receive the scheduling instruction for starting the autonomous driving function issued by the cockpit; Send the scheduling instruction for starting the autonomous driving function to the modules participating in the vehicle's autonomous driving function.

7. The method according to any one of claims 1 to 6, the method further includes: If autonomous driving is not supported, upload the abnormal information to the cockpit to start the degraded operation before starting the autonomous driving function in the cockpit.

8. An automatic driving start device, wherein, Applied to the system status management module, the startup device includes: A collection module for collecting status information in the modules participating in the vehicle's autonomous driving function; A receiving module for receiving the fault information of the modules participating in the vehicle's autonomous driving function collected by the fault management module; A judging module for judging whether the current system supports autonomous driving according to the status information and the fault information; An upload module, configured to upload exception information to the cockpit if autonomous driving is not supported, so as to limit the response before the autonomous driving function is activated in the cockpit.

9. An electronic device, comprising: A processor; And A memory arranged to store computer-executable instructions, which when executed cause the processor to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium storing one or more programs, which when executed by an electronic device including a plurality of application programs, cause the electronic device to execute the method according to any one of claims 1 to 7.

Images