A global carbon management and life cycle accounting system

Abstract

This invention discloses a comprehensive carbon management and lifecycle accounting system, relating to the field of carbon emission data management technology. It includes: a carbon flow unit library storing carbon flow units containing subject identifiers, spatial coordinates, timestamps, emission source type codes, and carbon emission values; a multi-level ledger aggregation engine extracting carbon flow units from the library, aggregating them level by level to generate carbon ledger views at each level; a cross-regional verification engine calculating hash digests of carbon flow units and writing them into a blockchain ledger; and outputting verification results by comparing hash digest consistency. A construction phase carbon footprint accounting unit collects data on building material transportation, construction machinery, and construction site energy consumption to calculate the total carbon emissions during the construction phase. An operation phase carbon footprint interface receives external operation data and concatenates it with construction phase data in chronological order to form a lifecycle carbon footprint sequence. This invention achieves unified collection, reliable verification, and full traceability of carbon data in scenarios where multi-level and lifecycle management coexist.

Description

Technical Field

[0001] This invention relates to the field of carbon emission data management technology, specifically a comprehensive carbon management and life-cycle accounting system. Background Technology

[0002] As the goals of carbon peaking and carbon neutrality are gradually achieved, the need for unified management of carbon emission data by management entities at all levels is becoming increasingly urgent. In carbon data management practice, carbon data from different levels of management entities, different regions, and different stages of the construction industry are usually stored in their own independent systems. The data formats are not uniform and the accounting standards are inconsistent, which makes it difficult to achieve unified collection, cross-verification, and full life cycle traceability of carbon data across the entire domain.

[0003] Several relevant technical solutions already exist. For example, the invention patent with prior art publication number CN121581884A, "A Method and System for Full Lifecycle Management of Enterprise Carbon Emission Data," proposes a carbon data governance solution for a single enterprise. It achieves multi-source data alignment through a unified time window, generates reliable carbon event frames, and constructs a path map for duplicate metering identification. Another example is the invention patent with prior art publication number CN121328890A, "A Method for Adaptive Carbon Emission Footprint Statistical Accounting in the Construction Phase," which improves the carbon emission accounting for the construction phase of a single building project. It calculates carbon emissions by clearly defining time, geography, and activity boundaries, using sub-items and sub-sections as units.

[0004] The above solutions are designed for specific scenarios such as enterprise-level carbon data management or single project construction phase accounting. None of them involve the decomposition of carbon indicators and automatic data aggregation among multi-level management entities, nor do they involve cross-regional carbon data sharing and verification mechanisms.

[0005] In summary, the technical problem this invention aims to solve is: how to achieve unified representation and cross-domain connectivity of carbon data in complex management scenarios involving multiple levels of management entities, cross-regional operations, and the entire building lifecycle. Specifically, carbon data from different levels, regions, and stages forms data silos due to differences in data format, accounting methods, and storage methods. Existing technologies lack a data model and system architecture capable of uniformly representing these heterogeneous data and achieving automatic cross-level aggregation and cross-regional cross-verification.

[0006] To address these issues, this invention proposes a comprehensive carbon management and life-cycle accounting system. By constructing a unified data model, it integrates multi-level ledgers, cross-regional verification, and building life-cycle accounting into the same technical framework. Summary of the Invention

[0007] The purpose of this invention is to overcome the shortcomings of existing technologies and provide a comprehensive carbon management and life-cycle accounting system. By constructing a data model with carbon flow units as the core and coordinating a multi-level ledger aggregation engine, a cross-regional verification engine, and a construction and operation carbon footprint accounting unit, it can unify and aggregate scattered heterogeneous carbon data into homogeneous data, realize the automatic decomposition and aggregation of carbon emission indicators at each level, the reliable cross-verification of cross-regional carbon data, and the seamless splicing and accounting of the carbon footprint of buildings throughout their entire life cycle.

[0008] To solve the above-mentioned technical problems, the present invention provides the following technical solution: a comprehensive carbon management and life-cycle accounting system, the system comprising: The carbon flow unit library is used to store carbon flow units. Each carbon flow unit contains five fields: subject identifier, spatial coordinates, timestamp, emission source type code, and carbon emission value. The carbon flow unit library serves as the system's sole data source, providing unified carbon data read and write services to all modules. The multi-level ledger aggregation engine is used to extract carbon flow units from the carbon flow unit library based on the subject identifier and spatial coordinates, aggregate them level by level according to the subject hierarchy, and generate carbon ledger views at each level. The cross-regional verification engine is used to extract the carbon emission values ​​of carbon stream units to be verified from the carbon stream unit library, calculate the hash digest and write it into the blockchain notarization ledger, and compare the consistency of hash digests of carbon stream units from different sources and output the verification results. The carbon footprint accounting unit during the construction phase is used to collect data on the weight and distance of building material transportation, fuel consumption of construction machinery, and energy consumption at the construction site, and to calculate the total carbon emissions during the construction phase. The carbon footprint interface for the operation phase is used to receive external carbon emission data for the operation phase and to concatenate the total carbon emission data for the construction phase with the carbon emission data for the operation phase in chronological order to form a full life cycle carbon footprint sequence.

[0009] Furthermore, the data structure of each carbon stream unit in the carbon stream unit library is a quintuple ( ),in This serves as a unique identifier for the carbon flow unit. As a primary identifier for generating carbon emissions, Spatial coordinates of the carbon emission sites For the timestamp of carbon emissions, Code the emission source type. This represents carbon emissions, measured in kgCO2e.

[0010] The quintuple data structure unifies the smallest granularity of global carbon data, ensuring that carbon data from different modules have a consistent format when entering the database.

[0011] Furthermore, the multi-level ledger aggregation engine is configured to perform the following steps; The hierarchical relationship between storage entities; Based on the total carbon emission control targets set by the higher-level entities, and combined with the historical carbon emission proportions of each lower-level entity, the decomposed indicator values ​​for each lower-level entity are calculated using the following formula: in Let be the decomposition index value of the i-th lower-level subject. The total carbon emission control target set by the higher-level entity. Let n be the historical carbon emissions of the i-th lower-level entity, and n be the total number of lower-level entities. This is the sum of the historical carbon emissions of all subordinate entities; The overall target is automatically quantified to each lower-level entity, providing a benchmark for subsequent progress tracking; Based on hierarchical relationships, all carbon flow units belonging to the same superior entity are extracted from the carbon flow unit library. The carbon emission values ​​are summed and summarized according to spatial coordinates and emission source type codes to generate a carbon ledger view of the superior entity. When a new carbon flow unit is added to the carbon flow unit library, the summation and summary are re-executed to update the carbon ledger view.

[0012] Furthermore, the cross-regional verification engine is configured to perform the following steps; The carbon emission values ​​and timestamps of carbon flow units are extracted from the carbon flow unit library, and a hash digest is calculated using the SHA-256 algorithm. The hash digest is then associated with the unique identifier of the carbon flow unit and written into the blockchain evidence ledger. Upon receiving an external verification request, the system extracts a first set of carbon flow units from the carbon flow unit library based on the target entity identifier and time range in the verification request. It calculates the sum of carbon emission values ​​of each carbon flow unit in the first set of carbon flow units as the first summary value. It reads the hash digest set of the same target entity identifier and the same time range that has been stored from the blockchain notarization ledger. It decodes and restores the hash digest set to obtain a second set of carbon flow units. It calculates the sum of carbon emission values ​​of each carbon flow unit in the second set of carbon flow units as the second summary value. It compares the first summary value with the second summary value. If the absolute value of the deviation is greater than a preset threshold, it is marked as a verification anomaly. Through the on-chain and off-chain bidirectional comparison of hash digests, the superior management entity has the technical capability to independently verify the authenticity of the data reported by the subordinate. Record the verification initiator identifier, target entity identifier, verification time range, and verification result for each verification operation, and write the verification log to the blockchain evidence ledger.

[0013] Furthermore, the preset threshold is 5% of the second aggregate value, where the 5% threshold serves as a deviation tolerance boundary, providing a reasonable tolerance space for unavoidable system errors during the carbon emission value measurement and calculation process, and avoiding frequent triggering of invalid verification due to minor deviations.

[0014] Furthermore, the construction phase carbon footprint accounting unit is configured to perform the following steps; Obtain the transport weight of the i-th type of building material Transportation distance And the carbon emission factors of the corresponding transportation methods for this type of building material ,according to Calculate the total carbon emissions from building material transportation Where i is the building material type number, i=1,2,…,n, and n is the total number of building material types. The unit of measurement is t. The unit of measurement is km. The unit of measurement is kgCO2e / t·km. The unit of measurement is kgCO2e; Obtain the fuel consumption of the j-th type of construction machinery. and the carbon emission factor of this type of fuel ,according to Calculate the total carbon emissions from fuel used in construction machinery Where j is the serial number of the construction machinery type, j=1,2,…,m, and m is the total number of construction machinery types. The unit of measurement is L or kg. The unit of measurement is kgCO2e / L or kgCO2e / kg. The unit of measurement is kgCO2e; Obtain the consumption of the kth energy source. and the carbon emission factor of this type of energy ,according to Calculate the total energy consumption and carbon emissions at the construction site Where k is the energy type index, k=1,2,…,p, and p is the total number of energy types. The unit of measurement is kWh or m³. The unit of measurement is kgCO2e / kWh or kgCO2e / m³. The unit of measurement is kgCO2e; Will and Add them together to get the total carbon emissions during the construction phase. .

[0015] Will and Add them together to get the total carbon emissions during the construction phase. The calculation results of the three emission stages during the construction phase are combined into a unified total, so that carbon emissions during the construction phase can participate in the whole life cycle splicing with a single value, avoiding the confusion of standards caused by the parallel transmission of data from multiple stages.

[0016] Furthermore, the carbon footprint accounting unit for the construction phase is also configured to: calculate the total carbon emissions during the construction phase. By combining the main identifier, spatial coordinates, construction time range, and emission source type code of the construction project, carbon flow units for the construction phase are generated and stored in the carbon flow unit library. The construction time range is based on the project start date as the start timestamp and the project completion date as the end timestamp. The calculation results of the construction phase are converted into carbon flow unit format, so that the carbon data of the construction phase and the carbon data of other modules share the same underlying data structure, providing a unified data entry point for full life cycle splicing and cross-regional verification.

[0017] Furthermore, the carbon footprint interface for the operational phase is configured to perform the following steps; After converting the externally input carbon emission data during the operation phase into carbon flow unit format, it is stored in the carbon flow unit library. The carbon flow unit of the carbon emission data during the operation phase includes the main identifier of the operation project, the spatial coordinates of the operation project, the operation timestamp, the operation emission source type code, and the operation carbon emission value. Based on the same project entity identifier, carbon flow units for the construction phase and carbon flow units for the operation phase are extracted from the carbon flow unit library, arranged in chronological order of timestamps, to generate the full life cycle carbon footprint time series of the project. By sequentially linking the construction carbon flow units and the operation carbon flow units, a complete carbon footprint timeline from the start of the project to the end of operation is formed.

[0018] Furthermore, the system also includes a hierarchical permission management unit, which stores three permission roles: data producer role, data manager role, and data supervisor role. The data producer role is configured to have the authority to write carbon stream units to the carbon stream unit library and the authority to query the carbon stream units of this entity. The data manager role is configured to have the authority to query all carbon flow units within its own and its subordinate jurisdictions and to generate carbon ledger views within its jurisdiction. The data supervisor role is configured to have the authority to query aggregated statistical data of carbon stream units across the entire domain and the authority to initiate verification requests to the cross-regional verification engine, but not the authority to query detailed data of individual carbon stream units. The hierarchical permission management unit, through the permission isolation of the three roles, presents differentiated views of data in the same carbon stream unit library to users at different levels, thereby achieving a balance between the need for cross-regional data sharing and the protection of detailed data privacy.

[0019] Furthermore, the system also includes an automatic report generation unit configured to perform the following steps: Store preset templates for total carbon emissions summary table, carbon emission intensity statistics table, and carbon index decomposition completion comparison table. Each template includes data field mapping rules and report layout rules. Based on the data field mapping rules, the carbon emission values ​​of the corresponding fields are extracted from the carbon flow unit library, and grouped and summarized by subject identifier, spatial coordinates or timestamp. Data is directly read from the carbon flow unit library and grouped and statistically analyzed according to the template rules, so that the report data is always based on the latest status of the carbon flow unit library and avoids data inconsistency caused by multi-level transmission. The grouped and summarized data is then filled into the report template according to the report layout rules to generate an exportable carbon emission report.

[0020] Compared with existing technologies, this comprehensive carbon management and life-cycle accounting system has the following advantages: This invention constructs a carbon flow unit data structure consisting of subject identifier, spatial coordinates, timestamp, emission source type code, and carbon emission value. This unifies heterogeneous carbon data generated at different levels, regions, and stages into basic data units with the same format. This allows the accounting results during the construction phase and external data during the operation phase to be stored in the same database in the form of carbon flow units. This fundamentally eliminates the cross-domain communication barriers caused by inconsistencies in data format and accounting standards, and realizes unified representation and fusion of carbon data in scenarios where multi-level management entities and the entire life cycle of buildings coexist.

[0021] This invention integrates multi-level ledger aggregation, cross-regional verification, construction phase accounting, and operation phase integration into a carbon flow unit library. Each module reads and writes carbon flow units through a unified data interface, avoiding direct transfer of raw data files between modules. At the same time, hierarchical permission management enables different roles to have different views of the same database, ensuring the consistency and auditability of carbon data in the collection, verification, and traceability processes, while also reducing the risk of data inconsistency and redundant construction costs caused by multi-system integration.

[0022] Other advantages, objectives and features of the invention will be set forth in part in the description which follows, and in part will be apparent to those skilled in the art from the following examination or study, or may be learned from the practice of the invention. Attached Figure Description

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

[0024] Figure 1 This is a structural block diagram of the comprehensive carbon management and life-cycle accounting system of the present invention; Figure 2 This is a schematic diagram of the carbon flow unit quintuple data structure of the present invention; Figure 3 This is a schematic diagram illustrating the generation of the full life-cycle carbon footprint time series according to the present invention. Detailed Implementation

[0025] To further illustrate the technical means and effects of the present invention in achieving its intended purpose, the following detailed description of the specific implementation methods, structures, features, and effects of the present invention, in conjunction with the accompanying drawings and preferred embodiments, is provided below.

[0026] This embodiment provides a comprehensive carbon management and life-cycle accounting system. This system unifies the decomposition and automatic aggregation of carbon indicators among multi-level organizational entities, the cross-verification of cross-regional carbon data, and the full life-cycle carbon footprint accounting of buildings from construction to operation into a single technical framework.

[0027] The system consists of a carbon flow unit library, a multi-level ledger aggregation engine, a cross-regional verification engine, a carbon footprint accounting unit for the construction phase, a carbon footprint interface for the operation phase, a hierarchical permission management unit, and an automatic report generation unit.

[0028] The carbon flow unit library, as the sole data source, uses a unified five-tuple data structure to store all carbon data, fundamentally eliminating issues of data format differences and inconsistent accounting standards. The multi-level ledger aggregation engine, based on the hierarchical relationships between entities, automatically decomposes the total carbon emission control targets set by higher-level entities into quantitative indicators for lower-level entities, and generates a carbon ledger view from the carbon flow unit library in real time according to hierarchy. The cross-regional verification engine uses the SHA-256 hash algorithm and a blockchain-based notarized ledger to perform on-chain and off-chain bidirectional comparison and verification of carbon data reported by organizations in different regions. The carbon footprint accounting unit during the construction phase incorporates accounting models for three stages: building material transportation, construction machinery fuel consumption, and construction site energy consumption. It calculates the total carbon emissions during the construction phase and converts them into carbon flow units, storing them in the carbon flow unit library. The carbon footprint interface during the operation phase receives external operational carbon emission data, converts it into carbon flow units of a unified format, and concatenates it with the carbon flow units during the construction phase in chronological order to generate a time series of the project's full lifecycle carbon footprint. The tiered access control unit strikes a balance between data sharing and privacy protection by accommodating three roles: data producer, data manager, and data supervisor. The automatic report generation unit, based on preset templates and a carbon flow unit library, can directly output various reports, including total emissions summaries, carbon emission intensity statistics, and comparisons of carbon indicator decomposition completion.

[0029] like Figure 1 As shown, the overall architecture of this system consists of a carbon flow unit library, a multi-level ledger aggregation engine, a cross-regional verification engine, a construction phase carbon footprint calculation unit, an operation phase carbon footprint interface, a hierarchical permission management unit, and an automatic report generation unit. The carbon flow unit library is the core data storage component of the system; all other modules interact with it through standardized data read / write interfaces. The multi-level ledger aggregation engine extracts carbon flow units from the carbon flow unit library and performs carbon index decomposition and ledger aggregation. The cross-regional verification engine extracts the data to be verified from the carbon flow unit library and calculates a hash digest, comparing it with the notarized digest in the blockchain notarized ledger. After completing the construction carbon emission calculation, the construction phase carbon footprint calculation unit writes the results back to the carbon flow unit library in the form of carbon flow units. The operation phase carbon footprint interface converts external operation carbon emission data into carbon flow units, stores them in the carbon flow unit library, and completes the full lifecycle assembly. The hierarchical permission management unit filters all requests to access the carbon flow unit library. The automatic report generation unit extracts data from the carbon flow unit library according to rules to generate reports. Each module works collaboratively around the carbon flow unit library to form a closed loop for the unified collection, circulation, and application of carbon data.

[0030] Spatial coordinates Record the geographical location information of carbon emission sites. In practice, spatial coordinates can be expressed by overlaying geographic zoning codes with latitude and longitude grid codes, or in the construction field, by combining the geographic coordinates of the project site with the building outline, ensuring an accurate correspondence between carbon data and geographic spatial location.

[0031] Timestamp Record the exact time of carbon emissions, down to the day. For continuous emission activities, such as mechanical operations over several days during a construction phase, the start and end dates of the activity can be converted into a single timestamp, such as taking the midpoint date, and the activity duration information can be appended to the extended field of the emission source type code if necessary, to keep the timestamp field concise and consistent.

[0032] Emission source type coding Emission sources are classified and coded according to a pre-defined classification system. The classification system can be established based on the emission source classification in the Intergovernmental Panel on Climate Change (IPCC) or relevant domestic accounting standards, covering multiple categories such as fossil fuel combustion, industrial processes, electricity consumption, and transportation. Special codes are set for key emission sources in the construction and operation phases, such as codes for diesel consumption of construction machinery, gasoline consumption for building material transportation, externally purchased electricity consumption at construction sites, and heating gas consumption during the operation phase.

[0033] carbon emission value This represents the carbon dioxide equivalent emissions corresponding to the carbon flow unit, measured in kgCO2e. All carbon emission values ​​have been converted to carbon dioxide equivalents before being included in the carbon flow unit database. The global warming potential values ​​used for this conversion are uniformly adopted from the century-scale values ​​in the Fifth Assessment Report of the Intergovernmental Panel on Climate Change.

[0034] The carbon flow unit library can be physically implemented using a relational database management system, which includes quintuple fields and unique identifiers. The data is mapped to a database table structure, and a joint index is established for subject identifiers, spatial coordinates, timestamps, and emission source type codes to support efficient retrieval in scenarios such as multi-level aggregation, cross-regional verification, and full lifecycle tracing. All modules must write and read carbon data through the unified data access interface provided by the carbon flow unit library, prohibiting the direct transfer of raw data files between modules, thereby ensuring data consistency and traceability from a mechanism perspective.

[0035] The multi-level ledger aggregation engine is responsible for handling the step-by-step decomposition of carbon indicators across levels and the automatic bottom-up aggregation of carbon emission data.

[0036] First, a hierarchy table is pre-defined in the system. This table records the direct superior entity identifier of each entity. For example, the superior of a project cluster operation entity is the municipal carbon management cluster entity, and the superior of the municipal carbon management cluster entity is the regional carbon management general cluster entity. The table supports dynamic updates to accommodate adjustments to the regional grid or changes in management responsibilities.

[0037] When a higher-level organization needs to break down annual or quarterly carbon emission control targets to lower-level entities, the engine quantifies and breaks them down based on historical carbon emission percentages. Specifically, the higher-level organization sets the total carbon emission control targets through the system interface. The engine then selects a reference historical period. It extracts all carbon stream units belonging to the selected parent entity within the chosen historical period from the carbon stream unit library, groups them by their direct subordinate entities, and sums the results to obtain the historical carbon emissions of each subordinate entity. Then, calculate the decomposition index value of the i-th lower-level subject according to the following formula. : in, This represents the sum of historical carbon emissions from all n subordinate entities. This calculation process is completed automatically within the engine, and the resulting sub-entity index values ​​are stored in an index management data table as a benchmark for subsequent progress tracking.

[0038] Regarding ledger generation, the engine monitors data changes in the carbon flow unit library in real time. Once a new carbon flow unit is written, the engine aggregates it level by level along the hierarchical relationship chain based on the main identifier of that carbon flow unit. For a given parent entity, the engine encodes the carbon emission value from the carbon flow units corresponding to all its direct and indirect subordinate entities, according to spatial coordinates and emission source type. Grouping and summarizing are performed. Summarization dimensions are flexibly configurable; common dimensions include: by geographic grid, by emission source type, and by time period. The final generated carbon ledger view is a multi-dimensional dataset that intuitively presents the total carbon emissions and composition of each geographic grid and emission source within the jurisdiction of the higher-level entity at different time periods. For example, when a municipal-level carbon management entity views its carbon ledger view, it can see the carbon emissions of each subordinate project zone, as well as the emissions from industrial, building, and transportation sources within each project zone, and can also view the monthly cumulative emission curves. Each update to the carbon flow unit library triggers an incremental refresh of the ledger view, ensuring near real-time data accuracy and avoiding time delays and data distortion caused by manual reporting at multiple levels.

[0039] The cross-regional verification engine provides a means of cross-verifying the authenticity of carbon data among different regional operation and management entities.

[0040] The engine internally includes a hash calculation module and a blockchain notarization client. When a new carbon stream unit is written to the carbon stream unit library, the engine asynchronously extracts the carbon emission value of that carbon stream unit. and timestamp The hash digest is calculated using the SHA-256 algorithm. SHA-256 is a widely used cryptographic hash function that outputs a fixed 256-bit hash value from input data of arbitrary length. It exhibits avalanche effect and collision resistance, and can sensitively reflect any changes in the input data. The hash digest is used as a unique identifier for the carbon stream unit. The data is associated with each other and packaged together into a single evidence-based transaction. This transaction is then sent to a pre-built consortium blockchain network via a blockchain evidence-based client and written into the blockchain evidence-based ledger.

[0041] When an operating entity has doubts about carbon emission data reported by another entity, it can initiate a cross-regional verification request through the system. The verification request must specify the entity identifier and time range of the verification target. After receiving the request, the engine executes the following verification process.

[0042] The first step is to directly extract all carbon flow units of the target entity within a specified time range from the carbon flow unit library to form the first carbon flow unit set, and then calculate the carbon emission value of each carbon flow unit in this set. The sum is denoted as the first aggregate value. The second step involves the engine querying the blockchain ledger to retrieve the hash digests of all stored data for the same target entity within the same time frame, along with their associated information. The system obtains a set of hash digests. For each hash in the hash digest set, the system needs to retrieve it from the carbon stream unit library based on... Extraction of raw carbon flow units and The hash is recalculated and compared with the hash of the on-chain notarized evidence to verify that the on-chain notarized evidence has not been tampered with. After successful verification, these carbon stream units are combined into a second carbon stream unit set, and a second summary value is calculated. The third step is to calculate the first summary value. Compared with the second summary value The absolute value of the deviation is used to determine whether it exceeds a preset threshold. In this embodiment, the preset threshold is the second summary value. The 5% tolerance threshold is set because the emission factors themselves have a certain degree of uncertainty in carbon emission accounting, and the on-site metering equipment also has reasonable accuracy errors. If the threshold is set too strictly, invalid verification will be triggered frequently, which will reduce the availability of the verification mechanism.

[0043] When the absolute value of the deviation exceeds the 5% threshold, the engine marks the verification result as abnormal, generates an alert, and pushes it to the verification initiator and the data auditing entity; if the deviation is within 5%, it is marked as verification passed. Fourthly, the engine records the complete information of this verification operation as a verification log entry. The log entry includes the verification initiator identifier, the verification target identifier, the verification time range, and the first summary value. Second summary value The percentage of deviation and the verification results are recorded in the verification log, which is also hashed and written into the blockchain ledger for future auditing and traceability.

[0044] Through the above mechanism, the superior operation and management entity or the remote data auditing agency does not need to directly access the original database of the subordinate or remote system. They can independently verify the authenticity of the data reported by the subordinate based solely on the publicly available hash evidence on the chain and the carbon flow unit data extracted by authorization, thus ensuring the credibility of carbon data in the process of cross-regional transfer.

[0045] The construction phase carbon footprint accounting unit addresses the carbon emission accounting needs during the construction of building projects by providing a standardized calculation process.

[0046] This unit receives construction activity data input by users or imported from external material management systems, covering three aspects: building material transportation, construction machinery, and energy consumption at the construction site. For carbon emissions from building material transportation, the accounting unit obtains the transportation weight of the i-th type of building material. The unit of measurement is t; transport distance The unit of measurement is km; and the carbon emission factor of the corresponding transportation method for this type of building material. The unit of measurement is kgCO2e / t·km. Carbon emission factors can be obtained from national or industry-issued accounting guidelines. For example, the factor for road diesel truck transportation is 0.162 kgCO2e / t·km, and the factor for rail transportation is also 0.162 kgCO2e / t·km. Users can select the corresponding factor based on their actual transportation method. Total carbon emissions from building material transportation The formula for calculation is: Where n is the total number of building material types, i = 1, 2, ..., n.

[0047] For carbon emissions from construction machinery fuel, the accounting unit obtains the fuel consumption of the j-th type of construction machinery. and the carbon emission factor of this type of fuel Fuel consumption The unit of measurement is L or kg, and it is obtained from the sum of machine shift records; carbon emission factor For diesel fuel, a value of 2.63 kg CO2e / L can be used, and for gasoline, 2.3 kg CO2e / L can be used. Total carbon emissions from construction machinery fuels. The formula for calculation is: , where m is the total number of construction machinery types, and j = 1, 2, ..., m.

[0048] For energy consumption and carbon emissions at construction sites, the accounting unit obtains the consumption of the kth type of energy. and corresponding carbon emission factors The main energy sources include electricity and natural gas. The unit of measurement is kWh or m 3 The carbon emission factor for electricity is the average emission factor of the power grid in the project area, such as 0.581 kgCO2e / kWh; the carbon emission factor for natural gas can be taken as 2.18 kgCO2e / m³. 3 Total energy consumption and carbon emissions at construction sites The formula for calculation is: Where p is the total number of energy types, and k = 1, 2, ..., p.

[0049] Adding the results of the above three parts together, we obtain the total carbon emissions during the construction phase. : After the calculation is completed, the carbon footprint accounting unit during the construction phase will not include... Instead of outputting data independently, the data is combined with the project's main identifier, spatial coordinates, construction time range, and emission source type code to generate one or more construction phase carbon flow units, which are then written into the carbon flow unit library. The main identifier is the identifier of the unit to which the construction project belongs; the spatial coordinates are the geographical coordinates of the project location; the construction time range uses the actual start date of the project as the start timestamp and the completion date as the end timestamp; and the emission source type code is assigned a corresponding code according to the three phases. For example, the building material transportation phase is assigned code B-01, the construction machinery fuel phase is assigned code B-02, and the construction site energy consumption phase is assigned code B-03, thus forming a carbon emission record subdivided by phase in the carbon flow unit library. Alternatively, the three phases can be merged into a single total carbon flow unit and assigned a comprehensive code B-00 as needed for accounting. This design ensures that the carbon emission data of the construction phase is completely isomorphic to the carbon data generated by other modules at the underlying level, eliminating the need for any format conversion when performing full life cycle splicing or cross-regional verification.

[0050] The carbon footprint interface during the operation phase is designed for carbon emission accounting after a building is put into use, and receives carbon emission data during the operation phase from building automation systems, energy management systems, or third-party carbon accounting platforms.

[0051] Upon receiving operational carbon emission data from external sources, the interface first performs data format validation to confirm that it includes necessary fields such as the operational project entity identifier, spatial coordinates, operational timestamp, operational emission source type code, and operational carbon emission value. After successful validation, the interface maps these fields one by one according to the five-tuple structure of the carbon flow unit, generating the corresponding operational stage carbon flow unit and storing it in the carbon flow unit library. For the operational timestamp, if the external data provides monthly or yearly granularity, it is uniformly assigned the start date of that period, and a period granularity identifier is appended to the emission source type code to ensure the timestamp's meaning is clear.

[0052] When it is necessary to trace the carbon footprint of a construction project throughout its entire lifecycle, the interface extracts all carbon flow units belonging to the construction and operation phases of the project from the carbon flow unit library based on the project's unified entity identifier. No filtering by emission source type is performed during extraction to ensure comprehensive accounting. The extracted carbon flow units are sorted from earliest to latest by timestamp, forming a carbon emission time series for the project from its commencement date to the current operational point in time. For example... Figure 3 As shown, each segment on the timeline corresponds to the carbon emissions of a carbon flow unit. The construction phase may include multiple carbon flow units summarized on a daily or weekly basis, while the operation phase presents continuous monthly or annual emission data points. All data points are strung together to form a complete and quantifiable full life cycle carbon footprint curve.

[0053] After sorting, the interface can provide the time series to the user in the form of charts or data files, and can also calculate statistical values ​​such as cumulative emissions for each stage and the emission percentage for each stage. Since the carbon flow units in the construction phase and the carbon flow units in the operation phase share the same carbon flow unit library, time series splicing can be completed with only one query, without the need for cross-system data transfer, thus ensuring the inherent consistency of carbon footprint data throughout the entire life cycle.

[0054] The hierarchical permission management unit maintains three permission roles: data producer, data manager, and data supervisor, and authenticates each read and write operation of the carbon stream unit library accordingly.

[0055] The data producer role is typically assigned to entities that actually generate carbon emissions, such as construction companies, building maintenance units, and park management organizations. This role has the right to write carbon flow units belonging to its own entity into the carbon flow unit library, and also has the right to query detailed data of all carbon flow units written by its own entity, but has no right to view data from other entities.

[0056] The data manager role is assigned to entities with multi-level coordination functions, such as regional carbon operation entities, municipal carbon coordination entities, and regional carbon cluster entities. This role has the right to query carbon flow units within its own level and all subordinate entities, and can generate carbon ledger views within its jurisdiction, i.e., obtain summary statistical information through a multi-level ledger aggregation engine, but cannot delete or modify the original carbon flow unit data generated by other entities.

[0057] The data regulator role is typically assigned to an independent data compliance auditing agency. This role does not have permission to query detailed data for individual carbon stream units; it is only authorized to view aggregated statistical data for all carbon stream units, such as the total emissions of a specific geographic area or the total emissions of a specific industry, as well as the permission to initiate verification requests to cross-regional verification engines. This design allows regulators to monitor and verify overall emissions and data consistency without seeing individual emission records of specific companies. The isolation mechanism of the three permission roles ensures that the same carbon stream unit library presents differentiated data views to users at different levels, satisfying the needs of cross-regional and cross-level data sharing and management while avoiding the leakage of corporate trade secrets and sensitive point source data, achieving a balance between data transparency and privacy protection.

[0058] The automatic report generation unit reduces the workload of manual report compilation and ensures that the carbon emission data reported externally always maintains the same source as the original data in the carbon flow unit library.

[0059] The unit pre-stores various templates, including a total carbon emission summary table template, a carbon emission intensity statistics table template, and a carbon index decomposition completion comparison table template. Each template defines data field mapping rules and report layout rules. The data field mapping rules describe the correspondence between each data cell in the report and the fields and aggregation methods in the carbon flow unit library. For example, the annual industrial source carbon emission of a certain city cluster in the total summary table corresponds to the carbon emission values ​​of all carbon flow units whose main body identifier belongs to that city cluster and whose emission source type code belongs to the industrial source category. The sum of all elements. Report formatting rules specify the table style, header, unit of measurement, decimal places, and output format.

[0060] When a user requests report generation, the automatic report generation unit queries the corresponding carbon emission values ​​from the carbon flow unit library according to the data field mapping rules, and groups and summarizes them by subject identifier, spatial coordinates, or timestamp. The grouping and summarizing operation is completed directly at the database level, without the need to export detailed data to intermediate files for processing. After summarization, the unit fills the corresponding positions in the report template with the grouping and summarizing results, generating an exportable carbon emission report. Supported export formats include spreadsheet files and portable document files. Because the report data comes directly from the latest state of the carbon flow unit library, any data updates written to the carbon flow unit library will be automatically reflected in the next report generation, avoiding data inconsistencies caused by asynchronous transmission at multiple levels. Furthermore, the report generation process is repeatable; report data generated by different users under the same query conditions is completely consistent, facilitating auditing and verification.

[0061] To further illustrate the practical application effect of this system, implementation data for three typical scenarios are given below.

[0062] In Scenario 1, the decomposition and tracking of carbon emission targets in the city-level building sector are implemented: A city-wide carbon coordination entity sets a total carbon emission control target of 1,000,000 kg CO2e for the city's building sector in 2026. The city has three project zones: A, B, and C. Based on historical data from the carbon flow unit database for 2025, project zone A has historical carbon emissions of 410,000 kg CO2e, project zone B 350,000 kg CO2e, and project zone C 240,000 kg CO2e. The multi-level ledger aggregation engine breaks down the total targets according to historical proportions, calculating the 2026 target as 410,000 kg CO2e for project zone A, 350,000 kg CO2e for project zone B, and 240,000 kg CO2e for project zone C. The system automatically distributes these targets to the data manager role view for each project zone. By the end of June 2026, the real-time carbon flow unit database showed that Project A's cumulative emissions reached 205,000 kg CO2e, achieving 50% of the annual target, consistent with the timeline; Project B's cumulative emissions reached 196,000 kg CO2e, achieving 56%, slightly exceeding the timeline; and Project C's cumulative emissions reached 108,000 kg CO2e, achieving 45%, slightly slower than the timeline. The city's carbon coordination entity can intuitively grasp the progress of each project zone through the carbon ledger view and can promptly supervise the work of Project C's zone.

[0063] In Scenario 2, cross-cluster enterprise carbon emission data verification: The data audit entity of Region A has doubts about the carbon emission data of a steel company registered in Region B but with a production base within its jurisdiction for March 2026, and initiates verification through the cross-regional verification engine. The target entity for verification is identified as this company, and the time range is March 2026. The engine extracts all carbon flow units of this company in March from the carbon flow unit library and calculates the first aggregated value. =50000kgCO2e. Simultaneously, the engine reads all the company's March notarized hashes from the blockchain ledger, verifies each one, reconstructs the second carbon flow unit set, and calculates the second aggregated value. =50120kgCO2e. The absolute value of the deviation is 120kgCO2e, and the relative deviation is approximately 0.24%, which is less than the 5% threshold. The verification result is passed. The verification log records the two parties involved in the verification, the time range, the two summaries, and the deviation, and writes them to the blockchain. The data audit entity of the A region cluster recognizes the data reported by the enterprise based on the verified result, without the need to send personnel for on-site verification, which significantly reduces the verification cost.

[0064] In Scenario 3, the carbon footprint of an office building throughout its entire life cycle is calculated: A newly built office building project has a total construction area of ​​15,000 square meters. 2Construction commenced on March 1, 2025, and is scheduled for completion on December 31, 2025. Detailed carbon emissions breakdown for the construction phase: Building material transportation: 180 tons of steel were transported over a distance of 60 km, and 12,000 tons of ready-mixed concrete over a distance of 25 km, all using diesel trucks. Combined with emissions from other building material transportation, this phase totals 50,949.6 kg CO2e. Construction machinery: A total of 8,200 liters of diesel fuel were consumed by construction machinery on-site, resulting in 21,566 kg CO2e emissions. On-site energy consumption: With a total electricity consumption of 135,000 kWh during the construction period, and based on regional power grid emission factors, this phase totals 78,435 kg CO2e emissions. Summarizing the data from these three phases, the total carbon emissions for the entire construction phase of this project are 150,950.6 kg CO2e. The system automatically generates standardized carbon flow units from this total construction volume and the data for each sub-phase, and writes them into the carbon flow unit library for aggregation. The project officially commenced operation in January 2026. During the operational phase, the carbon footprint interface seamlessly integrated with the building energy consumption monitoring system's real-time data. The carbon emission data for the three consecutive years of operation are as follows: 423,000 kg CO2e in 2026, 418,500 kg CO2e in 2027, and 422,100 kg CO2e in 2028. Based on the project's unified entity identifier, the system assembles all carbon flow units from the construction and operation phases in chronological order to generate a full lifecycle carbon footprint time series. Statistical results show that by the end of 2028, carbon emissions during the construction phase accounted for approximately 10% of the total emissions over the entire lifecycle, while those during the operation phase accounted for approximately 90%. After the project commenced operation, the annual carbon emission figures tended to stabilize, providing intuitive and quantifiable data support for the project operator to accurately identify emission reduction priorities and develop targeted low-carbon optimization plans.

[0065] As can be seen from the above embodiments, this system, by constructing a unified data model of carbon flow units, transforms heterogeneous carbon data, originally scattered across different levels, regions, and stages, into basic data units with a consistent format and clear semantics. Based on this, the multi-level ledger aggregation engine achieves the scientific decomposition of total emission control targets and the automatic collection of emission data. The cross-regional verification engine, through hash notarization and on-chain / off-chain comparison, endows carbon data with reliable cross-regional verification capabilities. The carbon footprint accounting unit in the construction phase and the carbon footprint interface in the operation phase collaboratively complete the seamless splicing of carbon emissions throughout the entire lifecycle of a building project, from commencement to operation. The hierarchical permission management unit and the automatic report generation unit improve the system's usability and management efficiency while ensuring data security. The entire system operates in a closed-loop logic, with each module working collaboratively, providing a practical technical solution for comprehensive carbon management in complex scenarios involving multiple levels, cross regions, and the entire lifecycle.

[0066] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-disclosed technical content to create equivalent embodiments without departing from the scope of the present invention. Any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.

Claims

1. A comprehensive carbon management and life-cycle accounting system, characterized in that, The system comprises: The carbon flow unit library is used to store carbon flow units, which contain five fields: subject identifier, spatial coordinates, timestamp, emission source type code, and carbon emission value. The multi-level ledger aggregation engine is used to extract carbon flow units from the carbon flow unit library based on the subject identifier and spatial coordinates, aggregate them level by level according to the subject hierarchy, and generate carbon ledger views at each level. The cross-regional verification engine is used to extract the carbon emission values ​​of carbon stream units to be verified from the carbon stream unit library, calculate the hash digest and write it into the blockchain notarization ledger, and compare the consistency of hash digests of carbon stream units from different sources and output the verification results. The carbon footprint accounting unit during the construction phase is used to collect data on the weight and distance of building material transportation, fuel consumption of construction machinery, and energy consumption at the construction site, and to calculate the total carbon emissions during the construction phase. The carbon footprint interface for the operation phase is used to receive external carbon emission data for the operation phase and to concatenate the total carbon emission data for the construction phase with the carbon emission data for the operation phase in chronological order to form a full life cycle carbon footprint sequence.

2. The comprehensive carbon management and life-cycle accounting system according to claim 1, characterized in that, The data structure of each carbon stream unit in the carbon stream unit library is a quintuple ( ),in This serves as a unique identifier for the carbon flow unit. As a primary identifier for generating carbon emissions, Spatial coordinates of the carbon emission sites For the timestamp of carbon emissions, Code the emission source type. This represents carbon emissions, measured in kgCO2e.

3. The comprehensive carbon management and life-cycle accounting system according to claim 1, characterized in that, The multi-level ledger aggregation engine is configured to perform the following steps; The hierarchical relationship between storage entities; Based on the total carbon emission control targets set by the higher-level entities, and combined with the historical carbon emission proportions of each lower-level entity, the decomposed indicator values ​​for each lower-level entity are calculated using the following formula: in Let be the decomposition index value of the i-th lower-level subject. The total carbon emission control target set by the higher-level entity. Let n be the historical carbon emissions of the i-th lower-level entity, and n be the total number of lower-level entities. This is the sum of the historical carbon emissions of all subordinate entities; The overall target is automatically quantified to each lower-level entity, providing a benchmark for subsequent progress tracking; Based on hierarchical relationships, all carbon flow units belonging to the same superior entity are extracted from the carbon flow unit library. The carbon emission values ​​are summed and summarized according to spatial coordinates and emission source type codes to generate a carbon ledger view of the superior entity. When a new carbon flow unit is added to the carbon flow unit library, the summation and summary are re-executed to update the carbon ledger view.

4. The comprehensive carbon management and life-cycle accounting system according to claim 1, characterized in that, The cross-regional verification engine is configured to perform the following steps; The carbon emission values ​​and timestamps of carbon flow units are extracted from the carbon flow unit library, and a hash digest is calculated using the SHA-256 algorithm. The hash digest is then associated with the unique identifier of the carbon flow unit and written into the blockchain evidence ledger. Upon receiving an external verification request, the system extracts a first set of carbon flow units from the carbon flow unit library based on the target entity identifier and time range in the verification request. It calculates the sum of carbon emission values ​​of each carbon flow unit in the first set of carbon flow units as a first summary value. It reads the hash digest set of the same target entity identifier and the same time range that has been stored from the blockchain notarization ledger. It decodes and restores the hash digest set to obtain a second set of carbon flow units. It calculates the sum of carbon emission values ​​of each carbon flow unit in the second set of carbon flow units as a second summary value. It compares the first summary value with the second summary value. If the absolute value of the deviation is greater than a preset threshold, it is marked as a verification anomaly. Record the verification initiator identifier, target entity identifier, verification time range, and verification result for each verification operation, and write the verification log to the blockchain evidence ledger.

5. The comprehensive carbon management and life-cycle accounting system according to claim 4, characterized in that, The preset threshold is 5% of the second aggregate value.

6. The comprehensive carbon management and life-cycle accounting system according to claim 1, characterized in that, The carbon footprint accounting unit for the construction phase is configured to perform the following steps; Obtain the transport weight of the i-th type of building material Transportation distance And the carbon emission factors of the corresponding transportation methods for this type of building material ,according to Calculate the total carbon emissions from building material transportation Where i is the building material type number, i=1,2,…,n, and n is the total number of building material types. The unit of measurement is t. The unit of measurement is km. The unit of measurement is kgCO2e / t·km. The unit of measurement is kgCO2e; Obtain the fuel consumption of the j-th type of construction machinery. and the carbon emission factor of this type of fuel ,according to Calculate the total carbon emissions from fuel used in construction machinery Where j is the serial number of the construction machinery type, j=1,2,…,m, and m is the total number of construction machinery types. The unit of measurement is L or kg. The unit of measurement is kgCO2e / L or kgCO2e / kg. The unit of measurement is kgCO2e; Obtain the consumption of the kth energy source. and the carbon emission factor of this type of energy ,according to Calculate the total energy consumption and carbon emissions at the construction site Where k is the energy type index, k=1,2,…,p, and p is the total number of energy types. The unit of measurement is kWh or m³. The unit of measurement is kgCO2e / kWh or kgCO2e / m³. The unit of measurement is kgCO2e; Will and Add them together to get the total carbon emissions during the construction phase. .

7. The comprehensive carbon management and life-cycle accounting system according to claim 6, characterized in that, The carbon footprint accounting unit for the construction phase is also configured to: calculate the total carbon emissions during the construction phase. The carbon flow units for the construction phase are generated by combining the main identifier, spatial coordinates, construction time range, and emission source type code of the construction project, and stored in the carbon flow unit library. The construction time range is based on the project start date as the start timestamp and the project completion date as the end timestamp.

8. The comprehensive carbon management and life-cycle accounting system according to claim 1, characterized in that, The carbon footprint interface for the operational phase is configured to perform the following steps; After converting the externally input carbon emission data during the operation phase into carbon flow unit format, it is stored in the carbon flow unit library. The carbon flow unit of the carbon emission data during the operation phase includes the main identifier of the operation project, the spatial coordinates of the operation project, the operation timestamp, the operation emission source type code, and the operation carbon emission value. Based on the same project entity identifier, carbon flow units for the construction phase and carbon flow units for the operation phase are extracted from the carbon flow unit library, arranged in chronological order of timestamps, to generate the full life cycle carbon footprint time series of the project.

9. The comprehensive carbon management and life-cycle accounting system according to claim 1, characterized in that, The system also includes a hierarchical permission management unit, which stores three permission roles: data producer role, data manager role, and data supervisor role. The data producer role is configured to have the authority to write carbon stream units to the carbon stream unit library and the authority to query the carbon stream units of this entity. The data manager role is configured to have the authority to query all carbon flow units within its own and its subordinate jurisdictions and to generate carbon ledger views within its jurisdiction. The data supervisor role is configured to have the authority to query aggregated statistics of carbon stream units across the entire domain and to initiate verification requests to the cross-regional verification engine, but not to query detailed data of individual carbon stream units.

10. A comprehensive carbon management and life-cycle accounting system according to claim 1, characterized in that, The system also includes an automatic report generation unit, configured to perform the following steps: Store preset templates for total carbon emissions summary table, carbon emission intensity statistics table, and carbon index decomposition completion comparison table. Each template includes data field mapping rules and report layout rules. Based on the data field mapping rules, the carbon emission values ​​of the corresponding fields are extracted from the carbon flow unit library and grouped and summarized according to the subject identifier, spatial coordinates or timestamp. The grouped and summarized data is then filled into the report template according to the report layout rules to generate an exportable carbon emission report.

Images