Cross-system data collaboration method and device, medium, equipment and program product

Abstract

The invention discloses a cross-system data collaboration method and device, a medium, equipment and a program product. The method comprises the following steps: acquiring to-be-processed hardware identification information; based on the hardware identification information, acquiring corresponding software and hardware associated data from a product data management system, and acquiring corresponding hardware production data from a production management system; according to the software and hardware associated data and the hardware production data, executing a query action corresponding to the hardware identification information type to obtain one or more pieces of candidate software version information; outputting the one or more pieces of candidate software version information as final software version information; and if multiple pieces of candidate software version information exist, performing cross validation and then outputting final software version information. According to the invention, precise and efficient positioning and closed-loop cooperation can be carried out on software and hardware versions of the engineering machinery.

Description

Technical Field

[0001] This invention relates to a cross-system data collaboration method, apparatus, medium, equipment, and program product, belonging to the field of data management technology. Background Technology

[0002] As the level of intelligence in construction machinery increases, the coupling between its software and hardware is becoming increasingly tight. Hardware platforms are diverse, and the accompanying software versions are numerous and iterated frequently, with strict correspondences between the software and hardware. This makes accurate and efficient software version identification and traceability a key technical challenge in equipment research and development, production, after-sales service, and procurement.

[0003] In the existing technological practices of the construction machinery industry, there are several technical challenges that urgently need to be addressed regarding the coordination and positioning of software and hardware versions.

[0004] Version matching usually relies on manually reviewing scattered documents or consulting with technical personnel through informal channels. This is not only time-consuming, but also prone to version mismatch due to outdated information, transmission errors, or human oversight. This can easily lead to abnormal equipment functions, performance degradation, or system failures, resulting in unplanned downtime and maintenance losses.

[0005] Software and hardware version-related data is scattered across multiple independent systems: the Product Data Management (PDM) system stores the compatibility relationships defined during the R&D phase; the Production Management System records the pre-installed software information when the hardware leaves the factory; the After-Sales Service Platform receives on-site feedback; and the Enterprise Resource Planning (ERP) system maintains material master data. The lack of an efficient and automated data synchronization mechanism between systems, relying on manual import / export or periodic batch processing for data exchange, results in data update delays, poor consistency, and difficulty in accurately tracing after-sales feedback back to the R&D end.

[0006] During equipment production or maintenance, the procurement process often struggles to automatically obtain the software information that accompanies the hardware, which can lead to software omissions or version mismatches. This can affect the equipment's assembly, debugging, and delivery schedules, and increase additional coordination costs.

[0007] Several technical solutions have attempted to address these issues. For example, Chinese patent CN115809441A discloses a method for associating versions with devices. It constructs a comparison database based on the hash values ​​of device and version numbers, and uses QR codes to compare versions with devices. This solution establishes a mapping relationship between devices and versions, but its association dimension is relatively simple, primarily serving offline version verification and failing to support refined traceability and real-time querying based on multi-dimensional information such as production batches and serial numbers. Another example is Chinese patent CN119383077A, which discloses a cross-platform interface configuration method, device, and equipment for engineering machinery vehicle data. It responds to the access selection of third-party vehicle networking systems, establishes protocol field mapping pairing groups, and configures conversion formulas. This solution focuses on the conversion and communication of specific data formats and does not involve the construction, management, and full-process closed-loop collaboration of software and hardware version relationships.

[0008] Therefore, existing technical solutions mostly focus on solving local or single-stage problems, and generally suffer from problems such as limited functionality, weak collaboration, and inability to support refined traceability of the entire lifecycle of software and hardware versions. They are difficult to meet the comprehensive technical needs of the construction machinery industry for cross-system, full-process, high-precision real-time collaboration and closed-loop management of software and hardware versions. Summary of the Invention

[0009] The purpose of this invention is to overcome the shortcomings of existing technologies and provide a cross-system data collaboration method, device, medium, equipment, and program product, capable of accurate and efficient positioning and closed-loop collaboration of engineering machinery software and hardware versions. To achieve the above objective, this invention employs the following technical solution:

[0010] In a first aspect, the present invention provides a cross-system data collaboration method, comprising:

[0011] Obtain the hardware identification information to be processed;

[0012] Based on the hardware identification information, obtain the corresponding software and hardware association data from the product data management system, and obtain the corresponding hardware production data from the production management system.

[0013] Based on the acquired software and hardware association data and hardware production data, a query action corresponding to the hardware identification information type is executed to obtain one or more candidate software version information; wherein, the query action includes at least one of matching query based on hardware model, parsing query based on hardware material number, and tracing query based on equipment serial number;

[0014] Output the one or more candidate software version information as the final software version information; if there are multiple candidate software version information, perform cross-validation and output the final software version information.

[0015] In conjunction with the first aspect, optionally, the step of obtaining corresponding software and hardware association data from the product data management system and obtaining corresponding hardware production data from the production management system based on the hardware identification information includes:

[0016] When the hardware identification information is a hardware model or hardware material number, the corresponding software and hardware association data is obtained from the product data management system.

[0017] When the hardware identification information is a device serial number, hardware production data containing the hardware production batch and pre-installed software records of the device serial number is obtained from the production management system.

[0018] In conjunction with the first aspect, optionally, the matching query based on hardware model includes:

[0019] Using the hardware model in the hardware identification information as the query condition, a matching search is performed in the software and hardware related data;

[0020] Output information on all candidate software versions that are compatible with the hardware model.

[0021] In conjunction with the first aspect, optionally, the step of parsing and querying based on the hardware component number includes:

[0022] According to the predefined material coding rules, the hardware material number in the hardware identification information is parsed to extract the key identifiers used for association query;

[0023] Based on key identifiers, matching is performed in software and hardware related data to obtain candidate software version information.

[0024] In conjunction with the first aspect, optionally, the traceability query based on the device serial number includes:

[0025] Using the device serial number in the hardware identification information as an index, the software version record pre-installed at the factory is queried in the hardware production data and used as the first candidate software version information;

[0026] If the records in the hardware production data are incomplete, a supplementary query request will be sent to the product data management system based on the production batch information associated with the device serial number in the hardware identification information to obtain the second candidate software version information.

[0027] The obtained first candidate software version information and / or second candidate software version information are used as candidate software version information.

[0028] In conjunction with the first aspect, optionally, if multiple candidate software version information exists, cross-validation is performed, including:

[0029] Compare multiple candidate software version information from different query actions;

[0030] If the version information matches, output the final software version information;

[0031] If the version information is inconsistent, the conflict will be resolved based on the effective time of the association in the software and hardware association data and the production timestamp in the hardware production data, or a report containing inconsistent version information and its source will be generated for the user to choose from.

[0032] In a second aspect, the present invention provides a cross-system data collaboration device, comprising:

[0033] Acquisition module: used to acquire hardware identification information to be processed; based on the hardware identification information, to acquire corresponding software and hardware association data from the product data management system, and to acquire corresponding hardware production data from the production management system;

[0034] Query module: used to perform a query action corresponding to the hardware identification information type based on the acquired software and hardware association data and hardware production data, to obtain one or more candidate software version information; wherein, the query action includes at least one of matching query based on hardware model, parsing query based on hardware material number, and tracing query based on equipment serial number;

[0035] Output module: Used to output the one or more candidate software version information as the final software version information; if there are multiple candidate software version information, the final software version information is output after cross-validation.

[0036] Thirdly, the present invention provides a computer-readable storage medium having a computer program / instructions stored thereon, which, when executed by a processor, implements the steps of the cross-system data collaboration method described in the first aspect.

[0037] Fourthly, the present invention provides a computer device, comprising:

[0038] Memory, used to store computer programs / instructions;

[0039] A processor for executing the computer program / instructions to implement the steps of the cross-system data collaboration method described in the first aspect.

[0040] Fifthly, the present invention provides a computer program product, including a computer program / instruction that, when executed by a processor, implements the cross-system data collaboration steps described in the first aspect.

[0041] Compared with the prior art, the beneficial effects achieved by the cross-system data collaboration method, apparatus, medium, device, and program product provided in the embodiments of the present invention include:

[0042] This invention acquires hardware identification information to be processed; based on the hardware identification information, it obtains corresponding software and hardware related data from the product data management system and corresponding hardware production data from the production management system; this invention establishes a data interface and synchronization mechanism with the product data management system and the production management system, ensuring the timeliness and consistency of software and hardware related data and production data, breaking down data barriers between systems, and providing a reliable and real-time data foundation for version positioning;

[0043] This invention, based on the acquired software and hardware association data and hardware production data, performs a query action corresponding to the hardware identification information type to obtain one or more candidate software version information; wherein, the query action includes at least one of matching query based on hardware model, parsing query based on hardware material number, and tracing query based on equipment serial number; by integrating three query paths—hardware model matching, hardware material number parsing, and equipment serial number tracing—and combining data from the product data management system and the production management system for cross-validation, this invention can handle information input under different scenarios, significantly improve the coverage and accuracy of version queries, and effectively reduce the risk of equipment failure caused by version mismatch;

[0044] This invention outputs one or more candidate software version information as the final software version information; if there are multiple candidate software version information, the final software version information is output after cross-validation; this invention outputs candidate software version information, which not only realizes the positive flow and query application of data from R&D, production to after-sales, but also provides accurate reverse data input for R&D optimization and procurement decisions through the connection of after-sales feedback and procurement information, forming a data application and optimization closed loop that runs through the entire life cycle of construction machinery;

[0045] This invention provides precise and efficient positioning and closed-loop coordination of the software and hardware versions of engineering machinery, which can directly serve equipment maintenance, upgrades and troubleshooting, and effectively shorten downtime caused by software problems. Attached Figure Description

[0046] Figure 1 This is a flowchart illustrating a cross-system data collaboration method provided in Embodiment 1 of the present invention;

[0047] Figure 2 This is a flowchart illustrating the cross-validation process for query actions in a cross-system data collaboration method provided in Embodiment 1 of the present invention.

[0048] Figure 3 This is an overall architecture diagram of data collaboration in a cross-system data collaboration method provided in Embodiment 1 of the present invention. Detailed Implementation

[0049] The present invention will be further described below with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and should not be used to limit the scope of protection of the present invention.

[0050] Example 1:

[0051] like Figure 3 As shown in the figure, this embodiment provides an overall architecture diagram of data collaboration in a cross-system data collaboration method, including a core data storage unit, two major functional modules and a cross-system collaboration layer.

[0052] The core data storage unit is a hardware and software related data storage unit that adopts a distributed data storage architecture to ensure high availability, consistency and traceability of data. It includes: core business tables, system support tables and database maintenance mechanisms.

[0053] The core business tables include a hardware information table, a software information table, and a software and hardware relationship table.

[0054] The hardware information table stores key information such as hardware identifier (Hardware_ID), model (Model), part number (Part_Number), serial number (Serial_Number), production batch (Batch_ID), and the identifier of the complete machine to which it belongs, providing basic data support for multi-mode positioning.

[0055] The software information table stores core attributes such as software identifier (Software_ID), version number (Version), software part number (SW_Part_Number), installation location (e.g., controller model), and version change description, and supports software compatibility determination.

[0056] To achieve accurate multi-dimensional association, the hardware and software association table is used to store multi-dimensional mapping relationships such as control unit identifier (ECU_ID), hardware identifier (Hardware_ID), software identifier (Software_ID), association type (such as standard adaptation, optional), association effective time (Valid_From), and association expiration time (Valid_To), so as to achieve accurate association between hardware and software.

[0057] The software and hardware relationship table supports full lifecycle traceability of the same hardware adapting to different software versions at different times, solving the industry pain point of chaotic adaptation between different batches of the same model.

[0058] The system support tables include a data synchronization log table and a data verification rule table.

[0059] The data synchronization log table is used to record detailed information for each cross-system data synchronization, including timestamp, synchronization type, amount of synchronized data, operation result (success / failure), error information, etc., for fault tracing and efficiency analysis.

[0060] The data validation rule table is used to store field-level validation logic and the validation logic of association consistency rules in a configurable manner, and supports dynamic updates of the rules.

[0061] The database maintenance mechanism includes the following steps:

[0062] Initialization: By calling the API interface provided by the Product Data Management System (PDM system), historical hardware information tables, software information tables, and hardware / software relationship tables are imported in batches. Data validation rules are used to validate the imported data to ensure data integrity.

[0063] Incremental Updates: When software compatibility changes occur in the Product Data Management (PDM) system, a real-time synchronization to the core data storage unit is triggered via event notification. The Production Management System pushes relevant data (such as data packages containing serial numbers, batch numbers, and pre-installed software versions) in real-time when hardware leaves the factory.

[0064] Data validation: Perform full data validation periodically, check the legality and consistency of data based on the data validation rule table, and issue an alert and temporarily store the abnormal data if abnormal data is found.

[0065] Disaster recovery backup: A multi-node backup mode is adopted to ensure data security and availability.

[0066] The two main functional modules include a software version location module and a cross-system data system module.

[0067] The software version location module is integrated into the after-sales service platform, providing a unified query entry point. Its core function is to execute a cross-system data collaboration method.

[0068] like Figure 1 As shown, this embodiment provides a cross-system data collaboration method, including:

[0069] Obtain the hardware identification information to be processed;

[0070] Based on the hardware identification information, obtain the corresponding software and hardware association data from the product data management system, and obtain the corresponding hardware production data from the production management system.

[0071] Based on the acquired software and hardware association data and hardware production data, a query action corresponding to the hardware identification information type is executed to obtain one or more candidate software version information; wherein, the query action includes at least one of matching query based on hardware model, parsing query based on hardware material number, and tracing query based on equipment serial number;

[0072] Output the one or more candidate software version information as the final software version information; if there are multiple candidate software version information, perform cross-validation and output the final software version information.

[0073] The specific steps include:

[0074] Step 1: Obtain the hardware identification information to be processed.

[0075] Hardware identification information includes one or more of the following: hardware model, hardware part number, and device serial number.

[0076] Step 2: Based on the hardware identification information, obtain the corresponding software and hardware association data from the product data management system and the corresponding hardware production data from the production management system.

[0077] When the hardware identification information is a hardware model or hardware material number, the corresponding software and hardware association data is obtained from the product data management system (PDM system).

[0078] When the hardware identification information is the device serial number, the hardware production data containing the hardware production batch and pre-installed software records of the device serial number is obtained from the production management system.

[0079] This embodiment establishes a data interface and synchronization mechanism with the product data management system and the production management system, ensuring the timeliness and consistency of software and hardware related data and production data, breaking down data barriers between systems, and providing a reliable and real-time data foundation for version positioning.

[0080] Step 3: Based on the obtained software and hardware association data and hardware production data, perform a query action corresponding to the hardware identification information type to obtain one or more candidate software version information.

[0081] The query action includes at least one of the following: matching query based on hardware model, parsing query based on hardware part number, and tracing query based on equipment serial number.

[0082] Step 3-a: Perform a matching query based on the hardware model, including:

[0083] Using the hardware model in the hardware identification information as the query condition, a matching search is performed in the software and hardware related data;

[0084] Output information on all candidate software versions that are compatible with the hardware model.

[0085] Matching queries based on hardware model are suitable for scenarios where users only know the hardware model and need to quickly obtain basic compatible software information.

[0086] The specific process is as follows: The user inputs the hardware model, and using the model as the key, the system queries all records in the hardware-software association table whose associated expiration time is in the future or is null. The system then obtains the corresponding software identifier list, queries the software information table, and outputs all candidate software version information that is compatible with the hardware model.

[0087] Step 3-b: Perform parsing and querying based on the hardware part number, including:

[0088] According to the predefined material coding rules, the hardware material number in the hardware identification information is parsed to extract the key identifiers used for association query;

[0089] Based on key identifiers, matching is performed in software and hardware related data to obtain candidate software version information.

[0090] Parsing and querying based on hardware part numbers is suitable for scenarios where users know the hardware part number and need to accurately locate the compatible software.

[0091] The specific process is as follows: The user inputs the material number, and the software version positioning module either has its own built-in material coding rules or loads them from the data verification rule table to parse the number (e.g., parse out the product series code). Using the parsed code, it matches it against the hardware information table to find the corresponding hardware identifier or model, and then proceeds to the model matching process. If parsing fails, the system directly uses the material number as a condition to call the Product Data Management System (PDM system) interface for real-time querying, and returns the query results, which are then synchronously updated to the core data storage unit.

[0092] Step 3-c: Perform a traceability query based on the device serial number, including:

[0093] Using the device serial number in the hardware identification information as an index, the software version record pre-installed at the factory is queried in the hardware production data and used as the first candidate software version information;

[0094] If the records in the hardware production data are incomplete, a supplementary query request will be sent to the product data management system based on the production batch information associated with the device serial number in the hardware identification information to obtain the second candidate software version information.

[0095] The obtained first candidate software version information and / or second candidate software version information are used as candidate software version information.

[0096] Traceability queries based on device serial numbers are suitable for scenarios where it is necessary to trace the original software version of a device.

[0097] The specific process is as follows: The user inputs the device serial number. The module first uses this serial number as an index to look up its production batch (Batch_ID) in the hardware information table. Using the Batch_ID, it queries the hardware production data synchronized from the production management system for a list of pre-installed software versions for that batch of devices, which serve as the first candidate software version information. If the records in the hardware production data are incomplete, it uses the Batch_ID as a condition to query the hardware-software association table, initiates a supplementary query request to the product data management system, and obtains the software association records, which serve as the second candidate software version information. The obtained first and / or second candidate software version information are used as the final candidate software version information.

[0098] This embodiment integrates three query paths: hardware model matching, hardware material number parsing, and equipment serial number tracing. It also combines data from the product data management system and the production management system for cross-validation. This approach can handle information input in different scenarios, significantly improve the coverage and accuracy of version queries, and effectively reduce the risk of equipment failure caused by version mismatch.

[0099] Step 4: Output the one or more candidate software version information as the final software version information; if there are multiple candidate software version information, perform cross-validation and output the final software version information.

[0100] like Figure 2 As shown, if multiple candidate software version information exists, cross-validation is performed, including:

[0101] Compare multiple candidate software version information from different query actions;

[0102] If the version information matches, output the final software version information;

[0103] If the version information is inconsistent, the conflict will be resolved based on the effective time of the association in the software and hardware association data and the production timestamp in the hardware production data, or a report containing inconsistent version information and its source will be generated for the user to choose from.

[0104] In some embodiments, conflict resolution based on the association effectiveness time in the software and hardware association data and the production timestamp in the hardware production data is based on time logic, such as selecting the most recent valid record. The resolution result, all candidate version information, and the basis for the resolution (timestamp, data source) are also displayed to the user for reference and selection.

[0105] Step 5: After outputting the final software version information, data synchronization is also included.

[0106] Specifically, hardware identification information, final software version information, and the query action type and verification conclusion used to obtain the final result are recorded in a structured data synchronization log table. The structured record format includes timestamp, operation type, and data source system fields.

[0107] The final software version information is then bound to its corresponding hardware material information and synchronized to the enterprise resource planning system for use in the procurement process.

[0108] This embodiment outputs candidate software version information, which not only realizes the positive flow and query application of data from R&D, production to after-sales, but also provides accurate reverse data input for R&D optimization and procurement decisions through the connection between after-sales feedback and procurement information, forming a closed loop of data application and optimization throughout the entire life cycle of construction machinery.

[0109] The cross-system data system module enables data interoperability among the Product Data Management System (PDM), Enterprise Resource Planning System (ERP), Production Management System, and After-sales Platform through APIs and standardized communication protocols, and designs a synchronization mode of "real-time triggering + timed batch processing".

[0110] Data synchronization details include:

[0111] Data Management System (PDM System) → After-sales Platform: Software material information, hardware and software compatibility relationships, software version changes, etc., are synchronized in real time using an interface + event-driven model;

[0112] Production Management System → After-Sales Platform: Hardware serial number, production batch, pre-installed software version, etc., adopt a data upload mode from the production management system and timed reading mode from the after-sales platform to ensure synchronization within a reasonable time range;

[0113] After-sales platform → Data management system (PDM system): After-sales software fault statistics, user requirements, version compatibility issues, etc., are collected by packaging data on the after-sales platform and uploading it through a protocol, and are regularly synchronized to support R&D optimization.

[0114] Data synchronization uses a universal data format for transmission, and key fields follow enterprise coding rules; the interface adopts standardized specifications, supports common operations, and sets up identity authentication and data security mechanisms.

[0115] Data synchronization also provides an exception handling mechanism: record data synchronization logs, set verification rules for batch synchronized data, temporarily store data that fails verification and generate a report, and resynchronize after correction.

[0116] This embodiment provides precise and efficient positioning and closed-loop coordination of the software and hardware versions of construction machinery, which can directly serve equipment maintenance, upgrades and troubleshooting, and effectively shorten downtime caused by software problems.

[0117] Example 2:

[0118] This embodiment provides a cross-system data collaboration device, including:

[0119] Acquisition module: used to acquire hardware identification information to be processed; based on the hardware identification information, to acquire corresponding software and hardware association data from the product data management system, and to acquire corresponding hardware production data from the production management system;

[0120] Query module: used to perform a query action corresponding to the hardware identification information type based on the acquired software and hardware association data and hardware production data, to obtain one or more candidate software version information; wherein, the query action includes at least one of matching query based on hardware model, parsing query based on hardware material number, and tracing query based on equipment serial number;

[0121] Output module: Used to output the one or more candidate software version information as the final software version information; if there are multiple candidate software version information, the final software version information is output after cross-validation.

[0122] Example 3:

[0123] This embodiment provides a computer-readable storage medium storing a computer program / instruction thereon, characterized in that, when the computer program / instruction is executed by a processor, it implements the steps of the cross-system data collaboration method described in Embodiment 1.

[0124] Example 4:

[0125] This embodiment provides a computer device, including:

[0126] Memory, used to store computer programs / instructions;

[0127] A processor for executing the computer program / instructions to implement the steps of the cross-system data collaboration method described in Embodiment 1.

[0128] Example 5:

[0129] This embodiment provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the cross-system data collaboration steps described in Embodiment 1.

[0130] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0131] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0132] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0133] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

Claims

1. A cross-system data collaboration method, characterized in that, include: Obtain the hardware identification information to be processed; Based on the hardware identification information, obtain the corresponding software and hardware association data from the product data management system, and obtain the corresponding hardware production data from the production management system. Based on the acquired software and hardware association data and hardware production data, a query action corresponding to the hardware identification information type is executed to obtain one or more candidate software version information; wherein, the query action includes at least one of matching query based on hardware model, parsing query based on hardware material number, and tracing query based on equipment serial number; Output the one or more candidate software version information as the final software version information; if there are multiple candidate software version information, perform cross-validation and output the final software version information.

2. The cross-system data collaboration method according to claim 1, characterized in that, The step of obtaining corresponding software and hardware association data from the product data management system and corresponding hardware production data from the production management system based on the hardware identification information includes: When the hardware identification information is a hardware model or hardware material number, the corresponding software and hardware association data is obtained from the product data management system. When the hardware identification information is a device serial number, hardware production data containing the hardware production batch and pre-installed software records of the device serial number is obtained from the production management system.

3. The cross-system data collaboration method according to claim 1, characterized in that, The matching query based on hardware model includes: Using the hardware model in the hardware identification information as the query condition, a matching search is performed in the software and hardware related data; Output information on all candidate software versions that are compatible with the hardware model.

4. The cross-system data collaboration method according to claim 1, characterized in that, The step of parsing and querying based on the hardware component number includes: According to the predefined material coding rules, the hardware material number in the hardware identification information is parsed to extract the key identifiers used for association query; Based on key identifiers, matching is performed in software and hardware related data to obtain candidate software version information.

5. The cross-system data collaboration method according to claim 1, characterized in that, The traceability query based on the device serial number includes: Using the device serial number in the hardware identification information as an index, the software version record pre-installed at the factory is queried in the hardware production data and used as the first candidate software version information; If the records in the hardware production data are incomplete, a supplementary query request will be sent to the product data management system based on the production batch information associated with the device serial number in the hardware identification information to obtain the second candidate software version information. The obtained first candidate software version information and / or second candidate software version information are used as candidate software version information.

6. The cross-system data collaboration method according to claim 1, characterized in that, If multiple candidate software version information exists, cross-validation is performed, including: Compare multiple candidate software version information from different query actions; If the version information matches, output the final software version information; If the version information is inconsistent, the conflict will be resolved based on the effective time of the association in the software and hardware association data and the production timestamp in the hardware production data, or a report containing inconsistent version information and its source will be generated for the user to choose from.

7. A cross-system data collaboration device, characterized in that, include: Acquisition module: used to acquire hardware identification information to be processed; based on the hardware identification information, to acquire corresponding software and hardware association data from the product data management system, and to acquire corresponding hardware production data from the production management system; Query module: used to perform a query action corresponding to the hardware identification information type based on the acquired software and hardware association data and hardware production data, to obtain one or more candidate software version information; wherein, the query action includes at least one of matching query based on hardware model, parsing query based on hardware material number, and tracing query based on equipment serial number; Output module: Used to output the one or more candidate software version information as the final software version information; if there are multiple candidate software version information, the final software version information is output after cross-validation.

8. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instruction is executed by the processor, it implements the steps of the cross-system data collaboration method as described in any one of claims 1-6.

9. A computer device, characterized in that, include: Memory, used to store computer programs / instructions; A processor for executing the computer program / instructions to implement the steps of the cross-system data collaboration method according to any one of claims 1-6.

10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the steps of cross-system data collaboration as described in any one of claims 1-6.

Images