WO2019104513A1 - Apparatus and methods to recover missing rlc pdus - Google Patents
Apparatus and methods to recover missing rlc pdus Download PDFInfo
- Publication number
- WO2019104513A1 WO2019104513A1 PCT/CN2017/113497 CN2017113497W WO2019104513A1 WO 2019104513 A1 WO2019104513 A1 WO 2019104513A1 CN 2017113497 W CN2017113497 W CN 2017113497W WO 2019104513 A1 WO2019104513 A1 WO 2019104513A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- grant
- status
- met
- pdu
- size
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1854—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1848—Time-out mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
Definitions
- the present disclosure relates generally to communication systems, and more particularly, to methods and apparatus for recovering missing RLC PDUs (e.g., efficiently recovering missing radio link control (RLC) protocol data units (PDUs) when grant is insufficient to include all the negative acknowledgement (NACK) information) using communications systems operating according to radio technologies, such as LTE and/or new radio (NR) technologies.
- RLC radio link control
- NACK negative acknowledgement
- Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
- Typical 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) .
- multiple-access technologies include Long Term Evolution (LTE) 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.
- LTE Long Term Evolution
- CDMA code division multiple access
- TDMA time division multiple access
- FDMA frequency division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single-carrier frequency division multiple access
- TD-SCDMA time division synchronous code division multiple access
- CUs central units
- CUs central units
- CNs central nodes
- ANCs access node controllers
- a set of one or more distributed units, in communication with a central unit may define an access node (e.g., a new radio base station (NR BS) , a new radio node-B (NR NB) , a network node, 5G NB, eNB, Next Generation Node B (gNB) , etc. ) .
- NR BS new radio base station
- NR NB new radio node-B
- gNB Next Generation Node B
- a base station or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a UE to a base station or distributed unit) .
- downlink channels e.g., for transmissions from a base station or to a UE
- uplink channels e.g., for transmissions from a UE to a base station or distributed unit
- NR new radio
- 3GPP Third Generation Partnership Project
- Certain aspects provide methods and apparatus for recovering missing RLC PDUs (e.g., efficiently recovering missing RLC PDUs when grant is insufficient to include all the NACK information) using communications systems operating according to radio technologies, such as LTE and/or new radio (NR) technologies.
- radio technologies such as LTE and/or new radio (NR) technologies.
- a method for wireless communications by a user equipment includes determining whether one or more grant conditions are met, and transmitting a partial status protocol data unit (PDU) and a buffer status report (BSR) based on the one or more grant conditions being met before starting a status prohibit timer if the one or more grant conditions are met.
- PDU partial status protocol data unit
- BSR buffer status report
- a method for wireless communications by a base station includes determining a size of an uplink (UL) grant for a user equipment (UE) , and receiving a partial status protocol data unit (PDU) and a buffer status report (BSR) having the size of the UL grant from the UE based on one or more grant conditions being met.
- BS base station
- the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
- the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
- FIG. 1 is a block diagram conceptually illustrating an example telecommunications system, in which aspects of the present disclosure may be performed.
- FIG. 3 is a diagram illustrating an example physical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure.
- FIG. 4 is a block diagram conceptually illustrating a design of an example BS and user equipment (UE) , in accordance with certain aspects of the present disclosure.
- FIG. 6 illustrates an example of a DL-centric subframe, in accordance with certain aspects of the present disclosure.
- FIG. 7 illustrates an example of an UL-centric subframe, in accordance with certain aspects of the present disclosure.
- FIG. 8 illustrates an example of sending one or more a partial status PDUs, in accordance with aspects of the present disclosure.
- FIG. 9 illustrates example operations for wireless communications by a user equipment (UE) , in accordance with aspects of the present disclosure.
- UE user equipment
- FIG. 10 illustrates example operations for wireless communications by a base station (BS) , in accordance with aspects of the present disclosure.
- BS base station
- FIG. 11 illustrates an example of sending one or more of a partial status PDU and/or BSR when certain conditions are met, in accordance with aspects of the present disclosure.
- FIG. 12 illustrates a flow chart that includes example operations for wireless communications, in accordance with aspects of the present disclosure.
- aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for radio technologies, such as LTE and/or NR (new radio access technology or 5G technology) .
- radio technologies such as LTE and/or NR (new radio access technology or 5G technology) .
- NR may support various wireless communication services, such as Enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g. 27 GHz or beyond) , massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) .
- eMBB Enhanced mobile broadband
- mmW millimeter wave
- mMTC massive MTC
- URLLC ultra-reliable low latency communications
- These services may include latency and reliability requirements.
- These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements.
- TTI transmission time intervals
- QoS quality of service
- these services may co-exist in the same subframe.
- E-UTRA Evolved UTRA
- UMB Ultra Mobile Broadband
- IEEE 802.11 Wi-Fi
- IEEE 802.16 WiMAX
- IEEE 802.20 Flash-OFDMA
- UMTS Universal Mobile Telecommunication System
- NR is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF) .
- 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA.
- LTE refers generally to LTE, LTE-Advanced (LTE-A) , LTE in an unlicensed spectrum (LTE-whitespace) , etc.
- LTE-A LTE-Advanced
- LTE-whitespace LTE in an unlicensed spectrum
- the wireless network 100 may include a number of BSs 110 and other network entities.
- a BS may be a station that communicates with UEs.
- Each BS 110 may provide communication coverage for a particular geographic area.
- the term “cell” can refer to a coverage area of a Node B and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used.
- the term “cell” and eNB, Node B, 5G NB, AP, NR BS, NR BS, gNB, or TRP may be interchangeable.
- a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station.
- the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, or the like using any suitable transport network.
- any number of wireless networks may be deployed in a given geographic area.
- Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies.
- a RAT may also be referred to as a radio technology, an air interface, etc.
- a frequency may also be referred to as a carrier, a frequency channel, etc.
- Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
- NR or 5G RAT networks may be deployed.
- a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell.
- a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
- a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
- a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG) , UEs for users in the home, etc. ) .
- CSG Closed Subscriber Group
- 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.
- the BSs 110a, 110b and 110c may be macro BSs for the macro cells 102a, 102b and 102c, respectively.
- the BS 110x may be a pico BS for a pico cell 102x.
- the BSs 110y and 110z may be femto BS for the femto cells 102y and 102z, respectively.
- a BS may support one or multiple (e.g., three) cells.
- the wireless network 100 may also include relay stations.
- a relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS or a UE) and sends a transmission 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.
- a relay station 110r may communicate with the BS 110a and a UE 120r in order 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, etc.
- the wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100.
- macro BS may have a high transmit power level (e.g., 20 Watts) whereas pico BS, femto BS, and relays may have a lower transmit power level (e.g., 1 Watt) .
- the wireless network 100 may support synchronous or asynchronous operation.
- the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time.
- the BSs 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.
- a network controller 130 may be coupled 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 one another, e.g., directly or indirectly via wireless or wireline backhaul.
- the UEs 120 may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile.
- a UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE) , a cellular phone, a smart phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a healthcare device, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.
- CPE Customer Premises Equipment
- PDA personal digital assistant
- an entertainment device e.g., a music device, a video device, a satellite radio, etc.
- a vehicular component or sensor e.g., a smart meter/sensor, a robot, a drone, industrial manufacturing equipment, a positioning device (e.g., GPS, Beidou, terrestrial) , or any other suitable device that is configured to communicate via a wireless or wired medium.
- a positioning device e.g., GPS, Beidou, terrestrial
- Some UEs may be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices, which may include remote devices that may communicate with a base station, another remote device, or some other entity.
- MTC machine-type communication
- eMTC evolved MTC
- Machine type communications may refer to communication involving at least one remote device on at least one end of the communication and may include forms of data communication which involve one or more entities that do not necessarily need human interaction.
- MTC UEs may include UEs that are capable of MTC communications with MTC servers and/or other MTC devices through Public Land Mobile Networks (PLMN) , for example.
- PLMN Public Land Mobile Networks
- MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, cameras, location tags, etc., that may communicate with a BS, another device (e.g., remote device) , or some other entity.
- a wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
- MTC UEs may be implemented as Internet-of-Things (IoT) devices, e.g., narrowband IoT (NB-IoT) devices.
- IoT Internet-of-Things
- NB-IoT narrowband IoT
- a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink.
- a dashed line with double arrows indicates interfering transmissions between a UE and a BS.
- Certain wireless networks utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink.
- OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc.
- K orthogonal subcarriers
- Each subcarrier may be modulated with data.
- modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM.
- the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth.
- the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a ‘resource block’) may be 12 subcarriers (or 180 kHz) . Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz) , respectively.
- the system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (e.g., 6 resource blocks) , and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.
- NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using time division duplex (TDD) .
- TDD time division duplex
- a single component carrier bandwidth of 100 MHz may be supported.
- NR resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration.
- Each radio frame may consist of 2 half frames, each half frame consisting of 5 subframes, with a length of 10 ms. Consequently, each subframe may have a length of 1 ms.
- Each subframe may indicate a link direction (e.g., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched.
- Each subframe may include DL/UL data as well as DL/UL control data.
- UL and DL subframes for NR may be as described in more detail below with respect to FIGs. 6 and 7.
- Beamforming may be supported and beam direction may be dynamically configured.
- MIMO transmissions with precoding may also be supported.
- MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells.
- NR may support a different air interface, other than an OFDM-based.
- NR networks may include entities such CUs and/or DUs.
- a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.
- a RAN may include a CU and DUs.
- a NR BS e.g., eNB, 5G Node B, Node B, transmission reception point (TRP) , access point (AP)
- NR cells can be configured as access cell (ACells) or data only cells (DCells) .
- the RAN e.g., a central unit or distributed unit
- DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals-in some case cases DCells may transmit SS.
- NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.
- FIG. 2 illustrates an example logical architecture of a distributed radio access network (RAN) 200, which may be implemented in the wireless communication system illustrated in FIG. 1.
- a 5G access node 206 may include an access node controller (ANC) 202.
- the ANC 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.
- the backhaul interface to neighboring next generation access nodes (NG- ANs) may terminate at the ANC.
- the ANC may include one or more TRPs 208 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, gNBs, or some other term) .
- TRPs 208 which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, gNBs, or some other term.
- TRP may be used
- the TRPs 208 may be a DU.
- the TRPs may be connected to one ANC (ANC 202) or more than one ANC (not illustrated) .
- ANC ANC
- RaaS radio as a service
- a TRP may include one or more antenna ports.
- the TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
- the local architecture 200 may be used to illustrate fronthaul definition.
- the architecture may be defined that support fronthauling solutions across different deployment types.
- the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter) .
- the architecture may share features and/or components with LTE.
- the next generation AN (NG-AN) 210 may support dual connectivity with NR.
- the NG-AN may share a common fronthaul for LTE and NR.
- the architecture may enable cooperation between and among TRPs 208. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 202. According to aspects, no inter-TRP interface may be needed/present.
- a dynamic configuration of split logical functions may be present within the architecture 200.
- the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU or CU (e.g., TRP or ANC, respectively) .
- a BS may include a central unit (CU) (e.g., ANC 202) and/or one or more distributed units (e.g., one or more TRPs 208) .
- CU central unit
- distributed units e.g., one or more TRPs 208 .
- FIG. 3 illustrates an example physical architecture of a distributed RAN 300, according to aspects of the present disclosure.
- a centralized core network unit (C-CU) 302 may host core network functions.
- the C-CU may be centrally deployed.
- C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS) ) , in an effort to handle peak capacity.
- AWS advanced wireless services
- a centralized RAN unit (C-RU) 304 may host one or more ANC functions.
- the C-RU may host core network functions locally.
- the C-RU may have distributed deployment.
- the C-RU may be closer to the network edge.
- a DU 306 may host one or more TRPs (edge node (EN) , an edge unit (EU) , a radio head (RH) , a smart radio head (SRH) , or the like) .
- the DU may be located at edges of the network with radio frequency (RF) functionality.
- RF radio frequency
- FIG. 4 illustrates example components of the BS 110 and UE 120 illustrated in FIG. 1, which may be used to implement aspects of the present disclosure.
- the BS may include a TRP.
- One or more components of the BS 110 and UE 120 may be used to practice aspects of the present disclosure.
- antennas 452, processors 466, 458, 464, and/or controller/processor 480 of the UE 120 and/or antennas 434, processors 430, 420, 438, and/or controller/processor 440 of the BS 110 may be used to perform the operations described herein and illustrated with reference to FIGs. 9 and 10.
- FIG. 4 shows a block diagram of a design of a BS 110 and a UE 120, which may be one of the BSs and one of the UEs in FIG. 1.
- the base station 110 may be the macro BS 110c in FIG. 1, and the UE 120 may be the UE 120y.
- the base station 110 may also be a base station of some other type.
- the base station 110 may be equipped with antennas 434a through 434t, and the UE 120 may be equipped with antennas 452a through 452r.
- 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 the Physical Broadcast Channel (PBCH) , Physical Control Format Indicator Channel (PCFICH) , Physical Hybrid ARQ Indicator Channel (PHICH) , Physical Downlink Control Channel (PDCCH) , etc.
- the data may be for the Physical Downlink Shared Channel (PDSCH) , etc.
- the processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively.
- the processor 420 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal.
- a transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 432a through 432t.
- the TX MIMO processor 430 may perform certain aspects described herein for RS multiplexing.
- Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc. ) to obtain an output sample stream.
- Each modulator 432 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
- Downlink signals from modulators 432a through 432t may be transmitted via the antennas 434a through 434t, respectively.
- the antennas 452a through 452r may receive the downlink signals from the base station 110 and may provide received signals to the demodulators (DEMODs) 454a through 454r, respectively.
- Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
- Each demodulator 454 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 the demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. For example, MIMO detector 456 may provide detected RS transmitted using techniques described herein.
- a receive processor 458 may process (e.g., demodulate, deinterleave, and 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.
- CoMP aspects can include providing the antennas, as well as some Tx/Rx functionalities, such that they reside in distributed units. For example, some Tx/Rx processings can be done in the central unit, while other processing can be done at the distributed units. For example, in accordance with one or more aspects as shown in the diagram, the BS mod/demod 432 may be in the distributed units.
- a transmit processor 464 may receive and process data (e.g., for the Physical Uplink Shared Channel (PUSCH) ) from a data source 462 and control information (e.g., for the Physical Uplink Control Channel (PUCCH) from the controller/processor 480.
- the transmit processor 464 may also generate reference symbols for a reference signal.
- the symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators 454a through 454r (e.g., for SC-FDM, etc. ) , and transmitted to the base station 110.
- the uplink signals from the UE 120 may be received by the antennas 434, processed by the modulators 432, detected by a MIMO detector 436 if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by the UE 120.
- the receive processor 438 may provide the decoded data to a data sink 439 and the decoded control information to the controller/processor 440.
- the controllers/processors 440 and 480 may direct the operation at the base station 110 and the UE 120, respectively.
- the processor 440 and/or other processors and modules at the base station 110 may perform or direct the processes for the techniques described herein.
- the processor 480 and/or other processors and modules at the UE 120 may also perform or direct processes for the techniques described herein.
- the memories 442 and 482 may store data and program codes for the BS 110 and the UE 120, respectively.
- a scheduler 444 may schedule UEs for data transmission on the downlink and/or uplink.
- FIG. 5 illustrates a diagram 500 showing examples for implementing a communications protocol stack, according to aspects of the present disclosure.
- the illustrated communications protocol stacks may be implemented by devices operating in a in a 5G system (e.g., a system that supports uplink-based mobility) .
- Diagram 500 illustrates a communications 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.
- RRC Radio Resource Control
- PDCP Packet Data Convergence Protocol
- RLC Radio Link Control
- MAC Medium Access Control
- PHY Physical
- the layers of a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE.
- a network access device e.g., ANs, CUs, and/or DUs
- a second option 505-b shows a unified implementation of a protocol stack, in which the protocol stack is implemented in a single network access device (e.g., access node (AN) , new radio base station (NR BS) , a new radio Node-B (NR NB) , a network node (NN) , or the like. ) .
- the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 may each be implemented by the AN.
- the second option 505-b may be useful in a femto cell deployment.
- a UE may implement an entire protocol stack (e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530) .
- an entire protocol stack e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530.
- FIG. 6 is a diagram 600 showing an example of a DL-centric subframe in accordance with certain aspects of the present disclosure.
- the DL-centric subframe may include a control portion 602.
- the control portion 602 may exist in the initial or beginning portion of the DL-centric subframe.
- the control portion 602 may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe.
- the control portion 602 may be a physical DL control channel (PDCCH) , as indicated in FIG. 6.
- the DL-centric subframe may also include a DL data portion 604.
- the DL data portion 604 may sometimes be referred to as the payload of the DL-centric subframe.
- the DL data portion 604 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE) .
- the DL data portion 604 may be a physical DL shared channel (PDSCH) .
- PDSCH physical DL shared channel
- the DL-centric subframe may also include a common UL portion 606.
- the common UL portion 606 may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms.
- the common UL portion 606 may include feedback information corresponding to various other portions of the DL-centric subframe.
- the common UL portion 606 may include feedback information corresponding to the control portion 602.
- Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information.
- the common UL portion 606 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs) , and various other suitable types of information.
- RACH random access channel
- SRs scheduling requests
- FIG. 7 is a diagram 700 showing an example of an UL-centric subframe in accordance with certain aspects of the present disclosure.
- the UL -centric subframe may include a control portion 702.
- the control portion 702 may exist in the initial or beginning portion of the UL-centric subframe.
- the control portion 702 in FIG. 7 may be similar to the control portion described above with reference to FIG. 6.
- the UL-centric subframe may also include an UL data portion 704.
- the UL data portion 704 may sometimes be referred to as the payload of the UL-centric subframe.
- the UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS) .
- the control portion 702 may be a physical DL control channel (PDCCH) .
- PDCCH physical DL control channel
- the end of the control portion 702 may be separated in time from the beginning of the UL data portion 704. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity) .
- the UL-centric subframe may also include a common UL portion 706.
- the common UL portion 706 in FIG. 7 may be similar to the common UL portion 706 described above with reference to FIG. 7.
- the common UL portion 706 may additional or alternative include information pertaining to channel quality indicator (CQI) , sounding reference signals (SRSs) , and various other suitable types of information.
- CQI channel quality indicator
- SRSs sounding reference signals
- One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.
- two or more subordinate entities may communicate with each other using sidelink signals.
- Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications.
- a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS) , even though the scheduling entity may be utilized for scheduling and/or control purposes.
- the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum) .
- a UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a radio resource control (RRC) dedicated state, etc. ) or a configuration associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc. ) .
- RRC radio resource control
- the UE may select a dedicated set of resources for transmitting a pilot signal to a network.
- the UE may select a common set of resources for transmitting a pilot signal to the network.
- a pilot signal transmitted by the UE may be received by one or more network access devices, such as an AN, or a DU, or portions thereof.
- Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE.
- One or more of the receiving network access devices, or a CU to which receiving network access device (s) transmit the measurements of the pilot signals may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs.
- the present disclosure relates generally to communication systems, and more particularly, to methods and apparatus for recovering missing RLC PDUs (e.g., efficiently recovering missing RLC PDUs when grant is insufficient to include all the NACK info) using communications systems operating according to radio technologies such as LTE and/or new radio (NR) technologies, for example.
- radio technologies such as LTE and/or new radio (NR) technologies, for example.
- a number (e.g., a large number) of PDUs in downlink may be missed by a user equipment.
- PDUs that were missed may be declared as missing after a reordering timer expires.
- the user equipment may generate a status uplink PDU and may then send the status uplink PDU to the network to let the network known that so many PDUs are missing and specifically which ones. Accordingly, the network can determine, from the status uplink PDU, which missing PDUs to retransmit.
- the network determines and provides an uplink grant that may limit and/or define a size (e.g., maximum size) of a status PDU that may be sent.
- a size e.g., maximum size
- the grant from the network may be smaller than a size of a status PDU that the user equipment would like to transmit (e.g., to a lower layer of the UE and then from the UE via an uplink channel) .
- the network may initially provide a grant 804 that is smaller than a status PDU 802, which would include or includes an actual NACK list.
- a partial status PDU is sent which is a portion of the status PDU 802 that is within the grant 804.
- a status prohibit timer 806 is started during which nothing is sent and any new grant 808 is ignored.
- another partial status PDU may be transmitted that includes a portion of the remaining status uplink PDU 810 that fits within the grant 812. This process can then be iterated until the entire status PDU is sent in grant sized partial status PDUs.
- a status PDU may be used by the receiving side of an acknowledgement mode (AM) RLC entity to inform the peer AM RLC entity about RLC data PDUs that are received successfully, and RLC data PDUs that are detected to be lost by the receiving side of an AM RLC entity.
- the status PDU tend to be of larger size (in order of hundreds of bytes) when there is a multiple PDU loss detected in RLC downlink.
- the size of a status PDU transmitted may also depend on the uplink grant received. If the grant is less than an actual NACK list, the status PDU will be truncated to fit into the obtained grant. Based on the specification, a status prohibit timer may be started to avoid duplicate PDUs in downlink. During this period, the transmission of a status PDU shall be prohibited even if a UE gets a sufficient grant.
- one or more cases may include one logical channel that is configured with a status prohibit timer.
- a multiple-PDU loss may be detected in RLC downlink amidst a data reception.
- An RLC reordering timer may then expire and deems the SNs within the hole as missing.
- the uplink grant received by the UE may not be enough to fit the complete status PDU.
- the UE may end up sending a partial status PDU and trigger a status prohibit timer.
- the UE shall wait until status prohibit timer expires and it gets a next uplink grant to send status PDU.
- Another partial status PDU and a triggering of a status prohibit timer may again be executed if the uplink grant is insufficient again.
- FIG. 8 illustrates an example of sending one or more a partial status PDUs, in accordance with aspects of the present disclosure.
- one or more cases may involve transmission of buffer status report (BSR) and the partial status PDU with the leftover uplink grant if the uplink grant received is less than configurable percentage of the status PDU and the grant size is less than configurable partial status maximum threshold.
- BSR buffer status report
- FIG. 9 illustrates example operations 900 for wireless communications by a user equipment (UE) , in accordance with aspects of the present disclosure.
- the operations 900 may include, at 902, determining whether one or more grant conditions are met. Further, the operations 900 may include, at 904, transmitting a partial status protocol data unit (PDU) and a buffer status report (BSR) based on the one or more grant conditions being met before starting a status prohibit timer if the one or more grant conditions are met (e.g., a UE may not start the status prohibit timer when BSR +partial status PDU is transmitted) .
- PDU partial status protocol data unit
- BSR buffer status report
- the one or more grant conditions includes an uplink (UL) grant size is less than a factor (e.g., a configurable factor) multiplied by a size associated with a negative acknowledgment (NACK) list or a factor multiplied by a size of a status PDU.
- the one or more grant conditions includes an uplink (UL) grant size is less than a fraction of a size of a status PDU.
- the one or more grant conditions includes an uplink (UL) grant satisfies a maximum partial status PDU threshold.
- the one or more grant conditions includes at least one of a partial NACK suppress threshold time has not been satisfied or an RLC receive window has moved passed a sequence number associated with a previously-sent NACK.
- the BSR is configured to indicate to a base station a grant size associated with remaining status PDU data.
- determining whether one or more grant conditions are met includes determining that one or more grant conditions are met.
- the operations 900 further comprise constructing the BSR and constructing the partial status PDU by selecting a subset of an actual NACK list associated with a status PDU.
- determining whether one or more grant conditions are met includes determining that one or more grant conditions are not met, and in such aspects, the operations 900 further comprise generating a status PDU from an actual NACK list, transmitting the status PDU and starting the status prohibit timer.
- FIG. 10 illustrates example operations 1000 for wireless communications by a base station (BS) , in accordance with aspects of the present disclosure.
- the operations 1000 may include, at 1002 determining a size of an uplink (UL) grant for a user equipment (UE) .
- the operations 1000 may further include, at 1004, receiving a partial status protocol data unit (PDU) and a buffer status report (BSR) having the size of the UL grant from the UE based on one or more grant conditions being met.
- PDU partial status protocol data unit
- BSR buffer status report
- Partial_NACK_suppress_threshold (default) : minimum 10ms, but could be
- RLC round trip time RLC round trip time
- Configurable_factor (default) : 0.5.
- Prev_nack_sn Last NACK_SN in previous partial status PDU.
- Cur_vr_r Current VR_R in RLC downlink.
- partial_status_max_threshold (default) : 200 bytes.
- FIG. 11 illustrates example operations 1100 of sending one or more of a partial status PDU and/or BSR when certain conditions are met, in accordance with aspects of the present disclosure.
- Another partial status PDU may be suppressed for a Partial_NACK_suppress_threshold time 1106 to avoid transmission of status PDUs too frequently.
- a new grant 1108 may be sent but will be ignored and no further partial status will be sent.
- a BSR is constructed and transmitted along with a partial status PDU with the left over grant 1112 from a remaining status PDU 1110, for example, at the first transmission opportunity indicated by lower layer (but if grant conditions are not met, the actions may be different, e.g., based on the flowchart and mentioned below) .
- a partial status PDU may be constructed along with BSR from a remaining status PDU 1116.
- the partial status PDU and BSR may then be transmitted within the grant 1118.
- a status prohibit timer 1120 may still not be triggered.
- FIG. 12 illustrates example operations 1200 for wireless communications, in accordance with aspects of the present disclosure. Particularly, in FIG. 12, a flow chart of operations is shown of an implementation of the above proposed algorithm.
- a UL grant may be received from a base station at a user equipment.
- an available UL grant size is compared to a configurable factor multiplied by a size of a status PDU.
- an available UL grant size may be compared to a partial status max threshold. If the UL grant size is not less than both then, as shown at operation 1206, a status PDU may be built according to UL grant and a status prohibit timer may be started.
- the methods disclosed herein comprise one or more steps or actions for achieving the described method.
- the method steps and/or actions may be interchanged with one another without departing from the scope of the claims.
- the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
- a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members.
- “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
- the term “and/or, ” when used in a list of two or more items means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed.
- the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.
- determining encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up 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.
- the term “some” refers to one or more.
- the term “or” is intended to mean an inclusive “or” rather than an exclusive “or. ” That is, unless specified otherwise, or clear from the context, the phrase, for example, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, for example the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B.
- the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
- the means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor.
- ASIC application specific integrated circuit
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- PLD programmable logic device
- 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.
- an example hardware configuration may comprise a processing system in a wireless node.
- the processing system may be implemented with a bus architecture.
- the bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints.
- the bus may link together various circuits including a processor, machine-readable media, and a bus interface.
- the bus interface may be used to connect a network adapter, among other things, to the processing system via the bus.
- the network adapter may be used to implement the signal processing functions of the PHY layer.
- a user interface e.g., keypad, display, mouse, joystick, etc.
- a user interface e.g., keypad, display, mouse, joystick, etc.
- the bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further.
- the processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.
- the functions may be stored or transmitted over as one or more instructions or code on a computer readable medium.
- Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
- Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
- the processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media.
- a computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
- the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface.
- the machine-readable media, or any portion thereof may be integrated into the processor, such as the case may be with cache and/or general register files.
- machine-readable storage media may include, by way of example, RAM (Random Access Memory) , flash memory, phase change 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 medium, or any combination thereof.
- the machine-readable media may be embodied in a computer-program product.
- a software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media.
- the computer-readable media may comprise a number of software modules.
- the software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions.
- the software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices.
- a software module may be loaded into RAM from a hard drive when a triggering event occurs.
- the processor may load some of the instructions into cache to increase access speed.
- One or more cache lines may then be loaded into a general register file for execution by the processor.
- any connection is properly termed a computer-readable medium.
- the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared (IR) , radio, and microwave
- the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
- Disk and disc include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
- computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media) .
- computer-readable media may comprise transitory computer- readable media (e.g., a signal) . Combinations of the above should also be included within the scope of computer-readable media.
- certain aspects may comprise a computer program product for performing the operations presented herein.
- a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein.
- instructions for performing the operations described herein and illustrated in the appended figures may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein.
- modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable.
- a user terminal and/or base station can be coupled to a server to facilitate the transfer of means for performing the methods described herein.
- various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc. ) , such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device.
- storage means e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.
- CD compact disc
- floppy disk etc.
- any other suitable technique for providing the methods and techniques described herein to a device can be utilized.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Certain aspects of the present disclosure relate to methods and apparatus for wireless communication and more particularly for recovering missing RLC PDUs. In aspects, a method for wireless communications by a user equipment (UE) is provided. The method includes determining whether one or more grant conditions are met, and transmitting a partial status protocol data unit (PDU) and a buffer status report (BSR) based on the one or more grant conditions being met before starting a status prohibit timer if the one or more grant conditions are met. Numerous other aspects are provided.
Description
Field of the Disclosure
The present disclosure relates generally to communication systems, and more particularly, to methods and apparatus for recovering missing RLC PDUs (e.g., efficiently recovering missing radio link control (RLC) protocol data units (PDUs) when grant is insufficient to include all the negative acknowledgement (NACK) information) using communications systems operating according to radio technologies, such as LTE and/or new radio (NR) technologies.
Description of Related Art
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical 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) . Examples of such multiple-access technologies include Long Term Evolution (LTE) 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.
In some examples, a wireless multiple-access communication system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, otherwise known as user equipment (UEs) . In 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 or 5G network) , a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs) , edge nodes (ENs) , radio heads (RHs) , smart radio heads (SRHs) , transmission reception points (TRPs) , etc. ) in communication with a number of central
units (CUs) (e.g., central nodes (CNs) , access node controllers (ANCs) , etc. ) , where a set of one or more distributed units, in communication with a central unit, may define an access node (e.g., a new radio base station (NR BS) , a new radio node-B (NR NB) , a network node, 5G NB, eNB, Next Generation Node B (gNB) , etc. ) . A base station or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a UE to a base station or distributed unit) .
These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example of an emerging telecommunication standard is new radio (NR) , for example, 5G radio access. NR is a set of enhancements to the LTE mobile standard promulgated by Third Generation Partnership Project (3GPP) . It is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) as well as support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
However, as the demand for mobile broadband access continues to increase, there exists a desire for further improvements in NR technology. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
BRIEF SUMMARY
The systems, methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure as expressed by the claims which follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled “Detailed Description” one will understand how the features of this disclosure provide advantages that include improved communications between access points and stations in a wireless network.
Certain aspects provide methods and apparatus for recovering missing RLC PDUs (e.g., efficiently recovering missing RLC PDUs when grant is insufficient to include all the NACK information) using communications systems operating according to radio technologies, such as LTE and/or new radio (NR) technologies.
In accordance with one or more cases, a method for wireless communications by a user equipment (UE) includes determining whether one or more grant conditions are met, and transmitting a partial status protocol data unit (PDU) and a buffer status report (BSR) based on the one or more grant conditions being met before starting a status prohibit timer if the one or more grant conditions are met.
In one or more cases, a method for wireless communications by a base station (BS) includes determining a size of an uplink (UL) grant for a user equipment (UE) , and receiving a partial status protocol data unit (PDU) and a buffer status report (BSR) having the size of the UL grant from the UE based on one or more grant conditions being met.
Aspects generally include methods, apparatus, systems, computer readable mediums, and processing systems, as substantially described herein with reference to and as illustrated by the accompanying drawings. Numerous other aspects are provided.
To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
So that the manner in which the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate
only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.
FIG. 1 is a block diagram conceptually illustrating an example telecommunications system, in which aspects of the present disclosure may be performed.
FIG. 2 is a block diagram illustrating an example logical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure.
FIG. 3 is a diagram illustrating an example physical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure.
FIG. 4 is a block diagram conceptually illustrating a design of an example BS and user equipment (UE) , in accordance with certain aspects of the present disclosure.
FIG. 5 is a diagram showing examples for implementing a communication protocol stack, in accordance with certain aspects of the present disclosure.
FIG. 6 illustrates an example of a DL-centric subframe, in accordance with certain aspects of the present disclosure.
FIG. 7 illustrates an example of an UL-centric subframe, in accordance with certain aspects of the present disclosure.
FIG. 8 illustrates an example of sending one or more a partial status PDUs, in accordance with aspects of the present disclosure.
FIG. 9 illustrates example operations for wireless communications by a user equipment (UE) , in accordance with aspects of the present disclosure.
FIG. 10 illustrates example operations for wireless communications by a base station (BS) , in accordance with aspects of the present disclosure.
FIG. 11 illustrates an example of sending one or more of a partial status PDU and/or BSR when certain conditions are met, in accordance with aspects of the present disclosure.
FIG. 12 illustrates a flow chart that includes example operations for wireless communications, in accordance with aspects of the present disclosure.
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.
Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for radio technologies, such as LTE and/or NR (new radio access technology or 5G technology) .
NR may support various wireless communication services, such as Enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g. 27 GHz or beyond) , massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) . These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements. In addition, these services may co-exist in the same subframe.
The following description provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a
claim. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.
The techniques described herein may be used for various wireless communication networks such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms “network” and “system” are often used interchangeably. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA) , cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) . An OFDMA network may implement a radio technology such as NR (e.g. 5G RA) , Evolved UTRA (E-UTRA) , Ultra Mobile Broadband (UMB) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS) . NR is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF) . 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) . cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) . “LTE” refers generally to LTE, LTE-Advanced (LTE-A) , LTE in an unlicensed spectrum (LTE-whitespace) , etc. The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies.
EXAMPLE WIRELESS COMMUNICATIONS SYSTEM
FIG. 1 illustrates an example wireless network 100, such as a new radio (NR) or 5G network, in which aspects of the present disclosure may be performed.
As illustrated in FIG. 1, the wireless network 100 may include a number of BSs 110 and other network entities. A BS may be a station that communicates with UEs. Each BS 110 may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a Node B and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term “cell” and eNB, Node B, 5G NB, AP, NR BS, NR BS, gNB, or TRP may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station. In some examples, the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, or the like using any suitable transport network.
In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG) , UEs for users in the home, 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 the example shown in FIG. 1, the BSs 110a, 110b and 110c may be macro BSs for the macro cells 102a, 102b and 102c, respectively. The BS 110x may be a pico BS for a pico cell 102x. The BSs 110y and 110z may be femto BS for the femto cells 102y and 102z, respectively. A BS may
support one or multiple (e.g., three) cells.
The wireless network 100 may also include relay stations. A relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS or a UE) and sends a transmission 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. In the example shown in FIG. 1, a relay station 110r may communicate with the BS 110a and a UE 120r in order 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, etc.
The wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100. For example, macro BS may have a high transmit power level (e.g., 20 Watts) whereas pico BS, femto BS, and relays may have a lower transmit power level (e.g., 1 Watt) .
The wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs 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.
A network controller 130 may be coupled 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 one another, e.g., directly or indirectly via wireless or wireline backhaul.
The UEs 120 (e.g., 120x, 120y, etc. ) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE) , a cellular phone, a smart phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL)
station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a healthcare device, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc. ) , an entertainment device (e.g., a music device, a video device, a satellite radio, etc. ) , a vehicular component or sensor, a smart meter/sensor, a robot, a drone, industrial manufacturing equipment, a positioning device (e.g., GPS, Beidou, terrestrial) , or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices, which may include remote devices that may communicate with a base station, another remote device, or some other entity. Machine type communications (MTC) may refer to communication involving at least one remote device on at least one end of the communication and may include forms of data communication which involve one or more entities that do not necessarily need human interaction. MTC UEs may include UEs that are capable of MTC communications with MTC servers and/or other MTC devices through Public Land Mobile Networks (PLMN) , for example. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, cameras, location tags, etc., that may communicate with a BS, another device (e.g., remote device) , or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. MTC UEs, as well as other UEs, may be implemented as Internet-of-Things (IoT) devices, e.g., narrowband IoT (NB-IoT) devices.
In FIG. 1, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. A dashed line with double arrows indicates interfering transmissions between a UE and a BS.
Certain 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 partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general,
modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a ‘resource block’) may be 12 subcarriers (or 180 kHz) . Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz) , respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (e.g., 6 resource blocks) , and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.
While aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communications systems, such as NR. NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using time division duplex (TDD) . A single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration. Each radio frame may consist of 2 half frames, each half frame consisting of 5 subframes, with a length of 10 ms. Consequently, each subframe may have a length of 1 ms. Each subframe may indicate a link direction (e.g., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. UL and DL subframes for NR may be as described in more detail below with respect to FIGs. 6 and 7. Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells. Alternatively, NR may support a different air interface, other than an OFDM-based. NR networks may include entities such CUs and/or DUs.
In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present
disclosure, as discussed further below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity. Base stations are not the only entities that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs) . In this example, the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication. A UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
Thus, in a wireless communication network with a scheduled access to time–frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.
As noted above, a RAN may include a CU and DUs. A NR BS (e.g., eNB, 5G Node B, Node B, transmission reception point (TRP) , access point (AP) ) may correspond to one or multiple BSs. NR cells can be configured as access cell (ACells) or data only cells (DCells) . For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals-in some case cases DCells may transmit SS. NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.
FIG. 2 illustrates an example logical architecture of a distributed radio access network (RAN) 200, which may be implemented in the wireless communication system illustrated in FIG. 1. A 5G access node 206 may include an access node controller (ANC) 202. The ANC 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. The backhaul interface to neighboring next generation access nodes (NG-
ANs) may terminate at the ANC. The ANC may include one or more TRPs 208 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, gNBs, or some other term) . As described above, a TRP may be used interchangeably with “cell. ”
The TRPs 208 may be a DU. The TRPs may be connected to one ANC (ANC 202) or more than one ANC (not illustrated) . For example, for RAN sharing, radio as a service (RaaS) , and service specific AND deployments, the TRP may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
The local architecture 200 may be used to illustrate fronthaul definition. The architecture may be defined that support fronthauling solutions across different deployment types. For example, the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter) .
The architecture may share features and/or components with LTE. According to aspects, the next generation AN (NG-AN) 210 may support dual connectivity with NR. The NG-AN may share a common fronthaul for LTE and NR.
The architecture may enable cooperation between and among TRPs 208. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 202. According to aspects, no inter-TRP interface may be needed/present.
According to aspects, a dynamic configuration of split logical functions may be present within the architecture 200. As will be described in more detail with reference to FIG. 5, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU or CU (e.g., TRP or ANC, respectively) . According to certain aspects, a BS may include a central unit (CU) (e.g., ANC 202) and/or one or more distributed units (e.g., one or more TRPs 208) .
FIG. 3 illustrates an example physical architecture of a distributed RAN 300, according to aspects of the present disclosure. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU may be centrally deployed. C-CU
functionality may be offloaded (e.g., to advanced wireless services (AWS) ) , in an effort to handle peak capacity.
A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Optionally, the C-RU may host core network functions locally. The C-RU may have distributed deployment. The C-RU may be closer to the network edge.
A DU 306 may host one or more TRPs (edge node (EN) , an edge unit (EU) , a radio head (RH) , a smart radio head (SRH) , or the like) . The DU may be located at edges of the network with radio frequency (RF) functionality.
FIG. 4 illustrates example components of the BS 110 and UE 120 illustrated in FIG. 1, which may be used to implement aspects of the present disclosure. As described above, the BS may include a TRP. One or more components of the BS 110 and UE 120 may be used to practice aspects of the present disclosure. For example, antennas 452, processors 466, 458, 464, and/or controller/processor 480 of the UE 120 and/or antennas 434, processors 430, 420, 438, and/or controller/processor 440 of the BS 110 may be used to perform the operations described herein and illustrated with reference to FIGs. 9 and 10.
FIG. 4 shows a block diagram of a design of a BS 110 and a UE 120, which may be one of the BSs and one of the UEs in FIG. 1. For a restricted association scenario, the base station 110 may be the macro BS 110c in FIG. 1, and the UE 120 may be the UE 120y. The base station 110 may also be a base station of some other type. The base station 110 may be equipped with antennas 434a through 434t, and the UE 120 may be equipped with antennas 452a through 452r.
At the base station 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 the Physical Broadcast Channel (PBCH) , Physical Control Format Indicator Channel (PCFICH) , Physical Hybrid ARQ Indicator Channel (PHICH) , Physical Downlink Control Channel (PDCCH) , etc. The data may be for the Physical Downlink Shared Channel (PDSCH) , etc. The processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal. A transmit (TX) multiple-input
multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 432a through 432t. For example, the TX MIMO processor 430 may perform certain aspects described herein for RS multiplexing. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc. ) to obtain an output sample stream. Each modulator 432 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 432a through 432t may be transmitted via the antennas 434a through 434t, respectively.
At the UE 120, the antennas 452a through 452r may receive the downlink signals from the base station 110 and may provide received signals to the demodulators (DEMODs) 454a through 454r, respectively. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 454 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 the demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. For example, MIMO detector 456 may provide detected RS transmitted using techniques described herein. A receive processor 458 may process (e.g., demodulate, deinterleave, and 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. According to one or more cases, CoMP aspects can include providing the antennas, as well as some Tx/Rx functionalities, such that they reside in distributed units. For example, some Tx/Rx processings can be done in the central unit, while other processing can be done at the distributed units. For example, in accordance with one or more aspects as shown in the diagram, the BS mod/demod 432 may be in the distributed units.
On the uplink, at the UE 120, a transmit processor 464 may receive and process data (e.g., for the Physical Uplink Shared Channel (PUSCH) ) from a data source 462 and control information (e.g., for the Physical Uplink Control Channel (PUCCH) from the controller/processor 480. The transmit processor 464 may also generate reference symbols for a reference signal. The symbols from the transmit
processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators 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 antennas 434, processed by the modulators 432, detected by a MIMO detector 436 if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by the UE 120. The receive processor 438 may provide the decoded data to a data sink 439 and the decoded control information to the controller/processor 440.
The controllers/ processors 440 and 480 may direct the operation at the base station 110 and the UE 120, respectively. The processor 440 and/or other processors and modules at the base station 110 may perform or direct the processes for the techniques described herein. The processor 480 and/or other processors and modules at the UE 120 may also perform or direct processes for the techniques described herein. The memories 442 and 482 may store data and program codes for the BS 110 and the UE 120, respectively. A scheduler 444 may schedule UEs for data transmission on the downlink and/or uplink.
FIG. 5 illustrates a diagram 500 showing examples for implementing a communications protocol stack, according to aspects of the present disclosure. The illustrated communications protocol stacks may be implemented by devices operating in a in a 5G system (e.g., a system that supports uplink-based mobility) . Diagram 500 illustrates a communications 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 the layers of a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE.
A first option 505-ashows a split implementation of a protocol stack, in which implementation of the protocol stack is split between a centralized network access device (e.g., an ANC 202 in FIG. 2) and distributed network access device (e.g., DU 208 in FIG. 2) . In the first option 505-a, an RRC layer 510 and a PDCP layer 515
may be implemented by the central unit, and an RLC layer 520, a MAC layer 525, and a PHY layer 530 may be implemented by the DU. In various examples the CU and the DU may be collocated or non-collocated. The first option 505-amay be useful in a macro cell, micro cell, or pico cell deployment.
A second option 505-b shows a unified implementation of a protocol stack, in which the protocol stack is implemented in a single network access device (e.g., access node (AN) , new radio base station (NR BS) , a new radio Node-B (NR NB) , a network node (NN) , or the like. ) . 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 may each be implemented by the AN. The second option 505-b may be useful in a femto cell deployment.
Regardless of whether a network access device implements part or all of a protocol stack, a UE may implement an entire protocol stack (e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530) .
FIG. 6 is a diagram 600 showing an example of a DL-centric subframe in accordance with certain aspects of the present disclosure. The DL-centric subframe may include a control portion 602. The control portion 602 may exist in the initial or beginning portion of the DL-centric subframe. The control portion 602 may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe. In some configurations, the control portion 602 may be a physical DL control channel (PDCCH) , as indicated in FIG. 6. The DL-centric subframe may also include a DL data portion 604. The DL data portion 604 may sometimes be referred to as the payload of the DL-centric subframe. The DL data portion 604 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE) . In some configurations, the DL data portion 604 may be a physical DL shared channel (PDSCH) .
The DL-centric subframe may also include a common UL portion 606. The common UL portion 606 may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion 606 may include feedback information corresponding to various other portions of the DL-centric subframe. For example, the common UL portion 606 may include feedback information
corresponding to the control portion 602. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion 606 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs) , and various other suitable types of information. As illustrated in FIG. 6, the end of the DL data portion 604 may be separated in time from the beginning of the common UL portion 606. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE) ) to UL communication (e.g., transmission by the subordinate entity (e.g., UE) ) . One of ordinary skill in the art will understand that the foregoing is merely one example of a DL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.
FIG. 7 is a diagram 700 showing an example of an UL-centric subframe in accordance with certain aspects of the present disclosure. The UL -centric subframe may include a control portion 702. The control portion 702 may exist in the initial or beginning portion of the UL-centric subframe. The control portion 702 in FIG. 7 may be similar to the control portion described above with reference to FIG. 6. The UL-centric subframe may also include an UL data portion 704. The UL data portion 704 may sometimes be referred to as the payload of the UL-centric subframe. The UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS) . In some configurations, the control portion 702 may be a physical DL control channel (PDCCH) .
As illustrated in FIG. 7, the end of the control portion 702 may be separated in time from the beginning of the UL data portion 704. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity) . The UL-centric subframe may also include a common UL portion 706. The common UL portion 706 in FIG. 7 may be similar to the common UL portion 706 described above with reference to FIG. 7.
The common UL portion 706 may additional or alternative include information pertaining to channel quality indicator (CQI) , sounding reference signals (SRSs) , and various other suitable types of information. One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.
In some circumstances, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS) , even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum) .
A UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a radio resource control (RRC) dedicated state, etc. ) or a configuration associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc. ) . When operating in the RRC dedicated state, the UE may select a dedicated set of resources for transmitting a pilot signal to a network. When operating in the RRC common state, the UE may select a common set of resources for transmitting a pilot signal to the network. In either case, a pilot signal transmitted by the UE may be received by one or more network access devices, such as an AN, or a DU, or portions thereof. Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE. One or more of the receiving network access devices, or a CU to
which receiving network access device (s) transmit the measurements of the pilot signals, may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs.
EXAMPLES OF RECOVERING SOME MISSING RLC PDUS (E. G., WHEN GRANT IS INSUFFICIENT TO INCLUDE ALL THE NACK INFO)
The present disclosure relates generally to communication systems, and more particularly, to methods and apparatus for recovering missing RLC PDUs (e.g., efficiently recovering missing RLC PDUs when grant is insufficient to include all the NACK info) using communications systems operating according to radio technologies such as LTE and/or new radio (NR) technologies, for example.
In one or more cases, a number (e.g., a large number) of PDUs in downlink may be missed by a user equipment. For example, PDUs that were missed may be declared as missing after a reordering timer expires. In response to detecting these missing PDUs, the user equipment may generate a status uplink PDU and may then send the status uplink PDU to the network to let the network known that so many PDUs are missing and specifically which ones. Accordingly, the network can determine, from the status uplink PDU, which missing PDUs to retransmit.
Additionally, before the user equipment sends the status PDU uplink, the network determines and provides an uplink grant that may limit and/or define a size (e.g., maximum size) of a status PDU that may be sent. In cases where many PDUs are missing a larger grant would be used in order to be able to transmit (e.g., to a lower layer of the UE and then from the UE via an uplink channel) an entire status PDU data that identifies all missing PDUs. However, in some cases, the grant from the network may be smaller than a size of a status PDU that the user equipment would like to transmit (e.g., to a lower layer of the UE and then from the UE via an uplink channel) .
In one or more cases, when the network provides a grant (e.g., for a status PDU) that is of a size smaller than an overall status PDU, a partial status PDU may be transmitted (e.g., to a lower layer of the UE and then from the UE) . An example of this is shown in FIG. 8 which illustrates example operations 800 of sending one or more a partial status PDUs (e.g., to a lower layer of the UE, and then possibly from the UE) , in accordance with aspects of the present disclosure.
As shown, the network may initially provide a grant 804 that is smaller than a status PDU 802, which would include or includes an actual NACK list. A partial status PDU is sent which is a portion of the status PDU 802 that is within the grant 804. Once sent, a status prohibit timer 806 is started during which nothing is sent and any new grant 808 is ignored. Once the status prohibit timer 806 expires, another partial status PDU may be transmitted that includes a portion of the remaining status uplink PDU 810 that fits within the grant 812. This process can then be iterated until the entire status PDU is sent in grant sized partial status PDUs.
In one or more cases, a status PDU may be used by the receiving side of an acknowledgement mode (AM) RLC entity to inform the peer AM RLC entity about RLC data PDUs that are received successfully, and RLC data PDUs that are detected to be lost by the receiving side of an AM RLC entity. The status PDU tend to be of larger size (in order of hundreds of bytes) when there is a multiple PDU loss detected in RLC downlink.
As described above, the size of a status PDU transmitted may also depend on the uplink grant received. If the grant is less than an actual NACK list, the status PDU will be truncated to fit into the obtained grant. Based on the specification, a status prohibit timer may be started to avoid duplicate PDUs in downlink. During this period, the transmission of a status PDU shall be prohibited even if a UE gets a sufficient grant.
For example, one or more cases may include one logical channel that is configured with a status prohibit timer. A multiple-PDU loss may be detected in RLC downlink amidst a data reception. An RLC reordering timer may then expire and deems the SNs within the hole as missing. The uplink grant received by the UE may not be enough to fit the complete status PDU. Thus, the UE may end up sending a partial status PDU and trigger a status prohibit timer. The UE shall wait until status prohibit timer expires and it gets a next uplink grant to send status PDU. Another partial status PDU and a triggering of a status prohibit timer may again be executed if the uplink grant is insufficient again. Based on the UE configuration, it might take hundreds of milliseconds to notify the network (NW) of all the missing PDUs in this scenario. For example, additional details may be found in section 5.2.3 of 3GPP TS 36.322, version 11.0.0 Release 11 that relate to this scenario.
In one or more cases, when STATUS reporting has been triggered, the receiving side of an AM RLC entity may, if a status prohibit timer is not running, construct a STATUS PDU and deliver it to lower layer at the first transmission opportunity indicated by lower layer. If a status prohibit timer is running then the entity will wait. Then, at the first transmission opportunity indicated by lower layer after the status prohibit timer expires, the entity may construct a single status PDU even if status reporting was triggered several times while the status prohibit timer was running and deliver it to lower layer.
Further, once a status PDU has been delivered to lower layer, the receiving side of an AM RLC entity may start a status prohibit timer. For example, as discussed above, an example of what may be provided is shown in FIG. 8. Particularly, FIG. 8 illustrates an example of sending one or more a partial status PDUs, in accordance with aspects of the present disclosure.
EXAMPLES OF RECOVERING (E. G., EFFICIENTLY RECOVERING) MISSING RLC PDUS (E. G., WHEN GRANT IS INSUFFICIENT TO INCLUDE ALL THE NACK INFO)
In accordance with one or more aspects, one or more cases may involve transmission of buffer status report (BSR) and the partial status PDU with the leftover uplink grant if the uplink grant received is less than configurable percentage of the status PDU and the grant size is less than configurable partial status maximum threshold.
FIG. 9 illustrates example operations 900 for wireless communications by a user equipment (UE) , in accordance with aspects of the present disclosure. The operations 900 may include, at 902, determining whether one or more grant conditions are met. Further, the operations 900 may include, at 904, transmitting a partial status protocol data unit (PDU) and a buffer status report (BSR) based on the one or more grant conditions being met before starting a status prohibit timer if the one or more grant conditions are met (e.g., a UE may not start the status prohibit timer when BSR +partial status PDU is transmitted) . In aspects, the one or more grant conditions includes an uplink (UL) grant size is less than a factor (e.g., a configurable factor) multiplied by a size associated with a negative acknowledgment (NACK) list or a factor multiplied by a size of a status PDU. In aspects, the one or more grant conditions includes an uplink
(UL) grant size is less than a fraction of a size of a status PDU. In aspects, the one or more grant conditions includes an uplink (UL) grant satisfies a maximum partial status PDU threshold. In aspects, the one or more grant conditions includes at least one of a partial NACK suppress threshold time has not been satisfied or an RLC receive window has moved passed a sequence number associated with a previously-sent NACK. In aspects, the BSR is configured to indicate to a base station a grant size associated with remaining status PDU data. In aspects, determining whether one or more grant conditions are met includes determining that one or more grant conditions are met. In such aspects, the operations 900 further comprise constructing the BSR and constructing the partial status PDU by selecting a subset of an actual NACK list associated with a status PDU. In aspects, determining whether one or more grant conditions are met includes determining that one or more grant conditions are not met, and in such aspects, the operations 900 further comprise generating a status PDU from an actual NACK list, transmitting the status PDU and starting the status prohibit timer. In aspects, determining whether one or more grant conditions are met includes determining that one or more grant conditions are not met, and in such aspects, the operations 900 further comprise generating a BSR and transmitting the BSR. In aspects, the operations 900 further comprise receiving an uplink (UL) grant of a reported size from a base station.
FIG. 10 illustrates example operations 1000 for wireless communications by a base station (BS) , in accordance with aspects of the present disclosure. The operations 1000 may include, at 1002 determining a size of an uplink (UL) grant for a user equipment (UE) . The operations 1000 may further include, at 1004, receiving a partial status protocol data unit (PDU) and a buffer status report (BSR) having the size of the UL grant from the UE based on one or more grant conditions being met.
For example, the following is a proposed algorithm in accordance with one or more cases:
If available UL grant size < configurable_factor *size of status PDU AND available UL grant size < partial_status_max_threshold:
If current_time –last_partial_NACK_sent_time >
Partial_NACK_suppress_threshold OR (prev_nack_sn < cur_vr_r) :
- Construct BSR
- Construct partial Status PDU with leftover grant
- Don’t trigger status prohibit timer
- last_partial_NACK_sent_time = current_time
Else:
- Don’t construct Status PDU
Else:
- Build status PDU (complete/partial)
- Start status prohibit timer
Notes:
Partial_NACK_suppress_threshold (default) : minimum 10ms, but could be
determined by RLC round trip time (RTT) .
Configurable_factor (default) : 0.5.
Prev_nack_sn: Last NACK_SN in previous partial status PDU.
Cur_vr_r: Current VR_R in RLC downlink.
partial_status_max_threshold (default) : 200 bytes.
In accordance with one or more cases, an example of this approach is shown in FIG. 11. Particularly, FIG. 11 illustrates example operations 1100 of sending one or more of a partial status PDU and/or BSR when certain conditions are met, in accordance with aspects of the present disclosure.
As shown a status PDU 1102 may be provided that includes an actual NACK list of all missing PDUs that the UE did not receive from the network. Further, the network base station may provide the UE with a grant 1104 that is smaller than the status PDU 1102. Accordingly, in one or more cases, a BSR may be constructed and transmitted within the grant 1104 along with a partial status PDU that includes some of the status PDU 1102 as shown.
As shown in FIG. 11, once a BSR is constructed and transmitted with a first partial status PDU, another partial status PDU may be suppressed for a Partial_NACK_suppress_threshold time 1106 to avoid transmission of status PDUs too frequently. During, for example, the partial_NACK suppress_threshold time 1106, a new grant 1108 may be sent but will be ignored and no further partial status will be sent. Once the partial_NACK suppress_threshold time 1106 expires, a BSR is constructed and transmitted along with a partial status PDU with the left over grant 1112 from a remaining status PDU 1110, for example, at the first transmission opportunity indicated by lower layer (but if grant conditions are not met, the actions may be different, e.g., based on the flowchart and mentioned below) .
In one or more cases, during the period 1114 when partial status PDU is suppressed, if the RLC DL window slides past the last NACK_SN sent in previous
partial status PDU, a partial status PDU may be constructed along with BSR from a remaining status PDU 1116. The partial status PDU and BSR may then be transmitted within the grant 1118. In one or more cases, once the partial status PDU is transmitted, a status prohibit timer 1120 may still not be triggered.
Further, a UL grant 1124 may be determined to be greater than half the size of a status PDU size 1122. In this case, a partial status PDU may be generated and transmitted within the grant 1124 and the status prohibit timer 1120 may be started.
FIG. 12 illustrates example operations 1200 for wireless communications, in accordance with aspects of the present disclosure. Particularly, in FIG. 12, a flow chart of operations is shown of an implementation of the above proposed algorithm.
Initially, at operation 1202, a UL grant may be received from a base station at a user equipment. At operation 1204, an available UL grant size is compared to a configurable factor multiplied by a size of a status PDU. Also at operations 1204, an available UL grant size may be compared to a partial status max threshold. If the UL grant size is not less than both then, as shown at operation 1206, a status PDU may be built according to UL grant and a status prohibit timer may be started.
If the UL grant size is less than both then, as shown in operation 1208, a current time less a last partial NACK sent time may be compared to a partial NACK suppress threshold. Additionally or alternatively, a previous NACK SN may be compared to a SN associated with a current RLC receive window or a current_vr_r value. Depending on the comparisons, at operation 1210, a partial status PDU may not be sent and rather a BSR may be sent in a leftover grant. Alternatively, depending on the comparisons in operation 1208, at operations 1212, a BSR may be constructed and a partial status PDU may be constructed with the leftover grant, a status prohibit timer may not be started, and a last partial NACK sent time may be set to a current time.
The methods disclosed herein comprise one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another 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 may be modified without departing from the scope of the claims.
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, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) . As used herein, including in the claims, the term “and/or, ” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing components A, B, and/or C, the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.
As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up 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.
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 generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” For example, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from the context to be directed to a singular form. Unless specifically stated otherwise, the term “some” refers to one or more. Moreover, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or. ” That is, unless specified otherwise, or clear from the context, the phrase, for example, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, for example the phrase “X employs A or
B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for. ”
The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components with similar numbering.
The various illustrative logical blocks, modules and circuits described in connection 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. A processor may also be implemented as a combination of computing devices, e.g., 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.
If implemented in hardware, an example hardware configuration may comprise a processing system in a wireless node. The processing system may be implemented with a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the
processing system and the overall design constraints. The bus may link together various circuits including a processor, machine-readable media, and a bus interface. The bus interface may be used to connect a network adapter, among other things, 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 case of a user terminal 120 (see FIG. 1) , a user interface (e.g., keypad, 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, and the like, which are well known in the art, and therefore, will not be described any further. The processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.
If implemented in software, the functions may be stored or transmitted over as one or more instructions or code on a computer readable medium. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media. A computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface. Alternatively, or in addition, the machine-readable media, or any portion thereof, may be integrated into the processor, such as the case may be with cache and/or general register files. Examples of machine-readable storage media may include, by way of example, RAM (Random Access
Memory) , flash memory, phase change 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 medium, or any combination thereof. The machine-readable media may be embodied in a computer-program product.
A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer-readable media may comprise a number of software modules. The software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. The software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of example, a software module may be loaded into RAM from a hard drive when a triggering event occurs. During execution of the software module, the processor may load some of the instructions into cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functionality of a software module below, it will be understood that such functionality is implemented by the processor when executing instructions from that software module.
Also, 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 technologies such as infrared (IR) , radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Thus, in some aspects computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media) . In addition, for other aspects computer-readable media may comprise transitory computer-
readable media (e.g., a signal) . Combinations of the above should also be included within the scope of computer-readable media.
Thus, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein. For example, instructions for performing the operations described herein and illustrated in the appended figures.
Further, it should be appreciated that modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc. ) , such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device can be utilized.
It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes 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 (12)
- A method for wireless communications by a user equipment (UE) comprising:determining whether one or more grant conditions are met; andtransmitting a partial status protocol data unit (PDU) and a buffer status report (BSR) based on the one or more grant conditions being met before starting a status prohibit timer if the one or more grant conditions are met.
- The method of claim 1, wherein the one or more grant conditions includes:an uplink (UL) grant size is less than a factor multiplied by a size associated with a negative acknowledgment (NACK) list or a factor multiplied by a size of a status PDU.
- The method of claim 1, wherein the one or more grant conditions includes:an uplink (UL) grant size is less than a fraction of a size of a status PDU.
- The method of claim 1, wherein the one or more grant conditions includes:an uplink (UL) grant satisfies a maximum partial status PDU threshold.
- The method of claim 1, wherein the one or more grant conditions includes at least one of:a partial NACK suppress threshold time has not been satisfied or an RLC receive window has moved passed a sequence number associated with a previously-sent NACK.
- The method of claim 1, wherein the BSR is configured to indicate to a base station a grant size associated with remaining status PDU data.
- The method of claim 1, wherein determining whether one or more grant conditions are met includes determining that one or more grant conditions are met; andfurther comprising:constructing the BSR; andconstructing the partial status PDU by selecting a subset of an actual NACK list associated with a status PDU.
- The method of claim 1, wherein determining whether one or more grant conditions are met includes determining that one or more grant conditions are not met; andfurther comprising:generating a status PDU from an actual NACK list;transmitting the status PDU andstarting the status prohibit timer.
- The method of claim 1, wherein determining whether one or more grant conditions are met includes determining that one or more grant conditions are not met; andfurther comprising:generating a BSR; andtransmitting the BSR.
- The method of claim 1, further comprising:receiving an uplink (UL) grant of a size from a base station.
- A method for wireless communications by a base station (BS) comprising:determining a size of an uplink (UL) grant for a user equipment (UE) ; andreceiving a partial status protocol data unit (PDU) and a buffer status report (BSR) having the size of the UL grant from the UE based on one or more grant conditions being met.
- A method, device, apparatus, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2017/113497 WO2019104513A1 (en) | 2017-11-29 | 2017-11-29 | Apparatus and methods to recover missing rlc pdus |
PCT/CN2018/089504 WO2019104979A1 (en) | 2017-11-29 | 2018-06-01 | Apparatus and methods to recover missing rlc pdus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2017/113497 WO2019104513A1 (en) | 2017-11-29 | 2017-11-29 | Apparatus and methods to recover missing rlc pdus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019104513A1 true WO2019104513A1 (en) | 2019-06-06 |
Family
ID=66663736
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/113497 WO2019104513A1 (en) | 2017-11-29 | 2017-11-29 | Apparatus and methods to recover missing rlc pdus |
PCT/CN2018/089504 WO2019104979A1 (en) | 2017-11-29 | 2018-06-01 | Apparatus and methods to recover missing rlc pdus |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/089504 WO2019104979A1 (en) | 2017-11-29 | 2018-06-01 | Apparatus and methods to recover missing rlc pdus |
Country Status (1)
Country | Link |
---|---|
WO (2) | WO2019104513A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11937122B2 (en) * | 2020-01-30 | 2024-03-19 | Qualcomm Incorporated | Self-reportable radio link control status protocol data units |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150215945A1 (en) * | 2014-01-28 | 2015-07-30 | Mediatek Inc. | Buffer Status Report and Logical Channel Prioritization for Dual Connectivity |
US20160127939A1 (en) * | 2014-10-31 | 2016-05-05 | Qualcomm Incorporated | Status prohibition timer disabling for partial status report |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101771518B (en) * | 2008-12-29 | 2013-06-12 | 电信科学技术研究院 | Method, device and system for sending status report |
CN103379543B (en) * | 2012-04-23 | 2016-06-15 | 普天信息技术研究院有限公司 | A kind of data transmission method based on TD-LTE |
KR101726705B1 (en) * | 2014-12-01 | 2017-04-26 | 아서스테크 컴퓨터 인코포레이션 | Method and apparatus for handling prohibit timer for scheduling request (SR) in a wireless communication system |
US20160227574A1 (en) * | 2015-02-02 | 2016-08-04 | Qualcomm Incorporated | Opportunistic utilization and mitigation of unused uplink grants in wireless communications |
-
2017
- 2017-11-29 WO PCT/CN2017/113497 patent/WO2019104513A1/en active Application Filing
-
2018
- 2018-06-01 WO PCT/CN2018/089504 patent/WO2019104979A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150215945A1 (en) * | 2014-01-28 | 2015-07-30 | Mediatek Inc. | Buffer Status Report and Logical Channel Prioritization for Dual Connectivity |
US20160127939A1 (en) * | 2014-10-31 | 2016-05-05 | Qualcomm Incorporated | Status prohibition timer disabling for partial status report |
Also Published As
Publication number | Publication date |
---|---|
WO2019104979A1 (en) | 2019-06-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3744040B1 (en) | Quasi co-location assumptions for aperiodic channel state information reference signal triggers | |
EP3619969B1 (en) | Method for broadcast information on supported and non-supported slices | |
KR102429932B1 (en) | Default Radio Link Monitoring Reference Signal (RLM-RS) Determination Procedure in New Radio (NR) | |
EP3577834B1 (en) | Resource allocation for physical uplink control channel (pucch) | |
EP3704908A1 (en) | Timing advance granularity for uplink with different numerologies | |
EP3602908B1 (en) | Radio resource control (rrc) entity selection for rrc messages | |
CA3075514A1 (en) | Aperiodic tracking reference signal | |
WO2018191250A1 (en) | Inter-radio access technology (rat), inter-band, or inter-carrier switching based on power consumption | |
WO2018175908A1 (en) | Mobility enhancement with channel state information reference signals (csi-rs) | |
EP3603205B1 (en) | Reliable delivery of system information | |
WO2019036692A1 (en) | Uplink power control | |
EP3619959B1 (en) | Unified access control | |
WO2018119133A1 (en) | Media access control transport block design | |
WO2019105182A1 (en) | Resource allocation for uplink control information (uci) and data multiplexing on a physical uplink shared channel (pusch) | |
WO2018191646A1 (en) | Scheduling request multiplexing based on reliability and latency objectives | |
EP3639453B1 (en) | Short burst channel design and multiplexing | |
WO2019006265A1 (en) | Physical uplink control channel (pucch) sequence configuration | |
US10750520B2 (en) | Radio link control/packet data convergence protocol window advance with holes | |
WO2018045065A1 (en) | Acknowledgement message prioritization | |
EP3603159B1 (en) | Handling overhead messages in 5g | |
WO2019104513A1 (en) | Apparatus and methods to recover missing rlc pdus | |
WO2018205265A1 (en) | Signaling continuity in a split architecture radio access network | |
EP3583730B1 (en) | Resource index determination for bundled channel transmission in special subframes | |
WO2018188013A1 (en) | Lossless handover with radio resource control (rrc) full reconfiguration | |
WO2020243976A1 (en) | Method and apparatus for method to improve user experience for dual connectivity devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17933686 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 17933686 Country of ref document: EP Kind code of ref document: A1 |