Vehicle data processing system and method, electronic device, and readable storage medium

Abstract

The application discloses a vehicle data processing system and method, an electronic device and a readable storage medium. The system comprises a foreground display module and a background data processing module installed on a vehicle, wherein the background data processing module is connected with a vehicle bus, used for receiving bus data from the vehicle bus and performing data processing on the bus data to generate first processing data; the foreground display module is connected with the background data processing module through Ethernet, used for generating display data according to the first processing data sent by the background data processing module and displaying the display data. The embodiment of the application replaces the existing CANOE to acquire and process bus data, thereby reducing the use of wiring harness, improving the development efficiency and greatly reducing the development cost.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a vehicle data processing system and method, electronic device and readable storage medium. Background Technology

[0002] Controller Area Network (CAN) is one of the most widely used fieldbuses internationally. In the development of automotive bus systems, existing technologies typically employ a CAN Open Environment (CANOE) to capture, analyze, and monitor data on the CAN bus.

[0003] However, CANOE requires multiple wiring harnesses to connect to various CAN channels of the vehicle (e.g., chassis CAN, powertrain CAN, etc.) and the computer, making it inconvenient for debugging; in addition, CANOE is expensive, which greatly increases development costs. Summary of the Invention

[0004] This application provides a vehicle data processing system and method, electronic device and readable storage medium to solve the shortcomings of the prior art when using CANOE for automotive bus development, which is inconvenient to debug and has high development costs.

[0005] To achieve the above objectives, this application provides a vehicle data processing system, including: a front-end display module and a back-end data processing module installed on the vehicle, wherein...

[0006] The background data processing module is connected to the vehicle bus and is used to receive bus data from the vehicle bus and process the bus data to generate first processed data.

[0007] The front-end display module is connected to the back-end data processing module via Ethernet. It is used to generate display data based on the first processed data sent by the back-end data processing module and to display the display data.

[0008] This application also provides a vehicle data processing method, applicable to a vehicle data processing system installed in a vehicle. The vehicle data processing system includes a back-end data processing module connected to the vehicle bus and a front-end display module connected to the back-end data processing module via Ethernet. The method includes:

[0009] The background data processing module receives bus data from the vehicle bus and processes the bus data to generate first processed data.

[0010] Based on the first processed data, display data is generated using the front-end display module, and the display data is then displayed.

[0011] This application also provides an electronic device, including:

[0012] Memory, used to store programs;

[0013] A processor is configured to run the program stored in the memory, wherein the program executes the vehicle data processing method provided in the embodiments of this application.

[0014] This application also provides a computer-readable storage medium storing a computer program executable by a processor, wherein the program, when executed by the processor, implements the vehicle data processing method provided in this application.

[0015] The vehicle data processing system and method, electronic device and computer-readable storage medium provided in this application replace the existing CANOE for acquiring and processing bus data by installing a back-end data processing module connected to the vehicle bus and a front-end display module connected to the back-end data processing module via Ethernet on the vehicle. This reduces the use of wiring harnesses, improves development efficiency and greatly reduces development costs.

[0016] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0017] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0018] Figure 1 This is a schematic diagram of the working wiring of CANOE in the prior art;

[0019] Figure 2 A schematic diagram of the structure of an embodiment of a vehicle data processing system provided in this application;

[0020] Figure 3 This is a schematic diagram of one embodiment of a vehicle-customized signal display panel provided in this application;

[0021] Figure 4 A flowchart of an embodiment of a vehicle data processing method provided in this application;

[0022] Figure 5 This is a schematic diagram of the structure of an embodiment of an electronic device provided in this application. Detailed Implementation

[0023] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0024] In some processes described in the specification, claims, and drawings of this application, multiple operations appearing in a specific order are included. However, it should be clearly understood that these operations may not be executed in the order they appear herein, or may be executed in parallel. The sequence numbers of the operations, such as 101, 102, etc., are merely used to distinguish different operations and do not themselves represent any execution order. Furthermore, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel. It should be noted that the descriptions such as "first," "second," etc., in this document are used to distinguish different messages, devices, modules, etc., and do not represent a sequential order, nor do they limit "first" and "second" to different types.

[0025] When developing automotive bus systems, existing technologies typically use data from the CANOE vehicle bus for capture, analysis, monitoring, and other processing. Figure 1 This is a schematic diagram of the wiring for CANOE operation in existing technology. Figure 1 As shown, developers need to connect the CANOE to the vehicle's bus and computer. Since there are many CAN channels on the vehicle, the CANOE needs to be connected to each CAN channel and the computer via multiple wiring harnesses, which is inconvenient for debugging. Furthermore, the high price of the CANOE significantly increases development costs.

[0026] To address the aforementioned technical problems, after a series of considerations and experiments, the inventors proposed the technical solution of this application, providing a vehicle data processing system, including a front-end display module and a back-end data processing module installed on the vehicle. The back-end data processing module is connected to the vehicle bus and is used to receive bus data from the vehicle bus and process the bus data to generate first processed data. The front-end display module is connected to the back-end data processing module via Ethernet and is used to generate display data based on the first processed data sent by the back-end data processing module, and to display the display data.

[0027] By installing a back-end data processing module connected to the vehicle bus and a front-end display module connected to the back-end data processing module via Ethernet on the vehicle, the existing CANOE is replaced for bus data acquisition and processing, thereby reducing the use of wiring harnesses, improving development efficiency, and greatly reducing development costs.

[0028] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0029] like Figure 2 The diagram shown is a structural schematic of one embodiment of a vehicle data processing system provided in this application. The vehicle data processing system includes a front-end display module and a back-end data processing module installed on the vehicle.

[0030] The background data processing module is connected to the vehicle bus and is used to receive bus data from the vehicle bus and process the bus data to generate the first processed data.

[0031] The front-end display module and the back-end data processing module are connected via Ethernet. The front-end display module generates display data based on the first processed data sent by the back-end data processing module and then displays the display data.

[0032] In this embodiment, the vehicle is equipped with a front-end display module and a back-end data processing module, which are connected and used in conjunction. The back-end data processing module is connected to the vehicle bus (also known as the Controller Area Network, or CAN), directly receiving bus data from the vehicle bus, avoiding the use of wiring harnesses to connect to the vehicle bus interface, thus reducing the use of wiring harnesses. Then, the back-end data processing module processes the acquired bus data, performing operations such as analysis and monitoring, to generate the first processed data.

[0033] The front-end display module and the back-end data processing module communicate via Ethernet. For example, the back-end data processing module can send the first processed data to the front-end display module via Hypertext Transfer Protocol (HTTP). After receiving the first processed data, the front-end display module generates display data for the user. For example, if the first processed data is vehicle speed data, the front-end display module can determine whether the vehicle is speeding. If it is, it generates display data to warn the user, such as a flashing red light. If the front-end module determines that the current vehicle speed is normal, it can directly display the speed value for the user's reference. Alternatively, it can display the change in the speed value in a more intuitive form, such as a waveform graph or bar chart, thereby improving the user experience.

[0034] The implementation of the background data processing module is described below. In practical applications, the background data processing module may include multiple processing cores, each capable of performing different data processing operations. Specifically, in the vehicle data processing system provided in this application embodiment, the background data processing module can be located on the XCU controller. This controller can be configured with multiple central processing unit (CPU) cores, such as a communication processing core for communicating with the vehicle bus, a receiving processing core for receiving bus data, and a data processing core for processing the bus data. These cores can be configured according to the actual application scenario. Inter-core communication is possible between the processing cores to achieve data processing. For example, communication can be achieved using the inter-core communication tool IPCF (a communication method developed by NXP that uses a shared memory zero-copy approach at the underlying level), but this is a limitation here.

[0035] Furthermore, in this embodiment, the background data processing module may include: a first processing core and a second processing core.

[0036] The first processing core can be used to communicate with the vehicle bus and perform bus data reception and forwarding operations;

[0037] The second processing core communicates with the first processing core and can be used to process bus data forwarded by the first processing core. The second processing core can also act as a server to provide data support for the front-end display module.

[0038] The XCU controller can be configured with two CPU cores: an M-core for the first processing and an A-core for the second. The M-core employs the ClassicAutoSAR architecture, offering strong real-time performance. Its primary function is to connect to the vehicle's CAN bus, communicating with it to collect and transmit data. The A-core boasts powerful computing capabilities, interacting with the M-core, receiving bus data, processing it, and acting as a server to support the front-end data processing.

[0039] Specifically, the second processing core can process the received bus data according to preset processing operations to generate the first processed data. These preset processing operations may include data calculation and analysis, data format conversion, and data value monitoring, and can be set according to the actual application scenario; no limitation is made here. After receiving bus data from the vehicle bus, the first processing core can directly send the bus data to the second processing core. The second processing core processes the bus data according to the preset processing operations, generates the first processed data, and sends it to the front-end display module.

[0040] To improve data processing efficiency, optionally, after receiving bus data from the vehicle bus, the first processing core can assemble the bus data into a data packet based on preset byte data and then send the data packet to the second processing core. Specifically, when the bus data sent by the vehicle bus is received by the first processing core, a hardware interrupt can be generated, calling the interrupt handler function to assemble the bus data according to the preset byte data. For example, a 4-byte header can be added to the beginning of the bus data to assemble the packet and obtain the data packet. Afterwards, the data packet can be sent to the second processing core via the inter-core communication tool IPCF.

[0041] At this point, the second processing core can receive the data packets sent by the first processing core. By parsing the data packets and identifying the header, preset byte data and bus data can be obtained. Then, the bus data can be processed according to preset processing operations to generate the first processed data.

[0042] To further improve data processing efficiency, after obtaining the aforementioned bus data, the second processing core can also send the bus data to a shared queue and send a prompt signal to its data processing service, such as a background server running on the second processing core. This prompt signal can instruct the data processing service to retrieve the bus data from the shared queue. Specifically, the second processing core can use this data processing service to process the bus data according to preset processing operations to generate the first processed data. The implementation of the shared queue can be configured according to the actual application scenario and is not limited.

[0043] The implementation of the front-end display module is described below. In this embodiment, the front-end display module may include a generation submodule and a display submodule.

[0044] The generation submodule can be used to generate display data that can be shown to the user based on the first processed data sent by the background data processing module.

[0045] The display submodule is used to present the display data to the user.

[0046] Specifically, the correspondence between the first processed data and the displayed data can be preset. For example, when the first processed data is vehicle speed data, the corresponding displayed data could be light color. Specifically, when the vehicle speed exceeds a certain preset value, the corresponding light color is red; when the vehicle speed does not exceed a certain preset value, the corresponding light color is green, etc., which can be set according to the actual application scenario. Then, the correspondence can be stored, so that when the first processed data is received, the corresponding displayed data can be generated based on the above correspondence.

[0047] Specifically, such as Figure 2 As shown, the display submodule may include one or more of the following: a vehicle basic information display section, a vehicle custom signal display section, and a user-defined display section.

[0048] The vehicle basic information display section displays basic vehicle information, such as battery level information.

[0049] The data displayed in the vehicle's custom signal display section may include one or more of the following: vehicle speed information, motor power information, and high beam status information;

[0050] The data displayed in user-defined display panels can include bus data from user-specified bus channels.

[0051] Furthermore, the data displayed in the front-end display module can be presented in the form of waveform graphs, bar charts, or other display formats. Figure 3 This is a schematic diagram illustrating the vehicle-customized signal display panel provided in this embodiment of the application. The diagram displays information such as vehicle speed, motor power meter, and high beam status in the form of waveform graphs.

[0052] For example, the front end will turn red when the vehicle speed exceeds a preset value (e.g., 100 km / h).

[0053] When the vehicle is running, the speed sensor continuously monitors the vehicle speed. When the speed exceeds 100 km / h, a warning signal is sent. The speed sensor sends a CAN frame to the target address, i.e., the instrument panel, via the CAN bus. Simultaneously, this CAN frame is received by the M-core hardware, generating a hardware interrupt. The M-core then calls the interrupt handler function. The interrupt handler function uses its own protocol to assemble the packet, adding a 4-byte header to the beginning of the CAN frame, and then sends it to the A-core via inter-core communication tools.

[0054] Core A parses the received data. Once the specified header is identified, the data following the header constitutes the CAN frame. After parsing, this CAN frame is sent to a shared queue, and a signal is sent to the background server program. Upon receiving the signal, the background server program running on Core A retrieves a CAN frame from the shared queue and then sends it to the foreground program via HTTP.

[0055] The front-end display module determines whether the vehicle speed signal carried in this CAN frame exceeds a specified value. If it does, the data is displayed in the corresponding section, for example, by flashing red. When the vehicle speed falls below the specified value, it turns back to normal green.

[0056] At this point, a complete frame of CAN data has been sent from the CAN bus, which is invisible to the user, to the front-end display module. The user can intuitively perceive the magnitude of the changes in its value and its trajectory.

[0057] The vehicle data processing system provided in this application replaces the existing CANOE for acquiring and processing bus data by installing a back-end data processing module connected to the vehicle bus and a front-end display module connected to the back-end data processing module via Ethernet on the vehicle. This reduces the use of wiring harnesses, improves development efficiency, and greatly reduces development costs.

[0058] Figure 4 A flowchart illustrating an embodiment of the vehicle data processing method provided in this application. Figure 4 As shown, the executing entity of this method can be various terminal or server devices with data processing capabilities, or it can be a device or chip integrated on these devices. This vehicle data processing method is applicable to a vehicle data processing system installed in a vehicle, which includes a back-end data processing module connected to the vehicle bus and a front-end display module connected to the back-end data processing module via Ethernet. Specifically, the method includes the following steps:

[0059] S401 receives bus data from the vehicle bus.

[0060] S402 processes the bus data to generate the first processed data.

[0061] S403, Generate display data based on the first processed data.

[0062] S404 displays the data.

[0063] Among them, the above steps S401 and S402 can be implemented using the background data processing module in the vehicle data processing system, and steps S403 and S404 can be implemented using the front-end display module in the vehicle data processing system. The specific implementation process has been described in detail in the foregoing embodiments and will not be repeated here.

[0064] Furthermore, when the background data processing module includes a first processing core that communicates with the vehicle bus and a second processing core that communicates with the first processing core, the method described above for receiving bus data from the vehicle bus using the background data processing module and processing the bus data to generate the first processed data may specifically include: receiving bus data from the vehicle bus using the first processing core and sending the bus data to the second processing core; receiving the bus data using the second processing core and processing the bus data according to a preset processing operation to generate the first processed data. The specific implementation process will not be elaborated further.

[0065] Furthermore, the data displayed may include one or more of the following: basic vehicle information, vehicle speed information, motor power information, high beam status information, and bus data from a user-specified bus channel. The data may be displayed as a waveform graph or a bar chart.

[0066] In this embodiment, the execution entity of the method can be the aforementioned vehicle data processing system. Specifically, it can receive bus data from the vehicle bus and process the bus data to generate first processed data. Then, the front-end display module generates display data based on the first processed data sent by the back-end data processing module and displays the display data.

[0067] For details on the implementation process of the vehicle data processing method provided in this application embodiment, please refer to the detailed description of the above system embodiment, which will not be repeated here.

[0068] The vehicle data processing method provided in this application replaces the existing CANOE for acquiring and processing bus data by installing a back-end data processing module connected to the vehicle bus and a front-end display module connected to the back-end data processing module via Ethernet on the vehicle. This reduces the use of wiring harnesses, improves development efficiency, and greatly reduces development costs.

[0069] The above describes the internal functions and structure of the vehicle data processing system, which can be implemented as an electronic device. Figure 5 A schematic diagram illustrating the structure of an embodiment of the electronic device provided in this application. (See attached diagram.) Figure 5As shown, the electronic device includes a memory 51 and a processor 52.

[0070] Memory 51 is used to store programs. In addition to the programs described above, memory 51 can also be configured to store various other data to support operation on the electronic device. Examples of this data include instructions for any application or method used to operate on the electronic device, contact data, phonebook data, messages, pictures, videos, etc.

[0071] The memory 51 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0072] The processor 52 is not limited to a central processing unit (CPU), but may also be a graphics processing unit (GPU), a field-programmable gate array (FPGA), an embedded neural network processor (NPU), or an artificial intelligence (AI) chip. The processor 52 is coupled to the memory 51 and executes the program stored in the memory 51. When this program runs, it performs the vehicle data processing method described in the above embodiments.

[0073] Furthermore, such as Figure 5 As shown, the electronic device may also include other components such as a communication component 53, a power supply component 54, an audio component 55, and a display 56. Figure 5 The diagram only shows some components and does not mean that the electronic device includes only these components. Figure 5 The components shown.

[0074] Communication component 53 is configured to facilitate wired or wireless communication between electronic devices and other devices. The electronic devices can access wireless networks based on communication standards, such as WiFi, 3G, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 53 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 53 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0075] Power supply component 54 provides power to various components of the electronic device. Power supply component 54 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device.

[0076] Audio component 55 is configured to output and / or input audio signals. For example, audio component 55 includes a microphone (MIC) configured to receive external audio signals when the electronic device is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 51 or transmitted via communication component 53. In some embodiments, audio component 55 also includes a speaker for outputting audio signals.

[0077] Display 56 includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touchscreen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation.

[0078] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0079] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A vehicle data processing system, characterized in that, include: The front-end display module and the back-end data processing module installed on the vehicle, among which, The background data processing module is connected to the vehicle bus and is used to receive bus data from the vehicle bus and process the bus data to generate first processed data. The background data processing module includes: The first processing core is used to communicate with the vehicle bus, receive bus data from the vehicle bus, assemble the bus data according to preset byte data to obtain a data packet, and send the data packet to the second processing core. The first processing core is an M-core and the second processing core is an A-core. The second processing core is used to communicate with the first processing core, receive data packets sent by the first processing core, parse the data packets to obtain the preset byte data and bus data, send the bus data to a shared queue, and send a prompt signal to the data processing service of the second processing core. The prompt signal is used to instruct the data processing service to retrieve the bus data from the shared queue. The data processing service processes the bus data according to a preset processing operation to generate first processed data, and sends the first processed data to the front-end display module. The front-end display module is connected to the back-end data processing module via Ethernet. It is used to generate display data based on the first processed data sent by the back-end data processing module and to display the display data.

2. The vehicle data processing system according to claim 1, characterized in that, The front-end display module is specifically used to generate display data based on the first processed data sent by the second processing core, and to display the display data.

3. The vehicle data processing system according to claim 1, characterized in that, The front-end display module includes: The generation submodule is used to generate display data corresponding to the first processed data based on the first processed data and a preset correspondence between the first processed data and the display data. The display submodule is used to display the display data.

4. The vehicle data processing system according to claim 3, characterized in that, The display submodule includes one or more of the following: a vehicle basic information display section, a vehicle-customized signal display section, and a user-customized display section. The data displayed in the vehicle basic information display section is the vehicle's basic information; The data displayed in the vehicle's custom signal display section includes one or more of the following: vehicle speed information, motor power information, and high beam status information. The user-defined display panel displays data including bus data from the bus channel specified by the user.

5. A vehicle data processing method, characterized in that, A vehicle data processing system suitable for installation in a vehicle, the vehicle data processing system including a back-end data processing module connected to the vehicle bus and a front-end display module connected to the back-end data processing module via Ethernet, the method comprising: The background data processing module receives bus data from the vehicle bus and processes the bus data to generate first processed data. Based on the first processed data, display data is generated using the front-end display module, and the display data is then displayed. The background data processing module includes: The first processing core is used to communicate with the vehicle bus, receive bus data from the vehicle bus, assemble the bus data according to preset byte data to obtain a data packet, and send the data packet to the second processing core. The first processing core is an M-core and the second processing core is an A-core. The second processing core is used to communicate with the first processing core, receive data packets sent by the first processing core, parse the data packets to obtain the preset byte data and bus data, send the bus data to a shared queue, and send a prompt signal to the data processing service of the second processing core. The prompt signal is used to instruct the data processing service to obtain the bus data from the shared queue. The data processing service processes the bus data according to a preset processing operation to generate first processed data, and sends the first processed data to the front-end display module.

6. An electronic device, characterized in that, include: Memory, used to store programs; A processor is configured to run the program stored in the memory to perform the vehicle data processing method as described in claim 5.

7. A computer-readable storage medium, characterized in that, It stores a computer program that can be executed by a processor, wherein the program, when executed by the processor, implements the vehicle data processing method as described in claim 5.

Images