Support for Application Data Unit-based Quality of Service

Abstract

Aspects relate to a core network entity that establishes a session including at least one of an application data unit (ADU) detection rule or an ADU processing rule related to detection of an ADU in a user plane, determines whether ADU awareness applies based on application of the ADU detection rule or the ADU processing rule for one or more quality of service (QoS) flows, transmits a request to create a session supporting the ADU-based QoS flows, negotiates at least one of an ADU-based QoS policy or an ADU QoS rule applicable to the session, and receives an acknowledgment of the creation of the session in response to completion of the negotiation. The radio access network entity conveys the one or more ADUs to a user equipment over the user plane during the session in accordance with the ADU-based QoS policy associated with the at least one ADU-aware QoS flow.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS)

[0001] This application claims priority to and the benefit of Greek Patent Application No. 20220100085, entitled "Support for Application Data Unit Based Quality of Service," filed with the Hellenic Patent and Trademark Office on January 28, 2022, the entire contents of which are incorporated by reference into this specification as if fully set forth below and for all applicable purposes.

[0002] TECHNICAL FIELD

[0002] The technology discussed below relates generally to wireless communication networks, and more particularly to support for Application Data Unit (ADU)-based Quality of Service (QoS). [Background technology]

[0003]

[0003] 3GPP systems have historically supported a Protocol Data Unit (PDU) based Quality of Service (QoS) framework. As an example, data is collected in PDUs. A stream of PDUs may form an IP flow. The IP flow can be filtered to separate into various QoS flows. These QoS flows can be differentiated according to QoS Flow Identifiers (QFIs), which are used to identify specific QoS flows in 5G systems. User plane traffic with the same QFI within a PDU session is subject to the same traffic forwarding measures (e.g., scheduling, admission thresholds).

[0004]

[0004] In the future, 3GPP systems may support an Application Data Unit (ADU)-based QoS framework (sometimes referred to as a PDU set-based QoS framework). An ADU can be a set of PDUs that are jointly processed by an application. An ADU is composed of multiple PDUs, and therefore, in any given QoS framework, different mechanisms may be required to process ADUs or ADUs and PDUs. Summary of the Invention

[0005]

[0005] The following presents a summary of one or more aspects of the present disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all of the contemplated features of the present disclosure, and is not intended to identify key or critical elements of all aspects of the present disclosure or to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure as a prelude to the more detailed description presented later.

[0006] In one embodiment, a core network entity for wireless communications is disclosed. The core network entity includes a memory and a processor coupled to the memory. In the embodiment, the processor and the memory are configured to establish a session including at least one of an Application Data Unit (ADU) detection rule or an ADU processing rule related to detection of an ADU in a user plane, and determine whether ADU awareness applies based on application of at least one of the ADU detection rule or the ADU processing rule for one or more Quality of Service (QoS) flows.

[0007] In another embodiment, a method in a core network entity is disclosed, the method including: establishing a session including at least one of an Application Data Unit (ADU) detection rule or an ADU processing rule related to detection of an ADU in a user plane; and determining, for one or more Quality of Service (QoS) flows, whether ADU awareness applies based on application of at least one of the ADU detection rule or the ADU processing rule.

[0008] According to one aspect, a core network entity for wireless communications is disclosed, the core network entity including a memory and a processor coupled to the memory, the processor and memory configured to send a request to create a session supporting an Application Data Unit (ADU)-based Quality of Service (QoS) flow, negotiate at least one of an ADU-based QoS policy or an ADU QoS rule applicable to the session, and receive an acknowledgment of the creation of the session in response to completion of the negotiation.

[0009] In another embodiment, a method in a core network entity is disclosed that includes sending a request to create a session supporting Application Data Unit (ADU)-based Quality of Service (QoS) flows, negotiating at least one of an ADU-based QoS policy or an ADU QoS rule applicable to the session, and receiving an acknowledgment of the creation of the session in response to completion of the negotiation.

[0010] In yet another embodiment, a method in a Radio Access Network (RAN) entity is disclosed, the method including receiving a session request, accepting establishment of the session, transmitting a session response, and conveying, during the session, one or more Application Data Units (ADUs) to a user equipment via a user plane in accordance with an ADU-based QoS policy associated with at least one ADU-aware QoS flow.

[0011]

[0011] These and other aspects will be more fully understood by reviewing the following "Description of the Preferred Embodiments". Other aspects, features, and embodiments will become apparent to those skilled in the art by reviewing the following description of certain exemplary embodiments in conjunction with the accompanying figures. Although features may be discussed in conjunction with certain embodiments and figures below, all embodiments may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with various embodiments discussed herein. Similarly, although embodiments may be discussed below as device, system, or method embodiments, it should be understood that such embodiments may be implemented in various devices, systems, and methods. [Brief description of the drawings]

[0012] [Figure 1]

[0012] FIG. 1 is a schematic diagram of a wireless communication system according to some aspects. [Diagram 2]

[0013] FIG. 1 illustrates a schematic diagram of an example of a radio access network, in accordance with some aspects. [Diagram 3]

[0014] 1 illustrates an example of a frame structure for use in a radio access network, in accordance with some aspects. [Figure 4]

[0015] FIG. 1 is a block diagram illustrating an example of a 5G wireless communication system, in accordance with some aspects. [Diagram 5]

[0016] 1 is a call flow diagram illustrating an application function session setup using QoS procedures. [Figure 6]

[0017] FIG. 1 is a call flow diagram associated with establishing a user equipment requested packet data unit session, according to some aspects. [Figure 7]

[0018] FIG. 2 is a block diagram illustrating an example of a hardware implementation of a core network entity employing a processing system, in accordance with some aspects. [Figure 8]

[0019] 1 is a flowchart illustrating an example process for wireless communication in a core network entity, according to some aspects. [Figure 9]

[0020] 1 is a flowchart illustrating an example process for wireless communication in a core network entity, according to some aspects. [Figure 10]

[0021] 1 is a flowchart illustrating an example process for wireless communication in a core network entity, according to some aspects. [Figure 11]

[0022] 1 is a block diagram illustrating an example of a hardware implementation of a radio access network entity employing a processing system, in accordance with some aspects. [Figure 12]

[0023] 1 is a flowchart illustrating an example process for wireless communication in a RAN entity, in accordance with some aspects. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013]

[0024] The detailed description of the invention described below in connection with the accompanying drawings is intended as an illustration of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description of the invention includes specific details intended to provide a thorough understanding of the various concepts. However, it will be apparent to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0014]

[0025] Although aspects and embodiments are described herein by way of example for some embodiments, those skilled in the art will appreciate that additional implementations and use cases may occur in many different configurations and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, aspects and / or applications may occur via integrated chip embodiments and other non-modular component-based devices (e.g., end user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). Some embodiments may or may not be specifically targeted to a use case or application, but a wide range of combination applicability of the described innovations may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and even aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, transmitting and receiving wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, summers / analog summers, etc.). It is contemplated that the innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed configurations, separate configurations (e.g., base stations and / or UEs), end user devices, etc., of various sizes, shapes, and configurations.

[0015]

[0026] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the "mmWave" band in documents and papers, even though FR2 is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "mmWave" band by the International Telecommunications Union (ITU).

[0016]

[0027] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands within FR3 may inherit the characteristics of FR1 and / or FR2, and therefore may effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. Furthermore, higher frequency bands are currently being considered to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is within the EHF band.

[0017]

[0028] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, frequencies that may be in the range of FR1, or frequencies that may include mid-band frequencies. Further, it should be understood that unless otherwise specified, terms such as "mmWave," as used herein, may broadly refer to frequencies that may be in the range of FR2, FR4, FR4-a, or FR4-1, and / or FR5, or frequencies that may be in the EHF band.

[0018]

[0029] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunications systems, network architectures, and communication standards. Referring now to FIG. 1, by way of an illustrative and non-limiting example, various aspects of the present disclosure are illustrated with reference to a wireless communication system 100. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. The wireless communication system 100 may enable the UE 106 to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0019]

[0030] The RAN 104 may implement any suitable wireless communications technology for providing radio access to the UEs 106. As one example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, often referred to as 5G. As another example, the RAN 104 may operate under a hybrid of 5G NR and the evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, often referred to as Long Term Evolution (LTE). 3GPP refers to this hybrid RAN as Next Generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of this disclosure.

[0020]

[0031] As shown, the RAN 104 includes multiple base stations 108. Generally, a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to and from UEs. In different technologies, standards, or contexts, a base station may be variously referred to by those skilled in the art as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), enhanced service set (ESS), access point (AP), Node B (NB), eNode B (eNB), gNode B (gNB), transmit / receive point (TRP), or some other suitable term. In some embodiments, a base station may include two or more TRPs, which may or may not be collocated. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In embodiments in which the RAN 104 operates according to both the LTE and 5G NR standards, one of the base stations may be an LTE base station, while another base station may be a 5G NR base station.

[0021]

[0032] The RAN 104 is further shown to support wireless communications for a plurality of mobile devices, which may be referred to as user equipment (UE) in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS), subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handset, terminal, user agent, mobile client, client, or some other suitable terminology. A UE may be a device (e.g., a mobile device) that provides access to network services for a user.

[0022]

[0033] Within the scope of this disclosure, a "mobile" device does not necessarily have the ability to move and may be stationary. The term mobile device or mobile device refers broadly to a wide variety of devices and technologies. A UE may include any number of hardware structural components sized, shaped, and arranged to facilitate communication, including antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile, cellular (cell) phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, those that are "Internet of Things" (IoT) enabled.

[0023]

[0034] The mobile device may further be an automobile or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multicopter, a quadcopter, a remote control device, a consumer device and / or a wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a camera, a game console, etc. The mobile device may further be a digital home device or a smart home device, such as a home audio, video, and / or multimedia device, an appliance, a vending machine, an intelligent lighting, a home security system, a smart meter, etc. The mobile device may further be a smart energy device, a security device, a solar panel or solar array, a city infrastructure device (e.g., smart grid) that controls power, lighting, water, etc., an industrial automation and enterprise device, a logistics controller, and / or an agricultural device, etc. Still further, the mobile device may provide connected medical or telemedicine support, such as remote healthcare. Remote medical devices may include remote medical monitoring devices and remote medical management devices, whose communications may be given preferential treatment or preferential access over other types of information, for example in terms of priority access for the transmission of critical service data and / or associated QoS for the transmission of critical service data.

[0024]

[0035] The wireless communication between the RAN 104 and the UE 106 may be described as utilizing an air interface. A transmission over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., similar to the UE 106) may be referred to as a downlink (DL) transmission. According to certain aspects of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating from a base station (e.g., base station 108). Another way to describe this scheme may be to use the term broadcast channel multiplexing. A transmission from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as an uplink (UL) transmission. According to further aspects of the present disclosure, the term uplink may refer to a point-to-point transmission originating from a UE (e.g., UE 106).

[0025]

[0036] In some embodiments, access to the air interface may be scheduled, with a scheduling entity (e.g., a base station 108) allocating resources for communication among some or all of the devices and equipment within its coverage area or cell. Within the scope of this disclosure, as discussed further below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources to one or more scheduled entities (e.g., UEs 106). That is, for scheduled communications, multiple UEs 106, which may be scheduled entities, may utilize resources allocated by the scheduling entity 108.

[0026]

[0037] The base station 108 is not the only entity that can function as a scheduling entity. That is, in some embodiments, a UE may function as a scheduling entity that schedules resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE may communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0027]

[0038] As shown in FIG. 1 , the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). Generally, the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and, in some embodiments, uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108. Meanwhile, the scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network, such as the scheduling entity 108. The scheduled entity 106 can further transmit uplink control information 118, including but not limited to scheduling requests or feedback information, or other control information, to the scheduling entity 108.

[0028]

[0039] Furthermore, the uplink control information 118 and / or the downlink control information 114 and / or the downlink traffic information 112 and / or the uplink traffic information 116 may be transmitted on a waveform that may be time-divided into frames, subframes, slots, and / or symbols. As used herein, a symbol may refer to a unit of time that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A slot may carry seven or fourteen OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame. Within the scope of this disclosure, a frame may refer to a predefined duration (e.g., 10 ms) for wireless transmission, with each frame consisting of, for example, ten subframes of 1 ms each. Of course, these definitions are not required and any suitable scheme for organizing the waveform may be utilized, and the various time divisions of the waveform may have any suitable duration.

[0029]

[0040] In general, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communications system 100. The backhaul portion 120 may provide a link between the base stations 108 and the core network 102. Moreover, in some embodiments, a backhaul network may provide interconnection between corresponding base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, etc., using any suitable transport network.

[0030]

[0041] The core network 102 may be part of the wireless communications system 100 and may be independent of the radio access technology used in the RAN 104. In some embodiments, the core network 102 may be configured in accordance with a 5G standard (e.g., 5GC). In other embodiments, the core network 102 may be configured in accordance with a 4G Evolved Packet Core (EPC), or any other suitable standard or configuration.

[0031]

[0042] 2, by way of an illustrative and non-limiting example, a schematic diagram of a radio access network (RAN) 200 is provided in accordance with some aspects of the present disclosure. In some embodiments, the RAN 200 may be the same as the RAN 104 described above and shown in FIG.

[0032]

[0043] The geographical region covered by the RAN 200 can be divided into a number of cellular regions (cells) that can be uniquely identified by user equipment (UE) based on an identification broadcast from an access point or base station over a geographical area. Figure 2 shows cells 202, 204, 206, and 208, each of which can include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors in a cell are served by the same base station. Radio links within a sector can be identified by a single logical identification belonging to that sector. In a cell divided into sectors, the multiple sectors within the cell can be formed by a group of antennas, each antenna responsible for communication with UEs in a portion of the cell.

[0033]

[0044] Various arrangements of base stations can be utilized. For example, in FIG. 2, two base stations, base station 210 and base station 212, are shown in cell 202 and cell 204. A third base station, base station 214, is shown controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna or may be connected to the antenna or RRH 216 by a feeder cable. In the illustrated embodiment, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells having a large size. Furthermore, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this embodiment, base station 218 supports a cell having a relatively small size, so cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNodeB, etc.). The sizing of the cells can be done according to system design and component constraints.

[0034]

[0045] It should be appreciated that the RAN 200 may include any number of wireless base stations and cells. Additionally, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. The base stations 210, 212, 214, 218 provide wireless access points to a core network for any number of mobile devices. In some embodiments, the base stations 210, 212, 214, and / or 218 may be the same as or similar to the scheduling entity 108 described above and shown in FIG. 1.

[0035]

[0046] 2 further includes an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. The UAV 220 may be configured to function as a base station, or more specifically, as a mobile base station. That is, in some embodiments, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of a mobile base station, such as the UAV 220.

[0036]

[0047] Within the RAN 200, the cells may include UEs capable of communicating with one or more sectors of each cell. Additionally, each base station 210, 212, 214, 218, and 220 may be configured to provide an access point to the core network 102 (see FIG. 1) for all UEs in the corresponding cell. For example, UE 222 and UE 224 may communicate with base station 210, UE 226 and UE 228 may communicate with base station 212, UE 230 and UE 232 may communicate with base station 214 via RRH 216, UE 234 may communicate with base station 218, and UE 236 may communicate with mobile base station 220. In some embodiments, the UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be the same as or similar to the UE / scheduled entity 106 described above and shown in FIG. 1. In some embodiments, the UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to function as a UE. For example, the UAV 220 may operate within the cell 202 by communicating with the base station 210.

[0037]

[0048] In further aspects of the RAN 200, sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station. Sidelink communications may be utilized, for example, in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signals 237 without relaying the communications through a base station. In some embodiments, UEs 238, 240, and 242 may each function as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and communicate sidelink signals 237 between those UEs without relying on scheduling or control information from a base station. In another embodiment, two or more UEs (e.g., UE 226 and UE 228) within the coverage area of ​​a base station (e.g., base station 212) may also communicate sidelink signals 227 via a direct link (sidelink) without conveying such communications through base station 212. In this embodiment, base station 212 may allocate resources to UE 226 and UE 228 for sidelink communications.

[0038]

[0049] In order for transmission over the air interface to obtain a low block error rate (BLER) while still achieving very high data rates, channel coding can be used. That is, wireless communications can generally utilize suitable error-correcting block codes. In a typical block code, an information message or sequence is divided into code blocks (CBs), and then an encoder (e.g., a CODEC) at the transmitting device mathematically adds redundancy to the information message. Exploiting this redundancy in the coded information message can improve the reliability of the message and allows for correction of any bit errors that may occur due to noise.

[0039]

[0050] Data encoding can be implemented in multiple ways. In the initial 5G NR specification, user data is encoded using quasi-cyclic low-density parity check (LDPC) with two different base graphs, i.e., one base graph is used for large code blocks and / or high code rates, and the other base graph is used otherwise. Control information and the Physical Broadcast Channel (PBCH) are encoded using polar coding based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0040]

[0051] Aspects of the present disclosure may be implemented utilizing any suitable channel codes. Various implementations of base stations and UEs may include suitable hardware and capabilities (e.g., encoders, decoders, and / or CODECs) for utilizing one or more of these channel codes for wireless communications.

[0041]

[0052] In the RAN 200, the ability of UEs to communicate while moving, independent of their location, is referred to as mobility. The various physical channels between the UEs and the RAN 200 are generally set up, maintained, and released under the control of an Access and Mobility Management Function (AMF). In some scenarios, the AMF may include a Security Context Management Function (SCMF) and a Security Anchor Function (SEAF) that performs authentication. The SCMF may manage, in whole or in part, the security context for both the control plane functions and the user plane functions.

[0042]

[0053] In various aspects of the disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to enable mobility and handover (i.e., transition of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, the UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from the neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may undertake a handoff or handover from its serving cell to a neighboring (target) cell. For example, the UE 224 may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. If the signal strength or quality from a neighbor cell 206 exceeds that of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating this condition to its serving base station 210. In response, the UE 224 may receive a handover command and the UE may complete a handover to the cell 206.

[0043]

[0054] In a network configured for UL-based mobility, UL reference signals from each UE may be utilized by the network to select a serving cell for each UE. In some embodiments, base stations 210, 212, and 214 / 216 may broadcast unified synchronization signals (e.g., unified primary synchronization signals (PSSs), unified secondary synchronization signals (SSSs), and unified physical broadcast channels (PBCHs). UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals and derive carrier frequency and slot timing therefrom, and may transmit uplink pilot signals or reference signals in response to deriving the timing. An uplink pilot signal transmitted by a UE (e.g., UE 224) may be received simultaneously by two or more cells (e.g., base stations 210 and 214 / 216) in the RAN 200. Each of those cells can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node in the core network) can determine the serving cell for the UE 224. As the UE 224 moves within the RAN 200, the RAN 200 can keep monitoring the uplink pilot signals transmitted by the UE 224. If the signal strength or signal quality of the pilot signal measured by a neighboring cell exceeds the signal strength or signal quality measured by the serving cell, the RAN 200 can handover the UE 224 from the serving cell to the neighboring cell, with or without notifying the UE 224.

[0044]

[0055] The synchronization signals transmitted by base stations 210, 212, and 214 / 216 may be unified, but may not identify a particular cell, but rather a zone of multiple cells operating on the same frequency and / or at the same timing. The use of zones in 5G networks or other next generation communication networks enables an uplink-based mobility framework and improves the efficiency of both UEs and networks because it reduces the number of mobility messages that need to be exchanged between the UE and the network.

[0045]

[0056] In various implementations, the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulatory body. Unlicensed spectrum provides sharing of a portion of the spectrum without the need for a government-granted license. Generally, compliance with some technical rules is still required to access unlicensed spectrum, but generally any operator or device can gain access. Shared spectrum may be somewhere between licensed and unlicensed spectrum, and may require technical rules or restrictions to access the spectrum, but still allow the spectrum to be shared by multiple operators and / or multiple RATs. For example, holders of licenses for portions of licensed spectrum may be offered Licensed Shared Access (LSA) to share the spectrum with other parties, e.g., who have suitable licensee determination terms to gain access.

[0046]

[0057] Devices communicating within the radio access network 200 may utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from the UEs 222 and 224 to the base station 210, and multiplexing for DL ​​transmissions from the base station 210 to one or more of the UEs 222 and 224 using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP). Furthermore, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Spread OFDM with CP (DET-s-OFDM), also referred to as Single Carrier FDMA (SC-FDMA). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spreading multiple access (RSMA), or other suitable multiple access schemes. Furthermore, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0047]

[0058] Devices in the radio access network 200 may also utilize one or more duplexing algorithms. Duplex refers to a point-to-point communication link where both endpoints can communicate with each other in both directions. Full duplex means that both endpoints can communicate with each other simultaneously. Half duplex means that only one endpoint at a time can transmit information to the other. Half duplex emulation is frequently implemented for wireless links utilizing time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some scenarios, a channel is dedicated to transmission in one direction, but at other times, the channel is dedicated to transmission in the opposite direction, where the direction may change very rapidly, e.g., several times per slot. In wireless links, full duplex channels generally rely on physical separation of the transmitter and receiver, and suitable interference cancellation techniques. Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or spatial division duplex (SDD). In FDD, transmissions in different directions may operate at different carrier frequencies (e.g., in a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from one another using spatial division multiplexing (SDM). In other embodiments, full-duplex communication may be implemented in an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of that carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0048]

[0059] Various aspects of the present disclosure will be described with reference to an OFDM waveform, as shown generally in Figure 3. Those skilled in the art will appreciate that the various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described herein below, i.e., while some embodiments of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles may be applied to SC-FDMA waveforms as well.

[0049]

[0060] 3, a close-up view of an exemplary subframe 302 is shown illustrating an OFDM resource grid. However, as one skilled in the art will readily appreciate, the physical (PHY) transmission structure for any particular application may differ from the example described herein depending on any number of factors. In this diagram, time is in units of OFDM symbols in the horizontal direction and frequency is in units of subcarriers of a carrier in the vertical direction.

[0050]

[0061] The resource grid 304 can be used to generally represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding number of resource grids 304 can be made available for communication. The resource grid 304 is divided into multiple resource elements (REs) 306. An RE, which is 1 subcarrier by 1 symbol, is the smallest individual portion of this time-frequency grid and contains a single complex value that represents data from a physical channel or signal. Depending on the modulation employed in a particular implementation, each RE can represent one or multiple bits of information. In some embodiments, a block of REs may be referred to as a physical resource block (PRB) or, more simply, a resource block (RB) 308, which includes any suitable number of consecutive subcarriers in the frequency domain. In one embodiment, an RB may include 12 subcarriers, a number that is independent of the numerology used. In some embodiments, depending on the numerology, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the scope of this disclosure, it is assumed that a single RB, such as RB 308, corresponds entirely to a single direction of communication (either transmission or reception for a given device).

[0051]

[0062] A set of contiguous or non-contiguous resource blocks may be referred to herein as a resource block group (RBG), subband, or bandwidth portion (BWP). A set of subbands or BWPs may span the entire bandwidth. Scheduling of a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 in one or more subbands or bandwidth portions (BWPs). Thus, a UE typically utilizes only a subset of the resource grid 304. In some embodiments, an RB may be the smallest unit of resource that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the more advanced the modulation scheme selected for the air interface, the higher the data rate for that UE. The RBs may be scheduled by a base station (e.g., gNB, eNB, etc.) or may be self-scheduled by a UE performing D2D sidelink communication.

[0052]

[0063] In this figure, the RB 308 is shown as occupying less than the entire bandwidth of the subframe 302, with several subcarriers shown above and below the RB 308. In a given implementation, the subframe 302 may have a bandwidth that corresponds to any number of one or more RBs 308. Moreover, although in this figure the RB 308 is shown as occupying less than the entire duration of the subframe 302, this is merely one possible example.

[0053]

[0064] Each 1 ms subframe 302 may consist of one or more contiguous slots. In the embodiment shown in FIG. 3, one subframe 302 includes four slots 310 as an illustrative example. In some embodiments, a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a slot may include seven or fourteen OFDM symbols with a nominal CP. Additional embodiments may include minislots, sometimes referred to as shortened transmission time intervals (TTIs), having a shorter duration (e.g., one to three OFDM symbols). These minislots or shortened transmission time intervals (TTIs) may be transmitted, in some cases occupying resources scheduled for ongoing slot transmissions for the same or different UEs. Any number of resource blocks may be utilized within a subframe or slot.

[0054]

[0065] An expanded view of one of the slots 310 shows the slot 310 including a control region 312 and a data region 314. In general, the control region 312 may carry a control channel and the data region 314 may carry a data channel. Of course, a slot may include all DL, all UL, or may include at least one DL portion and at least one UL portion. The structure shown in FIG. 3 is merely exemplary in nature and different slot structures may be utilized and may include one or more of each of the control and data regions.

[0055]

[0066] 3, various REs 306 in the RB 308 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 306 in the RB 308 may also carry pilot or reference signals. These pilot or reference signals may be provided for a receiving device to perform channel estimation of the corresponding channels, which may enable coherent demodulation / detection of the control and / or data channels in the RB 308.

[0056]

[0067] In some embodiments, slots 310 may be utilized for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to a point-to-multipoint transmission by one device (e.g., a base station, UE, or other similar device) to other devices, where a broadcast communication is delivered to all devices, while a multicast or groupcast communication is delivered to multiple intended recipient devices. Unicast communications may refer to a point-to-point transmission by one device to a single other device.

[0057]

[0068] In one embodiment of cellular communication on a cellular carrier over a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) can allocate one or more REs 306 (e.g., in the control region 312) to one or more scheduled entities (e.g., UEs) for carrying DL control information, including one or more DL control channels, such as a physical downlink control channel (PDCCH). The PDCCH carries downlink control information (DCI), including, but not limited to, power control commands (e.g., one or more open loop power control parameters and / or one or more closed loop power control parameters), scheduling information, grants, and / or allocation of REs for DL ​​and UL transmissions. The PDCCH can further carry hybrid automatic repeat request (HARQ) feedback transmissions, such as an acknowledgement (ACK) or a negative acknowledgement (NACK). HARQ is a technique well known to those skilled in the art, and may utilize any suitable integrity checking mechanism, such as a checksum or cyclic redundancy check (CRC), to check the integrity of a packet transmission at the receiving end for accuracy. If the integrity of the transmission is confirmed, an ACK may be sent, whereas if not, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc.

[0058]

[0069] The base station may further allocate one or more REs 306 (e.g., in the control region 312 or data region 314) to carry other DL signals, such as demodulation reference signals (DMRS), phase tracking reference signals (PT-RS), channel state information (CSI) reference signals (CSI-RS), and synchronization signal blocks (SSBs). The SSBs may be broadcast at regular intervals based on a periodicity (e.g., 5, 10, 20, 40, 80, or 160 ms). The SSBs include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve synchronization of radio frames, subframes, slots, and symbols in the time domain, to identify the center of the channel (system) bandwidth in the frequency domain, and to identify the physical cell identity (PCI) of the cell.

[0059]

[0070] The PBCH in the SSB may further include a Master Information Block (MIB) that includes various system information along with parameters for decoding the System Information Block (SIB). The SIB may be, for example, SystemInformationType1 (SIB1), which may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink numerology), system frame number, PDCCH control resource set (CORESET) configuration (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, raster offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may transmit other system information (OSI) as well.

[0060]

[0071] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 306 to convey UL control information (UCI), including one or more UL control channels, such as a physical uplink control channel (PUCCH), to the scheduling entity. The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding an uplink data transmission. Examples of uplink reference signals may include a sounding reference signal (SRS) and an uplink DMRS. In some embodiments, the UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule an uplink transmission. In this case, in response to the SR transmitted on the UCI, the scheduling entity may transmit downlink control information (DCI) capable of scheduling resources for an uplink packet transmission. The UCI may also include channel state feedback (CSF), such as HARQ feedback, CSI reporting, or any other suitable UCI.

[0061]

[0072] In addition to control information, one or more REs 306 (e.g., in the data region 314) may be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as a Physical Downlink Shared Channel (PDSCH) for DL ​​transmissions or a Physical Uplink Shared Channel (PUSCH) for UL transmissions. In some embodiments, one or more REs 306 in the data region 314 may be configured to carry other signals, such as one or more SIBs and DMRS. In some embodiments, the PDSCH may carry multiple SIBs, not limited to SIB1 as described above. For example, OSI may be provided in those SIBs, e.g., SIB2 or higher.

[0062]

[0073] In an embodiment of sidelink communication on a sidelink carrier via a Proximity Services (ProSe) PC5 interface, the control area 312 of the slot 310 may include a Physical Sidelink Control Channel (PSCCH) including sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g. a Tx V2X device or other Tx UE) towards a set of one or more other receiving sidelink devices (e.g. a Rx V2X device or other Rx UEs). The data area 314 of the slot 310 may include a Physical Sidelink Shared Channel (PSSCH) including sidelink data traffic transmitted by the initiating (transmitting) sidelink device via the SCI in resources reserved on the sidelink carrier by the transmitting sidelink device. Other information may also be transmitted on various REs 306 in the slot 310. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device in a Physical Sidelink Feedback Channel (PSFCH) in the slot 310. Additionally, one or more reference signals may be transmitted within the slot 310, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS).

[0063]

[0074] These physical channels mentioned above are typically multiplexed and mapped to transport channels for processing at the Medium Access Control (MAC) layer. The transport channels carry blocks of information called Transport Blocks (TBs). The Transport Block Size (TBS), which may correspond to the number of bits of information, can be a controlled parameter based on the Modulation and Coding Scheme (MCS) and the number of RBs in a given transmission.

[0064]

[0075] The channels or carriers shown in FIG. 3 are not necessarily all of the channels or carriers that may be utilized between devices, and one skilled in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic channels, control channels, and feedback channels.

[0065]

[0076] Historically, 3GPP systems support a Protocol Data Unit (PDU)-based QoS framework. An example of a PDU is an IP packet. A new framework, called an Application Data Unit (ADU)-based QoS framework (sometimes called a PDU set-based QoS framework), is currently being considered in 3GPP. Application Data Units (ADUs) can be a set of IP packets that are jointly processed by an application. For example, an ADU or a PDU set can include one or more PDUs that carry the payload of one information unit (e.g., a frame or video slice for an Extended Reality Mobile (XRM) service) generated at the application level. In some implementations, all PDUs in an ADU or a PDU set may be required by the application layer to use the corresponding information unit. In other implementations, the application layer can still recover all or part of the information unit even if some PDUs are missing.

[0066]

[0077] As used herein, a "burst" describes a set of ADUs (or PDU sets) that are generated by an application at substantially the same time. In other words, a burst (also referred to as a "data burst") can be a set of data that is generated and transmitted by an application within a short period of time. A data burst can include one or more ADUs or PDU sets.

[0067]

[0078] Applications consume data in ADUs. By definition, an ADU is larger than an IP packet since it consists of multiple IP packets. Key ADU-related performance indicators / ADU QoS parameters include at least ADU Error Rate (AER) and ADU Delay Budget (ADB).

[0068]

[0079] The AER defines the maximum allowable number of ADUs received in error on average. More specifically, the ADU Error Rate (AER) (also referred to as the PDU Set Error Rate (PSER)) may be an upper bound on the ratio of the number of ADUs (or PDU sets) not successfully received, measured over a measurement window, to the total number of ADUs (or PDU sets) transmitted towards the receiver. According to some aspects, the ADU error rate may be used by the communication system to set rate adaptation targets, number of HARQ retransmissions, and radio link control (RLC) parameters based on the ADU error rate instead of the PDU error rate.

[0069]

[0080] The ADB defines the maximum delay that can be tolerated for an ADU. More specifically, the ADU Delay Budget (ADB), also referred to as the PDU Set Delay Budget (PSDB), may define an upper bound on the time that an ADU (or PDU set) can be delayed between the UE and the N6 termination point in the UPF before it is considered not delivered successfully. The ADU Delay Budget may be applied to a DL ADU (or DL ​​PDU set) received by the UPF over the N6 interface and may represent the difference between the time that the last bit of the last PDU of that ADU (or PDU set) is injected into the UPF and the time that the last bit of the last PDU of that ADU (or PDU set) is delivered to the UE. For the UL, the ADU Delay Budget is applied to a UL ADU (or PDU set) transmitted by the UE and represents the difference between the time that the last bit of the last PDU of that ADU (or PDU set) is transmitted by the UE and the time that the last bit of the last PDU of that ADU (or PDU set) is delivered to the UPF. This may mean that the time when all PDUs in an ADU (or PDU set) must be received by the UE (in the DL case) and the UPF (in the UL case) is determined when the last PDU of that ADU (or PDU set) is received at the RAN.

[0070]

[0081] Additional ADU QoS parameters may include a maximum ADU size (also referred to as PDU Set Maximum Size (PSMS)). According to some aspects, the maximum ADU size may be expressed in bytes. The maximum ADU size may indicate to the RAN scheduler an upper bound on how many bytes can be scheduled within a particular delay budget.

[0071]

[0082] The aspects described herein may consider how to configure a 5G core network (5G CN), a 5G access network (AN), and a UE to use an ADU-based QoS framework.

[0072]

[0083] Referring now to FIG. 4, a block diagram is provided illustrating, by way of example and not limitation, one embodiment of various components of a 5G wireless communication system (5GS) 400. In some embodiments, the 5GS 400 may correspond to the wireless communication system 100 described above and shown in FIG. 1. The 5GS 400 includes a user equipment (UE) 402, a RAN entity 404 (e.g., a 5G AN), and a core network 406 (e.g., a 5G CN). The RAN entity 404 may be a 5G RAN and may correspond, for example, to the RAN 200 described above and shown in FIG. 2. Furthermore, the UE 402 may correspond to any of the UEs or other scheduled entities shown in FIG. 1 and / or FIG. 2. The wireless communication system 400 may enable the UE 402 to perform data communications with an Extended Reality Application Function (XR AF) or an Extended Reality Application Server (XR AS), collectively identified as an XR AF / AS 418. Of course, the UE 402 may be capable of performing data communication with any external data network (not shown), such as, but not limited to, the Internet or an Ethernet network. According to aspects herein, if application data unit (ADU) awareness is configured in the uplink, the UE 402 may be configured with an ADU-aware uplink filter. The ADU-aware uplink filter may be configured for the UE 402 by a session management function (SMF) 410 during protocol data unit (PDU) session establishment or PDU session modification.

[0073]

[0084] In addition to the SMF 410, the core network 406 may include, for example, an Access and Mobility Management Function (AMF) 408 and a User Plane Function (UPF) 414. The AMF 408 and the SMF 410 may employ control plane (e.g., Non-Access Stratum (NAS)) signaling to perform various functions related to mobility management and session management for the UE 402. For example, the AMF 408 may provide connectivity, mobility management, and authentication for the UE 402, while the SMF 410 may provide session management (SM) for the UE 402. Session management may include, for example, processing signaling related to PDU sessions between the UE 402 and the XR AF / AS 418 (or an external data network (not shown)). More specifically, the SMF 410 may determine the ADU 5G QoS flow identifier (A5QI) and the ADU-aware QoS flows. Further, the SMF 410 can configure the UPF 414 with ADU-aware filters and / or ADU detection rules. The UPF 414 can provide user plane connectivity for routing 5G NR packets to / from the UE 402 via the RAN entity 404. The RAN entity 404 can be involved in ADU-aware scheduling. Still further, the SMF 410 can configure the RAN 404 with ADU-aware QoS flows and A5QI, which can include values ​​for ADU Error Rate (AER) and / or ADU Delay Budget (ADB).

[0074]

[0085] The core network 406 may further include other functions, such as a network publishing function (NEF) and a policy control function (PCF), shown for convenience in one NEF / PCF 412 block. The NEF of the NEF / PCF 412 block may facilitate secure and robust access to published network services and capabilities. Thus, the NEF may provide secure information provisioning from external applications to the 3GPP network. The PCF of the NEF / PCF 412 block may provide policy rules for control plane functions, which may include network slicing, roaming, and mobility management. In aspects relevant to the present disclosure, the PCF may provide policies for ADU-based QoS. The PCF also supports 5G QoS policy and charging control functions.

[0075]

[0086] Various interfaces are shown in Figure 4. For example, the N6 interface between the XR AF / AS 418 and the UPF 414 is a user plane interface. The N5 / N33 interface between the XR AF / AS 418 and the NEF / PCF 412 may be provided for application negotiation (via the NEF / PCF 412).

[0076]

[0087] To establish a connection to a core network 406 (e.g., a 5G core network) via the RAN entity 404, the UE 402 may send a registration request to the AMF 408 of the core network 406 via the RAN entity 404. The AMF 408 may then initiate a non-access stratum (NAS) level authentication between the UE 402 and the core network (e.g., via AUSF and UDM (not shown)). The AMF 408 may then obtain mobility subscription data, SMF 410 selection data, and UE 402 context and communicate with the NEF / PCF 412 for policy association for the UE 402. The AMF 408 may then send a NAS secure registration accept message to the UE 402 to complete the registration.

[0077]

[0088] Once the UE 402 is registered with the core network 406, the UE 402 may send a PDU session establishment request to the core network 406 via the RAN entity 404 to establish one or more PDU sessions. The AMF 408 and SMF 410 may process the PDU session establishment request to establish, for example, a data network session (DNS) between the UE 402 and the XR AF / AS 418 via the UPF 414 and an application data unit processing layer (not shown). A DNS may include one or more sessions (e.g., data sessions or data flows) and may be served by multiple UPFs 414 (only one of which is shown for convenience). Examples of data flows include, but are not limited to, IP flows, Ethernet flows, and unstructured data flows.

[0078]

[0089] The core network 406 may include other functions in addition to those described above, such as, but not limited to, an authentication server function (AUSF), a unified data management (UDM) entity, a network slice selection function (NSSF), a network repository function (NRF), etc. Because these functions are known to those skilled in the art, for the sake of brevity, they will not be further described or illustrated.

[0079]

[0090] New QoS information and control plane signaling can be defined to configure the 5G CN (e.g., core network 406), 5G AN (e.g., RAN 404), and UE 402 to use the ADU-based QoS framework. For the new QoS information, new standardized A5QI values ​​can be utilized. New standardized values ​​exemplified in this disclosure include ADU error rate and ADU delay budget. For the control plane signaling, new negotiation between the Application Function (AF) and 5GS can be defined. More specifically, the negotiation between the AF and 5GS can involve negotiation regarding ADU-based QoS levels and ADU marking (also known as PDU set marking or burst marking) (e.g., marking to identify ADU in IP, Real-time Transport Protocol (RTP), and other protocols). According to an aspect, the SMF 410 can determine that ADU-based QoS is required. The SMF 410 can configure the UPF 414 and the RAN 404 to support ADU-based QoS. The SMF 410 can initiate a session management (SM) negotiation with the UE 402 to implement the ADU-based QoS. According to one aspect, the SM negotiation with the UE 402 can be accomplished by modifying (e.g., extending) current PDU establishment and / or PDU modification processes.

[0080]

[0091] Currently, 5GS relies on a PDU-based QoS framework, therefore the concept of an ADU-based QoS framework does not exist in the current 5GS specifications. The PDU-based QoS framework defines the following concepts: (1) a QoS profile that describes the characteristics of a QoS flow; and (2) A 5G QoS flow identifier (5QI) that identifies a specific QoS flow.

[0081]

[0092] According to aspects described herein, an ADU-based QoS framework may be based on the following: (1) ADU discovery in the user plane (this discovery is performed within the 5G core network); (2) the introduction of new policies regarding ADUs; and (3) Control of ADU-based QoS via SMF.

[0082]

[0093] In one embodiment, a new type of QoS profile can be defined to implement the ADU-based QoS framework. The new type of QoS profile can specifically support the ADU QoS framework. In other words, the new type of QoS profile can not include definitions of QoS information that is not related to the ADU QoS framework. According to a second embodiment, an existing QoS profile can be extended to encompass QoS aspects of both the existing PDU-based QoS framework and the new ADU-based QoS framework.

[0083]

[0094] QoS Profile 1 below shows an existing QoS profile according to the PDU-based QoS framework. QoS Profile 2 below shows a new QoS profile according to the ADU-based QoS framework. The following terms are abbreviated as shown: Allocation and Retention Priority (ARP), Reflective QoS Attribute (RQA), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), and Guaranteed Bit Rate (GBR).

[0084] [Table 1]

[0085]

[0095] Table 1 below is an excerpt from an existing standardized table of 5QI values. The excerpt is taken from section 5.7.4 of 3GPP TS 23.501, version 17.3.0, dated December 2021. Table 2 below is an example of a portion of the new standardized A5QI value table.

[0086] [Table 2]

[0087] [Table 3]

[0088]

[0096] QoS Profile 2 can be used in parallel with QoS Profile 1. Each row of the new ADU-based QoS Profile 2 includes an A5QI, an ADU Delay Budget (ADB) value, and an ADU Error Rate (AER) value.

[0089]

[0097] In another embodiment, QoS Profile 1 can be modified (as shown in QoS Profile 3 below) to include an indication (e.g., a flag) of whether the QoS profile applies to ADU-based QoS (in addition to PDU-based QoS), an indication of the ADU delay budget, and an indication of the AER. Similarly, the standardized table for 5QI and the standardized table for A5QI can be merged to create a new table that includes information related to both 5QI and A5QI (i.e., both PDU-based QoS and ADU-based QoS), as shown in Table 3 below.

[0090] [Table 4]

[0091] [Table 5]

[0092]

[0098] With respect to modifying control plane signaling to support ADU-based QoS, in accordance with aspects described herein, the control plane signaling can be modified to support Application Capabilities (AF) / 5GS negotiation regarding ADU-based QoS and ADU marking practices (e.g., in IP, RTP, and other protocols).

[0093]

[0099] FIG. 5 is a call flow diagram 500 illustrating an embodiment of establishing an application function session using QoS procedures. Shown are an application function (AF) 502, a network publishing function (NEF) 504, and a policy control function (PCF) 506. At 508, the AF 502 can send a request to reserve resources for an AF session by sending a Nnef_AFsessionWithQoS_Create request message to the NEF 504. The contents of the Nnef_AFsessionWithQoS_Create request message constitute the start of a negotiation between the AF 502 (via the PCF 506) and a 5G wireless communication system (5GS). Using the Nnef_AFsessionWithQoS_Create request message, the AF 502 effectively queries the PCF 506 whether the 5GS supports ADU-based QoS. The 5GS response via the PCF 506 can indicate whether ADU-based QoS or PDU-based QoS is supported.

[0094]

[0100] According to an aspect, the Nnef_AFsessionWithQoS_Create request message may include a UE address, an AF identifier, a flow description or an external application identifier, a QoS reference, and may further include an alternative service requirement. In some embodiments, a period or traffic volume for the requested QoS may be included in the Nnef_AFsessionWithQoS_Create request message. According to some aspects, instead of a QoS reference, the AF 502 may provide the following individual QoS parameters: requested 5GS delay (optional), requested priority (optional), requested guaranteed flow bit rate (GFBR), requested maximum flow bit rate (MFBR), flow direction, burst size (optional), burst arrival time at the UE (uplink) or UPF (downlink) (optional), periodicity (optional), time domain (optional), and / or time to live (optional). If alternative service requirements are provided by the AF 502, a set of alternative QoS related parameters in the form of an alternative QoS profile may be provided for each QoS reference. Thus, there may be one or more ways to indicate a request for support of ADU-based QoS. For example, an alternative QoS profile may be communicated to the PCF 506, such as QoS Profile 2 or QoS Profile 3 shown above (both of which include QoS flow parameters that may represent ADU-based QoS).

[0095]

[0101] At 510, during authorization, the NEF 504 may assign a transaction reference ID to the Nnef_AFsessionWithQoS_Create request message sent at 508. At 510, the NEF 504 may authorize the AF request and may apply policies to control the overall amount of QoS authorized to the AF 502. If the Nnef_AFsessionWithQoS_Create request message at 510 is not authorized or the requested / required QoS is not allowed, the actions at 512, 514, 518, 520, and 522 may be skipped and the NEF 504 may respond to the AF 502 at 516 with a Nnef_AFsessionWithQoS_Create response message, which may include the transaction reference ID and a result value. In such a case, the result value may indicate that the authorization at 510 failed. The result value may indicate the cause of the failure.

[0096]

[0102] If the NEF 504 does not receive any individual QoS parameters (e.g., specific QoS such as low latency or jitter, or QoS based on specific service requirements) from the AF 502, the NEF 504 can use the UE address (provided with the Nnef_AFsessionWithQoS_Create request message) to find the PCF 506 from a Building Support Function (BSF) (not shown). At 512, the NEF 504 can interact with the PCF 506 by sending a Npcf_PolicyAuthorization_Create request message to the PCF 506. The NEF 504 can provide the UE address (provided with the Nnef_AFsessionWithQoS_Create request message), AF identifier, flow description, QoS reference, and alternative service requirements (if included) to the PCF 506 with the Npcf_PolicyAuthorization_Create request message. Any reception duration or traffic volume can also be included and mapped to sponsored data connectivity information. The PCF 506 may respond with an Npcf_PolicyAuthorization_Create response at 514. The NEF 504 may also send an Npcf_PolicyAuthorization_Subscribe message at 518, and in response may receive an Npcf_PolicyAuthorization_Notify message from the PCF 506 at 520. Alternative steps (not shown) may also be performed.

[0097]

[0103] If the AF 502 is deemed trusted by the operator, the AF 502 may interact directly with the PCF 506 to request to reserve resources for the AF session using a Npcf_PolicyAuthorization_Create request message at 512. If the AF 502 is deemed trusted by the operator, the PCF 506 may send a Npcf_PolicyAuthorization_Create response message directly to the AF 502 at 514 (not shown).

[0098]

[0104] The PCF 506 may determine whether the Npcf_PolicyAuthorization_Create request message at 512 is authorized and may notify the NEF 504 via a Npcf_PolicyAuthorization_Create response message at 514 if the request is not authorized.

[0099]

[0105] If the Npcf_PolicyAuthorization_Create request message is authorized at 512, the PCF 506 may derive the required QoS parameters based on the information provided by the NEF 504 and may determine whether this QoS (i.e., the requested QoS) is allowed (according to its PCF configuration). The PCF 506 may inform the NEF 504 of the result via a Npcf_PolicyAuthorization_Create response message at 514. Furthermore, if an alternative service requirement is provided, the PCF 506 may derive an alternative QoS parameter set from one or more QoS reference parameters included in the alternative service requirement, with the same priority.

[0100]

[0106] In some embodiments, the PCF derived alternative QoS parameter set for the Policy and Charging Control (PCC) rule can then be used to establish an alternative QoS profile. The alternative QoS profile parameters provided to the NG-RAN (not shown) can be specified elsewhere. If the PCF 506 determines that the SMF (not shown) requires updated policy information, the PCF 506 can issue an Npcf_SMPolicyControl_UpdateNotify request message (not shown) with updated policy information for the PDU session. The Npcf_SMPolicyControl_UpdateNotify request message can be sent during a PCF 506 initiated SM policy association modification procedure (not shown, not described herein).

[0101]

[0107] At 518, the NEF 504 may send an Npcf_PolicyAuthorization_Subscribe message to the PCF 506 to subscribe to notifications of resource allocation status, and may subscribe to other events not described herein.

[0102]

[0108] At 520, when an event condition is met, for example, the success or failure of establishing transmission resources corresponding to the QoS update, the PCF 506 may send an Npcf_PolicyAuthorization_Notify message to the NEF 504 notifying the NEF 504 of the event.

[0103]

[0109] If the AF 502 is deemed trusted by the operator, the PCF 506 may send an Npcf_PolicyAuthorization_Notify message directly to the AF 502 (not shown).

[0104]

[0110] At 522, the NEF 504 may send a Nnef_AFsessionWithQoS_Notify message to the AF 502 with the event reported by the PCF 506.

[0105]

[0111] To revoke the AF request, the AF 502 can send a Nnef_AFsessionWithQoS_Revoke request message (not shown) to the NEF 504. The NEF 504 can grant the revocation request and can trigger Ntsctsf_QoSandTSCAssistance_Delete / Unsubscribe and / or Npcf_PolicyAuthorization_Delete and Npcf_PolicyAuthorization_Unsubscribe operations (not shown) in response to the Nnef_AFsessionWithQoS_Revoke request message.

[0106]

[0112] The call flow diagram 500 and the process described therein can be modified as necessary so that the AF 502 and the 5GS can negotiate the capability to support ADU-based QoS via the PCF 506 (e.g., simply, the AF 502 queries the 5GS whether the 5GS supports ADU-based QoS, and the 5GS responds accordingly). The AF 502 and the 5GS can negotiate how to identify the ADU on the user plane via the PCF 506 (e.g., IP-based approach, RTP-based approach, etc.). The AF 502 may require ADU-based QoS requirements (e.g., as provided in an extension of the QoS reference or in a new QoS parameter), and the 5GS can set up policies / rules via the PCF 506 accordingly.

[0107]

[0113] 6 is a call flow diagram 600 related to the establishment of a UE requested PDU session according to some aspects. Specifically, the call flow diagram 600 relates to the establishment of a PDU session in a non-roaming case and a roaming case with local breakout. The procedure can be used, for example, to establish a new PDU session, to handover a packet data network (PDN) connection in an evolved packet system (EPS) to a PDU session in 5GS without using an N26 interface (not shown), to switch an existing PDU session between a non-3GPP access and a 3GPP access, or to request a PDU session for emergency services. The N26 interface can be an interface that interconnects the AMF 408 and a 4G network node MME (not shown) to enable interworking from 5G to 4G and vice versa. Shown are a UE 602, a RAN 604, an AMF 606, a UPF 608, an SMF 610, a PCF 612, a UDM 614, and a data network (DN) 616. The procedure shown in Figure 6 assumes that the UE 602 is already registered with the AMF 606, so the AMF 606 has already obtained the user subscription data from the UDM 614, unless the UE 602 is emergency registered.

[0108]

[0114] In 621, the UE 602 may send a NAS message containing a PDU session establishment request to the AMF 606. To establish a new PDU session, the UE generates a new PDU session ID that is inserted in the NAS message. The UE initiates the establishment procedure of the UE requested PDU session by sending a NAS message containing a PDU session establishment request in an N1 Session Management (SM) container. The PDU session establishment request includes PDU Session ID, Request PDU Session Type, Request Session and Service Continuity (SSC) Mode, 5GSM Capability, Protocol Configuration Option (PCO), SM PDU DN Request Container, [Number of Packet Filters], [Header Compression Configuration], UE Integrity Protection Max Data Rate, [Always On PDU Session Request], [Redundancy Steering Number (RSN)], and [PDU Session Pair ID]. The packet filter number indicates the number of packet filters supported for the signaled QoS rule for the PDU session being established. The packet filter number indicated by the UE is valid for the lifetime of the PDU session.

[0109]

[0115] At 622, the AMF 606 may select the SMF 610.

[0110]

[0116] At 623, the AMF 606 may send either a Nsmf_PDUSession_CreateSMContext (or a Nsmf_PDUSession_UpdateSMContext request (not shown)) to the SMF 610.

[0111]

[0117] At 624, subscription information can be obtained and / or updated.

[0112]

[0118] At 625, the SMF 610 may send either a Nsmf_PDUSession_CreateSMContext response or a Nsmf_PDUSession_UpdateSMContext response (not shown) to the AMF 606 in response to the request received at 623.

[0113]

[0119] At 626, a secondary authentication / authorization can be performed.

[0114]

[0120] In 627a, if a dynamic PCC is to be used for the PDU session, the SMF 610 can perform a PCF 612 selection. If the request type indicates an "existing PDU session" or an "existing urgent PDU session", the SMF 610 can use the PCF 612 already selected for the PDU session. Otherwise, the SMF 610 can apply local policies.

[0115]

[0121] At 627b, the SMF 610 may perform an SM policy association establishment procedure or an SMF initiated SM policy association modification. According to aspects described herein, policy charging and control (PCC) rules provided by the PCF 612 may be updated to receive ADU-based QoS policies and to select a UPF 608 that supports an ADU-based QoS framework. According to an aspect, updates to policy rules provided by the PCF 612 may be applicable to dynamic PCC rules.

[0116]

[0122] In 628, the SMF 610 can select one or more UPFs 608, as needed. Furthermore, the PDU session establishment and / or PDU session modification can provide ADU (or PDU set) detection rules to be sent to the UPF.

[0117]

[0123] At 629, the SMF 610 may perform an SMF 610 initiated session management (SM) policy association modification procedure.

[0118]

[0124] If the request type indicates "initial request," the SMF 610 may initiate an N4 session establishment procedure with the selected UPF 608; otherwise, the SMF 610 may initiate an N4 session modification procedure with the selected UPF 608. The N4 session establishment / modification request / response may include packet detection rules. According to certain aspects described herein, these packet detection rules may be configured to optionally support ADU detection rules.

[0119]

[0125] In 630a, the SMF 610 may send an N4 session establishment / modification request to the UPF 608. If the SMF 610 determines to perform redundant transmission for one or more QoS flows of the PDU session, two CN tunnel information are requested by the SMF 610 from the UPF 608. The SMF 610 also instructs the UPF 608 to remove duplicate packets for the QoS flows in the uplink direction. The SMF 610 indicates to the UPF 608 that one CN tunnel information is used as a redundant tunnel for the PDU session. If the SMF 610 determines to insert two intermediate UPFs (I-UPFs) between the PSA UPF and the NG-RAN (e.g., RAN 604) for redundant transmission, the SMF 610 may request corresponding CN tunnel information and provide them to the I-UPF and the PSA UPF, respectively. The SMF 610 may also instruct the PSA UPF to remove duplicate packets for the QoS flows in the uplink direction.

[0120]

[0126] At 630b, the UPF 608 may acknowledge by sending an N4 Session Establishment / Modification response.

[0121]

[0127] At 631, the SMF 610 may send a Namf_Communication_N1N2MessageTransfer to the AMF 606. The Namf_Communication_N1N2MessageTransfer may include N2 SM information, which may include a QoS flow ID, a QFI, and a QoS profile, among other parameters. According to some aspects, the QFI and QoS profile may be configured to be consistent with the ADU-based QoS. Furthermore, the Namf_Communication_N1N2MessageTransfer may include an N1 SM container, which may include a PDU session establishment accept message, which may include a QoS rule and QoS flow-level QoS parameters, if required, for the QoS flow associated with the QoS rule, among other parameters. The QoS rule and QoS flow-level QoS parameters, if required, for the QoS flow associated with the QoS rule, may all be configured to be consistent with the ADU-based QoS.

[0122]

[0128] Furthermore, the N2 SM information carries information that the AMF 606 forwards to the RAN 604, including, among other things, one or more QoS profiles and corresponding QFIs that can be provided to the RAN 604. Furthermore, the PDU session establishment and / or PDU session modification can provide a new QoS profile to be sent to the RAN 604. The SMF 610 can indicate, for each QoS flow, whether redundant transmission is to be performed or not by a corresponding redundant transmission indicator. QoS rules and QoS flow level QoS parameters, if required, for the QoS flows associated with those QoS rules, and QoS profiles can be included in the PDU session establishment acceptance in the N1 SM and in the N2 SM information.

[0123]

[0129] At 632, the AMF 606 may send an N2 PDU session request (NAS message) to the RAN 604.

[0124]

[0130] At 633, the RAN 604 may issue an AN-specific signaling exchange with the UE 602 related to the information received from the SMF 610. For example, in the case of an NG-RAN, a radio resource control (RRC) connection reconfiguration may be performed in which the UE establishes the necessary NG-RAN resources related to the QoS rules for the PDU session request received at 632.

[0125]

[0131] At 634, the RAN may send an N2 PDU session response to the AMF 606. The N2 PDU session response may include, among other things, a list of accepted / rejected QFIs. The RAN 604 may reject the addition or modification of a QoS flow, for example due to UE-slice-MBR processing. If the RAN 604 rejects the QFI, the SMF 610 is responsible for updating the QoS rules and flow-level QoS parameters associated with the rejected QoS flow in the UE 602 accordingly.

[0126]

[0132] Following the first data uplink at 635, the AMF 606 may forward the N2 SM information received from the RAN 604 to the SMF 610 (not shown). If a list of rejected QFIs is included in the N2 SM information, the SMF 610 may release the QoS profiles associated with the rejected QFIs.

[0127]

[0133] 7 is a block diagram illustrating an example of a hardware implementation of a core network entity 700 (e.g., SMF, AF) employing a processing system 714, according to some aspects. For example, the core network entity 700 may correspond to the SMF 410 or the XR AF / AS 418, as shown and described in connection with FIG.

[0128]

[0134] According to various aspects of the disclosure, the elements, or any portion of the elements, or any combination of the elements, may be implemented using a processing system 714 including one or more processors, such as processor 704. Examples of processors 704 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the disclosure. In various embodiments, the core network entity 700 may be configured to perform any one or more of the functions described herein. That is, the processor 704, when employed within the core network entity 700, may be used to perform any one or more of the methods or processes described and illustrated in, for example, FIG. 5 and / or FIG. 6.

[0129]

[0135] The processor 704 may be implemented via a baseband or modem chip in some cases, while in other implementations the processor 704 may include any number of devices separate and distinct from the baseband or modem chip (e.g., in scenarios that may cooperate to achieve the embodiments discussed herein). As mentioned above, various hardware configurations and components other than a baseband modem processor may be used in the implementations, including radio frequency (RF) chains, power amplifiers, modulators, buffers, interleavers, summers / analog summers, etc.

[0130]

[0136] In this example, the processing system 714 may be implemented using a bus architecture, represented generally by bus 702. The bus 702 may include any number of interconnected buses and bridges, depending on the specific application of the processing system 714 and the overall design constraints. The bus 702 links together various circuits, including one or more processors (represented generally by processor 704), memory 705, and computer-readable media (represented generally by computer-readable media 706). The bus 702 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further.

[0131]

[0137] A bus interface 708 provides an interface between the bus 702 and an interface 710. The interface 710 may provide a communications interface or means for communicating with various other devices over a transmission medium (e.g., an air interface, a wired interface). Depending on the nature of the device, a user interface 712 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, control knobs, etc.) may also be provided. Of course, such a user interface 712 is optional and may be omitted in some embodiments.

[0132]

[0138] The processor 704 is responsible for managing the bus 702 and general processing, including executing software stored on the computer-readable medium 706. This software, when executed by the processor 704, causes the processing system 714 to perform various functions described below for any particular device. The computer-readable medium 706 and memory 705 can also be used to store data that is manipulated by the processor 704 when executing the software. For example, the memory 705 can store 5G QoS flow identifier (5QI) related parameters 760, ADU 5G QoS flow identifier (A5QI) related parameters 761, QoS flow parameters 762, QoS profiles 763, ADU recognition filters 764, ADU detection rules 765, and / or ADU processing rules 766. The foregoing list is exemplary and non-limiting.

[0133]

[0139] The one or more processors 704 in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on computer-readable medium 706.

[0134]

[0140] The computer readable medium 706 may be a non-transitory computer readable medium. Non-transitory computer readable media include, by way of example, a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic strip), an optical disk (e.g., a compact disk (CD) or a digital versatile disk (DVD)), a smart card, a flash memory device (e.g., a card, stick, or key drive), a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer readable medium 706 may be present within the processing system 714, may be external to the processing system 714, or may be distributed across multiple entities including the processing system 714. The computer readable medium 706 may be embodied in a computer program product. By way of example, the computer program product may include the computer readable medium in packaging materials. In some examples, computer readable medium 706 can be part of memory 705. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system. In some examples, computer readable medium 706 can be implemented on an article of manufacture, which may further include one or more other elements or circuits, such as processor 704 and / or memory 705.

[0135]

[0141] In some aspects, the core network entity 700 may include a memory and a processor coupled to the memory, where the processor (e.g., processing system 714, processor 704) and memory 705 are configured to perform any of the methods, functions, or algorithms described herein. In some aspects of the disclosure, the processor 704 may include circuitry configured for various functions. For example, the processor 704 may include communication and processing circuitry 740 configured to communicate with other core entities via interfaces therebetween. For example, if the core network entity 700 is an SMF, the SMF may communicate with the UPF via an N4 interface as shown and described in connection with FIG. 4.

[0136]

[0142] According to some aspects, the communication and processing circuitry 740 may also obtain policy rules associated with the ADU-based QoS policy from at least one of a policy control function (PCF) or a local configuration (e.g., if the policy is configured in the SMF). The communication and processing circuitry 740 may also be configured to obtain an identification of a user plane function that supports the ADU-based QoS policy from the policy control function (PCF).

[0137]

[0143] In some embodiments, the communications and processing circuitry 740 may include one or more hardware components that provide a physical structure to perform processes related to communications (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, the communications and processing circuitry 740 may include one or more modems. In some embodiments, the communications and processing circuitry 740 may include one or more hardware components that provide a physical structure to perform processes related to processing, such as, for example, obtaining policy rules related to the ADU-based QoS policy from at least one of a policy control function (PCF) or a local configuration and / or obtaining an identity of a user plane function that supports the ADU-based QoS policy from a policy control function (PCF). In some implementations where communication involves receiving information, the communications and processing circuitry 740 may obtain information from a component of the core network entity 700 (e.g., from an interface 710, which receives the information via an operative coupling, such as to a data network (not shown), either hardwired or wireless), process the information, and output the processed information. For example, the communications and processing circuitry 740 may output the information to another component of the processor 704, to the memory 705, or to the bus interface 708. In some embodiments, the communications and processing circuitry 740 may receive one or more of a signal, a message, other information, or any combination thereof. In some embodiments, the communications and processing circuitry 740 may include functionality related to a means for receiving.

[0138]

[0144] In some aspects of the disclosure, the processor 704 may include session establishment circuitry 741 configured for various functions including, for example, establishing a session including at least one of application data unit (ADU) detection rules or ADU processing rules related to detection of an ADU in the user plane. The session may be, for example, a PDU session. In some embodiments, the core network entity may be a session management function (SMF) and the session may be established with a user plane function (UPF) via an interface between the SMF and the UPF. The interface may be, for example, an N4 interface. The session establishment circuitry 741 may also configure an ADU-aware uplink filter for the user equipment during at least one of PDU session establishment or PDU session modification. The ADU-aware filter may be stored, for example, in an ADU-aware filter 764 portion of the memory 705 according to some embodiments. By way of example, an ADU may consist of a set of Internet Protocol (IP) packets or Ethernet frames (but not a combination of the two) that are jointly processed by at least one of an application function or an application server. One or more ADUs, each containing multiple PDUs, may be generated substantially simultaneously by an application server and may be grouped into at least one burst. In embodiments where the core network entity 700 is an application function (AF), the session establishment circuitry 741 may be further configured to, for example, send a request to create a session supporting an ADU-based QoS flow. In some embodiments, when the core network entity 700 is an application function (AF), the session may be an AF session.Furthermore, in an embodiment where the core network entity 700 is an application function (AF), if the core network entity is not a trusted core network entity, the request to create a session may be sent to a network publication function (NEF) and an acknowledgement may be received from the NEF, or if the core network entity is a trusted core network entity, the request to create a session may be sent to a policy control function (PCF) and an acknowledgement may be received from the PCF.

[0139]

[0145] In some embodiments, the session establishment circuitry 741 may include one or more hardware components that provide a physical structure to perform processes related to establishing a session including at least one of ADU detection rules or ADU processing rules related to detecting an ADU in the user plane, and / or establishing a session with a UPF via an interface, such as an N4 interface between the SMF and the UPF, for example, if the core network entity may be an SMF, and / or sending a request to create a session supporting an ADU-based QoS flow. The session establishment circuitry 741 and / or the communication and processing circuitry 740 may receive an acknowledgment of the creation of the session in response to completion of the negotiation. The session establishment circuitry 741 may be further configured to execute session establishment instructions 751 (e.g., software), stored on the computer-readable medium 706, to perform one or more of the functions described herein.

[0140]

[0146] In some aspects of the disclosure, the processor 704 may include ADU recognition determination circuitry 742 configured for various functions including, for example, determining whether ADU recognition applies based on application of at least one of ADU detection rules or ADU processing rules for one or more quality of service (QoS) flows. In some embodiments, the ADU recognition determination circuitry 742 may include one or more hardware components that provide a physical structure for performing processes related to determining whether ADU recognition applies based on application of at least one of ADU detection rules or ADU processing rules for one or more quality of service (QoS) flows. The ADU recognition determination circuitry 742 may be further configured to execute ADU recognition instructions 752 (e.g., software) stored on the computer-readable medium 706 to perform one or more functions described herein.

[0141]

[0147] In some aspects of the disclosure, the processor 704 may include A5QI assignment circuitry 743 configured for various functions including, for example, assigning at least one ADU 5G QoS flow identifier (A5QI) to at least one ADU-aware QoS flow in response to determining that ADU awareness applies (e.g., by utilizing the ADU awareness determination circuitry 742 described above). The A5QI may be associated with ADU QoS parameters, which may be included in at least one of a table of standardized 5G QoS flow identifier (5QI)-related QoS parameters or a table of standardized A5QI-related QoS parameters. These tables may be stored, for example, in a 5QI-related parameters 760 portion of the memory 705 and an A5QI-related parameters 761 portion of the memory 705, respectively. In some embodiments, the A5QI can be associated with ADU QoS parameters, which may include at least one of a maximum ADU size, a maximum number of packet data units (PDUs) per ADU, an ADU delay budget, an ADU maximum data burst amount, or an ADU error rate. The ADU QoS parameters can be stored, for example, in the QoS profile 763 portion of the memory 705. The QoS profile 763 portion and / or the QoS flow parameters 762 portion of the memory 705 can store, for example, a dedicated ADU QoS profile including QoS flow parameters exclusively associated with at least one A5QI, and / or a QoS profile including QoS flow parameters associated with a 5G QoS flow identifier (5QI) and at least one A5QI. In some embodiments, the A5QI assignment circuitry 743 can include one or more hardware components that provide a physical structure to perform processes related to assigning at least one A5QI to at least one ADU-aware QoS flow in response to determining that ADU awareness applies.The A5QI allocation circuitry 743 may be further configured to execute A5QI allocation instructions 753 (e.g., software) stored on the computer-readable medium 706 to perform one or more functions described herein.

[0142]

[0148] In some aspects of the disclosure, the processor 704 may include ADU-aware QoS flow configuration circuitry 744 configured for various functions including, for example, configuring a radio access network (RAN) entity with at least one A5QI and at least one ADU-aware QoS flow. The ADU-aware QoS flow configuration circuitry 744 may be further configured to configure a user plane function (UPF) with at least one of an ADU-aware filter or an ADU detection rule. In one embodiment, the SMF may send the ADU detection rule (PDU set detection rule) to the UPF over the N4 interface. In some embodiments, the ADU-aware QoS flow configuration circuitry 744 may include one or more hardware components that provide a physical structure for performing processes related to configuring a radio access network (RAN) entity with at least one A5QI and at least one ADU-aware QoS flow and for performing processes related to configuring a user plane function (UPF) with at least one of an ADU-aware filter or an ADU detection rule. The ADU-aware QoS flow configuration circuitry 744 may be further configured to execute ADU-aware QoS flow configuration instructions 754 (e.g., software), stored on the computer-readable medium 706, to perform one or more functions described herein.

[0143]

[0149] In some aspects of the disclosure, for example, when the core network entity 700 is an application function (AF), the processor 704 may include policy and rule negotiation circuitry 745 configured for various functions including, for example, negotiating at least one of an ADU-based QoS policy or ADU QoS rules applicable to a session. For example, the various policies and rules may be stored, for example, in an ADU detection rules 765 portion and / or an ADU processing rules 766 portion of the memory 705. In some embodiments, the policy and rule negotiation circuitry 745 may include one or more hardware components that provide a physical structure for performing processes related to negotiating at least one of an ADU-based QoS policy or ADU QoS rules applicable to a session. The policy and rule negotiation circuitry 745 may be further configured to execute policy and rule negotiation instructions 755 (e.g., software), stored on the computer-readable medium 706, to perform one or more functions described herein.

[0144]

[0150] FIG. 8 is a flow chart illustrating an example process 800 (e.g., a method) of wireless communication in a core network entity, according to some aspects. As described below, certain implementations within the scope of the present disclosure may omit some or all of the illustrated features, and some illustrated features may not be required for the implementation of all embodiments. In some embodiments, the process 800 may be performed by the SMF 410 illustrated in FIG. 4. The core network entity may be, for example, similar to the SMF 410 of FIG. 4. In some embodiments, the process 800 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0145]

[0151] In block 802, the core network entity may establish a session including at least one of an ADU detection rule or an ADU processing rule related to detection of an application data unit (ADU) in a user plane. For example, the session establishment circuitry 741 shown and described above in connection with FIG. 7 may provide a means for establishing a session including at least one of an ADU detection rule or an ADU processing rule related to detection of an application data unit (ADU) in a user plane. According to some aspects, the core network entity may be a session management function (SMF), and the session may be established with a user plane function (UPF) via an interface between the SMF and the UPF. According to one embodiment, the interface may be an N4 interface.

[0146]

[0152] At block 804, the core network entity may determine whether ADU awareness applies based on application of at least one of the ADU detection rules or the ADU processing rules for one or more quality of service (QoS) flows. For example, the ADU awareness determination circuitry 742 shown and described above in connection with FIG. 7 may provide a means for determining whether ADU awareness applies based on application of at least one of the ADU detection rules or the ADU processing rules for one or more quality of service (QoS) flows. In some embodiments, an ADU may consist of a set of Internet Protocol (IP) packets or Ethernet frames (but not a combination of the two) that are jointly processed by at least one of an application function or an application server. One or more ADUs, each including multiple PDUs, may be generated substantially simultaneously by an application server and may be grouped into at least one burst. In some aspects, the core network entity may obtain policy rules associated with the ADU-based QoS policy from at least one of a policy control function (PCF) or a local configuration. According to another aspect, a core network entity can obtain, from a policy control function (PCF), an identity of a user plane function that supports an ADU-based QoS policy.

[0147]

[0153] 9 is a flow chart illustrating an example process 900 (e.g., a method) of wireless communication in a core network entity, according to some aspects. As described below, certain implementations within the scope of the present disclosure may omit some or all of the illustrated features, and some illustrated features may not be required for the implementation of all embodiments. In some embodiments, the process 900 may be performed by the AMF 408 illustrated in FIG. 4. The core network entity may be, for example, similar to the AMF 408 of FIG. 4. In some embodiments, the process 900 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0148]

[0154] At block 902, the core network entity may assign at least one ADU 5G QoS flow identifier (A5QI) to at least one ADU-aware QoS flow in response to determining that ADU awareness applies. For example, the A5QI assignment circuitry 743 shown and described above in connection with FIG. 7 may provide means for assigning at least one ADU 5G QoS flow identifier (A5QI) to at least one ADU-aware QoS flow in response to determining that ADU awareness applies. According to some aspects, the A5QI may be associated with ADU QoS parameters, which may be included in at least one of a table of standardized 5G QoS flow identifier (5QI)-related QoS parameters or a table of standardized A5QI-related QoS parameters. In some embodiments, the A5QI can be associated with ADU QoS parameters, which can include at least one of a maximum ADU size, a maximum number of packet data units (PDUs) per ADU, an ADU delay budget, an ADU maximum data burst amount, or an ADU error rate. In another embodiment, the parameters associated with the at least one ADU-aware QoS flow can be provided in at least one of a dedicated ADU QoS profile that includes QoS flow parameters exclusively associated with the at least one A5QI, or a QoS profile that includes QoS flow parameters associated with a 5G QoS flow identifier (5QI) and the at least one A5QI.

[0149]

[0155] At block 904, the core network entity may configure a radio access network (RAN) entity with the at least one A5QI and the at least one ADU-aware QoS flow. For example, the ADU-aware QoS flow configuration circuitry 744 shown and described above in connection with FIG. 7 may provide a means for configuring a radio access network (RAN) entity with the at least one A5QI and the at least one ADU-aware QoS flow.

[0150]

[0156] At block 906, the core network entity may configure a user plane function (UPF) using at least one of the ADU-aware filters or ADU detection rules. For example, the ADU-aware QoS flow configuration circuitry 744 shown and described above in connection with FIG. 7 may provide a means for configuring a user plane function (UPF) using at least one of the ADU-aware filters or ADU detection rules. In some embodiments, the core network entity may configure an ADU-aware uplink filter for a user equipment during at least one of packet data unit (PDU) session establishment or PDU session modification.

[0151]

[0157] FIG. 10 is a flow chart illustrating an example process 1000 (e.g., a method) of wireless communication in a core network entity according to some aspects. As described below, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some illustrated features may not be required for the implementation of all embodiments. In some embodiments, the process 1000 may be performed by the core network entity 700 (e.g., an application function (AF)) illustrated in FIG. 7. The core network entity 700 may be similar to, for example, the XR AF 418 of FIG. 4. In some embodiments, the process 1000 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0152]

[0158] At block 1002, the core network entity may transmit a request to create a session supporting an application data unit (ADU)-based quality of service (QoS) flow. For example, the session establishment circuitry 741 shown and described above in connection with FIG. 7 may provide means for transmitting a request to create a session supporting an application data unit (ADU)-based quality of service (QoS) flow. According to some aspects, the core network entity may be an application function (AF) and the session may be an AF session. In some embodiments, if the core network entity is not a trusted core network entity, the request to create the session may be transmitted to a network publishing function (NEF) and an acknowledgment may be received from the NEF, or if the core network entity is a trusted core network entity, the request to create the session may be transmitted to a policy control function (PCF) and an acknowledgment may be received from the PCF. According to some aspects, the PCF may generate PCC rules for ADU-based QoS (PDU set-based QoS).

[0153]

[0159] At block 1004, the core network entity may negotiate at least one of an ADU-based QoS policy or ADU QoS rules applicable to the session. By way of example, if the core network entity is an AF, the AF may negotiate 5GS support capabilities. For example, the policy and rules negotiation circuitry 745 shown and described above in connection with FIG. 7 may provide a means for negotiating at least one of an ADU-based QoS policy or ADU QoS rules applicable to the session.

[0154]

[0160] At block 1006, the core network entity may receive an acknowledgment of the creation of the session in response to completion of the negotiation. For example, the communications and processing circuitry 740 and the policy and rules negotiation circuitry 745, in combination with the interface 710 shown and described above in connection with FIG. 7, may provide a means for receiving an acknowledgment of the creation of the session in response to completion of the negotiation.

[0155]

[0161] 11 is a block diagram illustrating an example of a hardware implementation of a RAN entity 1100 employing a processing system, in accordance with some aspects. For example, the RAN entity 1100 may correspond to any of the base stations (e.g., gNBs) or other scheduling entities shown in any one or more of FIGs. 1, 2, 4, and / or 6.

[0156]

[0162] According to various aspects of the disclosure, the elements, or any portion of the elements, or any combination of the elements, may be implemented using a processing system 1114 including one or more processors 1104. The processing system 1114 may be substantially similar to the processing system 714 shown in FIG. 7, including a bus interface 1108, a bus 1102, a memory 1105, a processor 1104, and a computer-readable medium 1106. Additionally, the RAN entity 1100 may include an optional user interface 1112, and a transceiver 1110. Additionally, the RAN entity may include an antenna / antenna array 1130, which may be operatively coupled to the transceiver 1110 and the bus interface 1108. In some embodiments, the transceiver 1110 and / or the antenna / antenna array 1130 may include phase shifters (not shown) for digital and / or analog beamforming via one or more of the antennas / antenna array 1130. When utilized within the RAN entity 1100, the processor 1104 may be used to perform any one or more of the processes described below.

[0157]

[0163] In some aspects of the disclosure, the processor 1104 may include circuitry configured for various functions. For example, the processor 1104 may include communication and processing circuitry 1140 configured to communicate with user equipment and various core network entities. The communication and processing circuitry 1140 of FIG. 11 may be substantially similar to the communication and processing circuitry 740 of FIG. 7, and therefore, for the sake of brevity, a description will not be repeated.

[0158]

[0164] In some aspects of the disclosure, the processor 1104 may include session establishment circuitry 1141 configured for various functions including, for example, receiving a session request, accepting the establishment of a session, and sending a session response. In some embodiments, the session establishment circuitry 1141 may include one or more hardware components that provide a physical structure for performing processes related to receiving a session request, accepting the establishment of a session, and sending a session response. The session establishment circuitry 1141 may be further configured to execute session establishment instructions 1151 (e.g., software) stored on the computer-readable medium 706 to perform one or more functions described herein.

[0159]

[0165] In some aspects of the disclosure, the processor 1104 may include ADU-aware QoS flow circuitry 1142 configured for various functions including, for example, communicating one or more application data units (ADUs) during a session to a user equipment over a user plane in accordance with an ADU-based QoS policy associated with at least one ADU-aware QoS flow. The ADU-based QoS policy may be stored, for example, in an ADU-based QoS policy 1160 portion of the memory 1105. According to some embodiments, the one or more ADUs, each of which may include multiple PDUs, may be generated substantially simultaneously by an application server and may be grouped into at least one burst. In some aspects, the at least one burst may correspond to at least one of a video frame or a slice of a video frame. According to some embodiments, session requests and session responses may be exchanged with a session management function (SMF) over an N2 interface via an access and mobility function (AMF). In some embodiments, the ADU-aware QoS flow circuitry 1142 may include one or more hardware components that provide a physical structure that performs processes related to conveying one or more application data units (ADUs) to user equipment over a user plane during a session in accordance with an ADU-based QoS policy associated with at least one ADU-aware QoS flow. The ADU-aware QoS flow circuitry 1142 may be further configured to execute ADU-aware QoS flow instructions 1152 (e.g., software) stored on the computer-readable medium 1106 to perform one or more functions described herein.

[0160]

[0166] FIG. 12 is a flow chart illustrating an example process 1200 (e.g., a method) of wireless communication in a RAN entity, according to some aspects. As described below, certain implementations within the scope of the present disclosure may omit some or all of the illustrated features, and some illustrated features may not be required for the implementation of all embodiments. In some embodiments, the process 1200 may be performed by the RAN entity 1100 illustrated in FIG. 11. The RAN entity 1100 may be similar to any of the RAN entities in any of FIG. 1, FIG. 2, FIG. 4, and / or FIG. 6, for example. In some embodiments, the process 1200 may be performed by any suitable device or means for performing the functions or algorithms described below.

[0161]

[0167] At block 1202, the RAN entity may receive a session request. At block 1204, the RAN entity may accept the establishment of the session. At block 1206, the RAN entity may transmit a session response. For example, the session establishment circuitry 1141, in combination with the transceiver 1110 and the antenna array 1130 shown and described above in connection with FIG. 11, may provide a means for receiving the session request, accepting the establishment of the session, and / or transmitting the session response. According to some aspects, the session may be a PDU session.

[0162]

[0168] At block 1208, the RAN entity can convey one or more application data units (ADUs) during a session to a user equipment over a user plane in accordance with an ADU-based QoS policy associated with at least one ADU-aware QoS flow. For example, the ADU-aware QoS flow circuitry 1142, in combination with the transceiver 1110 and the antenna array 1130 shown and described above in connection with FIG. 11, can provide a means for conveying one or more application data units (ADUs) during a session to a user equipment over a user plane in accordance with an ADU-based QoS policy associated with at least one ADU-aware QoS flow. According to some aspects, the ADU-based QoS policy can be stored in an ADU-based QoS policy 1160 portion of the memory 1105 of the RAN entity 1100, as shown and described in connection with FIG. 11.

[0163]

[0169] Several aspects of wireless communication networks have been presented with reference to example implementations. As will be readily appreciated by those skilled in the art, various aspects described throughout this disclosure can be extended to other telecommunications systems, network architectures, and communication standards.

[0164]

[0170] Aspect 1: A core network entity for wireless communications comprising: a memory; and a processor coupled to the memory, wherein the processor and the memory are configured to establish a session including at least one of an ADU detection rule or an ADU processing rule related to detection of an application data unit (ADU) in a user plane; and determine whether ADU recognition applies for one or more quality of service (QoS) flows based on application of at least one of the ADU detection rule or the ADU processing rule.

[0165]

[0171] Aspect 2: The core network entity of aspect 1, wherein the processor and memory are further configured to, in response to determining that ADU awareness is applied, assign at least one ADU 5G QoS flow identifier (A5QI) to the at least one ADU-aware QoS flow, and configure a radio access network (RAN) entity using the at least one A5QI and the at least one ADU-aware QoS flow.

[0166]

[0172] Aspect 3: The core network entity of aspect 2, wherein the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters are included in at least one of a table of standardized 5G QoS flow identifier (5QI)-related QoS parameters or a table of standardized A5QI-related QoS parameters.

[0167]

[0173] Aspect 4: The core network entity of aspect 1 or 2, wherein the A5QI is associated with ADU QoS parameters, the ADU QoS parameters including at least one of a maximum ADU size, a maximum number of packet data units (PDUs) per ADU, an ADU delay budget, an ADU maximum data burst amount, or an ADU error rate.

[0168]

[0174] Aspect 5: A core network entity of any of aspects 1 to 4, wherein parameters associated with at least one ADU-aware QoS flow are provided in at least one of a dedicated ADU QoS profile including QoS flow parameters exclusively associated with at least one A5QI, or a QoS profile including QoS flow parameters associated with a 5G QoS flow identifier (5QI) and at least one A5QI.

[0169]

[0175] Aspect 6: A core network entity of any of aspects 1 to 5, wherein the processor and memory are further configured to configure a user plane function (UPF) using at least one of an ADU recognition filter or an ADU detection rule.

[0170]

[0176] Aspect 7: A core network entity of any of aspects 1 to 6, wherein the core network entity is a session management function (SMF) and the session is established with a user plane function (UPF) via an interface between the SMF and the UPF.

[0171]

[0177] Example 8: The core network entity of example 7, wherein the interface is an N4 interface.

[0172]

[0178] Aspect 9: A core network entity of any of aspects 1 to 8, wherein the ADU is comprised of a set of Internet Protocol (IP) packets or Ethernet frames that are jointly processed by at least one of an application function or an application server.

[0173]

[0179] Aspect 10: A core network entity of any of aspects 1 to 9, wherein one or more ADUs, each including multiple PDUs, are generated substantially simultaneously by an application server and grouped into at least one burst.

[0174]

[0180] Aspect 11: A core network entity of any of aspects 1 to 10, wherein the processor and memory are further configured to configure an ADU-aware uplink filter for a user equipment during at least one of a packet data unit (PDU) session establishment or a PDU session modification.

[0175]

[0181] Aspect 12: A core network entity of any of aspects 1 to 11, wherein the processor and memory are further configured to obtain policy rules associated with the ADU-based QoS policy from at least one of a policy control function (PCF) or a local configuration.

[0176]

[0182] Aspect 13: A core network entity of any of aspects 1 to 12, wherein the processor and memory are further configured to obtain, from a policy control function (PCF), an identification information of a user plane function that supports the ADU-based QoS policy.

[0177]

[0183] Aspect 14: A method in a core network entity, comprising: establishing a session including at least one of an ADU detection rule or an ADU processing rule related to detection of an application data unit (ADU) in a user plane; and determining whether ADU recognition is applied for one or more quality of service (QoS) flows based on application of at least one of the ADU detection rule or the ADU processing rule.

[0178]

[0184] Aspect 15: The method of aspect 14, further comprising: in response to determining that ADU awareness is applied, assigning at least one ADU 5G QoS flow identifier (A5QI) to the at least one ADU-aware QoS flow; and configuring a radio access network (RAN) entity using the at least one A5QI and the at least one ADU-aware QoS flow.

[0179]

[0185] Aspect 16: The method of aspect 14 or 15, wherein the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters are included in at least one of a table of standardized 5G QoS flow identifier (5QI)-related QoS parameters or a table of standardized A5QI-related QoS parameters.

[0180]

[0186] Aspect 17: The method of any of aspects 14 to 16, wherein the A5QI is associated with ADU QoS parameters, the ADU QoS parameters including at least one of a maximum ADU size, a maximum number of packet data units (PDUs) per ADU, an ADU delay budget, an ADU maximum data burst amount, or an ADU error rate.

[0181]

[0187] Aspect 18: The method of any of aspects 14 to 17, wherein parameters associated with the at least one ADU-aware QoS flow are provided in at least one of a dedicated ADU QoS profile including QoS flow parameters exclusively associated with at least one A5QI, or a QoS profile including QoS flow parameters associated with a 5G QoS flow identifier (5QI) and at least one A5QI.

[0182]

[0188] Aspect 19: The method of any of aspects 14 to 18, further comprising configuring a user plane function (UPF) using at least one of an ADU recognition filter or an ADU detection rule.

[0183]

[0189] Aspect 20: The method of any of aspects 14 to 19, wherein the core network entity is a session management function (SMF) and the session is established with a user plane function (UPF) via an interface between the SMF and the UPF.

[0184]

[0190] Aspect 21: The method of any of aspects 14-20, wherein the ADU is comprised of a set of Internet Protocol (IP) packets or Ethernet frames that are jointly processed by at least one of an application function or an application server.

[0185]

[0191] Aspect 22: The method of any of aspects 14-21, wherein one or more ADUs, each including multiple PDUs, are generated substantially simultaneously by an application server and grouped into at least one burst.

[0186]

[0192] Aspect 23: The method of any of aspects 14-22, further comprising configuring an ADU-aware uplink filter for a user equipment during at least one of a packet data unit (PDU) session establishment or a PDU session modification.

[0187]

[0193] Aspect 24: The method of any of aspects 14-23, further comprising obtaining policy rules associated with the ADU-based QoS policy from at least one of a Policy Control Function (PCF) or a local configuration.

[0188]

[0194] Aspect 25: The method of any of aspects 14-24, further comprising obtaining, from a policy control function (PCF), an identification of a user plane function that supports the ADU-based QoS policy.

[0189]

[0195] Aspect 26: A core network entity for wireless communications, comprising: a memory; and a processor coupled to the memory, wherein the processor and memory are configured to send a request to create a session supporting an Application Data Unit (ADU)-based Quality of Service (QoS) flow, negotiate at least one of an ADU-based QoS policy or an ADU QoS rule applicable to the session, and receive an acknowledgment of the creation of the session in response to completion of the negotiation.

[0190]

[0196] Aspect 27: The core network entity of aspect 26, wherein the core network entity is an application function (AF) and the session is an AF session.

[0191]

[0197] Aspect 28: A core network entity of aspect 25 or 26, wherein if the core network entity is not a trusted core network entity, a request to create a session is sent to a Network Publication Function (NEF) and an acknowledgment is received from the NEF, or, if the core network entity is a trusted core network entity, a request to create a session is sent to a Policy Control Function (PCF) and an acknowledgment is received from the PCF.

[0192]

[0198] Aspect 29: A method in a core network entity, comprising: sending a request to create a session supporting an application data unit (ADU)-based quality of service (QoS) flow; negotiating at least one of an ADU-based QoS policy or an ADU QoS rule applicable to the session; and receiving an acknowledgment of the creation of the session in response to completion of the negotiation.

[0193]

[0199] Example 30: The method of example 29, wherein the core network entity is an application function (AF) and the session is an AF session.

[0194]

[0200] Aspect 31: The method of aspect 29 or 30, wherein if the core network entity is not a trusted core network entity, a request to create a session is sent to a Network Publication Function (NEF) and an acknowledgment is received from the NEF, or, if the core network entity is a trusted core network entity, a request to create a session is sent to a Policy Control Function (PCF) and an acknowledgment is received from the PCF.

[0195]

[0201] Aspect 32: A method in a radio access network (RAN) entity, comprising: receiving a session request; accepting establishment of the session; sending a session response; and conveying, during the session, one or more application data units (ADUs) to a user equipment via a user plane in accordance with an ADU-based QoS policy associated with at least one ADU-aware QoS flow.

[0196]

[0202] Aspect 33: The method of aspect 32, wherein one or more ADUs, each including multiple PDUs, are generated substantially simultaneously by the application server and grouped into at least one burst.

[0197]

[0203] Example 34: The method of example 33, wherein at least one burst corresponds to at least one of a video frame or a slice of a video frame.

[0198]

[0204] Aspect 35: The method of any of aspects 32 to 34, wherein a session request and a session response are exchanged with a session management function (SMF) over an N2 interface via an access and mobility function (AMF).

[0199]

[0205] Aspect 36: A core network entity configured for wireless communication, comprising at least one means for performing the method of any one of aspects 14 to 25 or aspects 29 to 31.

[0200]

[0206] Aspect 37: A non-transitory computer-readable medium storing computer-executable code, the code including code for causing a core network entity to perform any one of the methods of aspects 14 to 25 or aspects 29 to 31.

[0201]

[0207] Example 38: A radio access network entity configured for wireless communication comprising a processor and a memory coupled to the processor, wherein the processor and the memory are configured to perform any one of the methods of aspects 32 to 35.

[0202]

[0208] Aspect 39: A radio access network entity configured for wireless communication, comprising at least one means for performing any one of the methods of aspects 32-35.

[0203]

[0209] Aspect 40: A non-transitory computer-readable medium having stored thereon computer-executable code, the computer-executable code including code for causing a radio access network entity to perform any one of the methods of aspects 32-35.

[0204]

[0210] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolutionary Data Optimized (EV-DO). Other embodiments may be implemented within systems employing Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standard, network architecture, and / or communication standard employed will depend on the particular application and the overall design constraints imposed on the system.

[0205]

[0211] Within the scope of this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A is in physical contact with object B, and object B is in contact with object C, then object A and object C can still be considered to be coupled to each other even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even if the first object is not in any direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are not limited as to type of electronic circuitry, but are intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in this disclosure, and software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in this disclosure.

[0206]

[0212] One or more of the components, steps, features, and / or functions shown in Figures 1-12 can be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions can also be added without departing from the novel features disclosed herein. The apparatus, devices, and / or components shown in any one or more of Figures 1-12 can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or incorporated into hardware.

[0207]

[0213] It is understood that the specific order or hierarchy of steps in the methods disclosed are examples of example processes. Based on design preferences, it is understood that the specific order or hierarchy of steps in the methods can be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented, unless expressly stated in the method claims.

[0208]

[0214] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects set forth herein, but are to be accorded the full scope consistent with the language of the claims, and reference to an element in the singular is not intended to mean "only one" unless so expressly stated, but rather "one or more." Unless otherwise expressly stated, the term "some" refers to one or more. Phrases referring to "at least one of" a list of items refer to any combination of those items, including single members. By way of example, "at least one of a, b, or c" is intended to include a, b, c, a and b, a and c, b and c, and a, b, and c. Similarly, the construction "a and / or b" is intended to include a, b, and a and b. The constructs A and / or B are intended to encompass A, B, and A and B. All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are known or later become known to those of skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims.

Claims

1. A core network entity for wireless communication, comprising: a memory; a processor coupled to the memory, wherein the processor and the memory establish a session including at least one of an ADU detection rule or an ADU processing rule related to the detection of application data units (ADUs) in the user plane, where the application data unit comprises a plurality of protocol data units, and the ADU in the user plane is detected using an IP-based or RTP-based approach; Based on one or more QoS flow parameters, it is configured to determine whether ADU recognition is applied based on the application of at least one of the ADU detection rule or the ADU processing rule. A core network entity.

2. In response to determining that ADU recognition is to be applied, the processor and the memory allocate at least one ADU 5G QoS flow identifier (A5QI) to at least one ADU recognition QoS flow; The core network entity according to claim 1, further configured to configure a radio access network (RAN) entity using the at least one A5QI and the at least one ADU recognition QoS flow.

3. The core network entity according to claim 2, wherein the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters are included in at least one of a table of standardized 5G QoS flow identifier (5QI)-related QoS parameters or a table of standardized A5QI-related QoS parameters.

4. The core network entity according to claim 2, wherein the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters include at least one of a maximum ADU size, a maximum number of packet data units (PDUs) per ADU, an ADU delay budget, a maximum ADU data burst volume, or an ADU error rate.

5. The parameters related to the at least one ADU recognition QoS flow are ​ ​ A dedicated ADU QoS profile including QoS flow parameters exclusively related to the at least one A5QI, or The core network entity according to claim 2, provided in at least one of the QoS profiles including QoS flow parameters related to the 5G QoS flow identifier (5QI) and the at least one A5QI. **Claim 6** The processor and the memory are The core network entity according to claim 1, further configured to configure a user plane function (UPF) using at least one of an ADU recognition filter or the ADU detection rule. **Claim 7** The core network entity according to claim 1, wherein the core network entity is a session management function (SMF), and the session is established with the UPF via an interface between the SMF and the user plane function (UPF). **Claim 8** The core network entity according to claim 1, wherein the ADU is composed of a set of Internet Protocol (IP) packets or Ethernet frames jointly processed by at least one of an application function or an application server. **Claim 9** One or more ADUs, each including a plurality of PDUs, are Substantially simultaneously generated by an application server, Grouped within at least one burst, the core network entity according to claim 1. **Claim 10** The processor and the memory are The core network entity according to claim 1, further configured to configure an ADU recognition uplink filter for a user equipment during at least one of packet data unit (PDU) session establishment or PDU session modification. **Claim 11** The processor and the memory are A policy control function (PCF), or From at least one of local configurations, The core network entity according to claim 1, further configured to obtain policy rules related to an ADU-based QoS policy. **Claim 12** The processor and the memory are The core network entity according to claim 1, further configured to obtain identification information of a user plane function that supports a QoS policy based on an application data unit (ADU) from a policy control function (PCF).

13. A method in a core network entity, comprising: establishing a session including at least one of an ADU detection rule or an ADU processing rule related to the detection of an application data unit (ADU) in a user plane, wherein the application data unit comprises a plurality of protocol data units, and the ADU in the user plane is detected using an IP-based or RTP-based approach; determining whether ADU recognition is applied based on the application of at least one of the ADU detection rule or the ADU processing rule for one or more QoS flows based on quality of service (QoS) flow parameters.

14. responding to a determination that ADU recognition is applied by assigning at least one ADU recognition QoS flow identifier (A5QI) to at least one ADU recognition QoS flow; configuring a radio access network (RAN) entity using the at least one A5QI and the at least one ADU recognition QoS flow; and / or the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters are included in at least one of a table of standardized 5G QoS flow identifier (5QI)-related QoS parameters or a table of standardized A5QI-related QoS parameters, and / or the A5QI is associated with ADU QoS parameters, and the ADU QoS parameters include at least one of a maximum ADU size, a maximum number of packet data units (PDUs) per ADU, an ADU delay budget, a maximum ADU data burst volume, or an ADU error rate, and / or parameters related to the at least one ADU recognition QoS flow include a dedicated ADU QoS profile including QoS flow parameters exclusively related to the at least one A5QI, or The method according to claim 13, provided in at least one of the QoS profiles, comprising QoS flow parameters related to a 5G QoS flow identifier (5QI) and the at least one A5QI.

15. Further comprising configuring a user plane function (UPF) using at least one of an ADU recognition filter or the ADU detection rule, and / or the core network entity is a session management function (SMF), and the session is established with the UPF via an interface between the SMF and the user plane function (UPF), and / or the ADU is composed of a set of Internet Protocol (IP) packets or Ethernet frames jointly processed by at least one of an application function or an application server, and / or one or more ADUs, each including a plurality of PDUs, are substantially simultaneously generated by an application server, grouped within at least one burst, and / or further comprising configuring an ADU recognition uplink filter for a user equipment during at least one of a packet data unit (PDU) session establishment or a PDU session modification, and / or a policy control function (PCF), or from at least one of local configurations, further comprising obtaining a policy rule related to an ADU-based QoS policy, and / or further comprising obtaining, from a policy control function (PCF), identification information of a user plane function that supports an ADU-based QoS policy, The method according to claim 13.

Images