A carbon footprint intelligent management system based on a cloud platform

Abstract

The present application relates to carbon emission data management technical field, specifically related to a kind of carbon footprint intelligent management system based on cloud platform, the carbon footprint intelligent management system includes the following operations is executed: carbon activity record is collected as carbon temporary segment, and the corresponding source constraint and destination constraint are written for each carbon temporary segment, output the corresponding temporary carbon column of target business matter;Perform reverse fishing pairing, output the right carbon segment corresponding to target business matter;Cloud platform is according to right carbon segment, the right account is kept to the part that has been closed, to the part that has not been fished, keep as carbon segment to be pursued, and generate carbon footprint intelligent management result accordingly.The present application, by constructing the phased processing and dynamic matching mechanism of carbon activity, the accurate right of closed carbon activity and the continuous tracking of un-closed carbon activity are realized, so as to improve the integrity, accuracy and controllability of carbon footprint management.

Description

Technical Field

[0001] This invention relates to the field of carbon emission data management technology, and in particular to a cloud-based intelligent carbon footprint management system. Background Technology

[0002] As the dual-carbon goals continue to advance, carbon emission data generated by enterprises in production operations, logistics, and supply chain collaboration exhibits characteristics of diverse sources, complex paths, and dispersed responsible parties. Existing carbon footprint management methods typically rely on post-event aggregation, centrally collecting and statistically analyzing carbon emission data from various stages to form an overall carbon emission result. However, in actual business operations, a large amount of carbon activity data does not have its responsibility assigned at the same time, but rather exhibits an asynchronous characteristic where activities occur first and responsibility is assigned later, resulting in discontinuities in carbon emission data over time. At the same time, cross-system and multi-entity data interaction makes it difficult to directly match the source and destination of carbon activities, thus affecting the continuity and accuracy of carbon footprint accounting.

[0003] Existing technologies suffer from the following main problems: First, they lack an intermediate state management mechanism for carbon activities that have not yet completed their responsibility closure, leading to delayed processing or direct neglect of mismatched data and affecting the integrity of the overall carbon footprint results. Second, they lack a dynamic matching mechanism based on source and destination constraints, making it difficult to achieve a precise correlation between carbon activities and responsibility statements. Third, they lack continuous tracking and management methods for incomplete carbon activities, failing to provide effective tracking or verification evidence when data is incomplete. Therefore, it is necessary to build a cloud-based intelligent carbon footprint management system to improve the accuracy and traceability of carbon footprint management. Summary of the Invention

[0004] To achieve the above objectives, the present invention provides a cloud-based intelligent carbon footprint management system.

[0005] A cloud-based intelligent carbon footprint management system, the intelligent carbon footprint management system comprising the following functions: The cloud platform collects carbon activity records of target business items that have been formed on various cloud nodes but have not yet completed the responsibility closure into carbon temporary segments, writes corresponding source constraints and destination constraints into each carbon temporary segment, and outputs the temporary carbon column corresponding to the target business item. When the liability statement information of the target business matter arrives at the cloud platform, the temporary carbon column is used as input to perform reverse retrieval and matching, extract the temporary carbon segment that closes with the liability statement information from the temporary carbon column, and output the confirmation carbon segment corresponding to the target business matter. Based on the confirmed carbon segments, the cloud platform confirms and records the closed portions, retains the unrecovered portions as carbon segments to be tracked, and generates intelligent carbon footprint management results for the target business items accordingly.

[0006] Optionally, the cloud platform aggregates carbon activity records into carbon temporary storage segments, including: The cloud platform generates a unique temporary storage segment identifier for each carbon activity record generated in each cloud node, and extracts the business timestamp, node identifier, activity type and activity volume data of the carbon activity record to form the initial temporary storage record. The cloud platform marks the status of the initial temporary storage record that has not yet been bound to any liability statement information as pending retrieval and stores it in the temporary storage segment data table partitioned by target business item.

[0007] Optionally, the source constraints include the cloud node ID that generated the carbon activity, the subsystem source identifier, the original document number, and the time window in which the activity occurred; the destination constraints include the type of responsible entity for the corresponding carbon temporary storage segment, the allowed categories of liability statements, and the effective retrieval period for the temporary storage segment.

[0008] Optionally, the output of the temporary carbon column corresponding to the target business item includes: aggregating each temporary carbon segment carrying source constraints and destination constraints according to the business timestamp order or node priority to form the temporary carbon column corresponding to the target business item, and providing an interface for querying and retrieving according to constraints.

[0009] Optionally, the liability statement information includes the statement subject, the business period of the statement, the scope of the responsibility nodes of the statement, and the carbon activity type matching conditions.

[0010] Optionally, the reverse retrieval pairing includes: Using the liability statement information as the retrieval key, reverse retrieval and pairing are performed in the temporary carbon column, that is, each carbon temporary segment in the temporary carbon column is traversed and its source constraint and destination constraint are bidirectionally matched with the liability statement information; When multiple carbon temporary storage segments simultaneously meet the bidirectional matching conditions, the cloud platform prioritizes them according to the order of business timestamps or the correlation of the original document number in the source constraint, selects the carbon temporary storage segment with the highest matching degree as the closed segment, and updates the status of the corresponding closed segment from pending retrieval to paired.

[0011] Optionally, the carbon segment corresponding to the target business item is output as follows: extracting the paired carbon temporary segment from the temporary carbon column and generating the carbon segment corresponding to the target business item, specifically including the responsible entity, the amount of carbon activity to be confirmed, the confirmation timestamp, and the corresponding temporary segment identifier.

[0012] Optionally, the process of confirming and recording carbon rights includes: writing the responsible entity for the confirmed carbon segment, the amount of carbon activity confirmed, the confirmation timestamp, and the corresponding temporary storage segment identifier into an immutable confirmation ledger, and adding them to the total closed carbon amount of the target business transaction.

[0013] Optionally, retaining the unretrieved portions as carbon segments to be tracked includes: marking all unretrieved and paired carbon segments in the temporary carbon column that are still in the state of pending retrieval as carbon segments to be tracked, and maintaining their source constraints, destination constraints, and original activity records unchanged, and storing them in the carbon segment to be tracked library.

[0014] Optionally, the intelligent carbon footprint management results include a carbon footprint confirmation report, a list of carbon segments to be tracked, and management recommendations. The carbon footprint confirmation report includes details of confirmed carbon activities, responsible entities, and total closed-loop amounts. The list of carbon segments to be tracked includes source information, expected claim conditions, and generation timestamps for each segment. Management recommendations refer to automatically generating a responsibility tracking instruction or an anomaly verification task when the number of carbon segments to be tracked or the total carbon amount exceeds a preset threshold.

[0015] The beneficial effects of this invention are: This invention constructs a carbon activity processing mechanism of temporary storage, subsequent retrieval, and final confirmation of rights. This mechanism enables phased management and dynamic closure of carbon data when carbon activity occurrence and liability declaration information are not synchronized. By temporarily storing data at the initial stage of carbon activity and performing reverse retrieval and matching upon the arrival of subsequent liability information, it ensures that each carbon activity is fully preserved before liability is clarified and can be accurately matched and confirmed after liability is clarified. This avoids carbon data loss or misattribution and improves the accuracy and consistency of carbon footprint accounting results.

[0016] This invention establishes a carbon tracking segment management mechanism for incomplete carbon activities and maintains the integrity of their contextual information by combining source and destination constraints, ensuring that incomplete data remains traceable and searchable. Based on this, by quantifying the number of carbon tracking segments and the total amount of carbon, it automatically generates responsibility tracking instructions or anomaly verification tasks, realizing a shift from passive recording to proactive management. Attached Figure Description

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

[0018] Figure 1 This is a schematic diagram of the functional modules of the carbon footprint intelligent management system according to an embodiment of the present invention; Figure 2 This is a schematic diagram illustrating the execution process of the carbon footprint intelligent management system according to an embodiment of the present invention. Detailed Implementation

[0019] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. It should also be noted that, to make the embodiments more comprehensive, the following embodiments are the best and preferred embodiments, and those skilled in the art can use other alternative methods to implement some well-known technologies; moreover, the accompanying drawings are only for more specific description of the embodiments and are not intended to specifically limit the present invention.

[0020] It should be noted that the use of terms such as "an embodiment," "an embodiment," "an exemplary embodiment," and "some embodiments" in the specification indicates that the described embodiment may include a specific feature, structure, or characteristic, but not every embodiment necessarily includes that specific feature, structure, or characteristic. Furthermore, when a specific feature, structure, or characteristic is described in connection with an embodiment, implementing such a feature, structure, or characteristic in conjunction with other embodiments (whether explicitly described or not) should be within the knowledge of those skilled in the art.

[0021] Generally, terms can be understood at least partly from their use in context. For example, depending at least partly on the context, the term "one or more" as used herein can be used to describe any feature, structure, or characteristic in a singular sense, or a combination of features, structures, or characteristics in a plural sense. Additionally, the term "based on" can be understood not necessarily to convey an exclusive set of factors, but rather, alternatively, depending at least partly on the context, to allow for the presence of other factors that are not necessarily explicitly described.

[0022] like Figures 1-2 As shown, a cloud-based intelligent carbon footprint management system includes the following modules: Carbon temporary storage construction module: used to receive raw carbon activity data generated in the target business transaction, write source constraints and destination constraints on the carbon activity data, and construct the corresponding carbon temporary storage segment; Reverse retrieval and matching module: After receiving the liability statement information, it performs reverse matching processing on the carbon temporary segments in the temporary carbon column, determines the matching relationship based on the source constraint and the destination constraint, extracts the carbon temporary segments that have completed the liability closure, and generates the confirmed carbon segments; The carbon rights confirmation and pending tracking management module is used to perform carbon rights confirmation and accounting processing on the carbon rights confirmation segments, write the responsible entity, carbon activity amount and time information into the carbon rights confirmation ledger, and determine the status of carbon temporary segments that have not been retrieved and paired. Carbon temporary segments with the status of pending retrieval are marked as pending carbon segments and stored in the pending carbon segment library. At the same time, the total closed carbon amount and the set of pending carbon segments are generated respectively. The results generation and control module generates intelligent carbon footprint management results based on the closed total carbon amount and the set of carbon segments to be tracked. It includes a carbon footprint confirmation report and a list of carbon segments to be tracked. Based on the comparison results of the number of carbon segments to be tracked and the total amount of carbon to be tracked with the preset threshold, it generates corresponding management suggestions and actions.

[0023] More specifically, the carbon footprint intelligent management system performs the following steps to achieve intelligent management: S1: The cloud platform collects carbon activity records of target business items that have been formed on each cloud node but have not yet completed the responsibility closure into carbon temporary segments, writes corresponding source constraints and destination constraints for each carbon temporary segment, and outputs the temporary carbon column corresponding to the target business item. S11: The cloud platform performs unique identifier construction and structured extraction processing on each carbon activity record generated by each cloud node, transforming the original carbon activity record into a standardized initial temporary record. Specifically, the cloud platform generates a unique temporary segment identifier based on the node identifier, business timestamp, and intra-node sequence information of the carbon activity record, and introduces a checksum to constrain the integrity of the identifier, ensuring that each carbon activity record is unique and verifiable globally. Simultaneously, it extracts the business timestamp, node identifier, activity type, and activity volume data from the original record and binds them to the temporary segment identifier to form a structurally unified initial temporary record. The aforementioned temporary segment identifier is generated as follows: ; ,in, Indicates the first Temporary segment identifier corresponding to the pen carbon activity record; Indicates the first The node identifier corresponding to the pen carbon activity record; Indicates the first The business timestamps corresponding to the pen carbon activity records use millisecond-level Unix timestamps; Indicates the first The carbon activity record is recorded in the corresponding cloud node with a sequential count value. The initial value is set to 1, and it is incremented by 1 for each record in the order of arrival. Indicates the first The 16-bit checksum corresponding to the pen carbon activity record; Indicates the first The activity type code corresponding to the pen carbon activity record; Indicates field concatenation operation; CRC16 ( ) represents the CRC-16 cyclic redundancy check function, which generates a check result of 16 bits in length. Through the above processing, the carbon activity records that were originally scattered and inconsistent in format are converted into temporary segment objects with a unified structure and unique identifier, thereby providing a consistent data foundation for the unified management, retrieval and matching of subsequent temporary segments.

[0024] S12: The cloud platform performs status marking and partitioned storage processing on initial temporary carbon records, enabling sustainable management of carbon temporary carbon segments. Specifically, the cloud platform determines the status of each initial temporary carbon record based on whether a liability declaration information has been established and bound to it. Initial temporary carbon records not bound to any liability declaration information are uniformly marked as pending retrieval and managed as carbon temporary carbon segments awaiting further processing. Records that have been bound are marked as bound. Simultaneously, the cloud platform partitions and stores carbon temporary carbon segments according to the dimension of target business items, storing carbon temporary carbon segments belonging to the same target business item in the corresponding temporary carbon segment data table, thus forming a temporary carbon segment data set divided by business.

[0025] The determination of the pending retrieval status is based solely on whether a responsibility closure relationship has been established. That is, when the responsibility declaration information corresponding to the carbon activity record has not yet arrived or completed matching and binding, the temporary storage segment corresponding to the carbon activity record is in a responsibility-unclosed state and needs to be marked as pending retrieval. The status value of the initial temporary storage record is determined according to the following rules: ,in, Indicates the first The initial temporary record status value of the pen; Indicates the first Whether the initial temporary storage record has been linked to the liability statement information; when When, it indicates that it is not bound, and the corresponding state value is... And mark them as pending retrieval; when When, it indicates that it is bound, and the corresponding state value. Partitioned storage is generated using the following partition key: ,in, Indicates the first The partition key corresponding to each target business item; Indicates the business year to which the target business item belongs; Indicates the business month to which the target business item belongs; This indicates a unique business number representing the target business item; This represents the hash mapping function, using a 32-bit hash output. Through the aforementioned state marking and partitioned storage processing, the carbon temporary segment is transformed from transient data into a persistent data object with lifecycle management capabilities, forming a clear data organization structure from a business perspective.

[0026] Example: Taking the same target business matter as an example, if three types of carbon activity records are generated in the equipment system, energy system and logistics system respectively, namely electricity consumption, gas consumption and transportation consumption, in the absence of receiving the corresponding liability statement information, the above three types of carbon activity records are all processed in step S11 to form corresponding carbon temporary storage segments, and are uniformly marked as pending retrieval in step S12, and stored in the temporary storage segment data table corresponding to the same business matter.

[0027] S13: Building upon the carbon temporary storage segments established in S11 and S12, and the completion of status marking and partitioned storage, the cloud platform further writes source constraints and destination constraints onto each carbon temporary storage segment. This gives the segment a clear data source boundary and expected responsibility attribution, transforming it from a simple data record into a constrained object capable of participating in subsequent matching calculations. Specifically, the cloud platform performs constraint writing processing on each carbon temporary storage segment based on the business context in which the carbon activity record exists. The business context includes the cloud node information generated by the carbon activity, its subsystem, associated business documents, and the carbon activity's position within the business process. Based on this contextual information, the cloud platform first extracts the identifier information that uniquely represents the source of the carbon activity and writes it into the source constraint set to limit the generation path and data source range of the carbon temporary storage segment. Subsequently, based on the responsibility transfer direction of the carbon activity in the business process, it determines the expected corresponding responsible entity type and the allowed matching responsibility statement category, and, combined with the system's preset time window, writes an effective retrieval period for the carbon temporary storage segment, thus forming a destination constraint set. In this way, each carbon temporary segment not only contains activity data describing what happened, but also constraint information describing where it came from and who will claim it, so that the carbon temporary segment can be accurately filtered, located and matched in subsequent steps.

[0028] The time window for the above activities is determined as follows: ; ; ; ,in, Indicates the first The time window for the occurrence of activities corresponding to each carbon temporary storage segment; Indicates the first The start time of each carbon temporary storage segment corresponds to the time window. Indicates the first The end time of the time window corresponding to each carbon temporary storage segment; Indicates the first Each carbon temporary storage segment corresponds to a business timestamp of the carbon activity record; This represents the half-width of the time window, with a fixed value of 900 seconds, or 15 minutes.

[0029] Source constraints are used to narrow down the candidate temporary storage segments during subsequent reverse retrieval, avoiding mismatches of data across nodes or businesses. Specifically, source constraints are written into the carbon temporary storage segment using a structured set of fields, including the following information: Cloud Node ID, extracted directly from the node to which the carbon activity record belongs, used to uniquely identify the data source node; Subsystem Source Identifier, written according to the business subsystem category to which the carbon activity belongs, used to distinguish the data source generated by different business systems; Original Document Number, obtained from the business system and associated with the carbon activity, used to achieve cross-system data association; Activity Occurrence Time Window, a time interval constructed centered on the business timestamp of the carbon activity record according to a preset time range, used to limit the effective time range of the carbon activity.

[0030] Destination constraints are used to limit the matching scope and timeliness conditions of liability statement information, preventing irrelevant liability statements from incorrectly claiming temporary carbon segments. Specifically, destination constraints are also written into the carbon temporary carbon segment using a structured set of fields, including the following information: type of responsible entity, used to determine which type of entity should claim the carbon activity based on its position in the business process; liability statement category, used to determine the type of liability statement information that can be matched based on the mapping relationship between carbon activity type and business rules; and effective retrieval period, which is the maximum allowable retrieval time range for the carbon temporary carbon segment by adding a preset duration to the carbon activity occurrence time. The above source constraints and destination constraints are written according to the following structures: ; ; ; ,in, Indicates the first The set of source constraints corresponding to each carbon temporary storage segment; Indicates the first The set of destination constraints corresponding to each carbon temporary storage segment; Indicates the first The subsystem source identifier corresponding to each carbon temporary storage segment; Indicates the first The original document number corresponding to each carbon temporary storage segment; Indicates the first The types of entities expected to assume responsibility for each carbon temporary storage segment; Indicates the first Each carbon transfer segment allows for matching liability statement categories; Indicates the first The effective retrieval deadline for each carbon temporary storage segment; This indicates a uniformly set effective retrieval period, fixed at 168 hours, or 7 days. By writing structured source and destination constraints into each carbon temporary storage segment, carbon activity records can be transformed from ordinary data records into constrained and searchable temporary storage objects, thus providing clear boundary conditions and closure criteria for subsequent reverse retrieval pairing.

[0031] S14: After processing in S13, each carbon temporary segment is no longer a simple carbon activity record, but a constrained data object that carries both source and destination boundaries. However, these carbon temporary segments are still scattered and have not yet formed an ordered set oriented towards the same target business matter. Therefore, in S14, the cloud platform needs to further organize the carbon temporary segments belonging to the same target business matter, so that they are transformed from discrete records into temporary carbon columns that can be directly called.

[0032] When the system aggregates carbon data according to business timestamp order, it essentially arranges each temporary carbon segment in a time sequence based on the order in which carbon activity records occur. This results in a temporary carbon column that accurately reflects the order of carbon activities for the same target business transaction during execution. By forming the temporary carbon column in chronological order, the system can quickly locate candidate temporary carbon segments within a specific time interval during subsequent reverse retrieval and matching, avoiding unordered searching across the entire historical record. When aggregating according to business timestamp order, the sort key is determined as follows: ,in, Indicates the first The time sorting key corresponding to each carbon temporary storage segment; Indicates the first Each carbon temporary storage segment corresponds to a business timestamp of the carbon activity record; the cloud platform follows... The carbon temporary segments are arranged in ascending order to form a temporary carbon column.

[0033] When the system aggregates based on node priority, it essentially prioritizes each carbon temporary storage segment according to the importance of different cloud nodes, the importance of their respective subsystems, and the quality of their records. This approach is suitable for scenarios that emphasize processing efficiency and matching accuracy. During subsequent reverse retrieval, the system can prioritize candidate searches from higher-priority carbon temporary storage segments, thereby reducing the probability of invalid matches and incorrect claims. When aggregating by node priority, the node priority score is determined as follows: ,in, Indicates the first The node priority score corresponding to each carbon temporary storage segment; Indicates the first The master node level value of the cloud node to which each carbon temporary storage segment belongs is any integer among 1, 2, and 3, where 3 represents a core business node, 2 represents a process business node, and 1 represents an edge acquisition node. Indicates the first The importance level value of the subsystem to which each carbon temporary storage segment belongs is taken as a value. Any integer in the range, where 3 represents the main business subsystem, 2 represents the auxiliary business subsystem, and 1 represents the peripheral support subsystem; Indicates the first Each carbon temporary segment corresponds to a record quality level value, which takes any integer from 1, 2, and 3, where 3 indicates that the field completeness is not lower than [a certain value]. 2 indicates that the field completeness is 1. to 1 indicates that the field completeness is lower than 1. The cloud platform follows The carbon temporary segments are arranged in descending order to form a temporary carbon series.

[0034] After forming the temporary carbon column, S14 does not stop at static storage, but further provides an interface for querying and retrieving based on constraints. The purpose is to enable the system to perform targeted filtering of the temporary carbon column based on source or destination constraints, rather than blindly traversing all temporary carbon segments. This interface supports filtering based on constraints such as cloud node ID, subsystem source identifier, original document number, responsible entity type, liability declaration category, and effective retrieval period. When liability declaration information arrives, the system can first quickly filter out candidate temporary carbon segments that meet the conditions from the temporary carbon column based on the relevant fields in the liability declaration, and then perform subsequent closure judgments within the candidate range. The above-mentioned interface for querying and retrieving based on constraints performs filtering according to the following conditional expressions: ,in, Indicates the first Temporary carbon tracking numbers corresponding to each target business transaction; Indicates the first in the temporary carbon column A temporary carbon storage segment Indicates in the query conditions The returned set of carbon temporary segments; This indicates a combination of input constraints, which must include at least one of the following: cloud node ID, subsystem source identifier, original document number, type of responsible entity, type of liability statement, and effective retrieval period. Indicates the first Each carbon temporary storage segment executes the constraint matching decision function; when When, it indicates the first Each carbon temporary storage segment meets the query conditions; when When, it indicates the first The carbon temporary storage segment does not meet the query conditions; by aggregating the carbon temporary storage segments into a temporary carbon column and providing an interface for querying and retrieving according to constraints, it is possible to directly provide structured input for reverse retrieval and matching after the arrival of subsequent liability statement information, thereby improving the overall processing efficiency and historical traceability capability.

[0035] S2: When the liability statement information of the target business matter arrives at the cloud platform, the temporary carbon column is used as input to perform reverse retrieval and matching, extract the temporary carbon segment that closes with the liability statement information from the temporary carbon column, and output the confirmation carbon segment corresponding to the target business matter. S21: The cloud platform receives the liability statement information for the target business matter. The liability statement information includes the declaring entity, the business time period of the declaration, the scope of the declared responsibility nodes, and the carbon activity type matching conditions. S22: After receiving the liability declaration information, the cloud platform uses it as the retrieval basis to perform reverse retrieval and matching on the temporary carbon column formed in S1, filtering out the temporary carbon segments that match the liability declaration information. The reverse retrieval is not essentially deducing from the current data backward, but rather starting with the currently received liability declaration information and searching backward in the historical temporary carbon column for carbon segments that can form a closed liability relationship. In the specific execution process, the cloud platform will traverse each temporary carbon segment in the temporary carbon column one by one, and match each segment with the liability declaration information from both the source constraint and destination constraint directions, thus forming a two-way matching mechanism. Specifically: The source constraint matching decision function is expressed as: ; ;

[0036] ; ;in, Indicates the first The source constraint matching score corresponding to each carbon temporary storage segment; Indicates the first Whether the time window of the activity of each carbon temporary storage segment falls within the time period of the declaration business time of the liability statement information; Indicates the first Whether the cloud node corresponding to each carbon temporary storage segment is within the scope of the responsible node in the liability statement information; Indicates the first The type matching flag indicates whether the activity type corresponding to each carbon transfer segment meets the carbon activity type matching condition of the liability statement information; This represents the time matching weight, with a fixed value of 0.4. This represents the node matching weight, with a fixed value of 0.4. This indicates the activity type matching weight, with a fixed value of 0.2. Indicates the first The time window in which the activity of the carbon temporary storage segment occurs; Indicates the first The business period for the declaration of liability information; Indicates the first The cloud node ID corresponding to each carbon temporary storage segment; Indicates the first The scope of responsibility for each liability statement information; Indicates the first The activity type code corresponding to each carbon temporary storage segment; Indicates the first The carbon activity type matching condition corresponding to each liability statement information.

[0037] The destination constraint matching decision function is expressed as: ; ; ; ;in, Indicates the first The destination constraint matching score corresponding to each carbon temporary storage segment; Indicates the first Does the entity making the statement of liability information comply with Article [number]? The subject matching marker for the expected claimant type of carbon temporary storage segment; Indicates the first Does the liability statement category of this liability statement information belong to the category of Article [number missing]? Each carbon temporary storage segment allows for matching of the category matching flags within the range of liability statement categories; Indicates the first Is the arrival time of the liability statement information within the specified period? Time-matching markers within the effective retrieval period of each carbon temporary storage segment; This represents the subject matching weight, with a fixed value of 0.5; This represents the category matching weight, with a fixed value of 0.3. This indicates the timeliness matching weight, with a fixed value of 0.2; Indicates the first The entity that makes the statement of liability information; Indicates the first The types of entities expected to assume responsibility in the destination constraints of carbon temporary storage segments; Indicates the first The set of allowed matching liability statement categories in the carbon temporary storage segment destination constraints; Indicates the first The arrival time of the liability statement information on the cloud platform; Indicates the first The effective retrieval deadline for each carbon temporary storage segment.

[0038] The total score for two-way matching is expressed as follows: ; And set the threshold for two-way matching as follows: When satisfied At that time, the judgment of the first The carbon temporary storage segment and the first The liability statement information is matched twice and is valid. Among them, Indicates the first The carbon temporary storage segment is relative to the first The overall score for the two-way matching of the liability statement information; This represents the source constraint matching score weight, with a fixed value of 0.5; This represents the weight of the destination constraint matching score, with a fixed value of 0.5; This indicates that a two-way matching threshold has been passed, with a fixed value of 0.8. By jointly determining the source constraint matching and the destination constraint matching, candidate carbon temporary sites can be constrained from both the source boundary and the claim boundary, thereby avoiding mismatch problems caused by claiming based on only one-sided conditions.

[0039] S23: After reverse retrieval and pairing, multiple carbon temporary storage segments may simultaneously satisfy the bidirectional matching condition. The cloud platform performs priority sorting on these candidate carbon temporary storage segments, selects the unique optimal matching object as the closed segment, and updates its status. Priority sorting includes sorting according to the order of business timestamps or according to the correlation of the original document number in the source constraint. In the first sorting method, the cloud platform sorts candidate carbon storage segments based on the proximity between the business timestamp of the carbon storage segment and the time center position of the liability declaration information. Liability declaration information typically corresponds to a time interval, and the carbon activity most consistent with that liability declaration should occur near the core position of that time interval. Therefore, by calculating the deviation between the carbon storage segment time and the center time of the liability declaration time interval, carbon storage segments with smaller time deviations are ranked higher. This sorting method emphasizes time consistency and is suitable for scenarios with strong business process continuity, prioritizing the carbon storage segment that best matches the liability declaration time as the closed segment. Specifically, the time priority ranking value is expressed as: ,in, Indicates the first The time priority ranking value corresponding to each carbon temporary storage segment; Indicates the first Each carbon temporary storage segment corresponds to a business timestamp of the carbon activity record; Indicates the first Each liability statement corresponds to the center time of the declared business period, satisfying the requirement that... ,in: Indicates the first The declaration of liability information includes the start time of the business period. Indicates the first The statement of liability information indicates the end time of the business period.

[0040] In the second sorting method, the cloud platform sorts candidate carbon temporary storage segments based on the matching relationship between the original document number in the source constraints of the carbon temporary storage segment and the associated business document number in the liability declaration information. In business systems, different carbon activities are often linked through business documents; for example, data in the same order, batch, or business process usually share the same or similar document numbers. Therefore, if the document number corresponding to the carbon temporary storage segment and the liability declaration information is completely identical, it indicates the strongest consistency in business association; if only the prefix is ​​identical, it indicates that they belong to the same business category or batch; if they are completely inconsistent, the association is the lowest. By introducing document number association, the system can further filter more reasonable closed objects from the perspective of business logic association, beyond time matching. When prioritizing according to the original document number association in the source constraints, the document number association is expressed as: ,in, Indicates the first The correlation between the original document number and the carbon temporary storage segment; Indicates the first The original document number in the source constraints of the carbon temporary storage segment; Indicates the first The business document number associated with this liability statement information; This function represents retrieving the first 8 business prefixes of the document number. When a comprehensive sorting is performed using both the order of business timestamps and the correlation between the original document number and the order of business timestamps, the priority score is expressed as follows: And select the carbon temporary storage segment that meets the following conditions as the closed segment: ,in, Indicates the first A comprehensive priority score for each carbon temporary storage segment; This represents the total score weight for two-way matching, with a fixed value of 0.6; This represents the weight of the time priority sorting value, which is fixed at 0.2. This represents the correlation weight of the original document number, with a fixed value of 0.2. This represents the target carbon temporary segment index with the highest overall priority score; This indicates the selection of a comprehensive priority score. The carbon temporary segment with the highest value is selected. After prioritizing and determining the optimal carbon temporary segment, the cloud platform marks the carbon temporary segment as a closed segment and updates its status from pending retrieval to paired. By introducing a priority sorting mechanism based on time consistency and business document relevance, the platform can effectively eliminate multi-candidate matching conflicts, ensure the uniqueness and accuracy of closed segment selection, and thus improve the reliability and auditability of the carbon footprint confirmation process.

[0041] S24: The cloud platform extracts the paired carbon temporary storage segments from the temporary carbon column and generates the corresponding credited carbon segment for the target business item based on its activity data. The credited carbon segment includes the responsible entity, the credited carbon activity amount, the credit timestamp, and the corresponding temporary storage segment identifier. The core function of this step is to transform the carbon temporary storage segments that have completed responsibility closure into result data objects with clear responsibility attribution and accountable attributes.

[0042] S3: The cloud platform confirms and records the carbon rights of the closed part based on the confirmed carbon segments, and retains the part that has not been retrieved as carbon segments to be tracked, and generates the carbon footprint intelligent management results of the target business items accordingly. S31: For each carbon segment output by S2, the cloud platform performs a carbon crediting and accounting operation: It writes the responsible entity to which the carbon segment belongs, the amount of carbon activity credited, the crediting timestamp, and the corresponding temporary storage segment identifier into an immutable carbon crediting ledger, and adds this information to the total closed carbon amount of the target business transaction; specifically, the... Each carbon segment with confirmed rights is represented as follows: ,in, Indicates the first One carbon segment with confirmed ownership; Indicates the first The responsible party for each carbon segment with confirmed ownership; Indicates the first The amount of carbon activity corresponding to each carbon credit segment; Indicates the first Each carbon segment for rights confirmation corresponds to a rights confirmation timestamp; Indicates the first The temporary storage segment identifier corresponds to each confirmed carbon segment. The total closed carbon amount is calculated by summing as follows: ,in, Indicates the first Total closed-loop carbon emissions corresponding to each target business transaction; Indicates the first The number of carbon credit segments corresponding to each target business item; Indicates the first Each carbon credit segment corresponds to a carbon activity amount. By implementing tamper-proof accounting for each carbon credit segment and simultaneously accumulating the total carbon amount, reliable storage and consistent statistics of carbon emission data can be achieved, thereby improving the reliability and auditability of carbon footprint accounting results.

[0043] S32: The cloud platform retains and manages carbon temporary storage segments that have not yet completed responsibility closure after the reverse retrieval and matching process in S2. Specifically, the cloud platform identifies all carbon temporary storage segments that have not been retrieved and matched and are still in the pending retrieval status from the temporary carbon storage list, and marks these segments as pending carbon storage segments, subsequently storing them in the pending carbon storage segment library for continuous tracking. The purpose is to: for carbon activities that have not yet been claimed by the declaration of responsibility information within the current processing cycle, they are not directly deleted, nor are they prematurely recorded as closed results, but are retained in the pending tracking form, thereby maintaining the continuity of carbon activity records and the integrity of the responsibility tracking chain. Specifically, after step S2 is completed, some carbon temporary storage segments have formed a closed relationship with the declaration of responsibility information and have been extracted to generate confirmed carbon segments; other carbon temporary storage segments, although already in the temporary carbon storage list, have not yet found declaration of responsibility information that meets the two-way matching conditions at the current time. For these carbon temporary storage segments, the cloud platform determines that their responsibility closure is not yet complete, therefore they are not included in the confirmed accounting scope, but are automatically transferred to the pending tracking management scope. When transferring a carbon activity to pending tracking management, the cloud platform does not alter the original data content of the temporary carbon registration segment. Instead, it fully preserves its source constraints, destination constraints, and original activity records. Source constraints characterize the source node, source subsystem, original documents, and timeframe of the carbon activity. Destination constraints characterize the expected type of responsible party, the allowed categories of liability claims, and the effective retrieval period for the carbon activity. Original activity records retain the basic business information and activity volume data of the carbon activity. By maintaining these elements unchanged, the pending carbon registration segment can be guaranteed to retain complete contextual information during subsequent liability tracking, supplementary registration, or anomaly verification.

[0044] Furthermore, the cloud platform uniformly writes the aforementioned carbon segments to be tracked into a carbon segment database, transferring unclosed carbon activities from the temporary storage stage to a dedicated carbon tracking management stage. The carbon segment database is not a regular cache, but a dedicated data set for centrally storing unclosed carbon activities. It stores the temporary storage segment identifier, source constraints, destination constraints, activity type, activity volume data, and generation timestamp for each carbon segment to be tracked, thus providing a foundation for subsequent retrieval and management by business item, responsible entity, or time range. Simultaneously, the cloud platform can also accumulate unclosed carbon activities under the same target business item based on the activity volume data corresponding to each carbon segment in the carbon segment database, forming the total carbon tracking amount for that target business item. This total carbon tracking amount reflects the scale of carbon activities still in an unclosed state within the current business item and provides a basis for triggering subsequent management recommendations.

[0045] The above-mentioned rules for determining the state of the carbon segment to be traced are expressed as follows: ,in: Indicates the first The determination mark for whether a carbon temporary segment is marked as a carbon segment to be traced; Indicates the first The current state value of the carbon temporary storage segment; when When this occurs, it indicates that the temporary carbon storage section is still awaiting retrieval. And mark it as the carbon segment to be traced; when When this occurs, it indicates that the temporary carbon storage section is no longer in a state awaiting retrieval. The first in the carbon segment library to be traced The carbon segments to be traced are represented as follows: ,in: Indicates the first One carbon segment to be traced; Indicates the first The temporary segment identifier corresponding to the carbon traceable segment; Indicates the first The set of source constraints corresponding to each carbon segment to be traced; Indicates the first The set of destination constraints corresponding to each carbon segment to be traced; Indicates the first The activity type code corresponding to each carbon segment to be traced; Indicates the first Activity data corresponding to each carbon segment to be tracked; Indicates the first The generation timestamp of each carbon segment to be traced.

[0046] S33: Based on the total closed carbon amount in S31 and the carbon segment library to be tracked in S32, the cloud platform integrates the carbon activity status of target business items in a unified manner to generate structured intelligent carbon footprint management results. These results are used to simultaneously reflect the carbon activities that have completed responsibility closure and the carbon activities that have not yet been closed, and trigger subsequent management actions accordingly.

[0047] Specifically, the cloud platform first organizes the overall carbon data for the current target business matter, unifying and encapsulating the closed carbon segment set, the carbon segment set to be tracked, and the corresponding management actions to form a data structure for intelligent carbon footprint management results; this is represented as: ,in, Indicates the first Intelligent management results of carbon footprint corresponding to each target business item; Indicates the first Carbon footprint report corresponding to each target business item; Indicates the first List of carbon traceable segments corresponding to each target business item; Indicates the first Management recommendations and actions corresponding to each target business matter.

[0048] After completing the overall structure definition, the cloud platform summarizes the closed carbon activities and generates a carbon footprint assessment report. This report, based on the carbon footprint assessment segments output by S2 and combined with the total closed carbon amount accumulated by S31, provides a centralized representation of all carbon activities that have completed responsibility closure. The expression is as follows: ,in, Indicates the first The set of all confirmed carbon segments corresponding to each target business item; Indicates the first The total closed carbon amount corresponding to each target business activity. Subsequently, based on the pending carbon segment library formed in S32, the cloud platform extracts all pending carbon segments corresponding to the current target business activity, forming a pending carbon segment list. This list is used to record carbon activities that have not yet completed responsibility closure and retains their complete context information; the pending carbon segment list is represented as follows: ,in, Indicates the first All carbon traces corresponding to each target business item.

[0049] After completing the structured representation of closed and open carbon activities, the cloud platform further determines whether to trigger management recommendations based on the scale of the carbon segments to be tracked. Specifically, the number of carbon segments to be tracked and the total amount of carbon to be tracked are used as the criteria. When either indicator exceeds a preset threshold, the management action generation mechanism is triggered. The rules for the determination are as follows: ,in, Indicates the first A flag indicating whether a target business matter triggers a management recommendation action; Indicates the first The number of carbon segments to be traced for each target business item; This represents the threshold for the number of carbon segments to be traced, with a fixed value of 5. Indicates the first The total amount of carbon traceable corresponding to each target business item; This represents the threshold for the total carbon emissions to be tracked, with a fixed value of 1000; where, Units and activity data The units of measurement must remain consistent. When the determination result is a triggered state, that is... The cloud platform further determines the specific management action type based on the quantity and scale of the carbon segments to be tracked and the total carbon emissions. The specific rules are as follows: , in: Indicates the first The responsibility tracking instructions corresponding to each target business matter; Indicates the first Anomaly verification tasks are assigned to each target business item. By constructing a unified result structure that includes carbon footprint confirmation reports, a list of carbon segments to be tracked, and management recommendations, and by triggering a management mechanism based on the scale of carbon segments to be tracked, the structured expression and automated control of carbon footprint management results can be achieved, thereby improving the integrity and response efficiency of the carbon management process.

[0050] This invention encompasses any substitutions, modifications, equivalent methods, and solutions made within the spirit and scope of this invention. To provide the public with a thorough understanding of this invention, specific details are described in detail in the following preferred embodiments; however, those skilled in the art will fully understand the invention even without these details. Furthermore, to avoid unnecessary misunderstanding of the essence of this invention, well-known methods, processes, procedures, components, and circuits are not described in detail.

[0051] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A cloud-based intelligent carbon footprint management system, characterized in that, The carbon footprint intelligent management system includes the following functions: The cloud platform collects carbon activity records of target business items that have been formed on various cloud nodes but have not yet completed the responsibility closure into carbon temporary segments, writes corresponding source constraints and destination constraints into each carbon temporary segment, and outputs the temporary carbon column corresponding to the target business item. The cloud platform aggregates carbon activity records into carbon temporary storage segments, including: The cloud platform generates a unique temporary storage segment identifier for each carbon activity record generated in each cloud node, and extracts the business timestamp, node identifier, activity type and activity volume data of the carbon activity record to form the initial temporary storage record. The cloud platform marks the status of the initial temporary storage record that has not yet been bound to any liability statement information as pending retrieval and stores it in the temporary storage segment data table partitioned by target business item; The temporary carbon column corresponding to the output target business item includes: aggregating each temporary carbon segment carrying source constraints and destination constraints according to the business timestamp order or node priority to form the temporary carbon column corresponding to the target business item, and providing an interface for querying and retrieving according to constraint conditions. When the liability statement information of the target business matter arrives at the cloud platform, the temporary carbon column is used as input to perform reverse retrieval and matching, extract the temporary carbon segment that closes with the liability statement information from the temporary carbon column, and output the confirmation carbon segment corresponding to the target business matter. The liability statement information includes the declaring entity, the business period of the statement, the scope of the declared responsibility nodes, and the matching conditions for carbon activity types; The reverse retrieval pairing process includes: Using the liability statement information as the retrieval key, reverse retrieval and pairing are performed in the temporary carbon column, that is, each carbon temporary segment in the temporary carbon column is traversed and its source constraint and destination constraint are bidirectionally matched with the liability statement information; When multiple carbon temporary storage segments meet the bidirectional matching conditions at the same time, the cloud platform prioritizes them according to the order of business timestamps or the correlation of the original document number in the source constraint, selects the carbon temporary storage segment with the highest matching degree as the closed segment, and updates the status of the corresponding closed segment from pending retrieval to paired. The carbon segment corresponding to the target business item is generated by extracting the paired carbon temporary segment from the temporary carbon column and generating the carbon segment corresponding to the target business item. Specifically, it includes the responsible entity, the amount of carbon activity to be confirmed, the confirmation timestamp, and the corresponding temporary segment identifier. Based on the confirmed carbon segments, the cloud platform confirms and records the closed portions, retains the unrecovered portions as carbon segments to be tracked, and generates intelligent carbon footprint management results for the target business items accordingly.

2. The cloud-based intelligent carbon footprint management system according to claim 1, characterized in that, The source constraints include the cloud node ID that generated the carbon activity, the subsystem source identifier, the original document number, and the time window in which the activity occurred; the destination constraints include the type of responsible entity for the carbon temporary storage segment, the allowed categories of liability statements, and the effective retrieval period for the temporary storage segment.

3. The cloud-based intelligent carbon footprint management system according to claim 1, characterized in that, The process of confirming and recording carbon rights includes: writing the responsible entity for the confirmed carbon segment, the amount of carbon activity confirmed, the confirmation timestamp, and the corresponding temporary storage segment identifier into an immutable confirmation ledger, and adding it to the total closed carbon amount of the target business transaction.

4. The cloud-based intelligent carbon footprint management system according to claim 3, characterized in that, The step of retaining the unretrieved portions as carbon segments to be tracked includes: marking all unretrieved and paired carbon segments in the temporary carbon column that are still in the state of pending retrieval as carbon segments to be tracked, and maintaining their source constraints, destination constraints and original activity records unchanged, and storing them in the carbon segment to be tracked library.

5. The cloud-based intelligent carbon footprint management system according to claim 4, characterized in that, The intelligent carbon footprint management results include a carbon footprint confirmation report, a list of carbon segments to be tracked, and management recommendations. The carbon footprint confirmation report includes details of confirmed carbon activities, responsible parties, and total closed-loop amounts. The list of carbon segments to be tracked includes source information, expected claim conditions, and generation timestamps for each segment. Management recommendations are used to automatically generate accountability tracking instructions or anomaly verification tasks when the number of carbon segments to be tracked or the total carbon amount exceeds a preset threshold.

Images