System and method for issuing vehicle diagnostic data, and computer program product

Abstract

The invention discloses a vehicle diagnostic data publishing system and method, and a computer program product. The publishing system comprises a database for storing entity data, a database for storing configuration data used for indicating the entity data, a database for storing information of the diagnosis system and a task publishing module, and the task publishing module can generate task publishing information based on the information of the diagnosis system. And determining a target diagnosis system according to the information of the release task and the configuration data, and automatically executing the release task based on the release time, so as to enable the target diagnosis system to update entity data corresponding to the configuration data based on the configuration data after the configuration data is released to a target environment of the target diagnosis system. According to the mode, decoupling between the entity data of different target diagnosis systems is achieved, the entity data are issued to the multiple target diagnosis systems at the same time, the issuing platform is simple in configuration, the data expandability and the data issuing efficiency are improved, and the system and data maintenance cost is reduced.

Description

Technical Field

[0001] The present application relates to the field of vehicle diagnosis technology, and more specifically, to a vehicle diagnostic data publishing system and method, and a computer program product. Background Art

[0002] As an important part of vehicle technology development, vehicle diagnostic technology has an increasingly wide range of application scenarios. As vehicle diagnostic data becomes increasingly complex and diagnostic systems in different scenarios require different diagnostic data, how to publish corresponding diagnostic data to multiple diagnostic systems has become an urgent problem to be solved.

[0003] In the related art, databases of different target environments are usually built under the same service system, and then different database operation scripts are developed based on the database to publish diagnostic data to different diagnostic systems. However, since the diagnostic data required by different diagnostic systems are highly coupled, the release of diagnostic data in the related art cannot dynamically publish the corresponding vehicle diagnostic data to multiple diagnostic systems at the same time. Summary of the invention

[0004] The embodiments of the present application provide a vehicle diagnostic data publishing system and method, and a computer program product. The following introduces various aspects of the embodiments of the present application.

[0005] In a first aspect, a vehicle diagnostic data publishing system is provided, the publishing system comprising: a data layer, comprising a first database for storing entity data, a second database for storing configuration data, and a third database for storing diagnostic system information; the entity data has an entity data ID, the configuration data is used to indicate the entity data and the configuration data comprises the entity data ID and a data user associated with the entity data ID, and the diagnostic system information comprises the diagnostic system ID and a data user associated with the diagnostic system ID; a logic layer, comprising a publishing task module, the publishing task module is used to perform the following operations: construct a publishing task according to the diagnostic system information and generate the publishing task information, the publishing task information comprises a task ID, a publishing time plan and a target environment associated with at least one diagnostic system ID; determine a target diagnostic system according to the at least one diagnostic system ID in the publishing task information, the data user in the diagnostic system information and the data user in the configuration data; execute the publishing task according to the publishing task information to publish the configuration data to the target environment of the target diagnostic system, and after the target diagnostic system updates the configuration data to the configuration database of the target diagnostic system, update the entity database of the target diagnostic system based on the configuration data.

[0006] In a second aspect, a method for publishing vehicle diagnostic data is provided, the method being applied to a publishing system for vehicle diagnostic data, the publishing system comprising: a first database for storing entity data, a second database for storing configuration data, and a third database for storing diagnostic system information, the entity data having an entity data ID, the configuration data being used to indicate the entity data and the configuration data comprising the entity data ID and a data user associated with the entity data ID, the diagnostic system information comprising the diagnostic system ID and the data user associated with the diagnostic system ID; the method comprising: constructing a publishing task according to the information of the diagnostic system and generating information of the publishing task, the information of the publishing task comprising a task ID associated with at least one of the diagnostic system IDs, a publishing time schedule, and a target environment; determining a target diagnostic system according to the at least one of the diagnostic system IDs in the information of the publishing task, the data user in the information of the diagnostic system, and the data user in the configuration data; executing the publishing task according to the information of the publishing task to publish the configuration data to the target environment of the target diagnostic system, and after the target diagnostic system updates the configuration data to the configuration database of the target diagnostic system, updating the entity database of the target diagnostic system based on the configuration data.

[0007] According to a third aspect, a computer program product is provided, comprising: a computer program / instructions, which, when executed by a processor, implement the method described in the second aspect.

[0008] According to a fourth aspect, a computer-readable storage medium is provided, on which is stored data for executing the method described in the second aspect.

[0009] The embodiments of the present application can achieve decoupling between entity data of different target diagnostic systems by adding configuration data corresponding to the entity data and information of the diagnostic system. In addition, through the publishing task module of the publishing system, entity data can be simultaneously published to multiple target diagnostic systems based on the configuration data, information of the diagnostic system and information of the publishing task. The publishing system has a simple system configuration, improves data scalability and efficiency in publishing vehicle diagnostic data, and reduces the cost of system and data maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 Schematic diagram of the architecture of a vehicle diagnostic data publishing system provided in one embodiment of the present application.

[0011] Figure 2 It is a flowchart of a method for publishing vehicle diagnostic data provided in one embodiment of the present application.

[0012] Figure 3 It is a schematic diagram of the architecture of a vehicle diagnostic data publishing platform provided in another embodiment of the present application.

[0013] Figure 4 It is a schematic diagram of the architecture of a vehicle diagnostic data publishing platform provided in yet another embodiment of the present application.

[0014] Figure 5 It is a flowchart of a method for updating data in a test environment within a publishing system provided in an embodiment of the present application.

[0015] Figure 6 It is a flowchart of a method for constructing a publishing task provided in an embodiment of the present application.

[0016] Figure 7 It is a flowchart of a method for constructing a publishing task provided in yet another embodiment of the present application.

[0017] Figure 8 It is a flowchart of a method for publishing vehicle diagnostic data provided by another embodiment of the present application.

[0018] Fig. 9 It is a flowchart of a method for executing publishing termination by a publishing data management module provided in an embodiment of the present application.

[0019] Fig.10 It is a flowchart of a method for executing release version rollback by a release data management module provided in an embodiment of the present application.

[0020] Fig.11 It is a flowchart of a method for executing release version information comparison by a release data management module provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0022] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0023] In the description of the present application, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inside", "outside" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention; the terms "first", "second", and "third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance; in addition, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection or a detachable connection; it can be directly connected or indirectly connected through an intermediate medium, and it can be the internal connection of two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0024] As an important part of the technological development of vehicles, vehicle diagnostic technology has an increasingly wide range of application scenarios. As vehicle diagnostic data (or vehicle diagnostic basic data or entity data) becomes increasingly complex and the diagnostic systems in different scenarios (e.g., on-board diagnostic equipment, remote diagnostic equipment, after-sales diagnostic equipment, end-of-line (EOL) diagnostic equipment, etc.) require different vehicle diagnostic data, it is increasingly important to publish corresponding vehicle diagnostic data to multiple diagnostic systems, which directly affects the development cycle of the entire vehicle project. Therefore, how to publish corresponding vehicle diagnostic data to multiple diagnostic systems has become an urgent problem to be solved.

[0025] In the related art, the method for publishing the corresponding vehicle diagnostic data to the diagnostic system is: construct databases of different target environments under the same service system, and then realize the publishing of diagnostic data to different target diagnostic systems by developing database operation scripts and configuring database fields. For example, in the background service system, databases of the R&D environment, the test environment, and the formal environment are simultaneously constructed, and then the R&D environment data is migrated to the test environment database and the formal environment database by data replication, so that different diagnostic systems can obtain the test environment data and the formal environment data from the test environment database and the formal environment database. Specifically, different diagnostic systems can obtain the corresponding vehicle diagnostic data from the test database and / or the formal environment database of the background service system based on different configurations by developing an automated script program for operating the database.

[0026] However, since the diagnostic data required by different diagnostic systems are highly coupled, the release of diagnostic data in the related art cannot dynamically release the corresponding vehicle diagnostic data to multiple diagnostic systems at the same time.

[0027] In view of the above problems, an embodiment of the present application provides a vehicle diagnostic data publishing system, wherein the publishing system includes a first database for storing vehicle diagnostic data (hereinafter referred to as entity data for simplicity of description), a second database for storing configuration data for indicating entity data, a third database for storing information of the diagnostic system, and a publishing task module, wherein the publishing task module can generate information of the publishing task based on the information of the diagnostic system, can determine the target diagnostic system according to the information of the publishing task and the configuration data, and can automatically execute the publishing task based on the publishing time in the information of the publishing task, so as to publish the configuration data to the target diagnostic system and enable the target diagnostic system to update the configuration data to its configuration database, and then update its entity database based on the configuration data. By adding configuration data corresponding to the entity data and the information of the diagnostic system, the decoupling between the entity data of different target diagnostic systems can be achieved. In addition, the publishing task module can realize the publishing of entity data to multiple target diagnostic systems at the same time based on the configuration data, the information of the diagnostic system and the information of the publishing task. The system configuration of the publishing system is simple, which improves the scalability of data and the publishing efficiency of vehicle diagnostic data, and reduces the cost of system and data maintenance.

[0028] Combine the following Figure 1-Figure 11 The vehicle diagnostic data publishing system provided in the embodiments of the present application and the method for publishing data using the publishing system are described in detail.

[0029] like Figure 1 The vehicle diagnostic data publishing system includes a data layer and a logic layer. The logic layer is used for controlling and managing based on the data in the data layer.

[0030] The data layer includes a first database for storing entity data, a second database for storing configuration data, and a third database for storing information of a diagnosis system.

[0031] The first database can also be Figure 3 The entity data stored in the first database is vehicle diagnostic data. For example, the entity data may be entity data for a test environment, or the entity data may be entity data for a formal environment. In some embodiments, Figure 1 As shown, the first database may include an entity database for a test environment and an entity database for a formal environment. The entity data may have an entity data ID and a data version. The entity data ID is a unique identification number for the entity data. The data version refers to the developed entity data version number.

[0032] In some embodiments, the entity data in the first database may be obtained from an entity database in a development environment. As an implementation, the entity database in the development environment may be located in a publishing system. As another implementation, Figure 3 As shown, the entity database in the development environment may be located in the source system. The entity data may be created, developed or maintained by a data development tool in the source system, for example. Optionally, the entity data may be encrypted and stored in the entity database in the development environment.

[0033] The embodiment of the present application does not specifically limit the data type of entity data, and the data type includes but is not limited to the following types.

[0034] Diagnostic database file: contains diagnostic instructions, communication protocols, communication parameters, diagnostic trouble code (DTC) information, etc. of each vehicle's Electronic Control Unit (ECU). The formats of diagnostic database files include but are not limited to Vector standard database file format (CANdela DiagnosticDescription, CDD), Open Diagnostic data eXchange format (ODX), etc.

[0035] Diagnostic program file: refers to the automated diagnostic script programming file used for vehicle diagnosis. The format of the diagnostic program file includes but is not limited to programming files developed in languages ​​such as Java, Python, and Open Test Sequence eXchange format (otx).

[0036] Text: formats include but are not limited to eXtensible Markup Language (Xml), JavaScript Object Notation (Json), txt text, Hyper Text Markup Language (HTML) text, etc.

[0037] Document: Formats include but are not limited to DOC documents, Portable Document Format (PDF), etc.

[0038] Table: Formats include but are not limited to Excel files.

[0039] Pictures: Formats include but are not limited to JPG, PNG, JPEG, GIF and other formats.

[0040] Video: Formats include but are not limited to AVI, MPEG, WMV, etc.

[0041] The second database is Figure 3 The configuration data stored in the second database is data for indicating entity data, that is, the entity data corresponds to the configuration data. The configuration data may be configuration data for a test environment, or the configuration data may be configuration data for a formal environment. In some embodiments, Figure 1 As shown, the second database may include a configuration database for the test environment and a configuration database for the formal environment. The configuration data may be generated or changed synchronously with the corresponding entity data when the entity data is generated or changed.

[0042] In some embodiments, the configuration data in the second database may be obtained from a configuration database in a development environment. The configuration data in the configuration database in the development environment is generated synchronously based on the entity data in the development environment. That is, when new entity data is generated in the development environment, or when entity data changes, corresponding configuration data will be generated in the development environment. The storage form of the configuration data includes, but is not limited to, database field data, configuration files (such as XML files, Json files, text documents, tables, etc.).

[0043] The content of the configuration data includes but is not limited to the following: entity data ID; entity data name; data type of the entity data mentioned above; development status; availability status; data version, change information, and data user associated with the entity data ID, etc.

[0044] The development status may refer to the development status of the current entity data, including but not limited to initialization (newly created entity data), developing (entity data under development), and developed (entity data whose development has been completed).

[0045] The available status refers to whether the entity data is available. The statuses include disabled and available. Disabled means that the data is unavailable.

[0046] Change information refers to the description of the changes in the entity data of the corresponding data version.

[0047] In some embodiments, the data user associated with the entity data ID may include a user object set (or user object list) associated with the entity data ID and a vehicle identification information set (or vehicle identification information list) associated with the entity data ID. The user object set here refers to the set of user objects of the entity data corresponding to the entity data ID, and the user objects include but are not limited to on-board diagnostic equipment, remote diagnostic equipment, after-sales diagnostic equipment, EOL diagnostic equipment, engineering diagnostic equipment, etc. The vehicle identification information set here refers to the set of vehicle identification information associated with the entity data ID, and the vehicle identification information is not limited to vehicle model, vehicle configuration, brand, sales market, etc.

[0048] In some embodiments, the configuration data may further include a check code. The check code is generated by a check algorithm and is used to check data consistency. The check algorithms used include but are not limited to checksum, XOR check, cyclic redundancy check (CRC) check, MD5 message-digest algorithm, SM3 cryptographic hash algorithm, etc.

[0049] The third database can be Figure 3 The diagnostic system database of the publishing system in the diagnostic system information repository. The information of the diagnostic system stored in the diagnostic system information repository can be used to indicate the diagnostic system. The diagnostic system is a system that can be built and maintained by the publishing system, and the information of the diagnostic system can be generated by the publishing system when building, maintaining or managing the diagnostic system, and the diagnostic system is a system that needs to use entity data. The diagnostic system information repository can store information on all diagnostic systems that can be built, maintained or managed by the publishing system. In other words, the publishing system is used to manage, build or maintain multiple diagnostic systems.

[0050] The information of each diagnostic system includes but is not limited to the diagnostic system ID, the target system name, the data user associated with the diagnostic system ID, the server authentication information of the diagnostic system, the available status and the creation time.

[0051] The diagnostic system ID is the unique identification number of the diagnostic system. The server authentication information of the diagnostic system may be, for example, the target diagnostic system server address, authentication account, authentication key, etc. The available status may be an indicator of whether the diagnostic system is available, and the status includes disabled and available. Disabled means that the data is unavailable.

[0052] In some embodiments, the data user associated with the diagnostic system ID includes a user object set (or user object list) associated with the diagnostic system ID and a vehicle identification information set (or identification information list) associated with the diagnostic system ID. The user object set here refers to the set of user objects corresponding to the diagnostic system ID, and the user objects are as described above. The vehicle identification information set here refers to the set of vehicle identification information associated with the diagnostic system ID, and the vehicle identification information is as described above.

[0053] In some embodiments, the information of the diagnosis system may further include a release version. The release version refers to a data release version corresponding to the entity data of the formal environment of the diagnosis system.

[0054] The logic layer 112 may include a publishing task module, which is used to automatically publish configuration data to a target environment of a target diagnosis system based on information of the first database, the second database, and the third database, so that the target environment of the target diagnosis system updates its entity database.

[0055] As a way to achieve this, Figure 2 As shown, the publishing task module can execute steps S210 - S230 to publish the configuration data to the target environment of the target diagnostic system.

[0056] In step S210: construct a release task according to the information of the diagnostic system and generate information of the release task.

[0057] The publishing task is used to send configuration data and entity data to the target diagnosis system. Specifically, the publishing task can instruct to first send configuration data to the target diagnosis system, then make the target diagnosis system update its configuration database, and then update the entity data in the entity database based on the updated configuration data.

[0058] The embodiment of the present application does not specifically limit the type of the release task. For example, the release task may be a regular release task or a periodic release task.

[0059] The information of the published task is used to indicate the specific content of the published task. The information of the published task includes but is not limited to the following: task ID, publishing time plan, target environment and at least one diagnostic system ID associated with the task ID.

[0060] Task ID refers to the unique identification number of the release task. Target environment indicates the type of target environment of the target diagnostic system for which the release task is targeted. The target environment can be a test environment or a formal environment. Release schedule is used to indicate the time requirements for the execution of the release task. When the release task is a periodic release task, the release schedule includes the release cycle and the start-end time. The release cycle refers to how often the release task is executed. Start-end time: refers to the effective time period for the execution of the periodic release task. When the release task is a regular release task, the release schedule includes the release time. The release time indicates the specific time point at which the regular release task is executed.

[0061] Optionally, when the release task is a periodic release task, the release task information may further include the creation time of the release task.

[0062] The at least one diagnostic system ID associated with the task ID is used to indicate the diagnostic system associated with the task ID and to determine the target diagnostic system, wherein the target diagnostic system is part or all of the diagnostic systems corresponding to the at least one diagnostic system ID associated with the task ID.

[0063] In some embodiments, the published task is constructed based on the operation model, which will be described later. Based on this, the information of the published task may also include an operation model ID, and the operation model ID is associated with the task ID. The published task may be associated with an operation model information based on the operation model ID.

[0064] In some embodiments, when the release task is a periodic release task, the release task can be based on the job model to build a release tag, and then generate the periodic task information based on the release tag associated configuration data. At this time, the release tag information includes the information for the above release task. The periodic task information and the release tag information may be different. For example, the periodic task information may include: but not limited to entity data ID, data version, task ID, release status, creation time, etc. The data release status includes but is not limited to pending release, release termination, released, etc. In some embodiments, the periodic task information may be stored with Figure 3 In the periodic task information library.

[0065] In step S220 : a target diagnostic system is determined according to at least one diagnostic system ID in the information of the published task, a data user in the information of the diagnostic system, and a data user in the configuration data.

[0066] As an example, determining the target diagnostic system based on at least one diagnostic system ID in the information of the published task, the data user in the information of the diagnostic system, and the data user in the configuration data may include determining the target diagnostic system based on a first data user and a second data user, wherein the first data user may be determined based on the data user in the configuration data, the first data user being the data user associated with the entity data ID in the configuration data. The second data user may be determined based on at least one diagnostic system ID in the information of the published task and the data user in the information of the diagnostic system. The second data user is determined based on at least one diagnostic system ID associated with the task ID in the information of the published task and the data user associated with at least one diagnostic system ID indicated in the task system information.

[0067] In step S230: the publishing task is executed according to the information of the publishing task to publish the configuration data to the target environment of the target diagnostic system, and after the target diagnostic system updates the configuration data to the configuration database of the target diagnostic system, the entity database of the target diagnostic system is updated based on the configuration data.

[0068] The publishing system executes the publishing task according to the information of the publishing task, which may be executing the publishing task according to information such as the target environment and the publishing time plan in the publishing task information.

[0069] After the target diagnosis system updates the configuration data to the configuration database of the target diagnosis system, the method of updating the entity database of the target diagnosis system based on the configuration data may be similar to the method of updating the entity database in the publishing system, as described below.

[0070] The embodiment of the present application can achieve decoupling between entity data of different target diagnostic systems by adding configuration data corresponding to the entity data and information of the diagnostic system. In addition, through the release task module, entity data can be released to multiple target diagnostic systems at the same time based on the configuration data, information of the diagnostic system and information of the release task. The system configuration of the release system is simple, which improves the scalability of data and the release efficiency of vehicle diagnostic data, and reduces the cost of system and data maintenance.

[0071] As mentioned above, the publishing system can build or manage multiple diagnostic systems. In some embodiments, multiple diagnostic systems can be built by the publishing system based on a unified interface document. That is to say, all diagnostic systems that can obtain configuration data and entity data from the publishing system are connected to the publishing system through a unified interface document, and when a new diagnostic system needs to be established, the publishing system can be built based on the unified interface document. An interface document is a document that describes in detail how systems or components interact with each other. It defines the communication method, data format, request and response structure, error handling mechanism, etc. between different systems or modules.

[0072] In some embodiments, the diagnostic system may be Figure 3 The diagnostic system maintenance module in the system is constructed and maintained in real time. The diagnostic system information can be stored in Figure 3 The diagnostic system information repository in .

[0073] The publishing system can build or manage multiple diagnostic systems through a unified interface document to achieve dynamic and real-time construction of diagnostic systems, thereby avoiding the problem of secondary development of the service system when using scripts to build diagnostic systems in related technologies, and reducing data and system management costs.

[0074] The present application embodiment does not specifically limit the architecture of the diagnostic system. Figure 3 As shown, the diagnostic system may include a logic layer and a data layer. The logic layer of the diagnostic system includes a data processing module, and the data layer of the diagnostic system includes data for the test environment and data for the formal environment. The data for the test environment includes entity data stored in an entity database for the test environment and configuration data stored in a configuration database for the formal environment, and the entity data and the configuration data correspond. The data processing module communicates with the publishing system to process the data information sent and received.

[0075] As mentioned above, the data in the first database or the second database may be obtained from corresponding data in the R&D environment. Figure 3 As shown, the publishing system is connected to the source system in communication, and the publishing system and the source system can together constitute a publishing platform. The source system is used to independently manage the entity database and configuration database in the R&D environment. The second database in the publishing system can obtain data from the configuration database of the source system, and the first database in the publishing system can obtain data from the entity database of the source system.

[0076] In some embodiments, Figure 3As shown, the source system includes a R&D environment data layer and a logic layer. The R&D environment data layer includes an entity database for the R&D environment and a configuration database for the R&D environment. The configuration data in the configuration database corresponds to the entity data in the entity database. The source system may include a data processing module, a basic data configuration module, and a basic data development tool.

[0077] Combination Figure 4 As shown, the basic data development tool is used to create entity data, encrypt the entity data and store it in the entity database for the R&D environment, and generate the entity data ID and data version. In addition, the basic data development tool is also used to develop and maintain the entity data it created, and after each development or maintenance, it is encrypted and stored in the entity database for the R&D environment.

[0078] Combination Figure 4 As shown, the basic data configuration module is used to maintain (including generate or update) the corresponding configuration data when the basic data development tool creates entity data or develops or maintains (development or maintenance can be understood as updating) entity data. The basic data configuration module is also used to store the configuration data corresponding to the entity data maintained by it in the configuration database used for the R&D environment. Therefore, the configuration data is associated with the entity data. In addition, combined with Figure 4 As shown, after the configuration data in the configuration database for the R&D environment is updated, the basic data configuration module is also used to send the updated configuration data and the configuration data with a development status of "developed" to the publishing system.

[0079] For example, when the basic data development tool updates the entity data of an entity data ID, the basic data configuration module correspondingly updates the development status, data version, and change information of the configuration data corresponding to the entity data to generate updated configuration data.

[0080] The data processing module is used to communicate with the publishing system to process the data information sent or received. Figure 4 As shown, the data processing module is used to enable the publishing system to obtain corresponding entity data based on the updated configuration data.

[0081] As a way to achieve this, Figure 3 As shown, the logic layer of the publishing system also includes a data processing module, which can communicate with the source system and the diagnostic system, and process the sent and received data information. The data processing module in the publishing system is also used to enable the publishing system to obtain the corresponding entity data (that is, the entity data to be updated) based on the updated configuration data. The entity data to be updated can be obtained from the entity database of the source system based on the target entity data ID and data version in the updated configuration data. That is, the entity data ID of the entity data to be updated is the target entity data ID.

[0082] In some embodiments, the data processing module is used to perform the following operations: receiving updated configuration data in a configuration database from a source system; updating a second database according to the updated (including replacement or addition) configuration data; and updating (including replacement or addition or deletion) a first database according to the updated configuration data in the second database. In this way, the updated configuration data in the source system can be received in a timely manner and entity data to be updated corresponding to the updated configuration data can be obtained based on the configuration data.

[0083] In an embodiment of the present application, the first database includes an entity database for a test environment and / or an entity database for a formal environment, and the second database includes a configuration database for a test environment and / or a configuration database for a formal environment.

[0084] As mentioned above, the updated configuration data is obtained after the source system updates the entity data in the entity database used for the R&D environment. And the updated configuration data is the configuration data whose development status is developed. As an example, the data content of the updated configuration data can be Figure 4 The configuration data content in the updated configuration data. The entity data ID included in the updated configuration data is the target entity data ID.

[0085] As an implementation method, the data processing module of the publishing system updates the second database according to the updated configuration data, specifically including: determining whether there is target configuration data corresponding to the target entity data ID in the second database according to the target entity data ID; in response to the target configuration data being present in the second database, replacing the target configuration data with the updated configuration data; in response to the target configuration data corresponding to the target entity data ID not being present in the second database, adding the updated configuration data to the second database. Among them, the target configuration data is the configuration data originally existing in the configuration database of the publishing system, and the entity data ID in the configuration data is the target entity data ID. The updated configuration data can be understood as the configuration data that the publishing system needs to use the latest.

[0086] As an implementation method, the data processing module of the publishing system updates the first database according to the updated configuration data in the second database, specifically including: determining whether there is target entity data corresponding to the target entity data ID in the first database; in response to the target entity data existing in the first database and the updated configuration data in the second database indicating that the entity data is available, using the entity data to be updated sent by the source system to replace the target entity data; in response to the target entity data not existing in the first database and the updated configuration data in the second database indicating that the entity data is available, adding the entity data to be updated sent by the source system to the first database; in response to the target entity data existing in the first database and the updated configuration data in the second database indicating that the entity data is disabled, deleting the target entity data. Wherein, the target entity data is the entity data existing in the first database when the updated configuration data is not updated to the second data, and the entity data ID of the target entity data is the same as the target entity data ID.

[0087] In some embodiments, the updated configuration data includes a checksum and a data version. Before replacing the target entity data with the entity data to be updated sent by the source system, the data processing module is used to perform the following operations: in response to the existence of the target entity data in the first database and the updated configuration data in the second database indicating that the entity data is available, a first check is performed on the target entity data based on the checksum and the data version to obtain a first check result; in response to the first check result indicating that the target entity data does not meet the consistency requirement, the entity data to be updated sent by the source system is received. This setting can ensure the security of data updates and avoid repeated data replacement.

[0088] In some embodiments, when the target entity data is replaced by the entity data to be updated sent by the source system or the entity data to be updated sent by the source system is added to the first database, the data processing module can be specifically used to perform the following operations: perform a second check on the entity data to be updated sent by the source system based on the check code and the data version to obtain a second check result; in response to the second check result indicating that the entity data to be updated sent by the source system meets the consistency requirement, the target entity data in the first database is replaced by the entity data to be updated sent by the source system or the entity data to be updated sent by the source system is added to the first database; in response to the second check result indicating that the entity data to be updated sent by the source system meets the inconsistency requirement, an error is reported and the updated configuration data in the second database is restored to the target configuration data. This setting can ensure the security of data updates and avoid invalid database updates.

[0089] As a specific example, Figure 5 As shown, the update logic flow of the test environment data in the publishing system includes steps S510-S572.

[0090] In step S510, the publishing system receives the configuration data sent by the basic data configuration module of the source system, which is updated and has a development status of "developed"; in step S520, the data processing module of the publishing system replaces or adds the configuration data to the configuration database of the test environment based on the entity data ID; in step S530, the data processing module of the publishing system determines the available status in the configuration data; regardless of whether it is available, execute step S540; in step S540, determine whether there is entity data corresponding to the entity data ID in the configuration data in the entity database of the test environment; if it is available and exists, execute step S551; if it is available and does not exist, execute step S552; if it is disabled and exists, execute step S553; if it is disabled and does not exist, the execution ends; In step S551, it determines whether the data version and the check code in the configuration data are consistent; in step S552, the data processing module of the source system sends the entity data ID and the entity data corresponding to the data version in the entity database of the R&D environment to the publishing system; in step S553, the entity data corresponding to the entity data ID is deleted; after step S552, it can also include step S560, verifying whether the entity data sent by the source system passes the data consistency based on the check code, if consistent, execute step S571, if inconsistent, execute step S572; in step S571, add the updated entity data to the entity database of the test environment; in step S572, the update fails, an error is reported and the configuration data is restored to the previous state.

[0091] As mentioned above, the release task can be constructed based on the job model. As an implementation method, the logical layer of the release system also includes a job model maintenance module, which is used to perform the following operations: construct the information of the job model based on the diagnostic system information, and the information of the job model includes but is not limited to: the job model ID and at least one diagnostic system ID associated with the job model ID, the job model name, the data type list associated with the job model ID and the creation time. The job model ID is the unique identification number of the job model. The at least one diagnostic system ID associated with the job model ID can also be referred to as the list of diagnostic system IDs associated with the job model ID. Based on this, the task release module is used to perform the following operations: construct the release task based on the information of the job model and generate the release task information. The release task is a periodic release task or a regular release task. The task ID is associated with a job model ID. The information of the release task can be as described above and will not be repeated here.

[0092] As an example, when the release task is a periodic release task, the task release module is Figure 3 The periodic release task module in the job model dynamically builds and executes the periodic release task based on the information of the job model. In some embodiments, the information (or configuration information) of the periodic release task is stored in Figure 3 The periodic task information library in the periodic release task configuration information includes but is not limited to: task ID; release cycle; job model ID; start-end time; target environment.

[0093] As another example, when the release task is a periodic release task, the release task module is Figure 3 The periodic label publishing module and the periodic task publishing module in the job model are provided. The periodic label publishing module dynamically constructs the publishing label based on the information of the job model. In some embodiments, the information of the publishing label includes the information of the periodic publishing task (or configuration information), and the publishing label can be stored in Figure 3 The release tag information includes but is not limited to: task ID; job model ID; release time; target environment: creation time. The regular release task module dynamically builds and executes regular release tasks, associates the test environment configuration data with the release tag to generate regular task information, and stores the regular task information in the regular task information library, where the release status is "pending release". Regular task information includes but is not limited to entity data ID, data version, task ID, release status, creation time, etc.

[0094] In some embodiments, Figure 3 As shown, the data layer of the publishing system may also include a job model information library, and the information of the job model may be stored in the job model information library.

[0095] As a specific example, Figure 6 As shown, when the release task is a periodic release task, the process of the release system dynamically constructing the diagnostic system and periodically automatically releasing the task configuration includes: in step S610, the diagnostic system maintenance module dynamically constructs the diagnostic system and the diagnostic system maintenance module maintains the information of the diagnostic system in real time; in step S620, the job model maintenance module dynamically constructs the information of the job model based on the information of the diagnostic system; in step S630, the periodic release task module dynamically constructs the periodic release task based on the job model and executes it.

[0096] As a specific example, Figure 7 As shown, when the release task is a periodic release task, the process of the release system dynamically constructing the diagnostic system and periodically and automatically releasing the task configuration includes: in step S710, the diagnostic system maintenance module dynamically constructs the diagnostic system and the diagnostic system maintenance module maintains the diagnostic system information in real time; in step S720, the job model maintenance module dynamically constructs the job model information based on the diagnostic system information; in step S730, the periodic release tag module dynamically constructs the release tag based on the job model; in step S740, the periodic release task module dynamically constructs the periodic release task and executes it.

[0097] As mentioned above, the data user end includes a vehicle identification information set and a user device set. The publishing task module in the publishing system can determine the target diagnostic system based on at least one diagnostic system ID in the information of the publishing task, the data user end in the information of the diagnostic system, and the data user end in the configuration data. The task ID is associated with the operation model ID, and the operation model ID is associated with at least one diagnostic system ID. Therefore, the task ID is associated with at least one diagnostic system ID. Based on this, the data user end associated with at least one diagnostic system ID associated with the task ID includes a first data set group and a second data set group. The first data set group is at least one vehicle identification information set associated one-to-one with at least one diagnostic system ID, and the second data set group is at least one user device set associated one-to-one with at least one diagnostic system ID.

[0098] As an implementation method, the release task module is used to perform the following operations to determine the target diagnostic system: the vehicle identification information set associated with the entity data ID in the configuration data is calculated as the first intersection with each vehicle identification information set in the first set group, wherein the vehicle identification information set in the first set group whose first intersection result is not empty is the target vehicle identification information set; the use device set associated with the entity data ID in the configuration data is calculated as the second intersection with each use device set in the second set group, wherein the use device set in the second set group whose second intersection result is not empty is the target use device set; the diagnostic system corresponding to the diagnostic system ID associated with the target vehicle identification information set and the target use device set is determined as the target diagnostic system. In this way, the target diagnostic system that needs to be updated can be determined based on the configuration information and the information of the release task. Therefore, by changing the configuration information or the information of the release task, it is also possible to build a new target diagnostic system or publish diagnostic data (entity data) to multiple different target diagnostic systems at the same time. The system configuration is simple, no secondary development of the system is required, the scalability of the data is improved, and the system development and maintenance costs are reduced.

[0099] In addition, since the source system, diagnostic system and publishing system in the embodiments of the present application are all equipped with an entity database and a corresponding configuration database, and the entity database is updated with changes in the configuration database, this method can ensure the consistency of the configuration data and the corresponding entity data in the same configuration environment and avoid data redundancy.

[0100] As described above, the publishing task module can execute the publishing task. In some embodiments, when the target environment corresponding to the publishing task is the formal environment, the publishing task module is used to perform the following operations: in response to the target environment being the formal environment, update the configuration data from the configuration database for the test environment of the publishing system to the configuration database for the formal environment of the publishing system; update the entity database for the formal environment according to the configuration data updated to the configuration database for the formal environment; execute the publishing task to publish the configuration data updated to the configuration database for the formal environment to the formal environment of the target diagnostic system.

[0101] That is to say, when the publishing task indicates that the database of the formal environment of the target diagnostic system needs to be updated, the configuration database and entity database of the formal environment of the publishing system can be updated first, and then the configuration database of the target diagnostic system can be updated based on the configuration database of the formal environment of the publishing system, and the entity database of the target diagnostic system can be updated based on the update of the configuration database of the target diagnostic system.

[0102] In this way, the test environment and the formal environment can be isolated, thereby ensuring data security. At the same time, it also ensures that the entity data and configuration data in different systems and environments remain consistent, thereby reducing data maintenance costs and improving data scalability.

[0103] In order to further manage the data publishing of the publishing system, in some embodiments, the data processing module of the publishing system is also used to perform the following operations: receiving the update results sent by the target diagnostic system, the update results are used to indicate whether the publishing task is successfully published; generating publishing result information based on the update results. The publishing result information includes but is not limited to at least one of the following information: entity data ID, data version, task ID, target diagnostic system ID, target environment, publishing result, execution time. The results of the publishing include publishing termination, publishing success, publishing failure, etc. In some embodiments, the publishing result information can be stored in a Figure 3 The published information database is shown.

[0104] In order to manage the release version, in some embodiments, the database of the release system may also include a fourth database for storing release version information. The fourth database is as follows: Figure 3 The data processing module is also used to perform the following operations: in response to the update result indicating that the release task is successfully released and the target environment is the formal environment, generate the current release version information of the entity database of the formal environment of the target diagnostic system, the current release version information includes but is not limited to at least one of the following information: target diagnostic system ID, release version, entity data ID, data version, configuration data ID, update time; store the current release version information in Figure 3 The release repository shown; Figure 3 The release version of the diagnostic system information corresponding to the target diagnostic system in the database of the diagnostic system is updated to the current release version.

[0105] In order to further implement the version management of vehicle diagnostic data of each target diagnostic system based on the release version information library, in some embodiments, such as Figure 3 As shown, the logic layer of the publishing system also includes a publishing data management module. The publishing data management module can be used to execute publishing termination, publishing version data rollback or publishing version data comparison. These tasks can be based on button triggering or event triggering, etc.

[0106] As an example, the release data management module is used to perform the following operations: in response to the need to roll back the current release version in the formal environment of the target diagnostic system to the target historical release version, obtain the first configuration data ID in the information of the current release version and the second configuration data ID in the information of the target historical release version from the fourth database based on the target diagnostic system ID; obtain the first configuration data corresponding to the first configuration data ID and the second configuration data corresponding to the second configuration data ID from the configuration database of the formal environment of the target diagnostic system; determine the difference in entity data based on the first configuration data and the second configuration data, the difference in entity data being used to characterize the difference between the entity data corresponding to the second configuration data ID and the entity data corresponding to the first configuration data ID; publish the second configuration data and the difference in entity data to the target diagnostic system, so that the target diagnostic system updates the configuration database of the formal environment of the target diagnostic system based on the second configuration data and updates the entity database of the formal environment of the target diagnostic system based on the second configuration data.

[0107] In order to further manage the periodic release task, in some embodiments, the release task is a periodic release task, and the periodic release task has corresponding periodic release task information, and the periodic release task information includes the following interrelated information: data ID, task ID, release status, wherein before the periodic release task is executed, the release status is pending release. Before executing the periodic release task, the release data management module is used to perform the following operations: establish a release termination task, and the release termination task includes a task ID and a data ID; based on the task ID and data ID of the termination task ID, modify the release status of the task ID of the target task in the periodic release task information to release termination and generate a release result, and the release result indicates release termination; send the release result to the fifth database for storing release information.

[0108] The task ID of the target task is the task ID of the task whose publishing status is to be published in the regularly published task information, and the task ID of the target task is the same as the task ID of the terminated task, and the data ID associated with the task ID of the target task is the same as the data ID of the published terminated task. Figure 3 The published information database.

[0109] In some embodiments, Figure 3 As shown, the logic layer of the publishing system may further include a publishing information query module, which obtains historical publishing result information based on different screening conditions.

[0110] As mentioned above, the publishing task module can automatically execute the publishing task according to the information of the publishing task. Figure 8 The process of the publishing system in the embodiment of the present application to periodically and periodically automatically publish task execution logic is described in detail. Figure 8 As shown, the process includes steps S811-S890.

[0111] In step S811, the periodic publishing task module of the publishing system creates a periodic publishing task.

[0112] In step S812, the publishing system continuously detects the configuration data in the configuration database of the test environment according to the specified period (or event triggering) within the start-end time specified by the periodic publishing task;

[0113] In step S813, it is determined whether the configuration data is updated. If so, the process continues to step S814; if not, the process ends and waits for the next cycle.

[0114] In step S814, the updated configuration data is published to the target environment of the server of the matched one or more diagnostic systems according to the specified operation model, wherein the matched one or more diagnostic systems are the target diagnostic systems mentioned above.

[0115] In step S821, the regular publishing task module of the publishing system creates a regular publishing task.

[0116] In step S822, the designated publishing time triggers (or event triggers) the execution of the publishing task, and adjusts the publishing status in the periodic task information corresponding to the task ID to "published".

[0117] In step S823, the regular publishing task publishes the configuration data with the publishing status "to be published" in the regular task information to the target environment of the server of one or more matching target diagnosis systems according to the associated publishing tag information. After step S823 and step S814, step 830 is executed.

[0118] In step 830, the data processing module of the target diagnostic system updates the acquired configuration data to the corresponding target environment configuration database.

[0119] In step 840 , the data processing module of the target diagnosis system updates the entity database corresponding to the target environment based on the configuration data content.

[0120] In step 850, the data processing module of the target diagnosis system feeds back the update result to the diagnosis basic data publishing system.

[0121] In step 860, the diagnostic basic data publishing system data processing module generates publishing result information and stores it in the publishing information database.

[0122] In step 870 , it is determined whether the update is successful and whether the target environment is the formal environment. If the update is successful and the target environment is the formal environment, step 880 is executed.

[0123] In step 880, the data processing module of the publishing system generates the latest (or current) publishing version information of the formal environment database of the target diagnosis system and stores it in the publishing version information library.

[0124] In step 890, the release version corresponding to the target diagnostic system information in the target system information repository is updated to the latest release version.

[0125] Among them, step S814 and step S823 may specifically include the following contents.

[0126] Determine the target diagnostic system. Specifically, it includes: obtaining the vehicle identification information list Vehicle_Ids_0 and the user object list Users_0 in the configuration data; obtaining one or more diagnostic systems Target_Systems_0 associated with the operation model, and the vehicle identification information list Vehicle_Ids_1 and the user object list Users_1 associated with the diagnostic system; matching the intersection of the vehicle identification information list Vehicle_Ids_1 and Vehicle_Ids_0 and the one or more diagnostic systems (the one or more diagnostic systems are the target diagnostic system) Target_Systems_1 whose intersection of the user object list Users_1 and Users_0 is not empty.

[0127] Determine the target environment, including the following:

[0128] If the target environment is the test environment of the target diagnostic system, the configuration data is sent to the test environment database of the target diagnostic system Target_Systems_1.

[0129] If the target environment is the formal environment of the target diagnostic system, the configuration data is added to the configuration database of the formal environment of the publishing system, and the configuration data content is increased by the configuration data ID. The configuration data ID refers to the unique identifier of the configuration data. Then, based on the configuration data content, the difference entity data is added to the entity database of the formal environment of the publishing system, and then the configuration data is sent to the formal environment database of the target diagnostic system Target_Systems_1.

[0130] The method for adding entity data with differences based on the configuration data content to the entity database of the formal environment of the publishing system is as follows.

[0131] If the available status in the configuration data is "available", determine whether there is entity data corresponding to the entity data ID and data version in the configuration data in the formal entity database;

[0132] If there is no entity data, obtain the entity data corresponding to the entity data ID and data version in the configuration data from the test environment entity database, and verify the data consistency based on the checksum. If it fails, the update fails, an error is reported, and the configuration data is restored to the previous state. If it passes, add the entity data to the formal environment entity database;

[0133] If there is entity data, verify the data consistency based on the data version and checksum in the configuration data. If they are inconsistent, obtain the entity data corresponding to the entity data ID and data version in the configuration data from the test environment entity database, and verify the data consistency based on the checksum. If it fails, the update fails, an error is reported, and the configuration data is restored to the previous state. If it passes, add the entity data to the formal environment entity database.

[0134] If the available status in the configuration data is "disabled", it is not processed.

[0135] The above-mentioned step 840 may specifically include the following contents.

[0136] If the available status in the configuration data is "available", it is determined whether there is entity data corresponding to the entity data ID in the configuration data in the target environment entity database corresponding to the target diagnosis system;

[0137] If there is no entity data, the data processing module of the diagnostic basic data publishing system sends the entity data corresponding to the entity data ID and data version in the target environment entity database. The target diagnostic system obtains and verifies the data consistency based on the verification code. If it fails, the update fails, an error is reported, and the configuration data is restored to the previous state. If it passes, the updated entity data is added to the target environment entity database corresponding to the target diagnostic system;

[0138] If there is entity data, the data consistency is verified based on the data version and verification code in the configuration data. If it is inconsistent, the data processing module of the diagnostic basic data publishing system sends the entity data corresponding to the entity data ID and data version in the target environment entity database. The target diagnostic system obtains and verifies the data consistency based on the verification code. If it fails, the update fails, an error is reported, and the configuration data is restored to the previous state. If it passes, the updated entity data is added to the target diagnostic system corresponding to the target environment entity database.

[0139] If the available status in the configuration data is "disabled", it is determined whether there is entity data corresponding to the entity data ID in the target environment entity database corresponding to the target diagnostic system, and if so, it is deleted.

[0140] As mentioned above, the release data management module can execute release termination and release version data rollback. Fig.10 The execution logic of this process is described.

[0141] For data with a release status of "pending release" in the periodic task information, the release data management module of the release system needs to execute the specific method of release termination, such as Fig. 9 As shown, it specifically includes steps S910-S960.

[0142] In step S910, the publishing data management module sends "a data set of periodic task information with a filtering publishing status of "to be published"" to the periodic task information library;

[0143] In step S920, the periodic task information library returns the screened data set to the publishing data management module;

[0144] In step S930, the publishing data management module sends "screening periodic task information based on task ID and entity data ID, and modifying the corresponding publishing status to "publishing terminated"" to the periodic task information library;

[0145] In step S940, the periodic task information library returns the execution result to the publishing data management module;

[0146] In step S950, the publishing data management module generates publishing result information, where the publishing result is assigned the value "publishing terminated"

[0147] In step S960, the publishing data management module sends the publishing result to the publishing information database.

[0148] The specific method of rolling back the database of the formal environment of the target diagnostic system to the data corresponding to the historical release version based on the release version is as follows Fig.10 As shown. Fig.10 The process shown includes steps S1010-S1092.

[0149] In step S1010, the publishing data management module of the publishing system obtains the publishing version information of the formal environment data from the publishing version information library based on the target system ID;

[0150] In step S1020, the release data management module obtains the current release version from the target system information repository;

[0151] In step S1030, the release data management module obtains the configuration data ID corresponding to the historical release version and the current release version of the target diagnostic system from the release version information.

[0152] In step S1040, the publishing data management module obtains configuration data corresponding to the configuration data ID from the configuration database of the formal environment;

[0153] In step S1050, the release data management module obtains entity data difference results based on the configuration data of the current release version and the historical release version; the difference includes addition, replacement, deletion, etc.

[0154] In step S1060, the publishing data management module deserializes the entity data information of the difference based on the difference result;

[0155] In step S1070, the published data management module publishes the configuration data corresponding to the historical published version and the entity data of the difference to the corresponding target diagnosis system;

[0156] In step S1080, the target diagnosis system data processing module updates the configuration database of the formal environment of the target diagnosis system to the configuration data of the historical release version;

[0157] In step S1090, the target diagnosis system updates the entity data of the entity database of the formal environment based on the configuration data of the historical version; the updating method is adding, replacing, or deleting;

[0158] In step S1091, the target diagnosis system returns the execution result to the published data management module; if the formal environment configuration data and entity data of the target diagnosis system are all changed successfully, the change result is fed back to the published data management module, so that the published data management module executes step S1092;

[0159] In step S1092, the release data management module updates the release version corresponding to the target diagnostic system information in the target system information repository.

[0160] In some embodiments, if a target diagnostic system fails during the process of changing the formal environment configuration data or entity data, the target diagnostic system rolls back to the original data state through a transaction mechanism (such as a Java transaction locking mechanism) and feeds back the failure result to the publishing system.

[0161] As mentioned above, the release data management module in the embodiment of the present application is also used to perform release version data comparison. Fig.11 A detailed description is given of the comparison of target system data of different release versions of the target diagnostic system's formal environment. Fig.11 As shown, the execution logic of the release version data comparison includes steps S1110-S1160.

[0162] In step S1110, the release data management module obtains release version information of different release versions from the release version information library based on the target diagnosis system ID;

[0163] In step S1120, the release data management module compares different release version information, and screens the release version information with data version or configuration data ID differences based on the entity data ID; wherein the differences include addition, deletion, difference, etc.;

[0164] In step S1130, configuration data of different release versions are obtained based on the configuration data ID in the different release version information;

[0165] In step S1140, the difference field contents in the configuration data of different release versions are displayed;

[0166] Step S1150 , obtaining entity data files of different release versions based on the entity data ID and data version in the differential release version information;

[0167] In step S1160, the difference field contents in the configuration data of different release versions are displayed.

[0168] The above difference fields can all be compared using the Git difference comparison tool to obtain differences.

[0169] In some embodiments, Figure 3 In the publishing platform and target diagnosis system shown, the logic modules of the source system, publishing system, and target diagnosis system can be built based on the Spring Boot framework, and the system distributed microservice architecture module is executed based on the Spring Cloud framework. The sending and receiving of data between various systems are implemented using HTTP communication and message queue framework. The HTTP protocol sends request and receives response data objects to achieve data interaction; the message queue framework implements asynchronous communication and improves the scalability and flexibility of the system. Common message queue frameworks include RabbitMQ, RocketMQ, Kafka, etc.

[0170] In addition, an embodiment of the present application also provides a method for publishing vehicle diagnostic data, which is applied to the vehicle diagnostic data publishing system mentioned above, and the publishing system includes: a first database for storing entity data, a second database for storing configuration data, and a third database for storing diagnostic system information, the entity data has an entity data ID, the configuration data is used to indicate the entity data and the configuration data includes the entity data ID, a data user associated with the entity data ID, and the diagnostic system information includes the diagnostic system ID and the data user associated with the diagnostic system ID; the method includes: constructing a publishing task according to the information of the diagnostic system and generating information for the publishing task, the information for the publishing task includes a task ID associated with at least one diagnostic system ID, a publishing time plan, and a target environment; determining a target diagnostic system according to the at least one diagnostic system ID in the information of the publishing task, the data user in the information of the diagnostic system, and the data user in the configuration information; executing the publishing task according to the information of the publishing task to publish the configuration data to the target environment of the target diagnostic system, and after the target diagnostic system updates the configuration data to the configuration database of the target diagnostic system, updating the entity database of the target diagnostic system based on the configuration data.

[0171] The embodiment of the present application also provides a machine-readable storage medium for storing a program, and the program enables a computer to execute the method in each embodiment of the present application.

[0172] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The program enables a computer to execute the method in each embodiment of the present application.

[0173] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a machine-readable storage medium, or transmitted from one machine-readable storage medium to another machine-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The machine-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0174] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments of the present disclosure can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present disclosure.

[0175] In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0176] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0177] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0178] The above is only a specific embodiment of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present disclosure, which should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A vehicle diagnostic data publishing system, characterized in that: include: The data layer includes a first database for storing entity data, a second database for storing configuration data, and a third database for storing information of a diagnostic system; the entity data has an entity data ID, the configuration data is used to indicate the entity data and the configuration data includes the entity data ID and a data user associated with the entity data ID, and the information of the diagnostic system includes a diagnostic system ID and a data user associated with the diagnostic system ID; The logic layer includes a task publishing module, which is used to perform the following operations: Constructing a release task according to the information of the diagnostic system and generating information of the release task, wherein the information of the release task includes a task ID associated with at least one of the diagnostic system IDs, a release time plan, and a target environment; Determine a target diagnostic system according to the at least one diagnostic system ID in the information of the published task, the data user in the information of the diagnostic system, and the data user in the configuration data; The publishing task is executed according to the information of the publishing task to publish the configuration to the target environment of the target diagnostic system, and after the target diagnostic system updates the configuration data to the configuration database of the target diagnostic system, the entity database of the target diagnostic system is updated based on the configuration data.

2. The publishing system according to claim 1, characterized in that: The publishing system is in communication with a source system, the source system includes an entity database and a configuration database for a research and development environment, the configuration data in the configuration database corresponds to the entity data in the entity database, and the logic layer also includes a data processing module, the data processing module is used to perform the following operations: receiving updated configuration data in the configuration database from the source system, wherein the updated configuration data is obtained after the source system updates entity data in the entity database for the R&D environment; updating the second database according to the updated configuration data; updating the first database according to the updated configuration data in the second database; The first database includes an entity database for a test environment and / or an entity database for a formal environment, and the second database includes a configuration database for a test environment and / or a configuration database for a formal environment.

3. The publishing system according to claim 2, characterized in that: The entity data ID in the updated configuration data is the target entity data ID, and the data processing module is used to perform the following operations: Determine, according to the target entity data ID, whether there is target configuration data corresponding to the target entity data ID in the second database; In response to the target configuration data being present in the second database, replacing the target configuration data with the updated configuration data; In response to the target configuration data corresponding to the target entity data ID not being present in the second database, the updated configuration data is added to the second database.

4. The publishing system according to claim 2, characterized in that: The data processing module is used to perform the following operations: Determine whether there is target entity data corresponding to the target entity data ID in the first database; In response to the target entity data existing in the first database and the updated configuration data in the second database indicating that entity data is available, using the source system to send the entity data to be updated to replace the target entity data; In response to the target entity data not existing in the first database and the updated configuration data in the second database indicating that the entity data is available, adding the entity data to be updated sent by the source system to the first database; In response to the target entity data existing in the first database and the updated configuration data in the second database indicating that entity data is disabled, the target entity data is deleted.

5. The publishing system according to claim 4, characterized in that: The updated configuration data includes a checksum and a data version, and the data processing module is used to perform the following operations: In response to the target entity data existing in the first database and the updated configuration data in the second database indicating that the entity data is available, performing a first check on the target entity data based on the check code and the data version to obtain a first check result; In response to the first verification result indicating that the target entity data does not meet the consistency requirement, the entity data to be updated sent by the source system is received.

6. The publishing system according to claim 1, characterized in that: The logic layer also includes a job model maintenance module, which is used to perform the following operations: Constructing information of an operation model according to the diagnostic system information, wherein the information of the operation model includes an operation model ID and at least one of the diagnostic system IDs associated with the operation model ID; The task publishing module is used to perform the following operations: The publishing task is constructed according to the information of the operation model and the information of the publishing task is generated. The publishing task is a periodic publishing task or a regular publishing task. The task ID is associated with the operation model ID.

7. The publishing system according to claim 6, characterized in that: The data user end includes a vehicle identification information set and a user device set, and the data user end associated with at least one of the diagnostic system IDs associated with the task ID includes a first data set group and a second data set group, wherein the first data set group is at least one vehicle identification information set associated one-to-one with the at least one diagnostic system ID, and the second data set group is at least one user device set associated one-to-one with the at least one diagnostic system ID. The publishing task module is used to perform the following operations: Finding a first intersection of the vehicle identification information set associated with the entity data ID in the configuration data and each vehicle identification information set in the first set group, wherein the vehicle identification information set in the first set group whose first intersection result is not empty is the target vehicle identification information set; Calculate a second intersection of the usage device set associated with the entity data ID in the configuration data and each usage device set in the second set group, wherein the usage device set in the second set group whose second intersection result is not empty is the target usage device set; A diagnostic system corresponding to a diagnostic system ID commonly associated with the target vehicle identification information set and the target user device set is determined as a target diagnostic system.

8. The publishing system according to claim 1, characterized in that: The data processing module is also used to perform the following operations: receiving an update result sent by the target diagnosis system, wherein the update result is used to indicate whether the release task is released successfully; The publishing result information is generated according to the update result, and the publishing result information includes at least one of the following information: entity data ID, data version, task ID, target diagnosis system ID, target environment, publishing result, and execution time.

9. The publishing system according to claim 8, characterized in that: The data layer also includes a fourth database for storing release version information, and the data processing module is further used to perform the following operations: In response to the update result indicating that the release task is successfully released and the target environment is a formal environment, generating information of a current release version of the entity database of the formal environment of the target diagnostic system, wherein the information of the current release version includes at least one of the following information: target diagnostic system ID, release version, entity data ID, data version, configuration data ID, and update time; Storing the information of the current release version in the fourth database; The release version of the diagnostic system information corresponding to the target diagnostic system in the third database is updated to the current release version.

10. The publishing system according to claim 9, characterized in that: The logic layer also includes a publishing data management module, which is used to perform the following operations: In response to the need to roll back the current release version in the formal environment of the target diagnostic system to a target historical release version, acquiring, from the fourth database based on the target diagnostic system ID, a first configuration data ID in the information of the current release version and a second configuration data ID in the information of the target historical release version; Acquire, from a configuration database of the formal environment of the target diagnostic system, first configuration data corresponding to the first configuration data ID and second configuration data corresponding to the second configuration data ID; Determine different entity data based on the first configuration data and the second configuration data, where the different entity data is used to represent the difference between the entity data corresponding to the second configuration data ID and the entity data corresponding to the first configuration data ID; The second configuration data and the differential entity data are published to the target diagnostic system, so that the target diagnostic system updates the configuration database of the formal environment of the target diagnostic system based on the second configuration data and updates the entity database of the formal environment of the target diagnostic system based on the second configuration data.

11. The publishing system according to claim 7, characterized in that: The publishing task is the regular publishing task, and the regular publishing task has corresponding regular publishing task information, and the regular publishing task information includes the following interrelated information: data ID, task ID, publishing status, wherein before the regular publishing task is executed, the publishing status is to be published, and before the execution of the publishing task, the publishing data management module is used to perform the following operations: Establishing a publishing termination task, wherein the publishing termination task includes a task ID and a data ID; Based on the task ID and data ID of the terminated task, modify the publishing status of the task ID of the target task in the periodic publishing task information to publishing termination and generate a publishing result, wherein the publishing result indicates publishing termination; The publishing result is sent to a fifth database for storing publishing information.

12. A method for publishing vehicle diagnostic data, characterized in that: The method is applied to a vehicle diagnostic data publishing system, the publishing system comprising: a first database for storing entity data, a second database for storing configuration data, and a third database for storing diagnostic system information, the entity data having an entity data ID, the configuration data for indicating the entity data and the configuration data comprising the entity data ID and a data user associated with the entity data ID, the diagnostic system information comprising a diagnostic system ID and a data user associated with the diagnostic system ID; The method comprises: Constructing a release task according to the information of the diagnostic system and generating information of the release task, wherein the information of the release task includes a task ID associated with at least one of the diagnostic system IDs, a release time plan, and a target environment; Determine a target diagnostic system according to the at least one diagnostic system ID in the information of the published task, the data user in the information of the diagnostic system, and the data user in the configuration data; The publishing task is executed according to the information of the publishing task to publish the configuration data to the target environment of the target diagnostic system, and after the target diagnostic system updates the configuration data to the configuration database of the target diagnostic system, the entity database of the target diagnostic system is updated based on the configuration data.

13. A computer program product, characterized in that include: A computer program / instruction which, when executed by a processor, implements the method as claimed in claim 12.

Images