Feedback delivered at the radio access network level

Abstract

Various aspects of the present disclosure provide techniques for indicating at least one lost frame from an encoding device using radio access network (RAN) level negative acknowledgement (NAK) feedback. RAN level NAK feedback replaces or preempts the decoding device from transmitting end-to-end feedback to the encoding device using the real-time transport protocol (RTP), which has a long delay and may cause freezing at the decoding device. For example, the encoding device may transmit a request to a network entity for a configuration that configures the encoding device to send media frames to the decoding device. The network entity may provide NAK feedback indicating at least one lost frame. Upon receiving a configuration in response to the request, the encoding device sends the media frame to the decoding device via the network entity and monitors NAK feedback from the network entity according to the configuration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 17 / 365,867, filed on July 1, 2021, which claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 075,734, filed on September 8, 2020, which application is assigned to the assignee of this application and is incorporated herein by reference in its entirety as if fully set forth below and for all applicable purposes. Technical Field

[0003] Aspects of the present disclosure relate to wireless communications and, more particularly, to techniques for communicating feedback regarding an unsuccessful transmission of, for example, media content. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. These wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name a few.

[0005] In some examples, a wireless multiple access communication system may include several base stations (BS), each of which can simultaneously support communication of multiple communication devices (also referred to as user equipment (UE)). In an LTE or LTE-A network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next generation, new radio (NR) or 5G network), a wireless multiple access communication system may include several distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit receive points (TRPs), etc.) communicating with several central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a set of one or more DUs communicating with a CU may define an access node (e.g., which may be referred to as a BS, a 5G NB, a next generation NodeB (gNB or gNodeB), a transmit receive point (TRP), etc.). A BS or DU may communicate with a set of UEs on downlink channels (eg, for transmissions from the BS or DU to the UEs) and uplink channels (eg, for transmissions from the UEs to the BS or DU).

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. NR (e.g., New Radio or 5G) is an example of an emerging telecommunication standard. NR is an enhancement set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL). For these purposes, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies. Summary of the invention

[0008] The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed in the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description of the Invention," it will be understood how the features of the present disclosure provide advantages including improved communication between access points and stations in a wireless network.

[0009] Certain aspects provide a method for wireless communication by an encoding device. The method generally includes: transmitting a request to a network entity for a configuration to configure the encoding device to send a media frame to a decoding device, whereby the network entity is configured to provide negative acknowledgement (NAK) feedback indicating at least one lost frame; receiving a configuration in response to the request; sending the media frame to the decoding device via the network entity; and monitoring NAK feedback from the network entity according to the configuration.

[0010] Certain aspects provide a method for wireless communication by a network entity. The method generally includes: receiving a request from an encoding device for a configuration to configure the encoding device to send a media frame to a decoding device, wherein the configuration enables the network entity to provide a negative acknowledgement (NAK) feedback indicating at least one lost frame from the encoding device; transmitting the configuration in response to the request; receiving a media frame from the encoding device to stream the media frame to the decoding device; and transmitting the NAK feedback to the encoding device according to the configuration.

[0011] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes: means for transmitting a request to a network entity for a configuration to configure an encoding device to send a media frame to a decoding device, whereby the network entity is configured to provide negative acknowledgement (NAK) feedback indicating at least one lost frame; means for receiving the configuration in response to the request; means for sending the media frame to the decoding device via the network entity; and means for monitoring the NAK feedback from the network entity according to the configuration.

[0012] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes: means for receiving a request from an encoding device for a configuration to configure the encoding device to send media frames to a decoding device, wherein the configuration enables a network entity to provide negative acknowledgement (NAK) feedback indicating at least one lost frame from the encoding device; means for transmitting the configuration in response to the request; means for receiving media frames from the encoding device to stream the media frames to the decoding device; and means for transmitting the NAK feedback to the encoding device according to the configuration.

[0013] Certain aspects provide components, means and / or computer-readable media having computer-executable code stored thereon for performing the techniques described herein.

[0014] To achieve the aforementioned and related purposes, one or more aspects include the features fully described and particularly pointed out in the claims below. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are only indicative of some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order that the manner in which the above-mentioned features of the present disclosure are understood in detail, a more specific description briefly summarized above may be obtained by reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

[0016] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

[0017] Figure 2 is a block diagram illustrating an example logical architecture of a distributed radio access network (RAN) in accordance with certain aspects of the present disclosure.

[0018] Figure 3 is a diagram illustrating an example physical architecture of a distributed RAN in accordance with certain aspects of the present disclosure.

[0019] Figure 4is a block diagram conceptually illustrating designs of example base stations (BSs) and user equipment (UEs) in accordance with certain aspects of the present disclosure.

[0020] Figure 5 is a diagram illustrating an example for implementing a communication protocol stack in accordance with certain aspects of the present disclosure.

[0021] Figure 6 An example diagram illustrating real-time transport protocol (RTP) to RTP feedback between a rendering encoder and a decoder is shown in accordance with certain aspects of the present disclosure.

[0022] Figure 7 is a diagram illustrating an example transmission of a media frame in accordance with certain aspects of the present disclosure.

[0023] Figure 8

[0026] Example operations performed by an encoding device for wireless communications in accordance with certain aspects of the present disclosure are illustrated.

[0024] Fig. 9 Example operations performed by a decoding device for wireless communications in accordance with certain aspects of the present disclosure are illustrated.

[0025] Fig.10 An example diagram presenting radio access network (RAN) level early feedback between an encoder and a decoder is shown in accordance with certain aspects of the present disclosure.

[0026] Fig.11A An example of network coding feedback provided via physical layer (PHY) acknowledgement in accordance with certain aspects of the present disclosure is shown.

[0027] Fig. 11B An example of network coding feedback provided via medium access control (MAC) layer acknowledgment in accordance with certain aspects of the present disclosure is shown.

[0028] Fig. 11C An example of network coding feedback provided via radio link control (RLC) status reporting is shown in accordance with certain aspects of the present disclosure.

[0029] Fig.11D An example of network coding feedback provided via Packet Data Convergence Protocol (PDCP) status reporting is shown in accordance with certain aspects of the present disclosure.

[0030] Fig.12 It is shown that some aspects of the present disclosure may include a Figure 8 The operation of the various components of a communications device is illustrated.

[0031] Fig.13 It is shown that some aspects of the present disclosure may include a Fig. 9The operation of the various components of a communications device is illustrated.

[0032] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation. DETAILED DESCRIPTION

[0033] Various aspects of the present disclosure relate to wireless communications between an encoding device (e.g., a transmitter device, such as a user equipment (UE)) and a decoding device (e.g., a receiver device) via a radio access network (RAN) (e.g., a base station such as a gNB), such as, for example, delivering media content (e.g., audio and / or video) over an Internet Protocol (IP) network.

[0034] In one illustrative example, aspects of the present disclosure relate to techniques for providing RAN-level negative acknowledgment (NAK) feedback to an encoding device when transmission of at least one frame fails. A network entity may transmit RAN-level NAK feedback before a decoding device transmits any end-to-end feedback using the Real-time Transport Protocol (RTP). RTP is a network protocol for communication and entertainment systems with streaming media, including: telephones, video teleconferencing applications, television services, network-based push-to-talk applications, etc. By using the disclosed RAN-level NAK feedback, an encoding device may take timely corrective actions based on the NAK feedback to avoid interruptions at a decoding device. Without RAN-level NAK feedback, end-to-end RTP feedback between a decoding device and an encoding device may take 400ms or longer and cause playback freezes at the decoding device due to the inability to decode.

[0035] According to the present disclosure, an encoding device may transmit a request to a network entity for a configuration to configure the encoding device to send a media frame to a decoding device (essentially requesting to enable fast NAK feedback). The network entity may provide NAK feedback indicating at least one lost frame. Upon receiving the configuration in response to the request, the encoding device sends the media frame to the decoding device via the network entity and monitors the NAK feedback from the network entity according to the configuration. In some cases, the media frame is sent point-to-point between the encoding device and the decoding device via the network; in some cases, the media frame is an uplink media frame sent to the network entity, and the network entity further sends the media frame to the decoding device.

[0036] RAN-level NAK feedback can enable an encoding device to avoid substantial delays in end-to-end RTP feedback, since RTP feedback can take up to 400 milliseconds or longer. During the 400 milliseconds or longer delay, the encoding device may have transmitted additional information to the decoding device. In addition to the lost transmission, the encoding device may have to retransmit the additional information, which may have relied on the lost transmission for decoding. Thus, providing a RAN-level NAK can (1) minimize feedback delays between the encoding device and the decoding device; and (2) save retransmissions of the additional information by including decoding instructions in subsequent transmissions, so that decoding operations at the decoding device may no longer rely on the lost transmission.

[0037] In some cases, the encoding device transmits multiple media frames to the decoding device. The media frame can be a sequence of image frames including key frames and non-key frames. For example, non-key frames can be encoded based on key frames, so the decoding device needs to correctly receive key frames to decode non-key frames. During operation, transmission errors may occur, and the decoding device may not receive all key frames or non-key frames. As described above, it may take up to 400 milliseconds or more to transmit end-to-end RTP feedback to the encoding device. The encoding device transmits additional media frames, including non-key frames and key frames, during such a long delay time. As a result, non-key frames transmitted during this period may not be decodable and need to be retransmitted, even if they have been correctly received at the decoding device. The technology disclosed herein can enable the encoding device to realize the failure of media frame transmission via NAK within a short delay, and modify some non-key frames to key frames, so that the decoding device can decode the following non-key frames without freezing or stuttering.

[0038] The following description provides examples rather than limiting the scope, applicability or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace or add various procedures or components. For example, the described method may be performed in an order different from that described, and various steps may be added, omitted or combined. In addition, the features described with reference to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using additional or additional other structures, functionality or structure and functionality as various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The wording "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein need not be interpreted as being superior to or superior to other aspects.

[0039] The techniques described herein can be used for various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes other variants of Wideband CDMA (WCDMA) and CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS).

[0040] New Radio (NR) is an emerging wireless communication technology being developed in collaboration with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization called "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, although various aspects may be described herein using terms commonly associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations (such as 5G and later generations) including NR technology.

[0041] New Radio (NR) access (e.g., 5G technology) can support various wireless communication services, such as enhanced mobile broadband (eMBB) for wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) for high carrier frequency (e.g., 25 GHz or higher), massive machine type communication MTC (mMTC) for non-backward compatible MTC technology, and / or mission critical ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet their respective quality of service (QoS) requirements. In addition, these services can coexist in the same subframe.

[0042] Example Wireless Communication System

[0043] Figure 1 An example wireless communication network 100 is shown in which aspects of the present disclosure may be performed. For example, the wireless communication network 100 may include a network configured to perform Figure 8 and Fig. 9 Operations 800 and 900 of the UE 120 and / or the base station 110.

[0044] like Figure 1 As shown in , the wireless network 100 may include multiple base stations (BS) 110 and other network entities. BS 110 may be a station that communicates with a user equipment (UE). Each BS 110 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a node B (NB) and / or a node B subsystem that serves the coverage area, depending on the context in which the term is used. In the NR system, the terms "cell", next generation node B (gNB), new radio base station (NR BS), 5G NB, access point (AP), or transmit receive point (TRP) may be interchangeable. In some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move according to the location of the mobile BS. In some examples, the base station may be interconnected to each other and / or to one or more other base stations or network nodes (not shown) in the wireless communication network 100 through various types of backhaul interfaces (such as direct physical connections, wireless connections, virtual networks, etc.) using any suitable transmission network.

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

[0046] BS 110 may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in FIG. 1 , BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. BS 110 may support one or more (e.g., three) cells.

[0047] The wireless communication network 100 may also include a relay station. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a BS or a UE) and transmits the transmissions of the data and / or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. Figure 1 In the example shown in , a relay station 110r may communicate with a BS 110a and a UE 120r to facilitate communication between the BS 110a and the UE 120r. A relay station may also be referred to as a relay BS, a relay, or the like.

[0048] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relays, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 20 watts), while a pico BS, a femto BS, and a relay may have a lower transmit power level (e.g., 1 watt).

[0049] The wireless communication network 100 may support synchronous or asynchronous operation. For synchronous operation, each BS 110 may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, each BS may have different frame timing, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

[0050] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other (eg, directly or indirectly) via a wireless or wired backhaul.

[0051] UE 120 (e.g., 120x, 120y, etc.) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, home appliance, medical device or medical equipment, biometric sensor / device, wearable device (such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart necklace, etc.)), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. Some UEs may be considered as machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can provide connectivity to or to a network (e.g., a wide area network such as the Internet or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0052] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are transmitted in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.8 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.

[0053] Although aspects of the examples described herein may be associated with LTE technology, aspects of the present disclosure may be applicable to other wireless communication systems, such as NR. NR may utilize OFDM with CP on the uplink and downlink and include support for half-duplex operation using TDD. Beamforming may be supported and the beam direction may be dynamically configured. MIMO transmission with precoding may also be supported. The MIMO configuration in the DL may support up to 8 transmit antennas, multi-layer DL transmission with up to 8 streams, and up to 2 streams per UE. Multi-layer transmission of up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells.

[0054] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communications between some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communications, the subordinate entity utilizes the resources allocated by the scheduling entity. The base station is not the only entity that can be used as a scheduling entity. In some examples, a UE may be used as a scheduling entity, and resources for one or more subordinate entities (e.g., one or more other UEs) may be scheduled, and other UEs may utilize the resources scheduled by the UE for wireless communications. In some examples, a UE may be used as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In a mesh network example, UEs may communicate directly with each other in addition to communicating with a scheduling entity.

[0055] exist Figure 1 In FIG. 1 , a solid line with double arrows indicates desired transmission between a UE and a serving BS, which is a BS designated to serve the UE on a downlink and / or uplink. A thin dashed line with double arrows indicates interfering transmissions between the UE and the BS.

[0056] Figure 2 An example logical architecture of a distributed radio access network (RAN) 200 is shown, which may be Figure 1 . The 5G access node 206 may include an access node controller (ANC) 202. The ANC 202 may be a central unit (CU) of the distributed RAN 200. The backhaul interface to the next generation core network (NG-CN) 204 may terminate at the ANC 202. The backhaul interface to the adjacent next generation access node (NG-AN) 210 may terminate at the ANC 202. The ANC 202 may include one or more transmit receive points (TRPs) 208 (e.g., cells, BSs, gNBs, etc.).

[0057] The TRP 208 may be a distribution unit (DU). The TRP 208 may be connected to a single ANC (e.g., ANC 202) or more than one ANC (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, the TRP 208 may be connected to more than one ANC. Each of the TRPs 208 may include one or more antenna ports. The TRPs 208 may be configured to provide services to the UE individually (e.g., dynamically selected) or jointly (e.g., joint transmission).

[0058] The logical architecture of the distributed RAN 200 may support fronthaul solutions across different deployment types. For example, the logical architecture may be based on the transmitting network capabilities (eg, bandwidth, delay, and / or jitter).

[0059] The logical architecture of the distributed RAN 200 may share features and / or components with LTE. For example, the next generation access node (NG-AN) 210 may support dual connectivity with NR and may share a common fronthaul for LTE and NR.

[0060] The logical architecture of the distributed RAN 200 may enable collaboration between TRPs 208, for example, within a TRP and / or across TRPs via the ANC 202. An inter-TRP interface may not be used.

[0061] Logical functions can be dynamically distributed in the logical architecture of the distributed RAN 200. Figure 5 Described in more detail, the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer can be adaptively placed at the DU (e.g., TRP 208) or the CU (e.g., ANC202).

[0062] Figure 3 An example physical architecture of a distributed radio access network (RAN) 300 according to aspects of the present disclosure is shown. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU 302 may be centrally deployed. C-CU 302 functionality may be offloaded (e.g., to Advanced Wireless Services (AWS)) in an effort to handle peak capacity.

[0063] A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Optionally, the C-RU 304 may host core network functions locally. The C-RU 304 may have a distributed deployment. The C-RU 304 may be close to the network edge.

[0064] The DU 306 may host one or more TRPs (edge ​​node (EN), edge unit (EU), radio head (RH), smart radio head (SRH), etc.) The DU may be located at the edge of the network with radio frequency (RF) functionality.

[0065] Figure 4 It shows (as Figure 110 and UE 120, which may be used to implement aspects of the present disclosure. For example, antenna 452, processors 466, 458, 464, and / or controller / processor 480 of UE 120, and / or antenna 434, processors 420, 430, 438, and / or controller / processor 440 of BS 110 may be used to perform the Figure 8 and Fig. 9 Various techniques and methods are described herein.

[0066] At BS 110, a transmit processor 420 may receive data from a data source 412 and control information from a controller / processor 440. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 420 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols (e.g., for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 432a to 432t. Each modulator 432 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 432a through 432t may be transmitted via antennas 434a through 434t, respectively.

[0067] At the UE 120, antennas 452a to 452r may receive downlink signals from the base station 110 and may provide received signals to demodulators (DEMODs) in transceivers 454a to 454r, respectively. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and / or digitize) a corresponding received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain received symbols from all demodulators 454a to 454r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and / or decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller / processor 480.

[0068] On the uplink, at the UE 120, a transmit processor 464 may receive and process data from a data source 462 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 480 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 464 may also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 (if applicable), further processed by a demodulator in the transceivers 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, the uplink signals from the UE 120 may be received by the antenna 434, processed by the modulator 432, detected by the MIMO detector 436 (if applicable), and further processed by the receive processor 438 to obtain decoded data and control information transmitted by the UE 120. The receive processor 438 may provide decoded data to a data sink 439 and decoded control information to a controller / processor 440 .

[0069] Controllers / processors 440 and 480 may direct the operation at base station 110 and UE 120, respectively. Processor 440 and / or other processors and modules at BS 110 may perform or direct the execution of processes for the techniques described herein. Memories 442 and 482 may store data and program codes for BS 110 and UE 120, respectively. Scheduler 444 may schedule UEs for data transmission on the downlink and / or uplink.

[0070] Figure 5A diagram 500 showing an example for implementing a communication protocol stack according to various aspects of the present disclosure is shown. The communication protocol stack shown can be implemented by a device operating in a wireless communication system such as a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 shows a communication protocol stack including a radio resource control (RRC) layer 510, a packet data convergence protocol (PDCP) layer 515, a radio link control (RLC) layer 520, a medium access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, these layers of the protocol stack can be implemented as separate software modules, parts of a processor or ASIC, parts of non-collocated devices connected by a communication link, or various combinations thereof. Co-located and non-co-located implementations can be, for example, in a protocol stack for a network access device (e.g., AN, CU, and / or DU) or a UE.

[0071] The first option 505-a illustrates a split implementation of the protocol stack, where the implementation of the protocol stack is performed on a centralized network access device (e.g., Figure 2 ANC 202 in the system) and distributed network access equipment (e.g., Figure 2 In the first option 505-a, the RRC layer 510 and the PDCP layer 515 may be implemented by a central unit, and the RLC layer 520, the MAC layer 525, and the PHY layer 530 may be implemented by the DU. In various examples, the CU and the DU may be co-located or non-co-located. The first option 505-a may be useful in macro cell, micro cell, or pico cell deployments.

[0072] The second option 505-b shows a unified implementation of the protocol stack, where the protocol stack is implemented in a single network access device. In the second option, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 can each be implemented by an AN. The second option 505-b can be useful in, for example, a femtocell deployment.

[0073] Regardless of whether the network access device implements part or all of the protocol stack, the UE can implement the entire protocol stack as shown in 505-c (e.g., RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530).

[0074] In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe. In NR, the subframe is still 1 ms, but the basic TTI is called a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16,... slots), depending on the subcarrier spacing. An NR RB is 12 consecutive frequency subcarriers. NR can support a basic subcarrier spacing of 15 KHz, and other subcarrier spacings can be defined relative to the basic subcarrier spacing, such as 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. The symbol and slot lengths are proportional to the subcarrier spacing. The CP length also depends on the subcarrier spacing.

[0075] Example RTP feedback mechanism

[0076] Figure 6 FIG. shows an example diagram of real-time transport protocol (RTP) to RTP feedback between a presentation encoder and a decoder according to certain aspects of the present disclosure. As shown, the encoder on the UE side can stream media content to the decoder via the BS. For example, the UE can send media frames to the gNB, and the gNB communicates the media frames to the decoder (e.g., on a decoding device). The encoder on the UE side can encode the media frames, including compression, encryption, and / or other operations, for efficient, accurate, and secure transmission. The gNB communicates or streams the media frames to the decoding device. When at least one media frame is not correctly streamed, the decoder provides end-to-end RTP feedback to the encoder. The end-to-end RTP feedback typically has a delay of 400 milliseconds or longer. Such a delay can be considered substantial and is effectively reduced using the techniques disclosed herein. The UE sends multiple key and non-key media frames (e.g., x 1 , x 2 ,..., x 8 ) The example is shown in Figure 7 and described below.

[0077] Figure 7 is a diagram showing an example transmission of media frames according to certain aspects of the present disclosure. As shown, x 1 and x 7 are self-decodable key frames. x 1 is a non-key frame x 2 and x 5 and subsequent non-key frames (such as frame x 3 and x 6 ) provide decoding instructions. The non-key frames x 4 and x 6 can be decoded based on two or more other frames. For example, if x 1 , x 2 or x 3If any one of the above has been successfully received and decoded by the decoding device, then x 4 can be decoded. Similarly, if x has been successfully received and decoded 1 -x 5 Any one of these can decode x 6 . Keyframe x 7 For non-keyframe x 8 Provides decoding instructions.

[0078] In some cases, frame x 1 -x 8 It can represent video coding. In a general implementation (e.g., ignoring intra frames and assuming real-time transmission), multiple media frames are sent from an encoding device to a decoding device. The input is a sequence of frames: x 1 ,…,x N Some of these frames are key frames (they are transmitted directly), others are encoded based on previous frames. For example, a frame may be encoded as a "delta" relative to a previous frame. Figure 7 In the example shown, if x 2 If frame x is lost, 3 -x 6 All packets of are undecodable until the next keyframe x 7 .

[0079] In general, the encoding is a directed graph (frame x L The encoding is a collection of frames ( Among them, n i >0). Therefore, the decoded frame x L It may be necessary to set F(x L ). Therefore, when a frame is lost during transmission, or reception fails at the decoding device, subsequent frames sent during the feedback delay period cannot be decoded and need to be retransmitted. In addition, the longer the feedback delay period, the greater the number of undecodable frames will be sent because the encoding device is unaware of the dropped or missing frames until end-to-end RTP feedback is received. The disclosed technology alleviates these problems using NAK.

[0080] According to various aspects of the present disclosure, when the key frame x 1 or x 7 In the event of a drop during transmission, the encoding device, upon receiving a NAK at the RAN level, may adapt to this situation by retransmitting the dropped frame (e.g., when the NAK delay is negligible) or modifying one of the subsequent frames to include self-decoding information so that the decoding device can continue the decoding operation without the dropped frame. As a result, the decoding device may not freeze or need to provide end-to-end RTP feedback to the encoding device.

[0081] Example fast NAK feedback at radio access network level

[0082] Aspects of the present disclosure relate to wireless communications, and more specifically, to techniques for using radio access network (RAN) level negative acknowledgement (NAK) feedback to indicate at least one lost frame from an encoding device. In some aspects, the RAN level NAK feedback replaces or preempts the use of the real-time transport protocol (RTP) by the decoding device to transmit end-to-end feedback to the encoding device. RTP is a network protocol for streaming media content from an encoding device to a decoding device. For example, the media content may include: telephone, video teleconferencing applications, television services, network-based push-to-talk applications, etc.

[0083] In a data stream, such as passing audio and video from a sender (e.g., an encoding device) to a receiver (e.g., a decoding device) over an IP network, if a packet or frame is lost, the receiver may generate NAK feedback. In this case, the sender can adjust its predicted path or generate a repair packet to allow the receiver to continue decoding. However, the delay between the receiver and the sender often takes up to 400 milliseconds or longer. During this period, many frames that may rely on the lost frame for decoding are sent. As a result, the receiver will freeze until the repair packet is received and continues to decode correctly. Aspects of the present disclosure reduce or eliminate such freezing.

[0084] In a general aspect of the present disclosure, an encoding device may transmit a request to a network entity for a configuration that configures the encoding device to send a media frame to a decoding device. The encoding device then receives a configuration in response to the request. The encoding device sends the media frame to the decoding device via the network entity and monitors NAK feedback from the network entity according to the configuration. The media frame includes one or more key frames, which include decoding information required for decoding non-key frames. When NAK feedback is received from the network entity due to a transmission failure of a lost frame (e.g., the lost frame may be a key frame), the encoding device may send a correction frame generated from the non-key frame and corresponding decoding information of the lost frame. In some cases, the encoding device may retransmit the lost frame or cause the correction frame to include loss information of the lost frame.

[0085] Various aspects of the present disclosure are implemented in various protocol stack layers (e.g., at least one of the PDCP, RLC, MAC, or PHY layers, as described above with respect to Figure 5 The NAK feedback provided by the encoding device can quickly inform the encoding device of the lost frame or packet and obtain the updated incoming frame or packet to prevent freezing at the decoding device.

[0086] Figure 8Example operations 800 for wireless communications by an encoding device in accordance with certain aspects of the present disclosure are shown. Operations 800 may be performed, for example, by a UE (e.g., UE 120 in wireless communication network 100) that is streaming media frames to a decoding device (e.g., another UE 120 in wireless communication network 100) via a network (e.g., BS 110 in wireless communication network 100).

[0087] Operations 800 begin at 802 by transmitting to a network entity a request for a configuration to configure an encoding device to send a media frame to a decoding device. Using this configuration, the network entity may provide NAK feedback to the encoding device indicating at least one lost frame or streamed data packet. For example, some UEs may support RAN-level NAK feedback, while other UEs may rely only on end-to-end RTP feedback. This configuration allows the encoding device to receive and use RAN-level NAK feedback from the network entity. In some cases, the encoding device requests configuration of at least one of a logical channel or a radio bearer.

[0088] At 804, the encoding device receives a configuration in response to the request from the network entity. At 806, the encoding device sends (e.g., streams) the media frame to the decoding device via the network entity. For example, the media frame may include data packets or samples of audio, video, or both for telephone, video teleconferencing applications, television services, network-based push-to-talk applications.

[0089] In some examples, one or more media frames are segmented into multiple packets for transmission according to a certain mapping relationship. In this way, the encoding device can identify frame failure based on the mapping from frames to packets.

[0090] At 808, the encoding device monitors NAK feedback from the network entity according to the configuration. In various aspects, the NAK feedback may be provided via Radio Link Control (RLC) or Packet Data Convergence Protocol (PDCP) signaling. The NAK feedback may indicate that the lost packets are in the logical channel indicated by the encoding device.

[0091] In various aspects, the NAK feedback is provided via physical layer (PHY) or medium access control (MAC) layer signaling.The encoding device may determine the logical channel of the lost packet based on a mapping from logical channels to component carriers or physical layer priorities.

[0092] For example, the encoding device does not know whether the sent media frame has been successfully received. To minimize the delay between detecting a dropped frame and taking corrective action, NAK feedback from the network entity can quickly notify the encoding device about the dropped frame and prevent freezing at the decoding device. Fig.10 As shown, the gNB can provide early feedback to the UE when it detects dropped frames.

[0093] Fig. 9 900 illustrates example operations for wireless communications by a network entity in accordance with certain aspects of the present disclosure and may be considered to be an example of Figure 8 For example, operation 900 may be performed by one of the base stations (e.g., Figure 1 or Figure 2 BS 110) executes to process the Figure 8 The operation 800 of encoding a device (eg, Figure 1 120) of the network coding packet (and providing termination feedback to it).

[0094] Operations 900 begin at 902 by receiving a request for a configuration from an encoding device to configure the encoding device to send media frames. The configuration enables a network entity to provide NAK feedback to the encoding device indicating at least one lost frame from the encoding device. At 904, the network entity transmits the configuration in response to the request. At 906, the network entity receives a media frame from the encoding device to stream the media frame to a decoding device. At 908, the network entity transmits NAK feedback to the encoding device according to the configuration.

[0095] Figure 8 and Fig. 9 The operations 800 and 900 may generally refer to Fig.10 as well as FIG. 11A to FIG. 11D To describe, FIG. 11A to FIG. 11D It is shown how RAN level NAK feedback can be provided in the PHY, MAC, RLC or PDCP layer.

[0096] Fig.10 An example diagram showing early feedback at the radio access network (RAN) level between an encoder and a decoder is shown in accordance with certain aspects of the present disclosure. Fig.10 In, replace Figure 6 As shown, waiting for end-to-end RTP feedback from the decoding device, the gNB can use one or more of the PHY, MAC, RLC, or PDCP layers to inform the UE that a frame was lost in transmission. Using early feedback, the UE can retransmit the lost frame or modify subsequent frames to preempt potential decoding failures at the decoding device. FIG. 11A to FIG. 11D A detailed implementation is described in .

[0097] Fig.11AAn example of network coding feedback provided via physical layer (PHY) acknowledgement in accordance with certain aspects of the present disclosure is shown. As shown, the gNB provides PHY feedback to the UE when one or more of a plurality of media frames sent from the UE are dropped or otherwise not correctly received. In some aspects, the NAK feedback indicates a lost packet to the UE. Based on the NAK feedback, the UE determines that the network entity will not trigger a retransmission of the lost packet and flushes a hybrid automatic repeat request (HARQ) buffer based on the determination.

[0098] Many times, the PHY at the gNB may only know the success or failure of a given transmission or retransmission. That is, the UE may not know whether a given frame or packet has been correctly decoded by the gNB. Therefore, in some cases, the gNB may trigger a later retransmission of the same HARQ process regardless of the NAK feedback at the PHY layer. In addressing this potential problem, the present disclosure provides NAK feedback that indicates (1) the dropped frame or packet, and (2) the gNB does not intend to trigger another transmission of the same dropped frame or packet. Therefore, the UE can flush the HARQ buffer and does not need to expect a retransmission of the same packet.

[0099] In one aspect, a new downlink control information (DCI) indicating a HARQ process identifier (ID) of a lost packet may be used to provide PHY level NAK feedback. The DCI may include multiple bits and indicate the HARQ process ID via a starting bit position within the multiple bits. For example, the UE may be configured to monitor the DCI via RRC, configured with a corresponding search space, CORESET, and / or multiple candidates. The UE may be configured with a "starting bit" position in the DCI. The "starting bit" position may contain a HARQ process ID that the gNB has abandoned, allowing the UE to flush the HARQ buffer.

[0100] In some cases, the reserved values ​​of multiple bits indicate that there is no NAK feedback. Alternatively, the DCI indicates NAK feedback for multiple HARQ process IDs. Or, the DCI indicates NAK feedback for different coding devices. For example, one of the states can be reserved (e.g., set to all zeros) to indicate "no NAK" (the same DCI can include NAKs for different UEs). Using this method, NAK feedback can be provided to multiple HARQ processes at the same time, for example by configuring multiple fields to the UE. The DCI may include multiple fields for multiple HARQ processes for multiple failed frames in multiple frames of information. In some cases, the DCI may be transmitted on the same component carrier (CC) that schedules media frames for uplink traffic. Alternatively, the DCI may be configured in any CC and may include one or more CC indicators (e.g., a carrier indicator field (CIF)) that identifies which CC the HARQ process involves.

[0101] In a second aspect, a new field in the uplink DCI can be used to provide PHY-level NAK feedback. The DCI includes a toggled new data indicator (NDI) indicating that the decoding device will transmit a packet with a new transport block (TB). The DCI also includes an explicit acknowledgement indicator (EAI) that indicates whether the previous packet corresponding to the same HARQ process has been successfully received. For example, when a UE receives a DCI with a toggled NDI, the UE is informed that it should get a new TB instead of a retransmission. If the NDI value is toggled compared to the previous transmission for the same HARQ process, a new transmission is triggered, otherwise a retransmission is triggered. Since the UE may not be able to distinguish whether the gNB has successfully received a packet, or just abandoned it, the new field in the uplink DCI can indicate whether the previous packet for the same HARQ process has been successfully received.

[0102] The new field may be called EAI. For example, in one case, the UE is receiving NDI=1, but at some point, the UE starts receiving grants (new TBs) with NDI=0. In grants containing EAI=0, EAI means that the previous packet (NDI=1) has been correctly received. Otherwise, when the grant includes EAI=1, EAI means that the previous packet was not correctly received.

[0103] In a third aspect, the UE may be configured with a maximum number of retransmissions. The UE may declare a packet as lost based on the DCI carrying the NAK feedback or whether the maximum number of retransmissions is met for the packet. For example, the gNB scheduler may operate based on the maximum number of retransmissions for a given packet. After this number is reached, the gNB will no longer attempt to reschedule. Therefore, providing this number to the UE in the NAK feedback allows the UE to track the number of transmissions for a given frame or packet. When the number of transmissions is reached, the gNB may pass the NAK feedback to the UE. In some cases, the third aspect may be combined with either of the first two aspects. For example, the gNB may abandon the lost frame or packet before the number of retransmissions reaches the maximum number of retransmissions.

[0104] In the second and third aspects, the PHY may pass the NAK feedback to layers higher than the PHY layer ("higher layers"). The higher layers may map the failed TBs to different packets. The encoding device may provide an indication of the NAK feedback to processing layers above the PHY layer to identify lost frames, packets, or segments for retransmission. For example, if the RLC is operating in acknowledged mode (RLC AM), the network may mark the corresponding packets or segments for retransmission (i.e., the same as obtaining a NAK from the other end RLC entity). If the RLC is operating in unacknowledged mode (RLC UM), the network entity may pass the failure message up the stack (no recovery - the encoder will receive a NAK). If the PDCP is running duplication, the two RLC legs may be negatively acknowledged (NACK'd) so that the PDCP passes the failure to the upper layers. RLC AM and RLC UM are in Fig. 11C Further discussion in.

[0105] Fig. 11B An example of network coding feedback provided via a media access control (MAC) layer acknowledgement in accordance with certain aspects of the present disclosure is shown. Via the MAC layer, the gNB may indicate to the UE in the downlink direction with a NAK feedback (e.g., a MAC control element (CE)) that the gNB has discarded a frame or packet and will not request further retransmissions thereof. The MAC CE indicates the lost packets and is transmitted on the same component carrier (CC) as the scheduled media frame. For example, the MAC CE indicates one or more HARQ process IDs of the one or more lost packets. The MAC CE may include a component carrier (CC) indicator that identifies which CC the HARQ process ID relates to. In some cases, the MAC CE includes an NDI corresponding to the failed HARQ process ID.

[0106] In a first example case, the gNB may transmit a MAC CE on the same CC as the uplink data. The indication includes the HARQ process ID that the gNB decided to refresh. In a second example case, the gNB may transmit a MAC CE in a different CC than the uplink data. In this case, the MAC CE indicates the CC index of the failed HARQ process. In either of the first and second cases, there may be a "running condition" problem between the MAC CE and the identification of the HARQ process. A problem may arise when the coding device receives the MAC CE while the gNB may start a new UL transmission for the same HARQ process. This problem can be solved by the gNB not scheduling the same HARQ process until the MAC CE is acknowledged. Alternatively, the problem can be solved by including the NDI in the MAC CE so that the NDI corresponds to the failed HARQ process. In this way, the gNB can start a new transmission using the switched NDI. These solutions are applicable to either the first or second case.

[0107] Fig. 11C An example of network coding feedback provided via a radio link control (RLC) status report in accordance with certain aspects of the present disclosure is shown. A UE may transmit media frames in an RLC unacknowledged mode (UM) via unsegmented RLC service data units (SDUs) with sequence numbers. As shown, the gNB may transmit NAK feedback indicating the lost sequence number of the RLC SDU. For example, at the RLC layer, when the transmission of one of the media frames fails, the error may be detected as a "hole" in the receive window. With current RLC UMs, RLC SDUs typically do not have sequence numbers, so detecting lost packets may be difficult (unless all RLC SDUs are segmented). Therefore, by configuring the RLC UM so that unsegmented RLC SDUs (and segmented RLC SDUs) carry sequence numbers, "holes" in the receive window may be accurately identified. The sequence number may be implemented through RRC configuration for each RLC entity.

[0108] In some cases, the receiving RLC entity may run a timer each time a "hole" is detected (e.g., an RLC SDU with SN=x is received, but SN=x-1 has not yet been received). If no RLC SDU is received before the timer expires (e.g., 10-50 milliseconds, or depending on the frame rate), the receiving RLC entity will transmit a NAK feedback indicating the missing SN.

[0109] In such examples, the RLC UM behavior may be similar to that of RLC AM. The difference is that NAK feedback does not trigger retransmission of the lost frame at the UE. The NAK feedback from the gNB only informs higher layers about the lost frame. This technique can be implemented with RLC AM by changing the maximum number of retransmissions to “0” to achieve a similar effect.

[0110] In some cases, the decoding device or receiving entity may also transmit NAK feedback if some received segments are discarded, such as, for example, due to the SN being outside the reassembly window, or due to expiration of t-reassembly.

[0111] In terms of RLC AM, the UE may retransmit the lost frame upon receiving NAK feedback from the gNB and record the number of retransmissions of the lost frame. When the maximum number of retransmissions has been reached, the UE may indicate to the upper layers that a given packet has failed. Thus, the UE may declare an RLC SDU lost based on NAK feedback or whether the maximum number of retransmissions of the RLC SDU is met. The UE may provide an indication of the lost RLC SDU to the upper layers.

[0112] Fig.11DAn example of network coding feedback provided via a Packet Data Convergence Protocol (PDCP) status report in accordance with certain aspects of the present disclosure is shown. In various aspects, the UE may declare a PDCP SDU as failed based on NAK feedback from the gNB or expiration of an SDU timer. The UE may provide an indication of the failed SDU to the application layer.

[0113] Fig.12 A communication device 1200 (eg, UE) is shown, which may include devices configured to perform operations for the techniques disclosed herein (such as Figure 8 1200 (e.g., corresponding to means-plus-function components). The communication device 1200 includes a processing system 1202 coupled to a transceiver 1208 (e.g., a transmitter and / or a receiver). The transceiver 1208 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1200 via an antenna 1210. The processing system 1202 may be configured to perform processing functions for the communication device 1200, including processing signals received and / or to be transmitted by the communication device 1200.

[0114] The processing system 1202 includes a processor 1204 coupled to a non-transitory computer readable medium / memory 1212 via a bus 1206. In some aspects, the computer readable medium / memory 1212 is configured to store instructions (e.g., computer executable code) that, when executed by the processor 1204, cause the processor 1204 to perform Figure 8 Operation 800 as shown, or other operations for performing various techniques discussed herein. In some aspects, the computer-readable medium / memory 1212 stores: code 1213 for transmitting a request to a network entity for a configuration to configure an encoding device to send a media frame to a decoding device, whereby the network entity is configured to provide negative acknowledgement (NAK) feedback indicating at least one lost frame; code 1215 for receiving a configuration in response to the request; code 1217 for sending the media frame to the decoding device via the network entity; and code 1219 for monitoring NAK feedback from the network entity according to the configuration. In some aspects, the processor 1204 has circuitry configured to implement the code stored in the computer-readable medium / memory 1212. Based on the indicated UE's ability to switch between CCs, processor 1204 includes: a circuit 1218 for transmitting a request to a network entity for a configuration in which the encoding device is configured to send media frames to a decoding device, whereby the network entity is configured to provide negative acknowledgement (NAK) feedback indicating at least one lost frame; a circuit 1220 for receiving a configuration in response to the request; a circuit 1222 for sending the media frame to the decoding device via the network entity; and a circuit 1224 for monitoring NAK feedback from the network entity based on the configuration.

[0115] Fig.13 A communication device 1300 (eg, UE) is shown, which may include devices configured to perform operations for the techniques disclosed herein (such as Fig. 9 1300). The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or a receiver). The transceiver 1308 is configured to transmit and receive signals, such as the various signals described herein, for the communication device 1300 via an antenna 1310. The processing system 1302 may be configured to perform processing functions for the communication device 1300, including processing signals received and / or transmitted by the communication device 1300.

[0116] The processing system 1302 includes a processor 1304 coupled to a non-transitory computer readable medium / memory 1312 via a bus 1306. In some aspects, the computer readable medium / memory 1312 is configured to store instructions (e.g., computer executable code) that, when executed by the processor 1304, cause the processor 1304 to perform Fig. 9 , or other operations for performing various techniques discussed herein. In some aspects, the computer-readable medium / memory 1312 stores: code 1313 for receiving a request from an encoding device for a configuration to configure the encoding device to send a media frame to a decoding device, wherein the configuration enables a network entity to provide a negative acknowledgement (NAK) feedback indicating at least one lost frame from the encoding device; code 1315 for transmitting the configuration in response to the request; code 1317 for receiving a media frame from the encoding device to stream the media frame to a decoding device; and code 1319 for transmitting the NAK feedback to the encoding device according to the configuration. In some aspects, the processor 1304 has circuitry configured to implement the code stored in the computer-readable medium / memory 1312. Based on the indicated ability of the UE to switch between CCs, processor 1304 includes: circuit 1318 for receiving a request from an encoding device for a configuration to configure the encoding device to send media frames to a decoding device, wherein the configuration enables a network entity to provide a negative acknowledgement (NAK) feedback indicating at least one lost frame from the encoding device; circuit 1320 for transmitting the configuration in response to the request; circuit 1322 for receiving media frames from the encoding device to stream the media frames to the decoding device; and circuit 1324 for transmitting the NAK feedback to the encoding device based on the configuration.

[0117] Example aspects

[0118] Aspect 1: A method for wireless communication by an encoding device, comprising: transmitting a request to a network entity for a configuration to configure the encoding device to send media frames to a decoding device, whereby the network entity is configured to provide negative acknowledgment (NAK) feedback indicating at least one lost frame; receiving a configuration in response to the request; sending a media frame to the decoding device via the network entity; and monitoring NAK feedback from the network entity according to the configuration.

[0119] Aspect 2: A method according to Aspect 1, wherein: the media frame includes one or more key frames, and the one or more key frames include decoding information required to decode non-key frames; and the method also includes sending a correction frame generated from the non-key frame, the corresponding decoding information of the at least one lost frame, or both.

[0120] Aspect 3: The method according to Aspect 2, wherein the correction frame includes information of the lost frame.

[0121] Aspect 4: A method according to any one of Aspects 1-3, wherein the NAK feedback indicates a lost packet, and the method further comprises determining that the network entity will not trigger a retransmission of the lost packet; and refreshing a hybrid automatic repeat request (HARQ) buffer based on the determination.

[0122] Aspect 5: The method according to any one of aspects 1-4, wherein the NAK feedback is transmitted via downlink control information (DCI) indicating a hybrid automatic repeat request (HARQ) process ID of the lost packet.

[0123] Aspect 6: The method according to Aspect 5, wherein: the DCI comprises a plurality of bits; and the DCI indicates the HARQ process ID via a starting bit position within the plurality of bits.

[0124] Aspect 7: According to the method of Aspect 6, at least one of the following items: the reserved values ​​of the multiple bits indicate no NAK; the DCI indicates NAK feedback of multiple HARQ process IDs; or the DCI indicates NAK feedback of different coding devices.

[0125] Aspect 8: The method according to any one of aspects 5-7, wherein the DCI includes multiple fields for multiple hybrid automatic repeat request (HARQ) processes for multiple failed frames among multiple frames of information.

[0126] Aspect 9: The method according to any one of aspects 5-8, wherein the DCI is transmitted on the same component carrier (CC) that schedules the media frame.

[0127] Aspect 10: The method according to any one of aspects 5-9, wherein the DCI includes a component carrier (CC) indicator identifying which CC the HARQ process ID relates to.

[0128] Aspect 11: A method according to any one of Aspects 5-10, wherein the DCI includes: a switched new data indicator (NDI), indicating that the decoding device will transmit a packet with a new transport block (TB); and an explicit acknowledgment indicator (EAI), indicating whether a previous packet corresponding to the same HARQ process was successfully received.

[0129] Aspect 12: The method according to any one of Aspects 5-11 further includes: receiving a configuration for a maximum number of retransmissions; and declaring the packet as lost based on the DCI carrying NAK feedback or whether the maximum number of retransmissions is met for the packet.

[0130] Aspect 13: The method according to any one of aspects 5-12 further comprises: providing an indication of the NAK feedback to a processing layer above the physical layer to identify lost frames, packets or segments for retransmission.

[0131] Aspect 14: The method according to aspect 1, wherein the NAK feedback is transmitted via a medium access control (MAC) control element (CE) indicating that a packet is lost and the network entity will not request a retransmission.

[0132] Aspect 15: The method according to aspect 14, wherein the MAC CE is transmitted on the same component carrier (CC) that schedules the media frame and indicates one or more hybrid automatic repeat request (HARQ) process IDs of the one or more lost packets.

[0133] Aspect 16: The method according to aspect 14 or 15, wherein the MAC CE includes a component carrier (CC) indicator identifying which CC the hybrid automatic repeat request (HARQ) process ID relates to.

[0134] Aspect 17: The method according to any one of aspects 14-16, wherein the MAC CE includes: a switched new data indicator (NDI) corresponding to a failed hybrid automatic repeat request (HARQ) process ID.

[0135] Aspect 18: A method according to Aspect 1, wherein: the media frame is transmitted in RLC unacknowledged mode (UM) via an unsegmented radio link control (RLC) service data unit (SDU) with a sequence number; and the NAK feedback indicates a lost sequence number of the RLC SDU.

[0136] Aspect 19: The method according to Aspect 1 also includes: declaring a radio link control (RLC) SDU as lost based on NAK feedback or whether the maximum number of retransmissions of the RLC SDU is met; and providing an indication of the lost RLC SDU to an upper layer.

[0137] Aspect 20: The method according to aspect 1 further comprises declaring a packet data convergence protocol (PDCP) SDU as failed based on NAK feedback or expiration of an SDU timer, and providing an indication of the failed SDU to the application layer.

[0138] Aspect 21: The method according to aspect 1, wherein the encoding device requests configuration for at least one of a logical channel or a radio bearer.

[0139] Aspect 22: A method according to Aspect 21, wherein: the NAK feedback is provided via radio link control (RLC) or packet data convergence protocol (PDCP) signaling; and the NAK feedback indicates that the lost packet is in a logical channel indicated by the encoding device.

[0140] Aspect 23: A method according to Aspect 21 or 22, wherein: the NAK feedback is provided via physical layer or media access control (MAC) layer signaling; and the encoding device determines the logical channel of the lost packet based on a mapping from logical channels to component carriers or physical layer priorities.

[0141] Aspect 24: The method according to aspect 1, wherein one or more media frames are transmitted by being segmented into a plurality of packets; and the method further comprises identifying frame failure based on a mapping of frames to packets.

[0142] Aspect 25: A method for wireless communication by a network entity, comprising: receiving a request from an encoding device for a configuration to configure the encoding device to send media frames to a decoding device, wherein the configuration enables the network entity to provide a negative acknowledgement (NAK) feedback indicating at least one lost frame from the encoding device; transmitting the configuration in response to the request; receiving a media frame from the encoding device to stream the media frame to the decoding device; and transmitting the NAK feedback to the encoding device according to the configuration.

[0143] Aspect 26: A method according to Aspect 25, wherein: the media frame includes one or more key frames, and the one or more key frames include decoding information required to decode non-key frames; and the method also includes sending a correction frame generated from the non-key frame, and corresponding decoding information of at least one lost frame.

[0144] Aspect 27: The method according to Aspect 26, wherein the correction frame includes information of the lost frame.

[0145] Aspect 28: According to the method of Aspect 25, the NAK feedback is transmitted via downlink control information (DCI) indicating a hybrid automatic repeat request (HARQ) process ID of the lost packet.

[0146] Aspect 29: The method according to Aspect 28, wherein the DCI comprises a plurality of bits; and the DCI indicates the HARQ process ID via a starting bit position in the plurality of bits.

[0147] Aspect 30: According to the method of Aspect 28 or 29, at least one of the following items: the reserved value of the multiple bits indicates no NAK; the DCI indicates NAK feedback of multiple HARQ process IDs; or the DCI indicates NAK feedback of different coding devices.

[0148] Aspect 31: The method according to any one of aspects 28-30, wherein the DCI includes multiple fields for multiple hybrid automatic repeat request (HARQ) processes for multiple failed frames in the multiple frames of information.

[0149] Aspect 32: The method according to any one of aspects 28-31, wherein the DCI is transmitted on the same component carrier (CC) that schedules the media frame.

[0150] Aspect 33: The method according to any one of aspects 28-32, wherein the DCI includes a component carrier (CC) indicator identifying which CC the HARQ process ID relates to.

[0151] Aspect 34: A method according to any one of Aspects 28-33, wherein the DCI includes: a switched new data indicator (NDI), indicating that the decoding device will transmit a packet with a new transport block (TB); and an explicit acknowledgment indicator (EAI), indicating whether a previous packet corresponding to the same HARQ process was successfully received.

[0152] Aspect 35: The method according to any one of Aspects 28-34 further includes: transmitting a configuration for a maximum number of retransmissions; declaring the packet as lost based on a DCI carrying NAK feedback or whether the maximum number of retransmissions is met for the packet.

[0153] Aspect 36: The method according to aspect 25, wherein the NAK feedback is transmitted via a medium access control (MAC) control element (CE) indicating that the packet was lost and the network entity will not request a retransmission.

[0154] Aspect 37: The method according to Aspect 36, wherein the MAC CE is transmitted on the same component carrier (CC) that schedules the media frame and indicates one or more hybrid automatic repeat request (HARQ) process IDs of the one or more lost packets.

[0155] Aspect 38: The method according to aspect 36 or 37, wherein the MAC CE includes a component carrier (CC) indicator identifying which CC the hybrid automatic repeat request (HARQ) process ID relates to.

[0156] Aspect 39: The method according to any one of aspects 36-39, wherein the MAC CE includes: a switched new data indicator (NDI) corresponding to a failed hybrid automatic repeat request (HARQ) process ID.

[0157] Aspect 40: A method according to Aspect 25, wherein: a media frame having an unsegmented radio link control (RLC) service data unit (SDU) with a sequence number is transmitted in an RLC unacknowledged mode (UM); and the NAK feedback indicates a missing sequence number of the RLC SDU.

[0158] Aspect 41: The method according to aspect 25, wherein the request is for at least one of a logical channel or a radio bearer.

[0159] Aspect 42: A method according to Aspect 41, wherein: the NAK feedback is provided via radio link control (RLC) or packet data convergence protocol (PDCP) signaling; and the NAK feedback indicates that the lost packet is in a logical channel indicated by the encoding device.

[0160] Aspect 43: The method according to Aspect 41 or 42, wherein the NAK feedback is provided via physical layer or medium access control (MAC) layer signaling.

[0161] Aspect 44: The method according to Aspect 25, wherein one or more media frames are transmitted by being segmented into a plurality of packets; and the method further comprises: identifying frame failure based on a mapping of frames to packets.

[0162] Aspect 45: An apparatus for wireless communication by an encoding device, comprising means for performing the method of any one or more of Aspects 1-24.

[0163] Aspect 46: An apparatus for wireless communication by a network entity, comprising means for performing the method of any one or more of Aspects 25-44.

[0164] Aspect 47: A computer-readable medium having instructions stored thereon, which, when executed by a processor, performs the method of any one of claims 1-24.

[0165] Aspect 48: A computer-readable medium having instructions stored thereon, which, when executed by a processor, performs the method of any one of claims 25-44.

[0166] The method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be changed without departing from the scope of the claims.

[0167] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0168] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include computing, calculating, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0169] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one", but "one or more", unless otherwise specifically stated. Unless otherwise specifically stated, the term "some / some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structurally and functionally equivalent schemes currently or hereafter known to those of ordinary skill in the art, and are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be contributed to the public, regardless of whether such disclosure is explicitly stated in the claims. Any element of a claim should not be interpreted under the provisions of 35 U.S.C. §112 (f), unless the element is explicitly stated using the wording "device for..." or in the case of a method claim, the element is stated using the wording "step for...".

[0170] The various operations of the methods described above may be performed by any suitable means capable of performing the corresponding functions. These means may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where there are operations illustrated in the figures, those operations may have corresponding corresponding means-plus-function components. For example, Figure 8 and Fig. 9 The various operations shown can be performed by Figure 2 The various processors of BS 110 and / or UE 120 are shown to execute.

[0171] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), 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 commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0172] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the user terminal 120 (see Figure 1 ), a user interface (e.g., keyboard, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and will not be described further. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall system.

[0173] If implemented in software, the function can be stored or sent on a computer-readable medium as one or more instructions or codes. Software should be broadly interpreted as meaning instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both computer storage media and communication media, which include any media that facilitate the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read / write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separated from a wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any portion thereof may be integrated into a processor, such as a situation where a cache and / or a general register file may be used. As an example, examples of machine-readable storage media may include various non-transitory memories, such as RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. The machine-readable medium may be implemented in a computer program product.

[0174] A software module may include a single instruction or many instructions, and may be distributed over several different code segments, distributed in different programs, and distributed across multiple storage media. A computer-readable medium may include several software modules. These software modules include instructions that cause a processing system to perform various functions when executed by a device (such as a processor). These software modules may include a sending module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded into a RAM from a hard drive. During the execution of the software module, the processor may load some instructions into a cache to increase access speed. One or more cache lines may be subsequently loaded into a general register file for execution by the processor. When describing the functionality of a software module as described below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0175] Moreover, any connection is 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 technology (such as infrared (IR), radio and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio and microwave) is included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Disks, where disks often reproduce data magnetically, and discs reproduce data optically with lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0176] Thus, some aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored (and / or encoded) thereon instructions that can be executed by one or more processors to perform the operations described herein. For example, for performing the operations described herein and Figure 8 and Fig. 9 The operations shown in the instructions.

[0177] In addition, it should be appreciated that the modules and / or other appropriate devices for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by the user terminal and / or base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of the device for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.) so that once the storage device is coupled to or provided to the user terminal and / or base station, the device can obtain the various methods. In addition, any other suitable technology suitable for providing the methods and techniques described herein to the device can be utilized.

[0178] It will be understood that the claims are not limited to the precise configuration and components shown above. Various changes, substitutions and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. An apparatus for wireless communication at an encoding device, include: Memory; as well as a processor coupled to the memory, the memory and the processor being configured to: transmitting to a network entity a request for configuring the encoding device to send media frames to a decoding device, whereby the network entity is configured to provide negative acknowledgement (NAK) feedback indicating at least one lost frame without requesting retransmission of the at least one lost frame; receiving the configuration in response to the request; sending the media frame to the decoding device via the network entity; as well as According to the configuration, NAK feedback from the network entity is monitored.

2. The device according to claim 1, in: The media frame includes one or more key frames, the one or more key frames including decoding information required to decode non-key frames; and The memory and the processor are further configured to transmit a correction frame generated from a non-key frame, corresponding decoded information of the at least one lost frame, or both.

3. The device as claimed in claim 2, in, The correction frame includes information of the lost frame.

4. The device according to claim 1, in, The NAK feedback indicates a lost packet, and the memory and the processor are further configured to: determining that the network entity will not trigger a retransmission of the lost packet; as well as A hybrid automatic repeat request (HARQ) buffer is flushed based on the determination.

5. The device according to claim 1, in, The NAK feedback is transmitted via downlink control information DCI indicating the hybrid automatic repeat request HARQ process ID of the lost packet.

6. The device as claimed in claim 5, in: The DCI includes a plurality of bits; and The DCI indicates the HARQ process ID via a starting bit position within a plurality of bits.

7. The device of claim 6, wherein at least one of: The reserved value of the plurality of bits indicates an absence of NAK; The DCI indicates NAK feedback of multiple HARQ process IDs; or The DCI indicates NAK feedback of different coding devices.

8. The device according to claim 7, in, The DCI includes a plurality of fields for a plurality of hybrid automatic repeat request (HARQ) processes for a plurality of failed frames among a plurality of frames of information.

9. The device according to claim 6, in, The DCI is transmitted on the same component carrier CC that schedules the media frame.

10. The device according to claim 6, in, The DCI includes a component carrier CC indicator identifying which CC the HARQ process ID relates to.

11. The device according to claim 5, in, The DCI includes: a switched new data indicator NDI indicating that the decoding device will transmit a packet with a new transport block TB; and The explicit acknowledgement indicator EAI indicates whether the previous packet corresponding to the same HARQ process was successfully received.

12. The device according to claim 5, in, The memory and the processor are further configured to: receiving a configuration for a maximum number of retransmissions; and The packet is declared lost based on the DCI carrying the NAK feedback or whether the maximum number of retransmissions is met for the packet.

13. The device according to claim 5, in, The memory and the processor are further configured to: An indication of NAK feedback is provided to processing layers above the physical layer to identify lost frames, packets, or segments for retransmission.

14. The device according to claim 1, in, The NAK feedback is transmitted via a Medium Access Control MAC Control Element CE indicating that a packet is lost and that the network entity will not request a retransmission.

15. The device according to claim 14, in, The MAC CE is transmitted on the same component carrier CC that scheduled the media frame and indicates one or more hybrid automatic repeat request HARQ process IDs of one or more lost packets.

16. The device according to claim 14, in, The MAC CE includes a component carrier CC indicator identifying which CC the hybrid automatic repeat request HARQ process ID relates to.

17. The device according to claim 14, in, The MAC CE includes: The switched new data indicator NDI corresponding to the failed hybrid automatic repeat request HARQ process ID.

18. The device according to claim 1, in: The media frame is transmitted in RLC unacknowledged mode UM via an unsegmented radio link control RLC service data unit SDU having a sequence number; and The NAK feedback indicates the missing sequence number of the RLC SDU.

19. The apparatus of claim 1, wherein the memory and the processor are further configured to: Declaring the RLC SDU as lost based on NAK feedback or whether the maximum number of retransmissions of the radio link control RLC SDU is met; and Provides an indication to upper layers of missing RLC SDUs.

20. The apparatus of claim 1, wherein the memory and the processor are further configured to: Declaring a Packet Data Convergence Protocol PDCP SDU as failed based on NAK feedback or SDU timer expiration; and Provides an indication of failed SDUs to the application layer.

21. The device according to claim 1, in, The encoding device requests configuration for at least one of a logical channel or a radio bearer.

22. The device according to claim 21, in: The NAK feedback is provided via Radio Link Control RLC or Packet Data Convergence Protocol PDCP signaling; and The NAK feedback indicates that the lost packet is in a logical channel indicated by the encoding device.

23. The device according to claim 21, in: The NAK feedback is provided via physical layer or medium access control MAC layer signaling; and The encoding device determines a logical channel of a lost packet based on a mapping from logical channels to component carriers or physical layer priorities.

24. The device according to claim 1, in: One or more media frames are transmitted by being segmented into a plurality of packets; and The memory and the processor are further configured to identify a frame failure based on a frame-to-packet mapping.

25. An apparatus for wireless communication at a network entity, include: Memory; as well as a processor coupled to the memory, the memory and the processor being configured to: receiving, from an encoding device, a request for a configuration to configure the encoding device to send media frames to a decoding device, wherein the configuration enables the network entity to provide negative acknowledgement (NAK) feedback indicating at least one lost frame from the encoding device without requesting retransmission of the at least one lost frame; transmitting the configuration in response to the request; receiving a media frame from the encoding device to stream the media frame to the decoding device; as well as According to the configuration, the NAK feedback is transmitted to the encoding device.

26. The device according to claim 25, in: The media frame includes one or more key frames, the one or more key frames including decoding information required to decode non-key frames; and The memory and the processor are further configured to transmit a corrected frame generated from a non-key frame and corresponding decoded information of at least one lost frame.

27. The device according to claim 25, in, The NAK feedback is transmitted via downlink control information DCI indicating the hybrid automatic repeat request HARQ process ID of the lost packet.

28. The device of claim 25, in: One or more media frames are transmitted by being segmented into a plurality of packets; and The memory and the processor are further configured to identify a frame failure based on a frame-to-packet mapping.

29. A method for wireless communication at an encoding device, include: transmitting to a network entity a request for configuring the encoding device to send media frames to a decoding device, whereby the network entity is configured to provide negative acknowledgement (NAK) feedback indicating at least one lost frame without requesting retransmission of the at least one lost frame; receiving the configuration in response to the request; sending the media frame to the decoding device via the network entity; as well as According to the configuration, NAK feedback from the network entity is monitored.

30. A method of wireless communication at a network entity, include: receiving, from an encoding device, a request for a configuration to configure the encoding device to send media frames to a decoding device, wherein the configuration enables the network entity to provide negative acknowledgement (NAK) feedback indicating at least one lost frame from the encoding device without requesting retransmission of the at least one lost frame; transmitting the configuration in response to the request; receiving a media frame from the encoding device to stream the media frame to the decoding device; as well as According to the configuration, the NAK feedback is transmitted to the encoding device.

31. An apparatus for wireless communication, comprising means for performing the method according to any one of claims 29-30.

32. A computer readable medium having stored thereon instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 29-30.

33. A computer program product comprising computer instructions which, when executed by a processor, cause the processor to perform the method according to any one of claims 29-30.

Images