[go: up one dir, main page]

WO2019104979A1 - Appareil et procédés pour récupérer des pdu rlc manquants - Google Patents

Appareil et procédés pour récupérer des pdu rlc manquants Download PDF

Info

Publication number
WO2019104979A1
WO2019104979A1 PCT/CN2018/089504 CN2018089504W WO2019104979A1 WO 2019104979 A1 WO2019104979 A1 WO 2019104979A1 CN 2018089504 W CN2018089504 W CN 2018089504W WO 2019104979 A1 WO2019104979 A1 WO 2019104979A1
Authority
WO
WIPO (PCT)
Prior art keywords
grant
status
met
pdu
size
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/089504
Other languages
English (en)
Inventor
Vinay Rajkumar PATIL
Gang Xiao
Shailesh Maheshwari
Rudhir Upretee
Xing Chen
Haiqin LIU
Peng Wu
Ling Xie
Saket BATHWAL
Hongjin GUO
Xiaojian LONG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of WO2019104979A1 publication Critical patent/WO2019104979A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
  • 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) .
  • UEs user equipment
  • a set of one or more base stations may define an eNodeB (eNB) .
  • eNB eNodeB
  • 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.
  • DUs distributed units
  • EUs edge units
  • ENs edge nodes
  • RHs radio heads
  • SSRHs smart radio heads
  • TRPs transmission reception points
  • 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. 1A is a block diagram conceptually illustrating an example telecommunications system, in which aspects of the present disclosure may be performed.
  • FIG. 1B is a block diagram illustrating an example of an LTE network architecture, in accordance with certain aspects of the present disclosure.
  • 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 frame format for a new radio (NR) system, in accordance with certain aspects of the present disclosure.
  • NR new radio
  • FIG. 7 illustrates an example of sending one or more a partial status PDUs, in accordance with aspects of the present disclosure.
  • FIG. 8A illustrates example operations for wireless communications by a user equipment (UE) , in accordance with aspects of the present disclosure.
  • UE user equipment
  • FIG. 8B illustrates example components capable of performing the operations shown in FIG. 8A.
  • FIG. 9A illustrates example operations for wireless communications by a base station (BS) , in accordance with aspects of the present disclosure.
  • FIG. 9B illustrates example components capable of performing the operations shown in FIG. 9A.
  • FIG. 10 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. 11 illustrates a flow chart that includes example operations for wireless communications, in accordance with aspects of the present disclosure.
  • FIG. 12 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.
  • FIG. 13 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein 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.
  • 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.
  • 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
  • FIG. 1A 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.
  • NR new radio
  • 5G 5th Generation
  • 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.
  • FIG. 1B is a diagram illustrating an LTE network architecture 1100 in which aspects of the present disclosure may be practiced.
  • a first core network (CN) (e.g., EPC 1110) associated with a first RAT (e.g., 4G or 5G) , for example, receives first data from a first BS (e.g., eNB 1106) associated with the first RAT, the first data received at the first BS from a UE (e.g., UE 1102) .
  • the CN receives second data from a second CN (not shown) associated with a second RAT, the second RAT received at a second BS from the UE and communicated to the second CN by the second BS.
  • the CN then aggregates the first and the second data.
  • the LTE network architecture 1100 may be referred to as an Evolved Packet System (EPS) 1100.
  • the EPS 1100 may include one or more user equipment (UE) 1102, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 1104, an Evolved Packet Core (EPC) 1110, a Home Subscriber Server (HSS) 1120, and an Operator’s IP Services 1122.
  • the EPS can interconnect with other access networks, but for simplicity those entities/interfaces are not shown.
  • Exemplary other access networks may include an IP Multimedia Subsystem (IMS) PDN, Internet PDN, Administrative PDN (e.g., Provisioning PDN) , carrier-specific PDN, operator-specific PDN, and/or GPS PDN.
  • IMS IP Multimedia Subsystem
  • IMS IP Multimedia Subsystem
  • the EPS provides packet-switched services, however, as those skilled in the art will readily appreciate, the various concepts presented throughout this disclosure may be extended to networks providing circuit-s
  • the E-UTRAN includes the evolved Node B (eNB) 1106 and other eNBs 1108.
  • the eNB 1106 provides user and control plane protocol terminations toward the UE 1102.
  • the eNB 1106 may be connected to the other eNBs 1108 via an X2 interface (e.g., backhaul) .
  • the eNB 1106 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set, an access point, or some other suitable terminology.
  • the eNB 1106 may provide an access point to the EPC 1110 for a UE 1102.
  • Examples of UEs 1102 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a netbook, a smart book, an ultrabook, a drone, a robot, a sensor, a monitor, a meter, or any other similar functioning device.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • the UE 1102 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • the eNB 1106 is connected by an S1 interface to the EPC 1110.
  • the EPC 1110 includes a Mobility Management Entity (MME) 1112, other MMEs 1114, a Serving Gateway 1116, and a Packet Data Network (PDN) Gateway 1118.
  • MME Mobility Management Entity
  • PDN Packet Data Network
  • the MME 1112 is the control node that processes the signaling between the UE 1102 and the EPC 1110.
  • the MME 1112 provides bearer and connection management. All user IP packets are transferred through the Serving Gateway 1116, which itself is connected to the PDN Gateway 1118.
  • the PDN Gateway 1118 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 1118 is connected to the Operator’s IP Services 1122.
  • the Operator’s IP Services 1122 may include, for example, the Internet, the Intranet, an IP Multimedia Subsystem (IMS) , and a PS (packet-switched) Streaming Service (PSS) .
  • IMS IP Multimedia Subsystem
  • PS Packet-switched Streaming Service
  • the UE 1102 may be coupled to the PDN through the LTE network.
  • 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 e.g., a base station
  • 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) .
  • 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.
  • P2P peer-to-peer
  • UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
  • 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. 1A.
  • 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
  • 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. 1A, 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. 8A and 9A.
  • 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. 1A.
  • the base station 110 may be the macro BS 110c in FIG. 1A, 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 first option 505-a shows 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) .
  • a centralized network access device e.g., an ANC 202 in FIG. 2
  • distributed network access device e.g., DU 208 in FIG. 2
  • an RRC layer 510 and a PDCP layer 515 may be implemented by the central unit
  • an RLC layer 520, a MAC layer 525, and a PHY layer 530 may be implemented by the DU.
  • the CU and the DU may be collocated or non-collocated.
  • the first option 505-a may 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. ) .
  • 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 showing an example of a frame format 600 for NR.
  • the transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames.
  • Each radio frame may have a predetermined duration (e.g., 10 ms) and may be partitioned into 10 subframes, each of 1 ms, with indices of 0 through 9.
  • Each subframe may include a variable number of slots depending on the subcarrier spacing.
  • Each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols) depending on the subcarrier spacing.
  • the symbol periods in each slot may be assigned indices.
  • a mini-slot is a sub-slot structure (e.g., 2, 3, or 4 symbols) .
  • Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible) for data transmission and the link direction for each subframe may be dynamically switched.
  • the link directions may be based on the slot format.
  • Each slot may include DL/UL data as well as DL/UL control information.
  • a synchronization signal (SS) block is transmitted.
  • the SS block includes a PSS, a SSS, and a two symbol PBCH.
  • the SS block can be transmitted in a fixed slot location, such as the symbols 0-3 as shown in FIG. 6.
  • the PSS and SSS may be used by UEs for cell search and acquisition.
  • the PSS may provide half-frame timing, and the SS may provide the CP length and frame timing.
  • the PSS and SSS may provide the cell identity.
  • the PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc.
  • the SS blocks may be organized into SS bursts to support beam sweeping. Further system information such as, remaining minimum system information (RMSI) , system information blocks (SIBs) , other system information (OSI) can be transmitted on a physical downlink shared channel (PDSCH) in certain subframes.
  • RMSI remaining
  • 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 a 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, for example.
  • radio technologies such as LTE and/or new radio (NR) technologies, for example.
  • a number of PDUs in downlink may be missed by a user equipment.
  • the number of PDUs in downlink that may be missed by a UE may be large.
  • PDUs that are missed by the UE may be declared as missing after a reordering timer expires.
  • the user equipment may generate a status uplink PDU and may send the status uplink PDU to the network to let the network known that 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 by the UE.
  • 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 may like to transmit (e.g., to a lower layer of the UE and then from the UE via an uplink channel) .
  • a partial status PDU may be transmitted instead (e.g., to a lower layer of the UE and then from the UE) .
  • FIG. 7 illustrates example operations 700 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.
  • the network may initially provide a grant 704 that is smaller than a status PDU 702, which includes an actual NACK list.
  • a partial status PDU is sent which is a portion of the status PDU 702 that is within the grant 704.
  • a status prohibit timer 706 is started during which nothing is sent and any new grant 708 is ignored.
  • another partial status PDU may be transmitted that includes a portion of the remaining status uplink PDU 710 that fits within the grant 712. 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 sequence numbers (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 the UE 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.
  • the UE might take hundreds of milliseconds to notify the network (NW) of all the missing PDUs in this scenario.
  • the receiving side of an acknowledgement mode (AM) RLC entity may, if a status prohibit timer is not running, construct a status PDU and deliver the status PDU 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 the single status PDU to lower layer.
  • a status prohibit timer is not running then construct a status PDU and deliver the status PDU 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 the single status PDU to lower layer.
  • FIG. 7 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. 8A illustrates example operations 800A for wireless communications by a user equipment (UE) , in accordance with aspects of the present disclosure.
  • the operations 800A include, at 802A, determining whether one or more grant conditions are met. Further, the operations 800A include, at 804A, 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 that 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 that is less than a fraction of a size of a status PDU.
  • the one or more grant conditions include an uplink (UL) grant that satisfies a maximum partial status PDU threshold.
  • the one or more grant conditions includes at least one of a partial NACK suppress threshold time that has not been satisfied or an RLC receive window that 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 may be done through a number of different determinations. For example, 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 800A 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. In such aspects, the operations 800A 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. In such aspects, the operations 800A further comprise generating a BSR and transmitting the BSR. In aspects, the operations 800A further comprise receiving an uplink (UL) grant of a reported size from a base station.
  • UL uplink
  • an algorithm may be provided that can cover one or more of the above different determinations for determining whether one or more grant conditions are met. Such an algorithm could therefore be used to stall the triggering of the status prohibit timer while allowing for operations to proceed that send a status PDU using a BSR, partial status PDUs, grant size, or other factors.
  • a proposed algorithm in accordance with one or more cases:
  • a default value of the partial_NACK_suppress_threshold will be, at minimum, 10ms.
  • the partial_NACK_suppress_threshold could be determined by an RLC round trip time (RTT) .
  • the configurable_factor may have a default value of 0.5.
  • the Prev_nack_sn may be a last NACK_SN in previous partial status PDU.
  • the Cur_vr_r may be a current VR_R in RLC downlink.
  • the partial_status_max_threshold may have a default value of at or near 200 bytes.
  • FIG. 9A illustrates example operations 900A for wireless communications by a base station (BS) , in accordance with aspects of the present disclosure.
  • the operations 900A include, at 902A determining a size of an uplink (UL) grant for a user equipment (UE) .
  • the operations 900A further include, at 904A, 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
  • FIG. 10 illustrates example operations 1000 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.
  • an RLC status PDU may be transmitted in at least two separate uplink grants.
  • the UE does not start a status prohibit timer after a first transmission of RLC status PDU.
  • a status PDU 1002 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 1004 that is smaller than the status PDU 1002. Accordingly, in one or more cases, a BSR may be constructed and transmitted within the grant 1004 along with a partial status PDU that includes some of the status PDU 1002 as shown.
  • Another partial status PDU may be suppressed for a Partial_NACK_suppress_threshold time 1006 to avoid transmission of status PDUs too frequently.
  • a new grant 1008 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 1012 from a remaining status PDU 1010, 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 1016.
  • the partial status PDU and BSR may then be transmitted within the grant 1018.
  • a status prohibit timer 1020 may still not be triggered.
  • a UL grant 1024 may be determined to be greater than half the size of a status PDU size 1022.
  • a partial status PDU may be generated and transmitted within the grant 1024 and the status prohibit timer 1020 may be started.
  • FIG. 11 illustrates example operations 1145 for wireless communications, in accordance with aspects of the present disclosure. Particularly, in FIG. 11, 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 1160, a status PDU may be built according to UL grant and a status prohibit timer may be started.
  • 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.
  • a partial status PDU may not be sent and rather a BSR may be sent in a leftover grant.
  • 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.
  • FIG. 12 illustrates a communications device 1200 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in FIG. 8A.
  • the communications device 1200 includes a processing system 1214 coupled to a transceiver 1212.
  • the transceiver 1212 is configured to transmit and receive signals for the communications device 1200 via an antenna 1220, such as the various signal described herein.
  • the processing system 1214 may be configured to perform processing functions for the communications device 1200, including processing signals received and/or to be transmitted by the communications device 1200.
  • the processing system 1214 includes a processor 1208 coupled to a computer-readable medium/memory 1210 via a bus 1224.
  • the computer-readable medium/memory 1210 is configured to store instructions that when executed by processor 1208, cause the processor 1208 to perform the operations illustrated in FIG. 8A, or other operations for performing the various techniques discussed herein.
  • the processing system 1214 further includes a determining component 1202 for performing the operations illustrated at 802A in FIG. 8A. Additionally, the processing system 1214 includes a transmitting component 1204 for performing the operations illustrated at 804A in FIG. 8A.
  • the determining component 1202 and transmitting component 1204 may be coupled to the processor 1208 via bus 1224. In certain aspects, the determining component 1202 and transmitting component 1204 may be hardware circuits. In certain aspects, the determining component 1202 and transmitting component 1204 may be software components that are executed and run on processor 1208.
  • FIG. 13 illustrates a communications device 1300 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in FIG. 9A.
  • the communications device 1300 includes a processing system 1314 coupled to a transceiver 1312.
  • the transceiver 1312 is configured to transmit and receive signals for the communications device 1300 via an antenna 1320, such as the various signal described herein.
  • the processing system 1314 may be configured to perform processing functions for the communications device 1300, including processing signals received and/or to be transmitted by the communications device 1300.
  • the processing system 1314 includes a processor 1308 coupled to a computer-readable medium/memory 1310 via a bus 1324.
  • the computer-readable medium/memory 1310 is configured to store instructions that when executed by processor 1308, cause the processor 1308 to perform the operations illustrated in FIG. 9A, or other operations for performing the various techniques discussed herein.
  • the processing system 1314 further includes a determining component 1302 for performing the operations illustrated at 902A in FIG. 9A. Additionally, the processing system 1314 includes a receiving component 1304 for performing the operations illustrated at 904A in FIG. 9A.
  • the determining component 1302 and receiving component 1304 may be coupled to the processor 1308 via bus 1324. In certain aspects, the determining component 1302 and receiving component 1304 may be hardware circuits. In certain aspects, the determining component 1302 and receiving component 1304 may be software components that are executed and run on processor 1308.
  • 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
  • operations 800A illustrated in FIG. 8A, and operations 900A illustrated in FIG. 9A correspond to means 800B illustrated in FIG. 8B, means 900B illustrated in FIG. 9B, respectively.
  • means for transmitting and/or means for receiving may comprise one or more of a transmit processor 420, a TX MIMO processor 430, a receive processor 438, or antenna (s) 434 of the base station 110 and/or the transmit processor 464, a TX MIMO processor 466, a receive processor 458, or antenna (s) 452 of the user equipment 120.
  • means for determining, means for constructing, means for starting, and/or means for generating may comprise one or more processors, such as the controller/processor 440 of the base station 110 and/or the controller/processor 480 of the user equipment 120.
  • 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.
  • 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.
  • 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 FIGs. 8A and 9A 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

Selon certains aspects, la présente invention concerne des procédés et un appareil de communication sans fil, destinés en particulier à récupérer des PDU RLC manquants. Selon des aspects, l'invention concerne un procédé de communication sans fil exécuté par un équipement d'utilisateur (UE). Le procédé consiste à déterminer si une ou plusieurs conditions d'octroi sont satisfaites, et à transmettre une unité de données de protocole (PDU) d'état partiel et un rapport d'état de tampon (BSR) sur la base de la satisfaction desdites conditions d'octroi avant de démarrer un temporisateur d'état d'interdiction si lesdites conditions d'octroi sont satisfaites. L'invention concerne également de nombreux autres aspects.
PCT/CN2018/089504 2017-11-29 2018-06-01 Appareil et procédés pour récupérer des pdu rlc manquants Ceased WO2019104979A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PCT/CN2017/113497 WO2019104513A1 (fr) 2017-11-29 2017-11-29 Appareil et procédés pour récupérer des pdu rlc manquantes
CNPCT/CN2017/113497 2017-11-29

Publications (1)

Publication Number Publication Date
WO2019104979A1 true WO2019104979A1 (fr) 2019-06-06

Family

ID=66663736

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2017/113497 Ceased WO2019104513A1 (fr) 2017-11-29 2017-11-29 Appareil et procédés pour récupérer des pdu rlc manquantes
PCT/CN2018/089504 Ceased WO2019104979A1 (fr) 2017-11-29 2018-06-01 Appareil et procédés pour récupérer des pdu rlc manquants

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/113497 Ceased WO2019104513A1 (fr) 2017-11-29 2017-11-29 Appareil et procédés pour récupérer des pdu rlc manquantes

Country Status (1)

Country Link
WO (2) WO2019104513A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021155055A1 (fr) * 2020-01-30 2021-08-05 Qualcomm Incorporated Unités de données de protocole d'état de commande de liaison radio auto-rapportable

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101771518A (zh) * 2008-12-29 2010-07-07 大唐移动通信设备有限公司 一种发送状态报告的方法、装置及系统
CN103379543A (zh) * 2012-04-23 2013-10-30 普天信息技术研究院有限公司 一种基于td-lte的数据传输方法
CN105359619A (zh) * 2014-01-28 2016-02-24 联发科技股份有限公司 双连接的缓存状态报告和逻辑信道排程
US20160157256A1 (en) * 2014-12-01 2016-06-02 Asustek Computer Inc. Method and apparatus for handling prohibit timer for scheduling request (sr) in a wireless communication system
WO2016126346A1 (fr) * 2015-02-02 2016-08-11 Qualcomm Incorporated Utilisation et limitation opportunistes de ressources de liaison montante autorisées non utilisées dans des communications sans fil
CN107148762A (zh) * 2014-10-31 2017-09-08 高通股份有限公司 针对部分状态报告来禁用状态禁止定时器

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101771518A (zh) * 2008-12-29 2010-07-07 大唐移动通信设备有限公司 一种发送状态报告的方法、装置及系统
CN103379543A (zh) * 2012-04-23 2013-10-30 普天信息技术研究院有限公司 一种基于td-lte的数据传输方法
CN105359619A (zh) * 2014-01-28 2016-02-24 联发科技股份有限公司 双连接的缓存状态报告和逻辑信道排程
CN107148762A (zh) * 2014-10-31 2017-09-08 高通股份有限公司 针对部分状态报告来禁用状态禁止定时器
US20160157256A1 (en) * 2014-12-01 2016-06-02 Asustek Computer Inc. Method and apparatus for handling prohibit timer for scheduling request (sr) in a wireless communication system
WO2016126346A1 (fr) * 2015-02-02 2016-08-11 Qualcomm Incorporated Utilisation et limitation opportunistes de ressources de liaison montante autorisées non utilisées dans des communications sans fil

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021155055A1 (fr) * 2020-01-30 2021-08-05 Qualcomm Incorporated Unités de données de protocole d'état de commande de liaison radio auto-rapportable
US11937122B2 (en) 2020-01-30 2024-03-19 Qualcomm Incorporated Self-reportable radio link control status protocol data units

Also Published As

Publication number Publication date
WO2019104513A1 (fr) 2019-06-06

Similar Documents

Publication Publication Date Title
KR102763494B1 (ko) 비주기적 채널 상태 정보 레퍼런스 신호 트리거들에 대한 유사 코로케이션 가정들
EP3619969B1 (fr) Procédé de diffusion d'informations sur des tranches supportées et non supportées
KR102429932B1 (ko) 새로운 라디오(nr)에서의 디폴트 라디오 링크 모니터링 레퍼런스 신호(rlm-rs) 결정 프로시저
EP3625906B1 (fr) Surveillance de liaison radioélectrique avec sous-bandes
EP3818653B1 (fr) Procédé et appareil d'élargissement de signalisation de quasi-colocalisation (qcl) pour couvrir des scénarios variés
EP4344291A2 (fr) Configuration de signal de référence et transmission d'une cellule de desserte à une cellule voisine pour la mobilité
EP3580958A1 (fr) Lancement d'un signal de référence de mobilité sur la base de la qualité de signaux d'accès initiaux
WO2018175908A1 (fr) Amélioration de la mobilité avec des signaux de référence d'informations d'état de canal (csi-rs)
EP3603205B1 (fr) Fourniture fiable d'informations système
WO2018191250A1 (fr) Commutation entre technologies d'accès radio (rat), interbande ou inter-porteuse basée sur la consommation d'énergie
EP3610682A1 (fr) Configuration de synchronisation de nouvelle radio dans différents modes de fonctionnement
WO2019006265A1 (fr) Configuration d'une séquence d'un canal physique de commande de liaison montante (pucch)
EP3610693A1 (fr) Multiplexage de demande de planification basé sur des objectifs de fiabilité et de latence
WO2019018232A1 (fr) Combinaison d'informations à travers des faisceaux
EP3646631A1 (fr) Récupération dynamique de ressources réservées pour une compatibilité ascendante
US10750520B2 (en) Radio link control/packet data convergence protocol window advance with holes
CN113056885A (zh) 具有针对相同csi参考信号(csi-rs)资源的不同准共处一地(qcl)配置的信道状态信息(csi)测量
EP3635903A1 (fr) Saut de fréquence dans une mise en correspondance de premieres fréquences pour une couverture améliorée
WO2019104979A1 (fr) Appareil et procédés pour récupérer des pdu rlc manquants
WO2020243976A1 (fr) Procédé et appareil pour un procédé destinés à améliorer l'expérience d'utilisateur pour des dispositifs à double connectivité
WO2021223043A1 (fr) Détection et récupération de décrochage de données dans une connectivité double
WO2018188013A1 (fr) Transfert sans perte à reconfiguration complète de commande de ressources radio (rrc)
EP3583730A1 (fr) Détermination d'indice de ressource pour une transmission de canal groupé dans des sous-trames spéciales

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: 18884432

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: 18884432

Country of ref document: EP

Kind code of ref document: A1