COMMUNICATIONS METHOD, DEVICE, AND SYSTEM

Abstract

[0009] The present application discloses a communication method, a device, and a system. A first network element sends a first request to a second network element, the first request being for requesting authorization information for user-related data, the first request including user information and a first range of use of the user-related data, the first range of use including at least one of information on a first use target, a first purpose of use, and a first time period for use. The first network element receives a first response sent by the second network element, the first response including authorization information indicating whether a user corresponding to the user information allows the associated data to be used in the first range of use. When attempting to obtain user-related data for a user corresponding to the user information, the first network element may first send the first request to the second network element and obtain the authorization information via the second network element. When the authorization information indicates that the user allows the user-related data to be used in the first range of use, the first network element may perform a related operation based on the user-based data.

Description

[Technical field]

[0001] The present application relates to the field of communication technologies, and in particular to communication methods, devices and systems. [Background technology]

[0002] In current technology, user-based data generated by a user in a telecommunications operator network belongs to that user, and the operator network is prohibited from obtaining or using that user-based data at will.

[0003] In practical applications, there are some scenarios where a communication operator network needs to acquire and use user-based data to perform data analysis, etc. based on the acquired user-based data. However, in current technology, the communication operator network does not provide a solution for accurately acquiring authorization information of user-related data. Summary of the Invention

[0004] In view of this, the embodiments of the present application provide a communication method, device and system, through which authorization information of user-related data is accurately obtained.

[0005] In order to solve the above problems, the embodiments of the present application provide the following technical solutions.

[0006] According to a first aspect, an embodiment of the present application provides a communication method, the method including: a first network element sending a first request to a second network element. The first request is for requesting authorization information of user-related data, the first request including user information and a first use scope of the user-related data, the first use scope including at least one of the following information: a first use object, a first use purpose, and a first use time. The first network element receives a first response sent by the second network element. The first response includes authorization information, the authorization information indicating whether a user corresponding to the user information allows the associated data to be used for the first use scope. In this implementation, the user information indicates a user or several users, and the user information may be an identifier of an area where the user is located, an identifier of the user, an identifier of a user group to which the user belongs, an identifier of a network slice corresponding to the user, a data network name DNN of the user, and an identifier of a network element to which the user belongs. When intending to obtain user-related data of a user corresponding to the user information, the first network element may first send a first request to the second network element to obtain authorization information of the user through the second network element, whereby, if the authorization information indicates that the user corresponding to the user information permits the user-related data to be used for the first scope of use, the first network element obtains the user-related data, whereby the first network element may perform a related operation based on the user-based data. In this implementation, the first network element may accurately obtain the authorization information corresponding to the user-related data by sending the first request to the second network element, thereby performing the accurate obtaining.

[0007] In a possible implementation, the user-related data includes first data and / or second data related to a user, the first data includes data corresponding to the user generated by at least one of a terminal device, an application server, or a network device, and the second data includes a data analysis result obtained by performing a data analysis based on the first data. The first data may be classified into raw data and processed data. The raw data may include raw data corresponding to the user generated by at least one of a terminal device, an application server, or a network device. The processed data includes data processed based on the raw data. In particular, operations such as aggregation and anonymization may be performed on the raw data. In this implementation, the user-based data is divided to obtain multiple types of data and set separate authorization information for each type of data, thereby more comprehensively protecting the user-related data.

[0008] In a possible implementation, the first request further includes a first type identifier, and the first type identifier is for identifying a type of the user-related data, i.e., the first type identifier is for identifying that the first data and / or the second data in the user-related data need to be obtained. In this implementation, when requesting the authorization information from the second network element, the first network element requests the authorization information of the user-related data corresponding to the first type identifier. Specifically, if the first type identifier is an event identifier, it indicates that the authorization information of the first data is requested, or if the first type identifier is an analysis identifier, it indicates that the authorization information of the second data is requested.

[0009] In a possible implementation, when the user-related data is the first data, the first type identifier is an event identifier, and the first data is data associated with an event corresponding to the event identifier.

[0010] In a possible implementation, when the user-related data is the second data, the first type identifier is an analysis identifier, and the second data is a data analysis result corresponding to the analysis identifier.

[0011] In a possible implementation, when the first network element is a network data analysis function NWDAF network element, the second network element is an integrated data management UDM network element, a user data repository UDR network element, an authentication service function AUSF network element, or a terminal device.

[0012] In a possible implementation, when the user-related data is the first data, the first purpose of use may include performing data analysis, i.e., the first purpose of use indicates that data analysis is performed on the first data to obtain data analysis results. In this implementation, the purpose of obtaining the first data may be indicated by the first purpose of use, and user approval information for the purpose of use may be obtained.

[0013] In a possible implementation, when the user-related data is the first data, the first scope of use may further include an analysis identifier, and the analysis identifier is for indicating to perform a data analysis on the first data to obtain a data analysis result corresponding to the analysis identifier. In this implementation, a specific type of analysis to be performed on the first data may be specifically indicated by the analysis identifier.

[0014] In a possible implementation, when the user-related data is the first data, the first purpose of use may be to obtain data analysis results or to open up to a third-party AF for use, or it may be further defined which data analysis results are specifically to be obtained, for example, user movement trajectory analysis results are obtained.

[0015] In a possible implementation, the first request further includes a second use scope corresponding to the data analysis result, and the second use scope includes at least one of the following information: a second use target, a second use purpose, and a second use time. In this implementation, when a data analysis result obtained by performing data analysis on the first data is obtained, the use scope of the data analysis result may be further set. For example, the second use target is for indicating the target for which the data analysis result will be used, the second use purpose is for indicating the purpose for which the data analysis result will be used, and the second use time is for indicating the time when the data analysis result will be used. By further setting the second use scope, user approval information including the second use scope is obtained.

[0016] In a possible implementation, the first network element is a network publication function NEF network element, and the second network element is a unified data management UDM network element, a user data repository UDR network element, an authentication service function AUSF network element, or a terminal device. In this implementation, if the first network element is a NEF network element, the first network element may send a first request to any one of the UDM network element, the UDR network element, the AUSF network element, or the terminal device to request to obtain authorization information of the user.

[0017] In a possible implementation, the first consumer is an application server AF. In this implementation, if the first network element is a NEF network element, the consumer of the user-related data requested by the first network element may be the AF.

[0018] In a possible implementation, when the first network element is an access and mobility management function AMF network element, the second network element is an integrated data management UDM network element, a user data repository UDR network element, an authentication service function AUSF network element, or a terminal device.

[0019] In a possible implementation, the condition for the first network element to send the first request to the second network element may be triggered by the requirement of the first network element, or may be the case that the first network element receives a second request sent by a third network element, the second request being for requesting to obtain user-related data. The first network element sends the first request to the second network element based on the second request. In this implementation, when receiving the second request sent by the third network element, the first network element sends the first request to the second network element to request authorization information of the user.

[0020] In a possible implementation, the second request may include user information and a third use scope, where the user information is for identifying the user, and the user information may be an identifier of an area where the user is located, an identifier of the user, an identifier of a user group to which the user belongs, an identifier of a network slice corresponding to the user, a data network name DNN of the user, and an identifier of a network element to which the user belongs. The third use scope includes at least one of information of a third use object, a third use purpose, and a third use time. The third use object is for indicating a use object of the user-related data requested by the second request, the third use purpose is for indicating a use purpose of the user-related data requested by the second request, and the third use time is for indicating a use time of the user-related data requested by the second request.

[0021] In a possible implementation, the second request may further include a second type identifier, the second type identifier for identifying a type of user-related data requested by the third network element. The second type identifier may be an event identifier or an analysis identifier. In this case, the first network element may determine the first type identifier based on the second type identifier. In this implementation, if the second request includes the second type identifier, the first network element may determine the first type identifier in the first request based on the second type identifier and present the first type identifier in the first request.

[0022] In a possible implementation, the first network element determining the first type identifier based on the second type identifier may include the first network element determining the second data type identifier as the first type identifier.

[0023] In a possible implementation, the first network element determining the first type identifier based on the second type identifier may include the first network element determining the first type identifier based on configuration information and the second data type identifier, where the configuration information indicates a correspondence between the first type identifier and the second data type identifier, and in this implementation, the first network element maps the second type identifier to the first type identifier based on the configuration information and includes the first type identifier in the first request.

[0024] In a possible implementation, if the authorization information indicates that the user corresponding to the user information has authorized the user-related data to be used for the first scope of use, the method further includes the first network element sending a second response to the third network element, the second response including the user-related data requested by the third network element.

[0025] In a possible implementation, the third network element is an application server AF, a network function NF network element, a network management system network element, or a terminal device.

[0026] In a possible implementation, if the first network element is an application function AF network element, the second network element may be a network publication function NEF network element.

[0027] In a possible implementation, the method further includes the first network element acquiring the user-related data if the authorization information indicates that a user corresponding to the user information authorizes the user-related data to be used for the first scope of use. The first network element acquires the user-related data if the user authorizes the user-related data to be used, which avoids misuse of the user-related data and improves security of the user-related data.

[0028] In a possible implementation, the method further includes the first network element deleting the user-associated data or stopping acquiring the user-associated data if the authorization information indicates that the user corresponding to the user information has not authorized the user-associated data to be used for the first scope of use. In this implementation, if the user has not authorized the user-associated data to be used, the first network element deletes the user-associated data if the first network element has acquired the user-associated data, or stops acquiring the user-associated data if the first network element has not acquired the user-associated data, thereby ensuring security of the user-associated data.

[0029] In a possible implementation, if the approval information indicates that the user corresponding to the user information does not authorize the user-related data to be used for the first scope of use, the first response further includes reason information used to indicate why the user-related data is not authorized to be used. In this implementation, if the user does not authorize the user-related data to be used, the first response may further include reason information indicating why the user-related data is not authorized to be used, to inform the specific reason why the user-related data is not authorized to be used.

[0030] According to a second aspect, an embodiment of the present application provides a communication method, the method including: receiving, by a second network element, a first request sent by a first network element, the first request being for requesting authorization information of user-related data, the first request including user information and a first usage scope of the user-related data, the first usage scope including at least one of information of a first use subject, a first usage purpose, and a first usage time; determining, by the second network element, the authorization information based on the first request; and transmitting, by the second network element, a first response to the first network element, the first response including the authorization information, the authorization information indicating whether a user corresponding to the user information has allowed the user-related data to be used with respect to the first usage scope.

[0031] In a possible implementation, the second network element determining authorization information based on the first request includes the first network element determining authorization information corresponding to the user information based on whether the first request matches stored authorization information of the network user. In this implementation, the second network element may pre-store authorization information of users in the network. When receiving the first request sent by the first network element, the second network element determines authorization information corresponding to the user information based on whether the user information in the first request matches the authorization information of the user.

[0032] In a possible implementation, the second network element determining the authorization information based on the first request includes the second network element sending a third request to the terminal device corresponding to the user information based on the first request, the third request being for requesting the authorization information corresponding to the user information from the terminal device, and the second network element receiving a third response sent by the terminal device, the third response including the authorization information corresponding to the user information. In this implementation, the second network element obtains the authorization information corresponding to the user information by sending the third request to the terminal device.

[0033] In a possible implementation, the second network element determining the authorization information based on the first request includes the second network element initiating a fourth request to a fourth network element based on the first request, the fourth request being for requesting authorization information from the fourth network element corresponding to the user information, and the second network element receiving a fourth response sent by the fourth network element, the fourth response including the authorization information corresponding to the user information. In this implementation, the second network element obtains the authorization information corresponding to the user information by sending the fourth request to the fourth network element.

[0034] In a possible implementation, the user-related data includes first data and / or second data related to a user, the first data including data corresponding to the user generated by at least one of a terminal device, an application server, or a network device, and the second data including data analysis results obtained by performing data analysis based on the first data.

[0035] In a possible implementation, the first request further includes a first type identifier, the first type identifier for indicating a type of user-related data, and the first request for requesting approval information for the user-related data includes the first request for requesting approval information for user-related data corresponding to the first type identifier.

[0036] In a possible implementation, the first network element is a network data analysis function NWDAF network element and the second network element is an integrated data management UDM network element, a user data repository UDR network element, an authentication service function AUSF network element or a terminal device.

[0037] In a possible implementation, if the first data is user-related data, the first use is a network data analysis function NWDAF network element.

[0038] In a possible implementation, when the user-related data is the first data, the first purpose of use includes performing data analysis.

[0039] In a possible implementation, when the user-related data is the first data, the first scope of use further includes an analysis identifier, the analysis identifier for indicating to perform a data analysis on the first data to obtain a data analysis result corresponding to the analysis identifier.

[0040] In a possible implementation, the first request further includes a second scope of use corresponding to the data analysis result, and the second scope of use includes at least one of information of a second subject of use, a second purpose of use, and a second time of use.

[0041] In a possible implementation, if the user data is the second data, the first type identifier is an analysis identifier.

[0042] In a possible implementation, the first network element is a network publication function NEF network element and the second network element is an integrated data management UDM network element, a user data repository UDR network element, an authentication service function AUSF network element or a terminal device.

[0043] In a possible implementation, the first user is an application server AF.

[0044] In a possible implementation, the first network element is an access and mobility management function AMF network element, and the second network element is an integrated data management UDM network element, a user data repository UDR network element, an authentication service function AUSF network element, or a terminal device.

[0045] In a possible implementation, if the approval information indicates that the user corresponding to the user information has not authorized the user-related data to be used in relation to the first scope of use, the first response further includes reason information indicating why the user-related data is not authorized to be used.

[0046] According to a third aspect, an embodiment of the present application provides a communication method, the method including: a third network element sending a second request to the first network element. The second request is for requesting to obtain user-related data, and includes user information and a third use scope. The third use scope includes at least one of the following information: a third use subject, a third use purpose, and a third use time. The third network element receives a second response sent by the first network element. The second response includes the user-related data or indication information, and the indication information indicates that the user-related data has failed to be obtained.

[0047] In a possible implementation, the user-related data includes first data and / or second data related to a user, the first data including data corresponding to the user generated by at least one of a terminal device, an application server, or a network device, and the second data including data analysis results obtained by performing data analysis based on the first data.

[0048] In a possible implementation, when the second response includes the indication information, the second response further includes failure reason information, and notifies the third network element of the specific failure reason through the failure reason information.

[0049] In a possible implementation, the second request further includes a second type identifier, the second type identifier for identifying a type of user-related data that the third network element requests to obtain. In this implementation, the second type identifier for identifying the first data or the second data in the user-related data. If the user-related data requested by the third network element is the first data, the second type identifier is an event identifier. If the user-related data requested by the third network element is the second data, the second type identifier is an analysis identifier.

[0050] In a possible implementation, the third network element may be an application server AF or a network function NF network element.

[0051] According to a fourth aspect, an embodiment of the present application provides a communication method, the method including: a terminal device receiving a third request sent by a second network element. The third request is for requesting authorization information of the user-related data, the third request including a first use scope of the user-related data, the first use scope including at least one of the following information: a first use object, a first use purpose, and a first use time. The terminal device determines the authorization information based on the third request, and sends a third response to the second network element. The third response includes the authorization information.

[0052] In a possible implementation, the user-related data includes first data and / or second data related to a user, the first data including data corresponding to the user generated by at least one of a terminal device, an application server, or a network device, and the second data including data analysis results obtained by performing data analysis based on the first data.

[0053] According to a fifth aspect, a sending unit configured to send a first request to a second network element, the first request being for requesting authorization information of user-related data, the first request including user information and a first use scope of the user-related data, the first use scope including at least one of the following information: a first use object, a first use purpose, and a first use time; A communication device is provided that includes: a receiving unit configured to receive a first response transmitted by a second network element, the first response including authorization information, the authorization information indicating whether a user corresponding to the user information has authorized the user-related data to be used with respect to a first scope of use.

[0054] In a possible implementation, the user-related data includes first data and / or second data related to a user, the first data including data corresponding to the user generated by at least one of a terminal device, an application server, or a network device, and the second data including data analysis results obtained by performing data analysis based on the first data.

[0055] In a possible implementation, the first request further includes a first type identifier, the first type identifier for identifying a type of the user-related data; The first request is for requesting authorization information for user-related data, The first request includes being to request authorization information for user-related data corresponding to the first type identifier.

[0056] In a possible implementation, when the user-related data is the first data, the first type identifier is an event identifier, and the first data is data related to an event corresponding to the event identifier.

[0057] In a possible implementation, the first network element is a Network Data Analysis Function (NWDAF) network element and the second network element is a Unified Data Management (UDM) network element. , Yu The Authentication Service Function may be a User Data Repository (UDR) network element, an Authentication Service Function (AUSF) network element, or a terminal device.

[0058] In a possible implementation, if the first data is user-related data, the first use is a network data analysis function NWDAF network element.

[0059] In a possible implementation, when the first data is user-related data, the first purpose of use includes performing data analysis.

[0060] In a possible implementation, when the user-related data is the first data, the first scope of use further includes an analysis identifier, the analysis identifier for indicating to perform a data analysis on the first data to obtain a data analysis result corresponding to the analysis identifier.

[0061] In a possible implementation, the first request further includes a second scope of use corresponding to the data analysis result, and the second scope of use includes at least one of information of a second subject of use, a second purpose of use, and a second time of use.

[0062] In a possible implementation, when the user-related data is the second data, the first type identifier is an analysis identifier, and the second data is a data analysis result corresponding to the analysis identifier.

[0063] In a possible implementation, the communication device is a Network Exposure Function NEF network element and the second network element is a Unified Data Management UDM network element. , Yu The Authentication Service Function may be a User Data Repository (UDR) network element, an Authentication Service Function (AUSF) network element, or a terminal device.

[0064] In a possible implementation, the first user is an application server AF.

[0065] In a possible implementation, if the communication device is an access and mobility management function AMF network element, the second network element is an integrated data management UDM network element. , Yu The Authentication Service Function may be a User Data Repository (UDR) network element, an Authentication Service Function (AUSF) network element, or a terminal device.

[0066] In a possible implementation, the receiving unit is further configured to receive a second request sent by a third network element, the second request being for requesting to obtain user-related data.

[0067] The sending unit is specifically configured to send the first request to the second network element based on the second request.

[0068] In a possible implementation, the second request includes user information and a third scope of use, and the third scope of use includes at least one of the following information: a third object of use, a third purpose of use, and a third time of use. The device further includes a processing unit configured to obtain the first range of use based on the third range of use.

[0069] In a possible implementation, the second request includes a second type identifier, the second type identifier for identifying a type of user-related data requested by the third network element.

[0070] The processing unit is further configured to determine the first type identifier based on the second type identifier.

[0071] In a possible implementation, the processing unit is specifically configured to determine the second data type identifier as the first type identifier.

[0072] In a possible implementation, the processing unit is particularly configured to determine the first type identifier based on the configuration information and the second data type identifier, the configuration information indicating a correspondence between the first type identifier and the second data type identifier.

[0073] In a possible implementation, the third network element is an application server AF or a network function NF network element.

[0074] According to a sixth aspect, a receiving unit configured to receive a first request sent by a first network element, the first request being for requesting authorization information of user-related data, the first request including user information and a first use scope of the user-related data, the first use scope including at least one of the following information: a first use object, a first use purpose, and a first use time; a processing unit configured to determine authorization information based on the first request; A communication device is provided that includes: a transmitting unit further configured to transmit a first response to a first network element, the first response including authorization information, the authorization information indicating whether a user corresponding to the user information has authorized the user-related data to be used with respect to a first scope of use.

[0075] In a possible implementation, the processing unit is particularly configured to determine authorization information corresponding to the user information based on whether the first request matches stored authorization information of the network user.

[0076] In a possible implementation, the processing unit is specifically configured to initiate a third request to the terminal device corresponding to the user information based on the first request through the transceiver, the third request being for requesting authorization information corresponding to the user information from the terminal device through the transceiver and receiving a third response sent by the terminal device, the third response including the authorization information corresponding to the user information.

[0077] In a possible implementation, the processing unit is specifically configured to initiate a fourth request to the fourth network element based on the first request through the transceiver, the fourth request being for requesting authorization information corresponding to the user information from the fourth network element through the transceiver, and receiving a fourth response sent by the fourth network element, the fourth response including the authorization information corresponding to the user information.

[0078] In a possible implementation, the user-related data includes first data and / or second data related to a user, the first data including data corresponding to the user generated by at least one of a terminal device, an application server, or a network device, and the second data including data analysis results obtained by performing data analysis based on the first data.

[0079] In a possible implementation, the first request further includes a first type identifier, the first type identifier being for indicating a type of the user-related data; The first request is for requesting authorization information for user-related data, The first request includes being to request authorization information for user-related data corresponding to the first type identifier.

[0080] In a possible implementation, the first network element is a network data analysis function NWDAF network element and the communication device is an integrated data management UDM network element, a user data repository UDR network element, an authentication service function AUSF network element, or a terminal device.

[0081] In a possible implementation, if the first data is user-related data, the first use is a network data analysis function NWDAF network element.

[0082] In a possible implementation, when the first data is user-related data, the first purpose of use includes performing data analysis.

[0083] In a possible implementation, when the user-related data is the first data, the first scope of use further includes an analysis identifier, the analysis identifier for indicating to perform a data analysis on the first data to obtain a data analysis result corresponding to the analysis identifier.

[0084] In a possible implementation, the first request further includes a second scope of use corresponding to the data analysis result, and the second scope of use includes at least one of information of a second subject of use, a second purpose of use, and a second time of use.

[0085] In a possible implementation, if the user data is the second data, the first type identifier is an analysis identifier.

[0086] In a possible implementation, the first network element is a network publication function NEF network element and the communication device is an integrated data management UDM network element, a user data repository UDR network element, an authentication service function AUSF network element or a terminal device.

[0087] In a possible implementation, the first user is an application server AF.

[0088] In a possible implementation, the first network element is an access and mobility management function AMF network element, and the communication device is an integrated data management UDM network element, a user data repository UDR network element, an authentication service function AUSF network element, or a terminal device.

[0089] According to a seventh aspect, a communication device is provided, the communication device including a processor. The processor is coupled to a memory and may be configured to execute a method according to any one of the first to fourth aspects and any one of the possible implementations of the first to fourth aspects. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, the processor being coupled to the communication interface.

[0090] In an implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver or an input / output interface. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0091] In another implementation, the communication device is a network device. When the communication device is a network device, for example, any one or more of a first network element, a second network element, a third network element, and a fourth network element, the communication interface may be a transceiver or an input / output interface. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0092] In another implementation, the communication device is a chip or chip system. In the case where the communication device is a chip or chip system, the communication interface may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuitry on the chip or chip system, etc. The processor may alternatively be embodied as a processing circuit or logic circuit.

[0093] According to an eighth aspect, a system is provided. The system includes the aforementioned terminal device and the aforementioned network device. The network device in the embodiment of the present application is a network element on the network side. For example, the first network element, the second network element, the third network element, and the fourth network element may all be referred to as a network device. The network device in the embodiment of the present application may be any one or more of the first network element, the second network element, the third network element, or the fourth network element.

[0094] According to a ninth aspect, a computer program product is provided. The computer program product includes a computer program (sometimes called code or instructions). When the computer program is run, the computer is enabled to execute a method according to any possible implementation of the first aspect, or the computer is enabled to execute a method according to any implementation of the first to fourth aspects.

[0095] According to a tenth aspect, a computer readable storage medium is provided. The computer readable storage medium stores a computer program (sometimes called code or instructions). When the computer program is run on a computer, the computer is enabled to execute a method according to any possible implementation of the first aspect, or to execute a method according to any implementation of the first to fourth aspects. [Brief description of the drawings]

[0096] [Figure 1] FIG. 1 is a diagram of an architecture of a communication system according to an embodiment of the present application. [Diagram 2] 2 is a flowchart of a communication method according to an embodiment of the present application. [Diagram 3] 4 is a flowchart of another communication method according to an embodiment of the present application. [Figure 4] 4 is a flowchart of another communication method according to an embodiment of the present application. [Diagram 5] 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present application; [Figure 6] 1 is a schematic diagram of the structure of another communication device according to an embodiment of the present application; [Figure 7] 1 is a schematic diagram of the structure of another communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0097] In the description of this application, unless otherwise specified, " / " means "or." For example, A / B can mean A or B. The term "and / or" in this specification describes only the association relationship between associated objects, and indicates that there are three possible relationships. For example, "A and / or B" can represent three cases: "only A exists," "both A and B exist," and "only B exists." In the description of this application, unless otherwise specified, "at least one" means one or more, and "multiple" means two or more.

[0098] In addition, for the purpose of making it easier to clearly describe the technical solutions in the embodiments of the present application, words such as "first" and "second" are used in the embodiments of the present application to distinguish between the same items or similar items having essentially the same function or purpose. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity or execution order, and terms such as "first" and "second" do not indicate clear distinctions.

[0099] The technical solutions in the embodiments of the present application are applicable to a 4th Generation (4G) system, various systems evolved based on a 4G system, a 5th Generation (5G) system, and various systems evolved based on a 5G system. The 4G system may also be called an evolved packet system (EPS). In the 4G system, the core network (CN) may also be called an evolved packet core (EPC), and the access network may also be called a long term evolution (LTE). In the 5G system, the core network may also be called a 5G core (5GC), and the access network may also be called a new radio (NR). For ease of description, the present application is hereinafter described by using an example in which the present application is applied to a 5G system. When the present application is applied to a 4G system or another communication system, the network elements included in the present application are replaced with network elements having the same or similar functions in the corresponding communication system.

[0100] Figure 1 shows an example of a schematic diagram of the network architecture of a 5G system based on service interfaces. In this schematic diagram, the 5G system may include an authentication server function (AUSF) network element, an access and mobility management function (AMF) network element, a data network (DN), a unified data management (UDM) network element, a user data repository (UDR) network element, a policy control function (PCF) network element, a (radio) access network ((R)AN) network element, a user plane function (UPF) network element, a terminal, an application function (AF) network element, a session management function (SMF) network element, a binding support function (BSF) network element, a network data analytics function (NWDAF) network element, a network exposure function (NEF) network element, and a network repository function (NRF) network element.

[0101] For ease of description, hereinafter, an (R)AN network element, an AMF network element, an SMF network element, a UDM network element, a UDR network element, an AUSF network element, a UPF network element, a PCF network element, a BSF network element, an NWDAF network element, an NRF network element, an NEF network element, etc. will be represented by using RAN, AMF, SMF, UDM, UDR, AUSF, UPF, PCF, BSF, NWDAF, NRF, NEF, etc., respectively.

[0102] The 5G system is divided into an access network and a core network. The access network performs functions related to radio access and mainly includes RAN. The core network is for network service control, data transmission, etc. The core network includes multiple network elements, mainly including AMF, SMF, UPF, PCF, UDM, etc.

[0103] The functions of some network elements in FIG.

[0104] The PCF is configured to provide policies such as quality of service (QoS) policies and slice selection policies for the AMF and SMF.

[0105] The UDM is configured to handle 3rd generation partnership project (3GPP) authentication and key agreement (AKA), authentication credentials, user identification processing, access authorization, registration / mobility management, subscription management, short message service management, etc. In this application, the UDM may provide a function to store information about a network element (serving NF, such as a serving AMF, serving SMF, or serving NWDAF) currently serving the terminal.

[0106] As a logical repository for storing user data, the UDR is configured to facilitate sharing and distribution of user-related data.

[0107] The AUSF is configured to provide user authentication and authorization services for the network.

[0108] The AF may be an application server and may belong to an operator or a third party. The AF mainly supports interacting with the 3GPP core network to provide services, such as services that affect data routing decisions, policy control functions, or some third-party services provided for the network side.

[0109] The NEF is configured to provide customized functionality for network publishing, and further support authentication and authorization functions for third-party AFs.

[0110] The AMF is mainly responsible for functions such as signaling processing, e.g., terminal registration management, terminal connection management, terminal reachability management, terminal access authentication and authorization, terminal security functions, terminal mobility management (such as terminal location update, terminal registration to the network, and terminal handover), network slice selection, SMF selection, and terminal registration or deregistration.

[0111] The SMF is primarily responsible for all control plane functions of terminal session management, including UPF selection, control, and redirection, internet protocol (IP) address allocation and management, session QoS management, policy and charging control (PCC) policies obtained from the PCF, and bearer or session establishment, modification, and release.

[0112] As the anchor of the session connection of protocol data units (PDUs), the UPF is responsible for terminal data packet filtering, data transmission / forwarding, rate control, charging information generation, user plane QoS processing, uplink transmission authentication, transmission level verification, downlink data packet buffering, downlink data notification triggering, etc. The UPF can also act as a branching point for multi-homed PDU sessions. Resource transmission and scheduling functions for providing services for terminals in the UPF are managed and controlled by the SMF.

[0113] The NRF is a network element that stores information such as network element attributes, network element status, and network topology relationships. The NRF has network element discovery and management functions.

[0114] The BSF may bind or store the corresponding terminal address, terminal identifier, data network name (DNN), single network slice selection assistance information (S-NSSAI), PCF instance, and PCF set identifier for the PDU session. For example, the PCF corresponding to the terminal may be queried from the BSF.

[0115] The NWDAF has at least one of the following functions: data collection function and data analysis function. The data collection function is for collecting relevant data from a network element, a third-party service server, a terminal, or a network management system. The data analysis function is for performing analysis and training based on the relevant input data to provide data analysis results for the network element, the third-party service server, the terminal, or the network management system. The analysis result assists the network to select quality of service parameters of the service, or assists the network to perform traffic routing, or assists the network to select background traffic transmission policies. This application mainly includes the data collection function of the NWDAF. Since the NWDAF can only perform related training and analysis functions based on the collected data, the premise is that it is capable of collecting and obtaining related data. In possible implementations, the NWDAF network element may be integrated with another NF, or the NWDAF may be deployed independently. In addition, multiple NWDAFs may be deployed in a network.

[0116] The RAN is a network including one or more access network devices (sometimes called RAN nodes or network devices), which perform functions such as radio physical layer functions, resource scheduling and radio resource management, radio access control and mobility management functions, quality of service management, and data compression and encryption. The access network devices are connected to the UPF through a user plane interface N3 and are configured to transmit terminal data. The access network devices establish a control plane signaling connection to the AMF through a control plane interface N2 to perform functions such as radio access bearer control.

[0117] The access network devices may be base stations, wireless fidelity (Wi-Fi) access points (APs), worldwide interoperability for microwave access (WiMAX) sites, etc. There may be various forms of base stations, e.g., macro base stations, micro base stations (also called small cells), relay stations, and access points. Specifically, the base station may be an AP in a wireless local area network (WLAN), a base transceiver station (BTS) in a global system for mobile communications (GSM) or code division multiple access (CDMA), or a NodeB (NodeB, NB) in wideband code division multiple access (WCDMA), or an evolved NodeB (eNB or eNodeB), or a relay station or access point in LTE, an in-vehicle device, a wearable device, or the next generation NodeB (gNB) in a future 5G system, or a base station in a future evolved public land mobile network (PLMN) network, etc.

[0118] A terminal may be a wireless terminal or a wired terminal. A wireless terminal may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or another processing device connected to a wireless modem. The terminal and the access network device communicate with each other by using an air interface technology (e.g., NR technology or LTE technology). The terminals may also communicate with each other by using an air interface technology (e.g., NR technology or LTE technology). A wireless terminal may communicate with one or more core network devices, such as an AMF, an SMF, etc., through an access network device. A wireless terminal may be a mobile terminal, such as a mobile phone (or called a "cellular" phone), a smartphone, a satellite wireless device, a wireless modem card, or a computer with a mobile terminal. For example, a computer with a mobile terminal may be a laptop, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device that transmits and receives voice and / or data to and from an access network device. For example, a wireless terminal may be a personal communication service (PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), virtual reality (VR) glasses, augmented reality (AR) glasses, a machine-type communication terminal, or an Internet of Things terminal. In Internet of Vehicles communications, a communication device onboard a vehicle is a type of terminal, and a road side unit (RSU) may also be used as a type of terminal. A communication device onboard an unmanned aerial vehicle may also be considered as a type of terminal.A wireless terminal may also be called user equipment (UE), terminal device, subscriber unit, subscriber station, mobile station, mobile platform, remote station, access point, access terminal, user terminal, user agent, etc.

[0119] The DN refers to an operator network, such as an Internet Protocol multimedia service (IMS) or the Internet, that provides data transmission services for users. The terminal accesses the DN by establishing a PDU session between the terminal, the access network device, the UPF, and the DN.

[0120] It can be understood that the network architecture of a 5G network may further include other functional network elements in addition to the functional network elements shown in Figure 1. In the embodiments of the present application, the network elements may also be referred to as entities, devices, etc.

[0121] It should be noted that the RAN, AMF, SMF, AUSF, UDM, UPF, PCF, BSF, NWDAF, NRF, NEF, etc. in FIG. 1 are just names, and the names do not constitute any limitation on the network elements. In the 5G system and other future networks, the entities or devices corresponding to these network elements may have other names. This is not particularly limited in the embodiments of the present application. For example, the UDM may be replaced by a home subscriber server (HSS), a user subscription database (USD), a database network element, etc., as an alternative. An overview is provided here, and the details will not be repeated again hereafter.

[0122] In the network architecture of the aforementioned 5G system, since 3GPP Release 15 (Release 15, R15), an NWDAF network element has been introduced to obtain relevant data of domains such as terminals, networks (e.g., RAN, CN, transmission network (TN), etc.), AFs, and operation, administration, and maintenance (OAM), and to perform training analysis based on a large amount of obtained data through machine learning methods to generate analysis results. The analysis results may assist in formulating and executing network policies. For example, the NWDAF generates service experience analysis results based on data obtained from the network and data obtained from the AF. The service experience analysis results may help the PCF formulate PCC and QoS policies related to terminal services.

[0123] Multiple NWDAFs may be deployed in a communication network at the same time. From one dimension, different NWDAFs are responsible for analysis work for different purposes. For example, some NWDAFs are responsible for analyzing the movement trajectory of the terminal, some NWDAFs are responsible for analyzing the service experience, and some NWDAFs are responsible for analyzing the abnormal behavior of the terminal. From another dimension, different NWDAFs are responsible for different service areas. For example, some NWDAFs are responsible for data analysis in area 1, and another NWDAF is responsible for data analysis in area 2.

[0124] It may be understood that a network element or function may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). One or more services may be obtained through the division into network elements or functions. Furthermore, services that exist independently of a network function may arise. In this application, an instance of a function, an instance of a service included in a function, or an instance of a service that exists independently of a network function may be referred to as a service instance.

[0125] It should be noted that the embodiments of the present application are not limited to the above-mentioned system architecture, but may alternatively be applied to another future communication system, such as the 6th generation (6G) system architecture. In addition, in the embodiments of the present application, in the future communication system, the names of the above-mentioned used network elements may change, while the functions of those network elements may remain the same.

[0126] The user in the embodiment of the present application may be a person or object that uses a terminal device to perform communication services in a network. In addition, the user may alternatively be a terminal device, for example, a terminal device in the Internet of Things. The user information in the embodiment of the present application is for identifying a user, and the form of the user information is not limited here, as long as the user information can play a role in identifying and distinguishing users. The user information may be an International Mobile Subscriber Identification Number (IMSI), a subscription permanent identifier (SUPI), a generic public subscription identifier (GPSI), a user Internet Protocol (IP) filter / 5-tuple (UE IP filter / 5-tuple), a mobile station international ISDN number (MSISDN), an International Mobile Equipment Identification Number (IMEI), etc. The user information may further be an identifier of the area where the user is located, an identifier of the user, an identifier of a user group to which the user belongs, an identifier of a network slice corresponding to the user, a data network name (DNN) of the user, and an identifier of a network element to which the user belongs.

[0127] The user-related data is user-level data protected by the GDPR. In an embodiment of the present application, the user-related data may include one or more of the first data or the second data described below, where the first data includes raw data and / or processed data, and the raw data includes data generated for a user by a terminal device, an application server, or a network device. The data may be data reported to an operator network.

[0128] The data generated by the terminal device for the user may include one or more of data generated by the user on the terminal device, data of the terminal device, and data generated by the terminal device for the user. The data generated by the user on the terminal device may be, for example, Global Positioning System (GPS) information of the terminal device, input habits of the user on the terminal device, etc. The data of the terminal device used by the user may be, for example, the type approval code (TAC), memory capacity, and CPU model of the terminal device. The data generated by the terminal device for the user may be, for example, a port number assigned to the user by the terminal device, or a storage space assigned to the user.

[0129] The data generated by the application server for the user may be described as application layer data corresponding to the user. In an embodiment of the present application, the application layer data corresponding to the user includes one or more types of data: data generated in the application server by the user, data of the application server corresponding to the user, and data generated by the application server for the user. The data generated in the application server by the user may be, for example, the type of service used by the user, or information of the IP5 tuple corresponding to the user's service. The data of the application server corresponding to the user may be the type of service that can be provided by the application server, the IP address and port number corresponding to each type of service, the basic function of each service, the storage space of the application server, etc. The data generated by the application server for the user may be, for example, information on the application layer identifier assigned to the user by the service server, the service requirements assigned to the user's service, or the quality information of the user's service.

[0130] The data generated by the network device for the user may include one or more types of data: data generated on the access network and / or core network by the user, data of the access network and / or core network corresponding to the user, and data generated by the access network and / or core network for the user. The data generated on the access network and / or core network by the user may be, for example, the user's location information (e.g., a cell identifier or a TA identifier), or information on the network slice the user requests to access. The data of the access network and / or core network corresponding to the user may be, for example, the capacity of a cell in the access network, the load information of the AMF, or the bandwidth information of the UPF. The data generated by the access network and / or core network for the user may be, for example, the bandwidth allocated to the user's service by the access network, information on the slice selected for the user by the core network AMF, or information on the QoS policy customized for the user's service by the PCF. Specifically, in an embodiment of the present application, the network data of the user includes data on the access network corresponding to the user. Alternatively, in an embodiment of the present application, the network data of the user includes data on the core network corresponding to the user. Alternatively, in an embodiment of the present application, the network data of the user includes data on an access network corresponding to the user and data on a core network corresponding to the user. The access network may also be described as an access network of a telecommunications operator, and the core network may also be described as a core network of a telecommunications operator.

[0131] Processed data is data generated after corresponding processing such as aggregation (weighting data from multiple UEs or averaging data from a single UE over a period of time) or anonymization (removing UE identifying information) is performed on the raw data.

[0132] Specifically, to distinguish between different data in the first data, a data type or an event identifier may be used to distinguish between different data in the first data. The data type or event ID is used as an example. For example, data type=reference signal received power (RSRP) at the location of the cell where the UE is located. In another example, event ID=the location of the UE.

[0133] The second data is a data analysis result obtained by performing data analysis based on the first data, such as a UE mobility information analysis result, a UE abnormal behavior analysis result, or a UE service behavior analysis result generated by the NWDAF. Specifically, in order to distinguish between different data analysis results, an analysis identifier, an analysis ID, may be used for identification.

[0134] As a request for authorization information, the first network element in this embodiment may only request to obtain authorization information, or the first network element may also play the role of a data requester to request to obtain user-related data when requesting authorization information. The first network element may be an NWDAF network element, or may be another network element that needs to obtain user-related data, for example, an NEF network element, an AMF network element, or an AF network element. When requesting authorization information for user-related data, the first network element may include a usage scope in the request sent. The usage scope may include information such as a usage object, a usage purpose, and a usage time. The usage object is for indicating an object for which the obtained user-related data will be used. The object has multiple representation forms, for example, a public land mobile network (PLMN) identifier, a network domain (a core network domain, a RAN domain, and an OAM domain), an NF network element type (an AMF type and an SMF type), an NF network element instance identifier, an AF type, an AF instance identifier, or an application identifier. For example, if the target is a core network domain, it indicates that the target of use is a network element of the entire core network.

[0135] The purpose of use is to indicate the purpose of using the user-related data, i.e., what the user-related data is used for. The purpose of use may be defined separately based on the specific data in the acquired user-related data. For example, if the requested data is the first data, the purpose of use may be to obtain a data analysis result, or to open to a third-party AF for use, or it may be further defined which data analysis result will be specifically obtained, for example, a user's movement trajectory analysis result is obtained. If the requested data is the second data, the purpose of use may be to open to a third-party AF for use, or to further limit the specific use of opening to a third-party AF, for example, to perform infection monitoring, service application layer parameter adjustment, or paging area optimization.

[0136] The time of use is intended to indicate when the subject of use uses the user-related data, and may include a period and / or duration. For example, after obtaining the user-related data, the subject of use uses the user-related data during the period from January 1, 2020 to December 31, 2020, or after obtaining the user-related data, the subject of use uses the user-related data for six months after the time of obtaining.

[0137] In an embodiment of the present application, the second network element is configured to obtain, store and process the authorization information of the user-related data. The second network element may be a data management UDM network element, a data repository UDR network element, an authentication server function AUSF network element, a network publishing function NEF network element, a terminal device, etc. In future communication systems, the second network element may still be a UDM network element, a UDR network element, or have other names. This is not limited in the present application.

[0138] In an embodiment of the present application, the second network element may obtain the authorization information of the user-related data through the following method.

[0139] In one method, the second network element obtains the authorization information of the user-related data in a dynamic acquisition manner, the method specifically includes: in an initial network registration or mobility registration process, the terminal device triggers the user's authorization information to be reported to a network element (such as AMF) on the network side, and the network element then stores the user's authorization information in the second network element (such as UDM). Alternatively, when initiating a PDU session establishment or modification procedure, the terminal device triggers the user's authorization information to be reported to a network element (such as SMF) on the network side, and the network element then stores the authorization information in the second network element (such as UDM). Alternatively, the second network element queries the user's terminal device for the user's authorization information due to a trigger condition (another network element queries the second network element), and the terminal device sends the authorization information to the second network element, whereby the second network element stores the user's authorization information.

[0140] In another method, the second network element obtains the authorization information in a static configuration manner. Specifically, in a subscription stage before the user accesses the network, the terminal device stores the authorization information as subscription information in the second network element. When the user's authorization information changes, the subscription information in the second network element is updated to update the authorization information.

[0141] The authorization information may include user information (identifying a user), data type (such as first data and second data), use scope (subject to use, purpose to use, and time to use), and authorization status information (yes, no, unknown, etc.). When the authorization information transmitted by the terminal devices of multiple users is received, the second network element stores, for each user, the authorization information corresponding to the user. Which data is permitted to be used, which subject is permitted to use the data, the purpose for which the data is permitted to be used, when the data is permitted to be used, etc. can be known from the contents included in the authorization information. Specifically, after obtaining the user's authorization information, the second network element may store the user's authorization information as the user's subscription information and store the correspondence between the subscription information and the user identifier, or may store the user's authorization information as the user's context information and store the correspondence between the context information and the user identifier.

[0142] The approval information of the user-related data in this embodiment is for indicating whether the user corresponding to the user information permits the user-related data to be used in the requested scope of use. Specifically, there may be multiple options. For example, the approval information may be any one of "yes", "no", or "unknown". If the approval information is "yes", it indicates that the user-related data is permitted to be used. If the approval information is "no", it indicates that the user-related data is not permitted to be used. If the approval information is "unknown", it indicates that the user's attitude towards whether the user-related data is permitted to be used is unclear, that is, it is uncertain at the moment whether the user permits the user-related data to be used. In this case, it can be understood that the user does not approve, i.e., does not permit, the user-related data to be used. In relation to the above cases of user-related data, the authorization information in the embodiment of the present application may indicate any one or more of whether the first data is permitted to be used, whether the second data is permitted to be used, whether one or some data in the first data is permitted to be used, whether one or some data in the second data is permitted to be used, etc. For example, the authorization information indicates that the first data is permitted to be used. In another example, the authorization information indicates that the first data is permitted to be used but the second data is not permitted to be used. In another example, the authorization information indicates that the data a1 in the first data is permitted to be used but the data a2 in the first data is not permitted to be used. In another example, the authorization information indicates that the first data is not permitted to be used, the data b1 in the second data is permitted to be used, and the data b2 in the second data is not permitted to be used.

[0143] For example, Table 1 shows an example of the display form of the approval information of the user-related data, and the first and third rows in Table 1 are used as examples for description. As shown in the first row, the user-related data requested by the data requester is data corresponding to the event ID1 in the first data, the user identifier is ID1, the corresponding use scope includes a network element whose use object is an NWDAF type, the use purpose is to perform an analysis of the analysis ID1, the use time is the network registration period of the UE, and the approval information is "yes". In this case, the first row indicates that the user of ID1 permits the data corresponding to the event ID1 to be used in the network element whose use object is an NWDAF type, the use purpose is to perform a data analysis corresponding to the analysis ID1, and the use time is the use scope corresponding to the network registration period of the UE. As shown in the third line, the user-related data is data corresponding to analysis ID1 in the second data, the user identifier is ID1, the use object is an AF instance ID, the use purpose is infection monitoring, the use period is from January 1, 2020 to December 30, 2020, and the approval information is "No." In this case, the third line indicates that the user of ID1 has not permitted data corresponding to analysis ID1 to be used in the use range corresponding to the case where the use object is an AF instance ID, the use purpose is infection monitoring, and the use period is from January 1, 2020 to December 30, 2020.

[0144] [Table 1]

[0145] With respect to the first data, the authorization information may further indicate any one or more of whether the terminal device data corresponding to the user is permitted to be used, whether the network data of the user is permitted to be used, and whether the application server data corresponding to the user is permitted to be used. For example, the authorization information indicates that the terminal device data corresponding to the user is permitted to be used. In another example, the authorization information indicates that the terminal device data corresponding to the user is permitted to be used, but the network data of the user is not permitted to be used. In another example, the authorization information indicates that the terminal device data corresponding to the user is permitted to be used, and the network data of the user is permitted to be used, but the application server data corresponding to the user is not permitted to be used.

[0146] In this embodiment, the authorization information may further include other limiting information, which limits the user-related data. The other limiting information includes any one or more of time information, location information, service type, data network name (DNN) information, application identifier, and network slice information. The network slice information may be network slice identifier information, such as Network Slice Selection Assistance Information (NSSAI), single-Network Slice Selection Assistance Information (S-NSSAI), network slice instance (NSI) identifier, or network slice subnet instance (NSSI) identifier. For example, when the limiting information is a preset period and a preset location range, the authorization information indicates whether the user-related data generated within the preset period and the preset location range is allowed to be used. It should be noted that the time information identifier, location information, service type, DNN information, etc. in this embodiment all indicate information such as the corresponding time, area, service, and DNN when the user-related data is generated.

[0147] In this embodiment, when the authorization information of user-related data is divided based on limited information such as location information, time information, service type, application identifier, DNN, and network slice information, according to the above implementation, the user may report authorization information corresponding to all areas, all times, all service types, all application identifiers, all DNNs, and all slices of the user at once. Alternatively, the user may report authorization information corresponding to different areas, different times, different service types, different DNNs, and different slices at different times.

[0148] Based on the foregoing, in order to facilitate understanding of specific implementations of the embodiments of the present application, the following provides a description with reference to the accompanying drawings.

[0149] 2 is a flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 2, the method may include the following steps:

[0150] S201: A first network element sends a first request to a second network element.

[0151] In this embodiment, in order to obtain the approval information of the user-related data, 1 The network element may send a first request to a second network element, the first request being for requesting authorization information for user-related data, the first request may include user information and a first usage scope of the data corresponding to the user information.

[0152] The first scope of use may include one or more of a first object of use, a first purpose of use, and a first time of use. The first object of use is an object for using the user-related data, the first purpose of use is a specific purpose for using the user-related data, and the first time of use is a time for using the user-related data. The first time of use may include a duration of use and / or a specific period of use.

[0153] The second network element may be a network element such as a UDM, a UDR, an AUSF, or a NEF, or a terminal device. For ease of understanding, an example in which the second network element is a UDM is used for description. Authorization information of user-related data may be stored in user subscription information stored in the UDM. For example, when a user performs subscription, the authorization information of the user may be set, and the authorization information is stored in the UDM as part of the subscription information. The first network element calls the Nudm SDM Get service provided by the UDM through a service-based interface to obtain the subscription information of the user.

[0154] Specifically, the first network element may obtain authorization information of only one user at a time from the UDM. In this case, the first network element provides an identifier of only one user for the UDM. Correspondingly, the UDM feeds back authorization information of only one user at a time to the first network element. In another implementation, the first network element may also obtain authorization information of multiple users at a time from the UDM. In this case, the first network element provides information that may indicate identifiers of multiple users for the UDM. The identifiers of the users may be identifiers of a user group, identifiers of an area where the multiple users are located, identifiers of a network element, identifiers of a network slice, DNN, etc. Correspondingly, the UDM feeds back authorization information of multiple users at a time to the first network element.

[0155] In some implementations, the first request may further include a first type identifier, where the first type identifier is for identifying a type of the user-related data. In this case, the first request is for requesting approval information of the user-related data corresponding to the first type identifier. Specifically, the first type identifier is for identifying the first data and the second data in the user-related data. If the user-related data is the first data, the first type identifier may be an event identifier, where the first data is data related to an event corresponding to the event identifier. If the user-related data is the second data, the first type identifier may be an analysis identifier, where the second data is a data analysis result corresponding to the analysis identifier.

[0156] In some implementations, the first request may further include a filter criterion, and the first request is for requesting to obtain authorization information of a user that satisfies the filter criterion. The filter criterion may include any one or more of time information, location information, service type, data network name DNN information, and network slice information. In this embodiment, the time information indicates a time at which the user-related data is generated, the location information indicates a location at which the user-related data is generated, the service type indicates a service that generates the user-related data, the data network name DNN information indicates information about the DNN that generates the user-related data, and the network slice information indicates information about the slice that generates the user-related data.

[0157] The trigger condition for the first network element to send a first request to the second network element to request the authorization information of the user may be a requirement of the first network element to actively send the first request to the second network element, or to send the first request to the second network element according to the second request after the first network element receives a second request sent by a third network element (such as an AF or an NF). The second request is for requesting to obtain user-related data. That is, the trigger condition for the first network element to send the first request to the second network element is to receive the second request sent by the third network element. In this case, the first network element generates the first request based on the second request and sends the first request to the second network element.

[0158] The second request may include user information and a second type identifier, the second type identifier is for identifying a type of user-related data requested by the third network element, and the second type identifier may identify the first data and / or the second data in the user-related data. The second request may further include a third use scope, and the third use scope may include one or more of information such as a third use object, a third use purpose, and a third use time. After receiving the second request sent by the third network element, the first network element generates a first request based on the information included in the second request. Specifically, the first network element obtains a first use scope based on the third use scope. The first network element determines the first type identifier based on the second type identifier. The first network element obtaining the first use scope based on the third use scope may include the first network element directly determining the third use scope as the first use scope, or the first network element obtaining the first use scope based on the third use scope and the setting information. The configuration information indicates a mapping relationship between the third use range and the first use range. In addition, the first network element determining the first type identifier based on the second type identifier may include the first network element directly determining the second type identifier as the first type identifier, or the first network element obtaining the first type identifier based on the second type identifier and the configuration information. The configuration information identifies a mapping relationship between the first type identifier and the second type identifier. For example, if the user-related data requested by the third network element is data corresponding to an event identifier in the first data, the second type identifier is an event ID. If the first network element intends to request an authorization information event corresponding to the event ID from the second network element, the first network element may determine the event ID as the first type identifier.In another example, if the user-related data requested by the third network element is a data analysis result in the second data, the second type identifier is an analytics ID. If the first network element intends to request the second network element for authorization information corresponding to the analytics ID, the second network element determines the analytics ID as the first type identifier. In another example, if the user-related data requested by the third network element is a data analysis result in the second data, the second type identifier is an analytics ID. In this case, the first network element needs to determine an event identifier of the first data corresponding to the analytics identifier based on the analytics identifier and the configuration information, and the first type identifier is an event identifier. The event identifier may be represented by an event ID or a data type. S203: The second network element sends a first response to the first network element.

[0159] In this embodiment, when receiving the first request sent by the first network element, the second network element may obtain authorization information of the corresponding user-related data based on the first request, and send the authorization information to the first network element through a first response, so that the first network element obtains the authorization information of the user. The authorization information indicates whether the user corresponding to the user information permits the user-related data to be used for the first use scope. For example, the authorization information indicates whether the user corresponding to the user information permits the user-related data to be used by the first use object, whether the user-related data is permitted to be used for the first use purpose, whether the user-related data is permitted to be used at the first use time, etc.

[0160] The second network element may send the first response directly to the first network element, or may send the first response to the first network element through another intermediate network element.

[0161] Before sending the first response, the second network element may further perform step S202.

[0162] S202: The second network element determines authorization information of the user based on the first request.

[0163] The second network element may determine the user's authorization information based on the first request in a number of ways as described below.

[0164] According to a method, the second network element determines authorization information corresponding to the user information based on whether the first request matches the stored authorization information of the network user. In this implementation, the second network element may pre-store authorization information of the user in the network. When receiving the first request sent by the first network element, the second network element may perform a match based on the user information in the first request and the pre-stored authorization information of the user in the network. If the authorization information of the user corresponding to the user information exists in the pre-stored authorization information of the user in the network, the second network element determines the authorization information of the user. Specifically, the second network element performs a one-to-one match based on each item of contents included in the first usage scope in the first request, and determines the authorization information based on the matching result of each item. For example, when the first usage scope includes only the first usage object, the first usage object is matched with the usage object in the authorization information of the network user. If the two match, the authorization information is determined to be that the user-related data is permitted to be used in relation to the first scope of use, or if the two do not match, the authorization information is determined to be that the user-related data is not permitted to be used in relation to the first scope of use. In another example, if the first scope of use includes a first use object and a first use time, the first use object is matched with the use object in the authorization information of the network user to obtain a first result, and the first use time is matched with the use time in the authorization information of the network user to obtain a second result. If both the first result and the second result match, the authorization information is determined to be that the user-related data is permitted to be used in relation to the first scope of use, or if the first result or the second result do not match, the authorization information is determined to be that the user-related data is not permitted to be used in relation to the first scope of use.

[0165] According to another method, after receiving a first request sent by a first network element, the second network element determines a terminal device corresponding to the user information through the user information in the first request. The second network element sends a third request to the terminal device based on the first request, the third request is for requesting authorization information corresponding to the user information from the terminal device. After receiving the third request, the terminal device sends a third response to the second network element, the third response including the authorization information corresponding to the user information.

[0166] According to yet another method, after receiving the first request sent by the first network element, the second network element sends a fourth request to the fourth network element based on the first request, where the fourth request is for requesting authorization information corresponding to the user information. After receiving the fourth request, the fourth network element determines authorization information corresponding to the user information based on the fourth request, and sends a fourth response to the second network element. The fourth response includes authorization information corresponding to the user information. In this implementation, the fourth network element may pre-store the authorization information of the user. The relevant content in this part is similar to the content above, and the details will not be repeated here again. The fourth network element may be an AF, a UE, etc. The second network element may directly send the fourth request to the fourth network element, or may send the fourth request to the fourth network element through another network element. For example, if the fourth network element is an AF network element, the second network element sends the fourth request to the fourth network element through the NEF network element.

[0167] After step S203, the method may further include the following steps:

[0168] S204: If the authorization information indicates that the user corresponding to the user information permits the user-related data to be used for the first scope of use, the first network element acquires the user-related data.

[0169] In this embodiment, if the authorization information in the first response received by the first network element from the second network element indicates that the user-related data of the user corresponding to the user information is permitted to be used with respect to the first scope of use, the first network element may obtain the user-related data.

[0170] In some implementations, if a trigger condition of a first request sent by the first network element to the second network element is that the third network element sends a second request to the first network element, and if the authorization information indicates that user-related data corresponding to the user information is authorized to be used for the first scope of use, the first network element may send a second response to the third network element, the second response including the user-related data, whereby the third network element obtains the user-related data.

[0171] Specifically, if the user-related data requested by the third network element is the first data, the first network element may transmit the user-related data to the third network element when it obtains the user-related data. If the user-related data requested by the third network element is the second data, in an implementation, if the first network element obtains the second data from another network element having a data analysis function, the first network element transmits the second data to the third network element; in another implementation, if the first network element already has a data analysis function, the first network element may also first obtain the first data corresponding to the second data, perform data analysis on the first data to obtain the corresponding second data, and then transmit the second data to the third network element. In this implementation, the third network element may be an application server AF, a network function NF network element, a network management system network element, a terminal device, etc.

[0172] In some implementations, if the authorization information indicates that the user corresponding to the user information does not authorize the user-related data to be used for the first use range, the first response may further include reason information to indicate why the user-related data is not authorized to be used. The reason information indicates the reason why one or some data is not authorized to be used, for example, a data type is not within the authorization range of the UE, a use object is not within the authorization range of the UE, a use purpose is invalid, or a use time is not within the authorization range of the UE.

[0173] It can be known from the above steps that before acquiring user-related data, the first network element acquires user authorization information in advance, and the first network element acquires the user-related data only if the user-related data is authorized to be used, thereby prohibiting the user-related data from being acquired at will and protecting the user-related data.

[0174] In some implementations, the first network element may acquire the user-associated data through the following implementations: In the implementations, if the user-associated data is the first data, the first request may include an event identifier (e.g., an event ID) to identify a specific category of data that the first network element intends to acquire through the data identifier. The first network element sends a fifth request to a fifth network element, where the fifth request includes the event identifier. The first network element receives a fifth response sent by the fifth network element, where the fifth response includes the first data corresponding to the event identifier. That is, the first network element acquires the user-associated data by sending the fifth request to the fifth network element. The fifth network element is a network element where the user-associated data that the first network element intends to acquire is located. For example, the fifth network element may be an NF, an AF, a UE, an OAM, etc.

[0175] In another implementation, if the user-related data is the second data, the first request may include an analysis identifier (e.g., an analysis ID), and the analysis identifier is for identifying a category of a specific data analysis result that the first network element intends to obtain. Since the second data is data obtained by performing data analysis based on the first data, before obtaining the second data, the first network element may first obtain first data corresponding to the second data. Specifically, the first network element determines an event identifier (e.g., an event ID) corresponding to the first data based on the analysis identifier corresponding to the second data. The first network element obtains the first data based on the event identifier, and the first network element generates the user-related data based on the first data. In this implementation, the first network element may obtain the first data through the following method. The first network element may obtain the first data pre-stored in the first network element, for example, or may obtain the first data from another network element, such as an NF, an AF, a UE, or an OAM.

[0176] In some implementations, if the authorization information of the user-related data acquired by the first network element is authorization information corresponding to the first data, the first purpose of use in the first use scope may be to perform data analysis, i.e., the first data is for performing data analysis. Further, the first use scope may further include an event identifier, and the first data is data related to an event corresponding to the event identifier. Further, if the first purpose of use is to perform data analysis, the first use scope may further include an analysis identifier, and the analysis identifier is for indicating to perform data analysis on the first data to obtain a data analysis result corresponding to the analysis identifier. For example, if the event identifier, event ID, = user location data, and the analysis identifier, analysis ID, = user mobility analysis, it is indicated to perform data analysis on the user location data to obtain a user mobility analysis result.

[0177] Further, the first request may further include a second use range, and the second use range includes at least one of information such as a second use target, a second use purpose, and a second use time. The second use target is for indicating a target for which the data analysis result will be used, the second use purpose is for indicating a purpose for which the data analysis result will be used, and the second use time is for indicating a time when the data analysis result will be used. For example, if the data analysis result is a user mobility analysis result, the second use target is for indicating a target for which the user mobility analysis result will be used, such as an AF or AMF network element. The second use purpose is for indicating a purpose for which the user mobility analysis result will be used, such as infection monitoring or paging area optimization. The second use time is for indicating a time when the user mobility analysis result will be used, such as from January 1, 2020 to December 30, 2020.

[0178] In some implementations, when the first network element is a network data analysis function (NWDAF) network element, the second network element is a unified data management (UDM) network element. , Yu It may be a User Data Repository (UDR) network element, an Authentication Service Function (AUSF) network element, or a terminal device.

[0179] In some implementations, if the first network element is a network publishing function NEF network element, the second network element is a unified data management UDM network element. , Yu The Authentication Service Function may be a User Data Repository (UDR) network element, an Authentication Service Function (AUSF) network element, or a terminal device.

[0180] In some implementations, when the first network element is an access and mobility management function (AMF) network element, the second network element is an integrated data management (UDM) network element. , Yu The Authentication Service Function may be a User Data Repository (UDR) network element, an Authentication Service Function (AUSF) network element, or a terminal device.

[0181] In some implementations, when the first network element is an application function AF network element, the second network element is a network publication function NEF network element.

[0182] It should be noted that regardless of which network elements the first network element and the second network element are specifically, the authorization information of the user-related data can be obtained according to the embodiment shown in FIG.

[0183] It should be noted that not every step in the method embodiment provided in Figure 2 is required. Some steps in the method embodiment provided in Figure 2, such as S202 and S204 in Figure 2, are optional.

[0184] To facilitate understanding of the above procedure, in the example used hereinafter, a third-party AF (third network element) requests the user's data analysis results from the NWDAF (first network element), and the NWDAF queries the UDM for authorization information for description.

[0185] Figure 3 is a flowchart of another communication method according to an embodiment of the present application. For the contents in this embodiment of the present application that are the same as those in the embodiment of Figure 2, reference may be made specifically to the description of the embodiment in Figure 2. As shown in Figure 3, the method may include the following steps:

[0186] S301: A third network element sends a second request to the first network element, where the second request is for requesting to obtain user-related data.

[0187] In this embodiment, when intending to obtain the second data, the third network element may send a second request to the first network element. The second type identifier in the second request may be a specific analysis identifier (analysis ID), through which the specific data analysis result requested by the third network element is to be identified. The data analysis result needs to be obtained by performing data analysis by the first network element based on the corresponding first data. The second request may include an identifier of the third network element or an application identifier (application ID), through which the second data is used to describe. The second request may further include user information, which indicates the user having the second data requested by the third network element. For a specific display form of the user information, reference may be made to the above-mentioned embodiment, and the details will not be repeated here again in this embodiment.

[0188] The second request may further include a third scope of use, where the third scope of use includes one of information such as a third target of use, a third purpose of use, a third time of use, etc. The third target of use identifies a target of use of the data analysis result, the third purpose of use identifies a specific purpose of use of the data analysis result, and the third time of use identifies a specific time when the data analysis result is used.

[0189] S302: The first network element sends a first request to the second network element based on the second request, where the first request is for requesting authorization information of the user-related data.

[0190] In this embodiment, after determining the second request sent by the third network element, the first network element may generate a first request based on the received second request, and send the first request to the second network element to obtain the authorization information of the user-related data. That is, the first network element uses the second request sent by the third network element as a trigger condition to query the second network element for the user authorization information. The first network element may generate the first request based on the second request. For specific implementation, refer to the description in the preceding embodiment. The details will not be repeated again in this embodiment. For example, if the user information in the second request is the user's external identifier, the first network element may convert the user's network external identifier into the user's network internal identifier based on the configuration information, and include the user's network internal identifier in the first request.

[0191] S303: The second network element determines authorization information of the user based on the first request.

[0192] In this embodiment, the second network element may obtain user authorization information corresponding to the user information based on the user authorization information stored by the second network element and the first request.

[0193] Specifically, the second network element determines, based on the first use scope and the user information in the first request, whether the analysis ID is included in the data type of the user's authorization information, whether the object for which the analysis ID data analysis result is to be used includes a third network element ID or an application ID, whether the purpose for which the analysis ID data analysis result is requested to be used is consistent with the purpose authorized by the user, and whether the use time for which the analysis ID data analysis result is requested to be used is consistent with the use time authorized by the user. If all the above conditions are met, the second network element determines that the user-related data is authorized to be used for the first use scope; otherwise, the second network element determines that the user-related data is not authorized to be used for the first use scope or the corresponding authorization is unknown.

[0194] In addition, the second network element can further determine the user's authorization information by sending a request to another network element. The specific implementation is similar to the above, and the details are not repeated in this embodiment.

[0195] S304: The second network element sends a first response to the first network element, where the first response includes the acknowledgement information.

[0196] The approval information indicates whether a user corresponding to the user information permits the user-related data to be used in relation to a first range of use. Specifically, the approval information may be that the user corresponding to the user information permits the user-related data to be used in relation to the first range of use, or that the user-related data does not permit the user-related data to be used in relation to the first range of use, or that it is unclear whether the user-related data is permitted to be used in relation to the first range of use.

[0197] If the authorization information indicates that the user corresponding to the user information has not authorized the user-related data to be used with respect to the first scope of use, the first response may further include the data type that is not authorized to be used (in case the third network element simultaneously requests multiple data analysis results), reason information as to why the user-related data is not authorized to be used, etc.

[0198] S305: The first network element obtains first data, and performs data analysis on the first data to obtain a data analysis result.

[0199] When receiving the authorization information sent by the second network element, the first network element may obtain first data based on the authorization information, perform data analysis on the first data, and obtain a data analysis result to be obtained by the third network element.

[0200] Specifically, the first network element determines the first data that needs to be used to generate the data analysis result based on the analysis identifier in the second request, and then the first network element acquires the first data. The first network element may acquire the first data through multiple methods. According to one method, the first data is stored in the first network element. According to another method, the first network element sends a request to another network element to request to acquire the first data. A specific implementation of acquiring the first data by the first network element is described in the subsequent embodiments.

[0201] If the first data is acquired, the first network element performs a data analysis based on the acquired first data, and acquires a data analysis result corresponding to the analysis ID.

[0202] S306: If the authorization information indicates that the user corresponding to the user information authorizes the user-related data to be used for the first scope of use, the first network element sends a second response to the third network element, where the second response includes the user-related data.

[0203] In this embodiment, if the authorization information indicates that the user corresponding to the user information permits the relevant data to be used by the third network element, the first network element transmits the data analysis result obtained in S305 to the third network element. In response, the third network element receives the data analysis result and performs operations such as infection monitoring and paging area optimization by using the data analysis result.

[0204] S307: If the authorization information indicates that the user corresponding to the user information has not authorized the user-related data to be used in relation to the first scope of use, the first network element sends a feedback message to the third network element, where the feedback message may include a reason value indicating why the user-related data is not authorized to be used.

[0205] If the authorization information indicates that the user corresponding to the user information has not authorized the associated data to be used by the third network element, the first network element sends feedback information to the third network element, the feedback information indicating that the data analysis result requested by the third network element has been rejected and indicating the reason why the data analysis result has been rejected from being used.

[0206] It should be noted that in this embodiment, the execution conditions of S305 may include the following two cases: in one case, if the first network element determines that the user corresponding to the user information authorizes the user-related data to be used for the first scope of use, the first network element obtains the first data, performs data analysis on the first data to obtain a corresponding data analysis result, and executes S306; that is, if the authorization information indicates that the user corresponding to the user information does not authorize the user-related data to be used for the first scope of use, the first network element does not obtain the first data and does not perform data analysis.

[0207] In the other case, regardless of whether the user corresponding to the user information authorizes the user-related data to be used for the first scope of use, the first network element obtains the first data, performs data analysis based on the first data, and obtains a data analysis result. If the authorization information indicates that the user corresponding to the user information authorizes the user-related data to be used for the first scope of use, the first network element transmits the data analysis result to the third network element. If the authorization information indicates that the user corresponding to the user information does not authorize the user-related data to be used for the first scope of use, the first network element does not execute S306. That is, regardless of whether the user authorizes the user-related data to be used for the first scope of use, the first network element may first obtain the first data, perform data analysis, and obtain a data analysis result. Then, the first network element determines whether to transmit the data analysis result to the third network element based on a specific indication of the authorization information.

[0208] It should be noted that not all steps in the method embodiment provided in FIG. 3 are required. Some steps in the method embodiment provided in FIG. 3S305 to S307 in are optional.

[0209] It can be seen from the above embodiment that the first network element obtains the first data through multiple ways. In addition to pre-storing the user's related data, the first network element may further obtain the first data by requesting another network element. When obtaining the first data, the first network element may further request the second network element to obtain the user's authorization information. If the authorization information indicates that the user corresponding to the user information permits the user-related data to be used, the first network element obtains the first data. The example in which the first network element is the NWDAF and the second network element is the UDM is still used for description in the following embodiments.

[0210] With reference to the flowchart of the communication method shown in Figure 4, for the contents in this embodiment of the present application that are the same as those in the embodiments in Figures 2 and 3, reference may be made specifically to the descriptions of the embodiments in Figures 2 and 3. As shown in Figure 4, the method may include the following steps:

[0211] S401: A first network element sends a first request to a second network element, where the first request is for requesting authorization information of user-related data.

[0212] In this embodiment, to obtain the first data, the first network element first sends a first request to the second network element. The first request includes user information and a first use scope. The first use scope may include one of the following information: a first use object (e.g., NWDAF ID), a first use purpose (e.g., performing data analysis, analysis ID), and a first use time (e.g., from January 1, 2020 to June 1, 2020). Specifically, the first type identifier in the first request is an event identifier (e.g., event ID) for indicating a specific data type in the first data through the event identifier. If the first use purpose is to perform data analysis, the first use scope may further include an analysis identifier (e.g., analysis ID), and the analysis identifier is for indicating to perform data analysis on the first data to obtain a data analysis result corresponding to the analysis identifier. In addition, the first request may further include a second range of use, and the second range of use may include one or more of a second target of use, a second purpose of use, or a second time of use. The second target of use indicates a target of use of a data analysis result corresponding to the data analysis, and the second purpose of use indicates a purpose of use of the data analysis result. The second time of use indicates a time of use of the data analysis result. That is, the second range of use is a further restriction on the fourth purpose of use (obtaining the data analysis result).

[0213] S402: The second network element determines authorization information of the user based on the first request.

[0214] For a method in which the second network element determines the user's authorization information based on the first request, reference may be made to the specific implementation of S302, and details will not be repeated in this embodiment.

[0215] It should be noted that if the first request further includes a second scope of use corresponding to the data analysis result, the second network element determines, based on the user information and the second scope of use, whether the data analysis result corresponding to the analysis ID is included in the data type of the user's approval information, whether the second scope of use is included in the objects for which the user authorizes the data analysis result corresponding to the analysis ID to be used, whether the purpose authorized by the user and the second purpose of use are consistent, and whether the time of use authorized by the user to be used and the second time of use are consistent, thereby obtaining approval information regarding the second scope of use.

[0216] The second network element sends a first response to the first network element, the first response including the acknowledgement information.

[0217] S404. If the authorization information indicates that the user corresponding to the user information authorizes the first data to use the first range of use, the first network element acquires the first data.

[0218] In this embodiment, when the first request further includes a second use range corresponding to the data analysis result, the authorization information sent by the second network element includes both the authorization information on the first use range and the authorization information on the second use range. In this case, the authorization information may indicate that the user corresponding to the user information authorizes the first data to use the first range, and may indicate that the user corresponding to the user information authorizes the data analysis result corresponding to the first data to use the second range.

[0219] In this method, the first network element may acquire user-related data in cases where the user-related data is permitted to be acquired. The associated data generated by the user in the telecommunications operator network is acquired under the assumption that the GDPR law is complied with. On the one hand, the user-level data can be protected, and on the other hand, the data can be captured for training and analysis to assist in the formulation and implementation of network policies.

[0220] It should be noted that not every step in the method embodiment provided in Figure 4 is required. Some steps in the method embodiment provided in Figure 4, for example, S404 in Figure 4, are optional.

[0221] Based on the above method, Figure 5 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. As shown in Figure 5, the communication device may be a terminal device or a network device, or may be a chip or circuit, such as a chip or circuit that may be disposed in a terminal device, or a chip or circuit that may be disposed in a network device. The network device in the embodiment of the present application may be any one or more of a first network element, a second network element, a third network element, a fourth network element, or a terminal device.

[0222] Furthermore, the communication device 501 may further include a bus system. The processor 502, the memory 504, and the transceiver 503 may be connected through the bus system.

[0223] It should be understood that the processor 502 may be a chip. For example, the processor 502 may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or another integrated chip.

[0224] In the implementation process, the steps in the aforementioned method can be implemented by using hardware integrated logic circuits in the processor 502 or by using instructions in the form of software. The steps of the method disclosed with reference to the embodiments of the present application can be directly executed by a hardware processor, or can be executed by a combination of hardware modules and software modules in the processor 502. The software modules can be disposed in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is disposed in the memory 504, and the processor 502 reads the information in the memory 504 and completes the steps in the aforementioned method in combination with the hardware of the processor.

[0225] It should be noted that the processor 502 in the embodiment of the present application may be an integrated circuit chip and has signal processing capabilities. In implementation, the steps in the above method embodiment may be implemented by using an integrated logic circuit of hardware in the processor, or an instruction in the form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. It may implement or execute the method, steps, and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the method disclosed with reference to the embodiment of the present application may be directly performed and completed by using a hardware decoding processor, or may be performed and completed by using a combination of hardware modules and software modules in the decoding processor. The software modules may be located in mature storage media in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the method in combination with the hardware.

[0226] The transceiver may be, for example, a transceiver unit including a receiving unit and a transmitting unit. The transceiver may also be a transceiver circuit or an interface circuit. The transceiver is for communication between the processor and an external network element or elements.

[0227] It can be understood that the memory 504 in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memory. The non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM) and is used as an external cache. Many forms of RAM may be used, such as, by way of example and not limitation, static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DRRAM). It should be noted that memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0228] In the case where the communication device 501 corresponds to the first network element in the aforementioned method, the communication device may include a processor 502, a transceiver 503, and a memory 504. The memory 504 is configured to store instructions, and the processor 502 is configured to execute the instructions stored in the memory 504 to implement the related solutions of the first network element in any one or more of the corresponding methods shown in Figures 2 to 4. Specifically, the transceiver 503 is configured to: send a first request to the second network element, where the first request is for requesting authorization information of the user-related data, where the first request includes user information and a first range of use of the user-related data, where the first range of use includes at least one of information of a first use target, a first purpose of use, and a first time of use; and receive a first response sent by the second network element, where the first response includes authorization information indicating whether a user corresponding to the user information has allowed the user-related data to be used with respect to the first range of use.

[0229] In the case where the communication device 501 is a first network element, the transceiver 503 is particularly configured to receive a second request sent by a third network element, the second request being for requesting user-related data, and to send a first request to the second network element based on the second request.

[0230] In the case where the communication device 501 is the first network element, the processor 502 is configured to obtain the first range of use from the third range of use based on the second request.

[0231] In the case where the communication device 501 is a first network element, the processor 502 is further configured to determine the first type identifier based on the second type identifier.

[0232] In the case where the communication device 501 is a first network element, the processor 502 is specifically configured to determine a first type identifier based on the configuration information and the second data type identifier, the configuration information indicating a correspondence between the first type identifier and the second type identifier.

[0233] In the case where the communication device 501 is a first network element, the processor 502 is specifically configured to determine the second data type identifier as the first type identifier.

[0234] In the case where the communication device 501 is a data acquisition network element, the transceiver 503 is further configured to transmit a second response to the third network element, the second response including the user-related data requested by the third network element.

[0235] In the case where the communication device 501 is a first network element, the processor 502 is specifically configured to obtain the user-related data if the authorization information indicates that the user corresponding to the user information has authorized the user-related data to be used in relation to the first range of use.

[0236] In the case where the communication device 501 is a first network element, if the authorization information indicates that the user corresponding to the user information has not authorized the user-related data to be used in relation to the first scope of use, the processor 502 is specifically configured to delete the user-related data or stop acquiring the user-related data.

[0237] In the case where the communication device 501 corresponds to the second network element in the aforementioned method, the communication device may include a processor 502, a transceiver 503, and a memory 504. The memory 504 is configured to store instructions, and the processor 502 is configured to execute the instructions stored in the memory 504 to implement the related solutions of the second network element in any one or more of the corresponding methods shown in Figures 2 to 4. The transceiver 503 is configured to receive a first request sent by the first network element. The first request is for requesting authorization information of the user-related data, the first request including user information and a first use range of the user-related data, the first use range including at least one of the following information: a first use target, a first use purpose, and a first use time. The processor 502 is configured to determine the authorization information based on the first request and send a first response to the first network element, the first response including the authorization information of the user-related data.

[0238] In the case where the communication device 501 corresponds to the second network element in the aforementioned method, the processor 502 is particularly configured to determine authorization information corresponding to the user information based on whether the first request matches stored authorization information of the network user.

[0239] In the case where the communication device 501 corresponds to the second network element in the aforementioned method, the processor 502 is particularly configured to: initiate, based on the first request by the second network element, a third request to the terminal device corresponding to the user information, the third request being for requesting authorization information corresponding to the user information from the terminal device; and receive, by the second network element, a third response sent by the terminal device, the third response including the authorization information corresponding to the user information.

[0240] In the case where the communication device 501 corresponds to the second network element in the aforementioned method, the processor 502 is particularly configured to initiate, by the transceiver 503, a fourth request to the fourth network element based on the first request, the fourth request being for requesting authorization information corresponding to the user information from the fourth network element, and to receive a fourth response sent by the fourth network element, the fourth response including the authorization information corresponding to the user information.

[0241] In the case where the communication device 501 corresponds to the third network element in the aforementioned method, the communication device may include a processor 502, a transceiver 503, and a memory 504. The memory 504 is configured to store instructions, and the processor 502 is configured to execute the instructions stored in the memory 504 to implement the related solutions of the third network element in any one or more of the corresponding methods shown in Figures 2 to 4. The transceiver 503 sends a second request to the first network element. The second request is for requesting to obtain user-related data, and includes user information and a third use range. The third use range includes at least one of the following information: a third use target, a third use purpose, and a third use time. The transceiver 503 receives a second response sent by the first network element. The second response includes user-related data or display information, and the display information indicates a failure in obtaining the user-related data.

[0242] In the case where the communication device 501 corresponds to the terminal device in the aforementioned method, the communication device may include a processor 502, a transceiver 503, and a memory 504. The memory 504 is configured to store instructions, and the processor 502 is configured to execute the instructions stored in the memory 504 to implement the related solutions of the data-providing network element in any one or more of the corresponding methods shown in Figures 2 to 4. The transceiver 503 receives a third request sent by the second network element. The third request is for requesting authorization information of the user-related data, and the third request includes a first use range of the user-related data, and the first use range includes at least one of the following information: a first use target, a first use purpose, and a first use time. The processor 502 determines the authorization information based on the third request, and sends a third response to the second network element through the transceiver 503. The third response includes the authorization information.

[0243] If the communication device 501 corresponds to a data-providing network element in the aforementioned method, the transceiver 503 is particularly configured to: send a fifth request to the data-managing network element, the fifth request being for requesting to obtain user authorization information; and receive a fifth response from the data-managing network element, the fifth response carrying the user authorization information.

[0244] For the concept, explanation, detailed description and other steps of the communication device related to the technical solutions provided in the embodiments of the present application, please refer to the content description in the above method or other embodiments, and the details will not be repeated here again.

[0245] According to the aforementioned method, FIG. 6 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. As shown in FIG. 6, a communication device 601 may include a communication interface 604, a processor 602, and a transceiver 603. The communication interface 604 is configured to input and / or output information, and the processor 602 is configured to execute a computer program or instruction, whereby the communication device 601 implements the method on the terminal device side in the related solutions from FIG. 2-FIG. 4, or the communication device 601 implements the method on the network device side in the related solutions from FIG. 2-FIG. 4. The network device side is, for example, any one or more of a first network element, a second network element, a third network element, a fourth network element, and a fifth network element. In an embodiment of the present application, the transceiver 603 may implement the solution implemented by the transceiver 503 in FIG. 5, and the processor 602 may implement the solution implemented by the processor 502 in FIG. 5. This will not be repeated here.

[0246] According to the method provided in the embodiment of the present application, the embodiment of the present application further provides a communication system, which includes the above-mentioned network device and one or more terminal devices, the network device being, for example, any one or more of a first network element, a second network element, a third network element, a fourth network element, and a fifth network element.

[0247] Based on the above embodiment and the same concept, Figure 7 is a schematic diagram of a communication device according to an embodiment of the present application. As shown in Figure 7, the communication device 701 can be a terminal device or a network device, or a chip or circuit, such as a chip or circuit that can be disposed in a terminal device or a network device.

[0248] In the case where the communication device 701 corresponds to the first network element in the aforementioned method, the communication device may include a processing unit 702, a transceiver unit 703, and a storage unit 704. The storage unit 704 is configured to store instructions, and the processing unit 702 is configured to execute the instructions stored in the storage unit 704 to implement the related solutions of the first network element in any one or more of the corresponding methods shown in Figures 2 to 4. The transceiver unit 703 is configured to: send a first request to the second network element, the first request being for requesting authorization information of the user-related data, the first request including user information and a first range of use of the user-related data, the first range of use including at least one of information of a first use subject, a first purpose of use, and a first time of use; and receive a first response sent by the second network element, the first response including authorization information indicating whether a user corresponding to the user information has allowed the user-related data to be used with respect to the first range of use.

[0249] In the case where the communication device 701 corresponds to the second network element in the aforementioned method, the communication device may include a processing unit 702, a transceiver unit 703, and a storage unit 704. The storage unit 704 is configured to store instructions, and the processing unit 702 is configured to execute the instructions stored in the storage unit 704 to implement the related solutions of the second network element in any one or more of the corresponding methods shown in Figures 2 to 4. The transceiver unit 703 receives a first request sent by the first network element, the first request is for requesting authorization information of the user-related data, the first request includes user information and a first use scope of the user-related data, the first use scope includes at least one of the following information: a first use object, a first use purpose, and a first use time. The processing unit 702 determines the authorization information based on the first request. The transceiver unit 703 transmits a first response to the first network element, the first response including authorization information, the authorization information indicating whether a user corresponding to the user information has authorized the user-related data to be used with respect to the first range of use.

[0250] In the case where the communication device 701 corresponds to the third network element in the aforementioned method, the communication device may include a processing unit 702, a transceiver unit 703, and a storage unit 704. The storage unit 704 is configured to store instructions, and the processing unit 702 is configured to execute the instructions stored in the storage unit 704 to implement the related solutions of the third network element in any one or more of the corresponding methods shown in Figures 2 to 4. The transceiver unit 703 sends a second request to the first network element. The second request is for requesting to obtain user-related data, and includes user information and a third use range. The third use range includes at least one of the following information: a third use object, a third use purpose, and a third use time. The transceiver unit 703 receives a second response sent by the first network element. The second response includes user-related data or display information, and the display information indicates that the user-related data has failed to be obtained.

[0251] In the case where the communication device 701 corresponds to the terminal device in the aforementioned method, the communication device may include a processing unit 702, a transceiver unit 703, and a storage unit 704. The storage unit 704 is configured to store instructions, and the processing unit 702 is configured to execute the instructions stored in the storage unit 704 to implement the related solutions of the terminal device in any one or more of the corresponding methods shown in Figures 2 to 4. The transceiver unit 703 receives a third request sent by the second network element. The third request is for requesting authorization information of the user-related data, and the third request includes a first use scope of the user-related data, and the first use scope includes at least one of the following information: a first use object, a first use purpose, and a first use time. The terminal device determines the authorization information based on the third request, and sends a third response to the second network element. The third response includes the authorization information.

[0252] For the concept, explanation, detailed description and other steps of the communication device related to the technical solutions provided in the embodiments of the present application, please refer to the content description in the above method or other embodiments, and the details will not be repeated here again.

[0253] It can be understood that for the functions of the units in the communication device 701, please refer to the implementation of the corresponding method embodiments, and the details will not be repeated here again.

[0254] It should be understood that the division of the communication device into the above units is only a logical functional division. In actual implementation, all or some of the units may be integrated into one physical entity or may be physically separated. In the embodiment of the present application, the transceiver unit 702 may be implemented by the transceiver 503 in FIG. 5, and the processing unit 70 3 may be implemented by the processor 502 in FIG.

[0255] According to the method provided in the embodiment of the present application, the present application further provides a computer program product, which includes computer program code, which when run on a computer, causes the computer to execute the steps of FIG. 4 It is possible to carry out the method in any one of the embodiments shown in.

[0256] According to the method provided in the embodiment of the present application, the present application further provides a computer-readable storage medium, which stores a program code, when the program code is run on a computer, the computer is enabled to execute the method according to any one of the embodiments shown in FIG.

[0257] According to the method provided in the embodiment of the present application, the present application further provides a system, which includes one or more terminal devices as mentioned above and one or more network devices as mentioned above.

[0258] It should be noted that for specific implementations of each module in this embodiment, reference may be made to the aforementioned method embodiments, and details in this embodiment will not be repeated here.

[0259] In this application, it is to be understood that "at least one" means one or more, and "multiple" means two or more. The term "and / or" is used to describe an association relationship between associated objects, and indicates that three relationships may exist. For example, "A and / or B" may represent three cases: "only A is present", "only B is present", and "both A and B are present", where A and B may be singular or plural. The character " / " generally indicates an "or" relationship between associated objects. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or multiple items. For example, at least one of a, b, or c may refer to a, b, c, "a and b", "a and c", "b and c", or "a, b, and c", where a, b, and c may be singular or plural.

[0260] It should be noted that relationship terms such as "first" and "second" are used herein only to distinguish one entity or operation from another and do not necessarily require or imply that any actual relationship or order exists between these entities or operations. Moreover, the term "include" or any other variation thereof is intended to cover a non-exclusive inclusion, whereby a process, method, article, or device that includes a list of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article, or device. An element preceded by "includes a..." does not, without further constraints, exclude the presence of further identical elements in the process, method, article, or device that includes the element.

[0261] In conjunction with the embodiments disclosed herein, the method or algorithm steps may be implemented by hardware, a software module executed by a processor, or a combination thereof. The software module may be configured in a random access memory (RAM), memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium well known in the art.

[0262] The above disclosed embodiments are described to enable any person skilled in the art to make or use the present application. Various modifications to the embodiments will be apparent to those skilled in the art, and the general principles defined herein may be practiced without departing from the spirit and scope of the present application. Example Other embodiments may be implemented without departing from the scope of the present invention, and thus the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. sending a first request by a first network element to a second network element, the first request being for requesting authorization information of user-related data, the first request including user information and a first use scope of the user-related data, the user-related data including first data corresponding to a user generated by at least one of a terminal device, an application server, or a network device, the first use scope including a first use purpose of the user-related data, the first use purpose including performing data analysis of the first data; receiving, by the first network element, a first response sent by the second network element, the first response including the authorization information, the authorization information indicating whether the user corresponding to the user information permits the user-related data to be used with respect to the first scope of use; A communication method comprising:

2. The method of claim 1 , wherein the user-related data further comprises second data related to the user, the second data comprising data analysis results obtained by performing a data analysis based on the first data.

3. The first request further includes a first type identifier, the first type identifier for identifying a type of the user-related data; The first request is for requesting approval information of the user-related data, The method of claim 1 or 2, wherein the first request is for requesting approval information for user-related data corresponding to the first type identifier.

4. The method of claim 3 , wherein when the user-related data is first data, the first type identifier is an event identifier, and the first data is data associated with an event corresponding to the event identifier.

5. 5. The method of claim 1, wherein the first network element is a Network Data Analysis Function (NWDAF) network element and the second network element is a Unified Data Management (UDM) network element, a User Data Repository (UDR) network element, an Authentication Service Function (AUSF) network element, or a terminal device.

6. 6. The method of claim 5, wherein the first scope of use further includes a first object of use, and when the user-related data is first data, the first object of use is the Network Data Analysis Function (NWDAF) network element.

7. 6. The method of claim 5, wherein when the user-related data is first data, the first scope of use further includes an analysis identifier, the analysis identifier to indicate to perform a data analysis on the first data to obtain a data analysis result corresponding to the analysis identifier.

8. 8. The method of claim 7, wherein the first request further includes a second range of use corresponding to the data analysis result, the second range of use including at least one of information on a second target of use, a second purpose of use, and a second time of use.

9. The method of claim 3 , wherein when the user-related data is second data, the first type identifier is an analysis identifier, and the second data is a data analysis result corresponding to the analysis identifier.

10. 5. The method of claim 1, wherein the first network element is a Network Exposure Function (NEF) network element and the second network element is a Unified Data Management (UDM) network element, a User Data Repository (UDR) network element, an Authentication Service Function (AUSF) network element, or a terminal device.

11. The method according to claim 10, wherein the first scope of use further comprises a first object of use, the first object of use being an application server AF.

12. 5. The method according to claim 1, wherein if the first network element is an Access and Mobility Management Function (AMF) network element, the second network element is an Unified Data Management (UDM) network element, a User Data Repository (UDR) network element, an Authentication Services Function (AUSF) network element, or a terminal device.

13. receiving, by the first network element, a second request sent by a third network element, the second request being for requesting to obtain user-related data; The step of transmitting, by a first network element, a first request to a second network element, further comprises:

13. The method of claim 5, comprising the step of transmitting, by the first network element, the first request based on the second request to the second network element.

14. The second request includes user information and a third range of use, and the third range of use includes at least one of information on a third target of use, a third purpose of use, and a third time of use, and the method further includes: The method of claim 13 , further comprising the step of obtaining, by the first network element, the first usage range based on the third usage range.

15. the second request includes a second type identifier, the second type identifier for identifying a type of the user related data requested by the third network element, and the method further comprises: The method of claim 13 or 14, further comprising the step of determining, by the first network element, a first type identifier based on the second type identifier.

16. The step of determining, by the first network element, a first type identifier based on the second type identifier, further comprises:

16. The method of claim 15, comprising determining, by the first network element, the second type identifier as the first type identifier.

17. The step of determining, by the first network element, a first type identifier based on the second type identifier, further comprises:

16. The method of claim 15, further comprising: determining, by the first network element, the first type identifier based on configuration information and the second type identifier, the configuration information indicating a correspondence between the first type identifier and the second type identifier.

18. The method according to any one of claims 14 to 17, wherein the third network element is an Application Server (AF) or a Network Function (NF) network element.

19. A communication device, comprising: a memory containing computer readable instructions; a processor in communication with the memory, the processor being configured to execute the computer readable instructions to enable the communications device to perform the method of any one of claims 1 to 18; A communication device comprising:

20. A communication system comprising a first network element and a second network element, The first network element is configured to send a first request to the second network element to perform the method according to any one of claims 1 to 18, The second network element is configured to transmit a first response to the first network element.

21. 19. A computer readable storage medium having stored thereon computer readable instructions which, when invoked by a computer, enable the computer to perform the method of any one of claims 1 to 18.

22. sending a first request by a first network element to a second network element, the first request being for requesting authorization information of user-related data, the first request including user information and a first use scope of the user-related data, the user-related data including first data corresponding to a user generated by at least one of a terminal device, an application server, or a network device, the first use scope including a first use purpose of the user-related data, the first use purpose including performing data analysis of the first data; receiving, by the second network element, the first request from the first network element; sending, by the second network element, a first response to the first network element, the first response including the authorization information, the authorization information indicating whether the user corresponding to the user information permits the user-related data to be used in relation to the first scope of use; receiving, by the first network element, the first response from the second network element; A communication method comprising:

Images