Diagnostic message routing method and device, equipment, storage medium and product

Abstract

The invention discloses a diagnostic message routing method and device, equipment, a storage medium and a product. The method is applied to a domain controller, and comprises the following steps: when a diagnosis request message sent by a source node is received through a first source diagnosis channel, activating a first protocol data unit group of the first source diagnosis channel in a protocol data unit router layer, and forbidding a second protocol data unit group of a second source diagnosis channel, the first source diagnosis channel and the second source diagnosis channel are different and correspond to the same target diagnosis channel; routing the diagnosis request message to a target diagnosis channel through a protocol data unit router layer, and sending the diagnosis request message to a target node; and based on the target diagnosis channel and the protocol data unit router layer, routing a diagnosis response message sent by the target node to the first source diagnosis channel, and sending the diagnosis response message to the source node. Diagnostic routing and channels are effectively simplified, RAM and link consumption is greatly reduced, and configuration efficiency is improved.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of automatic driving, in particular to a diagnosis message routing method and device, equipment, storage medium and product. BACKGROUND

[0002] With the rapid development of automatic driving technology in the automotive field, the vehicle domain controller is often used as a key node for diagnosis routing. The current diagnosis message routing method of the vehicle domain controller is a "one-to-one" diagnosis routing, that is, a set of source diagnosis channels is used to route the diagnosis request message to another set of target diagnosis channels. When there are multiple electronic control unit (ECU) nodes, or when an ECU node communicates with a certain node through the domain controller using different diagnosis protocols, the domain controller needs to implement multiple sets of "one-to-one" diagnosis routing, and needs to add multiple sets of diagnosis channels for diagnosis routing.

[0003] For example, the gateway needs to use both the Diagnostics over Internet Protocol (DoIP) and the Diagnostics over Controller Area Network (DoCAN) protocols simultaneously, and the domain controller needs to perform CAN diagnosis upgrade on the radar. At this time, the domain controller must establish two sets of "one-to-one" diagnosis routing in parallel, and correspondingly add 4 sets of diagnosis channels for diagnosis routing, that is, two source diagnosis addresses correspond to two destination diagnosis addresses. Figure 1 As shown in the table, in the DoCAN to DoCAN diagnosis routing, the diagnosis request message initiated from the gateway CAN2 interface (diagnosis logical address 0x1314) enters the protocol data unit router layer (PduR) of the domain controller through the source diagnosis channel A1, and is forwarded to the target diagnosis channel B1 before being processed by the Controller Area Network Transport Layer Protocol (CAN TP), and is sent out by the CAN1 interface of the domain controller, and is finally received by the radar through the CAN1 interface, and the corresponding diagnosis logical address is 0x1315; in the DoIP to DoCAN diagnosis routing, the diagnosis request initiated from the gateway DoIp interface (DoIp Int) corresponding to the diagnosis logical address 0x1414 enters the protocol data unit router layer PduR of the domain controller through the source diagnosis channel A2, and is forwarded to the target diagnosis channel B2 before being processed by the CAN TP, and is sent out by the CAN1 interface of the domain controller, and is finally received by the radar through the CAN1 interface, and the corresponding diagnosis logical address is 0x1415. It can be seen that the two sets of routing share the same physical CAN1 bus but use different logical addresses.

[0004] From the whole vehicle diagnosis architecture, this kind of multi-group "one-to-one" diagnosis routing and diagnosis channel will increase the burden of the whole vehicle diagnosis architecture and the vehicle-mounted domain controller, as well as the consumption of the random access memory (RAM) space resources and the communication link inside the domain controller, and the arrangement of the internal diagnosis link will also be more redundant and cumbersome. SUMMARY

[0005] The application provides a diagnosis message routing method, device, equipment, storage medium and product, to solve the problems of architecture redundancy, resource waste and complex link arrangement existing in the existing diagnosis message routing method.

[0006] According to an aspect of the application, a diagnosis message routing method is provided, applied to a domain controller, and the method comprises:

[0007] When a diagnosis request message sent by a source node is received through a first source diagnosis channel, a first protocol data unit group of the first source diagnosis channel at a protocol data unit router layer is activated, and a second protocol data unit group of a second source diagnosis channel at the protocol data unit router layer is disabled, wherein the first source diagnosis channel and the second source diagnosis channel are different, and the first source diagnosis channel and the second source diagnosis channel correspond to the same target diagnosis channel;

[0008] The diagnosis request message is routed to the target diagnosis channel through the protocol data unit router layer and sent to a target node;

[0009] A diagnosis response message from the target node is received, the diagnosis response message is routed to the first source diagnosis channel based on the target diagnosis channel and the protocol data unit router layer, and sent to the source node through the first source diagnosis channel.

[0010] According to another aspect of the application, a diagnosis message routing device is provided, comprising:

[0011] A unit group activation module is configured to activate a first protocol data unit group of a first source diagnosis channel at a protocol data unit router layer when a diagnosis request message sent by a source node is received through the first source diagnosis channel, and to disable a second protocol data unit group of a second source diagnosis channel at the protocol data unit router layer, wherein the first source diagnosis channel and the second source diagnosis channel are different, and the first source diagnosis channel and the second source diagnosis channel correspond to the same target diagnosis channel;

[0012] A request message routing module is configured to route the diagnosis request message to the target diagnosis channel through the protocol data unit router layer and send it to a target node;

[0013] A response message routing module is used to receive a diagnostic response message from the target node, route the diagnostic response message to the first source diagnostic channel based on the target diagnostic channel and the protocol data unit router layer, and send it to the source node through the first source diagnostic channel.

[0014] According to another aspect of the present invention, an electronic device is provided, comprising:

[0015] at least one processor; and

[0016] a memory communicatively connected to the at least one processor; wherein,

[0017] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the diagnostic message routing method described in any embodiment of the present invention.

[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the diagnostic message routing method according to any embodiment of the present invention when executed.

[0019] According to another aspect of the present invention, a computer program product is provided. The computer program product includes a computer program. When the computer program is executed by a processor, the diagnostic message routing method according to any embodiment of the present invention is implemented.

[0020] The technical scheme provided by the embodiment of the application is applied to a domain controller, and the method comprises the following steps: when a diagnostic request message sent by a source node is received through a first source diagnostic channel, a first protocol data unit group of a protocol data unit router layer of the first source diagnostic channel is activated, and a second protocol data unit group of a second source diagnostic channel of the protocol data unit router layer is disabled, wherein the first source diagnostic channel and the second source diagnostic channel are different, and the first source diagnostic channel and the second source diagnostic channel correspond to the same target diagnostic channel; the diagnostic request message is routed to the target diagnostic channel through the protocol data unit router layer, and is sent to a target node; a diagnostic response message from the target node is received, the diagnostic response message is routed to the first source diagnostic channel based on the target diagnostic channel and the protocol data unit router layer, and is sent to the source node through the first source diagnostic channel. Through the above technical scheme, when the diagnostic request message sent by the source node through the first source diagnostic channel is received, the first protocol data unit group corresponding to the first source diagnostic channel is activated, and the second protocol data unit group of the second source diagnostic channel is disabled, so that it is ensured that the diagnostic response message will not be forwarded to other source diagnostic channels at the same time, thereby ensuring that only a one-to-one diagnostic route exists in the same time period, effectively reducing a plurality of one-to-one diagnostic routes and redundant diagnostic channels, significantly reducing consumption of RAM space resources and communication links inside the domain controller, and making the internal diagnostic link configuration more simple.

[0021] It should be understood that the content described in this part is not intended to identify key or important features of the embodiments of the application, nor is it intended to limit the scope of the application. Other features of the application will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiments description. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can also be obtained by those skilled in the art without creative effort on the basis of these drawings.

[0023] Figure 1 is a structural schematic diagram of a current diagnostic message routing method provided by the application;

[0024] Figure 2 is a flowchart of a diagnostic message routing method provided by the first embodiment of the application;

[0025] Figure 3 is a schematic diagram of internal processing of a message of a domain controller provided by the embodiment of the application;

[0026] Figure 4This is a schematic diagram of the structure of a diagnostic message routing method provided by an embodiment of the present invention;

[0027] Figure 5 This is a structural diagram of a diagnostic message routing device provided in Embodiment 2 of the present invention;

[0028] Figure 6 This is a structural diagram of an electronic device provided in Example 3 of the present invention. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] Example 1

[0032] Figure 2 This is a flow chart of a diagnostic message routing method provided by the first embodiment of the present invention. This embodiment is applicable to the case of routing diagnostic messages. The method can be executed by a diagnostic message routing device. The diagnostic message routing device can be implemented in the form of hardware and / or software. The diagnostic message routing device can be configured in an electronic device, which can be a domain controller. Figure 2 As shown, the method includes:

[0033] S110. When a diagnostic request message sent by a source node is received through a first source diagnostic channel, the first protocol data unit group of the first source diagnostic channel at the protocol data unit router layer is activated, and the second protocol data unit group of the second source diagnostic channel at the protocol data unit router layer is disabled, wherein the first source diagnostic channel and the second source diagnostic channel are different, and the first source diagnostic channel and the second source diagnostic channel correspond to the same target diagnostic channel.

[0034] In this embodiment, the source node can be understood as a node that sends a diagnostic request message, such as a gateway. The first source diagnostic channel can be understood as a diagnostic communication path established between the domain controller and the source node, used to transmit diagnostic request messages and corresponding diagnostic response messages between the source node and the domain controller. The first source diagnostic channel may include, among others, a sending interface on the source node side, a receiving interface on the domain controller side, and the diagnostic logical address of the source node. The target diagnostic channel can be understood as a communication diagnostic path between the domain controller and the target node, used to transmit diagnostic request messages and corresponding diagnostic response messages between the target node and the domain controller. The target diagnostic channel may include a sending interface on the domain controller side, a receiving interface on the target node side, and the diagnostic logical address of the target node. The target node can be understood as the diagnosed object that receives the diagnostic request message and returns the diagnostic response message, such as a radar. The first source diagnostic channel and the second source diagnostic channel correspond to the same target diagnostic channel. The second source diagnostic channel is different from the first source diagnostic channel. The two source diagnostic channels may correspond to different source nodes, or they may correspond to the same source node, but with different diagnostic logical addresses.

[0035] Among them, the diagnostic request message is used to trigger the target node to perform the diagnostic function. The protocol data unit router layer (PduR) is used to route the diagnostic request message and the diagnostic response message. The first protocol data unit group (PduRGroup) can be understood as a logical configuration unit associated with the first source diagnostic channel. When activated, it allows the diagnostic request message to be routed from the first source diagnostic channel to the target diagnostic channel, and allows the diagnostic response message to be routed from the target diagnostic channel back to the first source diagnostic channel. The second protocol data unit group can be understood as a logical configuration unit associated with the second source diagnostic channel. When disabled, it does not allow the diagnostic request message to be routed from the second source diagnostic channel to the target diagnostic channel, and does not allow the diagnostic response message to be routed from the target diagnostic channel back to the second source diagnostic channel.

[0036] Specifically, when a diagnostic request message sent by a source node is received through a first source diagnostic channel, the first PduR Group of the first source diagnostic channel in the PduR is activated in the callback function corresponding to the first source diagnostic channel, and the second PduR Group of the second source diagnostic channel in the PduR is disabled.

[0037] S120: Routing the diagnosis request message to the target diagnosis channel through the protocol data unit router layer, and sending it to the target node.

[0038] Specifically, after the diagnosis request message is routed to the target diagnosis channel through the protocol data unit routing layer, the diagnosis request message is sent to the target node.

[0039] S130. Receive a diagnostic response message from the target node, route the diagnostic response message to the first source diagnostic channel based on the target diagnostic channel and the protocol data unit router layer, and send the diagnostic response message to the source node through the first source diagnostic channel.

[0040] In this embodiment, the diagnosis response message can be understood as a response data packet of the target node to the diagnosis request message.

[0041] Specifically, after receiving the diagnostic request message, the target node performs diagnostic logic processing and sends a diagnostic response message to the domain controller. The diagnostic response message sent by the target node is received and sent to the protocol data unit router layer via the target diagnostic channel. The protocol data unit router layer then routes the diagnostic response message to the first source diagnostic channel and sends it to the source node via the first source diagnostic channel.

[0042] It is worth noting that when the protocol data unit router layer routes the diagnostic response message, since the second PduR Group of the second source diagnostic channel has been disabled, it can only be automatically routed to the first source diagnostic channel, meeting the diagnostic specification of "one-to-one" diagnostic communication with diagnostic physical addressing. If the second PduR Group is not disabled, the protocol data unit router layer will route the diagnostic response message to both the first source diagnostic channel and the second source diagnostic channel. Since the diagnostic request message is sent by the first source diagnostic channel, the source node can only recognize the diagnostic response message received by the first source diagnostic channel, but cannot recognize the diagnostic response message received by the second source diagnostic channel, resulting in failure to meet the diagnostic specification of "one-to-one" diagnostic communication with diagnostic physical addressing.

[0043] The technical solution provided in a first embodiment of the present invention is applied to a domain controller, and the method includes: when a diagnostic request message sent by a source node is received through a first source diagnostic channel, activating the first protocol data unit group of the first source diagnostic channel at the protocol data unit router layer, and disabling the second protocol data unit group of the second source diagnostic channel at the protocol data unit router layer, wherein the first source diagnostic channel and the second source diagnostic channel are different, and the first source diagnostic channel and the second source diagnostic channel correspond to the same target diagnostic channel; routing the diagnostic request message to the target diagnostic channel through the protocol data unit router layer, and sending it to the target node; receiving a diagnostic response message from the target node, routing the diagnostic response message to the first source diagnostic channel based on the target diagnostic channel and the protocol data unit router layer, and sending it to the source node through the first source diagnostic channel. Through the above technical solution, when a diagnostic request message is received from a source node via a first source diagnostic channel, the first protocol data unit group corresponding to the first source diagnostic channel is activated, and the second protocol data unit group of the second source diagnostic channel is disabled to ensure that the diagnostic response message will not be forwarded to other source diagnostic channels at the same time. This effectively reduces multiple groups of "one-to-one" diagnostic routes and redundant diagnostic channels while ensuring that only one-to-one diagnostic routes exist in the same time period, significantly reduces the consumption of RAM space resources and communication links within the domain controller, and makes the internal diagnostic link configuration more streamlined.

[0044] In some embodiments, the second source diagnostic channel is at least one to support any number of source nodes sharing the same target node without interfering with each other.

[0045] Specifically, there is at least one second source diagnostic channel. When the first protocol data unit group corresponding to the first source diagnostic channel is activated, the second protocol data unit groups corresponding to all second source diagnostic channels need to be disabled.

[0046] In some embodiments, the diagnostic channel is implemented based on a diagnostic communication protocol, including one based on a Controller Area Network (CAN) bus, Ethernet, a Local Interconnect Network (LIN) bus, or a FlexRay bus. This allows for adaptability to diagnostic scenarios across different bus types, significantly improving the compatibility and applicability of the bus architecture.

[0047] In this embodiment, the first source diagnostic channel can be implemented based on a diagnostic communication protocol, including a diagnostic communication protocol based on a controller area network CAN bus (DoCAN), a diagnostic communication protocol based on Ethernet (DoIP), a diagnostic communication protocol based on a local interconnect network LIN bus (DoLIN), or a diagnostic communication protocol based on a flexible FlexRay bus (DoFR); the second source diagnostic channel can be implemented based on a diagnostic communication protocol, including DoCAN, DoIP, DoLIN, or DoFR; the target diagnostic channel can be implemented based on a diagnostic communication protocol, including DoCAN, DoIP, DoLIN, or DoFR.

[0048] In some embodiments, the protocol data unit router layer includes a preset routing rule table, and the preset routing rule table is used to define a mapping relationship between a source diagnostic channel and a target diagnostic channel.

[0049] In this embodiment, the preset routing rule table is used to define the mapping relationship between source diagnostic channels and target diagnostic channels. Multiple source diagnostic channels can be associated with the same target diagnostic channel. For example, the first source diagnostic channel and the second source diagnostic channel can be associated with the same target diagnostic channel. This allows multiple source diagnostic channels to be mapped to one target diagnostic channel without having to configure a corresponding target diagnostic channel for each source diagnostic channel, thereby simplifying routing settings.

[0050] For example, Figure 3 This is a schematic diagram of a domain controller's internal message processing provided by an embodiment of the present invention. When the CAN interface (CAN Interface) receives a diagnostic response message, the domain controller copies the data content of the message and places it in the network layer protocol data unit (N-Pdu). After the N-Pdu is processed by the CAN TP, the data content is copied to the interaction layer protocol data unit (I-Pdu). The I-Pdu is routed through the PduR to the I-Pdu corresponding to other CAN interfaces or DoIp interfaces. Furthermore, after the I-Pdu is processed by the CAN TP or socket adapter (SoAd), the data content is copied to the corresponding N-Pdu, and then to the corresponding CAN interface or Ethernet interface (ETHInterface).

[0051] Furthermore, to ensure one-to-one diagnostic routing, it is necessary to restrict the activation and deactivation of protocol data unit groups. For example, when a diagnostic request message is sent to the radar via the first source diagnostic channel A1, the radar returns a diagnostic response message via the target diagnostic channel B. When the diagnostic response message is routed through the PduR, it needs to be routed to both the first source diagnostic channel A1 and the second source diagnostic channel A2. However, since the second PduRGroup corresponding to the second source diagnostic channel A2 is disabled, the diagnostic response message can only be routed to the first source diagnostic channel A1.

[0052] In some embodiments, the PDU router layer includes multiple PDU groups, each of which corresponds to a source diagnostic channel. By independently configuring a PDU group for each diagnostic channel, the domain controller can enable or disable the diagnostic channel as needed, thereby avoiding cross-interference and conserving RAM and link resources.

[0053] In some embodiments, the method further includes: before receiving the diagnostic request message, initializing the first source diagnostic channel and the second source diagnostic channel, and configuring the initial state of the protocol data unit group.

[0054] Specifically, before receiving any diagnostic request messages, the physical interfaces, IDs, caches, and other hardware resources of the first and second source diagnostic channels are initialized, and their corresponding protocol data unit groups are uniformly set to "off" or "inactive," laying the foundation for subsequent activation and deactivation of PduR Groups. This effectively achieves fast and conflict-free one-to-one routing.

[0055] For example, Figure 4 This is a schematic diagram of the structure of a diagnostic message routing method provided by an embodiment of the present invention. Figure 4 As shown: It includes two groups of diagnostic channel routing. The first source diagnostic channel A1 is routed to the target diagnostic channel B through PduR in the form of DoCAN, and the first source diagnostic channel A2 is routed to the target diagnostic channel B through PduR in the form of DoIp. In the other direction, the target diagnostic channel B is routed to the source diagnostic channels A1 and A2 at the same time in the form of DoCAN.

[0056] When the domain controller's underlying CAN module (CAN2) receives a diagnostic request message from the gateway via source diagnostic channel A1 (corresponding diagnostic logical address is 0x1314), the domain controller opens the PduR Group (PRG1) of source diagnostic channel A1 at the PduR layer in the CAN callback function and closes the PduR Group (PRG2) of source diagnostic channel A2 at the PduR layer. The purpose of this process is to open the routing of source diagnostic channel A1 while closing the routing of source diagnostic channel A2. The diagnostic request message is then routed to the target diagnostic channel B via the PduR, processed by the CAN TP, and sent out by the domain controller's CAN1 interface. Finally, it is received by the radar through the CAN1 interface. The corresponding diagnostic logical address is 0x1315.

[0057] After receiving the diagnostic request message, the radar node performs diagnostic logic processing and sends a diagnostic response message to the domain controller. When the diagnostic response message passes through the PduR layer of the domain controller, since the diagnostic routing of the source diagnostic channel A2 is closed, it can only be automatically routed to the source diagnostic channel A1. Then, the diagnostic response message is successfully sent to the gateway through the source diagnostic channel A1, meeting the diagnostic specifications of the one-to-one diagnostic communication of the diagnostic physical addressing.

[0058] Similarly, on the DoIp Int module (Ethernet interface) at the bottom layer of the domain controller, when a diagnostic request message is received from the gateway through the source diagnostic channel A2, the domain controller opens the PduRGroup (PRG2) of the source diagnostic channel A2 at the PduR layer in the SoAd callback function and closes the PduR Group (PRG1) of the source diagnostic channel A1 at the PduR layer, and then implements diagnostic message routing in the same way as above.

[0059] As can be seen, when the domain controller begins receiving a diagnostic request message on a source diagnostic channel, it immediately closes other source diagnostic channels that are also routed to the target diagnostic channel. This ensures that when receiving a diagnostic response message, it is not routed to all source diagnostic channels simultaneously, achieving the goal of enforcing one-to-one diagnostic routing within the same time period. Compared to existing one-to-one diagnostic routing, this effectively reduces the number of one-to-one diagnostic routing links, as well as redundant diagnostic channels and unnecessary CPU resources such as RAM, thereby improving the simplicity and stability of the diagnostic links within the domain controller.

[0060] Example 2

[0061] Figure 5 This is a structural diagram of a diagnostic message routing device provided in Example 2 of the present invention.

[0062] like Figure 5 As shown, the device includes:

[0063] a unit group activation module 21, configured to, when receiving a diagnostic request message sent by a source node through a first source diagnostic channel, activate a first protocol data unit group of the first source diagnostic channel at a protocol data unit router layer, and disable a second protocol data unit group of a second source diagnostic channel at the protocol data unit router layer, wherein the first source diagnostic channel and the second source diagnostic channel are different and correspond to the same target diagnostic channel;

[0064] The request message routing module 22 is used to route the diagnosis request message to the target diagnosis channel through the protocol data unit router layer and send it to the target node;

[0065] The response message routing module 23 is used to receive the diagnostic response message from the target node, route the diagnostic response message to the first source diagnostic channel based on the target diagnostic channel and the protocol data unit router layer, and send it to the source node through the first source diagnostic channel.

[0066] The technical solution provided in the second embodiment of the present invention ensures that only "one-to-one" diagnostic routes exist in the same time period, while effectively reducing multiple groups of "one-to-one" diagnostic routes and redundant diagnostic channels, significantly reducing the consumption of RAM space resources and communication links within the domain controller, and making the internal diagnostic link configuration more streamlined.

[0067] Optionally, there is at least one second source diagnostic channel.

[0068] Optionally, the diagnostic channel is implemented based on a diagnostic communication protocol, which includes a diagnostic communication protocol based on a controller area network (CAN) bus, a diagnostic communication protocol based on Ethernet, a diagnostic communication protocol based on a local interconnect network (LIN) bus, or a diagnostic communication protocol based on a flexible FlexRay bus.

[0069] Optionally, the protocol data unit router layer includes a preset routing rule table, and the preset routing rule table is used to define a mapping relationship between a source diagnostic channel and a target diagnostic channel.

[0070] Optionally, the protocol data unit router layer includes multiple protocol data unit groups, wherein each protocol data unit group corresponds to a source diagnostic channel.

[0071] Optionally, the diagnostic message routing device further includes:

[0072] An initialization module is used to initialize the first source diagnostic channel and the second source diagnostic channel and configure the initial state of the protocol data unit group before receiving the diagnosis request message.

[0073] The diagnostic message routing device provided in the embodiment of the present invention can execute the diagnostic message routing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0074] Example 3

[0075] Figure 6 : is a structural diagram of an electronic device provided in Example 3 of the present invention. The electronic device, which may be a domain controller, is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

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

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

[0078] The processor 11 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the diagnostic message routing method.

[0079] In some embodiments, the diagnostic message routing method can be implemented as a computer program that is tangibly contained in a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the diagnostic message routing method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform the diagnostic message routing method in any other appropriate manner (e.g., by means of firmware).

[0080] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

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

[0082] In the context of the present invention, computer-readable storage media can be tangible media that can contain or store a computer program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Computer-readable storage media can include but are not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, computer-readable storage media can be machine-readable signal media. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

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

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

[0085] A computing system may include clients and servers. The clients and servers are typically remote from each other and typically interact via a communication network. This client-server relationship arises through computer programs running on the respective computers, creating a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host. This server is a hosting product within the cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosting and VPS services.

[0086] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0087] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

[0088] An embodiment of the present invention further provides a computer program product, comprising a computer program and / or instructions, which, when executed by a processor, implements the diagnostic message routing method provided in any embodiment of the present application.

[0089] The computer program product may be implemented by writing computer program code for performing the operations of the present invention in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0090] Note that the above are only preferred embodiments of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments, and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments and may include many other equivalent embodiments without departing from the concept of the present invention. The scope of the present invention is determined by the scope of the appended claims.

Claims

1. A diagnostic message routing method, characterized in that: Applied to a domain controller, the method includes: When a diagnostic request message sent by a source node is received through a first source diagnostic channel, a first protocol data unit group of the first source diagnostic channel at a protocol data unit router layer is activated, and a second protocol data unit group of a second source diagnostic channel at the protocol data unit router layer is disabled, wherein the first source diagnostic channel and the second source diagnostic channel are different and correspond to the same target diagnostic channel; Routing the diagnostic request message to the target diagnostic channel through the protocol data unit router layer and sending it to the target node; Receive a diagnostic response message from the target node, route the diagnostic response message to the first source diagnostic channel based on the target diagnostic channel and the protocol data unit router layer, and send the diagnostic response message to the source node through the first source diagnostic channel.

2. The method according to claim 1, characterized in that The second source diagnostic channel is at least one.

3. The method according to claim 1, characterized in that The diagnostic channel is implemented based on a diagnostic communication protocol, which includes a diagnostic communication protocol based on a controller area network (CAN) bus, a diagnostic communication protocol based on Ethernet, a diagnostic communication protocol based on a local interconnect network (LIN) bus, or a diagnostic communication protocol based on a flexible FlexRay bus.

4. The method according to claim 1, wherein The protocol data unit router layer includes a preset routing rule table, and the preset routing rule table is used to define a mapping relationship between a source diagnostic channel and a target diagnostic channel.

5. The method according to claim 1, wherein The protocol data unit router layer includes a plurality of protocol data unit groups, wherein each protocol data unit group corresponds to a source diagnosis channel.

6. The method according to claim 1, characterized in that The method further comprises: Before receiving the diagnosis request message, the first source diagnosis channel and the second source diagnosis channel are initialized, and the initial state of the protocol data unit group is configured.

7. A diagnostic message routing device, characterized in that: include: a unit group activation module, configured to, when receiving a diagnostic request message sent by a source node through a first source diagnostic channel, activate a first protocol data unit group of the first source diagnostic channel at a protocol data unit router layer, and disable a second protocol data unit group of a second source diagnostic channel at the protocol data unit router layer, wherein the first source diagnostic channel and the second source diagnostic channel are different and correspond to the same target diagnostic channel; A request message routing module, configured to route the diagnostic request message to the target diagnostic channel through a protocol data unit router layer, and send the message to a target node; A response message routing module is used to receive a diagnostic response message from the target node, route the diagnostic response message to the first source diagnostic channel based on the target diagnostic channel and the protocol data unit router layer, and send it to the source node through the first source diagnostic channel.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the diagnostic message routing method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the diagnostic message routing method according to any one of claims 1 to 6 when executed.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the computer program implements the diagnostic message routing method according to any one of claims 1 to 6.

Images