Vehicle domain controller interaction system, method and device and storage medium

Abstract

The invention discloses a vehicle domain controller interaction system, method and device and a storage medium. Comprising a cloud platform, a communication module connected with the cloud platform, an on-chip system connected with the communication module and a micro-control unit connected with the on-chip system, the cloud platform is used for proofreading the software version of the vehicle domain controller, acquiring the vehicle request information when the proofreading is passed, generating a request message according to the vehicle request information, and forwarding the request message to the system on chip through the communication module; the system on chip is used for decrypting the obtained request message to generate a decrypted message and sending the decrypted message to the micro-control unit; and the micro-control unit is used for acquiring request data corresponding to the decrypted message, so that developers can remotely monitor and debug software of the vehicle domain controller, the functions of remote diagnosis, upgrading, calibration and the like of the vehicle domain controller are realized, the expansibility is high, the requirements of software and hardware of an upper computer can be reduced, and the development cost of software and hardware is saved.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle interaction, and particularly to a vehicle domain controller interaction system, method, device, and storage medium. Background Art

[0002] The diagnostic and calibration functions often used in vehicle domain controllers require an Ethernet environment for their application scenarios, that is, they need to be directly connected to DoIP or XCP host computer software with a network cable for diagnosis and calibration. When developers troubleshoot problems, they need to carry hardware devices to the site for joint debugging, which requires a great deal of manpower and time for both the hardware devices and developers, seriously affecting the development progress. Due to the high urgency of the project, for problems with a low recurrence rate or situations where it is difficult to retain the problem site, problem items are often ignored by developers, and the software reset method is directly used to avoid the problems, which undoubtedly poses a serious security risk to software quality.

[0003] Most current remote interaction solutions adopt custom protocols. The custom data formats and payloads often need to be predefined in advance. If the protocol changes, each relevant node in the upgrade process needs to synchronously update the software, which is very unfriendly to function expansion and remote debugging. Sometimes, there will also be problems with abnormal data in remote interaction caused by software version mismatches, and troubleshooting problems will also consume a large amount of time and manpower. Summary of the Invention

[0004] The present invention provides a vehicle domain controller interaction system, method, device, and storage medium, which can enable developers to remotely monitor and debug the software of the vehicle domain controller, and realize functions such as vehicle remote diagnosis, upgrade, and calibration.

[0005] According to an aspect of the present invention, a vehicle domain controller interaction system is provided. The system includes: a cloud platform, a communication module connected to the cloud platform, a system-on-chip connected to the communication module, and a microcontroller unit connected to the system-on-chip;

[0006] The cloud platform is used to proofread the software version of the vehicle domain controller. When the proofreading is passed, it obtains vehicle request information, generates a request message according to the vehicle request information, and forwards the request message to the system-on-chip through the communication module, where the vehicle request information includes fault information, variable data, or status information;

[0007] The system-on-chip is used to decrypt the obtained request message to generate a decrypted message, and send the decrypted message to the microcontroller unit;

[0008] The microcontroller unit is used to obtain the request data corresponding to the decrypted message.

[0009] Optionally, the system further includes: a client connected to the cloud platform; the client is configured to obtain an identification code input by a user, generate vehicle request information according to the identification code, and send the vehicle request information to the cloud platform.

[0010] Optionally, the micro control unit is further configured to send the request data to the system on chip; the system on chip is further configured to send the request data to the cloud platform through the communication module; the cloud platform is configured to parse the received request data to generate parsed data, and send the parsed data to the client; the client is configured to display the obtained parsed data in a specified manner.

[0011] Optionally, the micro control unit includes: an Internet data center and a diagnostic event management module; when the vehicle request information is a fault message, the cloud platform is configured to directly encrypt the vehicle request information to generate a request message; the Internet data center is configured to receive the decrypted message, obtain the fault information of the diagnostic event management module according to the decrypted message, and use the fault information as the request data.

[0012] Optionally, when the vehicle request information is variable data or status information, the cloud platform is configured to obtain an executable file, determine variable-related information included in the executable file according to the vehicle request information, and encrypt the variable-related information to generate a request message, where the variable-related information includes a variable start address and a variable length; the micro control unit is configured to obtain target data according to the variable start address and the variable length, and use the target data as the request data.

[0013] Optionally, the micro control unit further includes: an in-vehicle Ethernet diagnostic module and a diagnostic communication management module; the cloud platform is further configured to obtain a diagnostic request, and send the diagnostic request to the in-vehicle Ethernet diagnostic module through the communication module and the system on chip; the in-vehicle Ethernet diagnostic module is configured to establish a connection with the client based on the diagnostic request, generate a connection response, and send the connection response to the diagnostic communication management module; the diagnostic communication management module is configured to obtain a diagnostic result based on the connection response.

[0014] Optionally, the micro control unit further includes: a general measurement and calibration module; the cloud platform is further configured to obtain a calibration measurement request, and send the calibration measurement request to the general measurement and calibration module through the communication module and the system on chip; the general measurement and calibration module is configured to establish a connection with the client based on the calibration measurement request, and obtain a calibration result.

[0015] According to another aspect of the present invention, there is provided a vehicle domain controller interaction method, the method includes:

[0016] The software version of the vehicle domain controller is verified through a cloud platform. When the verification passes, vehicle request information is obtained, a request message is generated based on the vehicle request information, and the request message is forwarded to the system-on-chip through a communication module, where the vehicle request information includes fault information or variable data or status information;

[0017] The system-on-chip decrypts the obtained request message to generate a decrypted message and sends the decrypted message to the microcontroller unit;

[0018] The microcontroller unit obtains request data corresponding to the decrypted message.

[0019] According to another aspect of the present invention, there is provided an electronic device, which includes:

[0020] At least one processor; and

[0021] A memory communicatively connected to the at least one processor; wherein,

[0022] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute a vehicle domain controller interaction method according to any embodiment of the present invention.

[0023] According to another aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement a vehicle domain controller interaction method according to any embodiment of the present invention when executed.

[0024] The technical solution of the embodiments of the present invention includes: a cloud platform, a communication module connected to the cloud platform, a system-on-chip connected to the communication module, and a microcontroller unit connected to the system-on-chip; the cloud platform is used to verify the software version of the vehicle domain controller. When the verification passes, vehicle request information is obtained, a request message is generated based on the vehicle request information, and the request message is forwarded to the system-on-chip through the communication module; the system-on-chip is used to decrypt the obtained request message to generate a decrypted message and send the decrypted message to the microcontroller unit; the microcontroller unit is used to obtain request data corresponding to the decrypted message, which can enable developers to remotely monitor and debug the software of the vehicle domain controller, realize functions such as remote diagnosis, upgrade, and calibration of the vehicle domain controller, has strong scalability, can reduce the requirements for upper computer software and hardware, and saves the software and hardware development costs.

[0025] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present invention, nor is it used to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] To more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0027] Figure 1 is a schematic structural diagram of a vehicle domain controller interaction system provided according to Embodiment 1 of the present invention;

[0028] Figure 2 is a schematic structural diagram of another vehicle domain controller interaction system provided according to Embodiment 1 of the present invention;

[0029] Figure 3 is a schematic structural diagram of another vehicle domain controller interaction system provided according to Embodiment 2 of the present invention;

[0030] Figure 4 is a flowchart of a vehicle domain controller interaction method provided according to Embodiment 3 of the present invention;

[0031] Figure 5 is a schematic structural diagram of an electronic device for implementing the vehicle domain controller interaction method of the embodiments of the present invention. Detailed Embodiments

[0032] In order to enable those skilled in the art to better understand the solutions of the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above drawings are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present invention described here can be implemented in an order other than those illustrated or described here. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units does not necessarily need to be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or devices.

[0034] Embodiment 1

[0035] Figure 1 FIG. 4 is a schematic structural diagram of a vehicle domain controller interaction system provided by Embodiment 1 of the present invention. The system includes: a cloud platform 110, a communication module 120 connected to the cloud platform 110, a system-on-chip 130 connected to the communication module 120, and a microcontroller unit 140 connected to the system-on-chip 130.

[0036] Among them, the cloud platform 110 refers to a vehicle management and service platform based on cloud computing technology. It can store various information and data of the vehicle in the cloud and provide them for users to access and use through the Internet. The vehicle cloud platform 110 can realize functions such as remote monitoring, fault diagnosis, maintenance, vehicle scheduling, driving record, and driving behavior analysis of the vehicle, so as to improve the use efficiency and safety of the vehicle, and reduce the operation cost and maintenance cost of the vehicle. The communication module 120 is used for data transmission between the cloud platform 110 and the system-on-chip 130, and can be TBox-4 / 5G. The system-on-chip 130 (System on Chip, SOC) is the SOC node of the domain controller, which is a system that integrates the control and processing functions of the vehicle onto a single chip. The microcontroller unit 140 (Microcontroller Unit, MCU) is the MCU node of the domain controller, which is a microcontroller used to control and process various electronic devices and systems of the vehicle, and can realize various control and processing functions of the vehicle.

[0037] It can be known that SOC+MCU is the most commonly used electrical architecture for current in-vehicle domain controllers. As is well known, due to the limitation of MCU hardware resources, there is a lack of offline debugging means during the development and use process, and hardware debugging tools are often used in combination with debug. With more and more MCUs supporting Ethernet communication and the improvement of hardware resources, remote interaction and remote upgrade can be carried out with the MCU through Ethernet. Remote interaction can upload the internal status and data of the MCU to the cloud platform 110 for analysis. At present, there is no mature solution for remote interaction and upgrade in the industry. This system integrates the currently commonly used online debugging method and custom interaction method in the MCU, which can enable developers to remotely monitor and debug the software of the MCU, and realize functions such as remote diagnosis, upgrade, and calibration of the MCU.

[0038] Optionally, the cloud platform 110 is used to proofread the software version of the vehicle domain controller. When the proofreading is passed, the vehicle request information is obtained, a request message is generated according to the vehicle request information, and the request message is forwarded to the system-on-chip 130 through the communication module 120, where the vehicle request information includes fault information, variable data, or status information; the system-on-chip 130 is used to decrypt the obtained request message to generate a decrypted message and send the decrypted message to the microcontroller unit 140; the microcontroller unit 140 is used to obtain the request data corresponding to the decrypted message.

[0039] Specifically, the cloud platform 110 can proofread the software version of the vehicle domain controller. The proofreading is carried out by, after the power-on of the Autonomous Driving Unit (ADU) domain controller, the ADU-MCU actively sending the current software version information of the ADU-MCU to the real vehicle software management cloud platform 110 through a custom protocol. After receiving it, the cloud platform 110 goes to the software management server to find the software package corresponding to this version and updates it to the real vehicle software version management system. The software package contains files such as s19 / hex / elf to achieve software version proofreading. Through the real-time interaction between the cloud platform 110 and the software management server, if it is found that the real vehicle software version has changed, the corresponding elf file is synchronously updated for the use of the XCP host computer, avoiding the problem that the software used by the XCP host computer does not match the real vehicle software version. The cloud platform 110 can obtain the latest version of software on the software management server, compare it with the real vehicle software version, manage the real vehicle upgrade service, and each real vehicle can be upgraded individually according to different needs, making the software on the real vehicle more flexible; it can also implement batch upgrade operations, and the upgrade speed is faster.

[0040] When the proofreading is passed, the cloud platform 110 obtains the vehicle request information, including fault information, variable data, or status information, etc. Then, the cloud platform 110 generates a request message according to the vehicle request information and forwards the request message to the system-on-chip 130 through the communication module 120. After receiving the request message, the system-on-chip 130 decrypts it to generate a decrypted message and sends the decrypted message to the microcontroller unit 140. The microcontroller unit 140 obtains the request data corresponding to the decrypted message and performs corresponding processing according to the request data. By encrypting the transmission of the message, the security of communication and the consistency of data are ensured.

[0041] Figure 2 FIG. 1 is a schematic structural diagram of a vehicle domain controller interaction system provided in Embodiment 1 of the present invention. The microcontroller unit 140 specifically includes: an Internet data center 141, a diagnostic event management module 142, an in-vehicle Ethernet diagnostic module 143, a diagnostic communication management module 144, and a general measurement and calibration module 145.

[0042] Among them, the Internet Data Center 141 is used to directly interact with the Ethernet module of the SOC to implement the reporting of the status and fault information of the MCU. The Diagnostic Event Management Module 142 is used to record the fault status and fault information of the MCU and support the ISO14229 diagnostic standard. The Diagnostic Communication Management Module 144 is used to provide communication management and connection for the diagnostic service module to ensure the consistency and stability of the communication status. The General Measurement and Calibration Module 145 is used to implement the online calibration and measurement of variables in the RAM and ROM, as well as the acquisition and solidification of calibration data, etc.

[0043] Optionally, the microcontroller unit 140 includes: an Internet Data Center 141 and a Diagnostic Event Management Module 142; the cloud platform 110 is used to directly encrypt the vehicle request information to generate a request message when the vehicle request information is fault information; the Internet Data Center 141 is used to receive the decrypted message, obtain the fault information of the Diagnostic Event Management Module 142 according to the decrypted message, and use the fault information as the request data.

[0044] Specifically, the microcontroller unit 140 includes an Internet Data Center 141 and a Diagnostic Event Management Module 142. The Internet Data Center 141 is a facility for centralized management and storage of data. It can be connected to other devices and systems through the Internet to provide services such as data storage, processing, and distribution. The Diagnostic Event Management Module 142 is a module for processing vehicle fault diagnosis events. It can collect vehicle fault information and send it to the Internet Data Center 141 for processing. The cloud platform 110 is used to directly encrypt the vehicle request information to generate a request message when the vehicle request information is fault information, and then send the request message to the communication module 120. The communication module 120 forwards it to the system-on-chip 130, and the system-on-chip 130 decrypts the request message and sends it to the Internet Data Center 141.

[0045] Furthermore, the Internet Data Center 141 can receive the decrypted message sent by the system-on-chip 130, obtain the fault information in the RAM of the Diagnostic Event Management Module 142 according to the decrypted message, and use the fault information as the request data. It should be noted that the Diagnostic Event Management Module 142 will read the fault codes in the Flash into the RAM after power-on, update the RAM during operation, and write them back to the Flash after power-off.

[0046] Optionally, the cloud platform 110 is used to obtain an executable file when the vehicle request information is variable data or status information, determine the variable-related information included in the executable file according to the vehicle request information, and encrypt the variable-related information to generate a request message, where the variable-related information includes the variable start address and the variable length; the microcontroller unit 140 is used to obtain the target data according to the variable start address and the variable length, and use the target data as the request data.

[0047] Specifically, when the vehicle request information is variable data or status information, the cloud platform 110 can parse the elf file corresponding to the current in-vehicle software to obtain the executable file carrying data information, and determine the variable start address and variable length corresponding to the requested variable in the executable file as variable-related information. Then, the variable-related information is encrypted to generate a request message. The Internet Data Center 141 in the microcontroller unit 140 can obtain the target data in the RAM as the request data according to the variable start address and variable length. For example, the Internet Data Center can directly obtain the specified variable status through the requested address and length. By parsing the elf by the cloud platform 110, access to any variable can be achieved. Regardless of which status query requests need to be added, without modifying the communication protocol, the data at the specified RAM address can be directly accessed.

[0048] Optionally, the microcontroller unit 140 further includes: an in-vehicle Ethernet diagnostic module 143 and a diagnostic communication management module 144; the cloud platform 110 is further configured to obtain a diagnostic request and send the diagnostic request to the in-vehicle Ethernet diagnostic module 143 through the communication module 120 and the system-on-chip 130; the in-vehicle Ethernet diagnostic module 143 is configured to establish a connection with the client 150 based on the diagnostic request, generate a connection response, and send the connection response to the diagnostic communication management module 144; the diagnostic communication management module 144 is configured to obtain a diagnostic result based on the connection response.

[0049] Specifically, the diagnostic request includes a Vehicle Identification Number (VIN) code. The cloud platform 110 can transmit the diagnostic request transparently to the communication module 120 according to the VIN code. Here, transparent transmission means a data transmission method that directly transmits data without processing the data. The communication module 120 will transmit the diagnostic request transparently to the system-on-chip 130, and the system-on-chip 130 will transmit the diagnostic request transparently to the in-vehicle Ethernet diagnostic module 143 of the microcontroller unit 140. The microcontroller unit 140 can establish a connection with the in-vehicle Ethernet diagnostic host computer through the in-vehicle Ethernet diagnostic module 143 and perform diagnostic service interaction through the diagnostic communication management module 144 to obtain a diagnostic result. Through the in-vehicle Ethernet diagnostic module 143 and the diagnostic communication management module 144, functions such as remote diagnosis and troubleshooting of the vehicle can be realized, improving the reliability and safety of the vehicle. At the same time, through the cloud platform 110 and the communication module 120, real-time transmission and storage of vehicle diagnostic data can be achieved, providing an important reference basis for vehicle maintenance and servicing.

[0050] Optionally, the microcontroller unit 140 further includes: a general measurement and calibration module 145; the cloud platform 110 is further configured to obtain a calibration measurement request, and send the calibration measurement request to the general measurement and calibration module 145 through the communication module 120 and the system-on-chip 130; the general measurement and calibration module 145 is configured to establish a connection with the client 150 based on the calibration measurement request and obtain a calibration result.

[0051] Specifically, the calibration measurement request includes a vehicle VIN code. The VIN code transmits the calibration measurement request to the communication module 120. The communication module 120 transmits the calibration measurement request to the system-on-chip 130. The system-on-chip 130 transmits the calibration measurement request to the general measurement and calibration module 145 of the microcontroller unit 140. The microcontroller unit 140 can establish a connection with the general measurement and calibration host computer through the general measurement and calibration module 145 to obtain a calibration result.

[0052] The technical solution of the embodiment of the present invention includes: a cloud platform, a communication module connected to the cloud platform, a system-on-chip connected to the communication module, and a microcontroller unit connected to the system-on-chip; the cloud platform is configured to proofread the software version of the vehicle domain controller. When the proofreading is passed, obtain vehicle request information, generate a request message according to the vehicle request information, and forward the request message to the system-on-chip through the communication module; the system-on-chip is configured to decrypt the obtained request message to generate a decrypted message and send the decrypted message to the microcontroller unit; the microcontroller unit is configured to obtain request data corresponding to the decrypted message, which can enable developers to remotely monitor and debug the software of the vehicle domain controller, realize functions such as remote diagnosis, upgrade, and calibration of the vehicle domain controller, has strong scalability, can reduce the requirements for host computer software and hardware, and saves the software and hardware development costs.

[0053] Embodiment 2

[0054] Figure 3 FIG. 13 is a schematic structural diagram of a vehicle domain controller interaction system provided in Embodiment 2 of the present invention. In this embodiment, a client 150 is added on the basis of Embodiment 1 above.

[0055] Optionally, the system further includes: a client 150 connected to the cloud platform 110; the client 150 is configured to obtain an identification code input by a user, generate vehicle request information according to the identification code, and send the vehicle request information to the cloud platform 110.

[0056] Among them, the client 150 can be a mobile application or a web interface. Users can input an identification code through the client 150. The identification code can be a vehicle VIN code, a fault identifier, or a variable identifier. The client 150 will generate vehicle request information based on the identification code and send the vehicle request information to the cloud platform 110. The cloud platform 110 will perform corresponding processing according to the vehicle request information and return the processing result to the client 150. Through the interaction between the client 150 and the cloud platform 110, users can conveniently obtain relevant information about the vehicle, such as the vehicle status and fault information, etc., so as to realize remote monitoring and management of the vehicle.

[0057] Optionally, the microcontroller unit 140 is further configured to send the request data to the system-on-chip 130; the system-on-chip 130 is further configured to send the request data to the cloud platform 110 through the communication module 120; the cloud platform 110 is configured to parse the received request data to generate parsed data and send the parsed data to the client 150; the client 150 is configured to display the obtained parsed data in a specified manner.

[0058] Specifically, the system-on-chip 130 sends the request data to the cloud platform 110 through the communication module 120. The cloud platform 110 parses the received request data to generate parsed data and sends the parsed data to the client 150. For example, the cloud platform 110 can parse the received data according to elf to obtain the detailed information of the variables (including the parsing of each attribute of the struct) and feedback it to the client 150. The client 150 displays the obtained parsed data in a specified manner, such as displaying or recording it in the form of a chart. In this way, the client 150 can conveniently obtain the diagnostic results or vehicle information and display it to the user. At the same time, the cloud platform 110 can process and analyze the received request data to provide more accurate and detailed diagnostic results or vehicle information.

[0059] In addition, the general measurement and calibration module 145 can also establish a connection with the client 150 to realize interaction with the client 150. The client 150 can obtain the calibration result of the sensor through the general measurement and calibration module 145 and adjust the sensor according to the calibration result to improve the accuracy and reliability of the sensor.

[0060] The technical solution of the embodiment of the present invention includes: a cloud platform, a communication module connected to the cloud platform, a system-on-chip connected to the communication module, and a microcontroller unit connected to the system-on-chip; the cloud platform is used to proofread the software version of the vehicle domain controller, and when the proofreading passes, obtain vehicle request information, generate a request message according to the vehicle request information, and forward the request message to the system-on-chip through the communication module; the system-on-chip is used to decrypt the obtained request message to generate a decrypted message and send the decrypted message to the microcontroller unit; the microcontroller unit is used to obtain request data corresponding to the decrypted message, which can enable developers to remotely monitor and debug the software of the vehicle domain controller, realize functions such as remote diagnosis, upgrade, and calibration of the vehicle domain controller, with strong scalability, can reduce the requirements for upper computer software and hardware, and save the software and hardware development costs.

[0061] Embodiment III

[0062] Figure 4 The flowchart of a vehicle domain controller interaction method provided for Embodiment III of the present invention is applicable to the scenario where a user interacts with a vehicle. As Figure 4 shown, the method includes:

[0063] S310. Proofread the software version of the vehicle domain controller through the cloud platform. When the proofreading passes, obtain vehicle request information, generate a request message according to the vehicle request information, and forward the request message to the system-on-chip through the communication module, where the vehicle request information includes fault information, variable data, or status information.

[0064] Specifically, the cloud platform can proofread the software version of the vehicle domain controller. The proofreading is carried out by the ADU-MCU actively sending the current software version information of the ADU-MCU to the real vehicle software management cloud platform through a custom protocol after the Autonomous Driving Unit (ADU) domain controller is powered on. After receiving it, the cloud platform goes to the software management server to find the software package corresponding to this version and updates it to the real vehicle software version management system. The software package contains files such as s19 / hex / elf to achieve software version proofreading. Through the real-time interaction between the cloud platform and the software management server, if it is found that the real vehicle software version has changed, the corresponding elf file is synchronously updated for the XCP upper computer to use, avoiding the problem that the software used by the XCP upper computer does not match the real vehicle software version. The cloud platform can obtain the latest version of the software on the software management server, compare it with the real vehicle software version, manage the real vehicle upgrade service, and each real vehicle can be upgraded separately according to different needs, making the software on the real vehicle more flexible; it can also implement batch upgrade operations, and the upgrade speed is faster.

[0065] S320. Decrypt the obtained request message through the system on a chip to generate a decrypted message, and send the decrypted message to the microcontroller unit.

[0066] S330. Obtain the request data corresponding to the decrypted message through the microcontroller unit.

[0067] When the verification passes, the cloud platform will obtain vehicle request information, including fault information, variable data, or status information, etc. Then, the cloud platform will generate a request message based on the vehicle request information and forward the request message to the system on a chip through the communication module. After receiving the request message, the system on a chip will decrypt it to generate a decrypted message and send the decrypted message to the microcontroller unit. The microcontroller unit will obtain the request data corresponding to the decrypted message and perform corresponding processing according to the request data. By encrypting the transmission of the message, the security of communication and the consistency of data are ensured.

[0068] The technical solution of the embodiment of the present invention enables developers to remotely monitor and debug the software of the vehicle domain controller, realizing functions such as remote diagnosis, upgrade, and calibration of the vehicle domain controller. It has strong scalability, can reduce the requirements for the upper computer software and hardware, and saves the software and hardware development costs.

[0069] Embodiment 4

[0070] Figure 5 FIG. shows a schematic structural diagram of an electronic device 10 that can be used to implement the embodiments of the present invention. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are only examples and are not intended to limit the implementation of the present invention described and / or claimed herein.

[0071] As Figure 5As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0072] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0073] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The processor 11 executes the various methods and processes described above, such as a vehicle domain controller interaction method. That is: the software version of the vehicle domain controller is proofread through the cloud platform, and when the proofreading passes, the vehicle request information is obtained, a request message is generated according to the vehicle request information, and the request message is forwarded to the system on chip through the communication module, wherein the vehicle request information includes fault information or variable data or status information; the obtained request message is decrypted by the system on chip to generate a decrypted message, and the decrypted message is sent to the microcontroller; the request data corresponding to the decrypted message is obtained by the microcontroller.

[0074] In some embodiments, a method for vehicle domain controller interaction can be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the method for vehicle domain controller interaction described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform a method for vehicle domain controller interaction by any other suitable means (e.g., by means of firmware).

[0075] The various embodiments of the systems and techniques described above in this document can be implemented in digital electronic circuitry, integrated circuit systems, field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), application specific standard products (ASSP), systems on a chip (SOC), complex programmable logic devices (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special-purpose or general-purpose programmable processor that receives data and instructions from a storage system, at least one input device, and at least one output device, and transmits the data and instructions to the storage system, the at least one input device, and the at least one output device.

[0076] The computer programs for implementing the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions / operations specified in the flowchart and / or block diagram to be implemented. The computer programs can be executed entirely on the machine, partially on the machine, as a stand-alone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0077] In the context of the present invention, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable storage medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0078] In order to provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, speech input, or tactile input).

[0079] The systems and techniques described herein can be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer having a graphical user interface or a web browser through which the user can interact with an implementation of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local area network (LAN), wide area network (WAN), blockchain network, and the Internet.

[0080] A computing system may include a client and a server. The client and the server are generally far from each other and usually interact via a communication network. The relationship between the client and the server is created by computer programs that run on respective computers and have a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or a cloud host, which is a host product in the cloud computing service system, solving the defects of difficult management and weak business scalability existing in traditional physical hosts and VPS services.

[0081] It should be understood that various forms of the processes shown above can be used, with steps reordered, added, or deleted. For example, the steps recited in the present invention can be executed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved, and no limitation is made herein.

[0082] The above specific embodiments do not constitute a limitation on the protection scope of the present invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims

1. A vehicle domain controller interaction system, characterized in that, It includes: a cloud platform, a communication module connected to the cloud platform, a system-on-chip connected to the communication module, and a microcontroller unit connected to the system-on-chip; The cloud platform is used to proofread the software version of the vehicle domain controller. When the proofreading is passed, it acquires vehicle request information, generates a request message according to the vehicle request information, and forwards the request message to the system-on-chip through the communication module. Among them, the vehicle request information includes fault information, variable data, or status information; The system-on-chip is used to decrypt the acquired request message to generate a decrypted message and send the decrypted message to the microcontroller unit; The microcontroller unit is used to acquire request data corresponding to the decrypted message.

2. The system according to claim 1, characterized in that, The system further includes: a client connected to the cloud platform; The client is used to acquire an identification code input by a user, generate the vehicle request information according to the identification code, and send the vehicle request information to the cloud platform.

3. The system according to claim 2, characterized in that, The microcontroller unit is further used to send the request data to the system-on-chip; The system-on-chip is further used to send the request data to the cloud platform through the communication module; The cloud platform is used to parse the received request data to generate parsed data and send the parsed data to the client; The client is used to display the acquired parsed data in a specified manner.

4. The system according to claim 2, characterized in that, The microcontroller unit includes: an Internet data center and a diagnostic event management module; The cloud platform is used to directly encrypt the vehicle request information to generate a request message when the vehicle request information is fault information; The Internet data center is used to receive the decrypted message, acquire the fault information of the diagnostic event management module according to the decrypted message, and use the fault information as the request data.

5. The system according to claim 1, characterized in that, The cloud platform is used to acquire an executable file when the vehicle request information is variable data or status information, determine the variable-related information included in the executable file according to the vehicle request information, and encrypt the variable-related information to generate a request message. Among them, the variable-related information includes a variable start address and a variable length; The microcontroller unit is used to acquire target data according to the variable start address and the variable length and use the target data as the request data.

6. The system according to claim 4, characterized in that, The microcontroller unit further includes: an in-vehicle Ethernet diagnostic module and a diagnostic communication management module; The cloud platform is further used to acquire a diagnostic request and send the diagnostic request to the in-vehicle Ethernet diagnostic module through the communication module and the system-on-chip; The in-vehicle Ethernet diagnostic module is used to establish a connection with the client based on the diagnostic request, generate a connection response, and send the connection response to the diagnostic communication management module; The diagnostic communication management module is used to acquire a diagnostic result based on the connection response.

7. The system according to claim 6, characterized in that, The microcontroller unit further includes: a general measurement and calibration module; The cloud platform is further configured to obtain a calibration measurement request and send the calibration measurement request to the general measurement and calibration module through the communication module and the system-on-chip. The general measurement and calibration module is configured to establish a connection with the client based on the calibration measurement request and obtain a calibration result.

8. A vehicle domain controller interaction method, characterized in that, Applied to a vehicle domain controller interaction system according to any one of claims 1-7, comprising: The software version of the vehicle domain controller is verified through the cloud platform. When the verification is passed, vehicle request information is obtained, a request message is generated according to the vehicle request information, and the request message is forwarded to the system-on-chip through the communication module, where the vehicle request information includes fault information or variable data or status information. The obtained request message is decrypted by the system-on-chip to generate a decrypted message, and the decrypted message is sent to the microcontroller unit. The microcontroller unit obtains request data corresponding to the decrypted message.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method described in claim 8.

10. A computer storage medium, characterized in that, The computer storage medium stores computer instructions for causing a processor to execute the method described in claim 8 when executed.

Images