WO2021232210A1 - Récupération d'un décrochage de données dans des systèmes nouvelle radio non-autonomes - Google Patents

Récupération d'un décrochage de données dans des systèmes nouvelle radio non-autonomes Download PDF

Info

Publication number
WO2021232210A1
WO2021232210A1 PCT/CN2020/090922 CN2020090922W WO2021232210A1 WO 2021232210 A1 WO2021232210 A1 WO 2021232210A1 CN 2020090922 W CN2020090922 W CN 2020090922W WO 2021232210 A1 WO2021232210 A1 WO 2021232210A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
network
packet
configuration
new radio
Prior art date
Application number
PCT/CN2020/090922
Other languages
English (en)
Inventor
Jian Li
Fojian ZHANG
Hao Zhang
Chaofeng HUI
Yi Liu
Yuankun ZHU
Pan JIANG
Xiuqiu XIA
Weiying HE
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/090922 priority Critical patent/WO2021232210A1/fr
Publication of WO2021232210A1 publication Critical patent/WO2021232210A1/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/06—De-registration or detaching
    • 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

Definitions

  • aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for using a packet data convergence protocol (PDCP) sequence number (SN) jump threshold to recover from a data stall issue that can occur in non-standalone (NSA) new radio (NR) communications systems.
  • PDCP packet data convergence protocol
  • SN sequence number
  • NR new radio
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc. ) .
  • available system resources e.g., bandwidth, transmit power, etc.
  • multiple-access systems examples include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems, to name a few.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • LTE-A LTE Advanced
  • 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
  • New radio e.g., 5G NR
  • 5G NR is an example of an emerging telecommunication standard.
  • NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP.
  • NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) .
  • CP cyclic prefix
  • NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • MIMO multiple-input multiple-output
  • the method generally includes obtaining a packet data convergence protocol (PDCP) sequence number (SN) jump threshold; detecting that a first SN of a received first PDCP packet differs from a second SN of a previously received second PDCP packet by more than the PDCP SN jump threshold; transmitting a detach request to a network, in response to the detection; and transmitting an attach request to the network, subsequent to the detach request and in response to the detection.
  • PDCP packet data convergence protocol
  • SN sequence number
  • the method generally includes transmitting a configuration to a user equipment (UE) ; transmitting, to the UE, a first PDCP packet having a first SN that differs from a second SN of a previously transmitted second PDCP packet by more than a packet data convergence protocol (PDCP) sequence number (SN) jump threshold of the UE; receiving, from the UE, a detach request, in response to the first PDCP packet; and receiving, from the UE, an attach request to the network, subsequent to the detach request.
  • PDCP packet data convergence protocol
  • aspects of the present disclosure provide means for, apparatus, processors, and computer-readable mediums for performing the methods described herein.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the appended 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.
  • FIG. 1 is a block diagram conceptually illustrating an example wireless communication network, in accordance with certain aspects of the present disclosure.
  • FIG. 2 is a block diagram conceptually illustrating a design of an example a base station (BS) and user equipment (UE) , in accordance with certain aspects of the present disclosure.
  • BS base station
  • UE user equipment
  • FIG. 3 is an example frame format for certain wireless communication systems (e.g., new radio (NR) ) , in accordance with certain aspects of the present disclosure.
  • NR new radio
  • FIG. 4 illustrates an example system architecture for interworking between a 5G System (5GS) and an evolved universal mobile telecommunication system network (E-UTRAN) system, in accordance with certain aspects of the present disclosure.
  • 5GS 5G System
  • E-UTRAN evolved universal mobile telecommunication system network
  • FIG. 5 is a call flow illustrating example operations for indicating disabled dual connectivity with new radio (DCNR) support, in accordance with certain aspects of the present disclosure.
  • FIG. 6 is a diagram showing examples for implementing a communication protocol stack, in accordance with certain aspects of the present disclosure.
  • FIG. 7 is a flow diagram illustrating example operations for wireless communication by a UE, in accordance with certain aspects of the present disclosure.
  • FIG. 8 is a flow diagram illustrating example operations for wireless communication by a BS, in accordance with certain aspects of the present disclosure.
  • FIG. 9 is a call flow diagram illustrating example signaling for using a PDCP SN jump threshold to recover from a data stall issue, in accordance with aspects of the present disclosure.
  • FIG. 10 illustrates a communications device that may include various components configured to perform the operations illustrated in FIG. 7, in accordance with aspects of the present disclosure.
  • FIG. 11 illustrates a communications device that may include various components configured to perform the operations illustrated in FIG. 8, in accordance with aspects of the present disclosure.
  • a user equipment (UE) that has camped on an LTE or LTE-A anchor cell may be configured to with an NR type packet data convergence protocol (PDCP) layer to exchange data with the network.
  • PDCP packet data convergence protocol
  • the sequence number (SN) of the first PDCP packet has a very large difference from previous PDCP packets (e.g., PDCP packets the network sent via the LTE or LTE-Asystem) .
  • the PDCP packets have the large difference in PDCP SN, then the PDCP packets are dropped by the UE and a data stall occurs.
  • a UE may be configured with a PDCP sequence number jump threshold by the network. If the UE then detects that a received PDCP packet has a sequence number that differs from the sequence number of the most recently received PDCP packet, then the UE triggers a detach from the network, followed by an attach to the network. By so doing, the UE can cause the network to reset sequence numbers of the PDCP layer, allowing ongoing data transmissions from the network to be via the NR communications systems, instead of the UE declaring a radio link failure (RLF) and/or falling back to using only the LTE or LTE-Asystem for data communications.
  • RLF radio link failure
  • Data throughput speeds are typically higher via an NR communications system than via an LTE or LTE-Acommunications system.
  • 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.
  • 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 subcarrier, a frequency channel, a tone, a subband, etc.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • the techniques described herein may be used for various wireless networks and radio technologies. While aspects may be described herein using terminology commonly associated with 3G, 4G, and/or new radio (e.g., 5G NR) wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems.
  • 3G, 4G, and/or new radio e.g., 5G NR
  • NR access may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g., e.g., 24 GHz to 53 GHz or beyond) , massive machine type communications 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 machine type communications 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.
  • NR supports beamforming 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.
  • FIG. 1 illustrates an example wireless communication network 100 in which aspects of the present disclosure may be performed.
  • the wireless communication network 100 may be an NR system (e.g., a 5G NR network) .
  • the wireless communication network 100 may be in communication with a core network 132.
  • the core network 132 may in communication with one or more base station (BSs) 110 and/or user equipment (UE) 120 in the wireless communication network 100 via one or more interfaces.
  • BSs base station
  • UE user equipment
  • the BSs 110 and UEs 120 may be configured for using a packet data convergence protocol (PDCP) sequence number (SN) jump threshold to recover from a data stall issue, in accordance with aspects of the present disclosure.
  • the BS 110a includes a PDCP SN manager 112 that transmits a configuration including a packet data convergence protocol (PDCP) sequence number (SN) jump threshold to a user equipment (UE) ; transmits a first PDCP packet having a first SN that differs from a second SN of a previously transmitted second PDCP packet by more than the PDCP SN jump threshold; receives, from the UE, a detach request, in response to the first PDCP packet; and receives, from the UE, an attach request to the network, subsequent to the detach request., in accordance with aspects of the present disclosure.
  • the UE 120a includes a PDCP SN manager 122 that receives a configuration including a packet data convergence protocol (PDCP) sequence number (SN) jump threshold from a network; detect that a first SN of a received first PDCP packet differs from a second SN of a previously received second PDCP packet by more than the PDCP SN jump threshold; transmit a detach request to the network, in response to the detection; and transmits an attach request to the network, subsequent to the detach request and in response to the detection., in accordance with aspects of the present disclosure.
  • PDCP packet data convergence protocol
  • SN sequence number
  • the wireless communication network 100 may include a number of BSs 110a-z (each also individually referred to herein as BS 110 or collectively as BSs 110) and other network entities.
  • a BS 110 may provide communication coverage for a particular geographic area, sometimes referred to as a “cell” , which may be stationary or may move according to the location of a mobile BS 110.
  • the BSs 110 may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in wireless communication network 100 through various types of backhaul interfaces (e.g., a direct physical connection, a wireless connection, a virtual network, or the like) using any suitable transport network.
  • backhaul interfaces e.g., a direct physical connection, a wireless connection, a virtual network, or the like
  • 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 BSs for the femto cells 102y and 102z, respectively.
  • a BS may support one or multiple cells.
  • the BSs 110 communicate with UEs 120a-y (each also individually referred to herein as UE 120 or collectively as UEs 120) in the wireless communication network 100.
  • the UEs 120 (e.g., 120x, 120y, etc. ) may be dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile.
  • Wireless communication network 100 may also include relay stations (e.g., relay station 110r) , also referred to as relays or the like, that receive a transmission of data and/or other information from an upstream station (e.g., a BS 110a or a UE 120r) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE 120 or a BS 110) , or that relays transmissions between UEs 120, to facilitate communication between devices.
  • relay stations e.g., relay station 110r
  • relays or the like that receive a transmission of data and/or other information from an upstream station (e.g., a BS 110a or a UE 120r) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE 120 or a BS 110) , or that relays transmissions between UEs 120, to facilitate communication between devices.
  • a network controller 130 may be in communication with a set of BSs 110 and provide coordination and control for these BSs 110 (e.g., via a backhaul) .
  • the network controller 130 may be in communication with a core network 132 (e.g., a 5G Core Network (5GC) ) , which provides various network functions such as Access and Mobility Management, Session Management, User Plane Function, Policy Control Function, Authentication Server Function, Unified Data Management, Application Function, Network Exposure Function, Network Repository Function, Network Slice Selection Function, etc.
  • 5GC 5G Core Network
  • FIG. 2 illustrates example components of BS 110a and UE 120a (e.g., the wireless communication network 100 of FIG. 1) , which may be used to implement aspects of the present disclosure.
  • a transmit processor 220 may receive data from a data source 212 and control information from a controller/processor 240.
  • 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) , group common PDCCH (GC PDCCH) , etc.
  • the data may be for the physical downlink shared channel (PDSCH) , etc.
  • a medium access control (MAC) -control element (MAC-CE) is a MAC layer communication structure that may be used for control command exchange between wireless nodes.
  • the MAC-CE may be carried in a shared channel such as a physical downlink shared channel (PDSCH) , a physical uplink shared channel (PUSCH) , or a physical sidelink shared channel (PSSCH) .
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • PSSCH physical sidelink shared channel
  • the processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively.
  • the transmit processor 220 may also generate reference symbols, such as for the primary synchronization signal (PSS) , secondary synchronization signal (SSS) , PBCH demodulation reference signal (DMRS) , and channel state information reference signal (CSI-RS) .
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • DMRS PBCH demodulation reference signal
  • CSI-RS channel state information reference signal
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 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) 232a-232t.
  • MIMO modulation reference signal
  • Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc. ) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 232a-232t may be transmitted via the antennas 234a-234t, respectively.
  • a respective output symbol stream e.g., for OFDM, etc.
  • Each modulator 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 232a-232t may be transmitted via the antennas 234a-234t, respectively.
  • the antennas 252a-252r may receive the downlink signals from the BS 110a and may provide received signals to the demodulators (DEMODs) in transceivers 254a-254r, respectively.
  • Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each demodulator may further process the input samples (e.g., for OFDM, etc. ) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from all the demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120a to a data sink 260, and provide decoded control information to a controller/processor 280.
  • a transmit processor 264 may receive and process data (e.g., for the physical uplink shared channel (PUSCH) ) from a data source 262 and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor 280.
  • the transmit processor 264 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS) ) .
  • the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modulators in transceivers 254a-254r (e.g., for SC-FDM, etc. ) , and transmitted to the BS 110a.
  • the uplink signals from the UE 120a may be received by the antennas 234, processed by the modulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120a.
  • the receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to the controller/processor 240.
  • the memories 242 and 282 may store data and program codes for BS 110a and UE 120a, respectively.
  • a scheduler 244 may schedule UEs for data transmission on the downlink and/or uplink.
  • Antennas 252, processors 266, 258, 264, and/or controller/processor 280 of the UE 120a and/or antennas 234, processors 220, 230, 238, and/or controller/processor 240 of the BS 110a may be used to perform the various techniques and methods described herein. For example, as shown in FIG.
  • the controller/processor 240 of the BS 110a has an PDCP SN manager 241 that transmits a configuration including a packet data convergence protocol (PDCP) sequence number (SN) jump threshold to a user equipment (UE) ; transmits a first PDCP packet having a first SN that differs from a second SN of a previously transmitted second PDCP packet by more than the PDCP SN jump threshold; receives, from the UE, a detach request, in response to the first PDCP packet; and receives, from the UE, an attach request to the network, subsequent to the detach request, according to aspects described herein. As shown in FIG.
  • PDCP packet data convergence protocol
  • SN sequence number
  • the controller/processor 280 of the UE 120a has an PDCP SN manager 281 that receives a configuration including a packet data convergence protocol (PDCP) sequence number (SN) jump threshold from a network; detecting that a first SN of a received first PDCP packet differs from a second SN of a previously received second PDCP packet by more than the PDCP SN jump threshold; transmitting a detach request to the network, in response to the detection; and transmitting an attach request to the network, subsequent to the detach request and in response to the detection., according to aspects described herein. Although shown at the controller/processor, other components of the UE 120a and BS 110a may be used to perform the operations described herein.
  • PDCP packet data convergence protocol
  • SN sequence number
  • NR may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink.
  • OFDM orthogonal frequency division multiplexing
  • CP cyclic prefix
  • NR may support half-duplex operation using time division duplexing (TDD) .
  • OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth into multiple orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Modulation symbols may be 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 may be dependent on the system bandwidth.
  • the minimum resource allocation may be 12 consecutive subcarriers.
  • the system bandwidth may also be partitioned into subbands. For example, a subband may cover multiple RBs.
  • NR may support a base subcarrier spacing (SCS) of 15 KHz and other SCS may be defined with respect to the base SCS (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. ) .
  • SCS base subcarrier spacing
  • FIG. 3 is a diagram showing an example of a frame format 300 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 (e.g., 1, 2, 4, 8, 16, ...slots) depending on the SCS.
  • Each slot may include a variable number of symbol periods (e.g., 7, 12, or 14 symbols) depending on the SCS.
  • the symbol periods in each slot may be assigned indices.
  • a mini-slot which may be referred to as a sub-slot structure, refers to a transmit time interval having a duration less than a slot (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 block is transmitted.
  • SSBs may be transmitted in a burst where each SSB in the burst corresponds to a different beam direction for UE-side beam management (e.g., including beam selection and/or beam refinement) .
  • the SSB includes a PSS, a SSS, and a two symbol PBCH.
  • the SSB can be transmitted in a fixed slot location, such as the symbols 0-3 as shown in FIG. 3.
  • the PSS and SSS may be used by UEs for cell search and acquisition.
  • the PSS may provide half-frame timing, 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 SSBs 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.
  • the SSB can be transmitted up to sixty-four times, for example, with up to sixty-four different beam directions for mmWave.
  • the multiple transmissions of the SSB are referred to as a SS burst set.
  • SSBs in an SS burst set may be transmitted in the same frequency region, while SSBs in different SS bursts sets can be transmitted at different frequency regions.
  • FIG. 4 illustrates an example system architecture 400 for interworking between a 5G system (5GS) and E-UTRAN-EPC (evolved packet core) , in accordance with certain aspects of the present disclosure.
  • the UE 402 may be served by separate RANs 404A and 404B controlled by separate core networks 406A and 406B, where the RAN 404A provides E-UTRA services and RAN 404B provides 5G NR services.
  • the UE may operate under only one RAN/CN or both RANs/CNs at a time.
  • a UE may signal to the LTE network (e.g., the EPC) that it supports dual connectivity to LTE and 5G networks during initial network attachment.
  • the UE may authenticate and register at the network, establish an evolved packet system (EPS) session and bearer (s) for using services, and trigger mobility management functions for supporting the user’s movement.
  • EPS evolved packet system
  • MME Mobility Management Entity
  • a Mobility Management Entity (MME) in the network may establish a signaling connection with the UE and aid in exchanging control messages.
  • EPS Mobility Management (EMM) procedures may include ATTACH, DETATCH, and TAU.
  • the ATTACH procedure allows a UE to connect to the network, for example, for the first time (such as when the UE is turned on) or when a UE becomes detached.
  • a UE can attempt to attach to the network by sending an ATTACH request message 502.
  • RRC radio resource control
  • S1 signaling connection may be established over the S1-MME interface.
  • Non-access stratum (NAS) messages may be sent as RRC messages when passing through the RRC connection.
  • the ATTACH request message 502 may include UE network capability information.
  • the UE network capability information contained in the ATTACH request message 502 may include a tracking area identity (TAI) and the old globally unique temporary identifier (GUTI) of the UE.
  • the eNB of the LTE network sends an ATTACH accept message 504 to the UE. After successful attachment to the network, packets can flow in both directions.
  • a tracking area update (TAU) procedure may be initiated.
  • a UE may obtain a TAI list when it attaches to an LTE network.
  • the TAI list shows the tracking areas where the LTE network believes a UE is located and within which a UE can travel without TAU.
  • a UE may not send a TAU message to the MME so long as it stays within a TA contained in the TAI list.
  • Periodic TAU occurs when a UE in idle state sends a TAU request message to an MME periodically even when the UE stays within a TA in the TAI list. If a UE in idle state has stayed in one location (or moved within the TAs in the TAI list) and has not notified the MME of its current location, the network cannot tell whether the UE is still in idle state, or is not able to communicate. For this reason, the UE, even when the TA is not changed, may send TAU request messages to the MME periodically for the purpose of announcing its continued ability to receive data.
  • a UE operating in NSA mode after the initial attachment, may disable DCNR at 506.
  • the network sends a TAU reject message 510 to the UE.
  • the TAU reject message may include a cause code (e.g., an EMM cause code) specifying the reason for rejecting the TAU request.
  • the UE receives a TAU reject message including integrated service digital network (ISDN) cause code #111 indicating an unspecified protocol error.
  • ISDN integrated service digital network
  • FIG. 6 illustrates a diagram 600 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 600 illustrates a communications protocol stack including a Radio Resource Control (RRC) layer 610, a Packet Data Convergence Protocol (PDCP) layer 615, a Radio Link Control (RLC) layer 620, a Medium Access Control (MAC) layer 625, and a Physical (PHY) layer 630.
  • 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 605-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 access network controller (ANC) ) and a distributed network access device (e.g., a distributed unit (DU 208) ) .
  • a centralized network access device e.g., an access network controller (ANC)
  • a distributed network access device e.g., a distributed unit (DU 208)
  • an RRC layer 610 and a PDCP layer 615 may be implemented by a central unit (CU)
  • an RLC layer 620, a MAC layer 625, and a PHY layer 630 may be implemented by the DU.
  • the CU and the DU may be collocated or non-collocated.
  • the first option 605-a may be useful in a macro cell, micro cell, or pico cell deployment.
  • a second option 605-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 610, the PDCP layer 615, the RLC layer 620, the MAC layer 625, and the PHY layer 630 may each be implemented by the AN.
  • the second option 605-b may be useful in a femto cell deployment.
  • a UE may implement an entire protocol stack 605-c (e.g., the RRC layer 610, the PDCP layer 615, the RLC layer 620, the MAC layer 625, and the PHY layer 630) .
  • an entire protocol stack 605-c e.g., the RRC layer 610, the PDCP layer 615, the RLC layer 620, the MAC layer 625, and the PHY layer 630.
  • a user equipment (UE) that has camped on an LTE or LTE-A anchor cell may be configured to with an NR type packet data convergence protocol (PDCP) layer to exchange data with the network.
  • PDCP packet data convergence protocol
  • the sequence number (SN) of the first PDCP packet has a very large difference from previous PDCP packets (e.g., PDCP packets the network sent via the LTE or LTE-A system) .
  • the PDCP packets have the large difference in PDCP SN, then the PDCP packets are dropped by the UE and a data stall occurs.
  • PDCP packet data convergence protocol
  • SN sequence number
  • NR new radio
  • aspects of the present disclosure provide techniques for using a packet data convergence protocol (PDCP) sequence number (SN) jump threshold to recover from a data stall issue that can occur in non-standalone (NSA) new radio (NR) communications systems.
  • PDCP packet data convergence protocol
  • SN sequence number
  • NR new radio
  • a UE camped on an LTE cell as an anchor cell in a non-standalone communication system may be configured with an NR type PDCP layer.
  • the sequence number of the first PDCP packet sent via the NR PDCP layer can be significantly different from the SN of the most recent PDCP packet sent to the UE via another (e.g., LTE) PDCP layer.
  • the UE can drop all of the PDCP packets received via the NR PDCP layer as out of window (OOW) , and a data stall issue occurs.
  • OW out of window
  • the UE may also declare a radio link failure and fail back to using the LTE cell and not the NR cell.
  • the sequence of events is described below:
  • a UE e.g., UE 120a in FIG. 1
  • a UE camps on an LTE Anchor cell.
  • An NSA network (e.g., the network 100 in FIG. 1) configures an NR type PDCP layer on the UE.
  • Downlink PDCP SN jumps or fluctuates dramatically (e.g., by more than 512) suddenly after the NR type PDCP layer is configured on the UE.
  • All of the above received PDCP packets (i.e., received via the NR PDCP layer, as described in 3. above) are dropped as being OOW, and a data stall issue occurs.
  • a threshold for detecting the above described PDCP SN jump scenario may be defined in a network.
  • the network may configure the threshold on a UE.
  • the threshold for detecting the above described PDCP SN jump scenario may be named, “PDCPSN_Jump_Threshold. ”
  • the UE determines whether “PDCP SN received in current slot” – “PDCP SN received in latest previous slot” > PDCPSN_Jump_Threshold. If the condition is true, then the UE detects occurrence of a PDCP SN jump scenario.
  • the UE may trigger a DETACH and an ATTACH (with DCNR supported) to cause a resynchronization of PDCP SNs between the UE and the network.
  • a DETACH and an ATTACH with DCNR supported
  • the UE can avoid triggering an RLF.
  • a UE may determine a PDCP SN jump threshold based on PDCP packet window size received in a configuration (e.g., a PDCP layer configuration) from a network (i.e., a network entity, such as a BS, LTE cell, or NR cell) .
  • the UE may, for example, determine a PDCP SN jump threshold by adding 255 to a PDCP packet window size.
  • a UE operating as described herein may have a benefit of not falling back to LTE only communications (e.g., as in previously known techniques) , but instead the UE will try to work in NSA mode to provide higher packet-switched (PS) data throughput.
  • PS packet-switched
  • FIG. 7 is a flow diagram illustrating example operations 700 for wireless communication, in accordance with certain aspects of the present disclosure.
  • the operations 700 may be performed, for example, by a UE (e.g., the UE 120a in the wireless communication network 100) .
  • the operations 700 may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor 280 of FIG. 2) .
  • the transmission and reception of signals by the UE in operations 700 may be enabled, for example, by one or more antennas (e.g., antennas 252 of FIG. 2) .
  • the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., controller/processor 280) obtaining and/or outputting signals.
  • the operations 700 may begin, at block 702, by obtaining a packet data convergence protocol (PDCP) sequence number (SN) jump threshold.
  • PDCP packet data convergence protocol
  • SN sequence number
  • operations 700 continue by detecting that a first SN of a received first PDCP packet differs from a second SN of a previously received second PDCP packet by more than the PDCP SN jump threshold.
  • Operations 700 continue at block 706 by transmitting a detach request to a network, in response to the detection.
  • operations 700 continue by transmitting an attach request to the network, subsequent to the detach request and in response to the detection.
  • FIG. 8 is a flow diagram illustrating example operations 800 for wireless communication, in accordance with certain aspects of the present disclosure.
  • the operations 800 may be performed, for example, by a BS (e.g., the BS 110a in the wireless communication network 100) .
  • the operations 800 may be complementary to the operations 700 performed by the UE.
  • the operations 800 may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor 240 of FIG. 2) .
  • the transmission and reception of signals by the BS in operations 800 may be enabled, for example, by one or more antennas (e.g., antennas 234 of FIG. 2) .
  • the transmission and/or reception of signals by the BS may be implemented via a bus interface of one or more processors (e.g., controller/processor 240) obtaining and/or outputting signals.
  • the operations 800 may begin, at block 802, by transmitting a configuration to a user equipment (UE) .
  • UE user equipment
  • operations 800 continue by transmitting, to the UE, a first PDCP packet having a first SN that differs from a second SN of a previously transmitted second PDCP packet by more than a packet data convergence protocol (PDCP) sequence number (SN) jump threshold of the UE.
  • PDCP packet data convergence protocol
  • Operations 800 continue at block 806 by receiving, from the UE, a detach request, in response to the first PDCP packet.
  • operations 800 continue by receiving, from the UE, an attach request to the network, subsequent to the detach request.
  • FIG. 9 is a call flow diagram 900 illustrating example signaling for using a packet data convergence protocol (PDCP) sequence number (SN) jump threshold to recover from a data stall issue that can occur in non-standalone (NSA) new radio (NR) communications systems, in accordance with aspects of the present disclosure.
  • the example signaling is between a UE 902 (e.g., UE 120a) , an LTE cell 904, and an NR cell 906.
  • the UE sends an ATTACH REQUEST message indicating that the UE supports DCNR to the LTE cell.
  • the LTE cell sends an ATTACH ACCEPT to the UE.
  • the LTE cell sends an RRC configuration message configuring, on the UE, an NR type PDCP layer to receive PDCP packets from the NR cell.
  • the RRC configuration message may, for example, include a PDCP SN jump threshold, although the present disclosure is not so limited and the UE may receive a PDCP SN jump threshold in messages of other types.
  • the NR cell sends a PDCP packet to the UE.
  • the PDCP packet SN differs from an SN of the most recently received PDCP packet (not shown) by more than the PDCP SN jump threshold.
  • the UE detects the PDCP SN jump, i.e., that the PDCP packet SN of the PDCP packet at 916 differs from the SN of the most recently received PDCP packet by more than the PDCP SN jump threshold.
  • the UE sends a DETACH REQUEST (DETACH_REQ) message to the LTE cell.
  • the LTE cell sends a DETACH ACCEPT (DETACH_ACCEPT) message to the UE.
  • the UE sends another ATTACH REQUEST (ATTACH_REQ) message indicating that the UE supports DCNR to the LTE cell.
  • the LTE cell sends an ATTACH ACCEPT to the UE.
  • the UE sends a service request (SR) to the LTE cell.
  • the NR cell sends packet switched data to the UE.
  • FIG. 10 illustrates a communications device 1000 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. 7.
  • the communications device 1000 includes a processing system 1002 coupled to a transceiver 1008 (e.g., a transmitter and/or a receiver) .
  • the transceiver 1008 is configured to transmit and receive signals for the communications device 1000 via an antenna 1010, such as the various signals as described herein.
  • the processing system 1002 may be configured to perform processing functions for the communications device 1000, including processing signals received and/or to be transmitted by the communications device 1000.
  • the processing system 1002 includes a processor 1004 coupled to a computer-readable medium/memory 1012 via a bus 1006.
  • the computer-readable medium/memory 1012 is configured to store instructions (e.g., computer-executable code) that when executed by the processor 1004, cause the processor 1004 to perform the operations illustrated in FIG. 7, or other operations for performing the various techniques discussed herein for using a packet data convergence protocol (PDCP) sequence number (SN) jump threshold to recover from a data stall issue that can occur in non-standalone (NSA) new radio (NR) communications systems.
  • PDCP packet data convergence protocol
  • SN sequence number
  • NR new radio
  • computer-readable medium/memory 1012 stores code 1014 for obtaining a packet data convergence protocol (PDCP) sequence number (SN) jump threshold; code 1016 for detecting that a first SN of a received first PDCP packet differs from a second SN of a previously received second PDCP packet by more than the PDCP SN jump threshold; code 1018 for transmitting a detach request to a network, in response to the detection; and code 1020 for transmitting an attach request to the network, subsequent to the detach request and in response to the detection .
  • the processor 1004 has circuitry configured to implement the code stored in the computer-readable medium/memory 1012.
  • the processor 1004 includes circuitry 1024 for obtaining a packet data convergence protocol (PDCP) sequence number (SN) jump threshold; circuitry 1026 for detecting that a first SN of a received first PDCP packet differs from a second SN of a previously received second PDCP packet by more than the PDCP SN jump threshold; circuitry 1028 for transmitting a detach request to a network, in response to the detection; and circuitry 1030 for transmitting an attach request to the network, subsequent to the detach request and in response to the detection.
  • PDCP packet data convergence protocol
  • SN sequence number
  • FIG. 11 illustrates a communications device 1100 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. 8.
  • the communications device 1100 includes a processing system 1102 coupled to a transceiver 1108 (e.g., a transmitter and/or a receiver) .
  • the transceiver 1108 is configured to transmit and receive signals for the communications device 1100 via an antenna 1110, such as the various signals as described herein.
  • the processing system 1102 may be configured to perform processing functions for the communications device 1100, including processing signals received and/or to be transmitted by the communications device 1100.
  • the processing system 1102 includes a processor 1104 coupled to a computer-readable medium/memory 1112 via a bus 1106.
  • the computer-readable medium/memory 1112 is configured to store instructions (e.g., computer-executable code) that when executed by the processor 1104, cause the processor 1104 to perform the operations illustrated in FIG. 8, or other operations for performing the various techniques discussed herein for using a packet data convergence protocol (PDCP) sequence number (SN) jump threshold to recover from a data stall issue that can occur in non-standalone (NSA) new radio (NR) communications systems.
  • PDCP packet data convergence protocol
  • SN sequence number
  • NR new radio
  • computer-readable medium/memory 1112 stores code 1114 for transmitting a configuration to a user equipment (UE) ; code 1116 for transmitting, to the UE, a first PDCP packet having a first SN that differs from a second SN of a previously transmitted second PDCP packet by more than a packet data convergence protocol (PDCP) sequence number (SN) jump threshold of the UE; code 1118 for receiving, from the UE, a detach request, in response to the first PDCP packet; and code 1120 for receiving, from the UE, an attach request to the network, subsequent to the detach request.
  • the processor 1104 has circuitry configured to implement the code stored in the computer-readable medium/memory 1112.
  • the processor 1104 includes circuitry 1124 for transmitting a configuration to a user equipment (UE) ; circuitry 1126 for transmitting a first PDCP packet having a first SN that differs from a second SN of a previously transmitted second PDCP packet by more than a packet data convergence protocol (PDCP) sequence number (SN) jump threshold of the UE; circuitry 1128 for receiving, from the UE, a detach request, in response to the first PDCP packet; and circuitry 1130 for receiving, from the UE, an attach request to the network, subsequent to the detach request.
  • PDCP packet data convergence protocol
  • SN packet data convergence protocol sequence number
  • NR e.g., 5G NR
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • 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 CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA) , cdma2000, etc.
  • UTRA Universal Terrestrial Radio Access
  • 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) .
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as NR (e.g. 5G RA) , Evolved UTRA (E-UTRA) , Ultra Mobile Broadband (UMB) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDMA, etc.
  • NR e.g. 5G RA
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS) .
  • LTE and LTE-A are releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • NR is an emerging wireless communications technology under development.
  • the term “cell” can refer to a coverage area of a Node B (NB) and/or a NB subsystem serving this coverage area, depending on the context in which the term is used.
  • NB Node B
  • BS next generation NodeB
  • AP access point
  • DU distributed unit
  • TRP transmission reception point
  • a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cells.
  • 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 an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG) , UEs for users in the home, etc. ) .
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a pico cell may be referred to as a pico BS.
  • a BS for a femto cell may be referred to as a femto BS or a home BS.
  • 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.
  • CPE Customer Premises Equipment
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine-type communication
  • eMTC evolved MTC
  • MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, 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.
  • a network e.g., a wide area network such as Internet or a cellular network
  • Some UEs may be considered Internet-of-Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.
  • IoT Internet-of-Things
  • NB-IoT narrowband IoT
  • a scheduling entity (e.g., a BS) allocates resources for communication among some or all devices and equipment within its service area or cell.
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity.
  • Base stations are not the only entities that may function as a scheduling entity.
  • a UE may function as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs) , and the other UEs may utilize the 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 communicate directly with one another in addition to communicating with a scheduling entity.
  • the methods disclosed herein comprise one or more steps or actions for achieving the methods.
  • the method steps and/or actions may be interchanged with one another without departing from the scope of the claims.
  • the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
  • Embodiment 1 A method for wireless communications performed by a user equipment (UE) , comprising obtaining a packet data convergence protocol (PDCP) sequence number (SN) jump threshold; detecting that a first SN of a received first PDCP packet differs from a second SN of a previously received second PDCP packet by more than the PDCP SN jump threshold; transmitting a detach request to a network, in response to the detection; and transmitting an attach request to the network, subsequent to the detach request and in response to the detection.
  • PDCP packet data convergence protocol
  • SN sequence number
  • Embodiment 2 The method of Embodiment 1, wherein obtaining the PDCP SN jump threshold further comprises: receiving a configuration from the network; and determining the PDCP SN jump threshold based on the configuration.
  • Embodiment 3 The method of Embodiments 2, wherein the configuration is received in a radio resource configuration (RRC) message.
  • RRC radio resource configuration
  • Embodiment 4 The method of Embodiments 1-3, wherein the attach request comprises an indication that the UE supports dual connectivity with new radio (DCNR) .
  • DCNR new radio
  • Embodiment 5 The method of any of Embodiments 1-4, further comprising sending another attach request to the network with an indication that the UE supports dual connectivity with new radio (DCNR) prior to obtaining the PDCP SN jump threshold.
  • DCNR new radio
  • Embodiment 6 The method of any of Embodiments 1-5, further comprising receiving a configuration from the network that configures the UE with a new radio (NR) type PDCP layer.
  • NR new radio
  • Embodiment 7 A method for wireless communications performed by a base station (BS) , comprising transmitting a configuration to a user equipment (UE) ; transmitting, to the UE, a first PDCP packet having a first SN that differs from a second SN of a previously transmitted second PDCP packet by more than a packet data convergence protocol (PDCP) sequence number (SN) jump threshold of the UE; receiving, from the UE, a detach request, in response to the first PDCP packet; and receiving, from the UE, an attach request to the network, subsequent to the detach request.
  • PDCP packet data convergence protocol
  • SN packet data convergence protocol
  • Embodiment 8 The method of Embodiment 7, wherein the attach request comprises an indication that the UE supports dual connectivity with new radio (DCNR) .
  • DCNR new radio
  • Embodiment 9 The method of any of Embodiments 7-8, further comprising: receiving, from the UE, another attach request message with an indication that the UE supports dual connectivity with new radio (DCNR) prior to transmitting the configuration.
  • DCNR new radio
  • Embodiment 10 The method of any of Embodiments 7-9, wherein the configuration is transmitted in a radio resource configuration (RRC) message.
  • RRC radio resource configuration
  • Embodiment 11 The method of any of Embodiments 7-10, wherein the configuration comprises a new radio (NR) type PDCP layer configuration for the UE.
  • NR new radio
  • 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) .
  • 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 various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
  • the means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • PLD programmable logic device
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine.
  • 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, 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.
  • RAM Random Access Memory
  • ROM Read Only Memory
  • PROM Programmable Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrical 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, for example, instructions for performing the operations described herein and illustrated in FIG. 7 and/or FIG. 8.
  • 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.

Abstract

Certains aspects de la présente divulgation concernent des techniques de récupération d'un décrochage de données dans des systèmes nouvelle radio non-autonomes. Un procédé qui peut être mis en œuvre par un équipement utilisateur (UE) consiste à recevoir une configuration comprenant un seuil de saut de numéro de séquence (SN) de protocole de convergence de données par paquets (PDCP) en provenance d'un réseau; à détecter qu'un premier SN d'un premier paquet PDCP reçu diffère d'un second SN d'un second paquet PDCP précédemment reçu par un seuil supérieur au seuil de saut SN de PDCP; à transmettre une demande de détachement au réseau, en réponse à la détection; et à transmettre une demande de rattachement au réseau, suite à la demande de détachement et en réponse à la détection.
PCT/CN2020/090922 2020-05-18 2020-05-18 Récupération d'un décrochage de données dans des systèmes nouvelle radio non-autonomes WO2021232210A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/090922 WO2021232210A1 (fr) 2020-05-18 2020-05-18 Récupération d'un décrochage de données dans des systèmes nouvelle radio non-autonomes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/090922 WO2021232210A1 (fr) 2020-05-18 2020-05-18 Récupération d'un décrochage de données dans des systèmes nouvelle radio non-autonomes

Publications (1)

Publication Number Publication Date
WO2021232210A1 true WO2021232210A1 (fr) 2021-11-25

Family

ID=78708951

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/090922 WO2021232210A1 (fr) 2020-05-18 2020-05-18 Récupération d'un décrochage de données dans des systèmes nouvelle radio non-autonomes

Country Status (1)

Country Link
WO (1) WO2021232210A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104703293A (zh) * 2014-12-11 2015-06-10 中兴通讯股份有限公司 一种lipa/sipto连接的建立方法和装置
WO2018148325A1 (fr) * 2017-02-09 2018-08-16 Apple Inc. Double connectivité 5g/lte
WO2020060817A1 (fr) * 2018-09-18 2020-03-26 Cisco Technology, Inc. Procédés et appareil pour sélectionner une passerelle de service pour une session d'un équipement utilisateur (ue) dans un réseau mobile qui a des déploiements d'architecture 5g non autonomes (nsa)

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104703293A (zh) * 2014-12-11 2015-06-10 中兴通讯股份有限公司 一种lipa/sipto连接的建立方法和装置
WO2018148325A1 (fr) * 2017-02-09 2018-08-16 Apple Inc. Double connectivité 5g/lte
WO2020060817A1 (fr) * 2018-09-18 2020-03-26 Cisco Technology, Inc. Procédés et appareil pour sélectionner une passerelle de service pour une session d'un équipement utilisateur (ue) dans un réseau mobile qui a des déploiements d'architecture 5g non autonomes (nsa)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NGMN ALLIANCE: "DEFINITION OF THE TESTING FRAMEWORK FOR THE NGMN 5G TTI INTEROPERABILITY", NGMN THE ENGINE OF BROADBAND WIRELESS INNOVATION, 31 August 2018 (2018-08-31), pages 1 - 59, XP051562075 *

Similar Documents

Publication Publication Date Title
US10735078B2 (en) Operations with bandwidth part (BWP) switching
US11871424B2 (en) Paging design with short message indicator
US20220256499A1 (en) Resolution of paging collisions in multisim and c-rat operation
US20220116809A1 (en) Early measurement reporting
US10904789B2 (en) Methods and apparatus to reduce UE capability information message size
US10785797B2 (en) Beam refinement reference signal (BRRS) design for mmWave system in shared spectrum
CN114450998B (zh) 波束失败恢复以及相关定时确定技术
US11076406B2 (en) Beam management for physical downlink control channel (PDCCH) transmission and reception
US20210176349A1 (en) Packet data convergence protocol (pdcp) duplication enhancements
WO2020154993A1 (fr) Résolution de collision d'identifiant de cellule physique (pci)
WO2021217565A1 (fr) Gestion de rapport de mesure pour réduire les défaillances de session de communication pendant un transfert intercellulaire
WO2021232335A1 (fr) Techniques d'amélioration des transferts dans des réseaux sans fil
WO2021243668A1 (fr) Gestion dynamique de créneaux de trames radio
WO2021212315A1 (fr) Amélioration de canal de commande de liaison montante physique pour des trous de couverture intérieurs
WO2021232210A1 (fr) Récupération d'un décrochage de données dans des systèmes nouvelle radio non-autonomes
EP4162623A1 (fr) Transmissions de blocs de signaux de synchronisation dans des réseaux non terrestres
WO2021173332A1 (fr) Faisceau appliqué mis à jour avant un temps de transmission déclenché
WO2021208040A1 (fr) Message de demande attach (rattachement) permettant d'indiquer un support dcnr désactivé
WO2021223044A1 (fr) Techniques de récupération à partir d'un événement de libération de cellule pour une connectivité double
WO2021243725A1 (fr) Évitement de problèmes d'accès aléatoire dans des cellules de nouvelle radio non autonomes
WO2021253320A1 (fr) Atténuation de configuration d'agrégation de porteuses incorrecte
WO2021226942A1 (fr) Restauration de données en paquets commutés lorsqu'un support par défaut est supprimé
WO2021223203A1 (fr) Auto-adaptation d'ue pour connexion de session pdu dans un réseau autonome 5g
WO2021258387A1 (fr) Réduction du coût d'itinérance dans nr
WO2021243685A1 (fr) Procédé d'élagage d'échec de demande de planification (sr)

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

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

Country of ref document: EP

Kind code of ref document: A1