Complete intelligent entity traceability system for oil and gas pipeline network projects

Abstract

The present invention belongs to the field of oil and gas pipeline networks, and specifically relates to a complete intelligent entity traceability system for oil and gas pipeline network projects, which aims to solve the problems of lack of management of entity data, difficulty in tracing, and difficulty in verifying the whereabouts of existing oil and gas pipeline network projects. The present invention includes a service middle platform, an entity database, an application module, and a blockchain module; the application module is configured to obtain the entity material attributes and entity business activity processes of the entity to be managed, and is also configured to obtain the entered traceability code and related activity link data; the entity database is configured to store the entity public attribute library and the value domain rule library of the entity public attribute; the service middle platform is configured to perform data packet verification, traceability code generation, process contract generation and query, and data transposition; the blockchain module is configured to store evidence data packets and traceability codes. The present invention realizes the effective management of entity data in the construction of oil and gas pipeline network projects, and improves the accuracy of tracing and whereabouts verification.

Description

Technical Field

[0001] The present invention belongs to the field of oil and gas pipeline networks, and in particular relates to a complete intelligent entity tracing system for oil and gas pipeline network projects. Background Art

[0002] With the rapid development of oil and gas pipeline network facilities, operational safety and protection of pipeline construction face numerous challenges. Effective management of engineering entity data is a solid foundation for safe pipeline network construction and production. Various facilities within oil and gas pipeline network projects can be referred to as entities. Entities are countable and categorized, such as pipelines, stations, valve rooms, steel pipes, compressors, ball valves, and control systems. Generally speaking, entity data primarily includes the materials and equipment that make up the entity, as well as the operational flow of its construction.

[0003] The current material management system focuses on business activities and financial settlements, while data related to entities mainly rely on specialized manpower to archive procurement data, construction data, and design data during construction and after completion. Therefore, there are still many defects: 1. The brand and quality data of equipment parts and materials are lost during construction activities, large packages are split into small packages, and different materials are combined into one entity, making it difficult to find the initial data and impossible to trace; 2. There are inconsistencies between physical objects and materials, business processes and record progress, and there are omissions and supplements. The workload of supplementary entries is large, the errors are large, resulting in poor credibility and a lack of intelligent monitoring; 3. After-sales service is seriously formalized, there is a lack of coordination between upstream and downstream, the process cannot be traced, and there is a lack of intelligent constraints. Summary of the Invention

[0004] In order to solve the above-mentioned problems in the prior art, namely, the problems of lack of management, difficulty in tracing, and difficulty in verifying the whereabouts of entity data in the existing oil and gas pipeline network construction, the present invention provides a complete intelligent entity tracing system based on oil and gas pipeline network engineering, which includes:

[0005] Service middle platform, entity database, application module and blockchain module;

[0006] The application module includes an initial data entry unit and a traceability code entry unit;

[0007] The initial data entry unit is configured to obtain the physical material attributes and physical business activity process of the entity to be managed, take the physical material attributes of the entity to be managed as the first data packet, and send it to the data middle station of the service middle station, and send the physical business activity process to the smart contract middle station of the service middle station; the physical business activity process includes several activity links;

[0008] The traceability code entry unit is configured to obtain the entered traceability code and send it to the data center of the service center; it is also configured to receive and display the process contract corresponding to the activity link where the entered traceability code is located, and obtain the relevant activity link data of the activity link where the entity to be managed is located filled in based on the process contract, as a second data packet, and send it to the data center of the service center;

[0009] The entity database is configured to store a third data packet; the third data packet includes an entity common attribute library and a value range rule library for entity common attributes; the entity common attribute library is a database storing characteristics of common materials and equipment in oil and gas pipeline projects, standard links in business flows, and characteristic functions; the value range rule library for entity common attributes is a database storing mapping relationships between entity common attributes and preset value ranges;

[0010] The service middle platform includes a data middle platform, a traceability code management unit, and a smart contract middle platform;

[0011] The smart contract middle platform is configured to receive the entity business activity process and generate a process contract; the process contract includes the entity business activity process and the information filling identification fields corresponding to each activity link; the information filling identification fields are used to limit the type of information to be filled in each activity link;

[0012] The data middle platform includes a data packet verification unit, a transposition processing unit, and a process contract query unit;

[0013] The data packet verification unit is configured to receive the first data packet and verify it, and after verification, send it to the traceability code generation subunit and the transposition processing unit of the traceability code management unit; and is also configured to receive the second data packet and verify it, and send it to the transposition processing unit;

[0014] The transposition processing unit includes a data transposition unit, which is configured to perform data transposition on the first data packet or the second data packet after successful verification, and send the first data packet after data transposition and its corresponding traceability code or the second data packet after data transposition to the blockchain module;

[0015] The process contract query unit is configured to query the corresponding process contract based on the entered traceability code and the activity link located by the traceability code and send it to the traceability code entry unit;

[0016] The traceability code management unit includes a traceability code generation subunit; the traceability code generation subunit is configured to generate a traceability code based on the first data packet that has been successfully verified and send it to the data transposition unit;

[0017] In some preferred embodiments, the blockchain module is configured to receive and store a first data packet corresponding to the blockchain evidence data structure and its corresponding traceability code, or to receive and store a second data packet corresponding to the blockchain evidence data structure.

[0018] "Based on the entered traceability code and the activity link located by the traceability code, the corresponding process contract is queried and sent to the traceability code entry unit", the method is as follows:

[0019] Obtain the entered traceability code and query the process contract corresponding to the traceability code in the smart contract;

[0020] The participant role and activity link of the entered traceability code are obtained, and based on the activity link, the partial content corresponding to the queried process contract is sent to the traceability code entry unit; the partial content of the queried process contract includes the entity business activity process within the process contract and the information corresponding to the activity link filled in the identification field;

[0021] Among them, the participating roles of the traceability code and the activity links of the operator are obtained through the blockchain module.

[0022] In some preferred embodiments, the blockchain module further includes a user authority authentication unit;

[0023] The authority authentication unit is configured to authenticate the identities of participating roles and operators and assign specific permissions, wherein the assigned specific permissions correspond to the activity links.

[0024] The initial data entry unit is further configured to obtain the activity link data modified based on the current process contract, and send the modified activity link data to the smart contract middle platform;

[0025] The smart contract middle platform is also configured to receive the modified activity link data and update the entity business activity process within the current process contract based on the modified activity link data.

[0026] In some preferred embodiments, the traceability code management unit further includes a binding code generation subunit for generating a binding code, a unit traceability code generation subunit for generating a unit traceability code, and a sub-traceability code generation subunit for generating a sub-traceability code;

[0027] The binding code generating subunit is configured to generate a binding code for the entity to be bound based on the physical material attributes of the binding product entered by the initial data entry unit and the traceability code of the entity to be bound entered by the traceability code entry unit;

[0028] The unit traceability code generating subunit is configured to generate a unit traceability code for the entity to be disassembled based on the physical material attributes newly generated after the disassembly of the entity to be disassembled entered by the initial data entry unit;

[0029] The sub-traceability code generating sub-unit is configured to obtain quantity information corresponding to the entity to be distributed based on the physical material attributes entered by the initial data entry unit, and then generate a sub-traceability code for the entity to be distributed in combination with the quantity information.

[0030] In some preferred embodiments, the verification method of the first data packet and the second data packet is:

[0031] The verification method of the first data packet is:

[0032] Compare the physical material attributes in the first data packet with the attributes in the physical public attribute library and its value range rule library in the third data packet. If the corresponding attribute value can be found in the third data packet, it is determined that the verification is successful;

[0033] The verification method of the second data packet is:

[0034] The second data packet is compared with the attributes in the entity public attribute library and its value range rule library in the third data packet and the first entity material attributes in the first data packet after successful verification. If the corresponding attribute value can be queried in the third data packet and the first data packet after successful verification, and matches the quantity in the first data packet, it is determined that the verification is successful.

[0035] In some preferred embodiments, the transposition processing unit further includes a visualization processing unit;

[0036] The visualization processing unit is configured to send the first data packet and the second data packet, which are transposed into different data structures, to the traceability code entry unit in a table or graphic form for display based on the report model.

[0037] In some preferred embodiments, the method of "performing data transposition on the first data packet or the second data packet after successful verification" is as follows:

[0038] Combined with the stamp information of the set type corresponding to the first data packet or the second data packet after successful verification, the first data packet or the second data packet after successful verification is transposed into different data structures according to the data type, and signature authentication is performed according to the evidence contract to generate a blockchain evidence data structure.

[0039] In some preferred embodiments, the physical material attributes include design attributes, procurement attributes, basic production attributes and individual production attributes; the design attributes are in a one-to-many relationship with the procurement attributes, the basic production attributes and the individual production attributes respectively.

[0040] In some preferred embodiments, the set type of stamp information includes a time stamp, a geographic stamp, and an operator information stamp.

[0041] Beneficial effects of the present invention:

[0042] The present invention solves the problems of lack of management, difficulty in tracing and difficulty in verifying the whereabouts of entity data in existing oil and gas pipeline network construction.

[0043] (1) The present invention uses blockchain as the platform technology architecture to build a complete intelligent entity traceability system for oil and gas pipeline network projects, which can provide complete and real-time tracking, statistics and management of engineering entity data.

[0044] (2) In the present invention, the entity database includes two main attribute libraries: the entity common attribute library and the entity common attribute value range rule library. By standardizing the attribute values ​​and value ranges of the data in the entity database and comparing them with the input data, the correctness of the input data can be effectively guaranteed, thereby improving the statistical accuracy.

[0045] (3) In the present invention, the process contract is only set in the smart contract middle platform, and is not stored in the blockchain module. This allows the present invention to modify the process contract based on the obtained entity business activity process to be supplemented, so that the process contract can always be consistent with the entity's actual business activity process, and the entity's related activity link data can always correspond to the actual business activity process, meeting the variability in actual applications, and thus ensuring the accuracy of tracing and destination verification.

[0046] (4) In the present invention, the user authority authentication unit in the blockchain module can authenticate the identity of the participating roles and operators and assign specific permissions, wherein the assigned specific permissions correspond to the activity links, so that when the data middle platform obtains the identity information of the participating roles and operators, it can obtain the activity links of the participating roles and operators based on the blockchain module, and automatically send the corresponding process contract to the traceability code entry module based on the activity links, thereby achieving accurate limitation of the data entered by the participating roles and operators, thereby improving the accuracy of the data. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0048] Figure 1 It is a structural schematic diagram of an embodiment of the present invention;

[0049] Figure 2It is a structural diagram of the first data packet check in an embodiment of the present invention. DETAILED DESCRIPTION

[0050] To make the objectives, technical solutions, and advantages of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts shall fall within the scope of protection of the present invention.

[0051] The present application will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are intended only to illustrate the relevant invention and are not intended to limit the invention. It should also be noted that, for ease of description, only portions relevant to the relevant invention are shown in the accompanying drawings.

[0052] It should be noted that, unless there is any conflict, the embodiments and features in the embodiments of this application can be combined with each other.

[0053] The present invention provides a complete intelligent entity tracing system for oil and gas pipeline network engineering, such as Figure 1 As shown, the system includes: service middle platform, entity database, application module and blockchain module;

[0054] The application module includes an initial data entry unit and a traceability code entry unit;

[0055] The initial data entry unit is configured to obtain the physical material attributes and physical business activity process of the entity to be managed, take the physical material attributes of the entity to be managed as the first data packet, and send it to the data middle station of the service middle station, and send the physical business activity process to the smart contract middle station of the service middle station; the physical business activity process includes several activity links;

[0056] The traceability code entry unit is configured to obtain the entered traceability code and send it to the data center of the service center; it is also configured to receive and display the process contract corresponding to the activity link where the entered traceability code is located, and obtain the relevant activity link data of the activity link where the entity to be managed is located filled in based on the process contract, as a second data packet, and send it to the data center of the service center;

[0057] The entity database is configured to store a third data packet; the third data packet includes an entity common attribute library and a value range rule library for entity common attributes; the entity common attribute library is a database storing characteristics of common materials and equipment in oil and gas pipeline projects, standard links in business flows, and characteristic functions; the value range rule library for entity common attributes is a database storing mapping relationships between entity common attributes and preset value ranges;

[0058] The service middle platform includes a data middle platform, a traceability code management unit, and a smart contract middle platform;

[0059] The smart contract middle platform is configured to receive the entity business activity process and generate a process contract; the process contract includes the entity business activity process and the information filling identification fields corresponding to each activity link; the information filling identification fields are used to limit the type of information to be filled in each activity link;

[0060] The data middle platform includes a data packet verification unit, a transposition processing unit, and a process contract query unit;

[0061] The data packet verification unit is configured to receive the first data packet and verify it, and after verification, send it to the traceability code generation subunit and the transposition processing unit of the traceability code management unit; and is also configured to receive the second data packet and verify it, and send it to the transposition processing unit;

[0062] The transposition processing unit includes a data transposition unit, which is configured to perform data transposition on the first data packet or the second data packet after successful verification, and send the first data packet after data transposition and its corresponding traceability code or the second data packet after data transposition to the blockchain module;

[0063] The process contract query unit is configured to query the corresponding process contract based on the entered traceability code and the activity link located by the traceability code and send it to the traceability code entry unit;

[0064] The traceability code management unit includes a traceability code generation subunit; the traceability code generation subunit is configured to generate a traceability code based on the first data packet that has been successfully verified and send it to the data transposition unit;

[0065] The blockchain module is configured to receive and store a first data packet corresponding to the blockchain evidence data structure and its corresponding traceability code, or to receive and store a second data packet corresponding to the blockchain evidence data structure.

[0066] In order to more clearly illustrate the complete intelligent entity tracing system for oil and gas pipeline network engineering of the present invention, each module in an embodiment of the system of the present invention is described in detail below with reference to the accompanying drawings.

[0067] Specifically, if Figure 1 As shown, the present invention realizes complete and accurate statistics and management of entity data in oil and gas pipeline network construction by constructing two major work processes: initial data entry and work data entry, thereby greatly improving the convenience of tracing and whereabouts verification.

[0068] In the following embodiments, the working process of each module involved in the initial data entry is first described in detail, and then the working process of each module involved in the working data entry is described in detail.

[0069] 1. Initial data entry

[0070] The application module includes an initial data entry unit;

[0071] The initial data entry unit is configured to obtain the physical material attributes and physical business activity process of the entity to be managed, take the physical material attributes of the entity to be managed as the first data packet, and send it to the data middle station of the service middle station, and send the physical business activity process to the smart contract middle station of the service middle station; the physical business activity process includes several activity links;

[0072] In this embodiment, the physical material attributes include the physical material's design attributes, procurement attributes, basic production attributes, and individual production attributes. Design attributes and procurement attributes, procurement attributes and basic production attributes, and basic production attributes and individual production attributes each have a one-to-many relationship. Specifically, taking steel pipes as an example, design attributes include the pipe name (LSAW steel pipe), design specification (CDP2016), and unit of measurement (tons). Procurement attributes include contract number, purchase quantity, and supplier. Multiple LSAW steel pipe contracts generate multiple procurement attributes. Basic production attributes include the outer diameter, wall thickness, manufacturing standard, manufacturer, material, and quality inspection report of the steel pipe. Because the same contract may produce multiple different specifications and models of steel pipes, the same procurement attribute may correspond to multiple basic production attributes. Individual production attributes include pipe number, furnace number, length, and weight. The same specification and model of steel pipe may correspond to many pipes with different numbers and lengths. Therefore, the same basic production attribute may correspond to multiple individual production attributes. The entity business activity process includes design, procurement, production, delivery, transportation, arrival acceptance, warehousing, allocation, delivery, installation, construction inspection, debugging, and production.

[0073] It should be noted that, in this embodiment, the initial data entry unit includes at least two data entry modes: entry one by one and batch import. These two data entry modes are described in detail below.

[0074] (1) Enter item by item

[0075] A first database is preset in the initial data entry unit, which stores physical material attributes and physical business activity processes, and is displayed in the initial data entry unit according to design attributes, procurement attributes, basic production attributes, individual production attributes, and physical business activity processes for staff to fill in. Among them, attributes with limited ranges such as manufacturer and material, and their corresponding specific attribute values ​​(such as: XXX manufacturer, Lp360 material) are also stored in the first database and displayed in the initial data entry unit for staff to click, so as to standardize the staff's filling content. Attributes such as outer diameter, wall thickness, length, etc. that do not have a fixed range due to different actual needs, only the corresponding filling format is stored in the first database and displayed in the initial data entry unit, that is, only the staff's filling format is standardized, and the filling content is not limited.

[0076] (2) Batch import

[0077] The initial data entry unit is provided with a first data interface and a second data interface, and receives batch data imported by staff through the first data interface, and receives batch data automatically transmitted from other production systems through the second data interface, thereby improving the efficiency of data entry.

[0078] The entity database is configured to store a third data packet; the third data packet includes an entity common attribute library and a value range rule library for entity common attributes; the entity common attribute library is a database storing characteristics of common materials and equipment in oil and gas pipeline projects, standard links in business flows, and characteristic functions; the value range rule library for entity common attributes is a database storing mapping relationships between entity common attributes and preset value ranges;

[0079] In this embodiment, the entity public attribute library includes the main technical characteristics, quality characteristics and business characteristics of 197 commonly used materials and equipment of oil and gas pipeline engineering entities, as well as 15 standard activity links of common business flows (design, procurement, production, sampling, inspection, delivery, transportation, arrival acceptance, warehousing, allocation, outbound delivery, installation, construction inspection, debugging, and commissioning) and 7 characteristic functions (binding, distribution, disassembly, combination, after-sales service, random inspection, and dynamic configuration contract).

[0080] The value range rule library of the entity's common attributes includes several libraries set based on technical standards, organization types, brands, engineering projects, contract information, and basic information, such as: material name and type library, measurement unit selection library, product attribute library, material selection library, pipe type selection library, manufacturer brand library, pressure level type option library, station section library, anti-corrosion type library, anti-corrosion grade library, etc.

[0081] It should be noted that the entity material attributes and entity business activity processes stored in the first database correspond to the contents stored in the entity public attribute library and its value range rule library.

[0082] The service middle platform includes a data middle platform, a traceability code management unit, and a smart contract middle platform; the data middle platform includes a data packet verification unit, a transposition processing unit, and a process contract query unit;

[0083] The data packet verification unit is configured to receive the first data packet and verify it. If the verification is successful, the verified first data packet is sent to the traceability code generation subunit and the transposition processing unit of the traceability code management unit. If the verification fails, the verification failure information is sent to the initial data entry unit to remind the staff to modify the physical material attributes of the entity to be managed, and receive the modified new first data packet for verification until the verification is successful. It should be noted that when the physical material attributes and physical business activity processes corresponding to the first data packet are entered one by one, based on the matching characteristics of the first database and the third database, the first data packet does not need to be verified and can be sent to the traceability code management unit; when the physical material attributes and physical business activity processes corresponding to the first data packet are entered through batch import, the first data packet needs to be verified to ensure the standardization of the entered data.

[0084] In this embodiment, if Figure 2 As shown, the verification method of the first data packet is:

[0085] Read the third data packet in the entity database, determine the integrity of the first data packet, and compare the entity material attributes in the first data packet with the attributes in the entity common attribute library and its value range rule library in the third data packet. If there are no missing attributes in the first data packet and the corresponding attribute values ​​can be found in the third data packet, then the verification is determined to be successful;

[0086] The traceability code management unit includes a traceability code generation subunit; the traceability code generation subunit is configured to generate a traceability code based on the first data packet that has been successfully verified and send it to the transposition processing unit;

[0087] The transposition processing unit includes a data transposition unit, which is configured to perform data transposition on the first data packet after successful verification, and send the first data packet after data transposition and its corresponding traceability code to the blockchain module; it should be supplemented that before the entity business activity process corresponding to the first data packet is sent to the smart contract middle platform, the entity business activity process is first sent to the data transposition unit through the initial data entry unit, and the entity business activity process of the first data packet is bound to the traceability code corresponding to the first data packet based on the binding ID through the data transposition unit. After that, the bound entity business activity process is sent to the smart contract middle platform through the data transposition unit for realizing the traceability function.

[0088] In this embodiment, the data transposition method for the first data packet after successful verification is to combine the obtained stamp information of a set type corresponding to the first data packet after successful verification, transpose the first data packet after successful verification into a private data structure and a public data structure, perform signature authentication according to the evidence storage contract, and combine the private data structure and the public data structure to generate a first blockchain evidence storage data structure. Private data refers to business and personal information, such as contracts, the operator's name and contact information for each activity link, etc.; public data refers to the entity's technical information and the operation time and records of each activity link, such as product name, product image, specification model, quality report, and, for example, debugging time and debugging records. The set stamp information includes timestamp, geolocation stamp, and operator information stamp. It should also be noted that the data in the first data packet is divided into public data and private data. When the data transposition unit binds the entity business activity process of the first data packet with the traceability code corresponding to the first data packet based on the binding ID, the data transposition unit is also configured to read the permissions of the participating roles and operators from the blockchain module to obtain the data type of each data in the first data packet, and mark the public data and private data respectively through the permission identification classification identification number to distinguish between public data and private data.

[0089] The smart contract middle platform is configured to receive the entity business activity process and generate a process contract; the process contract includes the information filling identification field corresponding to the entity business activity process and its various activity links; the information filling identification field is used to limit the type of information to be filled in for each activity link; it is also configured to generate and store a proof contract.

[0090] In this embodiment, different activity links correspond to different information filling identification fields, and the information filling identification fields include information types such as the filling date and the person who filled it out, and the information filling fields also include specific content corresponding to the filling date, the person who filled it out and other information types (such as: XXX operator), so that when the staff fills in the information of each activity link, they can only fill in fixed information types and click on fixed specific content in the information type, thereby realizing the limitation of the information type and content to be filled in each activity link.

[0091] The blockchain module is configured to receive and store a first data packet corresponding to the first blockchain evidence data structure and its corresponding traceability code;

[0092] In this embodiment, the blockchain module includes a blockchain underlying platform and multiple blockchain nodes. The blockchain underlying platform is configured to receive a first data packet corresponding to a first blockchain evidence data structure and a traceability code corresponding to the first data packet, and complete evidence storage on multiple blockchain nodes, forming a consensus control mechanism for data synchronization between multiple blockchain nodes.

[0093] Furthermore, the blockchain module further includes a user authority authentication unit;

[0094] In this embodiment, the authority authentication unit is configured to authenticate the identities of the participating roles and operators and assign specific permissions, wherein the assigned specific permissions include settings for the data types of the data that the participating roles and operators need to enter, so as to distinguish between public data and private data.

[0095] 2. Work data entry

[0096] The application module also includes a traceability code entry unit;

[0097] The traceability code entry unit is configured to obtain the entered traceability code and send it to the data center of the service center; it is also configured to receive and display the process contract corresponding to the activity link where the entered traceability code is located, and obtain the relevant activity link data of the activity link where the entity to be managed is located filled in based on the process contract, as a second data packet, and send it to the data center of the service center;

[0098] In this embodiment, the traceability code entry unit displays the process contract corresponding to the activity link where the entered traceability code is located to limit the content filled in by the staff, thereby improving the standardization and completeness of the data filled in by the staff; and it should be noted that the traceability code entry unit also includes two data entry methods: entry one by one and batch import. Among them, the batch import method is the same as the batch import method in the initial data entry unit, so it will not be described in detail here.

[0099] The data middle platform also includes a process contract query unit;

[0100] The process contract query unit is configured to query the corresponding process contract based on the entered traceability code and the activity link located by the traceability code and send it to the traceability code entry unit;

[0101] Specifically, "based on the entered traceability code and the activity link located by the traceability code, the corresponding process contract is queried and sent to the traceability code entry unit", and the method is:

[0102] Obtain the entered traceability code and query the process contract corresponding to the traceability code in the smart contract;

[0103] In this embodiment, the binding ID on the entered traceability code is obtained, and based on the binding ID, the process contract corresponding to the traceability code is queried in the smart contract platform;

[0104] The participant role of the entered traceability code and the activity link where the operator is located are obtained, and based on the activity link, the corresponding part of the queried process contract is sent to the traceability code entry unit; the partial content of the queried process contract includes the entity business activity process within the process contract and the information corresponding to the activity link where it is located, and the identification field is filled in; wherein, the participant role of the traceability code and the activity link where the operator is located are obtained through the blockchain module.

[0105] In this embodiment, the participating roles of the entered traceability code and the activity link where the operator is located are obtained based on the data transposition unit.

[0106] The data transposition unit is further configured to obtain the activity links of the role and the operator based on the blockchain module.

[0107] The authority authentication unit is configured to authenticate the identities of the participating roles and operators and assign specific permissions, wherein the assigned specific permissions correspond to the activity links, and the assigned specific permissions include a determination of the data type of each data entered by the participating roles and operators, so as to distinguish public data from private data.

[0108] Specifically, the permission authentication unit has preset permission settings for the identity IDs of participating roles and operators. Before obtaining the entered traceability code, the traceability code entry unit must first obtain the identity IDs of the participating roles and operators and send them to the data transposition unit. The data transposition unit then receives the identity IDs of the participating roles and operators and reads the permissions corresponding to these identity IDs in the permission authentication unit. By analyzing the permissions, it determines the activity link to which the identity ID belongs.

[0109] The data packet verification unit is configured to receive the second data packet and perform verification. If the verification is successful, the verified second data packet is sent to the data transposition unit. If the verification fails, the verification failure information is sent to the traceability code entry unit to remind the staff to modify the physical material attributes of the entity to be managed, and receive a new second data packet for verification until the verification is successful.

[0110] It should be noted that when the relevant activity link data corresponding to the second data packet are entered one by one, based on the characteristics of the matching between the process contract and the third database, there is no need to verify the attribute values ​​of the second data packet, but only its quantity needs to be verified. When the relevant activity link data corresponding to the second data packet are entered through batch import, it is necessary to verify both the attribute values ​​and the quantity of the second data packet to ensure the standardization of the entered data.

[0111] In this embodiment, taking the second data packet generated based on the data entered in a batch import mode as an example, the verification method of the second data packet is:

[0112] The data transposition unit reads the first data packet that matches the entered traceability code from the blockchain module, reads the third data packet from the entity database, and compares the second data packet with the attributes in the entity public attribute library and its value domain rule library in the third data packet and the first entity material attributes in the first data packet after successful verification. If the corresponding attribute value can be found in the third data packet and the first data packet after successful verification, and the quantity matches, it is determined that the verification is successful. Specifically, "quantity matching" means that the first data packet after successful verification includes several procurement contracts or other contracts, and the contracts record the quantity of related entities. If the quantity of entities in the second data packet is greater than the quantity of the entities in the first data packet, it is determined to be "quantity mismatch". If the quantity of entities in the second data packet is not greater than the quantity of the entities in the first data packet, it is determined to be "quantity matching".

[0113] The data transposition unit is configured to perform data transposition on the second data packet after successful verification, and send the second data packet after data transposition to the blockchain module;

[0114] In this embodiment, the data transposition method for the second data packet after successful verification is to combine the obtained stamp information of the set type corresponding to the second data packet after successful verification, transpose the second data packet after successful verification into a private data structure and a public data structure, and perform signature authentication according to the evidence contract, and generate a second blockchain evidence data structure by combining the private data structure and the public data structure. Among them, the stamp information of the set type includes a timestamp, a geographic stamp, and an operator information stamp. Among them, the data transposition method for the second data packet after successful verification is the same as the data transposition method for the first data packet after successful verification, so it will not be described in detail here. At the same time, it should be noted that before the data transposition unit performs data transposition on the second data packet, the data transposition unit is also configured to read the corresponding permissions of the participating roles and operators from the user authority authentication unit to mark the data in the second data packet, thereby realizing the distinction between public data and private data in the second data packet.

[0115] The blockchain module is configured to receive and store a second data packet corresponding to the second blockchain evidence data structure.

[0116] Furthermore, the present invention satisfies the variability in the actual application of oil and gas pipeline network projects by constructing two major work processes: modifying process contracts and adding traceability codes.

[0117] In the following embodiment, the working process of each module involved in modifying the process contract is first described in detail, and then the working process of each module involved in adding a traceability code is described in detail.

[0118] 3. Modify the process contract

[0119] The initial data entry unit is configured to obtain the activity link data modified based on the current process contract, and send the modified activity link data to the smart contract middle platform;

[0120] In this embodiment, before obtaining the activity link data modified by the current process contract, the traceability code entry unit obtains the traceability code entered by the staff and sends it to the process contract query unit. The initial data entry unit obtains the process contract corresponding to the traceability code through the process contract query unit and displays it for the staff to modify the process contract. Afterwards, the initial data entry unit receives the modification operation performed by the staff. Specifically, the modification operations include "supplement" and "deletion", and it should be emphasized that the modification operation can only modify the activity links that have not been carried out. For the activity links that have been carried out, since the activity link data corresponding to the activity link has been stored in the blockchain, it cannot be modified. Among them, the activity link that has been carried out refers to the activity link for which the relevant activity link data has been entered, thereby achieving the goal of meeting the variability of actual applications while ensuring the accuracy of the data.

[0121] The smart contract middleware is further configured to receive the modified activity link data and update the entity business activity process within the current process contract based on the modified activity link data. This allows the present invention to modify the process contract based on the acquired entity business activity process to be modified, thereby ensuring that the process contract is always consistent with the entity's actual business activity process and that the entity's relevant activity link information always corresponds to the actual business activity process, thus satisfying the variability in practical applications and ensuring the accuracy of traceability and destination verification.

[0122] 4. Added traceability code

[0123] The traceability code management unit further includes a binding code generation subunit for generating a binding code, a unit traceability code generation subunit for generating a unit traceability code, and a sub-traceability code generation subunit for generating a sub-traceability code;

[0124] The binding code generation operation is mainly used when the shipment of packaging boxes, containers or other scattered entities needs to highlight some related situations. The binding code generation subunit is configured to generate the binding code of the entity to be bound based on the physical material attributes of the binding product entered by the initial data entry unit and the traceability code of the entity to be bound entered by the traceability code entry unit;

[0125] The generation method and binding method of the binding code are as follows:

[0126] The initial data entry unit obtains the physical material attributes of the binding product used by the binding entity and the traceability code of the entity to be bound, and sends the product information used by the binding entity as a fourth data packet to the binding code generation subunit and the data transposition unit, and sends the traceability code of the entity to be bound to the data transposition unit;

[0127] The binding code generating subunit generates a binding code based on the fourth data packet and sends the binding code to the data transposition unit;

[0128] The data transposition unit binds the binding code and the traceability code of the entity to be bound, receives the fourth data packet and performs data transposition, and sends the fourth data packet after data transposition and its corresponding bound binding code to the blockchain module for evidence storage.

[0129] The unit traceability code generation operation is mainly used when a large piece of equipment needs to be disassembled and the disassembled product does not have a traceability code. The unit traceability code generation subunit is configured to generate a unit traceability code for the entity to be disassembled based on the newly generated physical material attributes of the entity to be disassembled entered by the initial data entry unit;

[0130] The generation method and binding method of the unit traceability code are as follows:

[0131] The initial data entry unit obtains the traceability code of the entity to be disassembled and the physical material attributes of the entity newly generated after disassembly, and sends the traceability code of the entity to be disassembled to the data transposition unit, and sends the physical material attributes of the entity newly generated after disassembly as a fifth data packet to the unit traceability code generation subunit;

[0132] The unit tracing code generating subunit generates a unit tracing code based on the fifth data packet, and sends the unit tracing code and the fifth data packet to the data transposition unit;

[0133] The data transposition unit obtains the traceability code of the entity to be disassembled and the unit traceability code, associates the traceability code of the entity to be disassembled with the unit traceability code, and sends the associated unit traceability code and its corresponding fifth data packet to the blockchain module for evidence storage;

[0134] The sub-traceability code generation operation is primarily used when multiple small packages or multiple identical products need to be distributed. The sub-traceability code generation sub-unit is configured to obtain quantity information corresponding to the entity to be distributed based on the physical material attributes entered by the initial data entry unit, and then generate a sub-traceability code for the entity to be distributed based on this quantity information.

[0135] The generation method and binding method of the sub-traceability code are as follows:

[0136] The initial data entry unit obtains the traceability code of the entity to be distributed and the quantity information to be distributed, and sends the traceability code of the entity to be distributed to the data transposition unit, and sends the quantity information to be distributed as a sixth data packet to the sub-traceability code generation sub-unit;

[0137] The sub-traceability code generating sub-unit generates a sub-traceability code based on the sixth data packet, and sends the sub-traceability code and the sixth data packet to the data transposition unit;

[0138] The data transposition unit obtains the traceability code and sub-traceability code of the entity to be distributed, associates the data packet corresponding to the traceability code of the entity to be distributed with the sub-traceability code, and sends the associated sub-traceability code and its corresponding sixth data packet to the blockchain module for evidence storage. Furthermore, the data transposition unit also updates the first data packet corresponding to the traceability code of the entity to be distributed and sends the updated content as the seventh data packet to the blockchain module for evidence storage. The data packets corresponding to the traceability code of the entity to be distributed include the first to seventh data packets corresponding to the traceability code.

[0139] Furthermore, in the following embodiments, the working process of entity tracing is described in detail.

[0140] 5. Entity Traceability

[0141] The traceability code entry unit obtains the entered traceability code and traceability instruction, and sends the entered traceability code and traceability instruction to the data transposition unit, obtains the first data packet and the second data packet related to the traceability code through the data transposition unit, and sends them to the visualization processing unit of the transposition processing unit. After processing by the visualization processing unit, they are displayed in the traceability code entry unit for staff to view. Among them, the visualization processing unit is configured to obtain the first data packet and the second data packet transposed into different data structures from the blockchain module through the data transposition unit, and send the first data packet and the second data packet transposed into different data structures to the traceability code entry unit in a table or graphic form based on the report model for display. It should be noted that the visualization processing unit is preset with several report models generated based on different indicators and the calculation model corresponding to each report model. The report model can be in the form of a table, a graphic form, or a combination of a table and a graphic form. Taking the first data packet and the second data packet as data sources, extract the data in the first data packet and the second data packet based on the material type name, participating units, business flow activity links, time period and other standards, and fill in the data into the report model corresponding to the indicator according to the indicator query password entered by the staff through the traceability code entry unit, thereby realizing the display of the data. Among them, the indicators include but are not limited to chain operation analysis (unit chain quantity, material chain quantity, etc.), traceability link analysis (current activity link batch, activity link quantity), traceability query analysis (number of queries), traceability process quantity analysis (number of completed traceability links, material categories, etc.), comprehensive progress statistics of oil and gas pipeline material supply (detailed quantity of materials in production, delivery, installation, commissioning, etc.), and quality inspection statistics.

[0142] It should also be added that when the staff enters the traceability code through the traceability code entry unit to view historical data, the data transposition unit obtains the permissions corresponding to the participating roles and operators to limit the display content of the traceability code entry unit, such as only public data, only private data of the link, or other scopes.

[0143] It should be noted that the complete intelligent entity traceability system for oil and gas pipeline network projects 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 modules or steps in the embodiments of the present invention can be further decomposed or combined. For example, the modules in the above embodiment can be combined into one module, or further divided into multiple sub-modules to complete all or part of the functions described above. The names of the modules and steps involved in the embodiments of the present invention are only for the purpose of distinguishing the modules or steps and are not to be regarded as improper limitations on the present invention.

[0144] Those skilled in the art should be able to appreciate that, in conjunction with the modules and method steps of each example described in the embodiments disclosed herein, it is possible to implement them with electronic hardware, computer software, or a combination of the two, and the programs corresponding to the software modules and method steps can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. In order to clearly illustrate the interchangeability of electronic hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in electronic hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0145] The terms "first", "second", etc. are used to distinguish similar objects, rather than to describe or indicate a particular order or sequence.

[0146] The term "comprise" or any other similar term is intended to cover non-exclusive inclusion such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed or inherent to such process, method, article, or apparatus.

[0147] Thus far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art may make equivalent changes or substitutions to the relevant technical features, and the technical solutions after such changes or substitutions will fall within the scope of protection of the present invention.

Claims

1. A complete intelligent entity tracing system for oil and gas pipeline network engineering, characterized by: The system includes: a service platform, an entity database, an application module and a blockchain module; The application module includes an initial data entry unit and a traceability code entry unit; The initial data entry unit is configured to obtain the physical material attributes and physical business activity process of the entity to be managed, take the physical material attributes of the entity to be managed as the first data packet, and send it to the data middle station of the service middle station, and send the physical business activity process to the smart contract middle station of the service middle station; the physical business activity process includes several activity links; The traceability code entry unit is configured to obtain the entered traceability code and send it to the data center of the service center; it is also configured to receive and display the process contract corresponding to the activity link where the entered traceability code is located, and obtain the relevant activity link data of the activity link where the entity to be managed is located filled in based on the process contract, as a second data packet, and send it to the data center of the service center; The entity database is configured to store a third data packet; the third data packet includes an entity common attribute library and a value range rule library for entity common attributes; the entity common attribute library is a database storing characteristics of common materials and equipment in oil and gas pipeline projects, standard links in business flows, and characteristic functions; the value range rule library for entity common attributes is a database storing mapping relationships between entity common attributes and preset value ranges; The service middle platform includes a data middle platform, a traceability code management unit, and a smart contract middle platform; The smart contract middle platform is configured to receive the entity business activity process and generate a process contract; the process contract includes the entity business activity process and the information filling identification fields corresponding to each activity link; the information filling identification fields are used to limit the type of information to be filled in each activity link; the process contract only allows the modification of unexecuted links; The data middle platform includes a data packet verification unit, a transposition processing unit, and a process contract query unit; The data packet verification unit is configured to receive the first data packet and verify it, and after verification, send it to the traceability code generation subunit and the transposition processing unit of the traceability code management unit; and is also configured to receive the second data packet and verify it, and send it to the transposition processing unit; The transposition processing unit includes a data transposition unit, which is configured to perform data transposition on the first data packet or the second data packet after successful verification, and send the first data packet after data transposition and its corresponding traceability code or the second data packet after data transposition to the blockchain module; when transposing data, public data and private data are distinguished and displayed based on permissions; The process contract query unit is configured to query the corresponding process contract based on the entered traceability code and the activity link located by the traceability code and send it to the traceability code entry unit; The traceability code management unit includes a traceability code generation subunit; the traceability code generation subunit is configured to generate a traceability code based on the first data packet that has successfully been verified and send it to the data transposition unit; the traceability code management unit also includes a binding code generation subunit for generating a binding code, a unit traceability code generation subunit for generating a unit traceability code, and a sub-traceability code generation subunit for generating a sub-traceability code; The blockchain module is configured to receive and store a first data packet corresponding to the blockchain evidence data structure and its corresponding traceability code, or to receive and store a second data packet corresponding to the blockchain evidence data structure.

2. The complete intelligent entity tracing system for oil and gas pipeline network engineering according to claim 1 is characterized in that: "Based on the entered traceability code and the activity link located by the traceability code, the corresponding process contract is queried and sent to the traceability code entry unit." The method is: Obtain the entered traceability code and query the process contract corresponding to the traceability code in the smart contract; The participant role and activity link of the entered traceability code are obtained, and based on the activity link, the partial content corresponding to the queried process contract is sent to the traceability code entry unit; the partial content of the queried process contract includes the entity business activity process within the process contract and the information corresponding to the activity link filled in the identification field; Among them, the participating roles of the traceability code and the activity links of the operator are obtained through the blockchain module.

3. The complete intelligent entity tracing system for oil and gas pipeline network engineering according to claim 2 is characterized in that: The blockchain module also includes a user authority authentication unit; The authority authentication unit is configured to authenticate the identities of participating roles and operators and assign specific permissions, wherein the assigned specific permissions correspond to the activity links.

4. The complete intelligent entity tracing system for oil and gas pipeline network engineering according to claim 1 is characterized in that: The initial data entry unit is further configured to obtain the activity link data modified based on the current process contract, and send the modified activity link data to the smart contract middle platform; The smart contract middle platform is also configured to receive the modified activity link data and update the entity business activity process within the current process contract based on the modified activity link data.

5. The complete intelligent entity tracing system for oil and gas pipeline network engineering according to claim 1 is characterized in that: The binding code generation subunit is configured to generate a binding code for the entity to be bound based on the physical material attributes of the binding product entered by the initial data entry unit and the traceability code of the entity to be bound entered by the traceability code entry unit; The unit traceability code generating subunit is configured to generate a unit traceability code for the entity to be disassembled based on the physical material attributes newly generated after the disassembly of the entity to be disassembled entered by the initial data entry unit; The sub-traceability code generating sub-unit is configured to obtain quantity information corresponding to the entity to be distributed based on the physical material attributes entered by the initial data entry unit, and then generate a sub-traceability code for the entity to be distributed in combination with the quantity information.

6. The complete intelligent entity tracing system for oil and gas pipeline network engineering according to claim 1 is characterized in that: The verification method of the first data packet and the second data packet is: The verification method of the first data packet is: Compare the physical material attributes in the first data packet with the attributes in the physical public attribute library and its value range rule library in the third data packet. If the corresponding attribute value can be found in the third data packet, it is determined that the verification is successful; The verification method of the second data packet is: The second data packet is compared with the attributes in the entity public attribute library and its value range rule library in the third data packet and the first entity material attributes in the first data packet after successful verification. If the corresponding attribute value can be queried in the third data packet and the first data packet after successful verification, and matches the quantity in the first data packet, it is determined that the verification is successful.

7. The complete intelligent entity tracing system for oil and gas pipeline network engineering according to claim 1 is characterized in that: The transposition processing unit further includes a visualization processing unit; The visualization processing unit is configured to send the first data packet and the second data packet, which are transposed into different data structures, to the traceability code entry unit in a table or graphic form for display based on the report model.

8. The complete intelligent entity tracing system for oil and gas pipeline network engineering according to claim 1 is characterized in that: "Performing data transposition on the first data packet or the second data packet after successful verification", the method is as follows: Combined with the stamp information of the set type corresponding to the first data packet or the second data packet after successful verification, the first data packet or the second data packet after successful verification is transposed into different data structures according to the data type, and signature authentication is performed according to the evidence contract to generate a blockchain evidence data structure.

9. The complete intelligent entity tracing system for oil and gas pipeline network engineering according to claim 1 is characterized in that: The physical material attributes include design attributes, procurement attributes, basic production attributes and individual production attributes; the design attributes are in a one-to-many relationship with the procurement attributes, the basic production attributes and the individual production attributes respectively.

10. The complete intelligent entity tracing system for oil and gas pipeline network engineering according to claim 8 is characterized in that: The set type of stamp information includes a time stamp, a geographic stamp, and an operator information stamp.

Images