Data uploading method and device, vehicle and storage medium

Abstract

The embodiment of the invention discloses a data uploading method and device, a vehicle and a storage medium. The method comprises the steps that under the condition that a whole vehicle network is awakened, a target ECU receives a state frame sent by a T-BOX; when the target ECU detects that fault data needs to be uploaded and the state frame represents that the T-BOX allows the ECU to upload the fault data, a target floating frame is sent to the T-BOX, and the target floating frame is obtained after the fault data is inserted into the floating frame; and the T-BOX uploads the fault data to a cloud end according to the received target floating frame. By means of the method, when the vehicle network is awakened, the fault data can be uploaded in time, and the risk of communication congestion caused by additionally adding an uploading message is reduced.

Description

Technical Field

[0001] The present application belongs to the field of vehicle technology, and specifically relates to a data uploading method, device, vehicle and storage medium. Background Art

[0002] When a corresponding fault occurs in the current vehicle ECU, the fault data will be stored in the local log and the fault code will be recorded so that the fault information can be obtained through the diagnostic instrument at the 4S shop, but this method cannot obtain fault data in real time. Summary of the invention

[0003] In view of the above problems, the present application proposes a data uploading method, device, vehicle and storage medium to improve the above problems.

[0004] In a first aspect, an embodiment of the present application provides a data uploading method, the method comprising: when the vehicle network is awakened, the target ECU receives a status frame sent by the T-BOX; when the target ECU detects that fault data needs to be uploaded, and the status frame indicates that the T-BOX allows the ECU to upload the fault data, a target floating frame is sent to the T-BOX, wherein the target floating frame is obtained by inserting the fault data into a floating frame; the T-BOX uploads the fault data to the cloud according to the received target floating frame.

[0005] In a second aspect, an embodiment of the present application provides a data uploading device, the device comprising: a receiving unit, for the target ECU to receive a status frame sent by the T-BOX when the vehicle network is awakened; a sending unit, for sending a target floating frame to the T-BOX when the target ECU detects that there is fault data to be uploaded and the status frame indicates that the T-BOX allows the ECU to upload the fault data, wherein the target floating frame is obtained by inserting the fault data into a floating frame; an uploading unit, for the T-BOX to upload the fault data to the cloud according to the received target floating frame.

[0006] In a third aspect, an embodiment of the present application provides a vehicle, comprising at least one ECU, a T-BOX, one or more processors and a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the above-mentioned method.

[0007] In a fourth aspect, the present application provides a computer program product, comprising a computer program / instruction, which implements the steps of the above method when executed by a processor.

[0008] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a program code is stored, wherein the above method is executed when the program code is run.

[0009] The embodiments of the present application provide a data uploading method, device, vehicle and storage medium. When the vehicle network is awakened, the target ECU receives the status frame sent by the T-BOX. When the target ECU detects that there is fault data to be uploaded, and the status frame indicates that the T-BOX allows the ECU to upload the fault data, the target floating frame is sent to the T-BOX, wherein the target floating frame is obtained by inserting the fault data into the floating frame, and finally the T-BOX uploads the fault data to the cloud according to the received target floating frame. Through the above method, when the vehicle network is awakened, the fault data can be uploaded in time, reducing the risk of communication congestion caused by additional upload messages. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0011] Figure 1 A flow chart of a data uploading method proposed in an embodiment of the present application is shown;

[0012] Figure 2 A flow chart of a data uploading method proposed in another embodiment of the present application is shown;

[0013] Figure 3 A structural block diagram of a data uploading device proposed in an embodiment of the present application is shown;

[0014] Figure 4 A structural block diagram of a data uploading device proposed in an embodiment of the present application is shown;

[0015] Figure 5 A structural block diagram of a vehicle for executing a data uploading method according to an embodiment of the present application is shown;

[0016] Figure 6 A storage unit in an embodiment of the present application is shown for storing or carrying program code for implementing the data uploading method according to an embodiment of the present application. DETAILED DESCRIPTION

[0017] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0018] The embodiments of the present application propose a data uploading method, device, vehicle and storage medium. When the vehicle network is awakened, the target ECU receives the status frame sent by the T-BOX. When the target ECU detects that there is fault data that needs to be uploaded, and the status frame indicates that the T-BOX allows the ECU to upload the fault data, the target floating frame is sent to the T-BOX, wherein the target floating frame is obtained by inserting the fault data into the floating frame, and finally the T-BOX uploads the fault data to the cloud according to the received target floating frame. Through the above method, when the vehicle network is awakened, the fault data can be uploaded in time, reducing the risk of communication congestion caused by additional upload messages.

[0019] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0020] See also Figure 1 , a data uploading method provided in an embodiment of the present application comprises:

[0021] Step S110: When the vehicle network is awakened, the target ECU receives the status frame sent by the T-BOX.

[0022] In an embodiment of the present application, the whole vehicle network is awakened by a specific method to activate the vehicle network control system in a dormant state to restore it to a normal working state. The wake-up methods mainly include hard-line wake-up and network wake-up. Hard-line wake-up is achieved by monitoring the level changes of a specific line (such as the KL15 ignition signal line). When the level reaches the preset value, the controller is awakened. Network wake-up sends a wake-up message through a network such as the CAN bus, and the wake-up operation is performed after being parsed by the receiving node. In addition, remote wake-up technology, such as sending instructions through a specified application in an electronic device, can also realize remote wake-up of the whole vehicle network through network messages. These wake-up mechanisms jointly ensure that the vehicle network can be activated in time when needed to respond to the user's operational needs.

[0023] The target ECU is the ECU used to upload fault data in the embodiment of the present application. Optionally, the target ECU can be at least one ECU in the vehicle, which is not specifically limited here. The status frame is a message frame sent by the T-BOX to indicate the current data upload status of the T-BOX, and the status frame includes at least the upload flag and retransmission flag of different ECUs. Among them, the value of the upload flag of each ECU is used to indicate whether the T-BOX allows the ECU to upload fault data; the value of the retransmission flag of each ECU is used to indicate whether the T-BOX allows the ECU to retransmit fault data.

[0024] For example, taking a standard 64-bit CAN message as an example, the status frame may be as follows:

[0025]

[0026] In this data field, every 2 bits correspond to one ECU, the high-order bit corresponds to the upload flag, and the low-order bit corresponds to the retransmission flag.

[0027] When the high-order upload flag bit = 1, it means that T-BOX allows this ECU to upload fault data.

[0028] When the high-order upload flag bit = 0, it means that T-BOX prohibits this ECU from uploading fault data.

[0029] When the low-order retransmission flag bit = 1, it means that the T-BOX requires this ECU to retransmit the fault data.

[0030] When the low-order retransmission flag bit = 0, it means that T-BOX does not use this ECU to retransmit fault data.

[0031] When the vehicle network is awakened, the target ECU can receive the status frame sent by T-BOX, so that the target ECU can determine whether to upload the fault data or retransmit the fault data according to the values ​​of the upload flag and retransmission flag in the status frame.

[0032] Step S120: When the target ECU detects that fault data needs to be uploaded and the status frame indicates that the T-BOX allows the ECU to upload fault data, a target floating frame is sent to the T-BOX, wherein the target floating frame is obtained by inserting the fault data into a floating frame.

[0033] In the embodiment of the present application, the fault data in the ECU is mainly recorded and transmitted through diagnostic trouble codes (DTCs). Among them, DTC is a digital universal identifier of the fault condition identified by the vehicle's online diagnostic system, which is used to indicate the specific fault type; each DTC is usually composed of a series of letters and numbers, following the international standard protocol definition, such as ISO-14229-1 and SAEJ2012 OBD DTC, etc. These fault data are stored in the ECU's internal memory and can be read through special diagnostic tools to help maintenance personnel quickly locate and repair faults. Common fault data include sensor faults, actuator faults, communication faults, etc., and each fault type has a corresponding DTC code and description.

[0034] The floating frame occupies an unused position on the application frame transmitted by the ECU itself to send fault data, reducing the bus load, and can simultaneously transmit fault data when the vehicle is running in real time. The floating frame can at least include a fault data offset, a retransmission flag, and a floating frame flag. Among them, the floating frame flag is used to indicate whether the frame is a floating frame; the retransmission flag is used to indicate whether the frame is a retransmission frame; the fault data offset is used to indicate the space of unused bits in the current data field, pointing to the next bit of the last interactive signal.

[0035] For example, taking a standard 64-bit CAN message as an example, the format of a floating frame may be as follows:

[0036]

[0037] In this data field, the application interaction signals are arranged in sequence (such as interaction signals A / B / C / D). The last frame is the floating frame related flag bit, fault data offset (6 bits), retransmission flag (1 bit), floating frame flag (1 bit), and the rest are unused positions of the frame.

[0038] When the floating frame flag bit = 1, it means that the frame is a floating frame, and the unused bits will store fault data.

[0039] When the floating frame flag bit = 0, it means that the frame is not a floating frame. Except for this bit, the remaining area stores interactive signals. At this time, the fault data offset and retransmission flag are invalid, and interactive signals can be stored.

[0040] When the retransmission frame flag bit=1, it indicates that the frame is a retransmission frame, and the fault data stored in the unused bits are retransmitted.

[0041] When the retransmission frame flag bit=0, it indicates that the frame is not a retransmission frame, and the fault data stored in the unused bits are not retransmitted.

[0042] The fault data offset is 6 bits, which can indicate 64 states (0-64), corresponding to the 64 bits of the data field, and is used to indicate the unused bit space in the current data field, pointing to the next bit of the last interactive signal. In this example, it is 13, which points to the position of bit13, indicating that the space from bit48 to bit13 is unused and can be used to store fault data.

[0043] After the target ECU receives the status frame sent by T-BOX, it can start to detect whether the internally stored fault data needs to be uploaded; when the target ECU determines that the internally stored fault data needs to be uploaded, and the received status frame indicates that T-BOX allows the ECU to upload fault data, the target ECU can insert the fault data to be uploaded into the floating frame and send it to T-BOX. Inserting the fault data into the floating frame means inserting the fault data into the unused bit of the floating frame for storage. At this time, the floating frame flag of the floating frame = 1.

[0044] Step S130: the T-BOX uploads the fault data to the cloud according to the received target floating frame.

[0045] In an embodiment of the present application, after the T-BOX receives the target floating frame sent by the target ECU, the fault data in the target floating frame can be uploaded to the cloud in real time for storage.

[0046] The present application provides a data uploading method, in which when the vehicle network is awakened, the target ECU receives the status frame sent by the T-BOX. When the target ECU detects that there is fault data to be uploaded, and the status frame indicates that the T-BOX allows the ECU to upload the fault data, the target floating frame is sent to the T-BOX, wherein the target floating frame is obtained by inserting the fault data into the floating frame, and finally the T-BOX uploads the fault data to the cloud according to the received target floating frame. Through the above method, when the vehicle network is awakened, the fault data can be uploaded in time, reducing the risk of communication congestion caused by additional upload messages.

[0047] See also Figure 2 , a data uploading method provided in an embodiment of the present application comprises:

[0048] Step S210: When it is detected that the vehicle network is awakened, the T-BOX detects whether the target ECU is allowed to upload fault data.

[0049] In an embodiment of the present application, when it is detected that the vehicle network is awakened, T-BOX can start to detect whether the ECU is allowed to upload fault data.

[0050] As a method, when the vehicle network is detected to be awakened, the T-BOX obtains its own currently available internal cache space; based on its own currently available internal cache space, the T-BOX detects whether the target ECU is allowed to upload fault data.

[0051] When T-BOX detects whether to allow the target ECU to upload fault data based on its own currently available internal cache space, it can determine whether to allow the target ECU to upload fault data based on the size of its own currently available internal cache space and the data size of the fault data to be uploaded by the target ECU. Specifically, if the T-BOX's own currently available internal cache space is larger than the data size of the fault data to be uploaded by the target ECU, it can be determined that T-BOX allows the target ECU to upload fault data; otherwise, it can be determined that T-BOX does not allow the target ECU to upload fault data.

[0052] As another way, when it is detected that the vehicle network is awakened, the T-BOX obtains the current MCU processing performance; based on the current MCU processing performance, the T-BOX detects whether the target ECU is allowed to upload fault data.

[0053] Among them, the processing performance of MCU (microcontroller unit) is one of its core characteristics, which is mainly reflected in processing speed and task execution capability. Specifically:

[0054] High-performance processor: MCU usually has a built-in high-performance processor that can perform various complex calculations and logical operations, which provides it with a powerful processing capability foundation.

[0055] Processing speed: The processing speed of an MCU can be measured in MIPS (million instructions per second), which reflects the processing power of the system in the same second.

[0056] Task execution capability: In addition to processing speed, the MCU's task execution capability is also an important component of its processing performance, which includes the number of tasks it can handle simultaneously, the complexity of the tasks, and the efficiency of task execution.

[0057] In the embodiment of the present application, if the current MCU processing performance meets the preset condition, it can be determined that the T-BOX allows the target ECU to upload fault data; otherwise, it can be determined that the T-BOX does not allow the target ECU to upload fault data. The preset condition is a pre-set MCU processing performance that indicates when the T-BOX allows the target ECU to upload fault data.

[0058] Optionally, when it is detected that the vehicle network is awakened, the T-BOX obtains the current MCU processing performance and its own currently available internal cache space; based on the current MCU processing performance and its own currently available internal cache space, the T-BOX detects whether the target ECU is allowed to upload fault data.

[0059] Specifically, if the currently available internal cache space of the T-BOX itself is larger than the data size of the fault data to be uploaded by the target ECU, and the current MCU processing performance meets the preset conditions, it can be determined that the T-BOX allows the target ECU to upload the fault data; otherwise, it can be determined that the T-BOX does not allow the target ECU to upload the fault data.

[0060] Step S220: If the T-BOX detects that the target ECU is allowed to upload fault data, a status frame indicating that the T-BOX allows the ECU to upload fault data is sent to the target ECU.

[0061] In the embodiment of the present application, when the vehicle network is awakened, the T-BOX can continuously send status frames to the bus to indicate the current data upload status of the T-BOX according to the current MCU processing performance and its own currently available internal cache space and other conditions. When the T-BOX determines that the ECU is allowed to upload fault data, a status frame indicating that the T-BOX allows the ECU to upload fault data can be sent to the bus.

[0062] Step S230: When the target ECU detects that fault data needs to be uploaded and the status frame indicates that the T-BOX allows the ECU to upload fault data, a target floating frame is sent to the T-BOX, wherein the target floating frame is obtained by inserting the fault data into a floating frame.

[0063] In the embodiment of the present application, if the target ECU detects that there is no internal fault data to be uploaded, a floating frame is initiated, and the floating frame flag of the floating frame = 0.

[0064] If the target ECU detects that there is internal fault data that needs to be uploaded, a floating frame is initiated, the floating frame flag of the floating frame = 1, and the fault data is inserted into the floating frame.

[0065] Step S240: After receiving the target floating frame, the T-BOX reads the fault data offset from the target floating frame.

[0066] In the embodiment of the present application, the fault data offset can be understood as indicating the distance between the start of the fault data and the start of the message segment. The fault data offset can be used to determine the storage position of the fault data in the floating frame.

[0067] Step S250: Reading the fault data from the target floating frame based on the fault data offset.

[0068] In an embodiment of the present application, after the T-BOX receives the target floating frame sent by the target ECU, the fault data offset of the target floating frame can be read, so that the fault data uploaded by the target ECU can be obtained from a specified position in the target floating frame according to the read fault data offset.

[0069] Step S260: performing data verification on the fault data.

[0070] In the embodiment of the present application, after the T-BOX obtains the fault data uploaded by the target ECU from the target floating frame, it can perform data verification on the fault data to verify whether the fault data is complete.

[0071] When performing data verification on faulty data, the faulty data can be verified in a variety of ways, such as checksum: by summing the data bytes (or performing other operations), a check value is generated, and the receiver recalculates the check value using the same algorithm and compares it with the check value provided by the sender to verify data integrity.

[0072] XOR check: All data bits are XORed to obtain an XOR value as a check code. The receiver also performs an XOR operation and compares the results to verify the data.

[0073] CRC check: Cyclic redundancy check, which calculates the redundant check code of the data through polynomial division and appends it to the data for transmission. The receiver uses the same polynomial for check to detect data errors.

[0074] Format verification: Check whether the data meets the format requirements according to the predefined data format specifications.

[0075] Step S270: If the inspection passes, the fault data is uploaded to the cloud.

[0076] In the embodiment of the present application, if the data verification of the fault data passes, T-BOX can upload the fault data to the cloud.

[0077] Optionally, the method further includes: if the verification fails, adjusting the target retransmission flag of the status frame, so that the adjusted status frame indicates that the T-BOX requires the target ECU to retransmit the fault data.

[0078] The target retransmission flag refers to the retransmission flag corresponding to the target ECU.

[0079] Specifically, if the data verification of the fault data fails, the T-BOX can set the target retransmission flag of the status frame, so that the adjusted status frame indicates that the T-BOX requires the target ECU to retransmit the fault data. That is, the value of the target retransmission flag of the status frame is set to 1.

[0080] Optionally, the method further includes: obtaining a current upload load; if the upload load is greater than a preset load or the T-BOX itself is about to go into sleep, adjusting at least part of the upload flag bits of the status frame, so that the adjusted status frame indicates that the T-BOX stops uploading fault data of at least part of the ECUs.

[0081] The preset load is a preset load value that indicates the current load of the T-BOX. After the T-BOX obtains the fault data uploaded by the target ECU, the current upload load can be obtained. If the current upload load is greater than the preset load, or the T-BOX itself is about to go to sleep, at least part of the upload flag bits of the status frame can be set, so that the adjusted status frame indicates that the T-BOX stops uploading fault data to at least some ECUs. Setting at least part of the upload flag bits means setting the upload flag bits corresponding to at least some ECUs to 0.

[0082] Specifically, when T-BOX determines that the current upload load is greater than the preset load, it can stop one or some ECUs from uploading fault data by setting the status frame; when T-BOX itself is about to sleep, it can shut down the upload behavior of all ECUs 2s in advance by setting the status frame.

[0083] Optionally, the method also includes: the target ECU receives an adjusted status frame sent by the T-BOX; if the adjusted status frame indicates that the T-BOX requires the target ECU to retransmit the fault data, and the target ECU has not finished uploading the fault data, recording the fault data that is not currently sent, and retransmitting the fault data sent in the previous frame message, until the adjusted status frame indicates that no retransmission is required, the recorded fault data that is not sent is sent; if the adjusted status frame indicates that the T-BOX stops at least some ECUs from uploading fault data, and the target ECU has not finished uploading the fault data, recording the fault data that is not currently sent, and sending the recorded fault data that is not sent until the adjusted status frame indicates that upload is allowed.

[0084] Specifically, after the T-BOX sets the status frame, it will send the set status frame to the bus in real time, so that each ECU can obtain the latest status frame in real time.

[0085] When the target ECU has not finished uploading the fault data, and the received status frame after the setting indicates that T-BOX requires the target ECU to retransmit the fault data, the target ECU records the fault data that is not currently sent, and retransmits the fault data sent in the previous frame message, until the adjusted status frame indicates that retransmission is no longer required, and then the recorded fault data that is not sent is sent.

[0086] When the target ECU has not finished uploading fault data, and the received set status frame indicates that T-BOX stops at least some ECUs from uploading fault data, the target ECU records the currently unsent fault data until the adjusted status frame indicates that uploading is allowed, and then sends the recorded unsent fault data.

[0087] When the target ECU finishes uploading the fault data, it stops sending floating frames.

[0088] A data uploading method provided by the present application can upload fault data in a timely manner when the vehicle network is awakened, thereby reducing the risk of communication congestion caused by additional uploaded messages.

[0089] See also Figure 3 , an embodiment of the present application provides a data uploading device 300, the device 300 comprising:

[0090] The receiving unit 310 is used for the target ECU to receive the status frame sent by the T-BOX when the vehicle network is awakened.

[0091] The sending unit 320 is used to send a target floating frame to the T-BOX when the target ECU detects that fault data needs to be uploaded and the status frame indicates that the T-BOX allows the ECU to upload the fault data, wherein the target floating frame is obtained by inserting the fault data into the floating frame.

[0092] The uploading unit 330 is used for the T-BOX to upload the fault data to the cloud according to the received target floating frame.

[0093] As a method, the upload unit 330 is specifically used to read the fault data offset from the target floating frame after the T-BOX receives the target floating frame; read the fault data from the target floating frame based on the fault data offset; perform data verification on the fault data; if the verification passes, upload the fault data to the cloud.

[0094] As another way, the upload unit 330 is further configured to adjust the target retransmission flag of the status frame if the verification fails, so that the adjusted status frame indicates that the T-BOX requires the target ECU to retransmit the fault data.

[0095] Optionally, the uploading unit 330 is further used to obtain the current upload load; if the upload load is greater than a preset load or the T-BOX itself is about to sleep, at least part of the upload flag bits of the status frame are adjusted so that the adjusted status frame indicates that the T-BOX stops uploading fault data to at least part of the ECUs.

[0096] Optionally, the upload unit 330 is also used for the target ECU to receive the adjusted status frame sent by the T-BOX; if the adjusted status frame indicates that the T-BOX requires the target ECU to retransmit the fault data, and the target ECU has not finished uploading the fault data, record the fault data that is not currently sent, and retransmit the fault data sent in the previous frame message, until the adjusted status frame indicates that no retransmission is required, and then send the recorded fault data that is not sent; if the adjusted status frame indicates that the T-BOX stops at least some ECUs from uploading fault data, and the target ECU has not finished uploading the fault data, record the fault data that is not currently sent, and send the recorded fault data that is not sent until the adjusted status frame indicates that upload is allowed.

[0097] See also Figure 4 , the device 300 further includes:

[0098] The detection unit 340 is used for, when detecting that the vehicle network is awakened, the T-BOX detects whether the target ECU is allowed to upload fault data; if the T-BOX detects that the target ECU is allowed to upload fault data, sending a status frame to the target ECU indicating that the T-BOX allows the ECU to upload fault data.

[0099] As a method, the detection unit 340 is also used for the T-BOX to obtain its own currently available internal cache space when it detects that the vehicle network is awakened; the T-BOX detects whether the target ECU is allowed to upload fault data based on its own currently available internal cache space.

[0100] It should be noted that the device embodiment in the present application corresponds to the aforementioned method embodiment. The specific principles in the device embodiment can be found in the contents of the aforementioned method embodiment and will not be repeated here.

[0101] The following will be combined Figure 5 A vehicle provided in the present application is described.

[0102] See also Figure 5Based on the above data uploading method and device, the embodiment of the present application also provides another vehicle 800 that can execute the above data uploading method. The vehicle 800 includes one or more (only one is shown in the figure) processors 802, a memory 804, a network module 806, a T-BOX 808 and at least one ECU 809 that are coupled to each other. Among them, the memory 804 stores a program that can execute the content of the above embodiment, and the processor 802 can execute the program stored in the memory 804.

[0103] Among them, the processor 802 may include one or more processing cores. The processor 802 uses various interfaces and lines to connect various parts of the entire vehicle 800, and executes various functions and processes data of the vehicle 800 by running or executing instructions, programs, code sets or instruction sets stored in the memory 804, and calling data stored in the memory 804. Optionally, the processor 802 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 802 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing display content; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 802, but may be implemented separately through a communication chip.

[0104] The memory 804 may include a random access memory (RAM) or a read-only memory (ROM). The memory 804 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 804 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc. The data storage area may also store data created by the vehicle 800 during use (such as a phone book, audio and video data, chat record data), etc.

[0105] The network module 806 is used to receive and send electromagnetic waves, realize the mutual conversion between electromagnetic waves and electrical signals, and thus communicate with a communication network or other devices, such as communicating with a vehicle. The network module 806 may include various existing circuit elements for performing these functions, such as antennas, radio frequency transceivers, digital signal processors, encryption / decryption chips, user identity modules (SIM) cards, memories, etc. The network module 806 may communicate with various networks such as the Internet, corporate intranets, wireless networks, or communicate with other devices via wireless networks. The above-mentioned wireless networks may include cellular telephone networks, wireless local area networks, or metropolitan area networks. For example, the network module 806 may exchange information with a base station.

[0106] The T-BOX808, which stands for Telematics BOX, is an intelligent vehicle-mounted terminal in the Internet of Vehicles system, and is mainly used to communicate with the background system / mobile phone APP to realize the vehicle information display and control of the mobile phone APP. In the embodiment of the present application, the T-BOX is mainly used to obtain the fault data uploaded by each ECU, and upload the fault data uploaded by each ECU to the cloud or background.

[0107] At least one ECU809 (Electronic Control Unit) is an electronic control unit, also known as a "driving computer" or "on-board computer", which is a microcomputer controller dedicated to the car, equivalent to the "brain" of the engine and the vehicle. In the embodiment of the present application, at least one ECU is mainly used to insert the respective fault data into the floating frame and send it to the T-BOX.

[0108] Please refer to Figure 6 , which shows a structural block diagram of a computer-readable storage medium provided in an embodiment of the present application. The computer-readable storage medium 900 stores program codes, which can be called by a processor to execute the method described in the above method embodiment.

[0109] The computer-readable storage medium 900 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer-readable storage medium 900 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 900 has storage space for program code 910 that performs any method step in the above method. These program codes can be read from or written to one or more computer program products. The program code 910 can be compressed, for example, in an appropriate form.

[0110] The present application provides a data uploading method, device, vehicle and storage medium. When the vehicle network is awakened, the target ECU receives the status frame sent by T-BOX. When the target ECU detects that there is fault data to be uploaded, and the status frame indicates that T-BOX allows ECU to upload fault data, the target floating frame is sent to T-BOX, wherein the target floating frame is obtained by inserting the fault data into the floating frame, and finally T-BOX uploads the fault data to the cloud according to the received target floating frame. Through the above method, when the vehicle network is awakened, the fault data can be uploaded in time, reducing the risk of communication congestion caused by additional upload messages.

[0111] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.

Claims

1. A data uploading method, characterized in that: The method comprises: When the vehicle network is awakened, the target ECU receives the status frame sent by T-BOX; When the target ECU detects that fault data needs to be uploaded, and the status frame indicates that the T-BOX allows the ECU to upload the fault data, a target floating frame is sent to the T-BOX, wherein the target floating frame is obtained by inserting the fault data into a floating frame; The T-BOX uploads the fault data to the cloud according to the received target floating frame.

2. The method according to claim 1, characterized in that In the case where the vehicle network is awakened, before the target ECU receives the status frame sent by T-BOX, the following steps are also included: When it is detected that the vehicle network is awakened, the T-BOX detects whether the target ECU is allowed to upload fault data; If the T-BOX detects that the target ECU is allowed to upload fault data, a status frame indicating that the T-BOX allows the ECU to upload fault data is sent to the target ECU.

3. The method according to claim 2, characterized in that When the vehicle network is detected to be awakened, the T-BOX detects whether the target ECU is allowed to upload fault data, including: When the vehicle network is detected to be awakened, the T-BOX obtains its own currently available internal cache space; The T-BOX detects whether to allow the target ECU to upload fault data based on its own currently available internal cache space.

4. The method according to claim 1, characterized in that The T-BOX uploads the fault data to the cloud according to the received target floating frame, including: After receiving the target floating frame, the T-BOX reads the fault data offset from the target floating frame; reading the fault data from the target floating frame based on the fault data offset; Performing data verification on the fault data; If the inspection passes, the fault data is uploaded to the cloud.

5. The method according to claim 4, characterized in that The method further comprises: If the check fails, the target retransmission flag of the status frame is adjusted so that the adjusted status frame indicates that the T-BOX requires the target ECU to retransmit the fault data.

6. The method according to claim 4, characterized in that The method further comprises: Get the current upload load; If the upload load is greater than a preset load or the T-BOX itself is about to sleep, at least part of the upload flag bits of the status frame are adjusted so that the adjusted status frame indicates that the T-BOX stops at least part of the ECUs from uploading fault data.

7. The method according to claim 5 or 6, characterized in that: The method further comprises: The target ECU receives the adjusted status frame sent by the T-BOX; If the adjusted status frame indicates that T-BOX requires the target ECU to retransmit the fault data, and the target ECU has not finished uploading the fault data, the fault data that is not currently sent is recorded, and the fault data sent in the previous frame message is retransmitted, until the adjusted status frame indicates that retransmission is no longer required, the recorded fault data that is not sent is sent; If the adjusted status frame indicates that T-BOX stops at least some ECUs from uploading fault data, and the target ECU has not finished uploading fault data, the currently unsent fault data is recorded, and the recorded unsent fault data is sent until the adjusted status frame indicates that uploading is allowed.

8. A data uploading device, characterized in that: The device comprises: The receiving unit is used for the target ECU to receive the status frame sent by T-BOX when the vehicle network is awakened; a sending unit, configured to send a target floating frame to the T-BOX when the target ECU detects that fault data needs to be uploaded and the status frame indicates that the T-BOX allows the ECU to upload the fault data, wherein the target floating frame is obtained by inserting the fault data into a floating frame; The uploading unit is used for the T-BOX to upload the fault data to the cloud according to the received target floating frame.

9. A vehicle, characterized in that: The method comprises at least one ECU, a T-BOX, and one or more processors; one or more programs are stored in the memory and configured so that the one or more processors execute the method according to any one of claims 1 to 7.

10. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program code, wherein when the program code is executed by a processor, the method according to any one of claims 1 to 7 is executed.

Images