Business configuration bill payment system based on block chain

Abstract

The invention discloses a business configuration bill payment system based on a block chain, and the system comprises a business configuration event module which is used for generating a business configuration event sequence and a structure state sequence; the structure disturbance module is used for generating structure disturbance representation based on the structure state sequence and the baseline structure state sequence; the recovery cost module is used for generating a recovery cost sequence; the business configuration bill module is used for generating business configuration bill data based on the recovery cost sequence; the clearing commitment registration module is used for registering a recovery cost clearing commitment set; the clearing state module is used for updating and recovering the cost clearing commitment set based on the payment request and generating a clearing state sequence; and the consistency verification module is used for generating a bill consistency verification result of the payment bill. According to the method, modeling is carried out on the basis of link clearing commitment and structure evolution association, service configuration bill generation and payment consistency replay verification are realized, and the method has the advantages of being transparent, credible and accurate in positioning.

Description

A blockchain-based business configuration bill payment system Technical Field

[0001] This invention relates to the field of business configuration bill payment, and more particularly to a blockchain-based business configuration bill payment system. Background Technology

[0002] In existing business management systems, the business configuration process usually relies on manual recording and offline auditing to track resource changes, which makes it difficult to accurately reflect the true state of the business operation structure as it evolves over time. At the same time, bill generation is mostly based on static configuration information, which cannot correspond to business operation behavior, resulting in opaque cost allocation and difficulty in locating problems. When multi-party collaboration is involved, the problems of inconsistent billing data at each node and unclear settlement basis become more prominent.

[0003] Existing blockchain payment models primarily focus on recording transactions on the blockchain and ensuring the immutability of payment results. However, they are unable to link business configuration behavior with changes in operational status, and lack replayable and consistency verification mechanisms for bill calculation logic and payment settlement logic. Consequently, they cannot diagnose the causes of bill discrepancies and settlement anomalies. Therefore, there is an urgent need to construct a business configuration bill payment technology solution that can uniformly link business configuration behavior, structural change processes, bill calculation, and actual payment settlement behavior, and support auditable and replayable verification. Summary of the Invention

[0004] One objective of this invention is to propose a blockchain-based business configuration bill payment system. This invention is based on on-chain settlement commitment and structural evolution correlation modeling to achieve replayable verification of the consistency between business configuration bill generation and payment, and has the advantages of transparency, reliability, and accurate positioning.

[0005] A blockchain-based business configuration bill payment system according to an embodiment of the present invention includes:

[0006] The business configuration event module is used to generate business configuration event sequences and structure state sequences;

[0007] The structural perturbation module is used to generate structural perturbation representations based on the structural state sequence and the baseline structural state sequence;

[0008] The recovery cost module is used to combine structural disturbance representations with operational status data to generate a recovery cost sequence;

[0009] The business configuration billing module is used to generate business configuration billing data based on the recovery cost sequence;

[0010] The repayment commitment registration module is used to write business configuration billing data into the blockchain ledger and register the set of recovery cost repayment commitments;

[0011] The settlement status module is used to update the set of recovery cost settlement commitments based on payment requests and generate a settlement status sequence.

[0012] The consistency verification module is used to recalculate the business configuration bill based on the business configuration event sequence, running status data, and settlement status sequence, and generate the bill payment bill consistency verification result.

[0013] Optionally, modules can be integrated in the following ways:

[0014] Collect business configuration operations in the business operation environment, generate business configuration event sequences by time, collect business operation structure snapshots, generate baseline structure state sequences by time, and apply the business configuration event sequences to the baseline structure state sequences to generate structure state sequences.

[0015] Structural perturbation representations are generated by performing structural difference calculations on the structural state sequence and the baseline structural state sequence using the same time index.

[0016] The structural disturbance representation is combined with the operational status data collected under the corresponding time index to generate a recovery cost sequence;

[0017] Aggregate the recovery cost sequence by billing period to generate recovery cost records and generate business configuration billing data;

[0018] The business configuration billing data is compressed to generate a billing summary, which is then written into the blockchain ledger. The smart contract registers the set of recovery cost settlement commitments.

[0019] Receive payment requests, match payment amounts with business configuration billing data to generate target recovery costs, and use the recovery path simulation results driven by the target recovery costs to update the recovery cost repayment commitment set and generate a repayment status sequence;

[0020] During the audit, the business configuration event sequence, running status data, and settlement status sequence are read to regenerate the recalculation recovery cost sequence. This sequence is then compared with the business configuration bill data and settlement status sequence to generate a bill consistency verification result, forming a replayable verification closed loop for business configuration bill payment and structural recovery.

[0021] Optionally, the generation of the structural state sequence specifically includes:

[0022] In the business operation environment, business configuration operations are collected, and the collected business configuration operations are sorted according to the occurrence time to generate a business configuration event sequence.

[0023] Collect snapshots of the business operation structure, sort the collected snapshots according to the collection time, and generate a baseline structure state sequence;

[0024] Using the time index of the business configuration event sequence as the unique alignment benchmark, the structural states in the baseline structural state sequence are rearranged, and each business configuration event corresponds to a unique baseline structural state, generating a time-aligned baseline structural state sequence.

[0025] According to the time index order of the business configuration event sequence, the business configuration event under the corresponding time index is applied to the corresponding baseline structure state in the time-aligned baseline structure state sequence, the structure update process is performed, and the structure state update result under the corresponding time index is generated.

[0026] The structure state update results generated under each time index are arranged in the order of the time index to generate a structure state sequence.

[0027] Optionally, the generation of the structural perturbation representation specifically includes:

[0028] Read the structural state sequence and the baseline structural state sequence, and determine the time index correspondence between the structural state sequence and the baseline structural state sequence;

[0029] Based on the time index correspondence, the structural states under each time index in the structural state sequence are paired one by one with the baseline structural states under the same time index in the baseline structural state sequence to generate a set of structural state pairs.

[0030] For each structural state pair in the set of structural state pairs, perform structural difference calculation, extract the structural change results between the structural state and the corresponding baseline structural state, and generate the structural difference results under the corresponding time index;

[0031] The structural difference results generated under each time index are associated and organized according to the time index to form a structural difference sequence arranged by time index;

[0032] A unified representation processing is performed on the structural difference sequence, organizing the structural change results in the structural difference sequence into a structural perturbation representation.

[0033] Optionally, the generation of the recovery cost sequence specifically includes:

[0034] Read the structural perturbation representation in time index order, and record the structural perturbation value corresponding to each time index as the structural offset corresponding to that time index in the structural perturbation record sequence;

[0035] Within the same time index range as the structural disturbance recording sequence, operational status data is collected, and the operational status data corresponding to each time index is recorded as the operational cost impact amount corresponding to that time index in the operational status recording sequence.

[0036] To maintain consistency of time indexes, the structural disturbance record sequence and the running status record sequence are combined item by item under each time index to generate a combined record sequence that includes the structural offset and the impact of running costs.

[0037] While keeping the time index order of the combined record sequence unchanged, the structural offset and the impact of the running cost in the combined record under each time index are processed to extract the cost, and a recovery cost record sequence arranged by time index is generated.

[0038] Within the billing period, the time index order of the recovery cost record sequence is maintained, and the recovery cost records corresponding to multiple time indices are aggregated at the billing period level to generate a billing period-level recovery cost fragment.

[0039] Based on the order of business configuration identifiers in the business configuration event sequence, multiple billing period-level recovery cost fragments are combined sequentially. Each business configuration identifier corresponds to a unique billing period-level recovery cost value. The time index relationship between the business configuration identifier and the recovery cost value is maintained to generate a recovery cost sequence.

[0040] Optionally, the generation of the business configuration billing data specifically includes:

[0041] Maintain the time index order of the recovery cost sequence, and group the recovery cost sequence according to the service configuration identifier to form a recovery cost grouping sequence divided by the service configuration identifier;

[0042] Set the billing period time range, select the recovery cost value whose time index belongs to the billing period time range from the recovery cost grouping sequence, and aggregate them sequentially according to the business configuration identifier to generate a billing period-level recovery cost fragment sequence.

[0043] Maintain the correspondence between the service configuration identifiers of the billing period-level recovery cost fragment sequence and the billing period time range, and combine the billing period-level recovery cost fragment sequences in order of service configuration identifiers to generate a billing period-level recovery cost record sequence;

[0044] Maintain the business configuration identifier order and time index order of the billing period recovery cost record sequence, and compress the billing period recovery cost record sequence into a billing bill entry sequence containing multiple billing period recovery cost records;

[0045] Based on the billing period item sequence, while maintaining the correspondence between business configuration identifiers and billing period time ranges, the billing period item sequence is compressed into a set of billing items divided by business configuration identifiers, generating business configuration billing data.

[0046] Optionally, the commitment to settle the registration restoration costs specifically includes:

[0047] Read the corresponding billing period-level recovery cost record from the business configuration billing data according to the business configuration identifier, keep the order of business configuration identifier and billing period time range unchanged, and generate a billing period billing item sequence.

[0048] Compression processing is performed on the billing period entry sequence, multiple billing period entries are encoded and concatenated according to the preset field order, duplicate billing period fields and redundant description fields are removed, and a bill summary is generated;

[0049] Write the bill summary to the blockchain ledger, generate on-chain bill summary entries corresponding to the bill summary, and maintain a consistent correspondence between on-chain bill summary entries and the billing period range and business configuration identifier order;

[0050] Extract the period-level recovery cost records in the order of the business configuration identifiers in the business configuration billing data, combine the period-level recovery cost record corresponding to each business configuration identifier with the on-chain billing summary entries to generate a sequence of recovery cost settlement entries arranged by business configuration identifier, and aggregate the recovery cost settlement entry sequences to form a set of recovery cost settlement commitments.

[0051] The set of recovery cost repayment commitments is submitted to the smart contract, which then registers the set of recovery cost repayment commitments in the blockchain ledger. Each business configuration identifier's corresponding recovery cost repayment commitment is bound to an on-chain bill summary entry, thus completing the registration of the set of recovery cost repayment commitments.

[0052] Optionally, the generation of the settlement state sequence specifically includes:

[0053] Receive payment requests and parse payment amounts, maintain the correspondence between payment requests and business configuration identifiers, arrange them in the order of payment requests, and generate a sequence of payment records.

[0054] Based on the payment record sequence, the payment amount is matched item by item with the billing period-level recovery cost records arranged by business configuration identifier in the business configuration billing data to generate the target recovery cost sequence;

[0055] Based on the target recovery cost sequence, the target recovery cost and the structural state sequence are matched item by item according to the service configuration identifier and time index, and arranged in order according to the service configuration identifier to generate a recovery path simulation result sequence;

[0056] Based on the recovery path simulation result sequence, the set of recovery cost settlement commitments registered by the smart contract is read, and the recovery path simulation result sequence and the target recovery cost sequence are combined according to the business configuration identifier, while maintaining the order of the business configuration identifier, to generate a recovery cost settlement commitment update sequence.

[0057] The recovery cost settlement commitment update sequence is submitted to the smart contract, which then updates the recovery cost settlement commitment set and generates a settlement status sequence in the order of the payment record sequence.

[0058] Optionally, the generation of the replayable verification closed loop specifically includes:

[0059] Receive audit requests, determine the audit time range, filter business configuration event records from the business configuration event sequence according to the audit time range, and generate audit business configuration event sub-sequences by arranging them in order of business configuration identifier and time index.

[0060] Based on the audit business configuration event subsequence, the running status records are filtered from the running status data according to the audit time range, and aligned according to the time index order of the audit business configuration event subsequence to generate an audit running status data sequence.

[0061] Based on the audit business configuration event subsequence and the audit operation status data sequence, the structure status generation, structure disturbance representation generation and recovery cost generation are executed sequentially, and the recovery cost sequence is recalculated according to the time index order of the audit business configuration event subsequence.

[0062] Based on the recalculated recovery cost sequence, the period-level recovery cost records are extracted from the business configuration bill data according to the business configuration identifier to form audit business configuration bill sub-data. The settlement status records are extracted from the settlement status sequence according to the business configuration identifier and time index to form audit settlement status sub-sequence.

[0063] Based on the recalculation recovery cost sequence, audit business configuration bill sub-data and audit settlement status sub-sequence, the recalculation recovery cost record, bill period-level recovery cost record and settlement status record are compared item by item according to the business configuration identifier and time index to generate a consistency verification record sequence;

[0064] Based on the consistency verification record sequence, consistency verification information is summarized according to the audit time range and business configuration identifier order to generate bill consistency verification results, forming a replayable verification closed loop for business configuration bill payment and structure recovery.

[0065] The beneficial effects of this invention are:

[0066] This invention introduces a structure evolution-driven billing generation mechanism and an on-chain settlement commitment registration method, enabling a strict consistency relationship between system structure changes caused by business configuration and the billing payment process. This fundamentally solves the problems in existing technologies where bills are based solely on static cost accumulation, cannot be cross-verified with the actual structure evolution process, and are disconnected from system recoverability. In this invention, business configuration events, structure state sequences, and operational state data are uniformly mapped to recovery cost sequences and generate business configuration billing data. The bill no longer reflects isolated "cost records," but rather dynamic recovery costs closely bound to structural offsets, operational impacts, and recovery paths. This makes the bill an interpretable, traceable, and consistent expression of the billing period with the actual system evolution, enhancing credibility and payment rationality at the billing content level.

[0067] This invention uses a blockchain ledger as a trusted registration carrier for bill summaries and recovery cost repayment commitments. By simulating recovery paths triggered by payment requests and updating commitments, it establishes a causal link between payment and structural recovery. This transforms payment behavior from a mere result entry into a verification input for structural rollback capabilities. Addressing the issue in existing technologies where it's impossible to confirm whether the system status has been restored according to the payment content after bill payment, this invention continuously records the commitment fulfillment process through a repayment status sequence. Combined with the recalculation of recovery cost sequences under audit scenarios, this creates a closed-loop verification path for payment. The bill payment result matches the actual recovery progress, avoiding the information gap phenomenon of "bill paid, structure not repaired." Simultaneously, the replayable verification closed loop not only enhances the trusted payment capability of bills but also provides a high-granularity verification trajectory for system operation and maintenance, compliance auditing, and cost backtracking. This makes the calculation, repayment, and rollback capabilities of recovery costs verifiable and provable, thereby significantly improving the transparency, consistency, and anti-dispute capability of the bill payment process. Attached Figure Description

[0068] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used in conjunction with embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings:

[0069] Figure 1 is a schematic diagram of the overall structure of a blockchain-based business configuration bill payment system proposed in this invention;

[0070] Figure 2 is a flowchart of a blockchain-based business configuration bill payment system proposed in this invention.

[0071] Figure 3 is a data flow diagram of a blockchain-based business configuration bill payment system proposed in this invention. Detailed Implementation

[0072] The present invention will now be described in further detail with reference to the accompanying drawings. These drawings are simplified schematic diagrams, illustrating only the basic structure of the invention, and therefore only show the components relevant to the invention.

[0073] Referring to Figures 1-3, a blockchain-based business configuration bill payment system includes:

[0074] The business configuration event module is used to generate business configuration event sequences and structure state sequences;

[0075] The structural perturbation module is used to generate structural perturbation representations based on the structural state sequence and the baseline structural state sequence;

[0076] The recovery cost module is used to combine structural disturbance representations with operational status data to generate a recovery cost sequence;

[0077] The business configuration billing module is used to generate business configuration billing data based on the recovery cost sequence;

[0078] The repayment commitment registration module is used to write business configuration billing data into the blockchain ledger and register the set of recovery cost repayment commitments;

[0079] The settlement status module is used to update the set of recovery cost settlement commitments based on payment requests and generate a settlement status sequence.

[0080] The consistency verification module is used to recalculate the business configuration bill based on the business configuration event sequence, running status data, and settlement status sequence, and generate the bill payment bill consistency verification result.

[0081] In this embodiment, the modules are implemented in the following way:

[0082] Collect business configuration operations in the business operation environment, generate business configuration event sequences by time, collect business operation structure snapshots, generate baseline structure state sequences by time, and apply the business configuration event sequences to the baseline structure state sequences to generate structure state sequences.

[0083] Structural perturbation representations are generated by performing structural difference calculations on the structural state sequence and the baseline structural state sequence using the same time index.

[0084] The structural disturbance representation is combined with the operational status data collected under the corresponding time index to generate a recovery cost sequence;

[0085] Aggregate the recovery cost sequence by billing period to generate recovery cost records and generate business configuration billing data;

[0086] The business configuration billing data is compressed to generate a billing summary, which is then written into the blockchain ledger. The smart contract registers the set of recovery cost settlement commitments.

[0087] Receive payment requests, match payment amounts with business configuration billing data to generate target recovery costs, and use the recovery path simulation results driven by the target recovery costs to update the recovery cost repayment commitment set and generate a repayment status sequence;

[0088] During the audit, the business configuration event sequence, running status data, and settlement status sequence are read to regenerate the recalculation recovery cost sequence. This sequence is then compared with the business configuration bill data and settlement status sequence to generate a bill consistency verification result, forming a replayable verification closed loop for business configuration bill payment and structural recovery.

[0089] In this embodiment, the generation of the structural state sequence specifically includes:

[0090] In the business operation environment, business configuration operations are collected, and the collected business configuration operations are sorted according to the occurrence time to generate a business configuration event sequence.

[0091] Collect snapshots of the business operation structure, sort the collected snapshots according to the collection time, and generate a baseline structure state sequence;

[0092] Using the time index of the business configuration event sequence as the unique alignment benchmark, the structural states in the baseline structural state sequence are rearranged, and each business configuration event corresponds to a unique baseline structural state, generating a time-aligned baseline structural state sequence.

[0093] According to the time index order of the business configuration event sequence, the business configuration event under the corresponding time index is applied to the corresponding baseline structure state in the time-aligned baseline structure state sequence, the structure update process is performed, and the structure state update result under the corresponding time index is generated.

[0094] The generation of the structural state update result specifically includes:

[0095] Read the baseline structural state corresponding to the current time index from the time-aligned baseline structural state sequence, keeping the structural element identifiers and structural relationship identifiers unchanged, to form a structural state baseline record under the current time index; read the business configuration event corresponding to the current time index, determine the structural change target and structural change method from the business configuration event, and form a structural change record under the current time index; perform structural change processing in the structural state baseline record according to the structural change target and structural change method indicated by the structural change record, to form a structural state change record under the current time index; keep the structural element identifiers and structural relationship identifiers of the structural state change record under the current time index, and recombine the unchanged structural relationships in the structural state change record and the structural state baseline record according to the existing structural relationship organization method to form an updated structural state record; store the updated structural state record in the original time index order to form the structural state update result under the corresponding time index;

[0096] The structure state update results generated under each time index are arranged in the order of the time index to generate a structure state sequence.

[0097] In this embodiment, the generation of the structural perturbation representation specifically includes:

[0098] Read the structural state sequence and the baseline structural state sequence, and determine the time index correspondence between the structural state sequence and the baseline structural state sequence;

[0099] Based on the time index correspondence, the structural states under each time index in the structural state sequence are paired one by one with the baseline structural states under the same time index in the baseline structural state sequence to generate a set of structural state pairs.

[0100] For each structural state pair in the set of structural state pairs, perform structural difference calculation, extract the structural change results between the structural state and the corresponding baseline structural state, and generate the structural difference results under the corresponding time index;

[0101] The generation of the structural difference results specifically includes:

[0102] Read the structural state pair corresponding to the current time index from the structural state pair set. Keep the structural element identifier and structural relationship identifier of the structural state pair unchanged as the structural state record. Keep the structural element identifier and structural relationship identifier of the corresponding baseline structural state record in the structural state pair unchanged as the baseline structural state record. Perform structural element comparison between the structural state record and the baseline structural state record according to the structural element identifier. Record the structural element identifier that exists in the structural state record but does not exist in the baseline structural state record as the newly added structural element record. Record the structural element identifier that exists in the baseline structural state record but does not exist in the structural state record as the deleted structural element record. Perform structural relationship comparison between the structural state record and the baseline structural state record based on structural relationship identifiers. Compare the structural relationship identifiers associated with structural element identifiers in the structural state record with the corresponding structural relationship identifiers in the baseline structural state record item by item, and record inconsistent structural relationship identifiers as structural relationship change records. Maintain the correspondence between structural element identifiers and structural relationship identifiers in newly added structural element records, deleted structural element records, and structural relationship change records. Combine the above records according to the current time index order to form the structural change records under the current time index. Store the structural change records under the current time index in the original time index order to generate the structural difference results under the corresponding time index.

[0103] The structural difference results generated under each time index are associated and organized according to the time index to form a structural difference sequence arranged by time index;

[0104] A unified representation processing is performed on the structural difference sequence, and the structural change results in the structural difference sequence are organized into a structural perturbation representation;

[0105] The generation of the structural perturbation representation specifically includes:

[0106] Read the structural difference sequence in chronological order, and record the structural difference results corresponding to each time index in the structural difference sequence as structural difference records. Keeping the structural element identifiers and structural relationship identifiers in the structural difference records unchanged, align the structural difference records and combine structural difference records with the same structural element identifier and the same structural relationship identifier according to their time index to generate a structural change combination record sequence. Maintaining the correspondence between the structural element identifiers and structural relationship identifiers in the structural change combination record sequence, arrange the structural change combination record sequence according to their time index to generate a structural change arrangement record sequence. Maintaining the time index order of the structural change arrangement record sequence, aggregate the structural change arrangement records under each time index according to their structural element identifiers and structural relationship identifiers to generate a structural change aggregation record sequence. Organize the structural change aggregation record sequence while maintaining the continuous correspondence of time indices into a structural change aggregation result arranged by time index, generating a structural perturbation representation.

[0107] In this embodiment, the generation of the recovery cost sequence specifically includes:

[0108] Read the structural perturbation representation in time index order, and record the structural perturbation value corresponding to each time index as the structural offset corresponding to that time index in the structural perturbation record sequence;

[0109] The generation of the structural offset specifically includes:

[0110] Read the structural perturbation representation and extract the structural perturbation records arranged by time index. Under each time index, determine the structural change value representing the degree of structural change in the structural perturbation record as the structural change base value under the corresponding time index. Preserving the time index order of the structural change base values, perform amplitude delimiting processing on the structural change base values, and use the structural change base value after amplitude delimiting processing as the structural change delimiting value under the corresponding time index. Preserving the time index order of the structural change delimiting values, perform direction preservation processing on the structural change delimiting values, and use the structural change delimiting value after direction preservation processing as the structural change normalization value under the corresponding time index. Preserving the time index order of the structural change normalization values, perform scale alignment processing on the structural change normalization values, and use the structural change normalization value after scale alignment processing as the structural offset under the corresponding time index.

[0111] Within the same time index range as the structural disturbance recording sequence, operational status data is collected, and the operational status data corresponding to each time index is recorded as the operational cost impact amount corresponding to that time index in the operational status recording sequence.

[0112] To maintain consistency of time indexes, the structural disturbance record sequence and the running status record sequence are combined item by item under each time index to generate a combined record sequence that includes the structural offset and the impact of running costs.

[0113] The generation of the combined record sequence specifically includes:

[0114] Read the structural disturbance record sequence in time index order, and record the structural offset corresponding to each time index as a structural offset entry; read the running status record sequence within the same time index range as the structural disturbance record sequence, and record the running cost impact quantity corresponding to each time index as a running cost impact quantity entry; maintain time index consistency, align the structural offset entry under each time index with the running cost impact quantity entry under the corresponding time index item by item, forming an aligned entry pair sequence arranged by time index; maintain the time index order of the aligned entry pair sequence, and concatenate the structural offset entry and running cost impact quantity entry in each aligned entry pair in the original record format sequentially to generate a combined entry sequence arranged by time index; organize the combined entries corresponding to each time index in the combined entry sequence into a combined record sequence while maintaining the time index continuity and the original entry order;

[0115] While keeping the time index order of the combined record sequence unchanged, the structural offset and the impact of the running cost in the combined record under each time index are processed to extract the cost, and a recovery cost record sequence arranged by time index is generated.

[0116] The generation of the recovery cost record sequence specifically includes:

[0117] Read the combined record sequence in time index order, and record the combined records corresponding to each time index as a combined record entry sequence while maintaining the original time index order. Maintaining the time index order of the combined record entry sequence, extract structural offset entries and operational cost impact entries from each combined record entry to form a time index-arranged sequence of offset and impact corresponding records. Maintaining the time index order of the offset and impact corresponding record sequences, combine the structural offset entries and corresponding operational cost impact entries under each time index sequentially to form a time index-arranged sequence of cost extraction entries. Maintaining the time index order of the cost extraction entry sequence, perform cost extraction processing on the corresponding structural offset entries and operational cost impact entries in each cost extraction entry, and record them as recovery cost records under the corresponding time index. Maintain the time index continuity and generation order of the recovery cost records generated under each time index, and arrange them sequentially in time index order to form a time index-arranged sequence of recovery cost records.

[0118] Within the billing period, the time index order of the recovery cost record sequence is maintained, and the recovery cost records corresponding to multiple time indices are aggregated at the billing period level to generate a billing period-level recovery cost fragment.

[0119] According to the order of business configuration identifiers in the business configuration event sequence, multiple billing period-level recovery cost fragments are combined sequentially. Each business configuration identifier corresponds to a unique billing period-level recovery cost value. The time index relationship between the business configuration identifier and the recovery cost value is maintained to generate a recovery cost sequence.

[0120] The generation of the recovery cost sequence specifically includes:

[0121] Multiple billing period-level recovery cost fragments are read, and each billing period-level recovery cost fragment is recorded as a sequence of billing period-level recovery cost fragment entries while maintaining its generation order. Maintaining the time index order of the sequence of billing period-level recovery cost fragment entries, each billing period-level recovery cost fragment is matched to its corresponding business configuration identifier in the business configuration event sequence, forming a sequence of billing period-level recovery cost identifier entries arranged by business configuration identifier. Maintaining the business configuration identifier order of the sequence of billing period-level recovery cost identifier entries, the corresponding billing period-level recovery cost value in each billing period-level recovery cost identifier entry maintains its correspondence with its time index, generating a sequence of billing period-level recovery cost value records arranged by business configuration identifier and time index. Based on the sequence of billing period-level recovery cost value records, maintaining the business configuration identifier order, each billing period-level recovery cost value record is combined sequentially to form a sequence of recovery cost value entries indexed by the business configuration identifier. The recovery cost values ​​corresponding to each business configuration identifier in the sequence of recovery cost value entries are arranged sequentially according to the business configuration identifier order while maintaining the continuity of the time index and the business configuration identifier order, generating a recovery cost sequence.

[0122] In this embodiment, the generation of the business configuration bill data specifically includes:

[0123] Maintain the time index order of the recovery cost sequence, and group the recovery cost sequence according to the service configuration identifier to form a recovery cost grouping sequence divided by the service configuration identifier;

[0124] Set the billing period time range, select the recovery cost value whose time index belongs to the billing period time range from the recovery cost grouping sequence, and aggregate them sequentially according to the business configuration identifier to generate a billing period-level recovery cost fragment sequence.

[0125] Maintain the correspondence between the service configuration identifiers of the billing period-level recovery cost fragment sequence and the billing period time range, and combine the billing period-level recovery cost fragment sequences in order of service configuration identifiers to generate a billing period-level recovery cost record sequence;

[0126] Maintain the business configuration identifier order and time index order of the billing period recovery cost record sequence, and compress the billing period recovery cost record sequence into a billing bill entry sequence containing multiple billing period recovery cost records;

[0127] The generation of the billing cycle entry sequence specifically includes:

[0128] Read the billing period-level recovery cost record sequence, maintaining the order of business configuration identifiers and time indexes for each record. Arrange each record according to its business configuration identifier, forming a list of billing period-level recovery cost records ordered by identifier. Within this list, maintain the correspondence between business configuration identifiers and billing period time ranges, merging each record according to its billing period time range to its corresponding billing period position, forming a merged list of billing period-level recovery costs. Within this merged list, maintaining the order of billing period time ranges, group records within the same billing period... Multiple period-level recovery cost records merged under a period are sequentially connected according to the order of business configuration identifiers to form a concatenated result of period-level recovery costs, and multiple period-level recovery cost segments are generated with the period as the boundary; each period-level recovery cost segment is arranged in order of the period time range, keeping the order of business configuration identifiers within each period-level recovery cost segment unchanged, and each period-level recovery cost segment is compressed into a corresponding period entry, forming a sequence of period entries arranged by period; the sequence of period entries is then sequentially combined while keeping the order of the period time range and the order of business configuration identifiers consistent, and multiple period entries are organized in a sequential manner into a sequence of period bill entries containing multiple period-level recovery cost records;

[0129] Based on the billing period bill item sequence, while maintaining the correspondence between business configuration identifiers and billing period time ranges, the billing period bill item sequence is compressed into a set of bill items divided by business configuration identifiers to generate business configuration bill data;

[0130] The generation of the business configuration billing data specifically includes:

[0131] Read the billing period invoice entry sequence, maintaining the order of business configuration identifiers and billing period time ranges within the sequence. Map and organize each billing period invoice entry according to its business configuration identifier, forming a billing period invoice entry mapping record divided by business configuration identifier. In this mapping record, maintain the correspondence between each billing period invoice entry and its billing period time range. Arrange multiple billing period invoice entries corresponding to each business configuration identifier sequentially according to their billing period time ranges, forming a billing period invoice entry arrangement result divided by business configuration identifier. In this arrangement result, perform sequential compression on billing period invoice entries belonging to the same business configuration identifier, maintaining the billing period time range order, and merge multiple billing period invoice entries into a single invoice entry record corresponding to the business configuration identifier. Maintain the consistency between the business configuration identifier order and the billing period time range order in the invoice entry record, organizing all invoice entry records sequentially according to their business configuration identifier order, forming a billing entry sequence arranged by business configuration identifier. Finally, maintain the correspondence between the business configuration identifier and the billing period time range in the invoice entry sequence to generate business configuration invoice data.

[0132] In this embodiment, the commitment to settle the registration restoration costs specifically includes:

[0133] Read the corresponding billing period-level recovery cost record from the business configuration billing data according to the business configuration identifier, keep the order of business configuration identifier and billing period time range unchanged, and generate a billing period billing item sequence.

[0134] Compression processing is performed on the billing period entry sequence, multiple billing period entries are encoded and concatenated according to the preset field order, duplicate billing period fields and redundant description fields are removed, and a bill summary is generated;

[0135] Write the bill summary to the blockchain ledger, generate on-chain bill summary entries corresponding to the bill summary, and maintain a consistent correspondence between on-chain bill summary entries and the billing period range and business configuration identifier order;

[0136] Extract the period-level recovery cost records in the order of the business configuration identifiers in the business configuration billing data, combine the period-level recovery cost record corresponding to each business configuration identifier with the on-chain billing summary entries to generate a sequence of recovery cost settlement entries arranged by business configuration identifier, and aggregate the recovery cost settlement entry sequences to form a set of recovery cost settlement commitments.

[0137] The generation of the set of recovery cost settlement commitments specifically includes:

[0138] Read the period-level recovery cost records from the business configuration billing data according to the order of business configuration identifiers. Write the period-level recovery cost record corresponding to each business configuration identifier into the period-level recovery cost record sequence sequentially, ensuring that the order of business configuration identifiers in the period-level recovery cost record sequence is consistent with the billing period time range. Read the on-chain billing summary entries from the blockchain ledger according to the order of business configuration identifiers. Write the on-chain billing summary entry corresponding to each business configuration identifier into the on-chain billing summary entry sequence sequentially, ensuring that the order of business configuration identifiers in the on-chain billing summary entry sequence is consistent with the period-level recovery cost record sequence. Maintain the consistency between the period-level recovery cost record sequence and the on-chain billing summary entry sequence in terms of business configuration identifiers and billing period time range. The system sequentially combines the recovery cost record sequence at the billing period level with the on-chain bill summary entry sequence by business configuration identifier to generate a recovery cost settlement entry sequence arranged by business configuration identifier. Maintaining consistency between the order of business configuration identifiers and the billing period time range, the recovery cost settlement entry sequences are sequentially aggregated into a set of recovery cost settlement entries divided by business configuration identifiers, ensuring that the recovery cost settlement entry set corresponding to each business configuration identifier is unique within the billing period time range. Maintaining consistency in the order of the recovery cost settlement entry sets corresponding to each business configuration identifier, the recovery cost settlement entry sets corresponding to all business configuration identifiers are sequentially aggregated to generate a recovery cost settlement commitment set.

[0139] The set of recovery cost settlement commitments is submitted to the smart contract, which then registers the set of recovery cost settlement commitments in the blockchain ledger. Each business configuration identifier's corresponding recovery cost settlement commitment is bound to the on-chain bill summary entry, thus completing the registration of the set of recovery cost settlement commitments.

[0140] The aforementioned collective registration of recovery cost repayment commitments specifically includes:

[0141] The process involves: reading the set of recovery cost repayment commitments; forming a recovery cost repayment commitment sequence by arranging the commitments according to their business configuration identifiers; maintaining the business configuration identifier order of the recovery cost repayment commitment sequence; reading on-chain bill summary entries from the blockchain ledger according to their business configuration identifier order; maintaining business configuration identifier consistency; binding the recovery cost repayment commitment sequence and the on-chain bill summary entry sequence item by item according to the same business configuration identifier; submitting the recovery cost repayment commitment binding sequence to the smart contract, which then writes the sequence into the blockchain ledger, generating an on-chain recovery cost repayment commitment record sequence; maintaining the consistency between the business configuration identifier order of the on-chain recovery cost repayment commitment record sequence and the on-chain bill summary entry sequence; and aggregating the on-chain recovery cost repayment commitment record sequences into an on-chain recovery cost repayment commitment set, thus completing the registration of the recovery cost repayment commitment set.

[0142] In this embodiment, the generation of the settlement state sequence specifically includes:

[0143] Receive payment requests and parse payment amounts, maintain the correspondence between payment requests and business configuration identifiers, arrange them in the order of payment requests, and generate a sequence of payment records.

[0144] Based on the payment record sequence, the payment amount is matched item by item with the billing period-level recovery cost records arranged by business configuration identifier in the business configuration billing data to generate the target recovery cost sequence;

[0145] Based on the target recovery cost sequence, the target recovery cost and the structural state sequence are matched item by item according to the service configuration identifier and time index, and arranged in order according to the service configuration identifier to generate a recovery path simulation result sequence;

[0146] The generation of the recovery path simulation result sequence specifically includes:

[0147] Read the target recovery cost sequence in order of service configuration identifiers, and record the target recovery cost corresponding to each service configuration identifier as a target recovery cost record sequence according to the time index. Based on the target recovery cost record sequence, extract the corresponding structural state from the structural state sequence according to the service configuration identifier and time index, and record the extracted structural state as a structural state record sequence. Maintaining the consistency of service configuration identifiers and time indexes, align the target recovery cost record sequence and the structural state record sequence item by item to generate a target recovery cost structural state pair sequence. Based on the target recovery cost structural state pair sequence, maintaining the order of service configuration identifiers and time indexes, perform recovery path generation processing on each record in the target recovery cost structural state pair to generate a recovery path fragment sequence arranged by service configuration identifier and time index. Maintaining the order of service configuration identifiers and time indexes of the recovery path fragment sequence, combine the recovery path fragment sequences sequentially to generate a recovery path record sequence arranged by service configuration identifier. Maintaining the order of service configuration identifiers and time indexes of the recovery path record sequence, reorganize the recovery path record sequence into a recovery path evolution sequence. Maintaining the order of service configuration identifiers and time indexes of the recovery path evolution sequence, arrange the recovery path evolution sequence to generate a recovery path simulation result sequence.

[0148] Based on the recovery path simulation result sequence, the set of recovery cost settlement commitments registered by the smart contract is read, and the recovery path simulation result sequence and the target recovery cost sequence are combined according to the business configuration identifier, while maintaining the order of the business configuration identifier, to generate a recovery cost settlement commitment update sequence.

[0149] The generation of the recovery cost settlement commitment update sequence specifically includes:

[0150] Read the recovery path simulation result sequence in order of business configuration identifier, and record the recovery path simulation result corresponding to each business configuration identifier as a recovery path simulation record sequence; read the target recovery cost sequence in order of business configuration identifier, and record the target recovery cost corresponding to each business configuration identifier as a target recovery cost record sequence; maintain the consistency between business configuration identifier and time index, match the recovery path simulation record sequence with the target recovery cost record sequence item by item to generate a recovery cost path pair sequence; based on the recovery cost path pair sequence, read the recovery cost settlement commitment set registered by the smart contract, extract the corresponding recovery cost settlement commitment record according to the business configuration identifier, and form a recovery cost settlement commitment record sequence; maintain the order of business configuration identifier and time index, combine the recovery cost path pair sequence with the recovery cost settlement commitment record sequence item by item to generate a recovery cost settlement commitment update sequence;

[0151] The recovery cost settlement commitment update sequence is submitted to the smart contract, which then updates the recovery cost settlement commitment set and generates a settlement status sequence in the order of the payment record sequence.

[0152] The generation of the settlement status sequence specifically includes:

[0153] Read the recovery cost settlement commitment update sequence in the order of business configuration identifiers, and record the recovery cost settlement commitment update record corresponding to each business configuration identifier as a recovery cost settlement commitment update record sequence; submit the recovery cost settlement commitment update record sequence to the smart contract, and the smart contract updates the recovery cost settlement commitment set to form a recovery cost settlement commitment update result sequence; read the recovery cost settlement commitment update result sequence in the order of payment record sequence, and record the recovery cost settlement commitment update result corresponding to each payment record as a settlement result record sequence; maintain the payment record order and business configuration identifier order in the settlement result record sequence, arrange the settlement result record sequence in the order of the payment record sequence, and generate a settlement status sequence.

[0154] In this embodiment, the generation of the replayable verification closed loop specifically includes:

[0155] Receive audit requests, determine the audit time range, filter business configuration event records from the business configuration event sequence according to the audit time range, and generate audit business configuration event sub-sequences by arranging them in order of business configuration identifier and time index.

[0156] Based on the audit business configuration event subsequence, the running status records are filtered from the running status data according to the audit time range, and aligned according to the time index order of the audit business configuration event subsequence to generate an audit running status data sequence.

[0157] Based on the audit business configuration event subsequence and the audit operation status data sequence, the structure status generation, structure disturbance representation generation and recovery cost generation are executed sequentially, and the recovery cost sequence is recalculated according to the time index order of the audit business configuration event subsequence.

[0158] The generation of the recovery cost sequence specifically includes:

[0159] Based on the audit business configuration event subsequence, the configuration change type, configuration scope, and configuration effectiveness conditions corresponding to each business configuration event are parsed in time index order. Combined with the operation status records at corresponding time points in the audit operation status data sequence, structural status descriptions under each time index are generated, forming a structural status sequence. For the structural status descriptions corresponding to adjacent time indices in the structural status sequence, the structural status change is calculated based on the configuration change type and configuration scope, generating structural disturbance representations characterizing the magnitude and direction of structural changes, forming a structural disturbance representation sequence in time index order. Based on the structural disturbance representation sequence, according to the preset recovery cost calculation rules, each structural disturbance representation is mapped to a corresponding recovery cost, generating a recovery cost record corresponding to the time index. The recovery cost records generated under each time index are arranged in time index order of the audit business configuration event subsequence to form a recalculated recovery cost sequence.

[0160] Based on the recalculated recovery cost sequence, the period-level recovery cost records are extracted from the business configuration bill data according to the business configuration identifier to form audit business configuration bill sub-data. The settlement status records are extracted from the settlement status sequence according to the business configuration identifier and time index to form audit settlement status sub-sequence.

[0161] Based on the recalculation recovery cost sequence, audit business configuration bill sub-data and audit settlement status sub-sequence, the recalculation recovery cost record, bill period-level recovery cost record and settlement status record are compared item by item according to the business configuration identifier and time index to generate a consistency verification record sequence;

[0162] The generation of the consistency verification record sequence specifically includes:

[0163] Based on the recalculation recovery cost sequence, audit business configuration bill sub-data, and audit settlement status sub-sequence, the three are associated and matched according to the business configuration identifier to establish the correspondence between recalculation recovery cost records, billing period-level recovery cost records, and settlement status records under the same business configuration identifier, forming a business configuration identifier-level comparison set. For each business configuration identifier-level comparison set, the recalculation recovery cost records and billing period-level recovery cost records are compared item by item according to the time index order to determine the consistency or inconsistency between the recovery cost recalculation results and the billing period records under each time index, generating a recovery cost consistency judgment result. Based on the recovery cost consistency judgment result, combined with the settlement status record under the corresponding time index, it is determined whether the billing period-level recovery cost has been settled within the corresponding settlement period or is in an abnormal settlement state, generating a settlement status consistency judgment result. The recovery cost consistency judgment results generated under each time index are combined with the settlement status consistency judgment results to form a consistency verification record representing the consistency relationship between the recalculation recovery cost, billing period-level recovery cost, and settlement status, and arranged in the time index order to generate a consistency verification record sequence.

[0164] Based on the consistency verification record sequence, the consistency verification information is summarized according to the audit time range and the business configuration identifier order to generate the bill consistency verification result, forming a replayable verification closed loop for business configuration bill payment and structure recovery;

[0165] The generation of the replayable verifiable closed loop specifically includes:

[0166] Based on the consistency verification record sequence, the consistency verification records under each time index are grouped and summarized according to the audit time range and the order of business configuration identifiers to form an audit consistency verification information set for the corresponding business configuration identifier. For each business configuration identifier's audit consistency verification information set, the distribution of consistent and inconsistent state records under each time index is statistically analyzed to generate a verification result representing the consistency of bill payment and structural recovery of the business configuration within the audit time range. Based on the generated bill consistency verification result, the audit business configuration event subsequence, audit operation status data sequence, and recovery cost recalculation sequence are associated to construct a verification path that can reproduce the business configuration change, structural state evolution, and recovery cost calculation process according to the audit time range. The verification path is bound and stored with the bill consistency verification result, so that in subsequent audits or reviews, the structural state generation, structural disturbance representation generation, recovery cost recalculation, and consistency verification processes can be repeatedly executed based on the same audit time range and business configuration identifier, forming a replayable verification closed loop for business configuration bill payment and structural recovery.

[0167] Example 1:

[0168] To verify the feasibility of this invention in practice, it was applied to the business configuration management and expense settlement system within a provincial government service center. This center adjusts service window arrangements, access system parameters, cross-departmental collaboration relationships, and data exchange channels weekly based on business operations. Frequent business configuration changes lead to continuous changes in the underlying operational structure. Previously, in expense settlement and recovery work, bills only recorded the costs incurred due to configuration changes and the time spent on manual processing, failing to reflect which changes caused structural shifts, which recovery operations truly brought the system back to a stable operating state, and making it impossible to verify whether the recovery was completed according to the bill after payment. This resulted in problems such as payment completion without complete structural recovery, multiple extensions of billing cycles, difficulties in assigning responsibility, and the inability to provide a clear chain of evidence during audits. The government service center has long relied on offline records and manual reconciliation, which is time-consuming, inaccurate, and often makes it impossible to trace the actual recovery path after disputes arise. Auditors also lack the basis to determine whether the bill corresponds to the actual recovery status.

[0169] In practical applications, this invention continuously collects snapshots of service operation structures and corresponding service configuration operations within the information-based operating environment of government service centers. Every morning, the system automatically scans the service window layout, internal service links, and external system access status to form a time-continuous baseline structural state sequence. When maintenance personnel adjust service configurations before the morning peak, such as changing service window connection relationships, adjusting access interface rate limiting strategies, or modifying cross-departmental data synchronization rules, this invention automatically applies the service configuration events to the baseline structural state sequence in chronological order and generates a structural state sequence. Assuming that a configuration adjustment increases the risk of backend data link interruption, this invention can extract structural disturbance representations through structural difference calculations and combine them with on-site collected operational status data, such as fluctuations in user queuing time, changes in internal processing latency, and a tendency for concurrency capacity to decline, to generate a recovery cost sequence. This recovery cost not only includes the structural offset impact caused by configuration but also reflects observable performance deviations at the operational level, thereby achieving a quantitative expression of the impact of structural changes on reality.

[0170] In the operational environment of the government service center, a billing cycle is formed every ten days. This invention aggregates the continuous recovery cost sequence into a billing cycle-level recovery cost record, then generates business configuration bill data, and uses a compression method to generate a bill summary which is written into the blockchain ledger. The smart contract registers the set of recovery cost repayment commitments. When the finance department initiates a payment request based on the bill, this invention maps the recovery cost corresponding to the payment amount to the structural recovery strategy, simulates the recovery path, and generates a repayment status sequence. This process can clearly show which recovery content has been fulfilled and which is still in execution after the bill payment is completed, so that the payment result is strictly bound to the system recovery status. Unlike the past, where settlement was completed upon payment, this invention ensures that the payment process itself promotes structural recovery, rather than just being a financial settlement behavior.

[0171] After six months of operation, the government service center introduced a third-party auditing firm to audit the entire operation process. The replayable verification closed-loop function of this invention was invoked at the start of the audit. After the auditors input the time range, the system automatically filtered the business configuration events and operational status data within that time period, regenerated the recalculated recovery cost sequence, and compared it with the business configuration bill data and settlement status sequence generated during the period. Auditors did not need to rely on verbal explanations from maintenance personnel or organize a large number of business records to obtain a complete link to determine whether the bill was generated based on the actual recovery cost, whether the payment strictly corresponded to the settlement commitment, which recovery contents were indeed completed, and which were still not achieved. This recalculation and comparison mechanism effectively prevented situations such as opaque bill generation, mismatched recovery costs, and lack of traceable evidence in the audit. By comparing the time consistency between the bill, settlement status, and recalculated recovery cost, the auditing firm could clearly point out the recovery execution status and the degree of fulfillment of related commitments within any time period, thus having sufficient persuasiveness in legal and compliance verification.

[0172] In this scenario, the present invention effectively addresses three long-standing problems: First, billing data fails to reflect the true cost of structural recovery. The present invention expresses the recovery cost by coupling structural disturbances with operational status, thus linking billing content with the actual system state. Second, there is a lack of confirmation path for recovery fulfillment after payment. The present invention enables payment to drive recovery through repayment commitment updates and repayment status sequences. Third, the authenticity of bills cannot be verified during the audit process. The present invention achieves full-chain verification of bills, recovery processes, and structural evolution through a replayable verification closed loop. These capabilities have demonstrated their value in two consecutive audits of the government service center and in cross-departmental clearing. Audit institutions can fully track the correspondence between billing entries and system recovery during use, no longer relying on experience disputes or external explanatory documents, making bill payment a verifiable execution closed loop, significantly improving transparency and provability.

[0173] Table 1. Comparison of key indicators between the method of this invention and traditional bill payment methods

[0174]

[0175] As shown in Table 1, this invention achieves stable but not excessively exaggerated performance improvements in multiple stages, including bill generation, recovery progress, and audit alignment. These improvements work together to create a traceable and re-verifiable technical link between bill payment and structural recovery. Regarding bill generation and settlement efficiency, traditional methods rely on manual confirmation, cross-team communication, and configuration impact backtracking, resulting in a longer bill generation cycle. This invention, by generating a recovery cost sequence based on structural perturbation representation, provides a direct source of evidence for bill entries, reducing the number of round trips for manual comparison. This shortens the bill generation cycle from 9.6 working days to 8.1 working days, maintaining near-period performance for two consecutive billing cycles. While the reduction in time is not substantial, it is concentrated in the manual confirmation and cross-business group synchronization stages, which are often the most likely bottlenecks. Therefore, this improvement demonstrates that the present invention effectively reduces the confirmation overhead caused by unclear bill entry sources. In terms of payment completion to structural recovery confirmation, the present invention binds the target recovery cost with the simulation results of the recovery path, making "payment completion" no longer an isolated action, but a traceable constraint that can trigger the recovery process. This reduces the repeated steps of reconciling bills back and forth during the recovery confirmation process, shortening the overall settlement to recovery confirmation cycle by approximately 13.7%. In long-term operation, this is beneficial for compressing the lag window of business recovery.

[0176] The improved consistency between billing content and structural restoration behavior further highlights the effectiveness of this invention. By optimizing the generation path of the restoration cost sequence, this invention transforms billing entries from mere monetary records into entries that incorporate the degree of structural disturbance and the cost resulting from operational status. This provides a structural basis for billing entry formation, increasing the matching degree from 0.68 to 0.74. While this increase is small, it coincides with the decreasing trend in the rate of manual interpretation required for billing entries, which dropped from 29.7% to 22.6%. These two indicators mutually reinforce each other, demonstrating that this invention makes billing entries more understandable, reduces reliance on experience-based judgments in the interpretation process, and lowers the probability of billing disputes. Simultaneously, the restoration cost deviation rate decreased from 6.7% to 5.8%, indicating a closer convergence in the error between billing amounts and structural restoration costs. This trend can reduce business and financial discrepancies caused by accumulated budget estimation errors during the billing period.

[0177] The audit data further illustrates the supporting role of the bill payment closed loop in bill consistency and recalculation. In traditional methods, audits often require a large amount of supplementary information to trace the source of bill entries. However, through this invention, after recalculating and comparing the recovery cost sequence, settlement status sequence, and business configuration bill data, the amount of supplementary materials is reduced by approximately 21.4%. This means that the audit process no longer relies on a large amount of corroborating information. When the structural relationship between the generation of bill entries and settlement entries can be traced and recalculated during the audit, the audit backtracking path is shorter, resulting in a first-pass rate of 89.1%. Although this increase is not drastic, it is more in line with the gradual improvement approach in the actual operating environment and also reflects the consistent trend of decreasing audit costs and increasing bill transparency.

[0178] Regarding risk and anomaly handling capabilities, the 33.3% decrease in the missed detection rate indicates that the two-way comparison mechanism between the recovery cost repayment commitment set and the recovery path simulation results can effectively expose incomplete recovery items. Especially under the condition of bill payment-driven recovery execution, the comparison generates a repayment status sequence, making it easier to identify recovery omissions at the end of the billing period. At the same time, this invention does not rely entirely on structural models to predict recovery results, but adopts a method of associating bill data with recovery cost. Therefore, the improvement in the deviation rate is moderate, which reflects a real improvement trend within the scope of authority, rather than an artificially high performance brought about by model enhancement.

[0179] In summary, the improvements reflected in the data in the table are not extreme optimizations, but rather overall performance improvements achieved through the gradual accumulation of "clarification of bill sources, traceability of recovery paths, correlation between payment and recovery behaviors, and recalculation of bills." This establishes a technical closed loop between bill payment behavior and the structural recovery process, thereby reducing bill disputes, improving internal collaboration efficiency, reducing audit and supplementary evidence pressure, and enabling the recovery execution path to be replayed. This improvement method demonstrates that the core advantage of this invention is not to obtain exaggerated, de-managed values, but to elevate the bill payment behavior from a "monetary event" to a "structural recovery-driven event," thus forming a sustainable and applicable billing cycle evolution mechanism.

[0180] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention.

Claims

1. A blockchain-based business configuration bill payment system, characterized in that, include: The business configuration event module is used to generate business configuration event sequences and structure state sequences; The structural perturbation module is used to generate structural perturbation representations based on the structural state sequence and the baseline structural state sequence; The recovery cost module is used to generate a recovery cost sequence by combining structural disturbance representation and operational status data; the service configuration bill module is used to generate service configuration bill data based on the recovery cost sequence. The repayment commitment registration module is used to write business configuration bill data into the blockchain ledger and register the set of recovery cost repayment commitments; the repayment status module is used to update the set of recovery cost repayment commitments based on payment requests and generate a repayment status sequence; the consistency verification module is used to recalculate the business configuration bill based on the business configuration event sequence, running status data and repayment status sequence, and generate a bill payment bill bill consistency verification result.

2. The blockchain-based business configuration bill payment system according to claim 1, characterized in that, The modules are interconnected as follows: Business configuration operations in the operational environment are collected, a business configuration event sequence is generated by time, a snapshot of the operational structure is collected, a baseline structure state sequence is generated by time, and the business configuration event sequence is applied to the baseline structure state sequence by time-indexing to generate a structure state sequence; the structure state sequence and the baseline structure state sequence are combined by performing structural difference calculations at the same time index to generate a structure disturbance representation; the structure disturbance representation is combined with the operational state data collected under the corresponding time index to generate a recovery cost sequence; the recovery cost sequence is aggregated by billing period to generate recovery cost records, and business configuration billing data is generated; The business configuration bill data is compressed to generate a bill summary, which is written to the blockchain ledger. The smart contract registers the set of recovery cost repayment commitments. Upon receiving a payment request, the payment amount is matched with the business configuration bill data to generate a target recovery cost. The simulation results of the recovery path driven by the target recovery cost are used to update the set of recovery cost repayment commitments to generate a repayment status sequence. During auditing, the business configuration event sequence, running status data, and repayment status sequence are read to regenerate the recalculated recovery cost sequence. This sequence is then compared with the business configuration bill data and the repayment status sequence to generate a bill consistency verification result, forming a replayable verification closed loop for business configuration bill payment and structural recovery.

3. The blockchain-based business configuration bill payment system according to claim 2, characterized in that, The generation of the structural state sequence specifically includes: collecting business configuration operations in the business operation environment, sorting the collected business configuration operations according to their occurrence time, and generating a business configuration event sequence; collecting business operation structure snapshots, sorting the collected business operation structure snapshots according to their collection time, and generating a baseline structural state sequence; using the time index of the business configuration event sequence as a unique alignment benchmark, rearranging the structural states in the baseline structural state sequence, with each business configuration event corresponding to a unique baseline structural state, and generating a time-aligned baseline structural state sequence; applying the business configuration events under the corresponding time index to the corresponding baseline structural states in the time-aligned baseline structural state sequence according to the time index order of the business configuration event sequence, performing structural update processing, and generating structural state update results under the corresponding time index; arranging the structural state update results generated under each time index according to the time index order, and generating a structural state sequence.

4. A blockchain-based business configuration bill payment system according to claim 2, characterized in that, The generation of the structural perturbation representation specifically includes: reading the structural state sequence and the baseline structural state sequence, and determining the time index correspondence between the structural state sequence and the baseline structural state sequence; according to the time index correspondence, pairing the structural states under each time index in the structural state sequence with the baseline structural states under the same time index in the baseline structural state sequence one by one to generate a set of structural state pairs; performing structural difference calculation on each structural state pair in the set of structural state pairs, extracting the structural change results between the structural state and the corresponding baseline structural state, and generating the structural difference results under the corresponding time index; associating and organizing the structural difference results generated under each time index according to the time index to form a structural difference sequence arranged by time index; and performing unified representation processing on the structural difference sequence to organize the structural change results in the structural difference sequence into a structural perturbation representation.

5. A blockchain-based business configuration bill payment system according to claim 2, characterized in that, The generation of the recovery cost sequence specifically includes: reading the structural perturbation representation in time index order, recording the structural perturbation value corresponding to each time index as the structural offset corresponding to that time index in the structural perturbation recording sequence; collecting operational status data within the same time index range as the structural perturbation recording sequence, recording the operational status data corresponding to each time index as the operational cost impact amount corresponding to that time index in the operational status recording sequence; maintaining time index consistency, combining the structural perturbation recording sequence and the operational status recording sequence item by item under each time index to generate a combined recording sequence containing the structural offset and the operational cost impact amount; and maintaining the combined recording sequence. The time index order of the sequence remains unchanged. The structural offset and operational cost impact of the combined records under each time index are processed to extract costs, generating a recovery cost record sequence arranged by time index. Within the billing period, the time index order of the recovery cost record sequence is maintained, and the recovery cost records corresponding to multiple time indices are aggregated at the billing period level to generate a billing period-level recovery cost fragment. According to the order of business configuration identifiers in the business configuration event sequence, multiple billing period-level recovery cost fragments are combined sequentially. Each business configuration identifier corresponds to a unique billing period-level recovery cost value. The time index relationship between the business configuration identifier and the recovery cost value is maintained to generate a recovery cost sequence.

6. A blockchain-based business configuration bill payment system according to claim 2, characterized in that, The generation of the service configuration billing data specifically includes: maintaining the time index order of the recovery cost sequence, grouping the recovery cost sequence according to the service configuration identifier to form a recovery cost grouping sequence divided by the service configuration identifier; setting a billing period time range, selecting recovery cost values ​​whose time index belongs to the billing period time range in the recovery cost grouping sequence, and aggregating them sequentially according to the service configuration identifier order to generate a billing period-level recovery cost fragment sequence; maintaining the correspondence between the service configuration identifier and the billing period time range of the billing period-level recovery cost fragment sequence, combining the billing period-level recovery cost fragment sequence according to the service configuration identifier order to generate a billing period-level recovery cost record sequence; maintaining the order of the service configuration identifier and the time index order of the billing period-level recovery cost record sequence, compressing the billing period-level recovery cost record sequence sequentially into a billing period billing entry sequence containing multiple billing period-level recovery cost records; based on the billing period billing entry sequence, maintaining the correspondence between the service configuration identifier and the billing period time range, compressing the billing period billing entry sequence into a billing entry set divided by the service configuration identifier to generate service configuration billing data.

7. A blockchain-based business configuration bill payment system according to claim 2, characterized in that, The registration and recovery cost settlement commitment specifically includes: reading the corresponding billing period-level recovery cost record from the business configuration billing data according to the business configuration identifier, keeping the order of the business configuration identifier and the billing period time range unchanged, and generating a billing period billing entry sequence; performing compression processing on the billing period billing entry sequence, encoding and concatenating multiple billing period billing entries according to a preset field order, removing duplicate billing period fields and redundant description fields, and generating a bill summary; writing the bill summary into the blockchain ledger, generating an on-chain bill summary entry corresponding to the bill summary, and keeping the on-chain bill summary entry consistent with the billing period time range and the order of the business configuration identifier. The process involves: extracting period-level recovery cost records according to the order of business configuration identifiers in the business configuration billing data; combining the period-level recovery cost record corresponding to each business configuration identifier with the on-chain billing summary entry to generate a sequence of recovery cost settlement entries arranged by business configuration identifier; aggregating the recovery cost settlement entry sequence to form a recovery cost settlement commitment set; submitting the recovery cost settlement commitment set to the smart contract, which then registers the recovery cost settlement commitment set in the blockchain ledger; binding the recovery cost settlement commitment corresponding to each business configuration identifier with the on-chain billing summary entry to complete the registration of the recovery cost settlement commitment set.

8. A blockchain-based business configuration bill payment system according to claim 2, characterized in that, The generation of the settlement status sequence specifically includes: receiving payment requests and parsing payment amounts, maintaining the correspondence between payment requests and business configuration identifiers, arranging them in the order of payment requests, and generating a payment record sequence; based on the payment record sequence, matching the payment amounts with the period-level recovery cost records arranged by business configuration identifiers in the business configuration billing data item by item to generate a target recovery cost sequence; based on the target recovery cost sequence, matching the target recovery cost with the structural status sequence item by item according to business configuration identifiers and time indices, arranging them in the order of business configuration identifiers, and generating a recovery path simulation result sequence; based on the recovery path simulation result sequence, reading the set of recovery cost settlement commitments registered by the smart contract, combining the recovery path simulation result sequence with the target recovery cost sequence according to business configuration identifiers, maintaining the order of business configuration identifiers, and generating a recovery cost settlement commitment update sequence; submitting the recovery cost settlement commitment update sequence to the smart contract, which updates the set of recovery cost settlement commitments and generates a settlement status sequence in the order of the payment record sequence.

9. A blockchain-based business configuration bill payment system according to claim 2, characterized in that, The generation of the replayable verification closed loop specifically includes: receiving an audit request, determining the audit time range, filtering business configuration event records from the business configuration event sequence according to the audit time range, and arranging them according to the business configuration identifier and time index to generate an audit business configuration event sub-sequence; based on the audit business configuration event sub-sequence, filtering operating status records from the operating status data according to the audit time range, aligning them according to the time index order of the audit business configuration event sub-sequence, and generating an audit operating status data sequence; according to the audit business configuration event sub-sequence and the audit operating status data sequence, sequentially executing structure status generation, structure disturbance representation generation, and recovery cost generation, and regenerating the recalculated recovery cost sequence according to the time index order of the audit business configuration event sub-sequence; and performing recovery based on the recalculated recovery. The cost sequence extracts period-level recovery cost records from the business configuration billing data according to the business configuration identifier, forming audit business configuration billing sub-data. It also extracts settlement status records from the settlement status sequence according to the business configuration identifier and time index, forming an audit settlement status sub-sequence. Based on the recalculated recovery cost sequence, the audit business configuration billing sub-data, and the audit settlement status sub-sequence, the recalculated recovery cost records, period-level recovery cost records, and settlement status records are compared item by item according to the business configuration identifier and time index to generate a consistency verification record sequence. Based on the consistency verification record sequence, consistency verification information is summarized according to the audit time range and the order of the business configuration identifier to generate billing consistency verification results, forming a replayable verification closed loop for business configuration billing payment and structural recovery.

Images