CN115617558A

CN115617558A - Vehicle diagnostic system, method, storage medium, and vehicle

Info

Publication number: CN115617558A
Application number: CN202211321550.4A
Authority: CN
Inventors: 请求不公布姓名
Original assignee: Cambrian Jixingge Nanjing Technology Co ltd
Current assignee: Cambrian Jixingge Nanjing Technology Co ltd
Priority date: 2022-10-26
Filing date: 2022-10-26
Publication date: 2023-01-17

Abstract

The present disclosure discloses a vehicle diagnostic system, method, storage medium, and vehicle. The vehicle diagnosis method based on the vehicle diagnosis system can be flexibly adapted to various vehicle chip systems, and rapid deployment of the vehicle diagnosis system is realized under the scene of various vehicle chip systems.

Description

Vehicle diagnostic system, method, storage medium, and vehicle

Technical Field

The present disclosure relates generally to the field of intelligent driving. More particularly, the present disclosure relates to a vehicle diagnostic system, method, storage medium, and vehicle.

Background

The vehicle fault diagnosis technology plays an important role in ensuring normal work of the automobile, and application research aiming at the vehicle remote fault diagnosis technology is deeper and deeper. The traditional vehicle fault diagnosis technology has the defects of poor reusability, difficult calling of a heterogeneous platform, poor interoperability and the like; with the continuous improvement of the intellectualization degree and the electronization degree of the automobile, new requirements are also made on the vehicle fault diagnosis technology.

In a conventional Electronic and electrical architecture of a vehicle, a plurality of Electronic Control Units (ECUs) are used to independently Control functions of the vehicle, such as automatic driving, active safety, audio-video entertainment, and the like. In the vehicle fault diagnosis, each ECU reports the abnormal state of the vehicle independently, so as to form a longitudinal diagnosis mechanism as shown in fig. 1 (that is, in a single ECU, a lower-level diagnosis reports the operating state of the ECU to an upper-level diagnosis). The existing vehicle fault diagnosis mechanism mainly has the following defects:

the conventional vehicle fault diagnosis mechanism is designed for ECUs with the same software and hardware architecture, that is, the software and hardware architecture of each ECU in fig. 1 is identical, and the implemented diagnosis function is developed and completed in a specific software and hardware environment, and once the software and hardware architecture of a vehicle-mounted chip is changed, the original diagnosis function and diagnosis mechanism may not be used, and need to be re-developed. With the improvement of vehicle computing and functional requirements, a vehicle-mounted Chip System is often composed of a multi-core System on Chip (SoC) or a plurality of heterogeneous socs, and the Chip systems used by different vehicle manufacturers are different, so a vehicle diagnosis scheme capable of being rapidly deployed in a multi-core heterogeneous Chip scene is urgently needed.

Disclosure of Invention

In order to at least solve one or more technical problems as mentioned above, the present disclosure proposes, in various aspects, a vehicle diagnostic solution for a system on chip, which divides at least two stages of diagnostic units within the system on chip, configures different diagnostic functions and corresponding authorities for each stage of diagnostic unit through a configuration file, so that the vehicle diagnostic solution of the present disclosure can be flexibly and quickly deployed in various vehicle chip systems, especially in a multi-core heterogeneous chip system.

In a first aspect, the present disclosure provides a vehicle diagnostic system for diagnosing a vehicle chip system, the vehicle diagnostic system comprising: at least two stages of diagnosis units which are respectively arranged on different chip levels of the vehicle chip system, wherein each stage of diagnosis unit comprises a plurality of diagnosis function modules; the diagnostic function module is deployed on a corresponding chip level through a configuration file, the configuration file comprises a function permission parameter and/or a diagnostic permission parameter, the function permission parameter is used for configuring permissions related to function data for the diagnostic function module, the diagnostic permission parameter is used for configuring permissions related to the diagnostic data for the diagnostic function module, and the diagnostic function module is used for managing the function data and/or the diagnostic data on the related chip level according to the corresponding configuration file.

In a second aspect, the present disclosure provides a vehicle diagnostic method, performed by a vehicle diagnostic system comprising: at least two stages of diagnostic units respectively deployed on different chip levels of the vehicle chip system; the method comprises the following steps: the diagnostic function module of the superior diagnostic unit manages the function data and/or the diagnostic data of the subordinate diagnostic unit according to the configuration authority of the configuration file; the configuration file comprises a function permission parameter and/or a diagnosis permission parameter, the function permission parameter is used for configuring permissions related to function data for the diagnosis function module, and the diagnosis permission parameter is used for configuring permissions related to the diagnosis data for the diagnosis function module.

In a third aspect, the present disclosure provides a computer readable storage medium storing computer program code of a vehicle diagnostic method, which when executed, performs the above vehicle diagnostic method.

In a fourth aspect, the present disclosure provides a vehicle comprising a vehicle on-chip system and the vehicle diagnostic system described above, the vehicle diagnostic system being disposed on the vehicle on-chip system.

With the vehicle diagnostic scheme provided above, the scheme of the present disclosure divides the diagnostic system into at least two levels of diagnostic units, respectively deployed on different chip levels of the vehicle chip system. In an actual deployment scene, a plurality of independent diagnosis function modules can be deployed on different chip levels through standardized configuration files according to actual requirements, and different multi-core heterogeneous scenes can be flexibly adapted while various diagnosis functions are realized. In addition, because the diagnosis function modules are deployed through a standardized configuration file, different diagnosis authorities can be divided through the function authority parameters and the diagnosis authority parameters set in the configuration file, so that each diagnosis function module is decoupled, corresponding diagnosis problems can be solved independently, and the stability of the diagnosis function is improved.

Drawings

The above and other objects, features and advantages of exemplary embodiments of the present disclosure will become readily apparent from the following detailed description read in conjunction with the accompanying drawings. Several embodiments of the present disclosure are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to like or corresponding parts and in which:

FIG. 1 illustrates a deployment relationship diagram of a prior art vehicle diagnostic system;

FIG. 2 illustrates a schematic deployment diagram of a vehicle diagnostic system and its diagnosed vehicle chip system according to an embodiment of the disclosure;

FIG. 3 is a deployment diagram of a vehicle chip scenario to which the vehicle diagnostic system of the disclosed embodiment is applied;

FIG. 4 illustrates a deployment relationship diagram of another vehicle chip scenario to which the vehicle diagnostic system of the disclosed embodiment is applied;

FIG. 5 illustrates a deployment relationship diagram of another vehicle chip scenario to which the vehicle diagnostic system of the disclosed embodiment is applied;

FIG. 6 is a deployment diagram illustrating another vehicle chip scenario to which the vehicle diagnostic system of the disclosed embodiment is applied;

FIG. 7 is a schematic diagram illustrating the subscription and publication of data rights by various units/modules in a vehicle diagnostic system of an embodiment of the present disclosure;

FIG. 8 illustrates an exemplary flow chart of a vehicle diagnostic method according to one embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present disclosure will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are some, not all embodiments of the present disclosure. All other embodiments, which can be derived by one skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the scope of protection of the present disclosure.

It should be understood that the terms "first," "second," and "third," etc. as may be used in the claims, the description, and the drawings of the present disclosure are used to distinguish between different objects, and are not used to describe a particular order. The terms "comprises" and "comprising," when used in the specification and claims of this disclosure, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is also to be understood that the terminology used in the description of the disclosure herein is for the purpose of describing particular embodiments only, and is not intended to be limiting of the disclosure. As used in the specification and claims of this disclosure, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should be further understood that the term "and/or" as used in the specification and claims of this disclosure refers to any and all possible combinations of one or more of the associated listed items and includes such combinations.

As used in this specification and claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".

Specific embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

As mentioned in the background, the existing vehicle fault diagnosis mechanism based on simple chip architecture has not been suitable for the current highly complex SoC from the system design perspective. On one hand, the existing diagnosis mechanism is directed at a simple chip architecture as shown in fig. 1, while the future development direction tends to a multi-core heterogeneous SoC scenario, and the complex system function architecture makes the original vehicle fault diagnosis mechanism unable to meet the corresponding fault diagnosis requirement; on the other hand, due to the high complexity of SoC and the large number of abnormal sources, and the abnormal signals are usually distributed in different subsystems of SoC, the abnormal signals of all subsystems are gathered to MCU, which may also make the design of MCU diagnosis software complex and the load too high.

In view of this, the present disclosure provides a vehicle diagnostic system to meet the system function safety requirement of such multi-core heterogeneous SoC. In some embodiments, the vehicle diagnosis scheme disclosed by the disclosure can meet the requirements of rapidly deploying the vehicle diagnosis system in a plurality of different multi-core heterogeneous SoC scenes, and deploy a plurality of different diagnosis functions as much as possible so as to meet increasingly complex vehicle system diagnosis requirements. Thus, the vehicle diagnostic scheme of the disclosed embodiments introduces a design concept of multi-level diagnostics, distributing diagnostic behavior at a system level to different hardware entities at various levels.

The vehicle diagnostic system in the embodiment of the present disclosure is implemented based on a Service-Oriented Architecture (SOA). The SOA is a component model that splits the different functional units of an application and ties them together through well-defined interfaces and protocols between these services. Because the SOA is implemented based on Remote Procedure Calls (RPCs), which can solve the problem of cross-process or even cross-system communication, services built in various systems based on the SOA can interact in a uniform and universal manner.

FIG. 2 is a schematic deployment diagram of the vehicle diagnostic system and the vehicle chip system diagnosed by the vehicle diagnostic system. As shown in the figure, the vehicle on-chip system that needs to be diagnosed in the present disclosure includes an SoC (Micro Controller Unit) and an MCU (Micro Controller Unit). The SoC may have one or more chips, each SoC includes several processing cores, and an operating system is run on each processing core (depending on the actual scene, an operating system may be run on one processing core, or multiple operating systems may be run on one processing core (for example, multiple operating systems are installed by multiple virtual machines, respectively)). Based on the vehicle chip system including the SoC and the MCU, the system can be divided into at least two chip levels (the chip levels are hierarchical relationships between different chips (or processing cores) defined according to management authority between chips). In the diagnostic architecture of the existing vehicle chip system, an MCU belongs to the highest chip level outside the SoC, and such an MCU is generally called an external high-security level MCU and is used to monitor the operating status of each system in the SoC.

In practical applications, the heterogeneous scenarios of the vehicle-mounted chip can be from a hardware platform level, an operating system level, a programming language level or a functional requirement level. The complex heterogeneous scenario brings many adaptation problems to the vehicle fault diagnosis scheme. Therefore, the vehicle diagnostic system in the embodiment of the disclosure divides at least two stages of diagnostic units based on the chip level of the vehicle chip system, and the diagnostic units are respectively disposed on different chip levels of the vehicle chip system. Moreover, a plurality of diagnostic function modules can be configured in each stage of diagnostic unit according to actual requirements (such as different software and hardware types and different application functions). In order to adapt to the multi-core heterogeneous scene, the deployment of the diagnosis function module on different chip levels is realized through configuration files. And the diagnostic function module is used for managing the function data and/or the diagnostic data on the relevant chip level according to the corresponding configuration file. The "related chip level" refers to a chip level involved in executing the corresponding diagnostic function module (e.g., heartbeat monitoring, heartbeat packet messages are periodically sent from a lower chip level to an upper chip level, and the "related chip level" refers to the lower chip level and the upper chip level).

Specifically, the configuration file includes a function permission parameter and/or a diagnosis permission parameter. The functional permission parameter is used for configuring the permissions related to the functional data for the diagnosis functional module, and the diagnosis permission parameter is used for configuring the permissions related to the diagnosis data for the diagnosis functional module. Through the setting of the function permission parameters, the function data of the specific application function can be acquired in the operating system, and the diagnosis of the running state of the specific application function is realized by detecting the function data. By setting the diagnosis permission parameters, the management permission division among different diagnosis units (corresponding to different chip levels) can be realized (a higher diagnosis unit can acquire the diagnosis data of a lower diagnosis unit, and otherwise cannot acquire the diagnosis data), and the layer-by-layer report of the diagnosis information is realized, so that the vehicle diagnosis system can orderly manage the application functions in the system.

The deployment of the diagnostic function module in the embodiment of the disclosure is realized through the SOA, different diagnostic function modules can be regarded as different independent components in the SOA, the independent components can be installed in the vehicle diagnostic system through a uniform component interface, and after the independent components are registered in the vehicle diagnostic system through the configuration file, the corresponding diagnostic function can be realized. The problems of compatibility and adaptation caused by crossing hardware platforms and operating systems are solved, and on-demand deployment and rapid deployment of diagnosis functions are realized.

To further illustrate that the vehicle diagnosis scheme of the present disclosure can be adapted to a plurality of different heterogeneous scenarios, the following description is made for a plurality of SoC scenarios, respectively, and fig. 3 shows a deployment relationship diagram of a vehicle chip scenario applied by the vehicle diagnosis system of the embodiment of the present disclosure.

Referring to fig. 3, a vehicle on-chip system in an embodiment of the disclosure includes an MCU and an SoC, where the SoC includes at least two processing cores, a first processing core of the SoC has a lockstep mechanism, and a virtual machine monitor (Hypervisor, which is used to establish and execute software, firmware, or hardware of a virtual machine) runs on a second processing core, and accordingly, an implementation manner of a vehicle diagnostic system in an embodiment of the disclosure includes:

the vehicle diagnosis system in the embodiment of the disclosure is divided into three stages of diagnosis units, which are respectively as follows from top to bottom according to management authority: the system comprises a vehicle diagnosis unit, a system-on-chip diagnosis unit and a function diagnosis unit.

The functional diagnostic unit is configured to: and diagnosing the running states of all the application functions and the driving functions running in the virtual machines. In the embodiment of the present disclosure, a plurality of virtual machines all run in one operating system (e.g., hypervisor). Moreover, each virtual machine may further include an independent operating system, and each independent operating system is provided with N (N is an integer greater than zero) application functions (e.g., navigation map or video playing) and N driving functions (e.g., driving of a speaker or a microphone). A functional diagnosis agent module may be deployed in each virtual machine, and the functional diagnosis agent module is configured to diagnose an operating state of the deployed virtual machine (including an operating state of each application function and a running state of each driver function), and report diagnostic data to the functional diagnosis unit (since the functional diagnosis unit and each virtual machine operate in the Hypervisor, reporting may be performed in a memory sharing manner). The functional diagnostic agent module configures a corresponding reporting interface for each of the application functions and the driver functions (i.e., can distinguish which application function or driver function is abnormal). By way of example, a diagnostic function within a functional diagnostic unit includes: the device comprises a rationality detection module, a limit detection module, a heartbeat monitoring module, a hardware self-checking module and a plurality of functional diagnosis agent modules. In practical applications, the number and/or types of the diagnostic function modules configured in the diagnostic unit may be determined according to practical requirements, and are only referred to by way of example. As an example, in an embodiment running with Hypervisor, only one functional diagnostic unit may be deployed, and a plurality of functional diagnostic agent modules (corresponding to the number of virtual machines) are deployed in each virtual machine respectively.

The system-on-chip diagnostic unit is configured to: and diagnosing the Hypervisor, and the software and hardware functions running on the first processing core and the running states of all the function diagnosis units. The diagnosis of the Hypervisor and the diagnosis of the software and hardware functions can be realized by subscribing corresponding function data, and the diagnosis of the function diagnosis unit is realized by subscribing the diagnosis data issued by the function diagnosis unit. Since the vehicle diagnostic system in the embodiment of the present disclosure differentiates the hierarchy of the diagnostic units by the acquisition right of the diagnostic data, the system-on-chip diagnostic unit is configured with the right to subscribe to the diagnostic data issued by the functional diagnostic unit through the configuration file. As an example, the system-on-chip diagnostic unit may obtain the diagnostic data issued by the functional diagnostic unit in a Remote Procedure Call (RPC) manner or a shared memory manner. As an example, the diagnostic function module within the system-on-chip diagnostic unit includes: the system comprises a question and answer detection module, a heartbeat detection module, a Hypervisor detection module and a hardware self-checking module. It should be noted that, in a scenario where the Hypervisor runs, the soc diagnostic unit is configured with the Hypervisor detection module.

The vehicle diagnostic unit is configured to: diagnosing the operating status of on-board hardware (e.g., sensors), system-on-chip diagnostic units, and functional diagnostic units. The diagnosis of the vehicle-mounted hardware can be realized by subscribing corresponding functional data, and the diagnosis of the system-on-chip diagnosis unit and the functional diagnosis unit is realized by subscribing the diagnosis data issued by the system-on-chip diagnosis unit and the functional diagnosis unit. Since the vehicle diagnostic system in the embodiment of the present disclosure is a hierarchy that differentiates diagnostic units by the acquisition right of diagnostic data, the vehicle diagnostic unit is configured with a right to subscribe to the diagnostic data issued by the functional diagnostic unit and/or the system-on-chip diagnostic unit through a configuration file. As an example, the MCU may be loaded with a security System (e.g., a security Real Time Operating System (security Real Time Operating System)), and the vehicle diagnosis unit may be installed in the security OS through a software program scheme. By way of example, the vehicle diagnosis unit obtains the diagnosis data issued by the functional diagnosis unit and/or the system-on-chip diagnosis unit through a cross-domain communication mode (e.g., ethernet) of the SOA. As an example, a diagnostic function within a vehicle diagnostic unit includes: the system comprises a voting module, a heartbeat detection module, a monitor diagnosis module and a hardware self-checking module.

In the embodiment of the disclosure, the functional diagnosis unit is disposed in the second processing core of the Soc, the system-on-chip diagnosis unit is disposed in the first processing core of the Soc, and the vehicle diagnosis unit is disposed in the MCU. The first processing core is a processing core with a lockstep mechanism, and the second processing core is a processing core without a lockstep mechanism. The step locking mechanism means that the corresponding processing core is provided with a hardware self-checking module, the same instruction can be periodically executed, the result after the same instruction is executed is compared, and if the result is inconsistent, the abnormal operation is determined. For data security, the upper level diagnostic unit needs to have a more sophisticated security mechanism than the lower level diagnostic unit (i.e., the deployed processing cores have higher level hardware security functions), so the processing core with the lockstep mechanism is selected to deploy the system-on-chip diagnostic unit. Further, the first processing core may also have a security mechanism for memory isolation. Memory isolation refers to storing critical programs and data in isolated memory regions so that the isolated memory regions are not occupied while other programs are running. By way of example, the first processing core may be a Lockstep Dual R core, the second processing core may be an A core, and the Hypervisor operates in the second processing core.

In the embodiment of the disclosure, the functional diagnostic unit may be operated in the Hypervisor as an independent software program, so that the functional diagnostic unit can be software-isolated from an independent operating system on the virtual machine, and the functional diagnostic unit can be ensured to be operated safely and reliably. The functional diagnosis unit and the on-chip system diagnosis unit are isolated by hardware realized by different processing cores, namely, the hardware corresponding to the functional diagnosis unit generates faults, so that the diagnosis function of the on-chip system diagnosis unit is not influenced, and the safety and the reliability of the vehicle diagnosis system are further ensured.

Compared with the longitudinal diagnosis mechanism in a single ECU in fig. 1, the embodiments of the present disclosure adopt a transverse diagnosis mechanism between processing cores (or between chips), so that part of vehicle faults can be repaired in a middle layer diagnosis unit (i.e., a system on chip diagnosis unit), and all vehicle faults do not need to be reported to the MCU, thereby reducing the processing load of the MCU. In addition, each virtual machine is provided with a functional diagnosis agent module which can report the independent abnormal operation, so that the superior diagnosis unit can accurately position the virtual machine corresponding to the abnormal operation, and further can carry out targeted repair operation (such as reset) on the virtual machine with the abnormal operation, thereby avoiding the condition that the full SoC reset is required due to the abnormal operation of individual virtual machines.

Fig. 4 shows a deployment relationship diagram of another vehicle chip scenario to which the vehicle diagnostic system of the embodiment of the disclosure is applied. Referring to fig. 4, a vehicle chip system in an embodiment of the disclosure includes an MCU and an SoC, where the SoC includes a first processing core and at least two second processing cores, and the first processing core has a lockstep mechanism, and correspondingly, another embodiment of a vehicle diagnostic system in an embodiment of the disclosure includes:

The functional diagnostic unit is configured to: and diagnosing the running state of each application function and driving function which run in the operating system provided with the functional diagnosis unit. The operating system 1 in the figure is an operating system corresponding to the deployed system-on-chip diagnostic unit. The operating system 1 runs in the first processing core, and the other operating systems run in the plurality of second processing cores, respectively. Each operating system except the operating system 1 is respectively deployed with a functional diagnosis unit, and N application functions (e.g., navigation map or video playing, etc.) and N driving functions (e.g., driving of a sound box or a microphone, etc.) may be installed in the operating system in which the functional diagnosis unit is deployed. The functional diagnosis unit is provided with a corresponding reporting interface for each application function and driver function (i.e., it is possible to distinguish which application function or driver function is abnormal). By way of example, a diagnostic function within a functional diagnostic unit includes: the device comprises a rationality detection module, a limitation detection module, a heartbeat monitoring module and a hardware self-checking module.

The system-on-chip diagnostic unit is configured to: software and hardware functions running on the first processing core and the running state of each functional diagnosis unit. The diagnosis of the software and hardware functions can be realized by subscribing corresponding functional data, and the diagnosis of the functional diagnosis unit is realized by subscribing the diagnostic data issued by the functional diagnosis unit. By way of example, a diagnostic function within a system-on-chip diagnostic unit includes: the system comprises a question-answer detection module, a heartbeat detection module and a hardware self-checking module. Compared with the embodiment shown in fig. 3, the soc diagnostic unit in the embodiment of the disclosure does not have a Hypervisor detecting module, and other functions are the same as those of the soc diagnostic unit in the embodiment of fig. 3, which are not described herein again.

The vehicle diagnostic unit is configured to: and diagnosing the running states of the on-board hardware (such as a sensor), the on-chip system diagnosis unit and each function diagnosis unit. The diagnostic function implemented by the vehicle diagnostic unit in the embodiment of the present disclosure is the same as that of the vehicle diagnostic unit in the embodiment of fig. 3, and is not described herein again.

In the embodiment of the present disclosure, each operating system except the operating system 1 is respectively deployed with a functional diagnosis unit, and independent operation exception reporting can be performed, so that the upper level diagnosis unit can accurately locate the operating system corresponding to the operation exception, and further can perform targeted repair operation (e.g., reset) on the operating system in which the operation exception occurs, thereby avoiding a situation that the full SoC reset is required due to an individual operating system exception.

Fig. 5 shows a deployment relationship diagram of another vehicle chip scenario to which the vehicle diagnostic system of the embodiment of the disclosure is applied. Referring to fig. 5, a vehicle chip system in an embodiment of the present disclosure includes an MCU and an SoC, where the SoC includes at least two second processing cores, and all the processing cores in the SoC do not have a lockstep mechanism, and correspondingly, another implementation manner of a vehicle diagnostic system in an embodiment of the present disclosure includes:

the vehicle diagnosis system in the embodiment of the disclosure is divided into two stages of diagnosis units, which are respectively as follows from top to bottom according to management authority: a vehicle diagnostic unit and a functional diagnostic unit. Since all processing cores in the SoC do not have a lockstep mechanism, a diagnostic unit that manages all operating systems cannot be deployed within the SoC.

The functional diagnostic unit is configured to: and diagnosing the running state of each application function and driving function which run in the operating system provided with the functional diagnosis unit. Each operating system in the embodiments of the present disclosure is respectively deployed with one functional diagnostic unit, and N application functions (e.g., navigation map or video playing, etc.) and N driver functions (e.g., driver of sound box or microphone, etc.) may be installed in the operating system in which the functional diagnostic unit is deployed. The functional diagnosis unit is provided with a corresponding reporting interface for each application function and driver function (i.e., it is possible to distinguish which application function or driver function is abnormal). Compared with the embodiment shown in fig. 4, the reporting object of the functional diagnostic unit in the embodiment of the present disclosure is only the vehicle diagnostic unit, and other functions are the same as those of the functional diagnostic unit in the embodiment of fig. 4, and are not described herein again.

The vehicle diagnostic unit is configured to: and diagnosing the running states of the on-board hardware (such as a sensor), the on-chip system diagnosis unit and each function diagnosis unit. With respect to the embodiment shown in fig. 4, the vehicle diagnostic unit in the embodiment of the present disclosure does not need to subscribe to the diagnostic data of the system-on-chip diagnostic unit, and other diagnostic functions are the same as those of the vehicle diagnostic unit in the embodiment of fig. 4, and are not described herein again.

Fig. 6 shows a deployment relationship diagram of another vehicle chip scenario to which the vehicle diagnostic system of the embodiment of the disclosure is applied. Referring to fig. 6, a vehicle on-chip system in an embodiment of the present disclosure includes an MCU and at least two socs, each SoC includes at least a first processing core and a second processing core, where the first processing core has a step-locking mechanism, and the second processing core does not have the step-locking mechanism, and correspondingly, another embodiment of a vehicle diagnostic system in an embodiment of the present disclosure includes:

the vehicle diagnosis system in the embodiment of the disclosure is divided into three stages of diagnosis units, which are respectively as follows according to management authority from top to bottom: the system comprises a vehicle diagnosis unit, a system-on-chip diagnosis unit and a function diagnosis unit.

The functional diagnostic unit is configured to: and diagnosing the running state of each application function and driving function running in the operating system provided with the functional diagnosis unit.

The system-on-chip diagnostic unit is configured to: software and hardware functions running on the first processing core and the running state of each functional diagnostic unit.

The vehicle diagnostic unit is configured to: and diagnosing the running states of the on-board hardware (such as sensors), the various on-chip system diagnosis units and the various function diagnosis units.

The diagnostic functions implemented by the functional diagnostic unit, the system-on-chip diagnostic unit, and the vehicle diagnostic unit in the embodiments of the present disclosure are the same as those implemented by the functional diagnostic unit, the system-on-chip diagnostic unit, and the vehicle diagnostic unit in the embodiment of fig. 4, and are not described herein again.

In the embodiment of the disclosure, since the vehicle SoC has at least two socs, and each SoC has the first processing core, each SoC may be configured with one system-on-chip diagnostic unit, so that each SoC may independently manage the diagnostic function inside the SoC.

Taking the vehicle chip system shown in fig. 3 as an example, how each stage of the diagnosis units set the corresponding function permission parameters and diagnosis permission parameters through the configuration file is specifically described below, please refer to fig. 7, and fig. 7 is a schematic diagram of the permission for each unit/module to subscribe and publish data in the vehicle diagnosis system of the present disclosure.

In the embodiment of the present disclosure, the data information issued by each unit/module (including the unit/module in the vehicle diagnostic system and the functional module in the virtual machine) carries a theme flag, such as a functional theme (function topics) and a diagnostic theme (diagnostic topics), and the relevant functional data (function data) and diagnostic data (diagnostic data) can be obtained (or extracted) only when the corresponding subscription authority is configured. In the embodiment of the disclosure, the corresponding authority is configured for the diagnosis function module in the diagnosis unit through the function authority parameter and the diagnosis authority parameter in the configuration file. Wherein, the function authority parameter includes: subscribing to the functional data authority and publishing the functional data authority; the diagnosis authority parameters comprise: subscribing to diagnostic data rights and publishing diagnostic data rights. The functional data authority also distinguishes different application functions, driving functions and vehicle-mounted hardware functions, and various functional data correspond to unique subscription/publishing authority.

The arrows in fig. 7 pointing to the topics by the units/modules represent published data and the arrows pointing to the units/modules by the topics represent subscribed data, as shown in fig. 7:

the functional diagnosis agent module in the functional diagnosis unit configures the subscription functional data authority (subscription function data) and the publication diagnostic data authority (publication diagnostic data) through a configuration file.

The function diagnosis unit configures the subscription function data authority (subscription function data), the subscription diagnosis data authority (subscription diagnosis data) and the publication diagnosis data authority (publication diagnosis data) through a configuration file.

The system-on-chip diagnosis unit configures the subscription function data authority (subscription function data), the publishing function data authority (publishing function data) and the publishing diagnosis data authority (publishing diagnostic data) through a configuration file.

The vehicle diagnosis unit configures the subscription function data authority (subscription function data), the distribution function data authority (distribution function data), the subscription diagnosis data authority (subscription diagnosis data), and the distribution diagnosis data authority (distribution diagnosis data) with a configuration file.

In the embodiment of the disclosure, since the function topics and the diagnostic topics are separated, the safety of the functional data and the diagnostic data is ensured, and convenience is provided for the whole diagnostic framework to be transplanted into different heterogeneous environments.

As an example, the following gives a code for configuring the corresponding rights in a configuration file:

in the code of the above-described configuration file, "L1 functional diagnosis" indicates a functional diagnosis unit, "component" rationality detection "indicates that the constituent diagnostic function modules include a rationality detection module," script camera0_ data "indicates function data of the subscription camera0, and" publish diag0 "indicates diagnostic data of the publication reference number 0 (e.g., a reference number of the functional diagnosis unit). The "L2SOC diagnosis" indicates a system-on-chip diagnosis unit, the "subscribe data1" indicates the function data of the subscription number 1, and the "publish diag1" indicates the diagnosis data of the publication number 1 (e.g., the number of the system-on-chip diagnosis unit). "L3 vehicle diagnosis" denotes a vehicle diagnosis unit.

After configuring the corresponding authority through the configuration file, the diagnosis units at each level can respectively execute corresponding subscription/release operations, specifically:

the diagnostic function module of the functional diagnostic unit is configured to: subscribing corresponding functional data according to the authority configured by the configuration file; and determining and issuing corresponding diagnostic data according to the functional data subscribed by the functional diagnostic unit. As an example: after acquiring the relevant function data, the functional diagnosis unit updates a corresponding application function state (i.e., one of the diagnosis data issued by the functional diagnosis unit) according to the function data, and issues the application function state through a message carrying a diagnosis subject flag bit, where the application function state includes: application function is normal or application function is abnormal.

The diagnostic function module of the system-on-chip diagnostic unit is configured to: and according to the function data and/or the diagnosis data subscribed by the system-on-chip diagnosis unit, determining and publishing the corresponding diagnosis data. As an example: the on-chip system diagnosis unit subscribes functional data corresponding to the virtual machine monitor, updates the monitor state (namely, one kind of diagnosis data issued by the on-chip system diagnosis unit) after the functional data corresponding to the virtual machine monitor, and issues the monitor state through a message carrying a diagnosis subject flag bit, wherein the monitor state comprises: monitor normal or monitor abnormal. As an example: the system-on-chip diagnosis unit also subscribes the diagnosis data issued by the functional diagnosis unit and updates the diagnosis state of the system-on-chip diagnosis unit according to the diagnosis data issued by the functional diagnosis unit; the diagnostic state of the system-on-chip diagnostic unit is issued through a message carrying a diagnostic subject flag bit; wherein the diagnostic state of the system-on-chip diagnostic unit comprises: the system on chip operates normally or abnormally.

The diagnostic function module of the vehicle diagnostic unit is configured to: and according to the subscribed functional data and/or the diagnostic data, determining and issuing the corresponding diagnostic data. As an example: the diagnostic data issued by the vehicle diagnostic unit includes a vehicle diagnostic state, which is a diagnostic state according to the functional diagnostic unit and/or the system-on-chip diagnostic unit (e.g., if any one of the functional diagnostic unit and the system-on-chip diagnostic unit has an abnormal operation, the vehicle diagnostic state is a vehicle operation abnormality). Wherein the vehicle diagnostic status comprises: the vehicle is running normally or the vehicle is running abnormally.

Furthermore, the system-on-chip diagnosis unit and the vehicle diagnosis unit are used as superior diagnosis units, and an abnormal repair strategy for corresponding vehicle faults is preset. Thus, the system-on-chip diagnostic unit is further configured to: and responding to the diagnosis state of any functional diagnosis unit as a functional operation abnormity, and executing a corresponding abnormity repair strategy. The vehicle diagnostic unit is further configured to: and executing a corresponding abnormality repairing strategy in response to the vehicle diagnosis state being vehicle operation abnormality.

The disclosed embodiment also designs a vehicle diagnosis method executed by a vehicle diagnosis system, wherein the vehicle diagnosis system comprises: at least two stages of diagnostic units respectively deployed on different chip levels of the vehicle chip system; the method comprises the following steps:

the diagnostic function module of the superior diagnostic unit manages the function data and/or the diagnostic data of the inferior diagnostic unit according to the configuration authority of the configuration file; the configuration file comprises a function permission parameter and/or a diagnosis permission parameter, the function permission parameter is used for configuring permissions related to function data for the diagnosis function module, and the diagnosis permission parameter is used for configuring permissions related to the diagnosis data for the diagnosis function module.

The above-mentioned upper diagnostic unit and the lower diagnostic unit are relative concepts, and for example, the vehicle diagnostic unit belongs to the upper diagnostic unit relative to the functional diagnostic unit. The system-on-chip diagnosis unit belongs to a superior diagnosis unit relative to the functional diagnosis unit; the vehicle diagnostic unit belongs to a superior diagnostic unit relative to the system-on-chip diagnostic unit. On the contrary, the system-on-chip diagnosis unit belongs to a lower-level diagnosis unit relative to the vehicle diagnosis unit.

To further explain the vehicle diagnostic method in the embodiment of the present disclosure, the vehicle diagnostic method in the embodiment of the present disclosure is described in detail below by taking the vehicle chip system shown in fig. 3 as an example.

FIG. 8 illustrates an exemplary flow chart of a vehicle diagnostic method according to one embodiment of the present disclosure. Referring to fig. 8, an embodiment of a vehicle diagnostic method according to an embodiment of the disclosure includes:

in step S801, the diagnostic function module of the functional diagnostic unit subscribes to corresponding functional data according to the authority configured by the configuration file.

The diagnostic data issued by the functional diagnostic unit includes: an application function state; wherein the application function state comprises: application function is normal or application function is abnormal.

When the functional diagnostic agent module of the functional diagnostic unit acquires that the corresponding functional data is normal through subscribing to the functional data authority (subscription function data), the application functional state locally maintained by the functional diagnostic unit should be FUNTION _ OK (i.e., the application function is normal), otherwise, the application functional state is FUNTION _ ERROR (i.e., the application function is abnormal).

In step S802, the diagnostic function module of the functional diagnostic unit determines and issues corresponding diagnostic data according to the functional data subscribed by the functional diagnostic unit.

As an example, after determining that the application function status is FUNTION _ OK, the functional diagnostic unit may issue an L0_ NO _ ERROR status (i.e., the diagnostic status of the functional diagnostic unit is functional) onto a diag topics (diagnostic topic). After determining that the application function status is FUNTION _ ERROR, the functional diagnostic unit may issue publish L0_ FAULT (i.e., the diagnostic status of the functional diagnostic unit is a functional operation exception) to the diag topics.

In step S803, the diagnostic function module of the system-on-chip diagnostic unit subscribes to the corresponding functional data and/or the diagnostic data issued by the functional diagnostic unit according to the configured authority of the configuration file.

As an example, when the Hypervisor is normal, the Hypervisor state maintained by the system-on-chip diagnostic unit is Hypervisor _ NO _ ERROR (i.e., the monitor state is monitor normal); when the Hypervisor is abnormal, the Hypervisor state maintained by the system-on-chip diagnostic unit is Hypervisor _ FAULT (i.e., the monitor state is a monitor exception).

When the diagnostic data issued by the functional diagnostic unit subscribed by the on-chip system diagnostic unit is L0_ NO _ ERROR (that is, the diagnostic state of the functional diagnostic agent module is normal), determining that the state of the functional diagnostic unit maintained by the on-chip system diagnostic unit is SOC _ L1_ NO _ ERROR (that is, the state of the functional diagnostic unit is normal); on the contrary, if the functional diagnostic unit state is L0_ FAULT (i.e., the diagnostic state of the functional diagnostic agent module is abnormal), the functional diagnostic unit state maintained by the system-on-chip diagnostic unit is determined to be SOC _ L1_ ERROR (i.e., the functional diagnostic unit state is abnormal).

In step S804, the diagnostic function module of the system-on-chip diagnostic unit determines and issues corresponding diagnostic data according to the function data and/or diagnostic data subscribed by the system-on-chip diagnostic unit.

The diagnostic data issued by the system-on-chip diagnostic unit comprises at least one of the following: a monitor state, a diagnostic state of a functional diagnostic unit, and a diagnostic state of a system-on-chip diagnostic unit; wherein the monitor state comprises: monitor normal or monitor abnormal; the diagnostic state of the functional diagnostic unit includes: the function operation is normal or abnormal; the diagnostic state of the system-on-chip diagnostic unit includes: the system on chip operates normally or abnormally.

As an example, when the Hypervisor state maintained by the system-on-chip diagnostics unit is HYPERVISOR _ FAULT, HYPERVISOR _ SOC _ ERROR is issued onto the diag topics. When the state maintained by the SOC diagnostic unit is "hyperrisor _ SOC _ ERROR" or "SOC _ L1_ ERROR", the SOC diagnostic unit issues SOC _ ERROR (i.e., the diagnostic state of the SOC diagnostic unit is abnormal operation of the SOC) to the diag topics. On the contrary, when the states maintained by the SOC diagnostic unit are hyperreservoir _ NO _ ERROR and SOC _ L1_ NO _ ERROR, the SOC diagnostic unit issues the SOC _ NO _ ERROR state (i.e. the diagnostic state of the SOC diagnostic unit is that the SOC is operating normally) to the diag topics.

Further, in response to that the diagnosis state of any one functional diagnosis unit is a functional operation abnormality, the system-on-chip diagnosis unit executes a corresponding abnormality repairing policy to repair the corresponding functional operation abnormality.

In step S805, the diagnostic function module of the vehicle diagnostic unit subscribes to the corresponding functional data and/or the diagnostic data issued by the functional diagnostic unit and the system-on-chip diagnostic unit according to the authority configured by the configuration file.

As an example, when the diagnostic data issued by the functional diagnostic unit to which the VEHICLE diagnostic unit is subscribed is L0_ NO _ ERROR and the diagnostic data issued by the system-on-chip diagnostic unit is SOC _ NO _ ERROR, the VEHICLE diagnostic unit determines that the VEHICLE diagnostic status is VEHICLE _ NO _ ERROR (i.e., the VEHICLE is operating normally). Conversely, when the VEHICLE diagnostic unit subscribes to L0_ FAULT or SOC _ ERROR, the VEHICLE diagnostic unit determines that the VEHICLE diagnostic status is VEHICLE _ FAULT (i.e., VEHICLE operation abnormality).

In step S806, the diagnostic function module of the vehicle diagnostic unit determines and issues corresponding diagnostic data according to the functional data and/or diagnostic data subscribed by the vehicle diagnostic unit.

The diagnostic data issued by the vehicle diagnostic unit includes: a vehicle diagnostic status; wherein the vehicle diagnostic status comprises: normal vehicle operation and abnormal vehicle operation.

As an example, when the VEHICLE diagnostic unit determines that the VEHICLE diagnostic status is VEHICLE _ NO _ ERROR (i.e., the VEHICLE is operating properly), the VEHICLE diagnostic unit may issue VEHICLE _ NO _ ERROR onto the diag topics. Conversely, when the VEHICLE diagnostic unit determines that the VEHICLE diagnostic status is VEHICLE _ FAULT, the VEHICLE diagnostic unit may issue VEHICLE _ FAULT onto the diag topics.

Further, in response to the vehicle diagnosis state being a vehicle operation abnormality, the vehicle diagnosis unit may execute a corresponding abnormality repair strategy to repair a corresponding vehicle fault.

In the embodiment of the disclosure, the deployment of the diagnostic function modules of the diagnostic units at each stage is realized through the SOA, the diagnostic function modules can be regarded as independent components in the SOA, the independent components can be installed in the vehicle diagnostic system through a uniform component interface, and after the independent components are registered in the vehicle diagnostic system through the configuration file, the corresponding diagnostic function can be realized. The problems of compatibility and adaptation caused by crossing hardware platforms and operating systems are solved, and the on-demand deployment and the rapid deployment of the diagnosis function are realized.

Correspondingly, the embodiment of the disclosure also provides a vehicle, which comprises a vehicle chip system and the vehicle diagnosis system. For a specific vehicle diagnosis process, reference may be made to the embodiments of the vehicle diagnosis system and the vehicle diagnosis method described above, which are not described herein again.

It is noted that for the sake of brevity, the present disclosure describes some methods and embodiments thereof as a series of acts and combinations thereof, but those skilled in the art will appreciate that the aspects of the present disclosure are not limited by the order of the acts described. Accordingly, one of ordinary skill in the art will appreciate that certain steps may be performed in other sequences or simultaneously, in accordance with the disclosure or teachings of the present disclosure. Further, those skilled in the art will appreciate that the embodiments described in this disclosure are capable of alternative embodiments, in which acts or modules are involved, which are not necessarily required to practice one or more aspects of the disclosure. In addition, the present disclosure also focuses on the description of some embodiments, depending on the solution. In view of the above, those skilled in the art will understand that portions of the disclosure that are not described in detail in one embodiment may also be referred to in the description of other embodiments.

As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, method or computer program product. Thus, the present invention may be embodied in the form of: the term "computer readable medium" as used herein refers to any tangible medium that can contain, store, communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Furthermore, in some embodiments, the invention may also be embodied in the form of a computer program product in one or more computer-readable media having computer-readable program code embodied in the medium.

Any combination of one or more computer-readable media may be employed. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive example) of the computer readable storage medium may include, for example: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

While various embodiments of the present disclosure have been shown and described herein, it will be obvious to those skilled in the art that such embodiments are provided by way of example only. Numerous modifications, changes, and substitutions will occur to those skilled in the art without departing from the spirit and scope of the present disclosure. It should be understood that various alternatives to the embodiments of the disclosure described herein may be employed in practicing the disclosure. It is intended that the following claims define the scope of the disclosure and that equivalents or alternatives within the scope of these claims be covered thereby.

Claims

1. A vehicle diagnostic system for diagnosing a vehicle chip system, comprising:

at least two stages of diagnosis units which are respectively arranged on different chip levels of the vehicle chip system, wherein each stage of diagnosis unit comprises a plurality of diagnosis function modules;

the diagnostic function module is deployed on a corresponding chip level through a configuration file, the configuration file comprises a function permission parameter and/or a diagnostic permission parameter, the function permission parameter is used for configuring permissions related to function data for the diagnostic function module, the diagnostic permission parameter is used for configuring permissions related to the diagnostic data for the diagnostic function module, and the diagnostic function module is used for managing the function data and/or the diagnostic data on the related chip level according to the corresponding configuration file.

2. The vehicle diagnostic system of claim 1,

the vehicle chip system includes: the system on chip Soc and the microcontroller MCU; and

the at least two stages of diagnostic units comprise: a function diagnosis unit and a vehicle diagnosis unit;

the functional diagnosis unit is deployed in the Soc, and the vehicle diagnosis unit is deployed in the MCU.

3. The vehicle diagnostic system of claim 2,

the Soc comprises a first processing core and a second processing core; wherein the first processing core has a lockstep mechanism;

the at least two stage diagnostic unit further comprises: a system-on-chip diagnostic unit; the system-on-chip diagnosis unit is deployed in a first processing core of the Soc, and the functional diagnosis unit is at least deployed in a second processing core of the Soc;

the system-on-chip diagnosis unit is configured with the authority for subscribing the diagnosis data issued by the functional diagnosis unit through a configuration file;

and the vehicle diagnosis unit is configured with the authority of subscribing the diagnosis data issued by the function diagnosis unit and/or the on-chip system diagnosis unit through a configuration file.

4. The vehicle diagnostic system of claim 3,

the system-on-chip diagnosis unit acquires the diagnosis data issued by the functional diagnosis unit by a Remote Procedure Call (RPC)/shared memory mode; and/or

And the vehicle diagnosis unit obtains the diagnosis data issued by the functional diagnosis unit and/or the on-chip system diagnosis unit in a Service Oriented Architecture (SOA) cross-domain communication mode.

5. The vehicle diagnostic system of claim 3,

a virtual machine monitor runs in the second processing core, and a plurality of virtual machines run in the virtual machine monitor;

the functional diagnosis unit includes: a functional diagnostic agent module; the functional diagnosis agent module is deployed on each virtual machine, configured to diagnose the running state of the virtual machine and report the running state to the functional diagnosis unit;

and the system-on-chip diagnosis unit is also used for monitoring the authority of the running state of the virtual machine monitor through configuration of the configuration file.

6. The vehicle diagnostic system of claim 3,

the function permission parameters comprise: subscribing to the functional data authority and publishing the functional data authority;

the diagnosis authority parameters comprise: a subscribe diagnostic data authority and a publish diagnostic data authority.

7. The vehicle diagnostic system of claim 6, wherein each stage of diagnostic units is configured with at least one of:

the function diagnosis unit configures the subscription function data authority, the subscription diagnosis data authority and the release diagnosis data authority through a configuration file;

the system-on-chip diagnosis unit configures the subscription function data authority, the release function data authority and the release diagnosis data authority through a configuration file;

the vehicle diagnosis unit configures the subscription function data authority, the release function data authority, the subscription diagnosis data authority and the release diagnosis data authority through a configuration file.

8. The vehicle diagnostic system of claim 3,

a diagnostic function module of the functional diagnostic unit is configured to: subscribing corresponding functional data according to the authority configured by the configuration file; determining and issuing corresponding diagnostic data according to the functional data subscribed by the functional diagnostic unit;

the diagnostic function module of the system-on-chip diagnostic unit is configured to: subscribing corresponding functional data and/or diagnostic data issued by the functional diagnostic unit according to the authority configured by the configuration file, and determining and issuing the corresponding diagnostic data according to the subscribed functional data and/or diagnostic data of the system-on-chip diagnostic unit;

the diagnostic function module of the vehicle diagnostic unit is configured to: and according to the functional data and/or the diagnostic data subscribed by the vehicle diagnostic unit, determining and publishing the corresponding diagnostic data.

9. The vehicle diagnostic system of claim 8, wherein the diagnostic data is configured by at least one of:

the diagnostic data issued by the functional diagnostic unit comprises: an application function state; wherein the application function state comprises: the application function is normal or abnormal;

the diagnostic data issued by the system-on-chip diagnostic unit comprises at least one of: monitor status, diagnostic status of the functional diagnostic unit, and diagnostic status of the system-on-chip diagnostic unit; wherein the monitor state comprises: monitor normal or monitor abnormal; the diagnostic state of the functional diagnostic unit includes: the function is normal or abnormal; the diagnostic state of the system-on-chip diagnostic unit includes: the system on chip operates normally or abnormally;

10. The vehicle diagnostic system of claim 9,

the system-on-chip diagnostic unit is configured to: responding to the fact that the diagnosis state of any function diagnosis unit is the function operation abnormity, and executing a corresponding abnormity repair strategy; and/or

The vehicle diagnostic unit is configured to: and executing a corresponding abnormality repairing strategy in response to the vehicle diagnosis state being vehicle running abnormality.

11. The vehicle diagnostic system of any one of claims 3 to 10, wherein the diagnostic function is configured with at least one of:

the diagnostic function module deployed in the functional diagnostic unit comprises at least one of: the device comprises a rationality detection module, a limit detection module, a heartbeat monitoring module and a hardware self-checking module;

the diagnostic function module disposed in the vehicle diagnostic unit includes at least one of: the system comprises a question-answer detection module, a heartbeat detection module and a hardware self-checking module;

the diagnosis functional module deployed in the system-on-chip diagnosis unit comprises at least one of the following items: the system comprises a voting module, a heartbeat detection module, a monitor diagnosis module and a hardware self-checking module.

12. A vehicle diagnostic method, characterized by being executed by a vehicle diagnostic system comprising: at least two stages of diagnostic units respectively deployed on different chip levels of the vehicle chip system; the method comprises the following steps:

the diagnostic function module of the superior diagnostic unit manages the function data and/or the diagnostic data of the subordinate diagnostic unit according to the configuration authority of the configuration file;

the configuration file comprises a function permission parameter and/or a diagnosis permission parameter, the function permission parameter is used for configuring permissions related to function data for the diagnosis function module, and the diagnosis permission parameter is used for configuring permissions related to the diagnosis data for the diagnosis function module.

13. The vehicle diagnostic method according to claim 12,

the functional diagnosis unit is deployed in the Soc, the vehicle diagnosis unit is deployed in the MCU, and the vehicle diagnosis unit belongs to a superior diagnosis unit relative to the functional diagnosis unit.

14. The vehicle diagnostic method according to claim 13,

the at least two stages of diagnostic units further comprise: a system-on-chip diagnostic unit; the system-on-chip diagnosis unit is deployed in a first processing core of the Soc, and the functional diagnosis unit is at least deployed in a second processing core of the Soc;

the system-on-chip diagnosis unit belongs to a superior diagnosis unit relative to the functional diagnosis unit; the vehicle diagnosis unit belongs to a superior diagnosis unit relative to the system-on-chip diagnosis unit.

15. The vehicle diagnostic method according to claim 14,

the function permission parameters comprise: subscribing to functional data rights and publishing functional data rights;

16. The vehicle diagnostic method according to claim 15, wherein each stage of the diagnostic units is configured by at least one of:

17. The vehicle diagnosis method according to claim 14, wherein the step of managing the function data and/or the diagnosis data of the lower diagnostic unit according to the authority configured by the configuration file comprises:

the diagnostic function module of the function diagnostic unit subscribes corresponding function data according to the configured authority of the configuration file; determining and issuing corresponding diagnostic data according to the functional data subscribed by the functional diagnostic unit;

the diagnostic function module of the system-on-chip diagnostic unit subscribes corresponding functional data and/or diagnostic data issued by the functional diagnostic unit according to the configured authority of the configuration file, and determines and issues the corresponding diagnostic data according to the subscribed functional data and/or diagnostic data of the system-on-chip diagnostic unit;

and the diagnostic function module of the vehicle diagnostic unit subscribes corresponding functional data and/or diagnostic data issued by the functional diagnostic unit and the on-chip system diagnostic unit according to the configuration authority of the configuration file, and determines and issues the corresponding diagnostic data according to the subscribed functional data and/or diagnostic data of the vehicle diagnostic unit.

18. The vehicle diagnostic method of claim 17, wherein the diagnostic data is configured by at least one of:

the diagnostic data issued by the system-on-chip diagnostic unit comprises at least one of: monitor status, diagnostic status of the functional diagnostic unit, and diagnostic status of the system-on-chip diagnostic unit; wherein the monitor state comprises: monitor normal or monitor abnormal; the diagnostic state of the functional diagnostic unit includes: the function operation is normal or abnormal; the diagnostic state of the system-on-chip diagnostic unit includes: the system on chip operates normally or abnormally;

19. The vehicle diagnostic method of claim 18, further comprising:

the system-on-chip diagnosis unit responds to the fact that the diagnosis state of any function diagnosis unit is abnormal in function operation, and executes a corresponding abnormal recovery strategy; and/or

And the vehicle diagnosis unit responds to the vehicle diagnosis state as vehicle operation abnormity and executes a corresponding abnormity repair strategy.

20. A computer-readable storage medium, characterized in that computer program code of a vehicle diagnostic method is stored, which, when executed, performs the method of any one of claims 12 to 19.

21. A vehicle characterized by comprising a vehicle on-chip system and the vehicle diagnostic system of any one of claims 1 to 11, the vehicle diagnostic system being disposed in the vehicle on-chip system.