Vehicle control method, control system and vehicle

Abstract

The invention provides a vehicle control method and system and a vehicle. The method is applied to the technical field of intelligent driving. The method is applied to a multimedia host, and the multimedia host is in communication connection with an event data recorder. The method comprises the following steps: receiving event information sent by an event data recorder, wherein the event information is used for indicating that to-be-transmitted EDR data exists in the event data recorder; in response to the event information, sending a data request to an event data recorder; in response to the data request, receiving EDR data sent by the event data recorder; and displaying first prompt information in a display screen of the vehicle, wherein the first prompt information is used for prompting a user that the to-be-read EDR data exists. According to the method, the convenience of checking the EDR data can be improved.

Description

Technical Field

[0001] This application relates to the field of intelligent driving technology, and more specifically, to a vehicle control method, a control system, and a vehicle. Background Technology

[0002] With the rapid development of vehicle technology, users' demands for vehicle safety and accident analysis capabilities are constantly increasing. Event Data Recorders (EDRs), as devices that record critical vehicle data, can record accident data when an accident occurs.

[0003] In related technologies, EDR (Emergency Data Retrieval) stores accident data after detecting a collision event. When a user needs to retrieve the data, they must establish a connection with the vehicle using a third-party device and manually trigger a download request to obtain the accident data through the third-party device. However, since viewing accident data relies on a third-party device, it is inconvenient for users. Therefore, improving the convenience of viewing EDR data has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a vehicle control method, a control system, and a vehicle, which improves the convenience of viewing EDR data.

[0005] In a first aspect, this application provides a vehicle control method, which is applied to a multimedia host and is communicatively connected to an event data recorder; the method includes: receiving event information sent by the event data recorder, the event information indicating that there is EDR data to be transmitted in the event data recorder; in response to the event information, sending a data request to the event data recorder; in response to the data request, receiving EDR data sent by the event data recorder; and displaying a first prompt message on the vehicle's display screen, the first prompt message indicating to the user that there is EDR data to be read.

[0006] The above technical solution receives event information sent by the event data recorder, responds to the event information by sending a data request to the event data recorder, and responds to the data request by receiving EDR data sent by the event data recorder. A first prompt message is then displayed on the vehicle's screen, indicating to the user that there is EDR data to be read. Compared to existing technologies that rely on third-party devices to read EDR data, this application, through active interaction between the event data recorder and the multimedia host, can transmit EDR data to the multimedia host and prompt the user to read the EDR data, improving the user's understanding of the vehicle's status (avoiding user unawareness). Furthermore, the user only needs to perform an operation to intuitively view the EDR data, improving the convenience of viewing EDR data.

[0007] In one possible implementation, the method further includes: sending a download request to the event data logger; receiving response information of the download request sent by the event data logger in response to the download request; and sending a data request to the event data logger if the response information of the download request indicates that downloading is permitted.

[0008] In the above technical solution, the multimedia host sends a download request to the event data logger, and when the response information of the download request indicates that downloading is allowed, it sends a data request to the event data logger. By sending a download request to the event data logger, the multimedia host performs the data request after both parties have agreed to confirm the download event, thus ensuring the reliability and security of data transmission.

[0009] In one possible implementation, the data request includes a first data identifier, and the method further includes: receiving a second data identifier of EDR data sent by the event data recorder in response to the data request; verifying whether the EDR data is complete based on the first data identifier and the second data identifier; and displaying a second prompt message on the vehicle's display screen, the second prompt message being used to indicate whether the EDR data is complete.

[0010] The above technical solution receives the second data identifier of the EDR data sent by the event data recorder, and verifies whether the EDR data is complete based on the first data identifier and the second data identifier included in the data request, so as to display a second prompt message on the vehicle's display screen; by comparing the first data identifier in the data request sent by the multimedia host with the second data identifier of the EDR data sent by the EDR, the integrity of the EDR data is determined. This allows the user to directly determine the integrity of the EDR data when viewing it on the display screen, and thus handle the collision event based on the EDR data, improving user convenience.

[0011] In one possible implementation, the method further includes: obtaining the vehicle's current gear; and when the vehicle's current gear is park, displaying a first prompt message on the vehicle's display screen.

[0012] The above technical solution displays a first prompt message on the vehicle's display screen when the vehicle's current gear is park; by determining the vehicle's current gear, the first prompt message is displayed on the display screen only when the vehicle is in park, thus avoiding the impact of the prompt message on the driver during driving and ensuring driving safety.

[0013] In one possible implementation, the method further includes: in response to a user's viewing operation of EDR data, obtaining the user's identity information; and when the identity information indicates that the user is an authorized user, displaying the EDR data on the display screen.

[0014] The above technical solution, in response to a user's viewing operation of EDR data, obtains the user's identity information, and displays the EDR data on the screen when the identity information indicates that the user is an authorized user; by authenticating the user viewing the EDR data, it ensures that the user viewing the EDR data is an authorized user, ensures the security of the EDR data, and thus improves the user experience.

[0015] Secondly, this application provides a vehicle control method, which is applied to an event data recorder and is communicatively connected to a multimedia host. The method includes: when a collision event is detected in the vehicle, sending event information to the multimedia host, the event information indicating the existence of EDR data to be transmitted; in response to the event information, receiving a data request sent by the multimedia host; and in response to the data request, sending EDR data to the multimedia host, so that after receiving the EDR data, the multimedia host displays a first prompt message on the vehicle's display screen, the first prompt message indicating to the user that there is EDR data to be read.

[0016] The above technical solution, upon detecting a vehicle collision event, sends event information to the multimedia host. This event information indicates the existence of EDR data to be transmitted. In response to the event information, the system receives a data request from the multimedia host and, in response to the data request, sends EDR data back to the multimedia host. Upon receiving the EDR data, the multimedia host displays a first prompt message on the vehicle's screen, indicating the existence of EDR data to be read. By actively sending event information to the multimedia host, the event data recorder can inform the multimedia host of the existence of EDR data and complete the transmission of the EDR data through data interaction with the multimedia host. This allows the user to intuitively view the EDR data simply by performing a viewing operation on the screen, improving the convenience of viewing EDR data.

[0017] In one possible implementation, the method further includes: receiving a download request sent by a multimedia host; responding to the download request by sending a response message for the download request to the multimedia host; and receiving a data request sent by the multimedia host if the response message for the download request indicates that downloading is permitted.

[0018] The above technical solution receives data requests sent by the multimedia host when the response information of the download request indicates that downloading is allowed; by negotiating with the multimedia host before the data request, the reliability and efficiency of subsequent data transmission can be ensured.

[0019] In one possible implementation, the data request includes a first data identifier. The method further includes: in response to the data request, sending a second data identifier of the EDR data to the multimedia host, so that the multimedia host verifies whether the EDR data is complete based on the first data identifier and the second data identifier; the multimedia host displays a second prompt message on the vehicle's display screen, the second prompt message indicating whether the EDR data is complete.

[0020] The above technical solution sends a second data identifier of the EDR data to the multimedia host, so that the multimedia host can verify whether the EDR data is complete by using the first data identifier and the second data identifier and display it on the screen. By sending the data identifier synchronously during data transmission, the multimedia host can perform data integrity verification based on the data identifier and then display it on the screen, so that the user can clearly understand the integrity of the EDR data.

[0021] Thirdly, this application provides a vehicle control device configured in a multimedia host, which is communicatively connected to an event data recorder. The device includes: a communication module for receiving event information sent by the event data recorder, the event information indicating the existence of EDR data to be transmitted in the event data recorder; in response to the event information, sending a data request to the event data recorder; and in response to the data request, receiving EDR data sent by the event data recorder; and a processing module for displaying a first prompt message on the vehicle's display screen, the first prompt message indicating to the user that there is EDR data to be read.

[0022] In one possible implementation, the communication module is further configured to send a download request to the event data logger; receive a response message from the event data logger in response to the download request; and send a data request to the event data logger if the response message indicates that downloading is permitted.

[0023] In one possible implementation, the data request includes a first data identifier, and the communication module is further configured to receive a second data identifier of the EDR data sent by the event data logger in response to the data request; the processing module is further configured to verify whether the EDR data is complete based on the first data identifier and the second data identifier; and to display a second prompt message on the vehicle's display screen, the second prompt message being used to indicate whether the EDR data is complete.

[0024] In one possible implementation, the communication module is used to obtain the vehicle's current gear; when the vehicle's current gear is park, a first prompt message is displayed on the vehicle's display screen.

[0025] In one possible implementation, the processing module is further configured to obtain the user's identity information in response to the user's viewing operation of EDR data; and display the EDR data on the display screen when the identity information indicates that the user is an authorized user.

[0026] Fourthly, this application provides a vehicle control device configured in an event data recorder, the event data recorder being communicatively connected to a multimedia host; the device includes: a communication module, configured to send event information to the multimedia host when a collision event is detected, the event information indicating the existence of EDR data to be transmitted; in response to the event information, receiving a data request sent by the multimedia host; and in response to the data request, sending EDR data to the multimedia host, so that after receiving the EDR data, the multimedia host displays a first prompt message on the vehicle's display screen, the first prompt message indicating to the user that there is EDR data to be read.

[0027] In one possible implementation, the communication module is further configured to receive a download request sent by the multimedia host; in response to the download request, send a response message for the download request to the multimedia host; and, if the response message for the download request indicates that downloading is permitted, receive a data request sent by the multimedia host.

[0028] In one possible implementation, the data request includes a first data identifier, and the communication module is further configured to respond to the data request by sending a second data identifier of the EDR data to the multimedia host, so that the multimedia host can verify whether the EDR data is complete based on the first data identifier and the second data identifier; the multimedia host displays a second prompt message on the vehicle's display screen, the second prompt message being used to indicate whether the EDR data is complete.

[0029] Fifthly, this application provides a vehicle alerting system, including a multimedia host and an event data recorder; wherein the multimedia host is used to execute the vehicle control method in the first aspect or any possible implementation of the first aspect; and the event data recorder is used to execute the vehicle control method in the second aspect or any possible implementation of the second aspect.

[0030] Sixthly, this application provides a vehicle, including a memory and a processor, wherein the memory is used to store executable program code; and the processor is used to call and run the executable program code from the memory, causing the vehicle to execute the vehicle control method in the first aspect or any possible implementation thereof, or to execute the vehicle control method in the second aspect or any possible implementation thereof.

[0031] In a seventh aspect, this application provides a computer-readable storage medium storing computer program code that, when executed on a computer, causes the computer to perform the vehicle control method of the first aspect or any possible implementation thereof, or to perform the vehicle control method of the second aspect or any possible implementation thereof.

[0032] Eighthly, this application provides a computer program product comprising: computer program code, which, when executed on a computer, causes the computer to execute the vehicle control method in the first aspect or any possible implementation thereof, or to execute the vehicle control method in the second aspect or any possible implementation thereof. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of a vehicle control method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the framework of a vehicle control system provided in an embodiment of this application; Figure 3 This is a schematic flowchart of a vehicle control method provided in an embodiment of this application; Figure 4 This is a schematic flowchart of another vehicle control method provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a vehicle control device provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of another vehicle control device provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application. Detailed Implementation

[0034] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0035] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0036] To facilitate understanding of the technical solutions in the embodiments of this application, some terms involved in the embodiments of this application will be briefly explained below.

[0037] Event Data Recorder (EDR): An EDR is an onboard device that records vehicle operational data before and after a collision. When a vehicle triggers an EDR event (such as the deployment of airbags or a change in longitudinal acceleration exceeding a preset threshold), the EDR records critical operational data of the vehicle at the time of the accident.

[0038] EDR data, also known as Event Data Recorder data, is the vehicle's operational data at the time of a collision. It provides precise data evidence for traffic accident investigation and analysis, helping to reconstruct the event. EDR data includes, but is not limited to: vehicle speed, braking status, throttle opening, steering angle, seatbelt usage, number of airbags deployed, turn signals, speed changes before and after the collision, and the time of the event.

[0039] Head Unit Terminal (HUT): The HUT is the core device of the vehicle's infotainment system. It can receive and process signals from multiple data sources and output the corresponding data to the vehicle's display screen and speakers.

[0040] With the rapid development of vehicle technology, users' demands for vehicle safety and accident analysis capabilities are constantly increasing. Event data recorders, as devices that record critical vehicle data, can record accident data when an accident occurs.

[0041] In related technologies, EDR (Emergency Data Retrieval) stores accident data after detecting a collision event. When a user needs to retrieve the data, they must establish a connection with the vehicle using a third-party device and manually trigger a download request to obtain the accident data through the third-party device. However, because viewing the accident data relies on a third-party device, the user is unaware that the EDR data is recorded in the vehicle and does not know the specific EDR data recorded. Therefore, in scenarios involving minor collisions, even if the vehicle is not seriously damaged, users cannot easily obtain EDR data, causing inconvenience.

[0042] In view of this, this application proposes a vehicle control method, a control system, and a vehicle. Through the embodiments of this application, by actively interacting with the multimedia host through an event data logger, EDR data can be transmitted to the multimedia host, and the user is prompted to read the EDR data. This avoids the user being unaware of a vehicle collision event, improves the user's understanding of the vehicle's status, and enhances the user's confidence in vehicle safety. Furthermore, when the user needs to view EDR data, the user only needs to perform a viewing operation to view the EDR data, improving the convenience of viewing EDR data and thus enhancing the user experience.

[0043] To better understand the embodiments of this application, the application scenarios of the vehicle control method in the embodiments of this application are illustrated below.

[0044] Figure 1 This is a schematic diagram of a vehicle control method provided in an embodiment of this application.

[0045] For example, such as Figure 1 As shown, if vehicle 100 detects airbag deployment or the change in longitudinal acceleration of vehicle 100 exceeds a preset threshold (e.g., 8 km / h), a collision event is determined, and the EDR records key operational data of vehicle 100 at the time of the collision. Upon detecting a collision event, the EDR automatically sends event information to the HUT, prompting the HUT to actively send a data request to the EDR. Upon receiving the EDR data, the HUT displays a prompt message on the vehicle 100's screen to alert the user that unread EDR data exists.

[0046] Data interaction between HUT and EDR can be achieved without the need for third-party devices. EDR data can be sent to HUT, and users only need to make selections on HUT to view the EDR data, which improves the convenience of users viewing EDR data.

[0047] The following is combined Figure 2 The vehicle's control system will be introduced.

[0048] Figure 2 This is a schematic diagram of the framework of a vehicle control system provided in an embodiment of this application.

[0049] For example, such as Figure 2 As shown, the vehicle's control system 200 includes EDR 210 and HUT 220.

[0050] In the vehicle's control system 200, the EDR 210 is communicatively connected to the HUT 220. When the EDR 210 detects a collision event, it sends event information to the HUT 220, such as via a Controller Area Network (CAN) signal, to inform the HUT 220 of the existence of EDR data to be transmitted. Upon receiving the event information, the HUT 220 interacts with the EDR 210 to download and convert the EDR data into visualized data, displaying a prompt on the screen to indicate the existence of EDR data to be read. The user can view the EDR data simply by observing the operation.

[0051] By configuring EDR 210 in the vehicle's control system 200 and interacting with HUT 220 through EDR 210, users can view EDR data through the central control screen. EDR data includes, but is not limited to, data such as vehicle speed, braking status, and steering wheel angle.

[0052] Users can view EDR data. The vehicle's control system 200 also supports data export through multiple channels, including but not limited to: USB flash drive copying, Bluetooth transfer, and Wi-Fi connection and transfer to mobile devices. Users can choose the most convenient export method according to their needs, ensuring secure and convenient data transmission.

[0053] Figure 3 This is a schematic flowchart of a vehicle control method provided in an embodiment of this application.

[0054] For example, Figure 3 The vehicle control method shown can be executed interactively between the vehicle's multimedia host and the event data recorder; wherein, the event data recorder can be, for example, Figure 2 The EDR 210 shown can have a multimedia host (HUT) as follows: Figure 2 The HUT 220 shown.

[0055] Figure 3 The vehicle control method shown can be executed by the vehicle's multimedia host or chip; wherein, the multimedia host (HUT) can be, for example... Figure 2 The HUT 220 shown.

[0056] For example, such as Figure 3 As shown, the vehicle control method 300 includes S310 to S340.

[0057] S310, EDR sends event information to HUT when a collision event is detected.

[0058] For example, the EDR determines that a collision event has been detected when it detects that the airbags in the vehicle have deployed. Alternatively, the EDR determines that a collision event has been detected when it detects that the absolute value of the vehicle's longitudinal or lateral acceleration exceeds a preset threshold. A collision event refers to a vehicle triggering an EDR event, that is, the EDR begins recording the vehicle's state data.

[0059] Optionally, upon detecting a vehicle collision event, the EDR sends event information to the HUT, indicating that there is EDR data to be output. This event information informs the HUT to retrieve the EDR data.

[0060] For example, EDR can send event information to HUT immediately upon detecting a collision event; or it can send event information to HUT when the vehicle is in a stable state after detecting a collision event; no specific limitation is made here.

[0061] S320, HUT sends a data request to EDR.

[0062] For example, upon detecting a collision event, the EDR sends an event message to the HUT, indicating that there is EDR data to be transmitted in the EDR, thus prompting the HUT to make a data request. Upon receiving the event message from the EDR, the HUT sends a data request to the EDR, requesting the EDR to transmit the EDR data.

[0063] Optionally, after receiving the event information sent by EDR, HUT responds by sending a data request to EDR. Alternatively, after receiving the event information from EDR, HUT can also send a download request to EDR to authenticate HUT, facilitating subsequent EDR data transmission.

[0064] For example, the multimedia host receives event information sent by the event data logger, and in response to the event information, sends a download request to the event data logger. In response to the download request, the multimedia host receives a response message from the event data logger; if the response message indicates that downloading is permitted, the multimedia host sends a data request to the event data logger.

[0065] Upon receiving a download request from the HUT, the EDR can perform a security check on the HUT. If the security check passes, the EDR sends a response to the download request to the HUT, including whether downloading is allowed and the data transmission rules. Upon receiving the response, if the response indicates that downloading is allowed, the HUT sends a data request to the EDR according to the transmission rules required by the EDR.

[0066] Optionally, after receiving a download request from the HUT, the DER will perform data transmission condition determination and data transmission security verification. For example, if the download request from the HUT fails the security access verification, the data transmission condition is determined to be insecure; or, if the HUT needs to unlock or authorize the download request, but is currently in a locked or unauthorized state, the EDR will send the download request response information to the HUT.

[0067] In the above technical solution, the multimedia host sends a download request to the event data logger, and when the response information of the download request indicates that downloading is allowed, it sends a data request to the event data logger. By sending a download request to the event data logger, the multimedia host performs the data request after both parties have agreed to confirm the download event, thus ensuring the reliability and security of data transmission.

[0068] S330, EDR sends EDR data to HUT.

[0069] For example, when HUT receives event information sent by EDR, HUT sends a data request to EDR so that EDR sends EDR data to HUT.

[0070] Upon detecting a collision event, the EDR sends event information to the HUT. In response, the HUT sends a data request to the EDR. Upon receiving the data request, the EDR sends its data back to the HUT. This allows the HUT to display a subtle prompt on its screen upon receiving the EDR data, alerting the user to the presence of EDR data to be read.

[0071] To ensure user convenience in viewing data, the integrity of EDR data can also be verified.

[0072] In one example, the data request includes a first data identifier; in response to the data request, a second data identifier of EDR data sent by the event data logger is received; the EDR data is verified to be complete based on the first data identifier and the second data identifier; and a second prompt message is displayed on the vehicle's display screen to indicate whether the EDR data is complete.

[0073] Specifically, HUT sends a data request to EDR, which includes a first data identifier, representing the data content requested by HUT from EDR. Upon receiving the data request, EDR sends EDR data and a second data identifier to HUT, indicating the content of the EDR data. HUT then verifies whether the EDR data is complete based on the first and second data identifiers.

[0074] Understandably, whether the EDR data is complete indicates whether the EDR data corresponds to the complete data of the first identifier data requested by the HUT. That is, the HUT request data includes the first data identifier indicating the data currently requested by the HUT, the EDR data sent by the DER data, and the second data identifier indicating the currently sent EDR data. By comparing the consistency of the first data identifier and the second data identifier, the completeness of the EDR data can be fully verified.

[0075] The above technical solution receives the second data identifier of the EDR data sent by the event data recorder, and verifies whether the EDR data is complete based on the first data identifier and the second data identifier included in the data request, so as to display a second prompt message on the vehicle's display screen; by comparing the first data identifier in the data request sent by the multimedia host with the second data identifier of the EDR data sent by the EDR, the integrity of the EDR data is determined. This allows the user to directly determine the integrity of the EDR data when viewing it on the display screen, and thus handle the collision event based on the EDR data, improving user convenience.

[0076] In another example, the data request includes a first data identifier; in response to the data request, a second data identifier is received from the event data logger sending EDR data; the EDR data is verified to be complete based on the first and second data identifiers; if the EDR data is complete based on the first and second data identifiers, a second prompt message is displayed on the screen indicating that the EDR data is complete. If the EDR data is missing based on the first and second data identifiers, and the number of verifications is greater than or equal to a preset number, a second prompt message is displayed on the screen indicating that the EDR data is missing.

[0077] Understandably, missing EDR data indicates that the collision event caused hardware damage to the vehicle, resulting in a gap in the vehicle data collection process and thus missing EDR data.

[0078] Optionally, the preset number of times can be 3, 4, etc., and the preset number of times can be determined according to the actual situation. No specific limit is made here.

[0079] Taking a preset number of checks as an example (3 checks), the data request includes a first data identifier and a second data identifier received by the HUT from the EDR data sent by the event data logger. Based on the first and second data identifiers, the HUT verifies whether the EDR data is complete. If the EDR data is complete based on the first and second data identifiers, and the number of checks is less than 3, a second prompt message is displayed on the screen indicating that the EDR data is complete. If the EDR data is missing based on the first and second data identifiers, and the number of checks is greater than or equal to 3, a second prompt message is displayed on the screen indicating that the EDR data is missing.

[0080] The above technical solution, by repeatedly confirming the missing data, can avoid the problem of EDR data loss caused by interference during transmission, and improve the integrity of the EDR data displayed on the HUT control display screen.

[0081] The following section describes the data transmission between HUT and EDR via the Unified Diagnostic Services (UDS) protocol. The UDS protocol is a communication protocol whose core functions include reading fault codes, clearing fault codes, reading data streams, and reading / writing memory, enabling vehicle data synchronization. The following section provides a detailed introduction to the data transmission between HUT and EDR via the UDS protocol.

[0082] HUT and EDR communicate via a CAN-FD network (or a communication connection), with a physical layer transmission rate of 500 kbit / s and a maximum single frame data of 64 bytes. At the application layer, HUT and EDR interact according to the UDS protocol: when HUT needs to read EDR data, it sends a request to EDR using the diagnostic identifier 0x7E1, and EDR responds using the identifier 0x7E2.

[0083] HUT sends 0x10 0x03 to EDR to enter an extended session, specifically through the UDS service 0x10 (Diagnostic Session Control) to send 0x03 (Extended Session), causing EDR to enter "Data Transfer Mode". Then, it sends the 0x31 0x01 0x02 instruction to initiate the EDR "Upload Event" routine. Further, HUT sends 0x34 0x00 0x44 to EDR to request a download (or download request), which includes a starting address of 0x08040000 and a length of 16kB. EDR replies to HUT with a response to the download request, indicating whether downloading and transfer rules are allowed, or whether downloading is not permitted.

[0084] If the response to the download request indicates that downloading is permitted, HUT continuously sends 0x36 Transfer Data requests (or data requests, with the request block identified by the first data identifier) ​​to EDR in 4KB blocks. EDR responds with 0x76, returning the corresponding block data (i.e., EDR data and its corresponding second data identifier, which is the returned block). Since the maximum CAN single-frame data is 64 bytes, 16KB needs to be divided into 4 blocks (4KB×4), with each block requested using 0x36. By using block requests, if a block of data fails to be transmitted, the first and second data identifiers can be used to determine the data's origin, and HUT will repeat the request multiple times to avoid data loss. After all data transmission is complete, HUT sends a 0x37 Request Transfer Exit command to EDR to end the entire interaction process, using EDR to terminate the transmission and release resources.

[0085] Understandably, due to the limited data transmission capacity of a single frame, EDR data can be transmitted in multiple blocks. Since HUT can request data block by block, it can utilize EDR for block-based transmission. Furthermore, during transmission, HUT verifies the data for each transmission to ensure data integrity.

[0086] In the above technical solution, HUT first sends a command to enter extended session mode, then starts the "upload event" routine, and sends a download request to EDR, specifying the starting address and length of the data in EDR. Based on this, HUT requests data blocks in 4kB units in a loop, and EDR responds to each request; after all data blocks have been transmitted, HUT sends a command to end the current diagnostic session, thus completing a full event data reading process.

[0087] S340, HUT displays the first prompt message on the screen.

[0088] For example, when the EDR detects a collision event, it sends event information to the HUT. In response, the HUT sends a data request to the EDR, causing the EDR to send EDR data to the HUT. This prompts the HUT to display a first notification message on its display screen (the vehicle's central control display screen, used to display and operate various vehicle functions). The first notification message informs the user that there is EDR data to be read. By displaying the first notification message on the screen, the user can see the notification and then access the EDR data through the viewing operation.

[0089] To improve vehicle safety, a warning is given when the vehicle is stationary.

[0090] For example, when HUT receives EDR data sent by EDR, it obtains the current gear of the vehicle and displays a first prompt message on the vehicle's display screen when the current gear of the vehicle is the parking gear.

[0091] Specifically, after receiving EDR data, HUT obtains the vehicle's current gear and determines whether the current gear is the parking gear. When the vehicle's current gear is the parking gear, a first prompt message is displayed on the vehicle's display screen; when the vehicle's current gear is not the parking gear, the system continuously monitors the vehicle's gear until the vehicle shifts to the parking gear, at which point the first prompt message is displayed on the vehicle's display screen.

[0092] The above technical solution displays a first prompt message on the vehicle's display screen when the vehicle's current gear is park; by determining the vehicle's current gear, the first prompt message is displayed on the display screen only when the vehicle is in park, thus avoiding the impact of the prompt message on the driver during driving and ensuring driving safety.

[0093] The following is an introduction to EDR data.

[0094] Table 1

[0095] Table 1 shows the static data in the EDR data.

[0096] The data shown in Table 1 are all static data from the EDR (Electronic Data Recognition) system, meaning data that will not change due to a collision event. Each data point has a corresponding description and data type. It is understood that the Vehicle Identification Number (VIN) is a unique identifier for a vehicle. The ECU (Electronic Control Unit) is an embedded control system in the vehicle composed of a microcontroller. The SRS (Supplemental Restraint System) is a passive safety system used to assist in protecting occupants during a collision. The ABS (Anti-lock Braking System) is an active safety system that prevents wheels from locking up during braking to maintain steering capability and stability. The DTC (Diagnostic Trouble Code) is a diagnostic fault code; when the ECU detects a fault within the system or in related sensors or actuators, it stores a specific standardized code indicating the location and type of the fault.

[0097] Table 2

[0098] Table 2 shows the collision data in the EDR data.

[0099] The data shown in Table 2 are vehicle change data collected under the condition of a collision event. It can be understood that PDOF (Principal Direction of Force) is the direction of the resultant force in a collision. PDOF refers to the main direction of the resultant force acting on the center of gravity of the vehicle during the collision.

[0100] Table 3

[0101] Table 3 shows the airbag deployment command data when a vehicle triggers a collision event.

[0102] As shown in Table 3, when the vehicle detects the deployment of any airbag, a collision event is determined, and the EDR begins saving collision data. It's understandable that the EDR saves vehicle data as the vehicle moves, but when no collision event is triggered, it continuously updates the data, overwriting historical data. However, in the event of a collision, the EDR locates data from a preset time period prior to the collision event and stores and transmits this data, along with the data at the time of the collision, to the HUT.

[0103] Table 4

[0104] Table 4 shows the vehicle data for the 5 seconds prior to the collision event.

[0105] As shown in Table 4, in the event of a collision, EDR can provide a basis for subsequent accident judgment or analysis by recalling vehicle data within 5 seconds prior to the collision (a preset, calibrable time period). It is understandable that ESP (Electronic Stability Program) is an active safety system that actively applies braking force to one or more wheels and may intervene in engine torque to prevent vehicle skidding or loss of control (such as understeer or oversteer). TCS (Traction Control System) is a traction control system. When the drive tires tend to slip during vehicle start-up or acceleration, the system restores tire grip and ensures driving stability by reducing engine torque or applying braking to the slipping wheels. SOC (State of Charge) is the state of charge (or remaining battery charge), usually expressed as a percentage, referring to the ratio of the current remaining charge in the battery to its total capacity when fully charged. In addition, motor speed, battery SOC, battery temperature, and energy recovery status are unique parameters for new energy vehicles.

[0106] Table 5

[0107] Table 5 shows the vehicle trajectory data collected after a collision.

[0108] As shown in Table 5, the vehicle trajectory data collected after a collision includes, but is not limited to: longitudinal velocity change, lateral velocity change, vehicle rollover angle, time interval between consecutive collisions, and final stationary position.

[0109] It is understood that in the aforementioned disclosed embodiments, EDR data is only one type of data content that may actually be used. The EDR data type and data content can be adaptively added or removed according to actual needs, and no specific limitations are made here.

[0110] For example, in response to a user's operation to view EDR data, the user's identity information is obtained; when the identity information indicates that the user is an authorized user, the EDR data is displayed on the screen. Since the vehicle's screen displays a first prompt message and a second prompt message, the user views the EDR data by performing a viewing operation on the control corresponding to the EDR data to be read.

[0111] For example, when HUT detects a user clicking on a view control, it determines that the user needs to view EDR data. To ensure the security of the EDR data, it acquires the user's identity information through in-vehicle sensors and matches this information with the identity information of authorized users. If the user's identity information indicates that the user is not an authorized user, a third prompt message is displayed on the screen, prompting the user to authorize their identity before viewing the EDR data. If the user's identity information indicates that the user is an authorized user, the EDR data is displayed on the screen.

[0112] The above technical solution, in response to a user's viewing operation of EDR data, obtains the user's identity information, and displays the EDR data on the screen when the identity information indicates that the user is an authorized user; by authenticating the user viewing the EDR data, it ensures that the user viewing the EDR data is an authorized user, ensures the security of the EDR data, and thus improves the user experience.

[0113] For example, in response to a user's viewing of historical EDR data, HUT retrieves a list of historical data indicating the EDR data corresponding to historical collision events. The historical data list is displayed on the screen. Upon detecting a user's selection of a target event from the historical data list, the target EDR data corresponding to that target event is displayed on the screen.

[0114] For example, a user selects "Vehicle Health" on the central control screen to open the vehicle health interface, and then selects "EDR Records" within the vehicle health interface. The display shows a list of historical EDR data (as shown in Table 6). The user can then view the corresponding EDR data (or target EDR data) by clicking on a file link. It's understandable that when the user clicks the link, they select the event corresponding to that link as the target event. At the HUT underlying level, after the user clicks to view historical EDR data, EdrService.read() is called to display the EDR data.

[0115] Table 6

[0116] Table 6 is a schematic diagram of the historical data list.

[0117] As shown in Table 6, when a user chooses to view historical EDR data, they can select the corresponding event to view the corresponding EDR data. Of course, when viewing the current EDR data, the user can also switch to the historical data list display interface using the historical data control in the display interface.

[0118] For example, EDR and HUT store data in different formats. Therefore, after receiving EDR data, HUT performs data conversion and visualization processing so that users can view the readable EDR data on the display screen by clicking the view button. It can be understood that HUT needs to convert the EDR data sent by EDR and then store it. EDR data conversion refers to the conversion of the data format; the data content itself remains unchanged.

[0119] Upon receiving EDR data from EDR, HUT parses the EDR data and performs visualization processing to obtain readable EDR data. In response to a user's request to view the EDR data, it retrieves the user's identity information. If the identity information indicates the user is authorized, it displays the readable EDR data on the screen.

[0120] The following section introduces the process of HUT parsing and visualizing EDR data.

[0121] Byte order conversion: EDR stores data in big-endian format; HUT stores data in little-endian format, meaning HUT's processor (Advanced RISC Machine, ARM) uses little-endian byte order. In big-endian, the most significant byte comes first, followed by the least significant byte, such as 0x1234 representing 12*256+34=3092; while in little-endian, the least significant byte comes first, such as 0x1234 representing 34*256+12=8724. Therefore, byte order conversion is necessary.

[0122] Signal extraction is performed according to the signal extraction formula: Since the EDR data sent by the EDR is a 16-bit raw value (Raw16), Raw16 refers to the raw binary integer value output from the controller's analog-to-digital converter without any physical quantity conversion or processing, and its value ranges from 0 to 65535. The corresponding signal data is obtained by calculating the Raw16 value using the conversion formula corresponding to each signal. It is understandable that the Raw16 value may differ for different signals. For example, the expression for vehicle speed can be as follows: ; Where V represents vehicle speed, and Raw16 is a 16-bit raw value. By converting Raw16, the actual vehicle speed (unit: km / h) can be obtained. For example, if Raw16 is 4520, the vehicle speed is 45.2 km / h.

[0123] The steering wheel angle can be expressed as follows: ; Where θ represents the steering wheel angle, and Raw16 is a 16-bit raw value. By converting Raw16, the steering wheel angle (unit: °) can be obtained. A positive steering wheel angle indicates the opposite direction of vehicle rotation to a negative steering wheel angle; for example, a positive steering wheel angle indicates right turn, and a negative steering wheel angle indicates left turn.

[0124] The expression for longitudinal acceleration can be given as follows: ; Here, A represents the vehicle's longitudinal acceleration. When Raw16 ≥ 0, the vehicle's longitudinal acceleration is Raw16 * 0.001; otherwise, the vehicle's longitudinal acceleration is (Raw16 - 65536) * 0.001. It's important to understand that whether Raw16 is greater than 0 is not determined by the numerical value itself, but by the physical meaning it represents. For example, if Raw16 is negative when its value is between 0 and 32768, then any value between 0 and 32768 represents a value less than 0.

[0125] During time base restoration, the first frame timestamp is the Real-Time Clock (RTC) second value, and subsequent timestamps increment by 10ms. For missing frames, linear interpolation is used; that is, each subsequent frame timestamp is the previous frame timestamp plus 10ms. Linear interpolation is used to calculate the time of the missing frame. Key event markers include braking start point, collision point, and steering anomaly. In the braking start point (brake switch), a brake pedal state of 0 indicates the brake pedal is not depressed, and 1 indicates the brake pedal is depressed. The collision point T0 is the first airbag trigger frame. A steering anomaly occurs when the ratio of the change in steering wheel angle to the change in event value exceeds a preset threshold, such as |Δθ / Δt|>300° / s. This means the ratio of the change in steering wheel angle Δθ to the change in time Δt, i.e., the rate of change of steering wheel angle exceeds the preset threshold of 300° / s, and is thus marked as a steering anomaly.

[0126] Visualization: JSON is read via Binder IPC, and the three-axis curves are rendered. Text summaries are generated by a template engine and broadcast via TTS. For example, a red broken line represents vehicle speed changes, with a vertical marker line superimposed at the moment of collision; a green bar chart represents longitudinal acceleration, with automatic range scaling activated. A blue stepped line represents steering wheel angle, calculated based on the rate of change of angle, with areas exceeding a preset threshold (e.g., 300° / s) highlighted. Furthermore, users can view values ​​by clicking, add annotations by long-pressing chart content, and zoom and pan the timeline using two-finger touch gestures. Additionally, when EDR data is displayed on the screen, users can export the data to a USB drive or transfer it to a mobile device via Bluetooth or Wi-Fi if needed.

[0127] HUT possesses EDR data reading and parsing capabilities. By reading, parsing, and displaying EDR data, users can view it through the central control screen. Through the visualization of the displayed data, users can quickly find the required EDR data on the interactive interface and export the data if needed. For example, after viewing the EDR data, users can generate a data report for viewing and downloading by selecting an operation. A document password can be configured before downloading to ensure the security of the downloaded data. Furthermore, EDR data processing has a low load (low total overhead for data download and parsing), with a peak CPU single-core usage of 25% and a peak memory usage of 6MB. It can support concurrent reading at 0 vehicle speed without affecting the normal driving CAN load (less than 5%). Therefore, by forming a closed loop through EDR reading and storage, algorithm parsing, and UI display, HUT can present raw binary EDR events as visual icons and text data within one second without the need for external devices. Users only need to perform viewing operations to view the EDR data, significantly reducing the complexity of using or viewing EDR data.

[0128] The above technical solution receives event information sent by the event data recorder, responds to the event information by sending a data request to the event data recorder, and responds to the data request by receiving EDR data sent by the event data recorder. A first prompt message is then displayed on the vehicle's screen, indicating to the user that there is EDR data to be read. Compared to existing technologies that rely on third-party devices to read EDR data, this application, through active interaction between the event data recorder and the multimedia host, can transmit EDR data to the multimedia host and prompt the user to read the EDR data, improving the user's understanding of the vehicle's status (avoiding user unawareness). Furthermore, the user only needs to perform an operation to intuitively view the EDR data, improving the convenience of viewing EDR data.

[0129] For example, the event data recorder is communicatively connected to the multimedia host; when the event data recorder detects a collision event in the vehicle, it sends event information to the multimedia host, the event information indicating the existence of EDR data to be transmitted; in response to the event information, it receives a data request sent by the multimedia host; in response to the data request, the event data recorder sends EDR data to the multimedia host, so that after receiving the EDR data, the multimedia host displays a first prompt message on the vehicle's display screen, the first prompt message indicating to the user that there is EDR data to be read.

[0130] The above technical solution, upon detecting a vehicle collision event, sends event information to the multimedia host. This event information indicates the existence of EDR data to be transmitted. In response to the event information, the system receives a data request from the multimedia host and, in response to the data request, sends EDR data back to the multimedia host. Upon receiving the EDR data, the multimedia host displays a first prompt message on the vehicle's screen, indicating the existence of EDR data to be read. By actively sending event information to the multimedia host, the event data recorder can inform the multimedia host of the existence of EDR data and complete the transmission of the EDR data through data interaction with the multimedia host. This allows the user to intuitively view the EDR data simply by performing a viewing operation on the screen, improving the convenience of viewing EDR data.

[0131] For example, a download request is received from a multimedia host; in response to the download request, a response message for the download request is sent to the multimedia host; and if the response message for the download request indicates that downloading is permitted, a data request is received from the multimedia host.

[0132] The above technical solution receives data requests sent by the multimedia host when the response information of the download request indicates that downloading is allowed; by negotiating with the multimedia host before the data request, the reliability and efficiency of subsequent data transmission can be ensured.

[0133] For example, the data request includes a first data identifier, and in response to the data request, a second data identifier of the EDR data is sent to the multimedia host, so that the multimedia host can verify whether the EDR data is complete based on the first data identifier and the second data identifier; the multimedia host displays a second prompt message on the vehicle's display screen, the second prompt message being used to indicate whether the EDR data is complete.

[0134] The above technical solution sends a second data identifier of the EDR data to the multimedia host, so that the multimedia host can verify whether the EDR data is complete by using the first data identifier and the second data identifier and display it on the screen. By sending the data identifier synchronously during data transmission, the multimedia host can perform data integrity verification based on the data identifier and then display it on the screen, so that the user can clearly see the integrity of the EDR data.

[0135] Figure 4 This is a schematic flowchart of another vehicle control method provided in the embodiments of this application.

[0136] For example, Figure 4 The vehicle control method shown can be executed interactively between the vehicle's multimedia host and the event data recorder; wherein, the event data recorder can be, for example, Figure 2The EDR 210 shown can have a multimedia host (HUT) as follows: Figure 2 The HUT 220 shown.

[0137] For example, such as Figure 4 As shown, the vehicle control method 400 includes S410 to S480.

[0138] S410, EDR sends event information to HUT when a collision event is detected.

[0139] For example, the EDR determines that a collision event has been detected when it detects that the airbags in the vehicle have deployed. Alternatively, the EDR determines that a collision event has been detected when it detects that the absolute value of the vehicle's longitudinal or lateral acceleration exceeds a preset threshold. A collision event refers to a vehicle triggering an EDR event, that is, the EDR begins recording the vehicle's state data.

[0140] Optionally, upon detecting a vehicle collision event, the EDR sends event information to the HUT, indicating that there is EDR data to be output. This event information informs the HUT to retrieve the EDR data.

[0141] S420, HUT sends a download request to EDR.

[0142] For example, upon receiving a download request from the HUT, the EDR can perform a security verification on the HUT. After successful verification, the EDR sends a response to the download request to the HUT, including whether downloading is allowed and data transmission rules. The multimedia host sends a download request to the event data logger, ensuring the reliability and security of data transmission by confirming the download event through mutual agreement.

[0143] S430, EDR sends a response message to HUT regarding the download request.

[0144] For example, the multimedia host receives event information sent by the event data logger. In response to the event information, the multimedia host sends a download request to the event data logger. In response to the download request, the multimedia host receives a response from the event data logger, which includes whether downloading is allowed and data transmission rules. After receiving the response, if the response indicates that downloading is allowed, the HUT sends a data request to the EDR according to the transmission rules required by the EDR.

[0145] Optionally, after receiving a download request from the HUT, the DER will perform data transmission condition determination and data transmission security verification. For example, if the download request from the HUT fails the security access verification, the data transmission condition is determined to be insecure; or, if the HUT needs to unlock or authorize the download request, but is currently in a locked or unauthorized state, the EDR will send the download request response information to the HUT.

[0146] S440, if the response information of the download request indicates that the download is allowed, HUT sends a data request to EDR, the data request including a first data identifier.

[0147] For example, if the response information of the download request indicates that the download is permitted, a data request is sent to the event data logger. The data request includes a first data identifier, namely the data content that HUT requested from EDR.

[0148] S450, EDR sends EDR data and a second data identifier to HUT.

[0149] For example, the data request includes a first data identifier. In response to the data request, the second data identifier of the EDR data sent by the event data logger, i.e., the data content requested by HUT from the EDR, is received. Based on the first data identifier and the second data identifier, it is verified whether the EDR data is complete data.

[0150] Specifically, HUT sends a data request to EDR, which includes a first data identifier, representing the data content requested by HUT from EDR. Upon receiving the data request, EDR sends EDR data and a second data identifier to HUT, indicating the content of the EDR data. HUT then verifies whether the EDR data is complete based on the first and second data identifiers.

[0151] S460, HUT verifies whether the EDR data is complete based on the first data identifier and the second data identifier.

[0152] For example, whether the EDR data is complete indicates whether the EDR data corresponds to the complete data of the first identifier data requested by the HUT. That is, the HUT request data includes the first data identifier indicating the data currently requested by the HUT, the EDR data sent by the DER data, and the second data identifier indicating the currently sent EDR data. By comparing the consistency between the first data identifier and the second data identifier, the completeness of the EDR data can be fully verified.

[0153] When the S470 HUT is in the parking gear, it displays a first and a second notification message on the screen.

[0154] For example, when HUT receives EDR data sent by EDR, it obtains the vehicle's current gear position. When the vehicle's current gear position is parking, it displays a first prompt message and a second prompt message on the vehicle's display screen. The first prompt message is used to prompt the user that there is EDR data to be read, and the second prompt message is used to prompt whether the EDR data is complete.

[0155] Specifically, after receiving the EDR data, HUT obtains the vehicle's current gear and determines whether it is the parking gear. When the vehicle's current gear is the parking gear, a first and a second prompt message are displayed on the vehicle's screen. When the vehicle's current gear is not the parking gear, the system continuously monitors the vehicle's gear until the vehicle shifts to the parking gear, at which point the first and second prompt messages are displayed on the vehicle's screen.

[0156] S480, HUT detects a user's viewing operation on EDR data and obtains the user's identity information; when the identity information indicates that the user is an authorized user, it displays the EDR data on the display screen.

[0157] For example, in response to a user's operation to view EDR data, the user's identity information is obtained; when the identity information indicates that the user is an authorized user, the EDR data is displayed on the screen. Since the vehicle's screen displays a first prompt message and a second prompt message, the user views the EDR data by performing a viewing operation on the control corresponding to the EDR data to be read.

[0158] For example, when HUT detects a user clicking on a view control, it determines that the user needs to view EDR data. To ensure the security of the EDR data, in-vehicle sensors acquire the user's identity information and match it with the identity information of authorized users. If the user's identity information indicates that the user is not an authorized user, a third prompt message is displayed on the screen, prompting the user to authorize their identity before viewing the EDR data. If the user's identity information indicates that the user is an authorized user, the EDR data is displayed on the screen. Viewing the EDR data helps in quickly conducting accident analysis and determining liability.

[0159] The above technical solution, through active interaction between the event data logger and the multimedia host, enables the transmission of EDR data to the multimedia host and prompts the user to read the EDR data. This avoids the user being unaware of a collision event, improves the user's understanding of the vehicle's status, and enhances the user's confidence in vehicle safety. Furthermore, when the user needs to view the EDR data, they only need to perform a viewing operation to do so, improving the convenience of viewing EDR data and thus enhancing the user experience.

[0160] It should be understood that the above examples are provided to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of this application to the specific values ​​or scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the above examples, and such modifications or changes also fall within the scope of the embodiments of this application.

[0161] The above text combined Figures 1 to 4 The vehicle control method provided in the embodiments of this application is described in detail below; the following will be combined with Figure 5 and Figure 7 The apparatus embodiments of this application are described in detail below. It should be understood that the apparatus in the embodiments of this application can perform the various methods described in the foregoing embodiments of this application, that is, the specific working processes of the various products described below can be referred to the corresponding processes in the foregoing method embodiments.

[0162] Figure 5 This is a schematic diagram of the structure of a vehicle control device provided in an embodiment of this application.

[0163] The vehicle's control unit 500 is located in the multimedia host, which is connected to the event data recorder.

[0164] For example, such as Figure 5 As shown, the vehicle control device 500 includes: a communication module 510, used to receive event information sent by an event data recorder, the event information indicating that there is EDR data to be transmitted in the event data recorder; in response to the event information, sending a data request to the event data recorder; in response to the data request, receiving EDR data sent by the event data recorder; and a processing module 520, used to display a first prompt message on the vehicle's display screen, the first prompt message indicating to the user that there is EDR data to be read.

[0165] In one possible implementation, the communication module 510 is further configured to send a download request to the event data logger; receive response information of the download request sent by the event data logger in response to the download request; and send a data request to the event data logger if the response information of the download request indicates that downloading is permitted.

[0166] In one possible implementation, the data request includes a first data identifier, and the communication module 510 is further configured to receive a second data identifier of the EDR data sent by the event data logger in response to the data request; the processing module 520 is further configured to verify whether the EDR data is complete based on the first data identifier and the second data identifier; and to display a second prompt message on the vehicle's display screen, the second prompt message being used to indicate whether the EDR data is complete.

[0167] In one possible implementation, the communication module 510 is used to obtain the current gear of the vehicle; when the current gear of the vehicle is the parking gear, a first prompt message is displayed on the vehicle's display screen.

[0168] In one possible implementation, the processing module 520 is further configured to obtain the user's identity information in response to the user's viewing operation of EDR data; and to display the EDR data on the display screen when the identity information indicates that the user is an authorized user.

[0169] It should be noted that the control device 500 of the aforementioned vehicle is embodied in the form of a functional unit. The term "module" here can be implemented in software and / or hardware, without specific limitations.

[0170] Figure 6 This is a schematic diagram of the structure of another vehicle control device provided in an embodiment of this application.

[0171] The vehicle control unit 600 is located in the event data recorder, which is connected to the multimedia host for communication.

[0172] For example, such as Figure 6 As shown, the vehicle control device 600 includes: a communication module 610, configured to send event information to a multimedia host when a collision event is detected, the event information indicating the existence of EDR data to be transmitted; in response to the event information, receive a data request sent by the multimedia host; and in response to the data request, send EDR data to the multimedia host, so that after receiving the EDR data, the multimedia host displays a first prompt message on the vehicle's display screen, the first prompt message indicating to the user that there is EDR data to be read.

[0173] In one possible implementation, the communication module 610 is further configured to receive a download request sent by the multimedia host; in response to the download request, send a response message for the download request to the multimedia host; and, if the response message for the download request indicates that downloading is permitted, receive a data request sent by the multimedia host.

[0174] In one possible implementation, the data request includes a first data identifier, and the communication module 610 is further configured to respond to the data request by sending a second data identifier of the EDR data to the multimedia host, so that the multimedia host can verify whether the EDR data is complete based on the first data identifier and the second data identifier; the multimedia host displays a second prompt message on the vehicle's display screen, the second prompt message being used to indicate whether the EDR data is complete.

[0175] It should be noted that the control device 600 of the aforementioned vehicle is embodied in the form of a functional unit. The term "module" here can be implemented in software and / or hardware, without specific limitations.

[0176] For example, a "module" can be a software program, a hardware circuit, or a combination of both that implements the above functions. The hardware circuit may include an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components that support the described functions.

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

[0178] Figure 7 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application.

[0179] For example, vehicle 700 and Figure 1 Vehicle 100 in the text refers to the same vehicle.

[0180] For example, such as Figure 7 As shown, the vehicle 700 includes a memory 710 and a processor 720, wherein the memory 710 stores executable program code 730, and the processor 720 is used to call and execute the executable program code 730 to perform a vehicle control method.

[0181] For example, the memory 710 can be used to store programs related to the vehicle control method provided in the embodiments of this application; the processor 720 can call the programs related to the vehicle control method stored in the memory 710 to execute the vehicle control method of the embodiments of this application; for example, receiving event information sent by an event data recorder, the event information being used to indicate that there is EDR data to be transmitted in the event data recorder; in response to the event information, sending a data request to the event data recorder; in response to the data request, receiving EDR data sent by the event data recorder; displaying a first prompt message on the vehicle's display screen, the first prompt message being used to prompt the user that there is EDR data to be read.

[0182] This embodiment can divide the device into functional modules based on the above method example. For example, each module can correspond to a separate function, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0183] When each functional module is divided according to its corresponding function, the device may also include a communication module and a processing module. It should be noted that all relevant content regarding the steps involved in the above method embodiments can be referenced from the functional descriptions of the corresponding functional modules, and will not be repeated here.

[0184] It should be understood that the device provided in this embodiment is used to execute the above-described vehicle control method, and therefore can achieve the same effect as the above-described implementation method.

[0185] When using an integrated unit, the device may include a processing module and a storage module. When the device is applied to a vehicle, the processing module can be used to control and manage the vehicle's movements. The storage module can be used to support the vehicle in executing relevant program code.

[0186] The processing module may be a processor or a controller, which can implement or execute various exemplary logic blocks, modules, and circuits shown in conjunction with the disclosure of this application. The processor may also be a combination of functions that implement computing capabilities, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, etc., and the storage module may be a memory.

[0187] In addition, the device provided in the embodiments of this application may specifically be a chip, component or module. The chip may include a connected processor and a memory. The memory is used to store instructions. When the processor calls and executes the instructions, the chip can execute a vehicle control method provided in the above embodiments.

[0188] This application also provides a computer-readable storage medium storing computer program code. When the computer program code is run on a computer, it causes the computer to execute the above-described related method steps to implement a vehicle control method provided in the above embodiments. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, Digital Video Discs (DVDs), Compact Disc Read-Only Memory (CD-ROMs), microdrives, and magneto-optical disks, read-only memory (ROMs), random access memory (RAMs), erasable programmable read-only memory (EPROMs), electrically erasable programmable read-only memory (EEPROMs), dynamic random access memory (DRAMs), video random access memory (VRAMs), flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and / or data.

[0189] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned related steps to implement a vehicle control method provided in the above embodiments.

[0190] The vehicle, computer-readable storage medium, computer program product or chip provided in this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0191] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

[0193] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for controlling a vehicle, characterized in that, The method is applied to a multimedia host, which is communicatively connected to an event data logger; the method includes: Receive event information sent by the event data logger, the event information being used to indicate that there is EDR data to be transmitted in the event data logger; In response to the event information, a data request is sent to the event data recorder; In response to the data request, receive EDR data sent by the event data logger; The vehicle's display screen shows a first prompt message, which is used to inform the user that there is EDR data to be read.

2. The method according to claim 1, characterized in that, The method further includes: Send a download request to the event data logger; In response to the download request, receive the response information for the download request sent by the event data logger; Sending a data request to the event data logger includes: If the response information to the download request indicates that the download is permitted, the data request is sent to the event data logger.

3. The method according to claim 1, characterized in that, The data request includes a first data identifier, and the method further includes: In response to the data request, receive the second data identifier of the EDR data sent by the event data logger; Based on the first data identifier and the second data identifier, verify whether the EDR data is complete data; A second prompt message is displayed on the vehicle's screen, indicating whether the EDR data is complete.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Obtain the current gear of the vehicle; The display of the first prompt information on the vehicle's display screen includes: When the vehicle is currently in park, the first prompt message is displayed on the vehicle's display screen.

5. The method according to any one of claims 1 to 3, characterized in that, The method further includes: In response to the user's viewing operation of the EDR data, the user's identity information is obtained; When the identity information indicates that the user is an authorized user, the EDR data is displayed on the screen.

6. A method for controlling a vehicle, characterized in that, The method is applied to an event data logger, which is communicatively connected to a multimedia host; the method includes: When a vehicle collision event is detected, an event information is sent to the multimedia host, the event information being used to indicate the existence of EDR data to be transmitted; In response to the event information, receive the data request sent by the multimedia host; In response to the data request, EDR data is sent to the multimedia host, so that after receiving the EDR data, the multimedia host displays a first prompt message on the vehicle's display screen. The first prompt message is used to inform the user that there is EDR data to be read.

7. The method according to claim 6, characterized in that, The method further includes: Receive the download request sent by the multimedia host; In response to the download request, a response message for the download request is sent to the multimedia host; The receiving of the data request sent by the multimedia host includes: If the response information of the download request indicates that the download is permitted, the data request sent by the multimedia host is received.

8. The method according to claim 6, characterized in that, The data request includes a first data identifier, and the method further includes: In response to the data request, a second data identifier of the EDR data is sent to the multimedia host, so that the multimedia host can verify whether the EDR data is complete based on the first data identifier and the second data identifier; The multimedia host displays a second prompt message on the vehicle's display screen, indicating whether the EDR data is complete.

9. A vehicle control system, characterized in that, Includes a multimedia host and an event data logger; The multimedia host is used to execute the vehicle control method as described in any one of claims 1 to 5; The event data logger is used to execute the vehicle control method as described in any one of claims 6 to 8.

10. A vehicle, characterized in that, The vehicles include: Memory, used to store executable program code; A processor is configured to call and run the executable program code from the memory, causing the vehicle to perform the vehicle control method as described in any one of claims 1 to 8.

Images