User equipment policy for handling data collection within a network

Abstract

Methods for data collection within a network are described. A method implemented in a user device (UE) can include receiving, from a core network (CN), a Data Collection Routing Policy (DCRP) rule related to user-plane (UP) data collection. The method can include transmitting, to the CN, UP data according to the DCRP rule. Apparatuses for performing these methods are also described.

Description

PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 USER EQUIPMENT POLICY FOR HANDLING DATA COLLECTION WITHIN A NETWORKCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to and the benefit of the filing date of provisional U.S. Patent Application No. 63 / 745,308 entitled “User equipment policy for handling data collection within a network,” filed on January 14, 2025. The entire content of the provisional application is hereby expressly incorporated herein by reference.FIELD OF THE DISCLOSURE

[0002] This disclosure relates generally to wireless communication systems, and particularly to user equipment policies for handling user-plane data collection within a network for artificial intelligence and machine learning model training.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 Third Generation Partnership Project (3 GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR.). An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), and user equipment UE. The 5G NR architecture seeks to provide increased data rates, decreased latency, and increased capacity compared to previous generation cellular communication systems.Recently, to support these and other initiatives, operators have applied artificial intelligence (Al) and machine learning (ML) to wireless communications.

[0005] To better support AI / ML in wireless communication networks, 3GPP is studying ways to enable 5GC and air interface intelligence in terms of data collection, ML model training,PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 analytics inference, and other considerations. To support cross domain (i.e., UE, RAN, 5GC, OAM and AF) collaborative AI / ML mechanisms, 5G systems (6G systems and beyond) should perform cross-domain coordination to characterize AI / ML functionalities. For example, in systems contemplating training data collection for a UE-side model that performs inference entirely at the UE, 3 GPP is studying whether and how to support UE data collection to meet requirements for RAN Al support for air interface operation for UE-side model training documented in 3 GPP TR 38.843.

[0006] Training data collection can apply to various 3GPP system features and use cases across different domains at the RAN, core network (CN), and cloud applications. These AI / ML enabled features can enhance resource management including radio air interface management, radio resource management, RAN mobility, and CN automation. For example, AI / ML enabled features may include AI / ML-based channel state information (CSI) compression, AI / ML-based CSI prediction, AI / ML-based beam management with downlink beam prediction, AI / ML-assisted positioning for positioning accuracy enhancement, AI / ML-based network slicing, AI / ML-based coverage and capability optimization, AI / ML-based network energy saving, and AI / ML-enabled radio resource management (RRM) measurement prediction.

[0007] In some systems, a 5GS network data analytics function (NWDAF) can handle data collection for network automation aspects based on a UE application data collection framework, as described in 3GPP TS 26.531. The NWDAF can interact with a Data Collection application function (AF) (DCAF) in the trust domain of the operator’s network to collect data from UE applications as an input for analytics generation and ML Model training. The architectures defined in 3GPP TS.23.501 (4.2.3) can apply this framework such that DCAF is a data collection network function that connects with UPF via the N6 interface.

[0008] However, when considering training data collection related to AI / ML for an NR air interface such that the data collection network function (DCNF) resides in the 5GC for AI / ML model training for UE-side model inferencing, it remains unclear how the 5GC can enhance policy control and handle data collection with the UE to use an AI / ML model training service provided by the network.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0009] Moreover, considering the data volumes that the UE reports, systems using a user plane (UP)-based method may reduce or eliminate signaling storms in an end-to-end network. However, it remains unclear how the 5GC can enhance policy control and handle a UP data connection with the UE for UP data collection for use in an AI / ML model training service provided by the network.

[0010] Furthermore, it remains unclear how the 5GC can enhance policy control and handle UP data connections with the UE for UP data collection for different AI / ML enabled features. Specifically, it remains unclear how the UE and the network can coordinate to differentiate the collected data of corresponding AI / ML enabled features and route the training data to the appropriate data sink.SUMMARY

[0011] In one aspect, a method implemented in a user equipment (UE) includes receiving, from a core network (CN), a Data Collection Routing Policy (DCRP) rule related to user-plane (UP) data collection. The method further includes transmitting UP data to the CN in accordance with the DCRP rule.

[0012] In another aspect, a user equipment (UE) includes a transceiver and processing hardware. The processing hardware is configured to receive, from a core network (CN), a Data Collection Routing Policy (DCRP) rule related to user-plane (UP) data collection and transmit UP data to the CN in accordance with the DCRP rule.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate one or more embodiments and, together with the detailed description, explain these embodiments.

[0014] Fig. 1 is a block diagram of an example wireless communication system configured to support user equipment (UE) policies for handling data collection within a network;

[0015] Fig. 2 is a block diagram of an example protocol stack according to which the UE of Fig. 1 communicates with a base station and a core network;

[0016] Fig. 3 is a service-based representation of the 5GS architecture;

[0017] Fig. 4 is a reference-point based representation of a 5GS architecture;

[0018] Fig. 5 is a message sequence diagram illustrating a high-level procedure to support data collection from a UE based on a UE policy provisioned by a PCF or DCNF;

[0019] Fig. 6 is a message sequence diagram illustrating registration request enhancement for negotiation of UP data collection support;

[0020] Fig. 7 is a flow diagram of a method for traffic descriptor enhancement;

[0021] Fig. 8 is a flow diagram of a second method for traffic descriptor enhancement similar to the method of Fig. 7 and including connection capabilities information;

[0022] Fig. 9 is a flow diagram of a third method for traffic descriptor enhancement similar to the methods of Fig. 7 and Fig. 8 and including AI / ML feature IDs for model training;

[0023] Fig. 10 is a flow diagram illustrating route selection descriptor (RSD) enhancement;

[0024] Fig. 11 is a message sequence diagram illustrating an aspect including UE policies dedicated to data collection routing (DCRP) rules;

[0025] Fig. 12 is a flow diagram illustrating UE behavior regarding dedicated DCRP rules provisioned at the PDU Session level;

[0026] Fig. 13 is a message sequence diagram illustrating UE behavior regarding dedicated DCRP rules provisioned at the PDU Session level;PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0027] Fig. 14 is a flow diagram of a method performed by the UE; and

[0028] Fig. 15 is a flow diagram of another method performed by the UE.DETAILED DESCRIPTION OF THE DRAWINGS

[0029] As discussed in more detail below, a user equipment (UE) can support data collection for artificial intelligence and machine learning (AI / ML) model training using various scenarios or implementations. In one aspect, the UE receives a Data Collection Routing Policy (DCRP) rule from a core network (CN) and transmits user-plane (UP) data to the CN in accordance with the DCRP rule. The DCRP rule may include a traffic descriptor comprising a feature ID dedicated to AI / ML model training, and the feature ID can serve as a routing key that maps to a destination address and port number of a data collection network function (DCNF). This enables the UE to establish a UP data connection for transmitting training data associated with a specific AI / ML enabled feature to the appropriate DCNF. The DCRP rule may also include a data collection route selection descriptor (DC-RSD) comprising a UP security indication that indicates an allowed security mechanism. These security mechanisms can include Transport Layer Security (TLS) over Transmission Control Protocol (TCP) or TLS over Quick UDP Internet Connections (QUIC). Alternatively or additionally, the network and UE can implement messaging to negotiate UP data collection support during registration. Alternatively or additionally, traffic descriptors (TDs) in URSP rules can include descriptors for UP connections and for connection capabilities, among other possible descriptors.

[0030] Referring first to Fig. 1, an example wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, and a core network (CN) 110, which interconnect through various interfaces. In some implementations, the base stations 104 and 106 can operate in a RAN 105 connected to the core network (CN) 110. The base station 104 and / or base station 106 may provide coverage (e.g., one or more cells) via a satellite. 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 104 is an eNB, the cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell or a Narrow Band Internet of Things (NB-IoT) cell. IfPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 the base station 104 is a 6G base station, the cell 124 is a 6G cell or a 6G Internet of Things (6G-loT) cell. Similarly, the cell 126 is an NR cell, an E-UTRA or NB-IoT cell, a 6G or 6G-I0T cell, depending on whether the base station is a gNB, an ng-eNB or eNB, or a 6G base station. The cells 124 and 126 can be in the same Radio Access Network Notification Areas (RNA) or different RNAs. 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 one of a 6G, 5G R (or simply, “NR”), E-UTRA and / or NB-IoT air interface to communicate with the base station 104 or 106. Each of the base stations 104, 106 can connect to the CN 110 via an interface (e.g., SI, NG, N6G interface). The base stations 104 and 106 also can interconnect via an interface (e.g., X2, Xn, or X6G interface).

[0031] The CN 110 can be implemented as an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160, for example. The CN 110 can also be implemented as a sixth generation (6G) core 180, in another example. Among other components, the EPC 111 can include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network Gateway (PGW) 116. The SGW 112 in general transfers user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 manages authentication, security activation, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network. The 5GC 160 includes a User Plane Function (UPF) 162 and an Access and Mobility Management Function (AMF) 164, and / or Session Management Function (SMF) 166. Generally speaking, the UPF 162 transfers user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF 164 manages authentication, security activation, registration, paging, and other related functions, and the SMF 166 manages PDU sessions. The 6GC 180 includes a 6G UPF 182 and a 6G AMF 184, and / or 6G SMF 186, which are similar to the UPF 162, the AMF 164 and the SMF 166, respectively, with enhanced functions. In some implementations, the NR RAN 105 connects to the 6GC 180. In other implementations, the 6G RAN 105 connects to the 5GC 160.

[0032] The CN 110 may connect to a short message service center (SMSC) 170 directly or via one or more other network nodes to provide short message services (SMS) via a control planePATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 function or a user plane function. In some implementations, to support SMS via the control plane function, the MME 114 may connect to an SMS-Gateway Mobile Switching Center (SMS-GMSC) (not shown in Fig. 1) and the SMS-GMSC connects to the SMSC 170. In other implementations, the MME 114 may connect to the SMSC 170 directly, i.e., via an interface. In some implementations, to support SMS (i.e., IMS SMS) via the user plane function, the SGW 112 or PGW 116 connects to an IMS network (not shown in Fig. 1), the IMS network connects to an Internet Protocol (IP) short message gateway (IP-SM-GW), and the IP-SM-GW connects to the SMSC. In some implementations, to support SMS via the control plane function, the AMF 164, 184 may connect to a short message service function (SMSF) (not shown in Fig. 1) and the SMSF connects to the SMSC 170. In other implementations, to support SMS (i.e., IMS SMS) via the user plane function, the UPF 162,182 connects to an IMS network (not shown in Fig. 1), the IMS network connects to the SMSF, and the SMSF connects to the SMSC 170. The IMS network may include one or more Call Session Control Function (CSCF) nodes such as Interrogating CSCF, Proxy CSCF, and / or Serving CSCF.

[0033] The CN 110 may connect to a Home Subscriber Server (HSS) or a Unified Data Management (UDM) 172 directly or via one or more other network nodes. In some implementations, the MME 114 connects to the HSS 172 via an interface. In other implementations, the AMF 164, 184 connects to the UDM 172 via an interface. In yet other implementations, the SMF 166, 186, connects to the UDM 172 via an interface. The HSS / UDM 172 may connect to the SMSC 170 via an interface.

[0034] The base station 104 supports a cell 124, and the base station 106 supports a cell 126. The cells 124 and 126 can partially overlap, so that the UE 102 can select, reselect, or hand over from one of the cells 124 and 126 to the other. To directly exchange messages or information, the base station 104 and base station 106 can support an X2, Xn or X6G interface. In general, the CN 110 can connect to any suitable number of base stations supporting 6G cells, 6G-I0T cells, NR cells, EUTRA cells, and / or NB-IoT cells.

[0035] The base station 104 includes processing hardware 130 that can include one or more general -purpose processors (e.g., CPUs) and a non-transitory computer-readable memory (CRM) storing instructions that the one or more general-purpose processors execute. Additionally orPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 alternatively, the processing hardware 130 can include special -purpose processing units.According to an embodiment illustrated in Fig. 1, the processing hardware 130 includes a processor 132 to process data that the base station 104 will transmit in the downlink direction, or data that the base station 104 receives in the uplink direction. The processing hardware 130 also includes a transceiver 134 configured to transmit data in the downlink direction and to receive data in the uplink direction. The processing hardware 130 can include a memory storing executable codes for the processor 132 to perform methods according to embodiments described in this section. The processing hardware 130 can implement, among other components, a data collection controller 136 that implements some or all of the techniques for supporting AI / ML-related data collection, as discussed below.

[0036] The base station 106 can include generally similar components. In particular, components 140, 142, 144, and 146 of the base station 106 are similar to the components 130, 132, 134, and 136, respectively.

[0037] The UE 102 includes processing hardware 150 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 processing hardware 150 in an example implementation includes a processor 152 to process data that the UE 102 will transmit in the uplink direction, or process data that the UE 102 receives in the downlink direction. The processing hardware 150 also includes a transceiver 154 configured to transmit data in the downlink direction and to receive data in the uplink direction. The processing hardware 150 can implement, among other components, a data collection controller 156 to apply data collection policies and control, for example.

[0038] Fig. 2 illustrates, in a simplified manner, an example protocol stack 200 according to which the UE 102 can communicate with a 6G gNB, an eNB / ng-eNB or a gNB (e.g., one or more of the base stations 104, 106).

[0039] In the example stack 200, a physical (PHY) layer 202 provides transport channels to a MAC sublayer 204, which in turn provides logical channels to a RLC sublayer 206. The RLCPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 sublayer 206 in turn provides RLC channels to a PDCP sublayer 208. The PDCP sublayer 208 in turn can provide data transfer services to a radio resource control (RRC) sublayer 210, an Internet Protocol (IP) layer and / or a Service Data Adaptation Protocol (SDAP) sublayer (not shown in Fig. 2). The PDCP sublayer 208 receives packets (e.g., from the RRC sublayer 210, the SDAP sublayer, or the IP layer, layered directly or indirectly over the PDCP layer 208), which this disclosure refers to as service data units (SDUs), and outputs packets (e.g., to the RLC layer 206), which this disclosure refers 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.” In some implementations, the PHY layer 202, MAC sublayer 204, RLC sublayer 206, PDCP sublayer 208, RRC sublayer 210 are EUTRA layers or sublayers. In other implementations, the PHY layer 202, MAC sublayer 204, RLC sublayer 206, PDCP sublayer 208, RRC sublayer 210 are NR layers or sublayers.

[0040] The RRC sublayer 210 provides data transfer services to a Non-Access-Stratum (NAS) layer 212. The NAS layer 212 includes a mobility management (MM) sublayer and / or a session management (SM) sublayer. In some implementations, the MM sublayer is an EPS MM (EMM) sublayer, a 5G MM (5GMM) sublayer or a 6G MM (6GMM) sublayer. In some implementations, the SM sublayer is an EPS SM (ESM) sublayer, a 5G SM (5GSM) sublayer or a 6G SM (6GSM) sublayer.

[0041] On a control plane, the PDCP sublayer 208 can provide signaling radio bearers (SRBs) to the RRC sublayer 210 to exchange RRC messages or NAS messages (e.g., MM messages and / or SM messages), for example. On a user plane, the PDCP sublayer 208 can provide Data Radio Bearers (DRBs) to support user plane data exchange. User plane data exchanged on the PDCP sublayer 208 can be SDAP PDUs, Internet Protocol (IP) packets or Ethernet packets.

[0042] Fig. 3 is a service-based representation 300 of the 5GS architecture, which the system of Fig. 1 can implement. In the representation 300, the overall non-roaming reference architecture of the policy and charging control (PCC) framework for the 5GS illustrates components within the PCC framework using solid lines and illustrates other components 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 frameworkPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 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 (NSAAF) 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, the RAN 105, and a data network (DN) 330. An application server (AS) 331 operates in the DN 330.

[0043] 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. A data control network function (DCNF) can operate in the PCF 360 or separately in a DCNF 361 to control data collection as this disclosure describes in more detail below. The UE 102 connects to the RAN 105, which interfaces with the AMF 364 via an N1 interface and an N2 interface. The RAN 105 connects to the UPF 370 via an N3 interface. The SMF 366 connects to the UPF 370 via an N4 interface. The UPF 370 connects to the application server 331 via an N6 interface. A Binding Support Function (BSF) 390 can support correlation of sessions across multiple policy servers, which allows operators to scale the network.

[0044] Fig. 4 is a reference-point based representation 400 of the 5GS architecture. In Fig. 4, solid lines illustrate the non-roaming reference architecture of the PCC framework for the 5GS as blocks and connections and dashed lines illustrate components and connections outside the PCC framework. Also, the BSF 390 can have local respective interfaces to the AF 358, the NEF 354, and PCF 360.

[0045] Referring again to Figs. 1 and 3-4, the UE 102 can receive system information from the RAN 105 via a serving cell (e.g., cell 124). The system information may include one or more system information blocks (SIBs).PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0046] Aspects of the disclosure can be understood according to the following assumptions. First, an AI / ML-enabled feature can be identified by a Feature ID. When handling UP data collection and policies to control the UP data connection for UP data collection, a feature ID associates training data collection for a specific AI / ML enabled feature with an AI / ML model training service provided by the network. A UE may support one or more AI / ML-enabled features.

[0047] Second, aspects of the present disclosure enhance various components based on 5GS (TS23.501). For example, the proposed features of the network functions (AMF, SMF, PCF, NEF, AF) in the 5GS (TS23.501, 23.502, 23.503) implement enhanced corresponding features of the entities (MME, SGW, PGW, PCRF, SCEF, SCS) in the EPS (TS23.682 and 23.401), including for example implementation of a DCNF.

[0048] The convergence of communication network and Al technology can enable 5GC and air interface intelligence, e.g., in terms of data collection, ML model training, analytics inference, etc., by providing network automation and improving the efficiency of the 5G network architecture. To support the cross-domain (i.e., UE, RAN, 5GC, 0AM and AF) collaborative AI / ML mechanisms, 5G, 6G (and later) systems should perform AI / ML cross-domain coordination to characterize the AI / ML functionalities.

[0049] 3GPP is currently considering systems and methods to support training data collection for a UE-side model that performs inference entirely at the UE based on a functional framework for AI / ML for an NR air interface (TR 38.843). 3GPP is studying whether and how to support UE data collection to meet requirements for RAN Al support for air interface operation (for RAN) for UE-side model training. For example, 3GPP is studying how to enhance UE data collection and how to perform policy control in the 5G (or later) systems. The related technical report (3GPP TR 38.843, Section 7.2.1.3.2) for SA2 SID discussed an over-the-top scenario wherein the UE may collect and directly transfer training data to the Over-The-Top (OTT) server according to either OTT (TRansparent) or OTT (non-TRansparent) methods. In a core networkbased scenario, the UE may collect training data and transfer it to Core Network. The Core Network transfers the training data to the OTT server. In an OAM-based scenario, the UE may collect training data and transfer it to 0AM. The 0AM transfers the needed data to the OTTPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 server. A 5GS NWDAF can handle data collection for network automation aspects based on the UE application Data collection framework (3GPP TS 26.531). The NWDAF can interact with a Data Collection AF (DCAF) in the trust domain of the operator’s network to collect data from UE application(s) as an input for analytics generation and ML Model training. This framework can apply to non-transparent aspects of over-the-top scenarios, or to core network-based scenario named above, such that DCAF operates as a data collection network function that connects to the UPF via an N6 interface based on options defined in 3 GPP TR 38.843.

[0050] However, when considering training data collection related to AI / ML for an NR air interface for the core network-based scenario described above, existing systems do not specify how the 5GC can enhance policy control and handle data collection with the UE to use AI / ML model training services provided by the network.

[0051] Moreover, considering the data volumes that the UE reports, a UP approach may reduce or eliminate signaling storms in an end-to-end network. However, existing systems do not specify how the 5GC can enhance policy control and handle UP data connection with the UE for handling UP data collection to use network AI / ML model training services.

[0052] Aspects of the disclosure propose multiple solutions, described with reference to Figs.5-13, to the above-described scenarios. The invention applies training data collection for various 3 GPP system features, corresponding to different use cases across different domains at the RAN, CN, and cloud applications. These AI / ML enabled features enhance resource management in terms of radio air interface, radio resource management, RAN mobility, and core network automation, etc. For example, the following AI / ML-enabled features are considered: (i) AI / ML based CSI compression, AI / ML based 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, etc. (3GPP TR 38.843); (ii) supporting AI / ML-based network slicing, AI / ML based coverage and capability optimization, AI / ML -based Network Energy Saving for finer granularities, etc. (3GPP TR 38.743); (iii) AI / ML enabled RRM measurement prediction, measurement event prediction, etc. (3 GPP TR 38.744); (iv) AI / ML enabled QoS sustainability analytics enhancement, QoS and Policy AssistancePATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 Analytics enhancement, PDU Session traffic analytics enhancement, movement behavior analytics enhancement, location accuracy analytics enhancement, etc. (3 GPP TS 23.288).

[0053] Aspects of this disclosure provide solutions for the DCNF which can be an existing network function for a specific AI / ML-enabled feature, or a new (e.g., special purpose or dedicated) data collection network function providing a UP data collection service. The network can support UP data collection in the deployment according to at least one of at least three models: (i) a native Al / ML data collection model, wherein the DCNF is an existing network function, e.g. LMF, PCF, AMF, SMF, etc., which can support new service operations for UP data collection directly. For example, in the case of an AI / MU enabled feature for positioning accuracy enhancement, the UMF can be the DCNF to provide UP data collection service, (ii) a dedicated AI / ML data collection model, wherein the DCNF is a dedicated data collection network function introduced to support service operations for UP data collection on behalf of existing network functions, e.g., UMF, PCF, AMF, SMF, etc. In this case, the other network functions can request UP data collection service from the dedicated DCNF. (iii) an NWDAF and DCCF assisted data collection model based on TS23.288, wherein the DCNF is NWDAF with DCCF for data collection. In this case, the other network functions can request data collection service from the NWDAF with DCCF. In this case, the NWDAF associated with Nnwdaf_Datamanagement services collects data from the UE.

[0054] Aspects of the disclosure provide solutions to the above-mentioned issues. In one solution, a high-level procedure supports data collection from the UE based on a UE policy provisioned by the PCF / DCNF. In another solution, registration request message enhancement enables negotiation of UP data collection support. In yet another solution, a UE Policy Enhancement for a user equipment routing selection policy (URSP) rule provides multiple implementations. According to this solution, in one aspect, traffic descriptor (TD) enhancement using IP descriptors indicates a destination DCNF address, port number, and protocol ID for a secure UP connection In another aspect, TD enhancement including connection capabilities indicates a new (e.g., special purpose or dedicated) standardized component value for UP data collection. In another aspect, TD enhancement AI / ML enabled feature ID(s) supports AI / ML model training at the network for a UE-side model. In another aspect, route selection descriptorPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 (RSD) enhancement indicates information in addition to existing PDU Session related information, e.g., DNN, S-NSSAI, SSC mode, etc. Yet another solution provides new (e.g., special purpose or dedicated) UE policy of Data Collection Routing Policy (DCRP) rules. A still further solution provides new (e.g., special purpose or dedicated) DCRP rules in a PDU Session level with URSP rule enhancement including a UP data connection indication in RSD.

[0055] Fig. 5 illustrates high level procedures for UE interactions with a CN of the wireless cellular system, e.g. in 5GS or 6GS, for data collection for Al / ML model training (e.g. for inferencing using a UE-side model, network-side model, and / or AS side model) that uses data collected from the UE.

[0056] Generally speaking, similar events in Figs. 5-12 are labeled with similar reference numbers that share two least significant digits, with differences discussed below where appropriate. For example, event 502 is similar to event 602 of Fig. 6, event 702 of Fig. 7, event 802 of Fig. 8, event 902 of Fig. 9, and event 1002 of Fig. 10. With the exception of the differences shown in the figures and discussed below, any of the other implementations discussed with respect to a particular event (e.g., for messaging and processing) may apply to events labeled with similar reference numbers in other figures.

[0057] The UE performs 502 a Registration procedure to negotiate UP data collection support with the network (see, e.g., 3GPP TS 23.502 clause 4.2.2.2 (Figure 4.2.2.2.2-1: Registration Request procedure). The AMF selects 502a a PCF for the UE and creates a PCF for UE association. Aspects of the present disclosure provide enhancements to the Registration Request procedure as described later herein.

[0058] If the network supports UE policy handling, the PCF or DCNF performs 512 a UE Configuration Update procedure to provision UE policies for the UE. The DCNF can perform the UE Configuration Update procedure directly or via the PCF using an Namf_Communication_NlN2MessageTransfer message to provision Session Management UE policies, e.g., URSP rules enhanced for UP data collection according to aspects of the present disclosure described in more detail later herein. Alternatively or additionally, the PCF or DCNF can provide new (e.g., special purpose or dedicated) Data Collection Routing Policy (DCRP)PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 rules to the UE via the AMF (with reference to TS23.502 clause 4.2.4.3: UE Configuration Update procedure for transparent UE policy delivery (Figure 4.2.4.3-1 : UE Configuration Update procedure for transparent UE Policy delivery)) The PCF or DCNF can provide these DCRP rules to update UE policy based on triggering conditions. The triggering condition can include the DCNF receiving or detecting an AF or another network function’s request to enable UP data collection from the UE for enabling / disabling / updating a specific AI / ML enabled feature, e.g., for AI / ML model training services at the network.

[0059] Based on the triggering condition of the URSP rules evaluation, i.e., when the UE receives an upper layer (application) or lower layer (e.g., RRC / MAC / SDAP) request for UP data collection, the UE performs 522 policy evaluation and enforcement. Policy evaluation and enforcement can include (i) an evaluation of UE policies enhanced for UP data collection enforcement of a matched UE policy, and a determination of whether to perform a PDU Session Establishment / Modification request procedure for UP data collection of one or more AI / ML enabled features. Enabled features can include AI / ML model training services at the network.

[0060] Based on the enforced UE policy enhanced for UP data collection, the UE performs 532 a PDU Session Establishment / Modification request procedure (with reference, for example, to 3GPP TS 23.502 clause 4.3.2 (Figure 4.3.2.2.1-1: UE-requested PDU Session Establishment for non-roaming and roaming with local breakout). The SMF may select 532a a PCF / DCNF and create a PCF / DCNF association for the PDU Session to retrieve or update SM UE policies of the PDU Session. The PCF for the UE and the PCF for the PDU Session may be the same in some aspects, while in other aspects the PCF for the UE may be different from the PCF for the PDU Session. As a part of the PDU Session Establishment / Modification request procedure, the SMF obtains PCC rules from the PCF. The PCC rules contain the UP Data collection configuration information, and accordingly the SMF configures the UPF using N4 rules. The N4 rules can include UP data connection information, which can guide the UPF to route the traffic of related AI / ML data towards the corresponding DCNF address and port of a specific AI / ML enabled feature. The UE receives a PDU Session Establishment Accept message or a PDU Session Modification Command message from the network. This message confirms the use of the UP data collection for the PDU Session.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0061] Based on the UE policy and address information of DCNF, the UE requests 542 one or more secure user plane connections with the DCNF, e.g., using TLS over TCP or QUIC, for UP data collection of one or more AI / ML enabled features. According to an aspect, the PCC rules information in 5GC can include the UP Data collection configuration information which indicates the DCNF address and port number for UP data collection of an associated specific AI / ML enabled feature. For one or more AI / ML enabled features for a UE, the PCC rule can include a list of DCNF address / port number pairs which may also include a corresponding Protocol ID of the secure transport layer mechanism (e g., TLS over TCP or QUIC). According to an aspect, for each AI / ML enabled feature, the network allocates and transmits a specific pair of DCNF address and port numbers with corresponding protocol ID information to the UE to differentiate the data collected for different AI / ML features. Furthermore, according to an aspect (based on 3GPP TS 23.501 Table 5.8.5.6-1) the N4 includes the UP Data collection configuration information in the packet detection rule (PDR), which the UPF uses to detect the traffic containing data that the UE is to collect and report. When the traffic is detected based on the PDR, the UPF enforces a Forwarding Action Rule (FAR) that defines how the detected packet is to be forwarded, whereby the FAR can include: (i) in one aspect, enhanced existing attributes with new (e.g., special purpose or dedicated) settings: destination interface set as at core-side, and forwarding policy indicates steering traffic towards a target DCNF in 5GC; or (ii) in another aspect, new (e.g., special purpose or dedicated) attributes that indicate in-network forwarding information for a target DCNF in 5GC.

[0062] Fig. 6 illustrates a registration request message enhancement for negotiation of UP data collection support. As shown in Fig. 6, the UE 102 and the network negotiate support for UP data collection during the registration procedure. This negotiation enables the network to establish a secure user plane (UP) connection between a network function (e.g., the DCNF) and the UE 102 for collecting data from the UE 102, such as for AI / ML model training services provided by the network.

[0063] The UE 102 transmits 602, to the AMF 364, a Registration Request message. The Registration Request message includes: i.) UE capabilities for UP data collection as part of a 5GMM capability information element, and ii.) a Support indicator for URSP transport using aPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 control plane as a part of a UE Policy Classmark IE. The AMF 364 receives and stores the UE capabilities for UP data collection. The AMF 364 transmits 603, to the UDM 308, a request to retrieve subscription information for the UE 102. The UDM 308 stores UE subscription data including Session Management Subscription data that contains UP data collection information. This UP data collection information indicates whether the UE 102 is authorized to establish a PDU session for UP data collection purposes.

[0064] If the UE capabilities support UP data collection, and the UE subscription allows establishing a PDU Session for UP data collection, the AMF selects a PCF / DCNF and creates a PCF / DCNF association for the UE to handle and control UE policies. The AMF transmits 604, to the associated PCF / BSF, (i) an Npcf UEPolicyControl Create Request message or an Ndcnf_UE-DCPolicyControl Request message including the subscription permanent identifier (SUPI) of the UE and (ii) an indication of UE capability for UP data collection.

[0065] The PCF may include an IE indicating support for UP data collection in (i) an Npcf_UEPolicyControl Create Response 606 as shown in Fig. 6 (e.g., similar to URSP rules enhancement as described later herein), (ii) an Npcf UE-DCPolicyControl Create Response message (e.g., DCRP rules provisioning by PCF according to an aspect), or (iii) Ndcnf_UE-DCPolicyControl Create Response message (e.g., DCRP rules provisioning by DCNF according to an aspect) for provisioning UE policy for UP data collection in response to the request message transmitted in operation 604.

[0066] The PCF / DCNF for the UE registers 608 respective address information to a binding service function (BSF).

[0067] If the AMF 364 determines that the network supports UP data collection for purposes of AEML model training at the network, the AMF 364 transmits 610, to the UE 102, a Registration Accept message. The Registration Accept message includes UP data collection support as a part of a 5GS Network Feature Support IE for AEML model training services provided by the network (e.g., AI / ML data collection for UE-side model, AI / ML data collection for RAN-side model, AEML data collection for network-side model, etc. Otherwise, the AMFPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 364 does not include information related to network support of UP data collection, and the AMF 364 may include cause information that indicates lack of support for UP data collection.

[0068] Operations 612-642 can be similar to operations 512-542 in Fig. 5 described earlier herein.

[0069] Following the UE configuration update procedure 512 (Fig. 5) or 612 (Fig. 6), the PCF provisions UE policy in the form of URSP rules to the UE 102. Each URSP rule includes a traffic descriptor (TD) that identifies the traffic to which the rule applies, and a route selection descriptor (RSD) that specifies PDU Session parameters for routing the identified traffic, as defined in TS23.503 and TS24.526. The network and UE 102 can implement these and other aspects using methods illustrated with reference to the flow diagrams of Figs. 7-10.

[0070] In one aspect providing TD enhancement, the TD includes existing IP descriptors indicating a destination DCNF address, a port number, and a protocol ID for a secure UP connection.

[0071] Methods according to this aspect use existing IP descriptors that indicate Destination 1P 3-tuple(s) (including an IP address or an IPv6 network prefix, a port number, protocol ID of the protocol above IP) for identifying one or more AI / ML enabled features for use in the PDU session for UP data collection. The IP descriptors indicate a list of DCNF address and port number pairs with corresponding protocol ID, whereby (i) each pair of Destination address and port number corresponds to different features for AI / ML model training, e.g. RAN mobility optimization, CSI prediction, location reporting, etc.; and (ii) the protocol ID includes TLS over TCP or QUIC to ensure use of a secure UP connection for data collection. Table 1 illustrates example URSP rules:PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 """"

[0072] In methods according to this aspect, for each AI / ML enabled feature, the network allocates and transmits, to the UE 102, a specific pair of DC NF address / port number with corresponding protocol ID information to differentiate the data collected for different AI / ML enabled features.

[0073] The UE 102 obtains the list of DCNF address / port number pairs with a corresponding protocol ID for a specific AI / ML enabled feature from a NAS message, including: (i) in a new (e.g., special purpose or dedicated) IE in a Registration Accept message (e.g. in 610 in Fig. 6); (ii) in a new (e.g., special purpose or dedicated) payload container IE with payload container type set for data collection configuration in a DL NAS Transport message (e.g. as part of operation 512 in Fig. 5 or operation 612 in Fig. 6 of the UE Configuration Update Procedure or a standalone DL NAS Transport message that the DCNF transmits via the AMF 364 using an Namf_Communication_NlN2MessageTransfer message to the UE 102); or (iii) a PDU Session Establishment Accept message or PDU Session Modification Command message indicated as a dedicated IE or in an ePCO IE (e g. as part of operation 532 in Fig. 5 or operation 632 in Fig. 6).

[0074] When the UE 102 receives a UP connection request for data collection from an upper layer (e.g. application), or a lower layer (e.g. RRC / MAC / SDAP layer), to establish a secure UP connection with the destination addressing information corresponding to a specific pair of DCNFPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 address and port number, the UE 102 triggers URSP rules evaluation and enforces the URSP rule that includes the IP descriptor matching the information indicated in the UP connection request.

[0075] Fig. 7 illustrates an aspect providing traffic descriptor enhancement using IP descriptors. At block 702, the UE transmits, to the AMF 364, a Registration Request message including UE capabilities of UP data collection as a part of 5GMM capability and receives a Registration Accept message including network support of UP data collection.

[0076] At block 712, the UE 102 receives, from the PCF / DCNF 360 via the AMF 364, a DL NAS Transport message including UE policies of URSP rules enhanced for UP data collection, and a UP data collection configuration container, which contains a list of DCNF address and port number pairs with the protocol ID per AI / ML-enabled feature, which may be further identified by a feature ID. The UE 102 stores the UE policies of URSP rules and the data collection configuration

[0077] At block 722, the UE 102 triggers URSP rules evaluation when receiving a UP connection request for a specific AI / ML-enabled feature ID from a lower layer (RRC / MAC / SDAP) or upper layer (application).

[0078] At block 724, the UE 102 checks whether the UE 102 finds a matched URSP rule with IP descriptors against the stored UP data collection configuration. At block 724a, if there is no matched URSP rule selected, the UE 102 does not proceed with a PDU Session Establishment / Modification request procedure. The UE 102 provides a response to the UP connection request indicating causes, which can include indications that no matched URSP rule was found, or that there is no stored UP data collection configuration, or that there is no support for UP data collection for the AI / ML enabled feature, etc.

[0079] If there is a matched URSP rule selected, at block 732, the UE 102 enforces the matched URSP rule based on the RSD indicated in the matched URSP rule by requesting to establish / modify a PDU Session that supports UP data collection for the requested AI / ML-enabled feature. The UE 102 may receive updates of the UP data configuration in the PDU Session Establishment Accept message or a PDU Session Modification Command message from the SMF 366.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0080] At block 742, the UE further transmits, to the DCNF, a request (using TLS over TCP or QUIC) to establish a secure UP data connection and starts to transmit data required for the AI / ML-enabled feature if the secure UP data connection is set up successfully.

[0081] In another aspect of the present disclosure, for TD enhancement, the TD includes Connection Capabilities indicating a new (e.g., special purpose or dedicated) standardized component value as UP data collection.

[0082] Methods according to these and other aspects introduce a new (e.g., special purpose or dedicated) standardized component value of UP data collection for the Connection Capabilities component in TD, 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, one new (e.g., special purpose or dedicated) component value of connection capabilities indicates UP data collection. In this case, when the UE receives a UP connection request for UP data collection from an upper layer (e.g. application) or a lower layer (e.g. RRC / MAC / SDAP layer) to establish a secure UP connection, the UE triggers URSP rules evaluation and enforces the URSP rule that includes Connection Capabilities with a component value that matches the information indicated in the UP data collection request. Table 2 illustrates example URSP rules:""""PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0083] Fig. 8 illustrates an aspect providing traffic descriptor enhancement using connection capabilities information. At block 802, the UE transmits, to the AMF 364, a Registration Request message including UE capabilities of UP data collection as a part of 5GMM capability and receives a Registration Accept message including network support of UP data collection.

[0084] At block 812, the UE 102 receives, from the PCF / DCNF 360 via the AMF 364, a DL NAS Transport message including UE policies of URSP rules enhanced for data collection. The UE 102 stores the UE policies of URSP rules.

[0085] At block 822, the UE 102 triggers URSP rules evaluation when receiving a UP connection request indicating UP data collection as Connection Capabilities from a lower layer (RRC / MAC / SDAP) or upper layer (application).

[0086] At block 824, the UE 102 attempts to match a URSP rule with a TD including a Connection Capabilities component value set as UP data collection. At block 824a, if there is no matched URSP rule selected, the UE 102 does not proceed with a PDU Session Establishment / Modification request procedure. The UE 102 provides a response to the UP connection request indicating causes, which can include indications that no matched URSP rule was found, or that there is no stored UP data collection configuration, or indicating that there is no support for UP data collection for the AI / ML enabled feature, etc.

[0087] If there is a matched URSP rule selected, at block 832, the UE 102 enforces the matched URSP rule based on the RSD indicated in the matched URSP rule by requesting to establish or modify a PDU Session that supports UP data collection. The UE 102 obtains and stores the UP data connection configuration in the PDU Session Establishment Accept message or PDU Session Modification Command message from the SMF 366. The UP data collection configuration contains a list of DCNF address and port number pairs with a corresponding protocol ID for each AUML-enabled feature. Each AI / ML-enabled feature may be further identified by a feature ID.

[0088] At block 842, the UE 102 transmits, to the DCNF, a request (using TLS over TCP or QUIC) to establish a secure UP data connection and starts to transmit data required for the AI / ML-enabled feature if the secure UP data connection is set up successfully.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0089] Tn another aspect of the present disclosure, for TD enhancement, the TD includes a component that indicates AI / ML enabled feature ID(s) for AI / ML model training at the network for a UE-side model.

[0090] Methods according to this aspect introduce one or more additional components of an AI / ML enabled feature ID for UP data collection in TD, whereby the component value identifies one or more feature ID(s) for use in the PDU session for UP data collection, whereby the feature ID can be a standardized value defined in 3 GPP, or operator defined values.

[0091] When using an operator defined feature ID, the network provides the operator defined feature ID(s) in a dedicated container IE included in a Registration Accept message, DL NAS Transport message, PDU Session Establishment request message, or PDU Session Modification Command message.

[0092] 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 AEML-enabled feature ID(s). In this case, the UE may receive a UP connection request for UP data collection with a specific AI / ML enabled feature ID. The UP connection request may originate from an upper layer, e.g., an application, or from a lower layer, e.g., RRC / MAC / SDAP layer. In response to receiving the UP connection request to establish a secure UP connection, the UE triggers URSP rules evaluation. The UE then enforces the URSP having a TD that includes the AI / ML enabled feature ID(s) matching the information indicated in the UP data collection request.

[0093] Table 3 illustrates an enhancement of Table 6.6.2.1-2: UE Route Selection Policy Rule in TS 23.503 and Table 4 illustrates example URSP rules.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00Table 3PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 Example URSP rules:"" """"

[0094] Fig. 9 illustrates an aspect providing traffic descriptor enhancement using AI / ML enabled feature IDs. At block 902, the UE transmits, to the AMF 364, a Registration Request message including UE capabilities of UP data collection as a part of 5GMM capability and receives a Registration Accept message including network support of UP data collection.

[0095] At block 912, the UE 102 receives, from the PCF / DCNF 360 via the AMF 364, a DL NAS Transport message including UE policies of URSP rules enhanced for UP data collection of AI / ML enabled features. The UE 102 stores the UE policies of URSP rules.

[0096] At block 922, the UE 102 triggers URSP rules evaluation when receiving a UP connection request indicating one or more AI / ML enabled feature ID(s) for UP data collection from a lower layer (RRC / MAC / SDAP) or upper layer (application).

[0097] At block 924, the UE 102 determines whether a matched URSP rule exists having a TD that includes one or more AI / ML enabled feature IDs corresponding to the information provided in the UP connection request. At block 924a, if there is no matched URSP rule selected, the UE 102 does not proceed with a PDU Session Establishment / Modification request procedure. The UE 102 provides a response to the UP connection request indicating causes, which can include indications that no matched URSP rule was found, or that there is no stored UP data collectionPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 configuration, or indicating that there is no support for UP data collection for the AI / ML enabled feature, etc.

[0098] For a matched URSP rule selected at block 932, the UE 102 enforces the matched URSP rule based on the RSD indicated by requesting to establish or modify a PDU Session indicating the AI / ML feature ID that supports UP data collection. The UE 102 obtains the UP data connection configuration in the PDU Session Establishment Accept message or PDU Session Modification Command message from the SMF 366. The UE 102 stores the UP data connection configuration. The UP data collection configuration contains a list of DCNF address and port number pairs with the protocol ID for each indicated AI / ML-enabled feature. Each AI / ML-enabled feature may be identified by a feature ID.

[0099] At block 942, the UE 102 transmits, to the DCNF, a request (using TLS over TCP or QUIC) to establish a secure UP data connection and starts to transmit data required for the AI / ML-enabled feature if the secure UP data connection is set up successfully.

[0100] In another aspect of the present disclosure, for RSD enhancement, the RSD indicates information in addition to existing PDU Session-related information (e.g., DNN, S-NSSAI, SSC mode, etc.).

[0101] Methods according to this aspect enhance the RSD using one or more of the following aspects. In one aspect, the RSD includes a dedicated component of User plane security indication information. Following any of the aspects described earlier herein with reference to one or more of Figures 7-9, this component can include an indication of the allowed security mechanism for the transport layer protocol, e.g., TLS over TCP, and QUIC, of the UP data connection for UP data collection.

[0102] When the TD of a URSP rule matches the requested UP data connection for UP data collection from the upper / lower layer, the UE 102 enforces the URSP rule to establish or modify a PDU Session based on information indicated in the RSD. If the RSD includes this User plane security indication, the PDU session is solely for UP data collection. After establishing or modifying a PDU session, the UE 102 can request one or more UP data connections using TLS over TCP or QUIC with DCNFs for UP data collection within the PDU session based on UP dataPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 connection configuration that the UE 102 stores, including a list of DCNF address and port number pairs. The UE 102 does not request UP data collection not indicated in the RSD within the PDU Session, and the network does not route the related traffic not indicated in the RSD.

[0103] Table 5 illustrates an example RSD in the URSP rule, and can illustrate an enhancement of Table 6.6.2.1-3: Route Selection Descriptor:NOTE 1 : Rules in a URSP shall have different precedence values.NOTE 2: The information is used to identify the Application(s) that is(are) running on the UE's OS. The OSId does not include an OS version number. The OSAppId does not include a version number for the application.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0104] Table 6 illustrates example URSP rules:"" """""" """"

[0105] In another aspect, the RSD includes a dedicated component of UP data connection configuration. This component can include one or more pairs of DCAF address / port number with a Protocol ID indicating TLS over TCP or QUIC. The UE 102 does not request UP data collection not indicated in the RSD within the PDU Session and the network does not route the related traffic not indicated in the RSD.

[0106] When the TD of a URSP rule matches the requested UP data connection for UP data collection from the upper / lower layer, the UE 102 enforces the URSP rule to establish or modify a PDU Session based on information indicated in the RSD. After the UE 102 establishes thePATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 PDU Session, the UE 102 can continue to request one or more UP data connections using TLS over TCP or QUIC with DCNFs for UP data collection within the PDU session.

[0107] Table 7 illustrates an example RSD in the URSP rule. Table 7 can illustrate enhancement of Table 6.6.2.1-3: Route Selection Descriptor.

[0108] Table 8 illustrates example URSP rules:"" """"PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0109] Fig. 10 illustrates an aspect providing route selection descriptor enhancement. At block 1002, the UE 102 transmits, to the AMF 364, a Registration Request message including UE capabilities of UP data collection as a part of 5GMM capability and receives a Registration accept message including network support of UP data collection.

[0110] At block 1012, the UE 102 receives, from the PCF / DCNF 360 via the AMF 364, a DL NAS Transport message including UE policies of URSP rules enhanced for UP data collection of AI / ML enabled features. The UE 102 stores the UE policies of URSP rules.

[0111] At block 1022, the UE 102 triggers URSP rules evaluation when receiving a UP connection request from a lower layer (RRC / MAC / SDAP) or upper layer (application). At block 1024, the UE 102 determines whether a matched URSP rule exists having a TD (as indicated in other aspects described earlier herein) that matches the information provided in the UP connection request. At block 1024a, if the UE 102 does not find a matched URSP rule, the UE 102 does not proceed with a PDU Session Establishment / Modification request procedure. The UE 102 provides a response to the UP connection request indicating causes, which can include indications that the UE 102 did not find a matched URSP rule, or that there is no support for UP data collection, etc.

[0112] If the UE 102 finds a matched URSP rule, at block 1032, the UE 102 enforces the matched URSP rule based on the RSD indicated in the matched URSP rule by requesting to establish or modify a PDU Session that supports UP data collection. The RSD includes User plane security indication information or UP data connection configuration (described earlier herein).

[0113] At block 1042, with User plane security information or UP data connection configuration included in the RSD, the UE 102 transmits, to the DCNF, a request (using TLS over TCP or QUIC) to establish one or more secure UP data connections with one or more DCNFs as indicated in the UP data connection configuration, and starts to transmit data required if the secure UP data connection is set up successfully.

[0114] In another aspect of the present disclosure, systems can provide a dedicated UE policy of Data Collection Routing Policy (DCRP) rules.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0115] Following the UE configuration update procedure in operation 512 in Fig. 5, and operation 612(Fig. 6), the PCF / DCNF provisions or transmits, to the UE, a UE policy including dedicated Data Collection Routing Policy (DCRP) rules. The DCRP rule includes a TD for identifying the traffic to be applied for the PDU Session based on information indicated in a DC routing selection descriptor (DC-RSD) having a structure similar to a URSP rule.

[0116] Accordingly, the system can apply any of the aspects described earlier herein when the PCF / DCNF provisions or transmits the UE policy of DCRP rules. Aspects described below differ from using the UE policy of URSP rules for UP data in previously-described aspects in the following ways: (i) the system defines the DCRP rule solely for traffic routing for UP data collection service that the network provides; (ii) the UE triggers DCRP rule evaluation when the UE receives a UP data collection request from an upper layer (application) or a lower layer (RRC / MAC / SDAP); (iii) following a registration request procedure 502 (Fig. 5) or 602 (Fig. 6), the UE indicates UE capabilities of UP data connection, UE capabilities of handling UE policy for DCRP rules, or both in a 5GMM IE in the Registration Request message, and the AMF additionally indicates the support of UP data connection, the support of UE policy for DCRP rules, or both in the Registration Accept message if the network supports these capabilities.

[0117] Fig. 11 illustrates the message flow according to aspects of the present disclosure. The UE transmits 1102, to the AMF 364, a Registration Request message including UE capabilities of UP data collection as a part of 5GMM capability and Support indicator for DCRP transport using the control plane as a part of a UE Policy Classmark IE. The AMF 364 stores the UE capabilities of UP Data Collection and a Support indicator for DCRP rules. The AMF 364 requests to retrieve a subscription from the UDM 308. The UDM 308 stores a UE subscription with Session Management Subscription data including UP data collection information. The UP data collection information indicates whether the network allows a PDU session for UP data collection.

[0118] If the UE capabilities support UP data collection, handling UE policy for DCRP rules, or both, and the UE subscription is allowed to establish a PDU Session for UP data collection, the AMF selects a PCF / DCNF and creates a PCF / DCNF association for the UE to handle and control UE policies. The AMF transmits 1104, to the associated PCF / DCNF 360, anPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 Npcf_UEPol icy Control Create Request message (similarly to operation 604 (Fig. 6) or an Ndcnf UE-DCPolicyControl Create Request message including SUPI of the UE and indication of UE capability of UP data collection.

[0119] The PCF / DCNF 360 for the UE 102 registers corresponding UE address information to the BSF (similarly to operations 606 and 608 (Fig. 6)).

[0120] If the AMF 364 determines that the network supports UP data collection and the UE policy of UP Data Collection, e.g., for AI / ML model training service at the network, the AMF 364 transmits 1110, to the UE 102, a Registration Accept message. The Registration Accept message can include UP Data Collection Support as a part of 5GS Network Feature Support IE for an AI / ML model training service provided by the network (e.g. AI / ML data collection for a UE-side model, AI / ML data collection for a RAN-side model, AI / ML data collection for a network-side model, etc.). Otherwise, the AMF does not include related information of network support of UP data collection and / or network support of DCRP rules, the AMF may include a cause that indicates lack of support for UP data collection and / or DCRP rules.

[0121] If the network supports the UE policy of DCRP rules handling, the PCF or DCNF performs 1112 a UE Configuration Update procedure to provision UE policies of the DCRP rules for the UE. The DCNF can perform a UE Configuration Update procedure directly or via the PCF using an Namf_Communication_NlN2MessageTransfer message to provision Session Management UE policies of Data Collection Routing Policy (DCRP) rules to the UE via AMF (with reference to TS23.502 clause 4.2.4.3: UE Configuration Update procedure fortransparent UE policy delivery (Figure 4.2.4.3-1 : UE Configuration Update procedure for transparent UE Policy delivery). The PCF / DCNF can provide these DCRP rules to update UE policy of DCRP rules based on triggering conditions. The triggering condition can include the DCNF receiving or detecting an AF or another network function’s request to enable UP data collection from the UE for enabling / disabling / updating a specific AI / ML enabled feature, e.g., for AI / ML model training services at the network.

[0122] Based on the triggering condition of the DCRP rules evaluation, i.e. when the UE receives an upper layer (application) or lower layer (e.g. RRC / MAC / SDAP) request for UP dataPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 collection, the UE 102 performs 1122 (similarly to operation 522 (Fig. 5) policy evaluation and enforcement. Policy evaluation and enforcement can include an evaluation of UE policies enhanced for UP data collection enforcement of a matched UE policy, and a determination of whether to perform a PDU Session Establishment / Modification request procedure for UP data collection of one or more AI / ME enabled features for AI / ML model training services at the network.

[0123] Based on the enforced UE policy enhanced for UP data collection, the UE 102 performs 1132 (similarly to operation 532 (Fig. 5) a PDU Session Establishment / Modification request procedure (with reference, for example, to 3GPP TS 23.502 clause 4.3.2 (Figure4.3.2.2.1-1 : UE-requested PDU Session Establishment for non-roaming and roaming with local breakout)). Finally, the UE 102 requests 1142 (similarly to operation 542) one or more secure user plane connections with the DCNF, e.g., using TLS over TCP or QUIC, for UP data collection of one or more AI / ME enabled features.

[0124] In another aspect of the present disclosure, systems can provide dedicated DCRP rules at the PDU Session level. This aspect provides UE policy for DCRP rules in the PDU Session level to further guide the UE to enforce the DCRP policy within the established PDU session.

[0125] In this aspect, the URSP rule includes a UP data collection indication in the RSD. When this indication is included, the PDU Session is deemed for UP Data Collection only.

[0126] Further, when the UE 102 determines to establish a DC based PDU Session, the UE 102 indicates UP Data Collection Capabilities as UE capabilities to use UP Data Collection functionality in a PDU Session Establishment request or a PDU Session Modification request message. In response, the UE 102 obtains a UP Data Collection PDU Session Information IE in a PDU Session Establishment Accept message or a PDU Session Modification Command message if the network supports and determines to enable the UP Data Collection for the PDU Session. The UP Data Collection PDU Session IE can include at least one of the following pieces of information: (i) UP Data Connection Support Confirmation; (ii) a DA PDU Session Type, which specifies whether the established PDU Session is for UP data collection wherein, if specified, the UE 102 is allowed to trigger UP data connection within the PDU session; (iii) a securityPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 indication, which specifies the network supported security protection mechanism used in the transport layer for UP data connection within the PDU Session, such as TLS over TCP , QUIC, or both; and(iv) Feature ID(s) defined by 3GPP for a specific AI / ML enabled service provided by the network within the PDU Session such as AI / ML model training at the network.

[0127] The UE 102 obtains DCRP rules from the SMF 366 in a PDU Session Establishment Accept message or a PDU Session Modification Command message for identifying the matched traffic based on the TD to be applied for the PDU Session with components indicated in a Data Collection-routing selection descriptor (DC-RSD).

[0128] Based on DCRP rules, the UE 102 can request UP data connection using TLS over TCP or QUIC with a DCNF for UP data collection within the PDU session. The structure of the DCRP rule includes the following components. First, the UE 102 obtains Feature ID(s) defined by 3GPP for a specific AI / ML enabled service, e.g. AI / ML model training at the network, provided by the network within the PDU Session from the UP Data Collection PDU Session IE included in PDU Session Establishment Accept message or PDU Session Modification Command message.

[0129] The DCRP rule structure includes at least: (i) a rule identifier that uniquely identifies the DCRP Rule; (ii) rule Precedence that determines the order in which the UE 102 evaluates the DCRP rule; and (iii) a traffic Descriptor (TD) that defines the traffic descriptor components for the DCRP rule, which includes at least one of the following components: (a) application descriptor comprising one or more application identities that identify the application(s) generating the traffic for data collection; and (b) a Feature ID of UP Data Connection comprising a feature ID requested by the upper layer or lower layer to apply UP data connection in this PDU Session.

[0130] The DCRP rule structure can further include DC Route Selection Descriptors (DC-RSD), which include components for the DCRP rule when the traffic matches the components indicated in the TD. The DC-RSD can indicate at least one of the following components: (i) User plane security indication that indicates an allowed security mechanism for the transport layer protocol, e.g. TLS over TCP, or QUIC, of the UP connection for UP data collection of thePATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 Feature ID indicated in the TD; and (ii) UP data connection configuration that includes one or more pairs of DCAF address and port number pair for the matched feature ID indicated in TD. The UE 102 can randomly choose one of the pairs to set up UP data connection for the feature ID indicated in the TD for UP data collection.

[0131] Fig. 12 illustrates an aspect providing dedicated DCRP rules at the PDU Session level.

[0132] At block 1202, the UE 102 transmits, to the AMF 364, a Registration Request message including UE capabilities of UP data collection as a part of 5GMM capability and receives a Registration Accept message including network support of UP data collection.

[0133] At block 1212, the UE 102 receives, from the PCF / DCNF 360 via the AMF 364, a DL NAS Transport message including UE policies of URSP rules enhanced for UP data collection. The UE 102 stores the UE policies of URSP rules.

[0134] At block 1222, the UE 102 triggers URSP rules evaluation when receiving a UP connection request for UP data collection from a lower layer (RRC / MAC / SDAP) or upper layer (application).

[0135] At block 1224, the UE 102 determines whether a matched URSP rule exists having a TD that matches the information provided in the UP connection request, at block 1224a, if no matched URSP rule is selected, the UE 102 does not proceed with a PDU Session Establishment / Modification request procedure. The UE 102 provides a response to the UP connection request indicating causes, which can include indicating that no matched URSP rule was found, or that there is no stored UP data collection configuration, or indicating that there is no support for UP data collection for the AVML enabled feature, etc.

[0136] If there is a matched URSP rule selected, at block 1232, the UE 102 enforces the matched URSP rule (with UP data collection indication in RSD) by transmitting a PDU Session Establish Request message or PDU Session Modification Request message including a UP data collection indication. When this indication is included, the PDU Session is deemed for UP Data Collection only. The UE 102 receives and stores DCRP rules from a PDU Session Establishment Accept or a PDU Session Modification Command message including DCRP rules applied for the PDU Session from the SMF 366.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0137] At block 1241, theUE 102 triggers DCRP rules evaluation.

[0138] At block 1242, if there is a matched TD of a DCRP rule, the UE 102 enforces the DC- RSD by requesting one or more secure UP data connections, using TLS over TCP or QUIC, with DCNF(s) as indicated in the DC-RSD. The UE 102 starts to transmit required data if the secure UP data connection is set up successfully.

[0139] Fig. 13 illustrates the message flow according to aspects of the present disclosure providing dedicated DCRP rules at the PDU Session level.

[0140] The UE 102 performs 1302 a Registration Request Procedure (similarly to operations 602-610 ofFig. 6). ThePCF / DCNF 360 performs 1312 a UE Configuration Update procedure to provision UE policies of URSP rules enhanced for UP data collection (similarly to operation 612 in Fig. 6).

[0141] The UE 102 receives 1322 a UP connection request and triggers URSP rules evaluation (similarly to operation 622 (Fig. 6)).

[0142] Based on the enforced UE policy enhanced for UP data collection, the UE 102 transmits 1332 a PDU Session Establishment / Modification request message including an indication of UP data collection. The AMF 364 transmits 1334, to the SMF 366, anNsmf PDUSession CreateSMContext Request message including an indication of UP data collection.

[0143] With the indication of UP data collection, the SMF 366 requests 1336 DCRP rules from the DCNF using an Ndcnf_UE_DCPolicy Request message directly or via PCF using an Npcf_UE_DCPolicy Request message or via PCF using an Npcf_UE_Policy Request message including an indication of UP data collection. The DCNF / PCF 360 returns DCRP rules in an Ndcnf_UE_DCPolicy Response message directly or via PCF using an Npcf_UE_DCPolicy Response message or via PCF using an Npcf UE Policy Request message using a DCRP rules container. When using PCF to provision DCRP rules, the PCF uses an Ndcnf UE DCPolicy Request message to request DCRP rules from the DCNF and obtains the DCRP rules from the Ndcnf UE DCPolicy Request message. The SMF 366 also obtains PCC rules from the PCF in which the PCC rules contain the UP Data collection configuration information and configuresPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 the UPF 370 using N4 rules including UP data connection information, which guides the UPF 370 to route the traffic of related AI / ML data towards the corresponding DCNF address and port of a specific AI / ML enabled feature.

[0144] The SMF 366 provisions 1338 DCRP rules to the UE 102 via the AMF 364 using an Nsmf PDUSession CreateSMContext Response message including DCRP rules.

[0145] The UE 102 receives 1340, from the network, a PDU Session Establishment Accept message or a PDU Session Modification Command message including DCRP rules to provide guidance for the use of the UP data collection within the PDU Session.

[0146] The UE 102 stores and evaluates 1341 the DCRP rules.

[0147] If there is a matched TD of a DCRP rule, the UE 102 enforces 1342 the DC-RSD by requesting one or more secure UP data connection(s), using TLS over TCP or QUIC, with DCNF(s) as indicated in the DC-RSD. The UE 102 starts to transmit required data if the secure UP data connection is set up successfully.

[0148] Fig. 14 is a flow diagram of a method 1400 performed by the UE 102.

[0149] The method 1400 can begin at block 1412 with the UE 102 receiving, from a core network (CN), a UE policy related to user-plane (UP) data collection (see e.g., event 512).

[0150] The method 1400 can continue at block 1450 with the UE transmitting, to the CN, UP data according to the UE policy.

[0151] Fig. 15 is a flow diagram of another method 1500 performed by the UE 102.

[0152] The method 1500 can begin at block 1512 with the UE 102 receiving, from a core network (CN), a Data Collection Routing Policy (DCRP) rule related to user-plane (UP) data collection (see e.g., events 512, 612, 712, 812, 912, 1012, 1112, or 1340). The DCRP rule may include a traffic descriptor (TD) comprising a feature identifier (ID) dedicated to artificial intelligence (AI) / machine learning (ML) model training.

[0153] The DCRP rule may further include a destination address and a port number of a data collection network function (DCNF) corresponding to the feature ID. In at least these aspects, method 1500 can further include establishing a UP data connection with the DCNF using thePATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 destination address and the port number; and transmitting, to the DCNF over the UP data connection, training data associated with the feature ID. In at least these aspects, a TD of the DCRP rule includes a Connection Capabilities (CC) field indicating the UP data collection. Further in at least these aspects, the feature ID can identify specific AI / ML enabled features. Feature IDs of a plurality of different AI / ML enabled features can correspond to different addresses and port numbers.

[0154] The method 1500 can continue at block 1542 with the UE 102 transmitting, to the CN, UP data according to the DCRP rule (see, e.g., events 1242 and 1342).

[0155] In some aspects, the DCRP rule includes a data collection route selection descriptor (DC-RSD) comprising a UP security indication indicating an allowed security mechanism for a transport layer protocol. In at least these aspects, the allowed security mechanism comprises Transport Layer Security (TLS) over Transmission Control Protocol (TCP) or TLS over Quick UDP Internet Connections (QUIC).

[0156] In some aspects of the present disclosure, the DCRP rule can include a data collection route selection descriptor (DC-RSD) comprising a UP data connection configuration including an address of a data collection network function (DCNF) and a port number. In at least these aspects, the method 1500 can include requesting a secure UP connection with the DCNF in response to matching the DCRP rule (see, e.g., event 1242).

[0157] In some aspects of the present disclosure, the DCRP rule is received via a Packet Data Unit (PDU) Session Establishment Accept message or a PDU Session Modification Command message (see, e.g., event 1340). In some aspects of the present disclosure, the method 1500 can include receiving a request for the UP data collection (see, e.g., event 1222); and evaluating the DCRP rule in response to the request (see e.g., event 1241).

[0158] In some aspects of the present disclosure, the method 1500 can include transmitting, to the CN, a registration request message including a UE capability indication indicative of a capability of the UE with respect to the UP data collection (see, e.g., event 602). In at least these aspects, the method 1500 can include receiving, from the CN, a registration accept message including a network support indication indicative of whether the CN supports the UP dataPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 collection (see, e.g., event 610). In at least some aspects, the method 1500 can include transmitting, to the CN, a PDU Session Establishment Request message or a PDU Session Modification Request message including an indication of UP data collection (see, e.g., event 1332-1334).

[0159] The following examples pertain to further aspects of the present disclosure.

[0160] Example l is a method implemented in a user equipment (UE), the method comprising: receiving, from a core network (CN), a UE policy related to user-plane (UP) data collection; and transmitting, to the CN, UP data according to the UE policy.

[0161] Example 2 is the method of Example 1, further comprising: reporting, to the CN, a capability of the UE with respect to UP data collection.

[0162] Example 3 is the method of Example 2, wherein the reporting includes: transmitting, to the CN, a registration request message including a UE capability indication indicative of the capability of the UE with respect to the UP data collection.

[0163] Example 4 is the method of Example 3, further comprising: receiving, from the CN, a registration accept message including a network support indication indicative of whether the CN supports the UP data collection.

[0164] Example 5 is the method of any of Examples 3-4, wherein the reporting includes: including the UE capability indication in a 5G Mobility Management (5GMM) capability information element (IE).

[0165] Example 6 is the method of any of Examples 3-4, wherein the reporting includes: including, in a UE Policy Classmark information element (IE), a UE Route Selection Policy (URSP) transport support indicator indicative of whether the UE supports URSP transport using the control plane.

[0166] Example 7 is the method of Example 1, wherein the receiving of the UE policy includes: receiving a rule, wherein the rule is a URSP rule.

[0167] Example 8 is the method of Example 1, wherein the receiving of the UE policy includes: receiving a rule, wherein the rule is a Data Collection Routing Policy (DCRP) rule.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0168] Example 9 is the method of any of Examples 7-8, wherein: a traffic descriptor (TD) of the rule comprises an Internet Protocol (IP) descriptor including one or more of (i) an address of a destination data collection network function (DCNF), (ii) a port number, or (iii) a protocol identifier (ID).

[0169] Example 10 is the method of Example 9, wherein: the address and the port number correspond to one of a plurality of features of an Artificial Intelligence / Machine Learning (AI / ML) model.

[0170] Example 11 is the method of Example 10, wherein the one of the plurality of features is one of: (i) radio access network (RAN) mobility optimization, (ii) Channel State Information prediction, or (iii) location reporting.

[0171] Example 12 is the method of any of Examples 9-11, wherein: the protocol ID indicates Transport Layer Security (TLS) over Transmission Control Protocol (TCP).

[0172] Example 13 is the method of any of Examples 9-11, wherein: the protocol ID indicates TLS over Quick UDP Internet Connections (QUIC).

[0173] Example 14 is the method of any of Examples 7-8, wherein: a TD of the rule includes a Connection Capabilities (CC) field indicating the UP data collection.

[0174] Example 15 is the method of any of Examples 7-8, wherein: a TD of the rule includes a feature ID dedicated to AI / ML model training.

[0175] Example 16 is the method of Example 15, wherein the feature ID is a standardized value.

[0176] Example 17 is the method of Example 15, wherein the feature ID is an operator-defined value.

[0177] Example 18 is the method of Example 15, wherein the feature ID in the traffic descriptor serves as a routing key that maps to a destination address and port number of a data collection network function (DCNF), enabling the UE to establish a UP data connection for transmitting training data associated with a specific AI / ML enabled feature to the DCNF.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0178] Example 19 is the method of any of Examples 9-17, wherein: the TP descriptor is received via a Registration Accept message, in a special-purpose information element (IE) dedicated specifically to conveying the IP descriptor for the UE policy.

[0179] Example 20 is the method of any of Examples 9-15, wherein: the IP descriptor is received via a downlink (DL) non-access stratum (NAS) transport message, in a special -purpose IE dedicated specifically to conveying the IP descriptor for the UE policy.

[0180] Example 21 is the method of any of Examples 9-15, wherein: the IP descriptor is received via a Packet Data Unit (PDU) Session Accept message or PDU Session Modification Command message, in a special-purpose IE dedicated specifically to conveying the IP descriptor for the UE policy.

[0181] Example 22 is the method of any of Examples 9-15, wherein: the IP descriptor is received via a PDU Session Accept message or PDU Session Modification Command message, in an Enhanced Protocol Configuration Options (ePCO) IE.

[0182] Example 23 is the method of Example 7, wherein: a route selection descriptor (RSD) in the URSP rule includes a UP security indication.

[0183] Example 24 is the method of Example 23, wherein the UP security indication indicates an allowed security mechanism for a transport layer protocol.

[0184] Example 25 is the method of Example 24, wherein the allowed security mechanism comprises Transport Layer Security (TLS) over Transmission Control Protocol (TCP) or TLS over Quick UDP Internet Connections (QUIC).

[0185] Example 26 is the method of Example 7, wherein: an RSD in the URSP rule includes a UP data connection configuration including the address of the DCNF and the port number.

[0186] Example 27 is the method of Example 8, wherein: a data collection route selection descriptor (DC-RSD) in the DCRP rule includes a UP security indication indicating an allowed security mechanism for a transport layer protocol.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0187] Example 28 is the method of Example 27, wherein the allowed security mechanism comprises Transport Layer Security (TLS) over Transmission Control Protocol (TCP) or TLS over Quick UDP Internet Connections (QUIC).

[0188] Example 29 is the method of Example 8, wherein: a DC-RSD in the DCRP rule includes a UP data connection configuration including an address of the DCNF and a port number.

[0189] Example 30 is the method of any of Examples 7-26, further comprising: receiving, from another layer of the UE, a request for the UP data collection; evaluating the UE policy in response to the request for the UP data collection; and determining whether to enforce the UE policy based on the evaluating.

[0190] Example 31 is the method of Example 30, wherein the request for the UP data collection is received from an application layer of the UE.

[0191] Example 32 is the method of Example 30, wherein the request for the UP data collection is received from a lower layer of the UE.

[0192] Example 33 is the method of any of Examples 30-32, further comprising, in response to determining to enforce the UE policy: establishing or modifying a PDU session for the UP data collection.

[0193] Example 34 is the method of Example 7, further comprising, in response to determining to enforce the UE policy: transmitting, to the CN, a PDU Session Establishment Request message; and receiving, in a PDU Session Establishment Accept message, a DCRP rule.

[0194] Example 35 is the method of Example 7, further comprising, in response to determining to enforce the UE policy: transmitting, to the CN, a PDU Session Modification Request message; and receiving, in a PDU Session Modification Command, a DCRP rule.

[0195] Example 36 is the method of any of Examples 34-35, further comprising: requesting a secure UP connection with a DCNF in response to matching the DCRP rule.

[0196] Example 37 is the method of any of Examples 9-15, further comprising: requesting a secure UP connection with the DCNF in accordance with the UE policy.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0197] Example 38 is a user equipment (UE) comprising: a transceiver; and processing hardware configured to implement a method of any of Examples 1-37.

[0198] Example 39 is a user equipment (UE) comprising: a transceiver; and processing hardware configured to: receive, from a core network (CN), a Data Collection Routing Policy (DCRP) rule related to user-plane (UP) data collection; and transmit UP data to the CN in accordance with the DCRP rule.

[0199] Example 40 is the UE of Example 39, wherein the processing hardware is further configured to receive the DCRP rule in a PDU Session Establishment Accept message or a PDU Session Modification Command message.

[0200] Example 41 is the UE of any of Examples 39-40, wherein the DCRP rule includes a traffic descriptor (TD) comprising a feature ID dedicated to AI / ML model training.

[0201] Example 42 is the UE of Example 41, wherein the feature ID is a standardized value or an operator-defined value.

[0202] Example 43 is the UE of Example 42, wherein the feature ID in the traffic descriptor serves as a routing key that maps to a destination address and port number of a data collection network function (DCNF), enabling the UE to establish a UP data connection for transmitting training data associated with a specific AI / ML enabled feature to the DCNF.

[0203] Example 44 is the UE of any of Examples 39-43, wherein the DCRP rule includes a data collection route selection descriptor (DC-RSD) comprising a UP security indication indicating an allowed security mechanism for a transport layer protocol.

[0204] Example 45 is the UE of Example 44, wherein the allowed security mechanism comprises Transport Layer Security (TLS) over Transmission Control Protocol (TCP) or TLS over Quick UDP Internet Connections (QU1C).

[0205] Example 46 is the UE of any of Examples 39-45, wherein the DCRP rule includes a DC-RSD comprising a UP data connection configuration including an address of a data collection network function (DCNF) and a port number.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00

[0206] Example 47 is the UE of Example 46, wherein the processing hardware is further configured to request a secure UP connection with the DCNF in response to matching the DCRP rule.

[0207] Example 48 is the UE of any of Examples 39-47, wherein the processing hardware is further configured to: receive, from an application layer or a lower layer of the UE, a request for the UP data collection; and evaluate the DCRP rule in response to the request.

[0208] Example 49 is the UE of any of Examples 39-48, wherein the processing hardware is further configured to: transmit, to the CN, a registration request message including a UE capability indication indicative of a capability of the UE with respect to the UP data collection; and receive, from the CN, a registration accept message including a network support indication indicative of whether the CN supports the UP data collection.

[0209] Example 50 is the UE of Example 49, wherein the UE capability indication is included in a 5G Mobility Management (5GMM) capability information element (IE).

[0210] Example 51 is the UE of any of Examples 39-50, wherein the processing hardware is further configured to transmit, to the CN, a PDU Session Establishment Request message or a PDU Session Modification Request message including an indication of UP data collection.

[0211] Example 52 is a non-transitory computer-readable medium storing instructions that, when executed by processing hardware of a user equipment (UE), cause the UE to perform a method of any of Examples 1-37.

[0212] The following description may be applied to the description above.

[0213] Generally speaking, description for one of the above figures can apply to another of the above figures. Examples, implementations and methods described above can be combined, if there is no conflict. An event or block described above can be optional or omitted. For example, an event or block with dashed lines in the figures can be optional. In some implementations, “message” is used and can be replaced by “information element (IE),” and vice versa. In some implementations, “IE” is used and can be replaced by “field,” and vice versa. In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters,” and vice versa. The “attach” can be replaced by “registration.” The “Attach” can bePATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 replaced by “Registration.” The “EPS attach type” can be replaced by “5GS registration type”. “EPS emergency attach” can be “emergency registration.” The “emergency messaging service” can be replaced by “emergency SMS” or “emergency messaging services.” The “emergency messaging” can be replaced by “emergency SMS” or “emergency messaging service(s) “via a cell” can be replaced by “via a satellite.” “via the cell” can be replaced by “via the satellite.”

[0214] In some implementations, the “PDN connectivity procedure” can be replaced by “PDU session establishment procedure.” In such cases, the “PDN Connectivity Request” and “Activate Default EPS Bearer Context Request” can be replaced by “PDU Session Establishment Request” and “PDU Session Establishment Accept,” respectively and the “Activate Default EPS Bearer Context Accept” is omitted.

[0215] 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 intemet-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.

[0216] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may 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), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may alsoPATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 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.

[0217] 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 may be executed by one or more general-purpose processors or one or more specialpurpose processors.

Claims

PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 Claims:

1. A method implemented in a user equipment (UE), the method comprising:receiving, from a core network (CN), a Data Collection Routing Policy (DCRP) rule related to user-plane (UP) data collection; andtransmitting, to the CN, UP data according to the DCRP rule.

2. The method of claim 1, wherein:the DCRP rule includes a traffic descriptor (TD) comprising a feature identifier (ID) dedicated to artificial intelligence (Al)Zmachine learning (ML) model training.

3. The method of claim 2, wherein:the DCRP rule further includes a destination address and a port number of a data collection network function (DCNF) corresponding to the feature ID, and wherein the method further comprises:establishing a UP data connection with the DCNF using the destination address and a port number; andtransmitting, to the DCNF over the UP data connection, training data associated with the feature ID.

4. The method of claim 3, wherein a TD of the DCRP rule includes a Connection Capabilities (CC) field indicating UP data collection.

5. The method of claim 3, wherein the feature ID identifies specific AI / ML enabled features, and wherein feature IDs of a plurality of different AI / ML enabled features correspond to different addresses and port numbers.

6. The method of claim 1, wherein:the DCRP rule includes a data collection route selection descriptor (DC-RSD) comprising a UP security indication indicating an allowed security mechanism for a transport layer protocol.PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 7. The method of claim 6, wherein:the allowed security mechanism comprises Transport Layer Security (TLS) over Transmission Control Protocol (TCP) or TLS over Quick UDP Internet Connections (QUIC).

8. The method of claim 1, wherein:the DCRP rule includes a data collection route selection descriptor (DC-RSD) comprising a UP data connection configuration including an address of a data collection network function (DCNF) and a port number.

9. The method of claim 8, further comprising:requesting a secure UP connection with the DCNF in response to matching the DCRP rule.

10. The method of claim 1, wherein:the DCRP rule is received via a Packet Data Unit (PDU) Session Establishment Accept message or a PDU Session Modification Command message.

11. The method of claim 1, further comprising:receiving a request for UP data collection; andevaluating the DCRP rule in response to the request.

12. The method of claim 1, further comprising:transmitting, to the CN, a registration request message including a UE capability indication indicative of a capability of the UE with respect to UP data collection; and receiving, from the CN, a registration accept message including a network support indication indicative of whether the CN supports UP data collection.

13. The method of claim 12, wherein the UE capability indication is included in a 5G Mobility Management (5GMM) capability information element (IE).PATENT APPLICATION Attorney Docket No.: 31730 / 308835-00 14. The method of claim 1, further comprising:transmitting, to the CN, a PDU Session Establishment Request message or a PDU Session Modification Request message including an indication of UP data collection.

15. A user equipment (UE) comprising:a transceiver; andprocessing hardware configured to implement a method of any of the claims 1-14.

Images