Vehicle diagnosis method, vehicle and storage medium
By obtaining diagnostic ID information, the remote diagnostic controller controls the gateway to enter the corresponding state, solving the problem of diagnosis conflicts in the vehicle network architecture, and realizing arbitration of multiple diagnostic methods with high security and realizability.
Patent Information
- Application Number
- CN202510540630.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-27
- Publication Date
- 2025-07-29
AI Technical Summary
In the prior art, when the vehicle network architecture has both local diagnosis and remote diagnosis functions, diagnostic conflicts may occur, resulting in diagnostic failure.
By obtaining diagnostic ID information, the remote diagnostic controller enters the corresponding diagnostic mode, controls the gateway to enter the corresponding state, and rejects other diagnostic requests, realizing arbitration of multiple diagnostic methods to avoid diagnostic execution conflicts.
It effectively avoids diagnostic execution conflicts when multiple diagnostic access points access vehicles at the same time, improves the system's realization and security, and reduces the difficulty of developing Ethernet gateways.
Smart Images

Figure CN120386328A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of vehicles, and in particular, to a vehicle diagnosis method, a vehicle, and a storage medium. Background Art
[0002] With the development of automotive intelligence and networking, the complexity of the electronic and electrical system is getting higher and higher. The local diagnosis function alone cannot meet the requirements of after-sales diagnosis scenarios. Remote diagnosis solves the problem that a vehicle must enter a station for diagnosis and repair when a fault occurs. Through remote diagnosis, the fault information of the controller and the whole vehicle can be quickly obtained, and the fault problem can be quickly discovered and the diagnosis and repair of the vehicle can be completed. Therefore, it is necessary to implement the development of the whole vehicle remote diagnosis function, so as to reduce the costs of on-site rescue such as manpower, time, and expenses, improve business efficiency, and enhance customer satisfaction.
[0003] In the related art, for a vehicle network architecture with an independent gateway, which has both local diagnosis and remote diagnosis functions, when different diagnosis methods are accessed, a situation of diagnosis failure caused by diagnosis conflicts may occur. Therefore, it is necessary to provide a diagnosis processing strategy for different diagnosis modes based on multiple groups of diagnosis IDs. Summary of the Invention
[0004] The present invention aims to solve at least one of the technical problems existing in the prior art. For this purpose, the present invention proposes a vehicle diagnosis method, which enables the gateway to arbitrate multiple diagnosis methods such as remote diagnosis and local diagnosis, and at the same time avoids the diagnosis execution conflicts caused by multiple diagnosis access points accessing the vehicle simultaneously, and has high feasibility and security.
[0005] The present invention further proposes a vehicle.
[0006] The present invention further proposes a storage medium.
[0007] The present invention further proposes a vehicle.
[0008] The vehicle diagnosis method according to the first aspect embodiment of the present invention includes: in response to a diagnosis request, the gateway obtains diagnosis ID information; according to the diagnosis ID information, the remote diagnosis controller enters a diagnosis mode; according to the diagnosis mode, the status of the gateway is obtained; if the status of the gateway is in an idle state, the remote diagnosis controller controls the gateway to enter a state corresponding to the diagnosis mode and rejects the execution of other diagnosis requests when they are re-accessed.
[0009] The vehicle diagnosis method according to an embodiment of the present invention identifies a diagnosis mode through the obtained diagnosis ID information. After the remote diagnosis controller enters the diagnosis mode, it can instruct the gateway to enter a diagnosis state corresponding to the diagnosis mode. By identifying the diagnosis mode through the obtained diagnosis ID information, after the remote diagnosis controller enters the diagnosis mode, it can instruct the gateway to enter a diagnosis state corresponding to the diagnosis mode, which facilitates the arbitration of various diagnosis methods such as remote diagnosis and local diagnosis by the gateway. At the same time, it avoids the diagnosis execution conflict caused by multiple diagnosis access points accessing the vehicle simultaneously, reduces the development difficulty of the Ethernet gateway, and has high feasibility and security.
[0010] According to some embodiments of the present invention, the state of the gateway is one of an idle state, an OTA state, a local diagnosis state, and a remote diagnosis state. The method further includes: when the remote diagnosis controller enters the remote diagnosis mode; if the gateway is in the idle state, the remote diagnosis controller controls the gateway to enter the remote diagnosis state.
[0011] According to some embodiments of the present invention, the method further includes: when the gateway enters the remote diagnosis state, the gateway routes the diagnosis message sent by the remote diagnosis controller and does not route the local diagnosis message.
[0012] According to some embodiments of the present invention, the method further includes: after the remote diagnosis controller enters the remote diagnosis mode, it periodically sends diagnosis data to the gateway through physical addressing to maintain the remote diagnosis state of the gateway.
[0013] According to some embodiments of the present invention, the method further includes: when the gateway is in the remote diagnosis state, if the gateway does not receive the diagnosis data with physical addressing sent by the remote diagnosis controller within a set time, the gateway exits the remote diagnosis state; if the gateway receives an instruction to exit the remote diagnosis state sent by the remote diagnosis controller, the gateway exits the remote diagnosis state; if the gateway is powered off and reset or abnormally reset, the gateway exits the remote diagnosis state.
[0014] According to some embodiments of the present invention, the diagnosis request includes a local diagnosis request or a remote diagnosis request. The method further includes: if in response to a local diagnosis request, the gateway obtains the message for local diagnosis access, the remote diagnosis controller enters the local diagnosis mode after receiving the message sent by the gateway, and the gateway normally routes the local diagnosis message; if in response to a remote diagnosis request, the gateway obtains the message for remote diagnosis access, the remote diagnosis controller enters the remote diagnosis mode after receiving the message sent by the gateway, and the gateway does not route the local diagnosis message.
[0015] According to some embodiments of the present invention, the method further includes: responding to a diagnostic request according to a diagnostic priority; wherein, the diagnostic priority includes: when the vehicle is in the local diagnostic mode, rejecting a remote diagnostic request; or, when the vehicle is in the OTA mode, rejecting a local diagnostic request and a remote diagnostic mode request; or, when the vehicle is in the remote diagnostic mode, rejecting the OTA mode and the local diagnostic request.
[0016] A vehicle according to an embodiment of the third aspect of the present invention includes: at least one processor; a memory communicatively connected to the at least one processor; wherein, a computer program executable by the at least one processor is stored in the memory, and when the at least one processor executes the computer program, the vehicle diagnostic method is implemented.
[0017] A non-volatile readable storage medium according to an embodiment of the third aspect of the present invention stores a computer program thereon, and when the computer program is executed, the vehicle diagnostic method is implemented.
[0018] A vehicle according to an embodiment of the fourth aspect of the present invention includes: a TBOX controller, an Ethernet gateway, an Ethernet controller, and a CAN controller; the Ethernet gateway is respectively connected to the TBOX controller, the Ethernet controller, and the CAN controller, and the Ethernet gateway is further configured to communicatively connect to an OBD diagnostic device; the Ethernet gateway is used to establish a diagnostic network connection for the vehicle diagnostic method.
[0019] The additional aspects and advantages of the present invention will be partially given in the following description, partially become apparent from the following description, or be understood through the practice of the present invention. Description of the Drawings
[0020] The above and / or additional aspects and advantages of the present invention will become apparent and be readily understood from the description of the embodiments in conjunction with the following drawings, wherein: Figure 1 is a schematic diagram of device connection according to an embodiment of the present invention; Figure 2 is a flowchart of a vehicle diagnostic method according to an embodiment of the present invention; Figure 3 is a schematic diagram of a remote diagnostic method according to an embodiment of the present invention; Figure 4 is a structural block diagram of a vehicle according to an embodiment of the present invention; Figure 5 is a structural block diagram of a vehicle according to another embodiment of the present invention.
[0021] Reference Signs: Vehicle 100 ; processor 101 ; memory 102 ; TBOX controller 103 ; Ethernet gateway 104 ; Ethernet controller 105 ; CAN controller 106 ; OBD device diagnosis 107 . DETAILED DESCRIPTION
[0022] The embodiments of the present invention will be described in detail below. The embodiments described with reference to the accompanying drawings are exemplary. The embodiments of the present invention will be described in detail below.
[0023] To facilitate the description of the technical solution, the device connection method of the embodiment of the present invention is first described below.
[0024] like Figure 1 As shown in the figure, the TBOX controller, OBD diagnostic device, CAN controller, and Ethernet controller are each connected to the Ethernet gateway for information exchange. The TBOX controller, OBD diagnostic device, and Ethernet controller exchange information using the DOPI protocol. DOPI is an Ethernet-based diagnostic communication protocol that uses the Ethernet bus and offers advantages such as high bandwidth, high speed, and the ability to enable remote diagnosis. The CAN controller and Ethernet controller exchange information using the CAN protocol. CAN is a serial bus communication protocol used for real-time data exchange in automotive electronic systems. It is characterized by high speed, strong anti-interference capabilities, and excellent error detection and correction capabilities.
[0025] Reference below Figure 2 The vehicle diagnosis control method according to the first embodiment of the present invention is described as follows. Figure 2 As shown, the method at least includes steps S1 to S4.
[0026] Step S1: In response to a diagnosis request, the gateway obtains diagnosis ID information.
[0027] Specifically, when a diagnosis request is made to a vehicle, the diagnosis ID information is first obtained. After the diagnosis request is received, the diagnosis ID information is identified and judged. For example, there may be two pieces of diagnosis ID information, namely ID1 and ID2.
[0028] Step S2: The remote diagnosis controller enters a diagnosis mode according to the diagnosis ID information.
[0029] Specifically, after obtaining the diagnostic ID information, the diagnostic ID information is identified and judged, and according to different diagnostic ID information, different diagnostic modes are identified and then an in-vehicle diagnostic network connection is established. For example, when the identified diagnostic ID information is ID1 or ID2, the corresponding diagnostic mode is different, and the remote diagnostic controller enters the corresponding diagnostic mode.
[0030] Step S3: Obtain the state of the gateway according to the diagnostic mode.
[0031] Specifically, after obtaining the diagnostic ID information, identify and judge the diagnostic ID information. After the remote diagnostic controller enters the diagnostic mode corresponding to the diagnostic ID information, obtain the current state of the gateway. For example, the current state of the gateway is one of the idle state, OTA state, local diagnostic state, and remote diagnostic state.
[0032] Step S4, if the state of the gateway is in the idle state, the remote diagnostic controller controls the gateway to enter the state corresponding to the diagnostic mode and refuses to execute when other diagnostic requests are accessed again.
[0033] Specifically, after identifying the diagnostic mode and establishing an in-vehicle diagnostic network connection, when the remote diagnostic controller enters the diagnostic mode corresponding to the diagnostic ID information, if the gateway is in the idle state at this time, the remote diagnostic controller instructs the gateway to enter the state corresponding to the diagnostic mode in which the remote diagnostic controller is located, and refuses to execute the diagnostic requests accessed by the latter. For example, if the TBOX controller is in the remote diagnostic mode, it can instruct the gateway to enter the remote diagnostic state.
[0034] According to the vehicle diagnostic control method of the embodiment of the present invention, by identifying the diagnostic mode through the obtained diagnostic ID information, after the remote diagnostic controller enters the diagnostic mode, it can instruct the gateway to enter the diagnostic state corresponding to the diagnostic mode, which is convenient for the gateway to arbitrate various diagnostic methods such as remote diagnosis and local diagnosis. At the same time, it avoids the diagnostic execution conflict caused by multiple diagnostic access points accessing the vehicle simultaneously, reduces the development difficulty of the Ethernet gateway, and has high feasibility and security.
[0035] According to some embodiments of the present invention, the state of the gateway is one of the idle state, OTA state, local diagnostic state, and remote diagnostic and remote reading state.
[0036] Specifically, in the OTA state, software upgrade of in-vehicle controllers is performed; in the remote diagnostic state, specific diagnostic processes enter the remote diagnostic mode; in the remote reading state, diagnostic information is read; in the local diagnostic state, the OBD diagnostic device indirectly establishes a diagnostic connection with in-vehicle nodes through the gateway, and a vehicle information message needs to be sent; the OBD diagnostic device sends the vehicle information message to the Ethernet gateway, and the Ethernet gateway establishes a diagnostic connection with other Ethernet nodes.
[0037] According to some embodiments of the present invention, the method further includes: when the remote diagnostic controller enters the remote diagnostic mode, if the gateway is in the idle state, the remote diagnostic controller controls the gateway to enter the remote diagnostic state.
[0038] Specifically, the gateway is in idle state by default after normal power-on. When the TBOX controller receives a remote diagnosis task and enters the remote diagnosis mode, it determines whether the gateway is in idle state. If so, the TBOX sends a 31 routine service instruction to the gateway to enter the remote diagnosis state. If not, the gateway refuses to enter the remote diagnosis state.
[0039] Therefore, for systems with both offline diagnosis and remote diagnosis, a gateway remote diagnosis mode is set. In this mode, the diagnostic messages from the OBD interface are not routed, which facilitates the gateway to arbitrate remote diagnosis and local diagnosis.
[0040] Among them, the remote diagnostic state / mode refers to a special mode that the controller needs to enter before entering the diagnostic execution. This mode avoids diagnostic execution conflicts caused by multiple diagnostic access points accessing the vehicle at the same time.
[0041] According to some embodiments of the present invention, the method further includes: when the gateway enters the remote diagnosis state, the gateway routes the diagnosis message sent by the remote diagnosis controller, and does not route the diagnosis message from the local gateway.
[0042] Specifically, if Figure 3 As shown in FIG, when the gateway enters the remote diagnosis state, the gateway routes the diagnostic message sent by the remote diagnosis controller, does not route the diagnostic message from the local, and the remote diagnosis task is executed normally.
[0043] According to some embodiments of the present invention, the method further comprises: after the remote diagnosis controller enters the remote diagnosis mode, periodically sending diagnostic data to the gateway through physical addressing to maintain the remote diagnosis state of the gateway.
[0044] Specifically, when the gateway enters the remote diagnostic state, the remote diagnostic controller periodically sends diagnostic data to the gateway via physical addressing to maintain the gateway's remote diagnostic state. Conversely, if the gateway does not receive physically addressed diagnostic data from the remote diagnostic controller within a set time, the gateway exits the remote diagnostic state.
[0045] According to some embodiments of the present invention, the method further includes: when the gateway is in the remote diagnosis state, if the gateway does not receive the physically addressed diagnostic data sent from the remote diagnosis controller within a set time, the gateway exits the remote diagnosis state; if the gateway receives an instruction to exit the remote diagnosis state sent from the remote diagnosis controller, the gateway exits the remote diagnosis state; if the gateway is powered on and reset or abnormally reset, the gateway exits the remote diagnosis state.
[0046] That is to say, when the gateway does not receive the physically addressed diagnostic data sent from the remote diagnostic controller within the set time, or when the gateway receives the instruction to exit the remote diagnostic state from the remote diagnostic controller, or when a power-off reset or abnormal reset occurs, the gateway exits the remote diagnostic state.
[0047] In this way, the logic of maintaining the gateway in the remote diagnosis state can effectively deal with the situation where the remote diagnosis controller cannot issue 31 routine services to allow the gateway to exit the remote diagnosis state due to an abnormality, thereby improving security.
[0048] According to some embodiments of the present invention, the diagnostic request includes a local diagnostic request or a remote diagnostic request, and the method further includes: if in response to a local diagnostic request, the gateway obtains a local diagnostic access message, the remote diagnostic controller enters a local diagnostic mode after receiving the message sent from the gateway, and the gateway routes the local diagnostic message normally; if in response to a remote diagnostic request, the gateway obtains a remote diagnostic access message, the remote diagnostic controller enters a remote diagnostic mode after receiving the message sent by the gateway, and the gateway does not route the local diagnostic message.
[0049] Specifically, when local diagnosis is connected first, the gateway sends a message indicating local diagnosis access. TBOX receives and identifies the message sent by the gateway. At this time, if a remote diagnosis task is connected on the TBOX side, the TBOX does not execute the remote diagnosis task. The gateway routes the local diagnosis message normally, and the local diagnosis task is executed normally. When remote diagnosis is connected first, the TBOX enters remote diagnosis mode. TBOX sends a 31-routine service to enable the gateway to enter remote diagnosis state. At this time, the gateway routes the diagnostic message sent by the TBOX but does not route the diagnostic message from the OBD port. The remote diagnosis task is executed normally. In other words, the gateway is the arbitrator between remote and local diagnosis.
[0050] Therefore, for a system capable of both local diagnosis and remote diagnosis, the present invention solves the diagnostic execution conflict problem caused by multiple diagnostic access points accessing the vehicle at the same time by setting a gateway remote diagnosis mode.
[0051] According to some embodiments of the present invention, the method further includes: responding to diagnostic requests according to diagnostic priority; wherein the diagnostic priority includes: the entire vehicle is in local diagnostic mode, and remote diagnostic requests are rejected; or, the entire vehicle is in OTA mode, and local diagnostic requests and remote diagnostic mode requests are rejected; or, the entire vehicle is in remote diagnostic mode, and OTA mode and local diagnostic requests are rejected.
[0052] Specifically, if the gateway receives ID1 sent by the OBD diagnostic device, it determines whether the vehicle is in the OTA or remote diagnosis mode. If it is not in the remote diagnosis mode and not in the OTA mode, the vehicle enters the local diagnosis mode. The gateway establishes a diagnostic connection, and the controller performs a diagnostic response. If it is in the remote diagnosis mode or OTA mode, the diagnostic access is rejected, and the gateway does not establish a diagnostic connection. If the vehicle is in the local diagnosis mode, the TBOX does not send a diagnostic request. If it is not in the local diagnosis mode, the TBOX can send a diagnostic request ID2, and the TBOX establishes a diagnostic connection with the gateway and in-vehicle Ethernet nodes and performs a diagnostic response.
[0053] The vehicle 100 according to the third aspect embodiment of the present invention includes: a processor 101 and a memory 102.
[0054] Wherein, as Figure 4 shown, at least one processor 101 is communicatively connected to at least one memory 102. The memory 102 stores a computer program executable by at least one processor 101. When at least one processor 101 executes the computer program, a vehicle diagnosis control method is implemented.
[0055] According to the vehicle of the embodiment of the present invention, by identifying the diagnosis mode through the obtained diagnosis ID information, after the remote diagnosis controller enters the diagnosis mode, it can instruct the gateway to enter the diagnosis state corresponding to the diagnosis mode, which is convenient for the gateway to arbitrate various diagnosis methods such as remote diagnosis and local diagnosis. At the same time, it avoids the diagnostic execution conflict caused by multiple diagnosis access points accessing the vehicle simultaneously, reduces the development difficulty of the Ethernet gateway, and has high feasibility and security.
[0056] The non-volatile readable storage medium according to the third aspect embodiment of the present invention stores a computer program thereon. When the computer program is executed, a vehicle diagnosis method is implemented.
[0057] According to the vehicle of the fourth aspect embodiment of the present invention, the fourth aspect embodiment of the present invention provides a vehicle, as Figure 5 shown, the vehicle 100 includes: a TBOX controller 103, an Ethernet gateway 104, an Ethernet controller 105, and a CAN controller 106. Among them, the Ethernet gateway 104 is respectively connected to the TBOX controller 103, the Ethernet controller 105, and the CAN controller 106. The Ethernet gateway 104 is further used to communicate with the OBD diagnostic device 107.
[0058] Specifically, if the Ethernet gateway 104 receives ID1 sent by the OBD diagnostic device 107, it determines whether the vehicle is in the OTA or remote diagnosis mode. If it is not in the remote diagnosis mode and not in the OTA mode, the vehicle enters the local diagnosis mode. The Ethernet gateway 104 establishes a diagnostic connection, and the CAN controller 106 makes a diagnostic response. If it is in the remote diagnosis mode or the OTA mode, the diagnostic access is rejected, and the Ethernet gateway 104 does not establish a diagnostic connection.
[0059] If the vehicle is in the local diagnosis mode, the TBOX controller 103 does not send a diagnostic request. If it is not in the local diagnosis mode, the TBOX controller 103 can send a diagnostic request ID2. The TBOX controller 103 establishes a diagnostic connection with the Ethernet gateway 104 and the in-vehicle Ethernet node, and the in-vehicle controller makes a diagnostic response. In the local diagnosis mode or the remote diagnosis mode, for the in-vehicle CAN controller 106, both the OBD diagnostic device 107 and the TBOX controller 103 need to establish a diagnostic connection with the Ethernet gateway 104. The Ethernet gateway 104 performs diagnostic message protocol conversion. Based on the ID of the response message of the CAN controller 106, if it is the local diagnosis ID1, it is forwarded to the port of the OBD diagnostic device 107, and if it is the remote diagnosis ID2, it is forwarded to the port of the TBOX controller 103.
[0060] For the vehicle according to the embodiment of the present invention, by identifying the diagnosis mode through the obtained diagnosis ID information, the gateway can enter the diagnosis state corresponding to the diagnosis mode to achieve the arbitration of remote diagnosis and local diagnosis, avoid the diagnostic execution conflict caused by multiple diagnostic access points accessing the vehicle simultaneously, reduce the development difficulty of the Ethernet gateway, and have high feasibility and security.
[0061] In the description of the present invention, it should be understood that the orientation or positional relationship indicated by the terms "center", "longitudinal", "transverse", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc. is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the present invention.
[0062] In the description of this specification, the description referring to terms such as "one embodiment", "some embodiments", "schematic embodiments", "examples", "specific examples", or "some examples", etc. means that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example.
[0063] Although the embodiments of the present invention have been shown and described, those of ordinary skill in the art can understand that various changes, modifications, substitutions, and variations can be made to these embodiments without departing from the principles and spirit of the present invention, and the scope of the present invention is defined by the claims and their equivalents.
Claims
1. A vehicle diagnosis method, characterized in that, Including: In response to a diagnostic request, the gateway acquires diagnostic ID information; Based on the diagnostic ID information, the remote diagnostic controller enters a diagnostic mode; Based on the diagnostic mode, the status of the gateway is acquired; If the status of the gateway is in an idle state, the remote diagnostic controller controls the gateway to enter a state corresponding to the diagnostic mode and rejects execution when other diagnostic requests are re-accessed.
2. The vehicle diagnosis method according to claim 1, wherein, The status of the gateway is one of an idle state, an OTA state, a local diagnostic state, and a remote diagnostic state, and the method further includes: When the remote diagnostic controller enters the remote diagnostic mode; If the gateway is in an idle state, the remote diagnostic controller controls the gateway to enter the remote diagnostic state.
3. The vehicle diagnosis method according to claim 2, characterized in that, The method further includes: When the gateway enters the remote diagnostic state, the gateway routes diagnostic messages sent by the remote diagnostic controller and does not route local diagnostic messages.
4. The vehicle diagnosis method according to claim 2, characterized in that, The method further includes: After the remote diagnostic controller enters the remote diagnostic mode, diagnostic data is periodically sent to the gateway through physical addressing to maintain the remote diagnostic state of the gateway.
5. The vehicle diagnosis method according to claim 2, characterized in that The method further includes: When the gateway is in the remote diagnostic state, If the gateway does not receive physical addressing diagnostic data sent by the remote diagnostic controller within a set time, the gateway exits the remote diagnostic state; If the gateway receives an instruction from the remote diagnostic controller to exit the remote diagnostic state, the gateway exits the remote diagnostic state; If the gateway is powered off and reset or abnormally reset, the gateway exits the remote diagnostic state.
6. The vehicle diagnosis method according to claim 1, characterized in that, The diagnostic request includes a local diagnostic request or a remote diagnostic request, and the method further includes: If in response to a local diagnostic request, the gateway acquires a local diagnostic access message, and after the remote diagnostic controller receives the message sent by the gateway, it enters the local diagnostic mode, and the gateway normally routes local diagnostic messages; If in response to a remote diagnostic request, the gateway acquires a remote diagnostic access message, and after the remote diagnostic controller receives the message sent by the gateway, it enters the remote diagnostic mode, and the gateway does not route local diagnostic messages.
7. The vehicle diagnosis method according to claim 1, wherein The method further includes: Respond to diagnostic requests according to diagnostic priorities; Wherein, the diagnostic priorities include: when the vehicle is in the local diagnostic mode, remote diagnostic requests are rejected; or, when the vehicle is in the OTA mode, local diagnostic requests and remote diagnostic mode requests are rejected; or, when the vehicle is in the remote diagnostic mode, OTA mode and local diagnostic requests are rejected.
8. A vehicle, characterized in that, Including: At least one processor; 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 when the at least one processor executes the computer program, the vehicle diagnostic control method according to any one of claims 1-7 is implemented.
9. A non-volatile readable storage medium storing a computer program thereon, characterized in that, When the computer program is executed, the vehicle diagnostic control method according to any one of claims 1-7 is implemented.
10. A vehicle, characterized in that, Including: A TBOX controller, an Ethernet gateway, an Ethernet controller, and a CAN controller; The Ethernet gateway is respectively connected to the TBOX controller, the Ethernet controller and the CAN controller, and the Ethernet gateway is further used for communicating and connecting with an OBD diagnostic device; the Ethernet gateway is used for establishing a diagnostic network connection according to the vehicle diagnostic control method described in any one of claims 1-7.