WO2022061698A1 - Reprise sur échec de transfert de données de liaison descendante - Google Patents

Reprise sur échec de transfert de données de liaison descendante Download PDF

Info

Publication number
WO2022061698A1
WO2022061698A1 PCT/CN2020/117673 CN2020117673W WO2022061698A1 WO 2022061698 A1 WO2022061698 A1 WO 2022061698A1 CN 2020117673 W CN2020117673 W CN 2020117673W WO 2022061698 A1 WO2022061698 A1 WO 2022061698A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
data
tcp data
downlink
rrc connection
Prior art date
Application number
PCT/CN2020/117673
Other languages
English (en)
Inventor
Hao Zhang
Wei He
Miao Fu
Pan JIANG
Yan Wang
Jian Li
Yongrui PENG
Jinglin Zhang
Original Assignee
Qualcomm Incorporated
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 Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2020/117673 priority Critical patent/WO2022061698A1/fr
Publication of WO2022061698A1 publication Critical patent/WO2022061698A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/06—Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless

Definitions

  • the present disclosure relates generally to communication systems, and more particularly, to a configuration to recover from downlink data transfer failure.
  • 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. Examples of such multiple-access technologies include 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.
  • 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
  • 5G New Radio is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements.
  • 3GPP Third Generation Partnership Project
  • 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) .
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable low latency communications
  • 5G NR may be based on the 4G Long Term Evolution (LTE) standard.
  • LTE Long Term Evolution
  • the apparatus may be a device at a UE.
  • the device may be a processor and/or a modem at a UE or the UE itself.
  • the apparatus transmits, to a base station, uplink transmission control protocol (TCP) data.
  • TCP uplink transmission control protocol
  • the apparatus receives, from the base station, downlink TCP data.
  • the apparatus determines that the downlink TCP data comprises padding data.
  • the apparatus terminates a radio resource control (RRC) connection with the base station based on sending the uplink TCP data and not receiving valid downlink TCP data.
  • RRC radio resource control
  • the apparatus transmits, to the base station, a registration request for a new RRC connection with the 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 diagram illustrating an example of a wireless communications system and an access network.
  • FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.
  • FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.
  • FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.
  • FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.
  • FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.
  • UE user equipment
  • FIG. 4 is a call flow diagram of signaling between a UE and a base station.
  • FIG. 5 is a flowchart of a method of wireless communication.
  • FIG. 6 is a diagram illustrating an example of a hardware implementation for an example apparatus.
  • processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • processors in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the functions described may be implemented in hardware, software, or any combination thereof, If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media. Storage media may be any available media that canbe accessedby a computer.
  • such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessedby a computer.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • optical disk storage magnetic disk storage
  • magnetic disk storage other magnetic storage devices
  • combinations of the aforementioned types of computer-readable media or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessedby a computer.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100.
  • the wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC) ) .
  • the base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) .
  • the macrocells include base stations.
  • the small cells include femtocells, picocells, and microcells.
  • the base stations 102 configured for 4G LTE may interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface) .
  • the base stations 102 configured for 5G NR may interface with core network 190 through second backhaul links 184.
  • the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages.
  • NAS non-access stratum
  • RAN radio access network
  • MBMS multimedia broadcast multicast service
  • RIM RAN information management
  • the base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with eachother over third backhaul links 134 (e.g., X2 interface) .
  • third backhaul links 134 e.g., X2 interface
  • the first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.
  • the base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102′ may have a coverage area 110′ that overlaps the coverage area 110 of one or more macro base stations 102.
  • a network that includes both small cell and macrocells may be known as a heterogeneous network.
  • a heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) .
  • eNBs Home Evolved Node Bs
  • HeNBs Home Evolved Node Bs
  • CSG closed subscriber group
  • the communication links 120 betweenthe base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referredto as forward link) transmissions from a base station 102 to a UE 104.
  • the communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • the communication links may be through one or more carriers.
  • the base stations 102/UEs 104 mayuse spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.
  • the component carriers may include a primary component carrier and one or more secondary component carriers.
  • a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
  • D2D communication link 158 may use the DL/UL WWAN spectrum.
  • the D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBe
  • the wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like.
  • AP Wi-Fi access point
  • STAs Wi-Fi stations
  • communication links 154 e.g., in a 5 GHz unlicensed frequency spectrum or the like.
  • the STAs 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • the small cell 102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102′ may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as usedby the Wi-Fi AP 150. The small cell 102′, employing NR in anunlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
  • NR radio access network
  • the electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc.
  • two initial operating bands have been identified as frequency range designations FR1 (410 MHz -7.125 GHz) and FR2 (24.25 GHz -52.6 GHz) .
  • the frequencies between FR1 and FR2 are often referredto as mid-band frequencies.
  • FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz -300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • sub-6 GHz or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.
  • a base station 102 may include and/or be referred to as an eNB, gNodeB (gNB) , or another type of base station.
  • Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104.
  • the gNB 180 may be referred to as a millimeter wave base station.
  • the millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range.
  • the base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.
  • the base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′.
  • the UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182".
  • the UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions.
  • the base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions.
  • the base station 180/UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180/UE 104.
  • the transmit and receive directions for the base station 180 may or may not be the same.
  • the transmit and receive directions for the UE 104 may or may not be the same.
  • the EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172.
  • MME Mobility Management Entity
  • MBMS Multimedia Broadcast Multicast Service
  • BM-SC Broadcast Multicast Service Center
  • PDN Packet Data Network
  • the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • the MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160.
  • the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172.
  • IP Internet protocol
  • the PDN Gateway 172 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176.
  • the IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services.
  • the BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
  • the BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions.
  • PLMN public land mobile network
  • the MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.
  • MMSFN Multicast Broadcast Single Frequency Network
  • the core network 190 may include a Access and Mobility Management Function (AMF) 192, otherAMFs 193, a Session Management Function (SMF) 194, and aUser Plane Function (UPF) 195.
  • the AMF 192 may be in communication with a Unified Data Management (UDM) 196.
  • the AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190.
  • the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195.
  • the UPF 195 provides UE IP address allocation as well as other functions.
  • the UPF 195 is connected to the IP Services 197.
  • the IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.
  • IMS IP Multimedia Subsystem
  • PS Packet Switch
  • PSS
  • the base station may include and/or be referredto as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , atransmit reception point (TRP) , or some other suitable terminology.
  • the base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104.
  • Examples of UEs 104 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 smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • the UEs 104 may be referredto as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) .
  • the UE 104 may also be referredto as a station, 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, awireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • the UE 104 may be configured to terminate an RRC connection and request a new RRC connection based on the determination that downlink TCP data is invalid.
  • UE 104 may comprise a determination component 198 configured to determine that the downlink TCP data comprises padding data.
  • the UE 104 may transmit, to base station 180, uplink TCP data.
  • the UE 104 may receive, from the base station, downlink TCP data.
  • the UE 104 may determine that the downlink TCP data comprises padding data.
  • the UE 104 may terminate an RRC connection with the base station based on sending the uplink TCP data and not receiving valid downlink TCP data.
  • the UE 104 may transmit, to the base station, a registration request for a new RRC connection with the base station.
  • FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure.
  • FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe.
  • FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure.
  • FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe.
  • the 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL.
  • FDD frequency division duplexed
  • TDD time division duplexed
  • the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use betweenDL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols.
  • UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) .
  • DCI DL control information
  • RRC radio resource control
  • SFI received slot format indicator
  • a frame (10 ms) may be divided into 10 equally sized subframes (1 ms) .
  • Each subframe may include one or more time slots.
  • Subframes may also include mini-slots, which may include 7, 4, or 2 symbols.
  • Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols.
  • the symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols.
  • the symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission) .
  • the number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies ⁇ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology ⁇ , there are 14 symbols/slot and 2 ⁇ slots/subframe.
  • the subcarrier spacing and symbol length/duration are a fimction of the numerology.
  • the subcarrier spacing may be equal to 2 ⁇ *15 kHz, where ⁇ is the numerology 0 to 4.
  • the symbol length/duration is inversely related to the subcarrier spacing.
  • the slot duration is 0.25 ms
  • the subcarrier spacing is 60 kHz
  • the symbol duration is approximately 16.67 ⁇ s.
  • Each BWP may have a particular numerology.
  • a resource grid may be used to represent the frame structure.
  • Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers.
  • RB resource block
  • PRBs physical RBs
  • the resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
  • the RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE.
  • DM-RS demodulation RS
  • CSI-RS channel state information reference signals
  • the RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .
  • BRS beam measurement RS
  • BRRS beam refinement RS
  • PT-RS phase tracking RS
  • FIG. 2B illustrates an example of various DL channels within a subframe of a frame.
  • the physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six REgroups (REGs) , eachREG including 12 consecutive REs in an OFDMsymbol of an RB.
  • CCEs control channel elements
  • REGs REgroups
  • a PDCCH within one BWP may be referred to as a control resource set (CORESET) .
  • CORESET control resource set
  • a UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth.
  • a primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical hyer identity.
  • a secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame.
  • the SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DM-RS.
  • the physical broadcast channel (PBCH) which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) .
  • the MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) .
  • the physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.
  • SIBs system information blocks
  • some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station.
  • the UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) .
  • the PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH.
  • the PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used.
  • the UE may transmit sounding reference signals (SRS) .
  • the SRS may be transmitted in the last symbol of a subframe.
  • the SRS may have a comb structure, and a UE may transmit SRS on one of the combs.
  • the SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
  • FIG. 2D illustrates an example of various UL channels within a subframe of a frame.
  • the PUCCH may be located as indicated in one configuration.
  • the PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) ACK/NACK feedback.
  • UCI uplink control information
  • the PUSCH carries data, and may additionally be usedto carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.
  • BSR buffer status report
  • PHR power headroom report
  • FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network.
  • IP packets from the EPC 160 may be provided to a controller/processor 375.
  • the controller/processor 375 implements layer 3 and layer 2 functionality.
  • Layer 3 includes a radio resource control (RRC) layer
  • layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • the controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs
  • the transmit (TX) processor 316 andthe receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions.
  • Layer 1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing.
  • the TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) .
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • the coded and modulated symbols may then be split into parallel streams.
  • Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
  • IFFT Inverse Fast Fourier Transform
  • the OFDM stream is spatially precoded to produce multiple spatial streams.
  • Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing.
  • the channel estimate maybe derived from a reference signal and/or channel condition feedback transmitted by the UE 350.
  • Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX.
  • Each transmitter 318 TX may modulate an RF carrier with a respective spatial stream for transmission.
  • each receiver 354 RX receives a signal through its respective antenna 352.
  • Each receiver 354 RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356.
  • the TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions.
  • the RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream.
  • the RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) .
  • FFT Fast Fourier Transform
  • the frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal.
  • the symbols on each subcarrier, and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358.
  • the soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel.
  • the data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
  • the controller/processor 359 can be associated with a memory 360 that stores program codes and data.
  • the memory 360 may be referred to as a computer-readable medium.
  • the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160.
  • the controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
  • RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting
  • PDCP layer functionality associated with header
  • Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.
  • the UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350.
  • Each receiver 318RX receives a signal through its respective antenna 320.
  • Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
  • the controller/processor 375 can be associated with a memory 376 that stores program codes and data.
  • the memory 376 may be referred to as a computer-readable medium.
  • the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160.
  • the controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with 198 of FIG. 1.
  • a connection oriented communications protocol may be used to exchange messages between devices (e.g., UE and base station) .
  • a connection may be established between a UE and a base station, and then data may be exchanged between the UE and base station.
  • the data may include TCP data.
  • the UE may transmit uplink TCP data to the base station, after the connection between the UE and the base station is established.
  • the UE may transmit uplink TCP data to the base station, but the downlink TCP data received from the base station may be invalid, leading to a degraded user experience. In such instances, the downlink TCP data may be corrupted.
  • the data may have incorrect routing information or an incorrect IP address, such that the UE is unable to receive the data transmitted from the base station. In such instances, the UE may not be able to recover the connection by releasing and re-establishing a new RRC connection.
  • the invalid downlink TCP data may be due to an issue with the core network, for example.
  • aspects presented herein provide a configuration to allow a UE to terminate an RRC connection based on the determination that downlink TCP data is invalid. For example, aspects presented herein may allow a UE to terminate the RRC connection and request a new RRC connection with the base station upon the determination that the downlink TCP data comprises padding data. Padding data may refer to invalid data or corrupted data.
  • a UE may be configured to recover the connection with a base station upon the detection of invalid downlink TCP data transmitted from the base station.
  • the UE while in connection mode, may transmit uplink TCP data to the base station.
  • the uplink TCP data may be transmitted to the base station in accordance with a counter value. For example, the UE may transmit N uplink TCP data packets, where N > 0.
  • the UE may receive a corresponding downlink TCP data packet, from the base station, for each of the N uplink TCP data packets sent to the base station.
  • the UE may determine if the downlink TCP data packets are valid data packets or invalid data packets.
  • An invalid data packet may comprise padding data, for example.
  • padding data may be determined to be invalid downlink data based at least on the downlink data not having correct IP address information.
  • the UE may determine that the downlink TCP data received from the base station may comprise padding data if the downlink TCP data comprises at least one invalid downlink data packet.
  • all N downlink TCP data packets may be padding data, such that all N downlink TCP data packets are invalid.
  • the UE may reset the counter value if the UE receives a valid downlink TCP data packet before the N th downlink TCP data packet.
  • the UE may determine if all of the N received downlink TCP data packets comprise invalid data, and if so, then the UE may implement a procedure to re-establish the connection with the base station.
  • the UE when sending N uplink TCP data packets may expect to receive N valid downlink TCP data packets, such that if the UE does not receive N valid downlink TCP data packets, then the UE may assume that the network is experiencing some issues.
  • the UE may transmit, to the base station, an indication to terminate the RRC connection. This may allow the UE to disconnect from the network and enter an idle mode.
  • the UE may then send, to the base station, a registration request for a new RRC connection, thereby allowing the UE to recover from a single way data transfer.
  • the UE may be able initiate a recovery procedure in instances when the UE is receiving invalid downlink data.
  • the UE configured to initiate the recovery procedure may allow the UE to reduce the time to recover from a network issue in an efficient manner, which may lead to enhanced user experiences.
  • FIG. 4 is a call flow diagram 400 of signaling between a UE 402 and a base station 404.
  • the base station 404 may be configured to provide at least one cell.
  • the UE 402 may be configured to communicate with the base station 404.
  • the base station 404 may correspond to base station 102/180 and, accordingly, the cell may include a geographic coverage area 110 in which communication coverage is provided and/or small cell 102’ having a coverage area 110’.
  • a UE 402 may correspond to at least UE 104.
  • the base station 404 may correspond to base station 310 and the UE 402 may correspond to UE 350.
  • Optional aspects are illustrated with a dashed line.
  • the UE 402 may establish a connection with the base station 404.
  • the UE may enter a connected mode once a connection is established with the base station.
  • the UE 402 may transmit uplink TCP data.
  • the UE may transmit uplink TCP data to the base station 404.
  • the base station 404 may receive the uplink TCP data from the UE 402.
  • the uplink TCP data may be associated with a counter value.
  • a number of uplink TCP data packets transmitted to the base station 404 may be based on the counter value.
  • the UE 402 may transmit N uplink TCP data packets to the base station, where N > 0.
  • the number (e.g., N) of uplink TCP data packets transmitted by the UE 402 may be preconfigured or signaled to the UE 402 by the base station 404.
  • the UE 402 may receive downlink TCP data.
  • the UE may receive the downlink TCP data from the base station 404.
  • the base station 404 may transmit the downlink TCP data to the UE 402.
  • the downlink TCP data may comprise downlink TCP data packets.
  • the UE 402 may determine that the downlink TCP data comprises padding data.
  • the padding data may comprise invalid downlink data packets.
  • the downlink TCP data may be determined to comprise padding data if the downlink TCP data comprises at least one invalid downlink data packet.
  • padding data may be determined to be invalid downlink data due to the downlink data not having correct IP address information.
  • the UE 402 may terminate an RRC connection with the base station 404.
  • the UE 402 may terminate the RRC connection with the base station 404 based on sending the uplink TCP data, to the base station 404, and not receiving valid downlink TCP data from the base station 404.
  • the UE 402 may terminate the RRC connection with the base station 404 if a threshold number of downlink TCP data packets comprise padding data.
  • the UE 402 may maintain the RRC connection upon the determination that the downlink TCP data does not comprise padding data.
  • the UE 402 to terminate the RRC connection may transmit an indication to terminate the RRC connection upon the determination that the downlink TCP data comprises padding data.
  • the UE 402 may transmit, to the base station 404, the indication to terminate the RRC connection upon the determination that the downlink TCP data comprises padding data.
  • the UE 402 may enter an idle mode.
  • the UE 402 may enter the idle mode upon transmission of the indication to terminate the RRC connection.
  • the UE 402 may transmit a registration request for a new RRC connection.
  • the UE 402 may transmit, to the base station 404, the registration request for the new RRC connection with the base station 404.
  • FIG. 5 is a flowchart 500 of a method of wireless communication.
  • the method may be performed by a UE or a component of a UE (e.g., the UE 104; the apparatus 602; the cellular baseband processor 604, which may include the memory 360 and which may be the entire UE 350 or a component of the UE 350, such as the TX processor 368, the RX processor 356, and/or the controller/processor 359) .
  • One or more of the illustrated operations may be omitted, transposed, or contemporaneous.
  • Optional aspects are illustrated with a dashed line.
  • the method may allow a UE to terminate an RRC connection based on the determination that downlink TCP data is invalid.
  • the UE may transmit uplink TCP data.
  • 502 may be performed by TCP data component 640 of apparatus 602.
  • the UE may transmit uplink TCP data to the base station.
  • the uplink TCP data may be associated with a counter value.
  • a number of uplink TCP data packets transmitted to the base station may be based on the counter value.
  • the UE may transmit N uplink TCP data packets to the base station, where N > 0.
  • the number (e.g., N) of uplink TCP data packets transmitted by the UE may be preconfigured or signaled to the UE by the base station.
  • the UE may receive downlink TCP data.
  • 504 may be performed by TCP data component 640 of apparatus 602.
  • the UE may receive the downlink TCP data from the base station.
  • the downlink TCP data may comprise downlink TCP data packets.
  • the UE may determine that the downlink TCP data comprises padding data. For example, 506 may be performed by determination component 642 of apparatus 602.
  • the padding data may comprise invalid downlink data packets.
  • the downlink TCP data may be determined to comprise padding data if the downlink TCP data comprises at least one invalid downlink data packet.
  • the UE may terminate an RRC connection with the base station. For example, 508 may be performed by termination component 644 of apparatus 602.
  • the UE may terminate the RRC connection with the base station based on sending the uplink TCP data and not receiving valid downlink TCP data.
  • the UE may terminate the RRC connection with the base station if athreshold number of downlink TCP data packets comprise padding data.
  • the UE may maintain the RRC connection upon the determination that the downlink TCP data does not comprise padding data.
  • the UE may transmit an indication to terminate the RRC connection upon the determination that the downlink TCP data comprises padding data.
  • 510 may be performed by indication component 646 of apparatus 602.
  • the UE may transmit, to the base station, the indication to terminate the RRC connection upon the determination that the downlink TCP data comprises padding data.
  • the UE may enter an idle mode.
  • 512 may be performed by idle mode component 648 of apparatus 602.
  • the UE may enter the idle mode upon transmission of the indication to terminate the RRC connection.
  • the UE may transmit a registration request for a new RRC connection.
  • 514 may be performed by registration component 650 of apparatus 602.
  • the UE may transmit, to the base station, the registration request for the new RRC connection with the base station.
  • FIG. 6 is a diagram 600 illustrating an example of a hardware implementation for an apparatus 602.
  • the apparatus 602 is a UE and includes a cellular baseband processor 604 (also referred to as a modem) coupled to a cellular RF transceiver 622 and one or more subscriber identity modules (SIM) cards 620, an application processor 606 coupled to a secure digital (SD) card 608 and a screen610, a Bluetooth module 612, a wireless local area network (WLAN) module 614, a Global Positioning System (GPS) module 616, and a power supply 618.
  • the cellular baseband processor 604 communicates through the cellular RF transceiver 622 with the UE 104 and/or BS 102/180.
  • the cellular baseband processor 604 may include a computer-readable medium/memory.
  • the computer-readable medium/memory maybe non-transitory.
  • the cellular baseband processor 604 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory.
  • the software when executed by the cellular baseband processor 604, causes the cellular baseband processor 604 to perform the various functions described supra.
  • the computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor 604 when executing software.
  • the cellular baseband processor 604 further includes a reception component 630, a communication manager 632, and a transmission component 634.
  • the communication manager 632 includes the one or more illustrated components.
  • the components within the communication manager 632 may be stored in the computer-readable medium/memory and/or configured as hardware within the cellular baseband processor 604.
  • the cellular baseband processor 604 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.
  • the apparatus 602 may be a modem chip and include just the baseband processor 604, and in another configuration, the apparatus 602 may be the entire UE (e.g., see 350 of FIG. 3) and include the aforediscussed additional modules of the apparatus 602.
  • the communication manager 632 includes a TCP data component 640 that is configured to transmit uplink TCP data, e.g., as described in connection with 502 of FIG. 5.
  • the TCP data component 640 may be configured to receive downlink TCP data, e.g., as described in connection with 504 of FIG. 5.
  • the communication manager 632 further includes a determination component 642 that is configured to determine that the downlink TCP data comprises padding data, e.g., as described in connection with 506 of FIG. 5.
  • the communication manager 632 further includes a termination component 644 that is configured to terminate an RRC connection with the base station, e.g., as described in connection with 508 of FIG. 5.
  • the communication manager 632 further includes an indication component 646 that is configured to transmit an indication to terminate the RRC connection upon the determination that the downlink TCP data comprises padding data, e.g., as described in connection with 510 of FIG. 5.
  • the communication manager 632 further includes an idle mode component 648 that is configured to enter an idle mode, e.g., as described in connection with 512 of FIG. 5.
  • the communication manager 632 further includes a registration component 650 that is configured to transmit a registration request for a new RRC connection, e.g., as described in connection with 514 of FIG. 5.
  • the apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 5. As such, eachblock in the aforementioned flowchart of FIG. 5 may be performed by a component and the apparatus may include one or more of those components.
  • the components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.
  • the apparatus 602 includes means for transmitting, to a base station, uplink TCP data.
  • the apparatus includes means for receiving, from the base station, downlink TCP data.
  • the apparatus includes means for determining that the downlink TCP data comprises padding data.
  • the apparatus includes means for terminating an RRC connection with the base station based on sending the uplink TCP data and not receiving valid downlink TCP data.
  • the apparatus includes means for transmitting, to the base station, a registration request for a new RRC connection with the base station.
  • the apparatus further includes means for transmitting, to the base station, an indication to terminate the RRC connection upon the determination that the downlink TCP data comprises padding data.
  • the apparatus further includes means for entering an idle mode upon transmission of the indication to terminate the RRC connection.
  • the aforementioned means may be one or more of the aforementioned components of the apparatus 602 configured to perform the functions recited by the aforementioned means.
  • the apparatus 602 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359.
  • the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.
  • Example 1 is a method of wireless communication at a UE comprising transmitting, to a base station, uplink TCP data; receiving, from the base station, downlink TCP data; determining that the downlink TCP data comprises padding data; terminating an RRC connection with the base station based on sending the uplink TCP data and not receiving valid downlink TCP data; and transmitting, to the base station, a registration request for a new RRC connection with the base station.
  • Example 2 the method of Example 1 further includes that the uplink TCP data is associated with a counter value.
  • Example 3 the method of Example 1 or 2 further includes that a number of uplink TCP data packets transmitted to the base station is based on the counter value.
  • Example 4 the method of any of Examples 1-3 further includes that the downlink TCP data comprises downlink TCP data packets, wherein the UE terminates the RRC connection with the base station if a threshold number of downlink TCP data packets comprises the padding data.
  • Example 5 the method of any of Examples 1-4 further includes that the padding data comprises invalid downlink data packets.
  • Example 6 the method of any of Examples 1-5 further includes that the downlink TCP data is determined to comprise padding data if the downlink TCP data comprises at least one invalid downlink data packet.
  • Example 7 the method of any of Examples 1-6 further includes that terminating the RRC connection further includes transmitting, to the base station, an indication to terminate the RRC connection upon the determination that the downlink TCP data comprises padding data.
  • Example 8 the method of any of Examples 1-7 further includes entering an idle mode upon transmission of the indication to terminate the RRC connection.
  • Example 9 the method of any of Examples 1-8 further includes that the UE maintains the RRC connection upon the determination that the downlink TCP data does not comprise padding data.
  • Example 10 is a device including one or more processors and one or more memories in electronic communication with the one or more processors storing instructions executable by the one or more processors to cause the system or apparatus to implement a method as in any of Examples 1-9.
  • Example 11 is a system or apparatus including means for implementing a method or realizing an apparatus as in any of Examples 1-9.
  • Example 12 is a non-transitory computer readable medium storing instructions executable by one or more processors to cause the one or more processors to implement a method as in any of Examples 1-9.
  • Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C.
  • combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne une configuration destinée à permettre à un UE de couper une connexion RRC sur la base d'une détermination du fait que des données TCP de liaison descendante sont invalides. L'appareil transmet, à une station de base, des données TCP de liaison montante. L'appareil reçoit, en provenance de la station de base, des données TCP de liaison descendante. L'appareil détermine que les données TCP de liaison descendante comprennent des données de bourrage. L'appareil coupe une connexion RRC avec la station de base sur la base de l'envoi des données TCP de liaison montante et de l'absence de réception de données TCP de liaison descendante valides. L'appareil transmet, à la station de base, une demande d'enregistrement pour une nouvelle connexion RRC avec la station de base.
PCT/CN2020/117673 2020-09-25 2020-09-25 Reprise sur échec de transfert de données de liaison descendante WO2022061698A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/117673 WO2022061698A1 (fr) 2020-09-25 2020-09-25 Reprise sur échec de transfert de données de liaison descendante

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/117673 WO2022061698A1 (fr) 2020-09-25 2020-09-25 Reprise sur échec de transfert de données de liaison descendante

Publications (1)

Publication Number Publication Date
WO2022061698A1 true WO2022061698A1 (fr) 2022-03-31

Family

ID=80857192

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/117673 WO2022061698A1 (fr) 2020-09-25 2020-09-25 Reprise sur échec de transfert de données de liaison descendante

Country Status (1)

Country Link
WO (1) WO2022061698A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130260740A1 (en) * 2012-03-27 2013-10-03 Venkata Ratnakar Rao Rayavarapu Ue preference indicator for suspension
CN108810939A (zh) * 2017-04-28 2018-11-13 中兴通讯股份有限公司 一种提升数据通路可靠性的方法及装置
CN111373789A (zh) * 2017-11-16 2020-07-03 三星电子株式会社 无线通信系统中的通信方法和装置
CN111556506A (zh) * 2020-04-28 2020-08-18 锐迪科微电子科技（上海）有限公司 异常链路的处理方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130260740A1 (en) * 2012-03-27 2013-10-03 Venkata Ratnakar Rao Rayavarapu Ue preference indicator for suspension
CN108810939A (zh) * 2017-04-28 2018-11-13 中兴通讯股份有限公司 一种提升数据通路可靠性的方法及装置
CN111373789A (zh) * 2017-11-16 2020-07-03 三星电子株式会社 无线通信系统中的通信方法和装置
CN111556506A (zh) * 2020-04-28 2020-08-18 锐迪科微电子科技（上海）有限公司 异常链路的处理方法及设备

Similar Documents

Publication Publication Date Title
US11445491B2 (en) Reduced capability/complexity NR bandwidth part configuration
US11405094B2 (en) Default quasi co-location assumption after beam failure recovery for single-downlink control information-based multiple transmit receive point communication
AU2019399488A1 (en) Default beam selection based on a subset of coresets
US11540268B2 (en) Single transport block over multiple slots with discontinuous SLIVs
US11405809B2 (en) Radio link monitoring reference signals for UEs that do not support CSI-RS based radio link monitoring
US11678223B2 (en) Transmission power control command accumulation for NR-dual connectivity
US11588607B2 (en) User equipment-assisted information for full-duplex user equipment
US11791971B2 (en) Component carrier group based bandwidth part switching
WO2022056799A1 (fr) Commutation rapide de tranchage par l'intermédiaire d'une suspension ou d'une activation de scg
US11616558B2 (en) Procedural delays and scheduling restriction based on component carrier groups
US20210242925A1 (en) Uplink beam failure report for a default uplink beam
WO2022077207A1 (fr) Connectivité assistée
US20230300889A1 (en) Data transmission in rach procedures
US11224060B2 (en) Gap transmission in channel occupancy time
WO2022061698A1 (fr) Reprise sur échec de transfert de données de liaison descendante
US11991736B2 (en) Inter-cell interference coordination in mmWave networks
US11870589B2 (en) Method and apparatus with multi-configuration HARQ message
US11627609B2 (en) Multi-segment RAR window for PRACH retransmission
WO2021253267A1 (fr) Procédé de traitement en dehors d'une zone de service de réseau de données local (ladn)
WO2022056662A1 (fr) Procédés et appareil de vr/ar en nr-dc
US20220116892A1 (en) Uplink spatial filter and power control for joint channel estimation across physical uplink control channels
WO2022056666A1 (fr) Procédés et appareil de vidéo sur nr-dc
US20210360659A1 (en) User equipment processing capability indication
WO2022006855A1 (fr) Éviter l'enregistrement en mode autonome pour abonné non autonome
US20240023090A1 (en) Configuring uplink transmission configuration indicator list

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

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

Country of ref document: EP

Kind code of ref document: A1