CN114585049A

CN114585049A - Data processing method, device and equipment based on block chain network and storage medium

Info

Publication number: CN114585049A
Application number: CN202011376575.5A
Authority: CN
Inventors: 王珂; 杨波; 阎军智; 刘福文
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2020-11-30
Filing date: 2020-11-30
Publication date: 2022-06-03

Abstract

The invention discloses a data processing method, a device, equipment and a storage medium based on a block chain network. Wherein the method comprises the following steps: receiving slice operation data and resource configuration data broadcast by a first node in a block chain network; the first node characterizes an operator providing slicing services; receiving slicing service data broadcast by a second node in the block chain network; the second node characterizes an application service provider using the slice; verifying the authenticity of the slice operation data based on the resource configuration data and/or the slice service data; when the slice operation data are verified to be real slice operation data, forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record.

Description

Data processing method, device and equipment based on block chain network and storage medium

Technical Field

The present invention relates to the field of wireless communication technologies, and in particular, to a data processing method, apparatus, device, and storage medium based on a block chain network.

Background

With the rapid development of terminal technology, more and more service types are supported by a terminal, and in order to meet the network communication requirements of different types of services, an operator can recombine network resources to obtain a plurality of network slices, so that an application service provider can use the network slices to provide application services for the terminal. In general, in the process of providing a service to a terminal through a network slice, slice operation data is generated in a slice manager of an operator, and the operator may transmit the generated slice operation data to the application service provider in order to facilitate the application service provider to view the slice operation data. However, how to ensure that the slice operation data sent by the operator is authentic and credible and how to realize mutual trust of the two parties become a key technical problem.

Disclosure of Invention

In view of this, embodiments of the present invention are intended to provide a data processing method, device, apparatus, and storage medium based on a blockchain network.

The technical scheme of the embodiment of the invention is realized as follows:

at least one embodiment of the present invention provides a data processing method based on a blockchain network, the method including:

receiving slice operation data and resource configuration data broadcast by a first node in a block chain network; the first node characterizes an operator providing slicing services; receiving slicing service data broadcast by a second node in the block chain network; the second node characterizes an application service provider using the slice;

verifying the authenticity of the slice operation data based on the resource configuration data and/or the slice service data;

when the slice operation data are verified to be real slice operation data, forming a record of the verified slice operation data; and performs consensus mechanism operations on the formed records.

Further, in accordance with at least one embodiment of the present invention, verifying authenticity of the slice run data based on the resource configuration data comprises:

judging whether the mapping relation between the resource configuration data and the slice operation data meets a preset relation or not;

and when the mapping relation between the resource configuration data and the slice operation data is determined to meet a preset relation, verifying that the slice operation data is real slice operation data.

Further, in accordance with at least one embodiment of the present invention, verifying authenticity of the slicing operation data based on the slicing operation data includes:

judging whether the mapping relation between the slicing service data and the slicing operation data meets a preset relation or not;

and when the mapping relation between the slice service data and the slice operation data is determined to meet the preset relation, verifying that the slice operation data is real slice operation data.

Further, in accordance with at least one embodiment of the present invention, verifying authenticity of the slice run data based on the resource configuration data and slice traffic data comprises:

judging whether the mapping relation between the resource configuration data and the slice operation data meets a preset relation or not; judging whether the mapping relation between the slice service data and the slice operation data meets the preset relation or not;

and when the mapping relation between the resource configuration data and the slice operation data is determined to meet a preset relation and the mapping relation between the slice service data and the slice operation data meets the preset relation, verifying that the slice operation data is real slice operation data.

Furthermore, according to at least one embodiment of the present invention, applied to the second node, the method further includes:

reading the verified slice running data from the block chain network;

and judging whether the verified slice operation data meets the requirements of a Service Level Agreement (SLA).

Further, according to at least one embodiment of the present invention, the determining whether the verified slice run data meets SLA requirements includes:

reading SLA contracts from the blockchain network;

and judging whether the verified slice operation data meets the SLA requirements or not by utilizing the SLA contract.

Furthermore, in accordance with at least one embodiment of the present invention, before the reading of the SLA contract from the blockchain network, the method further comprises:

after the slice ordering is completed, acquiring first signature information corresponding to the first node and second signature information corresponding to the second node;

based on the first signature information and the second signature information, carrying out signature processing on the SLA contract to obtain the SLA contract after signature processing; the SLA contract is a contract that the slicing service between the operator and the application service provider should meet SLA requirements;

and issuing the SLA contract after signature processing to the block chain network.

Further, in accordance with at least one embodiment of the present invention, the method further comprises:

transmitting the slice operation data and the resource configuration data to other nodes except the first node and the second node in the block chain network;

and the resource configuration data is used for the other nodes to verify the authenticity of the slice operation data, and when the slice operation data is verified to be real data, the verified slice operation data is recorded and a consensus mechanism operation is executed.

transmitting the slice service data to other nodes in the block chain network;

and when the slice data is verified to be real data, the verified slice operation data is recorded and a consensus mechanism operation is executed.

At least one embodiment of the present invention provides a data processing apparatus based on a blockchain network, including:

the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving slice operation data and resource configuration data broadcasted by a first node in a block chain network; the first node characterizes an operator providing slicing services; receiving slicing service data broadcast by a second node in the block chain network; the second node characterizes an application service provider using the slice;

a first processing unit, configured to verify authenticity of the slice operation data based on the resource configuration data and/or the slice service data;

the second processing unit is used for forming a record of the verified slice operation data when the slice operation data is verified to be real slice operation data; and performs a consensus mechanism operation on the formed record.

Furthermore, according to at least one embodiment of the present invention, the first processing unit is specifically configured to:

judging whether the mapping relation between the resource configuration data and the slice operation data meets a preset relation or not; and when the mapping relation between the resource configuration data and the slice operation data is determined to meet the preset relation, verifying that the slice operation data is real slice operation data.

judging whether the mapping relation between the slicing service data and the slicing operation data meets a preset relation or not; and when the mapping relation between the slice service data and the slice operation data is determined to meet the preset relation, verifying that the slice operation data is real slice operation data.

judging whether the mapping relation between the resource configuration data and the slice operation data meets a preset relation or not; judging whether the mapping relation between the slice service data and the slice operation data meets the preset relation or not; and when the mapping relation between the resource configuration data and the slice operation data is determined to meet a preset relation and the mapping relation between the slice service data and the slice operation data meets the preset relation, verifying that the slice operation data is real slice operation data.

Furthermore, according to at least one embodiment of the present invention, applied to the second node, the apparatus further includes:

the judging unit is used for reading the verified slice operation data from the block chain network; and judging whether the verified slice operation data meets the SLA requirements.

Furthermore, according to at least one embodiment of the present invention, the determining unit is specifically configured to:

reading SLA contracts from the blockchain network; and judging whether the verified slice operation data meets the SLA requirements or not by utilizing the SLA contract.

Furthermore, according to at least one embodiment of the present invention, applied to the first node, the apparatus further includes:

the issuing unit is used for acquiring first signature information corresponding to the first node and second signature information corresponding to the second node after the slice ordering is finished; based on the first signature information and the second signature information, carrying out signature processing on the SLA contract to obtain the SLA contract after signature processing; the SLA contract is a contract that the slicing service between the operator and the application service provider should meet SLA requirements; and issuing the SLA contract after signature processing to the block chain network.

Further, in accordance with at least one embodiment of the present invention, the apparatus further comprises:

a sending unit, configured to send slice operation data and resource configuration data to other nodes in the blockchain network except the first node and the second node;

Furthermore, according to at least one embodiment of the present invention, the sending unit is further configured to:

transmitting the slice service data to other nodes in the block chain network;

At least one embodiment of the present invention is an electronic device including:

the communication interface is used for receiving slice operation data and resource configuration data broadcast by a first node in a block chain network; the first node characterizes an operator providing slicing services; receiving slicing service data broadcast by a second node in the block chain network; the second node characterizes an application service provider using the slice;

a processor for verifying authenticity of the slice operational data based on the resource configuration data and/or the slice traffic data; when the slice operation data are verified to be real slice operation data, forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record.

At least one embodiment of the invention provides an electronic device comprising a processor and a memory for storing a computer program capable of running on the processor,

wherein the processor is configured to perform the steps of any of the above methods when running the computer program.

At least one embodiment of the invention provides a storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of any of the methods described above.

The data processing method, the device, the equipment and the storage medium based on the block chain network provided by the embodiment of the invention receive slice operation data and resource configuration data broadcast by a first node in the block chain network; the first node characterizes an operator providing slicing services; receiving slicing service data broadcast by a second node in the block chain network; the second node characterizes an application service provider using the slice; verifying the authenticity of the slice operation data based on the resource configuration data and/or the slice service data; when the slice operation data are verified to be real slice operation data, forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record. By adopting the technical scheme provided by the embodiment of the invention, the operator uploads the slice operation data and the resource configuration data to the blockchain network, and the application service provider uploads the slice service data to the blockchain network, so that other nodes in the blockchain network can verify whether the slice operation data uploaded by the operator is real and credible, and the subsequent application service provider can acquire the real slice operation data provided by the operator, thereby realizing mutual trust between the two parties.

Drawings

FIG. 1 is a schematic diagram of a carrier-side slice manager managing slice operational data;

FIG. 2 is a schematic diagram of a system architecture applied to a data processing method based on a blockchain network according to an embodiment of the present invention;

fig. 3 is a schematic flowchart of an implementation of a data processing method based on a blockchain network according to an embodiment of the present invention;

FIG. 4 is a flow chart illustrating an implementation of issuing data for verifying whether slice operation data is real to a blockchain network according to an embodiment of the present invention;

fig. 5 is a schematic flow chart of a first implementation of verifying authenticity of slice operation data issued by an operator to a blockchain network according to an embodiment of the present invention;

fig. 6 is a schematic flow chart of a second implementation of verifying the authenticity of slice operation data issued by an operator to a blockchain network according to an embodiment of the present invention;

fig. 7 is a schematic flow chart of a third implementation of verifying the authenticity of slice operation data issued by an operator to a blockchain network according to an embodiment of the present invention;

fig. 8 is a schematic flow chart of an implementation of uploading an SLA contract for verifying SLA requirements to a blockchain network according to an embodiment of the present invention;

fig. 9 is a schematic flow chart of implementing SLA requirement verification on verified real sliced running data by a second node according to the embodiment of the present invention;

fig. 10 is a schematic structural diagram of a data processing apparatus based on a blockchain network according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

Before the technical solution of the embodiment of the present invention is introduced, a description is given of a related art.

In the related art, in a 5G mobile communication system, Network Slicing (NS) is introduced, so that customized and dedicated network services can be provided for different industries based on a shared physical infrastructure, a 4G single network mode is changed, and a 5G network supporting function customization, security and resource isolation, and topology optimization is created, thereby meeting the requirements of specific targets, specific service classes, and even specific customers. Based on network slicing, an operator can expand services from traditional voice and data to everything interconnection to form a new business model; the method is transformed from a traditional communication provider to a platform provider, and provides a platform for experiment, deployment and management, even end-to-end service, for the vertical industry through operation of network slices. The operator can sell the network slices in the modes of B2B, B2B2C and the like, thereby enabling the mobile virtual network operator, OTT manufacturers and the application of the vertical industry to dynamically rent slice resources from the telecom operator according to the needs. Fig. 1 is a schematic diagram of a slice manager at an operator side managing slice operation Data in the related art, and as shown in fig. 1, taking a 5G communication system as an example, a Network Data analysis Function (NWDAF) at the operator side is used for receiving and storing Network Data provided by a slice manager and a core Network corresponding to a service. A slice manager for continuously evaluating SLA satisfaction of slices in a run state after a slice creation phase; and updating GSRR and MSRR configuration parameters to a Radio Access Network (RAN) subdomain from time to time according to the inferred SLA meeting condition, and issuing refreshed Core Network (CN) resources to a slice control plane.

In summary, in the related art, the slice manager on the operator side collects slice operation data, and evaluates whether the slice operation data meets the SLA requirements, so as to adjust resource investment, thereby achieving a good balance between slice service cost and performance. However, the application service provider (tenant) is not opened as data support evidence of the quality of the provided slice service, that is, when the slice operation data is sent to the application service provider by the operator, there may be cases where the data is significantly withheld, even modified and forged (the data source, storage, and communication processes may all change), it is difficult to trace back the problem, the application service provider cannot correctly evaluate the quality of the network slice provided by the operator, and the operator cannot self-prove.

Based on this, in various embodiments of the present invention, slice operation data and resource configuration data broadcast by a first node in a blockchain network are received; the first node characterizes an operator providing slicing services; receiving slicing service data broadcast by a second node in the block chain network; the second node characterizes an application service provider that uses the slice; verifying the authenticity of the slice operation data based on the resource configuration data and/or the slice service data; when the slice operation data are verified to be real slice operation data, forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record.

The present invention will be described in further detail with reference to the accompanying drawings and examples.

Terms and expressions referred to in the embodiments of the present invention are explained, and the terms and expressions referred to in the embodiments of the present invention are applied to the following explanations.

1) Transactions (transactions), equivalent to the computer term "Transaction," does not refer solely to transactions in the business context, and embodiments of the present invention follow this convention in view of the convention in blockchain technology that colloquially uses the term "Transaction. In a blockchain network employing an account-based model, transactions include three different transaction types: deployment (deployment), invocation (Invoke) and Query (Query). The deployment transaction is used for installing a specified chain code to a node of the blockchain network, and the call and query type transaction is used for calling the chain code of the deployment number so as to realize the operation of relevant data of a target account in the ledger, wherein the operation of adding, deleting, checking and changing modifies the data in the form of Key-Value pairs in the account, or adds a new account in the ledger.

2) A Block (Block) recording a data structure of the ledger data updated by the exchange within a period of time, marked with a timestamp and a unique mark (e.g. a digital fingerprint) of a previous Block, and after the Block is subjected to consensus verification by nodes in the Block chain network, the Block is appended to the end of the Block chain to become a new Block.

3) A chain of blocks (Blockchain), a chain of data structures in which blocks are assembled in a sequentially contiguous manner, each block having a hash value of a previous block or a subset thereof referenced therein, to cryptographically secure the recorded transaction against tampering and forgery.

4) A blockchain network incorporates new blocks into a set of centerless nodes of the blockchain in a consensus manner.

5) The account book (Legger) is the sum of data recorded by taking an account as a dimension in a block chain network, and comprises the elements of the account book data, the state of the account book, the state certification of the account book, a block index and the like.

6) The ledger data, the actual block data storage, i.e. the record of a series of ordered and non-falsifiable transactions recorded in the block chain, may be expressed in the form of a file system, and the update of the data in the account/account is realized when an intelligent contract called in the transaction is executed.

7) The ledger state, also referred to as state data, i.e. the state of the ledger data, may be in the form of key-value pairs in the database terminal, where the real-time ledger state is used to represent the latest record of key-value pairs updated by the agreed-upon exchange and the historical ledger state is used to represent the historical record of key-value pairs.

8) Presence attestation is attestation of authenticity of presence of the account data implemented in cryptographic manner, such as attestation of the way the account data computes a merkel (Merkle) tree.

9) Consensus (Consensus), a process in a block-chain network, for agreeing on transaction results among a plurality of nodes involved, and mechanisms for achieving Consensus include PoW, PoS, certificate of authority (DPoS), certificate of elapsed time (PoET), and the like.

10) Intelligent contracts (SmartContracts), also called chain codes (Chaincode), are deployed in blockchain networks and trigger execution programs according to conditions, and are used for operating the ledger through inquiry, addition and modification so as to realize inquiry or update of the ledger.

Fig. 2 is a schematic diagram of a system architecture applied to a data processing method based on a block chain network according to an embodiment of the present invention, and as shown in fig. 2, the system includes:

a first node for broadcasting slice operation data and resource allocation data in a blockchain network;

a second node for broadcasting sliced service data in a blockchain network;

a third node (not shown in the figure) for receiving the slice operation data and the resource configuration data broadcasted by the first node in the block chain network; receiving slicing service data broadcast by a second node in the block chain network; verifying the authenticity of the slice operation data based on the resource configuration data and/or the slice service data; when the slice operation data are verified to be real slice operation data, forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record.

Here, the first node corresponds to an operator providing the slicing service, the second node corresponds to an application service provider using the slicing, and the third node may correspond to a device other than the operator or the application service provider, or may correspond to the operator or the application service provider. Operator node 1 to operator node m in fig. 1 correspond to the first node, and application service provider node 1 to application service provider node n correspond to the second node.

Fig. 3 is a schematic diagram of an implementation flow of a data processing method based on a blockchain network according to an embodiment of the present invention, which is applied to a third node, and illustrates an implementation process of fig. 2 with reference to a schematic diagram of a system architecture shown in fig. 2, where as shown in fig. 3, the method includes:

step 301: receiving slice operation data and resource configuration data broadcast by a first node in a block chain network; the first node characterizes an operator providing slicing services; receiving slicing service data broadcast by a second node in the block chain network; the second node characterizes an application service provider using the slice;

step 302: verifying the authenticity of the slice operation data based on the resource configuration data and/or the slice service data;

step 303: when the slice operation data are verified to be real slice operation data, forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record.

Here, in step 301, in actual application, the operator may use the slice manager to reassemble network resources, such as access network resources and core network resources, to obtain a plurality of network slices, and use the obtained network slices to provide a slicing service for the terminal. During the process of recombining network resources, resource configuration data, such as access network and core network resource data, is generated; in providing the slicing service to the terminal, slicing Operation data, such as Operation, administration and Maintenance (OAM) data and non-OAM data, is generated. The application service provider may also provide the slicing service to the terminal using the network slice, and in the process of providing the slicing service to the terminal, by obtaining the feedback of the user on the slicing service, slicing service data, such as Mean Opinion Score (MOS) data, may be generated.

Here, in actual application, if the authenticity of the slice operation data can be ensured, the quality of the slice service provided to the terminal can be ensured, and thus, the authenticity check needs to be performed on the slice operation data provided by the operator. In order to avoid the authenticity check of the slicing operation data by only depending on the data provided by the operator, the slicing operation data can be effectively checked by combining the slicing service data provided by the application service provider. Considering that the blockchain network has a highly reliable supervision function, the blockchain network may be constructed by a plurality of operator nodes and a plurality of application service providers, after the operator nodes generate slice operation data and resource configuration data, the slice operation data and the resource configuration data may be uploaded to the blockchain network, after the application service provider nodes generate slice service data, the slice service data may be uploaded to the blockchain network, and each node in the blockchain network receives the three data through a broadcast mechanism of the blockchain network, and subsequently, each node in each node may check authenticity of the slice operation data by using the resource configuration data and/or the slice service data.

Here, in step 302, in the actual application, if the actual resource provided for the terminal to perform the slicing service matches the resource required for slicing operation, it indicates that the slicing operation data is real, so that the authenticity of the slicing operation data generated by the operator can be verified by using the resource configuration data generated by the operator; and if the score for evaluating the slice service quality is consistent with the service quality provided by the slice operation, the slice operation data is true, so that the slice service data generated by the application service provider can be used for verifying the authenticity of the slice operation data generated by the operator.

The following is a detailed description of how to verify the authenticity of the operator-provided slice run data.

In practical application, an operator may recombine network resources such as an access network and a core network to obtain a plurality of network slices, and allocate corresponding wireless resources such as time slots, frequency spectrums, and the like to each of the plurality of network slices, thereby forming resource configuration data. In the slicing operation process, an operator can perform daily operation, management and maintenance on slices through a slice manager so as to form slice OAM data, and the slice OAM data is used as slice operation data; and/or the operator performs other management on the slice through the slice manager so as to form slice non-OAM data and uses the slice non-OAM data as slice operation data. In practical application, the wireless resources corresponding to the network slices can be updated to meet different types of service requirements of the terminal, so that resource configuration data generated by a slice manager in an operator can be changed; when a terminal performs different types of services, slices corresponding to the services may change, and thus, slice operation data generated by a slice manager in an operator may change. If the change of the resource configuration data is consistent with the change trend of the slice operation data, the slice operation data generated by the slice manager of the operator is true; otherwise, it indicates that the slice operation data generated by the slice manager of the operator is not real.

Based thereon, in an embodiment, verifying authenticity of the slice run data based on the resource configuration data comprises:

Here, the fact that the mapping relationship between the resource allocation data and the slice operation data satisfies the preset relationship may mean that the slice operation data and the resource allocation data satisfy a positive correlation relationship, and specifically, the change trend of the slice performance represented by the slice operation data may be the same as the change trend of the wireless resource allocated to the slice represented by the resource allocation data.

Here, the positive correlation may include: a linear increasing relationship, an exponential increasing relationship, and the like. The slice run data includes: slicing OAM data and/or slicing non-OAM data; the resource configuration data may refer to radio resource data allocated for a network slice currently used by the terminal.

Here, the slice OAM data includes: UE-level Minimization of Drive Test (MDT) data, Network Function (NF) performance measurement data, and Network-level KPI data; wherein the network-level KPI data comprises: the method comprises the steps of virtualization resource utilization rate, the number of registered users of the network and the network slice example, end-to-end time delay of the 5G network, uplink/downlink throughput of the network and the network slice example and the like. The slice non-OAM data includes: QoS flow level, UE level, or even traffic level data input from the core network. The Resource configuration data refers to Resource update data of an access network core network issued by a Slice manager according to the SLA satisfaction condition, for example, Guaranteed Slice Radio resources (GSRR, Guaranteed Slice Radio Resource), Maximum Slice Radio resources (MSRR, Maximum Slice Radio Resource), and the like. Slice SLA signing information may also be included.

For example, table 1 is a corresponding relationship between resource allocation data and slice operation data, and as shown in table 1, when the service type of the terminal is changed from service 1 to service 2, the radio resource corresponding to the slice is updated to obtain changed resource allocation data. It is assumed that the radio resource allocated for the service 1 is the time slot 1, and the radio resource allocated for the service 2 is the time slot 1 and the time slot 2, so that it can be determined that the variation trend of the radio resource is increased according to the resource configuration data. In addition, when the service type of the terminal is changed from service 1 to service 2, the corresponding slice is changed, and changed slice operation data is obtained. Assuming that the time delay measurement is performed on the slice 1 corresponding to the service 1, the obtained time delay is 5s, and the time delay measurement is performed on the slice 2 corresponding to the service 2, the obtained time delay is 3s, so that the variation trend of the slice performance can be determined to be continuously improved according to the slice operation data. Since the variation trend of the radio resource and the variation trend of the slice performance are the same, it can be determined that the slice operation data is real.

TABLE 1

In practical application, an operator can recombine network resources such as an access network and a core network to obtain a plurality of network slices, and in the slice operation process, the operator can perform daily operation, management and maintenance on the slices through a slice manager to form slice OAM data and take the slice OAM data as slice operation data; and/or the operator performs other management on the slice through the slice manager so as to form slice non-OAM data and uses the slice non-OAM data as slice operation data. During the slicing operation, the application service provider can evaluate the quality of the slicing, thereby forming slicing business data.

In practical application, when a terminal performs different types of services, slices corresponding to the services will change, so that slice operation data generated by a slice manager in an operator will change, and slice service data generated by an application service provider will change. If the change of the slicing service data is consistent with the change trend of the slicing operation data, the slicing operation data generated by the slicing manager of the operator is real; otherwise, it indicates that the slice operation data generated by the slice manager of the operator is not real.

Based on this, in an embodiment, verifying authenticity of the slice operation data based on the slice service data includes:

Here, the fact that the mapping relationship between the slice service data and the slice operation data satisfies the preset relationship may mean that the slice operation data and the slice service data satisfy a positive correlation relationship, and specifically, the change trend of the slice performance represented by the slice operation data and the change trend of the MOS value represented by the slice service data are the same.

Here, the positive correlation may include: a linear increasing relationship, an exponential increasing relationship, and the like. The slice run data includes: slice OAM data and/or slice non-OAM data; the slice service data may refer to data for evaluating the quality of a currently running slice, such as mean opinion score MOS data.

For example, table 2 is a corresponding relationship between slice service data and slice operation data, and as shown in table 2, when the service type of the terminal is changed from service 1 to service 2, the MOS score for evaluating the quality of the slice corresponding to the service changes, and the changed slice service data is obtained. Assuming that the MOS score of the slice 1 corresponding to the service 1 is 8 and the MOS score of the slice 2 corresponding to the service 2 is 10, it can be determined from the slice service data that the variation trend of the slice quality is improved. In addition, when the service type of the terminal is changed from service 1 to service 2, the corresponding slice is changed, and changed slice operation data is obtained. Assuming that the time delay measurement is performed on the slice 1 corresponding to the service 1, the obtained time delay is 5s, and the time delay measurement is performed on the slice 2 corresponding to the service 2, the obtained time delay is 3s, so that the variation trend of the slice performance can be determined to be continuously improved according to the slice operation data. Since the trend of variation of MOS scores for evaluating the slice quality and the trend of variation of slice performance are the same, it is true to determine slice run data.

TABLE 2

In practical application, in order to improve the accuracy of verifying the authenticity of the slice operation data, the authenticity of the slice operation data can be verified by combining the resource configuration data and the slice service data. If the change of the slice service data is consistent with the change trend of the slice operation data and the change of the resource configuration data is consistent with the change trend of the slice operation data, the slice operation data generated by a slice manager of an operator is true; otherwise, it indicates that the slicing operation data generated by the slicing manager of the operator is not real.

Based on this, in an embodiment, verifying authenticity of the slice operation data based on the resource configuration data and the slice service data includes:

Here, the fact that the mapping relationship between the resource allocation data and the slice operation data satisfies the preset relationship may mean that the slice operation data and the resource allocation data satisfy a positive correlation relationship, and specifically, the change trend of the slice performance represented by the slice operation data may be the same as the change trend of the wireless resource allocated to the slice represented by the resource allocation data. The fact that the mapping relationship between the slice service data and the slice operation data satisfies a preset relationship may mean that the slice operation data and the slice service data satisfy a positive correlation relationship, and specifically may mean that a variation trend of slice performance represented by the slice operation data is the same as a variation trend of MOS values represented by the slice service data.

Table 3 is, for example, a correspondence between resource configuration data, slice service data and slice operation data, as shown in table 3, it is assumed that the radio resource allocated to service 1 is timeslot 1, the radio resource allocated to service 2 is timeslot 1 and timeslot 2, the MOS score of slice 1 corresponding to service 1 is 8, the MOS score of slice 2 corresponding to service 2 is 10, the time delay measurement is performed on the slice 1 corresponding to the service 1, the obtained time delay is 5s, the time delay measurement is performed on the slice 2 corresponding to the service 2, the obtained time delay is 8s, thus, when the service type of the terminal is changed from the service 1 to the service 2, the change trend of the wireless resource can be determined to be increased according to the resource configuration data, the change trend of the slice quality can be determined to be improved according to the slice service data, and the change trend of the slice performance can be determined to be continuously reduced according to the slice operation data. Since the variation tendency of the radio resource and the variation tendency of the slice performance are different, and the variation tendency of the MOS score for evaluating the slice quality and the variation tendency of the slice performance are different, it is not true to determine the slice operation data.

TABLE 3

It should be noted that each node in the blockchain network can check the authenticity of the slice operation data issued by the operator to the blockchain network.

In practical applications, it is considered that the structure of the blockchain network may be a P2P structure, so that the third node may serve as the first node to send the resource configuration data and the slice operation data to the blockchain network for other nodes to check the authenticity of the slice operation data.

Based on this, in an embodiment, the method further comprises:

and the resource configuration data is used for the other nodes to verify the authenticity of the slice operation data, and when the slice operation data is verified to be real data, the verified slice service data is recorded and a consensus mechanism operation is executed.

In practical application, the structure of the blockchain network can be a P2P structure, so that the third node can serve as a second node to send the slice service data to the blockchain network for other nodes to check the authenticity of the slice operation data.

Based on this, in an embodiment, the method further comprises:

transmitting the slice service data to other nodes in the block chain network;

and when the slice data is verified to be real data, the verified slice service data is recorded and a consensus mechanism operation is executed.

In actual application, the third node may receive the resource configuration data and the slice operation data corresponding to the first node and the slice service data corresponding to the second node, and may also broadcast the data (the resource configuration data and the slice operation data) broadcast by the first node and/or the slice service data broadcast by the second node to other nodes, so that the other nodes perform authenticity check on the slice operation data.

Based on this, in an embodiment, the method further comprises:

transmitting the slice operation data and the resource configuration data broadcasted by the first node to other nodes except the first node and the second node in the block chain network; and/or the presence of a gas in the gas,

transmitting the slice service data broadcasted by the second node to other nodes except the first node and the second node in the block chain network;

and when the slice operation data is verified to be real, the verified slice operation data is recorded and a consensus mechanism operation is executed.

In actual application, when the third node verifies that the slice operation data is real, the third node may issue the verified real slice operation data to the block chain network, so that an application service provider corresponding to the second node determines whether the verified slice operation data meets the SLA requirements.

Based on this, in an embodiment, applied to the second node, the method further includes:

reading the verified slice running data from the blockchain network;

and judging whether the verified slice operation data meets the SLA requirements.

Here, the determining whether the verified slice operation data meets the SLA Requirement may refer to determining whether the verified slice operation data meets a Service Level Requirement (SLR) specified in an SLA contract.

It should be noted that, here, in addition to performing SLA requirement verification on the verified slice running data, one of the following operations may be performed:

after the second node reads the verified slice operation data from the blockchain network, settlement is carried out between the second node and the first node based on the read slice operation data;

and the second node performs post audit check based on the read slice operation data.

The second node performs post audit check on the read slice operation data, and when the detection is accurate, the second node can be provided for a third-party inquiry system to read the slice operation data.

If the hash value of the data is stored in the chain, the entity verifies whether the original data obtained from the data provider is correct according to the data hash in the read record.

In practical application, the operator and the application service provider can jointly sign an SLA contract, which specifies the SLA requirements that the slicing service provided by the operator should meet. Therefore, under the condition that the slicing operation data provided by the operator is real, the application service provider can further verify whether the slicing operation data provided by the operator meets the SLA requirement, so that the accuracy of verifying the SLA requirement is improved.

Based on this, in an embodiment, the determining whether the verified slice running data meets the SLA requirement includes:

Here, the SLA contract may refer to service terms of slicing arrangement, service area/time, and guarantee level agreed by the operator and the application service provider for the type of service provided.

Here, the SLA contract may be used for operators and application service providers to follow up on whether the sliced running data on the chain meets the requirements of the real data source. For example, it may be used to determine whether the signed SLA requirements are met.

Here, the service quality specified in the SLA contract may provide a platform for negotiating service prices and security levels between the operator (slicing service provider) and the application service provider (slicing tenant). For example, an operator may design a flexible contract framework containing multiple SLA terms, each with a corresponding service charge. In this way, slice tenants can enjoy superior quality of service at a high price range, and fall back to a next-level service level at a lower cost when needed. Therefore, the SLA compliance contract compliance issue between the slice renter and the network service provider (operator) is very important, on one hand, the operator needs to prove that different SLAs adopt different charging strategies according to the slice QoE condition, and obtain corresponding income through differentiated services; on the other hand, for application consumers, whether the SLA required by the service reaches the standard or not also needs to be known, and the basis of data credible support is needed.

Here, the SLA contracts may provide high quality slicing services for users in the 5G vertical industry. For operators, strict slice SLA management enables 5G networks to precisely control the quality of service of individual slices while serving a large number of industry applications. Efficient SLA management enables slicing to be fully automated, and meanwhile operation cost of slicing is reduced. Thus, operators will have the ability to offer customized bandwidth, latency, coverage and mobility capability 5G connectivity services to more vertical industries, creating a huge potential market. Slice tenants may also benefit from SLA guarantees. Thanks to the slice SLA guarantee architecture, digital interconnection of trillion-order sensors, robots, production lines and control centers will likely become a reality, and deterministic web services provided by 5G slices will bring subversive changes to daily operations and management of industry users in digital transformation. The slicing-enabled information sharing scale will be unprecedented, which will help slicing tenants in various industries simplify workflow and create additional business value in existing and emerging markets.

In practical application, after the terminal completes the slicing subscription, an SLA contract can be signed between the operator and the application service provider to ensure the quality of the slicing service. Considering that there may be a plurality of nodes corresponding to an operator in the blockchain network and a plurality of application service providers, an SLA contract may be generated by using signature information of a first node corresponding to a certain operator and signature information of a second node corresponding to a certain application service provider, and the generated SLA contract is issued to the blockchain network.

Based on this, in an embodiment, applied to the first node, before the reading of the SLA contract from the blockchain network, the method further includes:

Here, table 4 is an illustration of the first node issuing to an SLA contract in the blockchain network, in which the requirements for the guarantee level of the slicing service are clearly specified, as shown in table 4.

TABLE 4

In an example, as shown in fig. 4, in conjunction with the system architecture shown in fig. 1, a process for publishing data for verifying whether sliced running data is real to a blockchain network is described, including:

step 401: the first node publishes the slice operation data and the resource configuration data to a blockchain network.

Here, the first node refers to an operator node. The operator may be an operator providing a slice network, and is responsible for providing slice operation data such as OAM data and non-OAM data, participating in block chain consensus, and storing and viewing data on a chain.

Here, when the slice is instantiated and operated, the operator node signs the acquired slice operation data and broadcasts the signed slice operation data to other block chain nodes.

Step 402: and the second node issues the slice service data to the blockchain network.

Here, the second node refers to an application service provider node: the system refers to a vertical industry application service provider renting a slicing network, and is responsible for providing slicing service data such as MOS data, participating in block chain consensus, and storing and viewing the data on the chain.

Here, when the slice is instantiated and run, the application service provider node broadcasts the signed MOS data to other blockchain nodes.

Fig. 5 is a first process of verifying authenticity of slice operation data issued by an operator into a blockchain network, including:

step 501: receiving slice operation data and resource configuration data broadcast by a first node in a block chain network; and receiving the slicing service data broadcast by the second node in the block chain network.

Here, the first node characterizes an operator providing a slicing service. The second node characterizes an application service provider using the slice.

Here, after receiving the data broadcast by the first node and the second node, the third node may check whether the received data format is accurate, use the received data or the corresponding hash value as a record and stamp the record, use a consensus mechanism in the block chain to encapsulate the record obtained within a period of time into a new block and broadcast and release the encapsulated new block, so that other nodes in the block chain network verify the authenticity of the slice operation data provided by the operator.

Step 502: judging whether the mapping relation between the resource configuration data and the slice operation data meets a preset relation or not; when it is determined that the mapping relationship between the resource configuration data and the slice operation data satisfies the preset relationship, step 503 is executed.

Here, whether the mapping relationship between the resource allocation data and the slice operation data satisfies the preset relationship may refer to that the slice operation data and the resource allocation data satisfy a positive correlation relationship, and specifically includes one of the following:

the slice OAM data and the resource configuration data satisfy positive correlation;

positive correlation is satisfied between the slice non-OAM data and the resource configuration data;

the slice OAM data and the resource configuration data satisfy a positive correlation, and the slice non-OAM data and the resource configuration data satisfy a positive correlation.

Step 503: verifying that the slice run data is real slice run data; forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record.

Here, the performing of the consensus mechanism operation on the formed record may include:

encapsulating records formed within a period of time in a new block and broadcasting and issuing the new block to a block chain network; after receiving the new block, other nodes in the block chain network can verify whether the block and each recording format in the block are correct and complete, whether the block meets the requirement of a consensus mechanism, and if so, the new block is added into a block chain stored locally and forwarded; otherwise, the new block is discarded. And other nodes can also verify the authenticity of the data source of the record according to the relationship and decide whether to forward or discard the record. And writing an intelligent contract, writing the intelligent contract into the blockchain network if the verification strategy is met, and not writing the intelligent contract into the blockchain network if the verification strategy is not met.

Here, the performing a consensus mechanism operation on the formed record may further include:

signing the formed record and then sending the signed record to a specific node in a block chain network; after the specific node receives enough signed records, forwarding the received signed records to other specific nodes in the block chain network to generate blocks, and otherwise, discarding the blocks.

Here, the verified slice operation data, resource configuration data, and slice service data may also be formed into a record, and the consensus mechanism operation may be performed on the formed record. And then the method can be used for an operator or an application service provider to optimize the network management arrangement system of the operator or the application service provider by establishing a model.

Fig. 6 is a second process of verifying authenticity of slice operation data issued by an operator into a blockchain network, including:

step 601: receiving slice operation data and resource configuration data broadcast by a first node in a block chain network; and receiving the slicing service data broadcast by the second node in the block chain network.

Here, the first node characterizes an operator providing a slicing service. The second node characterizes an application service provider that uses the slice.

Step 602: judging whether the mapping relation between the slicing service data and the slicing operation data meets a preset relation or not; and when it is determined that the mapping relationship between the slice service data and the slice operation data satisfies the preset relationship, executing step 603.

Here, the fact that the mapping relationship between the slice service data and the slice operation data satisfies the preset relationship may mean that the mapping relationship between the slice operation data and the slice service data satisfies a positive correlation relationship, and specifically includes one of the following:

the positive correlation relation is satisfied between the slice OAM data and the MOS data;

positive correlation relation is satisfied between slice non-OAM data and MOS data;

the slice OAM data and the MOS data satisfy a positive correlation, and the slice non-OAM data and the MOS data satisfy a positive correlation.

Here, a positive correlation may be satisfied between part of the slice OAM data and the MOS data, or a positive correlation may be satisfied between all the slice OAM data and the MOS data.

Step 603: verifying that the slice run data is real slice run data; forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record.

Fig. 7 is a third process of verifying the authenticity of slice operation data issued by an operator into a blockchain network, including:

step 701: receiving slice operation data and resource configuration data broadcast by a first node in a block chain network; and receiving the slicing service data broadcast by the second node in the block chain network.

Step 702: judging whether the mapping relation between the resource configuration data and the slice operation data meets a preset relation or not; judging whether the mapping relation between the slice service data and the slice operation data meets the preset relation or not; when it is determined that the mapping relationship between the resource configuration data and the slice operation data satisfies the preset relationship, and the mapping relationship between the slice service data and the slice operation data satisfies the preset relationship, step 703 is executed.

Here, whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship may mean that the slice operation data and the resource configuration data satisfy a positive correlation relationship; the fact that the mapping relationship between the slice service data and the slice operation data satisfies the preset relationship means that the mapping relationship between the slice operation data and the slice service data satisfies a positive correlation relationship, which specifically includes one of the following:

the slice OAM data and the resource configuration data satisfy positive correlation, and the slice OAM data and the MOS data satisfy positive correlation;

the slice non-OAM data and the resource configuration data satisfy a positive correlation, and the slice non-OAM data and the MOS data satisfy a positive correlation.

Step 703: verifying that the slice run data is real slice run data; forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record.

Here, verifying the authenticity of slice operation data issued by an operator to a block chain network has the following advantages:

(1) an operator uploads slice operation data (such as slice OAM data and slice non-OAM data) and resource configuration data to a block chain network, and a vertical industry tenant (application service provider) uploads slice service data (such as MOS data) to the block chain network, so that other nodes in the block chain network can verify whether the slice operation data uploaded by the operator is real or not and store the slice operation data after the slice operation data is verified to be real.

(2) When a plurality of operators and a plurality of industry tenants form a coalition and participate in writing data on a chain together, multi-party authentication can be realized on the basis of the data, data counterfeiting of one operator is avoided, single-point fault risk can be reduced by improving reliability and consistency of storage and communication of slice operation data, and authenticity of a slice operation data source to a certain degree is improved.

(3) The verification of real slice operation data on the chain, resource configuration data on the chain and slice service data is a valuable analysis data source, and a subsequent operator can utilize the three data to optimize a network management and arrangement system of the operator by establishing a model.

In an example, as shown in fig. 8, in conjunction with the system architecture shown in fig. 1, a process for uploading an SLA contract for verifying SLA requirements to a blockchain network is described, including:

step 801: and the first node acquires first signature information corresponding to the first node and second signature information corresponding to the second node after the slice ordering is completed.

Here, the first node corresponds to an application service provider node.

Step 802: the first node carries out signature processing on the SLA contract based on the first signature information and the second signature information to obtain the SLA contract after signature processing;

here, the SLA contract is a contract that the slicing service agreed between the operator and the application service provider should satisfy SLA requirements.

Step 803: and the first node issues the SLA contract after signature processing to the block chain network.

Here, after the slicing store completes ordering a slice, the application service provider node adds a timestamp to the verified SLA contract signed by both parties, and issues the SLA contract to the blockchain network.

Fig. 9 is a process of SLA requirement verification by the second node on verified real sliced operational data, including:

step 901: and the second node reads the SLA contract from the blockchain network and reads the verified slice operation data.

Step 902: the second node judges whether the verified slice operation data meets the SLA requirement or not by utilizing an SLA contract; when the verified slice run data meets the SLA requirements, step 903 is performed.

Step 903: and the second node forms a record of the slice operation data meeting the SLA requirement and saves the record in a new block.

Here, the operator issues the SLA contract signed with the application service provider to the blockchain network, which has the following advantages:

(1) and the application service provider in the vertical industry performs uplink verification and storage on the signed SLA contract, and the uplink data has the characteristics of high reliability, incapability of being tampered, strong safety, irreversible time sequence and the like, so that the whole-process traceability of the data can be realized. On the basis of the evidence storage data, whether the slice meets SLA requirements can be self-proved, judged and chased.

(2) The reliability and consistency of the slice SLA contracts in storage and communication are improved.

(3) In the face of personalized slice subscription (lease of network resources) of numerous OTTs or virtual operators, repeated negotiation of SLA parameters and prices cannot be avoided, but intelligent contracts with the help of block chains can realize automation of simple and repeated negotiation processes, and meanwhile, efficiency can be remarkably improved in the aspect of automatic execution of protocols related to a plurality of slice lease services. Execution and evaluation of the associated SLAs is more efficient as both parties negotiate QoS levels and prices to become parameters of the intelligent contract.

By adopting the technical scheme of the embodiment of the invention, the operator uploads the slice operation data and the resource configuration data to the blockchain network, and the application service provider uploads the slice service data to the blockchain network, so that other nodes in the blockchain network can verify whether the slice operation data uploaded by the operator is real and effective, and a subsequent application service provider can acquire the real slice operation data provided by the operator.

In order to implement the data processing method based on the blockchain network according to the embodiment of the present invention, an embodiment of the present invention further provides a data processing apparatus based on the blockchain network, and fig. 10 is a schematic structural diagram of the data processing apparatus based on the blockchain network according to the embodiment of the present invention; as shown in fig. 10, the apparatus includes:

a receiving unit 101, configured to receive slice operation data and resource configuration data broadcast by a first node in a block chain network; the first node characterizes an operator providing slicing services; receiving slicing service data broadcast by a second node in the block chain network; the second node characterizes an application service provider using the slice;

a first processing unit 102, configured to verify authenticity of the slice operation data based on the resource configuration data and/or the slice service data;

a second processing unit 103, configured to form a record with the verified slice running data when the slice running data is verified to be real slice running data; and performs a consensus mechanism operation on the formed record.

Furthermore, according to at least one embodiment of the present invention, the first processing unit 102 is specifically configured to:

reading SLA contracts from the blockchain network;

Furthermore, in accordance with at least one embodiment of the present invention, before the reading of the SLA contract from the blockchain network, the apparatus further includes:

transmitting the slice service data to other nodes in the block chain network;

In practical application, the receiving unit 101 and the sending unit may be implemented by a communication interface in a data processing apparatus based on a block chain network; the first processing unit 102, the second processing unit 103, the determining unit and the issuing unit may be implemented by a processor in a data processing apparatus based on a blockchain network.

It should be noted that: in the data processing apparatus based on the blockchain network according to the embodiment, when the prediction based on the transmission power is performed, only the division of the program modules is illustrated, and in practical applications, the processing may be distributed to different program modules according to needs, that is, the internal structure of the apparatus is divided into different program modules to complete all or part of the processing described above. In addition, the data processing apparatus based on the block chain network provided in the foregoing embodiment and the prediction method embodiment based on the transmission power belong to the same concept, and specific implementation processes thereof are described in the method embodiment and are not described herein again.

An embodiment of the present invention further provides an electronic device, as shown in fig. 11, including:

a communication interface 111 capable of performing information interaction with other devices;

and the processor 112 is connected with the communication interface 111 and is used for executing the method provided by one or more technical schemes of the intelligent device side when running a computer program. And the computer program is stored on the memory 103.

It should be noted that: the specific processing procedures of the processor 112 and the communication interface 111 are detailed in the method embodiment, and are not described herein again.

Of course, in practice, the various components in the electronic device 110 are coupled together by the bus system 114. It is understood that the bus system 114 is used to enable connected communication between these components. The bus system 114 includes, in addition to a data bus, a power bus, a data processing bus based on a blockchain network, and a status signal bus. For clarity of illustration, the various buses are designated as bus system 104 in fig. 10.

The memory 103 in the embodiment of the present application is used to store various types of data to support the operation of the terminal 100. Examples of such data include: any computer program for operating on the terminal 100.

The method disclosed in the embodiments of the present application can be applied to the processor 102, or implemented by the processor 102. The processor 102 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 112. The processor 112 described above may be a general purpose processor, a digital data processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 112 may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the memory 113, and the processor 112 reads the information in the memory 113 and performs the steps of the aforementioned methods in conjunction with its hardware.

In an exemplary embodiment, the electronic device 110 may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, data processors based on a block-chain network, data processors based on a micro block-chain network (MCUs), microprocessors (microprocessors), or other electronic elements for performing the aforementioned methods.

It will be appreciated that the memory (memory 113) of embodiments of the present application may be either volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. Among them, the nonvolatile memory may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a magnetic random access memory (FRAM), a flash memory (flash memory), a magnetic surface memory, an optical disc, or a compact disc read only memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. The volatile memory may be a Random Access Memory (RAM) which serves as an external cache. By way of illustration and not limitation, many forms of RAM are available, such as 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), double-data-rate synchronous dynamic random access memory (ddr SDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synchronous Dynamic Random Access Memory (SDRAM), Synchronous Linked Dynamic Random Access Memory (SLDRAM), direct memory bus access memory (dma), and direct memory access memory (dma). The memories described in the embodiments of the present application are intended to comprise, without being limited to, these and any other suitable types of memory.

In an exemplary embodiment, the embodiment of the present invention further provides a storage medium, specifically a computer-readable storage medium, for example, a memory 113 storing a computer program, which is executable by a processor 112 of an electronic device 110 to perform the steps of the aforementioned data processing server-side method based on a blockchain network. The computer readable storage medium may be memory such as FRAM, ROM, PROM, EPROM, EEPROM, FlashMemory, magnetic surface memory, optical disk, or CD-ROM.

It should be noted that: "first," "second," and the like are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

In addition, the technical solutions described in the embodiments of the present invention may be arbitrarily combined without conflict.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A data processing method based on a block chain network is characterized by comprising the following steps:

when the slice operation data are verified to be real slice operation data, forming a record of the verified slice operation data; and performs a consensus mechanism operation on the formed record.

2. The method of claim 1, wherein verifying authenticity of the slice run data based on the resource configuration data comprises:

and when the mapping relation between the resource configuration data and the slice operation data is determined to meet the preset relation, verifying that the slice operation data is real slice operation data.

3. The method of claim 1, wherein verifying authenticity of the slice run data based on the slice traffic data comprises:

4. The method of claim 1, wherein verifying authenticity of the slice operational data based on the resource configuration data and slice traffic data comprises:

5. The method according to any of claims 1 to 4, applied to the second node, further comprising:

reading the verified slice running data from the blockchain network;

6. The method of claim 5, wherein the determining whether the verified sliced operational data meets the requirements of a service assurance level agreement (SLA) comprises:

reading SLA contracts from the blockchain network;

7. The method of claim 6, applied to the first node, before reading the SLA contract from the blockchain network, the method further comprising:

8. The method of claim 1, further comprising:

transmitting slice operation data and resource configuration data to other nodes except the first node and the second node in the block chain network;

9. The method of claim 1, further comprising:

transmitting the slice service data to other nodes in the block chain network;

10. A data processing apparatus based on a blockchain network, comprising:

the receiving unit is used for receiving slice operation data and resource configuration data broadcast by a first node in a block chain network; the first node characterizes an operator providing slicing services; receiving slicing service data broadcast by a second node in the block chain network; the second node characterizes an application service provider using the slice;

the second processing unit is used for forming a record of the verified slice operation data when the slice operation data is verified to be real slice operation data; and performs consensus mechanism operations on the formed records.

11. An electronic device, comprising:

12. An electronic device comprising a processor and a memory for storing a computer program capable of running on the processor,

wherein the processor is adapted to perform the steps of the method of any one of claims 1 to 9 when running the computer program.

13. A storage medium having a computer program stored thereon, the computer program, when being executed by a processor, realizing the steps of the method according to any of the claims 1 to 9.