A slice average subjective opinion score data sharing system, node, method and medium

Abstract

The present invention discloses a slice average subjective opinion data sharing system, node, method and medium, including: the operator node broadcasts the slice network data and / or the service average subjective opinion data to other blockchain nodes; the application service provider node broadcasts the service average subjective opinion data to other blockchain nodes, and / or, after receiving the new block, the operator node and the application service provider node verify whether the block and each record format in the block are correct and complete, if the verification is passed, the new block is added to the locally stored blockchain and forwarded, otherwise the new block is discarded; the query system is used for the relevant parties to access the query service network data and its corresponding average subjective opinion data, as well as other statistical information based on this. The present invention can be used to more widely share the service experience average subjective opinion data with the operation, management and maintenance and QoS flow data in the slice network.

Description

Technical Field

[0001] The present invention relates to the field of wireless communication technology, and in particular to a slice average subjective opinion score data sharing system, node, method and medium. Background Art

[0002] Figure 1 The following is a network diagram including network slicing. As shown in the figure, 5G introduces NS (Network Slicing), which provides customized and dedicated network services for different industries based on shared physical infrastructure. This changes the single network model of 4G and creates a 5G network that supports functional customization, security and resource isolation, and topology optimization to meet the needs of specific goals, specific service categories, and even specific customers. Network slicing services are based on the service terms agreed upon by a series of slicing service providers (such as operators) and slicing customers (such as content providers that use slicing to carry streaming media), providing high-quality slicing services for 5G users, especially 5G users in vertical industries. SLA (Service Level Agreement) is a service term for slice orchestration, service area / time, and guarantee level agreed upon for the type of service provided, which has a profound impact on the business model and pricing method of network slicing.

[0003] Slice SLA is usually monitored and evaluated by the slice manager based on the KPI (Key Performance Indicator) of the network slice (such as 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.). This means that the slice manager itself can evaluate whether the slice service meets the agreed SLA requirements.

[0004] In addition to the end-to-end SLA guarantee, the 5G network control plane must also develop corresponding functions for more dynamic and fine-grained slice QoE (Quality of Experience) level monitoring and management. The industry recommends that it can be approached from the perspective of the end user (i.e., ASP (Application Service Provider)) who has the most direct experience with the slice service. In general, ASP relies on a large number of QoE requirements to measure the perceived service quality. These requirements include but are not limited to: ASP's network service area, MOS (Mean Opinion Score), and user service MOS satisfaction percentage, such as 90% of users meeting or exceeding the specified service MOS requirements.

[0005] In order to obtain the average service MOS and the percentage of users who meet the service MOS, ASP needs to comprehensively consider the relationship between the service MOS value of a single user and the main network attributes (such as upload / download capacity, jitter, maximum allowed latency, network availability, and dedicated service characteristics), and design the corresponding MOS service model. Usually, service MOS is dominated by one or more network attributes that have the greatest impact on user experience, so the service MOS structure of different industry applications will be significantly different. For example, from the perspective of game developers / publishers, there are also obvious differences in the service MOS design of different types of game slices, such as cloud gaming experience is related to bandwidth, multiplayer games are more sensitive to latency, and e-sports pay more attention to the consistency of user experience. ASP is most concerned about the slice service experience and QoE and has a deep understanding of its own business logic. Therefore, different slice tenants have different requirements for the guarantee of the same communication service, which is also the reference baseline for slice SLA requirements. Slice QoE requirements and slice QoE statistics (for example, average service MOS) are key factors to be considered in slice SLA definition and management.

[0006] Currently, the industry is promoting the MOS model training framework to support slice SLA assurance. SMM (Service MOS Model) can be obtained by training a specific service of ASP through NWDAF (Network Data Analytics Function).

[0007] First, as the main data collection point of the 5G system, NWDAF receives and stores service MOS data from ASP or slice tenants, as well as network data provided by the slice manager and core network corresponding to the service. The OAM (Operation, Administration and Maintenance) data provided by the slice manager includes UE-level MDT (Minimization of Drive Test) data, NF (Network Function) performance measurement data and network-level KPI data. The data input from the 5G core network can be non-OAM data at the QoS flow level, UE (User Equipment) level or even service level. The introduction of slice tenant service MOS values ​​can assist operators to intuitively and effectively monitor the quality of slice operation, and therefore plays a vital role in the slice management / control process. Ideally, the service MOS perceived by vertical industries / third parties needs to be highly consistent with the operator's QoE fitting analysis results, indicating that a good balance has been achieved between slice service performance and operation and maintenance costs, thereby achieving a win-win situation between slice service providers and users.

[0008] With a large amount of service MOS and network data, NWDAF can use advanced AI (artificial intelligence) / ML (machine learning) algorithms to train and model the SMM (service MOS model) of a given service. SMM is used to characterize the relationship between the user's service experience MOS value and the OAM and QoS flow data in the slice network, allowing operators to fit the user's service experience based on network management and control data, visually monitor the quality of slice operation, and assist in slice configuration updates and control management.

[0009] Due to the large differences in the operation and business models of industries and slice users, the SMM applied by different industries may be very different. Therefore, the SMM of each slice tenant needs to be trained and verified in a targeted manner to capture the key network characteristics that affect the quality of slice service. In a dynamic business environment, the SMM itself may change over time or differ in different slice service areas. Therefore, it needs to be trained and strengthened through user experience data and network management / control parameters continuously provided by users and networks to ensure the generalization ability and long-term applicability of the model.

[0010] The industry is currently working to identify key SLA assurance scenarios and corresponding stakeholders (such as vertical industries / third parties, telecom vendors, operators, etc.), and to establish close industrial partnerships among stakeholders to jointly develop data analysis methods and business MOS models.

[0011] The deficiency of the existing technology is that the existing slice management solution only supports operators to obtain the experience data of third parties currently providing network slicing services through the NWDAF interface. Summary of the invention

[0012] The present invention provides a mean subjective opinion score data sharing system, node, method and medium, which are used to solve the problem that MOS data is inconvenient to query.

[0013] The present invention provides the following technical solutions:

[0014] A slice MOS data sharing system, comprising: a plurality of application service provider nodes, a plurality of operator nodes, and a plurality of query systems constituting a slice MOS data sharing blockchain network, wherein:

[0015] The operator node is a node of the operator that provides the slice network and is used to perform one or a combination of the following methods:

[0016] Broadcast slice network data and / or business MOS data to other blockchain nodes;

[0017] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0018] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0019] The application service provider node is a node of a vertical industry application service provider that rents a slice network and is used to perform one or a combination of the following methods:

[0020] Broadcast business MOS data to other blockchain nodes;

[0021] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0022] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0023] The query system is used for related parties to access the network data of the query service and its corresponding MOS data, as well as other statistical information based on this.

[0024] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0025] In implementation, the slice MOS data includes a hash value of the slice MOS data and a signature of the slice MOS data storage address;

[0026] Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0027] Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

[0028] A slice MOS data sharing node, comprising: a slice MOS data sharing blockchain network consisting of a plurality of application service provider nodes, a plurality of operator nodes, and a plurality of query systems, wherein:

[0029] The processor is configured to read the program in the memory and execute one or a combination of the following methods:

[0030] Broadcast slice MOS data to other blockchain nodes;

[0031] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0032] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0033] A transceiver is used to receive and send data under the control of the processor.

[0034] During implementation, the node is an operator node that provides slice network data and / or service MOS data, or an application service provider node that provides service MOS data, wherein the operator node is a node of an operator that provides a slice network, and the application service provider node is a node of a vertical industry application service provider that leases a slice network.

[0035] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0036] In implementation, the slice MOS data includes a hash value of the slice MOS data and a signature of the slice MOS data storage address;

[0037] Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0038] Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

[0039] A slice MOS data sharing node, comprising: a slice MOS data sharing blockchain network consisting of a plurality of application service provider nodes, a plurality of operator nodes, and a plurality of query systems, wherein:

[0040] A broadcast module, used to broadcast MOS data to other blockchain nodes, and / or, use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast and publish the block;

[0041] and / or,

[0042] The receiving module is used to verify whether the format of the block and each record in the block is correct and complete after receiving the new block, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, the new block is added to the locally saved blockchain and forwarded, otherwise the new block is discarded.

[0043] During implementation, the node is an operator node that provides slice network data and / or service MOS data, or an application service provider node that provides service MOS data, wherein the operator node is a node of an operator that provides a slice network, and the application service provider node is a node of a vertical industry application service provider that leases a slice network.

[0044] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0045] In implementation, the broadcast module is further used to broadcast the slice MOS data including the hash value of the slice MOS data and the signature of the slice MOS data storage address;

[0046] The receiving module is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0047] Each node further comprises:

[0048] The database is used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

[0049] A query system, comprising: a slice MOS data sharing blockchain network consisting of a plurality of application service provider nodes, a plurality of operator nodes, and a plurality of query systems, wherein:

[0050] The processor is used to read the program in the memory and execute the following procedures:

[0051] Provide network data and corresponding MOS data for related parties to query services, as well as other statistical information based on this data;

[0052] A transceiver is used to receive and send data under the control of the processor.

[0053] A query system, comprising: a slice MOS data sharing blockchain network consisting of a plurality of application service provider nodes, a plurality of operator nodes, and a plurality of query systems, wherein:

[0054] Interface, used for access by relevant parties;

[0055] The query module is used for related parties to access the network data of the query service and its corresponding MOS data, as well as other statistical information based on it.

[0056] A slice MOS data sharing method, in a slice MOS data sharing blockchain network composed of a plurality of application service provider nodes, a plurality of operator nodes, and a plurality of query systems, comprises:

[0057] The operator node of the operator providing the slice network performs one or a combination of the following methods:

[0058] Broadcast slice network data and / or business MOS data to other blockchain nodes;

[0059] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0060] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0061] The application service provider node of the vertical industry application service provider that rents the slice network performs one of the following methods or a combination thereof:

[0062] Broadcast business MOS data to other blockchain nodes;

[0063] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0064] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0065] After the relevant parties access the slice MOS data sharing blockchain network through the query system, they can query the network data of the business and its corresponding business MOS data, as well as other statistical information based on this.

[0066] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0067] In implementation, the slice MOS data includes a hash value of the slice MOS data and a signature of the slice MOS data storage address;

[0068] Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0069] Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

[0070] A slice MOS data sharing method, in a slice MOS data sharing blockchain network composed of a plurality of application service provider nodes, a plurality of operator nodes, and a plurality of query systems, comprises:

[0071] Do one or a combination of the following:

[0072] Broadcast slice MOS data to other blockchain nodes;

[0073] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0074] The consensus mechanism in the blockchain is used to encapsulate the records obtained within a period of time into a new block and broadcast the block.

[0075] During implementation, the node is an operator node that provides slice network data and / or service MOS data, or an application service provider node that provides service MOS data, wherein the operator node is a node of an operator that provides a slice network, and the application service provider node is a node of a vertical industry application service provider that leases a slice network.

[0076] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0077] In implementation, the slice MOS data includes a hash value of the slice MOS data and a signature of the slice MOS data storage address;

[0078] Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0079] Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

[0080] During implementation, the operator node and / or the application service provider node is further used to use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast and publish the block.

[0081] A query method, in a slice MOS data sharing blockchain network consisting of a plurality of application service provider nodes, a plurality of operator nodes, and a plurality of query systems, comprises:

[0082] Access by interested parties;

[0083] Provides network data and its corresponding MOS data for related parties to query services, as well as other statistical information based on this.

[0084] A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the above-mentioned slice MOS data sharing method.

[0085] The beneficial effects of the present invention are as follows:

[0086] In the technical solution provided by the embodiment of the present invention, since the blockchain network is composed of multiple operators and application service provider nodes, and the slice network data and / or business MOS data required for model training after consensus are stored on the chain, each node that needs to obtain MOS data is no longer limited to obtaining the experience data of the third party that currently provides the network slice service through the NWDAF interface, but can more widely share the business experience MOS data with the OAM and QoS flow data in the slice network.

[0087] Furthermore, this solution has at least one of the following effects:

[0088] Since MOS data is stored in the blockchain network, a decentralized slicing network data and / or business MOS data sharing system is provided;

[0089] Since consensus on data is required in the blockchain network, the consistency of distributed MOS data is guaranteed, and shared data synchronization between all relevant parties in the alliance - vertical industries / third parties, telecom manufacturers, operators, etc. is achieved;

[0090] Since MOS data is stored in the blockchain network, the risk of single point failure is reduced;

[0091] Furthermore, the solution also provides an authorized implementation plan, so that relevant parties within the alliance can selectively authorize data sharing. BRIEF DESCRIPTION OF THE DRAWINGS

[0092] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0093] Figure 1 A network diagram including network slicing in the background technology;

[0094] Figure 2 This is a schematic diagram of the structure of a slice MOS data sharing system in an embodiment of the present invention;

[0095] Figure 3 This is a schematic diagram of the blockchain network structure in an embodiment of the present invention;

[0096] Figure 4 This is a schematic diagram of a slice MOS data sharing node structure in an embodiment of the present invention;

[0097] Figure 5 This is a schematic diagram of a second slice MOS data sharing node structure in an embodiment of the present invention;

[0098] Figure 6 A schematic diagram of a query system structure in an embodiment of the present invention;

[0099] Figure 7 This is a schematic diagram of the query system structure 2 in an embodiment of the present invention;

[0100] Figure 8 It is a schematic diagram of the implementation process of the slice MOS data sharing method implemented by the system in an embodiment of the present invention;

[0101] Fig. 9 A schematic diagram of an implementation flow of a slice MOS data sharing method implemented by a node in an embodiment of the present invention;

[0102] Fig.10 The figure is a schematic diagram of the implementation flow of the query method in the embodiment of the present invention. DETAILED DESCRIPTION

[0103] The inventors noticed during the invention process that:

[0104] The existing slice management solution only supports operators to obtain the experience data of third parties who currently provide network slicing services through the NWDAF interface.

[0105] Since the slice service has not been fully implemented and commercialized, the amount of information available to operators is very small, which is not conducive to model training, maturity and development of slices. The wider sharing of service experience MOS data and OAM and QoS flow data in the slice network among stakeholders will help operators deploy a large number of slice services on the shared 5G infrastructure while better guaranteeing the service quality expected by each slice user. However, which platform will carry and manage the data shared by multiple parties is a problem.

[0106] The characteristics of blockchain in establishing multi-party trust, maintaining consistency, and decentralization make it very suitable for solving this problem. Based on this, an embodiment of the present invention proposes a solution for sharing slice network data and / or business MOS data based on blockchain, in which alliance members jointly provide and maintain slice network data and / or business MOS data, and data is shared within the alliance for business MOS model training. In this example, slice MOS data refers to slice operation network data (including operation, management and maintenance data provided by the slice manager, and / or network data provided by the core network) and / or MOS data of the services supported by the slice.

[0107] The specific implementation of the present invention will be described below in conjunction with the accompanying drawings.

[0108] In the description process, the implementation of the operator node, the application service provider node, and the query system will be described, and examples of their coordinated implementation will be given to better understand the implementation of the solution given in the embodiment of the present invention. This description does not mean that they must be implemented in coordination or must be implemented separately. In fact, when they are implemented separately, they also solve their own problems, and when they are used in combination, better technical effects will be obtained.

[0109] Figure 2 The following is a schematic diagram of the structure of the slice MOS data sharing system, as shown in the figure, which may include:

[0110] Several application service provider nodes, several operator nodes, and several query systems constitute the slice MOS data sharing blockchain network, including:

[0111] The operator node 201 is a node of an operator that provides a slice network, and is used to perform one or a combination of the following methods:

[0112] Broadcast slice network data and / or business MOS data to other blockchain nodes;

[0113] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0114] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0115] The application service provider node 202 is a node of a vertical industry application service provider that rents a slice network, and is used to perform one or a combination of the following methods:

[0116] Broadcast business MOS data to other blockchain nodes;

[0117] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0118] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0119] The query system 203 is used for related parties to access and query the network data of the service and its corresponding MOS data, as well as other statistical information based thereon.

[0120] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0121] Figure 3 This is a schematic diagram of the blockchain network structure. As shown in the figure, the system can also be as follows:

[0122] Operator node: refers to the operator that provides the slice network, responsible for providing the data collected by itself for model training, participating in the blockchain consensus, storing the slice network data and / or service MOS data used for model training, and viewing the slice network data and / or service MOS data in the chain. Some operator nodes can provide network data provided by the slice manager and the core network corresponding to the service. The OAM (Operation, Administration and Maintenance) data provided by the slice manager includes UE-level MDT (Minimization of Drive Test) data, NF (Network Function) performance measurement data, and network-level KPI data.

[0123] The data input from the 5G core network can be QoS flow level, UE level or even service level non-OAM data;

[0124] Other operator nodes can provide business network data collected by NWDAF from the network during internal training and business MOS data collected from application service providers.

[0125] Application service provider node: refers to the vertical industry application service provider that rents the slice network, responsible for providing the business MOS data collected by itself, participating in the blockchain consensus, and storing and viewing the slice network data and / or business MOS data;

[0126] Query system: It can be accessed by relevant parties to query the network data of a certain business and its corresponding MOS data and other statistical information based on it.

[0127] The implementation of the system is described below.

[0128] It can be mainly divided into two parts for explanation:

[0129] 1) Writing slice network data and / or business MOS data; 2) Viewing slice network data and / or business MOS data.

[0130] Furthermore, depending on whether the on-chain data is completely public, there may be different implementation methods, which are explained below.

[0131] 1. Implementation of full disclosure of on-chain data.

[0132] 1) Slice network data and / or service MOS data writing:

[0133] The operator node broadcasts the slice network data and / or business MOS data to other blockchain nodes; the operator node can also broadcast the slice network data, etc. to other blockchain nodes; the application service provider node broadcasts the business MOS data, etc. to other blockchain nodes.

[0134] Other blockchain nodes check the format of the received data and treat it as a record. There are three ways to record the data in the previous step:

[0135] (1) Slice MOS identification, slice network data (such as OAM data, QoS flow data, etc.), and service MOS data;

[0136] (2) Slice MOS identification and slice network data (such as OAM data, QoS flow data, etc.);

[0137] (3) Slice MOS identification and business MOS data.

[0138] In the example, the slice MOS identification method is used. The purpose of the slice MOS identification is to associate the slice network data with the slice MOS data. The slice MOS identification itself does not belong to the content of the slice MOS data. There are many specific implementation methods for associating the slice network data with the slice MOS data. The MOS identification in the embodiment is only one of the methods. It is relatively simple to use the identification method directly, so the slice MOS identification is taken as an example here; however, other methods can also be used, as long as the slice network data and the business MOS data can be associated. The slice MOS identification is only used to teach technical personnel in this field how to implement the present invention specifically, but it does not mean that only the slice MOS identification method can be used. The corresponding method can be determined in combination with practical needs during the implementation process.

[0139] The nodes use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0140] After receiving the new block, other nodes in the network verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If correct, the new block is added to the locally saved blockchain and forwarded; otherwise, the new block is discarded.

[0141] 2) View slice network data and / or service MOS data:

[0142] Entities that need to train the slice MOS model can view the slice network data and / or business MOS data stored on the blockchain. They can read the complete slice network data and / or business MOS data pair, or they can use the slice MOS identifier to find the corresponding network data and business MOS data to form a complete slice network data and / or business MOS data pair.

[0143] 2. The data on the chain is not public and requires authorization to view the implementation of the data on the chain.

[0144] In implementation, the slice MOS data includes a hash value of the slice MOS data and a signature of the slice MOS data storage address;

[0145] Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0146] Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

[0147] The details can be as follows:

[0148] 1) Slice network data and / or service MOS data writing:

[0149] The operator node signs the slice MOS identifier, the hash value of the slice MOS data, and the storage address of the slice MOS data, and broadcasts them to other blockchain nodes; the operator node can also sign the slice MOS identifier, the hash value of the slice network data and other data, and the storage address of the slice network data and other data, and broadcast them to other blockchain nodes; the application service provider node signs the slice MOS identifier, the hash value of the business MOS data and other data, and the storage address of the business MOS data and other data, and broadcasts them to other blockchain nodes.

[0150] Other blockchain nodes check the format and signature of the received data and treat it as a record. There are three ways to record the data in the previous step:

[0151] (1) Slice MOS identification, slice MOS data hash value, slice MOS data storage address;

[0152] (2) Slice MOS identification, hash value of slice network data and other data, storage address of slice network data and other data.

[0153] (3) Slice MOS identification, hash value of business MOS data and other data, storage address of business MOS data and other data.

[0154] The nodes use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0155] After receiving the new block, other nodes in the network verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If correct, the new block is added to the locally saved blockchain and forwarded; otherwise, the new block is discarded.

[0156] 2) View slice network data and / or service MOS data:

[0157] An entity that needs to train the slice MOS model can apply to view the slice network data and / or business MOS data stored on the blockchain. It can read the complete slice network data and / or business MOS data pair, that is, record (1), or it can search for the corresponding network data and business MOS data through the slice MOS identifier, that is, the associated data pair of records (2) and (3).

[0158] The entity applies for the corresponding original data from the address based on the read record, and each node decides whether to release the original data to the entity based on its own authorization policy.

[0159] The entity verifies whether the original data obtained is correct based on the data hash in the read record.

[0160] Based on the same inventive concept, the embodiments of the present invention also provide a MOS data sharing node, a MOS data sharing method, and a computer-readable storage medium. Since the principles of solving problems by these devices are similar to those of the MOS data sharing system, the implementation of these methods can refer to the implementation of the system, and the repeated parts will not be repeated.

[0161] Figure 4 This is a schematic diagram of the slice MOS data sharing node structure. As shown in the figure, the slice MOS data sharing blockchain network consists of several application service provider nodes, several operator nodes, and several query systems. The nodes include:

[0162] The processor 400 is configured to read the program in the memory 420 and execute one or a combination of the following methods:

[0163] Broadcast slice MOS data to other blockchain nodes;

[0164] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0165] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0166] The transceiver 410 is configured to receive and send data under the control of the processor 400 .

[0167] During implementation, the node is an operator node that provides slice network data and / or service MOS data, or an application service provider node that provides service MOS data, wherein the operator node is a node of an operator that provides a slice network, and the application service provider node is a node of a vertical industry application service provider that leases a slice network.

[0168] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0169] In implementation, the slice MOS data includes a hash value of the slice MOS data and a signature of the slice MOS data storage address;

[0170] Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0171] Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

[0172] Among them, Figure 4 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 400 and memory represented by memory 420. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 410 may be a plurality of components, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 400 is responsible for managing the bus architecture and general processing, and the memory 420 may store data used by the processor 400 when performing operations.

[0173] Figure 5 This is a schematic diagram of the second structure of the slice MOS data sharing node. As shown in the figure, the slice MOS data sharing blockchain network consists of several application service provider nodes, several operator nodes, and several query systems. The nodes include:

[0174] Broadcast module 501, used to broadcast MOS data to other blockchain nodes, and / or, use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast and publish the block;

[0175] and / or,

[0176] The receiving module 502 is used to verify whether the format of the block and each record in the block is correct and complete after receiving the new block, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, the new block is added to the locally saved blockchain and forwarded, otherwise the new block is discarded.

[0177] During implementation, the node is an operator node that provides slice network data and / or service MOS data, or an application service provider node that provides service MOS data, wherein the operator node is a node of an operator that provides a slice network, and the application service provider node is a node of a vertical industry application service provider that leases a slice network.

[0178] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0179] In implementation, the broadcast module is further used to broadcast the slice MOS data including the hash value of the slice MOS data and the signature of the slice MOS data storage address;

[0180] The receiving module is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0181] Each node further comprises:

[0182] The database is used to decide whether to issue MOS data based on the authorization policy when other nodes apply for MOS data.

[0183] During implementation, the broadcast module is further used to use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast and publish the block.

[0184] For the convenience of description, the various parts of the above-mentioned device are divided into various modules or units according to their functions and described separately. Of course, when implementing the present invention, the functions of each module or unit can be implemented in the same or multiple software or hardware.

[0185] Figure 6 This is a schematic diagram of the query system structure. As shown in the figure, the sliced ​​MOS data sharing blockchain network consists of several application service provider nodes, several operator nodes, and several query systems. The nodes include:

[0186] The processor 600 is used to read the program in the memory 620 and execute the following program:

[0187] Provide network data and corresponding MOS data for related parties to query services, as well as other statistical information based on this data;

[0188] The transceiver 610 is configured to receive and send data under the control of the processor 600 .

[0189] Among them, Figure 6 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 610 may be a plurality of components, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 when performing operations.

[0190] Figure 7This is a schematic diagram of the query system structure 2. As shown in the figure, it is located in a slice MOS data sharing blockchain network composed of several application service provider nodes, several operator nodes, and several query systems, where:

[0191] Interface 701, for access by relevant parties;

[0192] The query module 702 is used for related parties to access and query the network data of the service and its corresponding MOS data, as well as other statistical information based thereon.

[0193] For the convenience of description, the various parts of the above-mentioned device are divided into various modules or units according to their functions and described separately. Of course, when implementing the present invention, the functions of each module or unit can be implemented in the same or multiple software or hardware.

[0194] Figure 8 A schematic diagram of the implementation process of the slice MOS data sharing method implemented for the slice system, in a slice MOS data sharing blockchain network composed of several application service provider nodes, several operator nodes, and several query systems, as shown in the figure, may include:

[0195] Step 801: The operator node of the operator providing the slice network performs one of the following methods or a combination thereof:

[0196] Broadcast slice network data and / or business MOS data to other blockchain nodes;

[0197] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0198] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0199] Step 802: The application service provider node of the vertical industry application service provider that rents the slice network performs one of the following methods or a combination thereof:

[0200] Broadcast business MOS data to other blockchain nodes;

[0201] After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0202] Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block;

[0203] Step 803: After the relevant parties access the slice MOS data sharing blockchain network through the query system, they query the network data of the business and its corresponding MOS data, as well as other statistical information based on this.

[0204] There is no time sequence relationship between the steps, but they can occur simultaneously in the blockchain network, that is, each node can broadcast, download, and query blockchain data at the same time.

[0205] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0206] In implementation, the slice MOS data includes a hash value of the slice MOS data and a signature of the slice MOS data storage address;

[0207] Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0208] Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

[0209] Fig. 9 A schematic diagram of the implementation process of the slice MOS data sharing method implemented for a node, in a slice MOS data sharing blockchain network composed of a number of application service provider nodes, a number of operator nodes, and a number of query systems, as shown in the figure, may include:

[0210] Step 901: broadcast slice network data and / or business MOS data to other blockchain nodes; and / or,

[0211] Step 902: After receiving the new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block;

[0212] Step 903: Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block.

[0213] There is no time sequence relationship between the steps, but they can be implemented simultaneously, that is, nodes can broadcast and receive blockchain data at the same time.

[0214] During implementation, the node is an operator node that provides slice network data and / or service MOS data, or an application service provider node that provides service MOS data, wherein the operator node is a node of an operator that provides a slice network, and the application service provider node is a node of a vertical industry application service provider that leases a slice network.

[0215] During implementation, slice network data includes operation, management and maintenance data provided by the slice manager and / or network data provided by the core network.

[0216] In implementation, the slice MOS data includes a hash value of the slice MOS data and a signature of the slice MOS data storage address;

[0217] Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data;

[0218] Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

[0219] A computer-readable storage medium is also provided in an embodiment of the present invention. The computer-readable storage medium stores a computer program for executing the above-mentioned MOS data sharing method.

[0220] For specific implementation, please refer to the implementation of slice MOS data sharing system.

[0221] To sum up, an architecture is provided in an embodiment of the present invention: multiple operators and application service provider nodes form a blockchain network, and the chain stores the sliced ​​network data and / or business MOS data required for model training after consensus.

[0222] The operator node or application service provider node broadcasts the slice network data and / or business MOS data required for model training, slice network data and other data, business MOS data and other data to the blockchain network, and stores them in the blockchain node after the blockchain network consensus. The entity query obtains the slice network data and / or business MOS data.

[0223] The operator node or application service provider node broadcasts the hash value and original data storage address of the slice network data and / or business MOS data, slice network data and other data required for model training to the blockchain network. After the blockchain network consensus, the data is stored in the blockchain node. The entity queries the original data storage address and applies for the original data from it. The latter decides whether to disclose the original data to the applicant entity based on its own authorization policy. The applicant entity verifies whether the original data is correct based on the on-chain hash.

[0224] Fig.10 The flowchart of the query method implementation is shown in the figure. As shown in the figure, in the slice MOS data sharing blockchain network composed of several application service provider nodes, several operator nodes, and several query systems, it can include:

[0225] Step 1001: Access by relevant parties;

[0226] Step 1002: Provide the network data and corresponding MOS data of the query service to the relevant parties, as well as other statistical information based thereon.

[0227] This solution has at least one of the following effects:

[0228] Provide a decentralized slicing network data and / or business MOS data sharing system;

[0229] Ensure distributed data consistency: Achieve shared data synchronization among all parties in the alliance - vertical industries / third parties, telecom vendors, operators, etc.;

[0230] Reduce the risk of single point failure;

[0231] Relevant parties within the alliance can selectively authorize data sharing.

[0232] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0233] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0234] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0235] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0236] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A slice average subjective opinion score MOS data sharing system, characterized in that: include: Several application service provider nodes, several operator nodes, and several query systems constitute the slice MOS data sharing blockchain network, including: The operator node is a node of the operator that provides the slice network and is used to perform one or a combination of the following methods: Broadcast slice network data and / or business MOS data to other blockchain nodes; After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block; Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block; The application service provider node is a node of a vertical industry application service provider that rents a slice network and is used to perform one or a combination of the following methods: Broadcast business MOS data to other blockchain nodes; After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block; Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block; The query system is used for related parties to access the network data of the query service and its corresponding MOS data, as well as other statistical information based thereon; The slice network data includes operation, management and maintenance data provided by the slice manager, and / or network data provided by the core network; the slice MOS data includes: a hash value of the slice MOS data, and a slice MOS data storage address.

2. The system according to claim 1, characterized in that Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data; Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

3. A slice MOS data sharing node, characterized in that: include: Located in a sliced ​​MOS data sharing blockchain network consisting of several application service provider nodes, several operator nodes, and several query systems, where: The processor is configured to read the program in the memory and execute one or a combination of the following methods: Broadcast slice MOS data to other blockchain nodes; After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block; Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block; a transceiver for receiving and transmitting data under the control of the processor; The slice MOS data includes: a hash value of the slice MOS data, and a slice MOS data storage address.

4. The node according to claim 3, characterized in that The node is an operator node that provides slice network data and / or service MOS data, or an application service provider node that provides service MOS data, wherein the operator node is a node of an operator that provides a slice network, and the application service provider node is a node of a vertical industry application service provider that leases a slice network.

5. A slice MOS data sharing node, characterized in that: include: Located in a sliced ​​MOS data sharing blockchain network consisting of several application service provider nodes, several operator nodes, and several query systems, where: A broadcast module is used to broadcast the slice MOS data to other blockchain nodes, and / or use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block; and / or, The receiving module is used to verify whether the format of the block and each record in the block is correct and complete after receiving the new block, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, the new block is added to the locally saved blockchain and forwarded, otherwise the new block is discarded; The slice MOS data includes: a hash value of the slice MOS data, and a slice MOS data storage address.

6. A query system, characterized in that: include: Located in a sliced ​​MOS data sharing blockchain network consisting of several application service provider nodes, several operator nodes, and several query systems, where: The processor is used to read the program in the memory and execute the following procedures: Provide network data and corresponding MOS data for related parties to query services, as well as other statistical information based on this data; a transceiver for receiving and transmitting data under the control of the processor; The slice MOS data includes: a hash value of the slice MOS data, and a slice MOS data storage address.

7. A query system, characterized in that: include: Located in a sliced ​​MOS data sharing blockchain network consisting of several application service provider nodes, several operator nodes, and several query systems, where: Interface, used for access by relevant parties; The query module is used for related parties to access the network data of the query service and its corresponding MOS data, as well as other statistical information based on it; The slice MOS data includes: a hash value of the slice MOS data, and a slice MOS data storage address.

8. A slice MOS data sharing method, characterized in that: In the slice MOS data sharing blockchain network composed of several application service provider nodes, several operator nodes, and several query systems, including: The operator node of the operator providing the slice network performs one or a combination of the following methods: Broadcast slice network data and / or business MOS data to other blockchain nodes; After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block; Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block; The application service provider node of the vertical industry application service provider that rents the slice network performs one of the following methods or a combination thereof: Broadcast business MOS data to other blockchain nodes; After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block; Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block; After the relevant parties access the slice MOS data sharing blockchain network through the query system, they can query the network data of the business and its corresponding business MOS data, as well as other statistical information based on this; The slice network data includes operation, management and maintenance data provided by the slice manager, and / or network data provided by the core network; the slice MOS data includes: a hash value of the slice MOS data, and a slice MOS data storage address.

9. The method according to claim 8, characterized in that Each node is further used to read the slice MOS data to obtain the slice MOS data storage address, apply for the slice MOS data from the node corresponding to the address, and determine whether the data is correct according to the hash value of the slice MOS data; Each node is further used to decide whether to issue slice MOS data according to the authorization policy when other nodes apply for slice MOS data.

10. A slice MOS data sharing method, characterized in that: In a slice MOS data sharing blockchain network composed of several application service provider nodes, several operator nodes, and several query systems, one or a combination of the following methods is performed: Broadcast slice MOS data to other blockchain nodes; After receiving a new block, verify whether the format of the block and each record in the block is correct and complete, and whether the block meets the requirements of the consensus mechanism. If the verification is passed, add the new block to the locally saved blockchain and forward it, otherwise discard the new block; Use the consensus mechanism in the blockchain to encapsulate the records obtained within a period of time into a new block and broadcast the block; The slice MOS data includes: a hash value of the slice MOS data, and a slice MOS data storage address.

11. A query method, characterized in that: In the slice MOS data sharing blockchain network composed of several application service provider nodes, several operator nodes, and several query systems, including: Access by interested parties; Provide network data and corresponding MOS data for related parties to query services, as well as other statistical information based on this data; The slice MOS data includes: a hash value of the slice MOS data, and a slice MOS data storage address.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program for executing the method according to any one of claims 8 to 11.

Images