A blockchain-based carbon data storage system, method, and medium for CCER certification.
By segmenting and encrypting the embedded FBG optical fiber, the correspondence between carbon data in the power supply section and the on-chain evidence storage system is solved, realizing the continuity and verifiability of carbon data and supporting the accurate verification of CCER verification and monitoring ledgers.
Patent Information
- Application Number
- CN202611269918.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-20
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, it is difficult to maintain a continuous and verifiable correspondence between carbon data and power supply sections, computing power execution equipment, energy consumption receipts, tenant affiliation, on-chain evidence storage, and CCER verification and monitoring ledgers, making it difficult for third-party auditing agencies to reverse verify the content of the monitoring ledgers.
By segmenting the embedded FBG optical fiber, identifying the inner coating attachment, detachment from the wall, and wrinkled sections, and using the loop area to cover the power supply section, the energy consumption receipts and carbon accounting results of the computing execution equipment are screened, and the fragmented encryption and decryption are performed to generate on-chain carbon data storage records, ultimately forming a CCER verification and monitoring ledger.
It enables accurate definition of power supply sections, ensures the continuity and verifiability of carbon data correspondence, supports the verification of ledger contents by third-party auditing agencies, and avoids data disconnect.
Smart Images

Figure CN123114740A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of cloud platform technology, and in particular to a blockchain-based carbon data storage system, method, and medium for CCER certification. Background Technology
[0002] In computing power service scenarios, after the computing power requests submitted by tenants are batch-scheduled, the computing power execution equipment in the data center completes the calculations during the corresponding execution period. The equipment obtains power through bus trunking and power supply branches. The energy consumption metering end generates computing power energy consumption receipts, and the carbon accounting end combines carbon emission factors to generate carbon accounting results. For CCER project review and verification, relevant data also need to be collected by tenant, and evidence storage is completed while maintaining the access boundaries of business fields. In accordance with the verification request and monitoring plan template, a monitoring ledger is formed for verification by third-party review agencies.
[0003] The existing technical problem is that it is difficult to maintain a continuous and verifiable correspondence between the carbon data of the target computing power business and the actual power supply section, computing power execution equipment, energy consumption receipts, tenant affiliation, on-chain evidence storage and CCER verification and monitoring ledger. This is because the power supply side usually determines the business power consumption range based on the equipment list or static topology records, and it is difficult to accurately limit the affected power supply section by changes in the internal structure of the bus trunking. Business scheduling, energy consumption metering, carbon accounting, encrypted evidence storage and verification form filling process their own data separately. Fields and source indexes are prone to lose correlation when transferred across links, making it difficult for the monitoring ledger content obtained by the third-party auditing agency to be reverse-checked to the corresponding computing power business, tenant and on-chain evidence storage data. Summary of the Invention
[0004] The purpose of this invention is to address the shortcomings of existing technologies that make it difficult to accurately define the affected power supply sections based on changes in the internal structure of busbar trunking. The invention proposes a carbon data blockchain notarization system, method, and medium for CCER certification.
[0005] To address the problems existing in the prior art, the present invention adopts the following technical solution: A blockchain-based carbon data storage system for CCER certification includes: The sensing module segments the embedded FBG optical fiber according to the computing power execution device corresponding to the target computing power service, resulting in an inner coating attachment segment, an inner coating detachment segment, and an inner coating wrinkle segment; it extracts the region of the inner coating wrinkle segment to obtain the inner coating wrinkle loop region, and extracts the position of the optical fiber corresponding to each power supply segment to obtain the loop-covered power supply segment. The collection module extracts the carbon accounting results corresponding to the target computing power service based on the power supply section covered by the ring, and obtains the tenant's computing power carbon storage record. The encryption module performs fragmented encryption on the field encrypted carbon data fragments based on the tenant identifier in the tenant's computing power carbon storage record, thus obtaining the tenant's encrypted carbon data fragments. The verification module generates on-chain carbon data storage records corresponding to the tenant's encrypted carbon data shards. Based on the on-chain carbon data storage records, it decrypts the encrypted fields to be verified to obtain a subset of CCER verified carbon data. The ledger module writes the corresponding content into the CCER verification carbon data subset to obtain the verification ledger content; based on the verification ledger content, the CCER verification monitoring ledger is obtained.
[0006] Preferably, the process includes an inner coating attachment section, an inner coating separation section, and an inner coating wrinkling section, comprising: Obtain the computing power execution equipment corresponding to the target computing power service; Determine the target busbar for supplying power to the computing power execution equipment; Determine the embedded FBG optical fiber corresponding to the target busbar; Obtain the axial structure image sequence corresponding to the embedded FBG optical fiber; wherein, the embedded FBG optical fiber includes a quartz glass optical fiber, an inner coating covering the outside of the quartz glass optical fiber, and an FBG grating region disposed in the quartz glass optical fiber. Extract the outer contour of the quartz glass fiber corresponding to the quartz glass fiber and the inner contour of the inner coating corresponding to the inner coating from the axial structure image sequence. Based on the physical contact relationship between the inner contour of the inner coating and the outer contour of the quartz glass fiber, the embedded FBG fiber is segmented to obtain the inner coating attachment segment, the inner coating wall separation segment, and the inner coating wrinkling segment.
[0007] Preferably, the inner coating wrinkle collar region includes: The junction between the inner coating attachment section and the inner coating wall separation section is extracted to obtain the position where the collar separates. The position where the axial extension direction of the inner coating changes in the section of the inner coating away from the wall is extracted to obtain the fold-back position of the collar; The overlapping position of the inner coating after folding and the inner coating before folding in the inner coating wrinkle section is extracted to obtain the collar folding position; The junction between the inner coating wall section and the inner coating attachment section is extracted to obtain the collar reattachment position; Based on the collar detachment position, collar fold-back position, collar re-overlap position, and collar re-attachment position, the wrinkled section of the inner coating is extracted to obtain the wrinkled collar area of the inner coating.
[0008] Preferably, the loop-covered power supply section includes: Obtain the position of each FBG region on the embedded FBG fiber; Based on the inner coating wrinkle ring area, the location of each FBG gate area is extracted by regional overlap to obtain the ring-covered gate area; Based on the power supply location range of the computing power execution equipment, the target bus trunking is divided into sections to obtain multiple power supply sections; Obtain the fiber location range corresponding to each power supply section on the embedded FBG fiber; Based on the FBG grid area location corresponding to the ring-covered grid area, the location range of the optical fiber corresponding to each power supply section is extracted to obtain the ring-covered power supply section.
[0009] Preferably, the tenant's computing power carbon storage record is obtained, including: Obtain the tenant identifier, computing power request hash, batch merge record, computing power energy consumption receipt and carbon accounting result corresponding to the target computing power service; The computing power execution devices powered by the power supply section covered by the ring are extracted to obtain the ring-related computing power execution devices; Extract the computing power energy consumption receipts corresponding to the ring-linked computing power execution devices from the computing power energy consumption receipts corresponding to the target computing power service to obtain the ring-linked energy consumption receipts; Based on the ring-related energy consumption receipt, the carbon accounting results corresponding to the target computing power business are extracted to obtain the ring-related carbon accounting results; Based on the hash of computing power requests, the batch merge records and the carbon accounting results associated with the ring are aggregated accordingly to obtain the computing power carbon aggregation records; Write the tenant identifier into the computing power carbon collection record to obtain the tenant computing power carbon storage record.
[0010] Preferably, obtaining tenant encrypted carbon data fragments includes: Based on the tenant identifier in the tenant's computing power carbon storage record, the tenant's computing power carbon storage record is fragmented to obtain tenant carbon data fragments; Obtain tenant business fields from tenant carbon data shards; Obtain the data field-level key corresponding to the tenant's business field; By using data field-level keys, the tenant's business fields are encrypted at the field level to obtain field-encrypted carbon data fragments; Retrieve the tenant master key corresponding to the tenant identifier; Using the tenant's master key, the encrypted carbon data fragments are encrypted in segments to obtain the tenant's encrypted carbon data fragments.
[0011] Preferably, the subset of CCER-verified carbon data obtained includes: Generate the shard hash value corresponding to the tenant's encrypted carbon data shard; Write the tenant's encrypted carbon data shards, shard hash values, and the tenant identifier corresponding to the tenant's encrypted carbon data shards into the blockchain to obtain on-chain carbon data storage records. Obtain CCER verification requests initiated by third-party certification bodies; Based on the tenant identifier in the CCER verification request, the corresponding on-chain carbon data storage records are extracted to obtain the on-chain carbon data storage records corresponding to the tenant to be verified. The carbon data shards to be verified are determined based on the on-chain storage location in the on-chain carbon data storage record corresponding to the tenant to be verified. Based on the verification fields in the CCER verification request, the corresponding encrypted content in the carbon data shard to be verified is extracted to obtain the encrypted fields to be verified. Obtain the data field-level key corresponding to the encrypted field to be verified; Based on the data field-level key, the encrypted fields to be verified are decrypted to obtain a subset of CCER verified carbon data.
[0012] Preferably, the CCER verification and monitoring log is obtained, including: Obtain the CCER monitoring plan template corresponding to the CCER verification request; the CCER monitoring plan template includes multiple monitoring ledger fields; Based on the verification fields in the CCER verification request, the corresponding fields of multiple monitoring ledgers are extracted to obtain the verification ledger fields; Based on the fields in the verification ledger, the corresponding content in the CCER carbon verification data subset is written into the fields to obtain the verification ledger content; Based on the on-chain carbon data storage records corresponding to the CCER carbon data subset, extract the corresponding target on-chain storage location and target shard hash value. Write the target chain storage location and target shard hash value into the evidence index field corresponding to the verification ledger field to obtain the CCER verification and monitoring ledger.
[0013] To address the aforementioned problems, this invention also provides a blockchain-based carbon data notarization method for CCER verification, the method comprising: Based on the computing power execution equipment corresponding to the target computing power service, the embedded FBG fiber is segmented to obtain the inner coating attachment segment, the inner coating detachment segment, and the inner coating wrinkle segment; the inner coating wrinkle segment is extracted to obtain the inner coating wrinkle loop area, and the fiber position range corresponding to each power supply segment is extracted to obtain the loop-covered power supply segment. Based on the power supply section covered by the ring, the carbon accounting results corresponding to the target computing power service are extracted to obtain the tenant's computing power carbon storage record. Based on the tenant identifier in the tenant's computing power carbon storage record, the encrypted carbon data fragments in the field are encrypted to obtain the tenant's encrypted carbon data fragments. Generate on-chain carbon data storage records corresponding to the tenant's encrypted carbon data shards. Based on the on-chain carbon data storage records, decrypt the encrypted fields to be verified to obtain a subset of CCER verified carbon data. Write the corresponding fields in the CCER carbon data subset to obtain the verification ledger content; based on the verification ledger content, obtain the CCER verification monitoring ledger.
[0014] The present invention also provides a storage medium including a computer program, which, when executed by a processor, implements the above-described carbon data blockchain notarization system for CCER certification.
[0015] Compared with the prior art, the beneficial effects of the present invention are: 1. By using the embedded FBG fiber axial structure image and inner and outer contours, the attached, detached and folded sections are identified based on the contact relationship. The loop area is defined by the detachment, folding, overlapping and reattaching positions. The covered grid area is then mapped to the bus trunking power supply section, so that the local structural changes correspond to the computing power execution equipment, providing a boundary for screening energy consumption receipts and carbon accounting results.
[0016] 2. Screen computing power execution equipment, energy consumption receipts and carbon accounting results by covering the power supply section with a ring. Collect them by computing power request hash and write them into the tenant identifier so that power supply, energy consumption and carbon emissions correspond to the tenant. Then implement layered encryption with data field level key and tenant master key, and write the shard hash value into the blockchain to realize field access control, tenant isolation and on-chain integrity verification.
[0017] 3. Locate the on-chain carbon data storage records and carbon data fragments to be verified according to the tenant identifier and verification fields in the CCER verification request. Obtain the key only for the authorized fields and form a subset of CCER verification carbon data. Then write the fields and storage index according to the CCER monitoring plan template so that the third-party auditing agency can verify the ledger content, tenant source and on-chain transactions to avoid the ledger content being disconnected from the storage basis. Attached Figure Description
[0018] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings: Figure 1 This is a functional module diagram of a carbon data blockchain notarization system for CCER verification provided in an embodiment of the present invention; Figure 2 This is a diagram illustrating the data formation relationships in the CCER verification and monitoring ledger. Detailed Implementation
[0019] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.
[0020] This embodiment provides a blockchain-based carbon data notarization system for CCER certification. See [link to documentation]. Figure 1 It includes: a sensing module, which segments the embedded FBG optical fiber according to the computing power execution device corresponding to the target computing power service to obtain an inner coating attachment segment, an inner coating detachment segment, and an inner coating wrinkle segment; it extracts the region of the inner coating wrinkle segment to obtain the inner coating wrinkle loop region, and extracts the position of the optical fiber position range corresponding to each power supply segment to obtain the loop-covered power supply segment. In embodiments of the present invention, an inner coating attachment section, an inner coating separation section, and an inner coating wrinkling section are obtained, including: The inner coating attachment segment refers to the fiber segment where the inner surface of the inner coating continuously contacts the outer surface of the quartz glass fiber along the axial direction of the embedded FBG fiber, and is used to characterize the structural state in which the inner coating remains attached; the inner coating separation segment refers to the fiber segment where the inner surface of the inner coating and the outer surface of the quartz glass fiber are spaced apart along the axial direction of the embedded FBG fiber and have not yet formed a overlap, and is used to locate the range where the inner coating has detached from the quartz glass fiber; the inner coating wrinkling segment refers to the fiber segment where the inner coating changes its axial extension direction after detaching from the quartz glass fiber and forms a fold or overlap, and is used to determine the inner coating wrinkling loop area.
[0021] Obtain the computing power execution equipment corresponding to the target computing power service; The target computing power service refers to a single computing power processing service that currently accepts carbon data traceability processing and is defined by the service identifier in the service scheduling record; the computing power execution device refers to the device entity that undertakes the computing task of the target computing power service and generates corresponding energy consumption during the execution period of the target computing power service. The device entity is associated with the service scheduling record through the device identifier and serves as the starting point for determining the power supply path.
[0022] The business management terminal takes the target computing power business currently receiving carbon data traceability processing as the processing object, obtains the target computing power business identifier from the business scheduling record synchronously established when the target computing power business is formed, compares the business identifier field in the business scheduling record one by one with the target computing power business identifier, and continues to extract the device identifier field for the business scheduling record where the business identifier field is equal to the target computing power business identifier. The device entities in the device list are associated according to the device identifier field, and the device identifier fields that are not associated with the device entities are excluded. All associated device entities constitute the computing power execution device corresponding to the target computing power business.
[0023] Determine the target busbar for supplying power to the computing power execution equipment; The target busbar refers to the busbar that is in a conductive state during the execution period of the target computing power service and transmits electrical energy to the computing power execution equipment through the power supply branch. Its location and connection relationship are derived from the power supply topology record and are used to limit the monitoring objects of the embedded FBG optical fiber.
[0024] The power supply management terminal uses the device identifier of the computing power execution device corresponding to the target computing power service as the association key. It searches the power supply branch connecting the power supply port of the computing power execution device one by one from the power supply topology record. It traces the connection order of the device power supply branch to the power supply side to the bus trunk. It writes the switch status and power supply direction of each connection node during the service execution period into the corresponding tracing path. For the tracing path with the switch status on and the power supply direction pointing to the computing power execution device, it continues to check the bus trunk identifier. When the tracing paths of each computing power execution device point to the same bus trunk identifier, the bus trunk corresponding to that bus trunk identifier is determined as the target bus trunk. When the tracing paths of each computing power execution device point to different bus trunk identifiers, the bus trunk corresponding to the bus trunk identifier pointed to by the tracing path that undertakes the energy consumption metering of the target computing power service is determined as the target bus trunk.
[0025] Determine the embedded FBG optical fiber corresponding to the target busbar; Embedded FBG fiber refers to an optical fiber sensing carrier that is set inside the target busbar structure along the extension direction of the target busbar. Its deployment range corresponds to the power supply position of the target busbar and is used to obtain an axial structural image inside the target busbar and provide the axial position of each FBG grid area.
[0026] The fiber optic management terminal uses the target busbar identifier as the association key to retrieve records from the fiber optic deployment records generated during the installation of the target busbar where the busbar identifier field is equal to the target busbar identifier. It then verifies the fiber identifier, fiber start and end positions, and fiber installation positions in the retrieved records. The fiber identifiers that are installed inside the target busbar structure and whose fiber start and end positions cover the power supply positions of the target busbar are retained. The fiber pointed to by the retained fiber identifier is then identified as the embedded FBG fiber corresponding to the target busbar.
[0027] Obtain the axial structure image sequence corresponding to the embedded FBG optical fiber; wherein, the embedded FBG optical fiber includes a quartz glass optical fiber, an inner coating covering the outside of the quartz glass optical fiber, and an FBG grating region disposed in the quartz glass optical fiber. The axial structural image sequence refers to multiple images acquired sequentially along the axial direction of the embedded FBG fiber by the structural imaging device and arranged according to the axial position. Each image includes pixel grayscale, axial position, radial position, spatial resolution, and grayscale repeatability upper limit, used to continuously present the interface state between the quartz glass fiber and the inner coating. The quartz glass fiber refers to the quartz glass entity that constitutes the central light transmission part of the embedded FBG fiber, and its outer surface constitutes the reference surface for the inner coating to be attached or detached. The inner coating refers to the layered entity that covers the outside of the quartz glass fiber and can change its attachment form according to the internal state of the target busbar. The FBG grating area refers to the grating section set in the quartz glass fiber and having a corresponding fiber axial position, used to associate the inner coating corrugated loop area with the power supply section of the target busbar.
[0028] The structural imaging device uses the starting position of the optical fiber in the optical fiber deployment record as the axial acquisition start point and the ending position of the optical fiber as the axial acquisition end point, so that the imaging range covers the quartz glass fiber in the embedded FBG optical fiber, the inner coating covering the outside of the quartz glass fiber, and the FBG grating area set in the quartz glass fiber. The acquisition position is moved along the axial extension direction recorded in the optical fiber deployment record. The acquisition step size is determined according to the axial resolution capability of the structural imaging device to continuously identify the inner surface of the inner coating in adjacent images. At each acquisition position, the pixel grayscale matrix, the corresponding axial coordinate, radial coordinate, image spatial resolution, and the grayscale repeatability upper limit formed by the self-calibration of the structural imaging device in the same acquisition period are recorded. Images lacking axial coordinates or pixel grayscale matrices are discarded, and the missing acquisition positions are re-acquired. The retained images are arranged in ascending order of axial coordinates to obtain the axial structural image sequence corresponding to the embedded FBG optical fiber.
[0029] Extract the outer contour of the quartz glass fiber corresponding to the quartz glass fiber and the inner contour of the inner coating corresponding to the inner coating from the axial structure image sequence. The outer contour of the quartz glass fiber refers to the set of continuous contour points surrounding the center of the quartz glass fiber and located at the outer boundary of the quartz glass entity in the axial structure image sequence; the inner contour of the inner coating refers to the set of continuous contour points located on the surface of the inner coating facing the quartz glass fiber in the axial structure image sequence. Both use the same axial coordinates, radial coordinates and image spatial resolution to determine the physical contact relationship between the inner coating and the quartz glass fiber.
[0030] The image processing unit processes the axial structure image sequence frame by frame in ascending order of axial coordinates. Taking the fiber optic axis position recorded in each image as the radial starting point, pixels are arranged in ascending order of radial coordinates along each radial direction around the fiber optic axis position. The gray levels of adjacent pixels are subtracted, and the absolute value of the subtraction result is taken to form the gray level difference between adjacent pixels. The gray level difference between adjacent pixels is compared with the upper limit of gray level repeatability recorded in the image. The first boundary point that is greater than the upper limit of gray level repeatability and is continuously closed around the fiber optic axis position is selected from the fiber optic axis position. The first boundary points in each radial direction are then spatially arranged... Adjacent connections are used to form the outer contour of the quartz glass fiber corresponding to the quartz glass fiber. From the outer contour of the quartz glass fiber corresponding to the quartz glass fiber, the search continues outward to find the boundary points of adjacent pixels whose gray level difference is greater than the upper limit of gray level repeatability and which are continuous around the outer contour of the quartz glass fiber corresponding to the quartz glass fiber. When the boundary points exist, the boundary points closest to the outer contour of the quartz glass fiber corresponding to the quartz glass fiber in each radial direction are connected according to spatial adjacency. When the boundary points do not exist, the outer contour points of the quartz glass fiber corresponding to the quartz glass fiber in the same radial direction are used. All the connected boundary points form the inner contour of the inner coating corresponding to the inner coating.
[0031] Based on the physical contact relationship between the inner contour of the inner coating and the outer contour of the quartz glass fiber, the embedded FBG fiber is segmented to obtain the inner coating attachment segment, the inner coating wall separation segment, and the inner coating wrinkling segment.
[0032] Solid contact relationship refers to the structural relationship between the inner contour of the inner coating and the outer contour of the quartz glass fiber under the same axial coordinate and radial direction, where the contours coincide, separate, or separate and overlap. This relationship is based on the image spatial resolution of the axial structural image sequence as a scale that can distinguish between contact and spacing.
[0033] Under the same coordinate reference in the axial structural image sequence, the segmented processing end selects the inner contour points of the inner coating one by one in ascending order of axial coordinates, and selects the outer contour points of the quartz glass fiber in the same axial coordinate and radial direction. The radial coordinates of the inner contour points are subtracted from the radial coordinates of the outer contour points of the quartz glass fiber, and the absolute value of the subtraction result is taken to form the radial contour interval. The radial contour interval is compared with the image spatial resolution of the corresponding image. Axial positions with radial contour intervals less than or equal to the image spatial resolution are marked as solid contact axial positions, and axial positions with radial contour intervals greater than the image spatial resolution are marked as solid contact axial positions. The axial position of the solid contact axial position is merged into the inner coating attachment segment. The axial position of the solid away from the wall that is axially continuous and whose inner contour of the inner coating maintains the same extension direction along the axial direction is merged into the inner coating away from the wall segment. The range of the difference between adjacent axial coordinates of the inner contour of the inner coating in the solid away from the wall changes from positive to negative or from negative to positive, and the continuous range of multiple inner contour points corresponding to the same axial coordinate is merged into the inner coating wrinkle segment. When the contour point is missing, the comparison is re-executed after the contour points that are axially adjacent and radially continuous on both sides of the missing position are supplemented. The inner coating attachment segment, inner coating away from the wall segment and inner coating wrinkle segment are obtained.
[0034] The radial spacing of the contour directly represents the distance between the inner surface of the inner coating and the outer surface of the quartz glass fiber in the same axial position. The spatial resolution of the image limits the minimum distance that the axial structure image can distinguish. The comparison of the two can separate the contour overlap position from the contour separation position. The change of the sign of the axial coordinate difference of the inner contour of the inner coating and the relationship of multiple contour points with the same axial coordinate further separate the unidirectional extension of the wall-detached range from the folded-back overlapping range. Therefore, the merged continuous ranges constitute the inner coating attachment section, the inner coating wall-detached section, and the inner coating wrinkling section, respectively.
[0035] For example, the target computing power service is an AI inference task with a single rated power of 600W. The computing power execution device is determined to be a GPU server with a rated input voltage of 48V, and it is determined to be powered by a 48V DC target busbar slot numbered B3 with a cross-sectional size of 20mm×3mm. The embedded FBG fiber length corresponding to the target busbar slot is determined to be 20mm, with the outer diameter of the quartz glass fiber being 125μm and the outer diameter of the inner coating being 245μm. The FBG gate area is located between 8.0mm and 12.0mm along the axial coordinate. 201 axial junction images with a resolution of 2048×2048 and a pixel size of 2μm are acquired at axial intervals of 0.1mm. Images were constructed, and the outer contour of the quartz glass fiber and the inner contour of the inner coating were extracted from each image. The radial distance between the two contours along the circumferential direction was calculated. The inner coating attachment section was identified as the radial distance within the axial coordinate range of 0 mm to 6.4 mm with a radial distance of 0 to 1.5 μm and a contour contact ratio of not less than 95%. The inner coating separation section was identified as the radial distance within the axial coordinate range of 6.5 mm to 12.7 mm with a radial distance of 8 to 22 μm and a contour contact ratio of less than 20%. The inner coating wrinkling section was identified as the radial distance within the axial coordinate range of 12.8 mm to 20 mm with a periodic variation between 0 and 14 μm and a radial undulation amplitude of 6 to 10 μm in the inner contour of the inner coating.
[0036] In an embodiment of the present invention, an inner coating wrinkle collar region is obtained, including: The inner coating folded collar region refers to the continuous area that starts from the inner coating detaching from the outer surface of the quartz glass fiber, extends through the inner coating folding and folding, and extends to the inner coating reattaching to the outer surface of the quartz glass fiber. Its boundary is jointly defined by the collar detachment position, collar folding position, collar folding position, and collar reattaching position, and is used to determine the FBG gate area covered by the folded collar.
[0037] The junction between the inner coating attachment section and the inner coating wall separation section is extracted to obtain the position where the collar separates. The collar disengagement position refers to the axial position where the inner contour of the inner coating begins to separate from the outer contour of the quartz glass fiber when the fiber moves from the inner coating attachment section to the inner coating separation section along the embedded FBG fiber axis. This position constitutes the starting boundary of the inner coating wrinkle collar area.
[0038] The position extraction end arranges the inner coating attachment segment and the inner coating separation segment in ascending order of axial coordinates. It compares the segmentation of adjacent axial positions one by one along the spatial continuity direction of the inner contour of the inner coating. When the previous axial position belongs to the inner coating attachment segment and the next axial position belongs to the inner coating separation segment, it checks whether the inner coating separation segment extends continuously along the inner contour of the inner coating to the inner coating wrinkle segment. If the check fails, it continues to compare the next connection position of the inner coating attachment segment and the inner coating separation segment. If the check passes, it selects the contour point in the next axial position where the inner contour of the inner coating begins to separate from the outer contour of the quartz glass fiber, and determines the axial coordinate of the contour point as the collar disengagement position.
[0039] The segmentation of adjacent axial positions limits the boundary between the continuous attached state and the continuous detached state to the same inner contour of the inner coating. Furthermore, since the detached section of the inner coating can extend continuously to the wrinkled section of the inner coating, local detached boundaries unrelated to the wrinkled collar are excluded. Therefore, the selected axial coordinate corresponds to the collar disengagement position where the inner coating begins to form a wrinkled collar.
[0040] The position where the axial extension direction of the inner coating changes in the section of the inner coating away from the wall is extracted to obtain the fold-back position of the collar; The axial extension direction refers to the direction of increase or decrease of the coordinates of the inner contour of the inner coating along its spatial connection order on the axial direction of the embedded FBG fiber; the collar fold-back position refers to the position where the axial coordinate increase or decrease direction changes and begins to fold back after the inner coating leaves the quartz glass fiber, used to separate the inner coating before folding back and the inner coating after folding back.
[0041] Starting from the collar disengagement position, the position extraction end sequentially selects two adjacent inner contour points along the spatial connection order of the inner contour of the inner coating off-wall section. The axial coordinate of the inner contour point of the next inner coating is subtracted from the axial coordinate of the previous inner coating. The non-zero axial coordinate difference corresponding to each adjacent inner coating inner contour point is retained, and the positive and negative signs of the adjacent non-zero axial coordinate differences are compared according to the spatial connection order. If the positive and negative signs of the adjacent non-zero axial coordinate differences have not changed, the comparison of the next set of adjacent non-zero axial coordinate differences continues. When the adjacent non-zero axial coordinate difference changes from positive to negative or from negative to positive, the inner contour point of the inner coating corresponding to the two adjacent non-zero axial coordinate differences is selected, and the axial coordinate of the inner contour point of the inner coating is determined as the collar folding position.
[0042] The non-zero axial coordinate difference formed by the spatial connection sequence of the inner contour of the inner coating indicates the axial extension direction of the inner coating in each connection interval. The sign change of the continuous non-zero axial coordinate difference indicates that the inner coating no longer extends along the original direction and turns back from the conversion point. Therefore, the common inner contour point of the inner coating is the fold-back position of the collar.
[0043] The overlapping position of the inner coating after folding and the inner coating before folding in the inner coating wrinkle section is extracted to obtain the collar folding position; The inner coating before folding back refers to the portion of the inner coating extending from the disengaged position of the collar to the folded-back position of the collar; the inner coating after folding back refers to the portion of the inner coating extending along the opposite axial direction from the folded-back position of the collar; overlapping refers to the radial range where the inner coating before folding back and the inner coating after folding back occupy the same axial position; the collar folding position refers to the axial position where the inner coating after folding back begins to overlap with the inner coating before folding back when it continues to extend from the folded-back position of the collar.
[0044] The position extraction end separates the inner coating before and after the folding of the inner coating in the wrinkled section of the inner coating with the collar folding position. Under the same axial coordinate, the radial coordinate start point and radial coordinate end point occupied by the inner coating before folding and the radial coordinate start point and radial coordinate end point occupied by the inner coating after folding are extracted respectively. The radial coordinate start point with the largest value among the two radial coordinate start points is selected and the radial coordinate end point with the smallest value among the two radial coordinate end points is selected. When the radial coordinate start point with the largest value is greater than the radial coordinate end point with the smallest value, the next axial coordinate of the inner coating after folding is processed. When the radial coordinate start point with the largest value is less than or equal to the radial coordinate end point with the smallest value, the position corresponding to the axial coordinate is marked as the overlapping position. The first overlapping position is selected along the spatial connection order starting from the collar folding position of the inner coating after folding, and the axial coordinate of the first overlapping position is determined as the collar folding position.
[0045] The maximum value of the radial coordinate starting points of the two inner coating portions defines the inner boundary of the common radial range, and the minimum value of the two radial coordinate ending points defines the outer boundary of the common radial range. If the inner boundary is less than or equal to the outer boundary, it indicates that the two radial ranges have a common position. Selecting the first position that satisfies this relationship along the inner coating after folding back can determine the loop overlap position where the inner coating after folding back begins to cover the inner coating before folding back.
[0046] The junction between the inner coating wall section and the inner coating attachment section is extracted to obtain the collar reattachment position; The collar reattachment position refers to the axial position where, as the inner coating continues to extend from the collar re-fold position, it enters the inner coating attachment section from the inner coating wall section and makes the inner contour of the inner coating re-contact the outer contour of the quartz glass fiber. This position constitutes the termination boundary of the inner coating wrinkled collar area.
[0047] Starting from the folded collar position, the position extraction end compares the segmentation of adjacent axial positions one by one along the spatial continuity of the inner contour of the inner coating. When the previous axial position belongs to the inner coating off-wall segment and the next axial position belongs to the inner coating attachment segment, it checks whether the radial interval of the contour of the next axial position is less than or equal to the image spatial resolution of the corresponding image. If the check fails, it continues to compare the next set of adjacent axial positions. If the check passes, it selects the contour point in the next axial position where the inner contour of the inner coating re-contacts the outer contour of the quartz glass fiber, and determines the axial coordinate of the contour point as the collar reattachment position.
[0048] By finding the adjacent positions of the wall-detached segments that become attached segments along the inner contour of the same inner coating from the folded collar position, the search range can be limited to the folded portion of the current folded collar. If the radial interval of the contour is less than or equal to the image spatial resolution, it means that the two solid surfaces have resumed contact. Therefore, the selected axial coordinate corresponds to the collar reattachment position at the end of the collar.
[0049] Based on the collar detachment position, collar fold-back position, collar re-overlap position, and collar re-attachment position, the wrinkled section of the inner coating is extracted to obtain the wrinkled collar area of the inner coating.
[0050] The region extraction end places the collar disengagement position, collar fold-back position, collar overlap position, and collar reattachment position under the same axial coordinate reference in the axial structure image sequence. It checks whether the collar fold-back position and collar overlap position are within the closed axial range defined by the collar disengagement position and the collar reattachment position. If the check fails, it returns to the extraction process of the collar fold-back position and collar overlap position and re-extracts along the same inner contour of the inner coating until the collar fold-back position and collar overlap position are within the closed axial range. It extracts the axial coordinates of the inner coating wrinkle section that are greater than or equal to the axial coordinates of the collar disengagement position and less than or equal to the axial coordinates of the collar reattachment position. It then sequentially passes through all the inner coating contours and their occupied image areas at the collar fold-back position and collar overlap position along the spatial connection path of the inner coating contour. Finally, it connects all the extracted inner coating contours and their occupied image areas to form the inner coating wrinkle collar region.
[0051] The collar disengagement position and collar reattachment position define the axial start and end boundaries of the collar. The collar fold-back position and collar overlap position define the fold-back and overlap structures that must be included within these start and end boundaries. By jointly filtering the image parts that are discontinuous with the current fold-back path within the boundary according to the axial range and the inner contour space connection path of the inner coating, the connected area satisfies all the positional constraints of the inner coating collar area.
[0052] For example, taking the starting end of the embedded FBG fiber as axial coordinate 0mm, the sampling interval of the axial structure image is 0.1mm. The inner coating attachment section maintains contact with the outer contour of the quartz glass fiber within the axial coordinate range of 0mm to 6.4mm. The inner coating separation section starts from axial coordinate 6.5mm and forms a radial distance of more than 8μm with the outer contour of the quartz glass fiber. The midpoint between axial coordinates 6.4mm and 6.5mm, 6.45mm, is determined as the collar disengagement position. In the inner coating separation section, the axial extension direction of the inner contour of the inner coating is compared frame by frame. The axial direction component at axial coordinate 9.8mm changes from a positive value of 0.98 to a negative value of -0.91. The axial coordinate 9.8mm is determined as the collar folding position. In the inner coating wrinkling section, the inner contour of the inner coating after folding and the inner contour of the inner coating before folding are... An overlapping area with a length of 0.42 mm and a radial width of 18 μm is formed at an axial coordinate of 14.6 mm. The axial coordinate of 14.6 mm is determined as the collar re-folding position. The inner coating is in a detached state until the axial coordinate of 17.6 mm, and then it recovers to an attachment state with a radial spacing of no more than 1.5 μm and a contact ratio of 96% starting from the axial coordinate of 17.7 mm. The midpoint between the two, 17.65 mm, is determined as the collar re-attachment position. The pixel area enclosed by the inner contour before and after the folding is extracted from the inner coating wrinkle section according to the collar detachment position of 6.45 mm, the collar folding position of 9.8 mm, the collar re-folding position of 14.6 mm, and the collar re-attachment position of 17.65 mm. This yields an inner coating wrinkle collar area with an axial length of 11.2 mm and a maximum radial width of 0.18 mm.
[0053] In an embodiment of the present invention, a ring-covered power supply section is obtained, including: The power supply section covered by the collar refers to the power supply section on the embedded FBG fiber that includes the collar-covered gate area, and is used to determine the power supply range of the computing execution device corresponding to the inner coating wrinkled collar area.
[0054] Obtain the position of each FBG region on the embedded FBG fiber; The FBG grid area position refers to the starting axial coordinate, ending axial coordinate, and center axial coordinate of each FBG grid area under the embedded FBG fiber axial coordinate reference. It is derived from the correspondence between the fiber fabrication record and the fiber deployment record and is used to determine whether the FBG grid area is covered by the inner coating corrugated collar area.
[0055] The fiber management end uses the fiber identifier of the embedded FBG fiber as the association key to extract the identifiers of each FBG grating area with the same fiber identifier from the fiber manufacturing record, as well as the start distance, end distance, and center distance of each FBG grating area relative to the fiber start position. Then, based on the fiber start position and axial extension direction in the fiber deployment record, each start distance, end distance, and center distance is mapped to the fiber axial coordinate reference used in the axial structure image sequence, forming the FBG grating area position on the embedded FBG fiber, including the FBG grating area identifier, start axial coordinate, end axial coordinate, and center axial coordinate.
[0056] Based on the inner coating wrinkle ring area, the location of each FBG gate area is extracted by regional overlap to obtain the ring-covered gate area; Region overlap refers to the axial interval defined by the FBG gate area and the inner coating wrinkled collar area having the same axial position under the same fiber axial coordinate reference; collar-covered gate area refers to the FBG gate area that overlaps with the inner coating wrinkled collar area, and its FBG gate area position is used to continue matching the fiber position range corresponding to the power supply section.
[0057] The overlapping extraction end transforms the inner coating wrinkle loop region and the positions of each FBG gate region to the same fiber axial coordinate reference used in the axial structure image sequence. It extracts the starting and ending axial coordinates of the inner coating wrinkle loop region and selects the starting and ending axial coordinates of each FBG gate region position one by one. The starting axial coordinate with the largest value is selected from the starting axial coordinates of the inner coating wrinkle loop region and the starting axial coordinates of the FBG gate region position. The ending axial coordinate with the smallest value is selected from the ending axial coordinates of the inner coating wrinkle loop region and the ending axial coordinates of the FBG gate region position. When the starting axial coordinate with the largest value is greater than the ending axial coordinate with the smallest value, the corresponding FBG gate region is excluded. When the starting axial coordinate with the largest value is less than or equal to the ending axial coordinate with the smallest value, the corresponding FBG gate region is retained. All the retained FBG gate regions form a loop covering the gate region.
[0058] The maximum value of the starting axial coordinate and the minimum value of the ending axial coordinate of the two axial intervals define the two ends of the common axial range. The maximum starting axial coordinate being less than or equal to the minimum ending axial coordinate indicates that the FBG gate area and the inner coating wrinkle collar area have at least one common axial position. Therefore, the retained FBG gate area is the collar-covered gate area covered by the inner coating wrinkle collar area.
[0059] Based on the power supply location range of the computing power execution equipment, the target bus trunking is divided into sections to obtain multiple power supply sections; The power supply location range refers to the connection position of the power supply branch of the computing power execution device on the target bus trunk and the continuous power supply coverage area corresponding to the connection position, which is represented by the axial coordinate of the target bus trunk; the power supply section refers to the continuous section of the target bus trunk that is divided by the boundary of the power supply location range and maintains a power supply correspondence with at least one computing power execution device.
[0060] The power supply segment division end extracts the connection position of the power supply branch, the starting axial coordinate of the power supply range, and the ending axial coordinate of the power supply range of each computing power execution device from the power supply topology record of the target bus trunking. It merges the starting axial coordinates and ending axial coordinates of each power supply range and deletes duplicate boundary coordinates with the same coordinate value. It arranges all boundary coordinates in ascending order of axial coordinates and forms candidate power supply segments with each pair of adjacent boundary coordinates as the two ends of the segment. The starting axial coordinate of the candidate power supply segment is greater than or equal to the starting axial coordinate of the power supply range of any computing power execution device, and the ending axial coordinate of the candidate power supply segment is less than or equal to the ending axial coordinate of the power supply range of the same computing power execution device as the retention condition. Candidate power supply segments that do not meet the retention condition are deleted. The corresponding computing power execution devices are marked on the candidate power supply segments that meet the retention conditions. Candidate power supply segments that are axially adjacent and have the same corresponding computing power execution devices are connected. Multiple power supply segments are formed by the connected continuous segments.
[0061] The entire starting and ending boundaries of the power supply location range divide the target busbar into candidate power supply sections where the power supply correspondence does not change within the section. Using the condition that both ends of the candidate power supply section fall within the power supply location range of the same computing power execution device as a retention condition, the target busbar section without a power supply correspondence with the computing power execution device can be excluded. Then, by connecting adjacent sections with the same power supply correspondence, multiple power supply sections with complete boundaries and without omissions can be obtained.
[0062] Obtain the fiber location range corresponding to each power supply section on the embedded FBG fiber; The fiber optic location range refers to the axial range of the target busbar trunking in the power supply section, which is mapped onto the embedded FBG fiber according to the fiber optic deployment record. It includes the starting axial coordinates and ending axial coordinates of the fiber optic range and is used to support the FBG grid area position corresponding to the ferrule coverage area.
[0063] The fiber optic management terminal uses the target busbar identifier and the embedded FBG fiber identifier to jointly retrieve fiber optic deployment records, obtaining corresponding records of busbar location ranges and fiber optic location ranges arranged sequentially along the target busbar. It then selects the starting and ending axial coordinates of each power supply section, extracting records of busbar location ranges and fiber optic location ranges that cover the starting or ending axial coordinates of the power supply section. Based on the axial direction recorded in the corresponding records, it selects the starting axial coordinate of the fiber optic range corresponding to the starting axial coordinate of the power supply section and the ending axial coordinate of the fiber optic range corresponding to the ending axial coordinate of the power supply section. When a power supply section crosses adjacent corresponding records, it connects the fiber optic location ranges in each corresponding record according to the record order. The starting axial coordinate of the fiber optic range, the ending axial coordinate of the fiber optic range, and the continuous fiber axial ranges between them constitute the corresponding fiber optic location range of each power supply section on the embedded FBG fiber.
[0064] Based on the FBG grid area location corresponding to the ring-covered grid area, the location range of the optical fiber corresponding to each power supply section is extracted to obtain the ring-covered power supply section.
[0065] When the center axial coordinate of the location falls within the coverage area of the finger ring is between the starting and ending axial coordinates of the fiber location range corresponding to the power supply section, and is located at the common boundary of adjacent fiber location ranges, the corresponding power supply section is selected according to the boundary attribution relationship determined when the power supply section is divided.
[0066] The location-falling extraction end selects the central axial coordinate of the FBG gate area corresponding to the ring-covered gate area one by one, and selects the starting axial coordinate and ending axial coordinate of the fiber range corresponding to each power supply segment one by one. The central axial coordinate being greater than or equal to the starting axial coordinate and less than the ending axial coordinate is used as the location-falling condition. For the fiber position range at the end of the axial order, the central axial coordinate being equal to the ending axial coordinate is also used as the location-falling condition. When the central axial coordinate is located at the common boundary of two adjacent fiber position ranges, one power supply segment is retained according to the boundary assignment relationship recorded when multiple power supply segments are formed. Power supply segments that do not meet the location-falling condition are excluded. All power supply segments that meet the location-falling condition and contain the central axial coordinate of the FBG gate area corresponding to any ring-covered gate area are retained to obtain the ring-covered power supply segments.
[0067] The central axial coordinates of the FBG gate area corresponding to the ring-covered gate area determine the axial position of each ring-covered gate area to a single fiber. The start and end axial coordinates of the fiber position range constitute the closed boundary of the power supply section on the embedded FBG fiber. By adopting the comparison relationship that the start point includes the end point but not the end point, and that the end of the axial order includes the end point, it is possible to avoid the common boundary being repeatedly assigned to two power supply sections. Therefore, the retained power supply section is the ring-covered power supply section that includes the ring-covered gate area.
[0068] The collection module extracts the carbon accounting results corresponding to the target computing power service based on the power supply section covered by the ring, and obtains the tenant's computing power carbon storage record. In an embodiment of the present invention, obtaining the tenant's computing power carbon storage record includes: Tenant computing power carbon storage record refers to a persistent data record formed by combining computing power request hash, batch merge records and ring-related carbon accounting results according to the request correspondence of the target computing power business, with the tenant identifier corresponding to the target computing power business as the index. This record retains the source identifier and association order of each component data and is used to form carbon data to be encrypted by tenant.
[0069] Obtain the tenant identifier, computing power request hash, batch merge record, computing power energy consumption receipt and carbon accounting result corresponding to the target computing power service; Tenant identifier refers to the unique code assigned to tenants using computing power services and written into the business acceptance record in the tenant registration record, used to define the ownership of computing power carbon data; computing power request hash refers to the fixed-length digest data formed by the request acceptance end according to the hash rules recorded in the request record for the content of the target computing power service, which is written into the request acceptance record along with the request identifier and hash rule version, used to associate the data formed by the same computing power request in the batch merging and carbon accounting stages; batch merging record refers to the data record formed by the batch scheduling end when combining computing power requests entering the same execution batch, which includes batch identifier, computing power request hash list, merging order, execution time period, and computing power execution device identifier, used for... The target computing power service is restored to its corresponding position in the execution batch; the computing power energy consumption receipt refers to the data record formed by the energy consumption metering end after the computing power execution device completes the target computing power service. It includes the service identifier, computing power execution device identifier, energy consumption receipt identifier, metering start and end time, energy consumption, metering unit and record status, and is used to provide the equipment energy consumption basis for the carbon accounting results; the carbon accounting results refer to the data record formed by the carbon accounting end based on the computing power energy consumption receipt and its corresponding carbon emission factor. It includes the computing power request hash, energy consumption receipt identifier, computing power execution device identifier, carbon emission factor source and version, carbon emission amount, metering unit and record status, and is used to collect the carbon data corresponding to the power supply section covered by the ring.
[0070] The business data acquisition end uses the business identifier, computing power request identifier, and execution period of the target computing power service as matching fields. It selects tenant identifiers with the same business identifier and whose tenant status covers the execution period from the associated data of tenant registration records and business acceptance records. It selects computing power request hashes with the same computing power request identifier and valid record status from the request acceptance records. It selects batch merge records from the batch scheduling records whose computing power request hash list contains the aforementioned computing power request hashes and whose execution period intersects with the execution period of the target computing power service. Finally, it selects energy consumption receipt records generated by the energy consumption metering end with the same business identifier and whose metering start and end times are within the execution period of the target computing power service. The computing power energy consumption receipt selects carbon accounting results from the carbon accounting records generated by the carbon accounting terminal that have the same computing power request hash and whose energy consumption receipt identifier belongs to the computing power energy consumption receipt. When no unique matching record exists in any data source or the content of the valid record corresponding to the same identifier conflicts, this step is stopped and a missing record or conflict verification request is sent to the corresponding data management terminal. After the corresponding data management terminal writes back the unique valid record, each matching operation is re-executed. All data that passes the matching are kept in correspondence according to the computing power request hash and energy consumption receipt identifier to obtain the tenant identifier, computing power request hash, batch merged record, computing power energy consumption receipt and carbon accounting result corresponding to the target computing power service.
[0071] The computing power execution devices powered by the power supply section covered by the ring are extracted to obtain the ring-related computing power execution devices; The ring-linked computing power execution device refers to the device entity in the computing power execution device corresponding to the target computing power service that is confirmed by the power supply topology record to transmit power through any ring-covered power supply segment during the execution period of the target computing power service. Its device identifier corresponds to the ring-covered power supply segment identifier, which is used to limit the extraction scope of subsequent energy consumption receipts.
[0072] The device extraction end selects the power supply segment identifiers of the power supply segments covered by the loop one by one. It extracts the device power supply relationships with the same power supply segment identifier and whose effective power supply period covers the target computing power service execution period from the power supply topology record of the target bus trunking. It compares the computing power execution device identifier in the device power supply relationship with the device identifier of the computing power execution device corresponding to the target computing power service item by item. It retains the device entities with the same device identifier and whose power supply direction is from the power supply segment covered by the loop to the computing power execution device. It excludes the device entities with different device identifiers or whose effective power supply period does not cover the target computing power service execution period. When the same device identifier corresponds to multiple device power supply relationships with the same content, only one device entity is retained. When the power supply direction or effective power supply period corresponding to the same device identifier conflicts with each other, this step is stopped and the process is returned to the power supply topology record maintenance end for verification. The loop-associated computing power execution device is obtained from all the retained device entities.
[0073] Extract the computing power energy consumption receipts corresponding to the ring-linked computing power execution devices from the computing power energy consumption receipts corresponding to the target computing power service to obtain the ring-linked energy consumption receipts; The ring-linked energy consumption receipt refers to the set of receipts in the energy consumption receipts corresponding to the target computing power service, where the computing power execution device identifier belongs to the ring-linked computing power execution device and the metering start and end times are within the execution period of the target computing power service. This set of receipts retains the energy consumption receipt identifier, computing power execution device identifier, metering start and end times, energy consumption, metering unit, and record status, which are used to extract the carbon accounting results.
[0074] The energy consumption receipt extraction end uses the device identifier of the ring-linked computing power execution device as the matching key. It checks the computing power execution device identifier, service identifier, metering start and end time, and record status of each computing power energy consumption receipt corresponding to the target computing power service. It retains computing power energy consumption receipts whose computing power execution device identifier is the same as the device identifier of any ring-linked computing power execution device, whose service identifier is the same as the service identifier of the target computing power service, whose metering start and end time is within the execution period of the target computing power service, and whose record status is valid. It excludes computing power energy consumption receipts that do not meet any matching conditions. For duplicate records with the same energy consumption receipt identifier and the same content, only one is retained. For records with the same energy consumption receipt identifier but conflicting energy consumption, metering unit, or metering start and end time, extraction is stopped and the data is returned to the energy consumption metering end for verification. When no valid computing power energy consumption receipt is found for any ring-linked computing power execution device, a missing data supplementation request is sent to the energy consumption metering end. After the supplementation is completed, the data is re-matched. All retained computing power energy consumption receipts are arranged according to the metering start time and energy consumption receipt identifier to obtain the ring-linked energy consumption receipt.
[0075] Based on the ring-related energy consumption receipt, the carbon accounting results corresponding to the target computing power business are extracted to obtain the ring-related carbon accounting results; The ring-linked carbon accounting result refers to the carbon accounting data set in the carbon accounting result corresponding to the target computing power service, where the energy consumption receipt identifier is the same as the ring-linked energy consumption receipt and the corresponding relationship of the computing power execution device is maintained. This data set retains the computing power request hash, energy consumption receipt identifier, carbon emission factor source and version, carbon emission amount, unit of measurement and record status, and is used for batch merging and collection of records.
[0076] The carbon accounting result extraction end selects the energy consumption receipt identifier and computing power execution device identifier from the ring-linked energy consumption receipts one by one, and compares the energy consumption receipt identifier, computing power execution device identifier, computing power request hash, and record status in the carbon accounting results corresponding to the target computing power service. It retains carbon accounting results where the energy consumption receipt identifier is the same as the energy consumption receipt identifier in the ring-linked energy consumption receipt, the computing power execution device identifier is the same, the computing power request hash is the same as the computing power request hash corresponding to the target computing power service, and the record status is valid. It excludes carbon accounting results where any comparison relationship is not valid. When there are multiple valid versions of the same energy consumption receipt identifier, it retains the record where the carbon emission factor version corresponds to the accounting time point recorded in the carbon accounting result and the version status is valid. When there is no unique corresponding record or the carbon emission amount and unit of measurement of the corresponding record are missing, it stops this step and returns to the carbon accounting end to supplement or verify. It organizes all the retained carbon accounting results according to the arrangement order of the ring-linked energy consumption receipts to obtain the ring-linked carbon accounting results.
[0077] Based on the hash of computing power requests, the batch merge records and the carbon accounting results associated with the ring are aggregated accordingly to obtain the computing power carbon aggregation records; The computing power carbon collection record refers to a data record formed by combining the merged information of the batch in which the target computing power service belongs with the ring-linked carbon accounting results, using the computing power request hash as the associated index. It includes the computing power request hash, batch identifier, merge order, execution time period, computing power execution device identifier, energy consumption receipt identifier, carbon emission factor source and version, carbon emission amount and unit of measurement, and is used to write tenant affiliation information.
[0078] The data collection end uses the hash of the computing power request corresponding to the target computing power service as the collection key. It locates the request item with the same collection key from the list of computing power request hashes in the batch merged records and retains the batch identifier, merging order, execution time period, and computing power execution device identifier corresponding to the request item. It locates the record with the same computing power request hash and collection key from the ring-linked carbon accounting results and retains the corresponding energy consumption receipt identifier, carbon emission factor source and version, carbon emission amount, and unit of measurement. When there is no collection key in the batch merged records or the same collection key corresponds to multiple conflicting batch information, the collection is stopped and returned to the batch scheduling end for verification. When there is no record corresponding to the collection key in the ring-linked carbon accounting results, the collection is stopped and returned to the carbon accounting end for verification. The collection key, the batch information that has passed the verification, and the ring-linked carbon accounting results arranged according to the energy consumption receipt identifier are written into the same record, and the correspondence between the computing power execution device identifier and the energy consumption receipt identifier is maintained to obtain the computing power carbon collection record.
[0079] Write the tenant identifier into the computing power carbon collection record to obtain the tenant computing power carbon storage record.
[0080] The evidence storage record assembly terminal takes the tenant identifier and computing power carbon collection record corresponding to the target computing power service as the processing objects. It checks whether the computing power request hash in the computing power carbon collection record is the same as the computing power request hash belonging to the tenant identifier in the service acceptance record. If they are the same, the tenant identifier is written into the tenant affiliation field of the computing power carbon collection record and the batch information, ring-linked carbon accounting results and their corresponding order in the computing power carbon collection record are retained. If they are different, the writing stops and the process is returned to the service data acquisition terminal for verification. When the tenant affiliation field already has content, the existing content is retained and the assembly continues only if the existing content is the same as the tenant identifier. If the existing content is different from the tenant identifier, the writing stops and the process is returned to the tenant registration record maintenance terminal for verification. The tenant computing power carbon evidence storage record is obtained from the computing power carbon collection record after the tenant identifier is written.
[0081] The encryption module performs fragmented encryption on the field encrypted carbon data fragments based on the tenant identifier in the tenant's computing power carbon storage record, thus obtaining the tenant's encrypted carbon data fragments. In an embodiment of the present invention, obtaining tenant encrypted carbon data fragments includes: Tenant encrypted carbon data sharding refers to the process of dividing tenant computing power carbon storage records according to tenant identifiers, performing field-level encryption on the tenant business fields, and then performing sharding encryption on the entire field encrypted carbon data shard to form a data unit. This data unit contains tenant identifier, sharded ciphertext, key version, encryption algorithm identifier, and encryption parameters, and is used to write to the blockchain and accept subsequent verification field extraction.
[0082] Based on the tenant identifier in the tenant's computing power carbon storage record, the tenant's computing power carbon storage record is fragmented to obtain tenant carbon data fragments; Tenant carbon data sharding refers to the independent data units divided from the tenant's computing power carbon storage record according to the same tenant identifier relationship. Each independent data unit contains only the computing power request hash, batch information, ring-linked carbon accounting results and the original arrangement relationship of each field corresponding to the same tenant identifier, which is used to limit the tenant range of field-level encryption.
[0083] The sharding processing end selects the tenant identifier and its corresponding computing power request hash, batch information, and ring-related carbon accounting result from each tenant's computing power carbon storage record. It performs an equivalence comparison according to the encoded content of the tenant identifier, grouping records with the same tenant identifier into the same data unit while maintaining the existing order of each record in the tenant's computing power carbon storage record. Records with different tenant identifiers are grouped into different data units. When any record is missing a tenant identifier or the same record corresponds to multiple inconsistent tenant identifiers, sharding stops and returns to the storage record assembly end for verification. When records with the same tenant identifier and the same computing power request hash have completely identical content, only one copy is retained. When records with the same tenant identifier and the same computing power request hash have conflicting content, sharding stops and returns to the business data acquisition end for verification. The tenant carbon data shard is formed by the tenant identifier and the computing power request hash, batch information, and ring-related carbon accounting result belonging to that tenant identifier.
[0084] Obtain tenant business fields from tenant carbon data shards; Tenant business fields refer to data items in a tenant's carbon data shard that carry the target computing power business content and require access control by field. The scope of these fields is limited by the field name and field purpose marker in the business data structure record. They include computing power request hash, batch information, and energy consumption receipt identifier, carbon emission factor source and version, carbon emission amount and unit of measurement in the ring-related carbon accounting results. The field name, field data type, field content and the order of the record together maintain the position of the field in the shard.
[0085] The field extraction end takes each record in the tenant's carbon data shard as the processing object, and obtains the field name, field data type, and field purpose marker that are the same as the data version of the tenant's computing power carbon storage record from the business data structure record. It compares the field names in the tenant's carbon data shard with the field names in the business data structure record one by one, and retains the fields with the same field name and the field purpose marker indicating the target computing power business content. It also introduces the field data type, field content, and record order into the retained fields, and excludes shard management fields whose tenant identifier, record status, and field purpose marker are not the target computing power business content. When the field name in the tenant's carbon data shard does not have a unique corresponding item in the business data structure record or the field data type is inconsistent with the business data structure record, the extraction stops and returns to the business data structure record maintenance end for verification. All retained fields are arranged according to the record order and the existing field order in the tenant's carbon data shard to obtain the tenant's business fields.
[0086] Obtain the data field-level key corresponding to the tenant's business field; Data field-level keys refer to the encryption key data configured by the key management terminal according to the tenant identifier and the field name of the tenant's business field. It includes the tenant identifier, field name, key identifier, key material, encryption algorithm identifier, key version, parameter generation rules, and key status, and is used to perform field-level encryption only on the corresponding business field of the corresponding tenant.
[0087] The key acquisition end selects the field name of each tenant's business field and inputs the tenant identifier from the tenant's carbon data shard. It compares the tenant identifier, field name, key status, and key validity period from the field key records in the key management end. It retains the field key records where the tenant identifier and field name are the same, the key status is valid, and the key validity period covers the current encryption time. It obtains the key identifier, key material, encryption algorithm identifier, key version, and parameter generation rules from each retained field key record and keeps them corresponding to the tenant's business field according to the field name. When no valid field key record exists for any tenant's business field, it sends a key configuration request for the corresponding tenant identifier and field name to the key management end and re-compares after the valid field key record is written back. When the same tenant identifier and field name correspond to multiple valid field key records with the same key version but different key identifiers, it stops acquiring and returns to the key management end for verification. The data field-level key corresponding to the tenant's business field is obtained from the key data obtained from the compared field key records.
[0088] By using data field-level keys, the tenant's business fields are encrypted at the field level to obtain field-encrypted carbon data fragments; Field-level encryption refers to the encryption execution end processing a single tenant business field as the processing unit, using a data field-level key corresponding to the tenant identifier and field name to convert the field content into field ciphertext while retaining the field location information; field-encrypted carbon data sharding refers to the data unit formed after all tenant business fields in the tenant carbon data shard are replaced with field ciphertext, which retains the tenant identifier, field name, field data type, key version, encryption parameters, and the original record order of each field, and is used to continue to perform sharding encryption.
[0089] The encryption execution end selects tenant business fields one by one, encodes the field name, data type, and content of the tenant business fields into a continuous byte sequence according to the existing field order in the tenant carbon data shard. It obtains the key material, encryption algorithm identifier, key version, and parameter generation rule that uniquely correspond to the tenant identifier and field name from the data field-level key. It generates encryption parameters for the current tenant business field according to the parameter generation rule. The continuous byte sequence and encryption parameters are sequentially sent to the encryption operation specified by the encryption algorithm identifier and the encryption operation is performed using the key material. The data completely returned by the encryption operation is determined as the field ciphertext. The field ciphertext, along with the field name, data type, key version, and encryption parameters, is written back to the original position of the current tenant business field in the tenant carbon data shard. If the field encoding fails or the encryption operation does not completely return the field ciphertext, the processing stops and the unencrypted content of the tenant carbon data shard is restored. After the field content is repaired or the data field-level key is obtained again, the processing is restarted according to the existing field order. After all tenant business fields are written back to the field ciphertext, the tenant identifier and the original correspondence of each field are retained, resulting in the field-encrypted carbon data shard.
[0090] Field names, field data types, and field contents form a continuous byte sequence according to the existing field order, giving each tenant's business field a defined encrypted input boundary. The data field-level key, which uniquely corresponds to the tenant identifier and field name, ensures that the ciphertext of different business fields is formed by their respective key materials. The key version and encryption parameters maintain the field positioning relationship after being written back to their original positions with the ciphertext. Therefore, all field ciphertexts and their positioning information together satisfy the composition constraints of the field encrypted carbon data fragment.
[0091] Retrieve the tenant master key corresponding to the tenant identifier; The tenant master key refers to the encryption key data configured by the key management terminal for a single tenant identifier and used to protect the complete data fragments of that tenant. It includes the tenant identifier, key identifier, key material, encryption algorithm identifier, key version, parameter generation rules, effective period, and key status. It is used to convert the field-encrypted carbon data fragments into fragment ciphertext that can only be decrypted by the corresponding tenant key system.
[0092] The key acquisition end obtains the tenant identifier from the encrypted carbon data fragment and compares the tenant identifier, key status, and key validity period from the tenant key record of the key management end using the tenant identifier as the matching key. It retains the tenant key record with the same tenant identifier, valid key status, and key validity period covering the current encryption time point. It obtains the key identifier, key material, encryption algorithm identifier, key version, and parameter generation rules from the retained tenant key record. When there is no valid tenant key record, it sends a master key configuration request for the corresponding tenant identifier to the key management end and compares again after the valid tenant key record is written back. When the same tenant identifier corresponds to multiple valid tenant key records with the same key version but different key identifiers, it stops acquiring and returns to the key management end for verification. The tenant master key corresponding to the tenant identifier is obtained from the key data obtained from the unique valid tenant key record.
[0093] Using the tenant's master key, the encrypted carbon data fragments are encrypted in segments to obtain the tenant's encrypted carbon data fragments.
[0094] Fragmented encryption refers to the process by which the encryption execution end encrypts the carbon data fragments according to the record order and field order, encodes the complete fragment content, and then converts it into fragmented ciphertext using the tenant master key corresponding to the tenant identifier. This process forms a tenant-wide overall protection layer in addition to field-level encryption and retains the encryption information required to restore the fragment order.
[0095] The encryption execution end takes the field-encrypted carbon data fragment as the processing object. According to the record order and field order in the field-encrypted carbon data fragment, it encodes the tenant identifier, field name, field data type, field ciphertext, data field-level key version, and field encryption parameters into a fragment byte sequence in sequence. It obtains the key material, encryption algorithm identifier, key version, and parameter generation rule corresponding to the tenant identifier from the tenant master key. According to the parameter generation rule, it generates fragment encryption parameters for the field-encrypted carbon data fragment. The fragment byte sequence and fragment encryption parameters are sequentially sent to the encryption operation specified by the encryption algorithm identifier and the encryption operation is performed using the key material. The data completely returned by the encryption operation is determined as the fragment ciphertext. If the fragment byte sequence encoding fails or the encryption operation does not completely return the fragment ciphertext, the processing stops and incomplete data is not retained. After the field-encrypted carbon data fragment or the tenant master key is verified, the encoding and encryption operation are re-executed. The tenant identifier, fragment ciphertext, key version of the tenant master key, encryption algorithm identifier, and fragment encryption parameters are combined to obtain the tenant encrypted carbon data fragment.
[0096] The record order and field order in the field-encrypted carbon data fragments enable the fragment byte sequence to fully carry the field ciphertext and its corresponding information. The tenant master key corresponding to the tenant identifier restricts the fragment byte sequence to the current tenant's key system. The tenant identifier, the key version of the tenant master key, the encryption algorithm identifier, and the fragment encryption parameters together with the fragment ciphertext preserve the encryption relationship of the complete fragment. Therefore, the combined data satisfies all the constraints of the tenant-encrypted carbon data fragments.
[0097] The verification module generates on-chain carbon data storage records corresponding to the tenant's encrypted carbon data shards. Based on the on-chain carbon data storage records, it decrypts the encrypted fields to be verified to obtain a subset of CCER verified carbon data. In embodiments of the present invention, a subset of CCER-verified carbon data is obtained, including: CCER refers to the data category identifier in this scheme that accepts verification by a third-party auditing agency and provides carbon data according to the verification request; CCER verification carbon data subset refers to the data set formed after decrypting only the encrypted fields specified in the CCER verification request from the carbon data fragment to be verified. This data set includes the verification field name, field data type, field content, field order, and carbon data storage record identifier on the source chain, and is used to provide carbon data and storage source within a limited scope to the CCER verification monitoring ledger.
[0098] Generate the shard hash value corresponding to the tenant's encrypted carbon data shard; Shard hash value refers to the fixed-length digest data formed by the hash processing end according to the encoding order, hash algorithm identifier, group length, initial hash state, compression operation rules and digest length corresponding to the data version of the tenant's encrypted carbon data shard in the hash configuration record. It is used to identify the tenant's encrypted carbon data shard in the blockchain and support subsequent evidence consistency verification.
[0099] The hash processing end takes the tenant's encrypted carbon data fragments as the processing object. It retrieves the field encoding order, hash algorithm identifier, block length, initial hash state, compression operation rules, padding rules, and digest length corresponding to the data version of the tenant's encrypted carbon data fragment from the hash configuration record. Following the field encoding order, it sequentially encodes the tenant identifier, fragment ciphertext, tenant master key version, encryption algorithm identifier, and fragment encryption parameters into a byte sequence to be hashed. Starting from the beginning of the byte sequence to be hashed, it divides the data into blocks according to the block length. For data blocks whose end length is insufficient, it pads them to the block length according to the padding rules. The initial hash state is used as the input hash state for the first data block. The input and the current data block are processed sequentially using bitwise operations and modulo addition according to the compression operation rules. The data returned by the complete compression operation is determined as the current hash state, and the current hash state is used as the input for the hash state of the next data block. After all data blocks are processed, the digest byte sequence is extracted from the current hash state according to the digest length. The digest byte sequence is converted into a fragment hash value according to the encoding format recorded in the hash configuration record. If the field encoding fails, the hash configuration record is missing, the pending hash byte sequence is empty, or any compression operation does not completely return the current hash state, the generation stops and is returned to the tenant encrypted carbon data fragment maintenance end or the hash configuration record maintenance end for verification, and the fragment hash value corresponding to the tenant encrypted carbon data fragment is obtained.
[0100] The field encoding order allows all components of a tenant's encrypted carbon data fragment to enter a uniquely determined sequence of bytes to be hashed. Each data block after grouping participates in subsequent compression operations together with the previous current hash state, enabling any change in the content of any data block to be passed along the hash state to the digest byte sequence. The fragment hash value formed according to the digest length and encoding format thus corresponds to the complete content of the current tenant's encrypted carbon data fragment.
[0101] Write the tenant's encrypted carbon data shards, shard hash values, and the tenant identifier corresponding to the tenant's encrypted carbon data shards into the blockchain to obtain on-chain carbon data storage records. A blockchain refers to a distributed ledger maintained by multiple authorized blockchain nodes and storing evidence data in the order of transactions. After a successful write, a blockchain node returns a transaction identifier, block identifier, transaction location, on-chain write time, and transaction status. On-chain carbon data evidence records refer to evidence data records formed after the tenant's encrypted carbon data shards, shard hash values, and tenant identifiers are confirmed and written by the blockchain. These records include evidence record identifiers, transaction identifiers, tenant identifiers, tenant encrypted carbon data shards, shard hash values, on-chain storage locations, on-chain write times, and record status. They are used to locate the carbon data shards to be verified and provide shard evidence indexes.
[0102] The on-chain writer combines the tenant's encrypted carbon data shards, the shard hash value corresponding to each shard, and the tenant identifier corresponding to each shard according to the field order recorded by the blockchain interface to form the evidence storage transaction data. This data is then submitted to a normal blockchain node in the current evidence storage network. Upon receiving the transaction data, the blockchain node returns an on-chain submission receipt containing the transaction identifier, block identifier, transaction location, on-chain write time, and transaction status. The on-chain writer verifies the transaction status in the on-chain submission receipt to confirm successful writing and queries the blockchain using the transaction identifier. When the corresponding transaction found is identical to the data content of the notarized transaction and the tenant identifier is consistent, the block identifier, transaction location, and transaction identifier are recorded together as the on-chain storage location. The tenant's encrypted carbon data shard, shard hash value, tenant identifier, on-chain storage location, on-chain write time, and transaction status are written into the same record. When the on-chain submission receipt indicates that the write failed, the corresponding transaction does not exist, the corresponding transaction content is inconsistent, or the transaction identifiers of multiple on-chain submission receipts conflict with each other, the writing stops and no notarized record is formed. The record is then returned to the blockchain node for verification, thus obtaining the on-chain carbon data notarized record.
[0103] Obtain CCER verification requests initiated by third-party certification bodies; A third-party verification agency refers to an entity outside the tenant that independently verifies or reviews carbon data for the target computing power business and accesses the system through its agency identifier and authorized scope record. A CCER verification request refers to a data record submitted by a third-party verification agency through the verification request interface. It includes verification request identifier, agency identifier, authorization certificate identifier, tenant identifier, project identifier, methodology identifier, verification fields, verification time range, request initiation time, and request status, which are used to limit the extraction scope of on-chain evidence records, fields to be verified, and monitoring plan templates.
[0104] The verification request receiving end processes the request data submitted by the third-party certification body through the verification request interface. It parses the verification request identifier, organization identifier, authorization credential identifier, tenant identifier, project identifier, methodology identifier, verification fields, verification time range, request initiation time, and request status sequentially according to the data structure of the verification request interface. It compares the organization identifier and authorization credential identifier with the organization status, authorization data range, and authorization validity period in the organization's authorization record. Request data with a valid organization status, authorization data range including the tenant identifier and verification fields, authorization validity period covering the request initiation time, and request status "pending verification" are retained. If any required field is missing, authorization comparison fails, or multiple conflicting requests correspond to the same verification request identifier, the current request is rejected, and the missing or conflicting fields are returned to the third-party certification body. Only the uniquely verified request data is retained according to the verification request identifier, thus obtaining the CCER verification request initiated by the third-party certification body.
[0105] Based on the tenant identifier in the CCER verification request, the corresponding on-chain carbon data storage records are extracted to obtain the on-chain carbon data storage records corresponding to the tenant to be verified. The on-chain carbon data storage record corresponding to the tenant to be verified refers to the set of records in the on-chain carbon data storage record where the tenant identifier is the same as the tenant identifier in the CCER verification request, the on-chain write time is within the verification time range, and the record status is valid. This set of records maintains the correspondence between transaction identifier, on-chain storage location, shard hash value and tenant identifier, and is used to determine the carbon data shard to be verified.
[0106] The evidence record extraction end uses the tenant identifier and verification time range in the CCER verification request as matching conditions. It checks the tenant identifier, on-chain write time, transaction identifier, and record status of each on-chain carbon data evidence record. It retains on-chain carbon data evidence records with the same tenant identifier as the tenant identifier in the CCER verification request, on-chain write time within the verification time range, non-empty transaction identifier, and valid record status. It excludes on-chain carbon data evidence records that do not meet any matching conditions. For duplicate records with the same transaction identifier and content, only one is retained. For records with the same transaction identifier but conflicting on-chain storage location, shard hash value, or tenant identifier, the extraction is stopped and the process is returned to the on-chain write end for verification. When no record meets the matching conditions, this step is stopped and a request status of no verifiable evidence data is returned to the third-party verification agency. All retained records are arranged according to on-chain write time and transaction identifier to obtain the on-chain carbon data evidence record corresponding to the tenant to be verified.
[0107] The carbon data shards to be verified are determined based on the on-chain storage location in the on-chain carbon data storage record corresponding to the tenant to be verified. On-chain storage location refers to the combination of block identifier, transaction location, and transaction identifier that store evidence transaction data in the blockchain, used to locate a single evidence transaction from the blockchain ledger; carbon data shard to be verified refers to the encrypted carbon data shard obtained from the corresponding evidence transaction according to the on-chain storage location in the on-chain carbon data evidence record of the tenant to be verified, and which is consistent with the tenant identifier and transaction identifier. It retains the identifier of the source on-chain carbon data evidence record and is used to extract encrypted content under the verification field limitation.
[0108] The sharding positioning end selects the block identifier, transaction position, and transaction identifier from the on-chain carbon data storage records corresponding to the tenant to be verified. It locates the corresponding block in the blockchain according to the block identifier and the storage transaction in the corresponding block according to the transaction position. Then, it checks the transaction identifier of the located storage transaction against the transaction identifier. If they match, it extracts the tenant's encrypted carbon data shard and tenant identifier from the located storage transaction. It then performs an equivalence comparison with the tenant identifier in the CCER verification request. If the transaction identifier or tenant identifier comparison fails, the corresponding block does not exist, the transaction position does not exist, or the storage transaction is missing the tenant's encrypted carbon data shard, the positioning stops and returns to the blockchain node for verification. The tenant's encrypted carbon data shard that passes the comparison is kept in correspondence with the identifier of the source on-chain carbon data storage record. All tenant's encrypted carbon data shards that pass the comparison are organized according to the arrangement order of the on-chain carbon data storage records corresponding to the tenant to be verified, thus obtaining the carbon data shard to be verified.
[0109] Based on the verification fields in the CCER verification request, the corresponding encrypted content in the carbon data shard to be verified is extracted to obtain the encrypted fields to be verified. Verification fields refer to the set of field identifiers specified by a third-party verification agency and within the agency's authorized data scope in the CCER verification request. Each field identifier includes the field name, field data type, and request order. Verified encrypted fields refer to the encrypted data items extracted from the field-encrypted carbon data shards according to the verification fields after the carbon data shards to be verified have been decrypted at the sharding layer. They include the tenant identifier, field name, field data type, field ciphertext, data field-level key version, field encryption parameters, request order, and source chain on-chain carbon data storage record identifier. These are used to obtain the corresponding data field-level key and form plaintext data within the defined field range.
[0110] The field extraction end sequentially selects the tenant identifier, fragment ciphertext, key version of the tenant master key, encryption algorithm identifier, fragment encryption parameters, and carbon data storage record identifier from the carbon data fragment to be verified. Using the tenant identifier and key version of the tenant master key, it obtains the tenant master key corresponding to the tenant identifier from the key management end, whose purpose includes fragment decryption. The fragment ciphertext and fragment encryption parameters are sequentially fed into the inverse operation corresponding to the encryption algorithm identifier, and decryption is performed using the key material of the tenant master key corresponding to the tenant identifier. The data completely returned by the inverse operation is identified as the fragment byte sequence. The fragment byte sequence is parsed according to the record order and field order when the field-encrypted carbon data fragment was formed to obtain the field-encrypted carbon data fragment. CCER verification requests are then selected one by one. The verification fields are compared with the field names and data types in the encrypted carbon data shards. The ciphertext of the fields with the same field names and data types, the data field-level key version, and the field encryption parameters are retained. The tenant identifier, request order, and carbon data storage record identifier on the source chain are included in the retained content. If the shard layer decryption does not return a complete shard byte sequence, the shard byte sequence cannot be completely parsed, any verification field does not have a unique match, or the verification field exceeds the authorized data range of the institution, the extraction stops and no part of the result is retained. The result is returned to the key management end, third-party verification institution, or shard positioning end for verification. The encrypted field to be verified is obtained from all the ciphertexts of the fields that pass the comparison and their corresponding information.
[0111] The tenant master key and fragment encryption parameters corresponding to the tenant identifier enable the fragment ciphertext to be restored as field-encrypted carbon data fragments according to the encryption relationship at the time of formation, without directly exposing the plaintext of the tenant's business fields. The field name and field data type of the verified fields are then used to limit the extraction range of the field ciphertext in the field-encrypted carbon data fragments. Therefore, the retained field ciphertext and its corresponding information completely correspond to the encrypted fields to be verified specified in the CCER verification request.
[0112] Obtain the data field-level key corresponding to the encrypted field to be verified; The key acquisition end selects the tenant identifier, field name, and data field-level key version of each encrypted field to be verified. It compares the tenant identifier, field name, key version, and key purpose with the field key records from the key management end. It retains field key records with the same tenant identifier, field name, key version, and key purpose including verification and decryption. It obtains the key identifier, key material, encryption algorithm identifier, key version, and parameter processing rules from each retained field key record and keeps them corresponding to the encrypted fields to be verified according to the tenant identifier, field name, and key version. When any encrypted field to be verified does not have a corresponding field key record, the corresponding record is missing key material, or the same tenant identifier, field name, and key version correspond to multiple field key records with different key identifiers, the acquisition stops and some keys are not retained. The key is returned to the key management end for verification. The data field-level key corresponding to the encrypted field to be verified is obtained from the key data obtained from all uniquely corresponding field key records.
[0113] Based on the data field-level key, the encrypted fields to be verified are decrypted to obtain a subset of CCER verified carbon data.
[0114] Decryption refers to the process by which the encryption execution end performs the inverse operation of the encryption operation on the ciphertext of the field using the corresponding data field-level key, according to the field name, data field-level key version, field encryption parameters and encryption algorithm identifier recorded in the encrypted field to be verified, and then recovers the field content. This process only applies to the fields specified in the CCER verification request and which have passed the authorization comparison.
[0115] The encryption execution end selects the encrypted fields to be verified one by one according to the request order in the CCER verification request. It matches the tenant identifier, field name, and data field-level key version of the encrypted field to the corresponding data field-level key. The ciphertext and encryption parameters of the encrypted field are sequentially fed into the inverse operation corresponding to the encryption algorithm identifier in the data field-level key. Decryption is performed using the key material in the data field-level key. The data completely returned by the inverse operation is identified as the plaintext byte sequence of the field. The plaintext byte sequence is parsed according to the encoding order of the field name, data type, and content used during field encryption, and the decrypted data is then processed. The parsed field names and data types are compared with the field names and data types in the encrypted fields to be verified. If the comparison is successful, the parsed field content is retained and the request order and the carbon data storage record identifier on the source chain are included. If the comparison fails, the data field-level key is not unique, the decryption does not return a complete plaintext byte sequence, or the plaintext byte sequence cannot be completely parsed, the decryption stops and no part of the field content is retained. The data is then returned to the key management end or field extraction end for verification. All the field names, data types, content, and carbon data storage record identifiers on the source chain that have passed the comparison are combined according to the request order to obtain the CCER verification carbon data subset.
[0116] The tenant identifier, field name, and data field-level key version ensure a unique correspondence between each encrypted field to be verified and the data field-level key that forms the ciphertext of that field. The field encryption parameters and corresponding key materials enable the field ciphertext to be restored to the plaintext byte sequence of the field by performing the inverse operation during encryption. The parsed field name and field data type are then checked against the encrypted field to be verified and combined in the requested order, so that the resulting data contains only authorized verification fields and meets the scope limitation of the CCER carbon data verification subset.
[0117] The ledger module writes the corresponding content into the CCER verification carbon data subset to obtain the verification ledger content; based on the verification ledger content, the CCER verification monitoring ledger is obtained.
[0118] In an embodiment of the present invention, the CCER verification and monitoring log is obtained, including: The CCER verification and monitoring ledger refers to a structured record formed by writing the verification field content, target on-chain storage location, and target shard hash value of the CCER verification carbon data subset into the specified ledger fields according to the CCER monitoring plan template corresponding to the CCER verification request. This record retains the verification request identifier, template identifier, template version, verification ledger fields, verification ledger content, and evidence index, and is used by third-party verification agencies to verify the monitoring data and its on-chain source.
[0119] Obtain the CCER monitoring plan template corresponding to the CCER verification request; the CCER monitoring plan template includes multiple monitoring ledger fields; The CCER monitoring plan template refers to the ledger structure data configured according to project identifier and methodology identifier in the monitoring plan template library. It includes template identifier, template version, applicable project identifier, applicable methodology identifier, effective period, template status, and multiple monitoring ledger fields, which are used to determine the data writing structure of the current CCER verification request. The monitoring ledger field refers to the individual field definition in the CCER monitoring plan template. It includes field identifier, field name, field data type, unit of measurement, field order, data source field name, mandatory status, and evidence storage index field identifier, which are used to receive the carbon data to be verified and its on-chain evidence storage index.
[0120] The template acquisition end uses the project identifier, methodology identifier, and request initiation time in the CCER verification request as matching conditions. It retains CCER monitoring plan templates from the monitoring plan template library that have the same applicable project identifier, the same applicable methodology identifier, an effective period covering the request initiation time, and a valid template status. It verifies whether the template identifier, template version, and monitoring ledger fields in the retained CCER monitoring plan templates are complete. It also checks whether the field identifiers in multiple monitoring ledger fields are unique and whether the field names, field data types, field order, and data source field names exist. If no CCER monitoring plan template that meets the matching conditions exists, multiple templates with conflicting content corresponding to the same template version exist, or the monitoring ledger field verification fails, the acquisition stops and returns to the monitoring plan template library maintenance end for verification. It retains the only template that passes the verification and includes multiple monitoring ledger fields, thus obtaining the CCER monitoring plan template corresponding to the CCER verification request.
[0121] Based on the verification fields in the CCER verification request, the corresponding fields of multiple monitoring ledgers are extracted to obtain the verification ledger fields; The verification ledger field refers to a subset of fields in the CCER monitoring plan template whose data source field names are the same as the verification field names in the CCER verification request and whose data types are consistent. This subset of fields retains the template field identifier, field name, field data type, unit of measurement, field order, data source field name, and evidence index field identifier, and is used to limit the writing location of the verification ledger content.
[0122] The record field extraction end selects the verification field name, field data type, and request order from each CCER verification request. It then compares the data source field name, field data type, and field order among multiple monitoring record fields in the CCER monitoring plan template. It retains monitoring record fields whose data source field name is the same as the verification field name and whose field data type is consistent. The retained monitoring record fields are then assigned the corresponding verification field request order. Monitoring record fields with different data source field names or inconsistent field data types are excluded. When any verification field does not have a unique corresponding monitoring record field, the same monitoring record field corresponds to multiple verification fields, or the field order is missing, the extraction stops and returns to the third-party auditing agency or the monitoring plan template library maintenance end for verification. All retained monitoring record fields are arranged according to the field order recorded in the CCER monitoring plan template to obtain the verification record fields.
[0123] Based on the fields in the verification ledger, the corresponding content in the CCER carbon verification data subset is written into the fields to obtain the verification ledger content; The verification ledger content refers to the data set formed after the data source field name and field data type corresponding to the CCER carbon data subset are written into the verification ledger field. It maintains the correspondence between the template field identifier, field name, unit of measurement, field order, written content and carbon data storage record identifier on the source chain, and is used to continue writing the storage index.
[0124] The ledger content writing end selects the template field identifier, field name, field data type, unit of measurement, field order, and data source field name in the verification ledger fields one by one. It compares the field name, field data type, and request order in the CCER carbon data subset. It retains the field content where the field name is the same as the data source field name and the field data type is consistent. The field content is written to the verification ledger field pointed to by the corresponding template field identifier, and the unit of measurement, field order, and carbon data storage record identifier on the source chain recorded in the verification ledger field are included. When the verification ledger field does not have a unique corresponding field content, the field data type is inconsistent, or the field content corresponding to the mandatory state is empty, the writing stops and no part of the ledger content is retained. It returns to the field extraction end or the monitoring plan template library maintenance end for verification. All the verification ledger fields and their field content that have been written are organized according to the field order to obtain the verification ledger content.
[0125] Based on the on-chain carbon data storage records corresponding to the CCER carbon data subset, extract the corresponding target on-chain storage location and target shard hash value. The target on-chain storage location refers to the on-chain storage location recorded in the source on-chain carbon data storage record of each field in the CCER verification carbon data subset, which is used to locate the corresponding storage transaction in the CCER verification and monitoring ledger; the target shard hash value refers to the shard hash value recorded in the same source on-chain carbon data storage record and kept in pairs with the target on-chain storage location, which is used to identify the corresponding tenant encrypted carbon data shard in the CCER verification and monitoring ledger.
[0126] The evidence index extraction end selects the source on-chain carbon data evidence record identifiers in the CCER verification carbon data subset one by one, and compares the evidence record identifier and record status in the on-chain carbon data evidence records corresponding to the tenant to be verified. On-chain carbon data evidence records with the same evidence record identifier and valid record status are retained. The on-chain storage location and shard hash value are extracted from each retained on-chain carbon data evidence record. The on-chain storage location and shard hash value are kept in pairs according to the source on-chain carbon data evidence record identifier. Only one set of duplicate data with the same source on-chain carbon data evidence record identifier and the same content of on-chain storage location and shard hash value is retained. Data with the same source on-chain carbon data evidence record identifier but conflicting on-chain storage location or shard hash value is stopped from extraction and returned to the on-chain write end for verification. When there is no unique valid record for any source on-chain carbon data evidence record identifier, extraction is stopped and returned to the evidence record extraction end for verification. The target on-chain storage location and target shard hash value are obtained from all the verified on-chain storage locations and shard hash values.
[0127] Write the target chain storage location and target shard hash value into the evidence index field corresponding to the verification ledger field to obtain the CCER verification and monitoring ledger.
[0128] The evidence index field refers to the field location in the CCER monitoring plan template that is defined by the evidence index field identifier and is associated with the verification ledger field. Each evidence index field contains the source chain carbon data evidence record identifier, the target chain storage location, and the write location of the target shard hash value, which is used to establish a traceable relationship between the verification ledger content and the corresponding chain evidence data.
[0129] The ledger assembly service in the industrial cloud platform is based on verifying the ledger content. It selects the evidence index field identifier and the source on-chain carbon data evidence record identifier carried in the written field content of each field in the verification ledger. Through the on-chain evidence query interface of the industrial cloud platform, it finds the paired target on-chain storage location and target shard hash value according to the source on-chain carbon data evidence record identifier. Then, it locates the corresponding evidence index field in the CCER monitoring plan template maintained by the industrial cloud platform according to the evidence index field identifier, writes the target on-chain storage location into the on-chain location item of the corresponding evidence index field, and writes the target shard hash value paired with the target on-chain storage location into the same evidence. When the shard hash item of the index field is missing, or when the carbon data evidence record identifier on the source chain is missing, or when there are conflicting write contents in the same evidence index field, the industrial cloud platform stops assembling and does not retain part of the ledger. It then sends the abnormal data to the monitoring plan template library maintenance end or the evidence index extraction end for verification. After the verification is passed, the verification request identifier, template identifier, template version, verification ledger field, verification ledger content, and the completed evidence index field are combined to form a data record and stored in the CCER verification ledger library of the industrial cloud platform to obtain the CCER verification monitoring ledger.
[0130] The purpose of obtaining the CCER verification monitoring log is to create a traceable record of the monitoring boundaries, monitoring parameters, data sources, metering instruments, monitoring frequency, raw readings, abnormal data processing, emission reduction calculation process, and supporting materials for emission reduction projects. This record is used for internal project data management, third-party verification, emission reduction recalculation, anomaly tracking, and CCER emission reduction registration applications. For example, a 50MW wind power project recorded 120,000 MWh of electricity fed into the grid and 2,400 MWh of electricity consumed by the project itself in 2025. Based on the meter number and calibration certificate, the verification personnel determined that the net electricity fed into the grid was 117,600 MWh. Then, according to the applicable baseline emission factor of 0.5703 tCO2 / MWh, the emission reduction was recalculated to be 67,067.28 tCO2. The consistency of the data was verified by checking the monthly meter readings, grid settlement statements, and missing data processing records in the log, thereby determining whether the emission reduction has the monitoring and evidentiary basis for applying for CCER issuance.
[0131] This invention also provides a blockchain-based method for storing carbon data for CCER verification, the method comprising: Based on the computing power execution equipment corresponding to the target computing power service, the embedded FBG fiber is segmented to obtain the inner coating attachment segment, the inner coating detachment segment, and the inner coating wrinkle segment; the inner coating wrinkle segment is extracted to obtain the inner coating wrinkle loop area, and the fiber position range corresponding to each power supply segment is extracted to obtain the loop-covered power supply segment. Based on the power supply section covered by the ring, the carbon accounting results corresponding to the target computing power service are extracted to obtain the tenant's computing power carbon storage record. Based on the tenant identifier in the tenant's computing power carbon storage record, the encrypted carbon data fragments in the field are encrypted to obtain the tenant's encrypted carbon data fragments. Generate on-chain carbon data storage records corresponding to the tenant's encrypted carbon data shards. Based on the on-chain carbon data storage records, decrypt the encrypted fields to be verified to obtain a subset of CCER verified carbon data. Write the corresponding fields in the CCER carbon data subset to obtain the verification ledger content; based on the verification ledger content, obtain the CCER verification monitoring ledger.
[0132] The present invention also provides a storage medium including a computer program, which, when executed by a processor, implements the above-described carbon data blockchain notarization system for CCER certification.
[0133] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention.
Claims
1. A blockchain-based carbon data storage system for CCER certification, characterized in that: include: The sensing module segments the embedded FBG optical fiber according to the computing power execution device corresponding to the target computing power service, resulting in an inner coating attachment segment, an inner coating detachment segment, and an inner coating wrinkle segment; it extracts the region of the inner coating wrinkle segment to obtain the inner coating wrinkle loop region, and extracts the position of the optical fiber corresponding to each power supply segment to obtain the loop-covered power supply segment. The collection module extracts the carbon accounting results corresponding to the target computing power service based on the power supply section covered by the ring, and obtains the tenant's computing power carbon storage record. The encryption module performs fragmented encryption on the field encrypted carbon data fragments based on the tenant identifier in the tenant's computing power carbon storage record, thus obtaining the tenant's encrypted carbon data fragments. The verification module generates on-chain carbon data storage records corresponding to the tenant's encrypted carbon data shards. Based on the on-chain carbon data storage records, it decrypts the encrypted fields to be verified to obtain a subset of CCER verified carbon data. The ledger module writes the corresponding content into the CCER verification carbon data subset to obtain the verification ledger content; based on the verification ledger content, the CCER verification monitoring ledger is obtained.
2. The carbon data blockchain storage system for CCER verification according to claim 1, characterized in that, The process yields an inner coating attachment section, an inner coating separation section, and an inner coating wrinkling section, including: Obtain the computing power execution equipment corresponding to the target computing power service; Determine the target busbar for supplying power to the computing power execution equipment; Determine the embedded FBG optical fiber corresponding to the target busbar; Obtain the axial structure image sequence corresponding to the embedded FBG optical fiber; wherein, the embedded FBG optical fiber includes a quartz glass optical fiber, an inner coating covering the outside of the quartz glass optical fiber, and an FBG grating region disposed in the quartz glass optical fiber. Extract the outer contour of the quartz glass fiber corresponding to the quartz glass fiber and the inner contour of the inner coating corresponding to the inner coating from the axial structure image sequence. Based on the physical contact relationship between the inner contour of the inner coating and the outer contour of the quartz glass fiber, the embedded FBG fiber is segmented to obtain the inner coating attachment segment, the inner coating wall separation segment, and the inner coating wrinkling segment.
3. The carbon data blockchain storage system for CCER verification according to claim 1, characterized in that, The inner coating wrinkle collar area is obtained, including: The junction between the inner coating attachment section and the inner coating wall separation section is extracted to obtain the position where the collar separates. The position where the axial extension direction of the inner coating changes in the section of the inner coating away from the wall is extracted to obtain the fold-back position of the collar; The overlapping position of the inner coating after folding and the inner coating before folding in the inner coating wrinkle section is extracted to obtain the collar folding position; The junction between the inner coating wall section and the inner coating attachment section is extracted to obtain the collar reattachment position; Based on the collar detachment position, collar fold-back position, collar re-overlap position, and collar re-attachment position, the wrinkled section of the inner coating is extracted to obtain the wrinkled collar area of the inner coating.
4. The carbon data blockchain storage system for CCER verification according to claim 2, characterized in that, The power supply section covered by the loop includes: Obtain the position of each FBG region on the embedded FBG fiber; Based on the inner coating wrinkle ring area, the location of each FBG gate area is extracted by regional overlap to obtain the ring-covered gate area; Based on the power supply location range of the computing power execution equipment, the target bus trunking is divided into sections to obtain multiple power supply sections; Obtain the fiber location range corresponding to each power supply section on the embedded FBG fiber; Based on the FBG grid area location corresponding to the ring-covered grid area, the location range of the optical fiber corresponding to each power supply section is extracted to obtain the ring-covered power supply section.
5. The carbon data blockchain storage system for CCER verification according to claim 1, characterized in that, Obtain the tenant's computing power carbon storage record, including: Obtain the tenant identifier, computing power request hash, batch merge record, computing power energy consumption receipt and carbon accounting result corresponding to the target computing power service; The computing power execution devices powered by the power supply section covered by the ring are extracted to obtain the ring-related computing power execution devices; Extract the computing power energy consumption receipts corresponding to the ring-linked computing power execution devices from the computing power energy consumption receipts corresponding to the target computing power service to obtain the ring-linked energy consumption receipts; Based on the ring-related energy consumption receipt, the carbon accounting results corresponding to the target computing power business are extracted to obtain the ring-related carbon accounting results; Based on the hash of computing power requests, the batch merge records and the carbon accounting results associated with the ring are aggregated accordingly to obtain the computing power carbon aggregation records; Write the tenant identifier into the computing power carbon collection record to obtain the tenant computing power carbon storage record.
6. The carbon data blockchain storage system for CCER verification according to claim 1, characterized in that, Obtain the tenant's encrypted carbon data fragments, including: Based on the tenant identifier in the tenant's computing power carbon storage record, the tenant's computing power carbon storage record is fragmented to obtain tenant carbon data fragments; Obtain tenant business fields from tenant carbon data shards; Obtain the data field-level key corresponding to the tenant's business field; By using data field-level keys, the tenant's business fields are encrypted at the field level to obtain field-encrypted carbon data fragments; Retrieve the tenant master key corresponding to the tenant identifier; Using the tenant's master key, the encrypted carbon data fragments are encrypted in segments to obtain the tenant's encrypted carbon data fragments.
7. The carbon data blockchain storage system for CCER verification according to claim 1, characterized in that, The CCER carbon verification subset includes: Generate the shard hash value corresponding to the tenant's encrypted carbon data shard; Write the tenant's encrypted carbon data shards, shard hash values, and the tenant identifier corresponding to the tenant's encrypted carbon data shards into the blockchain to obtain on-chain carbon data storage records. Obtain CCER verification requests initiated by third-party certification bodies; Based on the tenant identifier in the CCER verification request, the corresponding on-chain carbon data storage records are extracted to obtain the on-chain carbon data storage records corresponding to the tenant to be verified. The carbon data shards to be verified are determined based on the on-chain storage location in the on-chain carbon data storage record corresponding to the tenant to be verified. Based on the verification fields in the CCER verification request, the corresponding encrypted content in the carbon data shard to be verified is extracted to obtain the encrypted fields to be verified. Obtain the data field-level key corresponding to the encrypted field to be verified; Based on the data field-level key, the encrypted fields to be verified are decrypted to obtain a subset of CCER verified carbon data.
8. The carbon data blockchain storage system for CCER verification according to claim 1, characterized in that, Obtain the CCER verification and monitoring log, including: Obtain the CCER monitoring plan template corresponding to the CCER verification request; the CCER monitoring plan template includes multiple monitoring ledger fields; Based on the verification fields in the CCER verification request, the corresponding fields of multiple monitoring ledgers are extracted to obtain the verification ledger fields; Based on the fields in the verification ledger, the corresponding content in the CCER carbon verification data subset is written into the fields to obtain the verification ledger content; Based on the on-chain carbon data storage records corresponding to the CCER carbon data subset, extract the corresponding target on-chain storage location and target shard hash value. Write the target chain storage location and target shard hash value into the evidence storage index field corresponding to the verification ledger field to obtain the CCER verification and monitoring ledger.
9. A method for storing carbon data on a blockchain for CCER certification, wherein the method is applied to a carbon data blockchain storage system for CCER certification as described in any one of claims 1-8, characterized in that, The method includes: Based on the computing power execution equipment corresponding to the target computing power service, the embedded FBG fiber is segmented to obtain the inner coating attachment segment, the inner coating detachment segment, and the inner coating wrinkle segment; the inner coating wrinkle segment is extracted to obtain the inner coating wrinkle loop area, and the fiber position range corresponding to each power supply segment is extracted to obtain the loop-covered power supply segment. Based on the power supply section covered by the ring, the carbon accounting results corresponding to the target computing power service are extracted to obtain the tenant's computing power carbon storage record. Based on the tenant identifier in the tenant's computing power carbon storage record, the encrypted carbon data fragments in the field are encrypted to obtain the tenant's encrypted carbon data fragments. Generate on-chain carbon data storage records corresponding to the tenant's encrypted carbon data shards. Based on the on-chain carbon data storage records, decrypt the encrypted fields to be verified to obtain a subset of CCER verified carbon data. Write the corresponding fields in the CCER carbon data subset to obtain the verification ledger content; based on the verification ledger content, obtain the CCER verification monitoring ledger.
10. A storage medium comprising a computer program, characterized in that, When a computer program is executed by a processor, it implements the carbon data blockchain storage system for CCER certification as described in any one of claims 1 to 8.
