Data rights and interests management method, communication device and storage medium

Abstract

Disclosed are a data rights and interests management method, a communication device and a storage medium. The data rights and interests management method comprises: determining data rights and interests of a second network element, the data rights and interests of the second network element being used for representing rights and interests of the second network element related to data generated by the second network element; and sending first data rights and interests information to the second network element, the first data rights and interests information comprising data rights and interests related information of the second network element.

Description

Data rights management method, communication device, and storage medium

[0001] This disclosure claims priority to Chinese patent application No. 202310940231.X, filed on July 27, 2023, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present disclosure relates to the field of communication network technology, and in particular to a data rights management method, a communication device, and a storage medium. Background Art

[0003] Under the current network architecture, the rights and interests of data-driven entities remain murky. For example, because network equipment vendors and end users lack the right to participate in or provide guidance on network planning and O&M optimization, operators are limited to using technologies such as self-organized networks (SON), minimized drive tests (MDT), and network data analysis functions (NWDAF) to conduct long-term measurements and collect big data on specific end users or network elements.

[0004] Summary of the Invention

[0005] In one aspect, a data rights management method is provided, which is applied to a first network element. The data rights management method includes:

[0006] Determine the data rights and interests of the second network element, where the data rights and interests of the second network element are used to represent the rights and interests of the second network element in relation to the data generated by the second network element;

[0007] The first data rights and interests information is sent to the second network element, where the first data rights and interests information includes data rights and interests related information of the second network element.

[0008] In another aspect, a data rights management method is provided, which is applied to a second network element. The data rights management method includes:

[0009] receiving first data rights and interests information sent by the first network element, where the first data rights and interests information includes data rights and interests related information of the second network element, where the data rights and interests represent the rights and interests of the second network element in relation to the data generated by the second network element;

[0010] The data rights and interests of the second network element are obtained according to the first data rights and interests information.

[0011] In another aspect, a data rights management method is provided, which is applied to a third network element. The data rights management method includes:

[0012] First data rights and interests information sent by the first network element is received, where the first data rights and interests information includes information related to data rights and interests of the second network element, where the data rights and interests of the second network element are used to represent the rights and interests of the second network element related to data generated by itself.

[0013] In another aspect, a data rights management device is provided, which is applied to a first node. The data rights management device includes:

[0014] a determination module, configured to determine the data rights and interests of the second network element, where the data rights and interests of the second network element are used to represent the rights and interests of the second network element in relation to the data generated by the second network element;

[0015] The sending module is configured to send the first data rights and interests information to the second network element, where the first data rights and interests information includes the data rights and interests related information of the second network element.

[0016] In another aspect, a data rights management device is provided, which is applied to a second node. The data rights management device includes:

[0017] A receiving module, configured to receive first data rights information sent by a first network element, where the first data rights information includes information related to data rights of a second network element, where the data rights are used to represent the rights of the second network element to data generated by itself;

[0018] The acquisition module is configured to acquire the data rights of the second network element according to the first data rights information.

[0019] In another aspect, a data rights management device is provided, which is applied to a third node. The data rights management device includes:

[0020] The receiving module is configured to receive first data rights information sent by a first network element, where the first data rights information includes information related to data rights of a second network element, and the data rights of the second network element are used to represent the rights of the second network element to data generated by itself.

[0021] On the other hand, a communication device is provided, comprising: a memory and a processor; the memory and the processor are coupled; the memory is used to store a computer program; and the processor implements the data rights management method described in any of the above aspects when executing the computer program.

[0022] On the other hand, a computer-readable storage medium is provided, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the data rights management method described in any of the above aspects is implemented.

[0023] On the other hand, a computer program product is provided, which includes computer program instructions, and when the computer program instructions are executed by a processor, the data rights management method described in any of the above aspects is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] To more clearly illustrate the technical solutions of the present disclosure, the following briefly introduces the drawings required for use in some embodiments of the present disclosure. Obviously, the drawings described below are only drawings of some embodiments of the present disclosure, and those skilled in the art can also derive other drawings based on these drawings.

[0025] FIG1 is a schematic diagram of a network architecture according to some embodiments.

[0026] FIG2 is a schematic diagram of another network architecture according to some embodiments.

[0027] FIG3 is a flowchart of a data rights management method according to some embodiments.

[0028] FIG4 is a flowchart of another data rights management method according to some embodiments.

[0029] FIG5 is a flowchart of another data rights management method according to some embodiments.

[0030] FIG6 is a flowchart of another data rights management method according to some embodiments.

[0031] FIG7 is a schematic structural diagram of a data rights management device according to some embodiments.

[0032] FIG8 is a schematic structural diagram of another data rights management device according to some embodiments.

[0033] FIG9 is a schematic structural diagram of another data rights management device according to some embodiments.

[0034] FIG10 is a schematic structural diagram of a communication device according to some embodiments. DETAILED DESCRIPTION

[0035] To help those skilled in the art better understand the technical solutions of the embodiments of the present disclosure, the technical solutions of the present disclosure will be clearly and completely described below in conjunction with the drawings in the present disclosure. Obviously, the embodiments described are only some of the embodiments of the present disclosure, not all of them. Based on the embodiments of the present disclosure, all other embodiments obtained by those of ordinary skill in the art without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0036] It should be noted that in this disclosure, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this disclosure as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

[0037] In the following, the terms "first," "second," etc. are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of technical features indicated. Therefore, a feature defined as "first," "second," etc. may explicitly or implicitly include one or more of such features.

[0038] In the description of this disclosure, unless otherwise specified, " / " means "or." For example, A / B can mean A or B. "And / or" herein is merely a description of an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: only A, only B, and both A and B. Furthermore, "at least one" means one or more, and "a plurality" means two or more.

[0039] The existing technology has the problem of unclear data rights and interests, which makes all network participants lack enthusiasm, makes data assets difficult to open up, and makes data transactions inefficient.

[0040] In response to the above technical problems, the embodiments of the present disclosure provide a data rights management method. The idea is to manage the data rights generated in the network by defining standardized first data rights information, clarify the data rights of network elements for various types of data, and enhance the value of various types of data in the network.

[0041] It's understandable that data rights and interests require defining the data's rights holders and the content of those rights—that is, who holds what rights to the data. Throughout the data lifecycle, from creation to extinction, four primary roles are involved: data owners, data producers, data users, and data managers. For different types of data assets, the owners, producers, users, and managers may differ. In other words, managing data rights and interests involves different behaviors for different roles.

[0042] Rights and interests encompass both rights and benefits, broadly referring to the roles, status, entitlements, and benefits assigned to specific entities. Operations based on the allocation, modification, and transaction of rights and interests can lead to greater value creation. In wireless systems, some network rights include the right to participate in network planning and construction, the right to assist in network maintenance and optimization, the right to dominate service operations, and the right to ownership of digital assets. Network entity interactions are facilitated by network elements (NEs), which can be devices, functions, entities, nodes, protocol layers, or components. When network data involves commercial activities or transactions, the data rights and interests of NEs correspond to the data rights and interests of commercial entities in a commercial sense. Common commercial entities include operators, equipment vendors, terminal manufacturers, individual consumers, government and enterprise clients, application providers, content providers, special NE node owners (e.g., property management), and super terminal users. For example, operators are commercial entities, and the core network equipment owned by operators is considered a network entity.

[0043] To protect the data rights and interests of each network entity, the disclosed embodiments first determine the roles of each network entity, and then conduct rights management such as rights confirmation and profit sharing for each network entity. Rights confirmation refers to clarifying each entity's rights to ownership, right to know, right to participate, right to control, right to manage, right to make suggestions, and right to process data. Rights management also includes specifying business behaviors and business models such as incentives (for example, incentives received by data producers for generating data), transaction rules, billing methods, transaction methods, and profit sharing strategies.

[0044] Referring to Figure 1, which is a schematic diagram of a network architecture involved in an embodiment of the present disclosure, the network architecture includes a core network (CN), a radio access network (RAN), user equipment (UE), and a data network (DN).

[0045] The core network has multiple network functions (NFs), and each NF can be accessed through a service-based interface. For example, the main NFs of the core network include:

[0046] The user plane function (UPF), as the user plane access NF of the network, is mainly responsible for packet routing and forwarding of user plane data, policy implementation, traffic reporting, and quality of service (QoS) processing.

[0047] The UPF and UPF can be connected through the user plane interface N9 interface to transmit uplink and downlink user data flows between UPFs.

[0048] The network storage function (NF repository function, NRF) is mainly responsible for registering and managing various NFs in the network.

[0049] Unified data management (UDM) is responsible for the unified management of user data such as user contract information and security information, as well as related functions such as user identification, access authorization, and mobility management.

[0050] The authentication server function (AUSF), as the authentication center of the network, is mainly responsible for providing authentication and access authentication for users. It can also authenticate external applications and toB.

[0051] The application function (AF) interacts with the application control plane and delivers application QoS requirements or parameters.

[0052] The network exposure function (NEF) supports third-party application AF to interact with various network elements in the core network through NEF.

[0053] The session management function (SMF) is mainly responsible for tunnel maintenance, Internet Protocol (IP) address allocation and management, user plane (UP) management, policy implementation, QoS control, billing data collection, roaming and other functions.

[0054] The SMF can also derive QoS profiles based on policy control and charging (PCC) rules and generate QoS flows. The SMF can also send QoS profiles to the RAN and packet detection rules (PDRs) to the UPF, binding the PCC rules to the QoS flows. The SMF can also select UPFs based on UE or session granularity, allocate IP addresses, collect billing data, and connect to the billing center.

[0055] The policy control function (PCF) is a network element of the policy and charging control architecture. It can provide policy rules for control plane functions, formulate PCC rules, and authorize SMFs in units of service data flows (SDFs).

[0056] The access and mobility management function (AMF), as the user's control plane access NF, is mainly responsible for user registration management, connection management, reachability management, security management, mobility management and other functions.

[0057] For example, the AMF can provide a session management message transmission channel between the UE and SMF, provide authentication and authorization functions for user access, and serve as the control plane access point for the radio access network and core network. For example, as shown in Figure 2, the AMF can forward the QoS profile from the SMF to the RAN and the QoS rule from the SMF to the UE.

[0058] The unified data repository (UDR) is responsible for storing structured user data, such as user contract data, policy data, capability development data, and application data.

[0059] The unstructured data storage function (UDSF) is responsible for storing unstructured data, such as UE context data.

[0060] NWDAF is responsible for data collection, transmission, storage and data analysis.

[0061] Edge nodes (e.g., mobile edge computing (MEC)) are nodes deployed at the edge of the core network and undertake a large number of computing tasks.

[0062] In some embodiments, the core network introduces a management data analytic function (MDAF) (not shown in Figure 1) to manage network configuration data. Through the coordinated cooperation of MDAF, CN NFs, and RAN, the core network provides primary data service capabilities.

[0063] UE is an important concept in mobile communications. UE can be a mobile phone, smart terminal, multimedia device, streaming media device, etc.

[0064] The UE and AMF are connected via the signaling plane interface N1.

[0065] RAN is a type of access network (AN). RAN refers to the introduction of a part or all of the access network AN into the wireless transmission medium to provide fixed terminal services and / or mobile terminal services to users.

[0066] The RAN and AMF are connected via the signaling plane interface N2. The RAN and UPF are connected via N3, which is used to transmit uplink and downlink user plane data.

[0067] Exemplarily, the RAN is a ground infrastructure, for example, a base station (BS).

[0068] Data network (DN) corresponds to operator services, Internet access or third-party services, etc. For example, third-party applications (Apps) can be deployed on the DN.

[0069] DN and UPF can be connected through the N6 interface to transmit uplink and downlink user data flows between UPF and DN.

[0070] It should be noted that the network architecture and application scenarios described in the embodiments of this disclosure are intended to more clearly illustrate the technical solutions of the embodiments of this disclosure and do not constitute a limitation on the technical solutions provided by the embodiments of this disclosure. Those skilled in the art will appreciate that, with the evolution of network architectures and the emergence of new business scenarios, the technical solutions provided by the embodiments of this disclosure will also be applicable to similar technical problems.

[0071] The following is an introduction to the data rights management method provided by the embodiment of the present disclosure.

[0072] As shown in FIG3 , the data rights management method provided by the embodiment of the present disclosure may include the following S101 - S103 .

[0073] S101: A first network element determines data rights and interests of a second network element.

[0074] It should be noted that the network element in the embodiments of the present disclosure refers to a network element. For example, a network element can be a function, entity, node, protocol layer, or component, etc., which is not limited in the embodiments of the present disclosure.

[0075] In some embodiments, the above-mentioned first network element may include at least one of the following: core network, wireless access network, business entity, terminal equipment, network management center, network control center, network data asset management network element, equity management network element, equity management center, equity management layer, equity management entity, equity management function, equity management component and equity management agent.

[0076] Exemplarily, the core network includes at least one of the following: PCF, AMF, SMF, UDM, UDR, UPF and NEF.

[0077] The above-mentioned wireless access network includes at least one of the following: a centralized unit (CU), a distributed unit (DU), a service data adaptation protocol (SDAP), a packet data convergence protocol (PDCP), a radio link layer control protocol (RLC), a medium access control (MAC), a RAN capability exposure function, etc.

[0078] The above-mentioned rights management network element includes at least one of the following: a dedicated rights network element, and a rights enhancement network element formed by adding rights management functions to an existing network element.

[0079] In some embodiments, the second network element may include at least one of the following: a terminal device, a base station, a wireless access network, a business entity, a core network, a third-party application, a capability exposure node, and an edge node.

[0080] Exemplarily, the core network includes at least one of the following: PCF, AMF, SMF, UDM, UDR, UPF and NEF.

[0081] The above-mentioned wireless access network includes at least one of the following: CU, DU, SDAP, PDCP, RLC and MAC.

[0082] The above-mentioned edge nodes include: MEC.

[0083] The above-mentioned capability exposure node includes at least one of the following: NEF, RAN capability exposure network element.

[0084] In some embodiments, the data rights of the second network element are used to represent the rights of the second network element to the data generated by itself.

[0085] Exemplarily, the above-mentioned data rights and interests include at least one of the following: scope of data usage, degree of data privacy, data computing capabilities, ownership of data, processing rights of data, use rights of data, maintenance rights of data, management rights of data, privacy and security protection rights of data, profit sharing strategy of data, validity period of data rights and interests, life cycle of data rights and interests, type of data rights and interests, billing method of data rights and interests, data rights and interests transaction method, and incentives obtained by the second network element for generating data.

[0086] Exemplarily, data rights and interests types refer to different data rights and interests corresponding to different data. For example, different data rights and interests can be defined for structured data and unstructured data. For example, different data rights and interests can be defined for data used for network optimization and data used for artificial intelligence (AI) model training. Therefore, the first data rights and interests information described above can include multiple rights and interests information, with different rights and interests information configured for different types of data.

[0087] Exemplarily, data computing capability refers to the computing power used in the data generation process. For example, a base station includes its computing capability in a data rights request message sent to the core network. The core network determines the data rights information to be provided to the base station based on the computing capability reported by the base station.

[0088] It is understood that the core network includes multiple NFs. The embodiments of the present disclosure add rights management functions to these NFs, and rights information can be transferred by calling service-based interfaces. For example, a first network element (e.g., PCF, SMF, UPF, or AMF in the core network) is used to perform centralized rights management, and a second network element (e.g., RNA node or terminal) reports rights capabilities; then, the first network element allocates rights.

[0089] Exemplarily, when the first network element is a PCF and the second network element is a different entity, the first network element determining the data rights and interests of the second network element may include: PCF determining the data rights and interests of the user terminal; PCF determining the data rights and interests of the base station; PCF determining the data rights and interests of the MEC; PCF determining the data rights and interests of the third-party application; PCF determining the data rights and interests of the data subject of the network participant, etc.

[0090] In some embodiments, as shown in FIG. 4 , the above S101 may be implemented as the following S1011 - S1012 .

[0091] S1011: The second network element sends a first data rights request message to the first network element. Correspondingly, the first network element receives the first data rights request message sent by the second network element.

[0092] The first data rights request message packet carries at least one of the following information: capability information related to the data rights of the second network element; and data rights that the second network element expects to obtain.

[0093] Exemplarily, the capability information related to the data rights and interests of the second network element may be tasks related to the data rights and interests that the second network element can perform, such as a task of collecting data or a task of model training.

[0094] In some embodiments, the above S1011 may be implemented as follows: the second network element sends a capability reporting message to the first network element; the capability reporting message carries a data rights request message.

[0095] In some embodiments, the above S1011 may be implemented as follows: the second network element sends a connection establishment request message to the first network element; the connection establishment request message carries a data rights request message.

[0096] In some embodiments, the above S1011 may be implemented as follows: the second network element sends a registration request message to the first network element; the registration request message carries a data rights request message.

[0097] In some embodiments, the above S1011 may be implemented as follows: the second network element sends a rights information request message to the first network element; the rights information request message carries a data rights request message.

[0098] In some embodiments, the above S1011 can be implemented as follows: in response to receiving the authentication request message sent by the first network element, the second network element sends a response message to the first network element; the response message to the authentication request message carries a data rights request message.

[0099] In some embodiments, the above S1011 may be implemented as follows: the second network element sends an authentication request message to the first network element; the authentication request message carries a data rights request message.

[0100] S1012: The first network element determines the data rights of the second network element according to the received first data rights request message.

[0101] Exemplarily, when the first data rights request message includes capability information related to the data rights of the second network element, the first network element determines the data rights of the second network element based on the capability information related to the data rights of the second network element. For example, assuming that the second network element is capable of performing the task of collecting data, the first network element may determine the data rights of the second network element based on the content, data type, and / or data volume of the data that the second network element can collect.

[0102] Exemplarily, when the first data rights request message includes the data rights that the second network element desires to obtain, the first network element determines the data rights of the second network element based on the data rights that the second network element desires to obtain. For example, assuming that the second network element desires to obtain the right to use data A, the first network element can determine the data rights of the second network element by determining whether the second network element is eligible to be granted the right to use data A.

[0103] Exemplarily, when the first data rights request message includes the capability information of the second network element and the data rights that the second network element desires to obtain, the first network element determines the data rights of the second network element based on the capability information of the second network element and the data rights that the second network element desires to obtain. For example, assuming that the second network element is capable of performing the task of collecting data A and that the second network element desires to obtain the right to use data A when performing the task of collecting data A, the first network element can determine the data rights of the second network element based on this information.

[0104] S102: The first network element sends first data rights information to the second network element. Correspondingly, the second network element receives the first data rights information sent by the first network element.

[0105] The first data rights and interests information includes data rights and interests related information of the second network element.

[0106] Illustratively, the first data rights information includes one of the following:

[0107] Information on data rights configuration;

[0108] Information on changes in data rights;

[0109] Information on the termination of data rights.

[0110] Exemplarily, the data rights configuration information includes: the data rights that can be granted to the second network element, the configuration of parameters related to the data rights, etc. For example, the data rights configuration information includes: the right to know and the right to use data A granted to the second network element. For example, the data rights configuration information includes: the proportion of the profit that the second network element will receive from commercial activities with data B.

[0111] Exemplarily, the data rights change information includes: the data rights to be changed in the second network element's data rights, and the details of the change. For example, assuming the second network element has the right to use data A for a period of three months, the data rights change information may include: a change to the term of the second network element's right to use data A, with the change extending the second network element's right to use data A to six months.

[0112] Exemplarily, the information regarding the data rights change includes: a change in the second network element's right to participate in network planning and construction. For example, if the second network element is a super terminal or a special network element node, the second network element may, after negotiation and authorization with the operator, serve as a legitimate service or relay node. Furthermore, the second network element may receive certain value feedback or rewards based on the rights allocation change process and its actual contribution to network planning and construction coverage.

[0113] Exemplarily, the information regarding the data rights change includes: a change in the network optimization assistance rights of the second network element. For example, if the second network element is a super terminal or a special network element node, after negotiation and authorization with the operator, the second network element can use its inherent intelligence to locally resolve certain network operation and maintenance optimization issues or provide reference suggestions and data corpus to the operator. Furthermore, the second network element can receive certain value feedback or rewards based on the rights allocation change process and its actual contribution to network optimization assistance.

[0114] Exemplarily, the information regarding the data rights change includes: a change in the service control authority of the second network element. For example, if the second network element is a hyperterminal or a special network element node, the second network element, after negotiating with the operator and obtaining authorization, can proactively request and specify its desired resource policy and RRC configuration for certain special service scenarios.

[0115] Exemplarily, the data rights termination information includes: the data rights that need to be terminated among the data rights of the second network element. For example, assuming that the second network element has the right to know about data A, the data rights termination information may include: terminating the second network element's right to know about data A.

[0116] In some embodiments, the above S102 may be implemented as follows: the first network element sends a second data rights request message to the second network element, where the second data rights request message carries the first data rights information.

[0117] In some embodiments, the above S102 can be implemented as follows: the first network element receives the first data rights request message sent by the second network element, and sends a response message to the first data rights request message to the second network element, where the response message to the first data rights request message carries the first data rights information.

[0118] In some embodiments, the above S102 can be implemented as follows: the first network element receives the data service registration message sent by the second network element, and sends a response message to the data service registration message to the second network element, where the response message to the data service registration message carries the first data rights information.

[0119] In some embodiments, the above S102 can be implemented as follows: the first network element receives the service query message sent by the second network element, and sends a response message to the service query message to the second network element, where the response message to the service query message carries the first data rights information.

[0120] In some embodiments, the above S102 may be implemented as follows: the first network element sends a connection request message to the second network element, where the connection request message carries the first data rights information.

[0121] In some embodiments, the above S102 can be implemented as follows: the first network element receives a connection request message sent by the second network element, and sends a response message to the connection request message to the second network element, where the response message carries the first data rights information.

[0122] In some embodiments, the above S102 may be implemented as follows: the first network element sends a broadcast message, where the broadcast message carries the first data rights information.

[0123] In some embodiments, the above S102 may be implemented as follows: the first network element sends a system configuration message, where the system configuration message carries the first data rights information.

[0124] In some embodiments, S102 may be implemented as follows: the first network element sends quality of service (QoS) information, and transmits the first data rights information in or along with the QoS information. Exemplarily, the QoS information includes at least one of the following: QoS characteristic parameters, a QoS profile, a QoS rule, and service-level agreement (SLA) contract information.

[0125] For example, as shown in Figure 2, when the second network element is a UE, the first network element sends a QoS rule to the second network element, and the QoS rule includes the first data benefit information (that is, the first data benefit information can be used as a parameter in the QoS rule). When the second network element is a RAN, the first network element sends a QoS profile to the second network element, and the QoS profile includes the first data benefit information (that is, the first data benefit information can be used as a parameter in the QoS profile).

[0126] In some embodiments, the above S102 may be implemented as follows: the first network element sends a data packet, the header of which carries the first data rights information.

[0127] In some embodiments, the above S102 may be implemented as follows: the first network element sends a data packet, and the data area of ​​the data packet carries the first data rights information.

[0128] In some embodiments, the above S102 may be implemented as follows: the first network element sends an authentication message to the second network element, where the authentication message carries the first data rights information.

[0129] In some embodiments, the above S102 can be implemented as: the first network element sends a signaling message to the second network element, the signaling message carries the first data rights information, wherein the signaling message includes at least one of the following: non-access stratum (NAS) message, radio resource control (RRC) message, system information (SI) message and QoS control message.

[0130] In some embodiments, when the first network element and the second network element cannot communicate directly, the above S102 can be implemented as: sending the first data rights information to the second network element via a third network element. Correspondingly, the second network element receives the first data rights information sent by the first network element via the third network element.

[0131] Exemplarily, sending the first data rights information to the second network element through the third network element may include the following a1-a2.

[0132] a1. The first network element sends first data rights information to the third network element. Correspondingly, the third network element receives the first data rights information sent by the first network element.

[0133] a2. The third network element sends the first data rights information to the second network element. Correspondingly, the second network element receives the first data rights information sent by the third network element.

[0134] Exemplarily, the above-mentioned third network element includes at least one of the following: AMF network element, NEF network element, access network capability exposure network element, relay network element, terminal equipment, base station, wireless access network, business entity, third-party application, capability exposure node and edge node.

[0135] Exemplarily, when the first network element is a core network (for example, a PCF network element or an SMF network element in the core network) and the second network element is a radio access network (for example, a base station), the above S102 can be implemented as follows:

[0136] The core network directly sends the first data rights information to the base station; or,

[0137] The core network sends the first data rights information to the access network device through the AMF; or,

[0138] The core network sends a QoS profile to the access network device; the QoS profile includes the first data rights information.

[0139] Exemplarily, when the first network element is a core network (for example, a PCF or SMF in the core network) and the second network element is a terminal device, the above S102 can be implemented as follows:

[0140] The core network directly sends the first data rights information to the terminal device; or,

[0141] The core network sends the first data rights information to the terminal device through the AMF network element; or,

[0142] The core network sends a QoS rule to the terminal device; the QoS rule message includes the first data rights information; or,

[0143] The AMF sends a NAS message to the terminal device; the NAS message includes the first data rights information.

[0144] Exemplarily, when the first network element is the core network (for example, PCF or SMF in the core network), the second network element is a third-party application (for example, MEC), and the third network element is NEF, the above S102 can be implemented as: PCF sends the first data rights information to MEC through NEF.

[0145] S103: The second network element obtains the data rights of the second network element according to the first data rights information.

[0146] Exemplarily, in a case where the first data rights information includes data rights configuration information, the second network element obtains the data rights granted to the second network element according to the data rights configuration information.

[0147] Exemplarily, in a case where the first data rights information includes information on data rights changes, the second network element obtains the data rights that need to be changed among the data rights of the second network element according to the information on the data rights changes.

[0148] Exemplarily, in a case where the first data rights information includes data rights termination information, the second network element obtains the data rights that need to be terminated among the data rights of the second network element according to the rights termination information.

[0149] It can be understood that the data rights management method provided by the embodiment of the present disclosure manages the data rights and interests generated in the network by defining standardized first data rights and interests information. It is oriented to various types of data, clarifies the data rights and interests of network elements in the network, and can enhance the value of various types of data in the network.

[0150] In some embodiments, as shown in FIG5 , before the above S103 , the method further includes the following S201 .

[0151] S201: A second network element sends a response message of first data rights information to a first network element. Correspondingly, the first network element receives the response message of the first data rights information sent by the second network element.

[0152] The response message of the first data rights information includes at least one of the following:

[0153] a rights feedback message, where the rights feedback message includes a feedback response from the second network element as to whether the content indicated by the first data rights information is accepted;

[0154] a rights negotiation request, where the rights negotiation request includes a request by the second network element to modify the rights information of the first data;

[0155] Second data rights and interests information, where the second data rights and interests information is rights and interests auxiliary information that the second network element assists the first network element in determining the first data rights and interests information;

[0156] Effect feedback message; the effect feedback information includes the reporting feedback of the second network element on the execution effect of the task corresponding to the first data rights information.

[0157] It is understandable that, if the first data rights information does not meet the expectations of the second network element, the second network element may generate second data rights information to assist the first network element in determining the first data rights information. For example, the second data rights information may include the second network element's recommendation value for the first data rights information.

[0158] In some embodiments, the second network element sends a response message of the first data rights information to the first network element through the third network element.

[0159] Exemplarily, when the first network element is a core network (for example, PCF or SMF in the core network) and the second network element is a wireless access network device (for example, a base station), the base station sends a response message of the first data rights information to the SMF (taking the core network as SMF as an example) through the AMF.

[0160] Exemplarily, when the first network element is a core network (for example, a PCF or SMF in the core network) and the second network element is a terminal device, the terminal device sends a response message of the first data rights information to the SMF through the AMF.

[0161] Exemplarily, when the first network element is the core network (for example, a PCF network element or an SMF network element in the core network) and the second network element is a third-party application (for example, MEC), MEC sends a response message of the first data rights information to the core network through the NEF network element.

[0162] In some other embodiments, as shown in FIG6 , the method further includes:

[0163] S301. A first network element sends first data rights and interests information to a third network element; accordingly, the third network element receives the first data rights and interests information.

[0164] S302: The third network element determines the data rights and interests of the third network element according to the first data rights and interests information.

[0165] Illustratively, the third network element may determine the data rights of the second network element based on the first data rights information; infer the data rights of the third network element based on the data rights of the second network element; and further, the third network element may also apply for the data rights of the third node.

[0166] In some embodiments, when the second network element and the third network element belong to the same type of network element, the third network element can use the data rights of the third network element based on the rights of the second network element. For example, assuming that the first network element is the core network, the second network element is UE1, and the third network element is UE2; if the data rights of UE1 determined by the core network include rights related to the AI ​​model, UE2 can use UE1's AI model based on UE1's data rights.

[0167] It can be understood that the data rights management method provided by the embodiment of the present disclosure can clarify data rights by exchanging data rights information between various network elements, which can enhance the value of various types of network data.

[0168] For ease of understanding, the data rights management information provided by the embodiments of the present disclosure is described below using different scenarios as examples.

[0169] Scenario 1: The first network element is the core network (for example, the PCF network element or SMF network element in the core network), the second network element is the UE, and the third network element is the AMF.

[0170] For example, in scenario one, the data rights management method provided by the embodiment of the present disclosure can be implemented as the following b1-b4.

[0171] b1. The UE sends a first data rights request message to the core network.

[0172] Exemplarily, the first data benefit request message includes at least one of the following: capability information related to the UE's data benefit, and data benefit that the UE expects to obtain.

[0173] Exemplarily, the UE may use a NAS message to send the first data rights request message to the core network, that is, the UE sends a NAS message to the core network, and the NAS message carries the first data rights request message.

[0174] b2. The core network determines the data rights of the UE according to the first data rights request message sent by the UE.

[0175] b3. The core network generates data rights information of the UE according to the data rights of the UE, and sends the data rights information of the UE to the UE.

[0176] Exemplarily, b3 can be implemented as follows: the core network sends a QoS rule to the UE through the AMF, and the QoS rule carries the UE's data rights information (that is, the UE's data rights information can be a parameter of the QoS rule).

[0177] Exemplarily, b3 may also be implemented as follows: the core network sends a signaling message to the UE, where the signaling message carries the data rights information of the UE.

[0178] b4. The UE obtains the UE's data rights and interests based on the UE's data rights and interests information.

[0179] Scenario 2: The first network element is the core network (for example, a PCF network element or an SMF network element in the core network), the second network element is a base station, and the third network element is an AMF.

[0180] For example, in scenario 2, the data rights management method provided by the embodiment of the present disclosure can be implemented as the following c1-c4.

[0181] c1. The base station sends a first data rights request message to the core network.

[0182] Exemplarily, the first data rights request message includes at least one of the following: capability information related to the data rights of the base station, and data rights that the base station expects to obtain.

[0183] Exemplarily, the base station sends a first data rights request message to the core network through the AMF.

[0184] c2. The core network determines the data rights of the base station according to the first data rights request message sent by the base station.

[0185] c3. The core network generates data rights and interests information of the base station according to the data rights and interests of the base station, and sends the data rights and interests information of the base station to the base station.

[0186] Exemplarily, c3 can be implemented as follows: the core network sends a QoS profile to the base station through the AMF, and the QoS profile carries the data rights and interests information of the base station (that is, the data rights and interests information of the base station can be used as a parameter of the QoS profile).

[0187] Exemplarily, c3 may also be implemented as follows: the core network sends a signaling message to the base station, where the signaling message carries data rights information of the base station.

[0188] c4. The base station obtains the data rights of the base station based on the data rights information of the base station.

[0189] Scenario three: the first network element is the core network (for example, a PCF network element or an SMF network element in the core network), the second network element is a third-party application, and the third network element is NEF.

[0190] For example, in scenario three, the data rights management method provided by the embodiment of the present disclosure can be implemented as the following d1-d4.

[0191] d1. The third-party application sends a first data rights request message to the core network.

[0192] Exemplarily, the first data rights request message includes at least one of the following: capability information related to the data rights of the third-party application, and the data rights that the third-party application expects to obtain.

[0193] Exemplarily, when a third-party application is deployed on the edge node MEC, the third-party application may send a first data rights request message to the core network through the NEF network element.

[0194] For example, the third-party application may send a capability reporting message to the core network through the NEF, where the capability reporting message includes a first data rights request message.

[0195] d2. The core network determines the data rights of the third-party application based on the first data rights request message sent by the third-party application.

[0196] For example, assuming that a third-party application has the ability to use network data for data analysis and AI reasoning and optimize network performance, the core network can determine the data rights and interests of the third-party application based on this capability and ensure that the network is open to the third-party application in a secure manner. In this way, the third-party application is also willing to actively assist in network optimization because of the incentive.

[0197] d3. The core network generates data rights and interests information of the third-party application based on the data rights and interests of the third-party application, and sends the data rights and interests information of the third-party application to the third-party application.

[0198] For example, when a third-party application is deployed on the edge node MEC, the core network may send data rights and interests information of the third-party application to the third-party application through NEF.

[0199] For example, the core network can send data rights and interests information of third-party applications to third-party applications through the RAN capability exposure function. For example, the third-party application sends a request message for the RAN capability exposure function to the core network; in response, the core network receives the request message for the RAN capability exposure function and sends a response message to the third-party application; the response message to the RAN capability exposure function request message carries the data rights and interests information of the third-party application, and the data rights and interests information of the third-party application carries the capabilities opened by the RAN for the third-party application, as well as the data rights and interests of the third-party application (for example, the third-party application has the right to process the data opened by the RAN, but does not have the right to own the data).

[0200] d4. The third-party application obtains the data rights of the third-party application based on the data rights information of the third-party application.

[0201] Scenario 4: The first network element is the core network (for example, the PCF network element or SMF network element in the core network), the second network element is the network entity A, and the third network element is the AMF.

[0202] For example, in scenario four, the data rights management method provided by the embodiment of the present disclosure can be implemented as the following e1-e4.

[0203] e1. Network entity A sends a first data rights request message to the core network.

[0204] Exemplarily, the network entity A may be a base station, a terminal, a third-party application, an intelligent network node, an integrated access backhaul (IAB) node, a satellite network node, etc.

[0205] Exemplarily, the first data rights request message includes at least one of the following: capability information related to the data rights of the network subject A, and the data rights that the network subject A expects to obtain.

[0206] Exemplarily, network entity A sends a first data rights request message to the core network through the AMF network element. For example, network entity A sends an authentication request message to the core network through the AMF, where the authentication request message includes the first data rights request message; or, network entity A sends a response message to the authentication request message sent by the core network through the AMF, where the response message to the authentication request message includes the first data rights request message.

[0207] e2. The core network determines the data rights of network subject A according to the first data rights request message sent by network subject A.

[0208] e3. The core network generates data rights and interests information of network subject A based on the data rights and interests of network subject A, and sends the data rights and interests information of network subject A to network subject A.

[0209] Exemplarily, the core network may send data rights information of network entity A to network entity A through AMF.

[0210] Exemplarily, the core network may send a broadcast message, where the broadcast message includes the data rights and interests information of the network subject A.

[0211] e4. Network subject A obtains the data rights and interests of network subject A based on the data rights and interests information of network subject A.

[0212] In other embodiments, for example, network entity A may register service capabilities related to data rights and interests with the core network, and the core network may then determine the data rights and interests of network entity A based on the server capabilities related to the data rights and interests registered by network entity A. When network entity B invokes the data service of network entity A, the core network may send network entity A's data rights and interests information to network entity B to inform network entity B of network entity A's data rights and interests.

[0213] Scenario 5: The first network element is a base station and the second node is a UE.

[0214] For example, in scenario five, the data rights management method provided by the embodiment of the present disclosure can be implemented as the following f1-f4.

[0215] f1. The UE sends a first data rights request message to the base station.

[0216] Exemplarily, the first data benefit request message includes at least one of the following: capability information related to the UE's data benefit, and data benefit that the UE expects to obtain.

[0217] Exemplarily, the UE may send the first data rights request message to the base station through air interface signaling. For example, the UE sends a measurement report message to the base station, and the measurement report message carries the first data rights request message.

[0218] f2. The base station determines the data rights of the UE according to the first data rights request message sent by the UE.

[0219] In some embodiments, the decision-making power of data rights lies with the core network. After receiving the first data rights request message sent by the UE, the base station sends the first data rights request message to the core network, and the core network determines the data rights of the UE; then, the core network sends the data rights of the UE to the base station.

[0220] f3. The base station generates data rights information of the UE according to the data rights of the UE, and sends the data rights information of the UE to the UE.

[0221] For example, the base station sends a signaling message to the UE, where the signaling message carries the data benefit information of the UE. The signaling message may be an RRC message, such as an RRC configuration message or an RRC reconfiguration message.

[0222] For example, the base station may send a broadcast message that carries the data benefit information of the UE. The broadcast message may be SI or a broadcast channel.

[0223] For example, a base station can send a broadcast message to recruit UEs that can actively perform measurements or data collection. To encourage participation, the broadcast message carries UE data rights information, which includes the data rights that UEs that perform measurement reporting or data collection tasks can obtain (for example, the measurement reporting or collected data belongs to the base station, but the UEs that perform data tasks such as measurement reporting or data collection can obtain some rewards).

[0224] After receiving the UE's data rights information, the UE can send a response message to the base station. The response message includes whether the UE accepts the data rights information and whether it wants to negotiate for modification. If the UE accepts the data rights information sent by the base station, the UE needs to provide the corresponding data services and divide the data rights holders and distribute the benefits according to the data rights information. If the UE does not accept the data rights indication sent by the base station, the UE can also initiate a rights negotiation request to the base station to suggest that the base station revise the data rights holder division method, rights content objects and benefit distribution, etc.

[0225] The UE sends a connection request message to the base station, and the connection request message carries a response message containing the UE's data rights information. If the response message includes a rights negotiation request, the base station may send a response message to the connection request message to the UE, and the response message carries the determined data rights information.

[0226] For example, in SON or MDT, a base station can send a broadcast message to announce a measurement task, and the broadcast message can carry the UE's data rights information. The UE's data rights information can include a rights distribution policy, which clarifies that the data belongs to the operator, but UEs that perform measurement tasks can receive rewards. The terminal that receives the profit distribution policy sends a response message, indicating its willingness to accept the data collection task.

[0227] f4. The UE obtains the UE's data rights and interests based on the UE's data rights and interests information.

[0228] Scenario 6: Rights management of data services.

[0229] In recent years, the value mining and application of massive amounts of network data have garnered increasing attention. With the development of technologies such as big data, artificial intelligence, and communication-aware convergence, data has become multidimensional, ubiquitous, time-series, and interconnected. 6G networks must provide data services that enable distributed collaboration, facilitate value realization, and prioritize security and privacy. Data services are provided by various data entities within the network. Entities directly connected to data include third-party applications, core networks, wireless access networks, terminals, transmission networks, and digital platforms.

[0230] Therefore, when providing data services, 6G networks can manage data rights and interests by transmitting data rights and interests information.

[0231] In some embodiments, during the network service registration phase, data rights and interests information may be carried in a data service registration message. Exemplarily, the first node is the core network (for example, the NRF network element in the core network) and the second node is the base station. The base station may send a data service registration message to the core network (the base station registers the data service capabilities that the base station can provide to the core network through the data service registration message), and carry a data rights and interests request message in the data service registration message, wherein the data rights and interests request message includes information such as the billing mode for using the data service, the rights and interests of the newly generated data during the data service process (for example, ownership rights, processing rights, usage rights, etc.), and the distribution of benefits obtained from providing data services. The core network determines the rights and interests of the data service of the base station, and sends the rights and interests information corresponding to the data service to the base station through a data service registration response message. By receiving the data service registration message, the core network can obtain and store the data rights and interests corresponding to each registered data service.

[0232] In other embodiments, during network operation, illegal or malicious calls to data services can be avoided by authorizing data services. For example, network entity B providing data services carries data rights information in a data service registration message. If a terminal wants to call the data service of the network entity, the network (e.g., core network or network management center, etc.) needs to determine whether the terminal meets the authorization policy based on the data rights information of the data service of network entity B carried in the received data service registration message; for terminals that meet the authorization policy, access is allowed and the use of the data service of network entity B is authorized; for terminals that do not meet the authorization policy, calling the data service of network entity B is not allowed.

[0233] In other embodiments, during the data service discovery phase, data rights information may be carried in a response message to a data service request message. For example, a third-party application sends a data service request message to the core network through NEF; the core network queries the data services and their data rights stored in the core network, and sends the data rights information of the data service to the third-party application (for example, the core network may send a response message to the data service request message to the third-party application, and the response message carries the data rights information of the data service). After receiving the data rights information of the data service sent by the core network, the third-party application pays the relevant fees to the operator when using the data rights, and the operator shares the profits with the data service provider based on the data profit-sharing strategy.

[0234] In other embodiments, during the data service authentication phase, data rights information may be transmitted based on a data service authentication message (e.g., an authentication message). For example, the terminal includes a request for data rights related to terminal security and privacy protection in an authentication request message. Accordingly, the core network includes the terminal's data rights information in the authentication message.

[0235] In other embodiments, before data collection, the data management center needs to obtain the data rights and interests information of the collection device (for example, a sensor), and use the data rights and interests information to clarify data ownership, data processing rights, data usage rights and other rights. For example, in a sensor perception scenario, the data management center can first obtain the data rights and interests of the sensor through a dedicated rights and interests message or a confirmation message, and then collect data. The way in which the data management center obtains the data rights and interests of the sensor includes: obtaining from the rights and interests management network element (such as the rights and interests contract database); the data management center sends a request message for data rights and interests information or a configuration message for data rights and interests information to the sensor, and receives a response message from the sensor, and the response message carries the data rights and interests information of the sensor.

[0236] The data management center may include at least one of the following: NWDAF, MDAF, new network element, data plane network element, and 6G new data management entity. The rights management network element may include at least one of the following: data management center, NRF, UDM, core network element, new network element, data plane network element, or 6G new data management entity.

[0237] In other embodiments, during data analysis and model training by the data analysis network element, feature datasets and data models are generated. These datasets and data models also require rights management. That is, the rights management center network element not only sends the data rights information of the data collection network element to the data analysis network element, but also needs to negotiate the data rights of the data analysis network element.

[0238] Exemplarily, after receiving the data rights and interests information corresponding to the data collection network element sent by the rights and interests management center network element, the data analysis network element sends the data rights and interests request information of the data analysis network element to the rights and interests management center network element (the data rights and interests request information includes: a request for rights and interests such as ownership of the feature data set and / or data model generated during the data analysis process, profit sharing strategy, transaction settlement method, etc.); accordingly, the rights and interests management center network element determines the data rights and interests of the data analysis network element based on the data rights and interests request information of the data analysis network element, and sends the data rights and interests information of the data analysis network element to the data analysis network element (for example, the rights and interests management center network element sends a broadcast message, and the broadcast message includes the data rights and interests information of the data analysis network element).

[0239] The rights management center network element may include at least one of the following: a core network element (e.g., PCF, SMF, UDM, UPF, or UDR) and a new network element (e.g., a data plane management network element). The data analysis network element may include at least one of the following: a core network element (e.g., NWDAF network element) and a new network element (e.g., a data plane analysis network element).

[0240] Scenario 7: Introduce the rights management network element, which will perform rights management.

[0241] In some embodiments, the network subject may manage data rights and interests by exchanging information related to data rights and interests with the rights and interests management network element.

[0242] Exemplarily, the equity management network element may be a function, entity, node, protocol layer or component related to equity. For example, the equity management network element is an equity management function, an equity management entity, an equity management node, an equity management layer or an equity management component. For example, the equity management network element may include at least one of the following: a task manager, a network controller, a core network function, a wireless access network, a new network management entity, a new protocol layer and a new component. Described from the perspective of type, the equity management network element includes but is not limited to: a dedicated equity network element (for example, an equity execution network element, an equity acquisition network element, an equity reporting network element, an equity request network element), and an enhanced network element formed by adding equity management functions to an existing network element.

[0243] Exemplarily, the rights management network element can be a new network function of the core network; or, the rights management network element can be part of the core network network function; or, the rights management network element can be deployed together with the core network function; for example, the rights management network element can be deployed in the CU, DU, PDCP layer, RLC layer, MAC layer or as an independent functional protocol layer.

[0244] For example, from the perspective of network layers, the rights management network element can be a centralized rights management network element, or the rights management network element can be a multi-level and multi-layered management network element. For example, the core network serves as a centralized rights management network element. In another example, the core network serves as a first-level rights management network element, responsible for rights management of the entire network; the base station serves as a second-level rights management network element, performing wireless-side rights management under the authorization of the core network; and the terminal serves as a third-level rights management network element, performing rights negotiation interactions between terminals under the authorization of the core network and / or base station.

[0245] For example, the rights management network element may also be a distributed rights management network element, each of which has certain rights formulation, rights negotiation, and rights trading capabilities. For example, each terminal has certain data rights, and data rights trading is carried out between terminals.

[0246] Exemplarily, the equity management network element may also be an enhanced network element, for example, an equity management unit is added to the CU to form a CU enhanced network element with equity management function.

[0247] Scenario 8: Lifecycle management of data rights and interests.

[0248] During the process of data generation and extinction, data rights and interests may also change. The validity period of data rights and interests and the life cycle of data rights and interests may be independent of the life cycle of data, that is, the life cycle management of data rights and interests includes the life cycle management from the generation of rights and interests to the extinction of rights and interests. The rights and interests of data may also disappear during the existence of data, and the data rights and interests may still exist when the data disappears. For example, the terminal provides measurement data to the network management center, and the network management center grants the terminal a profit-sharing right for the measurement data for one month. After one month, the network management center terminates the terminal's profit-sharing right for the measurement data and provides the data to other network entities for free. For example, an operator provides data to a third-party AI model training platform for AI model training to generate an AI model. Exemplarily, the third-party AI model training platform first sends a data rights and interests request message to the operator (requesting to obtain the corresponding data usage rights to train the AI ​​model); accordingly, the operator determines the data rights and interests of the third-party AI model training platform based on the data rights and interests request message sent by the third-party AI model training platform, and sends the data rights and interests information of the third-party AI model training platform. The data rights and interests information stipulates that: when an operator provides data to a third-party AI model training platform, the third-party AI model training platform has the right to use the data, but the data belongs to the operator; the AI ​​model generated by the third-party AI model training platform through training using this data belongs to the third-party AI model training platform, but the operator has the right to share in the profits of the AI ​​model for a certain period of time. From the provisions of the data rights and interests information, it can be seen that even if the data provided by the operator is no longer used, the data rights and interests can still exist for a period of time (for example, the operator has the right to share in the profits of the AI ​​model for a certain period of time).

[0249] Scenario 9: Rights and interests management of new network elements.

[0250] With technological advancements, a variety of new network elements will emerge in the future, bringing new value to the network. For example, smart super terminals can provide important wireless network coverage, relay services, and collaborative work in local area scenarios. For example, determining the rights and interests of smart super terminals can be achieved by: the network or operator first determines the data rights and interests of the smart super terminal based on the capability information reported by the smart terminal, and then sends the data rights and interests information belonging to the smart super terminal to the smart terminal. This can encourage the smart super terminal to provide auxiliary network services, thereby maximizing the utilization of terminal resources. At the same time, the smart super terminal can also obtain certain value feedback benefits by receiving data rights and interests information.

[0251] In some embodiments, the self-deployment of new network element nodes can alleviate the deployment difficulties of operators. For example, the new network element nodes may include at least one of the following: reconfigurable intelligence surface (RIS), small base stations for homes or enterprises, and roadside equipment. For example, by granting data rights to building properties, operators encourage building properties to install RIS patches on the glass exterior walls of buildings; by negotiating with households or enterprises, operators allow households or enterprises to have data rights to build their own base stations, and encourage households or enterprises to build their own flexibly deployed small base stations (which are under the jurisdiction of households and enterprises) to improve network coverage capabilities. Rights management fully utilizes the value of network participants through data rights confirmation and data rights information transmission for the above-mentioned new network elements, as well as the process of new network elements obtaining data rights, and reduces the network procurement costs and the pressure of network planning, construction, and maintenance of telecom operators.

[0252] Scenario 10: Data rights and information transactions.

[0253] With the future integrated deployment of space, air, and ground, terrestrial telecom operators can leverage satellite operators' satellite antenna resources to achieve wireless coverage in remote or specialized areas. Satellite operators can also share and utilize the surplus computing power resources of terrestrial telecom operators. When different operators interact with data, they need to transfer data rights information. This data rights information provides information about data rights trading rules, billing methods, and data transaction methods, allowing them to conduct commercial transactions based on data rights information.

[0254] The above mainly introduces the scheme of the embodiment of the present disclosure from the perspective of method. It can be understood that in order to realize the above functions, the data rights management device includes at least one of the hardware structure and software modules corresponding to the execution of each function. It should be easy for those skilled in the art to realize that, in combination with the units and algorithm steps of each example described in the embodiment disclosed herein, the embodiment of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiment of the present disclosure.

[0255] It is understandable that, in order to implement the above functions, the data rights management device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the algorithm steps of each example described in the embodiments of the present disclosure, the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present disclosure.

[0256] The embodiment of the present disclosure can divide the data rights management device into functional modules according to the above-mentioned method embodiment. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one functional module. The above-mentioned integrated module can be implemented in the form of hardware or software. It should be noted that the division of modules in the embodiment of the present disclosure is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0257] Figure 7 is a schematic diagram of the structure of a data rights management device provided in an embodiment of the present disclosure. The data rights management device is applied to a first network element and is configured to execute the data rights management method provided in the above method embodiment. As shown in Figure 7, the data rights management device 400 includes a determination module 401 and a sending module 402. In other embodiments, the data rights management device 400 may also include a receiving module 403.

[0258] The determination module 401 is configured to determine the data rights and interests of the second network element. The data rights and interests of the second network element are used to represent the rights and interests of the second network element in relation to the data generated by the second network element.

[0259] The sending module 402 is configured to send first data rights and interests information to the second network element, where the first data rights and interests information includes data rights and interests related information of the second network element.

[0260] In some embodiments, data rights and interests include at least one of the following: data usage scope, data privacy level, data computing capabilities, data ownership, data processing rights, data use rights, data maintenance rights, data management rights, data privacy and security protection rights, data profit sharing strategy, data rights and interests validity period, data rights and interests life cycle, data rights and interests type, data rights and interests billing method, data rights and interests transaction method, and incentives obtained by the second network element for generating data.

[0261] In some embodiments, the first data interest information includes one of the following:

[0262] Information on data rights configuration;

[0263] Information on changes in data rights;

[0264] Information on the termination of data rights.

[0265] In some embodiments, the determination module 401 is used to receive a first data rights request message sent by a second network element; the first data rights request message carries at least one of the following information: capability information related to the data rights of the second network element; the data rights that the second network element expects to obtain; and determine the data rights of the second network element based on the first data rights request message.

[0266] In some embodiments, the receiving module 403 is used to receive a response message to the first data rights and interests information sent by the second network element, where the response message to the first data rights and interests information includes at least one of the following: a rights and interests feedback message, where the rights and interests feedback message includes a feedback response from the second network element on whether the content indicated by the first data rights and interests information is accepted; a rights and interests negotiation request, where the rights and interests negotiation request includes a request from the second network element to modify the first data rights and interests information; second data rights and interests information, where the second data rights and interests information is rights and interests auxiliary information for the second network element to assist the first network element in determining the first data rights and interests information; and an effect feedback message, where the effect feedback information includes a report feedback from the second network element on the execution effect of the task corresponding to the first data rights and interests information.

[0267] In some embodiments, the sending module 402 is configured to send a second data rights request message to the second network element, where the second data rights request message carries the first data rights information; or, receive the first data rights request message sent by the second network element, and send a response message to the first data rights request message to the second network element, where the response message to the first data rights request message carries the first data rights information; or, receive a data service registration message sent by the second network element, and send a response message to the data service registration message to the second network element, where the response message to the data service registration message carries the first data rights information; or, receive a data service query message sent by the second network element, and send a response message to the data service query message to the second network element, where the response message to the service query message carries the first data rights information; or , sending a connection request message to the second network element, the connection request message carrying the first data rights and interests information; or, receiving the connection request message sent by the second network element, and sending a response message to the connection request message to the second network element, the response message to the connection request message carrying the first data rights and interests information; or, sending a broadcast message, the broadcast message carrying the first data rights and interests information; or, sending a system configuration message, the system configuration message carrying the first data rights and interests information; or, sending quality of service (QoS) information, the QoS information carrying the first data rights and interests information; or, sending a data packet, the header of the data packet carries the first data rights and interests information; or, sending a data packet, the data area of ​​the data packet carries the first data rights and interests information; or, sending an authentication message to the second network element, the authentication message carrying the first data rights and interests information.

[0268] In some embodiments, the QoS information includes at least one of the following: QoS characteristic parameters, QoS profile, QoS rule, and service level agreement (SLA) contract information.

[0269] In some embodiments, the sending module 402 is used to send a signaling message to the second network element, where the signaling message carries the first data rights information, wherein the signaling message includes at least one of the following: a non-access stratum (NAS) message, a radio resource control (RRC) message, a system information (SI) message, and a QoS control message.

[0270] In some embodiments, the sending module 402 is configured to send the first data rights information to the second network element via the third network element.

[0271] In some embodiments, the sending module 402 is further configured to send the first data rights and interests information to the third network element, so that the third network element determines the data rights and interests of the third network element according to the first data rights and interests information.

[0272] In some embodiments, the third network element includes at least one of the following: access and mobility management function (AMF) network element, network exposure function (NEF) network element, access network capability exposure network element, relay network element, terminal equipment, base station, wireless access network, business entity, third-party application, capability exposure node and edge node.

[0273] In some embodiments, the first network element includes at least one of the following: a core network, a wireless access network, a business entity, a terminal device, a network management center, a network control center, a network data asset management network element, a rights management network element, a rights management center, a rights management layer, a rights management entity, a rights management function, a rights management component, and a rights management agent.

[0274] In some embodiments, the core network includes at least one of the following: a policy control function (PCF), an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a unified data storage function (UDR), a user plane function (UPF) and a network exposure function (NEF); the wireless access network includes at least one of the following: a centralized unit (CU), a distributed unit (DU), a service data adaptation protocol (SDAP), a packet data convergence protocol (PDCP), a radio link layer control protocol (RLC) and a medium access control (MAC); the equity management network element includes at least one of the following: a dedicated equity network element, and an equity enhanced network element formed by adding an equity management function to an existing network element.

[0275] In some embodiments, the second network element includes at least one of the following: a terminal device, a base station, a wireless access network, a business entity, a core network, a third-party application, a capability exposure node, and an edge node.

[0276] In some embodiments, the core network includes at least one of the following: PCF, AMF, SMF, UDM, UDR, UPF and NEF; the wireless access network includes at least one of the following: CU, DU, SDAP, PDCP, RLC and MAC; the edge node includes: mobile edge computing MEC; the capability exposure node includes at least one of the following: NEF, RAN capability exposure network element.

[0277] Figure 8 is a schematic diagram of the structure of a data rights management device provided in an embodiment of the present disclosure. This device is applied to a second network element and is used to execute the data rights management method provided in the above method embodiment. As shown in Figure 8, the data rights management device 500 includes a receiving module 501 and an acquisition module 502. In other embodiments, the data rights management device 500 may also include a sending module 503.

[0278] The receiving module 501 is configured to receive first data rights information sent by a first network element. The first data rights information includes information related to data rights of a second network element. The data rights are used to represent the rights of the second network element to data generated by itself.

[0279] The acquisition module 502 is configured to acquire the data rights of the second network element according to the first data rights information.

[0280] In some embodiments, the content of data rights and interests includes at least one of the following: data usage scope, data privacy level, data computing capabilities, data ownership, data processing rights, data use rights, data maintenance rights, data management rights, data privacy and security protection rights, data profit sharing strategy, data rights and interests validity period, data rights and interests type, data rights and interests billing method, data rights and interests transaction method and the incentives obtained by the second network element for generating data.

[0281] In some embodiments, the first data interest information includes at least one of the following:

[0282] Information on data rights configuration;

[0283] Information on changes in data rights;

[0284] Information on the termination of data rights.

[0285] In some embodiments, the sending module 503 is configured to send a first data rights request message to the first network element, where the first data rights request message includes at least one of the following: capability information related to the data rights of the second network element; and data rights that the second network element expects to obtain.

[0286] In some embodiments, the sending module 503 is used to send a capability reporting message to the first network element, the capability reporting message including the first data rights request message; or, send a connection establishment request message to the first network element, the connection establishment request message including the first data rights request message; or, send a registration request message to the first network element, the registration request message including the first data rights request message; or, send an authentication request message to the first network element, the authentication request message including the first data rights request message; or, send a response message to the authentication request message sent by the first network element to the first network element, the response message to the authentication request message including the first data rights request message.

[0287] In some embodiments, the receiving module 501 is configured to receive a second data rights request message sent by the first network element, the second data rights request message carrying the first data rights information; or, receive a response message to the first data rights request message sent by the first network element, the response message to the first data rights request message carrying the first data rights information; or, receive a response message to a service registration message sent by the first network element, the response message to the service registration message carrying the first data rights information; or, receive a response message to a service query message sent by the first network element, the response message to the service query message carrying the first data rights information; or, receive a connection request message sent by the first network element, the connection request message carrying the first data rights information; or, receive a response to a connection request message sent by the first network element. response message, the response message of the connection request message carries the first data rights and interests information; or, receiving a broadcast message sent by the first network element, the broadcast message carries the first data rights and interests information; or, receiving a system configuration message sent by the first network element, the system configuration message carries the first data rights and interests information; or, receiving QoS information sent by the first network element, the QoS information carries the first data rights and interests information; or, receiving a data packet sent by the first network element, the header of the data packet carries the first data rights and interests information; or, receiving a data packet sent by the first network element, the data area of ​​the data packet carries the first data rights and interests information; or, receiving an authentication message sent by the first network element, the authentication message carries the first data rights and interests information; or, receiving a connection request message sent by the first network element, the connection request message carries the first data rights and interests information.

[0288] In some embodiments, the QoS information includes at least one of the following: QoS feature parameters, QoS profile, QoS rule, and SLA contract information.

[0289] In some embodiments, the receiving module 501 is used to receive a signaling message sent by the first network element, where the signaling message carries first data rights information; wherein the signaling message includes at least one of the following: NAS message, RRC message, system information SI message, and QoS control message.

[0290] In some embodiments, the sending module 503 is further used to send a response message of the first data rights and interests information to the first network element, and the response message of the first data rights and interests information includes at least one of the following: a rights feedback message, the rights feedback message includes a feedback response of the second network element on whether the content indicated by the first data rights and interests information is accepted; a rights negotiation request, the rights negotiation request includes a request from the second network element to modify the first data rights and interests information; second data rights and interests information, the second data rights and interests information is rights auxiliary information for the second network element to assist the first network element in determining the first data rights and interests information; an effect feedback message; the effect feedback information includes the report feedback of the second network element on the execution effect of the task corresponding to the first data rights and interests information.

[0291] In some embodiments, the sending module 503 is configured to receive the first data rights information sent by the first network element through the third network element.

[0292] In some embodiments, the third network element includes at least one of the following: access and mobility management function (AMF) network element, network exposure function (NEF) network element, access network capability exposure network element, relay network element, terminal equipment, base station, wireless access network, business entity, third-party application, capability exposure node and edge node.

[0293] In some embodiments, the first network element includes at least one of the following: a core network, a wireless access network, a business entity, a terminal device, a network management center, a network control center, a network data asset management network element, a rights management network element, a rights management center, a rights management layer, a rights management entity, a rights management function, a rights management component, and a rights management agent.

[0294] In some embodiments, the second network element includes at least one of the following: a terminal device, a base station, a wireless access network, a business entity, a core network, a third-party application, a capability exposure node, and an edge node.

[0295] Figure 9 is a schematic diagram of the structure of a data rights management device provided in an embodiment of the present disclosure. This device is applied to a third network element and is used to execute the data rights management method provided in the above method embodiment. As shown in Figure 9, the data rights management device 600 includes a receiving module 601. In other embodiments, the data rights management device 600 may also include a sending module 602 and a determining module 603.

[0296] The receiving module 601 is configured to receive first data rights information sent by a first network element, where the first data rights information includes information related to data rights of a second network element. The data rights of the second network element represent the rights of the second network element to data generated by itself.

[0297] In some embodiments, the sending module 602 is configured to send the first data rights information to the second network element.

[0298] In some embodiments, the determination module 603 is configured to determine the data rights and interests of the third network element based on the first data rights and interests information.

[0299] In the case of implementing the functions of the above-mentioned integrated modules in the form of hardware, the embodiment of the present disclosure provides a structure of the communication device involved in the above-mentioned embodiment. As shown in Figure 10, the communication device 700 includes: a memory 701, a processor 702, a communication interface 703, and a bus 704.

[0300] The memory 701 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0301] The processor 702 may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments of the present disclosure. The processor 702 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor 702 may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the embodiments of the present disclosure. The processor 702 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0302] The communication interface 703 is used to connect to other devices via a communication network, such as Ethernet, wireless access network, or wireless local area network (WLAN).

[0303] In some embodiments, memory 701 may exist independently of processor 702 and may be connected to processor 702 via bus 704 to store instructions or program code. When processor 702 calls and executes the instructions or program code stored in memory 701, the data rights management method provided in the embodiments of the present disclosure can be implemented.

[0304] In some embodiments, the memory 701 may also be integrated with the processor 702 .

[0305] Bus 704 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 704 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, FIG10 shows only one thick solid line, but this does not mean that there is only one bus or only one type of bus.

[0306] Some embodiments of the present disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium), which stores computer program instructions. When the computer program instructions are executed on a computer, the computer executes a data rights management method as described in any of the above embodiments.

[0307] Exemplarily, the computer-readable storage media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0308] An embodiment of the present disclosure provides a computer program product comprising instructions. When the computer program product is run on a computer, the computer is enabled to execute the data rights management method described in any one of the above embodiments.

[0309] The above is only a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or replacements within the technical scope disclosed in the present disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A data rights management method, applied to a first network element, wherein: The method comprises: Determining data rights and interests of the second network element, where the data rights and interests of the second network element are used to represent the rights and interests of the second network element related to the data generated by itself; First data rights and interests information is sent to the second network element, where the first data rights and interests information includes data rights and interests related information of the second network element.

2. The method according to claim 1, wherein: The data rights and interests include at least one of the following: scope of data use, degree of data privacy, data computing capability, ownership of data, right to process data, right to use data, right to maintain data, right to manage data, right to protect data privacy and security, data profit sharing strategy, validity period of data rights and interests, life cycle of data rights and interests, type of data rights and interests, billing method of data rights and interests, data rights and interests trading method, and incentives obtained by the second network element for generating data.

3. The method according to any one of claims 1 to 2, wherein: The first data rights and interests information includes one of the following: Information on data rights configuration; Information on changes in data rights; Information on termination of data rights.

4. The method according to any one of claims 1 to 3, wherein: The determining of the data rights and interests of the second network element includes: receiving a first data rights request message sent by the second network element; the first data rights request message carries at least one of the following information: capability information related to the data rights of the second network element; and data rights that the second network element expects to obtain; Determine the data rights and interests of the second network element according to the first data rights and interests request message.

5. The method according to any one of claims 1 to 3, wherein: After sending the first data rights and interests information to the second network element, the method further includes: receiving a response message to the first data rights and interests information sent by the second network element, where the response message to the first data rights and interests information includes at least one of the following: A rights feedback message, wherein the rights feedback message includes a feedback response of whether the second network element accepts the content indicated by the first data rights information; a rights negotiation request, the rights negotiation request comprising a request by the second network element to modify the first data rights information; Second data rights and interests information, where the second data rights and interests information is rights and interests auxiliary information that the second network element assists the first network element in determining the first data rights and interests information; Effect feedback message, wherein the effect feedback information includes the report feedback of the second network element on the execution effect of the task corresponding to the first data rights and interests information.

6. The method according to any one of claims 1 to 3, wherein: The sending the first data rights and interests information to the second network element includes: Sending a second data rights request message to the second network element, where the second data rights request message carries the first data rights information; or, receiving a first data rights request message sent by the second network element, and sending a response message of the first data rights request message to the second network element, where the response message of the first data rights request message carries the first data rights information; or, receiving a data service registration message sent by the second network element, and sending a response message of the data service registration message to the second network element, wherein the response message of the data service registration message carries the first data rights and interests information; or, receiving a service query message sent by the second network element, and sending a response message to the service query message to the second network element, wherein the response message to the service query message carries the first data rights information; or, Sending a connection request message to the second network element, where the connection request message carries the first data rights information; or, receiving a connection request message sent by the second network element, and sending a response message to the connection request message to the second network element, wherein the response message to the connection request message carries the first data rights and interests information; or, Send a broadcast message, where the broadcast message carries the first data rights information; or, Sending a system configuration message, where the system configuration message carries the first data rights information; or, Sending quality of service QoS information, where the QoS information carries the first data rights and interests information; or, Sending a data packet, wherein the header of the data packet carries the first data rights information; or, Sending a data packet, wherein the data area of ​​the data packet carries the first data rights information; or, An authentication message is sent to the second network element, where the authentication message carries the first data rights information.

7. The method according to claim 6, wherein: The QoS information includes at least one of the following: QoS characteristic parameters, QoS profile, QoS rule and service level agreement (SLA) contract information.

8. The method according to any one of claims 1 to 3, wherein: The sending the first data rights and interests information to the second network element includes: A signaling message is sent to the second network element, where the signaling message carries the first data rights and interests information, wherein the signaling message includes at least one of the following: a non-access layer NAS message, a radio resource control RRC message, a system information SI message, and a QoS control message.

9. The method according to claim 1, wherein: The sending the first data rights and interests information to the second network element includes: The first data rights and interests information is sent to the second network element through the third network element.

10. The method according to claim 1, further comprising: The first data rights and interests information is sent to a third network element, so that the third network element determines the data rights and interests of the third network element according to the first data rights and interests information.

11. The method according to claim 9 or 10, wherein: The third network element includes at least one of the following: access and mobility management function AMF network element, network open function NEF network element, access network capability open network element, relay network element, terminal equipment, base station, wireless access network, business entity, third-party application, capability open node and edge node.

12. The method according to any one of claims 1 to 3, wherein: The first network element includes at least one of the following: a core network, a wireless access network, a business entity, a terminal device, a network management center, a network control center, a network data asset management network element, a rights management network element, a rights management center, a rights management layer, a rights management entity, a rights management function, a rights management component, and a rights management agent.

13. The method according to claim 12, wherein: The core network includes at least one of the following: a policy control function PCF, an access and mobility management function AMF, a session management function SMF, a unified data management UDM, a unified data storage function UDR, a user plane function UPF and a network open function NEF; The wireless access network includes at least one of the following: a centralized unit CU, a distributed unit DU, a service data adaptation protocol SDAP, a packet data convergence protocol PDCP, a radio link layer control protocol RLC, and a medium access control MAC; The equity management network element includes at least one of the following: a dedicated equity network element, and an equity enhancement network element formed by adding an equity management function to an existing network element.

14. The method according to any one of claims 1 to 3, wherein: The second network element includes at least one of the following: terminal equipment, base station, wireless access network, business entity, core network, third-party application, capability exposure node and edge node.

15. The method according to claim 14, wherein: The core network includes at least one of the following: PCF, AMF, SMF, UDM, UDR, UPF and NEF; The wireless access network includes at least one of the following: CU, DU, SDAP, PDCP, RLC and MAC; The edge nodes include: mobile edge computing MEC; The capability opening node includes at least one of the following: NEF, RAN capability opening network element.

16. A data rights management method, applied to a second network element, wherein: The method comprises: receiving first data rights and interests information sent by the first network element, where the first data rights and interests information includes data rights and interests related information of the second network element, where the data rights and interests are used to represent the rights and interests of the second network element related to the data generated by itself; The data rights and interests of the second network element are obtained according to the first data rights and interests information.

17. The method according to claim 16, wherein: The content of the data rights and interests includes at least one of the following: scope of data use, degree of data privacy, data computing capability, ownership of data, right to process data, right to use data, right to maintain data, right to manage data, right to protect data privacy and security, data profit sharing strategy, validity period of data rights and interests, life cycle of data rights and interests, type of data rights and interests, billing method of data rights and interests, data rights and interests transaction method and incentives obtained by the second network element for generating data.

18. The method according to any one of claims 16 to 17, wherein: The first data rights and interests information includes at least one of the following: Information on data rights configuration; Information on changes in data rights; Information on termination of data rights.

19. The method according to any one of claims 16 to 18, further comprising: A first data rights request message is sent to the first network element, where the first data rights request message includes at least one of the following: capability information related to the data rights of the second network element; and data rights that the second network element expects to obtain.

20. The method according to claim 19, wherein: The sending a first data rights request message to the first network element includes: Sending a capability reporting message to the first network element, where the capability reporting message includes the first data rights request message; or, Sending a connection establishment request message to the first network element, where the connection establishment request message includes the first data rights request message; or, Sending a registration request message to the first network element, where the registration request message includes the first data rights request message; or, Sending an authentication request message to the first network element, where the authentication request message includes the first data rights request message; or, A response message to the authentication request message sent by the first network element is sent to the first network element, where the response message to the authentication request message includes the first data rights request message.

21. The method according to any one of claims 16 to 18, wherein: The receiving the first data rights and interests information sent by the first network element includes: receiving a second data rights request message sent by the first network element, where the second data rights request message carries the first data rights information; or, receiving a response message to a first data rights request message sent by the first network element, where the response message to the first data rights request message carries the first data rights information; or, receiving a response message to a service registration message sent by the first network element, wherein the response message to the service registration message carries first data rights information; or, receiving a response message to the service query message sent by the first network element, where the response message to the service query message carries the first data rights information; or, receiving a connection request message sent by the first network element, where the connection request message carries the first data rights information; or, receiving a response message to a connection request message sent by the first network element, wherein the response message to the connection request message carries the first data rights information; or, receiving a broadcast message sent by the first network element, where the broadcast message carries the first data rights information; or, receiving a system configuration message sent by the first network element, where the system configuration message carries the first data rights and interests information; or, receiving QoS information sent by the first network element, where the QoS information carries the first data rights and interests information; or, receiving a data packet sent by the first network element, wherein a header of the data packet carries the first data rights information; or, receiving a data packet sent by the first network element, wherein a data area of ​​the data packet carries the first data rights information; or, An authentication message sent by the first network element is received, where the authentication message carries the first data rights information.

22. The method according to claim 21, wherein: The QoS information includes at least one of the following: QoS characteristic parameters, QoS profile, QoS rule and SLA contract information.

23. The method according to any one of claims 16 to 18, wherein: The receiving the first data rights and interests information sent by the first network element includes: Receive a signaling message sent by the first network element, where the signaling message carries the first data rights and interests information; wherein the signaling message includes at least one of the following: a NAS message, an RRC message, a system information SI message, and a QoS control message.

24. The method according to any one of claims 16 to 18, further comprising: Sending a response message of the first data rights and interests information to the first network element, where the response message of the first data rights and interests information includes at least one of the following: A rights feedback message, wherein the rights feedback message includes a feedback response of whether the second network element accepts the content indicated by the first data rights information; a rights negotiation request, the rights negotiation request comprising a request by the second network element to modify the first data rights information; Second data rights and interests information, where the second data rights and interests information is rights and interests auxiliary information that the second network element assists the first network element in determining the first data rights and interests information; Effect feedback message; the effect feedback information includes the reporting feedback of the second network element on the execution effect of the task corresponding to the first data rights and interests information.

25. The method according to any one of claims 16 to 18, wherein: The receiving the first data rights and interests information sent by the first network element includes: The first data rights and interests information sent by the first network element is received through a third network element.

26. The method according to claim 25, wherein: The third network element includes at least one of the following: access and mobility management function AMF network element, network open function NEF network element, access network capability open network element, relay network element, terminal equipment, base station, wireless access network, business entity, third-party application, capability open node and edge node.

27. The method according to any one of claims 16 to 18, wherein: The first network element includes at least one of the following: a core network, a wireless access network, a business entity, a terminal device, a network management center, a network control center, a network data asset management network element, a rights management network element, a rights management center, a rights management layer, a rights management entity, a rights management function, a rights management component, and a rights management agent.

28. The method according to any one of claims 16 to 18, wherein: The second network element includes at least one of the following: terminal equipment, base station, wireless access network, business entity, core network, third-party application, capability exposure node and edge node.

29. A data rights management method, applied to a third network element, wherein: The method comprises: First data rights and interests information sent by a first network element is received, where the first data rights and interests information includes data rights and interests related information of a second network element, where the data rights and interests of the second network element are used to represent the rights and interests of the second network element related to data generated by itself.

30. The method of claim 29, further comprising: Send the first data rights and interests information to the second network element.

31. The method of claim 29, further comprising: Based on the first data rights and interests information, determine the data rights and interests of the third network element.

32. A communication device, comprising: a processor and a memory for storing instructions executable by the processor; The processor is configured to execute the instructions so that the communication device performs the data rights management method according to any one of claims 1 to 31.

33. A computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on an electronic device, the electronic device executes the data rights management method according to any one of claims 1 to 31.

Images