Parameter updating method and device

Abstract

The invention relates to a parameter updating method and device, a computer readable storage medium, a computer program product and a computer program. The method comprises the following steps: the terminal equipment sends first information, wherein the first information is used for indicating to update one or more user agreement parameters of the terminal equipment;

Description

Parameter updating method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a parameter updating method, device, computer-readable storage medium, computer program product, and computer program. Background Art

[0002] In related technologies, a growing number of third-party service providers are signing service-level agreements with operators, using the 5G Core (5GC) to provide auxiliary information to improve service quality. In particular, for services targeting terminal devices, the auxiliary information provided by the 5GC may involve user data or private data (depending on local laws and regulations), requiring user consent. This user consent, or the configuration of user consent parameters, falls under the operator's internal system management. However, finding a way to update the user consent parameters stored on the network side for terminal devices while ensuring the security of the terminal device's private data has become a challenge.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide a parameter updating method, device, computer-readable storage medium, computer program product, and computer program.

[0005] The present invention provides a parameter updating method, including:

[0006] The terminal device sends first information, where the first information is used to indicate updating of one or more user consent parameters of the terminal device.

[0007] The present invention provides a parameter updating method, including:

[0008] The first network device receives first information, where the first information is used to indicate updating of one or more user consent parameters of the terminal device.

[0009] The present invention provides a parameter updating method, including:

[0010] The second network device receives the second information sent by the first network device, where the second information is used by the second network device to update one or more user consent parameters of the terminal device.

[0011] An embodiment of the present application provides a terminal device, including:

[0012] The first communication unit is used to send first information, where the first information is used to indicate updating of one or more user consent parameters of the terminal device.

[0013] An embodiment of the present application provides a first network device, including:

[0014] The second communication unit is configured to receive first information, where the first information is used to indicate updating of one or more user consent parameters of the terminal device.

[0015] An embodiment of the present application provides a second network device, including:

[0016] The third communication unit is used to receive second information sent by the first network device, where the second information is used by the second network device to update one or more user consent parameters of the terminal device.

[0017] An embodiment of the present application provides a terminal device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above method.

[0018] An embodiment of the present application provides a first network device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the first network device executes the above method.

[0019] An embodiment of the present application provides a second network device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the second network device executes the above method.

[0020] The embodiment of the present application provides a chip for implementing the above method.

[0021] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method.

[0022] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a device to perform the above method when the computer program is executed by the device.

[0023] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above method.

[0024] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method.

[0025] By adopting the solution provided in this embodiment, the terminal device can send the first information to instruct the network to update the user consent parameters of the terminal device. Thus, by introducing the terminal device triggering the update of the user consent parameters, the network-side user consent parameter update of the terminal device can be controlled by the terminal device, thereby addressing the shortcomings of related technologies and preventing third-party application functions from abusing the private data of the terminal device, thereby ensuring the security of the private data of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0027] FIG2 is a schematic flowchart of a parameter updating method according to an embodiment of the present application.

[0028] FIG3 is a schematic flowchart of a parameter updating method according to another embodiment of the present application.

[0029] FIG4 is an exemplary flowchart of a parameter updating method according to another embodiment of the present application.

[0030] FIG5 is a schematic diagram of a composition architecture for adding a UCCF to a network according to an embodiment of the present application.

[0031] FIG6 is a schematic diagram of a composition architecture for adding a UCCF in a VPLMN and a HPLMN according to an embodiment of the present application.

[0032] 7 to 11 are various exemplary flow charts of parameter updating methods according to embodiments of the present application.

[0033] FIG12 is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0034] FIG13 is a schematic block diagram of a first network device according to an embodiment of the present application.

[0035] FIG14 is a schematic block diagram of a first network device according to another embodiment of the present application.

[0036] FIG15 is a schematic block diagram of a second network device according to an embodiment of the present application.

[0037] FIG16 is a schematic block diagram of a second network device according to another embodiment of the present application.

[0038] FIG17 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0039] FIG18 is a schematic block diagram of a chip according to an embodiment of the present application.

[0040] FIG19 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0041] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0042] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0043] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0044] In one possible implementation, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0045] In one possible implementation, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0046] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0047] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0048] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0049] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0050] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0051] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0052] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0053] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0054] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one possible implementation, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0055] In one possible implementation, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0056] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0057] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0058] To facilitate understanding of the embodiments of the present application, the following briefly describes the basic processes and basic concepts involved in the embodiments of the present application. It should be understood that the basic processes and basic concepts introduced below do not limit the embodiments of the present application.

[0059] Basic concepts of user consent:

[0060] 1. Scope: Depending on local regulations, 3GPP (3rd Generation Partnership Project) features may require user consent. User consent requirements and mechanisms only apply where required by regional regulations or local operator policies. Otherwise, they do not apply.

[0061] 2. Relationship between End-User and Subscriber: User consent is assumed to be obtained from the end-user. The end-user is either the subscriber themselves, or they authorize the subscriber to provide consent on the end-user's behalf. Alternatively, the end-user is authorized by the subscriber to provide consent. This means that user consent is always associated with the subscription information.

[0062] 3. Requirements: The UDM (Unified Data Management) should support the following services related to user consent: retrieval of user consent parameters; notification of changes to user consent parameters; user consent parameters should be stored as subscription data in the UDM / UDR (Unified Data Repository); user consent parameters should be tied to the SUPI (Subscription Permanent Identifier) / GPSI (Generic Public Subscription Identifier); user consent parameters should be tied to the data processing purpose; user consent parameters should include whether user consent has been granted; user consent is only effective after the point in time when user consent is given; user consent remains valid until it is revoked, which means that user consent parameters stored in subscription data do not have an expiration / validity timer. Note: The UDM does not provide a user consent revocation service; it only provides notification of changes to user consent parameters.

[0063] 4. User Consent Check: Any Network Function (NF) deemed as a user consent enforcement point should support retrieving user consent parameters from the UDM. Any NF deemed as a user consent enforcement point shall not accept any service or data processing request unless user consent is obtained. Any NF deemed as a user consent enforcement point shall determine the data processing purpose before data processing. If the data processing purpose is not implicitly known from the service request, the user consent enforcement point shall request or otherwise refuse the service. NFs that obtain or check user consent parameters shall consider the user consent parameters to be valid until they are revoked.

[0064] 5. User Consent Revocation: Any NF that is considered as a user consent enforcement point should support subscribing to the user consent parameter change notifications provided by the UDM. Consumer NFs (processing data related to user consent) should subscribe to the UDM to obtain user consent parameter change notifications, unless the consent enforcement NF that is considered as an enforcement point is tracking these NFs and proactively notifying these consumer NFs when a user consent is revoked.

[0065] Note: When authorizing consumer NFs to process data based on user consent, care should be taken not to authorize requests for necessary services or related parameters that do not support revocation. This is important because user consent may change in the future.

[0066] Upon receipt of a notice of revocation of user consent, any NF deemed to be the point of enforcement of user consent will no longer accept any requests for data processing services for the data subject whose consent has been revoked. Upon receipt of a notice of revocation of user consent, any NF deemed to be the point of enforcement of user consent may notify other NFs to cease processing the data subject whose consent has been revoked. Upon notification of revocation of user consent, the NF (processing data related to the revoked consent) shall cease processing and collecting data. Upon receipt of a notice of revocation of user consent, the NF may delete, isolate, or temporarily retain data related to the revoked user consent in accordance with local policies and legal restrictions.

[0067] Users who expose their information to application functions (AF) agree to:

[0068] When the AF requests auxiliary information from the 5G Core (5GC), if the requested data involves user information or privacy information (such as address) of a specific UE, user consent is required. In the R17 user consent research, "User's consent for exposure of information to Edge Applications" was used as a use case. In fact, this application can be extended to AFs for other services, such as Artificial Intelligence (AI) / Machine Learning (ML) AFs. For this type of use case, the Network Exposure Function (NEF) serves as the execution point for user consent, and the role of the execution point is as described above.

[0069] Centralized authorization to process user consent:

[0070] Whenever the NF / AF wants to retrieve data related to one or more UEs, it provides the list of UEs for which user consent is required in an authorization request to the User Consent Authorize Network Function (UCA NF). The UCA NF contacts the UDM / UDR to obtain which UEs provided user consent and which did not. This information can be reused by the UCA NF for other requests.

[0071] The UCA NF creates an authorization token that includes a list of allowed UE identities. This token is created in addition to the OAuth2.0 token that the NF needs to request from the Network Repository Function (NRF). The UCA NF sends the authorization token associated with the user consent in a signed response, which includes a list of UEs that have authorized data collection. Using this token and the OAuth2.0 token used for the authorization service, the NF / AF requests data about the UE from the data provisioning NFp. The NFp can verify both tokens before providing any data.

[0072] The UCA NF has a history of NFs / AFs that collected UE consent. This allows centralized sending of update or revocation notifications to those NFs that previously requested UE consent. To keep track, the UCA needs to subscribe to notifications from the UDM after collecting user consent for the relevant UE, or check itself periodically to maintain an up-to-date list.

[0073] Storage of user consent:

[0074] User consent parameters are stored in the UDM in the form of UE subscription data, as shown in Table 1 below:

[0075]

[0076] Table 1

[0077] In the related art, user consent is stored in the UDM as subscription data, and its configuration falls within the scope of the operator's internal system management. There is a lack of a mechanism for updating user consent triggered by the terminal device. The UE cannot revoke user consent in a timely manner and prevent the NF or third-party AF within the 5GC from obtaining the UE's privacy data; in particular, after the AF obtains the UE's specific data (such as the UE's location information, network performance analysis), if the UE's permissions change (for example, the edge computing client EAC or AI / ML client is uninstalled on the mobile device), due to the lack of a mechanism for the UE to trigger the user consent update, the AF can still use the previous UE ID to obtain the UE's relevant data from the 5GC. Therefore, how to trigger and update the UE's user consent parameters stored on the network side by the UE side so that the update of the UE's user consent parameters stored on the network side is synchronized with the UE's status change, thereby ensuring the security of the UE's privacy data, becomes a problem that needs to be solved.

[0078] In addition, in the related art, the research on user consent considers different execution points for different use cases. Such a design may be difficult to deploy or require continuous research on the processing situations under different use cases. Therefore, a solution idea of ​​centralized authorization of user consent is generated, but this solution is relatively simple and still needs to consider details. For example, in the user consent of R17, since the execution points are related to specific businesses, the execution points can understand the data processing purpose stored in the user consent parameters (for example, the network data analysis function (NWDAF, Network Data Analytics Function) can understand the collection and analysis of data). However, the centralized user consent authorization network element may not understand the processing method and processing granularity of the relevant data, and there may be a problem of excessive authorization scope. Therefore, how to deploy network elements on the network side that can understand the centralized management of user consent parameters, and how to update the user consent parameters of the same terminal device with a larger granularity, are also problems that need to be solved.

[0079] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0080] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0081] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0082] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0083] FIG2 is a schematic flow chart of a parameter updating method according to an embodiment of the present application. The method includes at least part of the following contents.

[0084] S210. The terminal device sends first information, where the first information is used to indicate an update of one or more user consent parameters of the terminal device.

[0085] FIG3 is a schematic flow chart of a parameter updating method according to another embodiment of the present application. The method includes at least part of the following contents.

[0086] S310. A first network device receives first information, where the first information is used to indicate updating one or more user consent parameters of a terminal device.

[0087] FIG4 is a schematic flow chart of a parameter updating method according to another embodiment of the present application. The method includes at least part of the following contents.

[0088] S410. The second network device receives second information sent by the first network device, where the second information is used by the second network device to update one or more user consent parameters of the terminal device.

[0089] In some possible implementations, the first information is used to instruct updating of one or more user consent parameters of the terminal device at a target granularity.

[0090] The first information includes: identification information of the terminal device, relevant information at the target granularity, and update operation type; wherein, the relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; the update operation type includes one of the following: deletion, addition, and modification.

[0091] The identification information of the terminal device can be expressed as a UE ID, and specifically can include at least one of the following: SUCI (Subscription concealed identifier), GPSI (Generic Public Subscription Identifier), and SUPI (SUbscription Permanent Identifier).

[0092] The update operation type can be represented by an indicator value, for example, when the indicator value is a first value, it is used to indicate that the update operation type is delete, when the indicator value is a second value, it is used to indicate that the update operation type is add, and when the indicator value is a third value, it is used to indicate that the update operation type is modify; wherein the first value, the second value, and the third value are all different, for example, the first value can be 00, the second value can be 01, and the third value can be 11, or the first value can be 11, the second value can be 10, and the third value can be 01, etc. As long as the first value, the second value, and the third value are all different, they are within the scope of protection of this embodiment. Alternatively, the update operation type can be directly represented by specific description information, for example, "Delete" or "Cancel" can be used to indicate that the update operation type is delete, "Add" can be used to indicate that the update operation type is add, and "Modify" can be used to indicate that the update operation type is modify; for example, the update operation type of delete can also be represented by "del", the update operation type can also be represented by "addition", and the update operation type of modify can also be represented by "adjust" or "adj", etc. It should be understood that the above is merely an exemplary description of several possible ways of updating the operation type, and does not exhaustively list all possible ways of expressing the update operation type.

[0093] The target granularity includes at least one of the following: AF, AF type, data type, and data processing purpose. The relevant information at the target granularity includes at least one of the following: the identifier of each target AF in one or more target AFs; one or more target AF types; one or more target data types; and one or more target data processing purposes.

[0094] Possible situations regarding the relevant information at the target granularity included in the first information are related to the update operation type.

[0095] Optionally, when the update operation type is deletion, the relevant information at the target granularity may only need to include the following parts: the identifier of each target AF in one or more target AFs, one or more target AF types, one or more target data types, and one or more target data processing purposes. This is because all user consent parameters of the terminal device are usually saved on the network side. Therefore, if the terminal device wants to delete one or more common user consent parameters in batches, it can directly use the characteristics that can represent the commonality of the user consent parameters as the relevant information at the target granularity, so that the network side can determine all user consent parameters to be deleted by the terminal device. For example, if the terminal device wants to delete all user consent parameters corresponding to a certain target AF in batches, the relevant information at the target granularity may only include the identifier of the target AF; for another example, if the terminal device wants to delete all user consent parameters of a certain target data processing purpose under a certain target AF in batches, the relevant information at the target granularity may only include the identifier of the target AF and the target data processing purpose.

[0096] Alternatively, in the case where the update operation type is deletion, the relevant information at the target granularity may also include all of the identifier of each target AF in one or more target AFs, one or more target AF types, one or more target data types, and one or more target data processing purposes. In the case where the relevant information at the target granularity includes all of the above contents, it can be specifically used to indicate one or more user consent parameters corresponding to the identifier of each target AF, or one or more user consent parameters corresponding to each target AF type, or user consent parameters corresponding to each target data type in one or more target data types, or one or more user consent parameters corresponding to each target data processing purpose in one or more target data processing purposes. This is because the terminal device may not need to delete all user consent parameters of a certain category with common characteristics. In this case, the terminal device can further indicate the specific content of one or more user consent parameters to be deleted this time.

[0097] In some possible examples, if the terminal device uninstalls the client corresponding to each of one or more target AFs, the terminal device may instruct to delete all user consent parameters for each target AF at once. In this case, the target granularity may be AF. The first information includes: identification information of the terminal device, identification of each of the one or more target AFs, and update operation type of deletion.

[0098] For example, the identification information of the terminal device is UE ID1 (the UE ID1 can be at least one of SUCI, GPSI, and SUPI), and the terminal device has uninstalled EAC (Edge Application Client) and AIML Client. Assuming that the identification of the AF corresponding to EAC is AF01 and the identification of the AF corresponding to the AIML client is AF02, the aforementioned first information can be as shown in Table 2, including: the identification information of the terminal device is UE ID1, the identification of the target AF is AF01 and AF02, and the update operation type is deletion.

[0099] Terminal equipment identification information target AF identification update operation type UE ID1AF01, AF02 deletion

[0100] Table 2

[0101] In some possible examples, the terminal device may not uninstall the client of one or more AFs, but the user of the terminal device decides to revoke at least some user consent parameters of one or more AFs.

[0102] If you need to delete all user consent parameters for the target data processing purpose corresponding to each target AF in one or more target AFs, you can use the AF and data processing purpose as the target granularity. The first information may include: the identification information of the terminal device, the identification of each target AF in the one or more target AFs, the one or more target data processing purposes, and the update operation type of deletion. Here, the one or more target data processing purposes can be the one or more target data processing purposes corresponding to the identification of each target AF.

[0103] If a terminal device deletes all user consent parameters under a target data type corresponding to each of one or more target AFs, the AF and data type can be used as the target granularity; the first information may include: identification information of the terminal device, the identification of each of the one or more target AFs, one or more target data types, and the update operation type being deletion. Here, the one or more target data types may be the one or more target data types corresponding to the identification of each target AF.

[0104] In some possible examples, if the terminal device uninstalls all clients under the target AF type, the terminal device can instruct to delete all user consent parameters under the target AF type at one time. In this case, the target granularity is AF type. The first information includes: identification information of the terminal device, one or more target AF types, and the update operation type is deletion. For example, the identification information of the terminal device is UE ID1, and the terminal device uninstalls all clients under the AF type of type A1. The aforementioned first information can be as shown in Table 3, including: the identification information of the terminal device is UE ID1, the target AF type is AF type A1, and the update operation type is deletion.

[0105] Terminal equipment identification information Target AF type Update Operation type UE ID1 AF type A1 Delete

[0106] Table 3

[0107] In some possible examples, the terminal device may not uninstall the client of one or more AF types, but the user of the terminal device decides to revoke at least part of the user consent parameters of one or more AF types.

[0108] If you need to delete all user consent parameters for the target data processing purpose corresponding to each of one or more target AF types, you can use the AF type and data processing purpose as the target granularity. The first information may include: the terminal device's identification information, one or more target AF types, one or more target data processing purposes, and the update operation type of deletion. Here, the one or more target data processing purposes can be the one or more target data processing purposes corresponding to the identification of each target AF.

[0109] If a terminal device deletes all user consent parameters under the target data type corresponding to each of one or more target AF types, the AF type and data type can be used as the target granularity; the first information may include: identification information of the terminal device, one or more target AF types, one or more target data types, and the update operation type is deletion. Here, the one or more target data types can be the one or more target data types corresponding to the identification of each target AF.

[0110] In some possible examples, if a terminal device disables the permission for a certain function, the terminal device may instruct the deletion of all user consent parameters for the data type and / or data processing purpose using the function. Specifically, the first information includes: identification information of the terminal device, one or more target data types, one or more target data processing purposes, and the update operation type is deletion. Alternatively, the first information may include: identification information of the terminal device, one or more target data processing purposes, and the update operation type is deletion.

[0111] For example, the identification information of the terminal device is UE ID1, and the terminal device has turned off the permission of the positioning function. The data type related to the positioning function that needs to be deleted this time is the user consent parameter corresponding to the terminal device positioning. The aforementioned first information may include: the identification information of the terminal device is UE ID1, the target data type is terminal device positioning (Location), and the update operation type is deletion; that is, the first information is used to indicate the deletion of all user consent parameters whose target data type is terminal device positioning. For example, all user consent parameters may include: user consent parameters whose data type is terminal device positioning and whose data processing purpose is collection, and user consent parameters whose data type is terminal device positioning and whose data processing purpose is analysis.

[0112] Optionally, when the update operation type is add or modify, the relevant information at the target granularity needs to include all of the following: the identifier of each target AF in one or more target AFs, one or more target AF types, one or more target data types, and one or more target data processing purposes. This is because, when the terminal device needs to add or modify one or more user consent parameters, the specific content of the one or more user consent parameters needs to be clearly reflected in the first information, so that the network side can determine the specific content of the user consent parameters to be added or modified by the terminal device.

[0113] In some possible examples, if a terminal device has installed a client corresponding to each of one or more target AFs, the terminal device may instruct to add one or more user consent parameters for each target AF at a time. In this case, the target granularity may be AF. The first information may specifically include: identification information of the terminal device, identification of each of the one or more target AFs, one or more user consent parameters corresponding to the identification of each target AF, and the update operation type being add.

[0114] For example, the identification information of the terminal device is UE ID1, and the terminal device has installed the client of the target AF (for example, AF03). The terminal device can add one or more user consent parameters under the target AF at one time. For example, the first information can be as shown in Table 4, including: the identification information UE ID1 of the terminal device, the identification AF03 of the target AF, the data processing purpose of the user consent parameter 1 is collection, the data type is location information, the data processing purpose of the user consent parameter 2 is analysis, the data type is the wireless connection performance of the terminal device, and the update operation type is addition.

[0115]

[0116] Table 4

[0117] If the terminal device does not uninstall the existing AF client or install a new client, but the terminal device wants to instruct to add or modify one or more target data processing purposes or one or more user consent parameters under one or more target data types under each existing target AF at one time. For example, the first information may specifically include: identification information of the terminal device, identification of each target AF in the one or more target AFs, one or more target data processing purposes, one or more target data types, and the update operation type is add (or modify).

[0118] In some possible examples, if the terminal device has installed an additional client under the target AF type, the terminal device can indicate at one time to add user consent parameters under the target AF type. For example, the identification information of the terminal device is UE ID1, and the terminal device has installed a client with the target AF type of A2. The terminal device can add multiple user consent parameters under the target AF type at one time. The first information can be as shown in Table 5, including: the identification information of the terminal device UE ID1, the target AF type A2, the data processing purpose collection and data type location information of the user consent parameter 3, the data processing purpose analysis and data type terminal device status of the user consent parameter 4 (the terminal device status can be at least one of the terminal device mobility analysis, terminal device abnormal behavior, terminal device wireless connection performance, etc.), and the update operation type is addition. The above is only an exemplary description. In actual processing, the terminal device may also add other user consent parameters under the target AF type, such as the data processing purpose is collection and / or analysis, the data type is a candidate UE list (i.e., a group of UE identifiers). This user consent parameter can be a user consent parameter for selecting a group of UEs for federated learning in an AIML service (such as the AF corresponding to AIML). All possible user consent parameters are not exhaustively listed here.

[0119]

[0120]

[0121] Table 5

[0122] If the terminal device has installed the client corresponding to the target AF type, the terminal device can simultaneously indicate the addition of one or more user consent parameters for one or more target data processing purposes of the target AF type. The first information may specifically include: identification information of the terminal device, one or more target AF types, one or more target data processing purposes, one or more data types, and the update operation type being "add".

[0123] If the existing AF type client is not uninstalled and no new client is installed, the terminal device needs to instruct to add or modify one or more target data processing items under each existing target AF type or one or more user consent parameters under one or more target data types at one time.

[0124] In some possible examples, if a terminal device has enabled permission for a certain function, the terminal device may indicate the addition of one or more user consent parameters for the data type and / or data processing purpose for using the function. For example, the first information includes: identification information of the terminal device, one or more target data types, one or more target data processing purposes, and the update operation type is addition.

[0125] It should be understood that the above is only an exemplary description of the first information and related information at the target granularity. In actual processing, it is not limited to the situations provided in the above examples, but is not enumerated here.

[0126] In some possible implementations, the terminal device sending the first information includes: the terminal device sending the first information to a first network device.

[0127] The first information is carried by one of the following: non-access stratum (NAS) signaling and uplink data of the user plane.

[0128] Optionally, the first information is carried by NAS signaling. In this scenario, the terminal device sending the first information to the first network device may include: the terminal device sending the first information to the first network device through a radio access network (RAN) device and a fifth network device. The fifth network device may be an AMF (Access and Mobility Management Function).

[0129] Specifically, the terminal device sends the first information to the first network device through the RAN device and the fifth network device, which may include: the terminal device sends the first information to the fifth network device through the RAN device, the first information is carried by NAS signaling, and the NAS signaling is signaling based on NAS security context encryption and integrity protection; the fifth network device sends the first information to the first network device.

[0130] It should also be noted that in one case, the first network device may be one of multiple candidate network devices that store user data; in this case, the fifth network device sending the first information to the first network device may include: the fifth network device searches for a candidate network device that stores the user data of the terminal device from multiple candidate network devices based on the identification information of the terminal device (such as the UE ID), and uses the candidate network device as the aforementioned first network device to send the first information to the first network device. In another case, the first network device may be a network element that stores the user data of all user devices on the network side. In this case, the fifth network device may directly send the first information to the first network device.

[0131] Optionally, the first information is carried by uplink data of the user plane. In this scenario, the terminal device sending the first information to the first network device may include: the terminal device sending the first information to the first network device through the RAN device and a sixth network device. The sixth network device may be an SMF (Session Management Function).

[0132] Specifically, the terminal device sends the first information to the first network device through the RAN device and the sixth network device, which may include: the terminal device sends the first information to the sixth network device through the RAN device, where the first information is carried by the uplink data of the user plane, and the uplink data of the user plane is data encrypted and integrity protected based on the UP (uplink) security context; the sixth network device sends the first information to the first network device.

[0133] It should also be noted that in one scenario, the first network device may be one of multiple candidate network devices that store user data; in this case, the sixth network device sending the first information to the first network device may include: the sixth network device searches for a candidate network device that stores the user data of the terminal device from multiple candidate network devices based on the identification information of the terminal device (such as the UE ID), and uses the candidate network device as the aforementioned first network device to send the first information to the first network device. In another scenario, the first network device may be a network element that stores the user data of all user devices on the network side. In this case, the sixth network device may directly send the first information to the first network device.

[0134] In some possible implementations, the first information further includes: a confirmation request; after the terminal device sends the first information, the method further includes: the terminal device receives a confirmation response to the first information; the confirmation response to the first information is used to confirm the completion of updating one or more user consent parameters of the terminal device.

[0135] Correspondingly, after the first network device updates one or more user consent parameters of the terminal device based on the first information, the method also includes: the first network device sends a confirmation response of the first information to the terminal device; the confirmation response of the first information is used to confirm the completion of updating one or more user consent parameters of the terminal device.

[0136] That is, the confirmation request is used to indicate that a confirmation response to the first information is fed back upon completing the update of one or more user consent parameters of the terminal device; the confirmation request can be expressed as an ack request. It should be noted that the first information may include the confirmation request or not; if the first information does not include the confirmation request, the first network device may not send an acknowledgment response to the first information to the terminal device.

[0137] The first network device is one of the following: a unified data management function (UDM, User Data Management), a unified data storage (UDR, Unified Data Repository), a user consent enforcement point (User Consent Enforcement point), and a first core network device.

[0138] Among them, the first core network device can be one of the following: user consent core function (UCCF, User Consent Core Function), user consent authorization network function (UCA NF, User consent authorize Network Function), and user consent network function (UC NF, User consent Network Function).

[0139] In some possible implementations, after the first network device receives the first information, the further step includes: the first network device updating one or more user consent parameters of the terminal device based on the first information. The detailed description of the first information is the same as that in the previous embodiment, and thus will not be repeated.

[0140] The first network device updates one or more user consent parameters of the terminal device based on the first information, including: the first network device obtains the user data of the terminal device based on the identification information of the terminal device; the first network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity; the first network device updates one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type.

[0141] The user data of the terminal device may include one or more user consent parameters of the terminal device. It should be understood that the one or more user consent parameters of the terminal device included in the user data of the terminal device can also be expressed as one or more user consent parameters of the terminal device, or one or more original user consent parameters of the terminal device, etc. This is not intended to limit the expression method of the network-side user consent parameters, but is only for the purpose of distinguishing them from the updated user consent parameters of the terminal device indicated by the first information.

[0142] It should be noted that the user data of the terminal device may also be referred to as user-related data of the terminal device, a user data collection of the terminal device, or other names. As long as it includes one or more user consent parameters of the terminal device, it is within the scope of protection of this embodiment. For example, in some possible examples, the user data of the terminal device may specifically be user subscription data of the terminal device. In addition, in addition to including the one or more user consent parameters of the terminal device mentioned above, the user data of the terminal device may also include other content, which is not limited in this embodiment.

[0143] In the related art, user consent (or user consent parameters) is for data types, that is, user consent parameters are saved with data type as the granularity, without considering the entity that actually uses the UE data collected by 5GC; while this application takes into account the differences in application services (i.e., AF) or the differences in application service types (AF types), and can bind the granularity of user consent parameters to the AF identifier and / or AF type. In an embodiment of the present application, the granularity or granularity of the user consent parameters or the content type includes at least one of the following: identification information of the terminal device, data type, data processing purpose, AF identifier, and AF type. In this way, by increasing the granularity of the user consent parameters and binding the granularity to the AF identifier and / or AF type, it is convenient to manage and update the user consent parameters of the terminal device at a larger granularity.

[0144] Several possible ways of adding an AF identifier and / or AF type to the user consent parameter are described below as examples:

[0145] In one example, referring to Table 6, the user consent parameters include: terminal device identification information (represented as SUCI / GPSI / SUPI in Table 6), data type, data processing purpose, and data consumer type; wherein the data consumer type includes the AF identifier (represented as AF ID in Table 6) and AF type (represented as AF Type in Table 6). For example, in the user consent parameters related to AIML applications, the AF ID and / or AF type corresponding to the AIML application are added, and in the user consent parameters related to Edge applications, the AF ID and / or AF type corresponding to the Edge application are added, and so on.

[0146]

[0147] Table 6

[0148] In another example, as shown in Table 7, the user consent parameters include: identification information of the terminal device (represented as SUCI / GPSI / SUPI in Table 7), UE data, and data processing purpose; wherein, the UE data includes the data type and the data consumer type; the data consumer type includes the AF identifier (represented as AF ID in Table 7) and the AF type (represented as AF Type in Table 7).

[0149]

[0150] Table 7

[0151] In another example, as shown in Table 8, the user consent parameters include: identification information of the terminal device (SUCI / GPSI / SUPI), data type, and data processing; among which, data processing includes data processing purpose and data consumer type; data consumer type includes AF identification (AF ID) and AF type (AF Type).

[0152]

[0153] Table 8

[0154] In some possible implementations, the first network device obtaining the user data of the terminal device based on the identification information of the terminal device includes: the first network device searching for the user data of the terminal device stored by the first network device based on the identification information of the terminal device. In this implementation, the first network device is a network device that stores at least the user data of the terminal device.

[0155] Optionally, when the update operation type is deletion, the first network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity, including: the first network device determines one or more user consent parameters of the terminal device at the target granularity contained in the user data based on the relevant information at the target granularity. The first network device updates one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: the first network device deletes one or more user consent parameters of the terminal device at the target granularity from the user data.

[0156] For example, the first information may include: identification information of the terminal device, the identification of each target AF in one or more target AFs, and the update operation type being deletion; that is, the relevant information at the target granularity in the first information includes the identification of each target AF in one or more target AFs. Accordingly, the first network device may search for user data of the terminal device stored in itself based on the identification information of the terminal device; then, based on the identification of each target AF in the one or more target AFs, determine all user consent parameters of the terminal device contained in the user data under the identification of each target AF; and delete all user consent parameters of the terminal device under the identification of each target AF from the user data.

[0157] For example, the first information may include: identification information of the terminal device, one or more target AF types, and an update operation type of deletion; that is, the relevant information at the target granularity in the first information includes one or more target AF types. Accordingly, the first network device can search for user data of the terminal device stored in itself based on the identification information of the terminal device; then, based on the one or more target AF types, determine all user consent parameters of the terminal device under each target AF type contained in the user data; and delete all user consent parameters of the terminal device under each target AF type from the user data.

[0158] For example, the first information may include: identification information of the terminal device, identification of each target AF in one or more target AFs, one or more target data types, one or more target data processing purposes, and the update operation type is deletion; that is, the first information is used to indicate the deletion of specific one or more user consent parameters. Accordingly, the first network device can search for the user data of the terminal device stored in itself based on the identification information of the terminal device; then, based on the identification of each target AF in the one or more target AFs, determine all user consent parameters of the terminal device under the identification of each target AF contained in the user data; and delete each target data type indicated by the first information and the user consent parameter corresponding to each target data processing purpose from all user consent parameters under the identification of each target AF contained in the user data. It should be understood that the identification of the above-mentioned target AF can also be replaced by the target AF type, and the specific processing is similar to the above, so it will not be repeated.

[0159] For example, the first information may include: identification information of the terminal device, identification of each target AF in one or more target AFs, one or more target data processing purposes, and the update operation type of deletion; that is, the relevant information at the target granularity in the first information includes the identification of each target AF in one or more target AFs and one or more target data processing purposes. Accordingly, the first network device can search for the user data of the terminal device stored in itself based on the identification information of the terminal device; then, based on the identification of each target AF in the one or more target AFs, determine all user consent parameters of the terminal device under the identification of each target AF contained in the user data; and delete one or more user consent parameters corresponding to each target data processing purpose in the one or more target data processing purposes indicated by the first information from all user consent parameters under the identification of each target AF contained in the user data. For example, if the identification of the target AF is AF01 and the target data processing purpose is collection, then all user consent parameters under AF01 with the data processing purpose of collection will be deleted from the user data. It should be understood that the identification of the target AF mentioned above can also be replaced by the target AF type, and the specific processing is similar to the above and will not be repeated.

[0160] The above is only an exemplary description of the corresponding processing performed by the first network device when the update operation type in the first information is deletion. In actual processing, the content that the first information can contain is not limited to the content of the above examples, and the processing performed by the first network device also depends on the specific content of the first information, but the processing method is similar to the above examples, so it is not exhaustive.

[0161] Optionally, when the update operation type is add, the first network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity, including: the first network device determines one or more user consent parameters of the terminal device at the target granularity indicated by the first information based on the relevant information at the target granularity. The first network device updates the one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: the first network device adds the one or more user consent parameters of the terminal device at the target granularity to the user data.

[0162] Since the update operation type is add, the relevant information at the target granularity in the first information will clearly indicate one or more user consent parameters to be added. On the first network device side, it is only necessary to add the one or more user consent parameters indicated in the first information to the user data of the terminal device.

[0163] For example, the first information may specifically include: identification information of the terminal device, identification of each of one or more target AFs, one or more target data types, one or more target data processing purposes, and the update operation type being add. The first network device may then search its stored user data for the terminal device based on the identification information of the terminal device; then, based on the identification of each target AF, each target data type, and each target data processing purpose, determine one or more user consent parameters to be added; and directly add the one or more user consent parameters to the user data.

[0164] Regarding the case where the update operation type is "add," the possible contents of the first information have been detailed in the aforementioned embodiment and will not be repeated here. Nor will an exhaustive list of the processes by which the first network device may add user consent parameters based on the specific contents of different first information be provided. Furthermore, the possible content types of the user consent parameters included in the first information are the same as those described for the user consent parameters in the aforementioned embodiment and will not be further elaborated here.

[0165] Optionally, when the update operation type is modification, the first network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity, including: the first network device determines one or more user consent parameters of the terminal device at the target granularity indicated by the first information based on the relevant information at the target granularity. The first network device updates one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: the first network device determines the user consent parameter corresponding to each of the one or more user consent parameters of the terminal device at the target granularity in the user data; the first network device modifies the corresponding user consent parameter in the user data based on each user consent parameter.

[0166] In which, the first network device determines the user consent parameter corresponding to each user consent parameter in the user data among the one or more user consent parameters of the terminal device at the target granularity; the first network device modifies the corresponding user consent parameter in the user data based on each user consent parameter, which can be specifically as follows: the first network device determines the kth user consent parameter corresponding to the i-th user consent parameter among the one or more user consent parameters of the terminal device at the target granularity; the first network device deletes the k-th user consent parameter in the user data and directly saves the i-th user consent parameter. In which, i and k are both positive integers; the i-th user consent parameter is any one of the one or more user consent parameters of the terminal device at the target granularity indicated by the first information. Since the processing of the one or more user consent parameters of the terminal device at the target granularity indicated by all first information is the same, they will not be described one by one.

[0167] Regarding the case where the update operation type is modification, the content that the first information may contain has been detailed in the aforementioned embodiment and will not be repeated here, nor will the processing of the first network device modifying the user consent parameter based on the specific content of different first information be exhaustively listed.

[0168] In some possible implementations, after the first network device updates one or more user consent parameters of the terminal device based on the first information, the method further includes: the first network device sends third information to a fourth network device when deleting one or more user consent parameters of the terminal device; the third information is used to instruct the fourth network device to stop processing data related to the deleted one or more user consent parameters of the terminal device.

[0169] The third information may also be referred to as a user consent revocation notification. The fourth network device is a consumer network element. In one example, the consumer network element may be represented as a "Consumer NF." In this embodiment, after receiving the third information, the fourth network device may determine, based on the laws of a specific region, whether one or more user consent parameters of the terminal device indicated in the third information should be deleted, isolated, or temporarily retained. This does not limit all possible processing by the fourth network device.

[0170] In this embodiment, the aforementioned first network device is specifically one of the following: a user consent enforcement point, a first core network device. The user consent enforcement point can be one of the following: NEF, EES (Edge Enable Server), NWDAF. The first core network device can be one of the following: UCCF, UCA NF, UC NF.

[0171] The first core network device may be located in a visited public land mobile network (VPLMN) or a home public land mobile network (HPLMN). Whether the first core network device is a core network device in the VPLMN or a core network device in the HPLMN is related to whether the current terminal device is a roaming terminal. For example, if the terminal device is a roaming terminal, the terminal device needs to access the VPLMN, and accordingly, the first core network device is a core network device in the VPLMN; otherwise, the first core network device is a core network device in the HPLMN.

[0172] Taking the first core network device, specifically UCCF, as an example, the UCCF is a centralized user consent processing function, which is explained in conjunction with Figure 5: the UCCF can be set up in the network and interact with the UCCF through the "Nuccf" message; the UCCF can obtain information from the NEF (Network Exposure Function) through the Nnef message in the network, interact with the UDM through the Nudm message, interact with the AUSF (Authentication Server Function) through the Nausf message, and interact with the AMF through the Namf message; In addition, Figure 5 also illustrates that the AMF can communicate with the RAN through the N2 interface and interact with the UE through the N1 interface. In addition, the UE can also directly interact with the AF (Application Function) through the Ua* interface. Specifically, the UCCF can be used to store user consent parameters, subscribe to the user consent update service of the UDM, receive user consent update parameters reported by the UE, and notify the consumer network element.

[0173] With reference to Figure 6, UCCF can be deployed in the HPLMN and VPLMN in non-roaming and roaming scenarios. For example, the left side of Figure 6 illustrates the architecture of deploying UCCF in the VPLMN. In the left side of Figure 6, the UE is in a roaming scenario. The VPLMN includes RAN, AMF, UPF (User Plane Function), AMF, SMF and UCCF. In the VPLMN, UCCF can be responsible for collecting and storing user consent parameters. The right side of Figure 6 illustrates the architecture of deploying UCCF in the HPLMN. The HPLMN includes UDM, SMF, AUSF, NEF, UPF and DN (Data Network). In the HPLMN, UCCF can be responsible for updating or obtaining the user consent parameters of the UDM and other processing. In addition, it can be seen from Figure 6 that the HPLMN and VPLMN interact through vSEEP and hSEEP. It should be pointed out that the UCCF in the aforementioned embodiment may be the first core network device, and the first core network device described in the aforementioned embodiment is located in the VPLMN or HPLMN, which does not mean that the UCCF can only be located in one of the VPLMN and the HPLMN, but refers to the UCCF used in the embodiments of the present application that is located in the VPLMN or the HPLMN. In fact, respective UCCFs can be set up in the VPLMN and the HPLMN, such as the UCCF in the HPLMN and the UCCF in the VPLMN, respectively. In the above scheme, by adding a core network device such as UCCF, user consent parameters can be centrally stored and updated. Since the UCCF can be deployed in the VPLMN and / or the HPLMN, it can be applied to scenarios where terminal devices roam.

[0174] This embodiment is particularly applicable to the architecture of deploying UCCF in the VPLMN on the left side of Figure 6, that is, it is particularly applicable to roaming scenarios. Since in the roaming scenario, the user consent parameters may be managed locally by the VPLMN, and the VPLMN uses UCCF to collect and store the user consent parameters, the roaming terminal device can directly report the first information to the UCCF of the roaming network, and the UCCF updates the user consent parameters in the locally stored user data; and if a user consent parameter is revoked or deleted, the consumer network element (i.e., the fourth network device) is notified to stop processing the data related to the user consent parameter. On the consumer network element, the UE data may be deleted, isolated, or temporarily retained according to the laws of the specific region.

[0175] Taking the terminal device as UE, the fifth network device as AMF, the sixth network device as SMF, the first network device as UCCF, and the fourth network device as a consumer network element as an example, the aforementioned implementation manner is exemplarily described in conjunction with FIG7, specifically including:

[0176] S701. A UE sends first information, where the first information is used to indicate an update of one or more user consent parameters of the UE. The first information includes a UE ID (SUCI, GPSI, SUPI), relevant information at a target granularity, and an update operation type.

[0177] This step can be divided into two cases: based on the control plane and based on the user plane:

[0178] S701a, uplink signaling based on the control plane: The UE sends a first message to the AMF through the RAN. The first message is used to indicate the update of one or more user consent parameters of the UE. The first message includes the UE ID (SUCI, GPSI, SUPI), relevant information at the target granularity, and the update operation type. In addition, the first message may also include an ACK request (acknowledgement request). The first message is carried by NAS signaling and is encrypted and integrity protected using the NAS security context.

[0179] S701b, uplink data based on the user plane: the UE sends first information to the SMF through the RAN, where the first information is used to indicate the update of one or more user consent parameters of the UE. The first information includes the UE ID (SUCI, GPSI, SUPI), relevant information at the target granularity, and the update operation type, which may include an ack request (confirmation request). The first information is carried by the user plane data and is encrypted and integrity protected using the UP security context.

[0180] The UE may currently be in a roaming scenario. The specific content of the first information has been described in detail in the above embodiment and will not be repeated here.

[0181] S702. AMF / SMF sends the first information to UCCF.

[0182] Here, since in a roaming scenario, the user consent parameters may be locally managed by the VPLMN, and the VPLMN uses the UCCF to collect and store the user consent parameters, the roaming terminal device can directly report the first information to the UCCF of the roaming network through the AMF / SMF, and the UCCF processes it. The first information sent by the AMF / SMF to the UCCF can be carried by a Nuccf message, and the specific message type is not limited in this embodiment.

[0183] S703. UCCF queries the corresponding user data based on the UE ID in the first information, determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity in the first information, and updates one or more user consent parameters of the UE at the target granularity in the user data based on the update operation type in the first information.

[0184] S704. UCCF returns a confirmation response of the first information to the UE through AMF / SMF. The confirmation response of the first information may be the "Acknowledgement" message shown in FIG. 7 .

[0185] S705. When deleting one or more user consent parameters of the UE, the UCCF sends third information to the consumer network element; the third information is used to instruct the consumer network element to stop processing data related to the one or more deleted user consent parameters of the UE.

[0186] S706. The consumer network element processes the one or more user consent parameters deleted by the UE based on the third information.

[0187] Specifically, the consumer network element may determine that one or more user consent parameters of the UE may be deleted, isolated, or temporarily retained based on the third information and the legal provisions of a specific region. All possible processing performed by the consumer network element is not limited here.

[0188] Regarding the process in Figure 7 above, it should also be noted that as long as the processing timing of the aforementioned S704 is after S703, it is within the protection scope of this example. The S704 can be before S705, after S705, or at the same time as S705. This example does not limit it.

[0189] In some possible implementations, the first network device acquires the user data of the terminal device based on the identification information of the terminal device, including one of the following:

[0190] The first network device obtains the locally stored user data of the terminal device when determining, based on the identification information of the terminal device, that the user data of the terminal device is locally stored;

[0191] When the first network device determines, based on the identification information of the terminal device, that the user data of the terminal device is not stored locally, the first network device obtains the user data of the terminal device from the third network device.

[0192] Specifically, the first network device detects whether the user data of the terminal device is stored locally based on the identification information of the terminal device; if it is determined that the user data of the terminal device is stored locally, the first network device obtains the locally stored user data of the terminal device; if it is determined that the user data of the terminal device is not stored locally, the first network device obtains the user data of the terminal device from the third network device.

[0193] The obtaining of the user data of the terminal device from the third network device may be as follows: the first network device sends a request message to the third network device, the request message carrying the identification information of the terminal device and indicating the acquisition of user consent parameters; the first network device receives all user consent parameters of the terminal device sent by the third network device, and the first network device stores all user consent parameters of the terminal device in the user data of the terminal device maintained by the first network device. Here, the corresponding processing of the third network device may include: the third network device receives the request message, searches for the locally stored user subscription data of the terminal device based on the identification information of the terminal device contained in the request message, and sends all user consent parameters of the terminal device contained in the user subscription data of the terminal device to the first network device.

[0194] In this embodiment, after obtaining the user data of the terminal device, the first network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity; the first network device updates the one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, which is the same as the previous embodiment and will not be repeated.

[0195] Furthermore, after the first network device updates one or more user consent parameters of the terminal device based on the first information, the method further includes: the first network device, upon deleting the one or more user consent parameters of the terminal device, sending third information to a fourth network device; the third information is used to instruct the fourth network device to stop processing data related to the one or more user consent parameters of the terminal device. The specific description of this part is the same as that of the previous embodiment and is not repeated here.

[0196] In this implementation, the key is not to modify the user subscription data stored in the third network device, but only to adjust or modify the user consent parameters stored in the first network device. Therefore, only when one or more user consent parameters of the terminal device (i.e., user data of the terminal device) are not stored in the first network device, will the process of interacting with the third network device and obtaining the user consent parameters of the terminal device be involved.

[0197] In this embodiment, the third network device is one of the following: UDM, UDR. The first network device is one of the following: user consent execution point, first core network device. The user consent execution point can be one of the following: NEF, EES (Edge Enable Server), NWDAF. The first core network device can be one of the following: UCCF, UCA NF, UC NF. The UCCF can be located in the VPLMN or HPLMN in Figure 6. The detailed description of UCCF has been detailed in the above description in conjunction with Figure 6 and will not be repeated here.

[0198] Taking the terminal device as UE, the fifth network device as AMF, the sixth network device as SMF, the third network device as UDM, the first network device as the user consent execution point, and the fourth network device as the consumer network element as an example, the aforementioned implementation method is exemplarily described in conjunction with Figure 8, specifically including:

[0199] S801. A UE sends first information indicating an update of one or more user consent parameters of the UE. The first information includes the UE ID (SUCI, GPSI, SUPI), relevant information at the target granularity, and the update operation type. The specific description of this step is the same as that of S701 above and is not repeated here.

[0200] S802. AMF / SMF sends a first message to the user consent execution point;

[0201] S803: The user consent execution point queries whether the UE user data is stored locally based on the UE ID in the first information. If not, execute S804; if stored, execute S807.

[0202] S804: The user consent enforcement point sends a request message to the UDM, which carries the UE ID. In addition to carrying the UE ID, the request message also indicates the need to obtain user consent parameters. For example, as shown in Figure 8 , the request message includes the UE ID and User Consent. This request message can be carried by a Nudm_SDM_GetRequest message, which is used to request the UE subscription data stored in the UDM using a "get" statement.

[0203] S805. The UDM queries the user consent parameter of the UE according to the UE ID.

[0204] S806. The UDM sends the UE's user consent parameters to the user consent execution point. The UE's user consent parameters may specifically refer to all UE's user consent parameters. The UE's user consent parameters may be carried in a Nudm_SDM_GetResponse message, which is a response message to the Nudm_SDM_GetRequest message.

[0205] Correspondingly, after receiving the user consent parameters of the UE returned by the UDM, the user consent execution point may save the user consent parameters of the UE under the user data of the UE.

[0206] S807: The user consent execution point determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity in the first information, and updates one or more user consent parameters of the UE at the target granularity in the user data based on the update operation type in the first information.

[0207] S808. The user agrees that the execution point returns a confirmation response of the first information to the UE via AMF / SMF.

[0208] S809. When deleting one or more user consent parameters of the UE, the user consent execution point sends third information to the consumer network element; the third information is used to instruct the consumer network element to stop processing data related to the one or more deleted user consent parameters of the UE.

[0209] S810. The consumer network element processes the one or more user consent parameters deleted by the UE based on the third information.

[0210] The detailed description of S810 is the same as that of S706, and will not be repeated here. As long as S808 is executed after S807, it is within the protection scope of this example.

[0211] Taking the terminal device as UE, the fifth network device as AMF, the sixth network device as SMF, the third network device as UDM, the first network device as UCCF, and the fourth network device as a consumer network element as an example, the aforementioned implementation manner is exemplarily described in conjunction with FIG9, specifically including:

[0212] S901. The UE sends first information indicating an update of one or more user consent parameters of the UE. The first information includes the UE ID (SUCI, GPSI, SUPI), relevant information at the target granularity, and the update operation type. The specific description of this step is the same as that of S701 above and is not repeated here.

[0213] S902. AMF / SMF sends the first information to UCCF; the first information sent by the AMF / SMF to UCCF can be carried by the Nuccf message, and the specific message type is not limited in this embodiment.

[0214] S903. The UCCF queries whether the user data of the UE is stored locally according to the UE ID in the first information. If not, execute S904; if stored, execute S907.

[0215] S904: The UCCF sends a request message to the UDM, which carries the UE ID. In addition to carrying the UE ID, the request message also indicates the need to obtain user consent parameters. For example, as shown in Figure 9, the request message includes the UE ID and User Consent. This request message can be carried by a Nudm_SDM_GetRequest message, which is used to request the UE subscription data stored in the UDM using a "get" statement.

[0216] S905. The UDM queries the user consent parameter of the UE according to the UE ID.

[0217] S906. The UDM sends the UE's user consent parameters to the UCCF. The UE's user consent parameters may specifically refer to all UE's user consent parameters. The UE's user consent parameters may be carried in a Nudm_SDM_GetResponse message, which is a response message to the Nudm_SDM_GetRequest message.

[0218] Correspondingly, after receiving the user consent parameter of the UE returned by the UDM, the UCCF may save the user consent parameter of the UE under the user data of the UE.

[0219] S907: UCCF determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity in the first information, and updates one or more user consent parameters of the UE at the target granularity in the user data based on the update operation type in the first information.

[0220] S908. UCCF returns a confirmation response of the first information to the UE through AMF / SMF.

[0221] S909. When deleting one or more user consent parameters of the UE, the UCCF sends third information to the consumer network element; the third information is used to instruct the consumer network element to stop processing data related to the one or more deleted user consent parameters of the UE.

[0222] S910. The consumer network element processes the one or more user consent parameters deleted by the UE based on the third information.

[0223] The detailed description of S910 is the same as that of S706, and will not be repeated here. As long as S908 is executed after S907, it is within the protection scope of this example.

[0224] In some possible implementations, after the first network device updates one or more user consent parameters of the terminal device based on the first information, the method further includes: the first network device sends second information to the second network device, and the second information is used by the second network device to update one or more user consent parameters of the terminal device.

[0225] The first network device sending the second information to the second network device may include: the first network device sending the second information to the second network device that has subscribed to sending notifications when subscription data is modified.

[0226] In this embodiment, the first network device is a network device that stores at least the user data of the aforementioned terminal device. After obtaining the user data of the terminal device, the first network device performs the following steps: determining one or more user consent parameters for the terminal device at the target granularity based on the relevant information at the target granularity; and updating the one or more user consent parameters for the terminal device at the target granularity in the user data based on the update operation type. These steps are the same as those in the aforementioned embodiment and are not described again.

[0227] Accordingly, the processing by the second network device includes: the second network device receiving second information sent by the first network device, where the second information is used by the second network device to update one or more user consent parameters of the terminal device. After the second network device receives the second information sent by the first network device, the processing also includes: the second network device updating the one or more user consent parameters of the terminal device based on the second information.

[0228] In this embodiment, the user data of the terminal device stored by the first network device may specifically be user subscription data of the terminal device stored by the first network device.

[0229] In some possible examples, the second information is related to the first information.

[0230] In one case, the second information is the same as the first information. That is, no matter what the first information includes, the first network device directly sends the first information as the second information to the second network device. In another case, when the first information includes the confirmation request, the second information includes: the identification information of the terminal device, the relevant information at the target granularity, and the update operation type. That is, if the first information includes a confirmation request, the first network device may not send the confirmation request to the second network device, but only send the identification information of the terminal device, the relevant information at the target granularity, and the update operation type in the first information as the second information to the second network device.

[0231] In both of the above cases, the second information at least includes the identification information of the terminal device, the relevant information at the target granularity, and the update operation type. Accordingly, the second network device updates one or more user consent parameters of the terminal device based on the second information, including: the second network device obtains the user data of the terminal device based on the identification information of the terminal device; the second network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity; the second network device updates one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type.

[0232] The second network device acquires the user data of the terminal device based on the identification information of the terminal device, specifically: the second network device acquires the locally stored user data of the terminal device based on the identification information of the terminal device. In this embodiment, the second network device is a network device that locally stores at least the user data of the terminal device.

[0233] When the update operation type is deletion, the second network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity, including: the second network device determines one or more user consent parameters of the terminal device at the target granularity contained in the user data based on the relevant information at the target granularity. The second network device updates one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: the second network device deletes one or more user consent parameters of the terminal device at the target granularity from the user data.

[0234] Since in this example, the second network device also performs processing based on the identification information of the terminal device, the relevant information at the target granularity, and the update operation type, the specific processing performed by the second network device when the update operation type is deletion should be the same as the specific processing performed by the aforementioned first network device when the update operation type is deletion, so it will not be repeated.

[0235] When the update operation type is increase, the second network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity, including: the second network device determines one or more user consent parameters of the terminal device at the target granularity indicated by the second information based on the relevant information at the target granularity. The second network device updates the one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: the second network device adds the one or more user consent parameters of the terminal device at the target granularity to the user data. Similarly, since in this example, the second network device also performs processing based on the identification information of the terminal device, the relevant information at the target granularity, and the update operation type, the specific processing performed by the second network device when the update operation type is increase should be the same as the specific processing of the first network device when the update operation type is increase, and therefore will not be repeated.

[0236] When the update operation type is modification, the second network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity, including: the second network device determines one or more user consent parameters of the terminal device at the target granularity indicated by the second information based on the relevant information at the target granularity. The second network device updates the one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: the second network device determines the user consent parameter corresponding to each user consent parameter in the user data among the one or more user consent parameters of the terminal device at the target granularity; the second network device modifies the corresponding user consent parameter in the user data based on each user consent parameter. Similarly, the specific processing performed by the second network device when the update operation type is modification should be the same as the specific processing performed by the aforementioned first network device when the update operation type is modification, so it will not be repeated.

[0237] It should be noted that if the second information received by the second network device includes the aforementioned confirmation request, the second network device may ignore the confirmation request. Alternatively, after completing the update of one or more user consent parameters of the terminal device, the second network device may send a confirmation response to the second information to the first network device; accordingly, the first network device may send a confirmation response to the first information to the terminal device after receiving the confirmation response to the second information, or the first network device may not need to wait for the confirmation response to the second information, and may send a confirmation response to the first information to the terminal device as soon as it completes the update of one or more user consent parameters of the terminal device. All of these are within the scope of protection of this embodiment.

[0238] In some possible examples, the second information includes one or more updated user consent parameters of the terminal device. The second network device updates the one or more user consent parameters of the terminal device based on the second information, including: the second network device saves the one or more updated user consent parameters of the terminal device.

[0239] Specifically, the second network device storing one or more updated user consent parameters of the terminal device may include: the second network device storing the one or more updated user consent parameters of the terminal device locally under the user data of the terminal device. This example differs from the previous example in that the second information contains all updated user consent parameters of the terminal device obtained by the first network device. Therefore, the second network device only needs to update and store all the content contained in the second information locally.

[0240] After the second network device updates one or more user consent parameters of the terminal device based on the second information, the method further includes: the second network device sends fourth information to the fourth network device when deleting one or more user consent parameters of the terminal device; the fourth information is used to instruct the fourth network device to stop processing data related to the deleted one or more user consent parameters of the terminal device.

[0241] The fourth network device is a consumer network element. The fourth information can also be referred to as a user consent revocation notification. The fourth network device is a consumer network element. In one example, the consumer network element can be represented as a "Consumer NF." In this embodiment, after receiving the fourth information, the fourth network device can determine, based on the legal provisions of a specific region, whether one or more user consent parameters of the terminal device indicated in the fourth information may be deleted, isolated, or temporarily retained. All possible processing of the fourth network device is not limited here.

[0242] In this embodiment, the first network device is one of the following: a unified data management function (UDM) or a unified data storage (UDR); the second network device is one of the following: a user consent enforcement point (UEP) or a first core network device. The UEP can be one of the following: an NEF, an EES (Edge Enable Server), or an NWDAF. The first core network device can be one of the following: an UCCF, an UCA NF, or an UC NF.

[0243] The previous embodiment described a first network device sending a second message to a second network device that has subscribed to notifications for modified subscription data. Assuming the first network device is a UDM and the second network device is a user consent enforcement point, the UDM can send the second message to a user consent enforcement point that has subscribed to the Nudm_SDM_Notification service. This second message can also be referred to as a user consent update notification.

[0244] The aforementioned second network device can be located in a VPLMN or an HPLMN. For example, for a roaming terminal device, the second network device is located in a VPLMN. The user consent parameters in the HPLMN need to be provided to the VPLMN. The UDM (i.e., the first network device) can discover and select the second network device through the NRF (Network Repository Function) and provide the user consent parameters to the second network device of the VPLMN.

[0245] Taking the terminal device as UE, the fifth network device as AMF, the sixth network device as SMF, the first network device as UDM, the second network device as the user consent execution point, the fourth network device as the consumer network element, and the user data of the UE stored in the first network device, namely the UDM, as an example, the aforementioned embodiment is further exemplified in conjunction with FIG10, specifically including:

[0246] S1001. A UE sends first information, where the first information is used to indicate an update of one or more user consent parameters of the UE. The first information includes a UE ID (SUCI, GPSI, SUPI), relevant information at a target granularity, and an update operation type.

[0247] This step can be divided into two cases: based on the control plane and based on the user plane:

[0248] S1001a, uplink signaling based on the control plane: The UE sends a first message to the AMF through the RAN. The first message is used to indicate the update of one or more user consent parameters of the UE. The first message includes the UE ID (SUCI, GPSI, SUPI), relevant information at the target granularity, and the update operation type. In addition, the first message may also include an ACK request (acknowledgement request). The first message is carried by NAS signaling and is encrypted and integrity protected using the NAS security context.

[0249] S1001b, uplink data based on the user plane: the UE sends first information to the SMF through the RAN, where the first information is used to indicate the update of one or more user consent parameters of the UE. The first information includes the UE ID (SUCI, GPSI, SUPI), relevant information at the target granularity, and the update operation type, which may include an ack request (acknowledgement request). The first information is carried by the user plane data and is encrypted and integrity protected using the UP security context.

[0250] The specific content of the first information has been described in detail in the above embodiment and will not be repeated here.

[0251] S1002. AMF / SMF sends the first information to UDM.

[0252] Specifically, AMF / SMF may send the first information to the UDM storing the user subscription data in the 5GC. The first information sent by the AMF / SMF to the UDM may be carried by a Nudm_SDM_Update / Modify (NF modifies / updates an existing subscription) message.

[0253] S1003. UDM queries the user subscription data of the UE according to the UE ID in the first information, determines one or more user consent parameters of the terminal device at the target granularity according to the relevant information at the target granularity in the first information, and updates one or more user consent parameters of the UE at the target granularity in the user subscription data of the UE based on the update operation type in the first information.

[0254] S1004. UDM returns a confirmation response of the first information to the UE through AMF / SMF. The confirmation response of the first information may be an "Acknowledgement" message.

[0255] S1005. The UDM sends second information to the user consent enforcement point, where the second information is used by the user consent enforcement point to update one or more user consent parameters of the UE.

[0256] Specifically, the UDM may send the second information to the user consent execution point that subscribes to the Nudm_SDM_Notification service. The second information may be carried by the Nudm_SDM_Notification message.

[0257] S1006: The user consent execution point updates one or more user consent parameters of the terminal device based on the second information. The specific processing of this step has been detailed in the above embodiment and will not be repeated here.

[0258] S1007. When deleting one or more user consent parameters of the UE, the user consent execution point sends fourth information to the consumer network element; the fourth information is used to instruct the consumer network element to stop processing data related to the one or more deleted user consent parameters of the UE.

[0259] S1008. The consumer network element processes the one or more user consent parameters deleted by the UE based on the fourth information.

[0260] Specifically, the consumer network element may determine that one or more user consent parameters of the UE may be deleted, isolated, or temporarily retained based on the fourth information and the legal provisions of a specific region. All possible processing performed by the consumer network element is not limited here.

[0261] As long as the aforementioned S1004 is executed after S1003, it is within the protection scope of this example. For example, S1004 can be executed before S1005, S1004 can be executed after S1005, etc., and there is no limitation on it.

[0262] Taking the terminal device as UE, the fifth network device as AMF, the sixth network device as SMF, the first network device as UDM, the second network device as UCCF, the fourth network device as a consumer network element, and the user data of the UE stored in the first network device, namely the UDM, as an example, the foregoing embodiment is further exemplarily described in conjunction with FIG11, specifically including:

[0263] S1101. A UE sends first information, where the first information is used to indicate an update of one or more user consent parameters of the UE. The first information includes a UE ID (SUCI, GPSI, SUPI), relevant information at a target granularity, and an update operation type.

[0264] This step can be divided into two cases: based on the control plane and based on the user plane:

[0265] S1101a, uplink signaling based on the control plane: The UE sends a first message to the AMF through the RAN. The first message is used to indicate the update of one or more user consent parameters of the UE. The first message includes the UE ID (SUCI, GPSI, SUPI), relevant information at the target granularity, and the update operation type. In addition, the first message may also include an ACK request (acknowledgement request). The first message is carried by NAS signaling and is encrypted and integrity protected using the NAS security context.

[0266] S1101b, uplink data based on the user plane: the UE sends first information to the SMF through the RAN, where the first information is used to indicate the update of one or more user consent parameters of the UE. The first information includes the UE ID (SUCI, GPSI, SUPI), relevant information at the target granularity, and the update operation type, which may include an ack request (acknowledgement request). The first information is carried by the user plane data and is encrypted and integrity protected using the UP security context.

[0267] The specific content of the first information has been described in detail in the above embodiment and will not be repeated here.

[0268] S1102. AMF / SMF sends the first information to UDM.

[0269] Specifically, AMF / SMF may send the first information to the UDM storing the user subscription data in the 5GC. The first information sent by the AMF / SMF to the UDM may be carried by a Nudm_SDM_Update / Modify (NF modifies / updates an existing subscription) message.

[0270] S1103. UDM queries the user subscription data of the UE according to the UE ID in the first information, determines one or more user consent parameters of the terminal device at the target granularity according to the relevant information at the target granularity in the first information, and updates one or more user consent parameters of the UE at the target granularity in the user subscription data of the UE based on the update operation type in the first information.

[0271] S1104. UDM returns a confirmation response of the first information to the UE through AMF / SMF. The confirmation response of the first information may be an "Acknowledgement" message.

[0272] S1105. The UDM sends second information to the UCCF, where the second information is used by the UCCF to update one or more user consent parameters of the UE. The second information may be carried in a Nudm_SDM_Notification message.

[0273] Specifically, the UDM may send the second information to the UCCF that has subscribed to the Nudm_SDM_Notification service. Alternatively, the UDM may discover and select a UCCF through the NRF and then send the second information to the UCCF. For example, the UDM may discover the UCCF through the URF and select a UCCF located in the VPLMN or the HPLMN.

[0274] S1106: UCCF updates one or more user consent parameters of the terminal device based on the second information. The specific processing of this step has been described in detail in the above embodiment and will not be repeated here.

[0275] S1107. When deleting one or more user consent parameters of the UE, the UCCF sends fourth information to the consumer network element; the fourth information is used to instruct the consumer network element to stop processing data related to the one or more deleted user consent parameters of the UE.

[0276] S1108. The consumer network element processes the one or more user consent parameters deleted by the UE based on the fourth information.

[0277] Specifically, the consumer network element may determine that one or more user consent parameters of the UE may be deleted, isolated, or temporarily retained based on the fourth information and the legal provisions of a specific region. All possible processing performed by the consumer network element is not limited here.

[0278] As long as the aforementioned S1104 is executed after S1103, it is within the protection scope of this example and is not limited thereto.

[0279] As can be seen, by adopting the above solution, the terminal device can send the first information to instruct the network to update the user consent parameters of the terminal device. In this way, by introducing the terminal device to trigger the update of the user consent parameters, the update of the user consent parameters of the terminal device on the network side can be controlled by the terminal device, thereby remedying the shortcomings of the relevant technology and avoiding the problem of third-party application functions abusing the private data of the terminal device, thereby ensuring the security of the private data of the terminal device.

[0280] FIG12 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application, including:

[0281] The first communication unit 1201 is configured to send first information, where the first information is used to indicate an update of one or more user consent parameters of the terminal device.

[0282] The first information is used to instruct updating of one or more user consent parameters of the terminal device at a target granularity.

[0283] The first information includes: identification information of the terminal device, relevant information at the target granularity, and update operation type; wherein, the relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; the update operation type includes one of the following: deletion, addition, and modification.

[0284] The target granularity includes at least one of the following: application function AF, AF type, data type, and data processing purpose.

[0285] The relevant information at the target granularity includes at least one of the following: an identifier of each target AF in one or more target AFs; one or more target AF types; one or more target data types; one or more target data processing purposes.

[0286] The first information also includes: a confirmation request; the first communication unit is used to receive a confirmation response to the first information after sending the first information; the confirmation response to the first information is used to confirm the completion of updating one or more user consent parameters of the terminal device.

[0287] The first communication unit is used to send the first information to the first network device.

[0288] The first information is carried by one of the following: non-access stratum NAS signaling and uplink data of the user plane.

[0289] The first network device is one of the following: a unified data management function UDM, a unified data storage UDR, a user consent execution point, and a first core network device.

[0290] The first core network device is located in a visited public land mobile network VPLMN or a home public land mobile network HPLMN.

[0291] The first core network device is one of the following: user consent core function UCCF, user consent authorization network function UCA NF, and user consent network function UC NF.

[0292] The terminal device of the embodiment of the present application can implement the corresponding functions of the terminal device in the aforementioned method embodiment. In addition to the above-mentioned first communication unit, the terminal device may also include a first processing unit, and the first processing unit can at least generate the above-mentioned first information. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the terminal device can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the terminal device of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.), or by the same module (sub-module, unit or component, etc.).

[0293] FIG13 is a schematic diagram of the composition structure of a first network device according to an embodiment of the present application, including:

[0294] The second communication unit 1301 is configured to receive first information, where the first information is used to indicate updating of one or more user consent parameters of the terminal device.

[0295] Based on FIG. 13 , as shown in FIG. 14 , the first network device further includes: a second processing unit 1302 , configured to update one or more user consent parameters of the terminal device based on the first information.

[0296] The first information is used to instruct updating of one or more user consent parameters of the terminal device at a target granularity.

[0297] The first information includes: identification information of the terminal device, relevant information at the target granularity, and update operation type; wherein, the relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; the update operation type includes one of the following: deletion, addition, and modification.

[0298] The target granularity includes at least one of the following: application function AF, AF type, data type, and data processing purpose.

[0299] The relevant information at the target granularity includes at least one of the following: an identifier of each target AF in one or more target AFs; one or more target AF types; one or more target data types; one or more target data processing purposes.

[0300] The second processing unit is used to obtain user data of the terminal device based on the identification information of the terminal device; determine one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity; and update one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type.

[0301] When the update operation type is deletion, the second processing unit is used to determine one or more user consent parameters of the terminal device at the target granularity contained in the user data based on the relevant information at the target granularity.

[0302] The second processing unit is configured to delete one or more user consent parameters of the terminal device at the target granularity from the user data.

[0303] When the update operation type is addition, the second processing unit is configured to add one or more user consent parameters of the terminal device at the target granularity to the user data.

[0304] When the update operation type is modification, the second processing unit is used to determine the user consent parameter corresponding to each user consent parameter in the user data among one or more user consent parameters of the terminal device at the target granularity; and modify the corresponding user consent parameter in the user data based on each user consent parameter.

[0305] The first information also includes: a confirmation request; the second communication unit is used to send a confirmation response of the first information to the terminal device after the second processing unit updates one or more user consent parameters of the terminal device based on the first information; the confirmation response of the first information is used to confirm the completion of updating one or more user consent parameters of the terminal device.

[0306] The second communication unit is used to send second information to the second network device after the second processing unit updates one or more user consent parameters of the terminal device based on the first information, and the second information is used by the second network device to update one or more user consent parameters of the terminal device.

[0307] The second information is related to the first information.

[0308] The second information is the same as the first information.

[0309] In the case where the first information includes the confirmation request, the second information includes: identification information of the terminal device, relevant information at the target granularity, and the update operation type.

[0310] The second information includes: one or more updated user consent parameters of the terminal device.

[0311] The first network device is one of the following: a unified data management function UDM, a unified data storage UDR; the second network device is one of the following: a user consent execution point, a first core network device.

[0312] The second processing unit is used to perform one of the following: when it is determined based on the identification information of the terminal device that the user data of the terminal device is locally stored, obtaining the locally stored user data of the terminal device; when it is determined based on the identification information of the terminal device that the user data of the terminal device is not locally stored, obtaining the user data of the terminal device from the third network device through the second communication unit.

[0313] The third network device is one of the following: UDM, UDR.

[0314] The second processing unit is used to send third information to the fourth network device through the second communication unit when one or more user consent parameters of the terminal device are deleted; the third information is used to instruct the fourth network device to stop processing data related to the one or more user consent parameters deleted by the terminal device; the second communication unit is used to send the third information to the fourth network device.

[0315] The fourth network device is a consumer network element.

[0316] The first network device is one of the following: a user consent execution point, a first core network device.

[0317] The first information is carried by one of the following: non-access stratum NAS signaling and uplink data of the user plane.

[0318] The first core network device is located in a VPLMN or a HPLMN.

[0319] The first core network device is one of the following: user consent core function UCCF, user consent authorization network function UCA NF, and user consent network function UC NF.

[0320] The first network device of the embodiment of the present application can implement the corresponding functions of the first network device in the aforementioned information verification method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the first network device can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the first network device of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0321] FIG15 is a second network device according to an embodiment of the present application, including:

[0322] The third communication unit 1501 is configured to receive second information sent by the first network device, where the second information is used by the second network device to update one or more user consent parameters of the terminal device.

[0323] Based on FIG. 15 , as shown in FIG. 16 , the second network device further includes: a third processing unit 1502 , configured to update one or more user consent parameters of the terminal device based on the second information.

[0324] The second information is related to the first information.

[0325] The first information includes: identification information of the terminal device, relevant information at the target granularity, and the update operation type;

[0326] The relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; the update operation type includes one of the following: deletion, addition, and modification.

[0327] The target granularity includes at least one of the following: application function AF, AF type, data type, and data processing purpose.

[0328] The relevant information at the target granularity includes at least one of the following: an identifier of each target AF in one or more target AFs; one or more target AF types; one or more target data types; one or more target data processing purposes.

[0329] The first information also includes: a confirmation request; the confirmation request is used to request confirmation of completion of updating one or more user consent parameters of the terminal device.

[0330] The second information is the same as the first information.

[0331] When the first information includes the confirmation request, the second information includes: identification information of the terminal device, relevant information at the target granularity, and the update operation type.

[0332] The third processing unit is used to obtain user data of the terminal device based on the identification information of the terminal device; determine one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity; and update one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type.

[0333] When the update operation type is deletion, the third processing unit is used to determine one or more user consent parameters of the terminal device at the target granularity contained in the user data based on the relevant information at the target granularity.

[0334] The third processing unit is configured to delete one or more user consent parameters of the terminal device at the target granularity from the user data.

[0335] When the update operation type is addition, the third processing unit is configured to add one or more user consent parameters of the terminal device at the target granularity to the user data.

[0336] When the update operation type is modification, the third processing unit is used to determine the user consent parameter corresponding to each user consent parameter in the user data among one or more user consent parameters of the terminal device at the target granularity; and modify the corresponding user consent parameter in the user data based on each user consent parameter.

[0337] The second information includes: one or more updated user consent parameters of the terminal device.

[0338] The third processing unit is used to save one or more updated user consent parameters of the terminal device.

[0339] The third processing unit is used to send fourth information to the fourth network device through the third communication unit when one or more user consent parameters of the terminal device are deleted; the fourth information is used to instruct the fourth network device to stop processing data related to the one or more user consent parameters deleted by the terminal device; the third communication unit is used to send the fourth information to the fourth network device.

[0340] The fourth network device is a consumer network element.

[0341] The first network device is one of the following: a unified data management function UDM, a unified data storage UDR; the second network device is one of the following: a user consent execution point, a first core network device.

[0342] The first core network device is located in a VPLMN or a HPLMN.

[0343] The first core network device is one of the following: user consent core function UCCF, user consent authorization network function UCA NF, and user consent network function UC NF.

[0344] The second network device of the embodiment of the present application can implement the corresponding functions of the second network device in the aforementioned information verification method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the second network device can be found in the corresponding descriptions in the above-mentioned method embodiments, and will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the second network device of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.), or by the same module (sub-module, unit or component, etc.).

[0345] Figure 17 is a schematic structural diagram of a communication device 1700 according to an embodiment of the present application. The communication device 1700 includes a processor 1710, which can call and execute a computer program from a memory to enable the communication device 1700 to implement the method in the embodiment of the present application.

[0346] In a possible implementation, the communication device 1700 may further include a memory 1720. The processor 1710 may call and execute a computer program from the memory 1720 to enable the communication device 1700 to implement the method in the embodiment of the present application.

[0347] The memory 1720 may be a separate device independent of the processor 1710 , or may be integrated into the processor 1710 .

[0348] In one possible implementation, the communication device 1700 may further include a transceiver 1730 , and the processor 1710 may control the transceiver 1730 to communicate with other devices. Specifically, it may send information or data to other devices, or receive information or data sent by other devices.

[0349] The transceiver 1730 may include a transmitter and a receiver. The transceiver 1730 may further include an antenna, and the number of antennas may be one or more.

[0350] In one possible implementation, the communication device 1700 may be a terminal device of an embodiment of the present application, and the communication device 1700 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be described in detail here. In one possible implementation, the communication device 1700 may be a first network device of an embodiment of the present application, and the communication device 1700 may implement the corresponding processes implemented by the first network device in each method of the embodiment of the present application. For the sake of brevity, they will not be described in detail here. In one possible implementation, the communication device 1700 may be a second network device of an embodiment of the present application, and the communication device 1700 may implement the corresponding processes implemented by the second network device in each method of the embodiment of the present application. For the sake of brevity, they will not be described in detail here.

[0351] 18 is a schematic structural diagram of a chip 1800 according to an embodiment of the present application. The chip 1800 includes a processor 1810, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0352] In one possible implementation, the chip 1800 may further include a memory 1820. The processor 1810 may call and execute a computer program from the memory 1820 to implement the method performed by the access network device or the first core network device in the embodiment of the present application. The memory 1820 may be a separate device independent of the processor 1810 or integrated into the processor 1810.

[0353] In one possible implementation, the chip 1800 may further include an input interface 1830. The processor 1810 may control the input interface 1830 to communicate with other devices or chips, specifically, to obtain information or data sent by other devices or chips. In one possible implementation, the chip 1800 may further include an output interface 1840. The processor 1810 may control the output interface 1840 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0354] In one possible implementation, the chip may be applied to the second network device in the embodiment of the present application, and the chip may implement the corresponding processes implemented by the second network device in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here. In one possible implementation, the chip may be applied to the terminal device in the embodiment of the present application, and the chip may implement the corresponding processes implemented by the terminal device in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here. In one possible implementation, the chip may be applied to the first network device in the embodiment of the present application, and the chip may implement the corresponding processes implemented by the first network device in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here. The chips applied to the second network device, the terminal device, and the first network device may be the same chip or different chips.

[0355] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0356] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0357] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may 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 may be a random access memory (RAM).

[0358] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0359] Figure 19 is a schematic block diagram of a communication system 1900 according to an embodiment of the present application. Communication system 1900 includes a second network device 1910, a terminal device 1920, and a first network device 1930. Second network device 1910 can be used to implement the corresponding functions implemented by the second network device in the above-described method, and terminal device 1920 can be used to implement the corresponding functions implemented by the terminal device in the above-described method. First network device 1930 can be used to implement the corresponding functions implemented by the first network device in the above-described method. For the sake of brevity, this description will not be repeated here.

[0360] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0361] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0362] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0363] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A parameter updating method, comprising: The terminal device sends first information, where the first information is used to indicate updating of one or more user consent parameters of the terminal device.

2. The method according to claim 1, wherein: The first information is used to indicate updating of one or more user consent parameters of the terminal device at a target granularity.

3. The method according to claim 2, wherein: The first information includes: identification information of the terminal device, relevant information at a target granularity, and an update operation type; The relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; The update operation type includes one of the following: delete, add, and modify.

4. The method according to claim 3, wherein: The target granularity includes at least one of the following: application function AF, AF type, data type, and data processing purpose.

5. The method according to claim 4, wherein: The relevant information at the target granularity includes at least one of the following: an identification of each of the one or more target AFs; One or more target AF types; one or more target data types; One or more target data processing purposes.

6. The method according to any one of claims 1 to 5, wherein: The first information further includes: a confirmation request; after the terminal device sends the first information, the method further includes: The terminal device receives a confirmation response to the first information; the confirmation response to the first information is used to confirm the completion of updating one or more user consent parameters of the terminal device.

7. The method according to any one of claims 1 to 6, wherein: The terminal device sends first information, including: The terminal device sends the first information to the first network device.

8. The method according to claim 7, wherein: The first information is carried by one of the following: non-access layer NAS signaling and uplink data of the user plane.

9. The method according to claim 7 or 8, wherein: The first network device is one of the following: a unified data management function UDM, a unified data storage UDR, a user consent execution point, and a first core network device.

10. The method according to claim 9, wherein: The first core network device is located in a visited public land mobile network VPLMN or a home public land mobile network HPLMN.

11. The method according to claim 10, wherein: The first core network device is one of the following: a user consent core function UCCF, a user consent authorization network function UCA NF, and a user consent network function UC NF.

12. A parameter updating method, comprising: The first network device receives first information, where the first information is used to indicate updating one or more user consent parameters of the terminal device.

13. The method according to claim 12, wherein: After the first network device receives the first information, the method further includes: The first network device updates one or more user consent parameters of the terminal device based on the first information.

14. The method according to claim 13, wherein: The first information is used to indicate updating of one or more user consent parameters of the terminal device at a target granularity.

15. The method according to claim 14, wherein: The first information includes: identification information of the terminal device, relevant information at a target granularity, and an update operation type; The relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; The update operation type includes one of the following: delete, add, and modify.

16. The method according to claim 15, wherein: The target granularity includes at least one of the following: application function AF, AF type, data type, and data processing purpose.

17. The method according to claim 16, wherein: The relevant information at the target granularity includes at least one of the following: an identification of each of the one or more target AFs; One or more target AF types; one or more target data types; One or more target data processing purposes.

18. The method according to any one of claims 15 to 17, wherein: The first network device updates one or more user consent parameters of the terminal device based on the first information, including: The first network device acquires user data of the terminal device based on the identification information of the terminal device; The first network device determines, based on the relevant information at the target granularity, one or more user consent parameters of the terminal device at the target granularity; The first network device updates, in the user data, one or more user consent parameters of the terminal device at the target granularity based on the update operation type.

19. The method according to claim 18, wherein: When the update operation type is deletion, the first network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity, including: The first network device determines one or more user consent parameters of the terminal device at the target granularity contained in the user data based on the relevant information at the target granularity.

20. The method according to claim 19, wherein: The first network device updates, in the user data, one or more user consent parameters of the terminal device at the target granularity based on the update operation type, including: The first network device deletes one or more user consent parameters of the terminal device at the target granularity from the user data.

21. The method according to claim 18, wherein: When the update operation type is increase, the first network device updates one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: The first network device adds one or more user consent parameters of the terminal device at the target granularity to the user data.

22. The method according to claim 18, wherein: When the update operation type is modification, the first network device updates one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: The first network device determines, among the one or more user consent parameters of the terminal device at the target granularity, a user consent parameter corresponding to each user consent parameter in the user data; The first network device modifies a corresponding user consent parameter in the user data based on each user consent parameter.

23. The method according to any one of claims 18 to 22, wherein: The first information further includes: a confirmation request; after the first network device updates one or more user consent parameters of the terminal device based on the first information, the method further includes: The first network device sends a confirmation response of the first information to the terminal device; the confirmation response of the first information is used to confirm the completion of updating one or more user consent parameters of the terminal device.

24. The method according to any one of claims 15 to 23, wherein: After the first network device updates one or more user consent parameters of the terminal device based on the first information, the method further includes: The first network device sends second information to the second network device, where the second information is used by the second network device to update one or more user consent parameters of the terminal device.

25. The method according to claim 24, wherein: The second information is related to the first information.

26. The method according to claim 25, wherein: The second information is the same as the first information.

27. The method according to claim 25, wherein: In the case where the first information includes the confirmation request, the second information includes: identification information of the terminal device, relevant information at the target granularity, and the update operation type.

28. The method of claim 24, wherein: The second information includes: one or more updated user consent parameters of the terminal device.

29. The method according to any one of claims 24 to 28, wherein: The first network device is one of the following: a unified data management function UDM, a unified data storage UDR; The second network device is one of the following: a user consent execution point, a first core network device.

30. The method according to any one of claims 18 to 23, wherein: The first network device acquires user data of the terminal device based on the identification information of the terminal device, including one of the following: The first network device obtains the locally stored user data of the terminal device when determining that the user data of the terminal device is locally stored based on the identification information of the terminal device; When the first network device determines, based on the identification information of the terminal device, that the user data of the terminal device is not stored locally, the first network device obtains the user data of the terminal device from the third network device.

31. The method according to claim 30, wherein: The third network device is one of the following: UDM, UDR.

32. The method according to any one of claims 13 to 23, 30 and 31, wherein: After the first network device updates one or more user consent parameters of the terminal device based on the first information, the method further includes: When deleting one or more user consent parameters of the terminal device, the first network device sends third information to the fourth network device; the third information is used to instruct the fourth network device to stop processing data related to the deleted one or more user consent parameters of the terminal device.

33. The method of claim 32, wherein: The fourth network device is a consumer network element.

34. The method according to any one of claims 30 to 33, wherein: The first network device is one of the following: a user consent execution point, a first core network device.

35. The method according to any one of claims 12 to 34, wherein: The first information is carried by one of the following: non-access layer NAS signaling and uplink data of the user plane.

36. The method according to claim 29 or 34, wherein: The first core network device is located in the VPLMN or the HPLMN.

37. The method of claim 36, wherein: The first core network device is one of the following: a user consent core function UCCF, a user consent authorization network function UCA NF, and a user consent network function UC NF.

38. A parameter updating method, comprising: The second network device receives second information sent by the first network device, where the second information is used by the second network device to update one or more user consent parameters of the terminal device.

39. The method of claim 38, wherein: After the second network device receives the second information sent by the first network device, the method further includes: The second network device updates one or more user consent parameters of the terminal device based on the second information.

40. The method of claim 39, wherein: The second information is related to the first information.

41. The method of claim 40, wherein: The first information includes: The identification information of the terminal device, relevant information at the target granularity, and the update operation type; The relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; The update operation type includes one of the following: delete, add, and modify.

42. The method according to claim 41, wherein: The target granularity includes at least one of the following: application function AF, AF type, data type, and data processing purpose.

43. The method of claim 42, wherein: The relevant information at the target granularity includes at least one of the following: an identification of each of the one or more target AFs; One or more target AF types; one or more target data types; One or more target data processing purposes.

44. The method according to any one of claims 41 to 43, wherein: The first information also includes: a confirmation request; the confirmation request is used to request confirmation of completion of updating one or more user consent parameters of the terminal device.

45. The method according to any one of claims 41 to 44, wherein: The second information is the same as the first information.

46. ​​The method according to any one of claims 41 to 44, wherein: When the first information includes the confirmation request, the second information includes: identification information of the terminal device, relevant information at the target granularity, and the update operation type.

47. The method according to any one of claims 41 to 46, wherein: The second network device updates one or more user consent parameters of the terminal device based on the second information, including: The second network device acquires user data of the terminal device based on the identification information of the terminal device; The second network device determines, based on the relevant information at the target granularity, one or more user consent parameters of the terminal device at the target granularity; The second network device updates, in the user data, one or more user consent parameters of the terminal device at the target granularity based on the update operation type.

48. The method of claim 47, wherein: When the update operation type is deletion, the second network device determines one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity, including: The second network device determines one or more user consent parameters of the terminal device at the target granularity contained in the user data based on the relevant information at the target granularity.

49. The method of claim 48, wherein: The second network device updates, in the user data, one or more user consent parameters of the terminal device at the target granularity based on the update operation type, including: The second network device deletes one or more user consent parameters of the terminal device at the target granularity from the user data.

50. The method of claim 47, wherein: When the update operation type is increase, the second network device updates one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: The second network device adds one or more user consent parameters of the terminal device at the target granularity to the user data.

51. The method of claim 47, wherein: When the update operation type is modification, the second network device updates one or more user consent parameters of the terminal device at the target granularity in the user data based on the update operation type, including: The second network device determines, among the one or more user consent parameters of the terminal device at the target granularity, a user consent parameter corresponding to each user consent parameter in the user data; The second network device modifies a corresponding user consent parameter in the user data based on each user consent parameter.

52. The method of claim 39, wherein: The second information includes: one or more updated user consent parameters of the terminal device.

53. The method of claim 52, wherein: The second network device updates one or more user consent parameters of the terminal device based on the second information, including: The second network device stores one or more updated user consent parameters of the terminal device.

54. The method according to any one of claims 39 to 53, wherein: After the second network device updates one or more user consent parameters of the terminal device based on the second information, the method further includes: When deleting one or more user consent parameters of the terminal device, the second network device sends fourth information to the fourth network device; the fourth information is used to instruct the fourth network device to stop processing data related to the deleted one or more user consent parameters of the terminal device.

55. The method of claim 54, wherein: The fourth network device is a consumer network element.

56. The method according to any one of claims 38 to 55, wherein: The first network device is one of the following: a unified data management function UDM, a unified data storage UDR; The second network device is one of the following: a user consent execution point, a first core network device.

57. The method of claim 56, wherein: The first core network device is located in the VPLMN or the HPLMN.

58. The method of claim 57, wherein: The first core network device is one of the following: a user consent core function UCCF, a user consent authorization network function UCA NF, and a user consent network function UC NF.

59. A terminal device, comprising: The first communication unit is used to send first information, where the first information is used to indicate updating one or more user consent parameters of the terminal device.

60. The terminal device according to claim 59, wherein: The first information is used to indicate updating of one or more user consent parameters of the terminal device at a target granularity.

61. The terminal device according to claim 60, wherein: The first information includes: identification information of the terminal device, relevant information at the target granularity, and an update operation type; wherein the relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; the update operation type includes one of the following: deletion, addition, and modification.

62. The terminal device according to claim 61, wherein: The target granularity includes at least one of the following: application function AF, AF type, data type, and data processing purpose.

63. The terminal device according to claim 62, wherein: The relevant information at the target granularity includes at least one of the following: an identifier of each target AF in one or more target AFs; one or more target AF types; one or more target data types; one or more target data processing purposes.

64. The terminal device according to any one of claims 59 to 63, wherein: The first information also includes: a confirmation request; the first communication unit is used to receive a confirmation response to the first information after sending the first information; the confirmation response to the first information is used to confirm the completion of updating one or more user consent parameters of the terminal device.

65. The terminal device according to any one of claims 59 to 64, wherein: The first communication unit is used to send the first information to the first network device.

66. The terminal device according to claim 65, wherein: The first information is carried by one of the following: non-access layer NAS signaling and uplink data of the user plane.

67. The terminal device according to claim 65 or 66, wherein: The first network device is one of the following: a unified data management function UDM, a unified data storage UDR, a user consent execution point, and a first core network device.

68. The terminal device according to claim 67, wherein: The first core network device is located in a visited public land mobile network VPLMN or a home public land mobile network HPLMN.

69. The terminal device according to claim 68, wherein: The first core network device is one of the following: a user consent core function UCCF, a user consent authorization network function UCA NF, and a user consent network function UC NF.

70. A first network device, comprising: The second communication unit is used to receive first information, where the first information is used to indicate updating one or more user consent parameters of the terminal device.

71. The first network device according to claim 70, wherein: The first network device also includes: a second processing unit, configured to update one or more user consent parameters of the terminal device based on the first information.

72. The first network device according to claim 71, wherein: The first information is used to indicate updating of one or more user consent parameters of the terminal device at a target granularity.

73. The first network device according to claim 72, wherein: The first information includes: identification information of the terminal device, relevant information at the target granularity, and an update operation type; wherein the relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; the update operation type includes one of the following: deletion, addition, and modification.

74. The first network device according to claim 73, wherein: The target granularity includes at least one of the following: application function AF, AF type, data type, and data processing purpose.

75. The first network device according to claim 74, wherein: The relevant information at the target granularity includes at least one of the following: an identifier of each target AF in one or more target AFs; one or more target AF types; one or more target data types; one or more target data processing purposes.

76. The first network device according to any one of claims 73 to 75, wherein: The second processing unit is used to obtain user data of the terminal device based on the identification information of the terminal device; Determine one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity; Based on the update operation type, one or more user consent parameters of the terminal device at the target granularity are updated in the user data.

77. The first network device according to claim 76, wherein: When the update operation type is deletion, the second processing unit is used to determine one or more user consent parameters of the terminal device at the target granularity contained in the user data based on the relevant information at the target granularity.

78. The first network device according to claim 77, wherein: The second processing unit is used to delete one or more user consent parameters of the terminal device at the target granularity from the user data.

79. The first network device according to claim 76, wherein: When the update operation type is addition, the second processing unit is used to add one or more user consent parameters of the terminal device at the target granularity to the user data.

80. The first network device according to claim 76, wherein: When the update operation type is modification, the second processing unit is used to determine, among the one or more user consent parameters of the terminal device at the target granularity, a user consent parameter corresponding to each user consent parameter in the user data; Based on each user consent parameter, a corresponding user consent parameter in the user data is modified.

81. The first network device according to any one of claims 76 to 80, wherein: The first information also includes: a confirmation request; the second communication unit is used to send a confirmation response to the first information to the terminal device after the second processing unit updates one or more user consent parameters of the terminal device based on the first information; the confirmation response to the first information is used to confirm the completion of updating one or more user consent parameters of the terminal device.

82. The first network device according to any one of claims 73 to 81, wherein: The second communication unit is used to send second information to the second network device after the second processing unit updates one or more user consent parameters of the terminal device based on the first information, and the second information is used by the second network device to update one or more user consent parameters of the terminal device.

83. The first network device according to claim 82, wherein: The second information is related to the first information.

84. The first network device according to claim 83, wherein: The second information is the same as the first information.

85. The first network device according to claim 83, wherein: In the case where the first information includes the confirmation request, the second information includes: identification information of the terminal device, relevant information at the target granularity, and the update operation type.

86. The first network device according to claim 82, wherein: The second information includes: one or more updated user consent parameters of the terminal device.

87. The first network device according to any one of claims 82 to 86, wherein: The first network device is one of the following: a unified data management function UDM, a unified data storage UDR; the second network device is one of the following: a user consent execution point, a first core network device.

88. The first network device according to any one of claims 76 to 81, wherein: The second processing unit is used to perform one of the following: when it is determined based on the identification information of the terminal device that the user data of the terminal device is locally stored, obtaining the user data of the terminal device stored locally; when it is determined based on the identification information of the terminal device that the user data of the terminal device is not locally stored, obtaining the user data of the terminal device from the third network device through the second communication unit.

89. The first network device according to claim 88, wherein: The third network device is one of the following: UDM, UDR.

90. The first network device according to any one of claims 71-81, 88, and 89, wherein: The second processing unit is configured to send third information to the fourth network device through the second communication unit when one or more user consent parameters of the terminal device are deleted; The third information is used to instruct the fourth network device to stop processing the data related to the one or more user consent parameters deleted by the terminal device; The second communication unit is used to send third information to the fourth network device.

91. The first network device according to claim 90, wherein: The fourth network device is a consumer network element.

92. The first network device according to any one of claims 88 to 91, wherein: The first network device is one of the following: a user consent execution point, a first core network device.

93. The first network device according to any one of claims 70 to 92, wherein: The first information is carried by one of the following: non-access layer NAS signaling and uplink data of the user plane.

94. The first network device according to claim 87 or 92, wherein: The first core network device is located in the VPLMN or the HPLMN.

95. The first network device according to claim 94, wherein: The first core network device is one of the following: a user consent core function UCCF, a user consent authorization network function UCA NF, and a user consent network function UC NF.

96. A second network device, comprising: The third communication unit is used to receive second information sent by the first network device, where the second information is used by the second network device to update one or more user consent parameters of the terminal device.

97. The second network device according to claim 96, wherein: The second network device also includes: The third processing unit is used to update one or more user consent parameters of the terminal device based on the second information.

98. The second network device according to claim 97, wherein: The second information is related to the first information.

99. The second network device according to claim 98, wherein: The first information includes: identification information of the terminal device, relevant information at the target granularity, and an update operation type; wherein the relevant information at the target granularity is used to determine one or more user consent parameters at the target granularity; the update operation type includes one of the following: deletion, addition, and modification.

100. The second network device according to claim 99, wherein: The target granularity includes at least one of the following: application function AF, AF type, data type, and data processing purpose.

101. The second network device according to claim 100, wherein: The relevant information at the target granularity includes at least one of the following: an identifier of each target AF in one or more target AFs; one or more target AF types; one or more target data types; one or more target data processing purposes.

102. The second network device according to any one of claims 99 to 101, wherein: The first information also includes: a confirmation request; the confirmation request is used to request confirmation of completion of updating one or more user consent parameters of the terminal device.

103. The second network device according to any one of claims 99 to 102, wherein: The second information is the same as the first information.

104. The second network device according to any one of claims 99 to 102, wherein: When the first information includes the confirmation request, the second information includes: identification information of the terminal device, relevant information at the target granularity, and the update operation type.

105. The second network device according to any one of claims 99 to 104, wherein: The third processing unit is used to obtain user data of the terminal device based on the identification information of the terminal device; Determine one or more user consent parameters of the terminal device at the target granularity based on the relevant information at the target granularity; Based on the update operation type, one or more user consent parameters of the terminal device at the target granularity are updated in the user data.

106. The second network device according to claim 105, wherein: When the update operation type is deletion, the third processing unit is used to determine one or more user consent parameters of the terminal device at the target granularity contained in the user data based on the relevant information at the target granularity.

107. The second network device according to claim 106, wherein: The third processing unit is used to delete one or more user consent parameters of the terminal device at the target granularity from the user data.

108. The second network device according to claim 105, wherein: When the update operation type is addition, the third processing unit is used to add one or more user consent parameters of the terminal device at the target granularity to the user data.

109. The second network device according to claim 105, wherein: When the update operation type is modification, the third processing unit is used to determine, among the one or more user consent parameters of the terminal device at the target granularity, a user consent parameter corresponding to each user consent parameter in the user data; Based on each user consent parameter, a corresponding user consent parameter in the user data is modified.

110. The second network device according to claim 97, wherein: The second information includes: one or more updated user consent parameters of the terminal device.

111. The second network device according to claim 110, wherein: The third processing unit is used to save one or more updated user consent parameters of the terminal device.

112. The second network device according to any one of claims 97 to 111, wherein: The third processing unit is used to send fourth information to the fourth network device through the third communication unit when one or more user consent parameters of the terminal device are deleted; The fourth information is used to instruct the fourth network device to stop processing the data related to the one or more user consent parameters deleted by the terminal device; The third communication unit is used to send fourth information to the fourth network device.

113. The second network device according to claim 112, wherein: The fourth network device is a consumer network element.

114. The second network device according to any one of claims 96-113, wherein: The first network device is one of the following: a unified data management function UDM, a unified data storage UDR; The second network device is one of the following: a user consent execution point, a first core network device.

115. The second network device according to claim 114, wherein: The first core network device is located in the VPLMN or the HPLMN.

116. The second network device according to claim 115, wherein: The first core network device is one of the following: a user consent core function UCCF, a user consent authorization network function UCA NF, and a user consent network function UC NF.

117. A terminal device comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the terminal device executes the method as claimed in any one of claims 1 to 11.

118. A first network device, comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so that the first network device executes the method as claimed in any one of claims 12 to 37.

119. A second network device, comprising: A transceiver, a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so that the second network device executes the method as claimed in any one of claims 38 to 58.

120. A chip, comprising: A processor, configured to call and run a computer program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1 to 11, or claims 12 to 37, or claims 38 to 58.

121. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method as claimed in any one of claims 1 to 11, or claims 12 to 37, or claims 38 to 58.

122. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 11, or claims 12 to 37, or claims 38 to 58.

123. A computer program causing a computer to perform the method of any one of claims 1 to 11, or claims 12 to 37, or claims 38 to 58.

Images