CN117641309A

CN117641309A - User intention verification method and device and network equipment

Info

Publication number: CN117641309A
Application number: CN202210970448.0A
Authority: CN
Inventors: 崇卫微
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-08-12
Filing date: 2022-08-12
Publication date: 2024-03-01
Also published as: WO2024032588A1

Abstract

The application discloses a user willingness verification method, a device and network side equipment, wherein the user willingness verification method comprises the following steps: the method comprises the steps that a first network element receives a data acquisition request, wherein the data acquisition request is used for requesting acquisition of target data, and the target data are: data corresponding to a roaming user equipment in a home public land mobile network HPLMN or a visiting public land mobile network VPLMN and/or data analysis results of the roaming user equipment generated by the HPLMN or the VPLMN; the first network element sends a user willingness verification request to an authorization management unit in the HPLMN, wherein the user willingness verification request is used for requesting to confirm the user willingness of the data acquisition request; the first network element receives a user intention verification response carrying the user intention information sent by the authorization management unit; the user willingness information is used for indicating: whether the user is allowed to acquire the target data.

Description

User intention verification method and device and network equipment

Technical Field

The application belongs to the technical field of wireless communication, and particularly relates to a user willingness verification method, a user willingness verification device and network side equipment.

Background

In a communication network, network elements, such as network data analysis functions (Network Data Analytics Function, NWDAF), are introduced for intelligent data analysis and for generating data analysis results for tasks. The data analysis result can assist the in-network and out-network equipment to make policy decisions, and aims to improve the degree of intellectualization of the policy decisions of the equipment by using an artificial intelligence (Artificial Intelligence, AI) method.

For example, NWDAF contains model training logic functions) (Model Training Logical Function, MTLF), and artificial intelligence/machine learning (AI/ML) model training may be performed based on training data to obtain a model corresponding to a certain AI task. The NWDAF comprises an analysis logic function (Analytics Logical Function, anLF)), and can perform model reasoning based on an AI/ML model and reasoning input data to obtain a data analysis result (or called as a reasoning result) corresponding to a specific AI reasoning task, and a consumer (consumer) of the NWDAF data analysis result, such as a policy control functional entity (Policy Control Function, PCF), can execute an intelligent policy and charging control (Policy and Charging Control, PCC) policy based on a certain reasoning result, such as making an intelligent user residence policy according to a user business behavior analysis result, so as to promote the business experience of a user; or, the consumer of NWDAF data analysis results, such as access mobility management function (Access and Mobility Management Function, AMF), can perform intelligent mobility management operation based on some inference result analysis, such as intelligent paging of the user according to the user's movement track analysis result, so as to improve the paging accessibility.

The NWDAF can acquire a large amount of data generated in the network, and generate data analysis results (data analysis). Generally, if the NWDAF needs to acquire data related to the user, it needs to confirm whether the user agrees, but in the prior art, no scheme is proposed for user willingness management in the data acquisition process of the roaming user equipment across PLMNs.

Disclosure of Invention

The embodiment of the application provides a user willingness verification method, a user willingness verification device and network side equipment, which can solve the problem of user willingness management in the process of acquiring data crossing PLMN and protect the privacy of user data.

In a first aspect, a method for verifying user willingness is provided, including:

the method comprises the steps that a first network element receives a data acquisition request, wherein the data acquisition request is used for requesting acquisition of target data, and the target data are: data corresponding to a roaming user equipment in a home public land mobile network HPLMN or a visiting public land mobile network VPLMN and/or data analysis results of the roaming user equipment generated by the HPLMN or the VPLMN;

the first network element sends a user willingness verification request to an authorization management unit in the HPLMN, wherein the user willingness verification request is used for requesting to confirm the user willingness of the data acquisition request;

The first network element receives a user intention verification response carrying the user intention information sent by the authorization management unit; the user willingness information is used for indicating: whether the user is allowed to acquire the target data.

In a second aspect, a method for verifying user will is provided, including:

the authorization management unit receives a user willingness verification request, wherein the user willingness verification request is used for requesting to confirm the user willingness of the data acquisition request; the data acquisition request is used for requesting to acquire target data, and the target data is: data corresponding to a roaming user equipment in a home public land mobile network HPLMN or a visiting public land mobile network VPLMN and/or data analysis results of the roaming user equipment generated by the HPLMN or the VPLMN;

the authorization management unit sends a user intention verification response carrying the user intention information; the user willingness information is used for indicating: whether the user is allowed to acquire the target data.

In a third aspect, there is provided a user intent verification apparatus including:

the first receiving module is used for receiving a data acquisition request, wherein the data acquisition request is used for requesting to acquire target data, and the target data is: data corresponding to a roaming user equipment in a home public land mobile network HPLMN or a visiting public land mobile network VPLMN and/or data analysis results of the roaming user equipment generated by the HPLMN or the VPLMN;

The first sending module is used for sending a user willingness verification request to an authorization management unit in the HPLMN, wherein the user willingness verification request is used for requesting to confirm the user willingness of the data acquisition request;

the first receiving module is further configured to receive a user intention verification response carrying the user intention information sent by the authorization management unit; the user willingness information is used for indicating: whether the user is allowed to acquire the target data.

In a fourth aspect, there is provided a user intent verification apparatus including:

the second receiving module is used for receiving a user willingness verification request, wherein the user willingness verification request is used for requesting to confirm the user willingness of the data acquisition request; the data acquisition request is used for requesting to acquire target data, and the target data is: data corresponding to a roaming user equipment in a home public land mobile network HPLMN or a visiting public land mobile network VPLMN and/or data analysis results of the roaming user equipment generated by the HPLMN or the VPLMN;

the second sending module is used for sending a user intention verification response carrying the user intention information; the user willingness information is used for indicating: whether the user is allowed to acquire the target data.

In a fifth aspect, a network side device is provided, comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor implement the steps of the user intent verification method as described in the first or second aspect above.

In a sixth aspect, there is provided a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the steps of the user intent verification method of the first or second aspect described above.

In a seventh aspect, there is provided a chip comprising a processor and a communication interface coupled to the processor, the processor being for running a program or instructions to implement the method of the first or second aspect.

In an eighth aspect, there is provided a computer program/program product stored in a storage medium, the computer program/program product being executable by at least one processor to perform the steps of the method according to the first or second aspect.

In the embodiment of the invention, the network element in the PLMN performs user wish verification of the user level on the data acquisition request, thereby ensuring the privacy of user data and improving the data security of the data acquisition process of the roaming user equipment crossing the PLMN.

Drawings

Fig. 1 is a block diagram of a wireless communication system to which embodiments of the present application are applicable;

FIG. 2 is a flowchart of a user intent verification method according to an embodiment of the present application;

FIG. 3 is a second flowchart of a user intent verification method according to an embodiment of the present disclosure;

fig. 4 is a flow chart of a user willingness verification method according to the first embodiment of the present application;

fig. 5 is a flow chart of a user intent verification method according to a second embodiment of the present application;

fig. 6 is a flow chart of a user willingness verification method in the third embodiment of the present application;

fig. 7 is a flowchart of a user intent verification method according to a fourth embodiment of the present application;

fig. 8 is a schematic structural diagram of a user intention verification apparatus according to an embodiment of the present application;

FIG. 9 is a second schematic diagram of a user intent verification apparatus according to an embodiment of the present disclosure;

FIG. 10 is a schematic diagram of a network measurement device according to an embodiment of the present disclosure;

FIG. 11 is a second schematic diagram of a network measurement device according to an embodiment of the present disclosure.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the terms "first" and "second" are generally intended to be used in a generic sense and not to limit the number of objects, for example, the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example and uses NR terminology in much of the description that follows, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a furniture), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. Note that, the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may comprise an access network device or core network device, wherein the access network device may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. The access network device may include a base station, a WLAN access point, a WiFi node, or the like, where the base station may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission receiving point (Transmitting Receiving Point, TRP), or some other suitable terminology in the field, and the base station is not limited to a specific technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiment of the present application, only the base station in the NR system is described by way of example, and the specific type of the base station is not limited. The core network device may include, but is not limited to, at least one of: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), user plane functions (User Plane Function, UPF), policy control functions (Policy Control Function, PCF), policy and charging rules function units (Policy and Charging Rules Function, PCRF), edge application service discovery functions (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data repository (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage functions (Network Repository Function, NRF), network opening functions (Network Exposure Function, NEF), local NEF (or L-NEF), binding support functions (Binding Support Function, BSF), application functions (Application Function, AF), and the like. In the embodiment of the present application, only the core network device in the NR system is described as an example, and the specific type of the core network device is not limited.

The user wish verification method, device and network side equipment provided by the embodiment of the application are described in detail below through some embodiments and application scenes thereof with reference to the accompanying drawings.

Referring to fig. 2, a user wish verification method provided in an embodiment of the present application includes:

step 21, the first network element receives a data acquisition request, where the data acquisition request is used to request acquisition of target data, and the target data is: data corresponding to a roaming user equipment in a home public land mobile network HPLMN or a visiting public land mobile network VPLMN and/or data analysis results of the roaming user equipment generated by the HPLMN or the VPLMN;

step 22, the first network element sends a user willingness verification request to an authorization management unit in the HPLMN, wherein the user willingness verification request is used for requesting to confirm the user willingness of the data acquisition request;

step 23, the first network element receives a user willingness verification response carrying user willingness information (user consent info) sent by the authorization management unit; the user willingness information is used for indicating: whether the user is allowed to acquire the target data.

In a specific embodiment of the present invention, the data acquisition request may be generated in various scenarios, as follows:

the data consumer of the target data is a data consumer in the VPLMN, and the data provider is a data provider in the VPLMN;

or alternatively

The data consumer of the target data is a data consumer in the VPLMN, and the data provider is a data provider of the HPLMN;

or alternatively

The data consumer of the target data is a data consumer in the HPLMN, and the data provider is a data consumer in the VPLMN.

That is, in some embodiments, the user intent verification method described above is applied to the VPLMN or the network element in the VPLMN obtaining the target data of the roaming user terminal in the HPLMN from the HPLMN.

In some embodiments, the user willingness verification method described above is applied to the HPLMN or the network element in the HPLMN obtains the target data of the roaming user terminal in the VPLMN from the VPLMN.

Meanwhile, in some embodiments, the method for verifying user will may be further applied to VPLMN or a network element in VPLMN to obtain the target data of the roaming user terminal in VPLMN from VPLMN.

The target data includes two types:

the data generated by the roaming user equipment in the PLMN can also be called data corresponding to the roaming user equipment in the HPLMN, and can be original data or processed intermediate data, such as slice information, PDU session information and the like of the HPLMN where the user equipment is located;

And

and the data analysis results of the roaming user equipment, such as historical track statistical information of the roaming user equipment in the PLMN, business behavior habit analysis of the roaming user equipment in the PLMN, data analysis results generated in real time by the roaming user equipment in the PLMN and the like.

The method of the embodiment of the invention is used for carrying out user willingness management on the data acquisition of the roaming user terminal crossing PLMN, and the user willingness management can be realized through the existing network element, namely the first network element can be the existing network element in the PLMN, for example, the network element for realizing the inter-PLMN communication function in each PLMN, but can also be other network elements, even newly added network elements or functional entities, and the method is not particularly limited.

Meanwhile, in the user intention verification method of the embodiment of the present invention, verification is performed based on user intention information, which is different from inter-PLMN authorization, and this is further described below.

For inter-PLMN authorization, the subscription information between PLMNs is of interest. Which may be subject to authorization management according to local policies or operator configuration policies. The home policy or operator configured policy may be, for example, a roaming agreement signed between two PLMNs. The roaming agreement signs information such as the range and/or type of data and/or data analysis results allowed to be acquired between two PLMNs.

Unlike inter-PLMN authorization information, the user intention information in the present application includes three layers of information: the method comprises the steps of a PLMN where a consumer is located, a PLMN where a data provider is located and user information, wherein the user information is not available in the authorization information among PLMNs. The user intention information expresses whether the user allows the acquisition of the target data, not whether the PLMN allows the acquisition of the target data.

In a specific embodiment of the present invention, the authorization management unit may be various network elements capable of storing user willingness information, such as UDM, UDR, NEF, SEPP in the HPLMN, or may independently set a new network element to implement the storage of the user willingness information, which will not be further described in detail.

In a specific embodiment of the present invention, the user willingness information is used to indicate: whether the user is allowed to acquire the target data corresponds to the three scenarios (the data consumer in the VPLMN requests the target data in the VPLMN; the data consumer in the VPLMN requests the target data in the HPLMN; the data consumer in the HPLMN requests the target data in the VPLMN), the user willingness information may be used to indicate: allowing or rejecting the VPLMN or the network element in the VPLMN to acquire the target data in the VPLMN by the user; allowing or rejecting the VPLMN or the network element in the VPLMN to acquire the target data in the HPLMN by the user; and allowing or rejecting the HPLMN or the network element in the HPLMN to acquire the target data in the VPLMN by the user.

In order to further improve the accuracy of the user willingness information indication, and achieve more accurate privacy management of the target data, the user willingness verification response may further carry at least one of the following first auxiliary information:

the first target data type information is used for indicating the type of the target data which the user is allowed to acquire;

the first target time period information is used for indicating a time period in which the user allows the acquired target data to be located;

the first destination information is used for indicating the permitted use destination of the target data which is permitted to be acquired by the user;

and the first area identification information is used for indicating a use area allowed by the target data allowed to be acquired by the user.

By setting the first auxiliary information, the target data acquired in the data acquisition process can be further controlled and limited, the accuracy of privacy management is further improved, and the safety of the data is also improved.

The method of the embodiment of the invention can be applied to various scenes (a data consumer in the VPLMN requests target data in the VPLMN, a data consumer in the VPLMN requests target data in the HPLMN, and a data consumer in the HPLMN requests target data in the VPLMN), so as to realize scene distinction and more refined user willingness management, and the user willingness verification request can carry at least one of the following information:

User equipment information for indicating the roaming user equipment;

the description information of the data provider is used for indicating the PLMN where the data provider of the target data is located;

and the description information of the data consumer is used for indicating the PLMN of the data consumer of the target data, or indicating the interface network element of the PLMN of the data consumer of the target data.

In a specific embodiment of the present invention, in the embodiment of the present invention, the roaming user equipment may be a certain user equipment roaming from the home PLMN to the visited PLMN, or may be all user equipment roaming from the home PLMN to the visited PLMN in a certain user equipment group, or may be all user equipment roaming from the home PLMN to the visited PLMN.

In a different manner, the ue information may be a ue ID, a ue group ID, region information corresponding to the ue, and other information that may describe the ue.

The above description information of the data consumer realizes management with different granularity according to different needs, for example: PLMN level management and network element level (consumer and interface network element) management.

The location of the information in the request message may be preconfigured for the above information to achieve an implicit indication, e.g. the information at location a is descriptive of the data provider and the information at location B is descriptive of the data consumer. The indication of the display may also be implemented by the information itself, e.g. the description information of the data provider comprises two parts, one being a PLMN ID and the other field indicating that the PLMN is associated with the data provider.

By setting the description information of the data provider and the description information of the data consumer, in combination with the user intention information, finer user intention management can be achieved, for example, the user a can allow the data consumer in the HPLMN to request the target data in the VPLMN but not allow the data consumer in the VPLMN to request the target data in the HPLMN, and the user B cannot allow the data consumer in the HPLMN to request the target data in the VPLMN but allow the data consumer in the VPLMN to request the target data in the HPLMN.

In order to further improve the accuracy of user willingness information management and realize more accurate privacy management of target data, the user willingness verification request can also carry at least one of the following second auxiliary information:

Second target data type information for indicating a type of the target data requested to be acquired;

the second target time period information is used for indicating the time period of the target data which is requested to be acquired;

second destination information indicating a destination of use of the target data requested to be acquired;

and the second area identification information is used for indicating an area where the target data requested to be acquired is located.

The setting of the second auxiliary information can also realize more accurate user willingness management.

The various types of information may be derived from a data acquisition request, and in this embodiment of the present application, optionally, the data acquisition request includes at least one of the following information:

a roaming indication for indicating that the data acquisition request is for a roaming user equipment;

user equipment information for indicating the roaming user equipment;

The description information of the data consumer is used for indicating the PLMN where the data consumer of the target data is located, or is used for indicating the data consumer of the target data, or is used for indicating the interface network element of the PLMN where the data consumer of the target data is located;

the description information of the data report is used for indicating the time or format and the like for feeding back the target data;

for the acquisition process of the target data of the roaming user equipment, the patent application with the application date of 2022/3/28, the application number of 202210317114.3 and the name of user willingness verification method, device and network side equipment is added as a quote file.

The auxiliary information in the user intention verification request and the user intention verification request response can be independently existed respectively, and can also be combined for use, so that user intention management with different accuracies, different granularities and different purposes can be realized, the accuracy of user intention management is improved, the accuracy of target data privacy management and the safety of user data are improved, and the flexibility of user intention management is also improved.

Considering that the user intention verification method in the embodiment of the invention focuses on user intention management and verification in the process of acquiring target data of a roaming user, interaction among PLMNs is involved in many cases, and in order to facilitate implementation of a flow, in a specific embodiment of the invention, the first network element can be implemented through an interface network element in the first PLMN, in this way, the interface network element can implement interaction of information/signaling/data among PLMNs by utilizing a communication function among PLMNs possessed by the interface network element, and indirect information/signaling/data transmission is not required to be implemented through other network elements, thereby simplifying implementation flow.

In a specific embodiment of the present invention, the user willingness information is used to indicate: whether the user is allowed to acquire the target data, that is, the above-described user intention information is ultimately control for data acquisition.

The first network element described above may be a network element capable of directly performing data acquisition operations. However, in some cases, for example, the first network element is a network element in the first PLMN, and the target data is data in another PLMN, where the first network element cannot directly use the user intention information to collect the data, where the first network element needs to forward the user intention information to an interface network element in the second PLMN.

That is, in the embodiment of the present invention, the network element initiating user wish verification and the network element performing data acquisition by using user wish information may be the same network element or may be different network elements.

In the above case, after receiving the user intention verification response carrying the user intention information sent by the authorization management unit, the first network element further includes:

the first network element executes data acquisition operation according to the user willingness information;

or alternatively

Forwarding the user willingness information to an interface network element in a second PLMN, so that the interface network element in the second PLMN can execute data acquisition operation according to the user willingness information, and the second PLMN is a VPLMN or an HPLMN.

In a specific embodiment of the present invention, when the user willingness information indicates that the user does not allow to acquire the target data, the data acquisition rejection response may be directly sent, or the reason information indicating the rejection reason may be carried in the data acquisition rejection response, for example, the VPLMN may be indicated in the data acquisition rejection response not to be in the user-specified whitelist, so as to improve the accuracy of the indication.

Referring to fig. 3, the embodiment of the present application further provides a user wish verification method, including:

Step 31, an authorization management unit receives a user willingness verification request, wherein the user willingness verification request is used for requesting to confirm the user willingness of the data acquisition request; the data acquisition request is used for requesting to acquire target data, and the target data is: data corresponding to a roaming user equipment in a home public land mobile network HPLMN or a visiting public land mobile network VPLMN and/or data analysis results of the roaming user equipment generated by the HPLMN or the VPLMN;

step 32, the authorization management unit sends a user intention verification response carrying the user intention information; the user willingness information is used for indicating: whether the user is allowed to acquire the target data.

In the user intention verification method, when the user intention information indicates that the target data is allowed to be acquired, the user intention verification response carries at least one of the following information:

and the first destination field information is used for indicating the permitted use destination of the target data which is permitted to be acquired by the user.

The first area identification information is used for indicating a use area allowed by the target data allowed to be acquired by a user;

in the user intention verification method, the user intention verification request carries at least one of the following information:

user equipment information for indicating the roaming user equipment;

In the user willingness verification method, the user willingness verification request carries at least one of the following information:

and the second area identification information is used for indicating an area where the target data requested to be acquired are located.

or alternatively

The user willingness verification method corresponds to the different scenes, and the user willingness information is specifically used for indicating:

allowing or rejecting the VPLMN or the network element in the VPLMN to acquire the target data in the VPLMN by the user;

or alternatively

Allowing or rejecting the VPLMN or the network element in the VPLMN to acquire the target data in the HPLMN by the user;

or alternatively

The user allows or denies the HPLMN or the network element in the HPLMN to acquire the target data in the VPLMN.

In the case where the authorization information indicates that the user is not allowed to acquire the target data, the user willingness verification response may further carry cause information indicating a reject cause in order to improve the accuracy of the indication.

The user wish verification method according to the embodiment of the present invention is further described in detail below in connection with different scenarios and specific data acquisition processes.

Fig. 4 is a schematic flow chart of a user willingness verification method according to an embodiment of the present application, where the schematic flow chart corresponds to a scenario in which a data consumer in a VPLMN requests target data in an HPLMN, and as shown in fig. 4, the flow chart includes:

In step 41, the data consumer in the VPLMN where the roaming UE (roaming user equipment) is located may be, for example, a 5GC Network Function (NF), an Application Function (AF), the UE itself, etc., send a first data acquisition request to a VPLMN interface network element (such as a data acquisition coordination function (DCCF) or NWDAF, NEF of the VPLMN) for triggering acquisition of related target data from the HPLMN of the UE.

Wherein the roaming UE may be a specific single UE roaming to the VPLMN; a group of UEs roaming to the VPLMN, or all UEs roaming to the VPLMN.

The target data may be data (raw data or processed intermediate data, such as slice information of the HPLMN where the UE is located, PDU session information, etc.) generated by the roaming UE in the HPLMN, or data analysis results (analysis, such as historical track statistics information of the UE in the HPLMN, and business behavior habit analysis of the UE).

The first data acquisition request message includes at least one of the following information:

roaming UE indication, which may be referred to as a roaming indication above, is used to indicate that the data acquisition request is for a roaming UE;

user equipment information for indicating the specific single UE; a set of UEs roaming to the VPLMN, or all UEs roaming to the VPLMN;

The HPLMN ID, which may be the description information of the data provider mentioned above, indicates the PLMN where the data provider of the target data is located;

HPLMN target area, which may be the second area identification information mentioned above, is used to indicate an area where the target data requested to be acquired is located. The corresponding data of the UE in the region indicated by HPLMN target area may be requested to be acquired through HPLMN target area;

time period, which may be the second target period information mentioned above, is used to indicate a period in which the target data requested to be acquired is located. The data corresponding to the UE in the Time period range indicated by the Time period can be requested to be acquired through the Time period;

a Data type/analysis ID, which may be the second target Data type information mentioned above, for indicating the type of the target Data requested to be acquired; for example, data type=ue location, or UPF ID corresponding to PDU session, analysis id=ue mobility or UE communication, etc.; the Data type/analysis ID can be used for requesting to acquire the Data of the UE, wherein the Data is the same as the type indicated by the Data type/analysis ID;

data reporting info, which may be descriptive information of the data report mentioned above, is used to indicate/agree on the time or format for feeding back the target data, etc. Feedback may be indicated by Data reporting info in accordance with the time or format indicated at Data reporting info when data is being fed back.

Step 41 described above is an optional step.

Step 42, after the interface network element in the vplmn receives the first data acquisition request, sending a second data acquisition request to the interface network element in the HPLMN, where the second data acquisition request includes, in addition to the information in the first data acquisition request, the following steps:

the ID of the VPLMN, the ID of the data consumer in the VPLMN, or the ID of the interface network element in the VPLMN may be used as the description information of the data consumer mentioned above, for indicating the PLMN where the data consumer of the target data is located, or for indicating the data consumer of the target data, or for indicating the interface network element of the PLMN where the data consumer of the target data is located.

Step 43, after receiving the second data acquisition request, the interface network element in the hplmn sends a user willingness verification request to the UDM/UDR (which may be used as the authorization management unit mentioned above), requesting the UDM to confirm and feed back the user willingness information;

the user authorization request message comprises at least one of the following contents:

A Data type/analysis ID, which may be the second target Data type information mentioned above, for indicating the type of the target Data requested to be acquired; for example, data type=ue location, or UPF ID corresponding to PDU session, analysis id=ue mobility or UE communication, etc.;

HPLMN target area, which may be the second area identification information mentioned above, is used to indicate the area where the target data requested to be acquired is located, and may be represented by TA and cell ID, and if indicated by geographic location description information HPLMN target area in step 42, it needs to be converted into a representation form of TA, cell ID, and the like, which represents network area information.

Time period, which may be the second target period information mentioned above, is used to indicate a period in which the target data requested to be acquired is located.

Step 44, the UDM/UDR in the HPLMN feeds back a user intention verification request response carrying user intention information to the HPLMN interface network element, where the user intention information indicates: whether the user allows the VPLMN or a network element in the VPLMN to acquire the target data; alternatively, the user intent information indicates: whether the user allows the VPLMN or a network element/device in the VPLMN to obtain the above-mentioned target data within the HPLMN.

The user willingness information indicates: in the case that the user is allowed to acquire the target data, the user willingness verification request response may further include:

the first purpose information is used for indicating the allowed use purpose of the target data which is allowed to be acquired by a user, for example, the first purpose information can be used for carrying out data statistics analysis by a VPLMN, further, the type of the data analysis can be indicated, and an analysis ID can be used for representing;

The user willingness information indicates: in the case where the user does not allow or refuse to acquire the target data described above, the user willingness verification request response may further include cause information for indicating a cause of the user disallowance, for example, the VPLMN is not in the user specified whitelist, etc.

Step 45, according to the user willingness information, the following operations are divided into two aspects: if the user willingness information contains permission indication information, namely the user is allowed to acquire the target data, the HPLMN interface network element receives a second data acquisition request from the VPLMN, otherwise, the HPLMN interface network element refuses the second data acquisition request;

step 46, under the condition that the user willingness information contains the permission indication information, the interface network element in the HPLMN acquires corresponding data;

in step 47, the interface network element in the hplmn sends a second data acquisition request response, when the user intention information indicates that: in the case where the user is allowed to acquire the target data, the second data acquisition request response includes the data acquired in step 46, and when the user intention information indicates: and if the user is not allowed to acquire the target data, the second data acquisition request is refused through the response of the second data acquisition request, wherein the request carries the reason information.

The VPLMN interface network element sends a first data acquisition request response to the data consumer in the VPLMN, step 48. The corresponding target data, or reject indication information and reject reason information may be carried according to different situations.

Fig. 5 is a schematic flow chart of a user willingness verification method in the second embodiment of the present application, where the schematic flow chart corresponds to a scenario in which a data consumer in the HPLMN requests target data in the VPLMN, and as shown in fig. 5, the flow chart includes:

in step 51, the data consumer in the HPLMN where the roaming UE (roaming user equipment) is located may be, for example, 5gc nf, af, UE itself, etc., and a third data acquisition request is sent to the HPLMN interface network element (such as DCCF or NWDAF, NEF, etc.) to trigger acquisition of the relevant target data from the VPLMN of the UE.

The target data may be data (original data or processed intermediate data, such as slice information of the HPLMN where the UE is located, PDU session information, etc.) generated by the roaming UE in the VPLMN, or data analysis results (analysis, such as historical track statistics information of the UE in the HPLMN, and business behavior habit analysis of the UE).

The third data acquisition request message includes at least one of the following information:

the VPLMN ID, which may be the description information of the data provider mentioned above, indicates the PLMN where the data provider of the target data is located;

VPLMN target area, which may be the second area identification information mentioned above, for indicating an area in which the target data requested to be acquired is located;

time period, which may be the second target period information mentioned above, is used to indicate a period in which the target data requested to be acquired is located;

data reporting info, which may be descriptive information of the data report mentioned above, is used to indicate/agree on the time or format for feeding back the target data, etc.

Step 51 described above is an optional step.

Step 52, after receiving the third data acquisition request, the interface network element in the hplmn sends a user willingness verification request to the UDM/UDR (which may be used as the authorization management unit mentioned above), requesting the UDM to confirm and feed back the user willingness information;

VPLMN target area, which may be the second area identification information mentioned above, is used to indicate the area where the target data requested to be acquired is located, and may be represented by TA and cell ID, and if indicated by geographic location description information HPLMN target area in step 42, it needs to be converted into a representation form of TA, cell ID, and the like, which represents network area information.

The HPLMN ID, the ID of the data consumer in the HPLMN, or the ID of the interface network element in the HPLMN may be used as the description information of the data consumer mentioned above, to indicate the PLMN where the data consumer of the target data is located, or to indicate the data consumer of the target data, or to indicate the interface network element of the PLMN where the data consumer of the target data is located.

Step 53, the UDM/UDR in the HPLMN feeds back a user intention verification request response carrying user intention information to the HPLMN interface network element, where the user intention information indicates: whether the user allows the HPLMN or a network element in the HPLMN to acquire the target data; alternatively, the user intent information indicates: whether the user allows the HPLMN or a network element/device in the HPLMN to obtain the above-mentioned target data within the VPLMN.

Step 54, according to the user willingness information, the following operations are divided into two aspects: if the user willingness information contains permission indication information, namely the user is allowed to acquire the target data, the HPLMN interface network element receives a third data acquisition request from the HPLMN, otherwise, the third data acquisition request is refused;

step 55-57, under the condition that the user willingness information contains the permission indication information, the interface network element in the HPLMN sends a fourth data acquisition request to the interface network element in the VPLMN, and after the data acquisition is completed by the interface network element in the VPLMN, the data of the response is returned through the response of the fourth data acquisition request;

At step 58, the HPLMN interface network element sends a third data acquisition request response to the data consumer in the HPLMN. The corresponding target data, or reject indication information and reject reason information may be carried according to different situations.

Fig. 6 is a schematic flow chart of a user willingness verification method in the third embodiment of the present application, where the schematic flow chart corresponds to a scenario in which a data consumer in the HPLMN requests target data in the VPLMN, and the difference between the flow chart and the flow chart shown in fig. 5 is that the user willingness verification is completed by an interface network element in the VPLMN.

As shown in fig. 6, the flow includes:

in step 61, the data consumer in the HPLMN where the roaming UE (roaming user equipment) is located may, for example, be 5gc nf, af, UE itself, etc., send a third data acquisition request to the HPLMN interface network element (such as DCCF or NWDAF, NEF, etc.) for triggering acquisition of related target data from the VPLMN of the UE.

Step 61 described above is an optional step.

Step 62, after the interface network element in the hplmn receives the third data acquisition request, the interface network element in the hplmn sends a fourth data acquisition request to the interface network element in the VPLMN, where the second data acquisition request includes, in addition to the information in the third data acquisition request, the information further includes:

the ID of the HPLMN, the ID of the data consumer in the HPLMN, or the ID of the interface network element in the HPLMN may be used as the description information of the data consumer mentioned above, to indicate the PLMN where the data consumer of the target data is located, or to indicate the data consumer of the target data, or to indicate the interface network element of the PLMN where the data consumer of the target data is located.

Step 63, after receiving the second data acquisition request, the interface network element in the vplmn sends a user willingness verification request to the UDM/UDR (which may be used as the authorization management unit mentioned above), requesting the UDM to confirm and feed back the user willingness information;

VPLMN target area, which may be the second area identification information mentioned above, is used to indicate the area where the target data requested to be acquired is located, and may be represented by TA, cell ID, and if indicated by geographical location description information HPLMN target area in step 62, it needs to be converted into a representation form of TA, cell ID, etc. representing network area information.

Step 64, the UDM/UDR in the hplmn feeds back a user intention verification request response carrying user intention information to the VPLMN interface network element, where the user intention information indicates: whether the user allows the HPLMN or a network element in the HPLMN to acquire the target data; alternatively, the user intent information indicates: whether the user allows the HPLMN or a network element/device in the HPLMN to obtain the above-mentioned target data within the VPLMN.

first purpose information, which is used for indicating the allowed use purpose of the target data allowed to be acquired by a user, for example, the first purpose information can be used for carrying out data statistics analysis by an HPLMN, further, the type of data analysis can be indicated, and an analysis ID can be used for representing the data analysis;

The user willingness information indicates: in the case where the user does not permit or refuse to acquire the target data described above, the user intention verification request response may further include cause information for indicating a cause of the user's disallowance, for example, the HPLMN is not in the user-specified whitelist, or the like.

Step 65, according to the user willingness information, the following operations are divided into two aspects: if the user willingness information contains permission indication information, namely the user is allowed to acquire the target data, the VPLMN interface network element receives a fourth data acquisition request from the HPLMN, otherwise, the fourth data acquisition request is refused;

step 66, under the condition that the user willingness information contains the permission indication information, the interface network element in the VPLMN acquires corresponding data;

step 67, the interface network element in the vplmn sends a fourth data acquisition request response, when the user intention information indicates: in the case where the user is allowed to acquire the target data, the second data acquisition request response includes the data acquired in step 66, and when the user intention information indicates that: and if the user does not allow the target data to be acquired, refusing the fourth data acquisition request through the fourth data acquisition request response, wherein the fourth data acquisition request carries the reason information.

The HPLMN interface network element sends a third data acquisition request response to the data consumer in the HPLMN, step 68. The corresponding target data, or reject indication information and reject reason information may be carried according to different situations.

Fig. 7 is a flowchart of a user willingness verification method according to a fourth embodiment of the present application, where the flowchart corresponds to a scenario in which a data consumer in the VPLMN requests target data in the VPLMN.

As shown in fig. 7, the flow includes:

in step 71, the data consumer in the VPLMN where the roaming UE (roaming user equipment) is located may, for example, be 5gc nf, af, UE itself, etc., send a fifth data acquisition request to the VPLMN interface network element (such as DCCF or NWDAF, NEF, etc.) for triggering acquisition of related target data from the VPLMN of the UE.

Step 71 described above is an optional step.

Step 72, after the interface network element in the vplmn receives the fifth data acquisition request, confirming the HPLMN interface network element or UDM corresponding to the roaming UE;

the following is a further detailed description of the direct discovery UDM as an example, and if the HPLMN is discovered, the relevant user willingness confirmation procedure is similar to that of fig. 4, and will not be further detailed here.

Step 73, the interface network element in the vplmn sends a user intention verification request to the UDM/UDR (which can be used as the authorization management unit mentioned above), requests the UDM to confirm and feed back user intention information;

Step 74, the UDM/UDR in the hplmn feeds back a user intention verification request response carrying user intention information to the VPLMN interface network element, where the user intention information indicates: whether the user allows the VPLMN or a network element in the VPLMN to acquire the target data; alternatively, the user intent information indicates: whether the user allows the VPLMN or a network element/device in the VPLMN to obtain the above-mentioned target data within the VPLMN.

Step 75, according to the user willingness information, the following operations are divided into two aspects: if the user willingness information contains permission indication information, namely the user is allowed to acquire the target data, the VPLMN interface network element receives a fifth data acquisition request from a VPLMN consumer, otherwise, the fifth data acquisition request is refused;

Step 76, in case that the user willingness information contains the permission indication information, the interface network element in the VPLMN obtains the corresponding data;

step 77, the interface network element in the vplmn sends a fifth data acquisition request response, when the user intention information indicates: in the case where the user is allowed to acquire the target data, the second data acquisition request response includes the acquisition of the data in step 76, and when the user intention information indicates: and if the user does not allow the target data to be acquired, refusing the fourth data acquisition request through the fourth data acquisition request response, wherein the fourth data acquisition request carries the reason information.

As shown in fig. 8, a user intention verification apparatus according to an embodiment of the present invention includes:

the first receiving module 81 is configured to receive a data acquisition request, where the data acquisition request is used to request acquisition of target data, and the target data is: data corresponding to a roaming user equipment in a home public land mobile network HPLMN or a visiting public land mobile network VPLMN and/or data analysis results of the roaming user equipment generated by the HPLMN or the VPLMN;

a first sending module 82, configured to send a user willingness verification request to an authorization management unit in the HPLMN, where the user willingness verification request is used to request for user willingness confirmation on the data acquisition request;

The first receiving module 81 is further configured to receive a user intention verification response carrying the user intention information sent by the authorization management unit; the user willingness information is used for indicating: whether the user is allowed to acquire the target data.

Wherein, in a case where the user intent information indicates that the user is allowed to acquire the target data, the user intent verification response carries at least one of the following information:

Wherein the user intent verification request carries at least one of the following information:

User equipment information for indicating the roaming user equipment;

Wherein, its characterized in that:

or alternatively

Or alternatively

The user willingness information is specifically used for indicating:

allowing or rejecting the VPLMN or the network element in the VPLMN to acquire the target data by the user;

or alternatively

Wherein the first network element is an interface network element in a first PLMN.

After receiving the user intention verification response carrying the user intention information sent by the authorization management unit, the first network element further includes:

or alternatively

And under the condition that the authorization information indicates that the user does not allow the target data to be acquired, the user willingness verification response also carries reason information indicating a reject reason.

As shown in fig. 9, a user intention verification apparatus according to an embodiment of the present invention includes:

a second receiving module 91, configured to receive a user intention verification request, where the user intention verification request is used to request to perform user intention confirmation on the data acquisition request; the data acquisition request is used for requesting to acquire target data, and the target data is: data corresponding to a roaming user equipment in a home public land mobile network HPLMN or a visiting public land mobile network VPLMN and/or data analysis results of the roaming user equipment generated by the HPLMN or the VPLMN;

a second sending module 92, configured to send a user intention verification response carrying the user intention information; the user willingness information is used for indicating: whether the user is allowed to acquire the target data.

Wherein, in a case where the user intent information indicates that the target data is allowed to be acquired, the user intent verification response carries at least one of the following information:

user equipment information for indicating the roaming user equipment;

Wherein,

or alternatively

The user willingness information is specifically used for indicating:

or alternatively

As shown in fig. 10, the embodiment of the present application further provides a first network side device 100, which includes a first processor 101 and a first memory 102, where a program or an instruction that can be executed on the first processor 101 is stored in the first memory 102, and the program or the instruction implements each step of the foregoing embodiment of the user wish verification method when executed by the first processor 101, and the steps can achieve the same technical effect, so that repetition is avoided, and no further description is given here.

Specifically, the embodiment of the application further provides the second network side device 110. As shown in fig. 11, the second network side device 110 includes: a second processor 111, a network interface 112 and a second memory 113. The network interface 112 is, for example, a common public radio interface (common public radio interface, CPRI), and the network interface 112 is used to implement a transmitting or receiving operation.

Specifically, the second network side device 110 in the embodiment of the present application further includes: the instructions or programs stored in the second memory 113 and capable of being executed on the second processor 111, the second processor 111 invokes the instructions or programs in the second memory 153 to execute the methods executed by the modules shown in fig. 8 and 9, and achieve the same technical effects, so that repetition is avoided and thus a description thereof is omitted.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the processes of the embodiment of the user wish verification method are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running a program or an instruction, implementing each process of the user wish verification method embodiment, and achieving the same technical effect, so as to avoid repetition, and no redundant description is provided herein.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product, where the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement each process of the foregoing embodiment of the user wish verification method, and the same technical effects can be achieved, so that repetition is avoided, and details are not repeated herein.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A method for verifying user intent, comprising:

2. The user intent verification method of claim 1, wherein the user intent verification response carries at least one of the following information in a case where the user intent information indicates that a user is allowed to acquire the target data:

3. The user intent verification method of claim 1, wherein the user intent verification request carries at least one of:

user equipment information for indicating the roaming user equipment;

4. The user intent verification method of claim 2, wherein the user intent verification request carries at least one of the following information:

5. The user intent verification method of claim 1, wherein:

or alternatively

6. The user intent verification method of claim 1, wherein the user intent information is specifically used for indicating:

or alternatively

7. The user intent verification method of claim 1, wherein the first network element is an interface network element in a first PLMN.

8. The method for verifying user intention as in claim 7, wherein after the first network element receives the user intention verification response carrying the user intention information sent by the authorization management unit, the method further comprises:

or alternatively

9. The user intent verification method according to claim 1, wherein in case the authorization information indicates that the user is not allowed to acquire the target data, the user intent verification response further carries cause information indicating a reject cause.

10. A method for verifying user intent, comprising:

11. The user intent verification method of claim 10, wherein the user intent verification response carries at least one of the following information in a case where the user intent information indicates that the target data is allowed to be acquired:

First destination field information for indicating a use destination permitted by the target data which the user is permitted to acquire;

12. The user intent verification method of claim 10, wherein the user intent verification request carries at least one of:

user equipment information for indicating the roaming user equipment;

13. The user intent verification method of claim 11, wherein the user intent verification request carries at least one of:

14. The user intent verification method as recited in claim 10, wherein:

or alternatively

15. The user intent verification method of claim 10, wherein the user intent information is specifically used for indicating:

or alternatively

16. The user intent verification method of claim 10, wherein the user intent verification response further carries cause information indicating a reject cause in case the authorization information indicates that the user is not allowed to acquire the target data.

17. A user intent verification apparatus, comprising:

18. A user intent verification apparatus, comprising:

19. A network side device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the user intent verification method as claimed in any one of claims 1 to 9; alternatively, the program or instructions, when executed by the processor, implement the steps of a user intent verification method as claimed in any one of claims 10 to 16.

20. A readable storage medium having stored thereon a program or instructions which when executed by a processor performs the steps of the user intent verification method as claimed in any one of claims 1 to 9; alternatively, the program or instructions, when executed by the processor, implement the steps of a user intent verification method as claimed in any one of claims 10 to 16.