Vehicle device information management method and vehicle device information management system

Abstract

The application discloses a vehicle equipment information management method and a vehicle equipment information management system, and belongs to the technical field of vehicles. The method comprises the following steps: when a vehicle is offline, storing an equipment information tree corresponding to a vehicle model of the vehicle; the equipment information tree stores the equipment information of the vehicle in a tree structure, and the tree structure of the equipment information tree is a mapping of the tree structure of a general equipment information tree suitable for all vehicle models; when a communication connection with a server is established, reporting the equipment information tree and a vehicle identifier of the vehicle to the server, so that the server stores the equipment information tree and the vehicle identifier in association. According to the application, the equipment information tree is written when the vehicle is offline, and cloud storage is performed when the vehicle is connected to a network for the first time, and different vehicle models are based on partial mappings of the general equipment information tree, so that the vehicle equipment information of diversified vehicle models can be efficiently and uniformly managed, and the vehicle equipment information plays a core role in subsequent scenes such as remote diagnosis, fault prediction and data analysis.

Description

Technical Field

[0001] This application belongs to the field of vehicle technology, and in particular relates to a vehicle equipment information management method and a vehicle equipment information management system. Background Technology

[0002] In vehicle OEMs (Original Equipment Manufacturers), teams responsible for ECU and system diagnostic design, development, and verification often operate in silos, lacking collaboration. Diagnostic content is not standardized, and data is typically defined in supplier-specific formats. For example, during vehicle production, vehicle-related data is defined and recorded using proprietary formats provided by suppliers, leading to incompatibility between different suppliers' formats. During EoL (Entity Over-Loop) and after-sales phases, manual recording and diagnostics using data from various suppliers are required.

[0003] Therefore, the related technologies suffer from problems of data dispersion, duplication, and fragmentation, making efficient and unified management difficult. Summary of the Invention

[0004] This application aims to address at least one of the technical problems existing in related technologies. To this end, this application proposes a vehicle equipment information management method and a vehicle equipment information management system to achieve efficient and unified management of vehicle equipment information.

[0005] In a first aspect, this application provides a vehicle equipment information management method, applied to a terminal device, the method comprising:

[0006] When a vehicle rolls off the production line, a device information tree corresponding to the vehicle model is stored. The device information tree stores the device information of the vehicle in a tree structure, and the tree structure of the device information tree is a mapping of the tree structure of a universal device information tree that is adapted to all vehicle models.

[0007] When a communication connection is established with the server, the device information tree and the vehicle identifier of the vehicle are reported to the server so that the server can associate and store the device information tree with the vehicle identifier.

[0008] According to the vehicle equipment information management method of this application, by storing the equipment information tree corresponding to the vehicle model when the vehicle is off the production line, the vehicle's equipment information is stored in a structured manner. By using a partial mapping method of a general equipment information tree, the equipment configuration of different vehicle models can be flexibly adapted without the need for special development for different vehicle models, which significantly reduces development costs and the complexity of equipment information management. Furthermore, by reporting the equipment information tree and the vehicle's vehicle identifier to the server when establishing a communication connection with the server, and having the server store the vehicle's equipment information tree, centralized and unified management of vehicle equipment information can be achieved, providing data support for subsequent remote diagnosis, maintenance, and standardized management of the vehicle.

[0009] According to one embodiment of this application, the information category of the device information includes at least a diagnostic questionnaire, which stores at least one service identifier, each service identifier corresponding to a diagnostic service; the method further includes: when a fault event is detected, acquiring fault information associated with the fault event; sending a remote diagnostic request to the server, the remote diagnostic request carrying the fault information and the vehicle identifier, the remote diagnostic request being used to trigger the server to determine a target device information tree based on the vehicle identifier, and to determine a target service identifier based on the target device information tree and the fault information; receiving the target service identifier issued by the server, performing self-diagnosis based on the target service identifier and the locally stored device information tree, and returning the diagnostic result of the self-diagnosis to the server.

[0010] Secondly, this application provides a vehicle equipment information management method, applied to a server, the method comprising:

[0011] When a communication connection is established with a vehicle, the system receives the vehicle identifier and device information tree sent by the vehicle's terminal device, and stores the vehicle identifier and the device information tree together.

[0012] The device information tree is written to the terminal device when the vehicle rolls off the production line. The device information tree stores the vehicle's device information in a tree structure. The tree structure of the device information tree is a mapping of the tree structure of a universal device information tree that is adapted to all vehicle models.

[0013] According to the vehicle equipment information management method of this application, when establishing a communication connection with a vehicle, the receiving terminal device automatically uploads the equipment information tree, achieving cloud storage of the equipment information tree without manual configuration of the server. This enables cloud backup and management of the vehicle's equipment information. Furthermore, since the equipment information tree is based on a partial mapping design of a general equipment information tree, it can adapt to multiple vehicle models without the need for development for specific vehicle types, reducing labor costs and the complexity of data storage and management, and achieving unified management of equipment information for all vehicles. By associating vehicle identifiers with the equipment information tree for storage, the associated equipment information tree can be used for subsequent remote diagnostics, fault prediction, and data analysis, enabling efficient and intelligent vehicle equipment information management.

[0014] According to one embodiment of this application, the method further includes: when a remote diagnostic request is received, extracting the vehicle identifier and fault information carried in the remote diagnostic request; based on the vehicle identifier, determining the target device information tree corresponding to the vehicle from the stored device information trees of each vehicle; based on the target device information tree and the fault information, determining a target service identifier; the target service identifier is used for the terminal device to perform self-diagnosis based on the target service identifier and the device information tree stored in the vehicle to obtain a diagnostic result; sending the target service identifier to the terminal device and receiving the diagnostic result returned by the terminal device.

[0015] Thirdly, this application provides a vehicle equipment information management device, applied to a terminal device, the device comprising:

[0016] The first storage module is used to store the equipment information tree corresponding to the vehicle model when the vehicle rolls off the production line; the equipment information tree stores the equipment information of the vehicle in a tree structure, and the tree structure of the equipment information tree is a mapping of the tree structure of a general equipment information tree adapted to all vehicle models.

[0017] The reporting module is used to report the device information tree and the vehicle identifier of the vehicle to the server when a communication connection is established, so that the server can associate and store the device information tree with the vehicle identifier.

[0018] According to the vehicle equipment information management device of this application, by storing the equipment information tree corresponding to the vehicle model when the vehicle is off the production line, the equipment information of the vehicle is stored in a structured manner. By using a partial mapping method of a general equipment information tree, the equipment configuration of different vehicle models can be flexibly adapted without the need for special development for different vehicle models, which significantly reduces development costs and reduces the complexity of equipment information management. Furthermore, by reporting the equipment information tree and the vehicle identification to the server when establishing a communication connection with the server, and having the server store the vehicle's equipment information tree, centralized and unified management of vehicle equipment information can be achieved, providing data support for subsequent remote diagnosis, maintenance and standardized management of the vehicle.

[0019] Fourthly, this application provides a vehicle equipment information management device, applied to a server, the device comprising:

[0020] The receiving module is used to receive a vehicle identifier and a device information tree sent by the vehicle's terminal device when a communication connection is established with the vehicle; wherein, the device information tree is written to the terminal device when the vehicle is off the production line, the device information tree stores the vehicle's device information in a tree structure, and the tree structure of the device information tree is a mapping of a tree structure of a universal device information tree adapted to all vehicle models.

[0021] The second storage module is used to associate and store the vehicle identifier with the device information tree.

[0022] According to the vehicle equipment information management device of this application, when establishing a communication connection with a vehicle, the receiving terminal device automatically uploads the equipment information tree, achieving cloud storage of the equipment information tree without manual configuration of the server. This enables cloud backup and management of the vehicle's equipment information. Furthermore, since the equipment information tree is based on a partial mapping design of a general equipment information tree, it can adapt to multiple vehicle models without the need for development for specific vehicle models, reducing labor costs and the complexity of data storage and management, and achieving unified management of equipment information for all vehicles. By associating the vehicle identifier with the equipment information tree for storage, the associated equipment information tree can be used for subsequent remote diagnostics, fault prediction, and data analysis, enabling efficient and intelligent vehicle equipment information management.

[0023] Fifthly, this application provides a vehicle equipment information management system, the system comprising off-line inspection equipment, terminal equipment, and a server; wherein:

[0024] The off-line detection device is used to write the device information tree corresponding to the vehicle model of the vehicle into the terminal device when the vehicle is off the line; the tree structure of the device information tree is a mapping of the tree structure of a general device information tree that is adapted to all vehicle models.

[0025] The terminal device is used to report the device information tree and the vehicle identifier of the vehicle to the server when establishing a communication connection with the server;

[0026] The server is configured to receive the device information tree and the vehicle identifier reported by the terminal device, and to associate and store the device information tree and the vehicle identifier together.

[0027] According to the vehicle equipment information management system of this application, the vehicle equipment information tree is written into the terminal device and uploaded to the server through the off-line testing equipment, realizing standardized management of vehicle equipment information and facilitating subsequent maintenance. When the vehicle's equipment information tree changes, the updated equipment information tree can be uploaded to the server in a timely manner through the terminal device, ensuring the real-time and accuracy of the equipment information in the cloud. After the server stores the equipment information tree, it can provide remote diagnostic support when a vehicle malfunctions. Thus, by managing equipment information throughout the entire process from vehicle off-line to actual use through the equipment information tree, the traceability and management efficiency of vehicle equipment information are improved.

[0028] Sixthly, this application provides a vehicle that includes the vehicle equipment information management device as described in the third aspect.

[0029] In a seventh aspect, this application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the vehicle equipment information management method as described in the first aspect or the second aspect above.

[0030] Eighthly, this application provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle equipment information management method as described in the first aspect or the second aspect above.

[0031] Ninthly, this application provides a chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the vehicle equipment information management method as described in the first aspect or the second aspect above.

[0032] In a tenth aspect, this application provides a computer program product, including a computer program that, when executed by a processor, implements the vehicle equipment information management method as described in the first aspect or the second aspect above.

[0033] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0034] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which:

[0035] Figure 1 This is a schematic diagram illustrating an application scenario of the vehicle equipment information management method provided in some embodiments of this application;

[0036] Figure 2 This is a flowchart illustrating the vehicle equipment information management method provided in some embodiments of this application;

[0037] Figure 3 This is a schematic diagram of the structure of the device information tree provided in some embodiments of this application;

[0038] Figure 4 This is a flowchart illustrating the vehicle equipment information management method provided in other embodiments of this application;

[0039] Figure 5 This is a topology diagram of the electrical topology provided in some embodiments of this application;

[0040] Figure 6 This is a topology diagram of the network topology provided in some embodiments of this application;

[0041] Figure 7 This is a schematic diagram of the overall framework of the vehicle equipment information management method provided in some embodiments of this application;

[0042] Figure 8 This is a schematic diagram of the structure of the vehicle equipment information management system provided in some embodiments of this application;

[0043] Figure 9 This is a schematic diagram of the structure of the vehicle equipment information management device provided in some embodiments of this application;

[0044] Figure 10 This is a schematic diagram of the structure of the vehicle equipment information management device provided in some other embodiments of this application;

[0045] Figure 11 This is a schematic diagram of the structure of a computer device provided in some embodiments of this application. Detailed Implementation

[0046] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0047] Unless otherwise defined, all technical and scientific terms used in this application have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used in the description of this application is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms "comprising" and "having," and any variations thereof, in the description, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the description, claims, or accompanying drawings of this application are used to distinguish different objects, not to describe a specific order or hierarchy.

[0048] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application can be combined with other embodiments.

[0049] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the terms "installation," "connection," "linking," and "attachment" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal communication between two components. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0050] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, in this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0051] In this application, "multiple" refers to two or more (including two), and similarly, "multiple groups" refers to two or more (including two), and "multiple pieces" refers to two or more (including two).

[0052] The vehicle's entire lifecycle comprises multiple phases. During the requirements definition and design phase, diagnostic requirements are typically documented in natural language formats within Application Lifecycle Management (ALM) tools. However, this information cannot be automated in subsequent development phases. During development, diagnostic data from ECU specifications is generally documented in vendor-specific proprietary formats. In the validation and verification phase, diagnostic and test data, specifications, and scripts are typically written using vendor-specific tools and data formats. Finally, at the end of vehicle diagnostic development, EoL (Entity Oversight) and after-sales departments typically use this data manually to provide diagnostic solutions.

[0053] In related technologies, data generated at different stages is stored in a scattered manner and the formats are incompatible. This leads to the need to manually call data from different systems when performing maintenance management or fault diagnosis of vehicle equipment information, resulting in low efficiency.

[0054] In view of this, embodiments of this application provide a vehicle equipment information management method, apparatus, and system, etc., which store vehicle equipment information in a structured manner through an equipment information tree. This enables unified storage of data generated by various systems in the vehicle's production process and clearly represents the hierarchical and relational relationships between equipment information. Furthermore, by employing a partial mapping method of a universal equipment information tree, it can flexibly adapt to the equipment configuration of all vehicle models, greatly improving the management efficiency of equipment information. Through association storage with a server, centralized management of vehicle equipment information can be achieved, facilitating subsequent analysis and application. For example, in after-sales scenarios, remote diagnostics can be achieved through the equipment information tree to quickly locate problematic vehicle equipment without requiring the vehicle to return to the factory for repair, thus reducing maintenance costs.

[0055] It should be noted that the vehicles mentioned in the embodiments of this application include, but are not limited to, gasoline vehicles, plug-in hybrid electric vehicles or new energy vehicles, etc., and this application does not make specific limitations in this regard.

[0056] The vehicle equipment information management method provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0057] The vehicle equipment information management method provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, vehicle 101 communicates with server 104 via terminal device 102. Terminal device 102 can be installed on vehicle 101, such as an in-vehicle terminal; or, terminal device 102 can be a computer device that communicates with vehicle 101, such as a user's mobile phone.

[0058] For example, terminal devices include, but are not limited to, one or more of various desktop computers, laptops, smartphones, tablets, in-vehicle terminals, IoT devices, or portable wearable devices. IoT devices may include one or more of smart speakers, smart TVs, smart air conditioners, or smart in-vehicle devices. Portable wearable devices may include one or more of smartwatches, smart bracelets, or head-mounted devices. Servers may be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, and big data and artificial intelligence platforms.

[0059] Among them, the vehicle equipment information management method can be applied to terminal equipment, specifically executed by the hardware or software in the terminal equipment.

[0060] The vehicle equipment information management method provided in this application can be executed by a terminal device or a functional module or entity within the terminal device that can implement the vehicle equipment information management method. The following description uses a terminal device as the executing entity to illustrate the vehicle equipment information management method provided in this application.

[0061] like Figure 2 As shown, the vehicle equipment information management method includes steps 210 to 220.

[0062] Step 210: When a vehicle rolls off the production line, store the equipment information tree corresponding to the vehicle model. The equipment information tree stores the vehicle's equipment information in a tree structure, and the tree structure of the equipment information tree is a mapping of the tree structure of a universal equipment information tree that is adapted to all vehicle models.

[0063] In the context of automobile manufacturing, "vehicle off the production line" refers to the process of removing a vehicle from the assembly line after all manufacturing stages, including production, assembly, and quality inspection. This typically marks the end of the vehicle's manufacturing phase and its transition to delivery, storage, or transportation. Vehicle off the production line signifies that manufacturing is complete and that equipment information is generated and recorded within the production process system.

[0064] Among them, vehicle equipment information refers to detailed data and attributes related to various hardware devices and software modules in the vehicle. Equipment information reflects the specific configuration of the vehicle and the characteristics of its functional components. It is key data in the vehicle's production, use, and maintenance processes, and plays a crucial role in subsequent after-sales service, fault diagnosis, and remote upgrades.

[0065] Equipment information includes various information categories, such as, but not limited to, one or more of the following: equipment attributes, electrical topology, network topology, diagnostic questionnaires, real-time monitoring lists, software information, vehicle models, and vehicle parameters.

[0066] For example, device attributes include, but are not limited to, one or more of the following: device identifier, device model (such as engine model, battery model, sensor model, etc.), supplier information (device manufacturer or supplier information), and specifications (such as physical or functional parameters of the engine or battery). Device identifiers include, but are not limited to, vehicle-specific identifiers such as serial number (SN) and part number. Electrical topology refers to the vehicle's electrical / electronic architecture (EE). Network topology refers to the communication connection structure between various electronic control units (ECUs) within the vehicle, including but not limited to network channels and the ECUs mounted on each channel. The diagnostic questionnaire stores identification information for multiple diagnostic services currently available for the vehicle, and one or more of the following: Diagnostic Trouble Codes (DTCs). These diagnostic service identification information can be used for remote diagnosis in subsequent fault diagnosis scenarios. The real-time monitoring list records abnormal situations that occur during vehicle use, such as fault events or accident events. Understandably, the real-time monitoring list is usually empty when the vehicle rolls off the production line. Subsequently, during vehicle use, when abnormal conditions are detected in real-time, the terminal device records them in the real-time monitoring list. Software information records the version number of the firmware or software installed on the vehicle, a description of the functions implemented by the software, and software-hardware compatibility data (such as operating system version and support for specific vehicle models). The vehicle model represents the physical architecture of the vehicle's equipment, such as the physical relationships between the body, frame, chassis, and wheels, as well as the installation location of the equipment within the vehicle. Vehicle parameters store adjustable parameters of the vehicle's hardware or software, such as the trigger sensitivity of driver assistance systems (e.g., lane keeping assist, automatic braking), power and torque adjustment parameters corresponding to different driving modes (e.g., Eco, Sport, Standard), or Adaptive Cruise Control (ACC) parameters.

[0067] It is readily understood that the device information applicable to the embodiments of this application is not limited to the device information listed above. For example, device information may also include one or more of the following: thermal management loop topology, high / low voltage circuit topology, DBC file, service interface, security authentication information (such as vehicle digital signature or authentication key), and user personalization settings (such as driver preference information). The device information tree can determine and store the appropriate device information category based on the vehicle model information.

[0068] In this embodiment, the vehicle's equipment information is stored in a structured manner in the form of an equipment information tree. The equipment information tree can be viewed as a vehicle equipment information management registry. In some embodiments, the terminal device can receive the equipment information tree sent by the off-line inspection device and store it locally. In other embodiments, the equipment information tree can also be directly written to the vehicle's local storage by the EOL (End of Line) when the vehicle leaves the production line, and the terminal device directly stores the equipment information tree.

[0069] For example, to enhance readability, the device information tree can be described using human-machine readable JSON / XML statements, enabling developers or operations personnel to quickly understand the vehicle's device information and the architectural relationships between them. For instance, the device information tree can be automatically generated as a JSON / XML file and stored using tools.

[0070] Computer equipment (which can be a terminal device or a server) can pre-build a universal device information tree that is compatible with all vehicle models. The tree structure of the device information tree for a particular vehicle model can be the same mapping or a partial mapping of the tree structure of the universal device information tree that is compatible with all vehicle models. That is, the tree structure of the device information tree can be the same as the tree structure of the universal device information tree, or it can be a subtree of the tree structure of the universal device information tree.

[0071] To achieve unified management of vehicle equipment information, the equipment information trees corresponding to different vehicle models are mapped to the same or different tree structures of a general equipment information tree. For example, the tree structure of the equipment information tree TreeA corresponding to vehicle model A corresponds to the A part of the tree structure of the general equipment information tree, while the tree structure of the equipment information tree TreeB corresponding to vehicle model B corresponds to the B part of the tree structure of the general equipment information tree. The tree structures of the A part mapping and the B part mapping can have some overlap.

[0072] Therefore, when a new vehicle model is added, or when the equipment information for a vehicle model is updated or adjusted, it is only necessary to adaptively adjust the corresponding tree structure and then enter the specific equipment information to achieve dynamic updates of the equipment information tree; the same applies to the dynamic updates of the general equipment information tree.

[0073] Therefore, by establishing and maintaining the equipment information tree, it is only necessary to develop once to adapt to various vehicle models, and it is possible to manage equipment information for all vehicles with the built-in equipment information tree, which greatly improves the management efficiency of vehicle equipment.

[0074] Step 220: When a communication connection is established with the server, the device information tree and the vehicle identification are reported to the server so that the server can associate and store the device information tree with the vehicle identification.

[0075] After the vehicle connects to the network, the terminal device initiates a connection request to the server, for example; once the server responds, a communication connection is established. After the terminal device establishes a communication connection with the server, it can report the device information tree stored locally to the server.

[0076] To distinguish between different vehicles, the terminal device also needs to report the vehicle's identification number. Correspondingly, the server associates and stores the vehicle's identification number with its device information tree, for example, using the vehicle identification number as an index to store the device information tree at the location indicated by that index. Thus, the server can store and back up the vehicle's device information tree, obtaining the vehicle's file.

[0077] The vehicle identifier is used to identify a vehicle. For example, the vehicle identifier can be the vehicle identification number (VIN), internal production serial number, or vehicle network ID, etc.

[0078] In some embodiments, the vehicle identifier can be stored in the device information tree (e.g., under the information category of "Device Attributes"), and the terminal device can then report the device information tree to the server.

[0079] The device information tree stored on the server can be used for scenarios such as after-sales maintenance, remote diagnostics, and software upgrades for the vehicle. For example, when a remote software update is required, the server uses the device information tree to determine the modules and compatible versions that need to be updated, improving update efficiency.

[0080] The vehicle equipment information management method provided in this application stores an equipment information tree corresponding to the vehicle model when the vehicle rolls off the production line, thereby structurally storing the vehicle's equipment information. By using a partial mapping method of a general equipment information tree, it can flexibly adapt to the equipment configuration of different vehicle models without the need for special development for different vehicle models, significantly reducing development costs and the complexity of equipment information management. Furthermore, by reporting the equipment information tree and the vehicle's vehicle identifier to the server when establishing a communication connection, and having the server store the vehicle's equipment information tree, it is possible to achieve centralized and unified management of vehicle equipment information, providing data support for subsequent remote diagnosis, maintenance, and standardized management of vehicles.

[0081] The device information tree stores device information in a tree structure, which includes multiple parent nodes, each parent node having at least one child node. In the embodiments of this application, each parent node is used to store an information category of device information, and the child nodes are used to store device information under the information category corresponding to their parent node. Accordingly, when the terminal device stores the device information tree, in some embodiments, storing the device information tree corresponding to the vehicle model includes: for any piece of device information, determining the target parent node corresponding to the target device information based on the information category of the target device information; under the target parent node, determining the target child node to which the target device information is to be stored, and storing the target device information in the target child node.

[0082] Specifically, when storing device information in a tree, for each type of information, the terminal device first determines the target parent node within each parent node. For example, if the device information is torque data in economy mode, the terminal device determines the target parent node as "vehicle parameters," corresponding to the vehicle parameters information category. The terminal device then determines the child nodes corresponding to this device information under the target parent node. For instance, if the parent node of "vehicle parameters" has multiple child nodes corresponding to information categories such as "driving mode" and "driving assistance system," the terminal device determines the target child node as "driving mode." If the "driving mode" child node is further subdivided into "economy mode," "sport mode," and "standard mode" child nodes, the terminal device can, for example, determine "economy mode" as the target child node and then store the device information in that target child node.

[0083] For example, the structure of the device information tree can be as follows: Figure 3As shown in the diagram. Each parent node corresponds to an information category, including "Device Attributes," "Electrical Topology & Network Topology," and "Diagnostic Questionnaire," etc. Each parent node has one or more levels of child nodes. For example, the parent node for "Device Attributes" includes multiple parallel child nodes, each used to store specific attribute information for devices such as batteries and motors. For example, the parent node of "Electrical Topology & Network Topology" includes multiple first-level child nodes and multiple second-level child nodes. First-level child nodes represent different network types, such as "CAN Network" or "ETH Network." Second-level child nodes represent specific device information under various network types. For instance, the second-level child node "CAN 1" indicates that under the CAN or CAN FD type, there are BMS, OBC / DCDC, etc., and the second-level child node "CAN 2" indicates that it has SICC, etc. The second-level child node "ETH 1" under the first-level child node "ETH Network" indicates that under a 1000Mb bandwidth ETH network, there are TBOX, gateway, and SICC, and so on. Similarly, the parent node of "Diagnostic Questionnaire" includes multiple first-level child nodes and multiple second-level child nodes. The first-level child nodes are used to store different diagnostic services and fault codes, such as "ECU Diagnostic Service" and "DTC," etc. The second-level child nodes are used to store the service identifiers of each system under "ECU Diagnostic Service" and the specific information of each fault code under "DTC," etc.

[0084] In the above embodiments, by storing device information in a tree structure and classifying nodes at multiple levels based on information categories, the device information is stored in a structured manner, which can efficiently and flexibly store a large amount of complex device information; subsequently, device information can be quickly located during query and retrieval, improving query and management efficiency.

[0085] As mentioned above, the information categories of device information may include diagnostic questionnaires. Diagnostic questionnaires store at least one service identifier, with each service identifier corresponding to a diagnostic service. For example, service identifier 0x10 stored in the diagnostic questionnaire corresponds to the diagnostic mode control service of the Battery Management System (BMS), service identifier 0x11 corresponds to the ECU reset service, ..., service identifier 0x2F corresponds to the I / O control service, and so on.

[0086] Accordingly, in some embodiments, the vehicle equipment information management method provided in this application further includes: when a fault event is detected, obtaining fault information associated with the fault event; sending a remote diagnostic request to the server, the remote diagnostic request carrying fault information and vehicle identifier, the remote diagnostic request being used to trigger the server to determine the target equipment information tree based on the vehicle identifier, and to determine the target service identifier based on the target equipment information tree and the fault information; receiving the target service identifier issued by the server, performing self-diagnosis based on the target service identifier and the locally stored equipment information tree, and returning the self-diagnosis result to the server.

[0087] When a vehicle is in use and a fault event is detected, such as engine malfunction or braking system failure, the terminal device obtains fault information related to the fault event, such as fault codes or vehicle status information at the time of the fault (e.g., speed, temperature, voltage). Then, the terminal device sends a remote diagnostic request to the server, requesting the server to perform remote diagnostics on the vehicle. To enable the server to locate the current vehicle, the remote diagnostic request carries a vehicle identifier. The server can then determine the corresponding cloud-stored device information tree, called the target device information tree, based on this vehicle identifier. Simultaneously, the terminal device also sends fault information to the server; that is, the remote diagnostic request also carries fault information, allowing the server to determine the specific diagnostic service required for remote diagnosis. Based on the fault information and the stored target device information tree, the server determines the target service identifier from multiple service identifiers stored in the target device information tree. This target service identifier indicates the diagnostic service requiring remote diagnosis, such as ECU service. For example, if the fault information involves sensor malfunction, the target service identifier sent by the server could be "01," which instructs the terminal device to read real-time sensor data. In some embodiments, the operation and maintenance personnel may determine the target service identifier and send it to the terminal device.

[0088] Since the target device information tree pre-stores operation and maintenance related information, such as diagnostic survey forms and service identifiers, DBC files and other configuration information used by operation and maintenance tools, the server can directly perform remote online diagnosis and issue target service identifiers based on the operation and maintenance related information stored in the cloud through software such as online diagnostic instruments.

[0089] Then, the terminal device receives the target service identifier issued by the server, and based on the target service identifier, finds the corresponding diagnostic questionnaire in the device information tree stored locally, executes the corresponding self-diagnosis service, and finally returns the self-diagnosis results to the server for backup or further analysis.

[0090] In the above embodiments, by acquiring fault information and sending a remote diagnostic request when a fault event occurs, the target device information tree can be quickly matched through the vehicle identifier, and the target service identifier related to the fault event can be accurately located, thereby performing targeted remote diagnostics. This achieves rapid and intelligent vehicle fault diagnosis and improves the efficiency and accuracy of remote diagnostics.

[0091] In some embodiments, self-diagnosis is performed based on the target service identifier and the locally stored device information tree, and the diagnostic results of the self-diagnosis are returned to the server. This includes: determining the target diagnostic service corresponding to the target service identifier based on the locally stored device information tree; performing self-diagnosis using the target diagnostic service to obtain diagnostic results, and returning the diagnostic results to the server.

[0092] The target service identifier issued by the server is also obtained from the previously stored device information tree of the vehicle. Therefore, there is a correspondence between this target service identifier and the service identifier stored locally on the terminal device. Based on the received target service identifier, the terminal device can determine the target diagnostic service indicated by the target service identifier by searching the device information tree. For example, if the target service identifier is "0x03", the terminal device locates the engine ECU and determines that the target diagnostic service matching "0x03" is the "read fault code" diagnostic service.

[0093] Then, the terminal device executes the target diagnostic service and parses the diagnostic data into structured information to obtain diagnostic results. For example, the diagnostic results may include, but are not limited to, one or more of the following: a list of fault codes and their detailed descriptions, device operating status, and self-diagnostic execution status (success or failure).

[0094] For example, during local self-diagnosis, the terminal device can execute the diagnostic service pointed to by the target service identifier, collect relevant data, and finally generate a Unified Diagnostic Services (UDS) file as the diagnostic result and send it to the server. This enables the complete recording of vehicle diagnostic data, providing important support for remote maintenance, fault analysis, and data archiving.

[0095] In the above embodiments, the mapping relationship between the device information tree and the target service identifier enables rapid and accurate location of the target device and its supported diagnostic services. Furthermore, by completing diagnostic data collection and preliminary processing locally on the vehicle, remote diagnostic efficiency is improved. By returning diagnostic results, the server can further analyze the root cause of the fault in conjunction with cloud data, optimize the remote diagnostic and fault handling process, and reduce the need for users to visit repair shops.

[0096] By storing service identifiers corresponding to various diagnostic services in a device information tree manner, it is possible to support the expansion and dynamic adaptation of different vehicle configurations, ensuring the universality and accuracy of diagnostic services across diverse vehicle models.

[0097] Due to the complex operating environment of vehicles, the execution of different diagnostic services often requires specific preconditions to be met. For example, some diagnostic services may only be performed when the vehicle is stationary, the engine is off, or a specific temperature range is reached. Failure to verify these preconditions may result in inaccurate diagnostic results or service failure.

[0098] Therefore, in some embodiments, performing a target diagnostic service to perform self-diagnosis to obtain a diagnostic result and returning the diagnostic result to the server includes: obtaining the vehicle's status information and determining whether the preconditions for self-diagnosis are met based on the status information; if the preconditions are met, performing a target diagnostic service to perform self-diagnosis to obtain a diagnostic result and returning the diagnostic result to the server.

[0099] Terminal devices can collect the vehicle's current status information through sensors, including but not limited to one or more of the following: vehicle speed (e.g., whether the vehicle is stationary, i.e., the speed is 0), engine status (e.g., whether the engine is off or running), external environmental conditions (e.g., whether the ambient temperature and battery voltage are within the diagnostic requirements), and diagnostic context information (e.g., whether the vehicle is currently in maintenance mode or diagnostic mode).

[0100] Based on the collected status information, the terminal device can compare it with the preconditions of the target diagnostic service to determine whether the target diagnostic service can be executed. For example, if the target diagnostic service is an airbag module diagnostic service, and its preconditions are "vehicle stationary, engine off," then the terminal device determines whether the vehicle speed is 0 and whether the engine is off. If so, the preconditions are met. If the preconditions are not met, the terminal device terminates the execution of the diagnostic service. In some embodiments, the terminal device can also generate error messages and return them to the server and / or prompt the user.

[0101] Once the prerequisites are met, the terminal device performs specific operations, such as component activation testing or signal detection, and generates and returns diagnostic results. The specific operations corresponding to each diagnostic service can be preset.

[0102] In the above embodiments, by acquiring vehicle status information, dynamically determining whether the preconditions for self-diagnosis are met, avoiding the execution of diagnostic services under unsuitable conditions, and calling the target diagnostic service when the conditions are met, generating accurate diagnostic results and uploading them to the server, the reliability of the diagnostic service execution and the validity of the data can be ensured, ensuring that the collected data has high credibility and providing a reliable basis for subsequent analysis and decision-making.

[0103] Of course, after a fault event is detected, on the one hand, the terminal device can perform remote diagnosis by executing the process in the above embodiments; on the other hand, the terminal device can also update the device information tree based on the acquired fault information.

[0104] To maintain the accuracy and timeliness of vehicle equipment information, dynamic updates of the equipment information tree are particularly important. Especially in remote diagnostics and cloud collaboration, the consistency and timeliness of equipment information are crucial for improving diagnostic efficiency. Therefore, in some embodiments, the vehicle equipment information management method provided in this application further includes: updating the locally stored equipment information tree based on fault information; and sending the fault information and / or the updated equipment information tree to the server, so that the server can update the vehicle's equipment information tree stored in the cloud based on the fault information and / or the updated equipment information tree.

[0105] Based on the fault information, the terminal device locates the target node (including parent and child nodes) in the device information tree, such as locating the "sensor" node in the "real-time monitoring list" to indicate that the sensor has failed, and adds or modifies the stored data under the target node, such as adding the fault information, thereby updating the locally stored device information tree.

[0106] In addition, the terminal device also needs to synchronize and update the device information tree stored in the cloud. The terminal device can send the updated device information tree and / or the fault information to the server to achieve a full or incremental update of the device information tree. Based on the received updated device information tree and / or fault information, the server locates the corresponding target device information tree and performs a full or incremental update. For example, it can directly replace the old device information tree stored in the cloud with the new device information tree received, or merge the newly added or modified nodes into the device information tree stored in the cloud, thereby ensuring the consistency between the device information tree stored in the cloud and the device information tree stored locally in the vehicle.

[0107] In the above embodiments, by synchronously updating the cloud device information tree, the information of cloud devices and local devices is kept consistent at all times, supporting remote diagnosis and collaborative maintenance; and the updated device information tree can provide more accurate reference for subsequent diagnostic services, reduce the possibility of repeated diagnosis, and improve fault handling efficiency.

[0108] Equipment replacement is a common scenario in the daily operation and maintenance of vehicles. After equipment replacement, the relevant equipment information needs to be updated to the vehicle's equipment information tree in a timely manner to ensure that the vehicle's diagnostic and control logic can operate accurately. Therefore, in some embodiments, the vehicle equipment information management method provided in this application further includes: when a new device is detected in the vehicle, obtaining the device information of the new device; updating the locally stored equipment information tree based on the device information of the new device; and sending the device information of the new device and / or the updated equipment information tree to the server, so that the server can update the vehicle's equipment information tree stored in the cloud based on the device information of the new device and / or the updated equipment information tree.

[0109] New equipment in a vehicle can be due to equipment replacement or the addition of new devices. Terminal devices can automatically detect equipment replacement through device scanning mechanisms. For example, the terminal device compares the device serial number with stored device information; if the serial number changes, it determines that the device has been replaced. When a device replacement or new device is detected, the terminal device can collect or read detailed information about the new device, such as device type, model, version, and a list of supported diagnostic services, thus obtaining the new device's equipment information. Then, the terminal device locates the node corresponding to the new device in the device information tree and replaces the information stored in that node, achieving incremental updates to the locally stored device information tree.

[0110] In addition, the terminal device also needs to synchronize and update the device information tree stored in the cloud. The terminal device can send the updated device information tree and / or the device information of the new device to the server to achieve a full or incremental update of the device information tree. Based on the received updated device information tree and / or device information of the new device, the server locates the corresponding target device information tree and performs a full or incremental update to ensure the consistency between the device information tree stored in the cloud and the device information tree stored locally in the vehicle.

[0111] In the above embodiments, by automatically detecting device replacements and automatically acquiring new device information, the vehicle's device information is ensured to remain consistent with the actual configuration. By updating the local device information tree and simultaneously updating the cloud-based device information tree, real-time synchronization and consistency maintenance of device information are achieved. This allows the vehicle to correctly execute diagnostic services based on the latest device information, improving the reliability and accuracy of intelligent vehicle diagnostics. Furthermore, device replacement records and their timestamps are stored in the device information tree, forming complete lifecycle data for the vehicle's devices, providing a basis for future traceability, analysis, and optimization.

[0112] In intelligent vehicle diagnostics and maintenance systems, cloud servers undertake core data management and analysis tasks. To achieve efficient storage and management of vehicle equipment information, the accuracy and scalability of the vehicle equipment information tree are crucial. Therefore, this application also provides a vehicle equipment information management method applied to a server. Figure 4 As shown, the vehicle equipment information management method includes steps 410 to 420. Wherein:

[0113] Step 410: When a communication connection is established with the vehicle, receive the vehicle identifier and device information tree sent by the vehicle's terminal device; wherein, the device information tree is written to the terminal device when the vehicle is off the production line, the device information tree stores the vehicle's device information in a tree structure, and the tree structure of the device information tree is a mapping of the tree structure of a universal device information tree adapted to all vehicle models.

[0114] When a terminal device establishes a communication connection between a vehicle and a server, it initiates a connection request to the server. Once the server responds, the communication connection is established. After establishing the connection with the vehicle, the server listens for data uploaded by the terminal device. This includes the terminal device uploading its locally stored device information tree and the vehicle identifier.

[0115] Step 420: Associate and store the vehicle identifier with the equipment information tree.

[0116] After receiving the vehicle identifier and device information tree, the server can determine whether the device information tree corresponding to the vehicle identifier has already been stored. If the vehicle identifier and device information tree are new data, the server can create a storage location, using the vehicle identifier as an index, and store the device information tree corresponding to the vehicle identifier in the storage location indicated by the index, thereby achieving associative storage of the vehicle identifier and device information tree.

[0117] Understandably, the server can store device information trees for multiple vehicles and distinguish them by vehicle identifiers.

[0118] The vehicle equipment information management method provided in this application automatically uploads the equipment information tree by the receiving terminal device when establishing a communication connection with the vehicle. This eliminates the need for manual server configuration and enables cloud storage of the equipment information tree, achieving cloud backup and management of the vehicle's equipment information. Furthermore, since the equipment information tree is based on a partial mapping design of a general equipment information tree, it can adapt to various vehicle models without requiring development for specific vehicle types. This reduces labor costs and the complexity of data storage and management, achieving unified management of equipment information for all vehicles. By associating vehicle identifiers with the equipment information tree, the associated equipment information tree can be used for subsequent remote diagnostics, fault prediction, and data analysis, enabling efficient and intelligent vehicle equipment information management.

[0119] In an intelligent vehicle remote diagnostic system, the core function of the server is to respond quickly to remote diagnostic requests initiated by terminal devices, combined with the device information tree stored in the cloud, to guide the vehicle's terminal devices to perform self-diagnosis efficiently. Therefore, in some embodiments, the vehicle device information management method provided in this application further includes: when a remote diagnostic request is received, extracting the vehicle identifier and fault information carried in the remote diagnostic request; based on the vehicle identifier, determining the target device information tree corresponding to the vehicle from the stored device information trees of each vehicle; based on the target device information tree and the fault information, determining a target service identifier; the target service identifier is used for the terminal device to perform self-diagnosis based on the target service identifier and the device information tree stored in the vehicle, obtaining diagnostic results; issuing the target service identifier to the terminal device, and receiving the diagnostic results returned by the terminal device.

[0120] When the server receives a remote diagnostic request from a terminal device, it extracts the vehicle identifier and fault information contained therein, and locates the device information tree corresponding to that vehicle based on the vehicle identifier; this is called the target device information tree. For example, the server can search among multiple device information trees stored in the cloud based on the vehicle identifier, and retrieve the device information tree associated with the vehicle identifier as the target device information tree corresponding to that vehicle.

[0121] Then, the server determines the target diagnostic service to be performed based on the fault information from the target device information tree stored in the cloud, and extracts the target service identifier of the target diagnostic service from the target device information tree.

[0122] The server sends the target service identifier to the terminal device. This target service identifier points to a specific diagnostic service for the vehicle to execute. After completing a self-diagnosis based on the target service identifier, the terminal device uploads the diagnostic results to the server. The server then receives the diagnostic results and performs backups or further analysis. In some embodiments, the server can also provide the diagnostic results to maintenance personnel for further diagnostics, etc.

[0123] In the above embodiments, by accurately locating the device information tree corresponding to the vehicle through vehicle identification and extracting target service identifiers related to fault information, remote diagnosis of vehicle faults can be achieved. This eliminates the need for users to drive to a repair shop, improving the efficiency and intelligence of vehicle fault handling and providing users with a more efficient and convenient service experience. Furthermore, the diagnostic results are stored in the cloud system, forming a complete vehicle history record, which helps in subsequent fault analysis and vehicle improvement.

[0124] After a vehicle malfunctions, the vehicle terminal updates its local device information tree based on the fault information and uploads it to the cloud server to ensure that the device information stored in the cloud is consistent with the actual condition of the vehicle. Accordingly, in some embodiments, the vehicle device information management method provided in this application further includes: receiving fault information uploaded by the vehicle and / or the updated device information tree; obtaining the updated device information tree by updating the device information tree stored in the vehicle based on the fault information using the terminal device; and updating the stored vehicle device information tree based on the fault information and / or the updated device information tree.

[0125] When a vehicle malfunction is detected, the terminal device updates the device information tree stored in the vehicle based on the acquired fault information, and then uploads the updated device information tree and / or related fault information. The server receives the fault information and / or the updated device information tree uploaded from the terminal device to perform incremental or full updates to the device information tree stored in the cloud. The specific process is similar to the aforementioned embodiments, and therefore will not be repeated here.

[0126] In some embodiments, when updating the cloud device information tree, the server also performs a consistency check to ensure that the newly uploaded data does not conflict with existing data in the cloud. If a conflict exists, the server will send an error message to the terminal device and request the terminal device to re-upload the data.

[0127] In the above embodiments, the vehicle terminal automatically updates the local device information tree when a fault occurs, and the server synchronously updates the cloud data to ensure the consistency between the in-vehicle device information and the cloud-stored information. The updated device information tree can provide a reliable basis for remote diagnosis and fault analysis, which is conducive to quickly locating the root cause of the fault and improving the efficiency of fault diagnosis.

[0128] As vehicle equipment is replaced or upgraded, the equipment information tree needs to be updated accordingly to ensure that the stored equipment information remains consistent with the actual vehicle configuration. The vehicle terminal can detect equipment replacement in real time and upload the new equipment information, updating the stored equipment information tree through the cloud server, thereby achieving information synchronization and automated equipment management.

[0129] Therefore, in some embodiments, the vehicle equipment information management method provided in this application further includes: receiving equipment information of a new device uploaded by the vehicle; obtaining the equipment information of the new device when the terminal device detects that the vehicle's equipment has been replaced; and updating the stored vehicle equipment information tree based on the equipment information of the new device and / or the updated equipment information tree.

[0130] When equipment is replaced in a vehicle, the vehicle's terminal equipment detects the new equipment information in real time and updates its locally stored equipment information tree. The terminal equipment sends the new equipment information and / or the updated equipment information tree to the server. The server can then perform incremental or full updates to the vehicle's equipment information tree stored in the cloud based on the new equipment information and / or the updated equipment information tree, thereby ensuring the timeliness of cloud data. The specific process is similar to the aforementioned embodiments, and therefore will not be repeated here.

[0131] In some embodiments, when updating the cloud device information tree, the server also performs a consistency check to ensure that the newly uploaded data does not conflict with existing data in the cloud. If a conflict exists, the server will send an error message to the terminal device and request the terminal device to re-upload the data.

[0132] In the above embodiments, the vehicle terminal detects equipment replacement in real time and uploads new equipment information, automatically updating the cloud-based equipment information tree. This achieves dynamic synchronous updates of the equipment information tree, enhances data consistency, facilitates subsequent remote diagnosis, maintenance, and management, and provides reliable data support for remote diagnosis.

[0133] In some embodiments, the device information tree stored on the server can provide a visual representation for operations and maintenance personnel. For example, based on specific device information under the electrical topology information category in the device information tree, the server can generate a visual schematic diagram of the electronic and electrical architecture, such as... Figure 5 As shown, Figure 5 The diagram illustrates the electrical topology relationships between various computing units and devices within the vehicle. For example, the central computing unit is interconnected with the vehicle controller, gateway, vehicle thermal management system, body algorithm, precision computing, OTA diagnostics, health management, and data applications, and is also linked to the water pump and vehicle networking module. The vehicle networking module supports wireless Wi-Fi, Bluetooth, and cellular communication. The central computing unit can be associated with the air conditioning controller, electric compressor, body controller, and low-speed alarm, while the body controller includes the steering wheel switch, logo light, and sunlight sensor. The central computing unit can also be connected to electric power steering, vehicle stability control, electro-hydraulic braking, and airbags. Furthermore, it can be linked to the high-voltage distribution module, motor controller, and high-voltage battery module. Additionally, the central computing unit can be connected to the intelligent cockpit module and intelligent driving domain control, with the intelligent cockpit module including the instrument panel and central control screen.

[0134] For example, based on specific device information under network topology information categories in the device information tree, the server can generate and visualize network topology diagrams, such as... Figure 6 As shown, Figure 6This demonstrates the network wiring and communication topology between various devices within the vehicle. For example, the vehicle network topology includes CAN and ETH networks. The CAN network comprises multiple networks, such as the powertrain communication network, chassis system communication network, and cockpit system communication network. Each system's communication network is further connected to multiple systems via electronic control units. For instance, the powertrain's CAN network is connected to the central controller, battery management system, on-board charger, DC-DC converter, motor control power supply, and so on. Therefore, by visualizing the device information tree, maintenance personnel can quickly and intuitively understand vehicle information, improving the efficiency of subsequent remote diagnostics, maintenance management, and R&D upgrades.

[0135] In a specific embodiment, such as Figure 7 As shown, when a vehicle rolls off the production line, the terminal device stores a device information tree written by the off-line inspection device. This device information tree includes, but is not limited to, device attributes, electrical topology, network topology, diagnostic survey forms, and DBC files. The vehicle's terminal device can update and maintain this device information tree locally. Furthermore, when establishing a communication connection with the server, the terminal device uploads the latest version of the locally stored device information tree, or an incremental portion, to the server for synchronous updates. Because each vehicle has a unified built-in device information tree, and the tree structure of the device information trees for different vehicle models is a mapping of the general device information tree structure, unified management of device information for various vehicle models and types is achieved.

[0136] When a vehicle malfunctions, the system can quickly and accurately retrieve the vehicle's internal configuration information based on the device information tree stored locally or in the cloud. This allows for a clear understanding of the vehicle's network relationships and the connections between devices, facilitating accurate problem localization and improving fault diagnosis and resolution efficiency. Furthermore, for each vehicle model, there's no need for customized integration with the Manufacturing Execution System (MES), saving manpower. Even with subsequent updates to vehicle models and equipment, the system can dynamically synchronize and update both offline and online device information trees, enabling intelligent and efficient management of device information.

[0137] For example, the device information tree can be described using human-machine readable JSON / XML statements, such as those used to describe the network topology of the powertrain system and related electronic control units (ECUs):

[0138] {"network":{

[0139] "CANs":[

[0140] {

[0141] "CANid":"1",

[0142] "type":"CAN",

[0143] "alias":"Power",

[0144] "ECUs":["CCU","BMS","OBC","DCDC","MCU"]}]

[0145] Based on the same inventive concept, embodiments of this application also provide a vehicle equipment information management system for achieving efficient and unified management of vehicle equipment information. For example... Figure 8 As shown, the system includes an offline detection device 801, a terminal device 802, and a server 803.

[0146] The offline testing device 801 is used to write the device information tree corresponding to the vehicle model into the terminal device when the vehicle is off the production line; the tree structure of the device information tree is a mapping of the tree structure of a universal device information tree that is adapted to all vehicle models.

[0147] Terminal device 802 is used to report the device information tree and the vehicle identification of the vehicle to the server when a communication connection is established with the server.

[0148] Server 803 is used to receive the device information tree and vehicle identifier reported by the terminal device, and to associate and store the device information tree and vehicle identifier.

[0149] The off-line inspection equipment is located at the end of the vehicle production line and is used to write the vehicle equipment information tree when the vehicle is about to leave the factory (off-line). In this embodiment, the off-line inspection equipment extracts a portion of the tree structure adapted to the vehicle model from the general equipment information tree, generates the vehicle's equipment information tree, and writes the generated equipment information tree to the vehicle's terminal device, such as an in-vehicle terminal. The terminal device then reports the vehicle identifier and equipment information tree when the vehicle establishes a communication connection with the server. The server is used to centrally store and manage the equipment information trees and related vehicle identifiers for each vehicle. That is, after the server establishes a communication connection with the terminal device, it receives the equipment information tree and vehicle identifier reported by the terminal device and stores the equipment information tree and vehicle identifier together. The specific process can be referred to the aforementioned embodiment, so it will not be repeated here.

[0150] The vehicle equipment information management system provided in this application embodiment writes the vehicle equipment information tree into a terminal device and uploads it to a server through off-line testing equipment, achieving standardized management of vehicle equipment information and facilitating subsequent maintenance. When the vehicle's equipment information tree changes, the updated equipment information tree can be uploaded to the server in a timely manner through the terminal device, ensuring the real-time nature and accuracy of the equipment information in the cloud. After the server stores the equipment information tree, it can provide remote diagnostic support when a vehicle malfunctions. Thus, by managing equipment information throughout the entire process from vehicle off-line production to actual use through the equipment information tree, the traceability and management efficiency of vehicle equipment information are improved.

[0151] In some embodiments, the information category of the diagnostic questionnaire is used to store the diagnostic questionnaire, which includes at least one service identifier, each service identifier corresponding to a diagnostic service. The terminal device is further configured to, when a fault event is detected, acquire fault information associated with the fault event; send a remote diagnostic request to the server, the remote diagnostic request carrying fault information and a vehicle identifier; the server is further configured to, based on the vehicle identifier, determine a target device information tree from the stored device information trees of each vehicle, determine a target service identifier based on the target device information tree and the fault information, and issue the target service identifier; the terminal device is further configured to, based on the target service identifier issued by the server and the locally stored device information tree, perform self-diagnosis, and return the self-diagnosis result to the server. The specific process can be referred to the foregoing embodiments and will not be repeated here. Thus, through the collaboration of the terminal device and the server, efficient location and diagnosis of vehicle faults are achieved, providing vehicle users with efficient after-sales support and maintenance services.

[0152] The vehicle equipment information management method provided in this application can be executed by a vehicle equipment information management device. This application uses the example of a vehicle equipment information management device executing the vehicle equipment information management method to illustrate the vehicle equipment information management device provided in this application.

[0153] This application also provides a vehicle equipment information management device, applied to a terminal device. For example... Figure 9 As shown, the vehicle equipment information management device includes a first storage module 901 and a reporting module 902. Wherein:

[0154] The first storage module 901 is used to store the equipment information tree corresponding to the vehicle model when the vehicle rolls off the production line. The equipment information tree stores the vehicle's equipment information in a tree structure, and the tree structure of the equipment information tree is a mapping of the tree structure of a universal equipment information tree that is adapted to all vehicle models.

[0155] The reporting module 902 is used to report the device information tree and the vehicle identification of the vehicle to the server when a communication connection is established, so that the server can associate and store the device information tree with the vehicle identification.

[0156] According to the vehicle equipment information management device provided in this application embodiment, by storing the equipment information tree corresponding to the vehicle model when the vehicle is off the production line, the vehicle equipment information is stored in a structured manner. By using a partial mapping method of a general equipment information tree, the equipment configuration of different vehicle models can be flexibly adapted without the need for special development for different vehicle models, which significantly reduces development costs and the complexity of equipment information management. Furthermore, by reporting the equipment information tree and the vehicle identifier to the server when establishing a communication connection with the server, and having the server store the vehicle equipment information tree, centralized and unified management of vehicle equipment information can be achieved, providing data support for subsequent remote diagnosis, maintenance and standardized management of the vehicle.

[0157] In some embodiments, the device information tree includes multiple parent nodes, each parent node including at least one child node; wherein, the parent node is used to store the information category of the device information, and the child node is used to store the device information under the information category corresponding to its parent node; the first storage module is further used to determine, for any device information, a target parent node corresponding to the target device information based on the information category of the target device information; under the target parent node, determine the target child node to which the target device information is to be stored, and store the target device information in the target child node.

[0158] In some embodiments, the information categories of the device information include at least a diagnostic questionnaire, which stores at least one service identifier, each service identifier corresponding to a diagnostic service; the apparatus further includes a first diagnostic module, configured to, when a fault event is detected, acquire fault information associated with the fault event; send a remote diagnostic request to the server, the remote diagnostic request carrying fault information and a vehicle identifier, the remote diagnostic request being used to trigger the server to determine a target device information tree based on the vehicle identifier, and to determine a target service identifier based on the target device information tree and the fault information; receive the target service identifier issued by the server, perform self-diagnosis based on the target service identifier and the locally stored device information tree, and return the diagnostic results of the self-diagnosis to the server.

[0159] In some embodiments, the first diagnostic module is further configured to determine the target diagnostic service corresponding to the target service identifier based on the device information tree stored locally; perform self-diagnosis of the target diagnostic service to obtain diagnostic results, and return the diagnostic results to the server.

[0160] In some embodiments, the first diagnostic module is further configured to acquire vehicle status information and determine whether the preconditions for self-diagnosis are met based on the status information; if the preconditions are met, the target diagnostic service is executed to perform self-diagnosis to obtain diagnostic results, and the diagnostic results are returned to the server.

[0161] In some embodiments, the above apparatus further includes a first update module, configured to update the locally stored device information tree based on fault information; and send the fault information and / or the updated device information tree to the server so that the server can update the vehicle's device information tree stored in the cloud based on the fault information and / or the updated device information tree.

[0162] In some embodiments, the first update module is further configured to, when a new device is detected in the vehicle, obtain device information of the new device; update the device information tree stored locally based on the device information of the new device; and send the device information of the new device and / or the updated device information tree to the server so that the server can update the vehicle's device information tree stored in the cloud based on the device information of the new device and / or the updated device information tree.

[0163] This application also provides a vehicle equipment information management device, applied to a terminal device. For example... Figure 10 As shown, the vehicle equipment information management device includes a receiving module 1001 and a second storage module 1002. Wherein:

[0164] The receiving module 1001 is used to receive the vehicle identifier and device information tree sent by the vehicle's terminal device when a communication connection is established with the vehicle; wherein, the device information tree is written to the terminal device when the vehicle is off the production line, the device information tree stores the vehicle's device information in a tree structure, and the tree structure of the device information tree is a mapping of the tree structure of a universal device information tree adapted to all vehicle models.

[0165] The second storage module 1002 is used to associate and store vehicle identifiers with the device information tree.

[0166] According to the vehicle equipment information management device provided in this application embodiment, when establishing a communication connection with a vehicle, the receiving terminal device automatically uploads the equipment information tree, eliminating the need for manual server configuration. This enables cloud storage of the equipment information tree, achieving cloud backup and management of the vehicle's equipment information. Furthermore, since the equipment information tree is based on a partial mapping design of a general equipment information tree, it can adapt to various vehicle models without requiring development for specific vehicle types. This reduces labor costs and the complexity of data storage and management, achieving unified management of equipment information for all vehicles. By associating vehicle identifiers with the equipment information tree for storage, the associated equipment information tree can be used for subsequent remote diagnostics, fault prediction, and data analysis, enabling efficient and intelligent vehicle equipment information management.

[0167] In some embodiments, the above-described apparatus further includes a second diagnostic module, configured to, upon receiving a remote diagnostic request, extract the vehicle identifier and fault information carried in the remote diagnostic request; determine the target device information tree corresponding to the vehicle from the stored device information trees of each vehicle based on the vehicle identifier; determine the target service identifier based on the target device information tree and the fault information; the target service identifier is used for the terminal device to perform self-diagnosis based on the target service identifier and the device information tree stored in the vehicle to obtain a diagnostic result; send the target service identifier to the terminal device and receive the diagnostic result returned by the terminal device.

[0168] In some embodiments, the above-mentioned apparatus further includes a second update module, configured to receive fault information uploaded by the vehicle and / or an updated device information tree; the updated device information tree is obtained by updating the device information tree stored in the vehicle based on the fault information by the terminal device; and the stored device information tree of the vehicle is updated based on the fault information and / or the updated device information tree.

[0169] In some embodiments, the second update module is further configured to receive device information of a new device uploaded by the vehicle; the device information of the new device is obtained when the terminal device detects that the vehicle's device has been replaced; and the stored device information tree of the vehicle is updated based on the device information of the new device and / or the updated device information tree.

[0170] The vehicle equipment information management device in this application embodiment can be a computer device or a component of a computer device, such as an integrated circuit or a chip. The computer device can be a terminal device or a server. For example, the computer device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle computer device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0171] This application embodiment also provides a vehicle, the vehicle including as follows: Figure 9The vehicle equipment information management device shown.

[0172] The vehicle equipment information management device in this application embodiment can be a device with an operating system. This operating system can be a Microsoft (Windows) operating system, an Android operating system, an iOS operating system, or other possible operating systems; this application embodiment does not specifically limit it.

[0173] The vehicle equipment information management device for terminal devices provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0174] The vehicle equipment information management device for server provided in this application embodiment can achieve... Figure 4 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0175] In some embodiments, such as Figure 11 As shown, this application embodiment also provides a computer device 1100, including a processor 1101, a memory 1102, and a computer program stored in the memory 1102 and executable on the processor 1101. When the program is executed by the processor 1101, it implements the various processes of the above-described method embodiments and can achieve the same technical effects. To avoid repetition, it will not be described again here.

[0176] It should be noted that the computer devices in this application embodiment include the mobile computer devices and non-mobile computer devices described above.

[0177] This application also provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described vehicle equipment information management method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0178] The processor is the processor in the computer device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0179] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described vehicle equipment information management method.

[0180] The processor is the processor in the computer device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0181] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described vehicle equipment information management method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0182] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0183] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0184] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the related technology, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0185] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0186] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0187] Unless otherwise specified, all embodiments and optional embodiments of this application can be combined to form new technical solutions.

[0188] Unless otherwise specified, all technical features and optional technical features of this application may be combined to form new technical solutions.

[0189] Unless otherwise specified, all steps of this application may be performed sequentially or randomly, preferably sequentially. For example, the method includes steps (a) and (b), indicating that the method may include steps (a) and (b) performed sequentially, or it may include steps (b) and (a) performed sequentially. For example, the mention that the method may also include step (c) indicates that step (c) may be added to the method in any order; for example, the method may include steps (a), (b), and (c), or it may include steps (a), (c), and (b), or it may include steps (c), (a), and (b), etc.

[0190] The above are merely preferred embodiments of this application and are not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for managing vehicle equipment information, characterized in that, Applied to a terminal device, the method includes: When a vehicle rolls off the production line, a device information tree corresponding to the vehicle model is stored. The device information tree stores the device information of the vehicle in a tree structure, and the tree structure of the device information tree is a mapping of the tree structure of a universal device information tree that is adapted to all vehicle models. When a communication connection is established with the server, the device information tree and the vehicle identifier of the vehicle are reported to the server so that the server can associate and store the device information tree with the vehicle identifier.

2. The method according to claim 1, characterized in that, The device information tree includes multiple parent nodes, each parent node including at least one child node; wherein, the parent node is used to store the information category of the device information, and the child node is used to store the device information under the information category corresponding to its parent node; the device information tree storing the vehicle model corresponding to the vehicle includes: For any given device information, determine the target parent node corresponding to the device information based on the information category described in the device information. Under the target parent node, determine the target child node where the target device information is to be stored, and store the target device information in the target child node.

3. The method according to claim 1 or 2, characterized in that, The device information categories include at least a diagnostic questionnaire, which stores at least one service identifier, each service identifier corresponding to a diagnostic service; the method further includes: When a fault event is detected, obtain the fault information associated with the fault event; A remote diagnostic request is sent to the server. The remote diagnostic request carries the fault information and the vehicle identifier. The remote diagnostic request is used to trigger the server to determine the target device information tree based on the vehicle identifier, and to determine the target service identifier based on the target device information tree and the fault information. The system receives the target service identifier issued by the server, performs self-diagnosis based on the target service identifier and the locally stored device information tree, and returns the self-diagnosis results to the server.

4. The method according to any one of claims 1 to 3, characterized in that, The self-diagnosis based on the target service identifier and the locally stored device information tree, and the return of the self-diagnosis results to the server, includes: Based on the device information tree stored locally, determine the target diagnostic service corresponding to the target service identifier; The target diagnostic service is executed to perform a self-diagnosis to obtain a diagnostic result, and the diagnostic result is returned to the server.

5. The method according to any one of claims 1 to 4, characterized in that, The step of performing self-diagnosis using the target diagnostic service to obtain diagnostic results and returning the diagnostic results to the server includes: Obtain the vehicle's status information and determine whether the preconditions for self-diagnosis are met based on the status information; If the aforementioned prerequisites are met, the target diagnostic service is executed to perform self-diagnosis, obtain diagnostic results, and return the diagnostic results to the server.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Based on the fault information, update the locally stored device information tree; The fault information and / or the updated device information tree are sent to the server so that the server can update the device information tree of the vehicle stored in the cloud based on the fault information and / or the updated device information tree.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: When a new device is detected in the vehicle, the device information of the new device is obtained; Update the locally stored device information tree based on the device information of the new device; Send the device information of the new device and / or the updated device information tree to the server so that the server can update the device information tree of the vehicle stored in the cloud based on the device information of the new device and / or the updated device information tree.

8. A method for managing vehicle equipment information, characterized in that, Applied to a server, the method includes: When a communication connection is established with a vehicle, the vehicle identifier and device information tree sent by the vehicle's terminal device are received; wherein, the device information tree is written to the terminal device when the vehicle is off the production line, the device information tree stores the vehicle's device information in a tree structure, and the tree structure of the device information tree is a mapping of a tree structure of a universal device information tree adapted to all vehicle models. The vehicle identifier is associated with and stored in the device information tree.

9. The method according to claim 8, characterized in that, The method further includes: When a remote diagnostic request is received, the vehicle identification and fault information carried in the remote diagnostic request are extracted; Based on the vehicle identifier, the target device information tree corresponding to the vehicle is determined from the stored device information trees of each vehicle; Based on the target device information tree and the fault information, a target service identifier is determined; the target service identifier is used by the terminal device to perform self-diagnosis based on the target service identifier and the device information tree stored in the vehicle, and obtain a diagnostic result; The target service identifier is sent to the terminal device, and the diagnostic results returned by the terminal device are received.

10. The method according to claim 8 or 9, characterized in that, The method further includes: The system receives fault information uploaded by the vehicle and / or an updated device information tree; the updated device information tree is obtained by updating the device information tree stored in the vehicle based on the fault information using the terminal device. Based on the fault information and / or the updated device information tree, update the stored device information tree of the vehicle.

11. The method according to any one of claims 8 to 10, characterized in that, The method further includes: Receive device information of a new device uploaded by the vehicle; the device information of the new device is obtained when the terminal device detects that the device of the vehicle has been replaced. Update the stored device information tree of the vehicle based on the device information of the new device and / or the updated device information tree.

12. A vehicle equipment information management device, characterized in that, The device includes: The first storage module is used to store the equipment information tree corresponding to the vehicle model when the vehicle rolls off the production line; the equipment information tree stores the equipment information of the vehicle in a tree structure, and the tree structure of the equipment information tree is a mapping of the tree structure of a general equipment information tree adapted to all vehicle models. The reporting module is used to report the device information tree and the vehicle identifier of the vehicle to the server when a communication connection is established, so that the server can associate and store the device information tree with the vehicle identifier.

13. A vehicle equipment information management device, characterized in that, The device includes: The receiving module is used to receive a vehicle identifier and a device information tree sent by the vehicle's terminal device when a communication connection is established with the vehicle; wherein, the device information tree is written to the terminal device when the vehicle is off the production line, the device information tree stores the vehicle's device information in a tree structure, and the tree structure of the device information tree is a mapping of a tree structure of a universal device information tree adapted to all vehicle models. The second storage module is used to associate and store the vehicle identifier with the device information tree.

14. A vehicle equipment information management system, characterized in that, The system includes offline testing equipment, terminal equipment, and a server; wherein: The off-line detection device is used to write the device information tree corresponding to the vehicle model of the vehicle into the terminal device when the vehicle is off the line; the tree structure of the device information tree is a mapping of the tree structure of a general device information tree that is adapted to all vehicle models. The terminal device is used to report the device information tree and the vehicle identifier of the vehicle to the server when establishing a communication connection with the server; The server is configured to receive the device information tree and the vehicle identifier reported by the terminal device, and to associate and store the device information tree and the vehicle identifier together.

15. The system according to claim 14, characterized in that, The information category of the diagnostic questionnaire is used to store the diagnostic questionnaire, which includes at least one service identifier, each service identifier corresponding to a diagnostic service; The terminal device is further configured to, when a fault event is detected, acquire fault information associated with the fault event; and send a remote diagnostic request to the server, the remote diagnostic request carrying the fault information and the vehicle identifier; The server is further configured to determine a target device information tree from the stored device information trees of each vehicle based on the vehicle identifier, determine a target service identifier based on the target device information tree and the fault information, and issue the target service identifier. The terminal device is also used to perform self-diagnosis based on the target service identifier issued by the server and the device information tree stored locally, and to return the self-diagnosis results to the server.

16. A vehicle, characterized in that, The vehicle includes the vehicle equipment information management device as described in claim 12.

17. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the vehicle equipment information management method as described in any one of claims 1-11.

18. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the vehicle equipment information management method as described in any one of claims 1-11.

19. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the vehicle equipment information management method as described in any one of claims 1-11.

Images