A vehicle bus data processing method, device, equipment and medium
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHONGQING SELIS PHOENIX INTELLIGENT INNOVATION TECH CO LTD
- Filing Date
- 2026-03-13
- Publication Date
- 2026-05-29
Smart Images
Figure CN122120364A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle networking technology, specifically to a vehicle bus data processing method, apparatus, device, and medium. Background Technology
[0002] In current vehicle testing technologies, message acquisition and playback rely on external hardware and software. However, tools from different manufacturers differ in interface protocols and data formats, leading to increased testing costs and reduced efficiency. Furthermore, the lack of a unified data processing mechanism necessitates adapting vehicle controller message parsing to various tool types, resulting in increased data conversion steps and more complex operational logic. Summary of the Invention
[0003] In view of the shortcomings of the prior art described above, this application provides a vehicle bus data processing method, apparatus, device and medium to solve the above technical problems.
[0004] This application provides a vehicle bus data processing method applied to a cloud server, comprising the following steps: Receive raw message data files with a predetermined format uploaded by the vehicle terminal, wherein the raw message data files contain raw message data of the vehicle controller; The original message data is parsed for the first time to obtain the first parsing result; The first parsing result is parsed a second time based on the pre-stored signal description file to obtain the second parsing result; The second parsing result is stored in the database for data consumers to access.
[0005] In one embodiment of this application, the first parsing of the original message data includes: The message type of the original message data is determined according to the predetermined identifier of the original message data; Call the parsing function corresponding to the message type according to the message type; The original message data is parsed using the parsing function to obtain the first parsing result.
[0006] In one embodiment of this application, the first parsing of the original message data further includes: The first parsing result is returned to the parsing function one by one through the generator mechanism, wherein the generator mechanism returns the first parsing result of the current single original message data in each iteration, so that the parsing function can perform subsequent processing.
[0007] In one embodiment of this application, the step of calling the parsing function corresponding to the message type according to the message type includes: If the message type is a first type of bus message, then the first parsing function is called; If the message type is a second type of bus message, then the second parsing function is called; wherein, the first type of bus message is a CAN message, and the second type of bus message is a CANFD message.
[0008] In one embodiment of this application, before performing a second analysis on the first analysis result, the method further includes: Detect the encoding of the signal description file; If the encoding belongs to an encoding type that is not the target character set, then an encoding conversion is performed to convert the signal description file into the target character set encoding.
[0009] In one embodiment of this application, if multiple original message data files are included, a multi-threaded or multi-process concurrent parsing mechanism is adopted to distribute the multiple original message data files to multiple parsing tasks for parallel processing.
[0010] In one embodiment of this application, the method further includes: The parsing results are extracted from the data platform, and the vehicle's operating status is dynamically presented through a front-end graphical component based on the signal names and corresponding signal values contained in the parsing results.
[0011] This application provides a vehicle bus data processing device, applied to a cloud server, comprising: The data receiving module is used to receive raw message data files with a predetermined format uploaded by the vehicle terminal, wherein the raw message data files contain raw message data of the vehicle controller. The first parsing module is used to perform a first parsing on the original message data to obtain a first parsing result; The second parsing module is used to perform a second parsing on the first parsing result based on a pre-stored signal description file to obtain a second parsing result. The data storage module is used to store the second parsing result in the database for data consumers to access.
[0012] This application provides a vehicle bus data processing device, comprising: One or more processors; A memory for storing one or more programs that, when executed by one or more processors, cause the vehicle bus data processing to implement the steps of the vehicle bus data processing method described above.
[0013] This application provides a computer-readable storage medium storing a computer program that, when executed by a computer's processor, causes the computer to perform the steps of the aforementioned vehicle bus data processing method.
[0014] The beneficial effects of this application are as follows: A vehicle bus data processing method of this application includes: receiving a raw message data file with a predetermined format uploaded by a vehicle, wherein the raw message data file contains raw message data from a vehicle controller; performing a first parsing on the raw message data to obtain a first parsing result; performing a second parsing on the first parsing result based on a pre-stored signal description file to obtain a second parsing result; and storing the second parsing result in a database for use by data consumers. This application, by automatically receiving, parsing twice, and storing vehicle bus data, transforms the complex raw message data from the vehicle end into directly usable structured information, greatly simplifying the vehicle data processing flow, reducing dependence on specific hardware and software, and improving the efficiency and accuracy of data analysis.
[0015] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description
[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings: Figure 1 A schematic diagram illustrating an exemplary vehicle bus data processing method implementation environment for this application. Figure 2 This is a schematic flowchart illustrating an exemplary vehicle bus data processing method of this application; Figure 3 This is an exemplary flowchart illustrating the initial parsing of raw message data according to this application. Figure 4 This is a block diagram of an exemplary vehicle bus data processing device according to this application; Figure 5 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation
[0017] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.
[0018] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the shape, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.
[0019] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the present application. However, it will be apparent to those skilled in the art that embodiments of the present application may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the present application.
[0020] Figure 1 This is a schematic diagram illustrating an exemplary vehicle bus data processing method implementation environment according to this application. Please refer to... Figure 1 The implementation environment includes terminal device 110 and server 120, which communicate with each other via a wireless network. The terminal device stores the CAN / CANFD messages of each vehicle controller in a predetermined file format, all of which are then uploaded to the vehicle infotainment system controller. The vehicle-side service periodically reports these messages to the server. The server receives the raw message data file with a predetermined format uploaded by the terminal device. This raw message data file contains the raw message data of the vehicle controller. The server performs a first parsing of the raw message data to obtain a first parsing result. Based on a pre-stored signal description file, it performs a second parsing of the first parsing result to obtain a second parsing result. The second parsing result is then stored in a database for data consumers to access.
[0021] It should be understood that Figure 1 The number of terminal devices and servers shown is merely illustrative. Any number of terminal devices and servers can be used depending on actual needs.
[0022] The terminal device corresponds to the client, which can be any electronic device with a user input interface, including but not limited to smartphones, tablets, laptops, computers, in-vehicle computers, etc. The user input interface includes but is not limited to touch screens, keyboards, physical buttons, audio pickup devices, etc.
[0023] Here, "server" corresponds to "service side," which can be a server that provides various services. It can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. This section does not impose any restrictions on this.
[0024] Terminal devices can communicate with the server via wireless networks such as 3G (third-generation mobile information technology), 4G (fourth-generation mobile information technology), and 5G (fifth-generation mobile information technology), and this document does not impose any restrictions on this.
[0025] The embodiments of this application respectively propose a vehicle bus data processing method, a vehicle bus data processing device, a vehicle bus data processing equipment, and a computer-readable storage medium, which will be described in detail below.
[0026] Please see Figure 2 , Figure 2 This is a flowchart illustrating a vehicle bus data processing method as shown in an exemplary embodiment of this application. This method can be applied to... Figure 1 The implementation environment shown is specifically executed by the server in that implementation environment. It should be understood that this method can also be applied to other exemplary implementation environments and specifically executed by devices in other implementation environments. This embodiment does not limit the implementation environment to which the method is applicable.
[0027] Please see Figure 2 , Figure 2 This is a schematic flowchart illustrating an exemplary vehicle bus data processing method according to this application. This vehicle bus data processing method is applied to a cloud server. Figure 2 As shown, the vehicle bus data processing method includes at least steps S210 to S240, which are described in detail below: Step S210: Receive the raw message data file with a predetermined format uploaded by the vehicle terminal, wherein the raw message data file contains the raw message data of the vehicle controller. The vehicle-side system stores the raw message data of each vehicle controller in a predetermined file format, all of which is then written to the vehicle infotainment system controller. The vehicle-side service periodically reports this data to the cloud server. The cloud server receives the raw message data files uploaded by the vehicle-side system and stores them using object storage.
[0028] In practice, vehicle-mounted devices can upload raw message data files to the cloud server in various ways. For example, the vehicle-mounted device can periodically upload the collected raw message data files to a designated directory on the cloud server via File Transfer Protocol (FTP).
[0029] Step S220: Perform the first parsing of the original message data to obtain the first parsing result; The purpose of the first parsing step is to extract basic message structure information from binary or hexadecimal formatted message data. Message structure information includes the attribute information of the original message data and the message data content. The attribute information may include timestamps, channel identifiers, message type identifiers, and data lengths. The data content refers to the raw binary or hexadecimal values carried in the message data fields; that is, the core payload that is actually transmitted after removing the CAN ID (Controller Area Network Identifier), control information, and other header data.
[0030] Step S230: Perform a second analysis on the first analysis result based on the pre-stored signal description file to obtain the second analysis result; A signal description file is a file pre-stored on a cloud server that describes the definitions of various signals in vehicle bus messages. A signal description file typically includes information such as the signal name, data type, start bit, length, offset, and unit.
[0031] The second parsing refers to converting the initial parsing result into a signal value with actual physical meaning—that is, the second parsing result—based on the definition in the signal description file after obtaining the preliminary message structure information from the first parsing. This could be such as the left front wheel speed or engine speed.
[0032] Step S240: Store the second parsing result in the database for data consumers to access.
[0033] After completing the second parsing and obtaining meaningful signal values, the results are persistently stored for subsequent querying, analysis, and application. For example, each signal and its corresponding value in the second parsing result, along with metadata such as the message timestamp, can be organized into a structured record and stored in a relational database. By centrally storing and managing the second parsing results, a unified data platform can be built, providing standardized data services to data consumers.
[0034] This application automates the reception, two-stage parsing, and storage of vehicle bus data, transforming complex raw message data from the vehicle end into directly usable structured information. This greatly simplifies the vehicle data processing flow, reduces dependence on specific hardware and software, and improves the efficiency and accuracy of data analysis.
[0035] The above technical solution is illustrated below with a more specific example: First, the terminal device on the vehicle side records the raw message data on the vehicle bus in real time and encapsulates it according to a predetermined file format (e.g., a log file containing multiple CAN (Controller Area Network) messages or CANFD (CAN with Flexible Data-Rate) messages), such as encapsulating it in ASCII (ASCII Logging File) file format. Then, the terminal device uploads the raw message data file to the cloud server via a wireless network.
[0036] Secondly, after receiving these raw message data files, the cloud server reads the uploaded raw message data files and performs preliminary parsing based on the message structure defined in the raw message data files (e.g., each message consists of a timestamp, channel identifier, message ID, data length, and data content). It identifies each raw message in the file and extracts its message ID, data length, and original hexadecimal data content to form the first parsing result. For example, "0x18F00400 01 02 03 04 05 06 07 08".
[0037] Then, the cloud server performs a second parsing of the first parsing result based on a pre-stored signal description file. This signal description file (e.g., a DBC (Database CAN) file) predefines the signal information corresponding to all message IDs on the vehicle bus, including the name of each signal (such as left front wheel speed, engine speed), its start bit, length, data type, and offset in the message data. The parsing service searches for the corresponding signal definition in the signal description file based on the message ID in the first parsing result. For example, for a message with message ID "0x18F00400", the signal description file may define a specific position in its data bytes representing the "vehicle speed" signal. Based on these definitions, the parsing service converts the original hexadecimal data "01 02 03 04 05 06 07 08" into specific physical values, such as converting a byte sequence into "vehicle speed: 60.5 km / h" or "engine speed: 2500 rpm", thus obtaining the second parsing result.
[0038] Finally, the cloud server stores these second-level parsing results, containing specific signal names and corresponding signal values, in a relational database (such as MySQL or Apache Doris). In this way, all parsed vehicle bus data is centrally and structurally stored, forming a data platform that can be shared across multiple business scenarios. This allows different users or application systems to retrieve parsing results and perform subsequent processing via data query commands. Other applications can directly obtain standardized and easily understood vehicle operation data from this data platform.
[0039] Please see Figure 3 , Figure 3 This is an exemplary flowchart illustrating the initial parsing of raw message data according to this application. Figure 3 The initial parsing of the original message data includes at least steps S310 to S330, which are detailed below: Step S310: Determine the message type of the original message data based on the predetermined identifier of the original message data; The predefined identifier is a specific marker in the original message data used to distinguish different message types. The predefined identifier can be a specific byte sequence in the message header, a frame ID, a protocol version number, or a specific field value in the data packet. The message type is a classification of the protocol to which the original message data belongs. For example, it could be a CAN message, a CANFD message, etc.
[0040] During the initial parsing of the original message data, the message type corresponding to the identifier is determined by matching the predetermined identifier contained in the original message data through a pre-defined lookup table (which defines the association between the predetermined identifier and the message type).
[0041] In one specific implementation, when the cloud server receives the raw message data file uploaded by the vehicle, it first reads the raw message data in the file and obtains a predetermined identifier. If the predetermined identifier of the message conforms to the frame format of the CAN protocol, it is determined to be a CAN message type; if it conforms to the frame format of the CANFD protocol, it is determined to be a CANFD message type.
[0042] Step S320: Call the parsing function corresponding to the message type according to the message type; After the message type is identified, the corresponding parsing function is selected and called from the preset function library. For example, for a CAN message, the CAN parsing function is called, which extracts the first parsing result from the raw message data according to the CAN protocol specification. Similarly, for a CANFD message, the CANFD parsing function is called to extract the corresponding parsing result. In this way, even if the raw message data file contains data from multiple bus protocols, it can be accurately classified and processed using the corresponding specialized parsing logic.
[0043] Step S330: The original message data is parsed using a parsing function to obtain the first parsing result.
[0044] After determining the parsing function, the original message data is converted into a structured first parsing result through the parsing rules and logic encapsulated in the parsing function, thereby realizing the conversion from raw data to understandable data fields.
[0045] This application determines the message type based on a predetermined identifier of the original message data before the first parsing and calls the corresponding parsing function accordingly, ensuring optimal parsing for each type of message data. This not only improves the accuracy and efficiency of data parsing but also allows the system to flexibly handle more types of bus protocols that may emerge in the future, enhancing the versatility and scalability of the data processing method.
[0046] In one embodiment, the first parsing result is returned to the parsing function one by one through a generator mechanism. The generator mechanism returns the parsing result of the current single original message data in each iteration for the parsing function to perform subsequent processing.
[0047] The generator mechanism returns the parsing result of a single message in each iteration, rather than loading all parsing results into memory at once. When the parsing function calls the generator, the generator function begins execution, parsing out the timestamp, channel identifier, message identifier, message length, and data content of a message. It then returns this data to the parsing function and pauses its own execution, preserving its current function state. Upon receiving this data, the parsing function immediately performs subsequent processing (e.g., a second parsing based on the signal description file). After processing, it requests the generator for the next message. The generator resumes from its pause, continues parsing the next message, and returns, repeating this process. This significantly reduces memory resource consumption and improves data processing response speed and overall throughput.
[0048] In one embodiment, calling a parsing function corresponding to the message type based on the message type includes: If the message type is a first-class bus message, then the first parsing function is called; If the message type is a second type of bus message, then the second parsing function is called; where the first type of bus message is a CAN message and the second type of bus message is a CANFD message.
[0049] As a specific implementation, when the cloud server receives the raw message data file uploaded by the vehicle, it first reads a predetermined identifier from a specific location in the raw message data file. Assuming this identifier indicates that the current data stream is a CAN message, a function named `parse_can_frame()` is called. If the identifier indicates that the current data stream is a CANFD message, another function named `parse_canfd_frame()` is called. In this way, each message type receives its own dedicated and refined parsing processing, thereby generating an accurate first parsing result.
[0050] In one embodiment, before performing a second parsing on the first parsing result, the method further includes: Encoding of the detection signal description file; If the encoding belongs to a type that is not the target character set, then an encoding conversion is performed to convert the signal description file to the target character set encoding.
[0051] Before the second parsing, the system identifies the character encoding format currently used in the signal description file. Then, it compares the detected encoding with the preset target character set encoding. If the detected encoding is inconsistent with the target character set encoding (i.e., it belongs to an encoding type not corresponding to the target character set), the system will automatically perform an encoding conversion operation, converting the content of the signal description file from its original encoding format to the target character set encoding. For example, if GBK encoding is detected, while the system's preset target character set encoding is UTF-8, the system will automatically convert the signal description file from GBK (Chinese Internal Code Specification) encoding to UTF-8 encoding. After the conversion, the UTF-8 (Unicode Transformation Format-8-bit) encoded signal description file is used for the second parsing. This ensures that the signal description file can be correctly read during the second parsing, avoiding parsing errors or data garbled problems caused by encoding mismatch.
[0052] In one embodiment, if multiple raw message data files are included, a multi-threaded or multi-process concurrent parsing mechanism is adopted to distribute the multiple raw message data files to multiple parsing tasks for parallel processing.
[0053] When the cloud server receives multiple raw message data files, the system no longer waits for one file to be completely processed before starting the next. Instead, it initiates a multi-threaded or multi-process concurrent parsing mechanism, assigning each raw message data file to a parsing task. Each parsing task then independently executes the steps in the vehicle bus data processing method described above. In this way, multiple raw message data files are parsed and stored simultaneously in different parsing tasks, greatly improving the parallelism of data processing and enabling the entire data processing flow to efficiently handle large-scale data input.
[0054] In one embodiment, the method further includes: extracting the parsing results from the data platform, and dynamically presenting the vehicle's operating status through a front-end graphical component based on the signal names and corresponding signal values contained in the parsing results.
[0055] After receiving and parsing the raw message data file uploaded by the vehicle, the cloud server stores the parsed signal names and their corresponding signal values in the database. To dynamically present the vehicle's operating status, the front-end application periodically sends data requests to the cloud server's API (Application Programming Interface). Upon receiving the request, the cloud server executes an SQL (Structured Query Language) query to retrieve the latest parsed results from the database. Subsequently, the server returns these signal names and values to the front-end application via the API. After receiving the data, the front-end application uses a graphical component to visualize the signal names and values. In this way, users can intuitively see the vehicle's operating status.
[0056] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0057] Figure 4 This is a schematic diagram of an exemplary vehicle bus data processing device according to this application. The device can be applied to... Figure 1 The implementation environment shown is specifically configured in the server. This device can also be applied to other exemplary implementation environments and specifically configured in other devices. This embodiment does not limit the implementation environment to which the device is applicable.
[0058] like Figure 4 As shown, this application provides a vehicle bus data processing device applied to a cloud server, the device comprising: The data receiving module 410 is used to receive a raw message data file with a predetermined format uploaded by the vehicle terminal, wherein the raw message data file contains the raw message data of the vehicle controller. The first parsing module 420 is used to perform the first parsing of the original message data to obtain the first parsing result; The second parsing module 430 is used to perform a second parsing on the first parsing result based on a pre-stored signal description file to obtain a second parsing result. The data storage module 440 is used to store the parsing results to the database for data consumers to access.
[0059] It should be noted that the vehicle bus data processing device and the vehicle bus data processing method provided in the above embodiments belong to the same concept. The specific ways in which each module and unit performs operations have been described in detail in the method embodiments, and will not be repeated here. In practical applications, the vehicle bus data processing device provided in the above embodiments 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, and this is not a limitation here.
[0060] Embodiments of this application also provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, cause the electronic device to implement the vehicle bus data processing method provided in the above embodiments.
[0061] Figure 5 A schematic diagram of a computer system suitable for implementing the memory of embodiments of this application is shown. It should be noted that... Figure 5 The computer system with the memory shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.
[0062] like Figure 5 As shown, the computer system 500 includes a Central Processing Unit (CPU) 501, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on programs stored in Read-Only Memory (ROM) 502 or programs loaded from storage into Random Access Memory (RAM) 503. The RAM also stores various programs and data required for system operation. The CPU 501, ROM 502, and RAM 503 are interconnected via a bus 504. An Input / Output (I / O) interface 505 is also connected to the bus 504.
[0063] The following components are connected to I / O interface 505: an input section 506 including a keyboard, mouse, etc.; an output section 507 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to I / O interface 505 as needed. Removable media 511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 510 as needed so that computer programs read from them can be installed into storage section 508 as needed.
[0064] Specifically, according to embodiments of this application, the processes described above with reference to the flowchart can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the vehicle bus data processing method of the aforementioned embodiments. In such embodiments, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium 511. When the computer program is executed by the central processing unit (CPU) 501, it performs various functions defined in the system of this application.
[0065] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM) 503, read-only memory (ROM) 502, erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.
[0066] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in the flowchart or block diagram may represent a module, program segment, or portion of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, or they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block or combination of blocks in the block diagram or flowchart may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0067] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.
[0068] Another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a computer's processor, causes the computer to perform the vehicle bus data processing method described above. This computer-readable storage medium may be included in the memory described in the above embodiments, or it may exist independently and not incorporated into that memory.
[0069] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the vehicle bus data processing method provided in the various embodiments described above.
[0070] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the claims of this application.
Claims
1. A vehicle bus data processing method, applied to a cloud server, characterized in that, include: Receive raw message data files with a predetermined format uploaded by the vehicle terminal, wherein the raw message data files contain raw message data of the vehicle controller; The original message data is parsed for the first time to obtain the first parsing result; The first parsing result is parsed a second time based on the pre-stored signal description file to obtain the second parsing result; The second parsing result is stored in the database for data consumers to access.
2. The vehicle bus data processing method according to claim 1, characterized in that, The first parsing of the original message data includes: The message type of the original message data is determined according to the predetermined identifier of the original message data; Call the parsing function corresponding to the message type according to the message type; The original message data is parsed using the parsing function to obtain the first parsing result.
3. The vehicle bus data processing method according to claim 2, characterized in that, After completing the first parsing of the original message data, the process also includes: The first parsing result is returned to the parsing function one by one through the generator mechanism, wherein the generator mechanism returns the first parsing result of the current single original message data in each iteration, so that the parsing function can perform subsequent processing.
4. The vehicle bus data processing method according to claim 2, characterized in that, The step of calling the parsing function corresponding to the message type according to the message type includes: If the message type is a first type of bus message, then the first parsing function is called; If the message type is a second type of bus message, then the second parsing function is called; wherein, the first type of bus message is a CAN message, and the second type of bus message is a CANFD message.
5. The vehicle bus data processing method according to claim 1, characterized in that, Before performing a second parsing on the first parsing result, the method further includes: Detect the encoding of the signal description file; If the encoding belongs to an encoding type that is not the target character set, then an encoding conversion is performed to convert the signal description file into the target character set encoding.
6. The vehicle bus data processing method according to claim 1, characterized in that, If multiple raw message data files are involved, a multi-threaded or multi-process concurrent parsing mechanism is used to distribute the multiple raw message data files to multiple parsing tasks for parallel processing.
7. The vehicle bus data processing method according to claim 1, characterized in that, The method further includes: The parsing results are extracted from the database, and the vehicle's operating status is dynamically presented through a front-end graphical component based on the signal names and corresponding signal values contained in the parsing results.
8. A vehicle bus data processing device, applied to a cloud server, characterized in that, include: The data receiving module is used to receive raw message data files with a predetermined format uploaded by the vehicle terminal, wherein the raw message data files contain raw message data of the vehicle controller. The first parsing module is used to perform a first parsing on the original message data to obtain a first parsing result; The second parsing module is used to perform a second parsing on the first parsing result based on a pre-stored signal description file to obtain a second parsing result. The data storage module is used to store the second parsing result in the database for data consumers to access.
9. A vehicle bus data processing device, characterized in that, include: One or more processors; A memory for storing one or more programs that, when executed by one or more processors, cause the vehicle bus data processing device to implement the steps of the vehicle bus data processing method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by the computer's processor, causes the computer to perform the steps of the vehicle bus data processing method according to any one of claims 1 to 7.