A multi-party participation automatic settlement method and system based on a blockchain

Abstract

The present application relates to the technical field of blockchain settlement, in particular to a multi-party participation automatic settlement method and system based on blockchain, comprising the following steps: acquiring multi-party node account records, identifying the relationship between the path and the account period field, comparing the field sequence, screening the releasable path, appending the control field, excluding the duplicate state, positioning the unused field, writing the account period settlement state field, and obtaining the account book synchronization result. In the present application, the order of the account period field in the path structure is processed, the multi-node account information is associated, the path behavior is limited through the corresponding relationship between the permission field and the identity field, the state usage range is constrained by appending the control field in the path, the used path records are excluded through the state field screening, the account book writing is completed by the settlement field and the state field according to the structure position, the path control range is limited, the account period behavior can be scheduled in segments in the multi-party participation scenario, and the state content maintains the structure differentiation in the chain writing process.

Description

Technical Field

[0001] This invention relates to the field of blockchain settlement technology, and in particular to a blockchain-based multi-party automatic settlement method and system. Background Technology

[0002] The blockchain settlement technology field encompasses transaction data recording and value transfer mechanisms based on decentralized ledgers. Its core components include maintaining ledger consistency through a distributed node network, ensuring data immutability and traceability through encryption algorithms, and guaranteeing the security and reliability of transaction confirmation and verification processes through consensus mechanisms. This technology is widely applied in various scenarios such as financial payments, supply chain collaboration, and asset transfer, offering advantages such as improved information transparency, simplified operational processes, and enhanced collaboration efficiency. In blockchain settlement scenarios, data synchronization, multi-party trust mechanisms, and automated accounting capabilities are key components. Multi-party data access, transaction verification mechanisms, and settlement logic modeling collectively construct a complete settlement system.

[0003] Among them, the blockchain-based multi-party automatic settlement method refers to a method that, under a pre-defined distributed ledger structure, addresses the participation conditions of multiple parties by defining participant identity identifiers and access control rules, combining programmable rules to set up participation processes, and writing the receivables and payable information of different participants in specific transaction behaviors into the blockchain in structured data form. Data consistency is verified by encryption using a hash function, and settlement logic is initiated through pre-set trigger conditions, calling pre-stored records in the distributed ledger for account matching and clearing operations. This method mainly covers identity trust modeling, transaction data format standardization, automatic settlement trigger mechanism setting, and ledger data consistency verification processing, using pre-programmed logic contracts and inter-node state synchronization mechanisms to jointly complete the above processes.

[0004] Existing technologies lack a mechanism for corresponding the order of path fields during multi-node settlement processing. Settlement fields lack a basis for identifying their positional relationship in different paths. Permission fields and status fields are not associated with control elements in the path structure, resulting in permission judgments failing to reflect path constraints. There is a lack of pre-screening methods to determine whether path statuses are reused in the ledger. Status writing lacks field placement constraints, and there may be issues such as path status rewriting or gaps in settlement fields in the ledger. Under conditions of concurrent writing by transaction nodes, path control failure causes state boundary confusion, settlement logic imbalance, and difficulty in maintaining the consistency of path settlement order during data propagation on-chain. Summary of the Invention

[0005] To address the technical problems existing in the prior art, this invention provides a blockchain-based multi-party automatic settlement method, comprising the following steps:

[0006] To achieve the above objectives, the present invention adopts the following technical solution: a blockchain-based multi-party automatic settlement method, comprising the following steps:

[0007] S1: Obtain the account writing records of multiple participating nodes, identify the combination relationship between path field and account period field, extract the account period field according to the node source, and compare the field content according to the path sorting and field position relationship to obtain the account period path cross field sequence;

[0008] S2: Based on the field content in the cross-field sequence of the billing period path, align the identity field and the permission field, analyze the triggering mechanism in the permission field, match the path field content, and obtain the set of paths for which permissions can be released;

[0009] S3: Based on the path field and permission field in the set of releasable permission paths, map the permission field to the billing period field, arrange the fields in the order of the path, and add the settlement control field to the path to obtain a list of write paths with control fields;

[0010] S4: Based on the list of write paths with control fields, analyze the content of the path status field, identify the field indexes that have been recorded in the ledger, filter out unoccupied path records, and obtain a list of ledger paths that can be synchronized.

[0011] S5: Based on the path records in the synchronizeable ledger path list, expand the account period field content, and write the settlement field and status field into the ledger according to their positions to obtain the settlement status written field set.

[0012] As a further embodiment of the present invention, the billing period path cross-field sequence includes path sorting information, billing period field position, and field corresponding position relationship; the set of releasable permission paths includes path fields, permission fields, and trigger condition matching content; the write path list with control fields includes path field order, permission field order, billing period field arrangement, and settlement control field; the synchronizeable ledger path list includes unoccupied path records, synchronization status data, and ledger status field index; and the settlement status write field set includes billing period field segmentation, settlement field, status field, and path structure mapping position.

[0013] As a further aspect of the present invention, the content of the matching path field refers to comparing the order of the path field and the permission field, analyzing the triggering mechanism in the path permission field, and identifying whether the path field has permission release capability.

[0014] The mapping permission field associated with the billing period field refers to the permission field appearing in the matching path field and the billing period field that is structurally associated with it.

[0015] As a further aspect of the present invention, adding a settlement control field to the path refers to adding control field information to the path structure based on the billing period span information associated with each path field;

[0016] The analysis of the path status field content refers to identifying the status field content in the path structure, comparing the status fields one by one according to the arrangement order of the fields in the path structure, and analyzing the embedding position in the path field based on the position association analysis.

[0017] As a further aspect of the present invention, the specific steps of S1 are as follows:

[0018] S101: Obtain the account writing records of multiple participating nodes, identify the pairing relationship between the path field and the account period identifier field in each record, record the path field content according to the account source node, locate the account period field in the path field, and obtain the node account period path field set;

[0019] S102: Based on the set of node billing period path fields, the order of the path fields is compared with the position index of the billing period fields, and the corresponding positions of the billing period fields are summarized in the path group to obtain the billing period field order mapping list.

[0020] S103: Based on the order mapping list of the payment period fields, according to the arrangement position information of the path fields in the accounting data, list the combination of payment period field positions in the path according to the order of field appearance, and obtain the payment period path intersection field sequence.

[0021] As a further aspect of the present invention, the specific steps of S2 are as follows:

[0022] S201: Based on the field content in the cross-field sequence of the billing period path, compare the node identity field and the path permission field according to the path sorting sequence, and match the positions according to the arrangement order in the path segment where the fields are located to obtain the field position matching result;

[0023] S202: Based on the field position pairing result, calculate the field value offset between the node identity field and the path permission field, and compare it according to the field arrangement order of the corresponding position in the path segment to obtain the field offset result;

[0024] S203: Based on the field offset result, locate the trigger value content in the path permission field, analyze its consistency with the field value set in the path field, and obtain the set of paths for which permissions can be released.

[0025] As a further aspect of the present invention, the specific steps of S3 are as follows:

[0026] S301: Based on the path field and corresponding permission field in the set of releasable permission paths, call the pairing relationship between the path field and the permission field, align the billing period field information associated with the permission field with the corresponding path field, retain the corresponding order between the fields, and obtain the path billing period field alignment details;

[0027] S302: Based on the alignment details of the path billing period field, calculate the span value of the path field in the billing period dimension according to the billing period field value associated with each path field, identify the number of consecutive billing periods covered in the billing period field value, associate the number with the corresponding path field, and obtain the path billing period span.

[0028] S303: Based on the path billing period span, call the corresponding permission field and billing period field information in the path field, match the settlement control field value of the path field, append the matching results to the path data one by one according to the path field information, filter the path information including field content, and obtain a list of write paths with control fields.

[0029] As a further aspect of the present invention, the specific steps of S4 are as follows:

[0030] S401: Based on the write path list with control fields, analyze the status field information field values ​​in the path structure, associate the corresponding status field in each path field with the path field position, and obtain the path status field information table according to the corresponding position of the path field.

[0031] S402: Based on the path status field information table, compare the status field index field value in the ledger record, identify the case where the status field value in the path field does not appear in the ledger field, partition the path field according to the status field missing situation, and obtain a path status field missing list.

[0032] S403: Based on the list of missing path status fields, add synchronization status data to the corresponding status field positions of the path fields, append the status field values ​​to the original path field information, and analyze the field integrity to obtain a list of synchronizeable ledger paths.

[0033] As a further aspect of the present invention, the specific steps of S5 are as follows:

[0034] S501: Based on the path record content in the synchronizeable ledger path list, locate the billing period field, settlement field and status field in the path structure, analyze the fields by field type according to the correspondence between field name and field position, and obtain the path field classification results;

[0035] S502: Based on the path field classification results, expand the billing period field in order of field value, divide the billing period field segment in each path record, and analyze the billing period coverage of each path field segment according to the start and end values ​​of the billing period field to obtain the billing period field segment.

[0036] S503: Based on the payment period field segment, fill the settlement field and status field in the path field into the corresponding payment period segment position, and write them according to the order of the fields in the path to obtain the settlement status writing field set.

[0037] A blockchain-based multi-party automated settlement system includes:

[0038] The path structure extraction module obtains the account writing records of nodes with multiple participants, identifies the combination relationship between path fields and payment period fields, calls the payment period field according to the node source, and reads the field correspondence within the path group according to the path sorting information to obtain the payment period path cross field sequence.

[0039] The permission path filtering module aligns the node identity field with the path permission field based on the billing period path cross field sequence, and filters path records with consistent field values ​​according to the trigger conditions to obtain a set of paths for which permissions can be released.

[0040] The settlement control labeling module identifies the billing period fields associated with the permission fields based on the set of releasable permission paths, arranges the associated fields in the order of the paths, adds settlement control fields to the paths, excludes duplicate records, and obtains a list of write paths with control fields.

[0041] The ledger synchronization verification module checks the status fields in the paths based on the list of write paths with control fields, identifies the field indexes that already exist in the ledger records, filters out paths that have not been recorded and used, and obtains a list of ledger paths that can be synchronized.

[0042] The settlement status writing module reads the payment period, settlement and status fields of each path based on the synchronizeable ledger path list, expands the payment period field into data segments, and writes the path data according to the field position to obtain the settlement status writing field set.

[0043] Compared with the prior art, the advantages and positive effects of the present invention are as follows:

[0044] In this invention, the order of the billing period field in the path structure is processed to associate the account information of multiple nodes. The correspondence between the permission field and the identity field restricts the path behavior. Control fields are added to the path to constrain the scope of state usage. The state field is used to screen and exclude path records that have already been used. The settlement field and the state field are written to the ledger according to the structural position. The scope of path control is limited. The billing period behavior can be segmented and scheduled in scenarios with multiple parties. The state content maintains structural differentiation during the on-chain writing process. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0046] Figure 1 This is a schematic diagram of the steps of the present invention;

[0047] Figure 2 This is a detailed schematic diagram of S1 of the present invention;

[0048] Figure 3 This is a detailed schematic diagram of S2 of the present invention;

[0049] Figure 4 This is a detailed schematic diagram of S3 of the present invention;

[0050] Figure 5 This is a detailed schematic diagram of S4 of the present invention;

[0051] Figure 6 This is a detailed schematic diagram of S5 of the present invention;

[0052] Figure 7 This is a system module diagram of the present invention. Detailed Implementation

[0053] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0054] In embodiments of the present invention, words such as "exemplarily," "for example," etc., are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" in the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present the concept in a concrete manner. Furthermore, in embodiments of the present invention, the meaning expressed by "and / or" can be both, or either one.

[0055] In the embodiments of this invention, the terms "image" and "picture" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning. Similarly, the terms "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning.

[0056] In this embodiment of the invention, sometimes a subscript such as W1 may be written in a non-subscript form such as W1. When the difference is not emphasized, the meaning they express is the same.

[0057] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0058] Please see Figure 1 This invention provides a blockchain-based multi-party automatic settlement method, comprising the following steps:

[0059] S1: Obtain the account writing records of multiple participating nodes, identify the combined content between the path field and the account period identifier field, extract the account period field appearing in the path field according to the node source, and obtain the account period path cross field sequence according to the path sorting information and the position of the account period field in each path group, and according to the position comparison field corresponding position relationship in the path group.

[0060] S2: Based on the field content in the cross-field sequence of the billing period path, extract the corresponding node identity field and path permission field, align the identity field and permission field, analyze the triggering mechanism in the path permission field, match the content corresponding to the path field, and obtain the set of paths with releasable permissions.

[0061] S3: Based on the path fields and corresponding permission fields in the set of releasable permission paths, map the billing period fields associated with the permission fields, arrange the permission fields and billing period field information in the order of the paths, and append the settlement control field content to the corresponding path information to obtain a list of write paths with control fields.

[0062] S4: Based on the list of write paths with control fields, analyze the status field information in the path structure, match the existing status field index in the ledger record, filter the currently unoccupied path records according to the difference between the path field and the ledger field content, import the synchronization status data content, and obtain the list of synchronizeable ledger paths.

[0063] S5: Based on the path record content in the synchronized ledger path list, extract the accounting period field, settlement field and status field of the path, expand the accounting period field into data segments in sequence, and write the path content into the segment according to the corresponding position of the ledger field in the path structure to obtain the settlement status written field set.

[0064] The cross-field sequence of billing period paths includes path sorting information, billing period field position, and field corresponding position relationship. The set of paths with releaseable permissions includes path fields, permission fields, and trigger condition matching content. The list of write paths with control fields includes path field order, permission field order, billing period field arrangement, and settlement control fields. The list of synchronized ledger paths includes unused path records, synchronization status data, and ledger status field index. The set of settlement status write fields includes billing period field segmentation, settlement field, status field, and path structure mapping position.

[0065] Please see Figure 2 The specific steps of S1 are as follows:

[0066] S101: Obtain the account writing records of multiple participating nodes, identify the pairing relationship between the path field and the account period identifier field in each record, record the path field content according to the account source node, locate the account period field in the path field, and obtain the node account period path field set;

[0067] First, a head-to-tail scan is performed based on the field structure. The path field is checked to see if there are any fields with the same format as the payment period identifier field. If the path field is "Cost / Sales / Code X" and the payment period field is "Code X", then the payment period field is embedded in the path field. In this case, the field's hierarchical position in the path can be identified by segmenting the data. If the path field is "Revenue / Region A / Code Y" and the payment period field is "Code Y", then the correspondence is at the third level. After identification, this corresponding information is marked as paired. If the path field in a record does not match the payment period field, it should not be included in the current processing. The payment period is matched with the data, and then the data is categorized according to its source. That is, the data is assigned to the node dimension according to the node that generated it. In this process, the node division can be performed by grouping the data based on the source identifier field. For example, records from node N1 are assigned to the N1 category pool. Then, the position of the payment period field is found in the path field of each node. An index operation is performed on each segment of the path field. If a segment of the content is consistent with the payment period field, its hierarchical position is recorded to form a list of corresponding positions between the path field and the payment period field. Finally, the records under each node that have the matching relationship between the path field and the payment period identifier field are merged into a unified data structure to obtain the node payment period path field set.

[0068] S102: Based on the set of node billing period path fields, the order of the path fields is compared with the position index of the billing period fields, and the corresponding positions of the billing period fields are summarized in the path group to obtain the billing period field order mapping list.

[0069] First, each level of paragraph in the path field is retrieved and numbered sequentially. A sorted sequence is formed by numbering each path field from left to right. Simultaneously, the specific location of the payment period field within the path field is extracted, and its relative index value within the path number is obtained. This forms the basis for comparing the path field sequence with the payment period field index. In practice, for example, if a path field is "Cost / Production / Code P" and the payment period field is "Code P", the sorted sequence is 1 to 3, corresponding to an payment period field index of 3. If another path field is "Management / Code Q / Process" and the payment period field is "Code Q", the sorted sequence is still 1 to 3, corresponding to an payment period field index of 2. A comparison operation needs to be performed item by item across multiple path fields to confirm whether the payment period field is correct. If the position of the payment period field differs across path fields, it should be grouped and organized, with each group corresponding to the same payment period field index value. The group should be categorized and numbered according to the original source of the path field. A unified judgment standard is required during this process. The payment period field format is based on a fixed character length, and the encoding must contain only letters or numbers, prohibiting spaces, symbols, and other interfering characters. After identifying the position of the payment period field, the hierarchical position of the payment period field in the path field can be obtained by comparing the relative relationship between the sorting number and the index position. This position result is then mapped to the node source. Finally, the hierarchical position of the payment period field in each path field is summarized, and this hierarchical value is aggregated according to the path number order to obtain the payment period field sequence mapping list.

[0070] S103: Based on the order mapping list of payment period fields, according to the arrangement position information of path fields in the accounting data, list the combination of payment period field positions in the path according to the order of field appearance, and obtain the payment period path intersection field sequence.

[0071] First, it's necessary to locate the sequential number of each path field in the accounting data record. For example, a path field might be "Purchasing / Materials / Section A / Period K," where "Period K" is the payment period field. Its position in the path is the 4th segment, and it ranks 5th in the overall field order of the accounting data. The position of the payment period field in the path can be confirmed by reading the corresponding index values ​​of the path field and the payment period field. Then, a field order aggregation operation is performed on all path fields to extract the relative position of the payment period field in the path field sequence, forming a continuous numbering sequence. Finally, based on the path field's corresponding position in the accounting data, sequential numbering is used to sort the fields. If a path field is ranked 3rd in the accounting field position, and its payment period field is in the 2nd segment of the path, then the path number is 3, and the payment period field is 5th. Position 2 forms the combination result "3-2". After performing this operation on multiple path fields, position combinations such as "4-3" and "5-2" are obtained respectively. These combination values ​​are further listed in the order of the path to obtain the cross sequence between the path field and the payment period field. Throughout the process, the payment period field must appear inside the path field structure and cannot be an independent field outside the path. The path field must have a splittable hierarchical structure. After being split by a slash or other delimiter, each segment must have a unique meaning and there cannot be duplicate names or empty segments. During the combination process, the content matching between the path field and the payment period field is not performed. Only the position classification of the payment period field is performed on the structure inside the path. Finally, the sequence set formed by the combination of path order and payment period position is obtained to obtain the payment period path cross field sequence.

[0072] Please see Figure 3 The specific steps of S2 are as follows:

[0073] S201: Based on the field content in the cross-field sequence of the billing period path, compare the node identity field and the path permission field according to the path sorting sequence, and match the positions according to the arrangement order in the path segment where the field is located to obtain the field position matching result;

[0074] First, the paragraphs in each path field need to be numbered hierarchically, assigning paragraph position identifiers from left to right. For example, a path field "Unit / Project / Payment Period / Amount" can be numbered from paragraph 1 to paragraph 4, and its payment period field has already been identified as paragraph 3 in the cross-field sequence. This path field structure is then used as the basis for pairing. Based on this, node identity fields and path permission fields are introduced to participate in the pairing operation. Node identity fields are typically organization, department, or role-based codes, such as "N1", "N2", and "N3". Path permission fields are control fields that limit the scope of a field, such as "read", "write", and "control". These two types of fields are assigned numbers respectively. For example, if the node identity field is "N2", the permission field is "write", and the path field is "Region / N2 / Payment Period / Write", then the node identity field and permission field are located in paragraph 2 and paragraph 4 respectively. Further, the paragraph number is compared horizontally with the position of the payment period field in paragraph 3 to record each path. The order of the three elements in the field is crucial during operation. For example, in a path field "Subject / N1 / Account Period / Read", the node field "N1" is the second segment, the account period field is the third segment, and the permission field is the fourth segment, with a path sorting sequence of 2-3-4. In another record, the path field "Budget / Account Period / N2 / Write" has the node field "N2" as the third segment, the account period field as the second segment, and the permission field as the fourth segment, with a sorting sequence of 3-2-4. By comparing the above sorting numbers with the actual field values ​​in the path segment positions, the relative positional relationship between the node identity field and the path permission field and the account period field in the path field can be located, and their alignment can be recorded. For example, whether there are structural differences such as overlap, interlacing, or empty segment insertion between the node field and the account period field. Based on the above position information comparison results, a segment pairing list of the node field, permission field, and account period field in the path field structure is formed. Finally, the comparison relationships in each path field are summarized to obtain the field position pairing results.

[0075] S202: Based on the field position pairing results, calculate the field value offset between the node identity field and the path permission field, and compare it according to the field arrangement order of the corresponding positions in the path segment to obtain the field offset result;

[0076] The formula for calculating the offset between the node identity field and the path permission field is as follows:

[0077] ;

[0078] in, Representing the The field value offset between the identity field and the path permission field of a path node. The path permission field represents the first position in the path segment. The current position index value of each field. The node identity field is the first in the path segment. The target alignment index value for each field The first field representing the node's identity The average position value of the item in the path. The field representing path permissions. The average position value of the item across multiple paths. The first field representing the node's identity The mean index of the frequency of an item in a path segment. The field representing path permissions. The mean index of the frequency of an item in a path segment. The first in the path record Keyness coefficients of the item field Representing the The minimum field spacing between the path field and the permission field in the mapping of a path record;

[0079] Parameter acquisition method and value source:

[0080] : Directly locate the index of the field in the path sequence from the path record structure;

[0081] : Determined by matching the path segment field mapping table with the node field;

[0082] , : Calculate the arithmetic mean of the index positions of the fields in 10 paths;

[0083] , : Count the number of times the node field and the permission field appear in the path structure respectively;

[0084] Density function estimation based on field matching success rate, taking the 95% confidence mean in the confidence interval (0.7, 0.9);

[0085] : The sum of the absolute values ​​of the differences between the positions of nodes and the permission fields within each path in the path set;

[0086] : The minimum nearest distance between the node field and the permission field across all samples;

[0087] Numerical substitution and result explanation:

[0088] Substitute the obtained parameter values ​​into the formula:

[0089] ;

[0090] Calculation in progress:

[0091] ;

[0092] ;

[0093] ;

[0094] ;

[0095] ;

[0096] Interpretation of results and numerical significance:

[0097] The results show that the field value offset between the path permission field and the node identity field in the path structure is 0.7496, which can be used to quantify the degree of consistency of field mapping in the structure alignment determination.

[0098] Explanation of the innovative aspects of the formula:

[0099] The advantage of the formula lies in the introduction of... , , , Based on parameters derived from path structure location frequency statistics, the structural differences between the node identity field and the path permission field in the current path segment are coupled. Furthermore, in constructing the field offset index The system forms a multi-factor weighted fusion, and through square superposition, square root and proportional normalization operations, it can reflect the coupling effect between structural shift, frequency difference and behavioral mapping distribution.

[0100] S203: Based on the field offset results, locate the trigger value content in the path permission field, analyze its consistency with the field values ​​already set in the path field, and obtain the set of paths for which permissions can be released.

[0101] First, extract the field position and corresponding field value of each path permission field from the existing field position offset data. Combine this with the value settings in the original path field configuration, and compare the trigger field. First, split the field offset results, extracting the offset value of the path permission field relative to the base field position and the corresponding field value for each record. Assuming the offset value of the path permission field is 2, it means that the field is located in the 3rd segment of the path field structure. Then, read the field value at that position. If it is "writable," then this field value is set as the trigger condition. Simultaneously, obtain the currently set field value from the original field segment set in the path field. For example, if the path field is configured as "Unit / Business / Writable / Account Period," the third segment is the permission field, and its original setting value is also "writable." At this point, it can be considered that the field value is completely consistent with the setting value in the path field, and continue processing other records. If the offset value field in a certain record is "read-only," while the path field... If a position in the segment settings was originally set to "writable", it is considered inconsistent. During this process, all path fields must be matched one by one. The offset field value is compared with the path setting field value at the content level. Standard character comparison rules are allowed, such as all letters, letters and numbers, etc. Fuzzy matching strategies are prohibited. When comparing field values, the field content length must be consistent, and there cannot be prefixes or suffixes. At the same time, the field content must use standard encoding, and non-standard characters or empty segments are not allowed. Once a field value is found to be consistent with the path setting content during the field matching process, the path is included in the releasable item. If there are multiple permission field setting positions in the path field, the field values ​​of each position must be compared one by one. Only paths that all match can be included in the next round of processing. After completing the correspondence verification of all path permission fields and setting field values, the set of paths with consistent field values ​​is filtered out to obtain the set of releasable permission paths.

[0102] Please see Figure 4 The specific steps of S3 are as follows:

[0103] S301: Based on the path field and corresponding permission field in the set of releasable permission paths, call the pairing relationship between the path field and the permission field, align the billing period field information associated with the permission field with the corresponding path field, retain the corresponding order between the fields, and obtain the path billing period field alignment details;

[0104] First, process each path field segment by segment, breaking it down into paragraphs according to delimiters. For example, if the path field is "Finance Department / Budget / Issuance Authority", it contains three field segments, numbered 1 to 3. The corresponding authority field is "Issuance Authority". By comparing the actual position of this authority field within the path field, we can determine that it is located in the 3rd segment of the path. Next, we call the pairing relationship table between path fields and authority fields to identify the corresponding billing period field for each record. For example, the billing period field corresponding to the authority field "Issuance Authority" is "Q3", and the billing period field corresponding to the other authority field "Approval Authority" is "Q2". We need to establish a direct mapping between the authority field and the billing period field. Then, based on the position information of the authority field in the path field, we align the billing period field with the structure of the corresponding path field. During the alignment process, we must maintain the corresponding segment of the path field and the billing period field. To ensure consistency, if the permission field is in the third segment of the path field, the payment period field must also be inserted in the third segment for alignment. In this case, the path field can be considered as "Finance Department / Budget / Q3". If the permission field is in the second segment of the path field, the payment period field must be arranged in the second segment. Then, the content of the payment period field is inserted into the original path field structure. By comparing the field sequence of the path field after insertion, the association relationship between the permission field and the payment period field is confirmed, and their corresponding segment number is marked. When processing multiple path fields, they must be uniformly numbered according to the path order, and the segment consistency of the field content of all path fields must be checked to ensure that the pairing rules of the permission field and the payment period field in the path structure are consistent. If the permission field or the payment period field is missing in the path field of a certain record, the record should not be processed temporarily to avoid data mismatch. After processing, the alignment results of all path fields and payment period fields are output to obtain the path payment period field alignment details.

[0105] S302: Align details based on path billing period field. Calculate the span value of the path field in the billing period dimension according to the billing period field value associated with each path field. Identify the number of consecutive billing periods covered by the billing period field value, associate the number with the corresponding path field, and obtain the path billing period span.

[0106] The formula for calculating the span value of the path field in the billing cycle dimension is as follows:

[0107] ;

[0108] in, Representing the The span value of the path field in the billing cycle. Representing the The first path field The weighted factor for changes in the payment period corresponding to each payment period field value. Representing the The first path field The payment period index number corresponding to each payment period field value Representing the The arithmetic mean of the billing period index numbers included in the path field. Representing the Inter-period adjustment deviation coefficient for the path field, Representing the The maximum value in the billing period index number of the path field. Representing the The minimum value in the billing period index number of the path field. Representing the The median of the billing cycle index numbers included in the path field. Representing the The payment period fluctuation adjustment factor for the path field. Representing the The number of billing period field values ​​included under the path field;

[0109] No. The set of path field billing period index numbers is as follows:

[0110] = , = , = ;

[0111] , , ;

[0112] The values ​​are consistent with the monitoring data, which shows a weighted adjustment range of 0.5-1.5.

[0113] Arithmetic Mean ;

[0114] median ;

[0115] Maximum and minimum number , ;

[0116] If the maximum period frequency is 20 times and the minimum period frequency is 5 times, the frequency ratio is 20 / 5 = 4. ;

[0117] Fluctuation balance adjustment factor By the total amount of payment period offset;

[0118] ;

[0119] ;

[0120] Therefore ;

[0121] Sample size ;

[0122] Substituting the above parameters into the formula yields:

[0123] ;

[0124] Calculation steps:

[0125] Molecular weighted bias sum:

[0126] ;

[0127] ;

[0128] ;

[0129] Inter-period adjustment items:

[0130] Molecular as a whole:

[0131] Denominator root:

[0132] After absolute value:

[0133] Interpretation of results and numerical significance: The result is compared with the baseline range of 0.05-0.20. It is within the range, indicating that the path payment period span value is normal. The corresponding result value in step 3 is 0.1074.

[0134] Explanation of the innovative aspects of the formula:

[0135] The advantage of the formula lies in the introduction of a weighting factor for changes in payment terms. Inter-period adjustment deviation coefficient Balance adjustment factor with payment period fluctuations The multiple combinations not only quantify the concentration, extreme fluctuation range and deviation from the average value of the account period value within the path field, but also introduce a coordinated comparison of amplitude and dispersion between the numerator and denominator, thereby dynamically calibrating the path account period span value from multiple angles.

[0136] S303: Based on the path billing period span, call the corresponding permission field and billing period field information in the path field, match the settlement control field value of the path field, append the matching results to the path data one by one according to the path field information, filter the path information including field content, and obtain a list of write paths with control fields;

[0137] First, the path field is read and processed in conjunction with its corresponding permission and payment period fields. The structure of the path field and its corresponding payment period span are determined first. For example, in the path field "Region / Project / Quarter 1", the payment period span is set to 1, indicating a single-segment structure between the permission and payment period fields under this path. The permission field content is then identified, such as "Write" for the permission field and "Quarter 1" for the payment period field. Next, the preset settlement control field information in the path field is extracted, such as "Approved". Then, the permission and payment period fields in the current path field are used as matching references. All path field records are read sequentially, and a field value comparison operation is performed on the settlement control fields. This means determining whether the settlement control field in the current record matches the reference field. For example, if the control field in the path "Region A / Project X / Quarter 1" is "Approved", and the reference field is also "Approved", then the record can be marked as a successful match. Continue processing other records. If a path field is "Region B / Project Y / Quarter 2", the control field is "Pending Review", and the reference field is "Approved", it is marked as a failed match. Throughout the matching process, the order of path fields and permission fields must be kept consistent to avoid misalignment affecting matching accuracy. At the same time, the matching operation should be performed one by one according to the original data arrangement of the path fields, without skipping segments or cross-comparison. After the matching is completed, the field values ​​of the successfully matched fields are appended to the end of the original path field record, and the matching status field is marked in the record. Then, all path records with a matching status field of "Pass" are filtered out. The filtering must include the complete content of the permission field, billing period field, and control field. If a record has missing fields or abnormal structure, it should be excluded and not included in the filtering summary. Finally, the path field information that meets the above conditions is aggregated to form a list, resulting in a list of write paths with control fields.

[0138] Please see Figure 5 The specific steps of S4 are as follows:

[0139] S401: Based on the list of write paths with control fields, analyze the status field information field values ​​in the path structure, associate the corresponding status field in each path field with the path field position, and obtain the path status field information table according to the corresponding position of the path field.

[0140] First, extract all field segments contained in the path field structure and break them down hierarchically. For example, if the path field is "Organization / Business / Status / Payment Period", it contains four segments, with "Status" being the status field, located in the third segment. During extraction, each path field needs structural parsing to identify the specific segment position of the status field. If another path field is "Region / Status / Process", the status field is in the second segment. After identifying the status field, continue reading its corresponding field value. For example, if the value of the third segment is "In Effect" or "Frozen", combine the field value with the field position information to form a record of the status field position information corresponding to the path field. Repeat this operation to process all path field records in sequence, ensuring that the status field name and value can be accurately extracted for each path field. In addition to the segment number, in actual use cases, if the path field structure is "Organization / Approval / Status / Plan" and the status field value is "Frozen", then the status field is recorded as being in segment 3 with the value "Frozen". In another path field "Project / Status / Issuance", the status field value is "Completed", then it is recorded as being in segment 2 with the value "Completed". After extraction, the data is uniformly organized according to the path field number, and the status field value and location information are appended to the corresponding item of the original path field number. The field value, field segment, and sequence number of the path field are uniformly displayed in the field information table to ensure that the relative position information of the same status field in different path structures is comparable. Finally, after completing the extraction and location allocation processing of the status fields of all path records, a unified detailed list is generated, resulting in the path status field information table.

[0141] S402: Based on the path status field information table, compare the status field index field values ​​in the ledger records, identify cases where the status field values ​​in the path fields do not appear in the ledger fields, partition the path fields according to the status field missing cases, and obtain a list of missing path status fields.

[0142] First, read all records in the path status field information table. For example, if a path field is "Region A / Approval in Progress / Cycle" and its status field value is "Approval in Progress," located in the second segment, simultaneously read the set of values ​​listed in the status field index of the ledger record. If the set contains "Frozen," "Completed," and "Effective," then it can be determined that "Approval in Progress" does not appear in it, and this record's status field is missing in the ledger. If another path field, "Region B / Frozen / Cycle," has a status field of "Frozen" and appears in the ledger record's field values, then this record's status field can be considered present. During the comparison process, the status field value comparison should be limited to a full field consistency match, meaning that character length, order, symbols, and capitalization must be completely identical, and there should be no variations or abbreviations. At the same time, the path field structure... The structure should maintain consistency in its decomposition to avoid mismatches caused by misalignment of status field segment positions. After performing a ledger comparison of all path status field records, records that fail to match are processed centrally. This involves extracting path fields whose status field values ​​are not present in the ledger and differentiating these path fields according to the status field missing status. They can be archived by status field value, such as "missing - under approval" or "missing - pending review". Alternatively, they can be partitioned by status segment number after being split by the path field structure, distributing the missing records in different structural segments to form a missing statistics under the structural dimension. At the same time, the original path field number and status segment corresponding to the record are marked. Finally, the missing path information of the above status fields is aggregated and output as a unified result set to obtain a list of missing path status fields.

[0143] S403: Based on the list of missing path status fields, add synchronized status data to the corresponding status field positions of the path fields, append the status field values ​​to the original path field information, and analyze the field integrity to obtain a list of synchronizeable ledger paths.

[0144] First, obtain the structural segment information and missing field segment number for each path in the missing list. For example, if the missing status field in the path "Business / Process / Payment Period" is located in the 2nd segment, then the status field content needs to be added at that position. Select the synchronized status data value "Issued" as the content to be filled. During the insertion process, the original path field structure should remain unchanged, and only the missing positions should be appended in parallel, thus forming the updated path field "Business / Issued / Process / Payment Period". If the original path was "Unit / Payment Period" and the status field segment was the 2nd segment, then the path after filling would become "Unit / Synchronized / Payment Period". This type of operation is applied sequentially to all path records in the missing list. Only one status field value is appended to each record. Multiple values ​​in parallel or duplicate insertions are prohibited. After completing the status value supplementation, the newly added field value is also appended to the missing field. The original path field information is used to form updated path information including status fields. Then, a field integrity analysis is performed on the updated path fields. The integrity analysis needs to focus on the consistency of field quantity and field position. First, each updated path record is segmented and counted to ensure that the number of fields meets the structural integrity requirements. If the total number of field segments after the update of a certain path field is less than the original standard field quantity, the record is considered incomplete and will not be included in the subsequent ledger writing list. Next, it is verified whether the status field is located in the preset segment. If the status field in a record is inserted into a non-standard segment, it is marked as a structural anomaly, and such records will not be included in the synchronization scope. Finally, all path field records with correct field segment count, complete structure, and reasonable status field supplementation position are selected and a unified data list is output to obtain the list of synchronizeable ledger paths.

[0145] Please see Figure 6 The specific steps of S5 are as follows:

[0146] S501: Based on the path record content in the synchronized ledger path list, locate the billing period field, settlement field and status field in the path structure, analyze the fields by field type according to the correspondence between field name and field position, and obtain the path field classification results;

[0147] First, locate the accounting period field. Usually, the accounting period field appears named with "cycle", "quarter", "accounting period", etc., and it is more common to appear in the third or fourth segment of the path field. For example, in the path "organization / department / accounting period / settlement status", "accounting period" is clearly the accounting period field and is located in the 3rd segment. Then, read "settlement status" and identify it as the settlement field, whose naming characteristics include keywords such as "settlement" and "payment", and the field is located in the 4th segment. Next, judge the status field, which may be named "status", "progress", "synchronization status", etc., and the common positions are the 2nd segment or the last segment. If the path field is "business / status / quarter / execution", the status field is "status" and the accounting period field is "quarter", then they are located in the 2nd and 3rd segments respectively. Continue to process other path records. For example, for "block / approval in progress / quarter 4 / complete", then "approval in progress" is the status field, "quarter 4" is the accounting period field, and "complete" is the settlement field. At this time, the status field is in the 2nd segment, the accounting period field is in the 3rd segment, and the settlement field is in the 4th segment. During the whole process, a mapping rule table for field names and types needs to be established to judge the attribution of fuzzy fields. For example, "Q3" is classified as the accounting period field, and "pending review" is classified as the status field. For fields with unclear naming, their categories need to be judged by combining their positions and context fields. If the field value is "settled", even if it is named "processing", it is still classified as the settlement field. Field cross-classification is not allowed during the processing, and there must be a one-to-one correspondence. Finally, the identification and classification of the accounting period field, status field, and settlement field are completed in all path fields, and a classification result table is formed, which should mark the field name, segment index, and attribution category to obtain the path field classification result.

[0148] S502: Based on the path field classification result, expand the accounting period field in the order of field values, divide the accounting period field section in each path record, and analyze the accounting period coverage range of each segment of the path field according to the start and end values of the accounting period field to obtain the accounting period field section;

[0149] First, extract the field values ​​identified as payment period fields from each path field and assign them a unique number based on their position in the path structure. For example, in the path field "Department A / Payment Period 3 / Settlement in Progress", the payment period field is "Payment Period 3", located in the second segment, and its value is recorded as 3. Continue extracting the path field "Department B / Payment Period 1 / Settled", where the payment period field is "Payment Period 1" and its value is 1. Collect the actual values ​​of the payment period field from all path records one by one. After summarizing, sort the payment period field values ​​by numerical value to form a continuous payment period sequence, such as 1, 2, 3, 4, 5, etc. Then, perform a segmentation operation on the sorted payment period field values, grouping the path fields according to the interval to which the payment period field value belongs. For example, paths with payment period values ​​of 1 to 2 are grouped into the first group, 3 to 4 into the second group, and 5 and above into the third group. The segments can be divided equally based on the amount of path data. Boundaries are manually set based on the payment period span. During the division process, the relationship between the payment period field value in each path record and the segment boundary needs to be determined. For example, if the payment period value is 3, it is determined to be in the interval 2 to 4, and thus belongs to the corresponding segment. Then, based on the path records in each segment, the start and end payment period values ​​covered by the segment are analyzed, and this range is recorded as the payment period coverage range of the path record. For example, if the start value in a segment is 1 and the end value is 3, then the payment period coverage range of the path field group is 1 to 3. Then, the payment period coverage range of all segments is summarized and organized, and the segment number, start and end payment period values, and number of path records covered are recorded to ensure that each path record belongs to a unique and non-repeating segment. If the payment period field value of a record is missing or cannot be identified, it is not included in the division. Finally, the details of the payment period intervals with completed payment period field division and marked coverage range are output, thus obtaining the payment period field segment.

[0150] S503: Based on the payment period field segment, fill the settlement field and status field in the path field into the corresponding payment period segment position, and write them according to the order of the fields in the path to obtain the settlement status written field set;

[0151] First, determine the payment period segment to which the path field belongs. For example, if the path field "Region A / Settlement Completed / Confirmed / Payment Period 3" belongs to payment period segment 3-4, then this path field is sequentially numbered as the 2nd item within the payment period segment. After reading its field content, extract "Settlement Completed" as the settlement field and "Confirmed" as the status field, recording their segment positions in the original path field structure, assuming they are the 2nd and 3rd segments. Then, map these two field values ​​back to the data structure of the current payment period segment according to their order in the original path structure, filling the settlement field column and status field column respectively from left to right. If the path field is "Project B / Paid / Completed / Payment Period 4", then "Paid" is the settlement field and "Completed" is the status field, originally in the 2nd and 3rd segments, and written into the structure of the payment period segment. The fields should remain in their original positions and be placed sequentially under the corresponding path records. If a path field in the original structure only contains a settlement field but no status field, the status field column should be marked as empty during writing and no field value should be filled to avoid displacement interference. At the same time, field type confusion is not allowed during the field writing process; that is, the settlement field should not be written into the status field column, and vice versa. After completing the field filling for all path records, consistency checks should be performed on the field records in each billing period segment to ensure that there are no duplicate field values, multiple segment mergings, or missing field values ​​in the field columns. Records with fields in the wrong positions should be removed and not included in subsequent output. Finally, a two-column data set of settlement fields and status fields written in the order of path fields should be formed in all billing period segments. The output data structure should be in a standard format to obtain the settlement status written field set.

[0152] Please see Figure 7 A blockchain-based multi-party automated settlement system includes:

[0153] The path structure extraction module obtains the account writing records of nodes with multiple participants, identifies the combination relationship between path fields and payment period fields, calls the payment period field according to the node source, and reads the field correspondence within the path group according to the path sorting information to obtain the payment period path cross field sequence.

[0154] The permission path filtering module aligns the node identity field with the path permission field based on the cross field sequence of the billing period path, and filters path records with consistent field values ​​according to the trigger conditions to obtain a set of paths for which permissions can be released.

[0155] The settlement control labeling module identifies the billing period fields associated with the permission fields based on the set of releasable permission paths, arranges the associated fields in the order of the paths, appends the settlement control fields to the paths, excludes duplicate records, and obtains a list of write paths with control fields.

[0156] The ledger synchronization verification module checks the status fields in the paths based on the list of write paths with control fields, identifies the field indexes that already exist in the ledger records, filters out paths that have not been recorded and used, and obtains a list of ledger paths that can be synchronized.

[0157] The settlement status writing module is based on the list of synchronized ledger paths. It reads the period, settlement and status fields of each path, expands the period field into data segments, and writes the path data according to the field position to obtain the set of settlement status writing fields.

[0158] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for automatic settlement based on blockchain with multi-party participation, characterized in that, The method comprises the following steps: S1: obtaining multi-party participating node account writing records, identifying the combination relationship of the path field and the account period field, extracting the account period field according to the node source, comparing the field content according to the path order and the field position relationship, and obtaining the account period path cross-field sequence; S2: based on the field content in the account period path cross-field sequence, aligning the identity field and the permission field, analyzing the trigger mechanism in the permission field, matching the path field content, and obtaining the releasable permission path set; S3: based on the path field and the permission field in the releasable permission path set, mapping the permission field associated account period field, arranging the fields according to the path order, and appending the settlement control field in the path to obtain the writing path list with control fields; S4: based on the writing path list with control fields, analyzing the path state field content, identifying the recorded field index in the account book, screening the unoccupied path record, and obtaining the synchronizable account book path list; S5: based on the path record in the synchronizable account book path list, expanding the account period field content, writing the settlement field and the state field according to the position in the account book, and obtaining the settlement state writing field set; The matching path field content refers to comparing the sequential position of the path field and the permission field, analyzing the trigger mechanism in the path permission field, and identifying whether the path field has permission release; The mapping of the permission field associated with the account period field refers to matching the permission field appearing in the path field and the account period field associated in structure; The settlement control field is appended in the path refers to adding the control field information into the path structure according to the account period span information associated with each path field; The analysis of the path state field content refers to identifying the state field content in the path structure, comparing the state field according to the arrangement order of the fields in the path structure, and analyzing the embedded position in the path field according to the position association; The specific steps of S1 are as follows: S101: obtaining multi-party participating node account writing records, identifying the pairing relationship between the path field and the account period identification field in each record, recording the path field content according to the account source node, locating the account period field in the path field, and obtaining the node account period path field set; S102: based on the node account period path field set, comparing the arrangement order according to the sorting number in the path field and the position index of the account period field, summarizing the corresponding position of the account period field in the path group, and obtaining the account period field order mapping list; S103: based on the account period field order mapping list, according to the arrangement position information of the path field in the account data, listing the account period field position combination in the path according to the field appearance order, and obtaining the account period path cross-field sequence. 2.The blockchain-based multi-party participation and automatic settlement method according to claim 1, wherein, The account period path intersection field sequence includes path ordering information, account period field position, and field corresponding position relationship. The releasable authority path set includes path field, authority field, and trigger condition matching content. The write-in path list with control field includes path field sequence, authority field sequence, account period field arrangement, and settlement control field. The synchronizable account book path list includes unoccupied path record, synchronization state data, and account book state field index. The settlement state write-in field set includes account period field segmentation, settlement field, state field, and path structure mapping position. 3.The blockchain-based multi-party participation and automatic settlement method according to claim 1, wherein, The specific steps of S2 are: S201: Based on the field content in the account period path intersection field sequence, the node identity field and the path authority field are arranged according to the path ordering sequence arrangement position, and the field position pairing result is obtained according to the pairing position of the arrangement sequence in the field path segment. S202: Based on the field position pairing result, the field value offset between the node identity field and the path authority field is calculated, and the field offset result is obtained by comparing the arrangement sequence of the corresponding position in the path segment. S203: Based on the field offset result, the trigger value content in the path authority field is located, and the consistency with the set field value in the path field is analyzed to obtain the releasable authority path set. 4.The blockchain-based multi-party participation and automatic settlement method according to claim 1, wherein, The specific steps of S3 are: S301: Based on the path field and the corresponding authority field in the releasable authority path set, the pairing relationship between the path field and the authority field is called, the account period field information associated with the authority field is aligned with the corresponding path field, the corresponding sequence between the fields is reserved, and the path account period field alignment details are obtained. S302: Based on the path account period field alignment details, the span value of the path field in the account period dimension is calculated according to the account period field value associated with each path field, the number of continuous account periods covered in the account period field value is identified, and the number is associated with the corresponding path field to obtain the path account period span. S303: Based on the path account period span, the authority field and the account period field information corresponding to the path field in the path field are called, the settlement control field value of the path field is matched, the matching result is added to the path data one by one according to the path field information, the path information including the field content is screened, and the write-in path list with control field is obtained. 5.The blockchain-based multi-party participation and automatic settlement method according to claim 1, wherein, The specific steps of S4 are: S401: Based on the write-in path list with control field, the state field information field value in the path structure is analyzed, the corresponding state field in each path field is associated with the path field position, and the path state field information table is obtained according to the corresponding allocation position of the path field. S402: Based on the path state field information table, the state field index field value in the account book record is compared, the case that the state field value in the path field does not appear in the account book field is identified, the path field is partitioned according to the state field missing condition, and the path state field vacancy list is obtained. S403: Based on the path state field vacancy list, the synchronization state data content is added to the state field position corresponding to the path field, the state field value is appended to the original path field information, and the field integrity is analyzed to obtain a synchronizable ledger path list. 6.The blockchain-based multi-party participation and automatic settlement method according to claim 1, wherein, The specific steps of S5 are: S501: Based on the path record content in the synchronizable ledger path list, the account period field, settlement field and state field in the path structure are located, the fields are analyzed according to the field type according to the corresponding relationship between the field name and the field position, and the path field classification result is obtained; S502: Based on the path field classification result, the account period field is expanded according to the field value sequence, the account period field section in each path record is divided, and the account period coverage range of each section of path field is analyzed according to the start and end values of the account period field, to obtain the account period field section; S503: Based on the account period field section, the settlement field and the state field in the path field are filled in the account period section position, and the settlement state writing field set is obtained according to the sequence in the path.

7. A blockchain-based multi-party participation automatic settlement system, characterized by, The system is used to realize the multi-party participation automatic settlement method based on the blockchain of any one of claims 1-6, and the system comprises: The path structure extraction module obtains multi-party participation node account writing records, identifies the combination relationship of the path field and the account period field, calls the account period field according to the node source, reads the path group field corresponding relationship according to the path sorting information, and obtains the account period path cross field sequence; The permission path screening module is based on the account period path cross field sequence, aligns the node identity field and the path permission field, screens the path records with consistent field values according to the trigger condition, and obtains a releasable permission path set; The settlement control labeling module is based on the releasable permission path set, identifies the account period field associated with the permission field, arranges the associated fields according to the path sequence, adds the settlement control field in the path, excludes duplicate records, and obtains a writing path list with control fields; The ledger synchronization verification module is based on the writing path list with control fields, checks the state field in the path, identifies the existing field index in the ledger record, screens out the paths not used by the record, and obtains a synchronizable ledger path list; The settlement state writing module is based on the synchronizable ledger path list, reads the account period, settlement and state fields of each path, segments the account period field expansion data, writes the path data according to the field position, and obtains a settlement state writing field set.

Images