Data processing method, device, equipment and storage medium based on blockchain network
Verify the data between the operator and the application service provider through the blockchain network, ensure the authenticity of the slice operation data, solve the problem of difficult data authenticity in network slice management, and realize the trust of both parties and network slice service. Transparency and reliability.
Patent Information
- Application Number
- CN202011376575.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-11-30
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2040-11-30
AI Technical Summary
In network slicing management, the slice operation data sent by the operator is difficult to ensure its authenticity, resulting in the application service provider being unable to accurately evaluate the quality of the network slicing and the operator being unable to prove its innocence.
Using a blockchain network-based data processing method, the resource configuration data and business data between operators and application service providers are received and verified, and the consensus mechanism is used to ensure the authenticity of the slice operation data, and the verified data is recorded. On the blockchain.
It realizes trust between operators and application service providers, ensures the authenticity and credibility of slice operation data, and improves the transparency and reliability of network slice services.
Smart Images

Figure CN114585049B_ABST
Abstract
Description
Technical Field
[0001] 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 blockchain network. Background Art
[0002] With the rapid development of terminal technology, terminals support more and more types of services. In order to meet the network communication needs of different types of services, operators can reorganize network resources to obtain multiple network slices. In this way, application service providers can use these network slices to provide application services to terminals. Generally, in the process of providing services to terminals through network slicing, slice operation data is generated in the operator's slice manager. In order to facilitate the application service provider to view the slice operation data, the operator can send the generated slice operation data to the application service provider. However, how to ensure that the slice operation data sent by the operator is authentic and reliable, and how to achieve mutual trust between the two parties have become key technical issues. Summary of the Invention
[0003] In view of this, embodiments of the present invention hope to provide a data processing method, apparatus, device and storage medium based on a blockchain network.
[0004] The technical solution of the embodiment of the present invention is achieved as follows:
[0005] At least one embodiment of the present invention provides a data processing method based on a blockchain network, the method comprising:
[0006] Receive slice operation data and resource configuration data broadcast by a first node in the blockchain network; the first node represents the operator providing slice services; and receive slice business data broadcast by a second node in the blockchain network; the second node represents the application service provider using the slice;
[0007] Verify the authenticity of the slice operation data based on the resource configuration data and / or the slice service data;
[0008] When it is verified that the slice operation data is authentic slice operation data, the verified slice operation data is recorded; and a consensus mechanism operation is performed on the formed record.
[0009] Furthermore, according to at least one embodiment of the present invention, verifying the authenticity of the slice operation data based on the resource configuration data includes:
[0010] Determining whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship;
[0011] When it is determined that the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship, it is verified that the slice operation data is real slice operation data.
[0012] In addition, according to at least one embodiment of the present invention, verifying the authenticity of the slice operation data based on the slice service data includes:
[0013] Determine whether the mapping relationship between the slice service data and the slice operation data satisfies a preset relationship;
[0014] When it is determined that the mapping relationship between the slice business data and the slice operation data satisfies a preset relationship, it is verified that the slice operation data is real slice operation data.
[0015] In addition, according to at least one embodiment of the present invention, verifying the authenticity of the slice operation data based on the resource configuration data and the slice service data includes:
[0016] Determine whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship; and determine whether the mapping relationship between the slice service data and the slice operation data satisfies the preset relationship;
[0017] 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 business data and the slice operation data satisfies the preset relationship, it is verified that the slice operation data is real slice operation data.
[0018] Furthermore, according to at least one embodiment of the present invention, applied to the second node, the method further includes:
[0019] Reading the verified slice operation data from the blockchain network;
[0020] Determine whether the verified slice operation data meets the service level agreement (SLA) requirements.
[0021] In addition, according to at least one embodiment of the present invention, determining whether the verified slice operation data meets the SLA requirements includes:
[0022] Reading the SLA contract from the blockchain network;
[0023] Use the SLA contract to determine whether the verified slice operation data meets the SLA requirements.
[0024] Furthermore, according to at least one embodiment of the present invention, applied to the first node, before reading the SLA contract from the blockchain network, the method further includes:
[0025] When the slice ordering is completed, obtain the first signature information corresponding to the first node and the second signature information corresponding to the second node;
[0026] Based on the first signature information and the second signature information, the SLA contract is signed to obtain a signed SLA contract; the SLA contract is a contract reached between the operator and the application service provider, which stipulates that the slice service should meet the SLA requirements;
[0027] The signed SLA contract is published to the blockchain network.
[0028] Furthermore, according to at least one embodiment of the present invention, the method further comprises:
[0029] Sending the slice operation data and resource configuration data to other nodes in the blockchain network except the first node and the second node;
[0030] Among them, 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 authentic data, the verified slice operation data is recorded and the consensus mechanism operation is performed.
[0031] Furthermore, according to at least one embodiment of the present invention, the method further comprises:
[0032] Sending slice business data to other nodes in the blockchain network;
[0033] Among them, the slice business data is used for the other nodes to verify the authenticity of the slice operation data, and when the slice data is verified to be authentic data, the verified slice operation data is recorded and the consensus mechanism operation is performed.
[0034] At least one embodiment of the present invention provides a data processing device based on a blockchain network, comprising:
[0035] A receiving unit is configured to receive slice operation data and resource configuration data broadcast by a first node in a blockchain network; the first node represents an operator providing slice services; and receive slice service data broadcast by a second node in the blockchain network; the second node represents an application service provider using the slice;
[0036] A first processing unit, configured to verify the authenticity of the slice operation data based on the resource configuration data and / or the slice service data;
[0037] The second processing unit is used to record the verified slice operation data when verifying that the slice operation data is true slice operation data; and perform consensus mechanism operations on the formed record.
[0038] Furthermore, according to at least one embodiment of the present invention, the first processing unit is specifically configured to:
[0039] Determine whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship; when it is determined that the mapping relationship between the resource configuration data and the slice operation data satisfies the preset relationship, verify that the slice operation data is real slice operation data.
[0040] Furthermore, according to at least one embodiment of the present invention, the first processing unit is specifically configured to:
[0041] Determine whether the mapping relationship between the slice business data and the slice operation data satisfies a preset relationship; when it is determined that the mapping relationship between the slice business data and the slice operation data satisfies the preset relationship, verify that the slice operation data is real slice operation data.
[0042] Furthermore, according to at least one embodiment of the present invention, the first processing unit is specifically configured to:
[0043] Determine whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship; and determine whether the mapping relationship between the slice business data and the slice operation data satisfies the preset relationship; 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 business data and the slice operation data satisfies the preset relationship, verify that the slice operation data is real slice operation data.
[0044] Furthermore, according to at least one embodiment of the present invention, applied to the second node, the apparatus further includes:
[0045] A judgment unit is used to read the verified slice operation data from the blockchain network; and judge whether the verified slice operation data meets the SLA requirements.
[0046] Furthermore, according to at least one embodiment of the present invention, the determining unit is specifically configured to:
[0047] Read the SLA contract from the blockchain network; use the SLA contract to determine whether the verified slice operation data meets the SLA requirements.
[0048] Furthermore, according to at least one embodiment of the present invention, applied to the first node, the apparatus further includes:
[0049] A publishing unit is used to obtain the first signature information corresponding to the first node and the second signature information corresponding to the second node after the slice order is completed; based on the first signature information and the second signature information, the SLA contract is signed to obtain the signed SLA contract; the SLA contract is a contract reached between the operator and the application service provider, which stipulates that the slice service should meet the SLA requirements; and the signed SLA contract is published to the blockchain network.
[0050] Furthermore, according to at least one embodiment of the present invention, the apparatus further comprises:
[0051] A sending unit, configured to send the slice operation data and resource configuration data to other nodes in the blockchain network except the first node and the second node;
[0052] Among them, 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 authentic data, the verified slice operation data is recorded and the consensus mechanism operation is performed.
[0053] In addition, according to at least one embodiment of the present invention, the sending unit is further configured to:
[0054] Sending slice business data to other nodes in the blockchain network;
[0055] Among them, the slice business data is used for the other nodes to verify the authenticity of the slice operation data, and when the slice data is verified to be authentic data, the verified slice operation data is recorded and the consensus mechanism operation is performed.
[0056] At least one embodiment of the present invention provides an electronic device, including:
[0057] A communication interface for receiving slice operation data and resource configuration data broadcast by a first node in a blockchain network; the first node represents an operator providing slice services; and receiving slice service data broadcast by a second node in the blockchain network; the second node represents an application service provider using the slices;
[0058] A processor is used to verify the authenticity of the slice operation data based on the resource configuration data and / or the slice business data; and when it is verified that the slice operation data is authentic slice operation data, record the verified slice operation data; and perform consensus mechanism operations on the formed record.
[0059] At least one embodiment of the present invention provides an electronic device including a processor and a memory for storing a computer program that can be run on the processor.
[0060] The processor is configured to execute the steps of any of the above methods when running the computer program.
[0061] At least one embodiment of the present invention provides a storage medium having a computer program stored thereon, wherein the computer program implements the steps of any of the above methods when executed by a processor.
[0062] The data processing method, apparatus, device, and storage medium based on a blockchain network provided by an embodiment of the present invention receive slice operation data and resource configuration data broadcast by a first node in the blockchain network; the first node represents the operator providing the slice service; and receive slice service data broadcast by a second node in the blockchain network; the second node represents the application service provider using the slice; based on the resource configuration data and / or the slice service data, verify the authenticity of the slice operation data; when the slice operation data is verified to be authentic slice operation data, record the verified slice operation data; and perform a consensus mechanism operation on the record. Using the technical solution provided by the embodiment of the present invention, the operator uploads slice operation data and resource configuration data to the blockchain network, and the application service provider uploads slice service data to the blockchain network. In this way, other nodes in the blockchain network can verify whether the slice operation data uploaded by the operator is authentic and trustworthy, and the application service provider can subsequently obtain the authentic slice operation data provided by the operator, thereby achieving mutual trust between the two parties. BRIEF DESCRIPTION OF THE DRAWINGS
[0063] Figure 1 This is a schematic diagram of the slice manager on the operator side managing slice operation data;
[0064] Figure 2 This is a schematic diagram of the system architecture of the data processing method based on the blockchain network according to an embodiment of the present invention;
[0065] Figure 3 This is a schematic diagram of the implementation process of the data processing method based on the blockchain network provided by an embodiment of the present invention;
[0066] Figure 4 This is a schematic diagram of the implementation process of publishing data used to verify whether slice operation data is authentic to the blockchain network in an embodiment of the present invention;
[0067] Figure 5 This is a schematic diagram of the first implementation process of verifying the authenticity of slice operation data published by the operator to the blockchain network in an embodiment of the present invention;
[0068] Figure 6 This is a schematic diagram of the second implementation process of verifying the authenticity of slice operation data published by the operator to the blockchain network in an embodiment of the present invention;
[0069] Figure 7 This is a schematic diagram of the third implementation process of verifying the authenticity of slice operation data published by the operator to the blockchain network in an embodiment of the present invention;
[0070] Figure 8 1. It is a schematic diagram of an implementation process of uploading an SLA contract for verifying SLA requirements to a blockchain network according to an embodiment of the present invention;
[0071] Figure 9 This is a schematic diagram of the implementation process of the second node in an embodiment of the present invention performing SLA requirement verification on the verified real slice operation data;
[0072] Figure 10 This is a schematic diagram of the structure of a data processing device based on a blockchain network provided by an embodiment of the present invention;
[0073] Figure 11 It is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0074] Before introducing the technical solutions of the embodiments of the present invention, the relevant technologies are first described.
[0075] In related technologies, network slicing (NS) has been introduced in 5G mobile communication systems, enabling customized and dedicated network services to be provided to different industries based on shared physical infrastructure. This changes the single 4G network model and creates a 5G network that supports function customization, security and resource isolation, and topology optimization to meet the needs of specific goals, specific service categories, and even specific customers. Based on network slicing, operators can expand their services from traditional voice and data to the Internet of Everything, forming a new business model; they can transform from traditional communications providers to platform providers, and through the operation of network slicing, they can provide vertical industries with a platform for experimentation, deployment, and management, and even provide end-to-end services. Operators can sell network slices through B2B and B2B2C methods, allowing mobile virtual network operators, OTT manufacturers, and vertical industry users to dynamically rent slice resources from telecom operators as needed. Figure 1 This is a schematic diagram of the slice manager on the operator side managing slice operation data in the related technology, such as Figure 1As shown in the figure, taking the 5G communication system as an example, the network data analysis function (NWDAF) on the operator side is used to receive and store network data provided by the slice manager and core network corresponding to the service. After the slice creation phase, the slice manager is used to continuously evaluate the SLA compliance of the slices in operation; based on the inferred SLA compliance, it updates the GSRR and MSRR configuration parameters to the radio access network (RAN) subdomain from time to time, and sends the refreshed core network (CN) resource configuration to the slice control plane.
[0076] To sum up, in the related technology, the slice manager on the operator side collects slice operation data and evaluates whether the slice operation data meets the SLA requirements to adjust resource investment, thereby achieving a good balance between slice service cost and performance. However, it is not open to application service providers (tenants) as data supporting evidence of the quality of the slice service provided. That is to say, when the operator sends the slice operation data to the application service provider, there may be important concealment, or even modification and falsification of data (data source, storage, and communication process may change), making it difficult to trace the problem. The application service provider cannot correctly evaluate the quality of the network slice provided by the operator, and the operator cannot prove its innocence.
[0077] 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 represents the operator providing slice services; and slice business data broadcast by a second node in the blockchain network is received; the second node represents the application service provider using the slice; based on the resource configuration data and / or the slice business data, the authenticity of the slice operation data is verified; when it is verified that the slice operation data is authentic slice operation data, the verified slice operation data is recorded; and a consensus mechanism operation is performed on the formed record.
[0078] The present invention will be described in further detail below with reference to the accompanying drawings and embodiments.
[0079] The nouns and terms involved in the embodiments of the present invention are explained. The nouns and terms involved in the embodiments of the present invention are subject to the following interpretations.
[0080] 1) Transaction, equivalent to the computer term "transaction," does not refer solely to transactions in a business context. Given the conventional use of the term "transaction" in blockchain technology, the embodiments of the present invention follow this convention. In a blockchain network based on an account model, transactions include three different transaction types: Deploy, Invoke, and Query. Deploy transactions are used to install a specified chaincode on a node in the blockchain network. Invoke and Query transactions are used to invoke the deployed chaincode to perform operations on the relevant data of the target account in the ledger, including add, delete, query, and modify operations to modify the key-value pair data in the account, or to add new accounts to the ledger.
[0081] 2) Block: A data structure that records the ledger data updated by exchanges over a period of time. It is marked with a timestamp and a unique identifier of the previous block (such as a digital fingerprint). After the block is verified by consensus among nodes in the blockchain network, it will be appended to the end of the blockchain as a new block.
[0082] 3) Blockchain: A chain data structure composed of sequentially connected blocks. Each block references the hash value of the previous block or its subset, thereby ensuring the tamper-proof and anti-forgery of recorded transactions through cryptographic methods.
[0083] 4) Blockchain network, a collection of decentralized nodes that incorporate new blocks into the blockchain through consensus.
[0084] 5) Ledger: The sum of data recorded in the blockchain network in the account dimension, including elements such as ledger data, ledger status, ledger status proof, and block index.
[0085] 6) Ledger data, the actual block data storage, is a series of orderly and tamper-proof transaction records recorded in the blockchain, which can be expressed in the form of files in the file system. When the smart contract called in the transaction is executed, the account / account data is updated.
[0086] 7) Ledger state, also known as state data, refers to the state of the ledger data, which can be expressed as key-value pairs in the database. The real-time ledger state is used to represent the latest record of the key-value pairs updated by the consensus exchange, and the historical ledger state is used to represent the historical record of the key-value pairs.
[0087] 8) Proof of existence is a cryptographic proof of the authenticity of ledger data, for example, by calculating a Merkle tree of ledger data.
[0088] 9) Consensus is a process in a blockchain network used to reach agreement on transaction results among multiple nodes involved. Mechanisms for achieving consensus include PoW, PoS, Delegated Proof-of-Stake (DPoS), and Proof of Elapsed Time (PoET).
[0089] 10) Smart Contracts, also known as chaincode, are programs deployed in the blockchain network that are triggered to execute according to conditions. They are used to operate the ledger by querying, adding, and modifying to query or update the ledger.
[0090] Figure 2 This is a schematic diagram of the system architecture of the data processing method based on the blockchain network according to the embodiment of the present invention. Figure 2 As shown, the system includes:
[0091] The first node is used to broadcast slice operation data and resource configuration data in the blockchain network;
[0092] The second node is used to broadcast slice business data in the blockchain network;
[0093] The third node (not shown in the figure) is used to receive the slice operation data and resource configuration data broadcast by the first node in the blockchain network; and receive the slice business data broadcast by the second node in the blockchain network; based on the resource configuration data and / or the slice business data, verify the authenticity of the slice operation data; when it is verified that the slice operation data is true slice operation data, record the verified slice operation data; and execute consensus mechanism operations on the formed record.
[0094] Here, it should be noted that the first node corresponds to the operator providing slicing services, the second node corresponds to the application service provider using the slices, and the third node can correspond to other devices other than the operator and application service provider, or can correspond to the operator or application service provider. Figure 1 The operator node 1 to the operator node m in all correspond to the first node, and the application service provider node 1 to the application service provider node n all correspond to the second node.
[0095] Figure 3 This is a flowchart of a data processing method based on a blockchain network provided by an embodiment of the present invention, which is applied to the third node and combined with Figure 2 The system architecture diagram shown in the figure shows Figure 2 The implementation process, such as Figure 3 As shown, the method includes:
[0096] Step 301: Receive slice operation data and resource configuration data broadcast by a first node in the blockchain network; the first node represents the operator providing slice services; and receive slice service data broadcast by a second node in the blockchain network; the second node represents the application service provider using the slice;
[0097] Step 302: Verify the authenticity of the slice operation data based on the resource configuration data and / or the slice service data;
[0098] Step 303: When it is verified that the slice operation data is authentic slice operation data, the verified slice operation data is recorded; and a consensus mechanism operation is performed on the recorded data.
[0099] Here, in step 301, in actual application, the operator can use the slice manager to reorganize network resources such as access network and core network resources to obtain multiple network slices, and use the obtained network slices to provide slice services to the terminal. In the process of reorganizing network resources, resource configuration data such as access network and core network resource data will be generated; in the process of providing slice services to the terminal, slice operation data such as operation, administration and maintenance (OAM) data and non-OAM data will be generated. Application service providers can also use network slices to provide slice services to terminals. In the process of providing slice services to terminals, slice service data such as mean subjective opinion score (MOS) data can be generated by obtaining user feedback on the slice service.
[0100] Here, in actual application, if the authenticity of the slice operation data can be guaranteed, the quality of the slice service provided to the terminal can be guaranteed. In this way, it is necessary to verify the authenticity of the slice operation data provided by the operator. In order to avoid relying solely on the data provided by the operator to verify the authenticity of the slice operation data, the slice operation data can be effectively verified in combination with the slice service data provided by the application service provider. Considering that the blockchain network has a highly reliable regulatory function, a blockchain network can be constructed by multiple operator nodes and multiple application service providers. After the operator node generates slice operation data and resource configuration data, the slice operation data and resource configuration data can be uploaded to the blockchain network. After the application service provider node generates slice service data, the slice service data can be uploaded to the blockchain network. Through the broadcast mechanism of the blockchain network, these three data are received by each node in the blockchain network. Subsequently, each of the nodes can use the resource configuration data and / or slice service data to verify the authenticity of the slice operation data.
[0101] Here, in step 302, in actual application, if the actual resources provided for the terminal for slicing service are consistent with the resources required for slice operation, it indicates that the slice operation data is authentic. In this way, the resource configuration data generated by the operator can be used to verify the authenticity of the slice operation data generated by the operator; if the score for evaluating the slice service quality is consistent with the service quality provided by the slice operation, it indicates that the slice operation data is authentic. In this way, the slice business data generated by the application service provider can be used to verify the authenticity of the slice operation data generated by the operator.
[0102] The following describes in detail the process of verifying the authenticity of the slice operation data provided by the operator.
[0103] In actual applications, operators can reorganize network resources, such as access networks and core networks, to obtain multiple network slices. They can then allocate corresponding radio resources, such as time slots and spectrum, to each of these multiple network slices, thereby generating resource configuration data. During slice operation, operators can use the slice manager to perform routine operations, management, and maintenance on the slices, thereby generating slice OAM data, which is used as slice operation data. Alternatively, operators can use the slice manager to perform other management tasks on the slices, thereby generating slice non-OAM data, which is used as slice operation data. In actual applications, the radio resources corresponding to network slices can be updated to meet the needs of different terminal services. This will cause changes in the resource configuration data generated by the operator's slice manager. When terminals perform different types of services, the corresponding slices will change, which will also cause changes in the slice operation data generated by the operator's slice manager. If the changes in resource configuration data align with the trends in the slice operation data, the slice operation data generated by the operator's slice manager is authentic. Otherwise, the slice operation data generated by the operator's slice manager is not authentic.
[0104] Based on this, in one embodiment, verifying the authenticity of the slice operation data based on the resource configuration data includes:
[0105] Determine whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship; when it is determined that the mapping relationship between the resource configuration data and the slice operation data satisfies the preset relationship, verify that the slice operation data is real slice operation data.
[0106] Here, the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship, which may mean that the slice operation data and the resource configuration data satisfy a positive correlation relationship, specifically, it may mean that the changing trend of the slice performance represented by the slice operation data and the changing trend of the wireless resources allocated to the slice represented by the resource configuration data are the same.
[0107] Here, the positive correlation may include: a linear increase relationship, an exponential increase relationship, etc. The slice operation data includes: slice OAM data and / or slice non-OAM data; the resource configuration data may refer to wireless resource data allocated to the network slice currently used by the terminal.
[0108] 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 includes: virtualization resource utilization, number of registered users of the network and network slice instances, 5G network end-to-end latency, network and network slice instance uplink / downlink throughput, etc. The slice non-OAM data includes: QoS flow level, UE level and even service level data input from the core network. The resource configuration data refers to the access network core network resource update data issued by the slice manager based on the satisfaction of the SLA, such as guaranteed slice radio resources (GSRR) and maximum slice radio resources (MSRR). It can also include slice SLA signing information.
[0109] For example, Table 1 shows the correspondence between resource configuration data and slice operation data. As shown in Table 1, when a terminal's service type changes from service 1 to service 2, the corresponding radio resources for the slice are updated, resulting in the changed resource configuration data. Assuming that the radio resource allocated to service 1 is timeslot 1, and the radio resources allocated to service 2 are timeslots 1 and 2, the resource configuration data indicates an increasing trend in radio resource usage. Furthermore, when a terminal's service type changes from service 1 to service 2, the corresponding slice changes, resulting in changed slice operation data. Assuming that the latency measurement for slice 1 corresponding to service 1 is 5 seconds, and the latency measurement for slice 2 corresponding to service 2 is 3 seconds, the slice operation data indicates an improving trend in slice performance. Since the trends in radio resource usage and slice performance are identical, the slice operation data can be confirmed to be authentic.
[0110]
[0111] Table 1
[0112] In actual applications, operators can reorganize network resources such as access networks and core networks to obtain multiple network slices. During the operation of the slices, operators can use the slice manager to perform daily operations, management, and maintenance on the slices, thereby generating slice OAM data and using the slice OAM data as slice operation data; and / or operators can use the slice manager to perform other management on the slices, thereby generating slice non-OAM data and using the slice non-OAM data as slice operation data. During the operation of the slices, application service providers can evaluate the quality of the slices, thereby generating slice service data.
[0113] In actual applications, when a terminal performs different types of services, the slices corresponding to the services will change. In this way, the slice operation data generated by the operator's slice manager will change, and the slice service data generated by the application service provider will change. If the change in slice service data is consistent with the change trend of slice operation data, it indicates that the slice operation data generated by the operator's slice manager is authentic; otherwise, it indicates that the slice operation data generated by the operator's slice manager is not authentic.
[0114] Based on this, in one embodiment, verifying the authenticity of the slice operation data based on the slice service data includes:
[0115] Determine whether the mapping relationship between the slice service data and the slice operation data satisfies a preset relationship;
[0116] When it is determined that the mapping relationship between the slice business data and the slice operation data satisfies a preset relationship, it is verified that the slice operation data is real slice operation data.
[0117] Here, the mapping relationship between the slice business data and the slice operation data satisfies the preset relationship, which may mean that the slice operation data and the slice business data satisfy a positive correlation relationship, specifically, it may mean that the changing trend of the slice performance represented by the slice operation data and the changing trend of the MOS value represented by the slice business data are the same.
[0118] Here, the positive correlation may include: a linear increase relationship, an exponential increase relationship, etc. The slice operation data includes: slice OAM data and / or slice non-OAM data; the slice service data may refer to data for evaluating the quality of the currently running slice, such as mean subjective opinion score (MOS) data.
[0119] For example, Table 2 shows the correspondence between slice service data and slice operation data. As shown in Table 2, when the terminal's service type changes from Service 1 to Service 2, the MOS score for evaluating the quality of the slice corresponding to the service changes, resulting in the changed slice service data. Assume that the MOS score for slice 1 corresponding to Service 1 is 8, and the MOS score for slice 2 corresponding to Service 2 is 10. Based on the slice service data, it can be determined that the slice quality trend is improving. Furthermore, when the terminal's service type changes from Service 1 to Service 2, the corresponding slice changes, resulting in the changed slice operation data. Assume that the latency measurement for slice 1 corresponding to Service 1 is 5 seconds, and the latency measurement for slice 2 corresponding to Service 2 is 3 seconds. Based on the slice operation data, it can be determined that the slice performance trend is continuously improving. Since the MOS score trend for evaluating slice quality and the slice performance trend are the same, the slice operation data is confirmed to be authentic.
[0120]
[0121] Table 2
[0122] In actual application, in order to improve the accuracy of verifying the authenticity of slice operation data, the authenticity of slice operation data can be verified by combining resource configuration data and slice service data. If the change of slice service data is consistent with the change trend of slice operation data, and the change of resource configuration data is consistent with the change trend of slice operation data, it indicates that the slice operation data generated by the operator's slice manager is authentic; otherwise, it indicates that the slice operation data generated by the operator's slice manager is not authentic.
[0123] Based on this, in one embodiment, verifying the authenticity of the slice operation data based on the resource configuration data and the slice service data includes:
[0124] Determine whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship; and determine whether the mapping relationship between the slice business data and the slice operation data satisfies the preset relationship; 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 business data and the slice operation data satisfies the preset relationship, verify that the slice operation data is real slice operation data.
[0125] Here, the mapping relationship between the resource configuration data and the slice operation data satisfies the preset relationship, which may mean that the slice operation data and the resource configuration data satisfy a positive correlation relationship, specifically, it may mean that the changing trend of the slice performance represented by the slice operation data and the changing trend of the wireless resources allocated to the slice represented by the resource configuration data are the same. The mapping relationship between the slice service data and the slice operation data satisfies the preset relationship, which may mean that the slice operation data and the slice service data satisfy a positive correlation relationship, specifically, it may mean that the changing trend of the slice performance represented by the slice operation data and the changing trend of the MOS value represented by the slice service data are the same.
[0126] For example, Table 3 shows the correspondence between resource configuration data, slice service data, and slice operation data. As shown in Table 3, assume that the radio resource allocated to service 1 is timeslot 1, and the radio resources allocated to service 2 are timeslots 1 and 2. The MOS score of slice 1 corresponding to service 1 is 8, and the MOS score of slice 2 corresponding to service 2 is 10. The latency measurement for slice 1 corresponding to service 1 results in a latency of 5s, and the latency measurement for slice 2 corresponding to service 2 results in a latency of 8s. Therefore, when the terminal's service type changes from service 1 to service 2, the resource configuration data indicates an increasing trend in radio resources, the slice service data indicates an improving trend in slice quality, and the slice operation data indicates a decreasing trend in slice performance. Because the trends in radio resource and slice performance differ, and the trends in the MOS score used to evaluate slice quality and slice performance differ, the slice operation data is determined to be untrue.
[0127]
[0128] Table 3
[0129] It should be noted that each node in the blockchain network can verify the authenticity of the slice operation data published by the operator to the blockchain network.
[0130] In actual application, considering that the structure of the blockchain network can be a P2P structure, the third node can act as the first node to send resource configuration data and slice operation data to the blockchain network for other nodes to verify the authenticity of the slice operation data.
[0131] Based on this, in one embodiment, the method further includes:
[0132] Sending the slice operation data and resource configuration data to other nodes in the blockchain network except the first node and the second node;
[0133] Among them, the resource configuration data is used for the other nodes to verify the authenticity of the slice operation data, and when the slice data is verified to be authentic data, the verified slice business data is recorded and the consensus mechanism operation is performed.
[0134] In actual application, considering that the structure of the blockchain network can be a P2P structure, the third node can serve as the second node to send the slice business data to the blockchain network for other nodes to verify the authenticity of the slice operation data.
[0135] Based on this, in one embodiment, the method further includes:
[0136] Sending slice business data to other nodes in the blockchain network;
[0137] Among them, the slice business data is used for the other nodes to verify the authenticity of the slice operation data, and when the slice data is verified to be authentic data, the verified slice business data is recorded and the consensus mechanism operation is performed.
[0138] In actual application, in addition to receiving the resource configuration data and slice operation data corresponding to the first node and the slice business data corresponding to the second node, the third node can also broadcast the data broadcast by the first node (resource configuration data and slice operation data) and / or the slice business data broadcast by the second node to other nodes, so that other nodes can verify the authenticity of the slice operation data.
[0139] Based on this, in one embodiment, the method further includes:
[0140] Sending the slice operation data and resource configuration data broadcast by the first node to other nodes in the blockchain network except the first node and the second node; and / or,
[0141] Sending the slice service data broadcast by the second node to other nodes in the blockchain network except the first node and the second node;
[0142] Among them, the resource configuration data and slice business data are used for the other nodes to verify the authenticity of the slice operation data, and when the slice operation data is verified to be authentic slice operation data, the verified slice operation data is recorded and the consensus mechanism operation is performed.
[0143] In actual application, when the third node verifies that the slice operation data is authentic, the third node can publish the verified authentic slice operation data to the blockchain network for the application service provider corresponding to the second node to determine whether the verified slice operation data meets the SLA requirements.
[0144] Based on this, in one embodiment, applied to the second node, the method further includes:
[0145] Reading the verified slice operation data from the blockchain network;
[0146] Determine whether the verified slice operation data meets the SLA requirements.
[0147] Here, the determination of whether the verified slice operation data meets the SLA requirements may refer to determining whether the verified slice operation data meets the service guarantee level requirements (SLR, Service Level Requirement) specified in the SLA contract.
[0148] It should be noted that, in addition to performing SLA verification on the verified slice operation data, one of the following operations may also be performed:
[0149] After the second node reads the verified slice operation data from the blockchain network, it performs settlement with the first node based on the read slice operation data;
[0150] The second node performs a post-audit check based on the read slice operation data.
[0151] Here, the second node performs a post-audit check on the read slice operation data. If the detection is accurate, it can provide the slice operation data to a third-party query system to read.
[0152] If the hash value of the data is stored on the chain, the entity verifies whether the original data obtained from the data provider is correct based on the data hash in the read record.
[0153] In actual applications, operators and application service providers can jointly sign an SLA contract that specifies the SLA requirements that the slice services provided by the operator should meet. In this way, while ensuring that the slice operation data provided by the operator is authentic, the application service provider can further verify whether the slice operation data provided by the operator meets the SLA requirements, thereby improving the accuracy of verifying the SLA requirements.
[0154] Based on this, in one embodiment, determining whether the verified slice operation data meets the SLA requirements includes:
[0155] Read the SLA contract from the blockchain network; use the SLA contract to determine whether the verified slice operation data meets the SLA requirements.
[0156] Here, the SLA contract may refer to the service terms agreed upon by the operator and the application service provider regarding slice orchestration, service area / time, and guarantee level for the type of service provided.
[0157] Here, the SLA contract can be used by operators and application service providers to conduct post-audits to check whether the slice operation data on the chain meets the requirements of the real data source and to hold them accountable. For example, it can be used to determine whether the signed SLA requirements are met.
[0158] The service quality specified in the SLA contract can provide a platform for negotiating service prices and guarantee levels between operators (slice service providers) and application service providers (slice tenants). For example, operators can design a flexible contract framework that includes multiple SLA clauses, each with corresponding service charges. This allows slice tenants to enjoy high-quality service quality within a high-price range, while falling back to a lower-level service level at a lower cost when needed. Therefore, ensuring SLA compliance between slice tenants and network service providers (operators) is particularly important. On the one hand, operators need to demonstrate that different SLAs adopt different charging strategies based on slice QoE and generate corresponding revenue through differentiated services. On the other hand, application consumers also need to know whether the SLAs required by their services are met, and this requires reliable data support.
[0159] SLA contracts can provide high-quality slice services for users in 5G vertical industries. For operators, strict slice SLA management enables 5G networks to serve a wide range of industry applications while precisely controlling the service quality of individual slices. Efficient SLA management not only enables full automation of slice operations but also reduces slice operating costs. This enables operators to offer customized 5G connectivity services with bandwidth, latency, coverage, and mobility capabilities to a wider range of vertical industries, creating a vast potential market. Slice tenants can also benefit from SLA guarantees. Thanks to the slice SLA guarantee architecture, the digital interconnection of trillions of sensors, robots, production lines, and control centers will become a reality. The deterministic network services provided by 5G slices will revolutionize the daily operations and management of industry users undergoing digital transformation. The unprecedented scale of information sharing enabled by slices will help slice tenants across various industries streamline their workflows and create additional business value in existing and emerging markets.
[0160] In actual application, after the terminal completes the slice order, an SLA contract can be signed between the operator and the application service provider to ensure the quality of the slice service. Considering that there can be multiple nodes corresponding to operators in the blockchain network, there can also be multiple nodes corresponding to application service providers. Therefore, the signature information of the first node corresponding to an operator and the signature information of the second node corresponding to an application service provider can be used to generate an SLA contract and publish the generated SLA contract to the blockchain network.
[0161] Based on this, in one embodiment, applied to the first node, before reading the SLA contract from the blockchain network, the method further includes:
[0162] When the slice ordering is completed, obtain the first signature information corresponding to the first node and the second signature information corresponding to the second node;
[0163] Based on the first signature information and the second signature information, the SLA contract is signed to obtain a signed SLA contract; the SLA contract is a contract reached between the operator and the application service provider, which stipulates that the slice service should meet the SLA requirements;
[0164] The signed SLA contract is published to the blockchain network.
[0165] Here, Table 4 is a schematic diagram of the SLA contract published by the first node to the blockchain network. As shown in Table 4, the SLA contract clearly stipulates the slice service guarantee level requirements.
[0166]
[0167] Table 4
[0168] In one example, if Figure 4 As shown, combined Figure 1 The system architecture shown describes the process of publishing data used to verify the authenticity of slice operation data to the blockchain network, including:
[0169] Step 401: The first node publishes the slice operation data and resource configuration data to the blockchain network.
[0170] Here, the first node refers to the operator node. The operator may be the operator that provides the slice network, responsible for providing slice operation data such as OAM data and non-OAM data, participating in the blockchain consensus, and storing and viewing on-chain data.
[0171] Here, when the slice is instantiated and running, the operator node will sign the collected slice operation data and broadcast it to other blockchain nodes.
[0172] Step 402: The second node publishes the slice business data to the blockchain network.
[0173] Here, the second node refers to the application service provider node: it refers to the vertical industry application service provider that rents the slice network, is responsible for providing slice business data such as MOS data, participating in blockchain consensus, and storing and viewing on-chain data.
[0174] Here, when the slice is instantiated and running, the application service provider node signs the MOS data and broadcasts it to other blockchain nodes.
[0175] Figure 5 It is the first process to verify the authenticity of slice operation data published by operators to the blockchain network, including:
[0176] Step 501: Receive slice operation data and resource configuration data broadcast by the first node in the blockchain network; and receive slice business data broadcast by the second node in the blockchain network.
[0177] Here, the first node represents an operator providing a slice service, and the second node represents an application service provider using the slice.
[0178] Here, after the third node receives the data broadcast by the first and second nodes, it can check whether the received data format is accurate, and take the received data or the corresponding hash value as a record and timestamp it. It uses the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the encapsulated new block so that other nodes in the blockchain network can verify the authenticity of the slice operation data provided by the operator.
[0179] Step 502: Determine whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship; when it is determined that the mapping relationship between the resource configuration data and the slice operation data satisfies the preset relationship, execute step 503.
[0180] Here, whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship may refer to whether the slice operation data and the resource configuration data satisfy a positive correlation relationship, specifically including one of the following:
[0181] There is a positive correlation between slice OAM data and resource configuration data;
[0182] There is a positive correlation between slice non-OAM data and resource configuration data;
[0183] There is a positive correlation between slice OAM data and resource configuration data, and there is a positive correlation between slice non-OAM data and resource configuration data.
[0184] Step 503: Verify that the slice operation data is real slice operation data; record the verified slice operation data; and perform consensus mechanism operations on the formed record.
[0185] Here, executing the consensus mechanism operation on the generated record may include:
[0186] Records generated over a period of time are encapsulated in a new block and broadcast to the blockchain network. Upon receiving the new block, other nodes in the blockchain network can verify the correctness and completeness of the format of the block and each record within it, and whether the block meets the requirements of the consensus mechanism. If so, the new block is added to the locally stored blockchain and forwarded; otherwise, it is discarded. Other nodes can also verify the authenticity of the data source based on the above relationship and decide whether to forward or discard the record. This can also be written into a smart contract. If the verification policy is met, the record is written to the blockchain network; if not, it is not written to the blockchain network.
[0187] Here, executing the consensus mechanism operation on the generated record may further include:
[0188] The generated record is signed and sent to a specific node in the blockchain network; after the specific node receives enough signed records, it forwards the received signed records to other specific nodes in the blockchain network to generate blocks, otherwise it is discarded.
[0189] It should be noted that here, the verified slice operation data, resource configuration data, and slice service data can also be recorded and the consensus mechanism operation can be performed on the recorded data. Subsequently, operators or application service providers can use this data to optimize their own network management and orchestration systems by building models.
[0190] Figure 6 This is the second process of verifying the authenticity of the slice operation data published by the operator to the blockchain network, including:
[0191] Step 601: Receive slice operation data and resource configuration data broadcast by the first node in the blockchain network; and receive slice business data broadcast by the second node in the blockchain network.
[0192] Here, the first node represents an operator providing a slice service, and the second node represents an application service provider using the slice.
[0193] Step 602: Determine whether the mapping relationship between the slice business data and the slice operation data satisfies a preset relationship; when it is determined that the mapping relationship between the slice business data and the slice operation data satisfies the preset relationship, execute step 603.
[0194] Here, the mapping relationship between the slice service data and the slice operation data satisfies a preset relationship may refer to a positive correlation relationship between the slice operation data and the slice service data, specifically including one of the following:
[0195] There is a positive correlation between slice OAM data and MOS data;
[0196] There is a positive correlation between the slice non-OAM data and MOS data;
[0197] There is a positive correlation between slice OAM data and MOS data, and there is a positive correlation between slice non-OAM data and MOS data.
[0198] It should be noted that, here, a positive correlation may be satisfied between part of the sliced OAM data and the MOS data, or a positive correlation may be satisfied between all the sliced OAM data and the MOS data.
[0199] Step 603: Verify that the slice operation data is real slice operation data; record the verified slice operation data; and perform consensus mechanism operations on the formed record.
[0200] Figure 7 This is the third process to verify the authenticity of the slice operation data published by the operator to the blockchain network, including:
[0201] Step 701: Receive slice operation data and resource configuration data broadcast by the first node in the blockchain network; and receive slice business data broadcast by the second node in the blockchain network.
[0202] Here, the first node represents an operator providing a slice service, and the second node represents an application service provider using the slice.
[0203] Step 702: Determine whether the mapping relationship between the resource configuration data and the slice operation data satisfies the preset relationship; and determine whether the mapping relationship between the slice business data and the slice operation data satisfies the preset relationship; 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 business data and the slice operation data satisfies the preset relationship, execute step 703.
[0204] Here, whether the mapping relationship between the resource configuration data and the slice operation data satisfies the preset relationship may refer to a positive correlation between the slice operation data and the resource configuration data; and whether the mapping relationship between the slice service data and the slice operation data satisfies the preset relationship may refer to a positive correlation between the slice operation data and the slice service data, specifically including one of the following:
[0205] There is a positive correlation between slice OAM data and resource configuration data, and there is a positive correlation between slice OAM data and MOS data;
[0206] There is a positive correlation between slice non-OAM data and resource configuration data, and there is a positive correlation between slice non-OAM data and MOS data.
[0207] Step 703: Verify that the slice operation data is real slice operation data; record the verified slice operation data; and perform consensus mechanism operations on the formed record.
[0208] Here, the authenticity of the slice operation data published by the operator to the blockchain network is verified, which has the following advantages:
[0209] (1) Operators upload slice operation data (such as slice OAM data, slice non-OAM data) and resource configuration data to the blockchain network, and vertical industry tenants (application service providers) upload slice business data (such as MOS 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 authentic and store it after verification.
[0210] (2) When multiple operators and multiple industry tenants form an alliance and jointly participate in writing data on the chain, they can verify the data from multiple parties to avoid data falsification by one company. By improving the reliability and consistency of slice operation data in storage and communication, the risk of single point failure can be reduced and the authenticity of the slice operation data source can be improved to a certain extent.
[0211] (3) The slice operation data verified on the chain, as well as the resource configuration data and slice business data on the chain, are valuable analysis data sources. Operators can subsequently use these three types of data to optimize their own network management and orchestration systems by building models.
[0212] In one example, if Figure 8 As shown, combined Figure 1 The system architecture shown here describes the process of uploading an SLA contract to the blockchain network for verifying SLA requirements, including:
[0213] Step 801: After the slice ordering is completed, the first node obtains the first signature information corresponding to the first node and the second signature information corresponding to the second node.
[0214] Here, the first node corresponds to an application service provider node.
[0215] Step 802: The first node signs the SLA contract based on the first signature information and the second signature information to obtain a signed SLA contract.
[0216] Here, the SLA contract is a contract reached between the operator and the application service provider, which stipulates that the slicing service should meet the SLA requirements.
[0217] Step 803: The first node publishes the signed SLA contract to the blockchain network.
[0218] Here, after the application service provider node completes the order of a slice at the slice store, it adds a timestamp to the verified SLA contract signed by both parties and publishes it to the blockchain network.
[0219] Figure 9 The second node verifies the SLA requirements of the verified slice operation data, including:
[0220] Step 901: The second node reads the SLA contract from the blockchain network and reads the verified slice operation data.
[0221] Step 902: The second node uses the SLA contract to determine whether the verified slice operation data meets the SLA requirements; when the verified slice operation data meets the SLA requirements, execute step 903.
[0222] Step 903: The second node records the slice operation data that meets the SLA requirements and saves the record in a new block.
[0223] Here, the operator publishes the SLA contract signed with the application service provider to the blockchain network, which has the following advantages:
[0224] (1) Application service providers in vertical industries will verify and store the signed SLA contracts on the chain. After being uploaded to the chain, the data will be highly reliable, tamper-proof, highly secure, and time-series irreversible, enabling full traceability of the data. Based on the stored data, it is possible to self-certify, judge, and hold accountable whether the slice meets the SLA requirements.
[0225] (2) Improve the reliability and consistency of slice SLA contracts in storage and communication.
[0226] (3) Faced with the personalized slice subscriptions (network resource leasing) of numerous OTT or virtual operators, repeated negotiations on SLA parameters and prices will be inevitable. However, with the help of blockchain smart contracts, simple, repetitive negotiation processes will be automated, and the efficiency of the automatic execution of many slice leasing business-related agreements will be significantly improved. As the QoS level and price negotiated by both parties become parameters of the smart contract, the execution and evaluation of the relevant SLAs will be more efficient.
[0227] By adopting the technical solution of the embodiment of the present invention, the operator uploads slice operation data and resource configuration data to the blockchain network, and the application service provider uploads slice business data to the blockchain network. In this way, other nodes in the blockchain network can verify whether the slice operation data uploaded by the operator is authentic and valid, and the application service provider can subsequently obtain the real slice operation data provided by the operator.
[0228] In order to implement the data processing method based on the blockchain network according to the embodiment of the present invention, the embodiment of the present invention also provides a data processing device based on the blockchain network. Figure 10 This is a schematic diagram of the structure of a data processing device based on a blockchain network according to an embodiment of the present invention; Figure 10 As shown, the device includes:
[0229] The receiving unit 101 is configured to receive slice operation data and resource configuration data broadcast by a first node in a blockchain network; the first node represents an operator providing slice services; and receive slice service data broadcast by a second node in the blockchain network; the second node represents an application service provider using the slices;
[0230] A first processing unit 102 is configured to verify the authenticity of the slice operation data based on the resource configuration data and / or the slice service data;
[0231] The second processing unit 103 is used to record the verified slice operation data when verifying that the slice operation data is authentic slice operation data; and perform consensus mechanism operations on the formed record.
[0232] Furthermore, according to at least one embodiment of the present invention, the first processing unit is specifically configured to:
[0233] Determining whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship;
[0234] When it is determined that the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship, it is verified that the slice operation data is real slice operation data.
[0235] In addition, according to at least one embodiment of the present invention, the first processing unit 102 is specifically configured to:
[0236] Determine whether the mapping relationship between the slice service data and the slice operation data satisfies a preset relationship;
[0237] When it is determined that the mapping relationship between the slice business data and the slice operation data satisfies a preset relationship, it is verified that the slice operation data is real slice operation data.
[0238] In addition, according to at least one embodiment of the present invention, the first processing unit 102 is specifically configured to:
[0239] Determine whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship; and determine whether the mapping relationship between the slice service data and the slice operation data satisfies the preset relationship;
[0240] 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 business data and the slice operation data satisfies the preset relationship, it is verified that the slice operation data is real slice operation data.
[0241] Furthermore, according to at least one embodiment of the present invention, applied to the second node, the apparatus further includes:
[0242] A judgment unit is used to read the verified slice operation data from the blockchain network; and judge whether the verified slice operation data meets the SLA requirements.
[0243] Furthermore, according to at least one embodiment of the present invention, the determining unit is specifically configured to:
[0244] Reading the SLA contract from the blockchain network;
[0245] Use the SLA contract to determine whether the verified slice operation data meets the SLA requirements.
[0246] Furthermore, according to at least one embodiment of the present invention, applied to the first node, before reading the SLA contract from the blockchain network, the apparatus further includes:
[0247] A publishing unit is used to obtain the first signature information corresponding to the first node and the second signature information corresponding to the second node after the slice order is completed; based on the first signature information and the second signature information, the SLA contract is signed to obtain the signed SLA contract; the SLA contract is a contract reached between the operator and the application service provider, which stipulates that the slice service should meet the SLA requirements; and the signed SLA contract is published to the blockchain network.
[0248] Furthermore, according to at least one embodiment of the present invention, the apparatus further comprises:
[0249] A sending unit, configured to send the slice operation data and resource configuration data to other nodes in the blockchain network except the first node and the second node;
[0250] Among them, 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 authentic data, the verified slice operation data is recorded and the consensus mechanism operation is performed.
[0251] In addition, according to at least one embodiment of the present invention, the sending unit is further configured to:
[0252] Sending slice business data to other nodes in the blockchain network;
[0253] Among them, the slice business data is used for the other nodes to verify the authenticity of the slice operation data, and when the slice data is verified to be authentic data, the verified slice operation data is recorded and the consensus mechanism operation is performed.
[0254] In actual application, the receiving unit 101 and the sending unit can be implemented by a communication interface in a data processing device based on a blockchain network; the first processing unit 102, the second processing unit 103, the judgment unit, and the publishing unit can be implemented by a processor in a data processing device based on a blockchain network.
[0255] It should be noted that the blockchain network-based data processing device provided in the above embodiment, when performing a prediction based on transmit power, only uses the division of the above-mentioned program modules as an example. In actual applications, the above-mentioned processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the above-described processing. In addition, the blockchain network-based data processing device provided in the above embodiment and the embodiment of the prediction method based on transmit power are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.
[0256] The embodiment of the present invention further provides an electronic device, such as Figure 11 As shown, including:
[0257] Communication interface 111, capable of exchanging information with other devices;
[0258] The processor 112 is connected to the communication interface 111 and is configured to execute the method provided by one or more technical solutions on the smart device side when running a computer program stored in the memory 103 .
[0259] 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 will not be repeated here.
[0260] Of course, in actual application, the various components in the electronic device 110 are coupled together through the bus system 114. It can be understood that the bus system 114 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 114 also includes a power bus, a data processing bus based on the blockchain network, and a status signal bus. However, for the sake of clarity, Figure 10 Various buses are labeled as bus system 104 .
[0261] 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 used to operate on the terminal 100.
[0262] The methods disclosed in the above 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 with signal processing capabilities. During implementation, the steps of the above methods can be completed by hardware integrated logic circuits or software instructions in the processor 112. The above processor 112 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 112 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 113. The processor 112 reads the information in the memory 113 and completes the steps of the above methods in combination with its hardware.
[0263] 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, blockchain-based data processors, microcontroller units (MCUs), microprocessors, or other electronic components to perform the aforementioned method.
[0264] It can be understood that the memory (memory 113) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can 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, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but 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), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), direct memory bus random access memory (DRRAM). The memory described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
[0265] In an exemplary embodiment, the present invention further provides a storage medium, namely, a computer storage medium, specifically, a computer-readable storage medium, such as a memory 113 storing a computer program. The computer program can be executed by the processor 112 of the electronic device 110 to complete the steps of the aforementioned blockchain network-based data processing server-side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface storage, optical disk, or CD-ROM.
[0266] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0267] In addition, the technical solutions described in the embodiments of the present invention can be arbitrarily combined without conflict.
[0268] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention.
Claims
1. A data processing method based on a blockchain network, characterized in that: The method comprises: Receive slice operation data and resource configuration data broadcast by a first node in the blockchain network; the first node represents the operator providing slice services; and receive slice business data broadcast by a second node in the blockchain network; the second node represents the application service provider using the slice; Verifying the authenticity of the slice operation data based on consistency between a change trend of the resource configuration data and / or the slice service data and a change trend of the slice operation data; When it is verified that the slice operation data is authentic slice operation data, the verified slice operation data is recorded; and a consensus mechanism operation is performed on the formed record.
2. The method according to claim 1, characterized in that Verifying the authenticity of the slice operation data based on the consistency between the change trend of the resource configuration data and the change trend of the slice operation data includes: Determining whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship; When it is determined that the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship, it is verified that the slice operation data is real slice operation data.
3. The method according to claim 1, characterized in that Verifying the authenticity of the slice operation data based on the consistency between the change trend of the slice service data and the change trend of the slice operation data includes: Determine whether the mapping relationship between the slice service data and the slice operation data satisfies a preset relationship; When it is determined that the mapping relationship between the slice business data and the slice operation data satisfies a preset relationship, it is verified that the slice operation data is real slice operation data.
4. The method according to claim 1, wherein Verifying the authenticity of the slice operation data based on consistency between a change trend of the resource configuration data and the slice service data and a change trend of the slice operation data includes: Determine whether the mapping relationship between the resource configuration data and the slice operation data satisfies a preset relationship; and determine whether the mapping relationship between the slice service data and the slice operation data satisfies the preset relationship; 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 business data and the slice operation data satisfies the preset relationship, it is verified that the slice operation data is real slice operation data.
5. The method according to any one of claims 1 to 4, characterized in that Applied to the second node, the method further includes: Reading the verified slice operation data from the blockchain network; Determine whether the verified slice operation data meets the SLA requirements.
6. The method according to claim 5, characterized in that The determining whether the verified slice operation data meets the service assurance level agreement (SLA) requirements includes: Reading the SLA contract from the blockchain network; Use the SLA contract to determine whether the verified slice operation data meets the SLA requirements.
7. The method according to claim 6, characterized in that Applied to the first node, before reading the SLA contract from the blockchain network, the method further includes: When the slice ordering is completed, obtain the first signature information corresponding to the first node and the second signature information corresponding to the second node; Based on the first signature information and the second signature information, the SLA contract is signed to obtain a signed SLA contract; the SLA contract is a contract reached between the operator and the application service provider, which stipulates that the slice service should meet the SLA requirements; The signed SLA contract is published to the blockchain network.
8. The method according to claim 1, characterized in that The method further comprises: Sending the slice operation data and resource configuration data to other nodes in the blockchain network except the first node and the second node; Among them, 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 authentic data, the verified slice operation data is recorded and the consensus mechanism operation is performed.
9. The method according to claim 1, characterized in that The method further comprises: Sending slice business data to other nodes in the blockchain network; Among them, the slice business data is used for the other nodes to verify the authenticity of the slice operation data, and when the slice data is verified to be authentic data, the verified slice operation data is recorded and the consensus mechanism operation is performed.
10. A data processing device based on a blockchain network, characterized in that: include: A receiving unit, configured to receive slice operation data and resource configuration data broadcast by a first node in a blockchain network; The first node represents the operator providing the slice service; and receiving the slice service data broadcasted by the second node in the blockchain network; The second node represents an application service provider using the slice; A first processing unit, configured to verify the authenticity of the slice operation data based on consistency between a change trend of the resource configuration data and / or the slice service data and a change trend of the slice operation data; a second processing unit, configured to, when verifying that the slice operation data is authentic, generate a record of the verified slice operation data; And perform consensus mechanism operations on the formed records.
11. An electronic device, characterized in that: include: Communication interface, used to receive slice operation data and resource configuration data broadcast by the first node in the blockchain network; The first node represents the operator providing the slice service; and receiving the slice service data broadcasted by the second node in the blockchain network; The second node represents an application service provider using the slice; a processor, configured to verify the authenticity of the slice operation data based on consistency between a change trend of the resource configuration data and / or the slice service data and a change trend of the slice operation data; And when it is verified that the slice operation data is real slice operation data, the verified slice operation data is recorded; and the consensus mechanism operation is performed on the formed record.
12. An electronic device, characterized in that: comprising a processor and a memory for storing a computer program capable of being executed on the processor, Wherein, when the processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 9.
13. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.
