WO2023217029A1 - 数据交易的计费方法、装置、系统及存储介质 - Google Patents

数据交易的计费方法、装置、系统及存储介质 Download PDF

Info

Publication number
WO2023217029A1
WO2023217029A1 PCT/CN2023/092485 CN2023092485W WO2023217029A1 WO 2023217029 A1 WO2023217029 A1 WO 2023217029A1 CN 2023092485 W CN2023092485 W CN 2023092485W WO 2023217029 A1 WO2023217029 A1 WO 2023217029A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
information
data
platform
node device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/092485
Other languages
English (en)
French (fr)
Inventor
苗丹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
Research Institute of China Mobile Communication Co Ltd
Original Assignee
China Mobile Communications Group Co Ltd
Research Institute of China Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, Research Institute of China Mobile Communication Co Ltd filed Critical China Mobile Communications Group Co Ltd
Publication of WO2023217029A1 publication Critical patent/WO2023217029A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0283—Price estimation or determination
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0869—Network architectures or network communication protocols for network security for authentication of entities for achieving mutual authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present disclosure relates to the field of data applications, and in particular, to a charging method, device, system and storage medium for data transactions.
  • the data trading industry involves data demanders, data providers, data regulators, data exchanges, technical service providers, etc.
  • the data trading market faces major problems such as low data circulation efficiency, extensive business models, and high data security requirements.
  • embodiments of the present disclosure provide a charging method, device, system and storage medium for data transactions, aiming to meet the needs of multi-party data transactions.
  • embodiments of the present disclosure provide a charging method for data transactions, which is applied to the first platform.
  • the method includes:
  • the method before performing the charging task based on the charging collection information, the method further includes:
  • the charging collection information corresponding to the process key and the node device is bidirectionally verified.
  • the billing collection information corresponding to the two-way verification of the process key and the node device includes:
  • Receive a first authentication request sent by the node device the first authentication request carries at least first authentication information, and the first authentication information is at least the charging collection information based on the process key pair by the node device.
  • Verify the first authentication information and send a second authentication request to the node device based on the verification result.
  • the second authentication request carries at least second authentication information.
  • the second authentication information is based on the process secret.
  • the key is generated by encrypting at least the billing collection information;
  • the billing collection information corresponding to the two-way verification of the process key and the node device includes:
  • the first authentication request carries at least first authentication information.
  • the first authentication information is based on the process key after the node device verifies the second authentication information.
  • the billing collection information is generated during the execution of a job task by the at least two node devices.
  • the job task includes at least one of the following: a joint modeling task, a joint online reasoning task, and a joint offline reasoning task. .
  • the billing collection information includes at least one of the following: the information value IV of the data field, the number of data fields, the sample size of the data set, the attributes of the data set, the computing engine used, the algorithm type used, the graphics processor GPU Usage, central processing unit CPU usage, memory usage and network bandwidth usage.
  • executing the charging task based on the charging collection information includes:
  • embodiments of the present disclosure provide a charging method for data transactions, which is applied to node devices.
  • the method includes:
  • the method also includes:
  • Bidirectional verification of the charging collection information is based on the process key and the first platform.
  • the two-way verification of the charging collection information based on the process key and the first platform includes:
  • the first authentication request carries at least first authentication information.
  • the first authentication information is generated by encrypting at least the accounting collection information based on the process key. of;
  • the second authentication request carries at least second authentication information.
  • the second authentication information is the basis after the first platform verifies the first authentication information.
  • the process key is generated by encrypting at least the billing collection information;
  • the two-way verification of the charging collection information based on the process key and the first platform includes:
  • the second authentication request carries at least second authentication information
  • the second authentication information is the first platform based on the process key pair and at least the accounting Generated by collecting information and encrypting it;
  • Verify the second authentication information and send a first authentication request to the first platform based on the verification result.
  • the first authentication request carries at least first authentication information.
  • the first authentication information is based on the process.
  • the key is generated by encrypting at least the charging collection information.
  • the job tasks include at least one of the following: joint modeling tasks, joint online reasoning tasks, and joint offline reasoning tasks.
  • the billing collection information includes at least one of the following: the information value IV of the data field, the number of data fields, the sample size of the data set, the attributes of the data set, the computing engine used, the algorithm type used, the graphics processor GPU Usage, central processing unit CPU usage, memory usage and network bandwidth usage.
  • the node device is a first node device as a data provider or a second node device as a data demander.
  • the method further includes:
  • the set charging rule is determined based on the first request.
  • the method further includes:
  • an embodiment of the present disclosure provides a charging device for data transactions, which is applied to the first platform.
  • the device includes:
  • a receiving module configured to receive charging requests respectively sent by at least two node devices, where the charging requests at least carry job task identifiers;
  • a task generation module configured to generate charging tasks based on each of the charging requests
  • the receiving module is also used to receive charging collection information sent by each node device
  • a task execution module configured to execute the charging task based on the charging collection information.
  • inventions of the present disclosure provide a charging device for data transactions, which is applied to node equipment.
  • the device includes:
  • a sending module configured to send a charging request to the first platform according to the job task, where the charging request at least carries the job task identifier;
  • the acquisition module is used to obtain the charging collection information during the execution of job tasks based on the set charging rules
  • the sending module is also configured to send the charging collection information to the first platform.
  • embodiments of the present disclosure provide a first platform, including: a processor and a memory for storing a computer program that can be run on the processor, wherein when the processor is used to run the computer program, Perform the steps of the method described in the first aspect of the embodiment of the present disclosure.
  • an embodiment of the present disclosure provides a node device, including: a processor and a memory used to store a computer program that can be run on the processor, wherein the processor is used to execute when running the computer program. The steps of the method described in the second aspect of the embodiment of the present disclosure.
  • an embodiment of the disclosure provides a data sharing service system, including: the first platform described in the fifth aspect of the embodiment of the disclosure and at least two node devices described in the sixth aspect of the embodiment of the disclosure.
  • an embodiment of the present disclosure provides a storage medium.
  • a computer program is stored on the storage medium.
  • the computer program is executed by a processor, the steps of any method described in the embodiment of the present disclosure are implemented.
  • the first platform receives charging requests sent by at least two node devices respectively; generates charging tasks based on each charging request; receives charging collection information sent by each node device, and collects information based on charging The information performs the billing task; in this way, billing can be performed based on the billing collection information of multiple parties in the data transaction, which can meet the needs of multi-party data transactions and can effectively improve the circulation efficiency of data transactions.
  • Figure 1 is a schematic structural diagram of a data sharing service system according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of a charging method for data transactions according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a charging method for data transactions according to another embodiment of the present disclosure.
  • Figure 4 is a schematic flowchart of a charging method for data transactions according to another embodiment of the present disclosure.
  • Figure 5 is a schematic diagram of the system architecture of an application embodiment of the present disclosure.
  • Figure 6 is a schematic flow chart of "network connection and computing environment preparation" in the application embodiment of the present disclosure
  • Figure 7 is a schematic flowchart of "joint modeling" in an application embodiment of the present disclosure.
  • Figure 8 is a schematic flow chart of "joint reasoning" in the application embodiment of the present disclosure.
  • Figure 9 is a schematic structural diagram of a charging device for data transactions according to an embodiment of the present disclosure.
  • Figure 10 is a schematic structural diagram of a charging device for data transactions according to another embodiment of the present disclosure.
  • Figure 11 is a schematic structural diagram of the first platform according to an embodiment of the present disclosure.
  • Figure 12 is a schematic structural diagram of a node device according to an embodiment of the present disclosure.
  • Embodiments of the present disclosure provide a data sharing service system for realizing online circulation of data between multiple parties, without being limited to traditional point-to-point data transactions, thereby improving the production and circulation efficiency of data elements.
  • This system can also be called a Data Sharing Service Network (DSSN) system.
  • the system includes: a first platform, namely the Data Sharing Service Platform (DSSP) shown in Figure 1 and multiple node devices (also called data service nodes), wherein the first
  • the platform can also be a data sharing platform (DSP); according to different roles, the node device is divided into a first node device as a data provider and a second node device as a data demander.
  • DSSP Data Sharing Service Platform
  • DSP data sharing platform
  • the first node device can also be called a Data Service Node (DSN), and the second node device can also be called a Data Service Node (DSN). It can be called a Data Requirement Node (DRN).
  • DSN Data Service Node
  • DRN Data Requirement Node
  • the DSSP/DSP and each node device can be connected through an Internet Protocol (IP) private network to improve the security of data transmission.
  • IP Internet Protocol
  • the first platform is mainly responsible for node management, data directory management, data circulation management, billing management, data transaction management, security compliance management, DSSN operation management, etc.;
  • the first node device is mainly responsible for the docking and network of shared data. Access, data security calculation, transaction processing, etc.;
  • the second node device is mainly responsible for network access of the data demand side, data service request processing, data security calculation, etc.
  • the embodiment of the present disclosure provides a charging method for data transactions, which is applied to the aforementioned first platform. As shown in Figure 2, the method includes:
  • Step 201 Receive charging requests respectively sent by at least two node devices, where the charging requests at least carry job task identifiers.
  • the data transactions in the embodiments of the present disclosure are different from the traditional point-to-point data cooperation model, and often involve multiple transaction parties jointly performing data circulation, for example, providing data based on private computing technologies such as federated learning or multi-party secure computing.
  • data demanders need to establish connections with multiple data providers to implement data transactions.
  • a data transaction involves job tasks for multiple node devices. After the data demander creates a data transaction project based on the first platform, the job tasks can be assigned to each node device. After each node device starts the corresponding job task, it can Send an accounting request carrying the job task identifier to the first platform.
  • Step 202 Generate a charging task based on each charging request.
  • the first platform After receiving the charging request sent by each node device as a participant, the first platform generates a charging task for the project based on the job task identifier of each node device.
  • the charging task can be understood as each job task for the data transaction project, and the charging bill is constructed based on the charging rules. For example, a weight value can be assigned to the sub-bill of each job task, and weighted based on each sub-bill. The summed result gives the total billing bill.
  • Step 203 Receive charging collection information sent by each node device.
  • each node device can locally obtain the charging collection information during the execution of the job task based on the set charging rules, and send the charging collection information to the first platform.
  • Step 204 Execute the charging task based on the charging collection information.
  • the first platform generates a charging sub-bill for each job task based on the charging collection information of each node device, and generates a total charging bill based on the charging sub-bill for each job task.
  • the first platform in the embodiment of the present disclosure receives charging requests sent by at least two node devices respectively; generates charging tasks based on each charging request; receives charging collection information sent by each node device, and performs the charging based on the charging request.
  • Collecting information to perform the billing task can perform billing based on the billing collection information of multiple parties in data transactions, which can meet the needs of multi-party data transactions and can effectively improve the circulation efficiency of data transactions.
  • the method further includes:
  • the charging collection information corresponding to the process key and the node device is bidirectionally verified.
  • the first information sent by the node device may be carried by the aforementioned charging request or sent separately by the node device, which is not limited in this embodiment of the disclosure.
  • the first information may be a key index number corresponding to the job task identifier;
  • the second information may include a key version number and a key algorithm identifier;
  • the process key in this embodiment of the disclosure may be the first platform Or the key management module on the node device side generates the process key based on the first information and the second information, that is, the key management module of the first platform can generate the process key based on the first information and the second information, and the key management module of the node device can also generate the process key.
  • the process key may be generated based on the first information and the second information.
  • the charging collection information corresponding to the two-way verification of the node device based on the process key includes:
  • Receive a first authentication request sent by the node device the first authentication request carries at least first authentication information, and the first authentication information is at least the charging collection information based on the process key pair by the node device.
  • Verify the first authentication information and send a second authentication request to the node device based on the verification result.
  • the second authentication request carries at least second authentication information.
  • the second authentication information is based on the process secret.
  • the key is generated by encrypting at least the billing collection information;
  • the key management module on the node device side can generate a process key based on the first information and the second information, and execute based on the process key pair.
  • the accounting collection information obtained during the job task is encrypted, the first authentication information is generated, and the first authentication request carrying the first authentication information is sent to the first platform.
  • the first authentication request also carries information such as the node identification and/or transaction time of the node device.
  • the first platform may determine the corresponding second information based on the first information from the node device, and the key management module on the first platform side generates a process key based on the first information and the second information, based on the process key pair Verify the first authentication information, and after passing the verification, encrypt at least the accounting collection information based on the process key, generate second authentication information and send a second authentication request carrying the second authentication information to the node device, and the node
  • the device verifies the second authentication information based on the process key. For example, it can encrypt the local accounting collection information based on the process key, compares the encrypted data with the second authentication information to obtain the verification result, and returns the verification result. The result is given to the first platform.
  • the charging collection information corresponding to the two-way verification of the node device based on the process key includes:
  • the first authentication request carries at least first authentication information.
  • the first authentication information is based on the process key after the node device verifies the second authentication information.
  • the first platform can determine the corresponding second information based on the first information from the node device, and the key management module on the first platform side generates the process key based on the first information and the second information, based on the
  • the process key encrypts the accounting collection information from the node device, generates second authentication information, and sends a second authentication request carrying the second authentication information to the node device.
  • the node device may be based on the second information from the first platform,
  • the key management module on the node device side generates a process key based on the first information and the second information, and verifies the second authentication information based on the process key. For example, the local charging collection information can be verified based on the process key. Encrypted and will be encrypted
  • the data is compared with the second authentication information to obtain the verification result.
  • the node device After the second authentication information passes the verification, the node device encrypts the accounting collection information based on the process key, generates the first authentication information, and sends a first authentication request carrying the first authentication information to the first platform.
  • the first platform can verify the first authentication information based on the process key, thereby realizing two-way verification of the charging collection information.
  • the charging collection information is generated during the execution of a job task by the at least two node devices.
  • the job task includes at least one of the following: a joint modeling task, a joint online reasoning task, and a joint offline reasoning task. .
  • the joint modeling task can be understood as building a computing model based on specified computing engines and algorithms for the aforementioned data transaction projects.
  • the joint online reasoning task can be understood as performing data transactions online.
  • Joint offline reasoning can be understood as executing data transactions offline.
  • the multi-party cooperation data transaction process in the embodiment of the present disclosure involves encryption and calculation of original data, thereby forming high-value data elements.
  • the selection of calculation engines and algorithms directly affects the model. Training and data security computing effects.
  • the guarantee of computing resources can improve the efficiency of data element production and have a positive impact on data circulation transaction income.
  • the billing collection information includes at least one of the following: information value (IV) of the data field, number of data fields, data set sample size, data set attributes, and calculation engine used. , the type of algorithm used, graphics processing unit (GPU) occupancy, central processing unit (Central Processing Unit, CPU) occupancy, memory occupancy and network bandwidth occupancy.
  • information value (IV) of the data field includes at least one of the following: information value (IV) of the data field, number of data fields, data set sample size, data set attributes, and calculation engine used. , the type of algorithm used, graphics processing unit (GPU) occupancy, central processing unit (Central Processing Unit, CPU) occupancy, memory occupancy and network bandwidth occupancy.
  • GPU graphics processing unit
  • CPU Central Processing Unit
  • executing the charging task based on the charging collection information includes:
  • the first platform can generate a charging sub-bill for each job task based on the charging collection information of each node device that has passed two-way verification, and generate a bill based on the charging sub-bill for each job task. into the total bill, perform online or offline deductions on the bill, and complete billing management.
  • the embodiment of the present disclosure also provides a charging method for data transactions, which is applied to the aforementioned node device. As shown in Figure 3, the method includes:
  • Step 301 Send a charging request to the first platform according to the job task, where the charging request at least carries the job task identifier.
  • the node device receives the job task assigned by the first platform based on the created data transaction project. After starting the job task, it can send a charging request carrying the job task identifier to the first platform.
  • Step 302 Obtain charging collection information during the execution of the job task based on the set charging rules.
  • the node device may respond to initiating the job task and obtain charging collection information during the execution of the job task based on the set charging rules.
  • the node device can monitor whether the job task is started based on the charging trigger module, and if so, trigger the charging collection module to obtain the charging collection information during the execution of the job task.
  • setting the charging rules may be indicated by the first platform when allocating job tasks, so that the node device can obtain corresponding charging collection information based on the indicated setting charging rules.
  • Step 303 Send the charging collection information to the first platform.
  • the node device may send the charging collection information to the first platform after the job task is executed, or send the charging collection information to the first platform periodically, or send the charging collection information to the third platform based on the set time period.
  • a platform which is not limited in the embodiments of this disclosure.
  • the data transactions in the embodiments of the present disclosure are different from the traditional point-to-point data cooperation model, and often involve multiple transaction parties jointly performing data circulation, for example, providing data based on private computing technologies such as federated learning or multi-party secure computing.
  • data demanders need to establish connections with multiple data providers to implement data transactions.
  • the first platform generates a charging task based on the charging request sent by each node device participating in the data transaction, and executes the charging task based on the charging collection information sent by each node device. In this way, it can be based on the charging collection information of multiple parties in the data transaction.
  • Billing can meet the needs of multi-party data transactions and can effectively improve the circulation efficiency of data transactions.
  • the method further includes:
  • Bidirectional verification of the charging collection information is based on the process key and the first platform.
  • the key management module of the node device can allocate a corresponding key index to the job task based on the set charging rules and key dispersion level, that is, the first information that determines the process key.
  • the first platform may determine the second information of the process key based on the job task identification, for example, determine the key version number and key algorithm identification of the process key.
  • the process key in the embodiment of the present disclosure can be generated by the key management module on the first platform or node device side based on the first information and the second information, that is, the key management module on the first platform can be generated based on the first information and the second information.
  • the key management module of the node device may also generate the process key based on the first information and the second information.
  • the two-way verification of the charging collection information based on the process key and the first platform includes:
  • the first authentication request carries at least first authentication information.
  • the first authentication information is generated by encrypting at least the accounting collection information based on the process key. of;
  • the second authentication request carries at least second authentication information.
  • the second authentication information is based on the process after the first platform verifies the first authentication information.
  • the key is generated by encrypting at least the billing collection information;
  • the key management module on the node device side can generate a process key based on the first information and the second information, and execute based on the process key pair.
  • the accounting collection information obtained during the job task is encrypted, the first authentication information is generated, and the first authentication request carrying the first authentication information is sent to the first platform.
  • the first authentication request also carries information such as the node identification and/or transaction time of the node device.
  • the first platform may determine the corresponding second information based on the first information from the node device, and the key management module on the first platform side generates a process key based on the first information and the second information, based on the process key pair Verify the first authentication information, and after passing the verification, encrypt at least the accounting collection information based on the process key, generate second authentication information and send a second authentication request carrying the second authentication information to the node device, and the node
  • the device performs the second authentication information based on the process key. Verification can be performed.
  • the local charging collection information can be encrypted based on the process key
  • the encrypted data can be compared with the second authentication information to obtain the verification result
  • the verification result can be returned to the first platform.
  • the two-way verification of the charging collection information based on the process key and the first platform includes:
  • the second authentication request carries at least second authentication information
  • the second authentication information is the first platform based on the process key pair and at least the accounting Generated by collecting information and encrypting it;
  • Verify the second authentication information and send a first authentication request to the first platform based on the verification result.
  • the first authentication request carries at least first authentication information.
  • the first authentication information is based on the process.
  • the key is generated by encrypting at least the charging collection information.
  • the first platform can determine the corresponding second information based on the first information from the node device, and the key management module on the first platform side generates the process key based on the first information and the second information, based on the
  • the process key encrypts the accounting collection information from the node device, generates second authentication information, and sends a second authentication request carrying the second authentication information to the node device.
  • the node device may be based on the second information from the first platform,
  • the key management module on the node device side generates a process key based on the first information and the second information, and verifies the second authentication information based on the process key. For example, the local charging collection information can be verified based on the process key. Encrypt, and compare the encrypted data with the second authentication information to obtain the verification result.
  • the node device After the second authentication information passes the verification, the node device encrypts the accounting collection information based on the process key, generates the first authentication information, and sends a first authentication request carrying the first authentication information to the first platform.
  • the first platform can verify the first authentication information based on the process key, thereby realizing two-way verification of the charging collection information.
  • the job tasks include at least one of the following: joint modeling tasks, joint online reasoning tasks, and joint offline reasoning tasks.
  • the billing collection information includes at least one of the following: the information value IV of the data field, the number of data fields, the sample size of the data set, the attributes of the data set, the computing engine used, the algorithm type used, the graphics processor GPU Usage, central processing unit CPU usage, memory usage and network bandwidth usage.
  • the billing method comprehensively considers various factors that affect the production of data elements in the data transaction process, can maximize the value of data, and promote the circulation efficiency of data transactions in a refined manner.
  • the node device is a first node device as a data provider or a second node device as a data demander. It can be understood that the multiple node devices in this embodiment of the present disclosure include a first node device as a data provider and a second node device as a data demander.
  • the method further includes:
  • the set charging rule is determined based on the first request.
  • the first request can be understood as instruction information sent by the first platform to the node device for the node device to create a job task.
  • the indication information may include: target node identification, identification of other nodes participating in the cooperation, cooperation content, computing engine, data fields, algorithms, whether to support GPU/CPU computing, charging rules, etc., wherein the charging rules may Clarify the dimensions of billing collection information, the weight of each dimension, and the pricing information of each dimension.
  • the method further includes:
  • the second request can be understood as a creation request sent by the second node device to request the creation of a data transaction item
  • the first platform can send the first request to each first node device based on the second request.
  • the second request may include at least one of the following: partners, cooperation content, charging methods, charging rules, computing engines, algorithms, data fields, whether to support GPU/CPU computing, etc.
  • the first platform sends the first request to each first node device that needs to cooperate based on the second request, it receives the confirmation information returned by each node device, and returns the request to the second node device based on the confirmation information of each node device.
  • the response indicates that the data transaction project has been successfully established.
  • the second node device establishes a connection with each first node device participating in the cooperation.
  • Figure 4 shows the charging method of data transactions applied to the data sharing service system according to the embodiment of the present disclosure.
  • the data sharing service system includes: DSSP/DSP, DSN as the data provider and DSN as the data demander.
  • DRN the method includes:
  • Step 401 Configure job information and start the job task.
  • each node device participating in the cooperation configures job information and starts the job task.
  • Configuring the job information includes: installing the algorithm and/or algorithm engine required to execute the job task, obtaining relevant data sources, etc.
  • Step 402 Send a charging request.
  • each node device sends an accounting request to the DSSP/DSP, and the accounting request carries the job task identifier.
  • Step 403 Generate a charging task.
  • the DSSP/DSP After receiving the charging request sent by each node device as a participant, the DSSP/DSP generates the charging task for the project based on the job task identifier of each node device.
  • Step 404 Collect data according to billing rules and synchronize billing collection information.
  • each node device can locally obtain the charging collection information during the execution of the job task based on the set charging rules, and send the charging collection information to the DSSP/DSP.
  • Step 405 The job task ends.
  • each node device After each node device completes the job task, it sends information indicating the end of the job to DSSP/DSP.
  • DSSP/DSP determines the end of the project's job task based on the information indicating the end of the job from each participant.
  • Step 406 Execute the billing task and update the account balance.
  • DSSP/DSP generates charging sub-bills for each job task based on the charging collection information of each node device, generates a total charging bill based on the charging sub-bills for each job task, and updates the account balance.
  • DSSP includes three parts: management functional area (DSS-M), transaction functional area (DSS-T) and service opening functional area (DSS-S).
  • DSS-M management functional area
  • DSS-T transaction functional area
  • DSS-S service opening functional area
  • the management functional area includes: network connection management, engine management, contract execution management, operations management and security management.
  • network connection management includes node registration, authentication, configuration management, node interconnection, node status monitoring, etc. of node devices;
  • engine management includes computing engine listing application, listing review, engine download management and version maintenance, etc., and supports heterogeneous engines. Loading management, thereby externally shielding heterogeneous engines, unifying services, and realizing engine-level interconnection;
  • contract execution management includes contract uploading, project creation, project issuance, task monitoring, metering statistics, etc.;
  • operation management includes user Account management, operation analysis, operation and maintenance monitoring, etc.;
  • security management includes system security, business security, container security, key management, etc.
  • the transaction functional area includes: data publishing, transaction services, billing management and transaction supervision.
  • data release includes data catalog registration, data catalog review, data catalog query, data catalog rights confirmation, etc.
  • transaction services include transaction portal, data value evaluation, transaction matching, contract signing, transaction certificate deposit, transaction order management, payment services, etc.
  • Transaction supervision includes compliance supervision, safety supervision, credit supervision, etc.
  • the service opening functional area is used to install an open service level, including platform-as-a-service (PaaS) service opening (for example, data model development tools, test environments, compliance audits, release and launch, etc. Capability opening), Software-as-a-service (SaaS) service opening (for example, services provided to the industry, blacklist query, etc.) and Data-as-a-service (DaaS) services Open three parts (for example, data products and services provided to the industry, such as corporate credit assessment models, etc.).
  • PaaS platform-as-a-service
  • SaaS software-as-a-service
  • DaaS Data-as-a-service
  • the node device includes user management, authentication and authorization, data directory, connection management, security management, project management, task management, engine management, key management, model management, log management, and system monitoring. , billing management, calculation engine, data security domain and other functional modules. It should be noted that the node device can provide different functional interfaces according to different customer groups (data demanders, data providers).
  • the charging method of this application embodiment involves the aforementioned charging management module on the node device side, the computing engine module, and the charging management on the DSSP/DSP side.
  • the charging management on the DSSP/DSP side supports two charging modes: online charging and offline charging.
  • the billing management mainly involves the integrated billing gateway, account balance management module, pricing management module, offline billing gateway module and billing system module.
  • the charging management module on the node device side includes a charging triggering module, and the computing engine module on the node device side includes a charging collection module.
  • the billing collection module is located in each computing engine of the node device. According to the specific billing business model, it is responsible for collecting and monitoring the customer's usage information of data, computing engines, algorithms, computing resources, etc. in data transaction tasks, that is, billing collection information. . Since the data circulation and transaction process involves the encryption and calculation of original data, thereby forming high-value data elements, on the one hand, it is difficult for the calculation engine, The choice of algorithm directly affects model training and data security calculation effects. On the other hand, the guarantee of computing resources can improve the efficiency of data element generation and have a positive impact on data circulation transaction income. This application embodiment uses key factors that affect data circulation transaction revenue as billing collection points, thereby forming multi-dimensional billing collection information.
  • the billing collection information includes but is not limited to the IV of the data field, the number of data fields, the size of the data sample, the attributes of the data set (training data, test data, inference data), the used computing engine, the used algorithm, and the GPU Usage, CPU usage, memory usage, network bandwidth usage, etc.
  • the billing trigger module located in the billing management module of the node device, is responsible for detecting whether the customer initiates a data transaction task at the service node, thereby triggering the billing function.
  • the key management module is located in the node device and is responsible for storing keys and encrypted transaction process data.
  • the keys are indexed according to different charging rules (offline, online) and different key dispersion levels.
  • the converged billing gateway is responsible for connecting the billing function modules of DSSP/DSP with the billing trigger module of the node device, generating converged billing bills based on the collected multi-dimensional billing collection information, and providing offline bills to offline billing.
  • the billing gateway module collects billing information in real time for online billing, completes the bill deduction function, calculates business quotas (i.e., business availability), and provides the calculation results to the billing trigger module.
  • the account balance management module is part of the online billing function and is responsible for storing and updating customer account balances.
  • the pricing management module is part of the online billing function and is responsible for determining the fees for using data transaction services based on the data element pricing strategy.
  • the offline billing gateway module is part of the offline billing function and is responsible for error checking, preprocessing and storage of billing bills, collecting transaction billing bills and sending them to the billing system module.
  • Billing system module through which customers are charged for data transaction services.
  • stage 1) includes the following steps:
  • Step 601 Node registration and network access.
  • the data demander and the data provider register their respective data service nodes to the DSSN network, the data service nodes are activated and go online, and the DSSP/DSP can view all activated node devices.
  • Step 602 Create a data directory and upload a sample data set.
  • the data provider creates a data directory on the first node device, including data field names, data volume, data pricing, data storage location, data sources, applicable industries, data sensitivity level, data directory visibility permissions, etc., and uploads samples.
  • Example data set sent to DSSP/DSP for review.
  • Step 603 Review the release data directory.
  • platform operators or data auditors review the data catalog and sample data sets at DSSP/DSP (the review content includes the legality, compliance, and completeness of the data catalog, data test sets, etc.), and release the data catalog after passing the review.
  • DSSP/DSP displays the data directory according to visible permissions.
  • Step 604 Request creation of projects and applications.
  • the second node device as the data demander requests to create a data transaction item, that is, sends the aforementioned second request to the DSSP/DSP.
  • This second request can specify the partner, cooperation content, billing method, and billing.
  • Rules, calculation engines, algorithms, data fields, whether to support GPU/CPU calculations, etc., DSSP/DSP can create applications (the applications are used to perform job tasks) according to the second request, and the instruction information of each application (i.e.
  • the aforementioned first Request may include: node identification (Identifier, ID), other node IDs participating in the cooperation, cooperation content, calculation engine, data fields, algorithms, whether to support GPU/CPU calculations, calculation rules, etc., among which the billing rules can clearly calculate The dimensions of fee collection information, the weight of each dimension and the pricing information of each dimension, etc.
  • Step 605 Forward the project and application.
  • DSSP/DSP audits projects and applications for example, audits and records billing methods and billing rules, and forwards projects and applications to participating node devices, that is, sends the first request to the node device.
  • Step 606 Review and confirm the project and application.
  • the node devices participating in the cooperation review and confirm the projects and applications store the charging methods and charging rules (the charging information that needs to be collected is notified to the charging collection module), and return the confirmation information to the DSSP/DSP.
  • Step 607 Return a response message indicating successful creation.
  • the DSSP/DSP returns a successfully created response message to the demand-side service node (ie, the second node device), where the response message carries the node ID of the cooperative data provider.
  • Step 608 Establish connections between service nodes.
  • connections are established between all participating node devices.
  • Step 609 Download and install the algorithm and calculation engine.
  • stage 2 includes the following steps:
  • Step 701 request data authorization.
  • all data service nodes participating in the cooperation request data authorization from the DSSP/DSP for example, send a user request carrying at least one of the following: node ID, data directory ID, project ID, application ID, and computing engine ID to the DSSP/DSP. Requests for data authorization.
  • Step 702 Return an authorization response.
  • the DSSP/DSP completes the data authorization review and returns a data authorization response.
  • the data authorization response can carry the node ID, project ID, and application ID.
  • Step 703 Create a training job task.
  • the service node of the data demander creates a training job task and sends a request carrying the job task ID to each participating data provider service node.
  • Step 704 The job preparation is completed.
  • each data provider service node returns indication information indicating completion of job preparation to the service node of the data demander.
  • Step 705 The job task is executed and the charging function is triggered.
  • the data demander and each data provider service node execute jobs
  • the charging trigger module monitors the execution of job tasks and triggers the charging function.
  • Step 706 Send a charging request.
  • each data service node participating in cooperation sends a charging request to the DSSP/DSP.
  • the charging triggering module of each data service node queries the key management module for the key index, and sends a charging request to the converged charging gateway.
  • the charging request can carry the node ID, project ID, Application ID, job task ID, billing collection information and key index number (ie, the aforementioned first information).
  • the billing collection module of each data service node can collect relevant data during the execution of job tasks to obtain billing collection information.
  • the billing collection information includes but is not limited to the IV of the data field and the number of data fields. , data sample size, data set attributes (training data, test data, inference data), used computing engine, used algorithm, GPU usage, CPU usage, memory usage, network bandwidth usage, etc.
  • Step 707 Generate a charging task.
  • the converged charging gateway of DSSP/DSP can generate charging bills for each service node according to the charging method and charging rules.
  • Step 708 Return a charging response.
  • DSSP/DSP can return a charging response to each data service node.
  • the charging response can carry the data demander charging account ID, job task ID, charging identification (online/offline), business quota, online/offline Offline accounting key version number, online/offline accounting key algorithm identification.
  • Step 709 Generate a message authentication code (Message Authentication Code, MAC) 1 based on the process key.
  • MAC Message Authentication Code
  • the key management module of each participating data service node can generate a process key based on the aforementioned key index number, key version number and key algorithm identification, and the charging triggering module pairs the node with the process key based on the process key.
  • ID, project ID, application ID, job task ID, transaction date, transaction time, billing collection information, etc. are encrypted to generate the message authentication code MAC1 (that is, the aforementioned first authentication information).
  • Step 710 Send a first authentication request.
  • the data service node participating in the cooperation sends a first authentication request carrying MAC1 to the DSSP/DSP.
  • the first authentication request may also carry node ID, transaction date, transaction time, etc.
  • Step 711 Verify MAC1, encrypt and calculate the accounting collection information based on the process key, and generate the message authentication code MAC2.
  • the key management module on the first platform side can generate a process key, and facilitate the process key to verify MAC1, obtain the charging collection information sent by the data service node, and encrypt and calculate the charging collection information based on the process key , generate the message authentication code MAC2 (that is, the aforementioned second authentication information).
  • Step 712 return the second authentication request.
  • the DSSP/DSP sends a second authentication request to the data service node participating in the cooperation,
  • the second authentication request carries at least the message authentication code MAC2.
  • Step 713 verify MAC2
  • the data service nodes participating in the cooperation verify MAC2 based on the process key.
  • the local charging collection information can be encrypted based on the process key, and the encrypted data can be compared with MAC2 to obtain the verification result.
  • Step 714 The job task is completed and the verification result is notified.
  • the job tasks of the participating data service nodes are completed, the model training is completed, and the verification result notification is sent to the DSSP/DSP.
  • Step 715 Complete charge deduction/update billing and update business quota.
  • the converged charging gateway of DSSP/DSP summarizes the charging bills of each participating data service node, updates the bill amount, completes deductions, and updates business quotas.
  • Step 716 The model is deployed to the running environment.
  • the trained model can be deployed to the running environment.
  • each data service node uses the process key internally based on the key management module to collect information on the node ID, project, application ID, job task ID, transaction date, transaction time, and billing.
  • the message authentication code MAC1 is obtained, and the MAC1 is sent to the first platform to avoid leakage of relevant information.
  • the first platform generates a process key based on the key management module to verify the MAC1.
  • DSSP/DSP is based on the process.
  • the key encrypts and calculates the accounting collection information to generate the message authentication code MAC2, and sends MAC2 to the data service node for verification.
  • the data collection information is in an encrypted state, which can effectively prevent leakage or tampering. Improved security of billing process. For example, if the two-way verification is successful, the data service node can notify the DSSP/DSP to complete the deduction and update the service quota.
  • stage 3 can be divided into two methods: online reasoning and offline reasoning.
  • online reasoning can include the following steps:
  • Step 801a Initiate an inference request.
  • the business system of the demand side initiates an inference request.
  • Step 802a Create a model inference task.
  • the data service node of the data demander creates a model inference job task and sends task information carrying the job task ID to the data service nodes of each cooperating data provider.
  • Step 803a The job preparation is completed.
  • the data service node of the participating data provider returns information indicating that the preparation is completed to the data service node of the data demander.
  • Step 804a job task execution and billing process.
  • each data service node participating in the cooperation enters the job task execution and billing process.
  • For the relevant billing process refer to steps 705 to 715 in Figure 7 , which will not be described again here.
  • Step 805a return the inference result.
  • the data service node of each data provider returns the model inference results to the data service node of the data demander.
  • Step 806a summarize the inference results.
  • the data service node on the data demand side summarizes the model inference results.
  • Step 807a return the inference result.
  • the data service node of the data demander returns the model inference results to the business system.
  • offline reasoning can include the following steps:
  • Step 801b Determine the job cycle and trigger time for running the batch job task.
  • the data service node of the data demander determines the job cycle and trigger time for running the batch job task based on the configuration information.
  • Step 802b Create a model inference job task.
  • the data service node of the data demander creates a model inference job task and sends the task information to the data service nodes of each cooperating data provider.
  • the task information carries the job task ID, the job cycle and the trigger time of the batch job.
  • Step 803b The job preparation is completed.
  • the data service node of the participating data provider returns information indicating that the preparation is completed to the data service node of the data demander.
  • Step 804b job task execution and billing process.
  • each data service node participating in the cooperation enters the job task execution and billing process.
  • For the relevant billing process refer to steps 705 to 715 in Figure 7 , which will not be described again here.
  • Step 805b return the inference result.
  • the data service node of each data provider returns the model inference results to the data requirements.
  • Party s data service node.
  • Step 806b Summarize the inference results.
  • the data service node on the data demand side summarizes the model inference results.
  • Step 807b Initiate an inference request.
  • the business system initiates the inference request asynchronously.
  • Step 808b return the inference result.
  • the data demander service node returns the inference results to the business system.
  • the charging method for data transactions in this application embodiment can charge multiple parties participating in the cooperation, involving the above-mentioned network connection and computing environment preparation, joint modeling, joint online reasoning, joint offline reasoning and other stages, and Supports two billing modes: online billing and offline billing.
  • the needs of multi-party data transactions can be met, thereby effectively improving the circulation efficiency of data transactions; in addition, based on multi-dimensional
  • the billing collection information enables the billing method of this application embodiment to comprehensively consider various factors that affect the production of data elements in the data transaction process, maximize the value of data, and promote the circulation efficiency of data transactions in a refined manner; again , In order to ensure that the billing collection information is safe and cannot be tampered with, this application embodiment uses a process key to encrypt and bidirectionally verify the billing collection information, which can ensure the security of data during the billing process.
  • the embodiments of the present disclosure also provide a charging device for data transactions.
  • the charging device for data transactions is applied to the first platform and corresponds to the above-mentioned charging method on the first platform side.
  • the above-mentioned Each step in the charging method embodiment on the first platform side is also fully applicable to the charging device embodiment of this data transaction.
  • the charging device for data transactions includes: a first receiving module 901 , a task generating module 902 and a task executing module 903 .
  • the first receiving module 901 is configured to receive charging requests respectively sent by at least two node devices, where the charging requests at least carry job task identifiers;
  • the task generating module 902 is configured to generate charging tasks based on each of the charging requests;
  • a receiving module 901 is also configured to receive charging collection information sent by each node device;
  • a task execution module 903 is configured to execute the charging task based on the charging collection information.
  • the charging device for data transactions also includes: a first sending module 904 and a first verification module 905; the first receiving module 901 is also used to receive confirmation sent by each node device.
  • the first sending module 904 is configured to send second information that determines the process key to each node device based on the first information;
  • the first verification module 905 is configured to determine the process key based on the The process key bidirectionally verifies the charging collection information corresponding to the node device.
  • the first verification module 905 is specifically used to:
  • Receive a first authentication request sent by the node device the first authentication request carries at least first authentication information, and the first authentication information is at least the charging collection information based on the process key pair by the node device.
  • Verify the first authentication information and send a second authentication request to the node device based on the verification result.
  • the second authentication request carries at least second authentication information.
  • the second authentication information is based on the process secret.
  • the key is generated by encrypting at least the billing collection information;
  • the first verification module 905 is specifically used to:
  • the first authentication request carries at least first authentication information.
  • the first authentication information is based on the process key after the node device verifies the second authentication information.
  • the charging collection information is generated during the execution of a job task by the at least two node devices.
  • the job task includes at least one of the following: a joint modeling task, a joint online reasoning task, and a joint offline task. reasoning tasks.
  • the billing collection information includes at least one of the following: information value IV of the data field, number of data fields, data set sample size, data set attributes, calculation engine used, algorithm type used, graphics processing GPU occupancy, central processing unit CPU occupancy, memory occupancy and network bandwidth occupancy.
  • the task execution module 903 is specifically used to:
  • the first receiving module 901, the task generating module 902, the task executing module 903, the first sending module 904 and the first verification module 905 can be implemented by the processor in the charging device for data transactions.
  • the processor needs to run computer programs in memory to perform its functions.
  • the embodiment of the present disclosure also provides a charging device for data transactions.
  • the charging device for data transactions is applied to a node device and corresponds to the charging method on the node device side.
  • the node device Each step in the charging method embodiment on the side is also fully applicable to the charging device embodiment of this data transaction.
  • the charging device for data transactions includes: a second sending module 1001 and an obtaining module 1002.
  • the second sending module 1001 is configured to send a charging request to the first platform according to the job task, where the charging request at least carries the job task identifier; the obtaining module 1002 is used to obtain the charging during the execution of the job task based on the set charging rules. Collect information; the second sending module 1001 is also used to send the charging collection information to the first platform.
  • the charging device for data transactions also includes: a determining module 1003, a second receiving module 1004, and a second verification module 1005.
  • the determining module 1003 is configured to determine the process key based on the set charging rule. first information; the second sending module 1001 is used to send the first information to the first platform; the second receiving module 1004 is used to receive the second information of the process key sent by the first platform;
  • the second verification module 1005 is used to bidirectionally verify the charging collection information based on the process key and the first platform.
  • the second verification module 1005 is specifically used to:
  • the first authentication request carries at least first authentication information.
  • the first authentication information is generated by encrypting at least the accounting collection information based on the process key. of;
  • the second authentication request carries at least second authentication information.
  • the second authentication information is based on the process after the first platform verifies the first authentication information.
  • the key is generated by encrypting at least the billing collection information;
  • the second verification module 1005 is specifically used to:
  • the billing collection information is encrypted and generated;
  • Verify the second authentication information and send a first authentication request to the first platform based on the verification result.
  • the first authentication request carries at least first authentication information.
  • the first authentication information is based on the process.
  • the key is generated by encrypting at least the charging collection information.
  • the job tasks include at least one of the following: a joint modeling task, a joint online reasoning task, and a joint offline reasoning task.
  • the billing collection information includes at least one of the following: information value IV of the data field, number of data fields, data set sample size, data set attributes, calculation engine used, algorithm type used, graphics processing GPU occupancy, central processing unit CPU occupancy, memory occupancy and network bandwidth occupancy.
  • the node device is a first node device serving as a data provider or a second node device serving as a data demander.
  • the second receiving module 1004 is further configured to receive the first request sent by the first platform; the determining module 1003 is further configured to based on the first Request to determine the set charging rules.
  • the second sending module 1001 is also used to send a second request to the first platform; the charging device for data transactions also includes: a connection module 1006. Based on the request response returned by the first platform, establish a connection with each first node device participating in the cooperation.
  • the second sending module 1001, the obtaining module 1002, the determining module 1003, the second receiving module 1004, the second verification module 1005 and the connecting module 1006 can be implemented by the processor in the charging device for data transactions.
  • the processor needs to run computer programs in memory to perform its functions.
  • the charging device for data transactions provided in the above embodiments performs charging for data transactions
  • only the division of the above program modules is used as an example.
  • the above processing can be allocated by Different program modules are completed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the charging device for data transactions provided in the above embodiments and the charging method embodiments for data transactions belong to the same concept. The specific implementation process can be found in the method embodiments and will not be described again here.
  • FIG. 11 only shows an exemplary structure of the first platform but not the entire structure. Part or all of the structure shown in FIG. 11 can be implemented as needed.
  • the first platform 1100 provided by the embodiment of the present disclosure includes: at least one processor 1101, a memory 1102, a user interface 1103, and at least one network interface 1104.
  • the various components in the first platform 1100 are coupled together through a bus system 1105 .
  • the bus system 1105 is used to implement connection communication between these components.
  • the bus system 1105 also includes a power bus, a control bus and a status signal bus.
  • the various buses are labeled as bus system 1105 in FIG. 11 .
  • the user interface 1103 may include a display, keyboard, mouse, trackball, click wheel, keys, buttons, touch pad or touch screen, etc.
  • the memory 1102 in the embodiment of the present disclosure is used to store various types of data to support the operation of the first platform. Examples of such data include: any computer program used to operate on the first platform.
  • the charging method for data transactions disclosed in the embodiment of the present disclosure can be applied to the processor 1101 or implemented by the processor 1101.
  • the processor 1101 may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the data transaction charging method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor 1101 .
  • the above-mentioned processor 1101 may be a general-purpose processor, a digital signal processor (Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the processor 1101 can implement or execute the disclosed methods, steps and logical block diagrams in the embodiments of the present disclosure.
  • a general-purpose processor may be a microprocessor or any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present disclosure can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a storage medium, and the storage medium is located in the memory 1102.
  • the processor 1101 reads the information in the memory 1102, and completes the steps of the charging method for data transactions provided by the embodiment of the present disclosure in conjunction with its hardware.
  • the first platform may be one or more application specific integrated circuits (Application Specific Integrated Circuits, ASICs), digital signal processors (Digital Signal Processors), programmable logic devices (Programmable Logic Devices, PLDs) , Complex Programmable Logic Device (CPLD), field programmable Implemented by a Field Programmable Gate Array (FPGA), a general-purpose processor, a controller, a Micro Controller Unit (MCU), a microprocessor (Microprocessor), or other electronic components for executing the foregoing method.
  • ASICs Application Specific Integrated Circuits
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • PLDs programmable logic devices
  • CPLD Complex Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • FPGA Field Programmable Gate Array
  • controller a Micro Controller Unit
  • MCU Micro Controller Unit
  • Microprocessor Microprocessor
  • FIG. 12 only shows an exemplary structure of the node device but not the entire structure. Part or all of the structure shown in FIG. 12 can be implemented as needed.
  • the node device 1200 provided by the embodiment of the present disclosure includes: at least one processor 1201, a memory 1202, a user interface 1203, and at least one network interface 1204.
  • the various components in node device 1200 are coupled together through bus system 1205 .
  • the bus system 1205 is used to implement connection communication between these components.
  • the bus system 1205 also includes a power bus, a control bus and a status signal bus.
  • the various buses are labeled bus system 1205 in FIG. 12 .
  • the user interface 1203 may include a display, keyboard, mouse, trackball, click wheel, keys, buttons, touch pad or touch screen, etc.
  • the memory 1202 in the embodiment of the present disclosure is used to store various types of data to support the operation of the node device. Examples of this data include: any computer program used to operate on the node device.
  • the charging method for data transactions disclosed in the embodiment of the present disclosure can be applied to the processor 1201 or implemented by the processor 1201.
  • the processor 1201 may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the data transaction charging method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor 1201 .
  • the above-mentioned processor 1201 can be a general-purpose processor, a digital signal processor (Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the processor 1201 can implement or execute the disclosed methods, steps and logical block diagrams in the embodiments of the present disclosure.
  • a general-purpose processor may be a microprocessor or any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present disclosure can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a storage medium, and the storage medium is located in the memory 1202.
  • the processor 1201 reads the information in the memory 1202, and completes the steps of the charging method for data transactions provided by the embodiment of the present disclosure in conjunction with its hardware.
  • node device 1200 may be configured by one or more ASICs, PLDs, CPLDs, FPGA, general processor, controller, MCU, Microprocessor, or other electronic components are implemented for executing the aforementioned method.
  • non-volatile memory can be read-only memory (Read Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory). , EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Magnetic Random Access Memory (Ferromagnetic Random Access Memory, FRAM), Flash Memory, Magnetic Surface Memory , optical disk, or CD-ROM (Compact Disc Read-Only Memory, CD-ROM); the magnetic surface memory can be magnetic disk storage or tape storage.
  • Volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM Random Access Memory
  • SRAM Static Random Access Memory
  • SSRAM Synchronous Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • SDRAM Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM SyncLink Dynamic Random Access Memory
  • DRRAM Direct Rambus Random Access Memory
  • An embodiment of the present disclosure also provides a data sharing service system, including: the first platform described in the embodiment of the present disclosure and at least two node devices described in the embodiment of the present disclosure.
  • the first platform and the node device can be connected through an IP private network to improve the security of data transmission.
  • the at least two node devices include a first node device (ie, DSN) as a data provider and a second node device (ie, DRN) as a data demander.
  • the embodiment of the present disclosure also provides a storage medium, that is, a computer storage medium, which may be a computer-readable storage medium, for example, including a memory 1102 that stores a computer program.
  • the computer program may be configured by the first platform.
  • the processor 1101 executes to complete the steps described in the first platform side method of the embodiment of the present disclosure; as another example, it includes a memory 1202 that stores a computer program.
  • the above computer program can be executed by the processor 1201 of the node device to complete the embodiment of the present disclosure.
  • Computer-readable storage media can be ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM and other memories.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本公开提出了一种数据交易的计费方法、装置、系统及存储介质。其中，该方法包括：第一平台接收至少两个节点设备分别发送的计费请求；基于各计费请求生成计费任务；接收各节点设备发送的计费采集信息，基于计费采集信息执行该计费任务。

Description

数据交易的计费方法、装置、系统及存储介质
相关申请的交叉引用
本申请主张在2022年5月10日在中国提交的中国专利申请号No.202210505641.7的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及数据应用领域，尤其涉及一种数据交易的计费方法、装置、系统及存储介质。
背景技术
随着大数据技术及数字经济的发展，数据要素作为新型的生产要素，受到社会各方的广泛重视，数据要素的流通、计算等数据交易的需求愈来愈普遍。
数据交易的产业涉及数据需求方、数据提供方、数据监管方、数据交易所、技术服务提供方等，数据交易的市场面临数据流通效率低、商业模式粗放、数据安全性要求高等主要问题。
相关技术中，数据交易发展碎片化、各自为政、良莠不齐，影响数据要素市场未来的规模化发展。以政府为主导的大数据交易所由于缺少利益驱动、缺乏数据、市场化运营的经验不足等原因，往往发展缓慢、甚至停滞。由于缺乏公共的服务设施，机构和/或企业之间需采用点到点的连接和数据合作，且多采用合同制。连接成本高，安全可靠性无保障，机构运营维护及技术实现成本高，从而也将提升数据业务发展的成本。受限于合同制的点到点的数据交易模式，数据要素生产及数据要素的流通效率低下。
发明内容
有鉴于此，本公开实施例提供了一种数据交易的计费方法、装置、系统及存储介质，旨在满足多方数据交易的需求。
本公开实施例的技术方案是这样实现的：
第一方面，本公开实施例提供了一种数据交易的计费方法，应用于第一平台，该方法包括：
接收至少两个节点设备分别发送的计费请求，所述计费请求至少携带作业任务标识；
基于各所述计费请求生成计费任务；
接收各所述节点设备发送的计费采集信息；
基于所述计费采集信息执行所述计费任务。
上述方案中，所述基于所述计费采集信息执行所述计费任务之前，所述方法还包括：
接收各所述节点设备发送的确定过程密钥的第一信息；
向各所述节点设备基于所述第一信息发送确定所述过程密钥的第二信息；
基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息。
上述方案中，所述基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息，包括：
接收所述节点设备发送的第一认证请求，所述第一认证请求至少携带第一认证信息，所述第一认证信息为所述节点设备基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第一认证信息进行验证，并基于验证结果发送第二认证请求给所述节点设备，所述第二认证请求至少携带第二认证信息，所述第二认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
接收所述节点设备返回的对所述第二认证信息进行验证的验证结果。
上述方案中，所述基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息，包括：
发送第二认证请求给所述节点设备，所述第二认证请求至少携带第二认证信息，所述第二认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
接收所述节点设备发送的第一认证请求，所述第一认证请求至少携带第一认证信息，所述第一认证信息为所述节点设备验证所述第二认证信息后基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第一认证信息进行验证，生成验证结果。
上述方案中，所述计费采集信息为所述至少两个节点设备执行作业任务过程中生成的，所述作业任务包括以下至少之一：联合建模任务、联合在线推理任务和联合离线推理任务。
上述方案中，所述计费采集信息包括以下至少之一：数据字段的信息值IV、数据字段数量、数据集样本量、数据集属性、使用的计算引擎、使用的算法类型、图形处理器GPU占用率、中央处理器CPU占用率、内存占用率和网络带宽占用率。
上述方案中，基于所述计费采集信息执行所述计费任务，包括：
基于验证后的所述计费采集信息生成计费账单；
对所述计费账单进行在线扣费或者离线扣费。
第二方面，本公开实施例提供了一种数据交易的计费方法，应用于节点设备，所述方法包括：
根据作业任务发送计费请求给第一平台，所述计费请求至少携带作业任务标识；
基于设定计费规则获取执行作业任务过程中的计费采集信息；
发送所述计费采集信息给所述第一平台。
上述方案中，所述方法还包括：
基于所述设定计费规则确定过程密钥的第一信息；
发送所述第一信息给所述第一平台；
接收所述第一平台发送的所述过程密钥的第二信息；
基于所述过程密钥与所述第一平台双向验证所述计费采集信息。
上述方案中，所述基于所述过程密钥与所述第一平台双向验证所述计费采集信息，包括：
发送第一认证请求给所述第一平台，所述第一认证请求至少携带第一认证信息，所述第一认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
接收所述第一平台发送的第二认证请求，所述第二认证请求至少携带第二认证信息，所述第二认证信息为所述第一平台验证所述第一认证信息后基 于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第二认证信息进行验证，并返回验证结果给所述第一平台。
上述方案中，所述基于所述过程密钥与所述第一平台双向验证所述计费采集信息，包括：
接收所述第一平台发送的第二认证请求，所述第二认证请求至少携带第二认证信息，所述第二认证信息为所述第一平台基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第二认证信息进行验证，并基于验证结果发送第一认证请求给所述第一平台，所述第一认证请求至少携带第一认证信息，所述第一认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的。
上述方案中，所述作业任务包括以下至少之一：联合建模任务、联合在线推理任务和联合离线推理任务。
上述方案中，所述计费采集信息包括以下至少之一：数据字段的信息值IV、数据字段数量、数据集样本量、数据集属性、使用的计算引擎、使用的算法类型、图形处理器GPU占用率、中央处理器CPU占用率、内存占用率和网络带宽占用率。
上述方案中，所述节点设备为作为数据提供方的第一节点设备或者作为数据需求方的第二节点设备。
上述方案中，若所述节点设备为所述第一节点设备，所述方法还包括：
接收所述第一平台发送的第一请求；
基于所述第一请求确定所述设定计费规则。
上述方案中，若所述节点设备为所述第二节点设备，所述方法还包括：
发送第二请求给所述第一平台；
基于所述第一平台返回的请求响应，与参与合作的各第一节点设备建立连接。
第三方面，本公开实施例提供了一种数据交易的计费装置，应用于第一平台，所述装置包括：
接收模块，用于接收至少两个节点设备分别发送的计费请求，所述计费请求至少携带作业任务标识；
任务生成模块，用于基于各所述计费请求生成计费任务；
所述接收模块还用于接收各所述节点设备发送的计费采集信息；
任务执行模块，用于基于所述计费采集信息执行所述计费任务。
第四方面，本公开实施例提供了一种数据交易的计费装置，应用于节点设备，所述装置包括：
发送模块，用于根据作业任务发送计费请求给第一平台，所述计费请求至少携带作业任务标识；
获取模块，用于基于设定计费规则获取执行作业任务过程中的计费采集信息；
所述发送模块还用于发送所述计费采集信息给所述第一平台。
第五方面，本公开实施例提供了一种第一平台，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器，用于运行计算机程序时，执行本公开实施例第一方面所述方法的步骤。
第六方面，本公开实施例提供了一种节点设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器，用于运行计算机程序时，执行本公开实施例第二方面所述方法的步骤。
第七方面，本公开实施例提供了一种数据共享服务系统，包括：本公开实施例第五方面所述的第一平台和至少两个本公开实施例第六方面所述的节点设备。
第八方面，本公开实施例提供了一种存储介质，所述存储介质上存储有计算机程序，所述计算机程序被处理器执行时，实现本公开实施例任一所述方法的步骤。
本公开实施例提供的技术方案，第一平台接收至少两个节点设备分别发送的计费请求；基于各计费请求生成计费任务；接收各节点设备发送的计费采集信息，基于计费采集信息执行该计费任务；如此，可以基于数据交易多方的计费采集信息进行计费，能够满足多方数据交易的需求，可以有效提升数据交易的流通效率。
附图说明
图1为本公开实施例数据共享服务系统的结构示意图；
图2为本公开一实施例数据交易的计费方法的流程示意图；
图3为本公开另一实施例数据交易的计费方法的流程示意图；
图4为本公开又一实施例数据交易的计费方法的流程示意图；
图5为本公开应用实施例的系统架构示意图；
图6为本公开应用实施例中“入网连接和计算环境准备”的流程示意图；
图7为本公开应用实施例中“联合建模”的流程示意图；
图8为本公开应用实施例中“联合推理”的流程示意图；
图9为本公开一实施例数据交易的计费装置的结构示意图；
图10为本公开另一实施例数据交易的计费装置的结构示意图；
图11为本公开实施例第一平台的结构示意图；
图12为本公开实施例节点设备的结构示意图。
具体实施方式
下面结合附图及实施例对本公开再作进一步详细的描述。
除非另有定义，本文所使用的所有的技术和科学术语与属于本公开的技术领域的技术人员通常理解的含义相同。本文中在本公开的说明书中所使用的术语只是为了描述具体的实施例的目的，不是旨在于限制本公开。
在对本公开实施例数据交易的计费方法进行说明之前，先对应用本公开实施例数据交易的计费方法的系统说明如下：
本公开实施例提供了一种数据共享服务系统，用于实现多方之间数据的线上流通，而不局限于传统的点到点的数据交易，进而提高数据要素的生产及流通效率。该系统又可以称为数据共享服务网络(Data Sharing Service Network，DSSN)系统。如图1所示，该系统包括：第一平台，即图1所示的数据共享服务平台(Data Sharing Service Platform，DSSP)和多个节点设备(又称为数据服务节点)，其中，第一平台也可以是数据共享平台(Data Sharing platform，DSP)；根据角色不同，节点设备又分为作为数据提供方的第一节点设备和作为数据需求方的第二节点设备。如图1所示，第一节点设备又可以称为数据提供方节点(Data Service Node，DSN)，第二节点设备又 可以称为数据需求方节点(Data Requirement Node，DRN)。DSSP/DSP和各节点设备之间可以通过互联网协议(Internet Protocol，IP)专网连接，以提升数据传递的安全性。
示例性地，第一平台主要负责节点管理、数据目录管理、数据流通管理、计费管理、数据交易管理、安全合规管理、DSSN运营管理等；第一节点设备主要负责共享数据的对接、网络接入、数据安全计算、交易处理等；第二节点设备主要负责数据需求方的网络接入、数据服务请求处理、数据安全计算等。
本公开实施例提供了一种数据交易的计费方法，应用于前述的第一平台，如图2所示，该方法包括：
步骤201，接收至少两个节点设备分别发送的计费请求，所述计费请求至少携带作业任务标识。
需要说明的是，本公开实施例的数据交易不同于传统的点对点的数据合作模式，往往会涉及多个交易方联合进行数据流通，例如，基于联邦学习或者多方安全计算等隐私计算技术提供数据的数据交易，数据需求方则需要与多个数据提供方建立连接，实现数据交易。换言之，一个数据交易会涉及多个节点设备的作业任务，数据需求方基于第一平台创建数据交易的项目后，可以向各节点设备分配作业任务，各节点设备在启动相应的作业任务后，可以发送携带作业任务标识的计费请求给第一平台。
步骤202，基于各所述计费请求生成计费任务。
这里，第一平台在接收到作为参与方的各节点设备发送的计费请求后，基于各节点设备的作业任务标识，生成该项目的计费任务。
示例性地，该计费任务可以理解为针对数据交易的项目的各作业任务，基于计费规则构建计费账单，例如，可以对各作业任务的子账单分配权重值，并基于各子账单加权求和的结果得到总的计费账单。
步骤203，接收各所述节点设备发送的计费采集信息。
示例性地，各节点设备可以在本地基于设定计费规则获取执行作业任务过程中的计费采集信息，并将计费采集信息发送给第一平台。
步骤204，基于所述计费采集信息执行所述计费任务。
示例性地，第一平台基于各节点设备的计费采集信息生成各作业任务的计费子账单，并基于各作业任务的计费子账单生成总的计费账单。
可以理解的是，本公开实施例的第一平台接收至少两个节点设备分别发送的计费请求；基于各计费请求生成计费任务；接收各节点设备发送的计费采集信息，基于计费采集信息执行该计费任务，可以基于数据交易多方的计费采集信息进行计费，能够满足多方数据交易的需求，可以有效提升数据交易的流通效率。
为了有效防止第一平台接收的来自各节点设备的计费采集信息被篡改，在一些实施例中，所述基于所述计费采集信息执行所述计费任务之前，所述方法还包括：
接收各所述节点设备发送的确定过程密钥的第一信息；
向各所述节点设备基于所述第一信息发送确定所述过程密钥的第二信息；
基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息。
示例性地，节点设备发送的第一信息可以由前述的计费请求携带或者由节点设备单独发送，本公开实施例对此不做限定。在一示例中，该第一信息可以为与作业任务标识对应的密钥索引号；该第二信息可以包括密钥版本号和密钥算法标识；本公开实施例的过程密钥可以第一平台或者节点设备侧的密钥管理模块基于第一信息和第二信息生成，即第一平台的密钥管理模块可以基于第一信息和第二信息生成过程密钥，节点设备的密钥管理模块也可以基于第一信息和第二信息生成过程密钥。
在一实施例中，所述基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息，包括：
接收所述节点设备发送的第一认证请求，所述第一认证请求至少携带第一认证信息，所述第一认证信息为所述节点设备基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第一认证信息进行验证，并基于验证结果发送第二认证请求给所述节点设备，所述第二认证请求至少携带第二认证信息，所述第二认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
接收所述节点设备返回的对所述第二认证信息进行验证的验证结果。
可以理解的是，节点设备接收到第一平台发送的第二信息后，可以由节点设备侧的密钥管理模块基于第一信息和第二信息生成过程密钥，并基于该过程密钥对执行作业任务过程中获取的计费采集信息进行加密处理，生成第一认证信息，并发送携带该第一认证信息的第一认证请求给第一平台。示例性地，第一认证请求还携带节点设备的节点标识和/或交易时间等信息。
第一平台可以基于来自节点设备的第一信息确定对应的第二信息，并由第一平台侧的密钥管理模块基于第一信息和第二信息生成过程密钥，基于该过程密钥对第一认证信息进行验证，并在验证通过后基于过程密钥对至少所述计费采集信息进行加密处理，生成第二认证信息并发送携带该第二认证信息的第二认证请求给节点设备，节点设备基于过程密钥对该第二认证信息进行验证，例如，可以基于过程密钥对本地的计费采集信息进行加密，并将加密后的数据与第二认证信息进行比较得到验证结果，返回验证结果给第一平台。
在另一实施例中，所述基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息，包括：
发送第二认证请求给所述节点设备，所述第二认证请求至少携带第二认证信息，所述第二认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
接收所述节点设备发送的第一认证请求，所述第一认证请求至少携带第一认证信息，所述第一认证信息为所述节点设备验证所述第二认证信息后基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第一认证信息进行验证，生成验证结果。
可以理解的是，第一平台可以基于来自节点设备的第一信息确定对应的第二信息，并由第一平台侧的密钥管理模块基于第一信息和第二信息生成过程密钥，基于该过程密钥对来自节点设备的计费采集信息进行加密处理，生成第二认证信息，发送携带第二认证信息的第二认证请求给节点设备，节点设备可以基于来自第一平台的第二信息，由节点设备侧的密钥管理模块基于第一信息和第二信息生成过程密钥，基于过程密钥对该第二认证信息进行验证，例如，可以基于过程密钥对本地的计费采集信息进行加密，并将加密后 的数据与第二认证信息进行比较得到验证结果。
节点设备可以该第二认证信息验证通过后，基于过程密钥对计费采集信息进行加密处理，生成第一认证信息，并发送携带该第一认证信息的第一认证请求给第一平台。第一平台可以基于过程密钥对第一认证信息进行验证，进而实现对计费采集信息的双向验证。
示例性地，所述计费采集信息为所述至少两个节点设备执行作业任务过程中生成的，所述作业任务包括以下至少之一：联合建模任务、联合在线推理任务和联合离线推理任务。
这里，联合建模任务可以理解为给前述的数据交易的项目基于指定的计算引擎和算法等构建计算模型。联合在线推理任务可以理解为在线执行数据交易。联合离线推理可以理解为离线执行数据交易。
相关技术中，在数据交易过程中，往往按照应用程序接口(Application Programming Interface，API)调用次数收费或者按照数据量大小来收费。然而在本公开实施例的多方合作的数据交易过程中，涉及对原始数据的加密、计算，从而形成高价值的数据要素，在该过程中，一方面，对计算引擎、算法的选择直接影响模型训练和数据安全计算效果，另一方面计算资源的保障能够提升数据要素产生的效率，对数据流通交易收益产生正向影响。
基于此，本公开实施例中，所述计费采集信息包括以下至少之一：数据字段的信息值(Information Value，IV)、数据字段数量、数据集样本量、数据集属性、使用的计算引擎、使用的算法类型、图形处理器(Graphics Processing Unit，GPU)占用率、中央处理器(Central Processing Unit，CPU)占用率、内存占用率和网络带宽占用率。如此，可以基于多维度的计费采集信息，使得本公开实施例的计费方法综合考虑了数据交易过程中的影响数据要素生产的多种因素，能够最大化发挥数据价值，精细化地促进数据交易的流通效率。
示例性地，基于所述计费采集信息执行所述计费任务，包括：
基于验证后的所述计费采集信息生成计费账单；
对所述计费账单进行在线扣费或者离线扣费。
示例性地，第一平台可以基于通过双向验证后的各节点设备的计费采集信息，生成各作业任务的计费子账单，并基于各作业任务的计费子账单，生 成总的计费账单，对该计费账单进行在线扣费或者离线扣费，完成计费管理。
本公开实施例还提供了一种数据交易的计费方法，应用于前述的节点设备，如图3所示，该方法包括：
步骤301，根据作业任务发送计费请求给第一平台，所述计费请求至少携带作业任务标识。
本公开实施例中，节点设备接收第一平台基于创建的数据交易的项目分配的作业任务，启动作业任务后，可以发送携带作业任务标识的计费请求给第一平台。
步骤302，基于设定计费规则获取执行作业任务过程中的计费采集信息。
这里，节点设备可以响应于启动作业任务，基于设定计费规则获取执行作业任务过程中的计费采集信息。
示例性地，节点设备可以基于计费触发模块监听是否启动作业任务，若是，则触发计费采集模块获取执行作业任务过程中的计费采集信息。示例性地，设定计费规则可以由第一平台分配作业任务时指示，使得节点设备可以基于指示的设定计费规则获取相应的计费采集信息。
步骤303，发送所述计费采集信息给所述第一平台。
示例性地，节点设备可以在作业任务执行完毕后，发送计费采集信息给第一平台，或者周期性地发送计费采集信息给第一平台，或者基于设定时长发送计费采集信息给第一平台，本公开实施例对此不做限定。
可以理解的是，本公开实施例的数据交易不同于传统的点对点的数据合作模式，往往会涉及多个交易方联合进行数据流通，例如，基于联邦学习或者多方安全计算等隐私计算技术提供数据的数据交易，数据需求方则需要与多个数据提供方建立连接，实现数据交易。第一平台基于参与数据交易的各节点设备发送的计费请求生成计费任务，并基于各节点设备发送的计费采集信息执行计费任务，如此，可以基于数据交易多方的计费采集信息进行计费，能够满足多方数据交易的需求，可以有效提升数据交易的流通效率。
示例性地，所述方法还包括：
基于所述设定计费规则确定过程密钥的第一信息；
发送所述第一信息给所述第一平台；
接收所述第一平台发送的所述过程密钥的第二信息；
基于所述过程密钥与所述第一平台双向验证所述计费采集信息。
这里，节点设备的密钥管理模块可以对做作业任务基于设定计费规则及密钥分散级别分配相应的密钥索引，即确定过程密钥的第一信息。
这里，第一平台可以基于作业任务标识确定过程密钥的第二信息，例如，确定过程密钥的密钥版本号和密钥算法标识。
本公开实施例的过程密钥可以由第一平台或者节点设备侧的密钥管理模块基于第一信息和第二信息生成，即第一平台的密钥管理模块可以基于第一信息和第二信息生成过程密钥，节点设备的密钥管理模块也可以基于第一信息和第二信息生成过程密钥。
在一实施例中，所述基于所述过程密钥与所述第一平台双向验证所述计费采集信息，包括：
发送第一认证请求给所述第一平台，所述第一认证请求至少携带第一认证信息，所述第一认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
接收所述第一平台发送的第二认证请求，所述第二认证请求至少携带第二认证信息，所述第二认证信息为所述第一平台验证所述第一认证信息后基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第二认证信息进行验证，并返回验证结果给所述第一平台。
可以理解的是，节点设备接收到第一平台发送的第二信息后，可以由节点设备侧的密钥管理模块基于第一信息和第二信息生成过程密钥，并基于该过程密钥对执行作业任务过程中获取的计费采集信息进行加密处理，生成第一认证信息，并发送携带该第一认证信息的第一认证请求给第一平台。示例性地，第一认证请求还携带节点设备的节点标识和/或交易时间等信息。
第一平台可以基于来自节点设备的第一信息确定对应的第二信息，并由第一平台侧的密钥管理模块基于第一信息和第二信息生成过程密钥，基于该过程密钥对第一认证信息进行验证，并在验证通过后基于过程密钥对至少所述计费采集信息进行加密处理，生成第二认证信息并发送携带该第二认证信息的第二认证请求给节点设备，节点设备基于过程密钥对该第二认证信息进 行验证，例如，可以基于过程密钥对本地的计费采集信息进行加密，并将加密后的数据与第二认证信息进行比较得到验证结果，返回验证结果给第一平台。
在另一实施例中，所述基于所述过程密钥与所述第一平台双向验证所述计费采集信息，包括：
接收所述第一平台发送的第二认证请求，所述第二认证请求至少携带第二认证信息，所述第二认证信息为所述第一平台基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第二认证信息进行验证，并基于验证结果发送第一认证请求给所述第一平台，所述第一认证请求至少携带第一认证信息，所述第一认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的。
可以理解的是，第一平台可以基于来自节点设备的第一信息确定对应的第二信息，并由第一平台侧的密钥管理模块基于第一信息和第二信息生成过程密钥，基于该过程密钥对来自节点设备的计费采集信息进行加密处理，生成第二认证信息，发送携带第二认证信息的第二认证请求给节点设备，节点设备可以基于来自第一平台的第二信息，由节点设备侧的密钥管理模块基于第一信息和第二信息生成过程密钥，基于过程密钥对该第二认证信息进行验证，例如，可以基于过程密钥对本地的计费采集信息进行加密，并将加密后的数据与第二认证信息进行比较得到验证结果。
节点设备可以该第二认证信息验证通过后，基于过程密钥对计费采集信息进行加密处理，生成第一认证信息，并发送携带该第一认证信息的第一认证请求给第一平台。第一平台可以基于过程密钥对第一认证信息进行验证，进而实现对计费采集信息的双向验证。
示例性地，所述作业任务包括以下至少之一：联合建模任务、联合在线推理任务和联合离线推理任务。
示例性地，所述计费采集信息包括以下至少之一：数据字段的信息值IV、数据字段数量、数据集样本量、数据集属性、使用的计算引擎、使用的算法类型、图形处理器GPU占用率、中央处理器CPU占用率、内存占用率和网络带宽占用率。如此，可以基于多维度的计费采集信息，使得本公开实施例 的计费方法综合考虑了数据交易过程中的影响数据要素生产的多种因素，能够最大化发挥数据价值，精细化地促进数据交易的流通效率。
示例性地，所述节点设备为作为数据提供方的第一节点设备或者作为数据需求方的第二节点设备。可以理解的是，本公开实施例的多个节点设备包括作为数据提供方的第一节点设备和作为数据需求方的第二节点设备。
示例性地，若所述节点设备为所述第一节点设备，所述方法还包括：
接收所述第一平台发送的第一请求；
基于所述第一请求确定所述设定计费规则。
这里，第一请求可以理解为第一平台发送给节点设备的指示信息，用于节点设备创建作业任务。示例性地，该指示信息可以包括：目标节点标识、参与合作的其他节点标识、合作内容、计算引擎、数据字段、算法、是否支持GPU/CPU运算、计费规则等，其中，计费规则可以明确计费采集信息的维度、各维度的权重及每个维度的定价信息等。
示例性地，若所述节点设备为所述第二节点设备，所述方法还包括：
发送第二请求给所述第一平台；
基于所述第一平台返回的请求响应，与参与合作的各第一节点设备建立连接。
这里，第二请求可以理解为第二节点设备发送的请求创建数据交易的项目的创建请求，第一平台可以基于该第二请求发送第一请求给各第一节点设备。
示例性地，第二请求可以包括以下至少之一：合作方、合作内容、计费方式、计费规则、计算引擎、算法、数据字段、是否支持GPU/CPU计算等。
示例性地，第一平台基于第二请求向需要合作的各第一节点设备发送第一请求后，接收各节点设备返回的确认信息，并基于各节点设备的确认信息向第二节点设备返回请求响应，即指示数据交易的项目已成功建立，第二节点设备基于该请求响应，与参与合作的各第一节点设备建立连接。
图4示出了本公开实施例应用于数据共享服务系统的数据交易的计费方法，参照图4，该数据共享服务系统包括：DSSP/DSP、作为数据提供方的DSN和作为数据需求方的DRN，该方法包括：
步骤401，配置作业信息，并启动作业任务。
这里，参与合作的各节点设备配置作业信息并启动作业任务，其中，配置作业信息包括：安装执行作业任务所需的算法和/或算法引擎，获取相关的数据源等。
步骤402，发送计费请求。
这里，各节点设备发送计费请求给DSSP/DSP，该计费请求携带作业任务标识。
步骤403，生成计费任务。
这里，DSSP/DSP在接收到作为参与方的各节点设备发送的计费请求后，基于各节点设备的作业任务标识，生成该项目的计费任务。
步骤404，根据计费规则采集数据，同步计费采集信息。
这里，各节点设备可以在本地基于设定计费规则获取执行作业任务过程中的计费采集信息，并将计费采集信息发送给DSSP/DSP。
步骤405，作业任务结束。
各节点设备执行完作业任务后，发送指示作业结束的信息给DSSP/DSP，DSSP/DSP基于各参与方指示作业结束的信息确定项目的作业任务结束。
步骤406，执行计费任务，更新账户余额。
这里，DSSP/DSP基于各节点设备的计费采集信息生成各作业任务的计费子账单，并基于各作业任务的计费子账单生成总的计费账单，更新账户余额。
下面结合应用实施例对本公开再作进一步详细的描述。
本应用实施例的系统架构如图5所示，DSSP包括管理功能区(DSS-M)、交易功能区(DSS-T)和服务开放功能区(DSS-S)三大部分。
示例性地，管理功能区包括：网络连接管理、引擎管理、合同执行管理、运营管理和安全管理。其中，网络连接管理包括节点设备的节点注册、鉴权、配置管理、节点互联、节点状态监控等；引擎管理包括计算引擎的上架申请、上架审核、引擎下载管理及版本维护等，支持异构引擎的加载管理，从而对外屏蔽异构引擎，统一服务，实现引擎层面的互联互通；合同执行管理包括合同上载、项目创建、项目下发、任务监控、计量统计等；运营管理包括用 户管理、运营分析、运维监控等；安全管理包括系统安全、业务安全、容器安全、密钥管理等。
示例性地，交易功能区包括：数据发布、交易服务、计费管理和交易监督。其中，数据发布包括数据目录登记、数据目录审核、数据目录查询、数据目录确权等；交易服务包括交易门户、数据价值评估、交易撮合、合同签约、交易存证、交易订单管理、支付服务等；交易监管包括合规监管、安全监管、信用监管等；
示例性地，服务开放功能区用于安装开放服务层级，包括平台即服务(Platform-as-a-Service，PaaS)服务开放(例如，数据模型开发工具、测试环境、合规审核、发布上线等能力开放)、软件即服务(Software-as-a-service，SaaS)服务开放(例如，面向行业提供的业务，黑名单查询等)和数据即服务(Data-as-a-service，DaaS)服务开放三部分(例如，面向行业提供的数据产品服务，比如企业信用评估模型等)。
如图5所示，示例性地，节点设备包括用户管理、认证鉴权、数据目录、连接管理、安全管理、项目管理、任务管理、引擎管理、密钥管理、模型管理、日志管理、系统监控、计费管理、计算引擎、数据安全域等功能模块。需要说明的是，节点设备可以根据不同的客户群体(数据需求方、数据提供方)提供不同的功能界面。
本应用实施例的计费方法涉及前述的节点设备侧的计费管理模块、计算引擎模块和DSSP/DSP侧的计费管理。
DSSP/DSP侧的计费管理支持在线计费和离线计费两种计费模式。该计费管理主要涉及融合计费网关、账户余额管理模块、批价管理模块、离线计费网关模块和计费系统模块。节点设备侧的计费管理模块包括计费触发模块，节点设备侧的计算引擎模块包括计费采集模块。
下面对上述各模块解释说明如下：
计费采集模块，位于节点设备各计算引擎内，根据具体计费商务模式，负责采集并监控客户在数据交易任务中的数据、计算引擎、算法、计算资源等使用用量信息，即计费采集信息。由于在数据流通交易过程中，涉及对原始数据的加密、计算，从而形成高价值的数据要素，因此一方面对计算引擎、 算法的选择直接影响模型训练和数据安全计算效果，另一方面计算资源的保障能够提升数据要素产生的效率，对数据流通交易收益产生正向影响。本应用实施例将影响数据流通交易收益的关键因素作为计费采集点，从而可以形成多维度的计费采集信息。
示例性地，计费采集信息包括但不限于数据字段的IV、数据字段数量、数据样本量、数据集属性(训练数据、测试数据、推理数据)、使用过的计算引擎、使用的算法、GPU占用率、CPU占用率、内存占用率、网络带宽占用率等。
计费触发模块，位于节点设备的计费管理模块，负责检测客户在该服务节点是否发起数据交易任务，从而触发计费功能。
密钥管理模块，位于节点设备，负责存储密钥及加密交易过程数据。其中密钥按照计费规则不同(离线、在线)及密钥分散级别不同建立密钥索引。
融合计费网关，负责将DSSP/DSP的各计费功能模块与节点设备的计费触发模块对接，根据采集到的多维度计费采集信息，生成融合计费账单，将离线账单提供给离线计费网关模块，对于在线计费账单，实时收集计费信息，完成账单扣费功能，并计算业务配额(即业务可用量)，将计算结果提供给计费触发模块。
账户余额管理模块，属于在线计费功能部分，负责存储并更新客户账户余额。
批价管理模块，属于在线计费功能部分，负责根据数据要素定价策略确定使用数据交易服务的费用。
离线计费网关模块，属于离线计费功能部分，负责计费账单的错误检查、预处理和存储，收集交易计费账单并发送给计费系统模块。
计费系统模块，通过该系统向客户收取数据交易服务的费用。
本应用实施例的数据交易主要涉及以下三个阶段：
1)、入网连接和计算环境准备；
2)、联合建模；
3)、联合推理。
下面分别对上述的阶段1)至阶段3)进行详细说明。
参照图6，上述阶段1)包括以下步骤：
步骤601，节点注册，网络接入。
示例性地，数据需求方和数据提供方将各自的数据服务节点注册至DSSN网络，数据服务节点激活上线，DSSP/DSP可以查看到已激活的所有节点设备。
步骤602，创建数据目录，上传样例数据集。
示例性地，数据提供方在第一节点设备创建数据目录，包括数据字段名称、数据量、数据定价、数据存储位置、数据来源、适用行业、数据敏感级别、数据目录可见权限等，并上传样例数据集，发送至DSSP/DSP进行审核。
步骤603，审核发布数据目录。
示例性地，平台运营人员或者数据审核员在DSSP/DSP审核数据目录及样例数据集(审核内容包括数据目录、数据测试集的合法合规性、完整性等)，审核通过后发布数据目录，DSSP/DSP根据可见权限展示数据目录。
步骤604，请求创建项目及应用。
示例性地，作为数据需求方的第二节点设备请求创建数据交易的项目，即发送前述的第二请求给DSSP/DSP，该第二请求可以明确合作方、合作内容、计费方式、计费规则、计算引擎、算法、数据字段、是否支持GPU/CPU计算等，DSSP/DSP可以根据第二请求分别创建应用(该应用用于执行作业任务)，各应用的指示信息(即前述的第一请求)可以包括：节点标识(Identifier，ID)、参与合作的其他节点ID、合作内容、计算引擎、数据字段、算法、是否支持GPU/CPU运算、计算规则等，其中，计费规则可以明确计费采集信息的维度、各维度的权重及每个维度的定价信息等。
步骤605，转发项目及应用。
DSSP/DSP审核项目及应用，例如，审核记录计费方式及计费规则，并转发项目及应用至参与合作的节点设备，即向节点设备发送第一请求。
步骤606，审核确认项目及应用。
示例性地，参与合作的节点设备审核确认项目及应用，存储计费方式、计费规则(需要采集的计费信息通知计费采集模块)，返回确认信息至DSSP/DSP。
步骤607，返回创建成功的响应消息。
示例性地，DSSP/DSP返回创建成功的响应消息至需求方服务节点(即第二节点设备)，该响应消息携带合作的数据提供方的节点ID。
步骤608，服务节点间建立连接。
这里，所有参与合作的节点设备之间建立连接。
步骤609，下载并安装算法及计算引擎。
这里，所有参与合作的节点设备根据项目约定信息从DSSP/DSP下载安装计算引擎和算法，完成连接及计算环境准备工作。
参照图7，上述阶段2)包括以下步骤：
步骤701，请求数据授权。
示例性地，所有参与合作的各数据服务节点向DSSP/DSP请求数据授权，例如向DSSP/DSP发送携带以下至少之一：节点ID、数据目录ID、项目ID、应用ID和计算引擎ID的用于数据授权的请求。
步骤702，返回授权响应。
示例性地，DSSP/DSP完成数据授权的审核，返回数据授权响应，该数据授权响应可以携带节点ID、项目ID及应用ID。
步骤703，创建训练作业任务。
示例性地，数据需求方的服务节点创建训练作业任务，发送携带作业任务ID的请求至各参与合作的数据提供方服务节点。
步骤704，作业准备完成。
示例性地，各数据提供方服务节点返回作业准备完成的指示信息给数据需求方的服务节点。
步骤705，作业任务执行，触发计费功能。
示例性地，数据需求方及各数据提供方服务节点执行作业，计费触发模块监听作业任务执行，触发计费功能。
步骤706，发送计费请求。
示例性地，各参与合作的数据服务节点发送计费请求至DSSP/DSP。本公开实施例中，各数据服务节点的计费触发模块向密钥管理模块查询密钥索引，发送计费请求至融合计费网关，该计费请求可以携带节点ID、项目ID、 应用ID、作业任务ID、计费采集信息和密钥索引号(即前述的第一信息)。
可以理解的是，各数据服务节点的计费采集模块可以在作业任务执行过程中采集相关的数据，得到计费采集信息，例如，计费采集信息包括但不限于数据字段的IV、数据字段数量、数据样本量、数据集属性(训练数据、测试数据、推理数据)、使用过的计算引擎、使用的算法、GPU占用率、CPU占用率、内存占用率、网络带宽占用率等。
步骤707，生成计费任务。
示例性地，DSSP/DSP的融合计费网关可以根据计费方式和计费规则生成各服务节点的计费账单。
步骤708，返回计费响应。
示例性地，DSSP/DSP可以返回计费响应至各数据服务节点，该计费响应可以携带数据需求方计费账户ID、作业任务ID、计费标识(在线/离线)、业务配额、在线/离线计费密钥版本号、在线/离线计费密钥算法标识。
步骤709，基于过程密钥生成报文认证码(Message Authentication Code，MAC)1。
示例性地，各参与合作的数据服务节点的密钥管理模块可以基于前述的密钥索引号、密钥版本号和密钥算法标识生成过程密钥，计费触发模块基于该过程密钥对节点ID、项目ID、应用ID、作业任务ID、交易日期、交易时间、计费采集信息等加密生成报文认证码MAC1(即前述的第一认证信息)。
步骤710，发送第一认证请求。
示例性地，参与合作的数据服务节点发送携带MAC1的第一认证请求至DSSP/DSP。该第一认证请求还可以携带节点ID、交易日期及交易时间等。
步骤711，校验MAC1，基于过程密钥对计费采集信息加密计算，生成报文认证码MAC2。
这里，第一平台侧的密钥管理模块可以生成过程密钥，并利于该过程密钥校验MAC1，得到数据服务节点发送的计费采集信息，并基于过程密钥对计费采集信息加密计算，生成报文认证码MAC2(即前述的第二认证信息)。
步骤712，返回第二认证请求。
示例性地，DSSP/DSP向参与合作的数据服务节点发送第二认证请求， 该第二认证请求至少携带报文认证码MAC2。
步骤713，校验MAC2
参与合作的数据服务节点基于过程密钥校验MAC2，例如，可以基于过程密钥对本地的计费采集信息进行加密，并将加密后的数据与MAC2进行比较得到验证结果。
步骤714，作业任务完成，验证结果通知。
参与合作的数据服务节点的作业任务执行完成，模型训练完成，发送验证结果通知至DSSP/DSP。
步骤715，完成扣费/更新计费账单、更新业务配额。
示例性地，DSSP/DSP的融合计费网关汇总各参与合作的数据服务节点计费账单，更新账单金额，并完成扣费及更新业务配额。
步骤716，模型部署至运行环境。
示例性地，可以将训练好的模型部署至运行环境。
需要说明的是，本应用实施例中，各数据服务节点基于密钥管理模块在其内部用过程密钥对节点ID、项目、应用ID、作业任务ID、交易日期、交易时间、计费采集信息等加密得到报文认证码MAC1，将MAC1传送至第一平台，可以避免相关的信息被泄露，且第一平台基于密钥管理模块生成过程密钥对该MAC1进行校验，DSSP/DSP基于过程密钥对计费采集信息加密计算生成报文认证码MAC2，并发送MAC2给数据服务节点进行校验，整个双向校验过程中，数据采集信息等均处于加密状态，可以有效防止泄露或者篡改，提高了计费过程的安全性。示例性地，若双向校验成功，则数据服务节点可以通知DSSP/DSP完成扣费，更新业务配额。
参照图8，上述阶段3)可以分为在线推理和离线推理两种方式。
如图8所示，在线推理可以包括以下步骤：
步骤801a，发起推理请求。
示例性地，需求方的业务系统发起推理请求。
步骤802a，创建模型推理作业任务。
示例性地，数据需求方的数据服务节点创建模型推理作业任务，发送携带作业任务ID的任务信息至各合作的数据提供方的数据服务节点。
步骤803a，作业准备完成。
示例性地，参与合作的数据提供方的数据服务节点在作业准备完成后，返回指示准备完成的信息给数据需求方的数据服务节点。
步骤804a，作业任务执行及计费流程。
示例性地，参与合作的各数据服务节点进入作业任务执行及计费流程，相关的计费流程可以参照图7的步骤705至步骤715，在此不再赘述。
步骤805a，返回推理结果。
示例性地，各数据提供方的数据服务节点返回模型推理结果至数据需求方的数据服务节点。
步骤806a，汇总推理结果。
示例性地，数据需求方的数据服务节点汇总模型推理结果。
步骤807a，返回推理结果。
示例性地，数据需求方的数据服务节点返回模型推理结果至业务系统。
如图8所示，离线推理可以包括以下步骤：
步骤801b，确定运行批作业任务的作业周期及触发时间。
示例性地，数据需求方的数据服务节点基于配置信息，确定运行批作业任务的作业周期及触发时间。
步骤802b，创建模型推理作业任务。
示例性地，数据需求方的数据服务节点创建模型推理作业任务，发送任务信息至各合作的数据提供方的数据服务节点。示例性地，该任务信息携带作业任务ID、批作业的作业周期及触发时间。
步骤803b，作业准备完成。
示例性地，参与合作的数据提供方的数据服务节点在作业准备完成后，返回指示准备完成的信息给数据需求方的数据服务节点。
步骤804b，作业任务执行及计费流程。
示例性地，参与合作的各数据服务节点进入作业任务执行及计费流程，相关的计费流程可以参照图7的步骤705至步骤715，在此不再赘述。
步骤805b，返回推理结果。
示例性地，各数据提供方的数据服务节点返回模型推理结果至数据需求 方的数据服务节点。
步骤806b，汇总推理结果。
示例性地，数据需求方的数据服务节点汇总模型推理结果。
步骤807b，发起推理请求。
示例性地，业务系统异步发起推理请求。
步骤808b，返回推理结果。
示例性地，数据需求方服务节点返回推理结果至业务系统。
需要说明的是，本应用实施例数据交易的计费方法，可以对参与合作的多方进行计费，涉及上述入网连接及计算环境准备、联合建模、联合在线推理、联合离线推理等阶段，且支持在线计费和离线计费两种计费模式。通过获取参与合作的各节点设备的计费采集信息，基于各节点设备的计费采集信息执行计费任务，可以满足多方数据交易的需求，进而有效提升数据交易的流通效率；此外，基于多维度的计费采集信息，使得本应用实施例的计费方法综合考虑了数据交易过程中的影响数据要素生产的多种因素，能够最大化发挥数据价值，精细化地促进数据交易的流通效率；再次，为了保障计费采集信息安全、不可篡改，本应用实施例采用过程密钥对计费采集信息进行加密及双向验证，可以确保计费过程中数据的安全性。
为了实现本公开实施例的方法，本公开实施例还提供一种数据交易的计费装置，该数据交易的计费装置应用于第一平台，与上述第一平台侧的计费方法对应，上述第一平台侧的计费方法实施例中的各步骤也完全适用于本数据交易的计费装置实施例。
如图9所示，该数据交易的计费装置包括：第一接收模块901、任务生成模块902和任务执行模块903。第一接收模块901用于接收至少两个节点设备分别发送的计费请求，所述计费请求至少携带作业任务标识；任务生成模块902用于基于各所述计费请求生成计费任务；第一接收模块901还用于接收各所述节点设备发送的计费采集信息；任务执行模块903用于基于所述计费采集信息执行所述计费任务。
在一些实施例中，该数据交易的计费装置还包括：第一发送模块904和第一验证模块905；第一接收模块901还用于接收各所述节点设备发送的确 定过程密钥的第一信息；第一发送模块904用于向各所述节点设备基于所述第一信息发送确定所述过程密钥的第二信息；第一验证模块905用于基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息。
在一些实施例中，第一验证模块905具体用于：
接收所述节点设备发送的第一认证请求，所述第一认证请求至少携带第一认证信息，所述第一认证信息为所述节点设备基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第一认证信息进行验证，并基于验证结果发送第二认证请求给所述节点设备，所述第二认证请求至少携带第二认证信息，所述第二认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
接收所述节点设备返回的对所述第二认证信息进行验证的验证结果。
在一些实施例中，第一验证模块905具体用于：
发送第二认证请求给所述节点设备，所述第二认证请求至少携带第二认证信息，所述第二认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
接收所述节点设备发送的第一认证请求，所述第一认证请求至少携带第一认证信息，所述第一认证信息为所述节点设备验证所述第二认证信息后基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第一认证信息进行验证，生成验证结果。
在一些实施例中，所述计费采集信息为所述至少两个节点设备执行作业任务过程中生成的，所述作业任务包括以下至少之一：联合建模任务、联合在线推理任务和联合离线推理任务。
在一些实施例中，所述计费采集信息包括以下至少之一：数据字段的信息值IV、数据字段数量、数据集样本量、数据集属性、使用的计算引擎、使用的算法类型、图形处理器GPU占用率、中央处理器CPU占用率、内存占用率和网络带宽占用率。
在一些实施例中，任务执行模块903具体用于：
基于验证后的所述计费采集信息生成计费账单；
对所述计费账单进行在线扣费或者离线扣费。
实际应用时，第一接收模块901、任务生成模块902、任务执行模块903、第一发送模块904及第一验证模块905，可以由数据交易的计费装置中的处理器来实现。当然，处理器需要运行存储器中的计算机程序来实现它的功能。
为了实现本公开实施例的方法，本公开实施例还提供一种数据交易的计费装置，该数据交易的计费装置应用于节点设备，与上述节点设备侧的计费方法对应，上述节点设备侧的计费方法实施例中的各步骤也完全适用于本数据交易的计费装置实施例。
如图10所示，该数据交易的计费装置包括：第二发送模块1001和获取模块1002。第二发送模块1001用于根据作业任务发送计费请求给第一平台，所述计费请求至少携带作业任务标识；获取模块1002用于基于设定计费规则获取执行作业任务过程中的计费采集信息；第二发送模块1001还用于发送所述计费采集信息给所述第一平台。
在一些实施例中，该数据交易的计费装置还包括：确定模块1003、第二接收模块1004及第二验证模块1005，确定模块1003用于基于所述设定计费规则确定过程密钥的第一信息；第二发送模块1001用于发送所述第一信息给所述第一平台；第二接收模块1004用于接收所述第一平台发送的所述过程密钥的第二信息；第二验证模块1005用于基于所述过程密钥与所述第一平台双向验证所述计费采集信息。
在一些实施例中，第二验证模块1005具体用于：
发送第一认证请求给所述第一平台，所述第一认证请求至少携带第一认证信息，所述第一认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
接收所述第一平台发送的第二认证请求，所述第二认证请求至少携带第二认证信息，所述第二认证信息为所述第一平台验证所述第一认证信息后基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
对所述第二认证信息进行验证，并返回验证结果给所述第一平台。
在一些实施例中，第二验证模块1005具体用于：
接收所述第一平台发送的第二认证请求，所述第二认证请求至少携带第二认证信息，所述第二认证信息为所述第一平台基于所述过程密钥对至少所 述计费采集信息进行加密处理生成的；
对所述第二认证信息进行验证，并基于验证结果发送第一认证请求给所述第一平台，所述第一认证请求至少携带第一认证信息，所述第一认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的。
在一些实施例中，所述作业任务包括以下至少之一：联合建模任务、联合在线推理任务和联合离线推理任务。
在一些实施例中，所述计费采集信息包括以下至少之一：数据字段的信息值IV、数据字段数量、数据集样本量、数据集属性、使用的计算引擎、使用的算法类型、图形处理器GPU占用率、中央处理器CPU占用率、内存占用率和网络带宽占用率。
在一些实施例中，所述节点设备为作为数据提供方的第一节点设备或者作为数据需求方的第二节点设备。
在一些实施例中，若所述节点设备为所述第一节点设备，第二接收模块1004还用于接收所述第一平台发送的第一请求；确定模块1003还用于基于所述第一请求确定所述设定计费规则。
在一些实施例中，若所述节点设备为所述第二节点设备，第二发送模块1001还用于发送第二请求给所述第一平台；该数据交易的计费装置还包括：连接模块1006，用于基于所述第一平台返回的请求响应，与参与合作的各第一节点设备建立连接。
实际应用时，第二发送模块1001、获取模块1002、确定模块1003、第二接收模块1004、第二验证模块1005及连接模块1006，可以由数据交易的计费装置中的处理器来实现。当然，处理器需要运行存储器中的计算机程序来实现它的功能。
需要说明的是：上述实施例提供的数据交易的计费装置在进行数据交易的计费时，仅以上述各程序模块的划分进行举例说明，实际应用中，可以根据需要而将上述处理分配由不同的程序模块完成，即将装置的内部结构划分成不同的程序模块，以完成以上描述的全部或者部分处理。另外，上述实施例提供的数据交易的计费装置与数据交易的计费方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
基于上述程序模块的硬件实现，且为了实现本公开实施例的方法，本公开实施例还提供一种第一平台。图11仅仅示出了该第一平台的示例性结构而非全部结构，根据需要可以实施图11示出的部分结构或全部结构。
如图11所示，本公开实施例提供的第一平台1100包括：至少一个处理器1101、存储器1102、用户接口1103和至少一个网络接口1104。第一平台1100中的各个组件通过总线系统1105耦合在一起。可以理解，总线系统1105用于实现这些组件之间的连接通信。总线系统1105除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图11中将各种总线都标为总线系统1105。
其中，用户接口1103可以包括显示器、键盘、鼠标、轨迹球、点击轮、按键、按钮、触感板或者触摸屏等。
本公开实施例中的存储器1102用于存储各种类型的数据以支持第一平台的操作。这些数据的示例包括：用于在第一平台上操作的任何计算机程序。
本公开实施例揭示的数据交易的计费方法可以应用于处理器1101中，或者由处理器1101实现。处理器1101可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，数据交易的计费方法的各步骤可以通过处理器1101中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1101可以是通用处理器、数字信号处理器(Digital Signal Processor)，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。处理器1101可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本公开实施例所公开的方法的步骤，可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于存储介质中，该存储介质位于存储器1102，处理器1101读取存储器1102中的信息，结合其硬件完成本公开实施例提供的数据交易的计费方法的步骤。
在示例性实施例中，第一平台可以被一个或多个应用专用集成电路(Application Specific Integrated Circuit，ASIC)、数字信号处理器(Digital Signal Processor)、可编程逻辑器件(Programmable Logic Device，PLD)、复杂可编程逻辑器件(Complex Programmable Logic Device，CPLD)、现场可编 程逻辑门阵列(Field Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器(Micro Controller Unit，MCU)、微处理器(Microprocessor)、或者其他电子元件实现，用于执行前述方法。
基于上述程序模块的硬件实现，且为了实现本公开实施例的方法，本公开实施例还提供一种节点设备。图12仅仅示出了该节点设备的示例性结构而非全部结构，根据需要可以实施图12示出的部分结构或全部结构。
如图12所示，本公开实施例提供的节点设备1200包括：至少一个处理器1201、存储器1202、用户接口1203和至少一个网络接口1204。节点设备1200中的各个组件通过总线系统1205耦合在一起。可以理解，总线系统1205用于实现这些组件之间的连接通信。总线系统1205除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图12中将各种总线都标为总线系统1205。
其中，用户接口1203可以包括显示器、键盘、鼠标、轨迹球、点击轮、按键、按钮、触感板或者触摸屏等。
本公开实施例中的存储器1202用于存储各种类型的数据以支持节点设备的操作。这些数据的示例包括：用于在节点设备上操作的任何计算机程序。
本公开实施例揭示的数据交易的计费方法可以应用于处理器1201中，或者由处理器1201实现。处理器1201可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，数据交易的计费方法的各步骤可以通过处理器1201中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1201可以是通用处理器、数字信号处理器(Digital Signal Processor)，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。处理器1201可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本公开实施例所公开的方法的步骤，可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于存储介质中，该存储介质位于存储器1202，处理器1201读取存储器1202中的信息，结合其硬件完成本公开实施例提供的数据交易的计费方法的步骤。
在示例性实施例中，节点设备1200可以被一个或多个ASIC、PLD、CPLD、 FPGA、通用处理器、控制器、MCU、Microprocessor、或其他电子元件实现，用于执行前述方法。
可以理解，存储器1102、1202可以是易失性存储器或非易失性存储器，也可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read Only Memory，ROM)、可编程只读存储器(Programmable Read-Only Memory，PROM)、可擦除可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)、电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、磁性随机存取存储器(Ferromagnetic Random Access Memory，FRAM)、快闪存储器(Flash Memory)、磁表面存储器、光盘、或只读光盘(Compact Disc Read-Only Memory，CD-ROM)；磁表面存储器可以是磁盘存储器或磁带存储器。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static Random Access Memory，SRAM)、同步静态随机存取存储器(Synchronous Static Random Access Memory，SSRAM)、动态随机存取存储器(Dynamic Random Access Memory，DRAM)、同步动态随机存取存储器(Synchronous Dynamic Random Access Memory，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate Synchronous Dynamic Random Access Memory，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced Synchronous Dynamic Random Access Memory，ESDRAM)、同步连接动态随机存取存储器(SyncLink Dynamic Random Access Memory，SLDRAM)、直接内存总线随机存取存储器(Direct Rambus Random Access Memory，DRRAM)。本公开实施例描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本公开实施例还提供了一种数据共享服务系统，包括：本公开实施例所述的第一平台和至少两个本公开实施例所述的节点设备。示例性地，如图1所示，第一平台和节点设备之间可以通过IP专网连接，以提升数据传递的安全性。这里，至少两个节点设备包括作为数据提供方的第一节点设备(即DSN)和作为数据需求方的第二节点设备(即DRN)。
在示例性实施例中，本公开实施例还提供了一种存储介质，即计算机存储介质，具体可以是计算机可读存储介质，例如包括存储计算机程序的存储器1102，上述计算机程序可由第一平台的处理器1101执行，以完成本公开实施例第一平台侧方法所述的步骤；又如，包括存储计算机程序的存储器1202，上述计算机程序可由节点设备的处理器1201执行，以完成本公开实施例节点设备侧方法所述的步骤。计算机可读存储介质可以是ROM、PROM、EPROM、EEPROM、Flash Memory、磁表面存储器、光盘、或CD-ROM等存储器。
需要说明的是：“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
另外，本公开实施例所记载的技术方案之间，在不冲突的情况下，可以任意组合。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开披露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以权利要求的保护范围为准。

Claims (22)

  1. 一种数据交易的计费方法，应用于第一平台，所述方法包括：
    接收至少两个节点设备分别发送的计费请求，所述计费请求至少携带作业任务标识；
    基于各所述计费请求生成计费任务；
    接收各所述节点设备发送的计费采集信息；
    基于所述计费采集信息执行所述计费任务。
  2. 根据权利要求1所述的方法，其中，所述基于所述计费采集信息执行所述计费任务之前，所述方法还包括：
    接收各所述节点设备发送的确定过程密钥的第一信息；
    向各所述节点设备基于所述第一信息发送确定所述过程密钥的第二信息；
    基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息。
  3. 根据权利要求2所述的方法，其中，所述基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息，包括：
    接收所述节点设备发送的第一认证请求，所述第一认证请求至少携带第一认证信息，所述第一认证信息为所述节点设备基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
    对所述第一认证信息进行验证，并基于验证结果发送第二认证请求给所述节点设备，所述第二认证请求至少携带第二认证信息，所述第二认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
    接收所述节点设备返回的对所述第二认证信息进行验证的验证结果。
  4. 根据权利要求2所述的方法，其中，所述基于所述过程密钥与所述节点设备双向验证相应的所述计费采集信息，包括：
    发送第二认证请求给所述节点设备，所述第二认证请求至少携带第二认证信息，所述第二认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
    接收所述节点设备发送的第一认证请求，所述第一认证请求至少携带第一认证信息，所述第一认证信息为所述节点设备验证所述第二认证信息后基 于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
    对所述第一认证信息进行验证，生成验证结果。
  5. 根据权利要求1所述的方法，其中，所述计费采集信息为所述至少两个节点设备执行作业任务过程中生成的，所述作业任务包括以下至少之一：联合建模任务、联合在线推理任务和联合离线推理任务。
  6. 根据权利要求1所述的方法，其中，所述计费采集信息包括以下至少之一：数据字段的信息值IV、数据字段数量、数据集样本量、数据集属性、使用的计算引擎、使用的算法类型、图形处理器GPU占用率、中央处理器CPU占用率、内存占用率和网络带宽占用率。
  7. 根据权利要求2所述的方法，其中，基于所述计费采集信息执行所述计费任务，包括：
    基于验证后的所述计费采集信息生成计费账单；
    对所述计费账单进行在线扣费或者离线扣费。
  8. 一种数据交易的计费方法，应用于节点设备，所述方法包括：
    根据作业任务发送计费请求给第一平台，所述计费请求至少携带作业任务标识；
    基于设定计费规则获取执行作业任务过程中的计费采集信息；
    发送所述计费采集信息给所述第一平台。
  9. 根据权利要求8所述的方法，所述方法还包括：
    基于所述设定计费规则确定过程密钥的第一信息；
    发送所述第一信息给所述第一平台；
    接收所述第一平台发送的所述过程密钥的第二信息；
    基于所述过程密钥与所述第一平台双向验证所述计费采集信息。
  10. 根据权利要求9所述的方法，其中，所述基于所述过程密钥与所述第一平台双向验证所述计费采集信息，包括：
    发送第一认证请求给所述第一平台，所述第一认证请求至少携带第一认证信息，所述第一认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
    接收所述第一平台发送的第二认证请求，所述第二认证请求至少携带第 二认证信息，所述第二认证信息为所述第一平台验证所述第一认证信息后基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
    对所述第二认证信息进行验证，并返回验证结果给所述第一平台。
  11. 根据权利要求9所述的方法，其中，所述基于所述过程密钥与所述第一平台双向验证所述计费采集信息，包括：
    接收所述第一平台发送的第二认证请求，所述第二认证请求至少携带第二认证信息，所述第二认证信息为所述第一平台基于所述过程密钥对至少所述计费采集信息进行加密处理生成的；
    对所述第二认证信息进行验证，并基于验证结果发送第一认证请求给所述第一平台，所述第一认证请求至少携带第一认证信息，所述第一认证信息为基于所述过程密钥对至少所述计费采集信息进行加密处理生成的。
  12. 根据权利要求8所述的方法，其中，所述作业任务包括以下至少之一：联合建模任务、联合在线推理任务和联合离线推理任务。
  13. 根据权利要求8所述的方法，其中，所述计费采集信息包括以下至少之一：数据字段的信息值IV、数据字段数量、数据集样本量、数据集属性、使用的计算引擎、使用的算法类型、图形处理器GPU占用率、中央处理器CPU占用率、内存占用率和网络带宽占用率。
  14. 根据权利要求8所述的方法，其中，所述节点设备为作为数据提供方的第一节点设备或者作为数据需求方的第二节点设备。
  15. 根据权利要求14所述的方法，其中，若所述节点设备为所述第一节点设备，所述方法还包括：
    接收所述第一平台发送的第一请求；
    基于所述第一请求确定所述设定计费规则。
  16. 根据权利要求14所述的方法，其中，若所述节点设备为所述第二节点设备，所述方法还包括：
    发送第二请求给所述第一平台；
    基于所述第一平台返回的请求响应，与参与合作的各第一节点设备建立连接。
  17. 一种数据交易的计费装置，应用于第一平台，所述装置包括：
    接收模块，用于接收至少两个节点设备分别发送的计费请求，所述计费请求至少携带作业任务标识；
    任务生成模块，用于基于各所述计费请求生成计费任务；
    所述接收模块还用于接收各所述节点设备发送的计费采集信息；
    任务执行模块，用于基于所述计费采集信息执行所述计费任务。
  18. 一种数据交易的计费装置，应用于节点设备，所述装置包括：
    发送模块，用于根据作业任务发送计费请求给第一平台，所述计费请求至少携带作业任务标识；
    获取模块，用于基于设定计费规则获取执行作业任务过程中的计费采集信息；
    所述发送模块还用于发送所述计费采集信息给所述第一平台。
  19. 一种第一平台，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，
    所述处理器，用于运行计算机程序时，执行权利要求1至7任一项所述方法的步骤。
  20. 一种节点设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，
    所述处理器，用于运行计算机程序时，执行权利要求8至16任一项所述方法的步骤。
  21. 一种数据共享服务系统，包括：如权利要求19所述的第一平台和至少两个如权利要求20所述的节点设备。
  22. 一种存储介质，所述存储介质上存储有计算机程序，其中，所述计算机程序被处理器执行时，实现权利要求1至16任一项所述方法的步骤。
PCT/CN2023/092485 2022-05-10 2023-05-06 数据交易的计费方法、装置、系统及存储介质 Ceased WO2023217029A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210505641.7 2022-05-10
CN202210505641.7A CN117094776A (zh) 2022-05-10 2022-05-10 数据交易的计费方法、装置、系统及存储介质

Publications (1)

Publication Number Publication Date
WO2023217029A1 true WO2023217029A1 (zh) 2023-11-16

Family

ID=88729710

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/092485 Ceased WO2023217029A1 (zh) 2022-05-10 2023-05-06 数据交易的计费方法、装置、系统及存储介质

Country Status (2)

Country Link
CN (1) CN117094776A (zh)
WO (1) WO2023217029A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN120031002A (zh) * 2025-04-24 2025-05-23 鱼快创领智能科技(南京)有限公司 一种基于规则和经验两种角度的可持续学习的运单撮合方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119383190B (zh) * 2024-09-23 2026-03-24 中国移动通信有限公司研究院 数据流通方法、装置、电子设备、存储介质及计算机程序产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112561510A (zh) * 2020-12-21 2021-03-26 北京红枣科技有限公司 缴费系统、方法、装置、设备及存储介质
CN113810178A (zh) * 2020-06-12 2021-12-17 中国移动通信有限公司研究院 密钥管理方法、装置、系统及存储介质
CN113839978A (zh) * 2020-06-24 2021-12-24 中兴通讯股份有限公司 基于计费平台的计费方法、电子设备和存储介质
CN114285678A (zh) * 2020-09-27 2022-04-05 中国移动通信有限公司研究院 一种计费方法、装置、设备及可读存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1932865A (zh) * 2006-10-10 2007-03-21 潘铁军 一种预付费计量表的付费方法
CN102611561B (zh) * 2011-01-25 2016-09-28 中兴通讯股份有限公司 一种对等网计费或统计信息验证的方法和系统
CN103379462B (zh) * 2012-04-23 2017-03-01 阿尔卡特朗讯 一种用于处理计费请求的方法和装置
CN106572453B (zh) * 2015-10-09 2020-04-28 中国电信股份有限公司 内容计费方法、计费网元、sp服务器以及计费系统
CN111431840B (zh) * 2019-01-09 2022-06-07 北京京东尚科信息技术有限公司 安全处理方法、装置、计算机设备及可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113810178A (zh) * 2020-06-12 2021-12-17 中国移动通信有限公司研究院 密钥管理方法、装置、系统及存储介质
CN113839978A (zh) * 2020-06-24 2021-12-24 中兴通讯股份有限公司 基于计费平台的计费方法、电子设备和存储介质
CN114285678A (zh) * 2020-09-27 2022-04-05 中国移动通信有限公司研究院 一种计费方法、装置、设备及可读存储介质
CN112561510A (zh) * 2020-12-21 2021-03-26 北京红枣科技有限公司 缴费系统、方法、装置、设备及存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN120031002A (zh) * 2025-04-24 2025-05-23 鱼快创领智能科技(南京)有限公司 一种基于规则和经验两种角度的可持续学习的运单撮合方法

Also Published As

Publication number Publication date
CN117094776A (zh) 2023-11-21

Similar Documents

Publication Publication Date Title
Xiong et al. Smart contract based data trading mode using blockchain and machine learning
US11150271B2 (en) Method or system for management of a device for energy consumption by applying blockchain protocol
CN109981679B (zh) 在区块链网络中执行事务的方法和装置
CN113222752B (zh) 基于区块链的数据处理系统、方法、计算设备及存储介质
CN116325833B (zh) 将设备标识集成到区块链的许可框架中
Debe et al. Blockchain-based decentralized reverse bidding in fog computing
WO2019125576A1 (en) Transference tracking
CN110535648A (zh) 电子凭证生成及验证和密钥控制方法、装置、系统和介质
CN111612452A (zh) 一种基于区块链的知识产权管理系统及方法
CN116155771B (zh) 网络异常测试方法、装置、设备、存储介质和程序
KR102450412B1 (ko) 사물인터넷에서 서비스 수준 협약 기반 공유경제 서비스 제공시스템 및 제공방법
CN113011883A (zh) 一种数据处理方法、装置、设备及存储介质
WO2023217029A1 (zh) 数据交易的计费方法、装置、系统及存储介质
CN101702650A (zh) 网络计算业务的计费方法及网络计算业务提供系统
CN114881757A (zh) 一种函证方法、系统和电子设备
CN117440010A (zh) 一种基于区块链的光伏管理方法、系统、存储介质及设备
Podgorelec et al. State channel as a service based on a distributed and decentralized web
EP3542300B1 (en) Method for operating a peer-to-peer application
CN113300853B (zh) 金融征信信息管理方法、装置、电子设备及存储介质
CN113781230B (zh) 基于区块链的交易处理方法和装置
CN108073699B (zh) 大数据聚合分析方法及装置
KR101120059B1 (ko) 클라우드 컴퓨팅 과금 공증장치, 과금 시스템 및 과금방법
CN115131021A (zh) 基于算力网络交易区块链的信息处理方法及装置
CN116957566A (zh) 基于区块链的数据处理方法及装置、电子设备、存储介质
Ramkumar et al. A survey on different consensus mechanisms for the blockchain technology

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23802801

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 21.03.2025)

122 Ep: pct application non-entry in european phase

Ref document number: 23802801

Country of ref document: EP

Kind code of ref document: A1