Data management system, method, device and equipment and storage medium

Abstract

The embodiment of the invention discloses a data management system, method and device, equipment and a storage medium, and belongs to the technical field of computers. The data management system comprises a first bill of material subsystem used for responding to a part information input operation, generating a part identity identifier corresponding to a target part, and storing the part identity identifier to a block chain node; the first bill of material subsystem is further used for generating a first data voucher corresponding to the target part based on part data in the part information input operation, and the first data voucher comprises the part data; the second bill of material subsystem is used for obtaining a first data voucher corresponding to the target part based on the part identity identifier in response to a part information calling operation; and the second bill of material subsystem is also used for analyzing the first data voucher to obtain part data corresponding to the target part.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a data management system, method, apparatus, device and storage medium. Background Art

[0002] The Bill of Material (BOM) records in detail all the lower-level materials and related properties used in each project, that is, the subordinate relationship between the parent part and all the sub-parts, unit usage and other properties.

[0003] In related technologies, by establishing a unified centralized data management platform, the physically distributed BOM system data are formed into a logically single database, providing a unique data source for data access and operation. In order to ensure data updates, it is necessary to regularly push and pull data from each independent system through interfaces or front-end machines.

[0004] However, this method of pushing and pulling data regularly can easily lead to problems such as untimely, inconsistent, inaccurate data updates, and incomplete coverage. Summary of the invention

[0005] The embodiments of the present application provide a data management system, method, apparatus, device and storage medium, which can improve the management efficiency of component data in a bill of materials. The technical solution is as follows:

[0006] In one aspect, an embodiment of the present application provides a data management system, the system comprising:

[0007] A first bill of materials subsystem, configured to generate a component identity identifier corresponding to a target component in response to a component information entry operation, and store the component identity identifier on a blockchain node;

[0008] The first bill of materials subsystem is further used to generate a first data voucher corresponding to the target component based on the component data in the component information entry operation, wherein the first data voucher includes the component data;

[0009] A second bill of materials subsystem is used to obtain a first data voucher corresponding to the target component based on the component identity identifier in response to the component information calling operation;

[0010] The second bill of materials subsystem is further used to parse the first data voucher to obtain component data corresponding to the target component.

[0011] On the other hand, an embodiment of the present application provides a data management method, the method comprising:

[0012] In response to the component information entry operation, a component identity identifier corresponding to the target component is generated by the first bill of materials subsystem, and the component identity identifier is stored on the blockchain node;

[0013] Based on the component data in the component information entry operation, generating a first data voucher corresponding to the target component, wherein the first data voucher includes the component data;

[0014] In response to the component information calling operation, based on the component identity identifier, obtaining a first data voucher corresponding to the target component through a second bill of materials subsystem;

[0015] The first data voucher is parsed to obtain component data corresponding to the target component.

[0016] On the other hand, an embodiment of the present application provides a data management device, the device comprising:

[0017] A first generating module, configured to generate a component identity identifier corresponding to a target component through a first bill of materials subsystem in response to a component information entry operation, and store the component identity identifier on a blockchain node;

[0018] A second generating module, configured to generate a first data voucher corresponding to the target component based on the component data in the component information input operation, wherein the first data voucher includes the component data;

[0019] A first acquisition module, configured to respond to a component information call operation and acquire a first data voucher corresponding to the target component through a second bill of materials subsystem based on the component identity identifier;

[0020] The second acquisition module is used to parse the first data voucher to obtain component data corresponding to the target component.

[0021] On the other hand, an embodiment of the present application provides a computer device, which includes a processor and a memory, wherein the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the data management method as described in the above aspects.

[0022] On the other hand, an embodiment of the present application provides a computer-readable storage medium, in which at least one instruction is stored. The at least one instruction is loaded and executed by a processor to implement the data management method as described in the above aspects.

[0023] On the other hand, an embodiment of the present application provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the data management method provided by the above aspect.

[0024] In an embodiment of the present application, the data management system includes a first bill of materials subsystem and a second bill of materials subsystem. When the component information of the target component is entered, the first bill of materials subsystem can generate a component identity identifier corresponding to the target component, and register and store it on the blockchain node. At the same time, based on the component data in the entry operation, a first data voucher is generated for realizing data sharing between the various bill of materials subsystems. Then, when a component information call operation is received, the second bill of materials subsystem can obtain the first data voucher corresponding to the target component according to the component identity identifier, and parse the first data voucher to obtain the component data. By storing the component data in the blockchain node in the form of the component identity identifier and the data voucher, distributed storage and management of the component data can be realized, thereby realizing data collaboration between the bill of materials subsystems and improving the efficiency of data management. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 A schematic diagram of the structure of a material management system in the related art is shown;

[0026] Figure 2 A schematic diagram showing an implementation environment provided by an exemplary embodiment of the present application is shown;

[0027] Figure 3 A schematic diagram of the structure of a data management system provided by an exemplary embodiment of the present application is shown;

[0028] Figure 4 A flow chart showing a data management method provided by an exemplary embodiment of the present application is shown;

[0029] Figure 5 A schematic diagram of the structure of a data management system provided by another exemplary embodiment of the present application is shown;

[0030] Figure 6 A flowchart of component information input and call provided by an exemplary embodiment of the present application is shown;

[0031] Figure 7 A data sharing sequence diagram between various bill of materials subsystems provided by an exemplary embodiment of the present application is shown;

[0032] Figure 8A structural block diagram of a data management device provided by an exemplary embodiment of the present application is shown;

[0033] Fig. 9 A schematic diagram of the structure of a computer device provided by an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION

[0034] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0035] First, the nouns involved in the embodiments of the present application are introduced:

[0036] Decentralized Identity (DID) is a set of digital identity identification and credential signature verification protocols based on blockchain technology. It includes two core components: Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs), and uses them as a basis for distributed, cross-system and cross-platform identity authentication and trusted data transfer. DID technology provides infrastructure for cross-system and cross-border trusted digital identity management, data access authorization and data exchange between entities. There is no need for centralized integration or data aggregation between multiple systems for the generation, holding and use of identity data. Each system uses blockchain to share, verify and collaborate on distributed trusted data, linking everything in the world in a new way, bridging data islands, and realizing data rights and unbounded trust.

[0037] The bill of material (BOM) is a structural table or structure tree of products or equipment that can be identified by computer equipment, which records in detail all the lower-level materials and related properties used in each project, that is, the subordinate relationship between the parent part and all the sub-parts, the unit usage and other properties. Take automobile manufacturers as an example: in order to improve the efficiency of product production, enhance the comprehensive competitiveness of products, strengthen the mutual connection between various links of the enterprise, and reduce the loss of materials, automobile manufacturers will use the BOM system to manage the bill of materials. In the entire automotive industry, both vehicle manufacturers and parts suppliers have adopted the product data management (Product Data Management, PDM) system, and BOM (bill of materials, also known as product database) is the core of PDM. Different types of BOM systems have different application scopes. The same company, especially large manufacturing companies, have built multiple BOM systems at the same time. BOM is the basis of enterprise production material management.

[0038] Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.

[0039] The underlying blockchain platform can include processing modules such as user management, basic services, and smart contracts. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining the generation of public and private keys (account management), key management, and the maintenance of the corresponding relationship between the user's real identity and the blockchain address (authority management), etc., and under authorization, supervises and audits the transaction of certain real identities and provides risk control rule configuration (risk control audit); the basic service module is deployed on all blockchain node devices to verify the validity of business requests, and records the valid requests to the storage after consensus is reached. For a new business request, the basic service first adapts the interface to parse and authenticate the request (interface adaptation), and then encrypts the business information through the consensus algorithm (consensus management), and transmits it to the shared account book in a complete and consistent manner after encryption (network communication), and records and stores it; the smart contract module is responsible for the registration and issuance of contracts, as well as contract triggering and contract execution. Developers can define the contract logic in a certain programming language and publish it to the blockchain (contract registration). According to the logic of the contract terms, call the key or other events to trigger the execution and complete the contract logic. At the same time, it also provides the function of contract upgrade and cancellation.

[0040] The platform product service layer provides the basic capabilities and implementation framework of typical applications. Developers can superimpose business features based on these basic capabilities to complete the blockchain implementation of business logic. The application service layer provides application services based on blockchain solutions for business participants to use.

[0041] In related technologies, most of the solutions for collaborative data management through multiple BOM systems are based on centralized data aggregation and integration. Data is regularly pushed and pulled from each independent system through interfaces or front-end machines, and concentrated on a newly built large-scale centralized data management platform to achieve data collaboration among multiple BOM systems.

[0042] Indicative, such as Figure 1As shown, by establishing a unified centralized data management platform 101, the user forms a logical single database of the physically distributed system data, providing a unique data source for data access and operation. All information systems of the enterprise use the centralized data management platform 101 as the target of data access. Each bill of materials system needs to read the parts data from the centralized data management platform 101, process the information, and store the new parts data generated by them in the platform according to the requirements of the centralized data management platform 101 for use by other bill of materials systems.

[0043] The centralized platform needs to store at least the product's geometric data, process planning data, process equipment data, service support data, quality data, and bill of materials, which results in high construction costs and long cycles. In order to ensure the consistency, integrity, latest, reliability, and redundancy of BOM data between various BOM systems, each BOM system needs to update component data in a timely manner during data processing to maintain synchronization between BOM systems. However, in actual application, data updates between various BOM systems are often not synchronized, timely, or fully covered.

[0044] In the embodiment of the present application, in order to solve the problem of untimely and unsynchronized data updates between various bill of materials systems, a data management system is built by adopting blockchain technology and distributed identity recognition technology.

[0045] Please refer to Figure 2 , which shows a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application. The implementation environment includes a terminal 220 and a server 240. The terminal 220 and the server 240 perform data communication via a communication network. Optionally, the communication network can be a wired network or a wireless network, and the communication network can be at least one of a local area network, a metropolitan area network, and a wide area network.

[0046] The terminal 220 is an electronic device installed with a data management system (including a bill of materials subsystem) client. The data management system client can be a native application in the terminal, or a third-party application; the electronic device can be a smart phone, a tablet computer, a personal computer, a wearable device, or a vehicle-mounted terminal, etc. Figure 2 In the description, the terminal 220 is taken as a personal computer as an example, but this is not a limitation.

[0047] The server 240 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms. In the embodiment of the present application, the server 240 may be a backend server of a data management system.

[0048] In one possible implementation, Figure 2 As shown, there is data interaction between the server 240 and the terminal 220. When the terminal 220 receives the component information entry operation performed by the user through the first bill of materials subsystem client, the component data in the component information entry operation is transmitted to the server 240, so that the server 240 generates a component identity identifier corresponding to the target component through the first bill of materials subsystem, and registers and stores the component identity identifier on the blockchain node, and generates a first data voucher for the component data shared between the various bill of materials subsystems. Then, when the terminal 220 receives the component information call operation performed by the user through the second bill of materials subsystem client, the server 240 obtains the first data voucher corresponding to the target component from the blockchain node through the second bill of materials subsystem according to the component identity identifier corresponding to the target component, and parses the first data voucher to obtain the component data corresponding to the target component, and then returns the component data to the terminal 220, and the user performs corresponding business processing.

[0049] Please refer to Figure 3 , which shows a schematic diagram of the structure of a data management system provided by an exemplary embodiment of the present application, wherein the data management system includes a first bill of materials subsystem and a second bill of materials subsystem.

[0050] Unlike the related art, the first bill of materials subsystem and the second bill of materials subsystem need to be respectively connected to a unified centralized data management platform, which causes the centralized data management platform to regularly pull data from each system for updating, resulting in problems of untimely and asynchronous data updates. In the embodiment of the present application, the first bill of materials subsystem and the second bill of materials subsystem are no longer integrated between systems, nor are they respectively connected to a unified centralized data management platform. Instead, they are each independently connected to a blockchain node deployed with a distributed identity service, so that each bill of materials subsystem continuously generates component data and generates a component identity identifier according to its own business capabilities, and stores the component data through data credentials.

[0051] Optionally, before using the first BOM subsystem and the second BOM subsystem to manage the parts data, in order to determine the actual controller of the parts data, the data management system may initialize the first BOM subsystem and the second BOM subsystem, that is, control the first BOM subsystem and the second BOM subsystem to connect to the blockchain distributed identity service, and generate and register system identity identifiers corresponding to each BOM subsystem on the blockchain, so that in the subsequent data management process, each BOM subsystem can sign the parts data generated by itself, and other BOM subsystems can perform on-chain verification.

[0052] Among them, the first bill of materials subsystem is used to generate a component identity identifier corresponding to the target component in response to the component information entry operation, and in order to enable other bill of materials subsystems to obtain the component identity identifier, the first bill of materials subsystem is also used to register the component identity identifier and store the component identity identifier on the blockchain node.

[0053] Optionally, the BOM subsystem may be a design BOM subsystem, an engineering BOM subsystem, a manufacturing BOM subsystem, a process BOM subsystem, or a customer BOM subsystem, which is not limited in the present application. Optionally, the first BOM subsystem is generally a design BOM subsystem, and the component information entry operation can be regarded as the beginning of the life cycle of the target component in the entire data management system process.

[0054] Optionally, when receiving the component information input into the system, the first bill of materials subsystem may generate a component identity identifier corresponding to the target component by calling a distributed identity service interface.

[0055] Optionally, the component identifier can be a string in the form of a Uniform Resource Locator (URL), consisting of a DID (Decentralized Identity) prefix, a DID method name, and an identification string specific to the DID method. For example, the component identifier can be expressed as did:tdid:0x00123456789abcdefg.

[0056] Optionally, the first bill of materials subsystem is further used to generate a first data voucher corresponding to the target component based on the component data in the component information entry operation, and the first data voucher includes the component data.

[0057] Optionally, the data credential is a verifiable credential (VCs) in a distributed identity, and the first data credential generated by the first bill of materials subsystem can be represented as a VCs-1 data credential.

[0058] Optionally, the first data voucher may include component data corresponding to the target component, such as the model, material, feature code, etc. of the target component, which is not limited in this embodiment of the present application.

[0059] Optionally, each BOM subsystem can obtain component data corresponding to the target component by sharing data credentials, so as to perform corresponding business processing.

[0060] Optionally, the second bill of materials subsystem is used to obtain the first data certificate corresponding to the target component from the blockchain node according to the component identity identifier corresponding to the target component when a component information call operation is received, so that the component data corresponding to the target component can be obtained by parsing the first data certificate, and then the business related to the target component can be processed.

[0061] To summarize, in an embodiment of the present application, the data management system includes a first bill of materials subsystem and a second bill of materials subsystem. When entering component information of a target component, the first bill of materials subsystem can generate a component identity identifier corresponding to the target component, and register and store it on a blockchain node. At the same time, based on the component data in the entry operation, a first data voucher is generated for data sharing between various bill of materials subsystems. Further, when a component information call operation is received, the second bill of materials subsystem can obtain the first data voucher corresponding to the target component based on the component identity identifier, and parse the first data voucher to obtain the component data. By storing the component data in the blockchain node in the form of a component identity identifier and a data voucher, distributed storage and management of the component data can be achieved, thereby achieving data collaboration between bill of materials subsystems and improving data management efficiency.

[0062] In a possible implementation, in the process of managing component data for a target component, in order to improve data management efficiency, a first component identity document corresponding to the target component may be generated through the first bill of materials subsystem, and the component identity identifier and the first data voucher of the target component may be managed through the first component identity document.

[0063] Optionally, the first bill of materials subsystem is also used to call the distributed identity service interface in response to the component information entry operation, and generate a component identity identifier corresponding to the target component. In order to uniformly manage the component information corresponding to the target component, while generating the component identity identifier corresponding to the target component, the first bill of materials subsystem can also be used to generate a first component identity document, thereby storing both the component identity identifier corresponding to the target component and the first component identity document on the blockchain node.

[0064] In a possible implementation, in the process of entering component information of a target component through the first BOM subsystem, it is taken into consideration that not all component information may be shared between various BOM subsystems, that is, some component data may be special data of the target component in the first BOM subsystem. Therefore, before generating the first data voucher, the first BOM subsystem may also be used to determine component sub-data based on the component data in the component information entry operation. The component sub-data is data shared between various BOM subsystems, that is, part data generated by each BOM subsystem based on its own business capabilities and shared with other BOM subsystems. Then, based on the component sub-data, a first data voucher is generated, which only includes the component sub-data.

[0065] In a possible implementation, in order to facilitate each bill of materials subsystem to search and call the component data of the target component, after generating the first data voucher, the first bill of materials subsystem can also be used to update the first storage address corresponding to the first data voucher to the first component identity document.

[0066] Optionally, the first component identity document may include a data voucher list, which is used to store the storage addresses of data vouchers generated by different bill of materials subsystems for the target component. Optionally, the data voucher list may also be stored in the first component identity document in the form of an access address corresponding to the list, and the data voucher list may be obtained by querying the access address.

[0067] Optionally, the first data voucher may be stored through a data voucher storage service, and the data vouchers generated by each bill of materials subsystem may be centrally stored through the data voucher storage service or may be independently stored, which is not limited in this embodiment of the present application.

[0068] Optionally, in order to improve the security of data sharing, access permissions can also be set for data credentials through the data credential storage service, that is, the data credential can only be obtained through the data credential storage service if the bill of materials subsystem has access permissions.

[0069] Optionally, the first component identity document records attribute data of the target component, including a component identity identifier, a first storage address corresponding to the first data voucher, and the like.

[0070] Schematically, the code data corresponding to the first component identity document may be as follows:

[0071] {"@context":"https: / / www.w3.org / ns / did / v1",

[0072] "id":"did:example:123456789abcdefghi", / / DID identifier of the component

[0073] "verificationMethod":[

[0074] {"id":"did:example:123456789abcdefghi#keys-1",

[0075] "type":"Ed25519VerificationKey2018",

[0076] "controller":"did:example:123456789abcdefghi",

[0077] "publicKeyBase58":"Gj7Fg2yvUWY7XfZjvRyYzjJZJ5J6zvJ5J6zvJ5J6zvJ5"}

[0078] {"id":"did:example:123456789abcdefghi#keys-2",

[0079] "type":"RsaVerificationKey2018",

[0080] "controller":"did:example:123456789abcdefghi",

[0081] "publicKeyPem":"----BEGIN PUBLIC KEY-----\nMIIBI jANBgkqhkiG9w0BAQEFAA0CAQ8AMIIBCgKCAQEAwJ\n---END PUBLICKEY--"}],

[0082] "authentication":["did:example:123456789abcdefghi#keys-1"],

[0083] "service":[

[0084] {"id":"did:examp le:123456789abcdefghi#vcs",

[0085] "type":"VerifiableCredentialService",

[0086] "serviceEndpoint":"https: / / example.com / vc-list / " / / The storage address of the data credential of this component}]}

[0087] Illustratively, the code data corresponding to the first data voucher may be as follows:

[0088] {

[0089] "@context":[

[0090] "https: / / www.w3.org / 2018 / credentials / v1",

[0091] "https: / / www.w3.org / 2018 / credent ials / examples / v1"

[0092] ],

[0093] "id":"http: / / example.car / credentials / 1872", / / data credential storage URL

[0094] "type":["VerifiableCredential","PartsVC"], / / The type of data credential is parts credential partsVC

[0095] "issuer":"https: / / example.edu / issuers / 565049",

[0096] "issuanceDate":"2023-01--01T19:73:24Z",

[0097] "credentialSubject":{

[0098] "id":"did:tdid:ebfeb1f712ebc6f1c276e12ec21", / / DID identifier of a component

[0099] "parts0f":{

[0100] "id":"did:tdid:c276e12ec21ebfeb1f712ebc6f1", / / The part belongs to a certain model year DID

[0101] "name":[{

[0102] "material":"wheel", / / Material of the component

[0103] "num":"CAR201503030113", / / A feature code of a component

[0104] }]

[0105] }

[0106] },

[0107] "proof":{

[0108] "type":"RsaSignature2018",

[0109] "created":"2023-06-18T21:19:10Z",

[0110] "proofPurpose":"assertionMethod",

[0111] "verificationMethod":"https: / / example.car / issuers / keys / 1",

[0112] "jws":"eyJhbGci0iJSUzI1NiIsImI2NCI6ZmFsc2UsImNyaXQiOLsiYjY0Il19..TCYt5X"

[0113] }

[0114] }

[0115] In a possible implementation, in order to facilitate other bill of materials subsystems to perform on-chain verification of the first data certificate of the target component on the blockchain node and improve the accuracy of component data call, the first bill of materials subsystem can also be used to use its corresponding first system identity identifier to sign the first data certificate corresponding to the target component.

[0116] Optionally, the first bill of materials subsystem may use a private key corresponding to the first system identity identifier to sign a first data certificate corresponding to the target component.

[0117] In one possible implementation, when a component information call operation is received, the second bill of materials subsystem can be used to retrieve the component identity identifier corresponding to the target component from the blockchain node, and then based on the component identity identifier, the first component identity document is parsed through the distributed identity service interface to obtain the first storage address corresponding to the first data voucher, and then the second bill of materials subsystem can obtain the first data voucher corresponding to the target component according to the first storage address.

[0118] In one possible implementation, considering that in the process of entering component information for a target component, the first bill of materials subsystem may not directly store the component identity identifier on the blockchain node, but rather indirectly stores the component identity identifier on the blockchain node through its own corresponding first system identity document, therefore in the process of calling the component information, the second bill of materials subsystem may also first search for the first system identity document corresponding to the first bill of materials subsystem on the blockchain node, and parse the first system identity document to obtain the component identity identifier corresponding to the target component.

[0119] Please refer to Figure 4 , which shows a flow chart of a data management method provided by an exemplary embodiment of the present application. This embodiment is described by taking the method used in a computer device as an example. The method includes the following steps:

[0120] Step 401, in response to the component information entry operation, a component identity identifier corresponding to the target component is generated by the first bill of materials subsystem, and the component identity identifier is stored on the blockchain node.

[0121] Optionally, the bill of materials subsystem can be a design bill of materials (Design BOM, DBOM) subsystem, an engineering bill of materials (Engineering BOM, EBOM) subsystem, a manufacturing bill of materials (Manufacturing BOM, MBOM) subsystem, a process bill of materials (Process BOM, PBOM) subsystem, a customer bill of materials (Customer BOM, CBOM) subsystem, or other bill of materials subsystems, which is not limited to the embodiments of the present application.

[0122] Optionally, considering that the component information entry operation can be regarded as the beginning of the life cycle of the target component in the entire data management system process, the first bill of materials subsystem is generally a design bill of materials subsystem.

[0123] In one possible implementation, upon receiving a component information entry operation, the computer device can generate a component identity identifier corresponding to the target component through the first bill of materials subsystem, and store the component identity identifier on the blockchain node so that the user can call the component information corresponding to the target component through other bill of materials subsystems.

[0124] Optionally, the component identifier can be represented as a URL string consisting of the DID prefix, the DID method name, and an identification string specific to the DID method.

[0125] In a possible implementation, in order to facilitate the management of component information, during the process of entering component information, the computer device may also create a corresponding first component identity document for the target component and store the first component identity document on the blockchain node.

[0126] Step 402: Generate a first data voucher corresponding to the target component based on the component data in the component information entry operation, wherein the first data voucher includes the component data.

[0127] In one possible implementation, in order to achieve component data sharing among various BOM subsystems, the computer device also needs to generate a first data voucher corresponding to the target component based on the component data in the component information entry operation. The component data contained in the first data voucher is the data that can be shared among various BOM subsystems.

[0128] In a possible implementation, in order to facilitate other BOM subsystems to verify the acquired parts data and determine its legality and integrity, etc. during the process of calling parts information, the computer device can also use the first system identity identifier corresponding to the first BOM subsystem to sign the first data certificate during the process of entering parts information for the target parts through the first BOM subsystem.

[0129] In one possible implementation, in order to improve the efficiency of searching for data vouchers, after the computer device generates the first data voucher through the first bill of materials subsystem, it can store it in a storage space that can be authorized to access by other bill of materials subsystems, and store the first storage address corresponding to the first data voucher in the first component identity document.

[0130] Step 403, in response to the component information calling operation, based on the component identity identifier, obtain the first data voucher corresponding to the target component through the second bill of materials subsystem.

[0131] In a possible implementation, upon receiving a component information call operation through the second bill of materials subsystem, the computer device may obtain a first data certificate corresponding to the target component from the blockchain node through the second bill of materials subsystem based on the component identity identifier.

[0132] In one possible implementation, the computer device first searches for the first system identity document corresponding to the first bill of materials subsystem in the blockchain node, and parses the first system identity document to obtain a component identity identifier corresponding to the target component, and then parses the first component identity document based on the component identity identifier to obtain a first storage address corresponding to a first data voucher stored in the first component identity document, and then obtains the first data voucher corresponding to the target component based on the first storage address.

[0133] Step 404, parse the first data voucher to obtain component data corresponding to the target component.

[0134] Furthermore, the computer device parses the first data voucher through the second bill of materials subsystem, thereby obtaining component data corresponding to the target component included in the first data voucher.

[0135] In a possible implementation, in order to determine the legitimacy and integrity of the component data in the first data certificate, the computer device may also verify the signature on the first data certificate through a distributed identity service in a blockchain node.

[0136] To summarize, in an embodiment of the present application, the data management system includes a first bill of materials subsystem and a second bill of materials subsystem. When entering component information of a target component, the first bill of materials subsystem can generate a component identity identifier corresponding to the target component, and register and store it on a blockchain node. At the same time, based on the component data in the entry operation, a first data voucher is generated for data sharing between various bill of materials subsystems. Further, when a component information call operation is received, the second bill of materials subsystem can obtain the first data voucher corresponding to the target component based on the component identity identifier, and parse the first data voucher to obtain the component data. By storing the component data in the blockchain node in the form of a component identity identifier and a data voucher, distributed storage and management of the component data can be achieved, thereby achieving data collaboration between bill of materials subsystems and improving data management efficiency.

[0137] In a possible implementation, after obtaining the component data corresponding to the target component through the second bill of materials subsystem, the computer device can perform corresponding business processing on the target component through the second bill of materials subsystem according to the component data, and generate a second data voucher corresponding to the target component based on the new component data generated during the business processing. In order to facilitate other bill of materials subsystems to call the component data, the computer device also needs to update the second storage address corresponding to the second data voucher to the first component identity document.

[0138] Optionally, the second data voucher generated by the second bill of materials subsystem may be represented as a VCs-2 data voucher.

[0139] In one possible implementation, upon receiving a component information call operation through the third bill of materials subsystem, the computer device uses the third bill of materials subsystem to search the blockchain node for the component identity identifier and the first component identity document corresponding to the target component, thereby parsing the first component identity document based on the component identity identifier, obtaining a first storage address corresponding to the first data voucher and a second storage address corresponding to the second data voucher stored in the first component identity document, and then obtaining the first data voucher and the second data voucher corresponding to the target component based on the first storage address and the second storage address, thereby parsing the first data voucher and the second data voucher to obtain the component data corresponding to the target component, and performing corresponding business processing based on the component data.

[0140] Please refer to Figure 5 , which shows a structural diagram of a data management system provided by another exemplary embodiment of the present application.

[0141] Schematically, the data management system includes multiple BOM systems, namely, DBOM system, EBOM system, MBOM system, PBOM system and CBOM system. Each BOM system corresponds to a blockchain DID service node, or has access rights to the blockchain DID service node.

[0142] Among them, each BOM system can generate and register a component identity identifier and a component identity document according to the component information entry operation, and obtain the component data based on the entry operation and business processing, and generate the corresponding data certificate, and then store the data certificate through the data certificate VCs storage service, and at the same time update the storage address of the data certificate to the component identity document in the blockchain node. Therefore, when the user calls the component information through one of the BOM systems, the computer device can obtain and parse the component identity identifier and the component identity document according to the BOM system, obtain the storage address of the data certificate corresponding to the component, and then obtain the data certificate in the storage address, parse the data certificate, obtain the component data, and perform corresponding business processing.

[0143] Please refer to Figure 6 , which shows a flowchart of component information entry and calling provided by an exemplary embodiment of the present application.

[0144] 1. Receive target parts input operation.

[0145] 2. Generate a component identity identifier and a first component identity document.

[0146] The computer device generates and registers a component identification identifier and a first component identification document through the BOM-1 system based on the component information entry operation.

[0147] 3. Generate the first data voucher VCs-1.

[0148] The computer device generates a first data voucher VCs-1 based on the component data in the component information entry operation, and updates the storage address of the first data voucher to the first component identity document.

[0149] 4. Obtain component identification identifiers.

[0150] When receiving a component information call operation through the BOM-2 system, the computer device obtains the component identity identifier through the BOM-2 system, and parses the first component identity document to obtain a first storage address corresponding to the first data voucher.

[0151] 5. Obtain the first data voucher VCs-1 and process it.

[0152] The computer device obtains the first data voucher VCs-1 through the BOM-2 system based on the first storage address and performs corresponding data processing.

[0153] 6. Generate a second data voucher VCs-2.

[0154] The computer device generates a second data voucher VCs-2 through the BOM-2 system based on the component data obtained through business processing, and updates the second storage address corresponding to the second data voucher to the first component identity document.

[0155] 7. Obtain VCs-1 & VCs-2 according to the component identity identifier, obtain component data, and perform business processing.

[0156] When receiving a component information call operation through the BOM-3 system, the computer device obtains the component identity identifier through the BOM-3 system, and parses the first component identity document to obtain the first storage address corresponding to the first data voucher and the second storage address corresponding to the second data voucher, and further obtains the first data voucher and the second data voucher, and then performs corresponding business processing.

[0157] Please refer to Figure 7 , which shows a data sharing timing diagram between various bill of materials subsystems provided by an exemplary embodiment of the present application.

[0158] 1. Generate and register the BOM-1 system identifier.

[0159] The computer equipment initializes the BOM-1 system, generates and registers the BOM-1 system identity identifier and system identity document.

[0160] 2. Generate and register the BOM-2 system identifier.

[0161] The computer equipment initializes the BOM-2 system, generates and registers the BOM-2 system identity identifier and system identity document.

[0162] 3. Generate and register the BOM-3 system identifier.

[0163] The computer equipment initializes the BOM-3 system, generates and registers the BOM-3 system identity identifier and system identity document.

[0164] 4. Receive parts information entry operation.

[0165] 5. Generate a component identity identifier and a first component identity document, and store them in the blockchain node.

[0166] Based on the component information entry operation, the computer device generates and registers the component identity identifier and the first component identity document through the BOM-1 system, and stores them in the blockchain node.

[0167] 6. Generate the first data certificate.

[0168] The computer device generates and stores the first data voucher VCs-1 based on the component data in the component information entry operation.

[0169] 7. Update the first storage address of the first data voucher to the first component identity document.

[0170] In order to facilitate other BOM systems to obtain the first data certificate, the computer device updates the first storage address of the first data certificate to the first component identity document.

[0171] 8. Receive component information call operation.

[0172] 9. Based on the component identity identifier, obtain a first component identity document.

[0173] When receiving a component information call operation through the BOM-2 system, the computer device obtains the component identification identifier and the first component identification document through the BOM-2 system.

[0174] 10. Parse the first component identity document and obtain the first storage address.

[0175] The computer device parses the first component identity document to obtain a first storage address of the first data voucher.

[0176] 11. Based on the first storage address, obtain a first data voucher.

[0177] The computer device obtains the first data voucher through the data voucher storage service based on the first storage address.

[0178] 12. Return the first data voucher.

[0179] 13. Perform business processing based on parts data.

[0180] Computer equipment processes business through the BOM-2 system and generates new parts data.

[0181] 14. Generate and store a second data credential.

[0182] The computer device generates and stores a second data voucher based on the new component data.

[0183] 15. Receive component information call operation.

[0184] 16. Based on the component identity identifier, obtain a first component identity document.

[0185] When receiving a component information call operation through the BOM-3 system, the computer device obtains the component identification identifier and the first component identification document through the BOM-3 system.

[0186] 17. Parse the first component identity document to obtain the first storage address and the second storage address.

[0187] The computer device parses the first component identity document to obtain a first storage address of the first data voucher and a second storage address corresponding to the second data voucher.

[0188] 18. Based on the first storage address and the second storage address, obtain a first data certificate and a second data certificate.

[0189] The computer device obtains the first data certificate and the second data certificate through the data certificate storage service based on the first storage address and the second storage address.

[0190] 19. Return the first data certificate and the second data certificate.

[0191] In combination with the above embodiments, it can be seen that in the embodiments of the present application, by applying blockchain technology and distributed identity DID technology between various BOM systems, the sharing of component data between various BOM systems is achieved.

[0192] First, in the process of entering parts information, by generating part identity identifiers for the parts and running through all independent BOM systems through blockchain nodes at the bottom layer, the part information is made consistent and transparent, avoiding problems such as untimely data updates, inconsistent data information, duplicate codes, and wrong codes, which is conducive to improving the accuracy of parts and spare parts procurement and use.

[0193] Secondly, by building distributed blockchain service nodes at the bottom layer, each BOM system can perform its duties and independently generate corresponding data according to its own business functions, and assign it to the component; the data demander can identify and parse the component identity identifier to obtain consistent material data information. The addition of a new BOM system only requires docking with the blockchain DID service, without the need for large-scale integration between multiple systems, forming a more open, lightweight, and low-cost new model for industrial system connection and collaboration.

[0194] In addition, using the component identity identifier as the query entry, all BOM systems perform DID query and resolution from the trusted blockchain DID service. The entry is unified and easy to manage. In addition, due to the blockchain's tamper-proof and traceable characteristics, as well as the distributed issuance verification and data ownership characteristics guaranteed by distributed identity technology, the query results are more reliable and independent.

[0195] Please refer to Figure 8 , which shows a structural block diagram of a data management device provided by an exemplary embodiment of the present application, the device comprising:

[0196] The first generation module 801 is used to generate a component identity identifier corresponding to a target component through the first bill of materials subsystem in response to a component information entry operation, and store the component identity identifier on a blockchain node;

[0197] A second generating module 802 is used to generate a first data voucher corresponding to the target component based on the component data in the component information input operation, wherein the first data voucher includes the component data;

[0198] A first acquisition module 803 is used to respond to the component information calling operation and acquire a first data voucher corresponding to the target component through the second bill of materials subsystem based on the component identity identifier;

[0199] The second acquisition module 804 is used to parse the first data voucher to obtain the component data corresponding to the target component.

[0200] Optionally, after parsing the first data voucher to obtain component data corresponding to the target component, the device further includes:

[0201] A third generating module, configured to perform business processing on the target component through the second bill of materials subsystem based on the component data, and generate a second data voucher corresponding to the target component;

[0202] An updating module is used to update the second storage address corresponding to the second data certificate into the first component identity document.

[0203] Optionally, the device further comprises:

[0204] A search module, configured to search for a component identity identifier corresponding to the target component from the blockchain node through a third bill of materials subsystem in response to the component information call operation;

[0205] A third acquisition module, configured to parse the first component identity document based on the component identity identifier, and acquire a first storage address corresponding to the first data voucher and a second storage address corresponding to the second data voucher;

[0206] The fourth acquisition module is used to acquire the first data certificate and the second data certificate corresponding to the target component based on the first storage address and the second storage address.

[0207] To summarize, in an embodiment of the present application, the data management system includes a first bill of materials subsystem and a second bill of materials subsystem. When entering component information of a target component, the first bill of materials subsystem can generate a component identity identifier corresponding to the target component, and register and store it on a blockchain node. At the same time, based on the component data in the entry operation, a first data voucher is generated for data sharing between various bill of materials subsystems. Further, when a component information call operation is received, the second bill of materials subsystem can obtain the first data voucher corresponding to the target component based on the component identity identifier, and parse the first data voucher to obtain the component data. By storing the component data in the blockchain node in the form of a component identity identifier and a data voucher, distributed storage and management of the component data can be achieved, thereby achieving data collaboration between bill of materials subsystems and improving data management efficiency.

[0208] It should be noted that: the device provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device and method embodiments provided in the above embodiment belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.

[0209] Please refer to Fig. 9 , which shows a schematic diagram of the structure of a computer device provided by an exemplary embodiment of the present application. Specifically, the computer device 900 includes a central processing unit (CPU) 901, a system memory 904 including a random access memory 902 and a read-only memory 903, and a system bus 905 connecting the system memory 904 and the central processing unit 901. The computer device 900 also includes a basic input / output system (I / O system) 906 that helps transmit information between various devices in the computer, and a large-capacity storage device 907 for storing an operating system 913, application programs 914 and other program modules 915.

[0210] The basic input / output system 906 includes a display 908 for displaying information and an input device 909 such as a mouse and a keyboard for user inputting information. The display 908 and the input device 909 are connected to the central processing unit 901 through an input / output controller 910 connected to the system bus 905. The basic input / output system 906 may also include an input / output controller 910 for receiving and processing inputs from a plurality of other devices such as a keyboard, a mouse, or an electronic stylus. Similarly, the input / output controller 910 also provides output to a display screen, a printer, or other types of output devices.

[0211] The mass storage device 907 is connected to the central processing unit 901 through a mass storage controller (not shown) connected to the system bus 905. The mass storage device 907 and its associated computer readable media provide non-volatile storage for the computer device 900. That is, the mass storage device 907 may include a computer readable medium (not shown) such as a hard disk or drive.

[0212] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data. Computer storage media include random access memory (RAM), read-only memory (ROM), flash memory or other solid-state storage technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, cassette, magnetic tape, disk storage or other magnetic storage devices. Of course, those skilled in the art will know that the computer storage medium is not limited to the above. The above-mentioned system memory 904 and mass storage device 907 can be collectively referred to as memory.

[0213] The memory stores one or more programs, and the one or more programs are configured to be executed by one or more central processing units 901. The one or more programs contain instructions for implementing the above-mentioned methods. The central processing unit 901 executes the one or more programs to implement the methods provided by the above-mentioned various method embodiments.

[0214] According to various embodiments of the present application, the computer device 900 can also be connected to a remote computer on the network through a network such as the Internet. That is, the computer device 900 can be connected to the network 911 through the network interface unit 912 connected to the system bus 905, or the network interface unit 912 can be used to connect to other types of networks or remote computer systems (not shown).

[0215] An embodiment of the present application also provides a computer-readable storage medium, in which at least one instruction is stored. The at least one instruction is loaded and executed by a processor to implement the data management method described in the above embodiment.

[0216] Optionally, the computer readable storage medium may include: ROM, RAM, solid state drives (SSD) or optical disks, etc. Among them, RAM may include resistance random access memory (ReRAM) and dynamic random access memory (DRAM).

[0217] The embodiment of the present application provides a computer program product, which includes computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the data management method described in the above embodiment.

[0218] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0219] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A data management system, characterized in that: The system comprises: A first bill of materials subsystem, configured to generate a component identity identifier corresponding to a target component in response to a component information entry operation, and store the component identity identifier on a blockchain node; The first bill of materials subsystem is further used to generate a first data voucher corresponding to the target component based on the component data in the component information entry operation, wherein the first data voucher includes the component data; A second bill of materials subsystem is used to obtain a first data voucher corresponding to the target component based on the component identity identifier in response to the component information calling operation; The second bill of materials subsystem is further used to parse the first data voucher to obtain component data corresponding to the target component.

2. The system according to claim 1, characterized in that The first bill of materials subsystem is used to: In response to the component information entry operation, calling a distributed identity service interface to generate a component identity identifier and a first component identity document corresponding to the target component; The component identity identifier and the first component identity document are stored on the blockchain node.

3. The system according to claim 2, characterized in that The first bill of materials subsystem is further used for: Determine component sub-data based on the component data in the component information entry operation, wherein the component sub-data is data shared between various bill of materials subsystems; Based on the component sub-data, generating the first data voucher, wherein the first data voucher includes the component sub-data; The first storage address corresponding to the first data voucher is updated into the first component identity document.

4. The system according to claim 3, characterized in that The first bill of materials subsystem is further used for: The first data voucher is signed using a first system identity identifier corresponding to the first bill of materials subsystem.

5. The system according to claim 1, characterized in that The second bill of materials subsystem is used to: In response to the component information calling operation, searching the blockchain node for a component identity identifier corresponding to the target component; Based on the component identity identifier, the first component identity document is parsed through a distributed identity service interface to obtain a first storage address corresponding to the first data voucher; Based on the first storage address, a first data voucher corresponding to the target component is obtained.

6. The system according to claim 5, characterized in that The second bill of materials subsystem is also used for: In response to the component information calling operation, searching the blockchain node for a first system identity document corresponding to the first bill of materials subsystem; The first system identity document is parsed to obtain a component identity identifier corresponding to the target component.

7. A data management method, characterized in that: The method comprises: In response to the component information entry operation, a component identity identifier corresponding to the target component is generated by the first bill of materials subsystem, and the component identity identifier is stored on the blockchain node; Based on the component data in the component information entry operation, generating a first data voucher corresponding to the target component, wherein the first data voucher includes the component data; In response to the component information calling operation, based on the component identity identifier, obtaining a first data voucher corresponding to the target component through a second bill of materials subsystem; The first data voucher is parsed to obtain component data corresponding to the target component.

8. The method according to claim 7, characterized in that After parsing the first data voucher to obtain component data corresponding to the target component, the method further includes: Based on the component data, the second bill of materials subsystem performs business processing on the target component to generate a second data voucher corresponding to the target component; The second storage address corresponding to the second data voucher is updated into the first component identity document.

9. The method according to claim 8, characterized in that The method further comprises: In response to the component information calling operation, searching the blockchain node for a component identity identifier corresponding to the target component through a third bill of materials subsystem; Based on the component identity identifier, the first component identity document is parsed to obtain a first storage address corresponding to the first data voucher and a second storage address corresponding to the second data voucher; Based on the first storage address and the second storage address, a first data certificate and a second data certificate corresponding to the target component are obtained.

10. A data management device, characterized in that: The device comprises: A first generating module, configured to generate a component identity identifier corresponding to a target component through a first bill of materials subsystem in response to a component information entry operation, and store the component identity identifier on a blockchain node; A second generating module, configured to generate a first data voucher corresponding to the target component based on the component data in the component information input operation, wherein the first data voucher includes the component data; A first acquisition module, configured to respond to a component information call operation and acquire a first data voucher corresponding to the target component through a second bill of materials subsystem based on the component identity identifier; The second acquisition module is used to parse the first data voucher to obtain component data corresponding to the target component.

11. A computer device, characterized in that: The computer device includes a processor and a memory; the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the data management method according to any one of claims 7 to 9.

12. A computer-readable storage medium, characterized in that: The storage medium stores at least one instruction, and the at least one instruction is used to be executed by a processor to implement the data management method according to any one of claims 7 to 9.

13. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device implements the data management method as described in any one of claims 7 to 9.

Images