Deadline-based data grouping

By introducing a deadline indication into the wireless communication system, the problems of jitter and delay management in data packet transmission are solved, communication efficiency and resource utilization are improved, and more devices can be connected.

CN119032552APending Publication Date: 2024-11-26QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033809.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-04-13
Filing Date
2023-04-14
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

Existing wireless communication systems struggle to effectively manage deadlines when dealing with data packet jitter and delay budgets, leading to data packet expiration and resource waste, which in turn affects communication efficiency and equipment support capabilities.

Method used

By introducing the concept of deadlines, network nodes and user equipment use deadline indications in data packet transmission to ensure that data packets arrive or are sent before the specified time, thereby optimizing data packet scheduling and resource utilization.

Benefits of technology

It improves the efficiency of data packet transmission, reduces resource waste, supports more devices, and enhances the overall performance of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032552A_ABST
    Figure CN119032552A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network node may receive an indication of a deadline for transmission of a set of protocol data units (PDUs), the indication of the deadline includes one or more of an indication of jitter of the set of PDUs, an indication of a packet delay budget based at least in part on the jitter of the set of PDUs and a nominal PDU set delay budget (PSDB), or an indication of an absolute time of the deadline. The network node may transmit the set of PDUs at a time based at least in part on the indication of the deadline. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 363,564, entitled “DEADLINE-BASED DATA PACKETS,” filed on April 25, 2022, and U.S. Provisional Patent Application No. 63 / 364,676, entitled “DEADLINE-BASED DATA PACKETS,” filed on May 13, 2022, and U.S. Non-Provisional Patent Application No. 18 / 300,311, entitled “DEADLINE-BASED DATA PACKETS,” filed on April 13, 2023, which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for deadline-based data packetization. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving an indication of a deadline for transmission of a set of protocol data units (PDUs), the indication of the deadline including one or more of: an indication of a jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter and a nominal PDU set delay budget (PSDB) for the set of PDUs, or an indication of an absolute time for the deadline. The method may include transmitting the set of PDUs at a time based at least in part on the indication of the deadline.

[0008] Some aspects described herein relate to a method of wireless communication performed by an application server. The method may include providing an indication of a deadline for transmission of a set of PDUs, the indication of the deadline comprising one or more of an indication of a jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter and a nominal PSDB for the set of PDUs, or an indication of an absolute time for the deadline. The method may include receiving the set of PDUs at a time based at least in part on the indication of the deadline.

[0009] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of a deadline for sending a set of PDUs, the indication of the deadline including one or more of the following. The one or more processors may be configured to send the set of PDUs at a time based at least in part on the indication of the deadline.

[0010] Some aspects described herein relate to an application server for wireless communication. The application server may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to provide an indication of a deadline for sending a set of PDUs, the indication of the deadline including one or more of the following. The one or more processors may be configured to receive the set of PDUs at a time based at least in part on the indication of the deadline.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive an indication of a deadline for sending a set of PDUs, the indication of the deadline comprising one or more of the following. The instruction set, when executed by one or more processors of the network node, may cause the network node to send the set of PDUs at a time based at least in part on the indication of the deadline.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by one or more instructions, the one or more instructions, when executed by one or more processors of an application server. The instruction set, when executed by the one or more processors of the one or more instructions, may cause the one or more instructions to provide an indication of a deadline for sending a set of PDUs when executed by the one or more processors of the one or more instructions, the indication of the deadline comprising one or more of the following. The instruction set, when executed by the one or more processors of the one or more instructions, may cause the one or more instructions to receive the set of PDUs at a time based at least in part on the indication of the deadline when executed by the one or more processors of the one or more instructions.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for receiving an indication of a deadline for sending a set of PDUs, the indication of the deadline comprising one or more of: an indication of a jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter and a nominal PSDB for the set of PDUs, or an indication of an absolute time for the deadline. The apparatus may include: means for sending the set of PDUs at a time based at least in part on the indication of the deadline.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for providing an indication of a deadline for transmission of a set of PDUs, the indication of the deadline comprising one or more of: an indication of a jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter and a nominal PSDB for the set of PDUs, or an indication of an absolute time for the deadline. The apparatus may include: means for receiving the set of PDUs at a time based at least in part on the indication of the deadline.

[0015] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include sending an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node. The method may include receiving the one or more data packets based at least in part on the one or more data packets arriving at or before the deadline.

[0016] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with data packets for a communication session. The method may include sending the one or more data packets based at least in part on the one or more data packets being sent at or before the deadline.

[0017] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node. The one or more processors may be configured to receive the one or more data packets based at least in part on the one or more data packets arriving at or before the deadline.

[0018] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with a data packet of a communication session. The one or more processors may be configured to send the one or more data packets based at least in part on the one or more data packets being sent at or before the deadline.

[0019] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to send an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive the one or more data packets based at least in part on the one or more data packets arriving at or before the deadline.

[0020] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with data packets of a communication session. The instruction set, when executed by one or more processors of the network node, may cause the network node to send the one or more data packets based at least in part on the one or more data packets being sent at or before the deadline.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node. The apparatus may include means for receiving one or more data packets based at least in part on one or more data packets arriving at or before the deadline.

[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of one or more of a cutoff time, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with data packets for a communication session. The apparatus may include means for sending one or more data packets based at least in part on the one or more data packets being sent at or before the cutoff time.

[0023] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as substantially described herein with reference to and as illustrated by the accompanying drawings, description, and appendices.

[0024] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0025] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0027] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0028] Figure 2 is a diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0029] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0030] Figure 4 is a diagram illustrating an example of jitter distribution according to the present disclosure.

[0031] Figure 5 is a diagram illustrating an example of a packet delay budget constraint for jitter-based communications according to the present disclosure.

[0032] Figures 6 to 10 is a diagram illustrating an example associated with data grouping based on a deadline according to the present disclosure.

[0033] Figures 11 to 14 is a diagram illustrating an example process associated with deadline-based data grouping according to the present disclosure.

[0034] Figures 15 to 17 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0035] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0036] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0037] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0038] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0039] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.

[0040] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0041] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. A base station 110 that relays communications may be referred to as a relay station, relay base station, relay, or the like.

[0042] The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0043] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0044] UE 120 may be distributed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0045] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0046] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0047] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0048] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0049] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz) and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0050] In view of the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0051] In some aspects, UE 120 may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may send an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node; and receive the one or more data packets based at least in part on the one or more data packets arriving at or before the deadline. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0052] In some aspects, the network node may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may receive an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with data packets for a communication session; and send the one or more data packets based at least in part on the one or more data packets being sent at or before the deadline.

[0053] As described in more detail elsewhere herein, the communications manager 150 may receive an indication of a deadline for transmission of a set of protocol data units (PDUs), the indication of the deadline comprising one or more of: an indication of jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter for the set of PDUs and a nominal PSDB, or an indication of an absolute time for the deadline; and transmit the set of PDUs at a time based at least in part on the indication of the deadline. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0054] In some aspects, the application server may communicate with the UE via the wireless network 100. In some aspects, the application server may communicate with the network node and / or an additional network node in communication with the network node. The application server may provide an indication of a deadline for sending a set of PDUs, the indication of the deadline comprising one or more of: an indication of a jitter of the set of PDUs, an indication of a packet delay budget based at least in part on the jitter of the set of PDUs and a nominal PSDB, or an indication of an absolute time of the deadline; and receiving the set of PDUs at a time based at least in part on the indication of the deadline. Additionally or alternatively, the application server may perform one or more other operations described herein.

[0055] In some aspects, the term "base station" (e.g., base station 110) or "network node" or "network entity" may refer to a clustered base station, a decomposed base station (e.g., a combined Fig. 9 110 ), integrated access and backhaul (IAB) nodes, relay nodes, and / or one or more components thereof. For example, in some aspects, a "base station", "network node", or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station", "network node", or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station", "network node", or "network entity" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station", "network node", or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station", "network node", or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the terms "base station," "network node," or "network entity" may refer to one of the base station functions but not another. In this manner, a single device may include more than one base station.

[0056] As indicated above, Figure 1 Other examples can be found in the Figure 1 The examples described are different.

[0057] Figure 22 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0058] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0059] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0060] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0061] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0062] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 6 to 13 ) or any aspect of any of the methods described herein.

[0063] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 6 to 13 ) or any aspect of any of the methods described herein.

[0064] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the network node may perform one or more techniques associated with deadline-based data grouping, as described in more detail elsewhere herein. In some aspects, the network node described herein is Figure 2 The base station 110 is shown, is included in the base station 110, or includes one or more components of the base station 110. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.11 Process 11. Fig.12 The process 1200 Fig.13 The process of 1300 Fig.14 1400 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion and / or interpretation), may cause one or more processors, UE 120 and / or base station 110 to perform or direct, for example Fig.11 Process 11. Fig.12 The process 1200 Fig.13 The process of 1300 Fig.14 The process 1400 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0065] In some aspects, the UE includes means for sending an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node; and / or means for receiving the one or more data packets based at least in part on the arrival of the one or more data packets at or before the deadline. The means for the UE to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0066] In some aspects, the network node includes means for receiving an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with data packets for a communication session; and / or means for sending one or more data packets based at least in part on one or more data packets being sent at or before the deadline. In some aspects, means for the network node to perform operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0067] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0068] As indicated above, Figure 2 Other examples can be found in the Figure 2 The examples described are different.

[0069] Figure 3 is a diagram illustrating an example 300 decomposed base station architecture according to the present disclosure.

[0070] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station (BS, e.g., base station 110) or one or more units (or one or more components) performing base station functions can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NR BS, a 5GNB, an access node (AP), a TRP, a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone BS or a monolithic BS) or a decomposed base station.

[0071] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or CUs, one or more DUs, or one or more RUs. In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual centralized unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0072] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an IAB network, an O-RAN (such as a network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0073] Figure 3 The decomposed base station architecture shown may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed base station units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 120 via one or more RF access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0074] Each of these units (e.g., CU 310, DU 330, RU 340), as well as near-RT RIC 325, non-RTRIC 315, and SMO framework 305 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0075] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 310. CU310 may be configured to handle user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). CU 310 may be implemented to communicate with DU 330 as needed for network control and signaling.

[0076] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0077] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split such as a lower layer functional split. In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0078] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 335) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 311 via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0079] The non-RT RIC 315 may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0080] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0081] As indicated above, Figure 3 Other examples can be found in the Figure 3 The examples described are different.

[0082] Figure 4 400 is a diagram illustrating an example of a jitter distribution according to the present disclosure. In some communications, data may be received quasi-periodically. For example, a network (e.g., a network node, such as a core network (CN) network node and / or a RAN network node) may receive data that is generally periodic with an offset from a periodic nominal arrival time 405. The nominal arrival time 405 may be associated with a center of a burst arrival time distribution at a user plane function. The nominal arrival time 405 may have a periodicity based at least in part on a multimedia periodicity associated with the communication (e.g., a refresh rate of a video stream and / or an extended reality (XR) communication, etc.).

[0083] As shown in example 400, some data may be received before a nominal arrival time 405 (e.g., early arrival data), and some data may be received after the nominal arrival time (e.g., late arrival data). In one example, for split XR communication (e.g., where the rendering process is performed by the UE and a network node such as an edge node), the jitter distribution may have a traffic arrival time gap of approximately 10 milliseconds (ms) in the downlink traffic arrival time.

[0084] The data may have jitter (e.g., an offset from a nominal arrival time 405) based at least in part on rendering time, encoder time, and / or Real-time Transport Protocol (RTP) packetization time at a device (e.g., an application server) that generates or forwards the data.

[0085] In some networks, XR downlink traffic may have quasi-periodic bursts (e.g., a collection of data packets associated with one or more scenarios) arriving at the network time. The jitter of the burst arrival time may be equal to about 48% of the XR periodicity (e.g., 8ms vs. 16.666ms). In this way, when using the packet delay budget (PDB) requirement, the jitter highly affects the overall XR system performance in terms of capacity and power consumption.

[0086] The XR client at the UE may have a de-jitter buffer that holds burst packets until the periodic timing for display. In some examples, the PDB requirement may indicate to the UE the expiration of a data packet that may be on time (e.g., where reception is a certain amount of time before the periodic timing for display to allow processing before display). In this case, the network node may discard data packets that could have been used to provide XR data to the UE. This may cause communication errors associated with the XR data, which may consume computing, power, communication, and / or network resources to detect and correct. Additionally or alternatively, communication errors may result in a communication configuration that reduces spectral efficiency based at least in part on the network node's attempt to correct and / or reduce errors.

[0087] As indicated above, Figure 4 Other examples can be found in the Figure 4 The examples described are different.

[0088] Figure 5 is a diagram illustrating an example 500 of a packet delay budget constraint for jitter-based communications in accordance with the present disclosure.

[0089] like Figure 5 As shown, a burst 505A of data packets may be directed to the UE. The burst 505A may be Figure 5510A relative to the nominal arrival time 510A. The nominal arrival time 510A may be associated with a periodic arrival time, and the burst 505A may be offset from the periodic arrival time by a jitter. However, the burst 505A may arrive at the nominal arrival time 510A with zero jitter.

[0090] The network may send a burst 505A, where reception at the UE is Figure 5 The amount of time between arrival at the network and receipt at the UE is latency 515A. The network may determine whether to send burst 505A based at least in part on whether latency 515A exceeds PDB 520A. PDB 520 indicates the amount of time the network can delay burst 505A after arriving at the network and before delivery to the UE. If PDB 520 is exceeded, the network may discard burst 505A and treat the data packets of burst 505A as expired. A PDB may be established for a communication session associated with a UE, and the PDB may be a fixed amount of time from arrival at the network.

[0091] Based at least in part on the latency 515A satisfying the PDB 520A, the network sends the burst 505A to the UE. From the UE's perspective, the UE must receive the burst 505A at or before the de-jitter buffer deadline 525A. The de-jitter buffer deadline 525A may be based at least in part on the display time and the amount of time the UE needs to process the burst 505A before displaying the scene associated with the burst 505A.

[0092] BURST 505B is available in Figure 5 The burst 505B may arrive at the network at a time indicated relative to the nominal arrival time 510B. The burst 505B may arrive before the nominal arrival time 510B, where the jitter 530B has a negative value to indicate an arrival time before the nominal arrival time 510B.

[0093] The network may determine the UE's Figure 5 520B is outside of PDB 520B without sending burst 505B. For example, latency 515B may be greater than PDB 520. Even if expected reception at the UE is before de-jitter buffer deadline 525B associated with burst 505B, the network may discard burst 505B and consider data packets of burst 505B as expired.

[0094] BURST 505C is available in Figure 5 Burst 505C may arrive at the network at a time indicated relative to nominal arrival time 510C. Burst 505C may arrive after nominal arrival time 510C, with jitter 530C having a negative value to indicate an arrival time after nominal arrival time 510C.

[0095] The network may determine the UE's Figure 5 The network may send burst 505B and treat the data packets of burst 505B as timely. However, if the network receives the data packets of burst 505B, the network may receive the data packets of burst 505B in a timely manner. Figure 5 As shown, PDB 520C may extend beyond de-jitter buffer deadline 525C. In this case, the network may send burst 505C after de-jitter buffer deadline 525C based at least in part on PDB 520C indicating that burst 505C is timely. Sending burst 505C when data packets of burst 505C are due and will not be rendered for display by the UE may consume computing, power, communication, and / or network resources.

[0096] In some networks, the network may attempt to prevent the transmission of expired data to save computing, power, communication and / or network resources. In order to prevent the transmission of expired data, the network may configure a PDB with a reduced duration to take into account the jitter of the data. For example, the network may reduce the duration of the PDB to prevent the jittered time amount and the duration of the PDB from extending from the nominal arrival time 510C past the jitter buffer cutoff time 525C. However, reducing the duration of the PDB may result in an increase in the number of discarded packets such as those of the burst 505B, which may have been received at the UE before the nominal arrival time 510B. Additionally or alternatively, the network may reduce the communication capacity to ensure that the PDB is met and packets are not discarded. However, this may reduce the number of devices that can be supported on the cell of the network.

[0097] As indicated above, Figure 5 Other examples can be found in the Figure 5 The examples described are different.

[0098] In some aspects described herein, a communication session may be associated with a deadline (e.g., a de-jitter buffer deadline) for receiving a data packet at a UE. In some aspects, the deadline may replace a PDB that may be configured for a data packet. Based at least in part on the use of the deadline, parameters for determining the expiration of a data packet and / or the prioritization of the transmission of a data packet may reflect the actual timing requirements of the data packet with improved accuracy. In this way, a network node may schedule the transmission of a data packet with improved efficiency without having to prioritize the data packet over other data packets with greater urgency. This may allow a network node to support additional devices in a cell operated by the network node, which may save computing, power, communication, and / or network resources that could otherwise be used to form and / or operate an additional cell for supporting additional devices.

[0099] In some aspects, the UE may determine the timing of the deadline. For example, the UE may determine the deadline (e.g., a de-jitter buffer deadline) based at least in part on a periodic display time (e.g., associated with a refresh rate of multimedia of a communication session) and a device internal data processing time (e.g., 3GPP protocol layer processing time + Internet Protocol (IP) packet processing time + video decoding time, etc.). In some aspects, the UE may use the longest processing time of the estimated device internal data processing times as a conservative estimate of the deadline. Additionally or alternatively, the UE may determine the deadline based at least in part on the periodic display time and an internal periodic timer for initiating video decoding.

[0100] The deadline can be associated with a packet generation timing adjustment (+ / -) of a phase-locked loop at the application layer utilizing the communication session between the application server and the application client at the UE. In this way, at the application layer, the deadline can be set to the nominal PDB + nominal arrival time to minimize motion to rendering photon (M2R2P) latency.

[0101] Figure 6 6 is a diagram of an example 600 associated with data grouping based on a deadline according to the present disclosure. Figure 6 As shown, multiple network nodes may communicate with a UE (e.g., UE 120). The multiple network nodes may include one or more base stations 110, one or more CUs, one or more DUs, one or more RUs, one or more core network nodes, one or more network servers, one or more application servers, and / or one or more access and mobility management functions (AMFs), etc. In some aspects, the UE and the network nodes in the multiple network nodes (e.g., RAN network nodes) may be part of a wireless network (e.g., wireless network 100). The UE and the network nodes may be in a Figure 6 The operations shown are performed after a wireless connection has been established.

[0102] In some aspects (e.g., as part of establishing a wireless connection), a network node may send and a UE may receive configuration information. In some aspects, the UE may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (CEs), and / or downlink control information (DCI), etc. In some aspects, the configuration information may include: an indication of one or more configuration parameters for selection by the UE (e.g., known to the UE and / or previously indicated by the first network node or another network device), and / or explicit configuration information for the UE to configure the UE, etc.

[0103] In some aspects, the configuration information may indicate that the UE is to communicate in a communication session with a deadline instead of a PDB. The configuration information may indicate that the UE is to provide an indication of the deadline and / or traffic mode information to the network node. In some aspects, the configuration information may indicate that the UE is to provide traffic mode information associated with the deadline (e.g., in addition to or in lieu of the deadline for use by the network node in deriving the deadline, etc.). In some aspects, the configuration information may indicate that the UE is to send an indication that a QoS flow of the communication session is associated with the deadline. In some aspects, the configuration information may indicate that the UE is to receive an indication that a QoS flow of the communication session is associated with the deadline.

[0104] The UE may configure itself based at least in part on the configuration information.In some aspects, the UE may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0105] As shown in reference numeral 605, the UE, the network node, the CN network node and / or the application server may establish a QoS flow based on a deadline. For example, the UE, the network node, the CN network node and / or the application server may establish a connection and / or parameters for communicating via a communication session. In some aspects (e.g., as part of establishing a QoS flow), the network node may indicate to the UE that the QoS flow is associated with a deadline and is not associated with a packet delay budget. In some aspects (e.g., as part of establishing a QoS flow), the UE may indicate to the network node that the QoS flow is associated with a deadline and is not associated with a packet delay budget. In some aspects, the CN network node and / or the application server may indicate to the network node that the QoS flow is associated with a deadline, is not associated with a packet delay budget, and / or the expiration of the data packet of the communication session is associated with a deadline and is not associated with a packet delay budget. In some aspects, the network node may (e.g., to the UE) send an indication that the expiration of the data packet of the communication session is associated with a deadline and is not associated with a packet delay budget.

[0106] In some aspects, the cutoff time is based at least in part on the periodic display time and the UE internal data processing time. For example, the cutoff time may be offset from the periodic display time by an amount equal to or greater than the UE internal data processing time. In some aspects, the periodic display time may be associated with the display of a scene of a video feed such as an XR video feed, etc.

[0107] In some aspects, the UE may receive (eg, as part of establishing a QoS flow) an indication of a mapping of the QoS flow to the IP flow. The mapping may be used to convert the IP flow to the QoS flow to indicate that the deadline applies to the QoS flow.

[0108] As shown by reference numeral 610, the UE may receive information indicating a deadline and / or traffic pattern information for a QoS flow from an app client (e.g., an application client of the UE or an application client of a connected device, etc.). In some aspects, the information may indicate a deadline (e.g., a de-jitter buffer deadline), a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, and / or a nominal arrival time, etc., for a data packet of a communication session.

[0109] In some aspects, the UE may identify a burst index for a data packet based at least in part on burst metadata available at an application layer of the data packet and / or a burst index determined based at least in part on a timing of the data packet. In some aspects, the deadline is periodic and the burst index is associated with a timing of the deadline.

[0110] As indicated by reference numeral 615, the UE may convert the deadline to the RAN time domain. For example, the UE may convert the deadline from a time relative to an application associated with the QoS flow or an absolute time to a RAN time domain unit, such as a subframe number and / or a time slot number, etc. In some aspects, the UE may convert the deadline to the RAN time domain including converting the deadline from the application time domain to the RAN time domain based at least in part on: a deadline map associated with a quality of service (QoS) flow, one or more deadline notification messages, and / or one or more data radio bearer (DRB) QoS parameters associated with the deadline, etc. In some aspects, the UE may receive the deadline map, the deadline notification message, and / or the DRB QoS parameters during or after establishing the QoS flow as described in conjunction with reference numeral 605 and / or via an application client, etc.

[0111] As shown by reference numeral 620, the UE may identify the IP flow and / or QoS flow to which the cutoff applies. For example, the UE may be aware of the IP flow associated with the cutoff based at least in part on the communication session and / or data packets being associated with the IP flow via the application client. In some aspects, the UE may use an IP flow to QoS flow mapping to identify the QoS flow with the IP flow. In some aspects, the UE may identify the IP flow to which the cutoff applies based at least in part on an indication of the IP flow via an application layer of the data packet and / or a logical channel identifier determined at least in part based on an IP packet index of the data packet, etc.

[0112] As indicated by reference numeral 625, the UE may send, and the network node may receive, an indication of a cutoff time and / or traffic pattern information (e.g., additional traffic pattern information) and / or an indication that a QoS flow is associated with a cutoff time. In some aspects, the traffic pattern information may include a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session associated with the QoS flow. In some aspects, the cutoff time may include a converted cutoff time (e.g., converted from an application-based time or an absolute time to a RAN time, such as a subframe number and / or a timeslot number, etc.).

[0113] In some aspects, the UE may send additional or alternative information. For example, the UE may send an indication that a QoS flow or logical channel associated with the data packet is associated with the cutoff time, an indication of a burst index associated with the timing of the cutoff time, and / or an indication that a logical channel identifier associated with the data packet is associated with the cutoff time, etc.

[0114] In some aspects, the UE may receive an additional indication that the QoS flow or logical channel is configured with a cutoff time and send an indication that the QoS flow or logical channel associated with the data packet is associated with the cutoff time. For example, the network node may indicate that the QoS flow is a QoS flow based on the cutoff time. In some aspects, the network node may indicate that the network node is informed of the cutoff time based at least in part on receiving traffic pattern information and / or an indication of jitter for the QoS flow from a CN network node, an application server, and / or a UE, etc.

[0115] In some aspects, the UE may send an indication of one or more of a deadline, periodicity, nominal packet delay budget, jitter of burst arrival time, or nominal arrival time for data packets of a communication session via an RRC message, a MAC CE, and / or an application layer indication, etc.

[0116] In some aspects, the UE may send an indication of the cutoff time and / or traffic pattern information to a CU of the network (e.g., a network node or a component of a network node). The CU may forward the cutoff time and / or traffic pattern information to a DU of the network (e.g., a network node or a component of a network node). In some aspects, the CU may use the traffic information to derive the cutoff time and may forward the cutoff time to the DU.

[0117] As indicated by reference numeral 630, the network node may receive, and the CN network node may provide, traffic pattern information and / or an indication of jitter associated with a QoS flow. In some aspects, the traffic pattern information may include periodicity of data packets for a communication session, a nominal packet delay budget, jitter of burst arrival times and / or nominal arrival times, etc. In some aspects, the network node may derive a cutoff time based at least in part on the traffic pattern information and / or jitter.

[0118] In some aspects, the network node may receive the traffic mode information from the CN network node as an alternative to receiving the traffic mode information from the UE. In some aspects, the network node may receive one or more information elements of the traffic mode information from the CN network node and one or more additional information elements of the traffic mode information from the UE.

[0119] In some aspects, the network node may receive an indication of jitter via a user plane header. For example, the network node may receive an indication of jitter in a general packet radio service (GPRS) tunneling protocol user plane (GTP-U) header. In some aspects, the jitter is based at least in part on the actual burst arrival network time and the nominal arrival time associated with the data packet. In this way, the jitter may indicate a deadline opportunity to which the data packet belongs. For example, positive jitter may indicate that the data packet may be approaching the deadline. Alternatively, negative jitter may indicate that the data packet is early and not approaching the deadline (e.g., if the data packet is approaching the deadline, a subsequent opportunity of the deadline is applied to the data packet).

[0120] As indicated by reference numeral 635, the network node may receive the data packet from the application server (eg, via the CN node). In some aspects, the data packet may be associated with a QoS flow and may be addressed to a UE.

[0121] As shown by reference numeral 640, the network node may identify the cut-off time and / or the burst group, and / or may discard the data packet. In some aspects, the network node may identify the cut-off time based at least in part on receiving an indication of the cut-off time or based at least in part on deriving the cut-off time using traffic pattern information received via the UE and / or CN network node, etc. In some aspects, the network node may identify the cut-off time based at least in part on one or more of the periodicity of the data packet, the nominal packet delay budget, the jitter of the burst arrival time, and / or the nominal arrival time. For example, the network node may derive the cut-off time and / or may determine the timing of the cut-off time to be applied to the data packet.

[0122] In some aspects, the network node may identify a deadline opportunity associated with the data packet. For example, the deadline may be periodic such that a data packet received late for a first deadline opportunity may be received before a second deadline opportunity. The network node may first identify which deadline opportunity applies to the data packet, and then determine whether the data packet is timely (e.g., meets the deadline).

[0123] In some aspects, the network node may discard data packets based at least in part on failure to meet the deadline.For example, the network node may discard data packets that the network node cannot schedule for transmission to the UE before or at the deadline.

[0124] In some aspects, a network node may identify a deadline to apply to the data packets based at least in part on a burst group of the data packets. For example, a network node may group the data packets into burst groups based at least in part on a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or an indication of a nominal arrival time for the data packets of a communication session. For example, a network node may group the data packets into groups associated with a deadline based at least in part on receiving the data packets within a threshold amount of time from the nominal arrival time and / or one or more deadlines (e.g., a previous deadline, a deadline, and / or a subsequent deadline).

[0125] As shown by reference numeral 645, the UE may receive and the network node may send an indication of downlink resources for receiving data packets for the QoS flow, an indication of acceptance of the cutoff time, and / or an indication of the QoS or logical channel identification (LCID) associated with the cutoff time. In some aspects, the downlink resources may be based at least in part on an indication of the cutoff time, periodicity, nominal packet delay budget, jitter of burst arrival time, and / or nominal arrival time for the data packets of the communication session. For example, the network node may schedule downlink resources to meet the cutoff time. In this way, the network node may prioritize the data packets appropriately while allowing the sending of additional data packets that may have greater urgency.

[0126] In some aspects, a network node may send an indication that the network node accepts a deadline and / or one or more business pattern information elements, such as periodicity of data packets for a communication session, a nominal packet delay budget, jitter of burst arrival times, or a nominal arrival time.

[0127] In some aspects, the network node may indicate to the UE that a QoS flow or logical channel associated with the data packet is associated with a cutoff time; an indication of a burst index associated with the timing of the cutoff time; and / or an indication that an LCID associated with the data packet is associated with the cutoff time.

[0128] In some aspects, the network node may send an additional indication that the QoS flow or logical channel associated with the data packet is configured with a cutoff time based at least in part on receiving an indication that the QoS flow or logical channel is associated with a cutoff time. For example, the network node may confirm that the QoS flow is configured to use a cutoff time based at least in part on receiving an indication that the QoS flow is associated with a cutoff time (e.g., from a UE, an application server, and / or a CN network node, etc.).

[0129] In some aspects, in preparing and / or when determining to send a data packet, a network node may identify a QoS associated with the data packet, apply a cutoff time to the data packet based at least in part on the QoS flow being associated with the cutoff time, and / or apply periodic timing of the cutoff time to the data packet based at least in part on a time at which the network node receives the data packet or an indication of a burst number of data packets.

[0130] As indicated by reference numeral 650, the UE may receive, and the network node may send, data packets for the QoS flow. In some aspects, the UE may receive, and the network node may send, the data packets based at least in part on a reception time and / or an expected reception time of the data packets meeting a deadline (e.g., at or before the deadline).

[0131] Based at least in part on the use of the deadline, parameters used to determine the expiration of data packets and / or the prioritization of the transmission of data packets can reflect the actual timing requirements of the data packets with improved accuracy. In this way, the network node can schedule the transmission of data packets with improved efficiency without having to prioritize data packets over other data packets with greater urgency. This can allow the network node to support additional devices in a cell operated by the network node, which can save computing, power, communication and / or network resources that could otherwise be used to form and / or operate additional cells for supporting the additional devices.

[0132] As indicated above, Figure 6 Other examples can be found in the Figure 6 The examples described are different.

[0133] Figure 7 is a diagram of an example 700 associated with deadline-based data grouping according to the present disclosure. Figure 7 As shown, a UE (e.g., UE 120) may communicate with a network (e.g., with one or more network nodes of the network). The network may include one or more base stations 110, one or more CUs, one or more DUs, one or more RUs, one or more core network nodes, one or more network servers, one or more application servers and / or one or more AMFs, etc. In some aspects, the UE and the network nodes in the plurality of network nodes (e.g., RAN network nodes) may be part of a wireless network (e.g., wireless network 100). The UE and the network nodes may be in a Figure 7 The operations shown are performed after a wireless connection has been established.

[0134] like Figure 7 As shown, a burst 705A of data packets may be directed to the UE. The burst 705A may be Figure 7710A relative to the nominal arrival time 710A. The nominal arrival time 710A may be associated with a periodic arrival time from which the burst 705A may be offset by a jitter. However, the burst 705A may arrive at the nominal arrival time 710A with zero jitter.

[0135] The network may send a burst 705A, where reception at the UE is Figure 7 The amount of time between arrival at the network and reception at the UE is latency 715A. Nominal PDB 720A may be the amount of time between nominal arrival time 710 and de-jitter buffer deadline 725A before or during which the network node may send burst 705A to the UE without failing to meet de-jitter buffer deadline 725A.

[0136] The network may determine whether to send burst 705A based at least in part on whether the network node can send burst 705A so that the UE receives burst 705A at or before de-jitter buffer deadline 725A. If de-jitter buffer deadline 725A is missed, the network may discard burst 705A and regard the data packets of burst 705A as expired.

[0137] Based at least in part on the latency 715A satisfying the de-jitter buffer deadline 725A, the network sends the burst 705A to the UE. From the UE's perspective, the UE must receive the burst 705A at or before the de-jitter buffer deadline 725A. In this manner, the same deadline (e.g., the de-jitter buffer deadline 725A) is applied to the data packets at the network and at the UE. The de-jitter buffer deadline 725A may be based at least in part on the display time and the amount of time the UE needs to process the burst 705A before displaying the scene associated with the burst 705A.

[0138] BURST 705B is available in Figure 7 The burst 705B may arrive at the network at a time indicated relative to the nominal arrival time 710B. The burst 705B may arrive before the nominal arrival time 710B, where the jitter 730B has a negative value to indicate an arrival time before the nominal arrival time 710B.

[0139] The network may determine the UE's Figure 7 The expected reception at the indicated time sends burst 705B at or before de-jitter buffer deadline 725B and / or nominal PDB 720B. For example, even if latency 715B is greater than nominal PDB 720B, latency 715B may not control whether the network node sends the data packet.

[0140] BURST 705C is available in Figure 7 The burst 705C may arrive at the network at a time indicated relative to the nominal arrival time 710C. The burst 705C may arrive after the nominal arrival time 710C, where the jitter 730C has a negative value to indicate an arrival time after the nominal arrival time 710C.

[0141] The network may determine the UE's Figure 7 The expected reception at the indicated time sends the burst 705C at or before the de-jitter buffer deadline 725C and / or the nominal PDB 720C. In some aspects, the network node may send the burst 705C with a relatively short latency 715C to meet the de-jitter buffer deadline 725C. For example, the network node may prioritize the burst 705C to send the burst 705C at or before the de-jitter buffer deadline 725C.

[0142] The nominal arrival time 710 is associated with a periodicity 735. The periodicity 735 may be based at least in part on an application associated with the data packet. For example, the periodicity 735 may be associated with a refresh rate of a video feed.

[0143] As indicated above, Figure 7 Other examples can be found in the Figure 7 The examples described are different.

[0144] Figure 8 is a diagram of an example 800 associated with deadline-based data grouping according to the present disclosure. Figure 8 As shown, multiple network nodes may communicate with a UE (e.g., UE 120). The multiple network nodes may include one or more base stations 110, one or more CUs, one or more DUs, one or more RUs, one or more core network nodes, one or more network servers, one or more application servers, and / or one or more AMFs, etc. In some aspects, the UE and the network nodes in the multiple network nodes (e.g., RAN network nodes) may be part of a wireless network (e.g., wireless network 100). The UE and the network nodes may be in a Figure 8 The operations shown are performed after a wireless connection has been established.

[0145] As shown by reference numeral 805, a CN network node may establish a QoS flow based on a deadline. For example, a CN network node (e.g., a 5G core network) may set up a new "QoS flow with a deadline" in a PDU session. A QoS flow may define a deadline instead of a PDB.

[0146] For QoS flows with a cutoff time, the UE may define its own cutoff time by indicating the timing to the network node, or the cutoff time may eventually converge to the nominal arrival time + nominal PDB. In some aspects, the 5G QoS flow table may include a new information element indicating a packet delivery requirement of "cutoff time" instead of "PDB". For example, the cutoff time may be defined using PDU set design parameters such as PSDB (e.g., application data unit (ADU) delay budget (ADB)) and / or PDU set error rate (PSER) (e.g., ADU error rate (AER)).

[0147] In some aspects, the CN network node may decide which IP flow to set for a QoS flow with a deadline (e.g., using a policy control function (PCF) / session management function (SMF)). In some aspects, the CN network node may indicate to the network node during PDU session establishment which QoS flow to set for the deadline. In some aspects, the CN network node may utilize a non-access stratum (NAS) message to indicate to the UE which QoS flow to set for the deadline. Additionally or alternatively, the network node may utilize an RRC message to indicate to the UE which LCID to set for the deadline.

[0148] In some aspects, relevant information elements in the communication standard can be extended. For example, [CN to NAS] N11 / N2 interface + F1 / E1 interface (e.g., PDU session-QoS parameters); [CN to UE] NAS message (e.g., indicating QoS flow for deadline); and / or [gNB to UE] RRC message (e.g., indicating LCID for deadline).

[0149] As indicated by reference numeral 810, the application client may provide, and the UE may receive, information indicating a deadline. In some aspects, the application client may provide information indicating a deadline using an application layer indication (eg, an X-layer application programming interface (API)).

[0150] In some aspects, in example 800, the UE and / or application client may not need to indicate a burst index and / or a PDU set index.

[0151] In some aspects, the application layer utilizes a Layer X API to indicate a deadline for an IP flow to a modem of a UE (eg, to translate an application deadline into a deadline understood by a network node).

[0152] The application client may indicate a specific timing of the UE internal clock for the deadline. The application client calculates the deadline based on the de-jitter buffer timing and converts the deadline to the UE clock timing. The clocks of the UE's modem and the application client may be different, so the application client may need to map (e.g., continuously or periodically) the UE clock timing and the application timing to compensate for clock drift.

[0153] The application client may indicate the burst index (or PDU set index) and / or the internal IP packet index to the UE. For example, the application client may indicate which burst index is associated with the deadline. If the burst metadata (or PDU set metadata) is available at the application layer, the application client may explicitly indicate the burst index to the UE. If the burst metadata is not available at the application layer, the application client may provide the IP packet index of the deadline, which may be assumed internally between the UE and the application client, and the UE may convert the IP packet index into a burst index (or PDU set index). The Uu interface may be used to provide the burst metadata (or PDU set metadata) index to the UE, and the UE may need to maintain mapping information between the burst index (or PDU set index) and the IP packet index.

[0154] The application client may provide an indication of an IP flow or an internal IP packet index. For example, the application layer may indicate which IP flow (e.g., IP 5-tuple) is associated with the deadline. In another example, the application layer may provide an IP packet index, and the UE may convert the IP packet index into an associated LCID.

[0155] The application client may indicate the traffic pattern and requirements. In some aspects, instead of eTSCAI (application server to network node), the application server may indicate the traffic pattern and requirements (e.g., periodicity, nominal PDB, nominal arrival time, etc.) to the application client, and the UE transmits all information related to the deadline to the network node.

[0156] As indicated by reference numeral 815, the UE may convert the deadline into the RAN time domain. In some aspects, the UE may convert the deadline using a deadline mapping with a QoS flow (e.g., an X-layer API). In some aspects, the UE may use a deadline notification message (e.g., a 3GPP-RRC message). In some aspects, the UE may use a DRB QoS parameter for the deadline (e.g., a deadline key performance indicator (KPI)).

[0157] In some aspects, the application layer does not know the information of the QoS flow, so the UE may need to provide an indication of the QoS flow to the network node. In some aspects, NAS messages are used to provide the UE with packet filters for the uplink direction, but the UE may not know the packet filters for the downlink direction. In some aspects, the network (e.g., a CN network node) may use NAS messages (mapping relationship between IP flows and QoS flows) to provide the UE with information on uplink and downlink packet filters. In some aspects, the network may indicate a packet filter with a service flow template (TFT) or a service data flow (SDF) template. For example, the network may indicate a packet filter that is typically composed of an IP 5-tuple = {source IP, destination IP, source port, destination port, protocol ID}. Based at least in part on the DL TFT, the UE converts the IP flow into a QoS flow.

[0158] As shown by reference numeral 820, the UE may send, and the network node may receive, an indication of a deadline and / or traffic pattern information. In some aspects, the UE may send the indication of the deadline and / or traffic pattern information via an RRC message. For example, the UE may send a message with information elements indicating the deadline notification: a deadline, a burst index, and / or a QoS flow or LCID.

[0159] In some aspects, the UE may have multiple flows, so the UE may need to specify which QoS flow has a cutoff time. In some aspects, for QoS mapping in the downlink direction, the CN SMF (NAS level) may use IP flow to QoS flow (packet filter, TFT) to indicate the mapping, the network node may use the SDAP layer (access stratum (AS) level) to indicate the QoS flow to DRB (n:1 mapping), and / or the network node may use the RLC layer to indicate DRB to LCID (1:1 mapping).

[0160] In some aspects, the UE may use a MAC CE command or an RRC message to indicate a deadline for a burst (or PDU set) to the network node. For example, for a MAC CE command, the deadline is directly related to the scheduling of the MAC layer (e.g., scheduling based on the deadline). Using the RRC message, the network node may utilize the RRC protocol to negotiate the timing of the deadline between the UE and the network node.

[0161] In some aspects, an indication of a deadline for a burst (e.g., a PDU set) may include one or more protocol information elements. For example, the indication may include a deadline (e.g., converted to a 5G system clock), a burst index (PDU set index), and / or a QoS flow or LCID. The deadline indication may indicate a specific timing of the deadline in the RAN system clock. For example, the UE converts the deadline timing indicated by the application client in the UE internal clock to the RAN system clock. For this conversion, the UE may require time synchronization between the application client and the UE. In some aspects, the time in the RAN system clock may include a subframe number (SFN) (e.g., the latest bit or partial bit), a subframe index (e.g., 10 bits, ms), and / or a time slot index. Additionally or alternatively, the time in the RAN system clock may include a SFN reference time (e.g., the latest bit or partial bit), a time difference between the SFN reference time and the deadline (e.g., ms or microseconds).

[0162] The indication of the burst index (or PDU set index) may indicate which burst (or PDU set) has a specific timing of the deadline. If the application layer does not have an explicit burst index, the UE may convert the IP packet index into a burst index (or PDU set index).

[0163] The indication of a QoS flow or LCID may include the UE indicating which QoS flow has a cut-off time. For example, the UE may convert an IP flow indicated by an application client into a QoS flow. Additionally or alternatively, the UE may indicate which LCID has a cut-off time. In this way, the RAN may handle the cut-off time without any information from upper layers. However, all QoS flows in an LCID may have the same cut-off time requirement.

[0164] In some aspects, the network node may respond to the indication of the cutoff time and / or traffic pattern information with an indication of acceptance or rejection.In some aspects, the cutoff time provided by the individual UE may not be acceptable at the network node side, so the network node may negotiate the cutoff time with the UE.

[0165] If the deadline is not acceptable at the network node side, the network node may transmit a rejection message to the UE. In some aspects, the network node may provide the negotiated deadline to the UE. Additionally or alternatively, if the deadline is rejected, the UE may need to adjust the display timing based at least in part on the updated deadline.

[0166] In some aspects, the UE may send an indication of a deadline and / or a business mode to a CU (e.g., a network node or a component of a network node). The CU may provide an indication of a deadline and / or a business mode to the DU. In some aspects, the CU may indicate the deadline using a new DRB QoS parameter via the F1 interface (CU to DU). For example, the DU may indicate the use of an information flow to provide an indication, such as a UE context to a DRB to a QoS flow-level QoS parameter to a dynamic 5G QoS identifier (5QI) descriptor. In some aspects, the CU may utilize a dynamic descriptor to specify a deadline timing to the DU. In some aspects, the CU may mark the QoS flow as associated with a deadline and indicate the deadline timing. In some aspects, the DU may transmit an acceptance or rejection message back to the CU.

[0167] As indicated by reference numeral 825, the network node may receive traffic mode information from the application server. For example, the network node may receive periodic and / or nominal PDBs from the application server. In some aspects, the network node may use enhanced TSCAI to provide the nominal PDB and periodicity to the network node (e.g., to provide application functionality to the network node). Alternatively, the UE may provide all traffic mode information to the network node.

[0168] In some aspects, the network node may determine the burst of data packets using implicit burst packet grouping for a deadline (e.g., for a deadline KPI). In some aspects, the network node may need to identify which IP packets belong to the nth burst (or PDU set). The UE may check the QoS flow of the packets so that the deadline is applied only to the relevant QoS flow. Based at least in part on the burst timing information (deadline, nominal PDB, periodicity), the network node may identify packets delivered within the following time period as part of the nth burst:

[0169] nth cutoff time - nominal PDB + n*periodicity + / -periodicity / 2

[0170] The Nth burst packet may need to be delivered within the nth deadline. For example, for the CN UPF solution, the CN UPF (e.g., CN network node) uses the UPF to mark the burst packet. The CN UPF identifies the burst packet based at least in part on the packet arrival timing to the UPF, and the CN UPF marks the burst in the GTP-U header. The CN UPF indicates the burst packet to the network node CU via the N3 interface (e.g., using the GTP-U header). The network node CU indicates the burst packet to the network node DU via the F1-U interface (e.g., using the GTP-U header).

[0171] In some aspects, the network node may use PDCP to mark burst packets. The network node DU may identify burst packets based at least in part on packet arrival timing to the network node CU, and the DU or CU may mark the burst in the GTP-U header. The network node CU indicates the burst packets to the network node DU via the F1-U interface (e.g., using the GTP-U header).

[0172] In some aspects, the network node DU may self-identify burst packets using a MAC layer indication. The network node DU self-identifies burst packets based at least in part on packet arrival timing to the network node DU. The LCID indicates which packet flows are associated with a deadline.

[0173] As shown by reference numeral 830, the UE may receive and the network node may send an indication of downlink resources for receiving data packets of the QoS flow. In some aspects, the network node may schedule services (e.g., XR services) for the data packets based at least in part on the cutoff time. In some aspects, the network node may perform implicit burst packet grouping. For example, the network node may group the data packets into bursts based at least in part on the cutoff time, the nominal PDB, and / or the periodicity (e.g., the cutoff time-nominal PDB+n*periodicity+ / -periodicity / 2).

[0174] In some aspects, the network node may schedule data packets arriving during [deadline-nominal PDB+n*periodicity+ / -periodicity / 2] to be sent before the deadline+n*periodicity. In some aspects, the network node may use [3GPP-burst grouping] to implicitly group bursts of data packets for the deadline KPI (e.g., implicit burst grouping). In some aspects, data packets delivered within a periodicity are assumed to be a burst packet set.

[0175] As indicated above, Figure 8 Other examples can be found in the Figure 8 The examples described are different.

[0176] Fig. 9 is a diagram of an example 900 associated with deadline-based data grouping according to the present disclosure. Fig. 9 As shown, multiple network nodes may communicate with a UE (e.g., UE 120). The multiple network nodes may include one or more base stations 110, one or more CUs, one or more DUs, one or more RUs, one or more core network nodes, one or more network servers, one or more application servers, and / or one or more AMFs, etc. In some aspects, the UE and the network nodes in the multiple network nodes (e.g., RAN network nodes) may be part of a wireless network (e.g., wireless network 100). The UE and the network nodes may be in a Fig. 9 The operations shown are performed after a wireless connection has been established.

[0177] As shown in reference numeral 905, the CN network node and the network node may establish a QoS flow based on a deadline. For example, the CN network node (e.g., 5G core network) may set up a new "QoS flow with a deadline" in a PDU session. The QoS flow may define a deadline instead of a PDB.

[0178] For QoS flows with a cutoff time, the UE may define its own cutoff time by indicating the timing to the network node, or the cutoff time may eventually converge to the nominal arrival time + nominal PDB. In some aspects, the 5G QoS flow table may include a new information element indicating a packet delivery requirement of "cutoff time" instead of "PDB". For example, the cutoff time may be defined using PDU set design parameters such as ADB and AER.

[0179] In some aspects, the CN network node may decide which IP flow to set for a QoS flow with a deadline (e.g., using PCF / SMF). In some aspects, the CN network node may indicate to the network node during PDU session establishment which QoS flow to set for the deadline. In some aspects, the CN network node may utilize NAS messages to indicate to the UE which QoS flow to set for the deadline. Additionally or alternatively, the network node may utilize RRC messages to indicate to the UE which LCID to set for the deadline.

[0180] In some aspects, relevant information elements in the communication standard can be extended. For example, CN to NAS N11 / N2 interface and F1 / E1 interface (e.g., for PDU session with QoS parameters); CN to UE NAS message (e.g., for indicating QoS flow for deadline); and / or network node to UE RRC message (e.g., for indicating LCID for deadline).

[0181] As shown by reference numeral 910, the CN network node may receive business mode information from an application server. For example, an application function of the application server may provide XR business mode information (e.g., periodicity, nominal PDB, nominal arrival time) to the CN network node. The application server may provide the XR business mode information using an Nx interface for sending enhanced TSCAI or another message. Alternatively, the UE may provide the information to the network node. In some aspects, the CN network node and the network node may need to be synchronized to determine the deadline using the nominal arrival time.

[0182] As shown by reference numeral 915, the network node may receive an indication of jitter for the QoS flow. In some aspects, the CN network node (e.g., using a user plane function) may use metadata of the burst in the N3 / F1 interface to mark the jitter in the GTP-U header. For example, the GTP-U header may indicate jitter of the burst arrival time. In some aspects, the CN network node (e.g., UPF) may mark the jitter of the burst arrival time for each burst in the GTP-U header.

[0183] In some aspects, the CN UPF calculates the jitter of the burst arrival time and uses the jitter to mark the GTP-U header. In some aspects, the jitter of the burst arrival time = the actual burst arrival time - the nominal arrival time. The CN UPF can indicate the jitter of the burst arrival time to the network node CU via the N3 interface. The network node CU can indicate the jitter information to the network node DU via the F1 interface.

[0184] The indication may be a new information element "Jitter of Burst Arrival Time" in the GTP-U header (N3 / F1 interface). The CNUPF may provide the network node with the jitter of the burst arrival time of the current burst (or PDU set). In order to reduce the amount of information bits, the jitter may be digitized (e.g., mean square error (MSB) of the jitter amount). The GTP-U may be extended to employ an indication of a burst or PDU set (e.g., burst index, PDU set index), and the jitter information may be added on top of the indication of the burst or PDU set.

[0185] In some aspects, the application server and the CN network node (eg, CN UPF) may need to be time synchronized to calculate jitter.

[0186] As indicated by reference numeral 920, the UE may receive, and the network node may send, an indication of downlink resources for receiving data packets for the QoS flow. In some aspects, the network node may use implicit burst packet grouping to correlate bursts with deadlines and / or timing of deadlines.

[0187] In some aspects, the network node may schedule downlink resources based at least in part on a cutoff time associated with a data packet. For example, a data packet arriving during [cutoff time - nominal PDB + n*periodicity + -periodicity / 2] should be delivered before the cutoff time + n*periodicity. Additionally or alternatively, the network node may perform implicit burst packet grouping based at least in part on the arrival time of the data packets.

[0188] As indicated above, Fig. 9 Other examples can be found in the Fig. 9 The examples described are different.

[0189] In some aspects, the network may be configured to use a nominal PSDB to identify a deadline for transmission of a set of PDUs. For example, the network may configure a nominal PSDB (e.g., a nominal PDB for a set of PDUs) for a flow (e.g., a data flow and / or a QoS flow, etc.). The nominal PSDB may be a reference delay budget associated with the flow. For example, the nominal PSDB may indicate a delay budget for a set of PDUs, where the delay is measured from the nominal arrival time to arrival at the UE.

[0190] In some aspects, the application server may indicate a jitter of the PDU set along with the PDU set. For example, the application server may indicate the jitter within a header (e.g., an application layer header or an RTP header, etc.). In some aspects, the application server may determine a deadline for sending the PDU set based at least in part on an offset from a nominal PSDB, wherein the offset is based at least in part on the jitter of the PDU set.

[0191] In some aspects, the network node may receive (eg, from an application server and / or additional network nodes such as a CN network node, etc.) an indication of a particular value for the nominal PSDB including any offset from jitter.

[0192] In some aspects, the application server may explicitly indicate jitter of generation time (e.g., PDU set generation and / or burst generation) within metadata of the PDU set. For example, the application server may indicate jitter in a PDU set header, such as an application layer header of the PDU set. The jitter of generation time may be based at least in part on rendering time, encoder time, and / or RTP packetization time. Based at least in part on the application server indicating jitter, the application server, the CN network node (e.g., a user plane function (UPF) entity), and / or the network node do not need to be time synchronized to communicate the deadline for transmission. Additionally or alternatively, the network node may not need to obtain flow service pattern information associated with the PDU set, such as periodicity or arrival time.

[0193] When scheduling a PDU set for transmission, the network node may take into account jitter and the nominal PSDB. For example, the UE may set a deadline for transmission using a dynamic PSDB based at least in part on the nominal PSDB plus an offset (e.g., positive or negative) based at least in part on the jitter of the PDU set.

[0194] In some aspects, a CN network node may set up a QoS flow using a nominal PSDB in a PDU session. For example, a CN network node may set up a new QoS identifier (QI) to define a nominal PSDB to replace a legacy PDB. In some aspects, a CN network node may set a non-dynamic QI to a representative value of a nominal PSDB predefined in a QoS flow table. In some aspects, a CN network node may provide a dynamic QI with a specific value of a nominal PSDB that takes into account jitter for a specific set of PDUs.

[0195] In some aspects, the application server provides an indication of jitter in the PDU aggregate header. The application server may attempt to set a nominal arrival time (e.g., based at least in part on the time at which the PDU aggregate is sent to the network) with an offset from a deadline (e.g., a de-jitter buffer deadline) that is equal to or greater than a nominal PDB (e.g., a nominal PSDB).

[0196] The network node may take into account (e.g., take into account) the jitter indicated in the PDU set header and the nominal PSDB when scheduling the PDU set. For example, the network node may use MAC scheduling with a dynamic PSDB determined as the difference between the nominal PSDB and the jitter of the PDU set. The network node may schedule the PDU set (e.g., XR service) based at least in part on the dynamic PSDB. In some aspects, the deadline for sending the PDU set is associated with the end of the dynamic PSDB.

[0197] In some aspects, the application server may indicate jitter (e.g., dynamic jitter) in a PDU aggregate header (e.g., using the RTP protocol). The application server may provide the jitter of the PDU aggregate directly in the PDU aggregate header. In order to improve latency, the application server and / or the network node (e.g., a CN network node) may set the deadline for the transmission of the PDU to the nominal arrival time plus the nominal PDB (e.g., nominal PSDB). In some aspects, the application server may indicate jitter in a GTP-U header. For example, the UPF may use a GTP-U (e.g., enhanced GTP-U) header to relay the jitter and / or other information of the PDU aggregate to the network node via the N1 and / or F1 interface.

[0198] In some aspects, when establishing a flow with a nominal PSDB, the network node may be configured to take into account the dynamic jitter of the PDU set. For example, the network node may be configured to take into account the jitter indicated in the application layer header of the PDU set based at least in part on the CN network node indicating to the network node that the field for the PDB is used to indicate the nominal PSDB. The PCF and / or SMF may provide an indication of the use of the PSDB to the AMF, which may provide the indication to the access node (AN), which may provide the indication to the network node (e.g., RAN network node) CU (e.g., via the N11 / N2 interface). The network node CU may, for example, provide the indication to the network node DU (via the F1 interface). In this way, the network node DU may know which QoS flow associated with the network node DU has a nominal PSDB.

[0199] In some aspects, the CN network node may identify the maximum jitter allowed for a QoS flow with a nominal PSDB. In some aspects, an application server is not allowed to provide jitter having a value (e.g., in a negative or positive direction) that exceeds the maximum allowed jitter. In some aspects, if the dynamic jitter provided by the application server provides more than the maximum allowed jitter, the network node may truncate the dynamic jitter to the maximum jitter. In some aspects, the CN network node may indicate the maximum allowed jitter to the application server and / or the network node.

[0200] In some aspects, if jitter is not provided with the PDU set (e.g., in a header or other metadata), the network node and / or the CN network node may apply a default value for the jitter. For example, the network node and / or the CN network node may apply a zero value or a maximum allowed jitter as the value for the jitter. In some aspects, the network node may be configured with a default value and / or a parameter for selecting a default value (e.g., an indication of selecting a maximum allowed jitter, etc.).

[0201] In some aspects, the application server may indicate (e.g., in metadata, header, and / or application layer, etc.) a delay budget (e.g., a dynamic PSDB) for a PDU set. For example, the server may provide an absolute time before which the PDU set should be delivered. The absolute time may be indicated as a reference time (e.g., a ReferenceTime information element) that is set to days, seconds, milliseconds (ms), etc. The PDU set should be delivered before the reference time. In these examples, the application server may need to synchronize time with the network node and / or the CN network node.

[0202] In some aspects, the application server may provide a deadline as a delay budget time before which a PDU set should be delivered. For example, the application server may indicate an amount of time (e.g., 10 ms) as the PSDB. In these examples, the application server does not need to be time synchronized with the network node and / or the CN network node.

[0203] In some aspects, the application layer header (e.g., RTP header and / or GTP-U header) includes a jitter value. In some aspects, the application server may add jitter to each PDU aggregate header. In order to reduce the overhead of jitter in the PDU aggregate header, the jitter value may be quantized (e.g., digitized) to a specific granularity level. Additionally or alternatively, in order to reduce the overhead of jitter in the PDU aggregate header, the jitter value may be referenced from a table or other data storage structure with a range of jitter values. When the connection is being established, or after the session is established, the application server and the CN network node may negotiate a bit mapping method for jitter.

[0204] In some aspects, the application server may dynamically update the PSDB of a PDU set based at least in part on updates to jitter in packet generation time, de-jitter buffer status of an application client of an associated UE (e.g., changes in the amount of data in the buffer and / or changes in the PSDB margin), and / or shifts in packet generation time according to a phase-locked loop at the application layer, and the like.

[0205] In some aspects, a UPF (e.g., a CN UPF) may relay the jitter of a PDU set to a network node (e.g., a RAN network node). The UPF may read the jitter of the PDU set from the RTP header and convert the indication of the jitter to a network protocol indication, such as a GTP-U header. The UPF may indicate the jitter of the PDU set to the network node CU via the N3 interface. The network node CU may relay the jitter of the PDU set to the network node DU via the F1 interface.

[0206] In some aspects, the GTP-U header of the N3 and F1 interfaces may be enhanced to include jitter information. For example, the GTP-U header may include a new information element for the jitter of a PDU set (e.g., for an N3 / F1 interface, etc.). The UPF may provide the jitter of a PDU set (e.g., a current PDU set) to the network node. In order to reduce the information bits of the GTP-U header, the jitter may be quantized (e.g., digitized) by a certain step size (e.g., the most significant bit of the jitter amount), or may be mapped by a table.

[0207] Based at least in part on an indication of a deadline for sending a set of PDUs received by the network node from an associated application server (wherein the indication of the deadline includes an indication of jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter of the set of PDUs and a nominal PSDB, and / or an indication of an absolute time for the deadline), the network node may send the set of PDUs according to the deadline. In some examples, the indication of the deadline including an indication of jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter of the set of PDUs and a nominal PSDB, and / or an indication of an absolute time for the deadline may permit the network node to send the set of PDUs according to the deadline without requiring synchronization between the server and the client and / or without requiring information about the business mode (e.g., XR business mode, periodicity, nominal arrival time, etc.). Additionally or alternatively, this may allow the network node to support additional devices in a cell operated by the network node, which may improve the efficiency of the cell and save computational, power, communication, and / or network resources that would otherwise be used to form and / or operate additional cells to support additional devices. For example, based at least in part on using the indication of the deadline, the network node can schedule the transmission of the PDU aggregate without necessarily prioritizing data packets over other data packets with greater urgency. By avoiding unnecessarily prioritizing data packets, the network node can support additional devices based at least in part on scheduling flexibility (e.g., rather than using a strict delay budget), which can provide the network node with a larger timing window for transmitting the PDU aggregate and transmitting communications for the additional devices.

[0208] Fig.10 is a diagram of an example 1000 associated with deadline-based data grouping according to the present disclosure. Fig.10 As shown, multiple network nodes may communicate with a UE (e.g., UE 120). The multiple network nodes may include one or more base stations 110, one or more CUs, one or more DUs, one or more RUs, one or more core network nodes, one or more network servers, one or more application servers, and / or one or more AMFs, etc. In some aspects, the UE and the network nodes in the multiple network nodes (e.g., RAN network nodes) may be part of a wireless network (e.g., wireless network 100). The UE and the network nodes may be in a Fig.10 The operations shown are performed after a wireless connection has been established.

[0209] As shown by reference numeral 1005, the application server, CN network node, network node, UE, and application client of the UE may establish a QoS flow with a nominal PSDB and / or one or more jitter parameters. For example, a CN network node (e.g., a 5G core network) may set a new "QoS flow nominal PSDB" in a PDU session. A QoS flow may indicate a nominal PSDB instead of a PDB.

[0210] In some aspects, the application server and / or the CN network node may define one or more of the jitter parameters. For example, the CN network node may define a maximum allowed jitter. The maximum allowed jitter may be for a specific stream or for all streams with a nominal PSDB. The CN network node may provide an indication of the maximum allowed jitter associated with the QoS stream to the network node and / or to the application server. In some aspects, the CN network node and / or the application server may define a default value for jitter (e.g., for use when jitter is not indicated with the PDU), a quantization of the indication of jitter (e.g., the allowed granularity of the jitter length that can be indicated), and / or a mapping of field values ​​(e.g., in metadata, headers, and / or other parts of a PDU set) to the value of jitter.

[0211] In some aspects, the CN, the network node, and the application server may perform time synchronization to obtain synchronized timing. In this manner, the application server may provide an indication of an absolute time of the deadline, wherein the absolute time of the deadline is based at least in part on the synchronized timing.

[0212] As indicated by reference numeral 1010, the CN network node may receive and the application server may provide a PDU set including an indication of jitter for the PDU set. In some aspects, the indication of jitter for the PDU set may be included in metadata of the PDU set, a header of the PDU set, a GTP-U header or an RTP protocol header of the PDU set, and the like.

[0213] In some aspects, the application server may indicate jitter and / or a nominal PSDB for a PDU set so that a deadline is indicated to the network node and / or the CN network node. The deadline may be based at least in part on jitter of a packet generation time of the PDU set at the application server, a de-jitter buffer state of an application client associated with the PDU set (e.g., at a UE), and / or a packet generation time shift associated with a phase-locked loop at an application layer associated with the PDU set, and the like.

[0214] The CN network node may convert the indication of jitter into a network protocol indication, as indicated by reference numeral 1015. For example, the CN network node may receive the indication of jitter in an RTP header and may convert the indication of jitter into a GTP-U header for forwarding to the network node.

[0215] As indicated by reference numeral 1020, the network node may receive and the CN network node may provide a PDU set and / or an indication of a deadline for the PDU set. In this manner, the network node may receive an indication of a deadline for the PDU set from an application server via the CN network node.

[0216] In some aspects, the indication of a deadline for a PDU comprises an indication of a jitter for a set of PDUs, an indication of a packet delay budget based at least in part on the jitter for a set of PDUs and a nominal PSDB, or an indication of an absolute time for the deadline, among other things.

[0217] As shown by reference numeral 1025, the network node may determine a deadline for transmission of a set of PDUs. In some aspects, the network node may determine the deadline based at least in part on an indication of jitter and a nominal PSDB. For example, the network node may determine the deadline based on the nominal PSDB plus an offset based at least in part on the jitter. In the case of a negative value of jitter, the deadline may be offset from the nominal PSDB by increasing the nominal PSDB. In the case of a positive value of jitter, the deadline may be offset from the nominal PSDB by decreasing the nominal PSDB.

[0218] In some aspects, the deadline for sending the PDU set is based at least in part on the maximum allowed jitter and the nominal PSDB. For example, the application server may provide an indication of the jitter of the PDU set, where the jitter exceeds the maximum allowed jitter. The network node may determine the deadline using the maximum allowed jitter instead of the jitter as indicated by the application server.

[0219] In some aspects, the deadline for sending the PDU set is based at least in part on a default value for jitter and a nominal PSDB. For example, the application server may omit an indication of jitter for the PDU set, and the network node may be configured with a default value for jitter (e.g., maximum allowed jitter or zero, etc.).

[0220] As indicated by reference numeral 1030, the network node may schedule the PDU set. In some aspects, the network node may schedule the PDU set so that the PDU set meets a deadline as indicated from an application server (e.g., using a nominal PSDB and jitter or using an indication of a dynamic PSDB after time synchronization). For example, the network node may schedule the PDU set at the earliest time at which the PDU set is the highest priority and / or is closest to a deadline for sending packets buffered to be sent by the network node.

[0221] As indicated by reference numeral 1035, the network node may send the set of PDUs. For example, the UE may send the set of PDUs at a time based at least in part on the indication of the deadline. The network node may send the set of PDUs using resources scheduled as described in conjunction with reference numeral 1030 and / or using periodic resources such as resources based on semi-persistent scheduling (SPS), etc.

[0222] Based at least in part on the network node receiving an indication of the transmission of the PDU set from the associated application server (wherein the indication of the deadline includes an indication of the jitter of the PDU set, an indication of a packet delay budget based at least in part on the jitter of the PDU set and a nominal PSDB, and / or an indication of the absolute time of the deadline), the network node may obtain the actual timing requirement of the PDU set. This may allow the network node to support additional devices in a cell operated by the network node, which may save computational, power, communication, and / or network resources that would otherwise be used to form and / or operate additional cells to support the additional devices.

[0223] As indicated above, Fig.10 Other examples can be found in the Fig.10 The examples described are different.

[0224] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a UE, according to the present disclosure. The example process 1100 is an example in which a UE (eg, UE 120) performs operations associated with deadline-based data packetization.

[0225] like Fig.11 As shown, in some aspects, process 1100 may include sending an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node (block 1110). For example, a UE (e.g., using communication manager 140 and / or Fig.15 The depicted transmitting component 1504 may transmit to the network node an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of the communication session, as described above. In some aspects, the UE may transmit the indication via metadata of a PDU set (e.g., within an application layer header).

[0226] like Fig.11 As further shown, in some aspects, process 1100 may include receiving one or more data packets based at least in part on the one or more data packets arriving at or before the deadline (block 1120). For example, a UE (e.g., using communications manager 140 and / or Fig.15Depicted receiving component 1502) can receive the one or more data packets based at least in part on one or more data packets arriving at or before a deadline, as described above.

[0227] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0228] In a first aspect, process 1100 includes receiving, from an application client at the UE, information indicating the deadline, the periodicity, the nominal packet delay budget, the jitter of burst arrival times, or the nominal arrival time of data packets of the communication session.

[0229] In a second aspect, alone or in combination with the first aspect, process 1100 includes converting the deadline into a radio access network (RAN) time domain to create a converted deadline, the deadline indicated by the indication being the converted deadline.

[0230] In a third aspect, either alone or in combination with one or more of the first and second aspects, converting the deadline to the RAN time domain comprises converting the deadline from the application time domain to the RAN time domain based at least in part on one or more of the following: a deadline mapping associated with a QoS flow, one or more deadline notification messages, or one or more DRB QoS parameters associated with the deadline.

[0231] In a fourth aspect, either alone or in combination with one or more of aspects 1 to 3, process 1100 comprises: identifying a burst index of these data packets based at least in part on one or more of: burst metadata available at an application layer of these data packets or a burst index determined at least in part based on the timing of these data packets, wherein the deadline is a periodic deadline, and wherein the burst index is associated with the timing of the deadline.

[0232] In a fifth aspect, either alone or in combination with one or more of aspects 1 to 4, process 1100 includes identifying an IP flow to which the deadline applies, the IP flow being associated with the data packets (e.g., the UE receives the data packets via the IP flow) and being identified based at least in part on one or more of: an indication of the IP flow by an application layer of the data packets or a logical channel identifier determined at least in part based on an IP packet index of the data packets.

[0233] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1100 includes: converting the IP flow into a QoS flow to which the deadline applies.

[0234] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 1100 comprises sending one or more of an indication of a QoS flow or logical channel associated with the data packets and associated with the cut-off time, an indication of a burst index associated with the timing of the cut-off time, or an indication of a logical channel identifier associated with the data packets and associated with the cut-off time.

[0235] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, process 1100 comprises receiving an additional indication that the QoS flow or the logical channel is configured with the deadline, and sending an indication that the QoS flow or the logical channel associated with these data packets is associated with the deadline.

[0236] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, process 1100 comprises receiving an indication that the expiration of the data packets of the communication session is associated with the deadline and is not associated with a packet delay budget, or sending an indication that the expiration of the data packets of the communication session is associated with the deadline and is not associated with a packet delay budget.

[0237] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, process 1100 comprises receiving an indication of acceptance of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time for data packets of the communication session.

[0238] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, sending the indication of one or more of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time of the data packets of the communication session includes: sending the indication via an RRC message, sending the indication via a MAC CE, or sending the indication via an application layer indication.

[0239] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the deadline is associated with a periodic display time and a UE internal data processing time.

[0240] In a thirteenth aspect, either alone or in combination with one or more of aspects one to twelfth, process 1100 comprises: receiving an indication of downlink resources for receiving these data packets, the downlink resources being based at least in part on the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the indication of the nominal arrival time for the data packets of the communication session, wherein the data packets are received based on the downlink resources.

[0241] In a fourteenth aspect, alone or in combination with one or more of aspects one to thirteen, process 1100 comprises: receiving an indication of a mapping of QoS flows to IP flows, wherein sending the indication of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time comprises sending additional indications of the QoS flows associated with the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time based at least in part on the mapping of the QoS flows to the IP flows.

[0242] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0243] Fig.12 is a diagram illustrating an example process 1200 performed, for example, by a network node according to the present disclosure. The example process 1200 is an example in which a network node (eg, a base station, a CU, a DU, and / or a RU) performs operations associated with deadline-based data packetization.

[0244] like Fig.12 As shown, in some aspects, process 1200 may include receiving an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with data packets of a communication session (block 1210). For example, a network node (e.g., using communication manager 150 and / or Fig.16 The depicted receiving component 1602 may receive an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with data packets of a communication session, as described above. In some aspects, the network node may receive the indication via metadata of a set of PDUs (e.g., within an application layer header). In some aspects, the network node may receive the set of PDUs from a UE or from a network node.

[0245] like Fig.12 As further shown, in some aspects, process 1200 may include sending the one or more data packets based at least in part on the one or more data packets being sent at or before the deadline (block 1220). For example, a network node (e.g., using communication manager 150 and / or Fig.16 Depicted sending component 1604) can send the one or more data packets based at least in part on the one or more data packets being sent at or before a deadline, as described above.

[0246] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0247] In a first aspect, receiving the indication comprises one or more of: receiving information indicating one or more of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time of the data packets of the communication session from a UE associated with the data packets; or receiving information indicating one or more of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time of the data packets of the communication session from an application server associated with the data packets.

[0248] In a second aspect, either alone or in combination with the first aspect, receiving the indication of one or more of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time for data packets of the communication session comprises receiving the indication via an RRC message, receiving the indication via a MAC CE, or receiving the indication via an application layer indication.

[0249] In a third aspect, alone or in combination with one or more of the first and second aspects, the cut-off time is associated with a periodic display time and a UE internal data processing time.

[0250] In a fourth aspect, either alone or in combination with one or more of aspects 1 to 3, process 1200 comprises sending an indication of downlink resources for receiving these data packets, the downlink resources being based at least in part on the deadline, periodicity, nominal packet delay budget, jitter of burst arrival time or indication of the nominal arrival time for data packets of the communication session, wherein the data packets are received by a receiving device at least in part based on these downlink resources.

[0251] In a fifth aspect, either alone or in combination with one or more of aspects 1 to 4, process 1200 comprises grouping data packets into burst groups based at least in part on the deadline, periodicity, nominal packet delay budget, jitter of burst arrival time, or an indication of the nominal arrival time of the data packets of the communication session.

[0252] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 1200 comprises receiving one or more of an indication of a QoS flow or logical channel associated with the data packets and associated with the cut-off time, an indication of a burst index associated with the timing of the cut-off time, or an indication of a logical channel identifier associated with the data packets and associated with the cut-off time.

[0253] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 1200 comprises sending an additional indication that the QoS flow or the logical channel associated with the data packets is configured with the deadline based at least in part on receiving the indication that the QoS flow or the logical channel associated with the deadline is associated with the deadline.

[0254] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, process 1200 includes sending an indication of a mapping of a QoS flow to an IP flow for converting the IP flow to which the deadline applies into the QoS flow to which the deadline applies.

[0255] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, process 1200 comprises sending an indication of acceptance of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time or the nominal arrival time for data packets of the communication session.

[0256] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, receiving the indication of the deadline includes receiving the indication of the deadline via a centralized unit, and the network node includes a distributed unit.

[0257] In an eleventh aspect, alone or in combination with one or more of aspects one to ten, sending the one or more data packets comprises: identifying a QoS flow associated with the data packets; applying the cutoff time to the data packets based at least in part on the QoS flow being associated with the cutoff time; and applying the cutoff time to the data packets at a periodic timing based at least in part on a time at which the network node receives the data packets or an indication of a burst quantity of the data packets.

[0258] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, receiving the jitter of burst arrival times comprises receiving an indication of the jitter of burst arrival times in a user plane header.

[0259] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the jitter of the burst arrival time is based at least in part on an actual burst arrival time and a nominal arrival time.

[0260] In a fourteenth aspect, either alone or in combination with one or more of aspects one to thirteen, process 1200 comprises receiving an indication that the expiration of the data packets of the communication session is associated with the deadline and is not associated with a packet delay budget, or sending an indication that the expiration of the data packets of the communication session is associated with the deadline and is not associated with a packet delay budget.

[0261] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, process 1200 includes discarding the one or more additional data packets based at least in part on a failure of the one or more additional data packets to meet the deadline.

[0262] In a sixteenth aspect, either alone or in combination with one or more of aspects one to fifteen, process 1200 comprises identifying the cut-off time based at least in part on one or more of the periodicity of the data packet, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time.

[0263] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0264] Fig.13 is a diagram illustrating an example process 1300 performed, for example, by a network node according to the present disclosure. The example process 1300 is an example in which a network node (eg, base station 110, CU, DU, and / or RU) performs operations associated with deadline-based data packetization.

[0265] like Fig.13 As shown, in some aspects, process 1300 may include: receiving an indication of a deadline for transmission of a set of PDUs, the indication of the deadline comprising one or more of: an indication of a jitter of the set of PDUs, an indication of a packet delay budget based at least in part on the jitter and a nominal PSDB of the set of PDUs, or an indication of an absolute time of the deadline (block 1310). For example, a network node (e.g., using communication manager 150 and / or Fig.15The depicted receiving component 1502) may receive an indication of a deadline for sending a PDU set, the indication of the deadline comprising one or more of: an indication of a jitter for the PDU set, an indication of a packet delay budget based at least in part on the jitter for the PDU set and a nominal PSDB, or an indication of an absolute time for the deadline, as described above.

[0266] like Fig.13 As further shown, in some aspects, process 1300 may include sending a set of PDUs at a time based at least in part on an indication of a deadline (block 1320). For example, a network node (e.g., using communication manager 150 and / or Fig.15 Depicted sending component 1504) can send a set of PDUs at a time based at least in part on an indication of a deadline, as described above.

[0267] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0268] In a first aspect, receiving the indication of the deadline includes receiving the indication of the deadline from an application server associated with the PDU set.

[0269] In a second aspect, either alone or in combination with the first aspect, receiving the indication of the deadline includes receiving the indication of the deadline via one or more of the metadata of the PDU set, the header of the PDU set, the GTP-U header of the PDU set, or the RTP protocol header.

[0270] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1300 comprises determining the cutoff time based at least in part on the indication of the jitter and the nominal PSDB, wherein the PDU set is sent based at least in part on the cutoff time.

[0271] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1300 includes receiving an indication of the nominal PSDB associated with a flow including the PDU set.

[0272] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, determining the cutoff time based at least in part on the indication of the jitter and the nominal PSDB comprises determining the cutoff time based on the nominal PSDB plus an offset based at least in part on the jitter.

[0273] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1300 includes receiving an indication of a maximum allowed jitter associated with a flow including the set of PDUs.

[0274] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the jitter exceeds the maximum allowed jitter, and the time for sending the PDU set is based at least in part on the maximum allowed jitter.

[0275] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, the indication of the jitter comprises: a default value of the jitter that is implicitly indicated at least in part based on the PDU set omitting explicit indication of the jitter, a quantized value of the jitter, or a field value mapped to the value of the jitter.

[0276] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the indication of the jitter comprises: a default value of the jitter implicitly indicated at least in part based on the PDU set omitting explicit indication of the jitter, and the default value is zero or the maximum allowed jitter.

[0277] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, process 1300 comprises: performing time synchronization with an application server associated with the PDU set to obtain synchronized timing between the application server and the network node, wherein the indication of the deadline comprises the indication of the absolute time of the deadline, and wherein the absolute time of the deadline is based at least in part on the synchronized timing.

[0278] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the deadline is based at least in part on one or more of: jitter in the packet generation time of the PDU set, a de-jitter buffer status of an application client associated with the PDU set, or a shift in the packet generation time associated with a phase-locked loop at an application layer associated with the PDU set.

[0279] In a twelfth aspect, either alone or in combination with one or more of aspects 1 to eleven, process 1300 comprises: scheduling the sending of the PDU set based at least in part on the indication of the deadline, wherein sending the PDU set is based at least in part on scheduling the sending.

[0280] although Fig.13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Fig.13The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1300 may be performed in parallel.

[0281] Fig.14 14 is a diagram illustrating an example process 1400 performed, for example, by an application server according to the present disclosure. The example process 1400 is an example in which an application server (eg, device 1700) performs operations associated with deadline-based data grouping.

[0282] like Fig.14 As shown, in some aspects, process 1400 may include providing an indication of a deadline for transmission of a set of PDUs, the indication of the deadline comprising one or more of: an indication of a jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter and a nominal PSDB for the set of PDUs, or an indication of an absolute time for the deadline (block 1410). For example, an application server (e.g., using Fig.17 The depicted communication component 1760) may provide an indication of a deadline for sending a set of PDUs, the indication of the deadline comprising one or more of: an indication of a jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter and a nominal PSDB for the set of PDUs, or an indication of an absolute time for the deadline, as described above.

[0283] like Fig.14 As further shown, in some aspects, process 1400 may include receiving a set of PDUs at a time based at least in part on an indication of a deadline (block 1420). For example, an application server (e.g., using Fig.17 Depicted communication component 1760) can receive a set of PDUs at a time based at least in part on an indication of a deadline, as described above.

[0284] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0285] In a first aspect, providing the indication of the deadline includes providing the indication of the deadline via one or more of metadata of the PDU set, a header of the PDU set, or an RTP protocol header.

[0286] In a second aspect, alone or in combination with the first aspect, process 1400 includes providing an indication of the nominal PSDB associated with a flow including the set of PDUs.

[0287] In a third aspect, alone or in combination with one or more of the first and second aspects, the deadline is based at least in part on the nominal PSDB plus an offset based at least in part on the jitter.

[0288] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1400 includes receiving an indication of a maximum allowed jitter associated with a flow including the set of PDUs.

[0289] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the indication of the jitter comprises: a default value of the jitter that is implicitly indicated at least in part based on the PDU set omitting explicit indication of the jitter, a quantized value of the jitter, or a field value mapped to the value of the jitter.

[0290] In a sixth aspect, either alone or in combination with one or more of aspects one to five, the indication of the jitter comprises: a default value of the jitter implicitly indicated at least in part based on the PDU set omitting explicit indication of the jitter, and the default value is zero or the maximum allowed jitter.

[0291] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 1400 comprises: performing time synchronization with an application server associated with the PDU set to obtain synchronized timing between the application server and the network node, wherein the indication of the deadline comprises the indication of the absolute time of the deadline, and wherein the absolute time of the deadline is based at least in part on the synchronized timing.

[0292] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, the deadline is based at least in part on one or more of: jitter in the packet generation time of the PDU set, a de-jitter buffer status of an application client associated with the PDU set, or a shift in the packet generation time associated with a phase-locked loop at an application layer associated with the PDU set.

[0293] although Fig.14 Example blocks of process 1400 are shown, but in some aspects, process 1400 may include Fig.14 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1400 may be performed in parallel.

[0294] Fig.151 is a diagram of an example apparatus 1500 for wireless communication. Apparatus 1500 may be a UE, or a UE may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a transmitting component 1504 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device) using receiving component 1502 and transmitting component 1504. As further shown, apparatus 1500 may include a communication manager 1508 (e.g., communication manager 140).

[0295] In some aspects, the apparatus 1500 may be configured to perform Figures 6 to 10 Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Fig.11 The process 1100. In some aspects, Fig.15 The device 1500 and / or one or more components shown may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Fig.15 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0296] The receiving component 1502 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1506. The receiving component 1502 may provide the received communications to one or more other components of the device 1500. In some aspects, the receiving component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1500. In some aspects, the receiving component 1502 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0297] Transmit component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and may provide the generated communications to transmit component 1504 for transmission to device 1506. In some aspects, transmit component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmit component 1504 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 1504 can be co-located with the receive component 1502 in a transceiver.

[0298] The sending component 1504 can send an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of the communication session to the network node. The receiving component 1502 can receive the one or more data packets based at least in part on the one or more data packets arriving at or before the deadline.

[0299] Receiving component 1502 can receive information from an application client at a UE indicating a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time of data packets for a communication session.

[0300] The communications manager 1508 may convert the cutoff time into the RAN time domain to create a converted cutoff time, the cutoff time indicated by the indication being the converted cutoff time.

[0301] The communication manager 1508 may identify a burst index for a data packet based at least in part on one or more of: burst metadata available at an application layer of the data packet or a burst index determined at least in part based on the timing of the data packet, wherein the deadline is a periodic deadline, and wherein the burst index is associated with the timing of the deadline.

[0302] The communications manager 1508 may identify an IP flow to which the deadline applies, the IP flow being associated with the data packet and being identified based at least in part on one or more of: an indication of the IP flow via an application layer of the data packet or a logical channel identifier determined at least in part based on an IP packet index of the data packet.

[0303] The communication manager 1508 may convert the IP flow into a QoS flow to which the deadline applies.

[0304] The sending component 1504 may send one or more of an indication of a QoS flow or logical channel associated with the data packet and the deadline, an indication of a burst index associated with the timing of the deadline, or an indication of a logical channel identifier associated with the data packet and the deadline.

[0305] Receiving component 1502 can receive an additional indication that the QoS flow or logical channel is configured with a deadline and send an indication that the QoS flow or logical channel associated with the data packet is associated with the deadline.

[0306] Receiving component 1502 can receive an indication that expiration of a data packet for a communication session is associated with a deadline and is not associated with a packet delay budget.

[0307] Transmitting component 1504 can transmit an indication that expiration of data packets for the communication session is associated with a deadline and not associated with a packet delay budget.

[0308] Receiving component 1502 can receive an indication of acceptance of a deadline, periodicity, a nominal packet delay budget, jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session.

[0309] The receiving component 1502 may receive an indication of downlink resources for receiving data packets, the downlink resources being based at least in part on an indication of a deadline, a periodicity, a nominal packet delay budget, a jitter in a burst arrival time, or a nominal arrival time for data packets of a communication session upon which the data packets are received.

[0310] Receiving component 1502 can receive an indication of a mapping of QoS flows to IP flows.

[0311] Fig.16 1 is a diagram of an example apparatus 1600 for wireless communication. Apparatus 1600 may be a network node, or a network node may include apparatus 1600. In some aspects, apparatus 1600 includes a receiving component 1602 and a transmitting component 1604 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1600 may communicate with another apparatus 1606 (such as a UE, a base station, or another wireless communication device) using receiving component 1602 and transmitting component 1604. As further shown, apparatus 1600 may include a communication manager (e.g., communication manager 150).

[0312] In some aspects, the apparatus 1600 may be configured to perform Figures 6 to 10 Additionally or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as Fig.12 The process 1200 Fig.13 In some aspects, Fig.16 The device 1600 and / or one or more components shown may include a combination of Figure 2 One or more components of the network node. Additionally or alternatively, Fig.16 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0313] The receiving component 1602 may receive communications from the device 1606, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1602 may provide the received communications to one or more other components of the device 1600. In some aspects, the receiving component 1602 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1600. In some aspects, the receiving component 1602 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network node.

[0314] The transmitting component 1604 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1606. In some aspects, one or more other components of the device 1600 may generate communications and may provide the generated communications to the transmitting component 1604 for transmission to the device 1606. In some aspects, the transmitting component 1604 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1606. In some aspects, the transmitting component 1604 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network node. In some aspects, the transmit component 1604 can be co-located with the receive component 1602 in a transceiver.

[0315] The receiving component 1602 can receive an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with data packets for the communication session. The sending component 1604 can send the one or more data packets based at least in part on the one or more data packets being sent at or before the deadline.

[0316] The sending component 1604 may send an indication of downlink resources for receiving data packets, the downlink resources being based at least in part on an indication of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets for a communication session, wherein the data packets are received by a receiving device based at least in part on the downlink resources.

[0317] The communications manager 1608 may group the data packets into burst groups based at least in part on a deadline, a periodicity, a nominal packet delay budget, a jitter in a burst arrival time, or an indication of a nominal arrival time for the data packets of the communication session.

[0318] Receiving component 1602 may receive one or more of an indication that a QoS flow or logical channel associated with a data packet is associated with a deadline, an indication of a burst index associated with a timing of the deadline, or an indication that a logical channel identifier associated with the data packet is associated with the deadline.

[0319] Transmitting component 1604 can transmit an additional indication that the QoS flow or logical channel associated with the data packet is configured with a cutoff time based at least in part on receiving an indication that the QoS flow or logical channel associated with the data packet is associated with a cutoff time.

[0320] The sending component 1604 can send an indication of a mapping of QoS flows to IP flows for converting the IP flows to which the deadlines apply to the QoS flows to which the deadlines apply.

[0321] Transmitting component 1604 can transmit an indication of acceptance of a deadline, periodicity, a nominal packet delay budget, jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session.

[0322] Receiving component 1602 can receive an indication that expiration of a data packet for a communication session is associated with a deadline and is not associated with a packet delay budget.

[0323] Transmitting component 1604 can transmit an indication that expiration of data packets for the communication session is associated with a deadline and not associated with a packet delay budget.

[0324] The communications manager 1608 may discard the one or more additional data packets based at least in part on the one or more additional data packets failing to meet the deadline.

[0325] The communications manager 1608 may identify the cutoff time based at least in part on one or more of a periodicity of the data packets, a nominal packet delay budget, jitter in the burst arrival time, or a nominal arrival time.

[0326] Fig.16 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.16 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.16 Two or more components shown may be implemented in a single component, or Fig.16 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.16 The component set (one or more components) shown may be described as being executable by Fig.16 Another component shown may be a collection of components that perform one or more functions.

[0327] The receiving component 1602 can receive an indication of a deadline for transmission of the PDU set, the indication of the deadline comprising one or more of: an indication of a jitter for the PDU set, an indication of a packet delay budget based at least in part on the jitter for the PDU set and a nominal PDU set delay budget (PSDB), or an indication of an absolute time for the deadline. The sending component 1604 can transmit the PDU set at a time based at least in part on the indication of the deadline.

[0328] The communications manager 1608 may determine a cutoff time based at least in part on the indication of jitter and the nominal PSDB, wherein the set of PDUs are to be sent based at least in part on the cutoff time.

[0329] Receiving component 1602 can receive an indication of a nominal PSDB associated with a flow including a set of PDUs.

[0330] Receiving component 1602 can receive an indication of a maximum allowed jitter associated with a flow including a set of PDUs.

[0331] The communications manager 1608 may schedule transmission of the set of PDUs based at least in part on the indication of the deadline, wherein transmitting the set of PDUs is based at least in part on scheduling the transmission.

[0332] Fig.16 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.16 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.16 Two or more components shown may be implemented in a single component, or Fig.16 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.16 The component set (one or more components) shown may be described as being executable by Fig.16 Another component shown may be a collection of components that perform one or more functions.

[0333] Fig.17 1700 is a diagram of example components of a device 1700 that may correspond to an application server and / or a CN network node. In some implementations, the application server and / or the CN network node includes one or more devices 1700 and / or one or more components of a device 1700. Fig.17 As shown, device 1700 may include a bus 1710 , a processor 1720 , a memory 1730 , an input component 1740 , an output component 1750 , and a communication component 1760 .

[0334] The bus 1710 includes one or more components that enable wired and / or wireless communication between components of the device 1700. The bus 1710 may be coupled to the device 1700, such as via an operational coupling, a communicative coupling, an electronic coupling, and / or an electrical coupling. Fig.17 Two or more components of the computer system are coupled together. Processor 1720 includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field programmable gate array, an application specific integrated circuit, and / or another type of processing component. Processor 1720 is implemented in hardware, firmware, or a combination of hardware and software. In some specific implementations, processor 1720 includes one or more processors that can be programmed to perform one or more operations or processes described elsewhere herein.

[0335] Memory 1730 includes volatile memory and / or non-volatile memory. For example, memory 1730 may include random access memory (RAM), read-only memory (ROM), a hard drive, and / or another type of memory (e.g., flash memory, magnetic memory, and / or optical memory). Memory 1730 may include internal memory (e.g., RAM, ROM, or hard drive) and / or removable memory (e.g., removable via a universal serial bus connection). Memory 1730 may be a non-transitory computer-readable medium. Memory 1730 stores information, instructions, and / or software (e.g., one or more software applications) related to the operation of device 1700. In some specific implementations, memory 1730 includes one or more memories such as coupled to one or more processors (e.g., processor 1720) via bus 1710.

[0336] Input component 1740 enables device 1700 to receive input, such as user input and / or sensed input. For example, input component 1740 may include a touch screen, keyboard, keypad, mouse, button, microphone, switch, sensor, global positioning system sensor, accelerometer, gyroscope and / or actuator. Output component 1750 enables device 1700 to provide output such as via a display, speaker and / or light emitting diode. Communication component 1760 enables device 1700 to communicate with other devices via wired connection and / or wireless connection. For example, communication component 1760 may include a receiver, a transmitter, a transceiver, a modem, a network interface card and / or an antenna.

[0337] Device 1700 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., memory 1730) may store an instruction set (e.g., one or more instructions or codes) for execution by processor 1720. Processor 1720 may execute an instruction set to perform one or more operations or processes described herein. In some specific implementations, execution of the instruction set by one or more processors 1720 causes one or more processors 1720 and / or device 1700 to perform one or more operations or processes described herein. In some specific implementations, hard-wired circuits may be used instead of instructions or in combination with instructions to perform one or more operations or processes described herein. Additionally or alternatively, processor 1720 may be configured to perform one or more operations or processes described herein. Therefore, the specific implementation described herein is not limited to any particular combination of hardware circuits and software.

[0338] In some aspects, communication component 1760 can provide an indication of a deadline for transmission of a set of PDUs, the indication of the deadline comprising one or more of: an indication of a jitter for the set of PDUs, an indication of a packet delay budget based at least in part on the jitter for the set of PDUs and a nominal PSDB, or an indication of an absolute time for the deadline. Receiving component 1602 can receive the set of PDUs at a time based at least in part on the indication of the deadline.

[0339] In some aspects, communication component 1760 may provide an indication of a nominal PSDB associated with a flow including a set of PDUs.

[0340] In some aspects, communicating component 1760 may receive an indication of a maximum allowed jitter associated with a flow comprising a set of PDUs.

[0341] Fig.17 The number and arrangement of components shown are provided as examples. Device 1700 may include Fig.17Those components shown may include additional components, fewer components, different components, or components arranged in a different manner. Additionally or alternatively, a set of components (e.g., one or more components) of device 1700 may perform one or more functions described as being performed by another set of components of device 1700.

[0342] The following provides an overview of some aspects of the disclosure:

[0343] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: sending an indication of one or more of a deadline, periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node; and receiving the one or more data packets based at least in part on the one or more data packets arriving at or before the deadline.

[0344] Aspect 2: The method according to Aspect 1 also includes: receiving information indicating the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time or the nominal arrival time of the data packets of the communication session from an application client at the UE.

[0345] Aspect 3: The method according to aspect 2 further includes: converting the deadline into a radio access network (RAN) time domain to create a converted deadline, the deadline indicated by the indication being the converted deadline.

[0346] Aspect 4: A method according to Aspect 3, wherein converting the deadline to the RAN time domain includes: converting the deadline from the application time domain to the RAN time domain based at least in part on one or more of the following: a deadline mapping associated with a quality of service (QoS) flow, one or more deadline notification messages, or one or more data radio bearer (DRB) QoS parameters associated with the deadline.

[0347] Aspect 5: The method according to any one of Aspects 3 or 4 further includes: identifying a burst index of the data packet based at least in part on one or more of the following: burst metadata available at the application layer of the data packet or a burst index determined at least in part based on the timing of the data packet, wherein the deadline is a periodic deadline, and wherein the burst index is associated with the timing of the deadline.

[0348] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: identifying an Internet Protocol (IP) flow to which the deadline applies, the IP flow being associated with the data packet and being identified at least in part based on one or more of the following: an indication of the IP flow via the application layer of the data packet or a logical channel identifier determined at least in part based on an IP packet index of the data packet.

[0349] Aspect 7: The method according to Aspect 6 further includes: converting the IP flow into a Quality of Service (QoS) flow to which the deadline applies.

[0350] Aspect 8: The method according to any one of Aspects 1 to 7 further includes: sending one or more of the following: an indication of a quality of service (QoS) flow associated with the data packet and associated with the cut-off time, an indication of a burst index associated with the timing of the cut-off time, or an indication of a logical channel identifier associated with the data packet and associated with the cut-off time.

[0351] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: receiving an additional indication that the QoS flow or the logical channel is configured with the deadline; and sending an indication that the QoS flow or the logical channel associated with the data packet is associated with the deadline.

[0352] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: receiving an indication that the expiration of the data packet of the communication session is associated with the deadline and is not associated with a packet delay budget, or sending an indication that the expiration of the data packet of the communication session is associated with the deadline and is not associated with a packet delay budget.

[0353] Aspect 11: The method according to any one of Aspects 1 to 10 also includes: receiving an indication of acceptance of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time or the nominal arrival time of the data packets of the communication session.

[0354] Aspect 12: A method according to any one of Aspects 1 to 11, wherein sending the indication of one or more of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time of the data packets of the communication session includes: sending the indication via a radio resource control (RRC) message, sending the indication via a medium access control (MAC) control element (CE), or sending the indication via an application layer indication.

[0355] Aspect 13: The method according to any one of aspects 1 to 12, wherein the cut-off time is associated with a periodic display time and a UE internal data processing time.

[0356] Aspect 14: The method according to any one of Aspects 1 to 13 further includes: receiving an indication of downlink resources for receiving the data packets, the downlink resources being at least partially based on the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the indication of the nominal arrival time for the data packets of the communication session, wherein the data packets are received based on the downlink resources.

[0357] Aspect 15: The method according to any one of aspects 1 to 14, further comprising: receiving an indication of a mapping of a quality of service (QoS) flow to an Internet Protocol (IP) flow, wherein sending the indication of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time comprises: sending an additional indication of the QoS flow associated with the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time based at least in part on the mapping of the QoS flow to the IP flow. Wherein sending the indication of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time comprises: sending an additional indication of the QoS flow associated with the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time based at least in part on the mapping of the QoS flow to the IP flow.

[0358] Aspect 16: A method of wireless communication performed by a network node, comprising: receiving an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time associated with data packets of a communication session; and sending the one or more data packets based at least in part on the one or more data packets being sent at or before the deadline.

[0359] Aspect 17: A method according to Aspect 16, wherein receiving the indication includes one or more of the following: receiving information indicating one or more of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time of the data packets of the communication session from a user equipment (UE) associated with the data packet; or receiving information indicating one or more of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time of the data packets of the communication session from an application server associated with the data packet.

[0360] Aspect 18: A method according to Aspect 17, wherein receiving the indication of one or more of the deadline, periodicity, nominal packet delay budget, jitter of burst arrival time, or the nominal arrival time of data packets of the communication session includes: receiving the indication via a radio resource control (RRC) message, receiving the indication via a medium access control (MAC) control element (CE), or receiving the indication via an application layer indication.

[0361] Aspect 19: The method according to any one of aspects 16 to 18, wherein the cut-off time is associated with a periodic display time and a UE internal data processing time.

[0362] Aspect 20: The method according to any one of Aspects 16 to 19 further includes: sending an indication of downlink resources for receiving the data packets, the downlink resources being at least partially based on the deadline, periodicity, nominal packet delay budget, jitter of burst arrival time or the indication of the nominal arrival time of the data packets of the communication session, wherein the data packets are received by the receiving device at least partially based on the downlink resources.

[0363] Aspect 21: The method according to any one of Aspects 16 to 20 also includes: grouping data packets into burst groups based at least in part on the deadline, periodicity, nominal packet delay budget, jitter of burst arrival time or indication of the nominal arrival time of the data packets of the communication session.

[0364] Aspect 22: The method according to any one of Aspects 16 to 21 further includes: receiving one or more of the following: an indication of a quality of service (QoS) flow associated with the data packet and associated with the cut-off time, an indication of a burst index associated with the timing of the cut-off time, or an indication of a logical channel identifier associated with the data packet and associated with the cut-off time.

[0365] Aspect 23: The method according to any one of Aspects 16 to 22 further includes: sending an additional indication that the QoS flow or the logical channel associated with the data packet is configured with the deadline based at least in part on receiving an indication that the QoS flow or the logical channel associated with the deadline is associated with the deadline.

[0366] Aspect 24: The method according to any one of Aspects 16 to 23 further includes: sending an indication of a mapping of a quality of service (QoS) flow to an Internet Protocol (IP) flow, so as to convert the IP flow to which the deadline applies into the QoS flow to which the deadline applies.

[0367] Aspect 25: The method according to any one of Aspects 16 to 24 further includes: sending an indication of acceptance of the deadline, the periodicity, the nominal packet delay budget, the jitter of the burst arrival time or the nominal arrival time of the data packets of the communication session.

[0368] Aspect 26: The method according to any one of aspects 16 to 25, wherein receiving the indication of the deadline comprises receiving the indication of the deadline via a centralized unit, and wherein the network node comprises a distributed unit.

[0369] Aspect 27: A method according to any one of Aspects 16 to 26, wherein sending the one or more data packets includes: identifying a quality of service (QoS) flow associated with the data packet; applying the cutoff time to the data packet based at least in part on the QoS flow being associated with the cutoff time; and applying the cutoff time to the data packet at a periodic timing based at least in part on the time at which the network node receives the data packet or an indication of a burst number of the data packet.

[0370] Aspect 28: The method according to any one of aspects 16 to 27, wherein receiving the jitter of burst arrival time comprises: receiving an indication of the jitter of burst arrival time in a user plane header.

[0371] Aspect 29: The method according to any one of aspects 16 to 28, wherein the jitter of burst arrival time is based at least in part on actual burst arrival time and nominal arrival time.

[0372] Aspect 30: The method according to any one of Aspects 16 to 29 further includes: receiving an indication that the expiration of the data packet of the communication session is associated with the deadline and is not associated with a packet delay budget, or sending an indication that the expiration of the data packet of the communication session is associated with the deadline and is not associated with a packet delay budget.

[0373] Aspect 31: The method according to any one of aspects 16 to 30, further comprising: discarding the one or more additional data packets based at least in part on the one or more additional data packets failing to meet the deadline.

[0374] Aspect 32: The method according to any one of Aspects 16 to 31 further includes: identifying the cut-off time based at least in part on one or more of the periodicity of the data packet, the nominal packet delay budget, the jitter of the burst arrival time, or the nominal arrival time.

[0375] Aspect 33: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 32.

[0376] Aspect 34: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 32.

[0377] Aspect 35: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 32.

[0378] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 32.

[0379] Aspect 37: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 32.

[0380] The following provides a summary of some additional aspects of the disclosure:

[0381] Aspect 1: A method of wireless communication performed by a network node, comprising: receiving an indication of a deadline for sending a set of protocol data units (PDUs), the indication of the deadline comprising one or more of: an indication of a jitter of the PDU set, an indication of a packet delay budget based at least in part on the jitter of the PDU set and a nominal PDU set delay budget (PSDB), or an indication of an absolute time of the deadline; and sending the PDU set at a time based at least in part on the indication of the deadline.

[0382] Aspect 2: The method according to aspect 1, wherein receiving the indication of the deadline includes: receiving the indication of the deadline from an application server associated with the PDU set.

[0383] Aspect 3: A method according to any one of Aspects 1 to 2, wherein receiving the indication of the deadline includes: receiving the indication of the deadline via one or more of: metadata of the PDU set, a header of the PDU set, a General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) header of the PDU set, or a Real-time Transport (RTP) protocol header.

[0384] Aspect 4: The method according to any one of Aspects 1 to 3 further includes: determining the deadline based at least in part on the indication of the jitter and the nominal PSDB, wherein the PDU set is sent based at least in part on the deadline.

[0385] Aspect 5: The method according to aspect 4 further comprises: receiving an indication of the nominal PSDB associated with the flow including the PDU set.

[0386] Aspect 6: A method according to any one of Aspects 4 to 5, wherein determining the cutoff time based at least in part on the indication of the jitter and the nominal PSDB includes determining the cutoff time according to the nominal PSDB plus an offset based at least in part on the jitter.

[0387] Aspect 7: The method according to any one of aspects 1 to 6, further comprising: receiving an indication of a maximum allowed jitter associated with a flow including the set of PDUs.

[0388] Aspect 8: The method of aspect 7, wherein the jitter exceeds the maximum allowed jitter, and wherein the time for sending the set of PDUs is based at least in part on the maximum allowed jitter.

[0389] Aspect 9: A method according to any one of Aspects 1 to 8, wherein the indication of the jitter includes: a default value of the jitter implicitly indicated at least in part based on the PDU set omitting an explicit indication of the jitter, a quantized value of the jitter, or a field value mapped to the value of the jitter.

[0390] Aspect 10: A method according to aspect 9, wherein the indication of the jitter includes: a default value of the jitter implicitly indicated at least in part based on the PDU set omitting an explicit indication of the jitter, and wherein the default value is zero or a maximum allowed jitter.

[0391] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: performing time synchronization with an application server associated with the PDU set to obtain synchronized timing between the application server and the network node, wherein the indication of the deadline includes the indication of the absolute time of the deadline, and wherein the absolute time of the deadline is at least partially based on the synchronized timing.

[0392] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the deadline is based at least in part on one or more of: jitter in the packet generation time of the PDU set, a de-jitter buffer status of an application client associated with the PDU set, or a shift in the packet generation time associated with a phase-locked loop at an application layer associated with the PDU set.

[0393] Aspect 13: The method according to any one of Aspects 1 to 12 further includes: scheduling the sending of the PDU set based at least in part on the indication of the deadline, wherein sending the PDU set is based at least in part on scheduling the sending.

[0394] Aspect 14: A method of wireless communication performed by an application server, comprising: providing an indication of a deadline for sending a set of protocol data units (PDUs), the indication of the deadline comprising one or more of: an indication of a jitter of the PDU set, an indication of a packet delay budget based at least in part on the jitter of the PDU set and a nominal PDU set delay budget (PSDB), or an indication of an absolute time of the deadline; and receiving the PDU set at a time based at least in part on the indication of the deadline.

[0395] Aspect 15: A method according to Aspect 14, wherein providing the indication of the deadline includes: providing the indication of the deadline via one or more of the following: metadata of the PDU set, a header of the PDU set, and a real-time transport (RTP) protocol header.

[0396] Aspect 16: The method according to any one of aspects 14 to 15, further comprising: providing an indication of the nominal PSDB associated with the flow including the set of PDUs.

[0397] Aspect 17: The method according to any one of aspects 14 to 16, wherein the cut-off time is based at least in part on the nominal PSDB plus an offset based at least in part on the jitter.

[0398] Aspect 18: The method according to any one of aspects 14 to 17, further comprising: receiving an indication of a maximum allowed jitter associated with a flow including the set of PDUs.

[0399] Aspect 19: A method according to any one of Aspects 14 to 18, wherein the indication of the jitter includes: a default value of the jitter implicitly indicated at least in part based on the PDU set omitting an explicit indication of the jitter, a quantized value of the jitter, or a field value mapped to the value of the jitter.

[0400] Aspect 20: A method according to aspect 19, wherein the indication of the jitter includes: a default value of the jitter implicitly indicated at least in part based on the PDU set omitting an explicit indication of the jitter, and wherein the default value is zero or a maximum allowed jitter.

[0401] Aspect 21: The method according to any one of Aspects 14 to 20 further includes: performing time synchronization with an application server associated with the PDU set to obtain synchronized timing between the application server and the network node, wherein the indication of the deadline includes the indication of the absolute time of the deadline, and wherein the absolute time of the deadline is at least partially based on the synchronized timing.

[0402] Aspect 22: A method according to any one of Aspects 14 to 21, wherein the deadline is based at least in part on one or more of: jitter in the packet generation time of the PDU set, a de-jitter buffer status of an application client associated with the PDU set, or a shift in the packet generation time associated with a phase-locked loop at an application layer associated with the PDU set.

[0403] Aspect 23: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 22.

[0404] Aspect 24: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 22.

[0405] Aspect 25: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 22.

[0406] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 22.

[0407] Aspect 27: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 22.

[0408] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0409] Further disclosure is included in the appendix. This appendix is ​​provided as an example only and should be considered a part of this specification. The definitions, illustrations, or other descriptions in the appendix do not replace or cover similar information contained in the specific embodiments or figures. In addition, the definitions, illustrations, or other descriptions in the specific embodiments or figures do not replace or cover similar information contained in the appendix. In addition, this appendix is ​​not intended to limit the disclosure of possible aspects.

[0410] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0411] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0412] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0413] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "any" or "only one").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: sending an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node; and The one or more data packets are received based at least in part on one or more data packets arriving at or before the cutoff time.

2. The UE of claim 1, wherein the one or more processors are further configured to: Information indicating the deadline, the periodicity, the nominal packet delay budget, the jitter of burst arrival times, or the nominal arrival time of data packets of the communication session is received from an application client at the UE.

3. The UE of claim 2, wherein the one or more processors are further configured to: The cut-off time is converted into a radio access network (RAN) time domain to create a converted cut-off time, the cut-off time indicated by the indication being the converted cut-off time.

4. The UE of claim 3, wherein to convert the cutoff time into the RAN time domain, the one or more processors are configured to convert the cutoff time from an application time domain to the RAN time domain based at least in part on one or more of: a deadline map associated with a Quality of Service (QoS) flow, One or more deadline notification messages, or One or more data radio bearer (DRB) QoS parameters associated with the deadline.

5. The UE of claim 3, wherein the one or more processors are further configured to: identifying a burst index for the data packet based at least in part on one or more of: burst metadata available at the application layer of the data packet, or a burst index determined based at least in part on the timing of said data packets, wherein the deadline is a periodic deadline, and The burst index is associated with an opportunity of the deadline.

6. The UE of claim 1, wherein the one or more processors are further configured to: Identifying an Internet Protocol (IP) flow to which the deadline applies, the IP flow being associated with the data packet and being identified based at least in part on one or more of: an indication of the IP flow via the application layer of the data packet, or a logical channel identification determined based at least in part on an IP packet index of the data packet; and The IP flow is converted into a Quality of Service (QoS) flow to which the deadline applies.

7. The UE of claim 1 , wherein the one or more processors are further configured to send one or more of: an indication that a Quality of Service (QoS) flow or logical channel associated with the data packet is associated with the cut-off time, an indication of a burst index associated with the opportunity of said deadline, or A logical channel associated with the data packet identifies an indication associated with the cut-off time.

8. The UE of claim 1, wherein the one or more processors are further configured to: The receiving QoS flow or logical channel is configured with an additional indication of said deadline; and An indication is sent that the QoS flow or the logical channel associated with the data packet is associated with the cutoff time.

9. The UE of claim 1, wherein the one or more processors are further configured to perform one or more of the following operations: receiving an indication that expiration of the data packets for the communication session is associated with the deadline and is not associated with a packet delay budget; sending an indication that expiry of the data packet for the communication session is associated with the deadline and is not associated with a packet delay budget; or An indication of acceptance of the deadline, the periodicity, the nominal packet delay budget, the jitter of burst arrival times, or the nominal arrival time of data packets for the communication session is received.

10. The UE of claim 1, wherein the cut-off time is associated with a periodic display time and a UE internal data processing time.

11. The UE of claim 1 , wherein the one or more processors are further configured to: receiving an indication of downlink resources for receiving the data packets, the downlink resources being based at least in part on the deadline, the periodicity, the nominal packet delay budget, the jitter of burst arrival times, or the indication of the nominal arrival time for data packets of the communication session, The data packet is received based on the downlink resource.

12. The UE of claim 1 , wherein the one or more processors are further configured to receive an indication of a mapping of a quality of service (QoS) flow to an Internet Protocol (IP) flow, wherein to send the indication of the deadline, the periodicity, the nominal packet delay budget, the jitter of a burst arrival time, or the nominal arrival time, the one or more processors are configured to: An additional indication of a QoS flow associated with the deadline, the periodicity, the nominal packet delay budget, the jitter of burst arrival times, or the nominal arrival time is sent based at least in part on the mapping of the QoS flow to the IP flow.

13. A network node for wireless communication, comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter in a burst arrival time, or a nominal arrival time associated with data packets of a communication session; and The one or more data packets are sent based at least in part on one or more data packets being sent at or before the cutoff time.

14. The network node of claim 13, wherein to receive the indication, the one or more processors are configured to perform one or more of the following operations: receiving information indicating one or more of the deadline, the periodicity, the nominal packet delay budget, the jitter of burst arrival times, or the nominal arrival time of data packets of the communication session from a user equipment (UE) associated with the data packets, or Information indicating the deadline, the periodicity, the nominal packet delay budget, the jitter of burst arrival times, or the nominal arrival time of data packets of the communication session is received from an application server associated with the data packets.

15. The network node according to claim 13, wherein the cut-off time is associated with a periodic display time and a UE internal data processing time.

16. The network node of claim 13, wherein the one or more processors are further configured to: sending an indication of downlink resources for receiving the data packets, the downlink resources being based at least in part on the deadline, the periodicity, the nominal packet delay budget, the jitter of burst arrival times, or the indication of the nominal arrival time for data packets of the communication session, The data packet is received by a receiving device based at least in part on the downlink resources.

17. The network node of claim 13, wherein the one or more processors are further configured to: Data packets are grouped into burst groups based at least in part on the deadline, periodicity, a nominal packet delay budget, the jitter of burst arrival times, or the indication of the nominal arrival times for data packets of the communication session.

18. The network node of claim 13, wherein the one or more processors are further configured to receive one or more of: an indication of a quality of service (QoS) flow associated with the data packet and associated with the deadline, an indication of a burst index associated with the opportunity of said deadline, or A logical channel associated with the data packet identifies an indication associated with the cut-off time.

19. The network node of claim 13, wherein the one or more processors are further configured to: An additional indication that a quality of service (QoS) flow or logical channel associated with the data packet is configured with the cutoff time is sent based at least in part on receiving an indication that the QoS flow or logical channel associated with the data packet is associated with the cutoff time.

20. The network node of claim 13, wherein the one or more processors are further configured to: An indication of a mapping of quality of service (QoS) flows to Internet Protocol (IP) flows is sent for converting the IP flows to which the deadline applies to the QoS flows to which the deadline applies.

21. The network node of claim 13, wherein the one or more processors are further configured to: An indication of acceptance of the deadline, the periodicity, the nominal packet delay budget, the jitter of burst arrival times, or the nominal arrival time of data packets for the communication session is sent.

22. The network node of claim 13, wherein to receive the indication of the deadline, the one or more processors are configured to receive the indication of the deadline via a centralized unit, and The network nodes include distributed units.

23. The network node of claim 13, wherein to send the one or more data packets, the one or more processors are configured to: identifying a quality of service (QoS) flow associated with the data packet; applying the cutoff time to the data packet based at least in part on the QoS flow being associated with the cutoff time; as well as The periodic timing of the cut-off time is applied to the data packets based at least in part on a time at which the network node receives the data packets or an indication of a bursty number of the data packets.

24. The network node of claim 13, wherein to receive the jitter of burst arrival times, the one or more processors are configured to: An indication of said jitter in burst arrival times is received in a user plane header.

25. The network node of claim 13, wherein the jitter of burst arrival times is based at least in part on actual burst arrival times and nominal arrival times.

26. The network node of claim 13, wherein the one or more processors are further configured to perform one or more of the following operations: receiving an indication that expiration of the data packets for the communication session is associated with the deadline and is not associated with a packet delay budget; sending an indication that expiration of the data packet for the communication session is associated with the deadline and is not associated with a packet delay budget; discarding the one or more additional data packets based at least in part on a failure of the one or more additional data packets to meet the deadline; or The cut-off time is identified based at least in part on one or more of the periodicity of data packets, the nominal packet delay budget, the jitter of burst arrival times, or the nominal arrival time.

27. The network node of claim 13, wherein to receive the indication of the deadline, the one or more processors are configured to receive the indication of the deadline via one or more of: metadata of the data packet, a header of the data packet, a General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U) header of the data packet, Real-time Transport (RTP) protocol header, or Secure Real-time Transport (SRTP) protocol header.

28. The network node according to claim 27, wherein the deadline for each PDU set or PDU is indicated by a PDU set delay budget (PSDB) or a packet delay budget (PDB) until the deadline.

29. A method of wireless communication performed by a user equipment (UE), comprising: sending an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter of a burst arrival time, or a nominal arrival time for data packets of a communication session to a network node; and The one or more data packets are received based at least in part on one or more data packets arriving at or before the cutoff time.

30. A method of wireless communication performed by a network node, comprising: receiving an indication of one or more of a deadline, a periodicity, a nominal packet delay budget, a jitter in a burst arrival time, or a nominal arrival time associated with data packets of a communication session; and The one or more data packets are sent based at least in part on one or more data packets being sent at or before the cutoff time.