WO2024037304A1

WO2024037304A1 - Vehicle diagnosis communication method and apparatus, and device, medium and program product

Info

Publication number: WO2024037304A1
Application number: PCT/CN2023/109481
Authority: WO
Inventors: 杨东耳
Original assignee: 北京经纬恒润科技股份有限公司
Priority date: 2022-08-16
Filing date: 2023-07-27
Publication date: 2024-02-22
Also published as: CN115390546A

Abstract

Provided are a vehicle diagnosis communication method and apparatus, and a device, a medium and a program product. The method comprises: receiving a diagnosis request sent by a diagnosis initiation apparatus (S401); in response to the diagnosis request, determining a diagnosis object on the basis of request content in the diagnosis request, wherein the diagnosis object comprises a target component requested to be diagnosed or accessed by means of the diagnosis request (S402); and returning a response message of the diagnosis request to the diagnosis initiation apparatus according to the diagnostic condition of the diagnosis object (S403).

Description

Vehicle diagnostic communication methods, devices, equipment, media and program products

Cross-references to related applications

This disclosure claims priority to Chinese patent application 202210983254.4 titled "Vehicle Diagnostic Communication Method, Device, Equipment and Medium" submitted on August 16, 2022. The entire content of this application is incorporated herein by reference.

Technical field

This application belongs to the field of vehicle technology, and specifically relates to a vehicle diagnostic communication method, device, equipment, media and program products.

Background technique

With the development of vehicle electronic technology, domain controllers have become an important part of vehicle electronic products. In the main control chip of the domain controller, a control unit and a computing unit are integrated. When the domain controller performs diagnostic communication, the control unit and the computing unit usually also need to communicate with each other. The domain controller communicates with other devices in the vehicle network. Domain controllers are also required for diagnostic communications.

Application content

In a first aspect, embodiments of the present application provide a vehicle diagnostic communication method, which is applied to a control unit in a domain controller of a vehicle. The vehicle diagnostic communication method includes:

Receive a diagnostic request sent by the diagnostic initiating device,

In response to the diagnosis request, determine the diagnosis object based on the request content in the diagnosis request, where the diagnosis object includes the target component required to be diagnosed or accessed by the diagnosis request,

According to the diagnosis situation of the diagnosis object, a response message of the diagnosis request is returned to the diagnosis initiating device.

In the second aspect, embodiments of the present application provide a vehicle diagnostic communication device, which is applied to a control unit in a domain controller of a vehicle. The vehicle diagnostic communication device includes:

a receiving unit, configured to receive a diagnosis request sent by the diagnosis initiating device,

a determination unit configured to respond to the diagnosis request and determine the diagnosis object based on the request content in the diagnosis request, wherein the diagnosis object includes the target component required to be diagnosed or accessed by the diagnosis request,

The sending unit is configured to return a response message of the diagnosis request to the diagnosis initiating device according to the diagnosis situation of the diagnosis object.

In a third aspect, the present application provides a chip, which includes a control unit configured to execute the vehicle diagnostic communication method as described in the first aspect.

In a fourth aspect, embodiments of the present application provide an electronic device. The electronic device includes: a processor and a memory storing computer program instructions. When the processor executes the computer program instructions, the vehicle diagnostic communication method of the first aspect is implemented:

In a fifth aspect, embodiments of the present application provide a computer storage medium. Computer program instructions are stored on the computer-readable storage medium. When the computer program instructions are executed by a processor, the vehicle diagnostic communication method of the first aspect is implemented.

In a sixth aspect, embodiments of the present application provide a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the vehicle diagnostic communication method of the first aspect.

In a seventh aspect, embodiments of the present application provide a computer program product, the program product is stored in a storage medium, and the program product is executed by at least one processor to implement the vehicle diagnostic communication method as in the first aspect.

Description of drawings

Figure 1 shows an example diagram of a vehicle network architecture using a domain controller.

Figure 2 shows an example flow diagram of diagnostic communication of a domain controller in the related art.

Figure 3 shows an example diagram of the software architecture for diagnostic communication between the control unit and the computing unit in the domain controller in the related art.

Figure 4 shows a schematic flowchart 1 of the vehicle diagnostic communication method provided by the embodiment of the present application.

Figure 5 shows a schematic flowchart 2 of the vehicle diagnostic communication method provided by the embodiment of the present application.

Figure 6 shows a schematic flowchart three of the vehicle diagnostic communication method provided by the embodiment of the present application.

Figure 7 shows a schematic flow chart of diagnostic communication when the diagnostic object is a domain controller, the domain controller is in a diagnostic state, and the diagnostic communication is used to instruct the domain controller to upgrade,

Figure 8 shows a schematic flow chart of diagnostic communication when the diagnostic object is a domain controller, the domain controller is in a diagnostic state, and the diagnostic communication is used to instruct the domain controller to upgrade,

Figure 9 shows a schematic flowchart 4 of the vehicle diagnostic communication method provided by the embodiment of the present application.

Figure 10 shows a schematic diagram of the software architecture for diagnostic communication between the control unit and the computing unit in the domain controller provided by the embodiment of the present application.

Figure 11 shows a schematic structural diagram of a vehicle diagnostic communication device provided by an embodiment of the present application.

Figure 12 shows the second structural schematic diagram of the vehicle diagnostic communication device provided by the embodiment of the present application.

Figure 13 shows a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application.

Detailed ways

Features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be described in further detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described here are only intended to explain the application, but not to limit the application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of embodiments is merely intended to provide a better understanding of the present application by illustrating examples thereof.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or operations are mutually exclusive. any such actual relationship or sequence exists between them. Furthermore, the terms "comprises,""comprises," or any other variations thereof are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also those not expressly listed other elements, or elements inherent to the process, method, article or equipment. exist Without further limitation, an element defined by the statement "including..." does not exclude the presence of additional identical elements in the process, method, article, or device that includes the element.

First, the terms involved in this application will be explained to facilitate understanding by those skilled in the art:

Diagnostic communication: The process in which the diagnostic instrument communicates with the vehicle based on the communication protocol used for vehicle diagnosis to provide diagnostic services to the vehicle. Among them, the communication protocol used for vehicle diagnosis is such as Unified Diagnostic Services (UDS).

As an example, when a vehicle fails, the maintenance personnel can connect the diagnostic instrument to the OBD (On-Board Diagnostic) port on the vehicle, and the diagnostic instrument sends a diagnostic request to the domain controller of the vehicle through the OBD port to request to read the interior of the vehicle. Some information, such as requesting some sensor data, application running logs, etc.

Domain controller: Divide various electronic functions on the vehicle into several areas, and the domain controller is responsible for realizing the functions in the corresponding areas. In the main control chip of the domain controller, at least one control unit and at least one computing unit are integrated. The control unit can be called a microcontroller unit (MCU), and the computing unit can be called a microprocessor unit (MPU).

In the related technology, the external diagnostic instrument sends the diagnosis request to the computing unit in the domain controller. The computing unit acts as a collaborator for diagnostic communication between the domain controller and the external diagnostic instrument through the Internet Diagnostic Communication Protocol (Diagnostic communication over Internet Protocol). (DoIp for short) sends the request content of the diagnostic request to the control unit in the domain controller. During the response process of diagnostic communication, the control unit sends the response content to the computing unit through DoIP, and then the computing unit forwards the response content to the external diagnostic instrument.

However, the above vehicle diagnostic communication methods are less efficient.

Embodiments of the present application provide a vehicle diagnostic communication method, device, equipment, media and program products, which can solve the problem of low efficiency of vehicle diagnostic communication.

According to the embodiment of the present application, during the diagnostic communication process of the vehicle, the control unit in the domain controller serves as the route of the diagnostic communication (that is, as the coordinator of the diagnostic communication) and can directly receive the diagnostic request from the diagnostic initiating device without domain control. The computing unit in the processor forwards the diagnostic request to the control unit; after confirming After determining the diagnosis object, the control unit can also directly return the response message of the diagnosis request to the diagnosis initiating device based on the diagnosis status of the diagnosis object, without the need for the computing unit to forward the response message of the diagnosis request to the diagnosis initiating device. In this way, the number of message forwardings during the diagnostic communication process is reduced, the communication delay of the diagnostic communication is reduced, and the efficiency of the diagnostic communication is improved.

As shown in Figure 1, the vehicle network architecture may include one or more domain controllers, such as domain controller 1, domain controller 2, ..., domain controller n in Figure 1, where n represents The number of domain controllers. Among them, each domain controller can communicate with each other through the Ethernet in the car. Each domain controller can connect multiple electronic control units (Electronic Control Unit, ECU). For example, in Figure 1, domain controller 1 is connected to ECU11~ECU1N1, ECU21~ECU2N2, domain controller 2 is connected to ECU31~ECU3N3, ECU41~ECU4N4, and domain controller n is connected to ECU51~ECU5N5, ECU61~ECU6N6. Among them, N1~N6 all represent the number of ECUs.

As shown in Figure 1, in the vehicle's vehicle network architecture, the domain controller can also assume the function of the gateway. For example, domain controller 1 (can be another domain controller, Figure 1 takes domain controller 1 as an example) is connected to the OBD port through Ethernet (industrial grade Ethernet) and controller area network (Controller Area Network, CAN) , to communicate with an external diagnostic tool. Domain controller 1 (can be other domain controllers, Figure 1 takes domain controller 1 as an example) can connect to multiple electronic control units (Electronic Control Units, ECUs), and can also connect through in-car Ethernet (car-grade Ethernet ) is connected to ECU7 with networking function. Among them, ECU7 with networking function can also have a diagnostic instrument function and can send diagnostic communication requests to the domain controller through the in-vehicle Ethernet.

FIG. 2 shows an example flow chart of diagnostic communication of a domain controller in the related art.

As shown in Figure 2, when the diagnostic request is executed by the control unit itself, the diagnostic communication process includes the following steps S201 to S204:

S201. The external diagnostic instrument 10 sends a diagnosis request to the computing unit 20 in the domain controller.

S202, after receiving the diagnosis request, the computing unit 20 forwards the diagnosis request to Control unit 30 in the domain controller.

S203, when the diagnosis request is executed by the control unit 30 itself, after the control unit 30 executes the diagnosis request, it returns a response message corresponding to the diagnosis request to the computing unit 20 through DoIP.

S204: After receiving the response message from the control unit 30, the computing unit 20 sends a response message corresponding to the diagnosis request to the computing unit 20.

As shown in Figure 2, when the diagnostic request is executed by other ECUs in the vehicle network, the diagnostic communication process is as follows: step S205:

S205, the external diagnostic instrument 10 sends a diagnosis request to the computing unit 20 in the domain controller.

S206: After receiving the diagnosis request, the computing unit 20 forwards the diagnosis request to the control unit 30 in the domain controller through DoIP based on the in-vehicle Ethernet.

S207: When the diagnosis request is executed by other ECUs 40 in the vehicle network, the control unit 30 sends the diagnosis request to the other ECUs 40.

S208, the control unit 30 receives the response message returned from the other ECU 40.

S209, the control unit 30 responds to the response message from other ECUs 40 and returns the response message to the computing unit 20 through DoIP.

S210, the computing unit 20 returns the response message to the external diagnostic instrument 10.

It can be seen that in the above process, the computing unit 20 in the domain controller is the collaborator between the domain controller and the external diagnostic instrument 10 .

FIG. 3 shows an example software architecture diagram for diagnostic communication between the control unit 30 and the computing unit 20 in the domain controller in the related art. As shown in FIG. 3 , the external diagnostic instrument 10 communicates with the computing unit 20 through the switch (SWITCH) 50 , the computing unit 20 and the control unit 30 also communicate through the switch 50 , and the computing unit 20 communicates with other ECUs 40 through CAN.

As shown in Figure 3, during the diagnostic communication process, the external diagnostic instrument 10 sends the diagnostic request to the computing unit 20 through the switch 50. In the computing unit 20, the diagnostic request passes through multiple protocol layers 21 and enters the DoIP server 22. The DoIP server 22 enters the DoIP client 23, and then the DoIP client 23 passes the diagnosis request to the protocol layer 21. After passing through multiple protocol layers 21 and the switch 50, the diagnosis request is Among the multiple protocol layers 31 sent to the control unit 30 , the control unit 30 may route the diagnostic request in the routing module 32 , in the case where the diagnostic request is executed by the control unit 30 itself, such as by FIG. The single-chip computer (Dcm) 33 in 3 can also send diagnostic requests to other ECUs 40 through the CAN communication link 34. Similarly, the response message of the diagnosis request may be transmitted from the control unit 20 to the computing unit 30 and then to the external diagnostic instrument 50 based on the transmission path of the diagnosis request.

The diagnostic communication process shown in Figures 2 and 3 has the following problems:

Problem 1: The diagnostic communication process requires multiple information forwardings, resulting in large communication delays and low efficiency.

Problem 2: The communication between the computing unit and the control unit in the domain controller is based on Ethernet. It not only occupies the bus bandwidth of the switch, control unit and computing unit, but also needs to handle the receiving interruption and sending interruption of the Ethernet, occupying the communication There are more resources,

Question 3: Both the computing unit and the control unit in the domain controller need to implement the software functions of the DoIP-based diagnostic server and diagnostic client (for the external diagnostic instrument, the computing unit is the diagnostic server, and for the control unit, the computing unit The unit is a diagnostic client, for the computing unit, the control unit is a diagnostic server, for other ECUs, the control unit is a diagnostic client), the overall software complexity is high, resulting in long software development time and high development costs. .

In order to solve the above problems, embodiments of the present application provide a vehicle diagnostic communication method, device, equipment, medium and program product. In the embodiment of the present application, it is considered that the diagnostic operations for the domain controller are mostly controlled and executed by the control unit in the domain controller. In the diagnostic communication, the control unit in the domain controller is responsible for the communication between the diagnostic initiating device and the domain controller. There is no need for the computing unit in the domain controller to forward information, which reduces the number of information forwardings, reduces communication delays, improves communication efficiency, and helps save communication resources. At the same time, since the computing unit no longer needs to undertake the information forwarding work in diagnostic communication, the computing unit does not need to implement the software functions of the diagnostic server and the diagnostic client, and the control unit does not need to implement the software functions of the diagnostic client, thus reducing the burden on the computing unit and the control unit. Software complexity associated with diagnostic communications.

Next, the vehicle diagnostic communication method provided by the embodiment of the present application will be introduced with reference to application scenarios and drawings.

Figure 4 shows a schematic flowchart 1 of the vehicle diagnostic communication method provided by the embodiment of the present application. As shown in Figure 4, the vehicle diagnostic communication method includes:

S401. The control unit 30 in the domain controller receives the diagnosis request sent by the diagnosis initiating device 10.

Among them, the diagnosis initiating device 10 is a device that initiates a diagnosis request (which can also be understood as generating a diagnosis request). The diagnosis request is used to request the domain controller to perform diagnostic communication. In other words, the diagnosis initiating device 10 requests diagnosis of the vehicle by sending a diagnosis request to the control unit 30 in the domain controller.

In this embodiment, the control unit 30 directly receives the diagnosis request sent by the diagnosis initiating device 10 without receiving the diagnosis request forwarded by the computing unit in the domain controller.

In some embodiments, the diagnosis initiating device 10 may include at least one of the following: an external device, an ECU with networking capabilities in the vehicle, or a computing unit in a domain controller. Therefore, the diagnosis request can be sent to the control unit 30 in the domain controller through the flexible and diverse diagnosis initiating device 10 .

In the case where the diagnosis initiating device 10 is an external device, the external device can connect to the vehicle through a diagnostic communication port (such as an OBD port). A possible implementation of S401 includes: the control unit 30 in the domain controller receives data through the diagnostic communication port. A diagnosis request sent by the diagnosis initiating device 10.

In the case where the diagnosis initiating device 10 is an ECU with a networking function in a domain controller, the ECU with the networking function can generate a diagnosis request in response to an instruction from a third-party device to perform vehicle diagnostic communication through the network. Another possibility in S401 The implementation method includes: the control unit 30 in the domain controller receives the diagnostic request sent by the ECU with the networking function through the in-vehicle Ethernet or CAN.

In the case where the diagnosis initiating device 10 is a computing unit in a domain controller, the computing unit has a diagnostic function, so the computing unit itself can generate diagnostic requests regularly, or the computing unit can perform vehicle diagnostic communication in response to instructions from a third-party device through the network. Instructions to generate diagnostic requests. Afterwards, the computing unit, as the diagnosis initiating device 10, sends a diagnosis request to the control unit 30. Another possible implementation of S401 includes: the control unit 30 receives the diagnosis request generated and sent by the computing unit.

S402. In response to the diagnosis request, the control unit 30 determines the diagnosis object based on the request content in the diagnosis request.

Among them, the diagnosis object refers to the target component required to be diagnosed or accessed by the diagnosis request.

In this embodiment, after receiving the diagnosis request, the control unit 30 can obtain the target address of the diagnosis request from the request content in the diagnosis request, and determine the diagnosis object targeted by the diagnosis request based on the target address of the diagnosis request. The target address of the diagnosis request includes the storage address and/or component identification where the data requested for the diagnosis request is located.

S403. The control unit 30 returns a response message of the diagnosis request to the diagnosis initiating device 10 according to the diagnosis status of the diagnosis object.

In this embodiment, after determining the diagnosis object, the control unit 30 may execute the diagnosis request by the diagnosis object. When the diagnosis of the diagnosis object is controlled by the control unit 30, the control unit 30 can directly obtain the diagnosis status of the diagnosis object. When the diagnosis of the diagnosis object is controlled by other components, the control unit 30 can listen to the diagnosis request of the diagnosis object. situation, that is, monitoring the diagnosis situation of the diagnosis object, and then the control unit 30 may return a response message of the diagnosis request to the diagnosis initiating device 10 based on the diagnosis situation of the diagnosis object. The response message may include diagnostic data requested by the diagnosis request, such as sensor data, running logs, etc. requested by the diagnosis request. The response message may also be a timer message to inform the diagnosis initiating device 10 to wait for a further period of time.

In the embodiment of the present application, the control unit 30 directly receives the diagnosis request from the diagnosis initiating device 10, determines the diagnosis object based on the request content in the diagnosis request, and returns a response message of the diagnosis request to the diagnosis initiating device 10 based on the diagnosis status of the diagnosis object. . Based on the characteristic that the control unit 30 in the domain controller is responsible for the execution of diagnostic requests, the control unit 30 in the domain controller acts as a route in the diagnostic communication process, without the need for the computing unit in the domain controller to be responsible for message forwarding in the diagnostic communication. It effectively reduces the number of message forwardings in the diagnostic communication process, reduces communication delays, improves communication efficiency, solves the problem of communication resources, and also reduces the software complexity related to diagnostic communication on the computing unit and control unit.

In some embodiments, the domain controller also includes a shared memory between the computing unit and the control unit, and the communication method between the computing unit and the control unit is inter-core communication based on the shared memory between the computing unit and the control unit ( Core to Core Communication, C2CC).

In this embodiment, during inter-core communication, the computing unit and the control unit can store the messages or data to be sent and received from each other in the shared memory, and the other party can read them in the shared memory. specific, control When the unit sends a message or data to the computing unit, the control unit writes the message or data into the shared memory. The computing unit reads the message or data written by the control unit from the shared memory. When the computing unit sends a message or data to the control unit, The computing unit writes messages or data into the shared memory, and the control unit reads the messages or data written by the computing unit from the shared memory.

Therefore, compared with the communication between the computing unit and the control unit through switches and DoIP, inter-core communication does not occupy the bus bandwidth of the switch, control unit and computing unit, and does not need to deal with Ethernet receiving interruptions and sending interruptions, saving communication resources.

Further, when the diagnosis initiating device is a computing unit, the control unit may receive the diagnosis request sent by the computing unit through inter-core communication. Therefore, when the computing unit initiates diagnostic communication, the efficiency of diagnostic communication is improved through inter-core communication and communication resources are saved.

In a possible implementation, the shared memory may also be provided in the computing unit and/or the control unit to implement inter-core communication through the shared memory located in the computing unit and/or the control unit.

Further, when the shared memory is provided in the computing unit and the control unit, the shared memory in the computing unit is communicatively connected with the shared memory in the control unit.

In some embodiments, the diagnostic object may include a domain controller where the control unit is located and/or a CAN ECU that communicates with the control unit via CAN. Therefore, the control unit can not only execute diagnostic requests for the domain controller where the control unit is located, but also serve as a route between the diagnostic initiating device and the CAN ECU, forwarding the diagnostic request to the CAN ECU to achieve diagnosis of the CAN ECU.

The following is an example in which the diagnostic object is a domain controller with reference to Figures 5 to 8:

Figure 5 shows a schematic flowchart 2 of the vehicle diagnostic communication method provided by the embodiment of the present application. As shown in Figure 5, the vehicle diagnostic communication method includes:

S501. The control unit 30 in the domain controller receives the diagnosis request sent by the diagnosis initiating device 10.

Among them, the implementation principles and technical effects of S501 can be referred to the foregoing embodiments and will not be described again.

S502. In response to the diagnosis request, the control unit 30 determines that the diagnosis object is the domain controller based on the request content in the diagnosis request.

In this embodiment, the control unit 30 may obtain the request content from the diagnosis request, for example, the request content It is simply a request to obtain the sensing data of a certain sensor or the fault information of a certain component. After that, the control unit 30 can determine the diagnosis object based on the target address in the request content. In the case where the target address in the request content points to the domain controller where the control unit 30 is located, the control unit 30 may determine that the diagnostic object is the domain controller where the control unit 30 is located.

S503. The control unit 30 performs the diagnosis operation corresponding to the diagnosis request.

In this embodiment, when the diagnosis object is the domain controller where the control unit 30 is located, the control unit 30 processes the diagnosis request as the domain controller, that is, the control unit 30 performs the diagnosis operation corresponding to the diagnosis request. For example, the control unit 30 obtains sensing data of sensors on the domain controller, fault information of components on the domain controller, running logs of software on the domain controller, etc.

S504. The control unit 30 returns a response message of the diagnosis request to the diagnosis initiating device 10 according to the execution status of the diagnosis operation.

In this embodiment, when the diagnostic object is the domain controller where the control unit 30 is located, the control unit 30 executes the diagnostic operation corresponding to the diagnostic request and obtains the execution request of the diagnostic operation, where the execution status of the diagnostic operation may include At least one of the following: the diagnostic operation is not completed, the diagnostic operation is completed, or the diagnostic data obtained by performing the diagnostic operation (such as sensor data, fault information, etc.). After obtaining the execution status of the diagnostic operation, the control unit 30 returns a response message of the diagnostic request to the diagnosis initiating device 10 . The response message carries the execution status of the diagnostic operation, so that the control unit 30 directly feeds back the status of the diagnostic operation to the diagnosis initiating device 10 . Implementation.

In the embodiment of the present application, the control unit 30 in the domain controller receives the diagnosis request sent by the diagnosis initiating device 10. When the diagnosis object is determined to be the domain controller according to the diagnosis request, the control unit 30 performs the diagnosis operation corresponding to the diagnosis request. , and directly feeds back the execution status of the diagnostic operation to the diagnosis initiating device 10 . Compared with the method in which the diagnosis request is forwarded by the computing unit to the control unit 30 and the execution status of the diagnosis operation is forwarded by the computing unit to the diagnosis initiating device 10 , the embodiment of the present application effectively reduces the number of message forwardings during the diagnosis communication process and reduces Communication delay improves communication efficiency.

In the case where the diagnostic object is a domain controller where the control unit is located, the diagnostic request may be related to a computing unit in the domain controller. Therefore, in some embodiments, if the diagnostic request is related to If the computing unit is related, the control unit and the computing unit perform diagnostic operations through inter-core communication. Therefore, through inter-core communication between the control unit and the computing unit, the efficiency of diagnostic communication is improved and the communication resources occupied by diagnostic communication are reduced.

The functions of diagnostic communication can include the following two: for vehicle fault diagnosis and for vehicle data upgrade. Therefore, in this embodiment, the diagnostic request related to the computing unit in the domain controller may include at least one of the following situations: the diagnostic request is used to request to obtain data stored in the computing unit, and the data requested by the diagnostic request needs to go through the computing unit Computed, diagnostic requests are used to request domain controllers for upgrades. Wherein, the diagnostic request used to request the domain controller to upgrade may include requesting the control unit and/or the computing unit to upgrade.

In the case where a diagnostic request is used to request an upgrade of a domain controller, the device status of the domain controller may include the following two types: diagnostic status and upgrade status. In the diagnostic state, the domain controller receives and stores upgrade data from the diagnostic initiating device. In the upgrade state, the domain controller performs upgrades based on the upgrade data from the diagnostic initiating device. Therefore, the control unit can take different operations by determining the device status of the domain controller, which will be described below through embodiments.

Among them, when the domain controller is in the diagnosis state, the control unit and computing unit in the domain controller are also in the diagnosis state. When the domain controller is in the upgrade state, the control unit and computing unit in the domain controller are also in the upgrade state.

Figure 6 shows a schematic flowchart 3 of the vehicle diagnostic communication method provided by this embodiment of the present application. This method is applied to the control unit in the domain controller. In other words, the execution subject of the vehicle diagnostic communication method provided by this embodiment is the control unit. unit. As shown in Figure 6, the vehicle diagnostic communication method includes:

S601. Receive the diagnosis request sent by the diagnosis initiating device.

S602. In response to the diagnosis request, determine that the diagnosis object is the domain controller based on the request content in the diagnosis request.

Among them, the implementation principles and technical effects of S601 and S602 can be referred to the foregoing embodiments, and will not be described again.

S603. Determine whether the diagnostic request instructs the domain controller to upgrade.

In this embodiment, the control unit can determine whether the diagnosis request belongs to an upgrade service request. Determine whether the diagnostic request instructs the domain controller to upgrade. If the control unit determines that the diagnostic request instructs the domain controller to upgrade, S604 is executed; otherwise, S606 is executed.

In a possible implementation, the control unit can determine whether the diagnostic request is a 0×11 request, a 0×34 request, a 0×36 request, a 0×37 request or a 0×38 request, and if so, determine the diagnostic request indication. Domain controller to upgrade, otherwise it was determined that the diagnostic request did not direct the domain controller to upgrade. Among them, 0×11 request, 0×34 request, 0×36 request, 0×37 request or 0×38 request are upgrade service requests in UDS. Therefore, based on these types of upgrade service requests in UDS, the accuracy of determining whether a diagnostic request belongs to an upgrade service request is improved.

S604. Determine whether the domain controller is in a diagnostic state.

In this embodiment, the control unit determines whether the domain controller is in the diagnostic state. If the domain controller is in the diagnostic state, S605 is executed. Otherwise, S606 is executed.

Among them, the execution order of S603 and S604 can be to execute S603 first, or to execute S604 first, or to execute S603 and S604 at the same time, and there is no restriction here.

In one possible implementation, the domain controller can enter diagnostic state by default upon startup. In this way, after the domain controller is started, the diagnostic initiating device can upgrade the domain controller by sending a diagnostic request instructing the domain controller to upgrade.

S605. Send the first upgrade data from the diagnosis initiating device to the computing unit through inter-core communication to assist the computing unit in upgrading.

The first upgrade data may include upgrade data used for upgrading the control unit and/or upgrade data used for upgrading the computing unit. Considering that the control unit is mainly responsible for control and the computing unit is mainly responsible for data processing, the storage capacity of the computing unit is stronger than that of the control unit. Therefore, in the domain controller, the upgrade data can be stored and processed by the computing unit.

In this embodiment, when the control unit determines that the diagnosis request instructs the domain controller to perform an upgrade and the domain controller is in a diagnosis state, the control unit may receive the first upgrade data from the diagnosis initiating device, and then send the first upgrade data to the computing unit. , stored by the computing unit. In the case where the first upgrade data contains upgrade data used for upgrading the computing unit, sending the first upgrade data to the computing unit is beneficial to Assist in upgrading computing units.

S606. Execute the diagnosis operation corresponding to the diagnosis request.

In this embodiment, when the diagnostic request does not instruct the domain controller to upgrade, the control unit itself can perform the diagnostic operation corresponding to the diagnostic request, for example, obtain the sensing data of the sensor, and when the diagnostic request instructs the domain controller to upgrade However, when the domain controller is in an upgrade state (that is, not in a diagnostic state), the control unit can perform an upgrade operation based on the first upgrade data stored in the computing unit. When the diagnostic request instructs the domain controller to upgrade and the domain controller When in the diagnostic state, after transmitting the first upgrade data to the computing unit, the controller can wait for the domain controller to enter the upgrade state, and after the domain controller enters the upgrade state, perform an upgrade operation based on the first upgrade data.

S607. Return a response message of the diagnosis request to the diagnosis initiating device according to the execution status of the diagnosis operation.

Among them, the implementation principles and technical effects of S607 can be referred to the foregoing embodiments and will not be described again.

In the embodiment of the present application, when the diagnostic object is a domain controller, the domain controller is in a diagnostic state, and the diagnostic request is used to instruct the domain controller to upgrade, the control unit sends the first upgrade data to the computing unit through inter-core communication. , thus, through the inter-core communication between the control unit and the computing unit, and using the control unit as the route in the upgrade process, diagnostic communication for upgrading the domain controller is realized, which improves the communication efficiency of diagnostic communication and saves communication resources. .

In some embodiments, FIG. 7 shows a schematic flowchart of diagnostic communication when the diagnostic object is a domain controller, the domain controller is in a diagnostic state, and the diagnostic communication is used to instruct the domain controller to upgrade. As shown in Figure 7, the diagnostic communication process may include:

S701. The diagnosis initiating device 10 sends a diagnosis request to the control unit 30. The diagnosis request is used to instruct the domain controller to upgrade.

S702. The control unit 30 returns a diagnosis response to the diagnosis initiating device 10. The diagnosis response is used to indicate to the diagnosis initiating device 10 that the control unit 30 has received the diagnosis request.

In this embodiment, when the control unit 30 determines that the diagnosis object is a domain controller according to the diagnosis request and the diagnosis request is used to instruct the domain controller to upgrade, the control unit 30 may return the diagnosis to the diagnosis initiating device 10 Response to inform the diagnostic initiating device that the control unit has received the diagnostic request.

S703. The diagnosis initiating device 10 sends a first message to the control unit 30 in response to the diagnosis response. The first message is used to indicate the start of data transmission to the control unit 30.

In this embodiment, after receiving the diagnosis response, the diagnosis initiating device 10 may send a first message to the control unit 30 in response to the diagnosis response. The first message is used to inform the control unit 30 of the start of data transmission. The first message may also be used to request the data transmission requirements of the control unit 30. The data transmission requirements of the control unit 30 may include the format that the control unit 30 can receive and parse, and the control unit 30 performs data transmission through inter-core communication. The data transfer rate that the transmission can accept.

S704. In response to the first message, the control unit 30 sends a second message to the computing unit 20. The second message is used to indicate the start of data transmission to the computing unit 20.

In this embodiment, since the upgrade data needs to be transmitted to the computing unit 20 for storage, after receiving the first message, the control unit 30 can send a second message to the computing unit 20 to inform the computing unit 20 of the data through the second message. The transmission begins so that the computing unit 20 is ready to receive the data. The second message can also be used to request the data transmission requirements of the computing unit 20. The data transmission requirements of the computing unit 20 may include the format that the data that the computing unit 20 can receive and parse must meet, and the computing unit 20 performs data transmission through inter-core communication. The data transfer rate that the transmission can accept.

S705. In response to the second message, the computing unit 20 returns a response message of the second message to the control unit 30. The response message of the second message is used to indicate that the computing unit 30 has received the second message and to indicate the data transmission requirement of the computing unit 30.

S706. In response to the response message of the second message returned by the computing unit 20, the control unit 30 sends a response message of the first message to the diagnosis initiating device 10. The response message of the first message is used to indicate that the control unit 30 has received the first message and Indicates the data transmission requirements of the control unit 30.

S707. In response to the response message of the first message, the diagnosis initiating device 10 sends a third message to the control unit 30, where the third message carries the first upgrade data.

In this embodiment, after receiving the response message of the first message, the diagnosis initiating device 10 can transmit the upgrade data, and therefore sends the third message to the control unit 30, carrying the First upgrade data. For the first upgrade data, reference may be made to the foregoing embodiments, which will not be described again.

S708. In response to the third message, the control unit 30 sends a fourth message to the computing unit 20, where the fourth message carries the first upgrade data.

In this embodiment, after receiving the third message, the control unit 30 can obtain the first upgrade file from the third message, generate a fourth message carrying the first upgrade data based on inter-core communication, and convert the fourth message to Sent to the computing unit through inter-core communication.

S709. After receiving the fourth message, the computing unit 20 returns a response message to the fourth message to the control unit 30. The response message to the fourth message is used to indicate to the control unit 30 that the first upgrade data transmission is completed.

S710. In response to the response message of the fourth message returned by the computing unit 20, the control unit 30 sends a response message of the third message to the diagnosis initiating device 10. The response message of the third message is used to indicate the first upgrade data to the diagnosis initiating device 10. Transfer completed.

In this embodiment, after receiving the fourth message, the computing unit 20 may obtain the first upgrade data from the fourth message and store the first upgrade data. At the same time, the computing unit 20 may return a response message of the fourth message to the control unit 30 to indicate to the control unit 30 that the computing unit 20 has received the first upgrade data. In response to the response message of the fourth message, the control unit 30 returns the response message of the third message to the diagnosis initiating device 10 to indicate to the diagnosis initiating device 10 that the transmission of the first upgrade data between the diagnosis initiating device 10 and the domain controller has been completed. , that is, the first upgrade data transmission is successful.

In some embodiments, as shown in Figure 7, after S710, the vehicle diagnosis communication method also includes: S711. The diagnosis initiating device 10 sends a data verification message to the control unit 30 to request the domain controller to verify the received first The upgrade data is verified. S712. In response to the data verification message from the diagnosis initiating device 10, the control unit 30 sends a data verification message to the computing unit 20 to request the computing unit 20 to verify the first upgrade data. S713. The computing unit 20 responds to the data verification message sent by the control unit 30 and returns a data verification response to the control unit 30 to indicate the data verification result to the control unit 30. S714. The control unit 20 responds to the data verification response of the computing unit. , sending a data verification response to the diagnosis initiating device 10 to indicate the data verification result to the diagnosis initiating device 10 . Therefore, after completing the transmission of the upgrade data, the upgrade data is verified to improve the accuracy and reliability of the upgrade data. Improves the success rate of domain controller upgrades through diagnostic communication.

The data verification result may be data verification success or failure.

Among them, the diagnosis response, the response message of the first message, the response message of the third message, and the data verification response returned by the control unit 30 to the diagnosis initiating device 10 all belong to the response messages of the diagnosis request.

In the embodiment of the present application, when the domain controller is in a diagnostic state and the diagnostic request instructs the domain controller to upgrade, the control unit 30 in the domain controller is used as a route to send the diagnosis initiating device 10 through inter-core communication. Messages indicating the start of data transmission, messages carrying upgrade data, and messages indicating data verification are forwarded to the computing unit 20, and messages indicating data transmission requirements, messages indicating data transmission completion, and instructions returned by the computing unit 20 are received through inter-core communication. Messages of data verification results are forwarded to the diagnosis initiating device 10 . In this way, the advantages of the control unit 30 and the computing unit 20 are fully utilized, and inter-core communication is utilized to improve communication efficiency and reduce communication resource occupation.

In some embodiments, when the control unit determines that the diagnostic request indicates that the domain controller is upgraded and the domain controller is in the upgrade state, the computing unit may send the second upgrade data to the computing unit through inter-core communication, and the control unit may 2. Upgrade data to upgrade.

The second upgrade data is upgrade data used for upgrading the control unit.

In this embodiment, when the first upgrade data contains the second upgrade data for the control unit upgrade, the computing unit can send the second upgrade data to the control unit through inter-core communication, and the control unit receives After the second upgrade data, the firmware or software in the control unit can be upgraded according to the second upgrade data. In the case where the first upgrade data also includes third upgrade data for upgrading the computing unit, the computing unit may upgrade the firmware or software in the computing unit according to the third upgrade data. In this way, the domain controller is upgraded.

In a possible implementation, the computing unit can also obtain upgrade data for domain controller upgrade through Over-the-Air Technology (OTA). In the case where the upgrade data includes the second upgrade data, the computing unit may send the second upgrade data to the control unit through inter-core communication. Thus, the flexibility of upgrade data acquisition is improved.

In one possible implementation, the domain controller enters the Upgrade status. Wherein, the upgrade triggering condition may include at least one of the following: the first upgrade data transmission from the diagnosis initiating device is completed, and/or the control unit receives a fifth message from the diagnosis initiating device, and the fifth message instructs the control unit to enter the upgrade state, The control unit receives a sixth message from the computing unit, and the sixth message instructs the control unit to enter an upgrade state.

In this implementation, the domain controller can enter the upgrade state when the first upgrade data transmission is completed, so as to perform the upgrade in time after the upgrade data transmission is completed, and/or the control unit can control the control after receiving the instruction from the diagnosis initiating device. In the case of the fifth message that the unit enters the upgrade state, the control domain controller enters the upgrade state, so that the diagnosis initiating device can actively trigger the domain controller to enter the upgrade state, and/or, the control unit can receive an instruction from the computing unit to enter the upgrade state. In the case of the sixth message of the upgrade state, the domain controller is controlled to enter the upgrade state, so that the computing unit can also actively trigger the domain controller to enter the upgrade state.

In an example, the fifth message may be a restart message or a reset message. Among them, the restart message instructs the domain controller to restart, and the reset message instructs the domain controller to reset. After receiving the fifth message, the control unit can control the domain controller to restart or reset. The diagnosis initiating device may send a fifth message to the control unit after the first upgrade data transmission is completed, so that the domain controller can upgrade in time.

In one example, after receiving the upgrade data for upgrading the domain controller through OTA, the computing unit can send a sixth message to the control unit, so that the domain controller can perform the upgrade in time after receiving the upgrade data, thereby improving domain performance through diagnostic communication. Upgrade efficiency of controller upgrades.

In some embodiments, FIG. 8 shows a schematic flowchart of diagnostic communication when the diagnostic object is a domain controller, the domain controller is in a diagnostic state, and the diagnostic communication is used to instruct the domain controller to upgrade. As shown in Figure 8, the diagnostic communication process may include:

S801. The control unit 30 receives the fifth message sent by the diagnosis initiating device 10.

S802. In response to the fifth message, the control unit 30 returns a response message of the fifth message to the diagnosis initiating device 10. The response message of the fifth message is used to indicate that the control unit 30 has received the fifth message.

For the fifth message, reference may be made to the foregoing embodiments, which will not be described again.

S803. In response to the fifth message, the control unit 30 sends the seventh message to the computing unit 20. The seventh message The message is used to indicate that the computing unit 20 is ready to enter the upgrade state.

S804. In response to the seventh message, the computing unit 20 returns a response message of the seventh message to the control unit 30. The response message of the seventh message is used to indicate that the computing unit 20 has received the seventh message.

In this embodiment, after the control unit 30 receives the seventh message, both the control unit 30 and the computing unit 20 enter the upgrade state, that is, the domain controller enters the upgrade state.

S805. The computing unit 20 sends the eighth message to the control unit 30. The eighth message is used to indicate the start of data transmission to the control unit 30.

In this embodiment, after entering the upgrade state, since the upgrade data is stored in the computing unit 20 , the computing unit 20 can, when the stored upgrade data includes the second upgrade data for upgrading the control unit 30 , through the inter-core Communication, sending an eighth message to the control unit 30 to inform the control unit 30 of the start of data transmission, that is, preparation for transmission of upgrade data.

The eighth message may also be used to request data transmission requirements from the control unit 30 so that the computing unit 20 sends upgrade data to the control unit 30 according to the data transmission requirements. The data transmission requirements may refer to the previous embodiments and will not be described again.

S806. In response to the eighth message, the control unit 30 returns a response message of the eighth message to the computing unit 20, so as to inform the computing unit 20 of the data transmission requirement of the control unit 30.

In this embodiment, after receiving the eighth message, the control unit 30 may return a response message of the eighth message to the computing unit 20 through inter-core communication. The response message of the eighth message carries the data transmission request of the control unit 30 .

S807. In response to the response message of the eighth message, the computing unit 20 sends a ninth message to the control unit 30, where the ninth message carries the second upgrade data.

In this embodiment, after receiving the response message of the eighth message, the computing unit 20 can obtain the second upgrade data from the stored upgrade data (such as the first upgrade data), and generate the ninth message carrying the second upgrade data, And the ninth message is sent to the control unit 30 through inter-core communication.

S808. In response to the ninth message, the control unit 30 sends a response message of the ninth message to the computing unit 20 to inform the computing unit 20 that the second upgrade data transmission is completed.

S809, the control unit 30 and the computing unit 20 are upgraded respectively.

In this embodiment, after receiving the second upgrade data, the control unit 30 can upgrade according to the second upgrade data, and the computing unit 20 can upgrade according to the third upgrade data used for upgrading the computing unit 20 . In this way, the upgrade of the domain controller is completed.

In a possible implementation, after receiving the response message of the ninth message, the computing unit 20 may send a data verification message to the control unit 30 in response to the response message of the ninth message. The control unit 30 responds to the data verification message. Verify message, verify the received second upgrade data, and send a data verification response to the computing unit 20 according to the verification result. Therefore, through data verification, the accuracy and reliability of upgrade data transmission between the computing unit 20 and the control unit 30 in the upgrade state are improved.

In a possible implementation, after the control unit 30 is upgraded, the control unit 30 may send an upgrade status query message to the computing unit 20 to query whether the computing unit 20 has completed the upgrade. The computing unit 20 may send a query message to the computing unit 20 according to its own upgrade status. The control unit 30 returns the upgrade status response message to inform the control unit 30 whether the computing unit 20 completes the upgrade through the upgrade status response message.

In a possible implementation, after receiving the upgrade status response message from the computing unit 20, if the control unit 30 determines that the upgrade of the computing unit 20 is completed according to the upgrade status response message, it may send a shutdown command to the computing unit 20 to indicate The computing unit 20 is shut down. After receiving the shutdown command, the computing unit 20 returns a shutdown response to the control unit 30 if it determines that shutdown is currently allowed. Therefore, after the upgrade is completed, the control unit 30 and the computing unit 20 are automatically shut down to ensure that the upgraded control unit 30 and the computing unit 20 can run according to the upgraded firmware and/or software after restarting.

Based on the foregoing embodiments, in the process of inter-core communication between the control unit and the computing unit, in some embodiments, the data structure used in the communication message includes a command data structure and a diagnostic data structure. Among them, the command data structure includes at least one of the following fields: command field, response field, error feedback field, command data length field, command data address field, and the diagnosis data structure includes at least one of the following fields: target node field, diagnosis data length field, diagnosis Data address field. In the case of command transmission between the control unit and the computing unit, the command data structure can be used. In the case of data (especially upgrade data) transmission between the control unit and the computing unit, the diagnostic data structure can be used to Improve data transmission efficiency in inter-core communication.

In this embodiment, in the command data structure: 1) The command field carries a command type value, and the command type value reflects the execution operation corresponding to the command message. For example, in the command message sent by the control unit to the computing unit, the command field carries When the command type value is 1, it means that the control unit instructs the computing unit to start. When the command type value carried in the command field is 2, it means that the control unit instructs the computing unit to reset. 2) The response field carries a response type value, and the response type value reflects the response message. The response content passed, for example, in the response message sent by the computing unit to the control unit, when the response type value carried in the response field is 1, it means that the computing unit is executing the execution operation indicated by the command message, and the command type carried in the command field When the value is 2, it means that the computing unit has completed the execution operation indicated in the command message. 3) The error code field carries an error type value. The error type value feeds back the error that occurred when the control unit or computing unit executed the execution operation in the command message. Error, 4) The command data length field carries the data length of the data address. The data address refers to the storage address of the relevant data in the command message or response message. 5) The command data address field carries the relevant data in the command message or response message. Storage address. Thus, the control unit and the computing unit can communicate clearly and accurately between cores based on the command data structure.

In this embodiment, in the diagnostic data structure: 1) The target node field carries the identification of the target node. The target node refers to the object conveyed by the message. For example, if the control unit sends the message to the computing unit, the computing unit is the target node. , 2) The diagnostic data length field carries the data length of the storage address where the diagnostic data is located, 3) The diagnostic data address field carries the storage address where the diagnostic data is located. Therefore, in inter-core communication, based on the diagnostic data structure, the control unit and the computing unit can store data in the shared memory, and can also accurately know where the other party stores the data in the shared memory, improving the accuracy of inter-core communication.

The following is an example in which the diagnostic object is CAN ECU in conjunction with Figure 9:

Figure 9 shows a schematic flowchart 4 of the vehicle diagnostic communication method provided by the embodiment of the present application. As shown in Figure 9, the vehicle diagnostic communication method includes:

S901. The control unit 30 in the domain controller receives the diagnosis request sent by the diagnosis initiating device 10.

The implementation principles and technical effects of S901 may be referred to the foregoing embodiments and will not be described again.

S902. The control unit 30 responds to the diagnosis request and determines that the diagnosis object is the CAN ECU 60 based on the request content in the diagnosis request.

In this embodiment, the control unit 30 can obtain the request content from the diagnosis request. For example, the request content is a request to obtain sensing data of a certain sensor or a request to obtain fault information of a certain component. After that, the control unit 30 can obtain the request content based on the request. The target address in the content determines the diagnostic object. In the case where the target address in the request content points to the CAN ECU 60 connected to the control unit 30 through CAN, the control unit 30 may determine that the diagnostic object is the CAN ECU 60.

S903. The control unit 30 sends a diagnosis request to the CAN ECU 60.

In this embodiment, when the control unit 30 determines that the diagnosis object is the CAN ECU 60, it can forward the diagnosis request to the CAN ECU 60 through the diagnosis routing module located in the control unit 30.

Specifically, the control unit 30 can convert the diagnostic request from an Ethernet message (such as a DoIP message) to a diagnostic (Diagnostic over Controller Area Network, DoCAN) message on the control local area network through the diagnostic routing module, and convert the converted The diagnostic request is sent to CAN ECU 60.

S904. The control unit 30 returns a response message of the diagnosis request to the diagnosis initiating device 10 according to the diagnosis situation of the CAN ECU 60.

In an example, the control unit 30 may send a response message of the diagnosis request to the diagnosis initiating device 10 after receiving the response message returned by the CAN ECU 60. Among them, after receiving the diagnostic request, the CAN ECU 60 can send a response message to the control unit 30 through CAN, and the control unit 30 can convert the response message from the CAN ECU 60 from the DoCAN message to the Ethernet message through the diagnostic routing module. , and then send the converted response message to the diagnosis initiating device 10 .

In another example, the control unit 30 may send a response message of the diagnosis request to the diagnosis initiating device 10 to inform the diagnosis initiating device 10 to wait if the response message returned by the CAN ECU 60 is not received for a period exceeding the preset market. for a period of time, or inform the diagnosis initiating device 10 to diagnose communication abnormalities.

In the embodiment of the present application, when the diagnosis object is the CAN ECU 60 that communicates with the control unit 30 through CAN, the control unit 30 acts as a route between the CAN ECU 60 and the diagnosis initiating device 10. The diagnosis request from the diagnosis initiating device 10 is forwarded to the CAN ECU 60 , and a response message to the diagnosis request can also be returned to the diagnosis initiating device 10 based on the diagnosis status of the CAN ECU 60 . Compared with the situation where the computing unit acts as a router, the embodiments of the present application effectively reduce the number of message forwardings in diagnostic communication, reduce the delay of diagnostic communication, and improve the efficiency of diagnostic communication.

FIG. 10 shows a schematic diagram of the software architecture for diagnostic communication between the control unit 30 and the computing unit 20 in the domain controller provided by the embodiment of the present application. As shown in FIG. 10 , shared memories are provided in the control unit 30 and the computing unit 20 respectively. In this example, the control unit 30 includes the shared memory 35 and the computing unit 20 includes the shared memory 24 .

As shown in FIG. 10 , during the diagnostic communication process, the external diagnostic instrument 10 can send a diagnostic request to the control unit 30 through the switch 50 . After the multiple protocol layers 31 in the control unit 30 receive the diagnostic request, the routing module 32 determines The diagnostic object for this diagnostic request. If the diagnostic object is the domain controller where the control unit 30 is located, the diagnostic operation can be performed by the microcontroller 33 in the control unit 30 , otherwise, a diagnostic request can be sent to other ECUs 40 through the CAN communication link 34 . During the process of performing a diagnostic operation, the microcontroller 33 can communicate with the shared memory 35 in the computing unit 20 via the routing module 32 and the shared memory 35 in the control unit 30 to realize inter-core communication between the control unit 30 and the computing unit 20 . In addition, as shown in Figure 10, the computing unit 20 is also provided with the following structures: Run-Time Environment (RTE) 25 and Over-the-Air Technology (OTA), which can be upgraded through OTA download data. The control unit 30 is also provided with the following structures: RTE 36 and application layer 37, which can perform corresponding operations in response to the requirements of the application layer.

Figure 11 shows a schematic structural diagram 1 of a vehicle diagnostic communication device provided by an embodiment of the present application. As shown in Figure 11, on the control unit side in the domain controller of the vehicle, the vehicle diagnostic communication device includes:

The receiving module 1101 is configured to receive a diagnosis request sent by a diagnosis initiating device.

The determination module 1102 is configured to respond to the diagnosis request and determine the diagnosis object based on the request content in the diagnosis request, where the diagnosis object includes the target component required to be diagnosed or accessed by the diagnosis request.

The processing module 1103 is configured to return a response message of the diagnosis request to the diagnosis initiating device according to the diagnosis status of the diagnosis object.

In some embodiments, the diagnosis object includes a domain controller. In the process of returning a response message to the diagnosis request to the diagnosis initiating device according to the diagnosis situation of the diagnosis object, the processing module 1103 is specifically configured to: perform a diagnosis operation corresponding to the diagnosis request. , according to the execution status of the diagnostic operation, return a response message of the diagnostic request to the diagnostic initiating device.

In some embodiments, the domain controller further includes a shared memory between the computing unit and the control unit, and the communication method between the computing unit and the control unit includes inter-core communication based on the shared memory between the computing unit and the control unit. In the process of executing the diagnostic operation corresponding to the diagnostic request, the processing module 1103 is specifically configured to: when the diagnostic request is related to the computing unit in the domain controller, perform the diagnostic operation through inter-core communication with the computing unit.

In some embodiments, the diagnostic request is related to the computing unit, including at least one of the following situations: the diagnostic request is used to request to obtain data stored in the computing unit, the data requested by the diagnostic request is obtained by the computing unit, and the diagnostic request is used to request The domain controller performs an upgrade, wherein the diagnostic request for requesting the domain controller for upgrade may include requesting a control unit and/or computing unit upgrade.

In some embodiments, when the diagnostic request is related to a computing unit in a domain controller, during the process of performing a diagnostic operation by performing inter-core communication with the computing unit, the processing module 1103 is specifically configured to: determine the diagnostic request indication domain The controller performs an upgrade, determines that the domain controller is in a diagnosis state, and sends the first upgrade data from the diagnosis initiating device to the computing unit through inter-core communication to assist the computing unit in upgrading.

In some embodiments, in the process of sending the first upgrade data from the diagnosis initiating device to the computing unit through inter-core communication to assist the computing unit in upgrading, the processing module 1103 is specifically configured to: include: receiving the diagnosis initiating device The first message is sent, the first message is used to indicate the start of data transmission to the control unit, in response to the first message, the second message is sent to the computing unit, the second message is used to indicate the start of data transmission to the computing unit, in response to the computing unit Return the response message of the second message, send the response message of the first message to the diagnosis initiating device, receive the third message sent by the diagnosis initiating device, the third message carries the first upgrade data, and respond to the third message to the computing device. The unit sends a fourth message, the fourth message carries the first upgrade data, and responds to the response message of the fourth message returned by the computing unit. message, sending a response message of the third message to the diagnosis initiating device, where the response message of the fourth message and the response message of the third message are used to indicate that the first upgrade data transmission is completed.

In some embodiments, when the diagnostic request is related to a computing unit in a domain controller, during the process of performing a diagnostic operation by performing inter-core communication with the computing unit, the processing module 1103 is specifically configured to: determine the diagnostic request indication domain The controller performs an upgrade, determines that the domain controller is in an upgrade state, receives the second upgrade data sent by the computing unit through inter-core communication, and performs the upgrade based on the second upgrade data.

In some embodiments, the domain controller enters the upgrade state when the upgrade trigger condition is met. The upgrade trigger condition includes at least one of the following: completion of the first upgrade data transmission, and/or receipt of the fifth step of the diagnosis initiating device. message, the fifth message indicates that the control unit enters the upgrade state, and/or a sixth message from the computing unit is received, the sixth message indicates that the control unit enters the upgrade state.

In some embodiments, during the process of determining that the domain controller is in the upgrade state, the processing module 1103 is specifically configured to: receive the fifth message sent by the diagnosis initiating device, and in response to the fifth message, return the fifth message to the diagnosis initiating device. response message, the response message of the fifth message indicates the start of the upgrade of the control unit, in response to the fifth message, send a seventh message to the computing unit, the seventh message instructs the computing unit to enter the upgrade state, and receive the response message of the seventh message returned by the computing unit , the response message of the seventh message indicates the start of the computing unit upgrade.

In some embodiments, during the process of receiving the second upgrade data sent by the computing unit through inter-core communication, the processing module 1103 is specifically configured to: receive an eighth message sent by the computing unit, and the eighth message indicates data transmission to the control unit. Start, in response to the eighth message, return the response message of the eighth message to the computing unit to inform the computing unit of the data transmission requirements of the control unit, and receive the ninth message sent by the computing unit, the ninth message carrying the second upgrade data , in response to the ninth message, sending a response message to the ninth message to the computing unit to inform the computing unit that the second upgrade data transmission is completed.

In some embodiments, in the inter-core communication between the control unit and the computing unit, the data structure used in the communication message includes a command data structure and a diagnostic data structure, wherein the command data structure includes at least one of the following fields: command field, response field, error feedback field, command data length field, command data address field, where the diagnostic data structure includes at least one of the following fields: target node word segment, diagnostic data length field, diagnostic data address field.

In some embodiments, the diagnosis object includes a CAN ECU that communicates with the control unit through the controller area network CAN. In the process of returning a response message of the diagnosis request to the diagnosis initiating device according to the diagnosis situation of the diagnosis object, the processing module 1103 specifically uses In: Send a diagnosis request to the CAN ECU, obtain the diagnosis status of the CAN ECU, and return a diagnosis response to the diagnosis initiating device according to the diagnosis status of the CAN ECU.

In some embodiments, the diagnosis initiating device includes at least one of the following: an external device, an ECU with networking capabilities in the vehicle, and a computing unit in the domain controller. When the diagnosis initiating device is a computing unit, the control unit receives the diagnosis initiation. In the process of a diagnosis request sent by the device, the receiving module 1101 is specifically configured to: receive a request sent by the computing unit through inter-core communication.

The vehicle diagnostic communication device provided by the embodiment of the present application can perform various steps implemented by the control unit in the above method embodiment. To avoid duplication, they will not be described again here.

Figure 12 shows the second structural diagram of the vehicle diagnostic communication device provided by the embodiment of the present application. It is applied to the computing unit in the domain controller of the vehicle. The communication method between the control unit and the computing unit in the domain controller is based on the control unit and Inter-core communication enabled by shared memory between computing units. As shown in Figure 12, on the side of the computing unit in the domain controller of the vehicle, the vehicle diagnostic communication device includes:

The receiving module 1201 is configured to receive the first upgrade data sent by the control unit through inter-core communication when the domain controller is in a diagnostic state, and/or,

The sending module 1202 is configured to send the second upgrade data to the control unit through inter-core communication when the domain controller is in an upgrade state.

The vehicle diagnostic communication device provided by the embodiment of the present application can perform various steps implemented by the computing unit in the above method embodiment. To avoid duplication, they will not be described again here.

Embodiments of the present application also provide a chip. The chip includes a control unit and/or a computing unit. The control unit is used to perform the steps performed by the control unit in any of the foregoing embodiments. The computing unit is used to perform the calculations in any of the foregoing embodiments. The steps executed by the unit will not be described again here.

Figure 13 shows a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application. As shown in Figure 13 As shown, electronic equipment includes:

Processor 1301 and memory 1302 storing computer program instructions.

Specifically, the above-mentioned processor 1301 may include a central processing unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits according to the embodiments of the present application.

Memory 1302 may include bulk storage for data or instructions. By way of example, and not limitation, the memory 1302 may include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a Universal Serial Bus (USB) drive or two or more A combination of many of the above. Storage 1302 may include removable or non-removable (or fixed) media, where appropriate. Where appropriate, the memory 1302 may be internal or external to the integrated gateway disaster recovery device. In certain embodiments, memory 1302 is non-volatile solid-state memory.

In particular embodiments, memory 1302 may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical/tangible memory storage devices . Thus, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or multiple processors) operable to perform the operations described with reference to a method according to an aspect of the present disclosure.

The processor 1301 reads and executes the computer program instructions stored in the memory 1302 to implement any of the vehicle diagnostic communication methods in the above embodiments.

In one example, the electronic device may also include a communication interface 1303 and a bus 1310. Among them, as shown in Figure 13, the processor 1301, the memory 1302, and the communication interface 1303 are connected through the bus 1310 and complete communication with each other.

The communication interface 1303 is mainly used to implement communication between modules, devices, units and/or equipment in the embodiments of this application.

Bus 1310 includes hardware, software, or both, coupling components of the vehicle diagnostic communication device to each other together. By way of example, and not limitation, the bus may include Accelerated Graphics Port (AGP) or other graphics bus, Enhanced Industry Standard Architecture (EISA) bus, Front Side Bus (FSB), HyperTransport (HT) interconnect, Industry Standard Architecture (ISA) Bus, Infinite Bandwidth Interconnect, Low Pin Count (LPC) Bus, Memory Bus, Micro Channel Architecture (MCA) Bus, Peripheral Component Interconnect (PCI) Bus, PCI-Express (PCI-X) Bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association Local (VLB) bus or other suitable bus or a combination of two or more of these. Where appropriate, bus 1310 may include one or more buses. Although the embodiments of this application describe and illustrate a specific bus, this application contemplates any suitable bus or interconnection.

The electronic device can execute the vehicle diagnostic communication method in the embodiment of the present application based on the sensing data, thereby realizing the vehicle diagnostic communication method and device described in conjunction with FIGS. 1 to 9 .

In addition, combined with the vehicle diagnostic communication method in the above embodiments, embodiments of the present application may provide a computer storage medium for implementation. Computer program instructions are stored on the computer storage medium. When the computer program instructions are executed by the processor, any one of the vehicle diagnostic communication methods in the above embodiments is implemented.

To be clear, this application is not limited to the specific configurations and processes described above and illustrated in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications and additions, or change the order between steps after understanding the spirit of the present application.

The functional blocks shown in the above structural block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, or the like. When implemented in software, elements of the application are programs or code segments that are used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted over a transmission medium or communications link via a data signal carried in a carrier wave. "Machine-readable medium" may include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, and the like. Code snippets can Downloaded via computer networks such as the Internet, Intranet, etc.

It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above steps. That is to say, the steps may be performed in the order mentioned in the embodiment, or may be different from the order in the embodiment, or several steps may be performed simultaneously.

Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that execution of the instructions via the processor of the computer or other programmable data processing apparatus enables Implementation of the functions/actions specified in one or more blocks of a flowchart and/or block diagram. Such a processor may be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It will also be understood that each block in the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can also be implemented by special purpose hardware that performs the specified functions or actions, or can be implemented by special purpose hardware and A combination of computer instructions.

The above are only specific implementations of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the above-described systems, modules and units can be referred to the foregoing method embodiments. The corresponding process will not be described again here. It should be understood that the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of various equivalent modifications or substitutions within the technical scope disclosed in the present application, and these modifications or substitutions should be covered. within the protection scope of this application.

Claims

A vehicle diagnostic communication method, applied to the control unit 30 in the domain controller of the vehicle, the vehicle diagnostic communication method includes:

S401. Receive the diagnosis request sent by the diagnosis initiating device 10,

S402. In response to the diagnosis request, determine a diagnosis object based on the request content in the diagnosis request, where the diagnosis object includes the target component required to be diagnosed or accessed by the diagnosis request,

S403. Return a response message of the diagnosis request to the diagnosis initiating device 10 according to the diagnosis situation of the diagnosis object.
The vehicle diagnosis communication method according to claim 1, wherein the diagnosis object includes the domain controller, and the response to the diagnosis request is returned to the diagnosis initiating device 10 according to the diagnosis situation of the diagnosis object. Messages, including:

perform a diagnostic operation corresponding to the diagnostic request,

According to the execution status of the diagnosis operation, a response message of the diagnosis request is returned to the diagnosis initiating device 10 .
The vehicle diagnostic communication method according to claim 2, wherein the domain controller further includes a shared memory between the computing unit 20 and the control unit 30, and the computing unit 20 and the control unit 30 The communication method includes inter-core communication based on the shared memory between the computing unit 20 and the control unit 30,

The execution of diagnostic operations corresponding to the diagnostic request includes:

In case the diagnostic request is related to the computing unit 20, the diagnostic operation is performed through inter-core communication with the computing unit 20.
The vehicle diagnostic communication method according to claim 3, wherein the diagnostic request is related to the computing unit 20, including at least one of the following situations:

The diagnosis request is used to request to obtain data stored in the computing unit 20,

The data requested by the diagnosis request are calculated by the calculation unit 20,

The diagnostic request is used to request the domain controller to perform an upgrade, wherein the diagnostic request is used to Requesting the domain controller for an upgrade may include requesting an upgrade of the control unit 30 and/or the computing unit 20 .
The vehicle diagnostic communication method according to claim 3 or 4, wherein in the case where the diagnostic request is related to the computing unit 20, the diagnosis is performed by performing inter-core communication with the computing unit 20 Operations, including:

determining that the diagnostic request instructs the domain controller to perform an upgrade,

Determine that the domain controller in question is in a diagnostic state,

Through inter-core communication, the first upgrade data from the diagnosis initiating device 10 is sent to the computing unit 20 to assist the computing unit 20 in upgrading.
The vehicle diagnostic communication method according to claim 5, wherein the first upgrade data from the diagnosis initiating device 10 is sent to the computing unit 20 through inter-core communication to assist the computing unit 20 in performing Upgrades include:

receiving a first message sent by the diagnosis initiating device 10, the first message being used to indicate the start of data transmission to the control unit 30,

In response to the first message, sending a second message to the computing unit 20, the second message being used to indicate the start of data transmission to the computing unit 20,

In response to the response message of the second message returned by the computing unit 20, sending the response message of the first message to the diagnosis initiating device 10,

receiving a third message sent by the diagnosis initiating device 10, where the third message carries the first upgrade data,

In response to the third message, sending a fourth message to the computing unit 20, the fourth message carrying the first upgrade data,

In response to the response message of the fourth message returned by the computing unit 20, sending the response message of the third message to the diagnosis initiating device 10, the response message of the fourth message and the response message of the third message. The response message is used to indicate that the first upgrade data transmission is completed.
The vehicle diagnostic communication method according to claim 3, wherein in the case where the diagnostic request is related to the computing unit 20 in the domain controller, by communicating with the computing unit 20 Perform inter-core communication and perform the diagnostic operations, including:

determining that the diagnostic request instructs the domain controller to perform an upgrade,

Determine that the domain controller in question is in an upgraded state,

receiving the second upgrade data sent by the computing unit 20 through inter-core communication,

Upgrade is performed according to the second upgrade data.
The vehicle diagnostic communication method according to claim 7, wherein the domain controller enters the upgrade state when an upgrade trigger condition is met,

The upgrade triggering conditions include at least one of the following:

The first upgrade data transfer is completed,

and/or, receiving the fifth message from the diagnosis initiating device 10, the fifth message instructing the control unit 30 to enter the upgrade state,

And/or, a sixth message from the computing unit 20 is received, the sixth message instructs the control unit 30 to enter the upgrade state.
The vehicle diagnostic communication method according to claim 7 or 8, wherein determining that the domain controller is in an upgrade state includes:

receiving the fifth message sent by the diagnosis initiating device 10,

In response to the fifth message, returning a response message of the fifth message to the diagnosis initiating device 10,

In response to the fifth message, sending a seventh message to the computing unit 20, the seventh message being used to indicate that the computing unit 20 is ready to enter the upgrade state,

The response message of the seventh message returned by the computing unit 20 is received.
The vehicle diagnostic communication method according to any one of claims 7-9, wherein receiving the second upgrade data sent by the computing unit 20 through inter-core communication includes:

receiving an eighth message sent by the computing unit 20, the eighth message being used to indicate the start of data transmission to the control unit 30,

In response to the eighth message, a response message of the eighth message is returned to the computing unit 20 to inform the computing unit 20 of the data transmission requirement of the control unit 30,

receiving the ninth message sent by the computing unit 20, the ninth message carrying the second upgrade data,

In response to the ninth message, a response message of the ninth message is sent to the computing unit 20 to inform the computing unit 20 that the second upgrade data transmission is completed.
The vehicle diagnostic communication method according to any one of claims 3-10, wherein in the inter-core communication between the control unit 30 and the computing unit 20, the data structure used in the communication message includes a command data structure and diagnostic data structure,

Wherein, the command data structure includes at least one of the following fields: command field, response field, error feedback field, command data length field, and command data address field,

Wherein, the diagnostic data structure includes at least one of the following fields: a target node field, a diagnostic data length field, and a diagnostic data address field.
The vehicle diagnosis communication method according to any one of claims 1 to 10, wherein the diagnosis object includes a CANECU communicating with the control unit 30 through a controller area network CAN, and the diagnosis according to the diagnosis object In this case, a response message of the diagnosis request is returned to the diagnosis initiating device 10, including:

sending said diagnostic request to said CAN ECU,

Get the diagnostic status of the CAN ECU,

According to the diagnosis situation of the CAN ECU, the diagnosis response is returned to the diagnosis initiating device 10.
The vehicle diagnostic communication method according to any one of claims 1 to 10, wherein the diagnosis initiating device 10 includes at least one of the following: an external device, an ECU with networking function in the vehicle, the domain controller Computing unit 20 in

When the diagnosis initiating device 10 is the computing unit 20, receiving the diagnosis request sent by the diagnosis initiating device 10 includes:

The diagnosis request sent by the computing unit 20 is received through inter-core communication.
A vehicle diagnostic communication device, applied to the control unit 30 in the domain controller of the vehicle, the vehicle diagnostic communication device includes:

The receiving module 1101 is used to receive the diagnosis request sent by the diagnosis initiating device 10,

Determining module 1102, configured to respond to the diagnosis request and determine a diagnosis object based on the request content in the diagnosis request,

The processing module 1103 is configured for the control unit 30 to return a response message of the diagnosis request to the diagnosis initiating device 10 according to the diagnosis situation of the diagnosis object.
An electronic device, the electronic device includes: a processor and a memory storing computer program instructions,

When the processor executes the computer program instructions, the vehicle diagnostic communication method according to any one of claims 1-13 is implemented.
A computer-readable storage medium. Computer program instructions are stored on the computer-readable storage medium. When the computer program instructions are executed by a processor, the vehicle diagnostic communication method according to any one of claims 1-13 is implemented. .
A computer program product. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device causes the electronic device to execute the vehicle diagnostic communication method according to any one of claims 1-13.