Differential treatment of user equipment (UE) non-application data

By indicating data type and configuring non-application specific QoS flows and DRBs, the solution addresses the challenges of differential charging and QoS for UE non-application data, optimizing data transmission in telecommunications systems.

WO2026238818A1PCT designated stage Publication Date: 2026-11-19NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/063952
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-16
Filing Date
2026-05-13
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing telecommunications systems face challenges in efficiently handling and differentiating the treatment of user equipment (UE) non-application data, such as AI/ML data, in terms of differential charging, quality of service (QoS), and default data radio bearers, due to the varying requirements and characteristics of this data type.

Method used

The proposed solution involves the RAN node indicating the purpose and data type of UE non-application data, allowing the UE to add type information to the data, and the CN determining and creating non-application specific QoS flows and DRBs to handle these data types differently from application data, with configurations and mappings to ensure appropriate handling and routing.

Benefits of technology

This approach enables efficient and differentiated treatment of UE non-application data, ensuring appropriate charging, QoS, and DRB management, thereby optimizing the transmission of AI/ML data and other non-application data in telecommunications systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026063952_19112026_PF_FP_ABST
    Figure EP2026063952_19112026_PF_FP_ABST
Patent Text Reader

Abstract

A method is provided that includes collecting non-application data of at least one data type among a plurality of data types of non-application data. The method includes adding, to the non-application data, type information that indicates the data type(s) of the non-application data. The method includes mapping the non-application data based on the type information to at least one non-application specific quality of service (QoS) flow created to carry the non-application data and associated with the data type(s) of the non-application data. The method includes mapping the at least one non-application specific QoS flow to at least one non-application specific data radio bearer (DRB). And the method includes transferring the non- application data on the non-application specific QoS flow(s) over the non-application specific DRB(s).
Need to check novelty before this filing date? Find Prior Art

Description

DIFFERENTIAL TREATMENT OF USER EQUIPMENT (UE) NON-APPLICATION DATA TECHNOLOGICAL FIELD

[0001] The present disclosure relates generally to telecommunications and, in particular, to data collection and reporting in a telecommunications system.BACKGROUND

[0002] Telecommunications systems can be seen as facilities that enable communications between two or more entities such as between two user equipment, between a user equipment and a base station, between two base stations, a user equipment and a network function of a communication network and / or a base station and other nodes. A telecommunications system can include a communication network and one or more user equipment. Communication sessions may comprise, for example, communication of data for carrying communications such as voice, video, electronic mail (email), text message, multimedia and / or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.

[0003] In a telecommunications system that includes a wireless communication network, at least a part of a communication session between at least two stations occurs over a wireless link. Examples of wireless communication networks comprise public land mobile networks (PLMN), satellite-based communication networks and different wireless local networks, for example wireless local area networks (WLAN). Some wireless communication networks can be divided into cells, and are therefore often referred to as cellular networks.

[0004] A user can access a communication network of the telecommunications system by means of an appropriate communication device or terminal. A communication device of a user may be referred to as user equipment (UE) or user device. A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access a carrier provided by, for example, a base station of a cell, and transmit and / or receive communications on the carrier.

[0005] Telecommunications systems have evolved through multiple generations, each bringing advancements in speed, capacity, and functionality. The Evolved Packet System (EPS) represents the 4G architecture, which includes Long-Term Evolution (LTE) and LTE-Advanced (LTE-A) as its radio access technologies. The 5G System (5GS) builds upon EPS, introducing 5G New Radio (5G NR) for enhanced mobile broadband, massive machine-type communications, and ultra-reliable low-latency communications. The future 6G System (6GS) is expected to further revolutionize telecommunications with even moreadvanced capabilities. Telecommunications systems are interconnected, with 5GS designed to interwork with EPS for seamless service continuity. The 3rd Generation Partnership Project (3GPP) plays a crucial role in developing and maintaining standards for these telecommunications systems, ensuring global interoperability and evolution from Universal Mobile Telecommunications System (UMTS) (3G) through to the ongoing development of 6G technologies.BRIEF SUMMARY

[0006] Example implementations of the present disclosure are directed to telecommunications and, in particular, to data collection and reporting in a telecommunications system. According to some aspects, the present disclosure includes the subject matter of the independent claims. Some further aspects are defined in the dependent claims.

[0007] The above-referenced and other aspects, features, and advantages of the present disclosure will be apparent from a reading of the following detailed description together with the accompanying figures, which are briefly described below. The present disclosure includes any combination of two, three, four or more features or elements set forth in this disclosure, regardless of whether such features or elements are expressly combined or otherwise recited in a specific example implementation described herein. The present disclosure is intended to be read holistically such that any separable features or elements of the disclosure, in any of its aspects and example implementations, should be viewed as combinable unless the context of the disclosure clearly dictates otherwise.

[0008] It will therefore be appreciated that this Brief Summary is provided merely for purposes of summarizing some example implementations so as to provide a basic understanding of some aspects of the disclosure. Accordingly, it will be appreciated that the above described example implementations are merely examples and should not be construed to narrow the scope or spirit of the disclosure in any way. Other example implementations, aspects and advantages will become apparent from the following detailed description taken in conjunction with the accompanying figures which illustrate, by way of example, the principles of some described example implementations.BRIEF DESCRIPTION OF THE FIGURE(S)

[0009] Having thus described example implementations of the disclosure in general terms, reference will now be made to the accompanying figures, which are not necessarily drawn to scale, and wherein:

[0010] FIG. 1 illustrates a telecommunications system that includes one or more public land mobile networks (PLMNs) coupled to one or more external data networks, according to some example implementations of the present disclosure;

[0011] FIG. 2 illustrates a PLMN, according to some example implementations;

[0012] FIG. 3 illustrates an overview of a portion of a radio protocol stack architecture, according to some example implementations;

[0013] FIG. 4 is a diagram of procedure(s) according to some example implementations;

[0014] FIG. 5 illustrates enforcement of quality of service (QoS) requirements for non-application data at a user equipment (UE), according to some example implementations;

[0015] FIGS. 6, 7, 8, 9, 10 and 11 are flowcharts illustrating various steps in methods according to various example implementations; and

[0016] FIG. 12 illustrates an apparatus according to some example implementations.DETAILED DESCRIPTION

[0017] Some implementations of the present disclosure will now be described more fully hereinafter with reference to the accompanying figures, in which some, but not all implementations of the disclosure are shown. Indeed, various implementations of the disclosure may be embodied in many different forms and should not be construed as limited to the implementations set forth herein; rather, these example implementations are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Like reference numerals refer to like elements throughout. Unless specified otherwise or clear from context, references to first, second or the like should not be construed to imply a particular order but are merely utilized to distinguish one item or operation from another.

[0018] As used herein, unless specified otherwise or clear from context, the “or” of a set of operands is the “inclusive or” and thereby true if and only if one or more of the operands is true, as opposed to the “exclusive or” which is false when all of the operands are true. Thus, for example, “[A] or [B]” is true if [A] is true, or if [B] is true, or if both [A] and [B] are true. Further, the articles “a” and “an” mean “one or more,” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, it should be understood that unless otherwise specified, the terms “data,” “content,” “digital content,” “information,” and similar terms may be at times used interchangeably. The term “network” may refer to a group of interconnected computers including clients and servers; and within a network, these computers may be interconnected directly or indirectly by various means including via one or more switches, routers, gateways, access points or the like.

[0019] The present disclosure discusses telecommunication systems and mobile or cellular networks and user equipment thereof, and while specific terms may be used, are broadly applicable across various technologies. For instance, while the present disclosure may reference radio access technologies such as 5G NR and 5G Advanced, the present disclosure is equally relevant to next generation radio access technologies, such as 6G. Example implementations of the present disclosure described herein alsomention public land mobile networks (PLMNs) and mobile network operators (MNOs), but example implementations are similarly applicable to standalone non-public networks (SNPNs).

[0020] Although some examples and figures focus on radio access networks (RANs) and in particular radio access networks that operate in accordance with the 3GPP standard for 5G NR (generally referred to as 3GPP access or 3GPP access networks), example implementations are applicable to any type of access networks. The applicability to any type of access network includes not only 3GPP access networks but also non-3GPP access networks, such as wireline access, untrusted non-3GPP access network, and trusted non-3GPP access network using wireless access gateway function (W-AGF), non-3GPP interworking function (N3IWF), or trusted non-3GPP gateway function (TNGF) to connect to a core network (e.g., a 5G core network (5GC) or a 6G core network (6GC)) of a mobile or cellular network.

[0021] Further, as used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry); (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); or (c) hardware circuit(s) and / or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0022] The above definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0023] FIG. 1 illustrates a telecommunications system 100 according to various example implementations of the present disclosure. Examples of suitable telecommunications systems include UMTS, EPS and 5GS, as well as the future 6GS. The telecommunications system (otherwise referred to as a system) generally includes one or more mobile or cellular networks. The one or more mobile or cellular networks may interwork with each other. As shown, for example, the system includes one or more PLMNs 102 coupled to one or more other external data networks (DN) 104 - notably including a wide area network (WAN) such as the Internet. As will be appreciated, a PLMN may be a standalone PLMN that includes a 5GC, or may be a non-standalone PLMN that includes both an Evolved Packet Core (EPC) and a 5GC connected to a RAN. Although the system shown includes one or more PLMNs, it will beappreciated that the system may include one or more non-public networks, or one or more PLMNs and one or more non-public networks.

[0024] Each of the PLMNs 102 includes a core network (CN) 106, such as the EPC, the 5GC, or a 6GC; and each CN is coupled to one or more RANs 108 that implement one or more radio access technologies (RATs). Examples of these RANs include the evolved UMTS terrestrial radio access network (E-UTRAN) of 4G LTE, the next generation (NG) radio access network (NG-RAN) of 5G NR, and the 6G RAN. As used herein, a “network device” refers to any suitable device of a RAN or a core network of a telecommunications system. Examples of suitable network devices are described in greater detail below.

[0025] Examples of RATs include 3GPP radio access technologies such as GSM, CDMA2000 1xEV-DO (HRPD), CDMA2000 1x (1xRTT), UTRA, E-UTRA, 5G NR, 5G Advanced, and 6G. Other examples of RATs include IEEE 802 technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.15 (including 802.15.1 (WPAN / Bluetooth), 802.15.4 (Zigbee) and 802.15.6 (WBAN)), Bluetooth, Bluetooth Low Energy (BLE), ultra wideband (UWB), and the like. Generally, a RAT may refer to any 2G, 3G, 4G, 5G, 6G or higher generation RAT and their different versions, as well as to any other RAT that may be arranged to interwork with such a RAT to provide access to the CN 106 of a MNO.

[0026] The telecommunications system 100 also includes one or more communication devices that may be varyingly known as user equipment (UE) 110, terminal device, terminal equipment, mobile station or the like. The UE is generally a device configured to communicate with a network device (e.g., an access node such as a RAN node of RAN 108) or a further UE in the telecommunications system. The UE may be a portable computer (e.g., laptop, notebook, tablet computer), mobile phone (e.g., cell phone, smartphone), wearable computer (e.g., smartwatch), or the like. In other examples, the UE may be an Internet of things (loT) device, an industrial loT (I loT device), a vehicle equipped with a vehicle-to-everything (V2X) communication technology, or the like. In some examples, as referenced by 3GPP, the UE may be a narrowband loT (NB-loT) device, an enhanced machine-type communication (eMTC) device, a reduced capability (RedCap) device, an ambient loT device, or the like.

[0027] In operation, these UEs 110 may connect to one or more RAN nodes of theRANs 108 according to their particular RATs to thereby access a particular CN 106 of a PLMN 102, or to access one or more of the external data networks 104 (e.g., the Internet) or services provided by the PLMN. The external data network may provide Internet access, or 3rd party services (e.g., service provided by 3rd party applications servers). For example, the International Telecommunication Union (ITU) has classified 5G mobile network services (e.g., services provided by a 5G mobile network) into three categories: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine type communications (mMTC) or massive internet of things (MIoT).

[0028] In various examples, a RAN 108 may be configured to provide one or more macrocells, microcells, picocells, femtocells or the like. The RAN may generally include one or more RAN nodes thatinteract with UEs 110. In various examples, a RAN node may be referred to as a base station (BS), access point (AP), base transceiver station (BTS). Examples of RAN nodes include a Node B (NB), evolved NB (eNB), macro BS, NB (MNB) or eNB (MeNB), home BS, NB (HNB) or eNB (HeNB), next generation NB (gNB), enhanced gNB (en-gNB), next generation eNB (ng-eNB), 6G NB (6gNB), or the like. The term ‘gNB’ in 5G NR may correspond to the eNB in 4G LTE. Also, a NG-RAN node may refer to a gNB or a ng-eNB. And unless otherwise specified, a gNB in 5G NR or a 6gNB in 6G may at times be more generally referred to as a (6)gNB or more simply a gNB.

[0029] The RAN 108 may include some type of network controlling / governing entity responsible for control of the RAN nodes. The network controlling / governing entity and RAN node may be separate entities or may be integrated into a single apparatus. The network controlling / governing entity may include processing circuity configured to carry out various management functions for controlling a RAN node or RAN nodes of the RAN. The processing circuity may be associated with a memory, computer-readable storage medium or a data storage device comprising a database for maintaining information required in the various management functions.

[0030] FIG. 2 illustrates an example of a PLMN 102, such as 4G LTE, 5G NR or 6G PLMN that communicates with a UE 110 and an external data network 104 of the telecommunications system 100. As shown, the RAN 108 (e.g., E-UTRAN, NG-RAN, 6G RAN) includes one or more RAN nodes 202 configured to connect one or more UEs to the RAN to thereby access the CN 106 (e.g., EPC, 5GC, 6GC). In 4G LTE, the UE, E-UTRAN and EPC compose the EPS. Similarly, in 5G NR, the UE, NG-RAN and 5GC compose the 5GS. And in 6G, the UE, 6G RAN and 6GC compose the 6GS.

[0031] In some implementations, operations of a gNB or other RAN node 202 may be distributed or functionally split into components including one or more remote radio head (RRHs) or radio units (RUs), and a baseband unit (BBU); and in some implementations, the BBU may be split into a central / centralized unit (CU) (central node) and a distributed unit (DU) (distributed node). The CU may be, for example, a server, host or node. In some implementations, the RRH / RU and DU may be collocated at a network device. It is also possible that operations of a gNB or RAN node may be distributed among a plurality of servers, hosts or nodes.

[0032] It should also be understood that the distribution of work between core network operations and RAN node operations may vary depending on implementation. A 5G or 6G network architecture, for example, may be based on a so-called CU-DU split. One gNB-CU (a CU) may control one or more gNB-DUs (DUs). The gNB-CU may control a plurality of spatially separated gNB-DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some example implementations, however, the gNB-DUs may include, for example, a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the gNB-CU may include the layers above the RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC), and an internet protocol (IP) layer. Other functionalsplits are also possible. It is considered that skilled person is familiar with the open systems interconnection (OSI) model and the functionalities within each layer.

[0033] In some example implementations, the server or CU may generate a virtual network through which the server communicates with the radio node. In general, virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, softwarebased administrative entity, a virtual network. Such virtual network may provide flexible distribution of operations between the server and the radio head / node. In practice, any digital signal processing task may be performed in either the CU or the DU 206, and the boundary where the responsibility is shifted between the CU and the DU may be selected according to implementation.

[0034] As also shown in FIG. 2, the CN 106 may include a number of network functions (NFs) divided between the control plane (CP) and the user plane (UP). In particular, for example, the CN may include, for example, NFs for access and mobility management (MM) (at times referred to as a MM NF) and session management (SM) (at times referred to as a SM NF), as well as a UP NF for reception and transmission of UP traffic (e.g., data).

[0035] The MM NF may be, for example, a mobility management entity (MME) in the EPS, a 5G MM or access and mobility management function (AMF) 204 in the 5GS, or a 6G MM in the 6GS. Similarly, the SM NF may be, for example, a serving gateway (SGW) control plane function (SGW-C) and / or packet data network gateway (PGW) control plane function (PGW-C) in the EPS, a 5G SM or session management function (SMF) 206 in the 5GS, or a 6G SM in the 6GS. The UP NF may be, for example, a SGW user plane function (SGW-U) and / or PGW user plane function (PGW-U) in the EPS, a user plane function (UPF) 208 in the EPS, or the like.

[0036] Another example of a suitable NF in the CN 106 is a policy control (PC) NF, such as a policy and charging function (PCF) 210, a policy and charging rules function (PCRF), or the like. Yet other examples of suitable NFs are NFs responsible for consolidation of subscriber and network-related data, such as a home subscriber server (HSS), a unified data repository (UDR) 212, a unified data management (UDM) 214, or the like.

[0037] FIG. 3 illustrates an overview of a portion of a radio protocol stack 300 architecture, between a UE 110 and a RAN node 202, according to some example implementations. As shown, the radio protocol stack has two different stacks depending on the type of data that is processed by the stack. User data goes through a UP stack 302, signaling messages go through a CP stack 304. Both UP and CP stacks are made up of a common structure including a Layer 1 (L1) with a PHY layer 306, and a layer 2 (L2) with sublayers including MAC 308, RLC 310, and PDCP 312. A layer 3 (L3) sits on topof PHY / MAC / RLC / PDCP, and includes sublayers that are different between the CP and UP. In the UP, L3 includes a sublayer referred to as service data adaptation protocol (SDAP) 314 that may be connected tothe UPF 208 or other suitable NF in the CN 106. In the CP, L3 includes two sublayers referred to as RRC 316 and non-access stratum (NAS) 318, and the NAS layer connects to the AMF 204 in the CN.

[0038] Generally, each layer of the radio protocol stack 300 performs a specific data communications task, a service to and for the layer that precedes it. For example, the RLC 310 provides its services to the PDCP 312. Similarly, the PDCP provides its services to the SDAP 314 (in the UP 302) or the RRC 316 (in the CP 304). The main services or functions of the PDCP include for example: header compression and decompression, transfer of user data, ciphering and deciphering, and timer-based service data unit (SDU) discard.

[0039] The process of layers of the radio protocol stack 300 performing specific data communication tasks can be likened to placing a letter in a series of envelopes before it is sent through the postal system. Each succeeding envelope adds another layer of processing or overhead information necessary to process the transaction. Together, all the envelopes help make sure the letter gets to the right address and that the message received is identical to the message sent. Once the entire package is received at its destination, the envelopes are opened one by one until the letter itself emerges exactly as written.

[0040] A data flow between a source and destination, such as the UE 110 and RAN node 202, is from top to bottom in the source, across the communications line, and then from bottom to top in the destination. Each time, user data passes downward from one layer to the next layer in the source more processing information is added. When that information is removed and processed by the peer layer in the destination, it causes various tasks (error correction, flow control, etc.) to be performed.

[0041] Briefly returning to FIG. 2, 3GPP has agreed to a number of use cases which require artificial intelligence (Al) / machine learning (ML) models (also at times referred to as ML models, or more simply “models”) to be executed in the RAN node 202 only, in the UE 110 only, or partially in the UE and partially in the RAN node. For AI / ML models to be (partly or wholly) executed in the UE, there needs to be functionality for training these AI / ML models. For training these AI / ML models, AI / ML data needs to be collected from the UEs and availed to the training functions. MNOs may require that the AI / ML data used for training be visible to the MNOs.

[0042] In 3GPP, a number of options have been identified through which AI / ML data can be collected for the UE 110 for training AI / ML models that are expected to be used in the UE (so called UE-sided models and corresponding UE-sided AI / ML data collection). The options that have been identified include:1. UE collects and directly transfers training data to an external over-the-top (OTT) server, either transparent or non-transparent;2. UE collects training data and transfers the training data to the CN 106, which transfers the training data to the OTT server.3. UE collects training data and transfers the training data to OAM, which transfers the needed training data to the OTT server.

[0043] Regarding UE-side AI / ML data collection, visibility and controllability of data content and data transfer for the MNO have been identified as two relevant aspects. In this regard, the MNO may be able to manage data transfer to OTT the server for UE-side data collection, including initiating, terminating and fully managing data transfer, without the need of a service level agreement (SLA). Additionally, visibility of the data content may signify that the MNO can, at least, be aware of, access, and comprehend the AI / ML data without the need of a SLA.

[0044] A vendor of UEs 110 or chipsets that enable 3GPP-defined functionalities may desire UE AI / ML data or other non-application data transmitted from UE(s) to a dedicated UE server, which may be located in the ON 106 or operations, administration and maintenance (OAM). In some cases, this dedicated UE server may be owned by the UE / chipset vendor, and used for the purpose of training or retraining AI / ML model(s), such as for AI / ML-based beam management, AI / ML-based positioning, AI / ML-based channel state information (CSI) or the like. The UE AI / ML data may be data of at least one data type among a plurality of data types, such as training data, inference data, monitoring data, ML model(s), or the like. In this context, the transmission of training data from the UE 110 to the dedicated UE server may be more continuous, and the transmission of inference data and monitoring data may be more periodic or intermittent. And the transmission of ML model(s) may also be more intermittent.

[0045] Due to the potentially substantial volume of UE AI / ML data or other non-application data involved, the transmission of the respective data from the UE to the dedicated UE server may need to occur the UP and not the CP. There are a number of possible paths over the UP from the UE to the dedicated UE server. For example, the UE may transmit the AI / ML data to a RAN node 202 which may forward the AI / ML data to a UPF 208 (UP termination), and the UPF may forward the AI / ML data to the dedicated UE server. In another example, the UE may transmit the AI / ML data to a RAN node (UP termination) which may forward the AI / ML data to OAM, and OAM may forward the AI / ML data to the dedicated UE server. And once an AI / ML model is trained in the dedicated UE server, the AI / ML model may be deployed in either or both the UE or RAN node to perform inferences.

[0046] From the perspective of the UP data flow, a number of problems exist that may need to be addressed, including problems related to the treatment of AI / ML data or other non-application data versus application data. In this context, application data refers to data collected in an application layer above the radio protocol stack 300. Conversely, non-application data (e.g., AI / ML data) refers to data collected in at least one layer of the radio protocol stack, such as data collected in the PDCP layer 312, RLC layer 310, MAC layer 308 and / or PHY layer 306. The problems related to the treatment of non-application data more particularly include problems related to differential charging, differential quality of server (QoS), the default data radio bearer (DRB), and one or more configured functionalities.

[0047] In the case of differential charging, it may be desirable for a MNO to not charge UE AI / ML data (non-application data) under a subscription for a UE 110. This differential charging may be due to the AI / MLdata being for a U E / chipset vendor’s operations and not a service consumed by the UE. The AI / ML data may therefore be treated differently (on the UE-side in the uplink, UL) from application data in the UP so that the PCF 210 in the CN 106 can distinguish application and non-application data with respect to charging.

[0048] A problem may also exist in the case of differential QoS for application data versus nonapplication data. The QoS for UE AI / ML data (non-application data) transfer may be differentiated differently from application data transfer in a number of different manners, such as based on the financial agreements (registered in the PCF 210, UDR 212 and / or UDM 214) between the UE / chipset vendor and the MNO of the PLMN 102. The AI / ML data may therefore be treated differently (on the UE-side in the uplink, UL) from application data in the UP so that QoS requirements for application data and non-application data are appropriately handled.

[0049] The CN 106 may provide the UE 110 with QoS rules to match application data (e.g., by application identifier (ID), IP address(es), port number(s), etc.) to route the application data to appropriate QoS flows. Legacy QoS rules, however, are not suitable for matching UE AI / ML data (non-application data) to route the UE AI / ML data to appropriate QoS flows. Similarly, the QoS profiles specified for application services may or may not be applicable for transfer of UE AI / ML data (non-application data). These QoS profiles may be identified by respective identifiers, such as 5G QoS identifiers (5Qls), 6G QoS identifiers (6Qls), or the like. If the QoS profiles are insufficient, new QoS profiles (e.g., 5Qls, 6Qls) may need to be specified as required for the transfer of AI / ML data.

[0050] The default DRB is a DRB within a protocol data unit (PDU) session that serves as a fallback bearer for user data when no specific mapping exists for a given QoS flow. In the case of the default DRB, as indicated above, the transfer of UE AI / ML data over the UP may be continuous, periodic or intermittent depending on the data type of the AI / ML data (e.g., training data, inference data, monitoring data, ML model) being transferred. If certain AI / ML data (e.g., training data) needs to be transferred continuously (with basic QoS requirements), repeatedly creating, modifying and removing a PDU session (and the corresponding QoS flow) may not be an efficient solution due to the amount of signaling required.

[0051] The legacy default PDU session (and corresponding non-guaranteed bit rate (GBR) QoS flow) created for basic application data transfer (e.g., basic internet connection for non-critical data traffic) may not be used for basic UE AI / ML data (e.g., training data) transfer due to differing basic QoS requirements and differing charging rules. And while the legacy default DRB to which the default PDU session (and the corresponding non-GBR QoS flow) may be mapped for basic application data transfer, the differing basic QoS requirements may prevent the legacy default DRB from also being used for basic UE AI / ML data transfer (e.g., training data).

[0052] As a further problem, one or more configured functionalities may also be different for application data and UE AI / ML data (non-application data). Examples of these configured functionality(ies)-1 flinclude ciphering, integrity protection, and the like. In this regard, ciphering and Integrity protection for application data may be necessary for protecting the application data from tampering or eavesdropping, and ensuring that the application data received at the RAN node 202 is exactly what was sent by the UE 110. For UE AI / ML data (non-application data), on the other hand, ciphering and integrity protection may not be needed if the UE AI / ML data is non-sensitive, or a different or simple ciphering and integrity protection mechanism may be needed. Considering ciphering and integrity protection are applied at the PDCP layer 312 at a DRB level, application specific and non-application specific QoS flows may not be mapped to the same DRB (default or dedicated) if application data and non-application data need to be treated differently at the PDCP layer.

[0053] When a UE 110 has AI / ML data (non-application data) to transfer over the user plane, the UE may have a number of options for transfer of the UE AI / ML data. The UE may use of an existing PDU session and the corresponding QoS flow for application data, modify an existing PDU session to add a new QoS flow to transfer the UE AI / ML data, or create a new PDU session and corresponding QoS flow. None of these possibilities, however, address all of the problems identified above for the differential treatment of application data and non-application data end-to-end (UE to RAN 108 to CN 106).

[0054] In view of the foregoing, example implementations of the present disclosure provide solution(s) for the differential treatment of UE application data and UE non-application data (e.g., AI / ML data). In the solution(s) of some example implementations, the RAN node 202 may indicate to the UE 110 a purpose for measurements or other data being requested, such as for a legacy purpose (e.g., mobility, handover, RRM, interference management) or AI / ML. In some examples involving AI / ML data, the RAN node may further indicate data type(s) of AI / ML data (non-application data) being requested, such as training data, inference data, monitoring data, ML model(s), or the like.

[0055] Based on the data type(s) of AI / ML data (non-application data), the UE 110 may add, to the AI / ML data, type information that indicates the data type(s) of the AI / ML data. The AI / ML data may be collected in layer(s) of the radio protocol stack 300, and the type information may be added to the AI / ML data at the layer(s). The AI / ML data may be tagged with the type information, or the type information may be added to a header of the AI / ML data. In some examples, the type information that indicates each data type may be added to a header of the AI / ML data of the data type. The AI / ML data with the added type information may then be transferred from the layer(s) of the radio protocol stack toward a higher-layer functionality above the layer(s) at which the AI / ML data may be mapped to non-application specific QoS flow(s) created to carry the AI / ML data and associated with the data type(s) of the AI / ML data.

[0056] In the solution(s) of some example implementations, the CN 106 may determine QoS profile(s) based on the data type(s) of AI / ML data. The CN may then create non-application specific QoS flow(s) associated with a PDU session based on the QoS profile(s) to carry the AI / ML data, which may be differentiated from other, application specific QoS flow(s) created to carry application data. The QoS flow(s)may also be associated with the data type(s) of the AI / ML data. Likewise, the CN may determine QoS rule(s) for different data types of AI / ML data (non-application data). The QoS rule(s) may be configured to the UE 110 for the UE to apply to map the AI / ML data by data type to the non-application specific QoS flow(s), such as based on charging agreements between a UE / chipset vendor and MNO.

[0057] Additionally or alternatively, in the solution(s) of some example implementations, the RAN node 202 may create a two default DRBs for the PDU session. The RAN node may create a default DRB for the PDU session to carry application specific QoS flow(s) to carry application data, and a second default DRB for the PDU session to carry the non-application specific QoS flow(s) to carry the AI / ML data (non-application data). The RAN node may also provide an overall configuration of parameters (e.g., SDAP layer 314, PDCP layer 312 parameters) for non-application specific DRB(s) to the UE 110, which may be enabled to differentiate DRBs (default or dedicated) as application-specific DRB(s) and non-application specific DRB(s) for different data type(s) of AI / ML data.

[0058] As indicated above and described below, a non-application specific QoS flow refers to a QoS flow dedicated to carry non-application data (e.g., AI / ML data) based on a QoS profile specified for non-application services. Likewise, an application specific QoS flow refers to a QoS flow dedicated to carry application data based on a QoS profile specified for application services. A non-application specific DRB refers to a DRB dedicated to carry a non-application specific QoS flow, and an application specific DRB refers to a DRB dedicated to carry an application specific QoS flow, in some examples, one or more configured functionalities for an application specific DRB may be disabled for the non-application specific DRB, such as ciphering and integrity protection.

[0059] According to some example implementations, a RAN node 202 may configure a UE 110 with a configuration for collection of non-application data of data type(s) among a plurality of data types of non-application data, and the configuration may indicate the data type(s) of the non-application data to be collected. The UE may receive the configuration, and send a PDU session request message to request establishment or modification of a PDU session, and the PDU session request may include an indication that the PDU session request is for non-application data. In some examples, the PDU session request may also indicate the data type(s) of the non-application data.

[0060] The CN 106 (e.g., SMF 206) may receive the PDU session request message, and determine QoS profile(s) based on the data type(s) of the non-application data. The CN (e.g., SMF) may create, based on the QoS profile(s), non-application specific QoS flow(s) to carry the non-application data and associated with the data type(s) of the non-application data. In some examples, the CN may also determine QoS rule(s) to be applied to map the non-application data by data type to the non-application specific QoS flow(s). The CN may then send, toward the UE 110, a PDU session accept message that indicates the non-application specific QoS flow(s) for the non-application data. The PDU session accept message may also include information that indicates the QoS rule(s).

[0061] In some examples, the CN 106 may also send, toward the RAN node 202 serving the UE, information that indicates the non-application specific QoS flow(s), and that indicates the QoS profile(s) associated with the non-application specific QoS flow(s). The RAN node may receive the information, and create non-application specific DRB(s) to carry the non-application specific QoS flow(s) based on the QoS profile(s). The RAN node may determine a mapping of the non-application specific QoS flow(s) to the non-application specific DRB(s). And the RAN node may configure the UE with at least one configuration that indicates the non-application specific DRB(s) and the mapping of the non-application specific QoS flow(s) to the non-application specific DRB(s).

[0062] The UE 110 may collect the non-application data of the data type(s). The UE may add, to the non-application data, type information that indicates the data type(s) of the non-application data, such as based on the configuration received from the RAN node 202. The UE may map the non-application data based on the type information to non-application specific QoS flow(s) (associated with the PDU session) created to carry the non-application data and associated with the data type(s) of the non-application data. In some examples, the UE may apply the QoS rule(s) to map the non-application data based on the type information to the non-application specific QoS flow(s) created to carry the non-application data and associated with the data type(s) of the non-application data. The UE may then map the non-application specific QoS flow(s) to non-application specific DRB(s) (associated with the PDU session), and transfer the non-application data on the non-application specific QoS flow(s) over the non-application specific DRB(s).

[0063] FIG. 4 is a diagram of procedure(s) according to some example implementations. The procedure(s) involve AI / ML data, but it should be understood that the procedure(s) are equally applicable to other non-application data (i.e., data collected in layer(s) of the radio protocol stack 300).

[0064] As shown at step 400, a vendor (e.g., UE / chipset vendor) may register subscription information in the PCF 210 of the CN 106. The subscription information may include, for example, charging information that indicates how much the vendor will be charged to collect UE AI / ML data (non-application data) from UE(s) 110. The subscription information may also include QoS profiles for the UE AI / ML data that defines the QoS parameters for different data types of the AI / ML data (e.g., training, inference, monitoring, model). In some examples, QoS profile(s) for the data type(s) of AI / ML data may be introduced within GBR, non-GBR or delay-critical GBR categories based on the vendor subscription. The QoS profile(s) may include respective identifiers (e.g., 5Qls, 6Qls), allocation and retention priorities (ARPs), and the like.

[0065] The vendor may at some point request data collection from one or more UEs 110, such as via a data collection request from an application function (AF) of the vendor to the AMF 204 in the CN 106. The AMF may forward the data collection request to the RAN node 202 serving UE(s) connected to the RAN 108 at step 401, and the RAN node may determine whether the request is for a legacy purpose (e.g., mobility, handover, RRM, interference management) or non-application data (e.g., AI / ML data). When therequest is for non-application data, the RAN node may also determine the data type(s) of the nonapplication data being requested. In the case of AI / ML data, the RAN node may determine the data type(s) (e.g., training, inference, monitoring, model) of the AI / ML data being requested.

[0066] The RAN node 202 may at step 402 configure the UE(s) with a configuration for the collection of the data. In some examples, the configuration may be a measurement configuration or logged measurement configuration (e.g., RRC measurement configuration), and the RAN node may send the configuration by a RRC reconfiguration message. In the configuration, the RAN node may indicate whether the data is to be collected for a legacy purpose or AI / ML (non-application); and when the data is to be collected for AI / ML, the RAN node may indicate the data type(s) of AI / ML data to be collected. As described below, at step 402A, the UE may use the indication of the purpose and data type(s) in the configuration to add type information to AI / ML data that is collected at layer(s) of the radio protocol stack 300, before the AI / ML data is transferred over the UP.

[0067] The UE 110 may decide to initiate a new PDU session to add a non-application specific QoS flow, or modify an existing PDU session to add a non-application specific QoS flow. The UE may then at step 403 send a PDU session request message to the CN 106 to request establishment or modification of a PDU session. In particular, for example, the UE may send the PDU session request to the AMF 204, and the AMF may forward the PDU session request to the SMF 206. The PDU session request message may include an indication that the PDU session request message is for a legacy purpose, AI / ML (non-application), or both.

[0068] In some examples in which the PDU session request indicates the purpose is for AI / ML, the PDU session request from the UE 110 may further indicate the data type(s) of AI / ML data being requested. In some examples, the PDU session request may include a data network name (DNN) attribute that is set to a value indicating the PDU session is for AI / ML data (non-application data), and which may also indicate the data type(s) of the AI / ML data.

[0069] In some more particular examples, the PDU session request may include two DNN attributes, one for application data (e.g., DNN-application = “service name”), and another for non-application data (e.g., DNN-non-application = “AI / ML data type”), either but not both of which may be set to “None.” The “service name” in the DNN attribute for application data may be as currently specified in 3GPP (e.g., “ims”). The “AI / ML data type” in the DNN attribute for non-application data may be set to a value having any of a number of different granularities, such as:Training data, inference data, monitoring data, ML model(s), etc.PHY-layer data, MAC-layer data, etc.Positioning data, CSI data, beam management data, etc.Other non-application data, e.g., sensing data, etc.

[0070] In some other more particular examples, the PDU session request may include a flag attribute that is set to a value indicating the PDU session is for non-application data. For example, the PDU session request may include a flag attribute APPLICATION set to “YES” or “NO” to indicate whether the requested PDU session is for application data or non-application data. In some of these example, the PDU session request may also include a DNN attribute that may be set to a value indicating the requested PDU session is for application data (e.g., “service name”), or indicating the data type(s) of the non-application data (e.g., “AI / ML data type”). The PDU session request may therefore in these other particular examples also achieve the granularity in the earlier more particular examples.

[0071] In some examples in which the AI / ML data (non-application data) is requested by a vendor (e.g., UE / chipset vendor), the PDU session request may also include information that indicates the vendor. The CN 106 (e.g., SMF 206, PCF 210) may use this information to appropriately charge the vendor to whom the AI / ML data is being transferred over the UP.

[0072] Upon receiving the PDU session request, the SMF 206 in the CN 106 may obtain policies related to the PDU session for the AI / ML data (non-application data), such as traffic steering and access control policies. These policies may depend on the subscription information registered at step 400 for the vendor to whom the AI / ML data is being transferred over the UP. The SMF may initiate an N4 session procedure in which the UPF may configure UP resources for the PDU session. The SMF may also, to a charging function (CHF) in the CN 106, a charging data request for the PDU session which may indicate the PDU session is for AI / ML data, and identify the vendor.

[0073] If the PDU session request for the AI / ML data (non-application data) is a first for UE 110, the SMF 206 in the CN 106 may determine QoS profile(s) (e.g., new 5Qls, 6Qls) based on the data type(s) of the AI / ML data (e.g., from the subscription information registered at step 400). The SMF may at step 404 create non-application specific QoS flow(s) based on the QoS profile(s). The non-application specific QoS flow(s) may therefore be created to carry the AI / ML data and associated with the data type(s) of the AI / ML data. In some examples, the non-application specific QoS flow(s) may be created with basic or default QoS profile(s) which may be different from the basic or default QoS profile(s) suitable for internet browsing for legacy application-specific QoS flow(s).

[0074] As shown at step 405, the CN 106 may send, toward the UE 110, a PDU session accept message, such as a PDU session establishment accept message or a PDU session modification accept message, that indicates the non-application specific QoS flow(s) for the AI / ML data (non-application data). In particular, for example, the SMF 206 may send a PDU session accept message toward the UE via the AMF 204. In some examples, such as when the PDU session request is a first for the UE, the SMF may determine QoS rule(s) to be applied by the UE to map the AI / ML data by data type to the non-application specific QoS flow(s). In these examples, the PDU session accept message may also include information that indicates the QoS rule(s).

[0075] As indicated above and described below, the UE 110 may apply the QoS rule(s) to match and distinguish the AI / ML data from legacy application data before packets of the AI / ML data (non-application data) are fed to the SDAP layer 314 of the radio protocol stack 300. In the case of legacy application data, QoS rules may include matching rules to classify packets of application data (e.g., on application ID, destination IP address, etc.) to application specific QoS flow IDs (QFIs). The QoS rule(s) for nonapplication data may include respective matching rule(s) to classify packets into non-application specific QFI(s).

[0076] In a first level, for example, a QoS rule for AI / ML data (non-application data) may include a matching rule to match packets without an application ID (e.g., application ID = None) to a non-application specific QoS flow ID (QFI) for AI / ML data. And in a second level, for example, QoS rules may include matching rules to match packets of AI / ML data by data type to non-application specific QFI(s) associated data type(s) of the AI / ML data. Packets of training data may therefore be matched to a non-application specific QFI associated with training data. Packets of inference data may be matched to a non-application specific QFI associated with inference data. Packets of monitoring data may be matched to a non-application specific QFI associated with monitoring data. And so forth.

[0077] The CN 106 may also send, toward the RAN node 202, information that indicates the non-application specific QoS flow(s) (e.g., QFI(s)), and that indicates the QoS profile(s) (e.g., new 5Qls, 6Qls) associated with the non-application specific QoS flow(s). In some examples, the SMF 204 may send the information to the AMF 206, and the AMF may at step 406 forward the information to the RAN node, such as in an N2 PDU session request. Similarly, the RAN node may receive information that indicates any application specific QoS flow(s) and QoS profile(s) associated with the application specific QoS flow(s). In some examples, the QoS profiles may each include a tag associated with a QoS flow that indicates whether the QoS flow is an application specific QoS flow or a non-application specific QoS flow.

[0078] The RAN node 202 may create non-application specific DRB(s) to carry the non-application specific QoS flow(s) based on the QoS profile(s) for the AI / ML data (non-application data). Similarly, the RAN nod may create application specific DRB(s) to carry any application specific QoS flow(s) based on QoS profile(s) for application data. In some examples, the RAN node may create a default DRB for the PDU session to carry application specific QoS flow(s) to carry application data, and a second default DRB for the PDU session to carry non-application specific QoS flow(s). And in some examples, one or more configured functionalities for the application specific DRB(s) may be disabled for the non-application specific DRB(s), such as ciphering and integrity protection.

[0079] The RAN node 202 may also determine a mapping of the non-application specific QoS flow(s) (e.g., QFI(s)) to the non-application specific DRB(s). Similarly, in some examples, the mapping may include any application specific QoS flow(s) to application specific DRB(s).

[0080] The RAN node 202 may then at steps 407A, 407B configure the UE 110 with configuration(s) that indicates at least the non-application specific DRB(s) and the mapping of the non-application specific QoS flow(s) to the non-application specific DRB(s). The configuration(s) may also indicate any application specific DRB(s), and the mapping may include application specific QoS flow(s) to the non-application specific DRB(s). In some examples in which a QoS flow is mapped to a default DRB, as there are may be two default DRBs, the mapping may indicate whether the QoS flow is mapped to the default DRB to carry application specific QoS flow(s), or the second default DRB to carry non-application specific QoS flow(s). As shown, the RAN node may configure the UE with the configuration(s) by RRC reconfiguration, such as radio bearer SDAP configuration, radio bearer PDCP configuration, or the like.

[0081] Once configured, the UE 110 may enforce the QoS requirements for the non-application data (and any application data) indicated by the QoS rule(s) and QoS profile(s) associated with the non-application specific QoS flow(s). FIG. 5 illustrates enforcement of QoS requirements for non-application data at the UE, according to some example implementations. As shown, for example, the UE may collect AI / ML data (non-application data) in at least one layer of the radio protocol stack, such as in the PDCP layer 312, RLC layer 310, MAC layer 308 and / or PHY layer 306.

[0082] The UE 110 may add type information that indicates the data type(s) (e.g., training, inference, monitoring, model) of the AI / ML data at the respective layer(s) of the radio protocol stack 300, such as by a tag or in a header of the AI / ML data. For example, the PDCP layer 312 may add a header (e.g., PDCPAIML-header) to packets of AI / ML data collected in the PDCP layer to indicate the data type of the AI / ML data. The RLC layer 310 may add a header (e.g., RLCAIML-header) to packets of AI / ML data collected in the RLC layer to indicate the data type of the AI / ML data. The MAC layer 308 may add a header (e.g., MACAIML-header) to packets of AI / ML data collected in the MAC layer to indicate the data type of the AI / ML data. And the PHY layer 306 may add a header (e.g., PHYAIML-header) to packets of AI / ML data collected in the PHY layer to indicate the data type of the AI / ML data.

[0083] The UE 110 may transfer the AI / ML data with the added type information, from the layer(s) of the radio protocol stack 300, to higher-layer functionality above the layer(s). The AI / ML data may then be mapped to the non-application specific QoS flow(s) at the higher-layer functionality, such as by application of QoS rule(s). As indicated above, in a first level, for example, a QoS rule for AI / ML data (non-application data) may include a matching rule to match packets without an application ID (e.g., application ID = None) to a non-application specific QFI for AI / ML data. And in a second level, for example, QoS rules may include matching rules to match packets of AI / ML data by data type to non-application specific QFI(s) associated data type(s). These QoS rules may include matching rules to match type information in headers (e.g., PDCPAIML-header, RLCAIML-header, MACAIML-header, PHYAIML-header) of the packets to QFIs associated with the data types indicated by the type information.

[0084] The UE 110 may therefore map the AI / ML data may then be mapped to the non-application specific QoS flow(s). The UE may similarly map any application data to application specific QoS flow(s). As also shown, the UE may map the non-application specific QoS flow(s) to the non-application specific DRB(s) (default or dedicated), and map any application specific QoS flow(s) to application specific DRB(s) (default or dedicated). As indicated above, one or more configured functionalities may be configured as disabled for the non-application specific DRB(s), such as ciphering and integrity protection. The AI / ML data may then be transferred on the non-application specific QoS flow(s) over the non-application specific DRB(s), and any application data may be transferred on the application specific QoS flow(s) over the application specific DRB(s).

[0085] FIG. 6 is a flowchart illustrating various steps in a method 600 according to various example implementations. The method includes collecting non-application data of at least one data type among a plurality of data types of non-application data, as shown at block 602. The method includes adding, to the non-application data, type information that indicates the at least one data type of the non-application data, as shown at block 604. The method includes mapping the non-application data based on the type information to at least one non-application specific quality of service (QoS) flow created to carry the non-application data and associated with the at least one data type of the non-application data, as shown at block 606. The method includes mapping the at least one non-application specific QoS flow to at least one non-application specific data radio bearer (DRB), as shown at block 608. And the method includes transferring the non-application data on the at least one non-application specific QoS flow over the at least one non-application specific DRB, as shown at block 610.

[0086] In some examples, the method 600 further includes receiving a configuration for collection of the non-application data, and the configuration indicates the at least one data type of the non-application data to be collected. In some of these examples, the type information is added to the non-application data at block 604 based on the configuration.

[0087] In some examples, the type information that indicates each data type of the at least one data type is added at block 604 to a header of the non-application data of the data type.

[0088] In some examples, the non-application data is collected at block 602 in at least one layer of a radio protocol stack. In some of these examples, the type information is added to the non-application data at block 604 at the at least one layer.

[0089] In some examples, the method 600 further includes transferring the non-application data with the added type information, from the at least one layer, toward a higher-layer functionality above the at least one layer of the radio protocol stack. In some of these examples, the non-application data is mapped at block 606 to the at least one non-application specific QoS flow at the higher-layer functionality.

[0090] In some examples, the at least one non-application specific QoS flow is associated with a protocol data unit (PDU) session for which a default DRB is created to carry at least one applicationspecific QoS flow created to carry application data. In some of these examples, a second default DRB is created to carry at least one non-application specific QoS flow.

[0091] In some examples, the at least one non-application specific DRB to which the at least one non-application specific QoS flow is mapped at block 608 includes the second default DRB.

[0092] In some examples, one or more configured functionalities are configured as disabled for the at least one non-application specific DRB to which the at least one non-application specific QoS flow.

[0093] FIG. 7 is a flowchart illustrating various steps in a method 700 according to various example implementations. The method includes configuring a user equipment (UE) with a configuration for collection of non-application data of at least one data type among a plurality of data types of non-application data, the configuration indicating the at least one data type of the non-application data to be collected, as shown at block 702. The method includes receiving information that indicates at least one non-application specific quality of service (QoS) flow created to carry the non-application data and associated with the at least one data type of the non-application data, and that indicates at least one QoS profile associated with the at least one non-application specific QoS flow, as shown at block 704. The method includes creating at least one non-application specific data radio bearer (DRB) to carry the at least one non-application specific QoS flow based on the at least one QoS profile, as shown at block 706. The method includes determining a mapping of the at least one non-application specific QoS flow to the at least one non-application specific DRB, as shown at block 708. And the method includes configuring the UE with at least one configuration that indicates the at least one non-application specific DRB and the mapping of the at least one non-application specific QoS flow to the at least one non-application specific DRB, as shown at block 710.

[0094] In some examples, the at least one non-application specific QoS flow is associated with a protocol data unit (PDU) session. In some of these examples, the method further includes creating a default DRB for the PDU session to carry at least one application specific QoS flow to carry application data, and a second default DRB for the PDU session to carry at least one non-application specific QoS flow.

[0095] In some examples, the at least one non-application specific DRB created to carry the at least one non-application specific QoS flow at block 706 includes the second default DRB.

[0096] In some examples, the at least one configuration further indicates that one or more configured functionalities are disabled for the at least one non-application specific DRB.

[0097] FIG. 8 is a flowchart illustrating various steps in a method 800 according to various example implementations. The method includes receiving a configuration for collection of non-application data of at least one data type among a plurality of data types of non-application data, as shown at block 802. The method includes sending a protocol data unit (PDU) session request message to request establishment or modification of a PDU session, the PDU session request message including an indication that the PDUsession request message is for the non-application data, as shown at block 804. The method includes collecting the non-application data of the at least one data type, as shown at block 806. The method includes adding, to the non-application data, type information that indicates the at least one data type of the non-application data, as shown at block 808. The method includes mapping the non-application data based on the type information to at least one non-application specific quality of service (QoS) flow associated with the PDU session, the at least one non-application specific QoS flow created to carry the non-application data and associated with the at least one data type of the non-application data, as shown at block 810. And the method includes mapping the at least one non-application specific QoS flow to at least one non-application specific data radio bearer (DRB) for the PDU session, as shown at block 812.

[0098] In some examples, the indication that the PDU session request message is for the non-application data includes a data network name (DNN) attribute in the PDU session request that is set to a value indicating the PDU session is for non-application data. In some of these examples, the value to which the DNN attribute is set further indicates the at least one data type of the non-application data.

[0099] In some examples, the indication that the PDU session request message is for non-application data includes a flag attribute in the PDU session request message that is set to a value indicating the PDU session is for non-application data. In some of these examples, the PDU session request message further includes a data network name (DNN) attribute that is set to a value indicating the at least one data type of the non-application data.

[0100] In some examples, the non-application data is requested by a vendor, and the PDU session request message further includes information that indicates the vendor.

[0101] In some examples, the type information that indicates each data type of the at least one data type is added to a header of the non-application data of the data type.

[0102] In some examples, the non-application data is collected at block 806 in at least one layer of a radio protocol stack. In some of these examples, the type information is added to the non-application data at block 808 at the at least one layer.

[0103] In some examples, the method 800 further includes transferring the non-application data with the added type information, from the at least one layer, toward a higher-layer functionality above the at least one layer of the radio protocol stack. In some of these examples, the non-application data is mapped at block 810 to the at least one non-application specific QoS flow at the higher-layer functionality.

[0104] In some examples, the at least one non-application specific QoS flow is associated with the PDU session for which a default DRB is created to carry at least one application specific QoS flow created to carry application data, and a second default DRB is created to carry at least one non-application specific QoS flow.

[0105] In some examples, the at least one non-application specific DRB to which the at least one non-application specific QoS flow is mapped at block 812 includes the second default DRB.

[0106] In some examples, one or more configured functionalities are configured as disabled for the at least one non-application specific DRB to which the at least one non-application specific QoS flow.

[0107] FIG. 9 is a flowchart illustrating various steps in a method 900 according to various example implementations. The method includes receiving, from a user equipment (UE), a protocol data unit (PDU) session request message to request establishment or modification of a PDU session for non-application data of at least one data type among a plurality of data types of non-application data, as shown at block 902. The method includes determining at least one QoS profile based on the at least one data type of the non-application data, as shown at block 904. The method includes creating, based on the at least one QoS profile, at least one non-application specific quality of service (QoS) flow to carry the non-application data and associated with the at least one data type of the non-application data, as shown at block 906. And the method includes sending, toward the UE, a PDU session accept message that indicates the at least one non-application specific QoS flow for the non-application data, as shown at block 908.

[0108] In some examples, the PDU session request message includes a data network name (DNN) attribute that is set to a value indicating the PDU session is for non-application data. In some of these examples, the value to which the DNN attribute is set further indicates the at least one data type of the non-application data.

[0109] In some examples, the PDU session request message includes a flag attribute that is set to a value indicating the PDU session is for non-application data. In some of these examples, the PDU session request message further includes a data network name (DNN) attribute that is set to a value indicating the at least one data type of the non-application data.

[0110] In some examples, the non-application data is requested by a vendor, and the PDU session request message further includes information that indicates the vendor.

[0111] In some examples, the method 900 further includes sending, to a charging function, a charging data request for the PDU session. In some of these examples, the charging data request indicates the PDU session is for the non-application data, and the charging data request identifies the vendor.

[0112] In some examples, the method 900 further includes sending, toward a radio access network (RAN) node serving the UE, information that indicates the at least one non-application specific QoS flow, and that indicates at least one QoS profile that is associated with the at least one non-application specific QoS flow.

[0113] FIG. 10 is a flowchart illustrating various steps in a method 1000 according to various example implementations. The method includes receiving a configuration for collection of non-application data of at least one data type among a plurality of data types of non-application data, as shown at block 1002. The method includes receiving information indicating at least one quality of service (QoS) rule to be applied to map the non-application data by data type to at least one non-application specific QoS flow associated withthe at least one data type of the non-application data, as shown at block 1004. The method includes collecting the non-application data of the at least one data type, as shown at block 1006. The method includes adding, to the non-application data, type information that indicates the at least one data type of the non-application data, as shown at block 1008. The method includes applying the at least one QoS rule to map the non-application data based on the type information to the at least one non-application specific QoS flow created to carry the non-application data and associated with the at least one data type of the non-application data, as shown at block 1010. And the method includes mapping the at least one non-application specific QoS flow to at least one non-application specific data radio bearer (DRB), as shown at block 1012.

[0114] In some examples, the type information that indicates each data type of the at least one data type is added at block 1008 to a header of the non-application data of the data type.

[0115] In some examples, the non-application data is collected at block 1006 in at least one layer of a radio protocol stack. In some of these examples, the type information is added to the non-application data at block 1008 at the at least one layer.

[0116] In some examples, the method 1000 further includes transferring the non-application data with the added type information, from the at least one layer, toward a higher-layer functionality above the at least one layer of the radio protocol stack. In some of these examples, the at least one QoS rule is applied at block 1010 to map the non-application data to the at least one non-application specific QoS flow at the higher-layer functionality.

[0117] In some examples, the method 1000 further includes sending a protocol data unit (PDU) session request message to request establishment or modification of a PDU session. In some of these examples, the PDU session request message includes an indication that the PDU session request message is for the non-application data.

[0118] In some examples, receiving the information indicating the at least one QoS rule at block 1004 comprises receiving a PDU session accept message that includes the information indicating the at least one QoS rule.

[0119] In some examples, the at least one non-application specific QoS flow is associated with a protocol data unit (PDU) session for which a default DRB is created to carry at least one application specific QoS flow created to carry application data, and a second default DRB is created to carry at least one non-application specific QoS flow.

[0010] In some examples, the at least one non-application specific DRB to which the at least one non-application specific QoS flow is mapped at block 1012 includes the second default DRB.

[0121] In some examples, one or more configured functionalities are configured as disabled for the at least one non-application specific DRB to which the at least one non-application specific QoS flow.

[0122] FIG. 11 is a flowchart illustrating various steps in a method 1100 according to various example implementations. The method includes receiving, from a user equipment (UE), a protocol data unit (PDU) session request message to request establishment or modification of a PDU session for non-application data of at least one data type among a plurality of data types of non-application data, as shown at block 1102. The method includes determining at least one QoS profile based on the at least one data type of the non-application data, as shown at block 1104. The method includes creating, based on the at least one QoS profile, at least one non-application specific quality of service (QoS) flow to carry the non-application data and associated with the at least one data type of the non-application data, as shown at block 1106. The method includes determining at least one QoS rule to be applied to map the non-application data by data type to the at least one non-application specific QoS flow, as shown at block 1108. And the method includes sending, toward the UE, a PDU session accept message that indicates the at least one non-application specific QoS flow for the non-application data, and that includes information indicating the at least one QoS rule, as shown at block 1110.

[0123] In some examples, the PDU session request message includes a data network name (DNN) atribute that is set to a value indicating the PDU session is for non-application data. In some of these examples, the value to which the DNN attribute is set further indicates the at least one data type of the non-application data.

[0124] In some examples, the PDU session request message includes a flag atribute that is set to a value indicating the PDU session is for non-application data. In some of these examples, the PDU session request message further includes a data network name (DNN) atribute that is set to a value indicating the at least one data type of the non-application data.

[0125] In some examples, the non-application data is requested by a vendor, and the PDU session request message further includes information that indicates the vendor.

[0126] In some examples, the method 1100 further includes sending, to a charging function, a charging data request for the PDU session. In some of these examples, the charging data request indicates the PDU session is for the non-application data, and the charging data request identifies the vendor.

[0127] In some examples, the method 1100 further includes sending, toward a radio access network (RAN) node serving the UE, information that indicates the at least one non-application specific QoS flow, and that indicates at least one QoS profile that is associated with the at least one non-application specific QoS flow.

[0128] According to example implementations of the present disclosure, a telecommunications system 100 or PLMN 102, and components thereof such as UE 110, CN 106, RAN 108, RAN node 202, MM NF (e.g., AMF 204), SM NF (e.g., SMF 206), UPF 208, PC NF (e.g., PCF 210), UDR 212 and / or UDM 214, may be implemented by various means. Means for implementing the system and its components mayinclude hardware, firmware, software, or combinations thereof. In some examples, one or more apparatuses may be configured to function as or otherwise implement the system and its components shown and described herein. In examples involving more than one apparatus, the respective apparatuses may be connected to or otherwise in communication with one another in a number of different manners, such as directly or indirectly via a wired or wireless network or the like.

[0129] According to some example implementations, at least some of the methods 600, 700 described with respect to FIG. 6 and FIG. 7 may be carried out by apparatuses comprising means for performing functions corresponding steps of the respective methods. Similarly, at least some of the methods 800, 900 described with respect to FIG. 8 and FIG. 9 may be carried out by apparatuses comprising means for performing functions corresponding steps of the respective methods. And at least some of the methods 1000, 1100 described with respect to FIG. 10 and FIG. 11 may be carried out by apparatuses comprising means for performing functions corresponding steps of the respective methods. Examples of a suitable apparatus may include a user equipment, user device, user terminal or the like. Other examples of a suitable apparatus may include a RAN node (e.g., ng-eNB, gNB, gNB-DU, gNB-CU) or any suitable apparatus, such as a server, host or node. Yet other examples of a suitable apparatus may include standalone computer comprising an SM NF (e.g., SMF), such as a server, host or node, a distributed computing system comprising an SM NF, or a cloud computing system comprising an SM NF. The SM NF may be implemented as a virtual machine or a container by a distributed computing system or a cloud computing system.

[0130] FIG. 12 illustrates an apparatus 1200 in which means for performing various operations includes hardware, alone or under direction of one or more computer programs from a computer-readable storage medium or other memory, such as computer memory, according to some example implementations of the present disclosure. The apparatus may include one or more of each of a number of components such as, for example, processing circuitry 1202 connected to computer-readable storage medium or other memory 1204.

[0131] The processing circuitry 1202 may be composed of one or more processors alone or in combination with one or more computer-readable storage media. The processing circuitry is generally any piece of computer hardware that is capable of processing information such as, for example, data, computer programs, computer code and / or other suitable electronic information. The processing circuitry is composed of a collection of electronic circuits some of which may be packaged as an integrated circuit or multiple interconnected integrated circuits (an integrated circuit at times more commonly referred to as a “chip”). The processing circuitry may be configured to execute computer programs, which may be stored onboard the processing circuitry or otherwise stored in the memory 1204 (of the same or another apparatus).

[0132] The processing circuitry 1 02 may comprise a number of processors, a multi-core processor or some other type of processor, such as a central processing unit, a graphics processing unit, a tensor processing, unit, or an accelerator, depending on the particular implementation. Further, the processing circuitry may be implemented using a number of heterogeneous processor systems in which a main processor is present with one or more secondary processors on a single chip. As another illustrative example, the processing circuitry may be a symmetric multi-processor system containing multiple processors of the same type. In yet another example, the processing circuitry may be embodied as or otherwise include one or more application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or the like. Thus, although the processing circuitry may be capable of executing a computer program to perform one or more functions, the processing circuitry of various examples may be capable of performing one or more functions without the aid of a computer program. In either instance, the processing circuitry may be appropriately programmed to perform functions or operations according to example implementations of the present disclosure.

[0133] The memory 1204 is generally any piece of computer hardware that is capable of storing information such as, for example, data, computer programs, instructions 1206 (e.g., computer-readable program code) and / or other suitable information either on a temporary basis and / or a permanent basis. The memory may include volatile and / or non-volatile memory, and may be fixed or removable. Examples of suitable memory include recording media, random access memory (RAM), read-only memory (ROM), a hard drive, a flash memory, a thumb drive, a removable computer diskette, an optical disk or some combination thereof.

[0134] The memory 1204 is a non-transitory device capable of storing information. One example of a suitable memory is a computer-readable storage medium, which is distinguishable from a computer-readable transmission medium capable of carrying information from one location to another. Examples of suitable computer-readable transmission media comprise electronic carrier signals, telecommunications signals, or some combination thereof. As used herein, the term “non-transitory” is a limitation of the medium itself (i.e. , tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM versus ROM). A computer-readable medium as described herein generally refers to a computer-readable storage medium or computer-readable transmission medium. A computer-readable medium is any entity or device capable in which information, such as one or more computer programs or portions thereof, may be stored and carried.

[0135] In addition to the memory 1204 (e.g., computer-readable storage medium), the processing circuitry 1202 may also be connected to one or more interfaces for displaying, transmitting and / or receiving information. The interfaces may include a communications interface 1208 and / or one or more user interfaces. The communications interface may be configured to transmit and / or receive information, such as to and / or from other apparatus(es), network(s) or the like. The communications interface may beconfigured to transmit and / or receive information by physical (wired) and / or wireless communications links. Examples of suitable communication interfaces include a network interface controller (NIC), wireless NIC (WNIC) or the like.

[0136] The user interfaces may include a display 1210 and / or one or more user input interfaces 1212. The display may be configured to present or otherwise display information to a user, suitable examples of which include a liquid crystal display (LCD), light-emitting diode (LED) display, organic LED (OLED) display, active-matrix OLED (AMOLED) or the like. The user input interfaces may be wired or wireless, and may be configured to receive information from a user into the apparatus, such as for processing, storage and / or display. Suitable examples of user input interfaces include a microphone, image or video capture device, keyboard or keypad, joystick, touch-sensitive surface (separate from or integrated into a touchscreen), biometric sensor or the like. The user interfaces may further include one or more interfaces for communicating with peripherals such as printers, scanners or the like.

[0137] Execution of the instructions 1206 by the processing circuitry 1202, or storage of the instructions in the memory 1204, supports combinations of operations for implementing example implementations of the present disclosure. In this manner, an apparatus 1200 may comprise at least one processing circuitry and at least one memory coupled to the at least one processing circuitry, where the at least one processing circuitry is configured to execute instructions stored in the at least one memory. It will also be understood that one or more functions, and combinations of functions, may be implemented by special purpose hardware-based computer systems and / or processing circuitry which perform the specified functions, or combinations of special purpose hardware and program code instructions.

[0138] Some example implementations of the present disclosure may also be carried out in the form of a computer process defined by one or more computer programs or portions thereof. Example implementations of the present disclosure may be carried out by executing at least one portion of a computer program comprising instructions. The computer program may be in source code form, object code form, or in some intermediate form. The computer program may be stored in a computer-readable medium that is readable by a computer, processing circuitry or other suitable apparatus. As indicated above, for example, the computer program may be stored in a memory, such as a computer-readable storage medium. Additionally or alternatively, for example, the computer program may be stored in a computer-readable transmission medium. The coding of software for carrying out example implementations of the present disclosure is well within the scope of a person of ordinary skill in the art.

[0139] As will be appreciated, any suitable instructions may be loaded onto a computer, a processor, a processing circuitry or other programmable apparatus from a memory or a computer-readable medium (e.g., computer-readable storage medium, computer-readable transmission medium) to produce a particular machine, such that the particular machine becomes a means for implementing the functions specified herein. The instructions may also be stored in a computer-readable medium that can direct a recomputer, a processor, a processing circuitry or other programmable apparatus to function in a particular manner to thereby generate a particular machine or particular article of manufacture. In some examples, the instructions stored in the computer-readable medium may produce an article of manufacture, where the article of manufacture becomes a means for implementing functions described herein. The instructions may be retrieved from a computer-readable medium and loaded into a computer, processor, processing circuitry or other programmable apparatus to configure the computer, processor, processing circuitry or other programmable apparatus to execute operations to be performed on or by the computer, processor, processing circuitry or other programmable apparatus.

[0010] Retrieval, loading and execution of instructions comprising program code instructions may be performed sequentially such that one instruction is retrieved, loaded and executed at a time. In some example implementations, retrieval, loading and / or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and / or executed together. Execution of the program code instructions may produce a computer-implemented process such that the instructions executed by the computer, processor, processing circuitry or other programmable apparatus provide operations for implementing functions described herein.

[0141] Many modifications and other implementations of the disclosure set forth herein will come to mind to one skilled in the art to which the disclosure pertains having the benefit of the teachings presented in the foregoing description and the associated figures. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Moreover, although the foregoing description and the associated figures describe example implementations in the context of certain example combinations of elements and / or functions, it should be appreciated that different combinations of elements and / or functions may be provided by alternative implementations without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and / or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

WHAT IS CLAIMED IS:

1. A method comprising:collecting non-application data of at least one data type among a plurality of data types of nonapplication data;adding, to the non-application data, type information that indicates the at least one data type of the non-application data;mapping the non-application data based on the type information to at least one non-application specific quality of service (QoS) flow created to carry the non-application data and associated with the at least one data type of the non-application data;mapping the at least one non-application specific QoS flow to at least one non-application specific data radio bearer (DRB); andtransferring the non-application data on the at least one non-application specific QoS flow over the at least one non-application specific DRB.

2. The method of claim 1 , wherein the method further comprises receiving a configuration for collection of the non-application data, and the configuration indicates the at least one data type of the non-application data to be collected, andwherein the type information is added to the non-application data based on the configuration.

3. The method of claim 1 or claim 2, wherein the type information that indicates each data type of the at least one data type is added to a header of the non-application data of the data type.

4. The method of any of claims 1 to 3, wherein the non-application data is collected in at least one layer of a radio protocol stack, and the type information is added to the non-application data at the at least one layer.

5. The method of claim 4, wherein the method further comprises transferring the non-application data with the added type information, from the at least one layer, toward a higher-layer functionality above the at least one layer of the radio protocol stack, andwherein the non-application data is mapped to the at least one non-application specific QoS flow at the higher-layer functionality.

6. The method of any of claims 1 to 5, wherein the at least one non-application specific QoS flow is associated with a protocol data unit (PDU) session for which a default DRB is created to carry atleast one application specific QoS flow created to carry application data, and a second default DRB is created to carry at least one non-application specific QoS flow.

7. The method of claim 6, wherein the at least one non-application specific DRB to which the at least one non-application specific QoS flow is mapped includes the second default DRB.

8. The method of any of claims 1 to 7, wherein one or more configured functionalities are configured as disabled for the at least one non-application specific DRB to which the at least one non-application specific QoS flow.

9. An apparatus comprising:at least one memory configured to store instructions; andat least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to perform the method of any of claims 1 to 8.

10. An apparatus comprising means for performing the method of any of claims 1 to 8.

11. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of claims 1 to 8.

12. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of claims 1 to 8.

13. A method comprising:configuring a user equipment (UE) with a configuration for collection of non-application data of at least one data type among a plurality of data types of non-application data, the configuration indicating the at least one data type of the non-application data to be collected;receiving information that indicates at least one non-application specific quality of service (QoS) flow created to carry the non-application data and associated with the at least one data type of the non-application data, and that indicates at least one QoS profile associated with the at least one non-application specific QoS flow;creating at least one non-application specific data radio bearer (DRB) to carry the at least one non-application specific QoS flow based on the at least one QoS profile;determining a mapping of the at least one non-application specific QoS flow to the at least one non-application specific DRB; andconfiguring the UE with at least one configuration that indicates the at least one non-application specific DRB and the mapping of the at least one non-application specific QoS flow to the at least one non-application specific DRB.

14. The method of claim 13, wherein the at least one non-application specific QoS flow is associated with a protocol data unit (PDU) session, andwherein the method further comprises creating a default DRB for the PDU session to carry at least one application specific QoS flow to carry application data, and a second default DRB for the PDU session to carry at least one non-application specific QoS flow.

15. The method of claim 14, wherein the at least one non-application specific DRB created to carry the at least one non-application specific QoS flow includes the second default DRB.

16. The method of any of claims 13 to 15, wherein the at least one configuration further indicates that one or more configured functionalities are disabled for the at least one non-application specific DRB.

17. An apparatus comprising:at least one memory configured to store instructions; andat least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to perform the method of any of claims 13 to 16.

18. An apparatus comprising means for performing the method of any of claims 13 to 16.

19. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of claims 13 to 16.

20. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of claims 13 to 16.