FIELD

[0001] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to determining a delay budget based on a remaining delay budget (“RDB”.

BACKGROUND

[0002] In certain wireless communications networks, a RDB may be used. In such networks, the RDB may be used in a variety of ways.

BRIEF SUMMARY

[0003] Methods for determining a delay budget based on a RDB are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes receiving, at a user equipment (“UE”), downlink control information (“DCI”) indicating a first RDB value from a set of RDB values indicated by higher layer signaling. In some embodiments, the method includes determining a time reference based on the DCI. In certain embodiments, the method includes determining whether a set of uplink (“UL”) slots from the time reference are counted in the first RDB value. In various embodiments, the method includes, in response to determining that the set of UL slots are counted in the first RDB value, setting a second RDB value to be the first RDB value. In some embodiments, the method includes, in response to determining that the set of UL slots are not counted in the first RDB value, determining a second RDB value based on the first RDB value and the set of UL slots. In certain embodiments, the method includes determining that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

[0004] One apparatus for determining a delay budget based on a RDB includes a UE. In some embodiments, the apparatus includes a receiver that receives DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling. In various embodiments, the apparatus includes a processor that: determines a time reference based on the DCI; determines whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, sets a second RDB value to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, determines a second RDB value based on the first RDB value and the set of UL slots; and determines that a delay budget is exceeded after the second RDB value elapses in relation to the time reference. [0005] Another embodiment of a method for determining a delay budget based on a RDB includes transmitting, from a network device to a UE, DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling. A time reference is determined based on the DCI; it is determined whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, a second RDB value is set to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, a second RDB value is determined based on the first RDB value and the set of UL slots; and it is determined that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

[0006] Another apparatus for determining a delay budget based on a RDB includes a network device. In some embodiments, the apparatus includes a transmitter that transmits, to a UE, DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling. A time reference is determined based on the DCI; it is determined whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, a second RDB value is set to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, a second RDB value is determined based on the first RDB value and the set of UL slots; and it is determined that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0008] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for determining a delay budget based on a RDB;

[0009] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for determining a delay budget based on a RDB;

[0010] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for determining a delay budget based on a RDB;

[0011] Figure 4 is a timing diagram illustrating one embodiment of a fixed frame period structure;

[0012] Figure 5 is a flow chart diagram illustrating one embodiment of a method for determining a delay budget based on a RDB; and [0013] Figure 6 is a flow chart diagram illustrating another embodiment of a method for determining a delay budget based on a RDB.

DETAILED DESCRIPTION

[0014] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0015] Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0016] Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0017] Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices. [0018] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0019] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc readonly memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0020] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0021] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0022] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0023] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0024] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0025] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0026] The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0027] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0028] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0029] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0030] Figure 1 depicts an embodiment of a wireless communication system 100 for determining a delay budget based on a RDB. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0031] In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via uplink (“UL”) communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0032] The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a location server, a core network (“CN”), a radio network entity, a Node-B, an evolved node-B (“eNB”), a 5G node-B (“gNB”), a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an access point (“AP”), new radio (“NR”), a network entity, an access and mobility management function (“AMF”), a unified data management (“UDM”), a unified data repository (“UDR”), a UDM/UDR, a policy control function (“PCF”), a radio access network (“RAN”), a network slice selection function (“NSSF”), an operations, administration, and management (“0AM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non- third generation partnership project (“3GPP”) gateway function (“TNGF”), or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0033] In one implementation, the wireless communication system 100 is compliant with NR protocols standardized in 3GPP, wherein the network unit 104 transmits using an orthogonal frequency division multiplexing (“OFDM”) modulation scheme on the downlink (“DL”) and the remote units 102 transmit on the UL using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, institute of electrical and electronics engineers (“IEEE”) 802. 11 variants, global system for mobile communications (“GSM”), general packet radio service (“GPRS”), universal mobile telecommunications system (“UMTS”), long term evolution (“LTE”) variants, code division multiple access 2000 (“CDMA2000”), Bluetooth®, ZigBee, Sigfox, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0034] The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.

[0035] In various embodiments, a remote unit 102 may receive, at a UE, DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling. In some embodiments, the remote unit 102 may determine a time reference based on the DCI. In certain embodiments, the remote unit 102 may determine whether a set of UL slots from the time reference are counted in the first RDB value. In various embodiments, the remote unit 102 may, in response to determining that the set of UL slots are counted in the first RDB value, set a second RDB value to be the first RDB value. In some embodiments, the remote unit 102 may, in response to determining that the set of UL slots are not counted in the first RDB value, determine a second RDB value based on the first RDB value and the set of UL slots. In certain embodiments, the remote unit 102 may determine that a delay budget is exceeded after the second RDB value elapses in relation to the time reference. Accordingly, the remote unit 102 may be used for determining a delay budget based on a RDB.

[0036] In certain embodiments, a network unit 104 may transmit, from a network device to a UE, DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling. A time reference is determined based on the DCI; it is determined whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, a second RDB value is set to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, a second RDB value is determined based on the first RDB value and the set of UL slots; and it is determined that a delay budget is exceeded after the second RDB value elapses in relation to the time reference. Accordingly, the network unit 104 may be used for determining a delay budget based on a RDB.

[0037] Eigure 2 depicts one embodiment of an apparatus 200 that may be used for determining a delay budget based on a RDB. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

[0038] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0039] The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

[0040] The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0041] The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, a liquid crystal display (“UCD”), a light emitting diode (“FED”) display, an organic light emitting diode (“OEED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0042] In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

[0043] In certain embodiments, the receiver 212 receives DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling. In various embodiments, the processor 202: determines a time reference based on the DCI; determines whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, sets a second RDB value to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, determines a second RDB value based on the first RDB value and the set of UL slots; and determines that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

[0044] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

[0045] Figure 3 depicts one embodiment of an apparatus 300 that may be used for determining a delay budget based on a RDB. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0046] In certain embodiments, the transmitter 310 transmits, to a UE, DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling. A time reference is determined based on the DCI; it is determined whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, a second RDB value is set to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, a second RDB value is determined based on the first RDB value and the set of UL slots; and it is determined that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

[0047] It should be noted that one or more embodiments described herein may be combined into a single embodiment.

[0048] In certain embodiments, a service-oriented design may have extended reality (“XR”) traffic characteristics (e.g., a) variable packet arrival rate: packets coming at 30-120 frames per second with some jitter, b) packets having variable and large packet size, c) bidirectional prediction image (“B”) and/or predicted image (“P”) (“B/P”) -frames being dependent on intracoded (“I”)-frames, d) presence of multiple traffic and/or data flows such as pose and video scene in uplink) can enable more efficient (e.g., in terms of satisfying XR service requirements for a greater number of UEs (“UEs”), or in terms of UE power saving) for XR service delivery.

[0049] In some embodiments, a latency requirement for XR traffic at a radio access network (“RAN”) side (e.g., air interface) is modelled as packet delay budget (“PDB”). The PDB is a limited time budget for a packet to be transmitted over the air from a gNB to a UE. A delay budget can be also defined for an application data unit (“ADU”), referred to as (“ADB”). A packet data unit (“PDU”) set may refer to a PDU and/or an ADU.

[0050] In various embodiments, if a scheduler is aware of delay budgets for a packet and/or ADU, a gNB may take this knowledge into account in scheduling transmissions (e.g., by giving priority to transmissions close to their delay budget limit, and by not scheduling (e.g., UL) transmissions for which the delay budget is exceeded or going to be exceeded very soon; the UE can also take advantage of such knowledge to determine 1) if an UL transmission (e.g., physical uplink control channel (“PUCCH”) in response to physical downlink shared channel (“PDSCH”), UL pose, or physical uplink shared channel (“PUSCH”)) corresponding to a transmission that exceeds its delay budget can be dropped (additionally, no need to wait for re-transmission of a PDSCH and no need to keep the erroneously received PDSCH in buffer for soft combining with a re-transmission that never occurs) or 2) how much of its channel occupancy time in case of using unlicensed spectrum can be shared with the gNB.

[0051] In certain embodiments, a RDB: 1) for a DL transmission can be indicated to a UE in DCI (e.g., for a packet of a video frame, slice of a video frame, and/or an ADU) or via a MAC- CE (e.g., for an ADU/video frame/slice); and 2) for an UL transmission can be indicated to the gNB via an UL transmission such as uplink control information (“UCI”), PUSCH transmission, and so forth. Described herein are mechanisms to indicate such RDB.

[0052] In various embodiments, devices and/or network nodes such as gNBs operate in an unlicensed spectrum may be required to perform listen-before-talk (“LBT”) (e.g., also referred to as channel sensing) prior to being able to transmit in an unlicensed spectrum. If the device and/or network node performing LBT does not detect the presence of other signals in the channel, the medium and/or channel is considered for transmission. In a frame based equipment (“FBE”) mode of operation (e.g., which is intended for environments where the absence of other technologies is guaranteed e.g., by level of regulations, private premises policies, and so forth), the device and/or the network node performs LBT in an idle period and once acquired the channel and/or medium, the device and/or network node can communicate within the non-idle time of a fixed frame period duration (e.g., referred to as COT (channel occupancy time)). In current specifications and/or regulations, the idle time is not shorter than the maximum of 5% of the fixed frame period (“FFP”) and 100 microseconds.

[0053] Figure 4 is a timing diagram illustrating one embodiment of a fixed frame period structure 400. The fixed frame period structure 400 includes a COT 402 and idle 404 period that together extend for a fixed frame period 406.

[0054] In certain embodiments, a UE can perform channel sensing and access a channel if it senses the channel to be idle. UE initiated channel occupancy (“CO”) may be useful especially in low-latency applications, wherein having UL data to be sent in configured grant resources is allowed to initiate a CO.

[0055] In various embodiments, XR is an umbrella term for different types of realities including: 1) virtual reality (“VR”) is a rendered version of a delivered visual and audio scene - the rendering is designed to mimic the visual and audio sensory stimuli of the real world as naturally as possible to an observer or user as they move within the limits defined by the application - virtual reality usually, but not necessarily, requires a user to wear a head mounted display (“HMD”) to completely replace the user's field of view with a simulated visual component, and to wear headphones, to provide the user with the accompanying audio - some form of head and motion tracking of the user in VR is usually also necessary to allow the simulated visual and audio components to be updated in order to ensure that, from the user's perspective, items and sound sources remain consistent with the user's movements - additional means to interact with the virtual reality simulation may be provided but are not strictly necessary; 2) augmented reality (“AR”) is when a user is provided with additional information or artificially generated items or content overlaid upon their current environment - such additional information or content will usually be visual and/or audible and their observation of their current environment may be direct, with no intermediate sensing, processing and rendering, or indirect, where their perception of their environment is relayed via sensors and may be enhanced or processed; and/or 3) mixed reality (“MR”) is an advanced form of AR where some virtual elements are inserted into the physical scene with the intent to provide the illusion that these elements are part of the real scene.

[0056] In certain embodiments, XR refers to all real -and- virtual combined environments and human-machine interactions generated by computer technology and wearables. It includes representative forms such as AR, MR, and VR and the areas interpolated among them. The levels of virtuality range from partially sensory inputs to fully immersive VR. A key aspect of XR is the extension of human experiences especially relating to the senses of existence (e.g., represented by VR) and the acquisition of cognition (e.g., represented by AR).

[0057] In certain embodiments, many of the XR and configured grant (“CG”) use cases are characterized by quasi-periodic traffic (e.g., with possible jitter) with high data rate in DL (e.g., video steam) combined with the frequent UL (e.g., pose and/or control update) and/or UL video stream. Both DL and UL traffic are also characterized by relatively strict PDB. The set of anticipated XR and CG services has a certain variety and characteristics of the data streams (e.g., video) may change “on-the-fly”, while the services are running over NR. Therefore, additional information on the running services from higher layers, e.g., the quality of service (“QoS”) flow association, frame-level QoS, ADU-based QoS, XR specific QoS and so forth may be beneficial to facilitate informed choices of radio parameters. XR application awareness by UE and gNB may improve user experience, improve an NR system capacity in supporting XR services, and reduce the UE power consumption. An ADU may be the smallest unit of data that can be processed independently by an application (e.g., such as processing for handling out-of-order traffic data).

[0058] In some embodiments, a latency requirement of XR traffic in RAN side (i.e., air interface) is modelled as a packet delay budget (“PDB”). The PDB may be a limited time budget for a packet to be transmitted over the air from a gNB to a UE. For a given packet, the delay of the packet incurred in an air interface is measured from the time that the packet arrives at the gNB to the time that it is successfully transferred to the UE. If the delay is larger than a given PDB for the packet, then the packet is said to violate PDB, otherwise the packet is said to be successfully delivered. The value of PDB may vary for different applications and traffic types, which may be 10-20 ms depending on the application.

[0059] In various embodiments, a 5G arrival time of data bursts on a downlink may be quasi-periodic (e.g., periodic with jitter). Some of the factors leading to jitter in burst arrival include varying server render time, encoder time, real time transport protocol (“RTP”) packetization time, link between server and 5G gateway, and so forth. In certain embodiments, 3GPP agreed simulation assumptions for XR evaluation model DL traffic arrival jitter using truncated Gaussian distribution with mean: Oms, std. dev: 2ms, range: [-4ms, 4ms] (baseline), [- 5ms, 5ms] (optional).

[0060] In certain embodiments, applications have a certain delay requirement on an ADU that may not be adequately translated into packet delay budget requirements. For example, if the ADU delay budget (“ADB”) is 10 ms, then PDB can be set to 10ms only if all packets of the ADU arrive at the 5G system at the same time. If the packets are spread out, then ADU delay budget is measured either in terms of the arrival of the first packet of the ADU or the last packet of the ADU. In either case, a given ADB may result in different PDB requirements on different packets of the ADU. In some embodiments, specifying the ADB to the 5G system can be beneficial.

[0061] In some embodiments, labelling delay across different protocol stack layers from an XR server to a RAN may improve scheduling packets that approach their latency limits. If the delay budget is over, the packet may be dropped at any particular layer or the priority of the packet may be re-adjusted (e.g. deprioritized). Delay labelling across layers from the XR server to the RAN may be specified to assist and optimize RAN scheduling. For example, every packet is independently labelled with its own remaining delay after each processing block or after each transmission layer. Hence, the delay budget is decremented after each step in the transmission. Also, the jitter value for each packet can be included in the delay calculation during labelling. Hence, two packets may have the same QoS characteristics but can be allocated to two different QoS flows or treated differently for the RAN scheduling or at the UE processing because of their two different remaining latency budgets. Higher layers don’t have visibility about the residual packet delay budget. A packet which is successful after multiple hybrid automatic repeat request (“HARQ”) re-transmissions at a physical layer (“PHY”) has consumed more time than a packet which is successful from first attempt. Hence, a delay labelling could be useful across layers to possibly prioritize packets with close to expiry delay budget.

[0062] In various embodiments, how to indicate a RDB may be made to a UE or from the UE to a gNB. In certain embodiments, an effect of jitter may be taken into account in determining a delay budget of a packet as such metric is more relevant from an XR application perspective compared to a PDB metric. In particular, a deadline budget (“DLB”) of a packet is defined with respect to a time reference corresponding to zero jitter. Further, described herein are mechanisms to indicate a RDB to a UE or from the UE to a gNB, and the RDB may be defined according to any delay metric such as PDB, DLB, or ADB. The embodiments herein may be applicable to delay labelling performed across layers. [0063] In some embodiments, it should be noted that, symbol, slot, subslot, and/or transmission time interval (“TTI”) can be a time unit with a particular duration (e.g., symbol could be a fraction and/or percentage of an OFDM symbol length associated with a particular subcarrier spacing (“SCS”)). An UL transmission (e.g., UL transmission burst) may include multiple transmissions (e.g., of the same and/or different priority in case a priority is associated with the transmissions) potentially with gaps between the transmissions, wherein the gaps are short enough in duration to not necessitate performing a channel sensing and/or LBT operation between the transmissions.

[0064] In various embodiments, sharing a COT implies that a device or node with which the COT is shared can forego an indicated or configured channel access category and/or type and instead apply and/or perform a channel access according to a category and/or type whose characteristic includes a generally shorter sensing period, an increased likelihood for the channel sensing to result in being able to transmit, or no required sensing period prior to transmission in the shared COT.

[0065] In certain embodiments, a UE and a gNB may know which TBs are associated with a packet and/or an ADU (e.g., by means of a DCI indication or a MAC-CE indication).

[0066] In a first set of embodiments, there may be a RDB indication in DCI in which DCI schedules a PDSCH.

[0067] In a first embodiment of the first set of embodiments: 1) a gNB transmits a DCI; 2) the DCI schedules a DL transmission (e.g., a PDSCH transmission); 3) the DCI indicates, in a first DCI field, a RDB for an ADU (e.g., video-frame and/or video-slice) associated with the PDSCH transmission and/or a RDB for an IP (Internet Protocol) packet associated with the PDSCH transmission; 4) the first DCI field is configured to have ‘n’ bits, wherein the DCI indicates a RDB out of at most 2 ^A n possible RDBs; and/or 5) the delay budget for the ADU and/or packet is exceeded after the remaining budget is elapsed from a time reference.

[0068] In certain examples of the first set of embodiments: 1) ‘n=nl+n2’, wherein ‘n 1 ’ bits indicate an RDB for the video frame and/or slice, and ‘n2’ bits for the IP packet; 2) the RDB for the ADU (e.g., referred to as R-ADB) may be determined as the RDB of the IP packet plus the RDB indicated via ‘nl’ bits; 3) the ‘n’ bit-field includes a resource indication value (“RTV”) corresponding to a scaled RDB ), which indicates DL packet RDB, and a length ^LrBs , which RB _start + ^LrBs indicates a scaled ADU RDB. The resource indication value is defined by: i , else , not exceed N^ ^e _P — RBstart, wherein N^ ^e _P refers to a maximum scaled RDB for an ADU (e.g., 5 or 10 ms), the packet RDB can be _an d the ADU RDB can be A*(B _start + ^LrBs ), wherein ‘A’ is fixed in the specifications, can be SCS dependent, or can be configured by higher layer signaling; 3) the first DCI field can be a part of a time domain resource allocation (“TDRA”) indication field in the DCI: the indicated row of TDRA, in addition to KO, start and length indicator value (“SLIV”), and mapping type, can indicate one or both of a packet RDB, and an ADU RDB; 4) a set of possible RDBs may include the delay values in ms or in slots or in symbols unit (e.g., example sets: {0, 1, 2, 3} ms and/or slots; {0, 1, 2.5, 5} ms and/or slots; multiples of a configured, fixed, or dynamically indicated value such as 2.5 ms, such as {0, 2.5, 5} ms; multiple of minimum configured KO (the time gap between DCI scheduling PDSCH and scheduled PDSCH) or KI (the time gap between scheduled PDSCH and corresponding HARQ acknowledgement (“ACK”) (“HARQ-ACK”)) or K2 (the time gap between DCI scheduling PUSCH and the scheduled PUSCH)), a) the set of RDB values may be different for the ADU and the IP packet, b) the indicated RDB value can mean the RDB is at least that value (e.g., in case of {0, 2.5, 5} ms if the ‘5’ is indicated, it could mean the delay budget is at least 5ms); 5) the time reference can be a) the slot in which the DCI is sent, b) the slot in which the PDSCH is transmitted and/or ended, c) the slot in which the acknowledgment in response to the PDSCH is transmitted and/or expected (e.g., for a limited set of RDB values, a later time reference may provide more accurate RDB, e.g., for the right hand side and/or higher end of the set of RDB values), cl) e.g., if the RDB set is {0,1, 2, 3} ms, if Kl=lms (e.g., KI is the indicated value in the PDSCH-to-HARQ_feedback timing indicator field in the DCI), then for an actual PDB=4 ms from the time DCI is sent, the DCI indicates ‘3’, which if the time reference is selected to be the slot including the acknowledgment, the UE can determine PDB=4 ms (Kl+RDB_in_DCI), whereas if the time reference is the slot including the DCI, the UE can determine the PDB is at least 3ms as opposed to 4ms, c2) e.g., if the RDB set is {0,1, 2, 5} ms, if Kl=l, then for a PDB=3 ms from the time the DCI is sent, the DCI indicates ‘2’, which if the time reference is selected to be the slot including the acknowledgment, the UE can determine PDB=3 ms, whereas if the time reference is the slot including the DCI, the UE can determine the PDB is at least 2ms, if KI =2, then for a PDB=3 ms from the DCI, if the time reference is selected to be the slot including the acknowledgment, the DCI indicates ‘ 1 ’the UE can determine PDB=3 ms, whereas if the time reference is the slot including the DCI, the DCI indicates ‘2’, and the UE can determine the PDB is at least 2ms, d) the slot in which the associated pose is transmitted or with respect to nearest configured grant resource for the pose, for each DL packet, the UE can determine one or more corresponding UL pose(s), and the number of corresponding UL poses can depend on frame per second (“FPS”) rate of video traffic, UL pose periodicity (e.g., 4ms or 5ms), the packet is part of an I-frame and/or slice or a P-frame and/or P-slice; 6) the PDB for the packet is determined to be the indicated RDB in the DCI plus and/or minus a function of the jitter associated with the packet (calculated based on the expected packet arrival rate (e.g., 60 FPS)), e.g., the function would be ‘y(x)=x’ or y(x)=Quantize(x), where ‘x’ is the jitter with respect to a nominal frame arrival time corresponding to zero jitter; 7) (e.g., semi-statically configured) UL slots (which may occur between DL slots) are not counted in the indicated value by DCI (e.g., the actual PDB includes, counts, and/or considers the UL slots), slots with flexible symbols are counted in the indicated RDB value by DCI, e.g., if RDB indicated by DCI indicates ‘2’ms, from the time reference, the UE starts counting slots to reach 2ms, wherein UL slots from the time reference are not counted in the indicated RDB - for example, there could be 1 ms span of UL slots from the time reference till 2ms span of DL slots - in that case, the actual PDB is 2+1=3 ms, whereas the indicated RDB is 2ms - not counting UL slots could be useful depending on the time division duplex (“TDD”) configuration, for instance, if the RDB set is {0, 1,2,3} ms, if PDB=4ms from a time reference with the following pattern after the time reference {U,U,U, D}, where each of ‘U’, and ‘D’ represents 1 ms uplink and 1 ms downlink respectively, then the DCI could indicate RDB=3ms, the PDB is considered exceeded after {U,U, U}, however, if only DL slots are counted, the DCI could indicate RDB=2ms, and the PDB is exceeded after {U,U,U,D}, the DCI indicates whether the UL slots from the time reference have been counted in the PDB value indicated by the DCI, and higher layer signaling (e.g., radio resource control (“RRC”) or MAC-CE) indicates whether the UL slots from the time reference have been counted in the PDB value indicated by the DCI, e.g., could be based on the TDD configuration; 8) RDB sets may be different for I frames and/or slices and for P frame and/or slices; and/or 9) if the same DCI format is used to schedule a traffic that is not associated with an RDB value (e.g., enhanced mobile broadband (“eMBB”) traffic which may be able to tolerate some latency), one value of set of RDBs could indicate that RDB is not applicable (or RDB can be out-of-range).

[0069] In a second set of embodiments, there may be group-common DCI.

[0070] In a first embodiment of the second set of embodiments: 1) a gNB transmits a group-common DCI with a group-common DCI format (e.g., DCI format 2-0); 2) the DCI includes N fields, wherein each field indicates a RDB for an ADU (e.g., video-frame and/or video-slice) associated with one or more PDSCH transmissions and/or a RDB for an internet protocol (“IP”) packet associated with one or more PDSCH transmissions; and/or 3) the delay budget is exceeded after the remaining budget is elapsed from a time reference. [0071] In some examples of the first embodiment of the second set of embodiments: 1) a time reference is a first slot that is at least ‘X’ symbols after the last symbol of the physical downlink control channel (“PDCCH”) with the DCI format, wherein ‘X’ is fixed in the specifications, and depends on the UE processing capability and SCS; 2) the UE starts a counter and/or timer with the determined RDB based on the DCI, and every slot (or time unit) the counter and/or timer is decremented, when the counter and/or timer expires, the UE determines the delay budget is exceeded for the packet and/or the ADU, a) the UE indicates to higher layers and/or application layer that the delay budget is exceeded for the packet and/or the ADU, b) if the counter and/or timer is running, and another DCI is received indicating an RDB for the ADU and/or packet, the counter and/or timer is restarted with the newly indicated RDB values; 3) the ADU and/or the packet index is indicated in each field of the ‘N’ fields; 4) the UE determines the ADU index based on a nominal frame arrival time; and/or 5) the RDB is selected from a set of RDB values, wherein the set is determined based on one or more of the following: a) the PDCCH monitoring periodicity of the DCI format, b) a number of bits allocated to indicating RDB in each field of the ‘N’ fields, and c) if 2 bits allocated for RDB indication, and the PDCCH monitoring periodicity is ‘P’ ms, the set could be {0, 0.33, 0.67, l}x ‘P’ms, wherein if the RDB is indicated to be ‘P’ ms, it means the RDB is at least ‘P’ ms. If a higher layer parameter is configured, the DCI format can include/indicate the ‘N’ fields (containing the RDB).

[0072] In a third set of embodiments, there may be a RDB indication in a MAC-CE.

[0073] In a first embodiment of the third set of embodiments: 1) a gNB transmits a DCI; 2) the DCI schedules a PDSCH transmission; 3) the PDSCH includes a MAC-CE indication; 4) the MAC-CE indicates a RDB for an ADU (e.g., video-frame and/or video-slice) associated with the PDSCH transmission and/or a RDB for an IP packet associated with the PDSCH transmission; and/or 5) the delay budget is exceeded after the remaining budget is elapsed from a time reference.

[0074] In various embodiments of the first embodiment of the third set of embodiments: 1) a DCI scheduling a transport block (“TB”) of a packet indicates an RDB of the packet, and the MAC-CE indicates the RDB of the ADU associated with the packet; 2) the MAC entity shall, if the MAC entity receives the MAC-CE indication on a serving cell, indicates to lower layers the information regarding the RDB of an ADU; 3) the time reference may be: a) the slot in which the DCI is sent; b) the slot in which the PDSCH is transmitted and/or ended; c) the slot in which the acknowledgment in response to the PDSCH is transmitted and/or expected; and/or d) a positive fixed and/or configured offset (e.g., 3ms) with respect to the slot in which the acknowledgment in response to the PDSCH is transmitted and/or expected (e.g., if a MAC-CE indicates 1 ms, then 3 ms after the slot in which the acknowledgment in response to the PDSCH is transmitted and/or expected, the PDB is 1 ms) and/or an offset with respect to the slot in which the MAC-CE is received; and/or 4) the MAC-CE indicates RDB for more than one ADU/IP-packet (e.g., T ADU/IP-packets or combination of thereof), and the MAC-CE indicates also the corresponding identifiers of the more than one ADU/IP-packet. The number ‘f can eb configured or specified in the specifications.

[0075] In a second embodiment of the third set of embodiments: 1) a gNB transmits a DCI; 2) a DCI schedules a PDSCH transmission; 3) the PDSCH includes a MAC-CE indication; 4) the MAC-CE indicates a set of RDBs for an ADU (e.g., video-frame and/or video-slice) associated with the PDSCH transmission and/or a set of RDBs for an IP packet associated with the PDSCH transmission; and/or 5) a second DCI indicates an RDB for ADU and/or packet wherein the RDB is selected from the set indicated by the MAC-CE. The second DCI can be sent/can be applicable not earlier than a certain time from the time the MAC-CE is sent.

[0076] In one embodiment of the third set of embodiments, for an UL packet and/or ADU, the RDB can be indicated in an UL pose. The UL pose can include the packet and/or ADU identifier (“ID”) (“ADU-ID”).

[0077] In certain embodiments, a UE is not expected to: 1) receive a DCI scheduling a TB associated with an ADU and/or packet that its corresponding delay budget is exceeded or is going to be exceeded prior to its corresponding HARQ-ACK can be sent; and/or 2) decode a PDSCH associated with an ADU and/or packet that its corresponding delay budget is exceeded.

[0078] Figure 5 is a flow chart diagram illustrating one embodiment of a method 500 for determining a delay budget based on a RDB. In some embodiments, the method 500 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 500 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0079] In various embodiments, the method 500 includes receiving 502, at a UE, DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling. In some embodiments, the method 500 includes determining 504 a time reference based on the DCI. In certain embodiments, the method 500 includes determining 506 whether a set of UL slots from the time reference are counted in the first RDB value. In various embodiments, the method 500 includes, in response to determining that the set of UL slots are counted in the first RDB value, setting 508 a second RDB value to be the first RDB value. In some embodiments, the method 500 includes, in response to determining that the set of UL slots are not counted in the first RDB value, determining 510 a second RDB value based on the first RDB value and the set of UL slots. In certain embodiments, the method 500 includes determining 512 that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

[0080] In certain embodiments, the set of RDB values is indicated by a MAC-CE. In some embodiments, the time reference comprises a slot in which the UE is expected to provide an acknowledgment in response to the DCI. In various embodiments, whether UL slots are counted in the first RDB value is indicated by higher layer signaling.

[0081] In one embodiment, whether UL slots are counted in the first RDB value is determined by aTDD configuration. In certain embodiments, the DCI indicates athird RDB value, the first RDB value corresponds to a packet delay budget, and the third RDB value corresponds to an ADU delay budget. In some embodiments, the set of RDB values is determined based on higher layer signaling and whether the DCI is associated with an I frame or a P frame.

[0082] In various embodiments, the DCI comprises a group-common DCI format. In one embodiment, the set of RDB values is determined based on a PDCCH monitoring periodicity corresponding to the group-common DCI format.

[0083] In certain embodiments, the set of RDB values is determined based on a TDD configuration. In some embodiments, the UE is not expected to: receive a second DCI scheduling a TB associated with an ADU, a packet, or a combination thereof having a corresponding delay budget that is exceeded; decode a PDSCH associated with the ADU, the packet, or the combination thereof having a corresponding delay budget that is exceeded; or a combination thereof.

[0084] Figure 6 is a flow chart diagram illustrating another embodiment of a method 600 for determining a delay budget based on a RDB. In some embodiments, the method 600 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 600 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0085] In various embodiments, the method 600 includes transmitting 602, from a network device to a UE, DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling. A time reference is determined based on the DCI; it is determined whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, a second RDB value is set to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, a second RDB value is determined based on the first RDB value and the set of UL slots; and it is determined that a delay budget is exceeded after the second RDB value elapses in relation to the time reference. [0086] In certain embodiments, the set of RDB values is indicated by a MAC-CE. In some embodiments, the time reference comprises a slot in which the UE is expected to provide an acknowledgment in response to the DCI. In various embodiments, whether UL slots are counted in the first RDB value is indicated by higher layer signaling.

[0087] In one embodiment, whether UL slots are counted in the first RDB value is determined by aTDD configuration. In certain embodiments, the DCI indicates athird RDB value, the first RDB value corresponds to a packet delay budget, and the third RDB value corresponds to an ADU delay budget. In some embodiments, the set of RDB values is determined based on higher layer signaling and whether the DCI is associated with an I frame or a P frame.

[0088] In various embodiments, the DCI comprises a group-common DCI format. In one embodiment, the set of RDB values is determined based on a PDCCH monitoring periodicity corresponding to the group-common DCI format.

[0089] In certain embodiments, the set of RDB values is determined based on a TDD configuration. In some embodiments, the UE is not expected to: receive a second DCI scheduling a TB associated with an ADU, a packet, or a combination thereof having a corresponding delay budget that is exceeded; decode a PDSCH associated with the ADU, the packet, or the combination thereof having a corresponding delay budget that is exceeded; or a combination thereof.

[0090] In one embodiment, an apparatus comprises a UE. The apparatus further comprises: a receiver that receives DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling; and a processor that: determines a time reference based on the DCI; determines whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, sets a second RDB value to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, determines a second RDB value based on the first RDB value and the set of UL slots; and determines that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

[0091] In certain embodiments, the set of RDB values is indicated by a MAC-CE.

[0092] In some embodiments, the time reference comprises a slot in which the UE is expected to provide an acknowledgment in response to the DCI.

[0093] In various embodiments, whether UL slots are counted in the first RDB value is indicated by higher layer signaling.

[0094] In one embodiment, whether UL slots are counted in the first RDB value is determined by a TDD configuration. [0095] In certain embodiments, the DCI indicates a third RDB value, the first RDB value corresponds to a packet delay budget, and the third RDB value corresponds to an ADU delay budget.

[0096] In some embodiments, the set of RDB values is determined based on higher layer signaling and whether the DCI is associated with an I frame or a P frame.

[0097] In various embodiments, the DCI comprises a group-common DCI format.

[0098] In one embodiment, the set of RDB values is determined based on a PDCCH monitoring periodicity corresponding to the group-common DCI format.

[0099] In certain embodiments, the set of RDB values is determined based on a TDD configuration.

[0100] In some embodiments, the UE is not expected to: receive a second DCI scheduling a TB associated with an ADU, a packet, or a combination thereof having a corresponding delay budget that is exceeded; decode a PDSCH associated with the ADU, the packet, or the combination thereof having a corresponding delay budget that is exceeded; or a combination thereof.

[0101] In one embodiment, a method in a UE comprises: receiving DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling; determining a time reference based on the DCI; determining whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, setting a second RDB value to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, determining a second RDB value based on the first RDB value and the set of UL slots; and determining that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

[0102] In certain embodiments, the set of RDB values is indicated by a MAC-CE.

[0103] In some embodiments, the time reference comprises a slot in which the UE is expected to provide an acknowledgment in response to the DCI.

[0104] In various embodiments, whether UL slots are counted in the first RDB value is indicated by higher layer signaling.

[0105] In one embodiment, whether UL slots are counted in the first RDB value is determined by a TDD configuration.

[0106] In certain embodiments, the DCI indicates a third RDB value, the first RDB value corresponds to a packet delay budget, and the third RDB value corresponds to an ADU delay budget.

[0107] In some embodiments, the set of RDB values is determined based on higher layer signaling and whether the DCI is associated with an I frame or a P frame. [0108] In various embodiments, the DCI comprises a group-common DCI format.

[0109] In one embodiment, the set of RDB values is determined based on a PDCCH monitoring periodicity corresponding to the group-common DCI format.

[0110] In certain embodiments, the set of RDB values is determined based on a TDD configuration.

[0111] In some embodiments, the UE is not expected to: receive a second DCI scheduling a TB associated with an ADU, a packet, or a combination thereof having a corresponding delay budget that is exceeded; decode a PDSCH associated with the ADU, the packet, or the combination thereof having a corresponding delay budget that is exceeded; or a combination thereof.

[0112] In one embodiment, an apparatus comprises a network device. The apparatus further comprises: a transmitter that transmits, to a UE, DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling, wherein: a time reference is determined based on the DCI; it is determined whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, a second RDB value is set to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, a second RDB value is determined based on the first RDB value and the set of UL slots; and it is determined that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

[0113] In certain embodiments, the set of RDB values is indicated by a MAC-CE.

[0114] In some embodiments, the time reference comprises a slot in which the UE is expected to provide an acknowledgment in response to the DCI.

[0115] In various embodiments, whether UL slots are counted in the first RDB value is indicated by higher layer signaling.

[0116] In one embodiment, whether UL slots are counted in the first RDB value is determined by a TDD configuration.

[0117] In certain embodiments, the DCI indicates a third RDB value, the first RDB value corresponds to a packet delay budget, and the third RDB value corresponds to an ADU delay budget.

[0118] In some embodiments, the set of RDB values is determined based on higher layer signaling and whether the DCI is associated with an I frame or a P frame.

[0119] In various embodiments, the DCI comprises a group-common DCI format.

[0120] In one embodiment, the set of RDB values is determined based on a PDCCH monitoring periodicity corresponding to the group-common DCI format. [0121] In certain embodiments, the set of RDB values is determined based on a TDD configuration.

[0122] In some embodiments, the UE is not expected to: receive a second DCI scheduling a TB associated with an ADU, a packet, or a combination thereof having a corresponding delay budget that is exceeded; decode a PDSCH associated with the ADU, the packet, or the combination thereof having a corresponding delay budget that is exceeded; or a combination thereof.

[0123] In one embodiment, a method in a network device comprises: transmitting, to a UE, DCI indicating a first RDB value from a set of RDB values indicated by higher layer signaling, wherein: a time reference is determined based on the DCI; it is determined whether a set of UL slots from the time reference are counted in the first RDB value; in response to determining that the set of UL slots are counted in the first RDB value, a second RDB value is set to be the first RDB value; in response to determining that the set of UL slots are not counted in the first RDB value, a second RDB value is determined based on the first RDB value and the set of UL slots; and it is determined that a delay budget is exceeded after the second RDB value elapses in relation to the time reference.

[0124] In certain embodiments, the set of RDB values is indicated by a MAC-CE.

[0125] In some embodiments, the time reference comprises a slot in which the UE is expected to provide an acknowledgment in response to the DCI.

[0126] In various embodiments, whether UL slots are counted in the first RDB value is indicated by higher layer signaling.

[0127] In one embodiment, whether UL slots are counted in the first RDB value is determined by a TDD configuration.

[0128] In certain embodiments, the DCI indicates a third RDB value, the first RDB value corresponds to a packet delay budget, and the third RDB value corresponds to an ADU delay budget.

[0129] In some embodiments, the set of RDB values is determined based on higher layer signaling and whether the DCI is associated with an I frame or a P frame.

[0130] In various embodiments, the DCI comprises a group-common DCI format.

[0131] In one embodiment, the set of RDB values is determined based on a PDCCH monitoring periodicity corresponding to the group-common DCI format.

[0132] In certain embodiments, the set of RDB values is determined based on a TDD configuration.

[0133] In some embodiments, the UE is not expected to: receive a second DCI scheduling a TB associated with an ADU, a packet, or a combination thereof having a corresponding delay budget that is exceeded; decode a PDSCH associated with the ADU, the packet, or the combination thereof having a corresponding delay budget that is exceeded; or a combination thereof.

[0134] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.