Data settlement method and device, electronic equipment and nonvolatile storage medium

Abstract

The invention discloses a data settlement method and device, electronic equipment and a nonvolatile storage medium. The method comprises the following steps: acquiring encrypted data corresponding to different operator nodes; decrypting the encrypted data in an isolation memory of the trusted execution area to obtain to-be-settled data; and performing settlement processing on the to-be-settled data to obtain a settlement result, and uploading information of the settlement result to the block chain for recording. According to the method and the device, the technical problem that the settlement privacy protection effect is poor due to the fact that on-chain calculation and off-chain calculation of a cross-operator settlement scheme in the related technology are separated and detail-level account checking and settlement cannot be realized under the privacy protection condition is solved.

Description

Technical Field

[0001] This application relates to the field of communication and information security technology, and more specifically, to a data settlement method, apparatus, electronic device, and non-volatile storage medium. Background Technology

[0002] In the current field of cross-carrier settlement and privacy protection, settlement processes typically rely on centralized clearing agencies or bilateral reconciliation systems, employing periodic batch processing to clear and settle traffic, call details, and charges. Specifically, operators transmit encrypted settlement files via dedicated communication links. These files contain critical information such as call logs, data usage, and charges, and are accompanied by digital signatures and hash verifications to ensure data integrity. However, this settlement method suffers from the following technical drawbacks:

[0003] First, the settlement schemes in related technologies mostly rely on periodic batch processing, with settlement cycles typically monthly, bi-monthly, or even longer. This results in insufficient real-time performance of the settlement process, failing to meet the demands for real-time settlement in modern communication operation environments. Second, although data is encrypted during transmission and access control policies are implemented in off-chain storage, the transparency and traceability of the data are limited, especially in detailed data processing, making it difficult to ensure the confidentiality and privacy of data during computation. Third, the dispute resolution process has a low degree of automation, relying mostly on manual intervention for comparison and arbitration, which is inefficient and prone to causing delays in the dispute resolution chain. Fourth, privacy protection is coarse-grained, lacking fine-grained control over the minimum visibility granularity and usage limitations of detailed data.

[0004] In summary, the relevant technologies have significant shortcomings in cross-carrier settlement and privacy protection, especially in data privacy protection, real-time settlement, result verifiability, automated dispute resolution, and end-to-end security automation. These issues limit the efficiency of the settlement process, increase operating costs, and reduce the trust among the participating parties.

[0005] There is currently no effective solution to the above problems. Summary of the Invention

[0006] This application provides a data settlement method, apparatus, electronic device, and non-volatile storage medium to at least solve the technical problem of poor settlement privacy protection caused by the fragmentation of on-chain and off-chain computing in cross-carrier settlement schemes in related technologies, and the inability to achieve detailed reconciliation and settlement under privacy protection conditions.

[0007] According to one aspect of the embodiments of this application, a data settlement method is provided, comprising: acquiring encrypted data corresponding to different operator nodes, wherein the encrypted data is obtained by encrypting data to be settled; decrypting the encrypted data in isolated memory of a trusted execution region to obtain data to be settled, wherein the isolated memory is a hardware isolation region inside the trusted execution region node, and the isolated memory is used to ensure that the data is not accessed or tampered with externally during the decryption and processing process; performing settlement processing on the data to be settled to obtain a settlement result, and uploading the settlement result information to a blockchain for recording, wherein the settlement processing is used to match and calculate the data to be settled between different operators, and the settlement result is used to characterize the financial income and expenditure of each operator participating in the settlement.

[0008] Optionally, obtaining encrypted data sent by different operator nodes includes: receiving encrypted data and digital signatures sent by operator nodes, wherein the encrypted data is obtained by the operator node encrypting the data to be settled using a target key, and the data to be settled is obtained by standardizing the original business data and desensitizing sensitive fields, wherein the original business data includes at least one of the following: call usage records, traffic usage records, SMS usage records, billing event data, and service usage duration.

[0009] Optionally, before receiving the encrypted data and digital signature sent by the operator node, the method further includes: receiving a remote verification request sent by the operator node, wherein the remote verification request is used to request the trusted execution zone node to provide relevant information about its hardware and operating environment to verify whether the trusted execution zone node is in a trusted state; in response to the remote verification request, sending first verification information to the operator node, wherein the first verification information is used to characterize that the hardware and computing environment of the trusted execution zone node is in a trusted state, and the first verification information includes at least one of the following: hardware identity identifier, firmware version information, hash value of the loader, trusted timestamp, and platform signature.

[0010] Optionally, decrypting the encrypted data in the isolated memory of the trusted execution region to obtain the data to be settled includes: verifying the digital signature, wherein the verification is used to determine the integrity and trustworthiness of the source of the received encrypted data to ensure that the encrypted data has not been tampered with and was indeed generated by the operator node; if the digital signature verification passes, decrypting the encrypted data in the isolated memory to obtain the data to be settled.

[0011] Optionally, the settlement processing of the data to be settled to obtain the settlement result includes: matching the data to be settled corresponding to different operators one by one according to a preset identifier, and aligning the data to be settled within a preset time window to ensure the consistency of the data recording time, wherein the preset identifier includes at least one of the following: International Mobile Subscriber Identity (IMSI) or Mobile Subscriber Number; calculating the billing amount of the matched and aligned data to be settled according to a preset billing rule to determine the amount payable and payable for each operator, thereby obtaining the settlement result, wherein the preset billing rule is used to calculate the fee according to different service types and billing standards; determining the hash value corresponding to the settlement result, and generating second proof information for the billing calculation process, wherein the second proof information is used to characterize the completeness and credibility of the billing calculation process.

[0012] Optionally, uploading the settlement result information to the blockchain for recording includes uploading the hash value corresponding to the settlement result, the second proof information, the settlement period, and the identifiers of the operator nodes participating in the settlement to the consortium blockchain for recording. If the smart contract deployed in the consortium blockchain verifies the validity of the second proof information, the corresponding account status between the operator nodes participating in the settlement will be updated.

[0013] Optionally, the method further includes: upon receiving an on-chain dispute request, re-acquiring encrypted data corresponding to different operator nodes, wherein the on-chain dispute request indicates that the user has objections to the information recorded in the consortium blockchain; recalculating the settlement result based on the re-uploaded encrypted data and generating new second proof information; and updating the information recorded in the consortium blockchain based on the recalculated settlement result and the new second proof information.

[0014] According to another aspect of the embodiments of this application, a data settlement apparatus is also provided, comprising: a data acquisition module for acquiring encrypted data corresponding to different operator nodes, wherein the encrypted data is obtained by encrypting data to be settled; a data decryption module for decrypting the encrypted data in isolated memory of a trusted execution region to obtain data to be settled, wherein the isolated memory is a hardware isolation region inside the trusted execution region node, and the isolated memory is used to ensure that the data is not accessed or tampered with externally during the decryption and processing process; and a data calculation module for performing settlement processing on the data to be settled, obtaining a settlement result, and uploading the settlement result information to the blockchain for recording, wherein the settlement processing is used to match and calculate the data to be settled between different operators, and the settlement result is used to characterize the financial income and expenditure of each operator participating in the settlement.

[0015] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the program executes a data settlement method during runtime.

[0016] According to another aspect of the embodiments of this application, a non-volatile storage medium is also provided, the non-volatile storage medium including a stored computer program, wherein the device where the non-volatile storage medium is located executes a data settlement method by running the computer program.

[0017] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps of a data settlement method.

[0018] In this embodiment, a cross-domain collaborative computing approach is adopted. By decrypting encrypted data in TEE isolated memory and linking it with blockchain smart contracts, and combining the verifiable on-chain computation results of the trusted execution environment, a highly secure, real-time, and automated cross-carrier data settlement is achieved. This solves the technical problem of poor settlement privacy protection caused by the separation of on-chain and off-chain computation and the inability to achieve detailed reconciliation and settlement under privacy protection conditions in related cross-carrier settlement schemes. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0020] Figure 1 This is a hardware structure block diagram of a computer terminal (or electronic device) for implementing a data settlement method according to an embodiment of this application;

[0021] Figure 2 This is a schematic diagram of a data settlement method flow provided according to an embodiment of this application;

[0022] Figure 3 This is a schematic diagram of a data settlement device provided according to an embodiment of this application. Detailed Implementation

[0023] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0025] To facilitate a better understanding of the embodiments of this application by those skilled in the art, some technical terms or nouns involved in the embodiments of this application are explained as follows:

[0026] Blockchain is a distributed ledger technology that uses cryptographic methods to chain data blocks together in chronological order, and uses a consensus mechanism to ensure the consistency and immutability of the ledger among distributed nodes. In this invention, the blockchain is used to store information such as settlement result hashes, execution proofs, and settlement cycles, and drives smart contracts to automatically execute clearing and allocation.

[0027] Trusted Execution Environment (TEE): A hardware-isolated execution area within the processor, capable of executing code in isolation from the operating system and protecting its data from external access and tampering. In this invention, the TEE is used for detailed-level decryption, matching, rate calculation, anomaly detection, and generation of execution proofs for cross-carrier settlement data.

[0028] Remote Attestation (RA): A secure verification mechanism provided by a TEE (Telecommunication Equipment Environment) to prove to a remote entity the authenticity and integrity of its runtime environment's hardware state, firmware version, and loader hash value. In this invention, remote attestation is used to ensure that the computing environment is in a trusted state before data is uploaded.

[0029] Proof of Execution (PoE): Verifiable data generated by the TEE, including the hash of the computation result, a trusted timestamp, a program hash, and a platform signature, used to prove that the computation process was executed in a trusted environment without tampering. In this invention, PoE serves as the basis for on-chain verification of the correctness of the settlement result.

[0030] Smart Contract: An automated program deployed on a blockchain that can automatically trigger and execute transactions or business logic based on preset conditions. In this invention, the smart contract is used to verify the execution proof and automatically execute cross-operator fund clearing and transfer operations after successful verification.

[0031] Byzantine Fault Tolerance (BFT): A fault-tolerance mechanism for distributed systems that ensures consistency of ledger data across all nodes even in the presence of malicious nodes. This invention employs the BFT consensus mechanism to guarantee the tamper-proof and consistency of the on-chain settlement ledger.

[0032] Quantum Key Distribution (QKD): A key distribution technology based on the principles of quantum mechanics, capable of generating session keys that cannot be eavesdropped on. In this invention, QKD can be used as an optional enhancement scheme to provide a physically secure encrypted channel between the operator and the TEE node.

[0033] In the current field of cross-carrier settlement and privacy protection, the mainstream practice relies on centralized clearing institutions or bilateral reconciliation systems to complete the clearing and settlement of traffic, call details and fees. The settlement process usually adopts a periodic batch processing method, transmits encrypted settlement files through dedicated communication links (such as SFTP, VPN), and uses digital signatures and hash verification to ensure data integrity. Privacy protection mainly relies on off-chain encrypted storage and access control policies, and data transparency and traceability are limited.

[0034] Among related technologies, some solutions attempt to introduce blockchain technology to record transaction summaries, batch hashes, or Merkle roots of cross-carrier settlements on the chain, achieving tamper-proof and verifiable accounting records. Simultaneously, they utilize the multi-party consensus mechanism of consortium blockchains to ensure the trustworthiness of the settlement process. Other solutions deploy Trusted Execution Environments (TEEs) off-chain, such as Intel SGX or AMD SEVs, to perform confidential calculations on the encrypted detailed data uploaded by all parties. Data decryption, reconciliation, and aggregation are completed in a hardware-isolated environment, avoiding direct exposure of the original data. However, in these technologies, blockchain and TEE often operate independently, lacking deep end-to-end integration. This makes it difficult to achieve full automation and real-time processing of the entire process from cross-domain identity authentication and data privacy protection to settlement execution. Problems such as blurred security boundaries, reliance on manual dispute resolution, and high settlement delays persist.

[0035] Specifically, the solutions in related technologies can be broadly categorized into two loosely coupled integrations: "blockchain ledger + traditional clearing / reconciliation process" and "TEE confidential computing reconciliation + on-chain evidence storage."

[0036] On the one hand, the operator still uses call detail records / event data (CDR / EDR) as the basis. After the billing middle platform performs normalization and rate-based processing, it generates TAP3 / NRTRDE files, which are then pushed to the data clearing party (DCH) through dedicated channels such as SFTP / AS. The files are accompanied by PKCS#7 signatures and SHA-256 verification. The clearing party performs schema verification, exchange rules and tax rate processing according to GSMA rules, and issues net settlement and dispute lists on a monthly (or bi-monthly) basis. The dispute process is completed by manually comparing detailed CSV / reports. To improve transparency, some pilot programs put the Merkle root / batch hash of "usage summary + total amount" on the blockchain (mostly using Hyperledger Fabric / Corda / Quorum consortium blockchains). Contracts record batch status, exchange rates and timestamps. Privacy is controlled through Fabric private data sets / channels or Corda flows. Detailed call records are still stored off-chain (such as object storage / IPFS / self-built HDFS). On-chain only timestamps and non-repudiable evidence are stored. Off-chain settlement engines or "oracles" periodically (5-15 minutes / day) update the status of the summary results on the blockchain.

[0037] On the other hand, some solutions deploy TEE (such as Intel SGX / AMD SEV) reconciliation services in neutral third-party or multi-cloud environments. Each operator uses its own public key to encrypt detailed call detail records. After remote attestation (EPID / DCAP), the records are decrypted, matched, and aggregated in a trusted execution environment (aligned by IMSI / MSISDN / cell / time window, and billing rules, anomaly filtering, and difference detection are executed). Only the encrypted difference and digest are output. The TEE side uses key sealing and session keys, calculates logs and result hashes, and then writes them back to the blockchain for evidence storage.

[0038] While the above solutions introduce on-chain traceability and TEE confidential computation, the two are mostly "independent": the on-chain only handles batch-level accounting and timestamps, while the TEE only performs black-box aggregation; the end-to-end cross-domain remote proof → detailed-level encrypted comparison → automated dispute resolution → contract-driven clearing and settlement / escrow payment are usually not integrated, still relying on batch processing windows and manual work orders, and the real-time performance and privacy boundary control (the smallest visible granularity of details, the verifiability of computation) are also relatively limited.

[0039] In summary, cross-carrier settlement solutions combining blockchain and TEE face several technical challenges in practical applications: First, there is a lack of deep collaboration between the blockchain and TEE sides; the blockchain only stores batch summaries or status information, failing to directly drive detailed-level automatic reconciliation and settlement execution. Second, while TEE calculations protect data privacy, most solutions lack cross-domain trusted proof and result verification mechanisms, making it difficult for third parties to independently verify the correctness of calculations. Third, the settlement process still relies on periodic batch processing, making it difficult to support near-real-time or even real-time settlement needs. Fourth, the dispute resolution process has low automation, relying heavily on manual intervention for comparison and arbitration, resulting in low efficiency and potential delays in the dispute resolution chain. Fifth, privacy protection is coarse-grained, lacking fine-grained control over the minimum visibility granularity and usage limitations of detailed data.

[0040] To address the aforementioned issues, this application provides a solution that achieves end-to-end integration of blockchain and TEE, enabling cross-operator settlement platforms to perform detailed, automated, and real-time reconciliation and settlement execution while ensuring data privacy and computational verifiability for all parties. This will be explained in detail below.

[0041] According to an embodiment of this application, a method embodiment for data settlement is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0042] The methods and embodiments provided in this application can be executed on mobile terminals, computer terminals, or similar computing devices. Figure 1 A hardware structure block diagram of a computer terminal (or electronic device) for implementing a data settlement method is shown. Figure 1 As shown, the computer terminal 10 (or electronic device) may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0043] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or electronic device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0044] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the data settlement method in this embodiment. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the aforementioned data settlement method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0045] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0046] The display may be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 10 (or electronic device).

[0047] Under the above operating environment, this application provides a data settlement method. Figure 2 This is a schematic diagram of a data settlement method flow provided according to an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0048] Step S202: Obtain encrypted data corresponding to different operator nodes, wherein the encrypted data is obtained by encrypting the data to be settled;

[0049] Step S204: Decrypt the encrypted data in the isolated memory of the trusted execution region to obtain the data to be settled. The isolated memory is a hardware isolation area inside the trusted execution region node. The isolated memory is used to ensure that the data is not accessed or tampered with externally during the decryption and processing.

[0050] Step S206: Perform settlement processing on the data to be settled to obtain the settlement result, and upload the settlement result information to the blockchain for recording. The settlement processing is used to match and calculate the data to be settled between different operators, and the settlement result is used to represent the financial income and expenditure of each operator participating in the settlement.

[0051] Through the above steps, by using TEE-isolated memory decryption of encrypted data and the linkage application of blockchain smart contracts, and by combining the verifiable on-chain calculation results of the trusted execution environment, a highly secure, real-time and automated cross-carrier data settlement purpose is achieved. This solves the technical problem of poor settlement privacy protection caused by the separation of on-chain and off-chain calculations in cross-carrier settlement schemes in related technologies, and the inability to achieve detailed reconciliation and settlement under privacy protection conditions.

[0052] The data settlement method in steps S202 to S206 of the embodiments of this application will be further described below.

[0053] First, each operator node encrypts the detailed data required for settlement (such as call detail records, traffic records, and billing events) locally, and then securely uploads it to the settlement node deployed with a Trusted Execution Environment (TEE) through cross-domain remote authentication. The details are as follows.

[0054] In some embodiments of this application, obtaining encrypted data sent by different operator nodes includes: receiving encrypted data and digital signatures sent by operator nodes, wherein the encrypted data is obtained by encrypting the data to be settled by the operator node using a target key, and the data to be settled is obtained by standardizing the original business data and desensitizing sensitive fields, wherein the original business data includes at least one of the following: call usage records, traffic usage records, SMS usage records, billing event data, and service usage duration.

[0055] Specifically, operators can collect the raw business data (CDR, EDR, traffic records, etc.) required for settlement through the Business Support System (BSS) or Operation Support System (OSS), and unify the data time precision to the millisecond level (NTP / PTP synchronization). Then, the raw business data can be standardized and converted into a unified format (such as JSON, Avro, Protobuf), and sensitive fields can be anonymized. Only the minimum dataset required for reconciliation (i.e., the data to be settled mentioned above) is retained. That is, the minimum visible granularity of the data is "reconciliation required fields". All non-essential fields are anonymized locally before being encrypted and uploaded. After that, the data to be settled can be encrypted using the session key (i.e., the target key mentioned above, such as AES-256-GCM) to obtain encrypted data. The session key is then encrypted with RSA-4096 / SM2 to generate a digital signature (ECDSA / secp256r1 or SM2).

[0056] Before uploading encrypted data to the trusted execution zone node, the trusted execution zone node needs to be verified through cross-domain remote proof, as follows.

[0057] In some embodiments of this application, before receiving the encrypted data and digital signature sent by the operator node, the method further includes: receiving a remote verification request sent by the operator node, wherein the remote verification request is used to request the trusted execution zone node to provide relevant information about its hardware and operating environment to verify whether the trusted execution zone node is in a trusted state; in response to the remote verification request, sending first verification information to the operator node, wherein the first verification information is used to characterize that the hardware and computing environment of the trusted execution zone node is in a trusted state, and the first verification information includes at least one of the following: hardware identity identifier, firmware version information, hash value of the loader, trusted timestamp, and platform signature.

[0058] Specifically, before uploading encrypted data and digital signatures to the Trusted Execution Zone (TEE), the operator node can perform remote proof (SGX DCAP / SEV-SNP) on the TEE settlement node (i.e., the Trusted Execution Zone node) to verify its hardware identity, firmware version, and loader hash value. For example, it can send a remote proof request to the Trusted Execution Zone node, requesting the Trusted Execution Zone node to provide relevant information about the hardware and operating environment.

[0059] After receiving a remote verification request, the trusted execution zone node responds by sending first verification information to the operator node. The first verification information can verify the hardware identity, firmware version, loader hash value, trusted timestamp, platform signature, etc. of the trusted execution zone node, confirming that the aforementioned trusted execution zone settlement node is running on a trusted firmware version and has loaded the specified reconciliation program.

[0060] After successful verification, the operator node can transmit encrypted data to the TEE node through a TLS 1.3 / QUIC secure channel.

[0061] For example, in a typical cross-border operator computing scenario, Operator A and Operator B need to perform real-time clearing and settlement of international roaming call detail records (CDRs). During the data collection and encrypted upload phase, Operator A and Operator B can each collect the CDRs generated by international roaming (fields include IMSI, MSISDN, start time, end time, traffic usage, and cost) in their local BSS. Then, the CDRs are encrypted using AES-256-GCM and an integrity tag is generated using SM2 digital signature. Furthermore, before uploading the encrypted data, both nodes initiate an IntelSGX DCAP remote verification to the TEE settlement node to confirm that the settlement node is running on a trusted firmware version and has loaded the specified reconciliation program. After successful verification, the encrypted CDRs are sent to the TEE node via a TLS 1.3 channel.

[0062] Before data upload, this application's embodiments employ a remote attestation mechanism to verify the hardware trustworthiness, firmware version, loader hash, and other security parameters of the TEE node, ensuring that data is only loaded into a trusted execution environment for processing. This effectively prevents settlement data from being intercepted by malicious nodes or tampered execution environments, ensuring the trustworthiness and security of the computing environment and defending against data leakage and tampering risks at the source.

[0063] After receiving encrypted data and a digital signature, the TEE node (trusted execution zone node) can perform identity and environment verification. After completing the identity and environment verification, it can decrypt the encrypted data within the hardware isolation zone, as detailed below.

[0064] In some embodiments of this application, decrypting encrypted data in isolated memory within a trusted execution region to obtain data to be settled includes: verifying a digital signature, wherein the verification is used to determine the integrity and source credibility of the received encrypted data to ensure that the encrypted data has not been tampered with and was indeed generated by the operator node; and if the digital signature verification passes, decrypting the encrypted data in isolated memory to obtain the data to be settled.

[0065] Specifically, TEE nodes can verify the identity of the data sender through digital signatures, ensuring that the data was definitely generated by the operator node and has not been tampered with. Only after successful verification will the data be further decrypted and processed. End-to-end encryption is maintained throughout the data lifecycle. The plaintext of the original details only exists briefly within the TEE and is destroyed by the Hardware Security Module (HSM) after the computation is completed.

[0066] After decrypting the encrypted data to obtain the data to be settled, the TEE node can perform settlement processing such as detailed-level matching, billing rule calculation and difference detection on the encrypted data within the hardware isolation zone. The specific steps are as follows.

[0067] In some embodiments of this application, the settlement processing of the data to be settled to obtain a settlement result includes: matching the data to be settled corresponding to different operators one by one according to a preset identifier, and aligning the data to be settled within a preset time window to ensure the consistency of the data recording time, wherein the preset identifier includes at least one of the following: International Mobile Subscriber Identity (IMSI) or Mobile Subscriber Number; calculating the billing amount of the matched and aligned data to be settled according to a preset billing rule to determine the amount payable and payable for each operator, thereby obtaining a settlement result, wherein the preset billing rule is used to calculate the fee according to different service types and billing standards; determining the hash value corresponding to the settlement result, and generating second proof information for the billing calculation process, wherein the second proof information is used to characterize the integrity and credibility of the billing calculation process. Specifically, the trusted execution region is a hardware-isolated execution region inside the processor, which can execute code in isolation from the operating system and protect the data therein from external access and tampering. The TEE node, after decrypting the encrypted data using the encapsulation key, obtains the plaintext data to be settled, which exists only in isolated memory (EPC / SEV area). During the settlement process, the data to be settled from different operators can be matched one by one according to the International Mobile Subscriber Identity (IMSI) / Mobile Subscriber Number (MSISDN) and time window (±10ms tolerance), and deduplication can be performed. It can also perform rate calculation, currency conversion, and tax rate application according to the GSMA TAP3 billing rules or the rules agreed upon by both parties (i.e., the pre-designed fee rules mentioned above), generate settlement results such as net settlement table, difference list, and abnormal record list, and calculate the hash value of the results. At the same time, it can use trusted timestamps and program hashes to generate a proof of execution (i.e., the second proof information mentioned above) and sign it with the TEE platform key.

[0068] For example, for encrypted data uploaded by operators A and B, the TEE node, after decrypting the call detail records (CDRs) of both parties, can match them one by one according to IMSI and time period, marking any discrepancies. It then applies the GSMA TAP3 billing rules to complete cross-currency conversion (based on real-time exchange rate oracle data stored on-chain) and tax rate calculation; generates a list of net differences in receivables and payables between the two parties and a summary of the total amount, and calculates the hash value of the results. Simultaneously, it can utilize the TEE's built-in trusted timestamps and program hashes to generate a proof of execution that verifies the calculation process.

[0069] By introducing a detailed-level secure computation mechanism based on a Trusted Execution Environment (TEE), the encrypted settlement data uploaded by all parties is decrypted, matched, billed, and anomaly detected within a hardware-isolated area. A verifiable Proof of Execution is generated during the computation process. This ensures that detailed-level settlement data is not accessed or tampered with by any unauthorized party during computation, overcoming the shortcomings of traditional off-chain computation in preventing leakage and tampering. Furthermore, the Proof of Execution ensures the verifiability and credibility of the results.

[0070] After obtaining the settlement result, the TEE node submits the hash digest of the calculation result and the necessary settlement metadata to the blockchain smart contract. The contract triggers multi-party consensus and records the immutable accounting status, as follows.

[0071] In some embodiments of this application, uploading the settlement result information to the blockchain for recording includes: uploading the hash value corresponding to the settlement result, the second proof information, the settlement period, and the identifiers of the operator nodes participating in the settlement to the consortium blockchain for recording, wherein, if the smart contract deployed in the consortium blockchain verifies the validity of the second proof information, the corresponding accounting status between the operator nodes participating in the settlement will be updated.

[0072] Specifically, TEE nodes can upload the hash value, computation proof (i.e., second proof information), settlement period, and participant ID corresponding to the settlement result to the consortium blockchain (Hyperledger Fabric, Corda, Quorum); after the smart contract verifies the validity of the proof through the chaincode, it updates the accounting status to "settled" and records an immutable timestamp and version number.

[0073] Furthermore, for confirmed settlement results, smart contracts can automatically execute clearing and payment instructions or generate dispute resolution tasks based on the settlement results, achieving a closed-loop settlement process. For example, it can call an off-chain payment gateway to execute fund transfers (supporting DCEP, SWIFT, cross-border stablecoins, etc.).

[0074] By deeply integrating blockchain with a Trusted Execution Environment (TEE) end-to-end, detailed-level secure computation of cross-carrier encrypted data is achieved within the TEE, and the results are verifiable on the blockchain. This overcomes the technical bottlenecks of the separation between on-chain and off-chain computation in related technical solutions, which cannot balance privacy protection and computation verification. While ensuring the confidentiality and privacy of business data of all parties, it significantly improves the real-time performance, automation, and transparency of settlement.

[0075] In addition, an automated dispute resolution and re-settlement mechanism is introduced in this application embodiment, as detailed below.

[0076] In this embodiment, if one party raises a dispute request on-chain, the contract triggers the trusted execution environment to reload the relevant data for secondary calculation and update the on-chain results. If the discrepancy is confirmed, the contract automatically generates new second proof information, the specific content of which is as follows:

[0077] In some embodiments of this application, the method further includes: upon receiving an on-chain dispute request, re-acquiring encrypted data corresponding to different operator nodes, wherein the on-chain dispute request indicates that the user has objections to the information recorded in the consortium blockchain; recalculating the settlement result based on the re-uploaded encrypted data and generating new second proof information; and updating the information recorded in the consortium blockchain based on the recalculated settlement result and the new second proof information.

[0078] Specifically, if a party submits an on-chain dispute request, the contract automatically generates a dispute task. Both parties re-upload the encrypted details to the TEE, recalculate the settlement result, and generate a new calculation proof. After contract verification, the settlement result is updated, and a compensation or refund instruction is triggered. For example, if an operator submits an on-chain dispute request, the smart contract triggers the TEE to reload the relevant call detail records for secondary calculation and update the on-chain result. If the difference is confirmed, the contract automatically generates a compensation settlement instruction.

[0079] This application's embodiments support an automated dispute resolution mechanism. Upon initiation of a dispute by either party, the system automatically triggers the re-uploading of disputed data and recalculation of the TEE, uploads the updated settlement results to the blockchain, and automatically completes the adjustment or refund process. This significantly reduces the time and manpower costs of dispute resolution, improves the accuracy and real-time nature of accounting adjustments, and reduces financial friction between operators.

[0080] In addition, to further enhance the security and scalability of this application, the following privacy protection and security strategies can be introduced, mainly including:

[0081] 1) In this application, a quantum key distribution (QKD) link can also be established between the operator node and the trusted execution area node. A one-time session key is generated through the BB84 protocol to encrypt the uploaded data, thus ensuring transmission security at the physical layer.

[0082] 2) A multi-TEE node parallel computing and fault tolerance mechanism can be introduced, adopting a multi-active architecture, deploying multiple trusted execution area nodes in different geographical locations, and using a sharding strategy to distribute reconciliation tasks to multiple nodes for parallel execution; and the blockchain contract aggregates the calculation results of each trusted execution area settlement node, using the Byzantine Fault Tolerance (BFT) algorithm to ensure result consistency.

[0083] 3) This application can also use zero-knowledge proof (ZKP) result verification. Based on the computational proof generated by the settlement in the trusted execution zone, zk-SNARKs are introduced to encode the settlement calculation steps into verifiable circuits, so that the on-chain verification process can confirm the correctness of the calculation without accessing the original data.

[0084] 4) Introducing cross-chain settlement and multi-currency support: When settlement involves multiple consortium chains (such as domestic chains and international chains), the results can be synchronized and funds can be transferred in multiple currencies through cross-chain gateways or relay protocols, supporting multiple payment methods such as digital RMB, Euro stablecoin, and US dollar stablecoin.

[0085] In summary, this application provides a cross-carrier settlement and privacy protection platform based on blockchain and a Trusted Execution Environment (TEE). It aims to build a technical system capable of securely, reliably, and efficiently completing detailed real-time reconciliation and settlement among multiple carriers. Its core objective is to address the problems of difficulty in guaranteeing data privacy, high settlement latency, and lack of verifiability in cross-carrier settlement. This solution organically combines the tamper-proof, multi-party consensus, and traceability characteristics of blockchain with the confidential computation and cross-domain remote proof capabilities of TEE. It achieves a closed-loop process for encrypted uploading, isolated decryption, privacy computation, verifiable result storage, and automated clearing and settlement of cross-domain data. This not only ensures the confidentiality and privacy of business data for all parties but also significantly reduces the cost and latency of manual reconciliation and dispute resolution, thereby meeting the comprehensive requirements for real-time performance, transparency, security, and scalability in the next-generation communication operation environment.

[0086] This proposed solution can operate stably in cross-carrier and cross-border settlement scenarios, supporting secure calculation and automatic clearing of massive concurrent call detail records (CDRs) or traffic data, and possesses excellent engineering feasibility. Both the TEE calculation process and the blockchain evidence storage process can be implemented using existing commercial hardware and blockchain platforms, and can seamlessly integrate with existing carrier BSS / OSS systems at low cost. Through this invention, the settlement cycle can be shortened from the traditional days or weeks to minutes, significantly reducing manual intervention rates, decreasing dispute resolution time by more than 80%, and meeting privacy compliance requirements such as GDPR and data security laws. It has direct application value and economic benefits in carrier production environments.

[0087] According to an embodiment of this application, an embodiment of a data settlement device is also provided. Figure 3 This is a schematic diagram of a data settlement device according to an embodiment of this application. Figure 3 As shown, the device includes:

[0088] The data acquisition module 30 is used to acquire encrypted data corresponding to different operator nodes, wherein the encrypted data is obtained by encrypting the data to be settled.

[0089] The data decryption module 32 is used to decrypt encrypted data in the isolated memory of the trusted execution region to obtain the data to be settled. The isolated memory is a hardware isolation area inside the trusted execution region node. The isolated memory is used to ensure that the data is not accessed or tampered with externally during the decryption and processing.

[0090] The data calculation module 34 is used to process the data to be settled, obtain the settlement result, and upload the settlement result information to the blockchain for recording. The settlement processing is used to match and calculate the data to be settled between different operators, and the settlement result is used to represent the financial income and expenditure of each operator participating in the settlement.

[0091] Optionally, obtaining encrypted data sent by different operator nodes includes: receiving encrypted data and digital signatures sent by operator nodes, wherein the encrypted data is obtained by the operator node encrypting the data to be settled using a target key, and the data to be settled is obtained by standardizing the original business data and desensitizing sensitive fields, wherein the original business data includes at least one of the following: call usage records, traffic usage records, SMS usage records, billing event data, and service usage duration.

[0092] Optionally, before receiving the encrypted data and digital signature sent by the operator node, the method further includes: receiving a remote verification request sent by the operator node, wherein the remote verification request is used to request the trusted execution zone node to provide relevant information about its hardware and operating environment to verify whether the trusted execution zone node is in a trusted state; in response to the remote verification request, sending first verification information to the operator node, wherein the first verification information is used to characterize that the hardware and computing environment of the trusted execution zone node is in a trusted state, and the first verification information includes at least one of the following: hardware identity identifier, firmware version information, hash value of the loader, trusted timestamp, and platform signature.

[0093] Optionally, decrypting the encrypted data in the isolated memory of the trusted execution region to obtain the data to be settled includes: verifying the digital signature, wherein the verification is used to determine the integrity and trustworthiness of the source of the received encrypted data to ensure that the encrypted data has not been tampered with and was indeed generated by the operator node; if the digital signature verification passes, decrypting the encrypted data in the isolated memory to obtain the data to be settled.

[0094] Optionally, the settlement processing of the data to be settled to obtain the settlement result includes: matching the data to be settled corresponding to different operators one by one according to a preset identifier, and aligning the data to be settled within a preset time window to ensure the consistency of the data recording time, wherein the preset identifier includes at least one of the following: International Mobile Subscriber Identity (IMSI) or Mobile Subscriber Number; calculating the billing amount of the matched and aligned data to be settled according to a preset billing rule to determine the amount payable and payable for each operator, thereby obtaining the settlement result, wherein the preset billing rule is used to calculate the fee according to different service types and billing standards; determining the hash value corresponding to the settlement result, and generating second proof information for the billing calculation process, wherein the second proof information is used to characterize the completeness and credibility of the billing calculation process.

[0095] Optionally, uploading the settlement result information to the blockchain for recording includes uploading the hash value corresponding to the settlement result, the second proof information, the settlement period, and the identifiers of the operator nodes participating in the settlement to the consortium blockchain for recording. If the smart contract deployed in the consortium blockchain verifies the validity of the second proof information, the corresponding account status between the operator nodes participating in the settlement will be updated.

[0096] Optionally, the data settlement device is also used to: upon receiving an on-chain dispute request, re-acquire encrypted data corresponding to different operator nodes, wherein the on-chain dispute request indicates that the user has objections to the information recorded in the consortium blockchain; recalculate the settlement result based on the re-uploaded encrypted data and generate new second proof information; and update the information recorded in the consortium blockchain based on the recalculated settlement result and the new second proof information.

[0097] It should be noted that each module in the above-mentioned data settlement device can be a program module (for example, a set of program instructions to implement a certain function) or a hardware module. For the latter, it can be manifested in the following forms, but is not limited to them: each of the above modules is manifested as a processor, or the functions of each of the above modules are implemented by a processor.

[0098] It should be noted that the data settlement device provided in this embodiment can be used to perform... Figure 2 The data settlement method shown above is also applicable to the embodiments of this application, and will not be repeated here.

[0099] This application embodiment also provides a non-volatile storage medium, which includes a stored computer program. The device containing the non-volatile storage medium executes the following data settlement method by running the computer program: obtaining encrypted data corresponding to different operator nodes, wherein the encrypted data is obtained by encrypting the data to be settled; decrypting the encrypted data in the isolated memory of the trusted execution region to obtain the data to be settled, wherein the isolated memory is a hardware isolation area within the trusted execution region node, used to ensure that the data is not accessed or tampered with externally during decryption and processing; performing settlement processing on the data to be settled to obtain a settlement result, and uploading the settlement result information to the blockchain for recording, wherein the settlement processing is used to match and calculate the data to be settled between different operators, and the settlement result is used to characterize the financial income and expenditure of each participating operator.

[0100] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the data settlement method described in various embodiments of this application: obtaining encrypted data corresponding to different operator nodes, wherein the encrypted data is obtained by encrypting the data to be settled; decrypting the encrypted data in the isolated memory of the trusted execution region to obtain the data to be settled, wherein the isolated memory is a hardware isolation region inside the trusted execution region node, and the isolated memory is used to ensure that the data is not accessed or tampered with externally during the decryption and processing process; performing settlement processing on the data to be settled to obtain a settlement result, and uploading the settlement result information to the blockchain for recording, wherein the settlement processing is used to match and calculate the data to be settled between different operators, and the settlement result is used to characterize the financial income and expenditure of each operator participating in the settlement.

[0101] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0102] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0103] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0104] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0105] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0106] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

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

Claims

1. A data settlement method, characterized in that, include: Obtain encrypted data corresponding to different operator nodes, wherein the encrypted data is obtained by encrypting the data to be settled; The encrypted data is decrypted in the isolated memory of the Trusted Execution Region to obtain the data to be settled. The isolated memory is a hardware isolation area inside the Trusted Execution Region node. The isolated memory is used to ensure that the data is not accessed or tampered with externally during the decryption and processing. The data to be settled is processed to obtain a settlement result, and the information of the settlement result is uploaded to the blockchain for recording. The settlement process is used to match and calculate the data to be settled between different operators, and the settlement result is used to represent the financial income and expenditure of each operator participating in the settlement.

2. The data settlement method according to claim 1, characterized in that, Obtaining encrypted data sent by different operator nodes includes: The operator receives the encrypted data and digital signature sent by the operator node. The encrypted data is obtained by the operator node encrypting the data to be settled using a target key. The data to be settled is obtained by standardizing the original business data and desensitizing sensitive fields. The original business data includes at least one of the following: call usage records, data usage records, SMS usage records, billing event data, and service usage duration.

3. The data settlement method according to claim 2, characterized in that, Before receiving the encrypted data and digital signature sent by the operator node, the method further includes: The system receives a remote authentication request sent by the operator node, wherein the remote authentication request is used to request the trusted execution zone node to provide relevant information about the hardware and operating environment to verify whether the trusted execution zone node is in a trusted state. In response to the remote authentication request, a first authentication information is sent to the operator node, wherein the first authentication information is used to characterize that the hardware and computing environment of the trusted execution area node are in a trusted state, and the first authentication information includes at least one of the following: hardware identity identifier, firmware version information, hash value of the loader, trusted timestamp, and platform signature.

4. The data settlement method according to claim 2, characterized in that, The encrypted data is decrypted in the isolated memory of the trusted execution region to obtain the data to be settled, including: The digital signature is verified, wherein the verification is used to determine the integrity and source credibility of the received encrypted data, so as to ensure that the encrypted data has not been tampered with and was indeed generated by the operator node; If the digital signature verification is successful, the encrypted data is decrypted in the isolated memory to obtain the data to be settled.

5. The data settlement method according to claim 1, characterized in that, The settlement process is performed on the data to be settled, and the settlement results include: Based on a preset identifier, the pending settlement data corresponding to different operators are matched one by one, and the pending settlement data are aligned within a preset time window to ensure the consistency of data recording time. The preset identifier includes at least one of the following: International Mobile Subscriber Identity (IMSI) or Mobile Subscriber Number. Based on the pre-design fee rules, the billing calculation is performed on the matched and aligned data to be settled to determine the amount receivable and payable for each operator, and the settlement result is obtained. The pre-design fee rules are used to calculate fees according to different service types and billing standards. The hash value corresponding to the settlement result is determined, and a second proof information for the billing calculation process is generated, wherein the second proof information is used to characterize the integrity and credibility of the billing calculation process.

6. The data settlement method according to claim 5, characterized in that, Uploading the settlement result information to the blockchain for recording includes: The hash value corresponding to the settlement result, the second proof information, the settlement period, and the identifiers of the operator nodes participating in the settlement are uploaded to the consortium blockchain for recording. When the smart contract deployed in the consortium blockchain verifies the validity of the second proof information, the corresponding account status among the operator nodes participating in the settlement will be updated.

7. The data settlement method according to claim 6, characterized in that, The method further includes: Upon receiving an on-chain dispute request, the encrypted data corresponding to different operator nodes is retrieved again, wherein the on-chain dispute request indicates that the user has an objection to the information recorded in the consortium blockchain. Based on the re-uploaded encrypted data, the settlement result is recalculated, and new second proof information is generated; Based on the recalculated settlement result and the new second proof information, the information recorded in the consortium blockchain is updated.

8. A data settlement device, characterized in that, include: The data acquisition module is used to acquire encrypted data corresponding to different operator nodes, wherein the encrypted data is obtained by encrypting the data to be settled; The data decryption module is used to decrypt the encrypted data in the isolated memory of the trusted execution region to obtain the data to be settled. The isolated memory is a hardware isolation area inside the trusted execution region node. The isolated memory is used to ensure that the data is not accessed or tampered with externally during the decryption and processing. The data calculation module is used to process the data to be settled, obtain the settlement result, and upload the settlement result information to the blockchain for recording. The settlement processing is used to match and calculate the data to be settled between different operators, and the settlement result is used to characterize the financial income and expenditure of each operator participating in the settlement.

9. An electronic device, characterized in that, include: A memory and a processor, the processor being configured to run a program stored in the memory, wherein the program, when running, executes the data settlement method according to any one of claims 1 to 7.

10. A non-volatile storage medium, characterized in that, The non-volatile storage medium includes a stored computer program, wherein the device containing the non-volatile storage medium executes the data settlement method according to any one of claims 1 to 7 by running the computer program.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the data settlement method according to any one of claims 1 to 7.

Images