A cloud edge-end cooperative geological archive full life cycle management method and system

Abstract

This invention relates to the field of geological archive digital resource management technology, specifically a cloud-edge-device collaborative method and system for the full lifecycle management of geological archives. The method includes: acquiring geological archive data, constructing a geoscientific semantic basis and generating acquisition basis records, and generating a forward lifecycle trajectory starting node based on the acquisition basis records; constructing a forward lifecycle trajectory, encapsulating the geoscientific semantic basis, the generated prescription chain, and the regeneration verification anchor into an archive seed package object; performing regeneration adjudication on the verified archive deliverables and performing lifecycle closure verification on the archive seed package object; selecting a target based on the archive seed package object to generate a prescription chain and construct regeneration instructions, which are then regenerated by edge nodes to obtain archive deliverables; generating correction task records and distributing them to edge nodes. This invention achieves regenerable, verifiable, traceable, and corrective management of geological archives during edge acquisition, edge processing, and cloud archiving.

Description

Technical Field

[0001] This invention relates to the field of geological archive digital resource management technology, specifically to a cloud-edge-device collaborative method and system for the full lifecycle management of geological archives. Background Technology

[0002] With the long-term development of geological exploration, mineral development, and geological disaster prevention, a large number of paper geological archives, audio-visual materials, and multi-source observation data have been gradually digitized and centrally managed through information systems. In new projects, electronic geological archive files are generally generated collaboratively through edge acquisition devices, edge computing nodes, and cloud archive platforms. In existing technologies, the work usually revolves around the archive files themselves, including cataloging, metadata indexing, format conversion, off-site backup, and long-term preservation. In cloud-edge-device multi-node deployment scenarios, the transfer and sharing of archives between different nodes is mostly achieved through file synchronization, interface transmission, or service calls. However, the overall management still focuses on the "final archive file" as the core object. The acquisition base, processing steps, regeneration process, and migration process between nodes that the archives undergo during their formation are only briefly recorded or stored in log form, lacking structured lifecycle management methods. In practical applications, there are still issues with the lack of verifiable lifecycle links and locating correction mechanisms for geological archives in multi-node, multi-round processing across cloud, edge, and end-user platforms. Specifically: On the one hand, after the same geological archive undergoes multiple processing and regeneration processes at end-user acquisition nodes, edge processing nodes, and cloud archive systems, there is a lack of a complete lifecycle path and content comparison basis that can be verified by technical means. Users find it difficult to determine whether the current archive version is still consistent with the initial geological semantics and acquisition basis. Once problems such as field loss, spatial range truncation, or incorrect mapping of geological objects occur during regeneration or format migration, manual investigation and location are often the only option. On the other hand, when the cloud or business system discovers abnormalities in the archive content or raises questions about the archive's reliability, it is difficult to determine in a timely manner whether the error was introduced during the acquisition stage, edge processing stage, or cloud archiving and subsequent regeneration stage. There is also a lack of correction instruction mechanisms for specific processing steps and nodes, which can easily lead to defective archive versions being stored for a long time or continuing to be used in downstream business scenarios, affecting the long-term credibility and traceability of geological archives. Summary of the Invention

[0003] The purpose of this invention is to provide a cloud-edge-device collaborative method and system for the full lifecycle management of geological archives, in order to solve the problem mentioned in the background art of the lack of verifiable lifecycle links and locating correction mechanisms for geological archives in multi-node, multi-round processing at the cloud, edge, and device levels.

[0004] To achieve the above objectives, the technical solution of the present invention is: a cloud-edge-device collaborative method for the full lifecycle management of geological archives, comprising: S1. Obtain geological archive data from the edge acquisition nodes, construct a geoscientific semantic base and generate acquisition base records, generate a positive lifecycle trajectory start node based on the acquisition base records, and send the geoscientific semantic base, acquisition base records and positive lifecycle trajectory start node to the edge nodes; S2. In the edge nodes, construct the positive life cycle trajectory based on the starting node of the positive life cycle trajectory, and construct the generation prescription chain including the processing step sequence and the regeneration verification anchor based on the geoscientific semantic base and the collection base record. Encapsulate the geoscientific semantic base, the generation prescription chain and the regeneration verification anchor to form an archive seed package object. Among them, the forward lifecycle trajectory is a temporal trajectory used to represent the processing stages and their sequential relationships experienced by the archive seed package object among the end-side acquisition nodes, edge nodes, and cloud nodes; the generation prescription chain is an ordered instruction chain obtained by encoding the processing steps required in the geological archive processing process and their execution sequence; the regeneration verification anchor is a set of reference data used to characterize the geological archive corresponding to the archive seed package object in terms of key fields, structural relationships, and statistical characteristics; the archive seed package object is a logical archive unit formed by binding the geoscientific semantic basis, the generation prescription chain, and the regeneration verification anchor around a single geological archive. S3. In the cloud node, a reverse reconstruction trajectory including a reverse processing step sequence is constructed based on the generated prescription chain. The generated prescription chain is called to generate a verification archive delivery. The verification archive delivery is reverse reconstructed based on the reverse reconstruction trajectory to obtain the reconstruction base result. The reconstruction base result is compared with the geoscientific semantic base for consistency. The verification archive delivery is regenerated and the archive seed package object is lifecycle closed verification. The lifecycle state marker is set for the archive seed package object. Among them, the reverse reconstruction trajectory is a chain representation of the processing steps that correspond to the processing steps in the generated prescription chain and are arranged in the opposite direction; the life cycle state marker is a life cycle state indicator field attached to the archive seed package object, specifically including the life cycle closed state and the life cycle broken state. S4. For archive seed package objects in the closed life cycle state, write the archive seed package object into the long-term archive storage unit. When a geological archive retrieval request is received, select the target according to the archive seed package object to generate a prescription chain construction regeneration instruction. The edge node then regenerates the archive delivery document according to the regeneration instruction. For archive seed package objects in the broken life cycle state, generate a correction task record and send it to the edge node.

[0005] Preferably, in step S2, the starting node of the forward lifecycle trajectory is a lifecycle node generated at the edge acquisition node and used to identify the starting position of the forward lifecycle trajectory. The starting node of the forward lifecycle trajectory includes the time information recorded by the acquisition base, the identifier of the edge acquisition node, and the status information recorded by the acquisition base. The forward lifecycle trajectory is a trajectory object composed of multiple lifecycle nodes arranged in the order of processing time. It is used to represent the processing stages that the archive seed package object goes through sequentially between the edge acquisition node, the edge node, and the cloud node, and their sequential relationship. It is also used to record the processing path and state evolution order of the archive seed package object throughout its entire lifecycle. The structural features of the forward lifecycle trajectory are: each lifecycle node includes a node type field, a timestamp field, an operation type identifier field, and a data status identifier field.

[0006] Preferably, in step S2, the generated prescription chain uses the geoscientific semantic basis and the collection basis records as input range, and is also used to constrain the processing flow executed by the end-side collection nodes, edge nodes, and cloud nodes when generating the archive deliverable; the generated prescription chain includes a sequence of processing steps consisting of multiple processing step units, each processing step unit including a step identifier field, an input data type identifier field, an output data type identifier field, and a processing algorithm identifier field; the processing step units in the processing step sequence establish a reference relationship between the predecessor step and the successor step according to a preset execution order, which is used to limit the execution dependency relationship between each processing step.

[0007] Preferably, in S2, the regeneration verification anchor is a set of reference data extracted from geological archive data and intermediate processing results based on the geoscientific semantic basis and the generated prescription chain. It is used to verify the verification archive deliverables and to provide a reference benchmark when comparing the archive deliverables for consistency. The data structure of the regeneration verification anchor includes a set of key field values, a set of structural relationship descriptions, and a set of statistical feature vectors. The archive seed package object is a logical archive unit formed by binding the geoscientific semantic basis, the generated prescription chain, and the regeneration verification anchor around the geological archive data according to a preset encapsulation format. It is used as the unique lifecycle management object of the corresponding geological archive and the basic object driving the regeneration of the verification archive deliverables and the lifecycle closure verification during the cloud-edge-device collaborative processing.

[0008] Preferably, in step S3, the reverse reconstruction trajectory is used to reverse reconstruct the verification file deliverable in the cloud node to recover the reconstruction base result, and is also used to map the processing steps in the generated prescription chain according to the mapping rules; wherein, the mapping rules of the reverse reconstruction trajectory are specifically as follows: each processing step in the generated prescription chain is pre-configured with a corresponding reverse processing step and an equivalent reconstruction rule, the reverse reconstruction trajectory arranges each reverse processing step in reverse order according to the processing steps in the generated prescription chain, and when performing reverse reconstruction on the verification file deliverable, each reverse processing step is called in reverse order, and the data flow during the reverse reconstruction process is opposite to the data flow of the corresponding processing step in the generated prescription chain.

[0009] Preferably, in S3, the verified archive deliverable is an instance of an archive deliverable generated based on the generated prescription chain with the geoscientific semantic base and the collected base records as input, used as the current archive object for performing reverse reconstruction and consistency comparison in the cloud node; the reconstructed base result is the base layer data representation obtained by performing reverse reconstruction on the verified archive deliverable based on the reverse reconstruction trajectory, used to participate in consistency comparison in the same representation space as the geoscientific semantic base; the consistency comparison between the reconstructed base result and the geoscientific semantic base involves comparing the reconstructed base result with the corresponding spatial range field, temporal range field, geological object identification field, and key semantic field in the geoscientific semantic base.

[0010] Preferably, in step S3, the lifecycle closure verification of the archive seed package object is implemented based on the lifecycle closure verification condition. Specifically, the lifecycle closure verification condition is as follows: when the reconstructed base result and the geoscientific semantic base satisfy the consistency comparison rule on all fields involved in the comparison, and the starting node of the forward lifecycle trajectory and the termination state corresponding to the reverse reconstruction trajectory point to the same acquisition base record, the archive seed package object is determined to be in a lifecycle closed state; otherwise, the archive seed package object is determined to be in a lifecycle broken state. The regeneration adjudication of the verified archive deliverable is based on the consistency comparison result and the reference data contained in the regeneration verification anchor to determine the regeneration adjudication result of the verified archive deliverable, and different regeneration processing operations are performed according to the regeneration adjudication result. The regeneration adjudication result includes a valid regeneration result, a result that needs to be regenerated, and a result that is prohibited from use.

[0011] Preferably, in step S4, the long-term archive storage unit is an archive storage resource pool for long-term storage of archive seed package objects in a closed lifecycle state; during the process of writing the archive seed package object into the long-term archive storage unit, a lifecycle version index is also constructed based on the forward lifecycle trajectory and reverse reconstruction trajectory corresponding to the archive seed package object, and the lifecycle version index is stored in the long-term archive storage unit in a one-to-one correspondence with the archive seed package object; the lifecycle version index includes a lifecycle node identifier set, a verification round identifier, and a generated prescription chain version identifier.

[0012] Preferably, in step S4, the regeneration instruction is a set of instructions generated by the cloud node based on the target generated prescription chain selected in the archive seed package object. The regeneration instruction carries a version identifier of the generated prescription chain and a corresponding sequence of processing steps, which is used to drive the regeneration of the archive delivery document in the edge node based on the target generated prescription chain. The archive delivery document is the archive output result obtained by the edge node through processing according to the regeneration instruction. The correction task record is a task record generated by the cloud node and sent to the edge node when the archive seed package object has a lifecycle broken state marker. It is used to instruct the edge node to perform a correction operation on the processing process associated with the archive seed package object. The data structure of the correction task record specifically includes the target archive seed package object identifier, the target edge node identifier, the correction type identifier, and the trigger reason identifier.

[0013] On the other hand, the present invention provides a cloud-edge-device collaborative geological archive lifecycle management system, including a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to implement the cloud-edge-device collaborative geological archive lifecycle management method described above.

[0014] Compared with the prior art, the above-mentioned technical solution of the present invention has the following beneficial technical effects: 1. In this invention, the archive closed-loop verification mechanism based on the forward life cycle trajectory, the reverse reconstruction trajectory, and the life cycle closure verification conditions can automatically determine whether the current archive content is still consistent with the original geoscientific semantics and the collection base after the geological archive has undergone multiple regenerations and format migrations. It can also distinguish the archive seed package objects with life cycle closure and life cycle rupture by life cycle status markers, thereby reducing the reliance on manual line-by-line verification and experience judgment. 2. In this invention, by building a lifecycle version index in the cloud and generating a regeneration instruction carrying a prescription chain version identifier and a processing step sequence, and generating a correction task record carrying a correction type identifier and a trigger cause identifier when the lifecycle breaks, the same geological archive can be repeatedly regenerated, version traceable, and automatically corrected for specific nodes and processing steps among end-side acquisition nodes, edge nodes, and cloud nodes, reducing the risk of erroneous archive versions being continuously used in the business system. Attached Figure Description

[0015] Figure 1 This is a flowchart of one embodiment of the present invention. Detailed Implementation

[0016] Example 1, as Figure 1 As shown, the specific implementation steps of the cloud-edge-device collaborative geological archive full lifecycle management method proposed in this invention are as follows: S1. Obtain geological archive data from the edge acquisition nodes, construct a geoscientific semantic base and generate acquisition base records, generate a positive lifecycle trajectory start node based on the acquisition base records, and send the geoscientific semantic base, acquisition base records and positive lifecycle trajectory start node to the edge nodes; S2. In the edge nodes, construct the positive life cycle trajectory based on the starting node of the positive life cycle trajectory, and construct the generation prescription chain including the processing step sequence and the regeneration verification anchor based on the geoscientific semantic base and the collection base record. Encapsulate the geoscientific semantic base, the generation prescription chain and the regeneration verification anchor to form an archive seed package object. Among them, the forward lifecycle trajectory is a temporal trajectory used to represent the processing stages and their sequential relationships experienced by the archive seed package object among the end-side acquisition nodes, edge nodes, and cloud nodes; the generation prescription chain is an ordered instruction chain obtained by encoding the processing steps required in the geological archive processing process and their execution sequence; the regeneration verification anchor is a set of reference data used to characterize the geological archive corresponding to the archive seed package object in terms of key fields, structural relationships, and statistical characteristics; the archive seed package object is a logical archive unit formed by binding the geoscientific semantic basis, the generation prescription chain, and the regeneration verification anchor around a single geological archive. S3. In the cloud node, a reverse reconstruction trajectory including a reverse processing step sequence is constructed based on the generated prescription chain. The generated prescription chain is called to generate a verification archive delivery. The verification archive delivery is reverse reconstructed based on the reverse reconstruction trajectory to obtain the reconstruction base result. The reconstruction base result is compared with the geoscientific semantic base for consistency. The verification archive delivery is regenerated and the archive seed package object is lifecycle closed verification. The lifecycle state marker is set for the archive seed package object. Among them, the reverse reconstruction trajectory is a chain representation of the processing steps that correspond to the processing steps in the generated prescription chain and are arranged in the opposite direction; the life cycle state marker is a life cycle state indicator field attached to the archive seed package object, specifically including the life cycle closed state and the life cycle broken state. S4. For archive seed package objects in the closed life cycle state, write the archive seed package object into the long-term archive storage unit. When a geological archive retrieval request is received, select the target according to the archive seed package object to generate a prescription chain construction regeneration instruction. The edge node then regenerates the archive delivery document according to the regeneration instruction. For archive seed package objects in the broken life cycle state, generate a correction task record and send it to the edge node.

[0017] In this embodiment S1, the end-side acquisition node is set up at the geological exploration or data processing site. The end-side acquisition node includes a data acquisition unit connected to acquisition equipment such as borehole, well logging, and geological logging, as well as a local processing unit for preprocessing the acquisition results. The geological archive data includes the original measurement records, interpretation results, map files and their metadata corresponding to a single geological archive. After completing one archive data acquisition or processing, the end-side acquisition node aggregates information such as acquisition task number, spatial location, time interval, data type and storage location to form a set of original archive data for archive management, and attaches it to the identifier of the current acquisition task in the local cache area as the input data source for subsequent construction of geoscientific semantic basis and acquisition basis records.

[0018] In this embodiment S1, the construction of the geoscientific semantic basis is based on the semantic extraction and structured mapping operations performed on the geological archive data acquired by the end-side acquisition nodes. By identifying and classifying fields such as borehole numbers, measurement point coordinates, stratigraphic codes, lithological descriptions, physical property parameters, and map indexes in the archives, an entity set between geological objects, spatial units, time slices, and attribute indicators is established. The stratigraphic contact relationships, spatial adjacency relationships, temporal evolution relationships, and attribute dependencies between entities are recorded in a structured form to obtain a semantic representation structure for a single geological archive. On this basis, taking a single archive acquisition or a single archive processing process as the recording granularity, fields such as archive number, acquisition task number, spatial range, time range, acquisition equipment information, data type set, and quality status information are combined to form an acquisition basis record corresponding to the archive acquisition process. The acquisition basis record is stored in the end-side local storage as the basic data entry connecting the geological archive data and the geoscientific semantic basis.

[0019] In this embodiment S1, the generation of the forward lifecycle trajectory starting node is based on the lifecycle start annotation operation performed on the acquisition base record. After assigning a new lifecycle identifier to the current acquisition base record, the acquisition time or archiving time recorded in the acquisition base record is used as the starting time field, the node identifier of the end-side acquisition node is used as the node identifier field, the archive status information in the acquisition base record is used as the data status field, and the node type field is set to indicate the node type of the end-side acquisition stage. The above fields are encapsulated according to the preset lifecycle node data structure to form the forward lifecycle trajectory starting node that identifies the starting position of the archive lifecycle. This starting node is associated with the corresponding acquisition base record through the lifecycle identifier and is used for subsequent forward lifecycle... The trajectory is extended as the first lifecycle node; after the edge acquisition node completes the construction of the geoscientific semantic base, the generation of the acquisition base record, and the generation of the positive lifecycle trajectory start node, it sends the geoscientific semantic base, the acquisition base record, and the positive lifecycle trajectory start node to the edge node in the form of message packets or data packets through the communication channel established with the edge node. During the transmission process, the file number, acquisition task number, and lifecycle identifier are attached to the message header for the edge node to perform associated storage and unified parsing of the three types of data. The transmission process supports integrity verification and retransmission control of data packets to ensure that the geoscientific semantic base, the acquisition base record, and the positive lifecycle trajectory start node form a consistent data start set at the edge node receiving end.

[0020] In this embodiment S2, the starting node of the forward lifecycle trajectory is a lifecycle node generated at the edge acquisition node and used to identify the starting position of the forward lifecycle trajectory. The starting node of the forward lifecycle trajectory includes the time information of the acquisition base record, the identifier of the edge acquisition node, and the status information of the acquisition base record. The forward lifecycle trajectory is a trajectory object composed of multiple lifecycle nodes arranged in the order of processing time. It is used to represent the processing stages that the archive seed package object goes through in sequence between the edge acquisition node, the edge node, and the cloud node and their sequential relationship. It is also used to record the processing path and state evolution order of the archive seed package object throughout its entire lifecycle. The structural features of the forward lifecycle trajectory are: each lifecycle node includes a node type field, a timestamp field, an operation type identifier field, and a data status identifier field.

[0021] In this embodiment S2, after receiving the geoscientific semantic base, the acquisition base record, and the starting node of the forward lifecycle trajectory sent by the end-side acquisition node, the edge node initializes a forward lifecycle trajectory based on the starting node of the forward lifecycle trajectory. The trajectory takes the starting node as the first lifecycle node and internally assigns a unique lifecycle identifier to the trajectory for association with subsequent archive seed package objects. When the edge node performs each processing stage on the same archive seed package object, it generates a new lifecycle node after each processing stage is completed. The new node is written with the node type of the current processing stage, the processing completion time, the corresponding processing operation type, and the status identifier of the archive data at this time. The node is appended to the end of the forward lifecycle trajectory in chronological order. The forward lifecycle trajectory adopts a chain node sequence or sequential list structure ordered by timestamp in the storage structure to support the chronological traversal of the processing process of the archive seed package object on different nodes.

[0022] In this embodiment S2, the starting node of the forward lifecycle trajectory is used to identify the starting position of the forward lifecycle trajectory by setting a starting point marker and an empty predecessor node reference in the node structure. When constructing the forward lifecycle trajectory, the node with the starting point marker is fixed as the first node of the trajectory, and this node is kept unreplaced in any subsequent node addition or trajectory query operation. The time information of the collected base record includes the collection start and end time or archiving time corresponding to the current geological archive collection or sorting process. It is used to initialize the timestamp field in the starting node and provide a reference for the time sequence of subsequent nodes. The end-side collection node identifier is a unique identifier code to distinguish different end-side collection nodes. It is used to mark the collection source corresponding to the start position of the archive lifecycle in the starting node and to provide a basis for distinguishing different collection locations or collection equipment in subsequent trajectory analysis. The status information of the collected base record is a status enumeration that represents the current archive collection data processing status, such as original collection completed, quality inspection passed, preliminary structuring completed, etc. When the starting node is generated, this status information is written into the data status identifier field to serve as the initial state for subsequent state evolution.

[0023] In this embodiment S2, the processing path and state evolution sequence of the archive seed package object throughout its entire lifecycle are recorded through a forward lifecycle trajectory. When the archive seed package object is first encapsulated at the edge node, the object is bound to the lifecycle identifier of the forward lifecycle trajectory. Subsequently, when the archive seed package object completes the prescription chain construction at the edge node, completes the verification of archive deliverable generation at the cloud node, performs reverse reconstruction and lifecycle closure verification, completes long-term storage in the long-term archive storage unit, or performs correction processing at the edge node, corresponding lifecycle nodes are generated and appended to the end of the forward lifecycle trajectory. This makes the forward lifecycle trajectory present the changes in processing stages from edge acquisition, edge processing to cloud verification and long-term storage in the node type field, and present the state evolution sequence from the initial acquisition state to the prescription generation state, verification passed or verification failed state, long-term storage state or state to be corrected in the data status identifier field. By traversing the trajectory in time order, the processing path and corresponding state evolution process of the archive seed package object throughout its entire lifecycle can be recovered.

[0024] In this embodiment S2, the generated prescription chain uses the geoscientific semantic basis and the collection basis records as input range, and is also used to constrain the processing flow executed by the end-side collection nodes, edge nodes, and cloud nodes when generating archive deliverables; the generated prescription chain includes a sequence of processing steps consisting of multiple processing step units, each processing step unit including a step identifier field, an input data type identifier field, an output data type identifier field, and a processing algorithm identifier field; the processing step units in the processing step sequence establish a reference relationship between the predecessor steps and the successor steps according to a preset execution order, which is used to limit the execution dependency relationship between each processing step.

[0025] In this embodiment S2, the prescription chain is organized in a chain structure, using a sequence of processing step units arranged in execution order as the basic data structure. Each processing step unit is logically connected end-to-end through the predecessor step identifier and the successor step identifier to form a unidirectional or branched ordered chain. During the construction of the prescription chain, the edge node first determines the various processing steps required from the original archival data to the archival deliverable based on the geological object type, spatial range, and attribute index set recorded in the geoscientific semantic base, as well as the data type, quality status, and collection range information recorded in the acquisition base record. These steps include data cleaning, format normalization, spatial coordinate transformation, attribute calculation, and version encapsulation. A corresponding processing step unit is generated for each step, and these processing step units are arranged in a preset execution order to form a complete processing chain from input data to archival deliverable output. When the end-side acquisition node, edge node, and cloud node perform processing operations related to the archival seed package object, they all use the prescription chain as the execution basis. Only the step unit matching the current node role is selected and executed within the processing step range covered by the prescription chain, thereby forming a unified constraint on the processing flow of generating archival deliverables throughout the entire chain.

[0026] In this embodiment S2, the sequence of processing steps in the generated prescription chain consists of multiple processing step units. When constructing the generated prescription chain, the edge node instantiates each processing action obtained from the analysis of the geoscientific semantic base and the collection base records into a processing step unit. The step identifier field of the processing step unit is set to a unique number within the current generated prescription chain, the input data type identifier field is set to the input data type required by the processing action, the output data type identifier field is set to the output data type generated after the processing action is completed, and the processing algorithm identifier field is set to the processing algorithm identifier that can be called in the local algorithm library or service interface. The execution order between each processing step is preset according to the archive processing business logic. By recording the predecessor step identifier list and the successor step identifier list in each processing step unit, the sequence of processing steps not only presents a linear arrangement relationship in the storage structure, but also forms a chain processing path with execution dependency constraints in the logical structure. When there is a branch process, a tree or directed acyclic graph structure can be formed by configuring multiple successor step units for the same predecessor step. The execution order and dependency relationship are still uniformly managed by the generated prescription chain.

[0027] In this embodiment S2, the step identifier field in the processing step unit is used to identify the unique identity of the processing step in the prescription chain and serves as the association key for the reference relationship between the predecessor step and the successor step; the input data type identifier field is used to describe the input data type or data structure required by the current processing step. When a node is ready to execute the processing step, it compares the currently held data type with the input data type identifier field to determine whether the execution conditions are met; the output data type identifier field is used to describe the data type generated after the processing step is executed and serves as the basis for the successor step to determine whether its input matches; the processing algorithm identifier field is used to indicate the specific processing algorithm or processing module that needs to be called when executing the processing step. In the actual execution process, each node loads the corresponding algorithm implementation from the local algorithm library or remote algorithm service according to the processing algorithm identifier field. Under the condition that the output data type of all predecessor steps matches the input data type identifier field of the current step and the predecessor steps have been completed, the processing step unit is set to the executable state, and the execution process of the processing step sequence is advanced in sequence according to the preset execution order and the reference relationship between the predecessor step and the successor step.

[0028] In this embodiment S2, the regeneration verification anchor is a set of reference data extracted from geological archive data and intermediate processing results based on the geoscientific semantic basis and the generated prescription chain. It is used to verify the verification archive deliverables and to provide a reference benchmark when comparing the archive deliverables for consistency. The data structure of the regeneration verification anchor includes a set of key field values, a set of structural relationship descriptions, and a set of statistical feature vectors. The archive seed package object is a logical archive unit formed by binding the geoscientific semantic basis, the generated prescription chain, and the regeneration verification anchor around the geological archive data according to a preset encapsulation format. It is used as the unique lifecycle management object of the corresponding geological archive and the basic object driving the regeneration of the verification archive deliverables and the lifecycle closure verification during the cloud-edge-device collaborative processing.

[0029] In this embodiment S2, the regeneration verification anchor, based on the processing scope defined by the geoscientific semantic base and the generated prescription chain, extracts reference data items for verification from geological archive data and intermediate processing results in the processing flow. First, it selects field values ​​corresponding to the spatial location of geological objects, stratigraphic codes, key physical property parameters, and important interface depths to form a set of key field values, which are used to compare the same fields item by item after the verification archive deliverables are generated. At the same time, it extracts structured descriptions representing stratigraphic relationships, fault contact relationships, topological relationships between measuring points, and index relationships between maps and attribute data, and encodes them into a set of structural relationship descriptions, which are used to check whether the structural relationships are maintained in the verification archive deliverables. Consistency; further, taking the numerical distribution of a certain attribute within a specific spatial range or time interval as the object, the mean, variance, quantiles, frequency distribution parameters and other statistical quantities are calculated for the original data or intermediate results to form a set of statistical feature vectors. This is used to evaluate whether the overall numerical level and distribution pattern of the verification archive deliverables are consistent with the reference state. When verifying the verification archive deliverables, the key field value set is first used to complete the field-level difference comparison, then the structural relationship description set is used to identify structural relationship destruction or mismatch, and finally the set of statistical feature vectors is used to determine whether there is an abnormal shift in the numerical distribution, thereby comprehensively giving the judgment result of whether the verification archive deliverables have passed the regeneration verification anchor verification.

[0030] In this embodiment S2, to explicitly record the execution traces of each processing step in the generated prescription chain in the forward lifecycle trajectory, multiple forward nodes are added to the forward lifecycle trajectory based on the generated prescription chain. A forward node represents a lifecycle node where a certain processing step in the generated prescription chain is completed on the edge node. The node type field is set to indicate the node type of the edge processing, the timestamp field is set to the time when the corresponding step is completed, the operation type identifier field is set to the operation identifier that matches the step identifier field in the processing step unit, and the data status identifier field is set to the status identifier of the archive data after executing the step. This is done according to the generated prescription chain. The preset order of the processing steps in the middle appends these positive nodes to the end of the positive lifecycle trajectory, forming an execution trajectory that corresponds one-to-one with the generated prescription chain. After the file seed package object is generated, the positive lifecycle trajectory identifier corresponding to the file seed package object is recorded internally. When the edge node sends the file seed package object to the cloud node, it packages and transmits the file seed package object and the positive lifecycle trajectory identifier together. This allows the cloud node to retrieve the complete positive lifecycle trajectory through the identifier when verifying the generation of the file deliverable and verifying the lifecycle closure, thus realizing the reference association between the file seed package object and the positive lifecycle trajectory.

[0031] In this embodiment S2, the archive seed package object, as a logical archive unit, uses a preset encapsulation format to uniformly bind the geoscientific semantic base, the generated prescription chain, and the regeneration verification anchor. The preset encapsulation format is defined during the system design phase based on geological archive management requirements and the cloud-edge-device collaborative processing flow. The encapsulation structure includes an archive identifier field, a lifecycle identifier field, a geoscientific semantic base reference area, a generated prescription chain storage area, a regeneration verification anchor storage area, and an association field with the positive lifecycle trajectory identifier. A logical archive unit refers to an abstract archive unit that uniformly manages the aforementioned multiple structured data in the form of a single object or a single record at the storage and transmission level. The process of generating the archive seed package object... In this process, the edge node first assigns an archive identifier and a lifecycle identifier to the current geological archive, writes the completed geoscientific semantic base reference into the geoscientific semantic base reference area, writes the sequence of processing steps for generating the prescription chain and its dependencies into the generated prescription chain storage area, writes the regeneration verification anchor composed of a set of key field values, a set of structural relationship descriptions, and a set of statistical feature vectors into the regeneration verification anchor storage area, and writes the trajectory identifier corresponding to the positive lifecycle trajectory. Finally, an archive seed package object is formed that can be transferred and managed between the end-side acquisition node, edge node, and cloud node, and is used to provide complete context information when subsequently regenerating and verifying archive deliverables and performing lifecycle closure verification.

[0032] In this embodiment S3, the reverse reconstruction trajectory is used to reverse reconstruct the verification file deliverable in the cloud node to recover the reconstruction base result, and is also used to map the processing steps in the generated prescription chain according to the mapping rules; wherein, the mapping rules of the reverse reconstruction trajectory are as follows: each processing step in the generated prescription chain is pre-configured with a corresponding reverse processing step and an equivalent reconstruction rule, the reverse reconstruction trajectory arranges each reverse processing step in reverse order according to the processing steps in the generated prescription chain, and when performing reverse reconstruction on the verification file deliverable, each reverse processing step is called in reverse order, and the data flow during the reverse reconstruction process is opposite to the data flow of the corresponding processing step in the generated prescription chain.

[0033] In this embodiment S3, after receiving the generation prescription chain associated with the target file seed package object, the cloud node first reads the set of processing step units recorded in the generation prescription chain and constructs a forward step list according to the preset execution order of the processing step units. Then, based on the forward step list, it traverses backward from the last step, queries the rule base for the corresponding reverse processing step definition for each forward processing step unit, generates a reverse processing step unit containing a reverse processing algorithm identifier, a reverse input data type identifier, and a reverse output data type identifier, and records the mapping relationship between it and the current forward processing step unit. During the traversal, each reverse processing step unit is added to the reverse reconstruction trajectory data structure in reverse order of the forward processing steps, so that the reverse reconstruction trajectory forms a reverse processing step sequence that traces back from the verified file delivery to the base layer data representation. This reverse processing step sequence serves as the sole execution path basis when performing reverse reconstruction on the verified file delivery in the future.

[0034] In this embodiment S3, the mapping rules for the reverse reconstruction trajectory are configured based on the processing algorithm identifier and data type flow recorded in the generated prescription chain. For each forward processing step, one or more mapping rule entries are pre-registered in the cloud rule base. Each mapping rule entry includes a forward processing algorithm identifier, a corresponding reverse processing algorithm identifier, a reversibility flag, an equivalent reconstruction rule identifier, and an input / output data type mapping relationship. The reversibility flag is used to indicate whether the forward processing algorithm has a strict mathematical inverse operation, and the input / output data type mapping relationship is used to indicate the input data type that the reverse processing step should accept and the recovered output data type when it is executed. The equivalent reconstruction rule identifier is used to approximately restore the data form of the previous stage when the forward processing steps are not completely reversible or when there is information compression or aggregation. When constructing the reverse reconstruction trajectory, the cloud node retrieves the matching mapping rule entry from the rule base for each forward processing step in the generated prescription chain according to its processing algorithm identifier, and instantiates the corresponding reverse processing step unit according to the reverse processing algorithm identifier and data type mapping relationship in the entry. The reverse processing step unit is then inserted into the reverse reconstruction trajectory in reverse order of the forward steps, so that the data flow direction during the reverse reconstruction process is opposite to the data flow direction of the corresponding processing step in the generated prescription chain.

[0035] In this embodiment S3, the process of pre-configuring the corresponding reverse processing step and equivalent reconstruction rule for each processing step in the generated prescription chain is completed during the system deployment or rule maintenance phase. The reverse processing step refers to a data processing step in the cloud node that takes the verified file delivery or intermediate reverse reconstruction result as input, and performs data transformation, inverse operation or reconstruction operation that is opposite to a certain forward processing step, and outputs data that semantically corresponds to the input data of the forward processing step. The equivalent reconstruction rule refers to a set of rules defined to constrain the reconstruction of the reverse processing step for forward processing steps that are not completely reversible or have information loss, based on the geoscientific semantic basis, the regeneration verification anchor and the processing parameters recorded in the generated prescription chain. The system includes a set of rules for behavior, which may include allowed numerical deviation ranges, structural relationship preservation conditions, and statistical feature consistency constraints. During the configuration phase, the available forward processing algorithms in the system are classified, and strictly corresponding reverse processing algorithms are registered for reversible algorithms. For algorithms that involve compression, segmentation aggregation, or pruning operations, approximate reverse processing algorithms based on equivalent reconstruction rules are registered. A mapping table is established in the rule base from forward processing algorithm identifiers to reverse processing algorithm identifiers and equivalent reconstruction rule identifiers. This enables cloud nodes to sequentially call the corresponding reverse processing steps and apply the corresponding equivalent reconstruction rules according to the mapping table when constructing and executing reverse reconstruction trajectories, thereby gradually restoring the reconstruction base result.

[0036] In this embodiment S3, the verification archive deliverable is an instance of the archive deliverable generated based on the generated prescription chain with the geoscientific semantic base and the collected base record as input. It is used as the current archive object for performing reverse reconstruction and consistency comparison in the cloud node. The reconstructed base result is the base layer data representation obtained by performing reverse reconstruction on the verification archive deliverable based on the reverse reconstruction trajectory. It is used to participate in consistency comparison in the same representation space as the geoscientific semantic base. The consistency comparison between the reconstructed base result and the geoscientific semantic base is to compare the reconstructed base result with the corresponding spatial range field, time range field, geological object identification field and key semantic field in the geoscientific semantic base.

[0037] In this embodiment S3, before completing the reverse reconstruction, the cloud node first generates a verification archive deliverable based on the generated prescription chain. The cloud parses and generates the prescription chain from the archive seed package object, and organizes the processing step units marked as participating in the generation of the archive deliverable into an execution plan according to the execution dependency and preset order. Using the geoscientific semantic basis and the collection basis records as the initial input data, the corresponding processing algorithm modules are called step by step to perform data cleaning, coordinate and projection transformation, field normalization, semantic annotation, layout generation and other steps. Before each step is executed, the data type of the current intermediate result is checked to see if it matches the input data type identifier field in the processing step unit. After the execution is completed, the output data type is updated and passed to the subsequent steps. When all the terminal steps in the execution plan are completed, the final output dataset and its layout and structured metadata are packaged into an archive deliverable instance and internally marked as a verification archive deliverable, which is used as the current archive object in the subsequent reverse reconstruction and consistency comparison process.

[0038] In this embodiment S3, after the cloud node completes the reverse reconstruction of the verification archive deliverables based on the reverse reconstruction trajectory, it unifies the obtained reconstruction base result according to the coordinate system, time reference, and geological object identification system used by the geoscientific semantic base. Coordinate-type fields undergo coordinate system transformation and spatial reference alignment; time-type fields undergo time zone standardization and time format unification; and geological object identification fields undergo encoding table mapping, ensuring that the reconstruction base result and the geoscientific semantic base are consistent in field structure and representation space. According to predefined comparison rules, spatial range fields, time range fields, geological object identification fields, and key semantic fields are extracted in pairs from the reconstruction base result and the geoscientific semantic base. Spatial range fields include coordinate boundaries and depth intervals of measurement points or structural objects; time range fields include collection or observation time intervals; geological object identification fields include stratigraphic numbers, structural numbers, and measurement point numbers; and key semantic fields include stratigraphic attributes, interface types, and important segmentation results. For each type of field, a corresponding difference threshold is pre-configured in the comparison rule base. The thresholds for spatial and time-type fields are set according to engineering accuracy requirements, while the thresholds for key semantic fields can be set separately according to different project types.

[0039] In this embodiment S3, the specific steps for comparing the reconstructed base result with the geoscientific semantic base are as follows: First, calculate the spatial difference degree based on the meaning of each pair of spatial range fields. Compare the coordinate range in the reconstructed base result with the coordinate range in the geoscientific semantic base in terms of position and range. If both the spatial offset and range difference fall within the corresponding spatial range threshold, the spatial range field is determined to be consistent. Second, calculate the time difference degree for each pair of time range fields. Compare the start and end times in the reconstructed base result with the start and end times in the geoscientific semantic base item by item. If the difference between the start and end times does not exceed the preset time threshold, the time range field is determined to be consistent. Then, perform an identifier consistency judgment on each pair of geological object identifier fields. The object numbers in the reconstructed basement results are matched one by one with the object numbers in the geoscientific semantic basement. When all matches are successful, the geological object identification field is determined to be consistent. For key semantic fields, the comparison method is selected according to the field type. For numerical key semantic fields, the numerical difference is calculated and compared with the corresponding numerical threshold. For categorical or aggregate key semantic fields, the number of missing and new items is counted and compared with the aggregate difference threshold. If the difference between all spatial range fields, temporal range fields, geological object identification fields and key semantic fields involved in the comparison does not exceed their respective preset thresholds, the reconstructed basement results and the geoscientific semantic basement are determined to meet the consistency comparison. Otherwise, the fields that do not meet the conditions and their difference information are recorded for subsequent regeneration adjudication and life cycle closure verification.

[0040] In this embodiment S3, the lifecycle closure verification of the archive seed package object is implemented based on the lifecycle closure verification condition. Specifically, the lifecycle closure verification condition is as follows: when the reconstructed base result and the geoscientific semantic base satisfy the consistency comparison rule on all fields involved in the comparison, and the starting node of the forward lifecycle trajectory and the termination state corresponding to the reverse reconstruction trajectory point to the same acquisition base record, the archive seed package object is determined to be in a lifecycle closed state; otherwise, the archive seed package object is determined to be in a lifecycle broken state. The regeneration adjudication of the verified archive deliverable is based on the consistency comparison result and the reference data contained in the regeneration verification anchor to determine the regeneration adjudication result of the verified archive deliverable, and different regeneration processing operations are performed according to the regeneration adjudication result. The regeneration adjudication result includes a valid regeneration result, a result that needs to be regenerated, and a result that is prohibited from use.

[0041] In this embodiment S3, the lifecycle closure verification condition is jointly constituted by the consistency comparison result and the lifecycle trajectory closure relationship. The consistency comparison rule is to compare the reconstructed base result with the spatial range field, temporal range field, geological object identification field, and key semantic field in the geoscientific semantic base one by one, and give the field-level pass status and overall pass mark. When all the fields participating in the comparison meet their respective preset threshold constraints, the consistency comparison result is marked as pass. The starting node of the forward lifecycle trajectory is the first lifecycle node created in the end-side acquisition stage. This node records the acquisition base record identifier, the end-side acquisition node identifier, and the initial data status information. The termination state corresponding to the reverse reconstruction trajectory is the reverse reconstruction trajectory. The base layer state description obtained after the last reverse processing step is completed also carries the acquisition base record identifier and data state description fields. Under the premise that the consistency comparison result is passed, the acquisition base record identifier in the starting node of the forward life cycle trajectory is further compared with the acquisition base record identifier in the termination state of the reverse reconstruction trajectory. When the two are consistent, the life cycle state mark of the file seed package object is updated to the life cycle closed state. When the consistency comparison fails or the acquisition base record identifier is inconsistent, the life cycle state mark is updated to the life cycle broken state, and the field type that caused the break or the reason for the trajectory not being closed is recorded in the life cycle state mark for subsequent traceability.

[0042] In this embodiment S3, the lifecycle closure state and lifecycle rupture state of the archive seed package object are used to distinguish the lifecycle integrity of geological archives in the cloud-edge-end collaborative processing process. The lifecycle closure state indicates that the content link and processing trajectory link associated with the archive seed package object, from the acquisition base record to the verification archive deliverable and then to the reconstruction base result, all form a closed loop. That is, after reverse reconstruction, the verification archive deliverable can reproduce the base layer data that meets the consistency comparison rules in the representation space consistent with the geoscientific semantic base. At the same time, the starting node of the forward lifecycle trajectory and the ending state of the reverse reconstruction trajectory both point to the same acquisition base record. The lifecycle rupture state indicates that at least one of the above two conditions is not met. It may be manifested as the difference between the reconstruction base result and the geoscientific semantic base in certain spatial range fields, time range fields or key semantic fields exceeding the threshold, or the acquisition base record pointed to by the ending state of the reverse reconstruction trajectory is inconsistent with the acquisition base record of the starting node of the forward lifecycle trajectory. At this time, in addition to the state type, the lifecycle state mark also includes a list of fields that do not meet the consistency comparison rules or an identifier of the acquisition base record with inconsistent trajectory, which is used to take targeted correction and management strategies for the archive seed package object in the future.

[0043] In this embodiment S3, the consistency comparison result and the verification result of the regeneration verification anchor are used as inputs. The consistency comparison result includes the pass / fail flags for each field-level comparison and the overall consistency flag. The verification result of the regeneration verification anchor includes the comparison results of the key field value set, the comparison results of the structural relationship description set, and the comparison results of the statistical feature vector set. A regeneration adjudication result is generated according to a preset adjudication rule. When the consistency comparison result passes and the regeneration verification anchor does not detect any anomalies exceeding the tolerance in all key fields, structural relationships, and statistical features, the regeneration adjudication result is determined as a valid regeneration result. Under this result, the current verified archive deliverable is registered as a valid archive deliverable version that can be provided externally or used for subsequent calls. When only a few fields in the consistency comparison result are slightly different... When a deviation is detected by the micro-threshold or the regeneration check anchor, which can be corrected by re-executing some processing steps, the regeneration adjudication result is determined to be a result requiring regeneration. Under this result, a regeneration task record is generated, instructing a new verification archive deliverable to be regenerated based on the same generation prescription chain and updating the status of this attempt. When the consistency comparison result is seriously unsuccessful or the regeneration check anchor detects problems such as damage to critical structural relationships or critical semantic errors that cannot be eliminated by simple repetitive processing, the regeneration adjudication result is determined to be a prohibited result. Under this result, the current verification archive deliverable is registered as an unusable version, and the reason for prohibition is written in the lifecycle status mark or associated record of the archive seed package object, providing a basis for subsequent correction and intervention for the archive seed package object.

[0044] In this embodiment S4, the long-term archive storage unit is an archive storage resource pool for long-term storage of archive seed package objects in the closed life cycle state. It supports indexing and accessing the archive seed package objects according to the archive identifier and the life cycle version identifier. During the process of writing the archive seed package object into the long-term archive storage unit, a life cycle version index is also constructed based on the forward life cycle trajectory and reverse reconstruction trajectory corresponding to the archive seed package object, and the life cycle version index is stored in the long-term archive storage unit in a one-to-one correspondence with the archive seed package object. The life cycle version index includes a life cycle node identifier set, a verification round identifier, and a generated prescription chain version identifier.

[0045] In embodiment S4, after the cloud node completes the lifecycle closure verification, it writes the file seed package object in the lifecycle closure state into the long-term archive storage unit. Specifically, it receives the encapsulated data structure of the file seed package object through the storage access interface, parses it to obtain the file identifier, lifecycle identifier, and binary content of the file seed package object, combines the file identifier with the newly allocated lifecycle version identifier to form a primary index key, and writes the file seed package object into the archive storage resource pool using this primary index key as the index item. The long-term archive storage unit maintains an archive object area and an index metadata area. The archive object area stores file seed package objects in physical or logical groups according to the file identifier and lifecycle version identifier. The index metadata area maintains the mapping relationship between the file identifier and the lifecycle version identifier set, as well as the mapping relationship between the lifecycle version identifier and the storage location identifier. When an index access request is received, the corresponding lifecycle version identifier set is retrieved according to the file identifier, and then the storage location of the target file seed package object in the archive object area is obtained according to the lifecycle version identifier, thereby realizing index access of the file seed package object according to the file identifier and the lifecycle version identifier.

[0046] In this embodiment S4, during the process of writing the archive seed package object into the long-term archive storage unit, the cloud node constructs a lifecycle version index based on the forward lifecycle trajectory and reverse reconstruction trajectory corresponding to the archive seed package object. Specifically, it extracts the key lifecycle node identifiers participating in the current lifecycle closure process from the forward lifecycle trajectory, including the starting node identifier of the edge acquisition stage, the key processing node identifier of the edge processing stage, and the node identifier of the cloud verification stage, and merges them with the node identifier corresponding to the termination state of the reverse reconstruction trajectory to form a lifecycle node identifier set; at the same time, it extracts the current verification round number from the regeneration adjudication process record as a verification round identifier to distinguish the same... An archive generates multiple closed versions under different regeneration rounds; and obtains the version number of the generation prescription chain used to generate the current verified archive deliverable from the internal records of the archive seed package object or the cloud algorithm configuration, as the generation prescription chain version identifier. The lifecycle node identifier set, the verification round identifier, and the generation prescription chain version identifier are combined to form a lifecycle version index structure. The lifecycle version index is established in a one-to-one correspondence with the archive identifier and lifecycle version identifier of the corresponding archive seed package object and written into the index metadata area, so that the long-term archive storage unit can trace back the set of processing nodes and the generation prescription chain version used in this version through the lifecycle version index during subsequent access.

[0047] In embodiment S4, after receiving a geological archive retrieval request, the cloud node parses the archive identifier, time conditions, quality level conditions, and usage type conditions contained in the request. First, based on the archive identifier, it retrieves all lifecycle version identifiers and their corresponding lifecycle version indexes from the long-term archive storage unit. It filters the lifecycle node identifier set and generated prescription chain version identifier recorded in each lifecycle version index, selecting lifecycle version identifiers whose lifecycle time range covers the time conditions of the retrieval request and whose corresponding version has been marked as a valid regeneration result. Further, based on the quality level conditions of the retrieval request, it prioritizes lifecycle version identifiers with higher verification round identifiers and that meet the target quality level requirements. Based on the usage type conditions, it matches the generated prescription chain version identifier with the corresponding usage label of the generated prescription chain usage tag. Finally, it determines the unique or highest priority target lifecycle version index, reads the generated prescription chain version identifier from this lifecycle version index as the version identifier of the target generated prescription chain, and constructs a regeneration instruction in combination with the archive identifier. In subsequent processing, the cloud node sends the regeneration instruction to the edge node, enabling the edge node to regenerate an archive delivery document that matches the geological archive retrieval request based on the target generated prescription chain version.

[0048] In this embodiment S4, the regeneration instruction is a set of instructions generated by the cloud node based on the target generated prescription chain selected in the archive seed package object. The regeneration instruction carries the version identifier of the generated prescription chain and the corresponding processing step sequence, which is used to drive the regeneration of the archive delivery document based on the target generated prescription chain in the edge node. The archive delivery document is the archive output result obtained by the edge node through processing according to the regeneration instruction. The correction task record is a task record generated by the cloud node and sent to the edge node when the archive seed package object has a life cycle broken state marker. It is used to instruct the edge node to perform correction operations on the processing process associated with the archive seed package object. The data structure of the correction task record specifically includes the target archive seed package object identifier, the target edge node identifier, the correction type identifier, and the trigger reason identifier.

[0049] In embodiment S4, after selecting a target prescription chain based on the lifecycle version index, the cloud node reads the version number and processing step sequence definition of the generated prescription chain, writes the version number into the generated prescription chain version identifier field of the regeneration instruction, and encodes the processing step units arranged in execution order into a processing step sequence field. The processing step sequence field records the step identifier, processing algorithm identifier, input / output data type identifier, and processing parameter set of each processing step unit in sequence. At the same time, the archive identifier, lifecycle version identifier, and call request identifier related to the current geological archive call request are written into the regeneration instruction header to form a complete regeneration instruction data structure. The cloud node sends the regeneration instruction carrying the generated prescription chain version identifier and the corresponding processing step sequence to the target edge node through a pre-established message channel with the target edge node, so as to drive the archive regeneration process to be executed according to the selected version of the generated prescription chain in the edge node.

[0050] In this embodiment S4, after receiving the regeneration instruction, the edge node parses the generated prescription chain version identifier and archive identifier in the regeneration instruction header, loads the generated prescription chain definition corresponding to the version identifier from the local prescription chain cache or cloud synchronization repository, and sequentially schedules the local data processing component to perform processing steps such as data preparation, format conversion, spatial registration, attribute calculation, and layout generation according to the order of the processing step sequence field recorded in the regeneration instruction. During the execution process, according to the input data type identifier recorded in the step unit, the edge node reads the geoscientific semantic base, collected base records, or intermediate result data as input from the data storage area associated with the target archive seed package object. After all processing steps are completed, the edge node obtains structured result data, layout file, and associated metadata. The edge node combines the above results to form the archive output result of this regeneration and registers it as the archive delivery item corresponding to the current geological archive call request. At the same time, the edge node returns the archive delivery item to the upper-level business system or forwards it to the caller through the cloud node to support geological archive query, retrieval, or download.

[0051] In this embodiment S4, when a cloud node determines that a certain archive seed package object has a lifecycle broken state marker, it generates a correction task record. The target archive seed package object identifier in the correction task record is used to uniquely indicate the archive seed package object that needs correction. The target edge node identifier is used to indicate the specific edge node instance responsible for the collection or processing of the archive. The correction type identifier is used to indicate the type of correction operation to be performed, including at least one of collection supplement correction, processing step revision correction, and replay correction based on update-generated prescription chain. The trigger cause identifier is used to record the cause information that caused the lifecycle brokenness, including field types that failed the consistency comparison, node information of unclosed trajectories, or marker information that the regeneration decision is a prohibited result. After the correction task record is sent to the target edge node through the message channel, the edge node selects a predefined correction workflow according to the correction type identifier and performs corresponding supplementary collection, parameter adjustment, or reprocessing operations on the collection process or processing process associated with the target archive seed package object. During the execution process, the trigger cause identifier is used to limit the correction scope and key objects to achieve correction of the processing process.

[0052] Example 2: The present invention proposes a cloud-edge-device collaborative geological archive lifecycle management system, which is applied to the cloud-edge-device collaborative geological archive lifecycle management method proposed in Example 1. It includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to implement the cloud-edge-device collaborative geological archive lifecycle management method in Example 1.

[0053] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the present invention is not limited thereto. Various changes can be made within the scope of knowledge possessed by those skilled in the art without departing from the spirit of the present invention.

Claims

1. A cloud-edge-device collaborative method for the full lifecycle management of geological archives, characterized in that, Includes the following steps: S1. Obtain geological archive data from the edge acquisition nodes, construct a geoscientific semantic base and generate acquisition base records, generate a positive lifecycle trajectory start node based on the acquisition base records, and send the geoscientific semantic base, acquisition base records and positive lifecycle trajectory start node to the edge nodes; S2. In the edge nodes, construct the positive life cycle trajectory based on the starting node of the positive life cycle trajectory, and construct the generation prescription chain including the processing step sequence and the regeneration verification anchor based on the geoscientific semantic base and the collection base record. Encapsulate the geoscientific semantic base, the generation prescription chain and the regeneration verification anchor to form an archive seed package object. Among them, the forward lifecycle trajectory is a temporal trajectory used to represent the processing stages and their sequential relationships experienced by the archive seed package object among the end-side acquisition nodes, edge nodes, and cloud nodes; the generation prescription chain is an ordered instruction chain obtained by encoding the processing steps required in the geological archive processing process and their execution sequence; the regeneration verification anchor is a set of reference data used to characterize the geological archive corresponding to the archive seed package object in terms of key fields, structural relationships, and statistical characteristics; the archive seed package object is a logical archive unit formed by binding the geoscientific semantic basis, the generation prescription chain, and the regeneration verification anchor around a single geological archive. S3. In the cloud node, a reverse reconstruction trajectory including a reverse processing step sequence is constructed based on the generated prescription chain. The generated prescription chain is called to generate a verification archive delivery. The verification archive delivery is reverse reconstructed based on the reverse reconstruction trajectory to obtain the reconstruction base result. The reconstruction base result is compared with the geoscientific semantic base for consistency. The verification archive delivery is regenerated and the archive seed package object is lifecycle closed verification. The lifecycle state marker is set for the archive seed package object. Among them, the reverse reconstruction trajectory is a chain representation of the processing steps that correspond to the processing steps in the generated prescription chain and are arranged in the opposite direction; the life cycle state marker is a life cycle state indicator field attached to the archive seed package object, specifically including the life cycle closed state and the life cycle broken state. S4. For archive seed package objects in the closed life cycle state, write the archive seed package object into the long-term archive storage unit. When a geological archive retrieval request is received, select the target according to the archive seed package object to generate a prescription chain construction regeneration instruction. The edge node then regenerates the archive delivery document according to the regeneration instruction. For archive seed package objects in the broken life cycle state, generate a correction task record and send it to the edge node.

2. The cloud-edge-device collaborative geological archive full lifecycle management method according to claim 1, characterized in that: In S2, the starting node of the forward lifecycle trajectory is a lifecycle node generated at the edge acquisition node and used to identify the starting position of the forward lifecycle trajectory. The starting node of the forward lifecycle trajectory includes the time information of the acquisition base record, the identifier of the edge acquisition node, and the status information of the acquisition base record. The forward lifecycle trajectory is a trajectory object composed of multiple lifecycle nodes arranged in the order of processing time. It is used to represent the processing stages that the archive seed package object goes through in sequence between the edge acquisition node, the edge node, and the cloud node, and their sequential relationship. It is also used to record the processing path and state evolution order of the archive seed package object throughout its entire lifecycle. The structural features of the forward lifecycle trajectory are: each lifecycle node includes a node type field, a timestamp field, an operation type identifier field, and a data status identifier field.

3. The cloud-edge-device collaborative geological archive full lifecycle management method according to claim 2, characterized in that: In S2, the generated prescription chain uses the geoscientific semantic basis and the collected basis records as input range, and is also used to constrain the processing flow executed by the end-side collection nodes, edge nodes, and cloud nodes when generating archive deliverables. The generated prescription chain includes a sequence of processing steps consisting of multiple processing step units. Each processing step unit includes a step identifier field, an input data type identifier field, an output data type identifier field, and a processing algorithm identifier field. The processing step units in the processing step sequence establish a reference relationship between the predecessor steps and the successor steps according to a preset execution order, which is used to limit the execution dependency relationship between each processing step.

4. The cloud-edge-device collaborative geological archive full lifecycle management method according to claim 3, characterized in that: In S2, the regeneration verification anchor is a set of reference data extracted from geological archive data and intermediate processing results based on the geoscientific semantic basis and the generated prescription chain. It is used to verify the verification archive deliverables and to provide a reference benchmark when comparing the archive deliverables for consistency. The data structure of the regeneration verification anchor includes a set of key field values, a set of structural relationship descriptions, and a set of statistical feature vectors. The archive seed package object is a logical archive unit formed by binding the geoscientific semantic basis, the generated prescription chain, and the regeneration verification anchor around the geological archive data according to a preset encapsulation format. It is used as the unique lifecycle management object of the corresponding geological archive and the basic object driving the regeneration of the verification archive deliverables and the lifecycle closure verification during the cloud-edge-device collaborative processing.

5. The cloud-edge-device collaborative geological archive full lifecycle management method according to claim 4, characterized in that: In S3, the reverse reconstruction trajectory is used to reverse reconstruct the verification file deliverable in the cloud node to recover the reconstruction base result, and is also used to map the processing steps in the generated prescription chain according to the mapping rules; wherein, the mapping rules of the reverse reconstruction trajectory are as follows: each processing step in the generated prescription chain is pre-configured with a corresponding reverse processing step and an equivalent reconstruction rule, the reverse reconstruction trajectory arranges each reverse processing step in reverse order according to the processing steps in the generated prescription chain, and when performing reverse reconstruction on the verification file deliverable, each reverse processing step is called in reverse order, and the data flow during the reverse reconstruction process is opposite to the data flow of the corresponding processing step in the generated prescription chain.

6. The cloud-edge-device collaborative geological archive full lifecycle management method according to claim 5, characterized in that: In S3, the verified archive deliverable is an instance of an archive deliverable generated based on the generated prescription chain with the geoscientific semantic base and the collected base records as input. It is used as the current archive object for performing reverse reconstruction and consistency comparison in the cloud node. The reconstructed base result is the base layer data representation obtained by performing reverse reconstruction on the verified archive deliverable based on the reverse reconstruction trajectory. It is used to participate in consistency comparison in the same representation space as the geoscientific semantic base. The consistency comparison between the reconstructed base result and the geoscientific semantic base involves comparing the reconstructed base result with the corresponding spatial range field, temporal range field, geological object identification field, and key semantic field in the geoscientific semantic base.

7. The cloud-edge-device collaborative geological archive full lifecycle management method according to claim 6, characterized in that: In S3, the lifecycle closure verification of the archive seed package object is implemented based on the lifecycle closure verification condition. Specifically, the lifecycle closure verification condition is as follows: when the reconstructed base result and the geoscientific semantic base satisfy the consistency comparison rule on all fields involved in the comparison, and the starting node of the forward lifecycle trajectory and the termination state corresponding to the reverse reconstruction trajectory point to the same acquisition base record, the archive seed package object is determined to be in a lifecycle closed state; otherwise, the archive seed package object is determined to be in a lifecycle broken state. The regeneration adjudication of the verified archive deliverable is based on the consistency comparison result and the reference data contained in the regeneration verification anchor to determine the regeneration adjudication result of the verified archive deliverable, and different regeneration processing operations are performed according to the regeneration adjudication result. The regeneration adjudication result includes a valid regeneration result, a result that needs to be regenerated, and a result that is prohibited from use.

8. The cloud-edge-device collaborative geological archive full lifecycle management method according to claim 7, characterized in that: In step S4, the long-term archive storage unit is an archive storage resource pool used for long-term storage of archive seed package objects in the closed life cycle state. During the process of writing the archive seed package object into the long-term archive storage unit, a life cycle version index is also constructed based on the forward life cycle trajectory and reverse reconstruction trajectory corresponding to the archive seed package object, and the life cycle version index is stored in the long-term archive storage unit in a one-to-one correspondence with the archive seed package object. The life cycle version index includes a life cycle node identifier set, a verification round identifier, and a generated prescription chain version identifier.

9. A cloud-edge-device collaborative method for the full lifecycle management of geological archives according to claim 8, characterized in that: In S4, the regeneration instruction is a set of instructions generated by the cloud node based on the target generated prescription chain selected in the archive seed package object. The regeneration instruction carries the version identifier of the generated prescription chain and the corresponding processing step sequence, which is used to drive the regeneration of the archive delivery document in the edge node based on the target generated prescription chain. The archive delivery document is the archive output result obtained by the edge node according to the regeneration instruction. The correction task record is a task record generated by the cloud node and sent to the edge node when the archive seed package object has a life cycle broken state mark. It is used to instruct the edge node to perform correction operation on the processing process associated with the archive seed package object. The data structure of the correction task record specifically includes the target archive seed package object identifier, the target edge node identifier, the correction type identifier, and the trigger reason identifier.

10. A cloud-edge-device collaborative geological archive lifecycle management system, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: The processor executes a computer program to implement the cloud-edge-device collaborative geological archive full lifecycle management method as described in any one of claims 1-9.

Images