WO2023199291A1

WO2023199291A1 - Quality of service determination for video frame transmission

Info

Publication number: WO2023199291A1
Application number: PCT/IB2023/053873
Authority: WO
Inventors: Hossein Bagheri; Vijay Nangia; Joachim Lohr; Razvan-Andrei Stoica
Original assignee: Lenovo (Singapore) Pte. Ltd.
Priority date: 2022-04-15
Filing date: 2023-04-15
Publication date: 2023-10-19

Abstract

Various aspects of the present disclosure relate to a device that incorporates and a method that provides for wireless communication with a quality of service (QoS) to meet a latency requirement. The QoS may also be defined in terms of error rate. The method includes receiving a control message that includes a scheduling assignment for a transmission by the user device. In response to determining that the transmission is associated with a portion of a video frame, the method includes determining a Quality of Service (QoS) parameter associated with the portion of the video frame from among at least a first QoS and a second QoS. The first QoS provides at least one of a lower error rate and a lower latency than the second QoS. The method includes transmitting the transmission according to the first QoS in response to determining that the transmission is associated with the first QoS.

Description

QUALITY OF SERVICE DETERMINATION FOR VIDEO FRAME TRANSMISSION

RELATED APPLICATION

[0001] This application claims priority to U.S. provisional application No. 63/331,767, filed April 15, 2022, the content of which is fully incorporated herein by reference.

TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to wireless communications scheduling to meet a latency and/or error rate quality of service requirement.

BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G.

[0004] A UE can communicate with a gNB to support extended Reality (XR) features. XR refers to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. XR is an umbrella term for different types of realities including Virtual reality (VR), Augmented reality (AR), and Mixed reality (MR), 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 (represented by VR) and the acquisition of cognition (represented by AR).

SUMMARY

[0005] The present disclosure relates to methods, apparatuses, and systems that support wireless communication with a quality of service (QoS) to meet a latency requirement for a portion of a video frame. According to one aspect, the QoS may also be defined in terms of error rate. A user device includes a transceiver including at least one transmitter and at least one receiver that enable the user device to communicate with a second device such as a network device. A communication manager is communicatively coupled to the transceiver. The communication manager receives a control message that includes a scheduling assignment for a transmission by the user device. In response to determining that the transmission is associated with a portion of a video frame, the communication manager determines a QoS parameter associated with the portion of the video frame from among at least a first QoS and a second QoS. The first QoS provides at least one of a lower error rate and a lower latency than the second QoS. In response to determining that the transmission is associated with the first QoS, the user device transmits the transmission according to the first QoS.

[0006] Some implementations of the method and apparatuses described herein may further include a user device that incorporates or a method that provides for wireless communication by the user device. The method includes receiving a control message that includes a scheduling assignment for a transmission by the user device. In response to determining that the transmission is associated with a portion of a video frame, the method includes determining a QoS parameter associated with the portion of the video frame from among at least a first QoS and a second QoS. The first QoS provides at least one of a lower error rate and a lower latency than the second QoS. In response to determining that the transmission is associated with the first QoS, the method includes transmitting the transmission according to the first QoS. [0007] In some implementations of the method and apparatuses described herein, a method for wireless communication by a network device is provided. The method includes, in response to determining that a pending uplink transmission is associated with a portion of a video frame, transmitting a control message that includes: (i) a scheduling assignment for the transmission by the user device; and (ii) a first control field having a value that is utilized by the user device to identify which of a plurality of QoS parameters to associate with the portion of the video frame. The QoS parameters includes a first QoS and a second QoS. The first QoS provides at least one of a lower error rate and a lower latency than the second QoS. The method includes configuring the network device to receive the transmission from the user device according to a specific one of the plurality of QoS parameters that corresponds to the value in the first control field. The method includes receiving the transmission according to the specific QoS.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] FIG. 1 illustrates an example of a wireless communications system that supports wireless communication with quality of service for appropriate latency and error rate requirements for video frame transmissions, in accordance with aspects of the present disclosure.

[0009] FIGs. 2 through 7 are example communication diagrams of transmission between a user device and base node of FIG. 1 illustrating wireless communication with indications of quality of service for transmissions, in accordance with aspects of the present disclosure.

[0010] FIG. 8 illustrates an example of a block diagram of a user device that supports wireless communication with a network device with an assigned transmission quality of service to meet a latency requirement, in accordance with aspects of the present disclosure.

[0011] FIG. 9 illustrates an example of a block diagram of a network device that supports scheduling and receiving wireless communication from a user device that transmits with an assigned quality of service to meet a latency requirement, in accordance with aspects of the present disclosure. [0012] FIGs. 10 through 11 illustrate flowcharts of respective methods that support wireless communication with transmission quality of service to meet a latency requirement appropriate for a portion of a video frame, in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0013] Extended reality (XR) traffic between a radio access network (RAN) and a user equipment (UE) over an air interface is modeled as a packet delay budget (PDB). The PDB is a limited time budget for a data packet to be transmitted over the air from a base node to the UE or from the UE to the base node. A delay budget can be also defined for an Application Data Unit (ADU). An ADU is the smallest unit of data that can be processed independently by an application, such as processing for handling out-of-order traffic data.

[0014] 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. Augmented reality (AR) provides a user with additional information, artificially generated items, or content overlaid upon their current environment. 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.

[0015] In the field of video compression, a video frame is compressed using different algorithms with different advantages and disadvantages, centered mainly around the amount of data compression. These different algorithms for video frames are called picture types or frame types. The three major picture types used in the different video algorithms are I, P and B. They are different in the following characteristics: (i) Intra-coded (I)-frames are the least compressible but don't require other video frames to decode; (ii) Predicted (P)-frames can use data from previous frames to decompress and are more compressible than I-frames; and (iii) Bi-directional predicted (B)-frames can use both previous and forward frames for data reference to get the highest amount of data compression. XR traffic has a number of characteristics: (i) variable packet arrival rate: packets coming at 30 - 120 frames/second with some jitter; (ii) packets having variable and large packet size; (iii) B/P-frames being dependent on I-frames, and (iv) presence of multiple traffic/ data flows such as pose and video scene in uplink. A delay budget for video frame ADUs is especially important in XR traffic because of decoding requirements of video content. A video frame can be an I-frame, P- frame, or can be composed of I-slices, and/or P-slices. I-frames/I-slices are more important and larger than P-frames/P-slices. The importance is related to impact of late traffic on the ability to successfully decode and use the traffic.

[0016] Due to traffic size variation and traffic jitter, dynamic scheduling via Downlink Control Information (DCI) is quite relevant for XR. Given the limited DCI size, one approach to enable service-oriented design considering XR traffic characteristics is to allow a DCI field to indicate different values depending on XR traffic characteristics. In an example, an I- frame/slice can be considered to be more important than a P-frame/slice. In another example, Internet Protocol (IP) packets of an I-frame/slice that are reaching their delay budgets are of more importance. A “P0” power value indicated by the open-loop power control (OLPC) parameter set indication field in a DCI to boost the transmission power of an important transmission can indicate: (i) first P0 value for IP packets of the I-frame/I-slice that still have some delay budget left, and (ii) a second P0 value that is higher than the first P0 value for IP packets of the I-frame/I-slice that are reaching their delay budgets. To cater for packets with different reliability and/or latency requirements, the present disclosure identifies and enables some DCI fields to be allowed to indicate a value from different sets of values, wherein the sets correspond to different reliability and/or latency requirements.

[0017] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams, flowcharts that relate to identifying and enabling a control message, such as fields of downlink control information (DCI), to indicate a value from different sets of values. Each set corresponds to a QoS for different reliability and/or latency requirements. By using one or more embodiments, the present disclosure satisfies XR service requirements for a greater number of UEs and/or enhances UE power saving. Data packets with different reliability and/or latency requirements are catered to. [0018] FIG. 1 illustrates an example of a wireless communications system 100 that supports wireless communication with quality of service consideration for appropriate latency and error rate requirements for video frame transmissions, in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as a New Radio (NR) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0019] The one or more base stations 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the base stations 102 described herein may be, may include, or may be referred to as a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), a network device, or other suitable terminology. A base station 102 and a UE 104 may communicate via a communication link 108, which may be a wireless or wired connection. For example, a base station 102 and a UE 104 may wirelessly communicate over a user to user (Uu) interface.

[0020] A base station 102 may provide a geographic coverage area 110 for which the base station 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 110. For example, a base station 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a base station 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 110 may be associated with different base stations 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0021] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

[0022] The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. A UE 104 may be capable of communicating with various types of devices, such as the base stations 102, other UEs 104, or network equipment (e.g., the core network 106, a relay device, an integrated access and backhaul (IAB) node, or another network equipment), as shown in FIG. 1. Additionally, or alternatively, a UE 104 may support communication with other base stations 102 or UEs 104, which may act as relays in the wireless communications system 100.

[0023] A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 112. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to- everything (V2X) deployments, or cellular-V2X deployments, the communication link 112 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface. PC5 refers to a reference point where the UE 104 directly communicates with another UE 104 over a direct channel without requiring communication with the base station 102.

[0024] A base station 102 may support communications with the core network 106, or with another base station 102, or both. For example, a base station 102 may interface with the core network 106 through one or more backhaul links 114 (e.g., via an SI, N2, or another network interface). The base stations 102 may communication with each other over the backhaul links 114 (e.g., via an X2, Xn, or another network interface). In some implementations, the base stations 102 may communicate with each other directly (e.g., between the base stations 102). In some other implementations, the base stations 102 may communicate with each other indirectly (e.g., via the core network 106). In some implementations, one or more base stations 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communication with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0025] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for the one or more UEs 104 served by the one or more base stations 102 associated with the core network 106.

[0026] Some implementations of the method and apparatuses described herein may further include signaling or a handshake between a base node, such as base stations 102, and a user device, such as UEs 104, that indicate which transport blocks (TBs) are associated with a packet and/or an application data unit (ADU). In an example, the signaling or handshake can be downlink control information (DCI) indication or a medium access control (MAC) control element (CE) indication. In one or more embodiments, the base node and device can use a priority indication for priority of particular types of video transmission. In an example, I-frame/slice can have high priority and P-frame/slice may have low priority.

[0027] In the description that follows, the timing of transmissions and retransmissions of control channels and data channels supports latency and/or error rate requirements for portions of video frames and may be referred to as time units. Time units such as a symbol, slot, subslot, and transmission time interval (TTI) can have a particular duration. In an example, a symbol could be a fraction or percentage of an orthogonal frequency division multiplexing (OFDM) symbol length associated with a particular subcarrier spacing (SCS). In another example, an uplink (UL) transmission burst can be comprised of multiple transmissions. The multiple transmission can have the same priority, different priorities, or may have no associated priority. The multiple transmissions may include gaps between the transmissions that are short enough in duration to not necessitate performing a channel sensing or listen before transmit (LBT) operation between the transmissions.

[0028] Aspects of the present disclosure may apply to communicating in unlicensed spectrum using sidelink communication over the PC5 interface. Devices such as base stations 102 and UEs 104 can support one-to-one or one-to-many direct communication between devices sharing the unlicensed spectrum without network scheduling. Sharing a channel occupancy time (COT) implies that the device or base node with which the COT is shared can forego an indicated or configured channel access category/type. Instead, the device or base node can apply or perform a channel access according to a category/type whose characteristic includes: (i) a generally shorter sensing period; (ii) an increased likelihood for the channel sensing to result in being able to transmit; or (iii) no required sensing period prior to transmission in the shared COT.

[0029] According to a first embodiment of the disclosure, a first node, referred to elsewhere as a network node, schedules a transmission for a second node, referred to elsewhere as a user device, by signaling a control message, such as downlink control information (DCI). In an example, the first node is a base node such as a gNB and the second node is device such as a UE. The transmission can be an uplink (UL), a downlink (DL), or a sidelink (SL) transmission. The control message includes a first control field with a first value. The second node determines if the transmission is associated with a first QoS or with a second QoS, which are described below as being based on one or more of seven indications. The seven indications are illustrative and not an all-inclusive list. The QoS can be defined in terms of one or more of error rate, delay budget, content type, and frame/slice nature (e.g., I- frame/slice vs. P-frame/slice) for an ADU. In response to determining that the transmission is associated with the first QoS, the second node determines a second value based on the first value and prepares for the transmission based on the second value. In response to determining that the transmission is associated with the second QoS, the second node determines a third value based on the first value and prepares for the transmission based on the third value. The second node communicates with the first node according to the prepared transmission. In an example, the first value is an index indicated in a DCI field such as open loop power control field. The second value for an open loop power control parameter is selected based on the indicated index from a first set of configured values. The third value for an open loop power control parameter is selected based on the indicated index from a second set of configured values. Once the UE determines the transmission is associated with the first QoS, the transmission power is determined based on the second value for the open loop power control parameter. Once the UE determines the transmission is associated with the second QoS, the transmission power is determined based on the third value for the open loop power control parameter.

[0030] According to one or more aspects, the second node identifies the QoS (e.g., the first QoS or the second QoS) based on one or more of a plurality of different indications, which are described hereafter. A first indication is a previous uplink transmission, such as a scheduling request (SR) or a logical channel identifier (LCID) in a buffer status report (BSR), that indicates whether the data pending in a buffer of the second node, such as a UE 104, is at least mostly related to an I-frame or a P-frame. A second indication is the control message. In an example of interlaced transmission of I-slices and P-slices, the DCI of the control message indicates whether the scheduled TB corresponds to an I-slice or a P-slice. A third indication is a pattern for QoS. In an example of the third indication of the QoS, group of pictures (GoP) format, which specifies the order in which intra-frames and inter-frames are arranged, is based on a frame arrival rate such as 60 frames per second (FPS). In another example, the first and second nodes are aware of the format of previously transmitted frames, which indicates whether an I-frame or a P-frame is expected next, given the already transmitted frames.

[0031] A fourth indication is an additional indication in the control message or in a second control message, such as a group-common DCI, that explicitly or implicitly indicates the QoS. In an example, the implicit or explicit indication is a percentage of a data volume of an ADU that is not yet transmitted or scheduled for transmission, which may include or may not include TBs requiring/pending retransmission. In another example, the implicit or explicit indication is a remaining duration for which the transmissions correspond to an I- slice/frame or a P-slice/frame. The duration can be derived based on a physical downlink control channel (PDCCH) and search space monitoring periodicity corresponding to a group- common DCI format. The duration is one of a hypothetical, nominal, estimated, minimum, or expected duration and can be different than the actual transmission duration of an ADU. The expected duration can be calculated according to a reference transmission format. In an example, the reference transmission format is based on a set of common assumptions for transmissions between a UE and gNB, such as an assumed modulation and coding scheme (MCS), number of resource blocks (RBs), etc. With this implementation, the reference transmission format can be determined based on an indication in the second control message. In an example, the MCS for the reference transmission format is the indicated MCS in the second control channel or the scheduling DCI or a reference scheduling DCI such as the last DCI scheduling a transmission.

[0032] A fifth indication is when the second value is equal to the first value received within the first control field of the control message. The third value can be derived from the first value based on a mapping from a lookup table or by adding/subtracting a fixed offset.

[0033] A sixth indication is a QoS indication in a downlink (DL) DCI. If the QoS is indicated from UE to gNB (e.g., in a previous UL transmission), the gNB determines an updated QoS value based on the indicated QoS and the time the gNB schedules the UL transmission. The UE prepares the UL transmission based on the updated QoS value. If the QoS is indicated from gNB to UE (e.g., in a DCI command), the UE determines an updated QoS value based on the indicated QoS and the time the gNB schedules a DL transmission such as a PDSCH. The UE receives the DL transmission based on the updated QoS value. FIG. 2 is a communication diagram 200 of a downlink 201 with transmission of a DL DCI 202 containing QoS indication 204 followed after elapsed time “T” by a scheduled physical downlink shared channel (PDSCH) 206. The UE can determine an updated QoS, such as one of the first QoS and the second QoS, based on the indicated QoS in the DL DCI 202 and the time of the scheduled PDSCH ('T’) from the DL DCI. For instance, the UE determines a delay budget for the TB of the PDSCH or for the ADU associated with the PDSCH based on the indicated delay budget and the time ‘T’. The QoS is related to the delay budget. The updated delay budget would be the indicated delay budget minus ‘T’. The UE receives the scheduled PDSCH based on the updated QoS. Particular resource blocks and/or symbols and/or TB repetitions within the scheduled PDSCH may be selected to satisfy the updated QoS such as to prioritize TBs approaching a delay budget.

[0034] A seventh indication is an uplink QoS report and an uplink DCI transmitted on the downlink. The DCI control message schedules an UL transmission, and the UE selects the second value for a DCI field based on the first value indicated in the DCI field. Also, the third value for the DCI field is by default equal to the second value unless the QoS has been reported to gNB (e.g., certain time prior to receiving the DCI scheduling the UL transmission) or the reported QoS has been implicitly or explicitly acknowledged by the gNB prior to the DCI scheduling the UL transmission. In the latter case, the third value can be different than the second value. In an example, the first value is an index indicated in a DCI field such as beta offset indicator field. The second value for a beta offset is selected based on the indicated index from a first set of configured values, and the third value for the beta offset is selected based on the indicated index from a second set of configured values. Once the UE determines the transmission is associated with the first QoS, rate-matching of an Uplink Control Information (UCI) around PUSCH resources is determined based on the second value for the beta offset, and once the UE determines the transmission is associated with the second QoS, rate-matching of the UCI around PUSCH resources is determined based on the third value for the beta offset.

[0035] FIG. 3 presents communication diagram 300 of a downlink 301 and an uplink 302. A QoS report 304 is transmitted on the uplink 302. After a time “T” that is greater than or equal to a time unit “TO”, an uplink DCI 306 is transmitted on downlink 301 having an index 308 that indicates an element of one of Set 1 310a and Set 2 310b. The receiving UE determines whether the index 308 indicated in the UL DCI 306 scheduling the scheduled physical uplink shared channel (PUSCH) 312 on uplink 302 is selecting an element from Set 1 310a and Set 2 310b. The UE is provisioned with two or more sets of QoS elements. The elements define parameters of the respective QoS in terms of data latency and/or error rate. The determination is based on the QoS report 304 reported at least TO time units before the UL DCI 306. Set 1 310a and Set 2 310b can be configured by radio resource control (RRC) configuration. Alternatively, Set 2310b can be determined based on Set 1 310a.

[0036] In one or more embodiments, the present disclosure provides enhancements for specific DCI fields. In an example, the control message includes an open-loop power control (OLPC) parameter set indication. In a second embodiment, the base node, such as a gNB, transmits a DCI. The DCI schedules an UL transmission (e.g., a PUSCH transmission). The DCI indicates a first OLPC value for an open-loop power control parameter set indication. The UE determines a QoS parameter. In response to determining the QoS parameter has a first QoS value or has a value smaller than or equal to a threshold value, the UE determines a power boost to be a first P0 power value based on the first OLPC value. In response to determining the QoS parameter has a second QoS value or a value larger than the threshold value, the UE determines the power boost to be a second P0 power value based on the first OLPC value. The device transmits the UL transmission with a transmit power that includes the power boost. The set of OLPC parameters provides an acceptable range for the UL transmit power. A range is given, allowing some latitude for the UE to provide a power boost when necessary to meet the QoS requirement or to provide a lower power level when not required, enabling power savings. The UE selects a particular boost value from the set. The corresponding increase in transmit power from the lowest first P0 power value to perhaps a higher selection provides the power boost.

[0037] In one or more embodiments, the UE is scheduled by a DCI format that does not include a Sounding Reference Resource (SRS) Resource Indicator (SRI) field. Alternatively, the UE is not configured with PUSCH power control based on SRI indication in DCI. In an example, the UE is not configured with SRI-PUSCH-PowerControl field that comprises a set of power control parameters. With these embodiments, if PO-PUSCH-Set, comprising a set of power control parameters, is provided to the UE and the DCI format includes an openloop power control parameter set indication field, the UE determines a value of P_o _UE PuscH,b,f,c(j)- The value of P_o uE_PuscH,b,f,c(j) is a target received power at the gNB for a bandwidth part ‘b’ of carrier f of serving cell c according to a set of parameters corresponding to an index 'j'_ The value of P_{o UE} puscH,b,f,c(j) is determined by using one of the below options:

(i) A first PO-PUSCH-AlphaSet (including a pair of (PO, alpha)) from a plurality of pO-AlphaSets, if a value of the open-loop power control parameter set indication field is 'O' (in case the bit width of the DCI field is 1 bit) or '00' (in case the bit width of the DCI field is 2 bits).

(ii) If the UE determines a remaining delay budget for an ADU, packet, TB, or hybrid automatic repeat request (HARQ) process is larger than a threshold, and/or if the ADU/packet is associated with a P-frame/slice (or not associated with an I-frame/slice):

(a) A first value in PO-PUSCH-Set (i.e., a set comprising a plurality of PO values) with the lowest pO-PUSCH-SetID (i.e., the index of a PO-PUSCH-Set) value if a value of the open-loop power control parameter set indication field is T (in case the bit width of the DCI field is 1 bit) or '01' (in case the bit width of the DCI field is 2 bits); and

(b) A second value in PO-PUSCH-Set with the lowest pO-PUSCH-SetID value if a value of the open-loop power control parameter set indication field is ' 1 O' (in case the bit width of the DCI field is 2 bits).

(iii) If the UE determines a remaining delay budget for an ADU, packet/TB/HARQ process is not larger than a threshold, and/or if the ADU or packet is associated with an I-frame/slice:

(a) A first value in PO-PUSCH-Set with the second lowest pO-PUSCH-SetID value if a value of the open-loop power control parameter set indication field is T (in case the bit width of the DCI field is 1 bit) or '01' (in case the bit width of the DCI field is 2 bits); and

(b) a second value in PO-PUSCH-Set with the second lowest pO-PUSCH- SetlD value if a value of the open-loop power control parameter set indication field is ' 1 O' (in case the bit width of the DCI field is 2 bits). In one embodiment, instead of second lowest pO-PUSCH-SetID, a pre-configured pO- PUSCH-SetlD or the highest pO-PUSCH-SetID can be used.

[0038] However, if PO-PUSCH-Set is not provided to the UE and the DCI format does not include an open-loop power control parameter set indication field, the UE determines P_o UE PuscH,b,f,c(j) from the value of the first PO-PUS CH- AlphaSet in pO- AlphaSets. In a related embodiment regarding power control for configured grant physical uplink shared channel (PUSCH), a GC-DCI indicates an index for OLPC, and the UE determines an OLPC parameter value (e.g., P0_2 or P0_3) based on the indicated index, and a QoS parameter. According to one embodiment, a similar rule can be utilized for the dynamic PUSCH. In another embodiment, the UE is configured with a first pO-PUSCH- Alpha, and a second pO- PUSCH-Alpha. The UE would then choose between the first and the second pO-PUSCH- Alpha based on a first value for QoS, and a second value for QoS, respectively. In an example, the UE chooses the second pO-PUSCH- Alpha if the UE has informed the gNB about the second value for QoS at least a certain time before the transmission.

[0039] In one or more embodiments, the present disclosure provides additional enhancements for specific DCI fields. In an example, the control message includes a beta offset indication. With these embodiments, a UE determines a number of resources for multiplexing hybrid automatic repeat request (HARQ) and acknowledgement (ACK) information and for multiplexing CSI reports in a PUSCH based on a provided beta offset value from a set of beta offset values. The set of beta offset values may be provided/configured by higher layers. Beta offset values are also defined for multiplexing configured grant (CG) uplink control information (UCI) in a CG-PUSCH. The beta offset values are signaled to a UE either by a field (e.g., beta offset indicator) in a DCI format scheduling the PUSCH transmission or by higher layers. In this embodiment, the base node, such as a gNB, transmits a DCI to a UE. The DCI schedules an UL transmission (e.g., a PUSCH transmission). The DCI indicates an index via a beta offset indication. The UE determines a QoS parameter. In response to determining that the QoS parameter has a first QoS value or a value smaller than or equal to a threshold value, the UE determines a beta offset to be a first ^offset- In response to determining the QoS parameter has a second QoS value or a value larger than the threshold value, the UE determines the beta offset to be a second Offset- The UE multiplexes a UCI in the UL transmission based on the determined beta offset. The UE transmits the resulting UL transmission. In some examples, the second ^offset is larger than the first /?_off_set-

[0040] In related embodiments, if the remaining delay budget for an UL ADU, packet, TB, or HARQ process corresponding to the scheduled PUSCH is smaller than a threshold or if the delay budget is exceeded, the UE would not multiplex the UCI into the PUSCH. The threshold value utilized depends on a UCI multiplexing timeline, a PUSCH preparation time, etc. In an example, UCI multiplexing timeline is the minimum time required between the last symbol of a PDSCH for which HARQ-ACK UCI is to be provided and the earliest symbol of overlapping PUCCH corresponding to the PDSCH and the PUSCH. Alternatively, or in addition, the threshold value is indicated by the DCI scheduling the PUSCH. FIG. 4 is a communication diagram 400 presenting a downlink 401 and an uplink 402. The downlink 401 carries a DL DCI 404 followed by a physical downlink shared channel (PDSCH) 406 transmitted by a base node. Then, the uplink 402 carries a QoS report 408 transmitted by the receiving UE. The downlink 401 carries a UL DCI 410 after a time “tl” from the QoS report 408. The uplink 402 carries a physical uplink control channel (PUCCH) 414 after a time “T2” from the PDSCH 406. The PUCCH 414 overlaps with transmission of a scheduled PUSCH 416 carried on the uplink 402 by beginning first and overlapping a beginning of the PUSCH 416. The PUCCH 414 and PUSCH 416 overlap but UCI is not multiplexed into PUSCH even though the UCI multiplexing timeline is satisfied due to the delay budget for the PUSCH being small. In an example, the UCI multiplexing timeline is satisfied when T2 > Tmux, which is the minimum time required between the last symbol of the PDSCH and earliest symbol of an overlapping PUCCH. Tl needs to be larger than a certain time to ensure the gNB can decode the QoS report and take the reported QoS into account in the UL DCI. Otherwise, the PUCCH is dropped, and the UCI is dropped or alternatively postponed. The UL DCI may indicate postponing the UCI (e.g., UL DCI may indicate a new PUCCH resource for the UCI or just indicate to the UE that the UCI will be later assigned a PUCCH resource.). In one or more embodiments, the postponed UCI may be multiplexed in a subsequent PUSCH. In an example, the postponed UCI is multiplexed when the subsequent PUSCH has a sufficient delay budget that is larger than a threshold. Alternatively, or in addition, the postponed UCI is multiplexed when the subsequent PUSCH has a certain priority level(s).

[0041] In an example, if the delay budget is exceeded for an ADU or IP-packet, the UE would drop the corresponding PUSCH transmissions. In that case, the UE does not cancel the PUCCH when a UCI was intended to be multiplexed into the PUSCH due to overlapping the PUCCH and the PUSCH. The UE transmits the UCI on the PUCCH if the UE determines or reports the delay budget is exceeded before a time “T3” before the PUCCH resource. In some examples, the PUSCH is dropped but the PUCCH and/or UCI is postponed if “T3” is not sufficient or larger than a threshold. FIG. 5 is a communication diagram 500 showing a downlink 501 and an uplink 502. The downlink 501 carries a DL DCI 504 followed by an PDSCH 505 and UL DCI 506. Following, a QoS report 508 is carried on the uplink 502. After a time “T3” following the QoS report 508, the uplink 502 carries a PUCCH 514 at a time T2 after the PDSCH 505. The PUCCH 514 punctures transmission of a scheduled PUSCH 516 carried on the uplink 502. The UCI multiplexing timeline is satisfied. In an example, UCI multiplexing timeline is satisfied when Time “T2” is greater than or equal to a minimum time “Tmux” required to multiplex the UCI into the PUSCH. The UE drops or does not transmit the PUSCH if a delay budget associated with the PUSCH is exceeded. If T3 is large enough, the UE sends the PUCCH 514 with the UCI included. Otherwise, when a delay budget associated with the PUSCH is exceeded and either (a) when the UCI multiplexing timeline is not satisfied or (b) when the UCI multiplexing timeline is satisfied but “T3” is not large enough, the UE drops and does not transmit both PUCCH 514 and PUSCH 516. Alternatively, the UE transmits the UCI incorporated into the PUSCH and the PUSCH transmission is not dropped, if a UCI multiplexing timeline is satisfied, although the corresponding delay budget is exceeded. Alternatively, the UCI is sent on the resources assigned for the PUSCH, but no TBs are included in uplink shared channel (UL-SCH). The gNB is notified of no UL-SCH because the delay budget is exceeded. Alternatively, the UCI is sent on the PUSCH 516, and instead of the PUSCH TB, a predetermined, dummy, medium access control (MAC) control element (CE), or buffer status report (BSR) information is included in the PUSCH 516. In some examples, the MAC-CE can indicate that no UL-SCH (TB) are included. The MAC-CE may possibly indicate the cause for the no UL-SCH such as (a) delay budget exceeded, (b) no remaining delay budget, (c) value of delay budget etc. In some examples, the remaining resources (REs and/or bits) corresponding to the TB are instead used for additional UCI resources. In an example, repetition of the multiplexed UCI in the first UCI resources determined based on the beta-offset value improves the reliability of the UCI. The MAC-CE and the UCI bits are channel-coded and rate-matched similar as a TB is channel-coded and rate-matched in the TB encoding processing procedure. In another example, the indication of no UL-SCH (TB) is included in the multiplexed UCI and the UCI in the additional UCI resources, corresponding to the REs of the TB, is channel-coded and rate-matched according to the UCI encoding procedure.

[0042] According to one aspect, if the UE is configured with two sets of beta offsets corresponding to priority 1 and priority 0, the UE performs according to one of the following processes:

(i) the UE uses the set of beta offsets corresponding to priority 1 for multiplexing UCI that has high priority into the PUSCH. In an example, priority 1 is appropriate when the UE determines a remaining delay budget for an UL ADU, packet, TB, or HARQ process corresponding to the scheduled PUSCH is approaching, but has not passed, a threshold limit, requiring priority in transmission to satisfy the latency and/or data rate and/or data error requirement. In another example, priority 1 is appropriate when the UE determines that the ADU/packet is associated with an I-frame/slice.

(ii) the UE uses the set of beta offsets corresponding to priority 0 that is not a high priority for multiplexing UCI into the PUSCH. In another example, priority 0 is appropriate when the UE determines that the remaining delay budget is greater than the threshold limit and will arrive too late to be used. In an additional example, priority 0 is appropriate when the UE determines that the remaining delay budget is larger than a threshold indicating that a priority 0 is sufficient to remain within a latency and/or data rate and/or data error requirement. In yet another example, priority 0 is appropriate when the UE determines that the ADU/packet is associated with a P-frame/slice.

[0043] In one or more embodiments, if the UCI includes at most 2 bits and/or if the UCI punctures the PUSCH, a MAC-CE in the PUSCH could indicate which set of beta offsets is used in the PUSCH for UCI multiplexing. For a UCI with more than 2 bits (or when the PUSCH is rate matched around the UCI), having different meanings/values for a beta offset (i.e., having different sets of beta offsets depending on QoS) only works if the gNB can determine the same or a similar QoS as that determined by the UE and hence the gNB is able to know which set of beta offsets is used by the UE.

[0044] In one or more embodiments, if a DCI format does not include a beta offset indicator field but does schedule a PUSCH transmission, the UE can be configured (e.g., by radio resource control (RRC) signaling) with a first set of beta offset values for multiplexing different UCIs (e.g., HARQ-ACK, CSI, CG-UCI, etc.). Depending on the QoS value, the UE uses the first set of beta offset values or determines a second set of beta offset values for multiplexing different UCIs. In an example, RRC configures the second set of beta offset values. The UE can be configured with two sets of beta offsets corresponding to priority 1 and priority 0. Depending on the remaining delay budget for an UL ADU, packet, TB, or HARQ process corresponding to the scheduled PUSCH, the UE can determine which set of beta offset values is to be used. In an example, one set of beta offset values has less latency than another, enabling the UE to associate different priorities to respective beta offset values. The remaining delay budget can be communicated between UE and gNB (e.g., prior to UL transmission), so that both can determine which beta offset value the UE would use for the transmission. It is appreciated that, in one or more embodiments, the DCI format may not include a priority indication field for the UL transmission.

[0045] Aspects of the present disclosure include addressing time domain resource assignment (TDRA). When the UE is scheduled to receive a PDSCH by a DCI, the TDRA field value m of the DCI provides a row index m + 1 to an allocation table (referred to as TDRA table). The indexed row defines the slot offset Ko, (slot offset between the scheduling PDCCH and the scheduled PDSCH), the start and length indicator (SI. IV), or directly the start symbol S and the allocation length L, and the PDSCH mapping type to be assumed in the PDSCH reception. The indexed row may also define a repetition number for PDSCH transmission.

[0046] The TDRA field size in DCI can be small (e.g., at most 4 bits for DCI format 1- 2) and hence cannot point to many combinations of (K0, mapping, SLIV, repetition). According to one aspect, the gNB can take advantage of the (almost) common knowledge of a delay budget (corresponding to an ADU/packet/HARQ process, etc.) between UE and gNB (if such a knowledge is available), and hence indicate more (KO, mapping, SLIV, repetition) combinations without increasing the TDRA field size.

[0047] In an embodiment, the UE determines a KO for a scheduled PDSCH to be zero/small (referred to as “kO_d”) although the indicated row of the TDRA table corresponds to a KO (referred to as KO TDRA) that is larger than the kO_d when a QoS parameter (e.g., remaining delay budget) associated with the scheduled PDSCH is going to be exceeded if KO TDRA is used. The UE may determine a maximum value for K0_d that keeps the QoS parameter larger/smaller than a threshold. For instance, the UE may determine a maximum value for K0_d that keeps remaining delay budget larger than a threshold.

[0048] Alternatively, the UE is not expected to receive an indication or be scheduled by the base node to utilize a set of resources for a PDSCH for which the delay budget is exceeded by the end of the PDSCH transmission or by the end of the associated acknowledgment. For an example, the UE is not expected to be indicated a “KO” offset leading to exceeding the delay budget. The UE may discard or alternatively may receive repetitions of a PDSCH/TB after its delay budget is exceeded. As utilized herein, KO is the offset between the DL slot where the PDCCH(DCI) for downlink scheduling is received and the DL slot where PDSCH data is scheduled to be received.

[0049] Additionally, as utilized below, KI is the offset between the DL slot where the data is scheduled on PDSCH and the UL slot where the ACK/NACK Feedback for the scheduled PDSCH data need to be sent. K2 is the offset between the DL slot where the PDCCH(DCI) for UL scheduling is received and the UL Slot where the UL data need to be sent on PUS CH.

[0050] Similarly for the uplink, in an embodiment, the UE determines a K2 (i.e., a slot offset between the scheduling PDDCH and PUSCH) for a scheduled PUSCH to be zero or small. K2 is referred to as “k2_d”; however, the indicated row of the time domain resource assignment (TDRA) table corresponds to a K2 (referred to as K2 TDRA) that is larger than k2_d when a QoS parameter (e.g., remaining delay budget) associated with the scheduled PUSCH is going to be exceeded if K2 TDRA is used. When the UE is scheduled to transmit PUSCH by a DCI, a TDRA field value “m” of the DCI provides a row index m + 1 to TDRA table.

[0051] Alternatively, the UE is not expected to be indicated a set of resources for a PUSCH for which the delay budget is exceeded by the end of the PUSCH transmission. For an example, the UE is not expected to be indicated a K2 leading to exceeding the delay budget. The UE may discard or alternatively may transmit repetitions of a PUSCH/TB after an associated delay budget (e.g., corresponding to an IP-packet/ADU associated with the PUSCH) is exceeded.

[0052] Aspects of the present disclosure include modifying transmit power for a scheduled PUCCH. In an embodiment, the UE determines a different transmit power control (TPC) value for a PUCCH associated with a PDSCH corresponding to a packet or ADU with remaining delay budget that is smaller than a threshold compared to the case when the remaining delay budget is larger than the threshold.

[0053] Aspects of the present disclosure also include a PDSCH to HARQ feedback timing indicator. The UE is not expected to be indicated a KI value (e.g., slot/time offset from PDSCH to a PUCCH resource for sending the corresponding acknowledgment (HARQ- ACK)) which results in exceeding the delay budget for a packet/ADU associated with the scheduled PDSCH. Alternatively, the UE could be indicated to skip the acknowledgment in such a case, or the UE could be indicated a N/A for the acknowledgment, or the UE based on the knowledge of the remaining delay budget, the UE could skip or defer the acknowledgement.

[0054] In an embodiment, the UE is scheduled by a DCI with a TDRA field indicating a number of repetitions. If the UE discards a last few repetitions of the number of repetitions, such as based on a QoS (e.g., based on a remaining delay budget), the UE will determine a new kl value taking into account the dropped repetitions. For example, if repetitions in the last two slots have been dropped, the UE would perform one of the following: (i) reduce the indicated Kl by 2, and keep the time reference for Kl, the last slot of the number of repetitions (including the dropped ones) or (ii) keep the indicated Kl but update the time reference for Kl to be the last slot of transmitted/not-discarded repetitions. Both options lead to the same time for transmission of the HARQ-ACK, according to one embodiment which is different than the time for transmission of the HARQ-ACK, according to the DCI, if repetitions were not dropped.

[0055] FIG. 6 is a communication graph 600 showing a downlink 601 and an uplink 602. On the downlink 601, a DL DCI 604 is transmitted that schedules four PDSCH repetitions: PDSCH repetition 0 (“repO”) 606a, PDSCH repetition 1 (“repl”) 606b, PDSCH repetition 2 (“rep2”) 606c, and PDSCH repetition 3 (“rep3”) 606d. Delay budget is exceeded during PDSCH rep 2 606c and PDSCH rep 3 606d. Uplink 602 carries updated PUCCH resource (PUCCH2) 608a. In one example, PUCCH2 uses a short format instead of using the indicated PUCCH resource (PUCCH1) 608b in a long format. PUCCH1 and PUCCH2 are two of five formats of PUCCH. PUCCH1 is a long PUCCH with multiplexing in the same physical resource block (PRB). Time-multiplexes the UCI and demodulation reference signal (DMRS). PUCCH2 is a short PUCCH with no multiplexing in the same PRB and frequency multiplexes UCI and DMRS. In one or more embodiments, PUCCH1 and PUCCH2 can have the same PUCCH format. Generally, the PUCCH format depends on the number of UCI bits, which could be the same whether some PDSCH repetitions are dropped or not.

[0056] FIG. 7 is a communication graph 700 of a downlink 701 on which is transmitted a DL DCI 704 that schedules four PDSCH repetitions: PDSCH repetition 0 (“repO”) 706a, PDSCH repetition 1 (“repl”) 706b, PDSCH repetition 2 (“rep2”) 706c, and PDSCH repetition 3 (“rep3”) 706d. Delay budget is indicated in the DCI scheduling PDSCH with the time reference for the beginning of the delay budget (delay budget is exceeded after the indicated delay budget is elapsed from the time reference) determined based on the last repetition of the PDSCH.

[0057] In the one or more embodiments described herein, the UE is not expected to receive a DCI scheduling a TB associated with an ADU or packet when a corresponding delay budget is exceeded. In one or more embodiments described herein, the UE is not expected to decode a PDSCH associated with an ADU or packet when a corresponding delay budget is exceeded. [0058] FIG. 8 illustrates an example of a block diagram 800 of a user device 802 that provides for wireless communication with a quality of service (QoS) applied to meet a latency and/or a reliability/error rate requirement, in accordance with aspects of the present disclosure. The user device 802 may be an example of a UE 104 as described herein. The user device 802 may support wireless communication with one or more base stations 102, UEs 104, or any combination thereof. The user device 802 may include components for bidirectional communications including components for transmitting and receiving communications, such as a communications manager 804, a processor 806, a memory 808, a receiver 810, a transmitter 812, and an I/O controller 814. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses). The receiver 810 and transmitter 812 may exist on a same chip and be collectively referred to as a transceiver 815.

[0059] The communications manager 804, the receiver 810, the transmitter 812, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the communications manager 804, the processor 806, the receiver 810, the transmitter 812, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0060] In some implementations, the communications manager 804, the receiver 810, the transmitter 812, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 806 and the memory 808 coupled with the processor 806 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 806, instructions stored in the memory 808). [0061] Additionally, or alternatively, in some implementations, the communications manager 804, the receiver 810, the transmitter 812, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 806. If implemented in code executed by the processor 806, the functions of the communications manager 804, the receiver 810, the transmitter 812, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

[0062] In some implementations, the communications manager 804 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 812, or both. For example, the communications manager 804 may receive information from the receiver 810, send information to the transmitter 812, or be integrated in combination with the receiver 810, the transmitter 812, or both to receive information, transmit information, or perform various other operations as described herein. Although the communications manager 804 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communications manager 804 may be supported by or performed by the processor 806, the memory 808, or any combination thereof. For example, the memory 808 may store code, which may include instructions executable by the processor 806 to cause the user device 802 to perform various aspects of the present disclosure as described herein, or the processor 806 and the memory 808 may be otherwise configured to perform or support such operations.

[0063] For example, the communications manager 804 may support wireless communication at a first device (e.g., the user device 802) in accordance with examples as disclosed herein. The communications manager 804 may be configured as or otherwise support wireless communication with QoS appropriate for a portion of a video frame. In particular, the processor 806 configures the communications manager 804 and transceiver 815 to perform wireless communication with QoS to meet latency and/or error rate requirements. [0064] The processor 806 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 806 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 806. The processor 806 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 808) to cause/configure the user device 802 to perform various functions of the present disclosure.

[0065] The memory 808 may include random access memory (RAM) and read-only memory (ROM). The memory 808 may store computer-readable, computer-executable code including instructions that, when executed by the processor 806 cause the user device 802 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 806 but may cause/configure a computer (e.g., when the code is compiled and executed) to perform functions described herein. In some implementations, the memory 808 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0066] The I/O controller 814 may manage input and output signals for the user device 802. The I/O controller 814 may also manage peripherals not integrated into the user device 802. In some implementations, the I/O controller 814 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 814 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 814 may be implemented as part of a processor, such as the processor 806. In some implementations, a user may interact with the user device 802 via the I/O controller 814 or via hardware components controlled by the I/O controller 814.

[0067] In some implementations, the user device 802 may include a single antenna 816. However, in some other implementations, the user device 802 may have more than one antenna 816, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The receiver 810 and the transmitter 812 may communicate bidirectionally, via the one or more antennas 816, wired, or wireless links as described herein. For example, the receiver 810 and the transmitter 812 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 816 for transmission, and to demodulate packets received from the one or more antennas 816.

[0068] FIG. 9 illustrates an example of a block diagram 900 of a network device 902 that supports wireless communication with a quality of service (QoS) applied to meet a latency and/or a reliability/error rate requirement, in accordance with aspects of the present disclosure. The network device 902 may be an example of a base station 102 or a base node, as described herein. The network device 902 may support wireless communication with one or more base stations 102 and core network 106 as described in FIG. 1, UEs 104, or any combination thereof. The network device 902 may include components for bi-directional communications including components for transmitting and receiving communications, such as a scheduler 904, a processor 906, a memory 908, a receiver 910, transmitter 912, and an I/O controller 914. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses). The receiver 910 and transmitter 912 may be located on a single chip and collectively referred to as a transceiver 915.

[0069] The scheduler 904, the receiver 910, the transmitter 912, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the scheduler 904, the receiver 910, the transmitter 912, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0070] In some implementations, the scheduler 904, the receiver 910, the transmitter 912, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field- programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 906 and the memory 908 coupled with the processor 906 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 906, instructions stored in the memory 908).

[0071] Additionally, or alternatively, in some implementations, the scheduler 904, the receiver 910, the transmitter 912, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 906. If implemented in code executed by the processor 906, the functions of the scheduler 904, the receiver 910, the transmitter 912, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

[0072] In some implementations, the scheduler 904 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 912, or both. For example, the scheduler 904 may receive information from the receiver 910, send information to the transmitter 912, or be integrated in combination with the receiver 910, the transmitter 912, or both to receive information, transmit information, or perform various other operations as described herein. Although the scheduler 904 is illustrated as a separate component, in some implementations, one or more functions described with reference to the scheduler 904 may be supported by or performed by the processor 906, the memory 908, or any combination thereof. For example, the memory 908 may store code, which may include instructions executable by the processor 906 to cause/configure the network device 902 to perform various aspects of the present disclosure as described herein, or the processor 906 and the memory 908 may be otherwise configured to perform or support such operations.

[0073] For example, the scheduler 904 may support wireless communication at a first network device (e.g., the network device 902) in accordance with examples as disclosed herein. The scheduler 904 may be configured as or otherwise support wireless communication with QoS appropriate for a portion of a video frame. In particular, the processor 806 configures the communications manager 804 and transceiver 815 to perform wireless communication with selected/applied QoS to meet latency and/or error rate requirements.

[0074] The processor 906 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 906 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 906. The processor 906 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 908) to cause the network device 902 to perform various functions of the present disclosure.

[0075] The memory 908 may include random access memory (RAM) and read-only memory (ROM). The memory 908 may store computer-readable, computer-executable code including instructions that, when executed by the processor 906 cause the network device 902 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 906 but may cause/configure a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 908 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0076] The I/O controller 914 may manage input and output signals for the network device 902. The I/O controller 914 may also manage peripherals not integrated into the network device 902. In some implementations, the I/O controller 914 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 914 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS- WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 914 may be implemented as part of a processor, such as the processor 906. In some implementations, a user may interact with the network device 902 via the I/O controller 914 or via hardware components controlled by the I/O controller 914.

[0077] In some implementations, the network device 902 may include a single antenna 916. However, in some other implementations, the network device 902 may have more than one antenna 916, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The receiver 910 and the transmitter 912 may communicate bidirectionally, via the one or more antennas 916, wired, or wireless links as described herein. For example, the receiver 910 and the transmitter 912 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 916 for transmission, and to demodulate packets received from the one or more antennas 916.

[0078] FIG. 10 illustrates a flowchart of a method 1000 that supports wireless communication with a quality of service (QoS) applied to meet a latency and/or error rate requirement for a portion of a video frame, in accordance with aspects of the present disclosure. In one or more embodiments, the QoS may also be defined in terms of error rate, in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a user device or its components as described herein. For example, the operations of the method 10 may be performed by a UE 104 as described with reference to FIGs. 1 through 9. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using specialpurpose hardware.

[0079] At 1005, the method 1000 may include receiving a control message that includes a scheduling assignment for a transmission by the user device. The operations of 1005 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1005 may be performed by a device as described with reference to FIG. 1 [0080] At 1010, the method 1000 may include, in response to determining that the transmission is associated with a portion of a video frame, determining a Quality of Service (QoS) parameter associated with the portion of the video frame from among at least a first QoS and a second QoS. The first QoS provides at least one of a lower error rate and a lower latency than the second QoS. The operations of 1010 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1010 may be performed by a device as described with reference to FIG. 1.

[0081] At 1015, the method 1000 may include transmitting the transmission according to the first QoS in response to determining that the transmission is associated with the first QoS. The operations of 1015 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1015 may be performed by a device as described with reference to FIG. 1.

[0082] In one or more embodiments, the method 1000 includes transmitting the transmission according to the second QoS in response to determining that the transmission is not associated with the first QoS. In one or more embodiments, the method 1000 includes transmitting the transmission according to a default QoS in response to determining that the transmission is not associated with a portion of a video frame. In one or more embodiments, the first QoS and the second QoS are defined by one or more parameters of a group comprising: (i) error rate; (ii) remaining delay budget; (iii) remaining data volume; (iv) remaining expected duration of transmission; (v) required percentage of transmission for correct decoding; and (vi) content type (e.g., I-slice vs. P-slice) for a portion of a video frame. In one or more particular embodiments, the QoS parameter is defined at least in part by the remaining data volume that does not include any previously transmitted portion for which an explicit or implicit acknowledgement from the second device is pending.

[0083] In one or more embodiments, the method 1000 includes receiving, within the control message, a first control field comprising a first value. The method 1000 includes determining that the transmission is associated with the first QoS based on the first control field including the first value. [0084] In one or more embodiments, the method 1000 includes receiving, within the control message, downlink control information (DCI) comprising an open-loop power control (OLPC) parameter and an indication of a UL DCI for scheduling the UL transmission. In response to determining the QoS parameter is at least one of the first QoS or smaller than or equal to a QoS threshold (such as for a function of error rate and/or latency), the method 1000 includes assigning a first power boost value as a power boost. In response to determining the QoS parameter is at least one of the second QoS value or larger than the QoS threshold, the method 1000 includes assigning, as the power boost, a second power boost value that is greater than the first power boost value. The method 1000 includes transmitting the UL transmission with a transmission power based on the power boost. In one or more particular embodiments, the QoS threshold is a function of at least one of a group comprising: (i) an error rate threshold; (ii) a latency threshold; (iii) a delay budget threshold; (iv) a content type threshold; and (v) a priority threshold.

[0085] In one or more embodiments, in assigning the power boost, the method 1000 includes receiving a set of more than one transmit power levels, including at least a first power value and a second power value for uplink physical uplink shared channel (PUSCH) transmission, the first power value being less than the second power value. The method 1000 includes determining whether at least one condition exists from among (i) a remaining delay budget for content to be transmitted is larger than a delay threshold and (ii) a content type for content to be transmitted being associated with one of a P-frame or P-slice. In response to determining an existence of the at least one condition, the method 1000 includes determining open-loop power control for the uplink PUSCH transmission based on the first power value. In response to not determining an existence of the at least one condition, the method 1000 includes determining open-loop power control for the uplink PUSCH transmission based on the second value.

[0086] In one or more embodiments, in assigning the power boost, the method 1000 includes receiving a set of more than one transmit power levels, including at least a first power value and a second power value, for uplink physical uplink shared channel (PUSCH) transmission. The first power value is less than the second power value. The method 1000 includes determining whether at least one condition exists from among (i) a remaining delay budget for content to be transmitted is smaller than a delay threshold and (ii) a content type for content to be transmitted being associated with one of an I-frame or I-slice. In response to determining an existence of the at least one condition, the method 1000 includes determining open-loop power control for the uplink PUSCH transmission based on the second power value. In response to not determining an existence of the at least one condition, the method 1000 includes determining open-loop power control for the uplink PUSCH transmission based on the first value.

[0087] In one or more embodiments, the method 1000 includes receiving a higher layer configuration that configures beta offset values indicating beta-offset capability, the beta offset values defining a number of resources for multiplexing an uplink control information (UCI) into the physical uplink shared channel (PUSCH). The method 1000 includes receiving the control message having: (i) a scheduling assignment of the transmission on a physical uplink shared channel; and (ii) a beta offset index. In response to determining that the multiplexing timeline of the UCI into the PUSCH is satisfied, the method 1000 includes determining, in part based on the beta offset index, as a beta offset, a first beta offset value among the beta-offset values in response to the QoS parameter identifying at least one of (i) the first QoS or (ii) another QoS smaller than or equal to a QoS threshold. The method 1000 includes determining, in part based on the beta offset index, as the beta offset, a second beta offset value among the beta-offset values in response to the QoS parameter identifying at least one of (i) the second QoS or (ii) a third QoS that is larger than the QoS threshold. The method 1000 includes determining that a remaining delay budget is larger than a threshold time based on an amount of latency that renders the transmission not useful to the second communication device. The method 1000 includes transmitting the transmission by multiplexing the transmission and the UCI in the physical uplink shared channel according to the beta offset, in responses to the remaining delay budget being larger than the threshold time. In one or more particular embodiments, the UCI includes at least one of HARQ-ACK information and channel state information (CSI).

[0088] In one or more embodiments, in response to determining that the remaining delay budget is not larger than the threshold and that the uplink control information is to puncture resource elements of the physical uplink shared channel, the method 1000 includes transmitting the transmission if a multiplexing timeline of the uplink control information into the PUSCH is satisfied and not transmitting the transmission if the multiplexing timeline of the uplink control information into the PUSCH is not satisfied. In one or more particular embodiments, in response to the remaining delay budget not being larger than the threshold, the method 1000 includes performing one of: (i) postponing UCI transmission to a later transmission resource indicated in an uplink DCI scheduling the PUSCH; (ii) transmitting the UCI on the physical uplink shared channel (PUSCH) and replaces data traffic comprising the PUSCH transport block (TB) with predetermined information; (iii) transmitting the UCI on the physical uplink shared channel (PUSCH) and includes a Medium Access Control Element (MAC-CE) to the PUSCH. In one or more specific embodiments, the MAC-CE indicates the beta offset; and (iv) transmitting the UCI and one or more repetitions of the UCI on the PUSCH.

[0089] In one or more embodiments, the method 1000 includes determining that the transmission is associated with the first QoS, in response to determining that the transmission contains a portion of a remaining data volume that is smaller than a threshold data volume. In one or more embodiments, the method 1000 includes determining that the transmission is associated with the first QoS based on transmitting a status report to the second device indicating that content of a transmit buffer is associated with the first QoS. In one or more embodiments, the method 1000 includes determining that the transmission is associated with the first QoS based on content of a transmit buffer being intra-coded content and not predicted coded content.

[0090] In one or more embodiments, the method 1000 includes determining that the transmission is associated with the one of the first QoS and the second QoS. The method 1000 includes transmitting a second control message to the second device indicating the corresponding one of the first QoS and the second QoS.

[0091] In one or more embodiments, the method 1000 includes receiving a second control message comprising a reference transmission format. The method 1000 includes determining that the transmission is associated with the one of the first QoS and the second QoS based on determining that transmitting a remaining portion of the portion of the video frame according to the reference transmission format will exceed a remaining duration of a delay budget.

[0092] In one or more embodiments, the method 1000 includes transmitting an indicated QoS of the first QoS and the second QoS to the second device in a previous uplink transmission to prompt the second device to determine an updated QoS value based on the indicated QoS. The method 1000 includes transmitting the transmission according to the updated QoS.

[0093] In one or more embodiments, the method 1000 includes receiving a QoS indication of one of the first QoS and the second QoS in downlink control information (DCI). The method 1000 includes determining an updated QoS value based on the indicated QoS and a time that the second device schedules a downlink transmission. The method 1000 includes receiving the downlink transmission based on the updated QoS value.

[0094] FIG. 11 illustrates a flowchart of a method 1100 that supports wireless communication with a quality of service (QoS) applied to meet a latency and/or error rate requirement for a portion of a video frame, in accordance with aspects of the present disclosure. The QoS may also be defined in terms of error rate. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by a network device, base node, or base station 102 as described with reference to FIGs. 1 through 9. In some implementations, the network device may execute a set of instructions to control the function elements of the network device to perform the described functions. Additionally, or alternatively, the network device may perform aspects of the described functions using special-purpose hardware.

[0095] At 1105, the method may include, in response to determining that a transmission is associated with a portion of a video frame, transmitting a control message that includes: (i) a scheduling assignment of the transmission by the user device; and (ii) a first control field having a value that is utilized by the user device to identify which of a plurality of Quality of Service (QoS) parameters to associate with the portion of the video frame. The QoS parameters includes a first QoS and a second QoS, the first QoS providing at least one of a lower error rate and a lower latency than the second QoS. The operations of 1105 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1105 may be performed by a device as described with reference to FIG. 1

[0096] At 1110, the method may include configuring the network device to receive the transmission from the user device according to a specific one of the plurality of QoS parameters that corresponds to the value in the first control field. The operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to FIG. 1

[0097] At 1115, the method may include receiving the transmission according to the specific QoS. The operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to FIG. 1.

[0098] In one or more embodiments, the method 1100 includes receiving, scheduled according to the first QoS, the transmission from the user device in response to the value being a first value that corresponds to the first QoS. The method 1100 includes receiving, scheduled according to the second QoS, the transmission from the user device in response to the value being a second value that corresponds to the second QoS. In one or more embodiments, the first QoS and the second QoS are defined by one or more parameters of a group of parameters comprising: (i) error rate; (ii) remaining delay budget; (iii) remaining data volume; (iv) remaining expected duration of transmission; (v) required percentage of transmission for correct decoding; and (vi) content type for a portion of a video frame.

[0099] In one or more embodiments, the transmission is an uplink (UL) transmission by the user device and the method 1100 includes transmitting within the control message, downlink control information (DCI) including an open-loop power control (OLPC) parameter and an indication of a UL DCI for scheduling the UL transmission. The method 1100 includes receiving the UL transmission from the user device, scheduled according to the first QoS and at a first power boost value, in response to the user device determining that the QoS parameter is at least one of the first QoS or smaller than or equal to a QoS threshold. The method 1100 includes receiving the UL transmission from the user device, according to the second QoS and at a second power boost value, in response to the user device determining that the QoS parameter is at least one of the second QoS value or larger than the QoS threshold.

[0100] In one or more embodiments, the method 1100 includes transmitting a set of more than one transmit power levels including at least a first power value and a second power value for uplink physical uplink shared channel (PUSCH) transmission by the user device. The first power value is less than the second power value. The user device is prompted to determine whether at least one condition exists from among (i) a remaining delay budget for content to be transmitted is larger than a delay threshold and (ii) a content type for content to be transmitted being associated with one of a P-frame or P-slice. The user device is further prompted to, in response to determining an existence of the at least one condition, determine open-loop power control for the uplink PUSCH transmission based on the first power value. The user device is further prompted to, in response to not determining an existence of the at least one condition, determine open-loop power control for the uplink PUSCH transmission based on the second power value.

[0101] In one or more embodiments, the method 1100 includes transmitting the control message comprising: (i) a scheduling assignment of the transmission on a physical uplink shared channel; and (ii) beta offset values indicating beta-offset capability, the beta offset values defining a number of resources for multiplexing an uplink control information (UCI) into the physical uplink shared channel (PUSCH). In one or more particular embodiments, in response to determining that the remaining delay budget is not larger than the threshold and that the uplink control information is to puncture resource elements of the physical uplink shared channel, the method 1100 includes receiving the transmission if a multiplexing timeline of the uplink control information is satisfied. The method 1100 includes not receiving the transmission if the multiplexing timeline of the uplink control information is not satisfied.

[0102] In one or more embodiments, the method 1100 includes configuring the user device to receive the transmission scheduled according to the first QoS in response to determining that the transmission contains a portion of a remaining data volume that is smaller than a threshold data volume. In one or more embodiments, the method 1100 includes configuring the user device to receive the transmission scheduled according to the first QoS based on receiving a status report from the user device indicating that content of a transmit buffer is associated with the first QoS. In one or more embodiments, the method 1100 includes configuring the user device to receive the transmission according to one of the first QoS and the second QoS based on receiving a second control message from the user device indicating the corresponding one of the first QoS and the second QoS. In one or more particular embodiments, the method 1100 includes receiving the second control message with a reference transmission format. The method 1100 includes determining whether the content is associated with the one of the first QoS and the second QoS based on determining that receiving a remaining portion of the portion of the video frame according to the reference transmission format will exceed a remaining duration of a delay budget.

[0103] In one or more embodiments, the method 1100 includes receiving an indicated QoS of the first QoS and the second QoS from the user device in a previous uplink transmission. The method 1100 includes determining an updated QoS value based on the indicated QoS and a time that the user device transmitted the previous uplink transmission. The method 1100 includes receiving the content, transmitted by the user device, according to the updated QoS. In one or more embodiments, the method 1100 includes transmitting a QoS indication of one of the first QoS and the second QoS in downlink control information (DCI).

[0104] In one or more aspects of the present disclosure, a method provides for service- oriented transmission to meet a latency requirement. The method includes receiving a scheduling assignment via a control message scheduling a transmission. The control message includes a first control field with a first value. The method includes determining if the transmission is associated with a packet and/or a video frame/slice having a first QoS or a second QoS. In response to determining the transmission is associated with the first QoS, the method includes determining a second value based on the first value, and preparing the transmission based on the second value. In response to determining the transmission is associated with the second QoS, the method includes determining a third value based on the first value, and preparing the transmission based on the third value. The first QoS and the second QoS include parameters of one or more of: (i) an error-rate for a packet, video frame/slice; (ii) a remaining delay budget for the packet, video frame/slice; (iii) a remaining data volume; (iv) a remaining expected duration according to a reference transmission format; (v) a percentage of packets required for correct decoding of the video frame/slice; and (vi) video frame/slice type (e.g., I-frame/slice vs. P-frame/slice)) of the video frame/slice. The method includes transmitting the prepared transmission.

[0105] In one or more embodiments, the method includes determining a third value by determining that at least a part of an indication indicated by the first control field is not applicable. In one or more embodiments, the requirements for the first QoS and the second QoS include evaluating the remaining data volume to be transmitted or scheduled to be transmitted, without including transmissions for which an implicit or explicit acknowledgment is pending. In one or more embodiments, the first or second QoS is indicated in the control message.

[0106] In one or more embodiments, the transmission is an UL transmission. The DCI control message schedules the UL transmission, and the UE selects the second value for a DCI field based on the first value indicated in the DCI field. Also, the third value for the DCI field is by default equal to the second value unless the QoS has been reported to gNB (e.g., a certain time prior to receiving the DCI scheduling the UL transmission) or the reported QoS has been implicitly or explicitly acknowledged by the gNB prior to the DCI scheduling the UL transmission. In one or more particular embodiments, the second QoS has been reported to gNB not later than a certain time prior to the scheduling assignment. In one or more particular embodiments, the reference transmission format includes a reference MCS, a reference number of symbols per slot, a reference number of resource blocks per symbol, a reference number of resource elements per resource block, and a reference number of transmission layers.

[0107] In one or more embodiments, the first control field is an open-loop power control parameter set indication. The control message has an UL DCI format scheduling an UL transmission. In response to determining the transmission is associated with the first QoS, the UE determines a “P0” power value in determining UL transmission power based on the lowest pO-PUSCH-SetID of the set of configured pO-PUSCHs. In one or more embodiments, in response to determining the transmission is associated with the second QoS, the UE determines a value of PO power value in determining UL transmission power based on the second lowest pO-PUSCH-SetID of the set of configured pO-PUSCHs. In one or more embodiments, in response to determining the transmission is associated with the second QoS, the UE determines a value of PO power value in determining UL transmission power, based on a configured pO-PUSCH-SetID of the set of configured pO-PUSCHs, where the configured pO-PUSCH-SetID is different from the lowest pO-PUSCH-SetID.

[0108] In one or more embodiments, the prepared transmission is a PUSCH transmission. The method includes preparing the transmission based on the third value by: (i) determining if a UCI is to be multiplexed into the PUSCH; (ii) in response to determining a UCI is to be multiplexed into the PUSCH, determining if the UCI is to puncture the REs of the PUSCH; (iii) in response to determining the UCI is to puncture the REs of the PUSCH, transmitting the prepared transmission if a UCI multiplexing timeline is satisfied; and (iv) dropping the prepared transmission if a UCI multiplexing timeline is not satisfied or if the UCI is not to puncture the REs of the PUSCH.

[0109] It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0110] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. [0111] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0112] Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0113] Any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media. [0114] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0115] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described example.

[0116] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMS What is claimed is:

1. A user device for wireless communication, the user device comprising: a transceiver comprising at least one transmitter and at least one receiver that enable the user device to communicate with a second device; a communication manager communicatively coupled to the transceiver and which: receives a control message that includes a scheduling assignment for a transmission by the user device; in response to determining that the transmission is associated with a portion of a video frame: determines a Quality of Service (QoS) parameter associated with the portion of the video frame from among at least a first QoS and a second QoS, the first QoS providing at least one of a lower error rate and a lower latency than the second QoS; and in response to determining that the transmission is associated with the first QoS, transmits the transmission according to the first QoS.

2. The user device of claim 1, wherein, in response to determining that the transmission is not associated with the first QoS, the communication manager transmits the transmission according to the second QoS.

3. The user device of claim 1, wherein the transmission is an uplink (UL) transmission and the communication manager: receives, within the control message, downlink control information (DCI) comprising an open-loop power control (OLPC) parameter and an indication of a UL DCI for scheduling the UL transmission; in response to determining the QoS parameter is at least one of the first QoS or smaller than or equal to a QoS threshold, assigns a first power boost value as a power boost, wherein the QoS threshold is a function of at least one of a group comprising: (i) an error rate threshold; (ii) a latency threshold; (iii) a delay budget threshold; (iv) a content type threshold; and (v) a priority threshold; in response to determining the QoS parameter is at least one of a second QoS value or larger than the QoS threshold, assigns, as the power boost, a second power boost value that is greater than the first power boost value; and transmits the UL transmission with a transmission power based on the power boost.

4. The user device of claim 3, wherein to assign the power boost the communication manager: receives a set of more than one transmit power levels including at least a first power value and a second power value for uplink physical uplink shared channel (PUSCH) transmission, the first power value being less than the second power value; determines whether at least one condition exists from among (i) a remaining delay budget for content to be transmitted is larger than a delay threshold and (ii) a content type for content to be transmitted being associated with one of a P-frame or P-slice; in response to determining an existence of the at least one condition, determines openloop power control for the uplink PUSCH transmission based on the first power value; and in response to not determining an existence of the at least one condition, determines open-loop power control for the uplink PUSCH transmission based on the second value.

5. The user device of claim 3, wherein to assign the power boost the communication manager: receives a set of more than one transmit power levels including at least a first power value and a second power value for uplink physical uplink shared channel (PUSCH) transmission, the first power value being less than the second power value; determines whether at least one condition exists from among (i) a remaining delay budget for content to be transmitted is smaller than a delay threshold and (ii) a content type for content to be transmitted being associated with one of an I-frame or I-slice; in response to determining an existence of the at least one condition, determines openloop power control for the uplink PUSCH transmission based on the second power value; and in response to not determining an existence of the at least one condition, determines open-loop power control for the uplink PUSCH transmission based on the first value.

6. The user device of claim 1 , wherein the communication manager: receives a higher layer configuration, configuring beta offset values indicating betaoffset capability, the beta offset values defining a number of resources for multiplexing an uplink control information (UCI) into a physical uplink shared channel (PUSCH); receives the control message comprising: (i) a scheduling assignment of the transmission on a physical uplink shared channel; and (ii) a beta offset index; and in response to determining that a multiplexing timeline of the UCI into the PUSCH is satisfied: determines, in part based on the beta offset index, as a beta offset, a first beta offset value among the beta-offset values in response to the QoS parameter identifying at least one of (i) the first QoS or (ii) another QoS smaller than or equal to a QoS threshold; determines, in part based on the beta offset index, as the beta offset, a second beta offset value among the beta-offset values in response to the QoS parameter identifying at least one of (i) the second QoS or (ii) a third QoS that is larger than the QoS threshold; determines that a remaining delay budget is larger than a threshold time based on an amount of latency that renders the transmission not useful to the second communication device; and transmits the transmission by multiplexing the transmission and the UCI in the physical uplink shared channel according to the beta offset, in responses to the remaining delay budget being larger than the threshold time.

7. The user device of claim 6, wherein, in response to determining that the remaining delay budget is not larger than the threshold and that the uplink control information is to puncture resource elements of the physical uplink shared channel, the communication manager: transmits the transmission if a multiplexing timeline of the uplink control information into the PUSCH is satisfied; and does not transmit the transmission if the multiplexing timeline of the uplink control information into the PUSCH is not satisfied.

8. The user device of claim 6, wherein, the communication manager: in response to the remaining delay budget not being larger than the threshold, performs at least one of:

(i) postpones UCI transmission to a later transmission resource indicated in an uplink DCI scheduling the PUSCH; and

(ii) transmits the UCI on the physical uplink shared channel (PUSCH) and replaces data traffic comprising a PUSCH transport block (TB) with predetermined information;

(iii) transmits the UCI on the physical uplink shared channel (PUSCH) and includes a Medium Access Control Element (MAC-CE) to the PUSCH; and

(iv) transmits the UCI and one or more repetitions of the UCI on the PUSCH.

9. The user device of claim 1 , wherein the communication manager: receives a second control message comprising a reference transmission format; and determines that the transmission is associated with the one of the first QoS and the second QoS based on determining that transmitting a remaining portion of the portion of the video frame according to the reference transmission format will exceed a remaining duration of a delay budget.

10. The user device of claim 1 , wherein the communication manager: receives a QoS indication of one of the first QoS and the second QoS in downlink control information (DCI); determines an updated QoS value based on the indicated QoS and a time that the second device schedules a downlink transmission; and receives the downlink transmission based on the updated QoS value.

11. A network device for wireless communication, the network device comprising: a transceiver comprising at least one transmitter and at least one receiver that enable the network device to communicate with a user device; and a processor communicatively coupled to the transceiver and which: in response to determining that a transmission is associated with a portion of a video frame: transmits a control message that includes: (i) a scheduling assignment of the transmission by the user device; and (ii) a first control field having a value that is utilized by the user device to identify which of a plurality of Quality of Service (QoS) parameters to associate with the portion of the video frame, the QoS parameters comprising a first QoS and a second QoS, the first QoS providing at least one of a lower error rate and a lower latency than the second QoS; configures the network device to receive the transmission from the user device according to a specific one of the plurality of QoS parameters that corresponds to the value in the first control field; and receives the transmission according to the specific QoS.

12. The network device of claim 11 , wherein the first QoS and the second QoS are defined by one or more parameters of a group of parameters comprising: (i) error rate; (ii) remaining delay budget; (iii) remaining data volume; (iv) remaining expected duration of transmission; (v) required percentage of transmission for correct decoding; and (vi) content type for a portion of a video frame.

13. The network device of claim 11, wherein the transmission is an uplink (UL) transmission by the user device and wherein the network device: transmits within the control message, downlink control information (DCI) comprising an open-loop power control (OLPC) parameter and an indication of a UL DCI for scheduling the UL transmission; receives the UL transmission from the user device, scheduled according to the first QoS and at a first power boost value, in response to the user device determining that the QoS parameter is at least one of the first QoS or smaller than or equal to a QoS threshold; and receives the UL transmission from the user device, according to the second QoS and at a second power boost value, in response to the user device determining that the QoS parameter is at least one of the second QoS value or larger than the QoS threshold.

14. The network device of claim 13, wherein the network device: transmits a set of more than one transmit power levels including at least a first power value and a second power value for uplink physical uplink shared channel (PUSCH) transmission by the user device, the first power value being less than the second power value, prompting the user device to: determine whether at least one condition exists from among (i) a remaining delay budget for content to be transmitted is larger than a delay threshold and (ii) a content type for content to be transmitted being associated with one of a P-frame or P-slice; in response to determining an existence of the at least one condition, determine open-loop power control for the uplink PUSCH transmission based on the first power value; and in response to not determining an existence of the at least one condition, determine open-loop power control for the uplink PUSCH transmission based on the second power value.

15. The network device of claim 11 , wherein the processor transmits the control message comprising: (i) a scheduling assignment of the transmission on a physical uplink shared channel; and (ii) beta offset values indicating beta-offset capability, the beta offset values defining a number of resources for multiplexing an uplink control information (UCI) into the physical uplink shared channel (PUSCH).

16. The network device of claim 11, wherein the network device configures the user device to receive the transmission according to one of the first QoS and the second QoS based on receiving a second control message from the user device indicating the corresponding one of the first QoS and the second QoS.

17. The network device of claim 16, wherein the network device: receives the second control message comprising a reference transmission format; and determines whether content is associated with the one of the first QoS and the second QoS based on determining that receiving a remaining portion of the portion of the video frame according to the reference transmission format will exceed a remaining duration of a delay budget.

18. The network device of claim 16, wherein the network device: receives an indicated QoS of the first QoS and the second QoS from the user device in a previous uplink transmission; determines an updated QoS value based on the indicated QoS and a time that the user device transmitted the previous uplink transmission; and receives content, transmitted by the user device, according to the updated QoS.

19. A method for wireless communication by a user device, the method comprising: receiving a control message that includes a scheduling assignment for a transmission by the user device; in response to determining that the transmission is associated with a portion of a video frame: determining a Quality of Service (QoS) parameter associated with the portion of the video frame from among at least a first QoS and a second QoS, the first QoS providing at least one of a lower error rate and a lower latency than the second QoS; in response to determining that the transmission is associated with the first QoS, transmitting the transmission according to the first QoS; and in response to determining that the transmission is not associated with the first QoS, transmitting the transmission according to the second QoS; and in response to determining that the transmission is not associated with a portion of a video frame, transmitting the transmission according to a default QoS.

20. The method of claim 19, wherein the transmission is an uplink (UL) transmission, and the method further comprises: receiving, within the control message, downlink control information (DCI) comprising an open-loop power control (OLPC) parameter and an indication of a UL DCI for scheduling the UL transmission; in response to determining the QoS parameter is at least one of the first QoS or smaller than or equal to a QoS threshold, assigning a first power boost value as a power boost; in response to determining the QoS parameter is at least one of a second QoS value or larger than the QoS threshold, assigning, as the power boost, a second power boost value that is greater than the first power boost value; and transmitting the UL transmission with a transmission power based on the power boost.