User consent for training data collection in a cellular communication system

Abstract

A user equipment (UE) determines a user consent preference with respect to data collection. The UE communicates, with a core network (CN) and in a non-access stratum (NAS) message, an indication of the user consent preference.

Description

PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00USER CONSENT FOR TRAINING DATA COLLECTION IN A CELLULAR COMMUNICATION SYSTEMCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to and the benefit of the filing date of provisional U.S. Patent Application No. 63 / 753,438 entitled “User Data Consent for Artificial Intelligence and Machining Learning Training Data Collection in a Cellular Communication System,” filed on February 3, 2025 and provisional U.S. Patent Application No. 63 / 756,046 entitled “User Data Consent for Artificial Intelligence and Machining Learning Training Data Collection in a Cellular Communication System,” filed on February 13, 2025. The entire content of the provisional applications is hereby expressly incorporated herein by reference.FIELD OF THE DISCLOSURE

[0002] This disclosure relates generally to methods, devices, and articles in wireless communication systems, such as 3GPP communication systems, and in particular to determining and communicating user consent information related to data collection.BACKGROUND

[0003] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] The 3rd Generation Partnership Project (3GPP) contemplates convergence between communication system functions and Artificial Intelligence (Al) technology, to improve the intelligence at the fifth-generation core (5GC) and the air interface and support network automation. More particularly, 3GPP has begun to address such topics as data collection (DC), machine learning (ML) model training, analytics inference, etc. These technical areas require collaborative AI / ML mechanisms for coordinating functionality across such domains as userPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00equipment (UE), radio access network (RAN), 5GC, operations and maintenance (OAM), and application functions (AF).

[0005] To support collection of training data for a UE-side model that generates complete inferences at the UE, based on the specifications related to AI / ML for New Radio (NR) air interface documented in 3GPP TR 38.843, 3GPP has agreed to study the potential support of UE data collection to meet the requirements for RAN Al support for air interface operation. Today, the remaining issues include enhancement of UE data collection and policy control in a 5G system.

[0006] 3GPP has identified several options for data collection for UE-side model training: (i) a UE collecting and directly transferring training data to an Over-the-Top (OTT) server, in a transparent or non-transparent manner; (ii) the UE collecting training data and transferring the training data to the core network, which then transfers the training data to the OTT server; or (iii) the UE collecting training data and transferring the training data to an OAM, which then transfers the relevant data to the OTT server.

[0007] According to TS 23.288, a network data analytics function (NWDAF) can support data collection for network automation based on the UE application data collection framework described in TS 26.531. The NWDAF can interact with a data collection application function (DCAF) in the trusted domain of the operator network, to collect data from a UE application as an input for analytics generation and ML model training. This framework can apply to the UE collecting and directly transferring training data to an OTT server as discussed above, where the DCAF operates as a data collection network function (DCNF) that connects to the User- Plane Function (UPF) via an N6 interface.

[0008] To comply with local regulations and operator policy, and before collecting AI / ML model training data, the network should obtain, from the UE, user consent for the corresponding AI / ML-enabled features for various purposes, e.g., AI / ML training for a UE-sided model, a RAN-sided model, or a CN-side model. However, according to TS 23.501 and TS 23.288, the user consent for data collection currently is based on the subscription information stored in a Unified Data Management function (UDM). The subscription information indicates whether thePATENT APPLICATION Attorney Docket No.: 31730 / 308899-00user authorizes data collection and usage of the UE data for a particular purpose, where the purpose for data collection is analytics or model training.

[0009] The existing mechanisms are designed for collecting UE data managed and stored in the core network, and the NWDAF generates an AI / ML model or analytics requested by consumers (e.g., an AF, a Policy Control Function (PCF), a Session Management Function (SMF), an Access & Mobility Management Function (AMF), or an OAM) for network-side inferencing. The existing mechanisms are insufficient to properly analyze user consent.

[0010] In particular, there is no standardized mechanism that allows a UE (or the user) to change the user consent setting(s) for the purpose of data collection. Further, the existing subscription-based user consent is too coarse to properly reflect data sensitivities of different AI / ML-enabled features, which may require user consent based on user preferences; nor can the existing subscription-based user consent properly address potential future regulations and regulatory requirements.

[0011] Further, according to TS 23.288, when collecting training data from a UE application, an application service provider (ASP) is responsible for obtaining user consent prior to sharing data with a mobile network operator (MNO) and operating an ASP-side model for AI / ML inference. In these scenarios, the network can use training data from the ASP without performing further user consent checking. As a result, the user may not be aware how the data is shared with the MNO, and the user cannot provide consent for specific conditions such as location and / or time.

[0012] According to the approach in which the UE collects training data related to AI / ML for NR air interface and transfers this data to a core network, the DCNF operates in a core network for AI / ML model training for UE-side model inferencing, and the DCNF collects AI / ML training data directly from the UE for the corresponding AI / ML-enabled feature. This requires a sophisticated user consent mechanism to enforce training data collection. However, it is not clear how the existing user consent mechanisms should be enhanced to provide finer granularities of user consent for AI / ML training data collection, and to allow a user to initially indicate, modify, and update the consent in a systematic manner.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0013] Still further, in addition to collecting training data for AI / ML related to the NR air interface, various other 3GPP features can require training data collection. These 3GPP features can correspond to various use cases and can span various domains such as the RAN, the core network, and cloud applications. These AFML-enabled features are expected to enhance resource management for the radio interface, radio resource management, RAN mobility, and core network automation.

[0014] It remains unclear how a core network can enhance policy control and manage user consent for data connections for collecting data, at the user plane (UP) or control plane(UP) for one or more AI / ML- enabled features, specifically associated with a UE reporting collected training data to a DCNF at a 5GC for UE-side model training. For example, it is unclear how the UE and the network can enforce user consent checking based on the target AI / ML training data of the corresponding AI / ML enabled feature.SUMMARY

[0015] The techniques discussed below address the challenges outlined above and support management of user consent for AI / ML training data collection, particularly for UE-side modeling.

[0016] An example embodiment of these techniques is a method implemented in a user equipment (UE). The method includes determining a user consent preference with respect to data collection; and transmitting, to a core network (CN) and in a non-access stratum (NAS) message, an indication of the user consent preference.

[0017] Another example embodiment of these techniques is a method implemented in a UE. The method includes receiving, from a CN and in an NAS message, an indication of the user consent preference with respect to UP data collection, and storing the user consent preference at the UE.

[0018] Another example embodiment of these techniques is a UE including a transceiver and processing hardware. The UE is configured to implement one of the methods above.BRIEF DESCRIPTION OF THE DRAWINGSPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0019] Fig. 1 is a block diagram of an example wireless communication system that can implement one or more of the techniques of this disclosure for managing user consent for userplane data collection;

[0020] Fig. 2 is a block diagram of an example protocol stack according to which the UE of Fig. 1 can communicate with the RAN of Fig. 1;

[0021] Fig. 3 is a service-based representation of the CN architecture, which the system of Fig. 1 can implement.

[0022] Fig. 4 is a reference-point based representation of the CN architecture, which the system of Fig. 1 can implement.

[0023] Fig. 5 is a flow diagram of an example method for exchanging, with a core network, user consent preference information, which can be implemented in a UE of Fig. 1;

[0024] Fig. 6 is a flow diagram of an example method generally similar to that of Fig. 5, but according to which the user consent preference information applies to one or more specified AI / ML-cnablcd features;

[0025] Fig. 7 is messaging diagram of an example scenario in which the UE or the CN of Fig.1 initiates a user consent update for UP data collection;

[0026] Fig. 8 is a flow diagram of an example method in an SMF for using a policy and charging control (PCC) rule with UP data collection configuration that includes a user consent indication and the address for the UP data collection;

[0027] Fig. 9 is a flow diagram of an example method in an SMF for using a PCC rule, with UP data collection configuration, to generate N4 rules for the UPF;

[0028] Fig. 10A is a messaging diagram of an example scenario in which the UE uses the registration request procedure to report, to the network, user consent preference for UP data collection;

[0029] Fig. 10B is a messaging diagram of an example scenario in which the UE uses the registration request procedure to receive, from the network, user consent preference for UP data collection;PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0030] Fig. 11 is a messaging diagram of an example scenario in which the UE and the network perform consent management using UL NAS Transport and / or DL NAS Transport messaging;

[0031] Fig. 12A is a messaging diagram of an example scenario in which a UE performs a UE-initiated user consent preference update procedure using a PDU session;

[0032] Fig. 12B is a messaging diagram of an example scenario in which a UE performs a network-initiated user consent preference update procedure using a PDU session;

[0033] Fig. 13A is a flow diagram of an example method in a UE for configuring data collection using a traffic descriptor (TD) with an indication for updating a user consent preference for UP data collection;

[0034] Fig. 13B is a flow diagram of an example method in a UE using a TD with an indication for updating a user consent preference for UP data collection for one or more AI / ML-enabled features;

[0035] Fig. 13C is a flow diagram of an example method in a UE using a TD that specifies one or more AI / ML-enabled features and a route selection descriptor (RSD) that includes an indication for updating a user consent preference for UP data collection;

[0036] Fig. 13D is a flow diagram of an example method in a UE using an RSD with an indication for updating a user consent preference;

[0037] Fig. 14 is a messaging diagram of an example scenario in which a UE uses one of the techniques of Figs. 13A-D;

[0038] Fi. 15 is a messaging diagram of an examples scenario in which a UE uses a dedicated UE policy of data collection and routing policy (DCRP) rules for user consent management for UP data collection;

[0039] Fig. 16 is a messaging diagram of an example scenario in which a UE uses dedicated DCRP rules provisioned at a PDU session level; and

[0040] Fig. 17 is a flow of an example method a UE can implement to apply dedicated DCRP rules provisioned at a PDU session level.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00DETAILED DESCRIPTION OF THE DRAWINGS

[0041] Generally speaking, a UE and one or more network functions (NFs) operating in core network (CN) support data collection for AI / ML training (or simply “training data”) in view of user consent information. The training data the UE transmits to a DCNF can apply for various 3GPP system features and can correspond to various use cases related to RAN, CN, and / or cloud functionality. These AI / ML-enabled features can enhance resource management for the radio interface, radio resource management, RAN mobility, core network automation, etc.

[0042] Some of the specific examples of such features include AI / ML based channel state information (CSI) compression, AI / ML based CSI reference signal (CSI-RS) overhead reduction, AI / ML-based CSI prediction, AI / ML based beam management with downlink beam prediction, direct AI / ML positioning, and AI / ML-assisted positioning for positioning accuracy enhancement, supporting AI / ML based network slicing, AI / ML based coverage and capability optimization, AI / ML based Network Energy Saving (NES) for finer granularities, AI / ML enabled radio resource management (RRM) measurement prediction, measurement event prediction, AI / ML enabled quality of service (QoS) sustainability analytics enhancement, QoS and Policy Assistance Analytics enhancement, Packet Data Unit (PDU) session traffic analytics enhancement, movement behavior analytics enhancement, location accuracy analytics enhancement, etc.

[0043] In at least some of the implementations, the AFML-enabled features have respective feature identifiers (IDs). A UE in general supports one or more AI / ML-enabled features and uses a feature ID to associate particular training data with a particular AI / ML-enabled feature. More generally, a UE and / or the network (e.g., the CN) can use feature IDs when handling UP data collection and policies that control UP data connections for UP data collection.

[0044] The approaches discussed below can apply to a UE, a DCNF (which can be implemented in a legacy NF or can operate as a special-purpose, dedicated NF), or both.

[0045] In some implementations, the DCNF operates within an existing (legacy) NF such as for example a Location Management Function (LMF), a PCF, an AMF, or an SMF. The entity in which the DCNF operates can support service operations for UP data collection directly. ForPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00example, an AI / ML-enabled feature can be related to positioning accuracy enhancement, and the LMF can operate as the DCNF to provide the UP data collection service for that feature.

[0046] In other implementations, the DCNF is a dedicated NF configured to support operations related to UP data collection for, or on behalf of, the existing (legacy) NFs such as an LFM, a PCF, an AMF, or an SMF for example. According to this approach, NFs can request a UP data collection service from the dedicated DCNF.

[0047] In yet other implementations, a DCNF operates in an NWDAF with coordination functionality, i.e., with a Data Collection Coordination Function (DCCF). According to this approach, NFs operate as consumers and request a data collection service from the NWDAF with the DCCF. Accordingly, the NWDAF with DCCF can enhance operations of Nnwdaf_DataManagement services, to collect training data from a UE.

[0048] The approaches discussed below provide at least the following functionality: (i) message exchange related to user preferences for UP data collection, (ii) message exchange related to user preferences for UP data collection with respect to or more particular AI / ME enabled features, so as to improve the granularity of user consent, (iii) support of UE-initiated or network-initiated user consent update mechanism, for user consent management, (iv) a registration request procedure that supports user consent management, (v) user consent management via uplink (UL) non-access stratum (NAS) transport or downlink (DL) NAS transport, (vi) user consent management via PDU Session Establishment or modification, (vii) user consent management via configuration of UE policy for a User Equipment Route Selection Policy (URSP) rule, (viii) user consent management via UE policy for a Data Collection Routing (DCRP) rule, or (ix) user consent management by provisioning of a DCRP ride provisioned at the level of a PDU session.

[0049] While this disclosure uses 5G networks as an example, one will appreciate that the principles of this disclosure generally apply to 3G networks, 4G networks, 6G networks, and future generations of networks.

[0050] Further, although the disclosure primarily refers to UP data collection, at least some of the techniques discussed herein can also apply to control-plane (CP) data collection.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00Example system architecture

[0051] Referring first to Fig. 1, an example wireless communication system 100 can implement one or more of the techniques of this disclosure for managing user consent for UP data collection. The example wireless communication system 100 includes UEs 102 A, 102B, a base station (BS) 104, a base station 106, and a core network (CN) 110, such as a fifth generation (5G) core (5GC). The base stations 104 and 106 can operate in a RAN 105 connected to the CN 110. The CN 110 can also be implemented as a sixth generation (6G) core or another suitable core network.

[0052] The base station 104 covers a cell 124, and the base station 106 covers a cell 126. If the base station 104 is a gNB, the cell 124 is an NR cell. If the base station 124 is an ng-eNB, the cell 124 is an evolved universal terrestrial radio access (E-UTRA) cell. Similarly, if the base station 106 is a gNB, the cell 126 is an NR cell, and if the base station 126 is an ng-eNB, the cell 126 is an E-UTRA cell. The cells 124 and 126 can be in the same Radio Access Network Notification Areas (RNA) or different RNAs. The cells 124 and 126 can partially overlap, so that the UE 102 A and UE 102B can select, reselect, or hand over from one of the cells 124 and 126 to the other. In general, the RAN 105 can include any number of base stations, and each of the base stations can cover one, two, three, or any other suitable number of cells. The UE 102 can support at least a 5G NR (or simply, “NR”) air interface to communicate with the base stations 104 and 106. Each of the base stations 104, 106 can connect to the CN 110 via an interface (e.g., SI or NG interface). The base stations 104 and 106 also can be interconnected via an interface (e.g., X2 or Xn interface) for interconnecting NG RAN nodes.

[0053] Several network functions (NFs) that make up the CN 110 are discussed below with reference to Figs. 3A and 3B. The CN 110 includes a DCNF 142, which in different implementations can operate as a separate NF within the CN 110 or as a component of another NF such as an LMF for example. In some implementations, a data collection application function (DCAF) 144 can operate in the trusted domain of the CN 110. The CN 110 can communicate with an application server (AS) 146, which also can operate in a trusted domain. Further, in some scenarios or implementations, one or more NFs of the CN 110 operate on a CN-side AI / ML model 147.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0054] While not depicted in Fig. 1 to avoid clutter, the CN 110 may include processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable memory storing instructions that the one or more general-purpose processors execute. Additionally or alternatively, the processing hardware can include specialpurpose processing units.

[0055] The base station 104 can be equipped with processing hardware that can include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable memory storing instructions that the one or more general-purpose processors execute (not shown).Additionally or alternatively, the processing hardware can include special-purpose processing units.

[0056] The UE 102A is equipped with processing hardware 130 that can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. The UE 102A also includes a transceiver 132 to communicate with the RAN 105 over a radio interface. Further, the UE 102 A includes a memory 134 storing a user consent controller 136 and user consent setting 135. The memory 134 in some cases further stores a UE-side ML model 137. The UE 102B may be configured in a similar manner as the UE 102A.

[0057] Fig. 2 illustrates, in a simplified manner, an example protocol stack 200 according to which the UE 102A, 102B, or 102C can communicate with an eNB / ng-eNB 230 or a gNB 232 (e.g., one or more of the base stations 104, 106). In the example stack 200. a physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to a EUTRA PDCP sublayer 208 and. in some cases, to an NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 in turn can provide data transfer services to Service Data Adaptation Protocol (SDAP) 212 or a radio resource control (RRC) sublayer (not shown inPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00Fig. 2). The UE 102A, 102B, or 102C, in some implementations, supports both the EUTRA and the NR stack as shown in Fig. 2, to support handover between EUTRA and NR base stations and / or to support DC over EUTRA and NR interfaces. Further, as illustrated in Fig. 2, the UE 102A or 102B can support layering of NR PDCP 210 over EUTRA RLC 206A, and SDAP sublayer 212 over the NR PDCP sublayer 210.

[0058] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets (e.g.. from an Internet Protocol (IP) layer, layered directly or indirectly over the PDCP layer 208 or 210) that can be referred to as service data units (SDUs), and output packets (e.g., to the RLC layer 206A or 206B) that can be referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as “packets.”

[0059] On a control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide signaling radio bearers (SRBs) or RRC sublayer (not shown in Fig. 2) to exchange RRC messages or non-access-stratum (NAS) messages, for example. On a user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide data radio bearers (DRBs) to support data exchange. Data exchanged on the NR PDCP sublayer 210 can be SDAP PDUs, Internet Protocol (IP) packets, or Ethernet packets.

[0060] Fig. 3 is a service-based representation 300 of an example CN architecture, which the system of Fig. 1 can implement as the CN 110. In the representation 300, the overall nonroaming reference architecture of the policy and charging control (PCC) framework for the 5GS includes components illustrated using solid lines, and the other components are illustrated using dashed lines. According to this representation, network functions enable other authorized network functions to access their services. The components that are outside the PCC framework include a Network Slicing Selection Function (NSSF) 302, a Network Repository Function (NRF) 306, a Unified Data Management (UDM) 308, an Edge Application Server Discovery Function (EASDF) 310, a Network Slice Specific Authentication and Authorization Function (NSSAAF) 312, an Authentication Server Function (AUSF) 314, a Service Communication Proxy (SCP) 316, and a Network Slice Admission Control Function (NSACF) 318. The non-PCC architecture further includes the UE 102 and the (R)AN 105.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0061] The PCC framework in the architecture 300 includes a Unified Data Repository (UDR) 352, a Network Exposure Function (NEF) 354, a network data analytics function (NWDAF) 356, an Application Function (AF) 358, a Policy Control Function (PCF) 360, a Charging Function (CHF) 362, an Access & Mobility Management Function (AMF) 364, a Session Management Function (SMF) 366, and a User Plane Function (UPF) 370. The UPF 370 can access a data network (DN) 330, in which an application server (AS) 346 can operate.

[0062] The AMF 364 is generally configured to manage registration, connection, and mobility of a UE (such as the UE 102A or 102B) and provide transport for session management (SM) messages between the UE 102A or 102B and the SMF 366. The SMF 366 is generally configured to manage sessions, allocate IP addresses for UEs, and provides downlink (DL) notifications. In some implementations, the SMF 366 also includes following functionalities for PIN service: providing per-QoS flow non-3GPP QoS assistance information to the UE (e.g., PEGC), and supporting IP address allocation to UE and PDR configuration with packet filter set for PIN to UPF for framed routing based on PIN group information from the UDM 308.

[0063] The UDM 308 is generally configured to handle user identification, access authorization based on subscription data, and subscription management. In some implementations, the UDM 308 supports the functionality of PIN group management handling.

[0064] The UDR 352 is generally configured to store subscription-related information, such as subscription data, policy data, structured data for exposure, and application data. The UPF 370 is generally configured to handle packet routing and forwarding. The NEF 354 is generally configured to expose a network’s capabilities and services to authorized third-party applications.

[0065] The AF 357 in some deployment operates in a trusted domain 311 or outside the trusted domain 311, i.e., in a non-trusted domain. The trusted domain 311 is generally internal to the CN 110 and includes such components as the UDM 308, the UDR 352, the PCF 358, the AMF 364, the SMF 366, and the UPF 370. Generally speaking, an AF operating outside the trusted domain 311 (such as operated by an authorized third-party entity) can access the network functions of the CN 110 only via the NEF 354, whereas an AF operating within the trusted domain 311 can access at least some of the network functions of the CN 110 directly, or may access these functions via the NEF 354 in some deployments.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0066] The CN 300 can include a DCNF 342 as a separate node. Additionally or alternatively, one or more of the NFs of the CN 300 can include an instance of a DCNF. For example, a DCNF can operate in an LMF 345, the PCF 358, the AMF 364, or the SMF 366.

[0067] Fig. 4 is a reference-point based representation 400 of the example 5GS architecture discussed with reference to Fig. 3. In Fig. 4, the non-roaming reference architecture of the PCC framework for the 5GS is illustrated as blocks and connections with solid lines, and components and connections outside the PCC framework are illustrated using dashed lines. The interfaces are labeled with the corresponding protocols, e.g., N3 between the RAN 105 and the UPF 370, N1 between the AMF 364 and the UE 102, etc.

[0068] The communication system shown Figs. 1-4 in may include additional, fewer, and / or alternative devices or functionalities, and may be configured to perform additional, fewer, or alternate actions, including functionalities / actions described herein.Example techniques for user consent management

[0069] Generally speaking, user consent management in the system of Fig. 1 can include the UE 102 and the CN 110 exchanging information to communicate user consent preferences.

[0070] In some implementations, the user consent preference can be associated with all AI / ML-enabled features that require data collection from a UE to facilitate AL / ML model training at the CN or an AS operating in a trusted domain (e.g., in a cloud). The AI / ML inference for an AI / ML-enabled feature can take place at the UE (e.g., to develop the UE-side model 137 illustrated in Fig. 1), at an NF in the CN (e.g.. to develop the CN-side model 147 illustrated in Fig. 1), or at the RAN (to develop a RAN-side model), etc.

[0071] Generally speaking, similar events in Figs. 5-17 are labeled with similar reference numbers that share two least significant digits, with differences discussed below where appropriate. For example, event 760 is similar to event 1060 and 1160. and event 1012B is similar to block 1312B.

[0072] Referring to Fig. 5, a method 500 can be implemented in a UE such as the UE 120. The method 500 begins at block 502, where the UE initiates a user consent preference update. To this end, the UE retrieves, from the memory of the UE, user consent preference for UP dataPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00collection included in the UE context or the UE configuration. At block 504, the UE sends a NAS message such as a Registration Request message, a PDU Session Establishment Request message, a PDU Session Modification Request message, a UL NAS Transport message, or a dedicated, special-purpose NAS message. The NAS message includes an indication of the user consent preference for UP data collection. In an example implementation, the indication is one of (i) the UP data collection is allowed, (ii) the UP data collection is disallowed, or (iii) user consent for the UP data collection is pending. In the latter case, the network can determine to trigger a procedure for obtaining user consent from the UE prior to enabling or activating UP data collection.

[0073] The NF that receives the NAS message including the indication of the user consent preference (e.g., the AMF 364, the SMF 366, the PCF 358, the DCNF 342, the UDM 308) can store the user consent preference information for the UE, at the UDM 308 or the UDR 352, in the PCF 358 or the DCNF 342 of the UE, or in the UE context or UE configuration of the NF.

[0074] The method 500 optionally includes a block 506, where the UE receives, from the core network, an updated user consent preference for UP data collection. In particular, a CN node (e.g., the AMF 364, the SMF 366, the PCF 358, the DCNF 342, the UDM 308) in some cases can initiate a user consent preference update by sending, to the UE, a NAS message such as a Registration Accept message, a PDU Session Establishment Accept message, a PDU Session Modification Request Command, a DL NAS Transport message, or a dedicated, special-purpose NAS message. The NAS message can include an indication of the user consent preference for UP data collection. The indication can be one of (i) the UP data collection is allowed, (ii) the UP data collection is disallowed, or (iii) user consent for the UP data collection is pending. In the latter case, the UE can determine to update its latest user consent preference when enabling or activating UP data collection.

[0075] At block 508, the UE can store user consent preference for UP data collection in the UE context or the UE configuration.

[0076] Now referring to Fig. 6, a UE such as the UE 102 can implement a method 600 to exchange information regarding a user consent preference specific to a certain AI / ML-enabled feature, which the UE and the network can identify using a feature ID. The AI / ML-enabledPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00feature requires data collection from a UE to facilitate AI / ML model training at the CN or an AS operating in a trusted domain (e.g., in a cloud). The AI / ML inference for an AI / ML-enabled feature can take place at the UE (e.g., to develop the UE-side model 137 illustrated in Fig. 1), at an NF in the CN (e.g., to develop the CN-side model 147 illustrated in Fig. 1), or at the RAN (to develop a RAN- side model), etc.

[0077] The method 600 begins at block 603, where the UE initiates a user consent preference update. To this end, the UE retrieves, from the memory of the UE, user consent preference for UP data collection included in the UE context or the UE configuration. At block 605, the UE sends a NAS message such as a Registration Request message, a PDU Session Establishment Request message, a PDU Session Modification Request message, a UL NAS Transport message, or a dedicated, special-purpose NAS message. The NAS message includes a feature ID and an indication of the user consent preference for UP data collection. In an example implementation, the indication is one of (i) the UP data collection is allowed, (ii) the UP data collection is disallowed, or (iii) user consent for the UP data collection is pending. In the latter case, the network can determine to trigger a procedure for obtaining, from the UE, user consent for the AI / ML feature corresponding to the feature ID prior to enabling or activating UP data collection for this feature.

[0078] The NF that receives the NAS message including the feature ID and the indication of the user consent preference (e.g., the AMF 364, the SMF 366, the PCF 358, the DCNF 342, the UDM 308) can store the user consent preference information specific to the AI / ML-enabled feature for the UE, at the UDM 308 or the UDR 352, in the PCF 358 or the DCNF 342 of the UE, or in the UE context or UE configuration of the NF.

[0079] The method 600 optionally includes a block 607, where the UE receives, from the core network, an updated user consent preference for UP data collection. A CN node such as the AMF 364, the SMF 366, the PCF 358, the DCNF 342, or the UDM 308 in some cases can initiate a user consent preference update by sending, to the UE, a NAS message such as a Registration Accept message, a PDU Session Establishment Accept message, a PDU Session Modification Request Command, a DL NAS Transport message, or a dedicated, special-purpose NAS message. The NAS message can include a feature ID and an indication of the user consentPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00preference for UP data collection. The indication can be one of (i) the UP data collection is allowed, (ii) the UP data collection is disallowed, or (iii) user consent for the UP data collection is pending. In the latter case, the UE can determine to update its latest user consent preference for the AI / ML-enabled feature when enabling or activating UP data collection.

[0080] At block 608, the UE can store user consent preference for UP data collection, for the AI / ML feature corresponding to the feature ID, in the UE context or the UE configuration.

[0081] In some implementations, the NAS message the UE sends at block 605 and / or the NAS message the UE receives at block 607 includes multiple feature IDs. The NAS message can include for example a list of feature IDs to which a certain value of the user consent preference applies. Thus, the NAS message can include a list {FeaturelDl, FeatureID2, ... FeaturelDN] and a user consent value that applies to the list. In another implementation, the NAS message includes a list with respective, potentially different user consent preference values, e.g.,{ (FeaturelDl, allowed), (FeatureID2, disallowed), ... , (FeaturelDN, pending) }.

[0082] Thus, the method 600 allows the UE and the CN to exchange user consent preference information with a finer granularity, i.e., on a per-feature basis, compared to method 500.

[0083] Next. Fig. 7 illustrates a scenario 700 in which the UE 102 and the CN 110 exchange information related to user consent preferences. More generally, the scenario 700 can apply to any suitable UE and a wireless cellular system, e.g., a fifth-generation system (5GS) or a sixthgeneration system (6GS).

[0084] The UE 102 performs 710 a registration procedure to negotiate, with the network. UP data collection support. The registration procedure can generally follow the scheme of TS 23.502 clause 4.2.2.2, for example. The AMF 364 can select a PCF for the UE 102 (in this example, the PCF 358) and create 711 an association between the UE 102 and the PCF.Example enhancements to the registration request procedure, to support user consent management, are discussed below with reference to Figs. 10A and 10B.

[0085] If the network supports UE policy handling, and a triggering condition is satisfied, the PCF 358 or the DCNF 342 performs 730 a UE configuration update procedure to provision UE policies for the UE 102. The DCNF 342 can perform the UE configuration update procedurePATENT APPLICATION Attorney Docket No.: 31730 / 308899-00directly, or via the PCF 358 using an Namf_Communication_NlN2MessageTrcmsfer message to provision session management (SM) UE policies to the UE 102 via the AMF 364. The UE configuration update procedure can generally follow the scheme of TS 23.502 clause 4.2.4.3 (describing a UE configuration update procedure for transparent UE policy delivery), when the PCF 358 or the DCNF 342 determine to update the UE policy based on triggering conditions.

[0086] Examples of these triggering conditions include one or more of (i) determining, at the DCNF 342, to enable UP data collection from the UE 102 for a specific AEML-enabled feature using an AI / ML model training service at the network, (ii) receiving, at the DCNF 342, a request from an AF or another NF, (iii) determining, at the DCNF 342, to update the UE policy with information related to the user consent preference at the UE 102. Example enhancements to the UE configuration procedure, so as to support user consent preference management, are discussed below with reference to Figs. 11-17 (using URSP rules enhanced for UP data collection, using DCRP rules, etc.).

[0087] With continued reference to Fig. 7, the UE 102 and the network can use 750 DL NAS Transport messages and / or UL NAS Transport messages to exchange information related to user consent preference, as a part of user consent preference management. An example enhancement of a NAS Transport message exchange to support user consent preference management is discussed below with reference to Fig. 11.

[0088] Based on the triggering condition of the UE policy evaluation, the UE 120 can perform 760 at least some of the following: (i) evaluate UE policies enhanced for UP data collection (discussed with reference to Figs. 13A-15), (ii) determine to enforce a matched UE policy, and (iii) determine whether to perform a PDU Session Establishment or modification request procedure for UP data collection for one or more APML-enabled features (e.g., for AI / ML model training service at the network). One example triggering condition at the UE for UE policy evaluation is receiving a request from an upper layer (e.g., the application) or a lower layer (e.g., RRC, MAC, SDAP) to establish or release UP data collection. Another example triggering condition at the UE for UE policy evaluation includes receiving, from an upper layer or a lower layer, a request to obtain or update the user consent preference for UP data collection for one or more AI / ML-enabled features.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0089] The UE 102 can perform 770 a PDU Session Establishment or modification request procedure, based on the enforced UE policy enhanced for UP data collection. The PDU Session Establishment or modification request procedure can be generally similar to the procedures outlined in TS 23.502 clause 4.3.2, describing a UE-requested PDU Session Establishment for non-roaming and roaming with local breakout.

[0090] The SMF 366 can select 772 a PCF and a DCNF, such as the PCF 358 and the DCNF 342, and create an association with the PCF and the DCNF for the PDU session, so as to retrieve or update SM UE policies of the PDU Session. In general, the PCF the network assigns to the UE 102, and the PCF the network uses to manage the PDU session may be the same PCF or different PCFs. For simplicity, however, this disclosure references the same PCF 358 for both behaviors.

[0091] As part of the PDU Session Establishment or modification request procedure, the SMF 366 obtains PCC rules from the PCF 358. The PCC rules contain a UP data collection configuration information including user consent indication (as discussed in more detail below with reference to Figs. 8, 9A, and 9B). The SMF 366 configures the UPF 370 using N4 rules, which can include UP data connection information, to guide the UPF 370 with respect to routing traffic related to the AI / ML data toward the corresponding DCNF 342 address and port. The (address, port) tuple can correspond to a specific AI / ML-enabled feature.

[0092] The UE 102 receives 770 a PDU Session Establishment accept message or a PDU Session Modification command message from the network. This message can confirm the use of UP data collection for the PDU Session. The UE 102 and the network use the PDU Session Establishment or modification request procedure to exchange user consent preference for data collection for one or more AI / ML-enabled features.

[0093] An example enhancement of a PDU Session Establishment or modification procedure to support user consent preference management is discussed below with reference to Fig. 12A, 12B, and 17.

[0094] Referring still to Fig. 7, the UE 102 can request 790 one or more secure user plane connections with the DCNF 342, e.g., using Transport Layer Security (TLS) over TransmissionPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00Control Protocol (TCP) or QUIC, for UP data collection for one or more AI / ML-enabled features, based on the UE policy and the address information of the DCNF 342.

[0095] In some implementations consistent with the approach discussed with reference to Fig.7, the PCC rule information in the core network can include a UP Data collection configuration information, which includes a user consent preference indication and the corresponding DCNF address and DCNF port number for UP data collection for the corresponding AI / ML-enabled feature. Thus, for one or more AI / ML-enabled features for the UE 102, the UP data collection configuration information in the PCC rule can include a user consent preference indication for each tuple including a DCNF address and a port number. The tuple can also include the corresponding protocol ID of the secure transport layer mechanism, e.g., TLS over TCP or QUIC: AIMLFeatureN = (ADDRESSDCNF, PORTDCNF, ProtocolID).

[0096] If the user consent value indicates the consent is pending, the network can determine to initiate a procedure to obtain to user consent from the UE 102, for the specific AI / ML-enabled feature, if the UE 102 in fact determines to enable UP data collection for the AI / ML-enabled feature.

[0097] Using the information discussed above (the DCNF address and port number, the protocol ID, and the user consent indication), the SMF 366 can determine how to manage the PDU Session Establishment or modification request procedure the UE 102 initiated, and / or whether to initiate a PDU Session Modification procedure with the RAN 104 and the UPF 370 to invoke or revoke data collection for the AI / ML-enabled feature. These approaches are further discussed below.

[0098] For example, Fig. 8 illustrates a method 870 that an SMF (e.g., the SMF 366) can implement to configure a UPF (e.g., the UPF 370) for UP data collection information.According to this approach, the PCC rules information in the core network include a UP Data collection configuration information, which includes a user consent preference indication as well as the corresponding DCNF address and port number for UP data collection, for the corresponding AI / ML-enabled feature. For one or more AI / ML-enabled features at the UE, the UP data collection configuration information in the PCC rule can include user consent indicationPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00for each (ADDRESSDCNF, PORTDCNF) tuple, which also can include the protocol ID of the secure transport layer mechanism, e.g. TLS over TCP or QUIC.

[0099] Thus, at block 871, the SMF retrieves PCC rule information with the UP data collection configuration information. At block 873, the SMF obtains, from the UP data collection configuration information, the user consent indication for a tuple that also indicates the DCNF address and the port number. At block 874, the SMF determines if the user consent indication is set to “allowed,” “disallowed,” or “pending.” Using this information, the SMF can determine how to manage the PDU Session Establishment or modification request procedure the UE initiated, or whether to initiate a PDU Session Modification procedure with the RAN and UPF to invoke or revoke data collection for the AI / ML enabled feature.

[0100] If the user consent indication for the relevant AFML-enabled feature is “allowed,” the SMF at block 875 A can invoke data collection for the AI / ML-enabled feature in the PDU session. If the user consent indication for the AI / ML-enabled feature is “pending,” the SMF can query the UE to obtain user consent information for the ML-enabled feature. Finally, if the user consent indication for the AI / ML-enabled feature is “disallowed,” the SMF can revoke data collection for the AI / ML-enabled feature in the PDU session.

[0101] Fig. 9 illustrates a method 970 that an SMF (e.g., the SMF 366) can implement to configure a UPF (e.g., the UPF 358) with N4 rules based on the UP data collection information in the PCC rules. Block 971 is similar to block 871 discussed above. At block 976, the SMF determines whether the user consent indication is set to “allowed,” “disallowed.

[0102] At block 977A, when the user consent indication for the relevant AI / ML-enabled feature is “allowed,” the SMF can configure a packet detection rule (PDR) in a set of N4 rules (i.e., rules associated with the N4 interface). The PDR rule can include a DCAF address and the port number of the specific AI / ML-enabled feature, for detecting traffic that contains training data the UE collects and reports. At block 977B, when the user consent indication for the relevant AI / ML-enabled feature is “disallowed,” the SMF can deactivate the AI / ML-enabled feature at the UPF, by removing the PDR with the corresponding DCAF address and port number (if already configured).PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0103] When the UPF 370 detects traffic based on the PDR, the UPF 370 can enforce the Forwarding Action Rule (FAR) that specifies how the network should forward the detected packet. In one implementation, the UPF 370 uses the existing (legacy) FAR with settings specific to UP data collection, e.g., the destination interface specifies the network core, and the forwarding policy requires steering traffic toward the target DCNF address and port number, within the core network. In another implementation, the UPF 370 uses a special-purpose, dedicated attribute defined specifically for the purposes of supporting UP data collection. This special-purpose attribute can require in-network forwarding information for the target DCNF address and the port number, within the core network.Using a registration request procedure for user consent management

[0104] Now referring to Figs. 10A and 10B, the UE and the core network can use a registration request procedure 1010A, 1010B which can be a UE- initiated user consent preference update or network-initiated user consent preference update. These procedures 1010A, 1010B are details of procedure 710 and 711 previously described.

[0105] Referring first to Fig. 10A, the UE 102 can store a user consent preference for UP data collection, in the UE context or as a part of the UE configuration, for example. The UE 102 sends 1012A, to the AMF 364, a registration request message including the user consent preference for UP data collection. The UE 102 can also send 1012A, to the AMF 364, an indication of UE capabilities of UP data collection as a part of the 5GMM capability, for example, and a support indicator for URSP / DCRP transport using control plane as a part of a UE Policy Classmark IE. The AMF 364 can store the UE capabilities for UP data collection.

[0106] The AMF 364 performs 1013A the following: (i) send, to the UDM 308. an Nudm_UECM_Registration message to register the UE at the UDM; (ii) send, to the UDM 308, an Nudm_SDM_Get message to request to retrieve the UE subscription data from the UDM 308, and the subscription data can include UP data collection information indicating whether UP data collection is allowed; (iii) send, to the UDM 308, an Nudm_SDM_Info message or an Nudm_SDM_Notification message including the user consent preference for UP data collection, so that the UDM 308 can store the user consent preference for UP data collection as a part of the user consent subscription data, or as a part of the application data at the UDR 352.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0107] If the UE capabilities support UP data collection, and the UE subscription indicates that the UP data collection is allowed, the AMF 364 can select a PCF and a DCNF and create a PCF / DCNF association for the UE as discussed above, to handle and control UE policies. The AMF 364 can further send 1014A, to the associated PCF 358 or the DCNF 342, an Npcf JEPolicyControl Create Request message or an NdcnfJJE-DCPolicyControl Request message, including the user consent preference, the Subscription Permanent Identifier (SUPI) of the UE 102, and an indication of the UE capability for UP data collection.

[0108] The PCF 348 can send 1015A, to the AMF 364, an NpcfJJEPolicyControl Create Response message including an indication of support for UP data collection (as a corresponding IE), for the UE policy of URSP rules. Alternatively, the PCF 348 can send 1015A, to the AMF 364, a dedicated message such as an Npcf JE-DCPolicyControl Create Response message for the dedicated UE policy of DCRP rules. As yet another alternative, the DCNF 342 can send 1015A, to the AMF 364, an NdcnfJJE-DCPolicyControl Create Response message for the dedicated UE policy of DCRP rules, in response to the receiving 1014A the request message.

[0109] If the AMF 364 determines that the network supports UP data collection, e.g. for AI / ML model training at the network, the AMF 364 sends 1016A, to the UE 102, a registration accept message that includes an indication of UP data collection support (e.g., as a part of the 5GS Network Feature Support IE for AI / ML model training service such as AI / ML data collection for a UE-side model, AI / ML data collection for a RAN-side model, or AI / ML data collection for a network-side model). Otherwise, the AMF 364 does not include an indication of network support of UP data collection in the registration accept message. In some implementations, the AMF 364 also includes a cause value that explicitly indicates lack of support for UP data collection.

[0110] The procedures 1050. 1060, 1070. and 1090 are similar to the procedures 750. 760, 770, and 790, respectively.

[0111] On the other, in a scenario 1000B of Fig. 10B, the network determines the user consent preference based on the UE subscription data rather than an indication from the UE 102 (as in the scenario of Fig. 10A). The UE 102 sends 1012B, to the AMF 364, a registration request message including an indication of UE capabilities of UP data collection as a part of the 5GMMPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00capability for example, and a support indicator for URSP / DCRP transport using control plane as a part of UE Policy Classmark IE. The AMF 364 can store the UE capabilities for UP data collection.

[0112] The AMF 364 further can send 1013B, to the UDM 308, an Nudm_UECM_Registration message to register the UE 102 at the UDM 308, and an Nudm_SDM_Get message to request retrieval of UE subscription data for the UE 102 from the UDM 308. The subscription data includes UP data collection information, which indicates whether UP data collection is allowed, and additionally user consent preference for UP data collection.

[0113] If the UE capabilities support UP data collection, and the UE subscription indicates that the UP data collection is allowed, the AMF 364 can select a PCF and a DCNF and create a PCF / DCNF association for the UE as discussed above, to handle and control UE policies. The AMF 364 can further send 1014B, to the associated PCF 358 or the DCNF 342, an Npcf_UEPolicyControl Create Request message or an Ndcnf_UE-DCPolicyControl Request message, including the SUPI of the UE 102, and an indication of the UE capability for UP data collection.

[0114] The PCF 358 can send 1015B, to the AMF 364, an Npcf_UEPolicyControl Create Response message including the user consent preference for UP data collection and an indication of support for UP data collection (as a corresponding information element (IE), for the UE policy of URSP rules. Alternatively, the PCF 358 can send 1015B, to the AMF 364, a dedicated message such as an Npcf_UE-DCPolicyControl Create Response message for the dedicated UE policy of DCRP rales. As yet another alternative, the DCNF 342 can send 1015B, to the AMF 364, an Ndcnf_UE-DCPolicyControl Create Response message for the dedicated UE policy of DCRP rules, in response to receiving 1014B the request message.

[0115] If the AMF 364 determines that the network supports UP data collection, e.g. for AI / ML model training at the network, the AMF 364 sends 1016B, to the UE 102, a registration accept message that includes the user consent preference for UP data collection and indication of UP data collection support (e.g., as a part of the 5GS Network Feature Support IE for AI / ML model training service such as AI / ML data collection for a UE-side model, AI / ML dataPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00collection for a RAN-side model, or AI / ML data collection for a network-side model).Otherwise, the AMF 364 does not include an indication of network support of UP data collection in the registration accept message. In some implementations, the AMF 364 also includes a cause value that explicitly indicates lack of support for UP data collection. The UE 102 stores 1017 the user consent preference, in the UE context or as a part of the UE configuration.UL and DL NAS Transport messaging for user consent management

[0116] In some implementations, the UE 102 and the CN 110 perform user consent management using UL NAS Transport and / or DL NAS Transport messages. This NAS Transport exchange for a user consent update can be UE-initiated or network-initiated. A UE or a network node can include the user consent preference in a payload container, which can be of an existing (legacy) payload container type (e.g., a UE parameters update transparent container) or a dedicated container defined specifically to transfer user consent preference information. In other words, the container type in some implementations can operate as an indication that the includes a user consent preference update.

[0117] According to one such approach, a UE (e.g., the UE 102) initiates the user consent preference update procedure. The UE receives, from an upper layer (e.g., from an application) or a lower layer (e.g. RRC / MAC / SDAP), a request to establish UP data collection or to update the user consent preference. As discussed with reference to Fig. 11, the UE 102 sends, to the AMF 364, a UL NAS Transport message that can include an indication of the user consent preference update, a payload container type set to “UE parameters update transparent container,” and the corresponding payload container including the user consent preference for UP data collection.

[0118] The indication of the user consent preference update can be an indicator for UP data collection (e.g., with value set to “active” or “inactive”). Based on the indication of the user consent preference update and the payload container type, the AMF 364 can (i) send, to the UDM 308, an Nudm_SDM_Info message including the user consent preference for UP data collections for storage at the UDM 308 and the UDR 352, or (ii) send, to the PCF 358 and the DCNF 342, an Npcf_UEPolicyControl Create Request message or a special-purpose message such as an NdcnfJJE-DCPolicy Control Request message including the user consent preference for UP data collection.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0119] Alternatively, the UE 102 can send, to the AMF 364, a UL NAS Transport message that can include a special-purpose payload container type dedicated to conveying user consent preference, and the corresponding payload container including the user consent preference for UP data collection. Based on the payload container type, the AMF 364 can (i) send, to the UDM 308, an Nudm_SDM_lnfo message including the user consent preference for UP data collections for storage at the UDM 308 and the UDR 352, or (ii) send, to the PCF 358 and the DCNF 342, an Npcf JEPolicyControl Create Request message or a special-purpose message such as an Ndcnf JE-DCPolicyControl Request message including the user consent preference for UP data collection.

[0120] As an alternative to the approach according to which the UE initiates the user consent procedure using a UL NAS Transport message, the network can determine to obtain a user preference update from the UE 102. In this case, UDM 308 in cooperation the UDR 352, or the PCF 358 in cooperation with the DCNF 342, requests that the AMF 366 send an indication of a user consent update, in the DL NAS Transport request message. After receiving this indication, the UE can send a UL NAS Transport with a user preference update as discussed above.

[0121] In particular, referring to Fig. 11, the UE 102 can send 1112, to the AMF 364, an indication of UE capabilities of UP data collection as a part of the 5GMM capability, for example, and a support indicator for URSP / DCRP transport using control plane as a part of UE Policy Classmark IE. The AMF 364 can store 1113 the UE capabilities for UP data collection. The AMF 364 can also send 1113, to the UDM 308, an Nudm_UECM_Registralion message to register the UE at the UDM 308 and an Nudm_SDM_Get message to retrieve the UE subscription data from the UDM 308. The subscription data includes the UP data collection information indicating whether UP data collection is allowed.

[0122] If the UE capabilities support UP data collection, and the UE subscription indicates that the UP data collection is allowed, the AMF 364 can select a PCF 358 and a DCNF 342 and create a PCF / DCNF association for the UE as discussed above, to handle and control UE policies. The AMF 364 can further send 1114, to the associated PCF 358 or the DCNF 342, an Npcf_UEPolicyControl Create Request message or an Ndcnf_UE-DCPolicyControl RequestPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00message, including the user consent preference, the Subscription Permanent Identifier (SUPI) of the UE 102, and an indication of the UE capability for UP data collection.

[0123] The PCF 348 can send 1115. to the AMF 364, an Npcf JEPolicyControl Create Response message including an indication of support for UP data collection (as a corresponding IE), for the UE policy of URSP rules. Alternatively, the PCF 348 can send 1115, to the AMF 364, a dedicated message such as an Npcf JE-DCPolicyControl Create Response message for the dedicated UE policy of DCRP rules. As yet another alternative, the DCNF 342 can send 1115, to the AMF 364, an Ndcnf_UE-DCPolicyControl Create Response message for the dedicated UE policy of DCRP rules, in response to the receiving 1014A the request message.

[0124] If the AMF 364 determines that the network supports UP data collection, e.g. for AI / ML model training at the network, the AMF 364 sends 1116, to the UE 102, a registration accept message that includes an indication of UP data collection support (e.g., as a part of the 5GS Network Feature Support IE for AI / ML model training service such as AI / ML data collection for a UE-side model, AI / ML data collection for a RAN-side model, or AI / ML data collection for a network-side model). Otherwise, the AMF 364 does not include an indication of network support of UP data collection in the registration accept message. In some implementations, the AMF 364 also includes a cause value that indicates lack of support for UP data collection. The procedure 1130 can be similar to the procedure 730 discussed above with reference to Fig. 7.

[0125] Optionally, during a procedure 1150, the UDM 308 determines to obtain user consent preference from the UE 102 and sends 1151, to the AMF 364, an Nudm_SDM_Notification message that includes an indication of a user consent preference update. Alternatively (or additionally), the PCF 358 or the DCNF 342 determines to obtain user consent preference from the UE 102 and sends 1152, to the AMF 364, an Namf_Communication_NlN2MessageTransfer message that includes an indication of a user consent preference update. The AMF 364 sends 1153, to the UE 102, a DL NAS Transport message including the indication of user consent preference update.

[0126] The UE 102 configures 1154 the user consent preference based on the user consent preference update the UE 102 received 1153 from the AMF 364, or based on a local (i.e.,PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00originated at the UE 102) update of the user consent preference. The UE 102 then may determine to provide, to the network, the user consent preference for data collection.

[0127] The UE 102 sends 1155, to the AMF 364, a UL NAS transport message including the user consent preference. The AMD 364 in turn forwards 1156, to the UDM 308, the user consent preference in an Nudm_SDM_Info message or an Nudm_SDM_Notificadon message, for storing the user consent preference for UP data collection as a part of the user consent subscription data or as part of the application data, at the UDR 353.

[0128] The AMF 364 optionally forwards 1157, to the PCF 358 and the DCNF 342, the user consent preference in an Npcf_UEPolicyControl Create Request message or a dedicated message such as for example an NdcnfJJE-DCPolicyControl Request message.

[0129] The procedures 1160, 1170, and 1190 are similar to the procedures 760, 770, and 790, respectively.Using PDU Session Establishment or modification to indicate user consent

[0130] According to some implementations, a UE and a network perform user consent management using a PDU Session Establishment request procedure or a PDU Session Modification request procedure. User consent updates in this case can be UE-initiated or network-initiated. The UE or a network node can include the user consent preference in a payload container, which can be of an existing (legacy) payload container type (e.g., a UE parameters update transparent container) or a dedicated container defined specifically to transfer user consent preference.

[0131] According to one such approach, when the UE determines to establish or modify a PDU Session for UP data collection, the UE sends, to the SMF 366 via the AMF 364, a PDU Session Establishment request message or PDU Session Modification request message. The request indicates the UE capability for UP data collection, the payload container type and / or an indication of user consent update, and a payload container including the user consent preference. The user consent preference update can indicate whether UP data collection is active.

[0132] Based on the payload container type or the indication of user consent update, the SMF 366 can send, to the UDM 308, an Nudm_SDM_lnfo message including the user consentPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00preference for UP data collection, for storing at the UDR 352. Alternatively, the SMF 366 can send, to the PCF 358 and the DCNF 342, an Npcf_UEPolicyControl Create Request message or a dedicated message such as an Ndcnf_UE-DCPolicyControl Request message, including the user consent preference for UP data collection.

[0133] In particular, referring to Fig. 12A, the procedures 1210, 1230, and 1260 are similar to the procedures 710, 730 and 760 discussed above. The UE 102 then sends 1280A, to the AMF 364, a PDU Session Establishment or modification request message including an indication of the UE capability for UP data collection, the payload container type, and / or an indication of user consent preference update, and a payload container indicating the user consent preference for the data collection within the PDU Session.

[0134] If the UE capabilities support UP data collection, and the UE subscription indicates that the UP data collection is allowed, the AMF 364 forwards 1281A, to the SMF 366, the user consent preference and the UE capability indication in an Nsmf_PDUSession_CreateSMContextRequest message, so as to request an establishment or a modification of a PDU Session. Based on the payload container type or indication of user consent preference update, the SMF can further forward 1282A, to the UDM 308, the user consent preference using an Nudm_SDM_Info message, for storage at the UDR 352, or to the PCF 358 and the DCNF 354 using an Npcf_UEPolicyControl Create Request message or a dedicated message such as an Ndcnf JE-DCPolicyControl Request message. Further, based on the PCC rules including the user consent preference indication received from the PCF 358 (as discussed above), the SMF 366 can configure 1283A the UPF 370 with N4 rules, to route AI / ML related data toward the DCNF 342. The SMF 366 then responds 1284A, 1285 A to the UE 102 via AMF 364, to indicate a successful establishment or modification of the PDU Session.Procedure 1290 is similar to the procedure 790 discussed above.

[0135] Fig. 12B illustrates a scenario 1200B generally similar to that of Fig. 12A, but here the UE and the network perform a pull procedure 1270B rather than a push for user consent updates.

[0136] The procedures 1210, 1230, and 1260 are similar to the procedures 710, 730 and 760 discussed above. The UE 102 then sends 1280B, to the AMF 364, a PDU Session Establishment or modification request message including an indication of the UE capability for UP dataPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00collection. If the UE capabilities support UP data collection, and the UE subscription indicates that the UP data collection is allowed, the AMF 364 forwards 1282B, to the SMF 366, the UE capability indication in an Nsmf_PDUSession_CreateSMContextRequest message, so as to request an establishment or a modification of a PDU Session.

[0137] The SMF 366 can further forward 1282B, to the PCF 358 and the DCNF 354 using an Npcf_UEPolicyControl Create Request message or a dedicated message such as an Ndcnf_UE-DCPolicyControl Request message. Further, based on the PCC rules including the user consent indication received from the PCF 358 (as discussed above), the SMF can configure 1283B the UPF 370 with N4 rules, to route AI / ML related data toward the DCNF 342. The SMF 366 then responds 1284B, 1285B to the UE 102 via AMF 364, to indicate a successful establishment or modification of the PDU Session. The UE NAS Transport messaging 1255, 1256, and 1257 is similar to the messaging 1155, 1156, and 1157 discussed above, and procedure 1290 is similar to the procedure 790 discussed above.UE policy for URSP rules to support user consent management

[0138] In some implementations, user consent management is based on the UE policy and certain enhancements of the PDU Session Establishment request procedure or the PDU Session Modification request procedure. Referring back to Fig. 7, this approach required modifications to the UE policy provisioning procedure 730. In particular, the PCF 358 provisions the UE 102 with a UE policy of URSP, so that the relevant URSP rule includes a traffic descriptor (TD) for identifying the traffic for a PDU Session, based on the information in a route selection descriptor (RSD), generally similar to the description in TS S23.503 and TS 24.526.

[0139] According to a TD-indication-based approach discussed with reference to Fig. 13 A, the TD includes an indication for updating the user consent preference for data collection, and the Connection Capabilities (CC) field indicates a new standardized component value as UP data collection. According to the feature-specific TD-indication-based approach discussed with reference to Fig. 13B, the TD includes an indication for updating the user consent preference for data collection, for one or more AI / ML-enabled features; according to the TD-and-RSD-based approach discussed with reference to Fig. 13C, the TD includes one or more AI / ME-enabled features, and the RSD includes an indication for updating the user consent preference for dataPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00collection using the a PDU Session. According to the RSD-based approach discussed with reference to Fig. 13D, the RSD includes a UP data connection configuration with an indication for updating the user consent preference for data collection using a PDU Session.A. TD-indication based approach

[0140] According to the TD-indication-based approach, a TD includes an indication for updating user consent preference for data collection, and a Connection Capabilities (CC) parameter indicates a dedicated standardized component value as “UP data collection.” A user consent preference is for data collection using the PDU Session (based on PDU Session attributes, e.g. DNN, S-NSSAI), and the values can include “allowed,” “disallowed,” or “pending.” The user consent preference applies to all Al / ML-enabled features that use the PDU Session.

[0141] According to this approach, an URSP rule includes an indication for updating user consent preference for data collection as a new component in the URSP rule. The indication for updating the user consent preference for data collection indicates whether the UE needs to update its user consent preference of the data collection when enforcing the URSP rule based on the RSD for the traffic that is matched with the TD.

[0142] The CC component in the TD can include a dedicated standardized component value for UP data collection, e.g., for AI / ML model training at the network. For example, for UP data collection for the AI / ML model training at the network, a certain dedicated component value of the CC field can correspond to UP data collection. In this case, the UE receives a UP connection request for UP data collection from an upper layer (e.g., the application layer) or a lower layer (e.g. the RRC / MAC / SDAP layer) in order to establish a secure UP connection. In response, the UE triggers URSP rule evaluation and enforces the URSP rule that includes a CC with the component value that matches with information indicated in UP data collection request.

[0143] Table 1-1 illustrates an example TD format, with an indication for the updating user consent preference for data collection as a new component:PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00Table 1-1

[0144] Table 1-2 below illustrates an example URSP rule:PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00""""

[0145] Referring to Fig. 13A, a method 1300A can be implemented in a UE such as the UE 102 for example. At block 1312A, the UE sends, to the AMF, a registration request message including an indication of UE capabilities for UP data collection, as a part of 5GMM for example. At block 1316A, the UE receives a registration accept message including an indication of network support for UP data collection.

[0146] Next, at block 1353 A, the UE receives a DL NAS Transport message including UE policies of URSP rules enhanced for UP data collection. In particular, the TD in a URSP rule can include an indication for updating user consent preference for data collection, as discussed above. At block 1359, the UE stores the UE policies of URSP rules. At block 1361A, the UE receives, from a lower layer (e.g., RRC / MAC / SDAP) or an upper layer (application), a UP connection request indicating UP data collection, in the CC field. At block 1360, in response to the UP connection request, the UE triggers URSP rule evaluation.

[0147] At block 1363 A, the UE checks whether there is a matched URSP rule with a TD including the CC component value corresponding to UP data collection. If there is no match for a URSP rule, the UE proceeds to block 1364 and omits the PDU Session Establishment orPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00Modification procedure. In some implementations, the UE replies to the UP connection request and specifies a cause such as “no matched URSP rule found,” “lacking stored UP data collection configuration,” or “no support of UP data collection for the AI / ML enabled feature,” for example.

[0148] Otherwise, when there is a matched URSP rule with the CC indicating UP data collection, the flow proceeds to block 1380A. At block 1380A, based on the RSD indicated in the matched URSP rule, the UE can enforce the matched URSP rule, if the user consent check for data collection using the PDU Session (based on PDU Session attributes, e.g., DNN, S-NSSAI) is set to “allowed” or “pending.” To enforce the matched URSP rule, the UE can send, to the SMF, a PDU Session Establishment request message or a PDU Session Modification command message, including the user consent preference with the value set to “allowed” or “pending.”

[0149] At block 1385A, the UE can receive, from the SMF, a PDU Session Establishment Accept message or PDU Session Modification Command message. The UE obtains and stores the UP data connection configuration included in the message. The UP data collection configuration can contain a list of (DCNF address, port number) pairs, with the protocol IDs in at least some of the implementations, per an APML-enabled feature corresponding to a respective feature ID.

[0150] If the user consent preference is set to “allowed,” the network does not need to send an individual request for the update of the user consent preference for each AI / ML enabled feature before starting data collection. If the user consent preference is set to “pending,” the network needs to request an update of the user consent preference for each AI / ML enabled feature before starting data collection, e.g., using UL NAS Transport message and / or DL NAS Transport message as discussed above.

[0151] If the user consent check for data collection using the PDU Session (based on PDU session attributes, e.g., DNN, S-NSSAI) is disallowed, the UE does not enforce the matched URSP rule and skips the URSP rule.

[0152] At block 1390, the UE can request a secure user-plane connection with the DCNF, e.g., using TLS over TCP or QUIC, for UP data collection for one or more AFML-enabled features.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00B. Feature-specific TD-indication based approach

[0153] According to the feature- specific TD-indication-based approach, a TD includes an indication for updating user consent preference for data collection for one or more AI / ML-enabled features. A user consent preference is for data collection of one or more feature(s) using the PDU Session (based on PDU Session attributes, e.g., DNN, S-NSSAI, etc.), and the values similarly can include “allowed,” “disallowed,” or “pending.”

[0154] According to this approach, an URSP rule includes an indication for updating user consent preference for data collection as a new component in the URSP rule. The indication for updating the user consent preference for data collection indicates whether the UE needs to update its user consent preference of the data collection when enforcing the URSP rule based on the RSD for the traffic that is matched with the TD.

[0155] Unlike the TD-indication based approach discussed above, here the URSP rule further includes one or more feature ID for use in the PDU session for UP data collection. The feature ID can be a standardized value defined in 3GPP, or an operator-defined value.

[0156] When using an operator- defined feature ID, the network can provide the operator-defined feature ID in a new container IE included in a registration accept message, DL NAS Transport message, PDU Session Establishment request message, or PDU Session Modification Command massage.

[0157] For example, in case of UP data collection for a specific A I / ML service provided at the network, e.g., A I / ML model training for the UE-side model or A I / ML model training for the network side model, the dedicated component can indicate one or more AI / ML-enabled Feature ID(s). In this case, when the UE receives an UP connection request for UP data collection with a specific AI / ML-enabled feature ID from an upper layer or a lower layer (in order to establish a secure UP connection), the UE triggers URSP rules evaluation, and enforces the URSP rule with the TD including the A I / ML enabled feature ID(s) that matches the information indicated in UP data collection request.

[0158] Table 2-1 illustrates an example TD format consistent with this approach:PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00Table 2-1

[0159] Table 2-2 below illustrates an example URSP rule:PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00"" """"

[0160] Referring to Fig. 13B, a method BOOB can be implemented in a UE such as the UE 102 for example. Block 1312B and 1316B are similar to block 1312A and 1316A. Next, block 1353B differs from 1353 A, because the UE receives a DL NAS Transport message including UE policies of URSP rules enhanced for UP data collection for AI / ML-enabled features. In particular, the TD in a URSP rule can include an indication for updating user consent preference for data collection on a feature-specific basis, as discussed above. At block 1359, the UE stores the UE policies of URSP rules.

[0161] At block 1361B, the UE receives, from a lower layer (e.g., RRC / MAC / SDAP) or an upper layer (application), a UP connection request indicating one or more AI / ML-enabled features for UP data collection, in the CC field for example. At block 1360, in response to the UP connection request, the UE triggers URSP rule evaluation.

[0162] At block 1363B, the UE checks whether there is a matched URSP rule with a TD including an AI / ML enabled-feature ID against the information provided in the UP connection request. If there is no match for a URSP rule, the UE proceeds to block 1364 as previously described.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0163] Otherwise, when there is a matched URSP rule, the flow proceeds to block 1380B. At block 1380B, based on the matched TD including indication for updating user consent preference for data collection, the UE can perform the consent check. If the user consent check for data collection using the PDU Session (based on PDU Session attributes, e.g., DNN, S-NSSAI), is “allowed” or “pending” for the matched feature ID(s), the UE enforces the matched URSP rule. To enforce the matched URSP rule, the UE can send, to the SMF, a PDU Session Establishment request message or a PDU Session Modification command message, including the user consent preference with the value set to “allowed” or “pending.”

[0164] The flow completes with block 1385B and 1390 similar to blocks 1385A and 1390 from FIG. 13 A.C. TD-and-RSD-based approach

[0165] According to the TD-and-RSD-based approach, the TD indicates one or more AI / ML enabled features using feature ID(s), and the RSD includes an indication for updating user consent preference for data collection using the PDU Session. A user consent preference is for data collection of one or more feature(s) using the PDU Session (based on PDU Session attributes, e.g., DNN, S-NSSAI, etc.), and the values similarly can include “allowed,” “disallowed,” or “pending.”

[0166] According to this approach, an URSP ride includes one or more feature IDs for use in the PDU session for UP data collection. The feature ID can be a standardized value defined in 3GPP, or an operator-defined value. When using an operator- defined feature ID, the network can provide the operator- defined feature ID in a new container IE included in a registration accept message, DL NAS Transport message, PDU Session Establishment request message, or PDU Session Modification Command massage.

[0167] For example, in case of UP data collection for a specific AI / ML service provided at the network, e.g., AI / ML model training for the UE-side model or AI / ML model training for the network side model, the dedicated component can indicate one or more AI / ML-enabled Feature ID(s). In this case, when the UE receives a UP connection request for UP data collection with a specific AI / ML-enabled feature ID from an upper layer or a lower layer (in order to establish a secure UP connection), the UE triggers URSP rules evaluation, and enforces the URSP rule withPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00the TD including the AI / ML enabled feature ID(s) that matches the information indicated in UP data collection request.

[0168] Further, according to this approach, the RSD of the URSP rule includes an indication for updating user consent preference for data collection as a new component. The indication for updating user consent preference for data collection indicates whether the UE needs to update the user consent preference of the data collection using the PDU Session based on RSD for the traffic matched with the TD.

[0169] Table 3-1 illustrates an example TD format consistent with this approach:Table 3-1

[0170] Table 3-2 below illustrates an example RSD:PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00Table 3-2

[0171] Referring to Fig. 13C, a method 1300C can be implemented in a UE such as the UE 102 for example. Blocks 1312C and 1316C are similar to blocks 1312A and 1316A.

[0172] Next, at block 1353C, the UE receives a DL NAS Transport message including UE policies of URSP rules enhanced for UP data collection for AI / ML-enabled features. In particular, the TD in a URSP rule can include an indication for updating user consent preference for data collection, as discussed above. At block 1359, the UE stores the UE policies of URSP rules. At block 1361C, the UE receives, from a lower layer (e.g., RRC / MAC / SDAP) or an upper layer (application), a UP connection request indicating one or more AI / ML-enabled feature IDs for UP data collection. At block 1360, in response to the UP connection request, the UE triggers URSP rule evaluation.

[0173] At block 1363C, the UE checks whether there is a matched URSP rule with a TD including AI / ML-enabled feature IDs, by matching the URSP rule against the information included in the UP connection request. If there is no match for a URSP rule, the UE proceeds to block 1364 and omits the PDU Session Establishment or Modification procedure. In some implementations, the UE replies to the UP connection request and specifies a cause such as “no matched URSP rule found,” “lacking stored UP data collection configuration,” or “no support of UP data collection for the AI / ML enabled feature,” for example.

[0174] Otherwise, when there is a matched URSP rule, the flow proceeds to block 1380C. At block 1380C, based on the RSD indicated in the matched URSP rule and the indication for updating user consent preference for data collection, the UE can enforce the matched URSP rule, if the user consent check for data collection using the PDU Session (based on PDU SessionPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00attributes, e.g. DNN, S-NSSAI) is set to “allowed” or “pending” for the matched feature ID. To enforce the matched URSP rule, the UE can send, to the SMF, a PDU Session Establishment request message or a PDU Session Modification command message, including the feature ID and the user consent preference with the value set to “allowed” or “pending.”

[0175] Block 1385C is similar to block 1385A but specific to a feature ID..

[0176] If the user consent preference for the feature ID is set to “allowed,” the network does not need to send an individual request for the update of the user consent preference for each AI / ML enabled feature before starting data collection. If the user consent preference for the feature ID is set to “pending,” the network needs to request an update of the user consent preference for each AI / ML enabled feature before starting data collection, e.g. using UL NAS Transport message and / or DL NAS Transport message as discussed above.

[0177] If the user consent check for data collection using the PDU Session (based on PDU session attributes, e.g. DNN, S-NSSAI) is disallowed, the UE does not enforce the matched URSP rule and skips the URSP rule.

[0178] At block 1390, the UE can request a secure user-plane connection with the DCNF, e.g., using TLS over TCP or QUIC, for UP data collection for one or more AI / ML-enabled features.D. RSD-based approach

[0179] According to the RSD-based approach, the RSD includes a UP data connection configuration with an indication for updating a user consent preference for data collection using a PDU session. A user consent preference is for data collection of one or more feature(s) using the PDU Session (based on PDU Session attributes, e.g. DNN, S-NSSAI, etc.), and the values similarly can include “allowed,” “disallowed,” or “pending.”

[0180] The RSD includes a dedicated component of UP data connection configuration. This component can include one or more pairs of (DCAF address, port number) values, with a user consent preference indication. According to one such implementation, the UE will not request UP data collection with a PDU Session, unless the RSD indicates UP data collection, and the network will not route the related traffic, unless the RSD refers to this traffic.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0181] When the UE matches the TD of an URSP rule, the UE enforces the URSP rule to establish or modify a PDU Session based on the information indicated in the RSD. After establishing or modifying the PDU session, the UE can continue to request one or more UP data connections using TLS over TCP or QUIC with DCNF(s) for UP data collection within the PDU session, as the RSD indicates.

[0182] Table 4-1 illustrates an example RSD format consistent with this approachTable 4-1

[0183] Table 4-2 illustrates an example URSP rule:PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00"" """"Table 4-2

[0184] Referring to Fig. 13D, a method 1300D can be implemented in a UE such as the UE 102 for example. Blocks 1312D and 1316D are similar to 1312A and 1316A.

[0185] Next, block 1353D and 1359 are similar to 1353B and 1359 from Fig. 13B. At block 1361D, the UE receives, from a lower layer (e.g., RRC / MAC / SDAP) or an upper layer (application), a UP connection request indicating one or more AI / ML-enabled feature IDs for UP data collection. At block 1360, in response to the UP connection request, the UE triggers URSP rule evaluation.

[0186] At block 1363D, the UE checks whether there is a matched URSP rule with a TD by matching he URSP rule against the information provided in the UP connection request. The information can include an application identifier, IP descriptors (each of which can include a set of IP 3-tuples as defined in 3GPP TS 23.503). the destination IP address, the destination port number, and the protocol in use above the IP, non-IP descriptors (i.e. destination information of non-IP traffic), DNN, connection capabilities (e.g. set as UP data collection), domain descriptorsPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00(i.e. destination FQDN(s) or a regular expression as a domain name), PIN ID, connectivity group ID, etc.

[0187] If there is no match for a URSP rule, the UE proceeds to block 1364 as previously described.

[0188] Otherwise, when there is a matched URSP rule, the flow proceeds to block 1380D. At block 1380D, based on the RSD indicated in the matched URSP rule and the indication for updating user consent preference for data collection, the UE can enforce the matched URSP rule, if the user consent check for data collection using the PDU Session (based on PDU Session attributes, e.g., DNN, S-NSSAI) is set to “allowed” or “pending” for the matched feature ID. To enforce the matched URSP rule, the UE can send, to the SMF, a PDU Session Establishment request message or a PDU Session Modification command message, including the feature ID and the user consent preference with the value set to “allowed” or “pending.”

[0189] At block 1385D, the UE obtains and stores the UP data connection configuration in the PDU Session Establishment Accept message or PDU Session Modification Command message. The UP data collection configuration contains a list of DCNF address and port number pair with the protocol ID per AI / ML-enabled feature, which may be further identified by feature ID. The network handles the user preference consent values for the feature ID similar to block 1385A discussed above

[0190] At block 1390D, the UE performs a user consent check and determines whether to establish a secure UP data connection with the a DCNF.

[0191] Fig. 14 is a messaging diagram of an example scenario 1400 in which a UE uses one of the techniques of Figs. 13A-D. The messages 1412-1416 of the procedure 1410 are similar to the messages in box 1110 discussed above with reference to Fig. 11. A UE Configuration Update procedure for data collection 1430 includes the PCF 358 and the DCNF 342 determining 1431 to update UE policy with enhancement for user consent preference management from the UE 102. The UE policies can be URSP rules or a dedicated DCRP rules, as discussed below.

[0192] If the network supports UE policy handling and the triggering condition is satisfied, the PCF 358 and the DCNF 342 continue performing 1430 the UE Configuration Update procedurePATENT APPLICATION Attorney Docket No.: 31730 / 308899-00and send 1432, to the AMF 364, an Namf_Communication_N 1 N2MessageTransfer message, to provision UE policies for the UE 102. More specifically, the DCNF 342 can perform 1430 the UE Configuration Update procedure directly or via the PCF 358 using the Namf_Communication_NlN2MessageTransfer message to provision the UE 102 with Session Management UE policies via the AMF 364. This procedure can include the techniques described in TS 23.502 clause 4.2.4.3, when the PCF 358 and / or the DCNF 342 decides to update UE policy based on triggering conditions.

[0193] The AMF 364 then sends 1433, to the UE 102, a DL NAS Transport message including UE policy, in a payload container. The payload container type in the DL NAS message can be the “UE policy container” or a dedicated “UE policy for Data collection container” type. The procedures 1460, 1470, and 1490 can be similar to the procedures 760. 770, and 790 discussed above with reference to Fig. 7.Dedicated UE policy for DCRP rules

[0194] According to this approach, user consent management is based on the configuration of the UE policy for dedicated DCRP rules and on modifications to the PDU Session Establishment request procedure (or the PDU Session Modification request procedure) to support the user consent preferences. The UE and the network can support the UE policy for dedicated DCRP rules during the UE configuration update procedure 730 illustrated in Fig. 7, for example.

[0195] Generally speaking, the PCF 358 or the DCNF 342 provisions the UE 102 with a UE policy of a dedicated DCRP rule. The DCRP rule includes a TD for identifying traffic for the PDU Session, based on the information indicated in DC routing selection descriptor (DC-RSD) with structure similar to a URSP rale.

[0196] Some of the differences between the techniques discussed with reference to Figs. 13A-D and the DCRP-rale approach include following: (i) a DCRP rule applies solely for traffic routing for UP data collection service provided by the network; (ii) the UE triggers DCRP rale evaluation when the UE receives UP data collection request from an upper layer or a lower layer: (iii) during a Registration Request procedure, (a) the UE sends a Registration Request message including the UE capabilities for UP data connection, the UE capabilities for handling UE policy for DCRP rules, or both, in a 5GMM IE, and (b) the AMF indicates support for UP dataPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00connection, support of UE policy for DCRP rules, or both, in a Registration Accept message, if the network supports UP data connection and / or UE policy for DCRP rules; (iii) when performing a UE Configuration Update procedure for data collection, the network and the UE can use a DL NAS Transport message that includes the UE policy of DCRP rules in a payload container, and the payload container type can corresponding to the “UE policy container” type or to the dedicated “UE policy for Data collection container” type.

[0197] In particular, referring to Fig. 15, in a scenario 1500 and procedure 1510, the UE 102 sends 1512, to the AMF 364, a Registration Request message including UE capabilities for UP data collection as a part of the 5GMM capability, for example. The Registration Request message further includes a support indicator for DCRP transport using control plane, as a part of a UE Policy Classmark I, for example.

[0198] The AMF 364 stores 1513, at the UDM 308, the UE capabilities for UP data collection as well as the support indicator for DCRP rales. The AMF 364 can retrieve 1513 the subscription data from the UDM 308. The UE subscription data include session management subscription data including the UP data collection information, which indicates whether a PDU session for UP data collection is allowed.

[0199] If the UE capabilities support UP data collection, handling a UE policy for DCRP rales, or both, and the UE subscription indicates that establishing a PDU Session for UP data collection is allowed, the AMF 364 selects a PCF and a DCNF (in this example, the PCF 358 and the DCNF 342) and creates a PCF / DCNF association for the UE 102, to handle and control UE policies. The AMF 364 sends 1514, to the PCF 358 and the DCNF 342, aNpcf_UEPolicyControl Create. Request message (or an Ndcnf_UE-DCPolicy Control Create Request message) including the SUPI of the UE and an indication of UE capability for UP data collection. The PCF 358 can send 1515, to the AMF 364, an NpcfJJEPolicyControl Create Response message including an indication of network support for DCRP rules. The PCF 358 and the DCNF 342 associated with the UE 102 can register the address information with the binding service function (BSF) (not shown).

[0200] If the AMF 364 determines that the network supports UP data collection and the UE policy for UP data collection, e.g. for AI / ML model training service at the network, the AMFPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00364 sends 1516, to the UE 102, a Registration Accept message including an indication of UP data collection support (e.g., as a part of the 5GS Network Feature Support IE for AI / ML model training service such as AI / ML data collection for a UE-side model, AI / ML data collection for a RAN-side model, or AI / ML data collection for a network-side model). Otherwise, the AMF 364 does not include an indication of network support of UP data collection and / or network support of DCRP rules in the Registration Accept message, and instead can include a cause value to explicitly indicate lack of support for UP data collection and / or for DCRP rules.

[0201] With continued reference to Fig. 15, the procedure 1530 can include events 1431-1433 discussed above, except that the UE policies in this case relate to dedicated DCRP rules rather than URSP rides. If the network supports UE policy for DCRP rules handling, the PCF 358 or DCNF 342 performs 1530 the UE configuration update procedure to provision the UE 102 with UE policies of the DCRP rales, which indicate user consent preference in a TD and / or an RSD. The DCNF can 342 perform 1530 the UE configuration update procedure directly or via PCF 358 using an Namf_Communication_NlN2MessageTransfer message. In any case, the DCNF 342 provisions the UE 102 with session management UE policies of DCRP rules (which can be generally similar to TS 23.502 clause 4.2.4.3), when the PCF 358 or the DCNF 342 determines to update the UE policy of DCRP rales based on triggering conditions for UP data collection. A triggering condition can be, for example, the DCNF 342 determining (or receiving, from the AF or another NF, a request) to enable UP data collection from the UE 102 for enabling, disabling, or updating a specific AI / ML enabled feature, e.g., for AI / ML model training service at the network. Another triggering condition can be the DCNF 342 determining to obtain an update of user consent preference from the UE 102.

[0202] Procedures 1560, 1570, and 1590 are similar to the procedures 760, 770, and 790. respectively, discussed above with reference to Fig. 7.Dedicated DCRP rales provisioned at the PDU session level

[0203] In some implementations, user consent preference management is based on providing a UE with a UE policy for dedicated DCRP rules in a PDU Session Establishment Accept message or a PDU Session Modification Command message, during a PDU Session Establishment procedure or a PDU Session Modification procedure, and based on the user consent preferencePATENT APPLICATION Attorney Docket No.: 31730 / 308899-00discussed above. In this implementation, the DCRP rule includes a traffic descriptor (TD) for identifying the traffic to be applied for the PDU Session based on information indicated in a DC-RSD with a similar structure as the URSP rule.

[0204] According to this approach, a URSP rule can include a UP data collection indication in the RSD. When this indication is present, the PDU Session indicated in the RSD is dedicated exclusively to UP data collection. The UE may include the UP data collection indication or specify the PDU Session type as “data collection” in a PDU Session Establishment Request message or a PDU Session Modification Request message.

[0205] When the UE determines to establish a PDU Session for data collection, the UE indicates that its UP data collection capabilities include the capability to use the UP data collection functionality in a PDU Session Establishment Request or a PDU Session Modification request message. If the network supports and determines to enable UP data collection for a PDU session, the UE can receive a UP data collection PDU session information IE in a PDU Session Establishment Accept or a PDU Session Modification Command message. The UP data collection PDU session information IE can include the following information: (i) a UP data connection support confirmation, (ii) a DC PDU Session Type, which specifies whether the established PDU Session is for UP data collection (if yes, the UE is allowed to trigger a UP data connection within a PDU session), (iii) one or more feature IDs. which can be 3GPP-defined. for specific APML-enabled service(s) the network provides within the PDU session, e.g. AI / ML model training at the network.

[0206] The UE can obtain, from the SMF in a PDU Session Establishment Accept message or a PDU Session Modification Command message, DCRP rules for identifying traffic based on the TD, for application to the PDU Session with components indicated in the DC-RSD. Based on the DCRP rules, the UE can request a UP data connection using TLS over TCP or QUIC, with a DCNF for UP data collection, within the PDU session. The UE can obtain a 3GPP-defined feature ID for a specific AI / ML enabled service the network provides within the PDU session, e.g.. AI / ML model training at the network, from the PDU Session Establishment Accept message or the PDU Session Modification Command message.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0207] A DCRP rule can include the following information: (i) a rule identifier, which can be unique identifier for the DCRP Rule; (ii) an indication of rule precedence, which determines the order in which the UE evaluates the DCRP rule relative to other rules; (iii) a TD that specifies traffic description components for the DCRP rule, which can be similar to the TD of a URSP rule and also include the feature ID of the UP data connection, which can be the feature ID the upper layer or the lower layer requests for application to the UP data connection in the given PDU Session); and (iv) a DC-RSD that includes components for the DCRP rule when the traffic matches the components indicated in the TD.

[0208] A DC-RSD in turn can include a UP data connection configuration that includes one or more (DCAF address, port number) pairs for the matched feature ID indicated in the TD. The UE can randomly choose one of the pairs to set up the UP data connection for the feature ID indicated in the TD for UP data collection. The DC-RSD further can include an indication of the user consent preference, which in some implementations can apply to all features in the TD for the PDU session, and in other implementations can apply for the AI / ML-enabled features in the PDU session, per features IDs in the TD.

[0209] Now referring to Fig. 16, a scenario 1600 begins with procedures 1610, 1630, and 1660 generally similar to the procedures 710, 730, and 760, respectively. As a part of a PDU Session Establishment or modification request procedure 1670. the UE 102 sends 1680, to the SMF 366 via the AMF 364, a PDU Session Establishment Request message or a PDU Session Establishment Request message including a capability for UP data collection capability. The AMF 364 can forward 1681 this information to the SMF 366 using a Nsmf_PDUSession_CreateSMContext Request message.

[0210] The SMF 366 requests 1682 DCRP rules from the DCNF 342. To this end, the SMF 366 can send 1682 an Ndcnf_UE_DCPolicy Request message directly, or via the PCF 358 using an Npcf_UE_DCPolicy Request message, or via the PCF 358 via using an Npcf_UE_Policy Request message with an indication of UP data collection. In any case, the SMF 366 can include the UE capability for data collection. The DCNF 342 then can return 1682 the DCRP rules in an Ndcnf_UE_DCPolicy Response message directly, or via the PCF 358 using an Npcf_UE_DCPolicy Response message, or via the PCF 358 using an Npcf_UE_Policy RequestPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00message using a DCRP rules container. When the PCF 358 provisions DCRP rules, the PCF 358 can use an Ndcnf_UE_DCPolicy Request message to request the DCRP rules from the DCNF 342 and receive the DCRP rules in an Ndcnf_UE_DCPolicy Request message.

[0211] The SMF 366 also obtains 1683, from the PCF 358, PCC rales that contain the UP data collection configuration information, and configures 1683 the UPF 358 using N4 rules that include the UP data connection information. The N4 rules can guide the UPF 358 to route the relevant AI / ML traffic towards the corresponding DCNF address and port, for the specific AI / ML-enabled feature.

[0212] The SMF 366 then provisions 1684, 1685 the DCRP rules to the UE 102, via the AMF 364 using an N smf_P DU Session_CreateSMContext Response message that includes the DCRP rales. The UE 102 receives 1685, from the network, a PDU Session Establishment Accept message or a PDU Session Modification Command message including the DCRP rules. The DCRP rales provide the UE 102 with guidance for UP data collection within the PDU session and based on the user consent preference associated with the UE 102.

[0213] The UE 102 evaluates 1688 the DCRP rales. When the UE detects 1688 a matching TD of a DCRP rale, the UE 102 determines whether to enforce the DC-RSD by requesting one or more secure UP data connections, using TLS over TCP or QUIC, with DCNF(s) as indicated in DC-RSD, based on the UE checking the user consent preference. The UE 102 also may send 1655 a UL NAS Transport message to update 1656, 1657 the user consent preference, similar to the events 1155-1157 discussed above. The UE 102 then starts 1690 to transmit the required data, if the UE 102 successfully sets up a secure UP data connection.

[0214] Finally, referring to Fig. 17, a method 1700 can be implemented in a UE such as the UE 102. At block 1712, the UE sends, to the AMF, a registration request message including an indication of UE capabilities for UP data collection, as a part of the 5GMM for example. At block 1716, the UE receives a registration accept message including an indication of network support for UP data collection.

[0215] At block 1753, the UE receives a DL NAS Transport message including UE policies of URSP rules enhanced for UP data collection. At block 1759, the UE stores the UE policies of URSP rules. Next, at block 1761, the UE receives a UP connection request for UP dataPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00collection from a lower layer (RRC / MAC / SDAP) or an upper layer (application) and, at block 1760, the UE triggers URSP rules evaluation.

[0216] At block 1763, the UE checks whether there is a matching URSP rule with a TD, based on a comparison with the information in UP connection request. At block 1774, when there is no matched URSP rule selected, the UE does not proceed with PDU Session Establishment or Modification request procedure. In some implementations, the UE replies to the UP connection request and specifies a cause for the rejection, e.g., “no matched URSP rule found,” “no stored UP data collection configuration,” or “no support of UP data collection for the AUML-enabled feature.”

[0217] At block 1780, when the UE finds a matching URSP rule, the UE enforces the matched URSP rule (which includes an RSD with a UP data collection indication) by sending a PDU Session Establish Request message or a PDU Session Modification Request message with a UP data collection indication. When the UE includes this indication, the UE and the network can interpret the PDU session as being dedicated exclusively to UP Data collection. The UE receives and stores 1781 DCRP rules for the PDU Session, included in PDU Session Establishment Accept or PDU Session Modification Command message. Finally, blocks 1785 and 1790 are similar to the blocks 1685 and 1690 discussed above.

[0218] The following list of examples reflects a variety of the embodiments explicitly contemplated by the present disclosure.

[0219] Example 1. A method implemented in a user equipment (UE), the method comprising: determining a user consent preference with respect to data collection; and communicating, with a core network (CN) and in a non-access stratum (NAS) message, an indication of the user consent preference.

[0220] Example 2. The method of claim 1, wherein: the determining of the user consent preference includes retrieving the user consent preference from a UE context or a UE configuration stored at the UE; and the communicating of the user consent preference includes transmitting, to the CN, the indication of the user consent preference.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0221] Example 3. The method of claim 1, wherein the NAS message is a Registration Request message.

[0222] Example 4. The method of claim 3, wherein the Registration Request message includes an indication of UE capabilities with respect to data collection.

[0223] Example 5. The method of claim 3, further comprising: receiving, from the CN and in response to the Registration Request message, a Registration Response message including an indication of whether the CN supports the data collection.

[0224] Example 6. The method of claim 1, wherein the NAS message is a NAS Transport message.

[0225] Example 7. The method of claim 6, further comprising: including the indication of the user consent preference in a container of a type associated with updating UE parameters.

[0226] Example 8. The method of claim 6, further comprising: including the indication of the user consent preference in a container of a type dedicated to transferring the user content preference.

[0227] Example 9. The method of any of claims 6-8, wherein: the transmitting of the UL NAS Transport message is in response to receiving, from an upper layer or a lower layer, a request to establish the data collection.

[0228] Example 10. The method of any of claims 6-8, wherein: the transmitting of the NAS Transport message is in response to receiving, from an upper layer or a lower layer, a request to update the user consent preference

[0229] Example 11. The method of any of claims 6-10, wherein the NAS Transport message is an uplink (UL) NAS Transport message.

[0230] Example 12. The method of claim 11, wherein the UL NAS Transport message is a packet data unit (PDU) Session Establishment Request message.

[0231] Example 13. The method of claim 1, wherein the NAS message is a PDU Session Establishment Request message or a PDU Session Modification Request message.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0232] Example 14. The method of claim 13, further comprising: including the indication of the user consent preference in a container of a type associated with updating UE parameters.

[0233] Example 15. The method of claim 13, further comprising: including the indication of the user consent preference in a container of a type dedicated to transferring the user content preference.

[0234] Example 16. The method of any of claims 13-15, wherein the PDU Session Establishment Request message or the PDU Session Modification Request message includes an indication of UE capabilities with respect to data collection.

[0235] Example 17. The method of claim 1, wherein: the communicating of the user consent preference includes receiving, from the CN, an indication that the UE is to report the user consent preference.

[0236] Example 18. The method of claim 1, wherein the NAS message is a Registration Accept message.

[0237] Example 19. The method of claim 18, further comprising: transmitting, to the CN, a Registration Request message including an indication of UE capabilities with respect to data collection.

[0238] Example 20. The method of claim 1, wherein the NAS message is a downlink (DL) non-access stratum (NAS) Transport message.

[0239] Example 21. The method of claim 20, wherein: the indication of the user consent preference is included in a container of a type associated with updating UE parameters.

[0240] Example 22. The method of claim 20, wherein: the indication of the user consent preference is included in a container of a type dedicated to transferring the user content preference.

[0241] Example 23. The method of claim 1, wherein the NAS message is a PDU Session Establishment Accept message or a PDU Session Modification Command message.

[0242] Example 24. The method of claim 23, wherein: the indication of the user consent preference is included in a container of a type associated with updating UE parameters.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0243] Example 25. The method of claim 23, wherein: the indication of the user consent preference is included in a container of a type dedicated to transferring the user content preference.

[0244] Example 26. The method of claim 1, wherein: the user consent preference pertains to a particular feature that requires data collection.

[0245] Example 27. The method of claim 26, wherein: the feature is associated with a feature identifier (ID), and the communicating of the user consent preference includes communicating the feature ID.

[0246] Example 28. The method of claim 27, wherein the feature ID is operator-defined.

[0247] Example 29. The method of any of claims 26-28, wherein: the feature is an artificial intelligence (AI) / machine learning (ML)-enabled feature.

[0248] Example 30. The method of claim 29, wherein the AVML-enabled feature corresponds to training an AVML model.

[0249] Example 31. The method of any of claims 1 or 13-16, further comprising: receiving, from the CN, a configuration of a UE policy related to the data collection; determining to report the user consent preference to the CN uses the configuration of the UE policy.

[0250] Example 32. The method of claim 5, wherein the receiving of the configuration of the UE policy includes: receiving, from the CN, a policy rule, wherein the policy rule includes an indication that the UE is to update the user consent preference for the data collection if the selection policy rule is enforced.

[0251] Example 33. The method of claim 32, wherein: a connection capabilities (CC) field in a Traffic Descriptor (TD) of the policy rule includes a value indicating the data collection.

[0252] Example 34. The method of claim 33, wherein the receiving of the configuration of the UE policy includes: receiving, from the CN, a policy rule, wherein a TD of the selection policy rule includes: an indication that the UE is to update the user consent preference for the data collection if the selection policy rule is enforced, and a feature identifier (ID) that identifies a feature to which the data collection pertains.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0253] Example 35. The method of claim 33, wherein the receiving of the configuration of the UE policy includes: receiving, from the CN, a policy rule, wherein: a TD of the selection policy rule includes a feature ID that identifies a feature to which the data collection pertains, and a Route Selection Descriptor (RSD) of the selection policy rule includes an indication that the UE is to update the user consent preference for the data collection if the selection policy rule is enforced.

[0254] Example 36. The method of claim 33, wherein the receiving of the configuration of the UE policy includes: receiving, from the CN, a selection policy rule, wherein: an RSD of the selection policy rule includes a data connection configuration comprising: (i) an address of a network node to which the UE is to direct traffic associated with the data collection, (ii) a port of the network node, and (iii) the user consent preference.

[0255] Example 37. The method of claim 36, wherein data connection configuration pertains to specified one or more features that require data collection.

[0256] Example 38. The method of any of claims 32-37, wherein the policy rule is a User Equipment Route Selection Policy (URSP) rule.

[0257] Example 39. The method of any of claims 32-37, wherein the policy rule is a Data Collection Routing Rule (DCRP) rule dedicated to the data collection.

[0258] Example 40. The method of claim 39, further comprising: transmitting, to the CN and in a Registration Request message, an indication of UE capabilities with respect to DCRP rule handling.

[0259] Example 41. The method of claim 40, further comprising: receiving, from the CN and in a Registration Accept message, an indication that the CN supports the DCRP rule handling.

[0260] Example 42. The method of any of claims 39-41, further comprising: triggering evaluation of the DCRP rule in response to a request from an upper layer or a lower layer.

[0261] Example 43. The method of any of claims 31-42, wherein the receiving of the configuration of the UE policy includes: receiving a UE Configuration Update command during a UE Configuration Update procedure.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0262] Example 44. The method of claim 1, further comprising: receiving, from the CN and in a message related to a PDUs session, a configuration of the UE policy related to the data collection; and determining to report the user consent preference of the enforced policy rale uses the configuration of the UE policy.

[0263] Example 45. The method of claim 44, wherein the message related to the PDU session is a PDU Session Establishment Accept message.

[0264] Example 46. The method of claim 44, wherein the message related to the PDU session is a PDU Session Modification Command message.

[0265] Example 47. The method of any of claims 44-46, wherein the receiving of the configuration of the UE policy includes: receiving, from the CN, a selection policy rale.

[0266] Example 48. The method of claim 47, wherein the policy rule is a DCRP rule dedicated to the data collection.

[0267] Example 49. The method of any of the preceding claims, wherein: wherein the indication of the user consent preference contains one of (i) an allowed value, (ii) a disallowed value, or (iii) a pending value.

[0268] Example 50. The method of claim 49, wherein the pending value corresponds to a requirement that the CN request user consent from the UE prior to initiating the data collection, or the UE update the user consent preference prior to enabling the data collection at the UE.

[0269] Example 51. The method of claim 49, wherein the indication of the user consent preference corresponds to a feature ID.

[0270] Example 52. The method of any of the preceding claims, wherein the data collection is user-plane (UP) data collection.

[0271] Example 53. A user equipment (UE) comprising: a transceiver; and processing hardware; the UE configured to implement a method of any of the preceding claims.

[0272] Example 54. A method implemented in a Session Management Function (SMF) of a core network (CN) of a cellular communication system, the method comprising: establishing, for a user equipment (UE), a packet data unit (PDU) session, including obtaining a configurationPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00for user plane (UP) data collection, the configuration including an indication of user consent preference with respect to the UP data collection; and configuring one or more rules for routing traffic associated with the UP data collection, in view of the indication of the user consent preference.

[0273] Example 55. The method of claim 54, wherein to obtain the configuration for the UP data collection, the SMF receives, from a Policy Control Function (PCF), a Policy and Charging Control (PCC) ride.

[0274] Example 56. The method of claim 54 or 55, wherein the configuration for the UP data collection indicates: (i) an address of a network node to which the UE is to direct traffic associated with the UP data collection, and (ii) a port of the network node.

[0275] Example 57. The method of claim 56, wherein the configuration for the UP data collection indicates a protocol identifier (ID) of a secure transport layer mechanism.

[0276] Example 58. The method of claim 56, wherein the network node is a Data Collection Network Function (DCNF).

[0277] Example 59. The method of any of claims 54-58, wherein: the indication of the user consent preference pertains to a particular feature that requires data collection.

[0278] Example 60. The method of any of claims 54-58, wherein: the indication of the user consent preference pertains to a particular feature that requires data collection.

[0279] Example 61. The method of any of claims 54-60, further comprising: in response to determining that user consent preference indicates the UP data collection is allowed, configure the UP data collection in the PDU session.

[0280] Example 62. The method of any of claims 54-60, further comprising: in response to determining that user consent preference indicates the UP data collection is not allowed, prevent the PDU session from including the UP data collection.

[0281] Example 63. The method of any of claims 54-60, further comprising: in response to determining that user consent preference indicates the UP data collection is pending, query the UE for an update of the user consent preference.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00

[0282] Example 64. An apparatus comprising processing hardware and configured to implement a method of any of claims 54-63.Additional considerations

[0283] As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).

[0284] A user device in which the techniques of this disclosure can be implemented (e.g., the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media- streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0285] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may can be software modules (e.g., code, or machine-readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application- specific integrated circuit (ASIC), aPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0286] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more specialpurpose processors.

Claims

PATENT APPLICATION Attorney Docket No.: 31730 / 308899-00What is claimed is:

1. A method implemented in a user equipment (UE), the method comprising: determining a user consent preference with respect to data collection; and communicating, with a core network (CN) and in a non-access stratum (NAS) message. an indication of the user consent preference.

2. The method of claim 1, wherein:the determining of the user consent preference includes retrieving the user consent preference from a UE context or a UE configuration stored at the UE; andthe communicating of the user consent preference includes transmitting, to the CN, the indication of the user consent preference.

3. The method of claim 2,wherein the NAS message is a Registration Request message; the method further comprising:receiving, from the CN and in response to the Registration Request message, a Registration Response message including an indication of whether the CN supports the data collection.

4. The method of claim 1, wherein:the communicating of the user consent preference includes receiving, from the CN, an indication that the UE is to report the user consent preference.

5. The method of any of the preceding claims, wherein:the user consent preference pertains to a particular feature that requires data collection.

6. The method of claim 5, wherein:the feature is associated with a feature identifier (ID), andPATENT APPLICATION Attorney Docket No.: 31730 / 308899-00the communicating of the user consent preference includes communicating the feature ID.

7. The method of any of the preceding claims, further comprising:receiving, from the CN, a configuration of a UE policy related to the data collection; determining to report the user consent preference to the CN using the configuration of the UE policy.

8. The method of claim 7, wherein the receiving of the configuration of the UE policy includes:receiving, from the CN, a policy rule,wherein the policy rule includes an indication that the UE is to update the user consent preference for the data collection if the policy rule is enforced.

9. The method of claim 7, wherein the receiving of the configuration of the UE policy includes:receiving, from the CN, a policy rule,wherein a traffic descriptor (TD) of the policy rule includes a feature identifier (ID) that identifies a feature to which the data collection pertains; andone of the TD or a Route Selection Descriptor (RSD) of the policy rule includes an indication that the UE is to update the user consent preference for the data collection if the policy rule is enforced.

10. The method of claim 1, further comprising:receiving, from the CN and in a message related to a PDUs session, a configuration of the UE policy related to the data collection; anddetermining to report the user consent preference of the policy rule uses the configuration of a UE policy.PATENT APPLICATION Attorney Docket No.: 31730 / 308899-0011. A method implemented in a Session Management Function (SMF) of a core network (CN) of a cellular communication system, the method comprising:establishing, for a user equipment (UE), a packet data unit (PDU) session, including obtaining a configuration for user plane (UP) data collection, the configuration including an indication of user consent preference with respect to the UP data collection; and configuring one or more rules for routing traffic associated with the UP data collection, in view of the indication of the user consent preference.

12. The method of claim 11, wherein to obtain the configuration for the UP data collection, the SMF receives, from a Policy Control Function (PCF), a Policy and Charging Control (PCC) rule.

13. The method of claim 11 or 12, wherein the configuration for the UP data collection indicates:(i) an address of a network node to which the UE is to direct traffic associated with the UP data collection, and(ii) a port of the network node.

14. The method of any of claims 11-13, wherein:the indication of the user consent preference pertains to a particular feature that requires data collection.

15. An apparatus comprising processing hardware and configured to implement a method of any of the preceding claims.

Images