Data format conversion method and device, sovd server and vehicle

Abstract

The application relates to a data format conversion method and device, an SOVD server and a vehicle. The method is applied to an SOVD server on the vehicle and comprises the following steps: when receiving diagnosis-related data, extracting identification information from the diagnosis-related data; according to the identification information, searching a first target description file corresponding to the identification information from a first database constructed in advance; wherein the first database stores description files corresponding to each electronic control unit on the vehicle; the description file corresponding to each electronic control unit is used for indicating a conversion rule between an SOVD data format and a non-SOVD data format supported by each electronic control unit; when the first target description file corresponding to the identification information exists, performing format conversion on the diagnosis-related data according to the first target description file to obtain target diagnosis-related data. The method can enable the vehicle control unit to realize fast conversion of SOVD format service diagnosis.

Description

Technical Field

[0001] This application relates to the field of vehicle communication, and in particular to data format conversion methods, devices, SOVD servers, and vehicles. Background Technology

[0002] With the development of vehicle technology, vehicle diagnostics has become increasingly complex, and diagnostic methods have become more diversified. In recent years, diagnostic methods have mainly included in-vehicle diagnostics, local diagnostics, and remote diagnostics. The traditional DoIP (Diagnostics over Internet Protocol) diagnostic method is no longer sufficient to meet current needs. Therefore, international standards organizations have proposed the next-generation diagnostic method SOVD (Service-Oriented Vehicle Diagnostics).

[0003] SOVD is a next-generation automotive diagnostic technology standard designed to address the limitations of traditional UDS (Unified Diagnostic Services) protocols in the era of intelligent connected vehicles. SOVD diagnostics requires both request data and response messages to be organized in JSON Schema format. However, there are situations where the vehicle's ECUs only support traditional UDS (Unified Diagnostic Services) diagnostics. Therefore, how to achieve rapid conversion to SOVD format business diagnostics has become a key research focus. Summary of the Invention

[0004] In view of this, this application provides a data format conversion method, apparatus, SOVD server, and vehicle to achieve rapid conversion of SOVD format business diagnostics for vehicle control units.

[0005] Firstly, this embodiment provides a data format conversion method, which is applied to an SOVD server on a vehicle; the data format conversion method includes:

[0006] Upon receiving diagnostic-related data, identification information is extracted from the diagnostic-related data;

[0007] Based on the identification information, a search is conducted in a pre-built first database to determine if a first target description file corresponding to the identification information exists; wherein, the first database stores description files corresponding to each electronic control unit on the vehicle; the description file corresponding to each electronic control unit is used to indicate the conversion rules between SOVD data format and non-SOVD data formats supported by each electronic control unit;

[0008] When a first target description file corresponding to the identification information exists, the diagnostic-related data is format-converted according to the first target description file to obtain target diagnostic-related data.

[0009] Secondly, this embodiment provides a data format conversion device applied to an SOVD server in a vehicle; the device includes:

[0010] The extraction module is used to extract identification information from the diagnostic-related data when diagnostic-related data is received;

[0011] The database lookup module is used to search a pre-built first database for the existence of a first target description file corresponding to the identification information, based on the identification information; wherein, the first database stores description files corresponding to each electronic control unit on the vehicle; the description files corresponding to each electronic control unit are used to indicate the conversion rules between SOVD data format and non-SOVD data formats supported by the electronic control unit;

[0012] The conversion module is used to convert the format of the diagnosis-related data according to the first target description file when the identification information exists, so as to obtain the target diagnosis-related data.

[0013] Thirdly, this embodiment provides an SOVD server, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the data format conversion method described in the first aspect above.

[0014] Fourthly, this embodiment provides a vehicle that includes the SOVD server described in the third aspect or the data format conversion device described in the second aspect.

[0015] The data format conversion method, apparatus, SOVD server, and vehicle provided in this application store ECU (Electronic Control Unit) description files in a database, effectively modeling and managing the complex relationships between description files and electronic control units. Furthermore, identification information is extracted from diagnostic-related data, and using this identification information as an index, a first target description file associated with the ECU corresponding to the diagnostic-related request is quickly retrieved from the first database. Through this first target description file, conversion rules indicating the conversion between SOVD data format and non-SOVD data formats supported by each electronic control unit are efficiently obtained. Then, through this first target description file, diagnostic-related data is bidirectionally converted between SOVD format and non-SOVD data formats supported by the ECU, thereby achieving efficient and rapid conversion of diagnostic-related data between SOVD and non-SOVD data formats. Attached Figure Description

[0016] Figure 1 A flowchart of an embodiment of the data format conversion method provided in this application;

[0017] Figure 2 This is an application scenario diagram illustrating a data format conversion method as an exemplary embodiment of this application;

[0018] Figure 3 A flowchart of Embodiment 2 of the data format conversion method provided in this application;

[0019] Figure 4 A flowchart of Embodiment 3 of the data format conversion method provided in this application;

[0020] Figure 5 A schematic diagram illustrating the information table of a description document for an exemplary embodiment of this application;

[0021] Figure 6 A flowchart of Embodiment 4 of the data format conversion method provided in this application;

[0022] Figure 7 A flowchart of Embodiment 5 of the data format conversion method provided in this application;

[0023] Figure 8 This is a schematic diagram of an embodiment of the SOVD server provided in this application;

[0024] Figure 9 A flowchart of Example Six of Data Format Conversion Provided for This Application;

[0025] Figure 10 A hardware structure diagram of the SOVD server where the data formatting device provided in this application is located;

[0026] Figure 11This is a schematic diagram of the structure of a data formatting device according to an embodiment of this application. Detailed Implementation

[0027] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application.

[0028] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used herein are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0029] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0030] The following specific embodiments are given to illustrate the technical solution of this application in detail.

[0031] Figure 1 This is a flowchart of an embodiment of the data format conversion method provided in this application. Please refer to... Figure 1 The method provided in this embodiment may include:

[0032] S101. Upon receiving diagnostic-related data, extract identification information from the diagnostic-related data.

[0033] The diagnostic-related data includes diagnostic request data sent by the SOVD client and diagnostic response data returned by the ECU in response to the diagnostic request. Specifically, the diagnostic-related data includes fault codes, data identifiers (DIDs), application logs, and other data.

[0034] The identification information serves as an index to the description file in the first database, with different identification information corresponding to different ECUs. Thus, when the diagnostic-related data is diagnostic request data, the first target description file can be indexed from the first database based on the identification information, and it can also be mapped to the ECU corresponding to the current diagnosis based on the identification information; similarly, when the diagnostic-related data is diagnostic response data, the first target description file can be indexed based on the identification information.

[0035] Optionally, the identification information can be the Component Name (file identifier) ​​of a description file. When the SOVD client sends a diagnostic request, the entity to be diagnosed in the vehicle is determined based on the diagnostic request; the entity to be diagnosed corresponds to one or more electronic control units (ECUs) used to perform the corresponding diagnostic functions; then, through table lookup or mapping, the Component Name associated with the entity to be diagnosed is used as identification information and directly added to the diagnostic request data. For example, after receiving diagnostic-related data, the Component Name field can be extracted from the data as identification information.

[0036] Alternatively, the identification information can be the ECU Address (the second address information of the electronic control unit). For example, when the ECU returns diagnostic response data, the ECU Address field in the diagnostic response data is extracted as the identification information.

[0037] S102. Based on the identification information, search the pre-built first database to see if there is a first target description file corresponding to the identification information; wherein, the first database stores description files corresponding to each electronic control unit on the vehicle; the description file corresponding to each electronic control unit is used to indicate the conversion rules between SOVD data format and non-SOVD data formats supported by each electronic control unit.

[0038] The first database stores description files that correspond one-to-one with all electronic control units (ECUs) of the current vehicle. The conversion rules provided by these description files include encoding rules for SOVD data format, decoding rules for non-SOVD data formats, and conversion formulas required for data conversion. Specifically, the identification information is used as an index for the description files in the first database, and the first target description file is obtained based on this identification information.

[0039] Optionally, each description file is organized in SQLite database format and uses ".db" as the file extension. The filename of the description file can be set to a pre-configured specified string; or it can be composed of the ECU's physical address, the ECU's software part number, and the version information of that software part number. Organizing the description files using the SQLite database format not only effectively manages diagnostic-related data and the complex many-to-many relationships between the description files and the electronic control unit, but also significantly reduces the overall storage space occupied by the database due to its lightweight and embedded characteristics.

[0040] The conversion rules provided by the description files in the first database are implemented through a diagnostic request data information table and a diagnostic response data information table, depending on the type of diagnostic-related data. The diagnostic request data information table includes the encoding rules and format information for the requested data, while the diagnostic response data information table includes the decoding rules and format information for the response data. The encoding and decoding rules are set independently for different electronic control units (ECUs). The diagnostic request data format information is used to indicate to the SOVD server the data format to be used when diagnostic-related data is used as request data; the diagnostic response data format information is used to indicate to the SOVD server the data format to be used when diagnostic-related data is used as response data.

[0041] S103. When a first target description file corresponding to the identification information exists, the format of the diagnostic-related data is converted according to the first target description file to obtain the target diagnostic-related data.

[0042] Optionally, diagnostic-related data in non-SOVD data format is decoded according to the decoding rules defined in the first description file; the decoding rules may include information such as data type, byte order, and length; the numerical values ​​involved in the decoded data are converted into engineering values ​​according to the conversion formula defined in the first description file; the conversion formula includes offset, scaling factor, etc.; and the above data is encapsulated into a structured SOVD data format.

[0043] Optionally, the engineering values ​​in the diagnostic-related data in SOVD data format are converted into numerical values ​​recognizable by the ECU according to the conversion formula defined in the first description file; the conversion formula may also include information such as offset and scaling factor; according to the encoding rules defined in the first description file, the above numerical values ​​are encoded into data in a non-SOVD data format, and the encoding rules may include information such as data type, byte order, and length.

[0044] The data format conversion in this embodiment stores the description file of the ECU (Electronic Control Unit) in a database, effectively modeling and managing the complex relationship between the description file and the ECU. By extracting the identification information from the diagnostic data and using the identification information as an index, the first target description file associated with the ECU corresponding to the diagnostic request is quickly retrieved in the first database. Through this first target description file, the diagnostic data is bidirectionally converted between SOVD format and non-SOVD data formats supported by the ECU, thereby achieving efficient and fast conversion of diagnostic data between SOVD and non-SOVD data formats.

[0045] Before introducing the data format conversion method provided in this application, let's briefly describe its application scenarios. Specifically, Figure 2 This diagram illustrates an application scenario of a data format conversion method as shown in an exemplary embodiment of this application. Please refer to... Figure 2 The data format conversion method provided in this application is deployed on an SOVD (Service-Oriented Vehicle Diagnostics) server in a vehicle. Optionally, the SOVD server may include one or more processors and a memory for storing data. The processor may include, but is not limited to, a microprocessor (MCU) or a programmable logic device (FPGA). The memory may be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the data format conversion method in any embodiment of this application. The processor executes various functional applications and data processing by running the computer program stored in the memory, thereby implementing the above-described method. The memory may include high-speed random access memory and may also include non-volatile memory.

[0046] The SOVD server can establish communication connections with both the SOVD client and the on-board electronic control unit (ECU) via a network. The SOVD client can be set up locally in the vehicle (such as in the vehicle's infotainment system or diagnostic interface device) or deployed on a remote terminal (such as a service station diagnostic device or a mobile terminal). The SOVD server can also connect to a cloud server via a communication module to support functions such as remote diagnostics and database updates.

[0047] The data format conversion method provided in this application will be further described below. Specifically, when the first target description file corresponding to the identification information does not exist, Figure 3 A flowchart of Embodiment 2 of the data format conversion method provided in this application; as follows: Figure 3 As shown, the data format conversion method also includes:

[0048] S301. Based on the identification information, search the pre-built second database to see if there is a second target description file corresponding to the identification information; wherein, the second database stores at least one shared description file; each shared description file is a description file corresponding to a type of electronic control unit, used to indicate the conversion rules between SOVD data format and non-SOVD data format supported by that type of electronic control unit.

[0049] The shared description file extracts and describes common information about a class of ECUs in terms of data format, conversion rules, etc., and is used to indicate the conversion rules between the SOVD data format and non-SOVD data formats supported by multiple electronic control units of the current category. Optionally, the shared description files in the second database can cover electronic control units of multiple vehicle models; and each shared description file corresponds to a different electronic control unit. A shared description file can store multiple mapping relationships between identification information and corresponding electronic control units.

[0050] For example, the first database stores description files corresponding to all electronic control units (ECUs) in a specified model of brand A. The first database also stores multiple shared description files, which cover all electronic control units in all models under brand A.

[0051] S302. When a second target description file corresponding to the identification information exists, the format of the diagnostic-related data is converted according to the second target description file to obtain the target diagnostic-related data.

[0052] The method for data format conversion based on the second target description file can be found in the description of data conversion based on the first target description file above, and will not be repeated here.

[0053] When the electronic control unit deployed in the vehicle is upgraded or replaced, but the first database has not been updated in sync, or when the first database is damaged and some description files are missing, there is a possibility that the first target description file corresponding to the identification information cannot be found in the first database.

[0054] To address this issue, this embodiment pre-constructs a second database storing shared description files, with each shared description file in the second database corresponding to a type of electronic control unit (ECU) with common characteristics. By extracting common information about data conversion for this type of ECU from the shared description files, the system can still support format conversion of diagnostic data even when a specific ECU-specific description file is missing from the first database, thereby improving the success rate and compatibility of the diagnostic process.

[0055] Furthermore, when the diagnostic-related data is diagnostic request data and the identification information is the file identifier of the description file; after obtaining the target diagnostic-related data in step S302, the method includes: obtaining a configuration information record table pre-configured for the second database; searching for the third address information corresponding to the file identifier in the configuration information record table; sending the target diagnostic-related data to the third target electronic control unit corresponding to the third address information, so as to instruct the third target electronic control unit to execute the diagnostic request corresponding to the target diagnostic-related data and return diagnostic response data.

[0056] When the diagnostic-related data is diagnostic response data and the identification information is the fourth address information of the electronic control unit that provides feedback diagnostic response data; based on the identification information, search the pre-built second database to see if there is a third target description file corresponding to the identification information, including: obtaining the configuration information record table pre-configured for the second database; searching the configuration information record table for the target file identifier corresponding to the fourth address information; and searching the second database for the third target description file corresponding to the target file identifier.

[0057] The diagnostic data mentioned above includes diagnostic request data sent by the client and diagnostic response data sent by the ECU. The following section explains the different types of diagnostic response data.

[0058] In one embodiment, the diagnostic-related data is diagnostic request data; the identification information is the file identifier of the description file; Figure 4 A flowchart of Embodiment 3 of the data format conversion method provided in this application; as follows: Figure 4 As shown, after converting the format of the diagnostic-related data according to the first target description file, the data format conversion method further includes:

[0059] S401. Obtain the configuration information record table pre-configured for the first database; wherein, the configuration information record table is used to record the correspondence between the file identifier of the description file corresponding to each electronic control unit and the address information of the electronic control unit.

[0060] The configuration information record table can be a pre-configured table or a dynamically generated table after reading and integrating the file identifiers of multiple description files and the address information of the electronic control unit. For example, in addition to indicating the conversion rules between SOVD data format and non-SOVD data formats supported by each electronic control unit, the description files may also record the mapping relationship between the file identifiers of each description file and the address information of the corresponding electronic control unit. In one embodiment, the method for constructing the configuration information record table includes: traversing the information tables of each description file in a first database to obtain the mapping relationship between the file identifiers of each description file and the address information of the electronic control unit corresponding to each scan file; and constructing the configuration information record table based on the mapping relationship between the file identifiers of each description file and the address information of the electronic control unit corresponding to each scan file.

[0061] Optionally, the number of description files is confirmed by enumerating the description files in the first database, and each description file is opened in turn to access the information table and extract the Component Name and ECU Address information pairs until the number of times the description files are opened reaches the number of description files. Then, it is determined that the SOVD server has loaded all mapping relationships, and the mapping relationships are summarized to build a configuration information record table. Figure 5 This is a schematic diagram illustrating the information table of a description document for an exemplary embodiment of this application. For example... Figure 5 As shown, the first database contains description files, and each description file contains an information table. The information table records the mapping relationship between the electronic control unit address and the file identifier; where the ECU address (ECUAddress) can be a string like "1001 / 1002 / 1003", and the file identifier (Component Name) can be a string like "DHU / ADCU / ZCU".

[0062] By integrating the configuration information record table into the information table within the description file, it becomes possible to automatically update the configuration information record table based on the updated description files in the first database after the first database is updated, without human intervention or manual maintenance. Specifically, when the description files in the first database are updated, the step of traversing the information table of the description files in the first database to obtain the mapping relationship between the file identifier of each description file and the address information of the corresponding electronic control unit is re-executed, thereby realizing the automatic update of the configuration information record table and significantly improving the reliability and maintainability of the system.

[0063] S402. Search for the first address information corresponding to the file identifier in the configuration information record table.

[0064] See also Figure 5After the Component Name is entered, the SOVD server's search engine performs a matching query in the first database based on that Component Name, returning the detailed path name of the corresponding database file, thereby indexing the first target description file in the first database. Furthermore, the search engine can also map the address of the ECU corresponding to the diagnostic request data from the ECU information data table based on the Component Name. During SOVD server testing, the Tester (testing end) inputs the Component Name into the search engine; during real-vehicle application, the SOVD server extracts the Component Name from the diagnostic-related data and then inputs that Component Name into the search engine.

[0065] S403. Send the target diagnostic data to the first target electronic control unit corresponding to the first address information, so as to instruct the first target electronic control unit to execute the diagnostic request corresponding to the target diagnostic data and return the diagnostic response data.

[0066] In this embodiment, after acquiring the target diagnostic-related data for format conversion, the first target electronic control unit that needs to execute the diagnostic request is quickly retrieved and determined based on the identification information carried by the diagnostic request data, thereby reducing redundant query and matching processes and improving SOVD diagnostic efficiency.

[0067] Furthermore, in one embodiment, the diagnostic request data includes a request body and a request link; Figure 6 A flowchart of Embodiment 4 of the data format conversion method provided in this application; as follows: Figure 6 As shown, the process of sending target diagnostic data to the first target electronic control unit corresponding to the first address information includes:

[0068] S601. Extract the request parameters from the request link and obtain the diagnostic service data corresponding to the request parameters in the first target description file.

[0069] The request link is the network address used by the SOVD client to initiate a diagnostic service request to the SOVD server. Request parameters instruct the ECU on the diagnostic actions to be performed. Specifically, the request parameters can specify the specific diagnostic operation the ECU needs to perform and the specific request method for that operation. The action instruction specifies the functional behavior the ECU needs to complete, such as reading the ECU session state, listing the SOVD control services supported by the ECU, and clearing fault codes. The request method specifies the implementation method of the above actions, such as reading data, writing data, and creating a service.

[0070] Optionally, the SOVD client initiates access to the SOVD service via the HTTPS protocol. The HTTPS access link (request link) can be defined in the SOVD Server's general OpenAPI. For example, the HTTPS link address includes request parameters such as `mode-id` and `operation-id` to specify the specific diagnostic operation; and request parameters such as `get`, `put`, `post`, and `delete` to specify the specific request method. Furthermore, the HTTPS link address also includes a file identifier. Here, `mode-id` is the identifier of the specific diagnostic mode, `operation-id` is the identifier of the specific diagnostic operation, `get` is for reading data, `put` is for writing data, `post` is for creating a service, and `delete` is for clearing the service status.

[0071] The description file includes diagnostic service data related to the electronic control unit (ECU), which is the information required to perform diagnostic operations on the ECU. Optionally, the diagnostic service data specifically includes one or more of the following data tables: a project system information table, used to record vehicle project information; a diagnostic service information data table, used to define the diagnostic services supported by the ECU; a diagnostic session service information data table, used to describe the services that the ECU is allowed to enable under different diagnostic session modes; a diagnostic data DID service information data table, used to configure the correspondence between the ECU and each individual DID (Data Identifier); a diagnostic combination DID information data table, used to configure the correspondence between the ECU and combination DIDs; a diagnostic control service information data table, used to define the control-type diagnostic services supported by the ECU; a diagnostic sub-function information data table, used to describe the sub-function diagnostic services supported by the ECU; a diagnostic snapshot data information table, used to record snapshot data collected by the ECU when a fault occurs; a diagnostic fault code information table, storing a list of diagnostic fault codes supported by the ECU; and a diagnostic negative response code information data table, defining relevant information for various negative response codes of the ECU.

[0072] Optionally, there is a predefined mapping relationship between the request parameters and the information tables constructed above. The SOVD client uses the request parameters as an index to locate one or more corresponding data tables within the description file and reads the diagnostic service data stored in these data tables.

[0073] S602. Based on the first target description file, the request body in the request data is formatted to obtain target diagnosis related data.

[0074] The SOVD client initiates access to the SOVD service via HTTPS. The request body of this HTTPS request transmits the necessary input parameters in JSON format. The specific structure, field names, data types, and constraints of these input parameters are all defined by the OpenAPI provided by the SOVD server. Correspondingly, the response body of the same HTTPS request transmits the necessary input parameters in JSON format. The specific structure, field names, data types, and constraints of these input parameters can also be defined by the OpenAPI provided by the SOVD server.

[0075] Optionally, according to the conversion rules provided in the first target description file, the JSON format request body is converted into a non-SOVD data format supported by the first target electronic control unit to obtain target diagnostic related data.

[0076] S603. The diagnostic service data and target diagnostic related data are sent to the first target electronic control unit to instruct the first target electronic control unit to execute the diagnostic request corresponding to the diagnostic service data and target diagnostic related data, and return diagnostic response data.

[0077] Optionally, based on diagnostic service data and target diagnostic-related data, a diagnostic request message in a non-SOVD data format supported by the first target electronic control unit is constructed; the request message is then sent to the first target electronic control unit. The electronic control unit parses the request message and performs the corresponding diagnostic operation.

[0078] In this embodiment, the request parameters are embedded into the request link, enabling the SOVD server to efficiently index diagnostic service data based on the request parameters, thereby improving the efficiency of SOVD format business diagnostics.

[0079] In one embodiment, the diagnostic-related data is diagnostic response data, and the identification information is the second address information of the electronic control unit that provides feedback on the diagnostic response data. Based on the identification information, searching in a pre-built first database for the existence of a first target description file corresponding to the identification information includes: obtaining a configuration information record table pre-configured for the first database; searching in the configuration information record table for the target file identifier corresponding to the second address information; and searching in the first database for the first target description file corresponding to the target file identifier.

[0080] The configuration information record table records the mapping relationship between the second address information and the target file identifier, and the first target description file can be indexed based on the target file identifier.

[0081] Optionally, the SOVD server's search engine queries the configuration information record table based on the second address information to locate the corresponding target file identifier; further, the search engine uses the target file identifier to retrieve and obtain the associated first target description file in the first database.

[0082] In this embodiment, after acquiring the target diagnostic-related data for format conversion, the first target electronic control unit that needs to execute the diagnostic request is quickly retrieved and determined based on the second address information of the electronic control unit carried by the diagnostic response data, thereby improving the efficiency of data query and matching and thus improving the diagnostic efficiency of SOVD.

[0083] In one embodiment, Figure 7 A flowchart of Embodiment 5 of the data format conversion method provided in this application; as follows: Figure 7 As shown, please refer to Figure 7 Based on the above embodiments, the method further includes:

[0084] S701. Based on the configuration information record table pre-configured for the first database, determine the first software number of the electronic control unit corresponding to each diagnostic description file.

[0085] The first software number is a set of software component numbers of the electronic control unit recorded in all description files in the first database. Optionally, when the filename of a description file is composed of the physical address of the ECU, the software component number of the ECU, and the version information of the software component number, the first software number can be obtained by traversing the filenames of each description file.

[0086] S702, Obtain the second software number corresponding to each electronic control unit in the vehicle.

[0087] The second software number is a collection of software component numbers of the electronic control units already installed in the vehicle.

[0088] S703. Compare the first software number and the second software number, and determine the second target electronic control unit where the software numbers differ.

[0089] Specifically, if the first software number and the second software number are different, it can be determined that the second target electronic control unit deployed in the current vehicle has been updated, and the description file corresponding to the second target electronic control unit needs to be updated accordingly.

[0090] S704. Update the description file corresponding to the second target electronic control unit in the first database.

[0091] Optionally, the cloud can pre-configure description files according to vehicle model series. The SOVD server connects to the cloud, and when it detects the existence of a second target electronic control unit, the SOVD server downloads and updates the description file corresponding to the second target electronic control unit from the cloud. Specifically, when the SOVD client initiates a diagnostic request, the SOVD server actively executes the above steps S701 to S704; or, the cloud issues an update command, and the SOVD server responds to the update command issued by the cloud by executing the above steps S701 to S704.

[0092] In this embodiment, the first database that needs to be updated is determined by comparing software numbers, the differences between the first database and the vehicle's deployed ECU are accurately identified, and the differential update of the description file in the first database is implemented based on the differences, thereby improving update efficiency and ensuring diagnostic resources and consistency.

[0093] Based on the same technical concept, in one embodiment, a diagnostic data request method for an SOVD client is also provided, comprising: generating diagnostic-related data corresponding to an electronic control unit in a vehicle in response to a diagnostic request for that electronic control unit; wherein the diagnostic-related data includes identification information associated with a specified description file in a pre-built first database; and the first database is configured on an SOVD server in the vehicle.

[0094] The diagnostic-related data includes request links and request data. In response to vehicle-side instructions, a vehicle diagnostic request is generated, which includes: determining the preset link format and data structure according to the predefined interface specifications; in response to vehicle-side instructions, generating a request link that conforms to the link format and includes a diagnostic file identifier, and request data that conforms to the data structure, thereby obtaining the diagnostic-related data.

[0095] Optionally, the SOVD server defines a general OpenAPI JSON interface, which includes SOVD request links for all supported ECUs, the request data for each link, and the response data format for each link. SOVD clients access the SOVD service through the OpenAPI JSON interface to obtain diagnostic data.

[0096] Table 1 shows the SOVD request links supported by the OpenAPI structure in this embodiment and their diagnostic methods.

[0097]

[0098] Here, "base_url" is the base URL (network link) generated in real time based on the SOVD client request; "components" is a fixed field in the SOVD request link, used to indicate that the request link is intended to initiate an operation to convert the format of diagnostic-related data; "ecu-id" and subsequent fields such as "data" and "status" are request parameters.

[0099] Furthermore, the SOVD client sends diagnostic-related data to the SOVD server to instruct the SOVD server to perform a data format conversion method. Figure 8 This is a schematic diagram of an embodiment of the SOVD server provided in this application, as shown below. Figure 8 As shown, the SOVD server includes a gateway, an OpenAPI service processing module, a data processing module, a first database, and a second database. The gateway connects to the SOVD client, and the first database connects to the cloud; the SOVD server receives diagnostic-related data from the SOVD client. The SOVD server downloads and updates the description file corresponding to the second target electronic control unit from the cloud. Specifically, Figure 9 The flowchart of Embodiment Six of the data format conversion provided in this application includes the following methods:

[0100] S901 The gateway receives diagnostic request data sent by the SOVD client and forwards the diagnostic request data to the OpenAPI service processor.

[0101] S902, the OpenAPI service processor extracts the file identifier from the diagnostic request data and sends the file identifier from the diagnostic request data to the data processor.

[0102] S903, the data processor searches for the first address information corresponding to the file identifier in the configuration information record table.

[0103] S904. The data processor determines whether the first target description file corresponding to the identification information can be found in the pre-built first database based on the identification information. If yes, then S905 is executed; otherwise, S906 is executed.

[0104] S905. Based on the identification information, search for the target description file corresponding to the identification information in the pre-built second database, and execute S907.

[0105] S906. Search for the target description file corresponding to the identification information from the pre-built first database.

[0106] S907: The data processor locks the target description file, converts the diagnostic request data according to the target description file, and sends the converted diagnostic request data to the ECU.

[0107] Specifically, the data processor locks the first target description file based on the file identifier, and the database returns the file name information of the first target description file; the data processor opens the first target description file and obtains the opening result of the first target description file; the data processor queries the conversion rules and diagnostic service data corresponding to the diagnostic request data in the first target description file; the database feeds back the queried conversion rules and diagnostic service data to the data processor; the data processor performs format conversion on the diagnostic-related data according to the conversion rules to obtain the target diagnostic-related data and diagnostic service data.

[0108] S907, the ECU returns diagnostic response data.

[0109] S908, the data processor performs format conversion on the diagnostic response data according to the first target description file, and forwards the converted diagnostic response data to the SOVD client through the gateway to obtain the SOVD diagnostic result.

[0110] Specifically, the implementation principles and processes of steps S901 to S908 can be found in the descriptions in the previous embodiments, and will not be repeated here.

[0111] Corresponding to the aforementioned embodiment of a data formatting method, this application also provides an embodiment of a data formatting apparatus.

[0112] An embodiment of a data formatting device disclosed in this application can be applied to an SOVD server. The device embodiment can be implemented through software, hardware, or a combination of both. Taking software implementation as an example, as a logical device, it is formed by the processor of the SOVD server loading the corresponding computer program instructions from non-volatile memory into memory for execution. From a hardware perspective, such as... Figure 10 The diagram shown is a hardware structure diagram of the SOVD server where the data formatting device of this application is located. Except for... Figure 10 In addition to the processor, memory, network interface, and non-volatile memory shown, the SOVD server where the device is located in the embodiment may also include other hardware depending on the actual function of the data format device, which will not be described in detail here.

[0113] Figure 11 This is a schematic diagram of the structure of a data formatting device according to an embodiment of this application. Please refer to... Figure 11 The device provided in this embodiment is applied to an SOVD server in a vehicle; the device includes:

[0114] The extraction module 11 is used to extract identification information from the diagnostic-related data when diagnostic-related data is received.

[0115] The database lookup module 12 is used to search the pre-built first database for whether a first target description file corresponding to the identification information exists, based on the identification information. The first database stores description files corresponding to each electronic control unit on the vehicle. The description files corresponding to each electronic control unit are used to indicate the conversion rules between SOVD data format and non-SOVD data formats supported by the electronic control unit.

[0116] The conversion module 13 is used to convert the format of the diagnostic-related data according to the first target description file when there is a first target description file corresponding to the identification information, so as to obtain the target diagnostic-related data.

[0117] The apparatus of this embodiment can be used to perform... Figure 1 The steps of the method embodiment shown are similar in principle and process, and will not be repeated here.

[0118] In some embodiments, when no first target description file corresponding to the identification information exists, the database lookup module 12 is further configured to: search a pre-built second database for a second target description file corresponding to the identification information; wherein the second database stores at least one shared description file; each shared description file is a description file corresponding to a type of electronic control unit, used to indicate the conversion rules between SOVD data format and non-SOVD data formats supported by that type of electronic control unit; when a second target description file corresponding to the identification information exists, the diagnostic-related data is format-converted according to the second target description file to obtain target diagnostic-related data.

[0119] In some embodiments, the diagnostic-related data is diagnostic request data; the identification information is the file identifier of the description file; after the diagnostic-related data is format-converted according to the first target description file, the conversion module 13 is further used to obtain a configuration information record table pre-configured for the first database; wherein, the configuration information record table is used to record the correspondence between the file identifier of the description file corresponding to each electronic control unit and the address information of the electronic control unit; the first address information corresponding to the file identifier is searched from the configuration information record table; the target diagnostic-related data is sent to the first target electronic control unit corresponding to the first address information to instruct the first target electronic control unit to execute the diagnostic request corresponding to the target diagnostic-related data and return diagnostic response data.

[0120] Optionally, the diagnostic request data includes a request body and a request link; the conversion module 13 sends the target diagnostic-related data to the first target electronic control unit corresponding to the first address information, including: extracting the request parameters from the request link and obtaining the diagnostic service data corresponding to the request parameters in the first target description file; converting the format of the request body in the request data according to the first target description file to obtain the target diagnostic-related data; sending the diagnostic service data and the target diagnostic-related data to the first target electronic control unit to instruct the first target electronic control unit to execute the diagnostic request corresponding to the diagnostic service data and the target diagnostic-related data, and returning diagnostic response data.

[0121] In some embodiments, the diagnostic-related data is diagnostic response data, and the identification information is the second address information of the electronic control unit that provides feedback on the diagnostic response data; the database search module 12 searches the pre-built first database for the existence of a first target description file corresponding to the identification information based on the identification information, including: obtaining a configuration information record table pre-configured for the first database; searching the configuration information record table for the target file identifier corresponding to the second address information; and searching the first database for the first target description file corresponding to the target file identifier.

[0122] In some embodiments, the data format conversion device further includes an information construction module, which is used to traverse the information tables of each description file in the first database to obtain the mapping relationship between the file identifier of each description file and the address information of the electronic control unit corresponding to each scan file; and to construct a configuration information record table based on the mapping relationship between the file identifier of each description file and the address information of the electronic control unit corresponding to each scan file.

[0123] In some embodiments, the data format conversion device further includes an update module, which is used to determine the first software number of the electronic control unit corresponding to each diagnostic description file according to a configuration information record table pre-configured for the first database; obtain the second software number corresponding to each electronic control unit in the vehicle; compare the first software number and the second software number and determine the second target electronic control unit where the software number differs; and update the description file corresponding to the second target electronic control unit in the first database.

[0124] Please continue to refer to Figure 10 This application also provides an SOVD server, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps of the data format method in this application.

[0125] This application also provides a vehicle that includes the SOVD server provided in any embodiment of this application, which can execute the steps of the data format conversion method in any of the above method embodiments. Alternatively, the vehicle includes the data format conversion device described in any of the above device embodiments.

[0126] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the methods provided in this application.

[0127] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0128] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0129] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A data format conversion method, characterized in that, The data format conversion method is applied to the SOVD server on the vehicle; the data format conversion method includes: Upon receiving diagnostic-related data, identification information is extracted from the diagnostic-related data; Based on the identification information, a search is conducted in a pre-built first database to determine if a first target description file corresponding to the identification information exists; wherein, the first database stores description files corresponding to each electronic control unit on the vehicle; the description file corresponding to each electronic control unit is used to indicate the conversion rules between SOVD data format and non-SOVD data formats supported by each electronic control unit; When a first target description file corresponding to the identification information exists, the diagnostic-related data is format-converted according to the first target description file to obtain target diagnostic-related data.

2. The method according to claim 1, characterized in that, When a first target description file corresponding to the identification information does not exist, the method further includes: Based on the identification information, a search is conducted in a pre-built second database to determine if a second target description file corresponding to the identification information exists; wherein, the second database stores at least one shared description file; each shared description file is a description file corresponding to a type of electronic control unit, used to indicate the conversion rules between SOVD data format and non-SOVD data formats supported by that type of electronic control unit; When a second target description file corresponding to the identification information exists, the diagnostic-related data is format-converted according to the second target description file to obtain target diagnostic-related data.

3. The method according to claim 1, characterized in that, The diagnostic-related data is diagnostic request data; the identification information is the file identifier of the description file; after converting the format of the diagnostic-related data according to the first target description file, the method further includes: Obtain a configuration information record table pre-configured for the first database; wherein, the configuration information record table is used to record the correspondence between the file identifier of the description file corresponding to each electronic control unit and the address information of the electronic control unit; Search the configuration information record table for the first address information corresponding to the file identifier; The target diagnostic data is sent to the first target electronic control unit corresponding to the first address information, so as to instruct the first target electronic control unit to execute the diagnostic request corresponding to the target diagnostic data and return diagnostic response data.

4. The method according to claim 3, characterized in that, The diagnostic request data includes a request body and a request link; the step of sending the target diagnostic-related data to the first target electronic control unit corresponding to the first address information includes: Extract the request parameters from the request link, and obtain the diagnostic service data corresponding to the request parameters in the first target description file; Based on the first target description file, the request body in the request data is converted to a new format to obtain target diagnosis related data; The diagnostic service data and the target diagnostic related data are sent to the first target electronic control unit to instruct the first target electronic control unit to execute the diagnostic request corresponding to the diagnostic service data and the target diagnostic related data, and return diagnostic response data.

5. The method according to claim 1 or 3, characterized in that, The diagnostic-related data is diagnostic response data, and the identification information is the second address information of the electronic control unit that feeds back the diagnostic response data; The step of searching a pre-built first database for a first target description file corresponding to the identification information includes: Obtain the configuration information record table that has been pre-configured for the first database; Search the configuration information record table for the target file identifier corresponding to the second address information; Search the first target description file corresponding to the target file identifier in the first database.

6. The method according to claim 3, characterized in that, The method for constructing the configuration information record table includes: Traverse the information tables of each description file in the first database to obtain the mapping relationship between the file identifier of each description file and the address information of the electronic control unit corresponding to each scan file; The configuration information record table is constructed based on the mapping relationship between the file identifier of each description file and the address information of the electronic control unit corresponding to each scan file.

7. The method according to claim 1, characterized in that, The method further includes: Based on the configuration information record table pre-configured for the first database, determine the first software number of the electronic control unit corresponding to each diagnostic description file; Obtain the second software number corresponding to each electronic control unit in the vehicle; Compare the first software number and the second software number, and determine the second target electronic control unit whose software number differs; Update the description file corresponding to the second target electronic control unit in the first database.

8. A data format conversion device, characterized in that, SOVD server applied to vehicles; the device includes: The extraction module is used to extract identification information from the diagnostic-related data when diagnostic-related data is received; The database lookup module is used to search a pre-built first database for the existence of a first target description file corresponding to the identification information, based on the identification information. The first database stores description files corresponding to various electronic control units on the vehicle. The description files corresponding to each electronic control unit are used to indicate the conversion rules between SOVD data format and non-SOVD data formats supported by the electronic control unit. The conversion module is used to convert the format of the diagnosis-related data according to the first target description file when the identification information exists, so as to obtain the target diagnosis-related data.

9. An SOVD server, characterized in that, The SOVD server includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method according to any one of claims 1 to 7.

10. A vehicle, characterized in that, The vehicle includes the SOVD server as described in claim 9 or the data format conversion device as described in claim 8.

Images