WO2021208051A1 - Restauration de connectivité de données après une défaillance par libérations de connexion rrc dans un réseau non autonome - Google Patents

Restauration de connectivité de données après une défaillance par libérations de connexion rrc dans un réseau non autonome Download PDF

Info

Publication number
WO2021208051A1
WO2021208051A1 PCT/CN2020/085233 CN2020085233W WO2021208051A1 WO 2021208051 A1 WO2021208051 A1 WO 2021208051A1 CN 2020085233 W CN2020085233 W CN 2020085233W WO 2021208051 A1 WO2021208051 A1 WO 2021208051A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmitting
communication
serving cell
count
aspects
Prior art date
Application number
PCT/CN2020/085233
Other languages
English (en)
Inventor
Hao Zhang
Chaofeng HUI
Fojian ZHANG
Jian Li
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/085233 priority Critical patent/WO2021208051A1/fr
Publication of WO2021208051A1 publication Critical patent/WO2021208051A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for restoration of data connectivity after failure by radio resource control connection releases in a non-standalone network.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, and/or the like) .
  • 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, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE) .
  • LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
  • UMTS Universal Mobile Telecommunications System
  • a wireless communication network may include a number of base stations (BSs) that can support communication for a number of user equipment (UEs) .
  • a user equipment (UE) may communicate with a base station (BS) via the downlink and uplink.
  • the downlink (or forward link) refers to the communication link from the BS to the UE
  • the uplink (or reverse link) refers to the communication link from the UE to the BS.
  • a BS may be referred to as a Node B, a gNB, an access point, a radio head, a transmit receive point (TRP) , a New Radio (NR) BS, a 5G Node B, and/or the like.
  • New Radio which may also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
  • 3GPP Third Generation Partnership Project
  • 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 orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL) , using CP-OFDM and/or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink (UL) , as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)
  • DFT-s-OFDM discrete Fourier transform spread OFDM
  • MIMO multiple-input multiple-output
  • a method of wireless communication may include determining, while registered with a non-standalone (NSA) network, whether a count of radio resource control (RRC) connection releases satisfies a release threshold, based at least in part on transmitting one or more service requests; and transmitting, based at least in part on determining that the count satisfies the release threshold, an indication that the UE does not support dual connectivity with New Radio (DCNR) .
  • NSA non-standalone
  • a UE for wireless communication may include memory and one or more processors coupled to the memory.
  • the memory may include instructions executable by the one or more processors to cause the UE to determine, while registered with an NSA network, whether a count of RRC connection releases satisfies a release threshold, based at least in part on transmitting one or more service requests; and transmit, based at least in part on determining that the count satisfies the release threshold, an indication that the UE does not support DCNR.
  • a non-transitory computer-readable medium may store one or more instructions for wireless communication.
  • the one or more instructions when executed by one or more processors of a UE, may cause the UE to determine, while registered with an NSA network, whether a count of RRC connection releases satisfies a release threshold, based at least in part on transmitting one or more service requests; and transmit, based at least in part on determining that the count satisfies the release threshold, an indication that the UE does not support DCNR.
  • an apparatus for wireless communication may include means for determining, while registered with an NSA network, whether a count of RRC connection releases satisfies a release threshold, based at least in part on transmitting one or more service requests; and means for transmitting, based at least in part on determining that the count satisfies the release threshold, an indication that the apparatus does not support DCNR.
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.
  • Fig. 1 is a block diagram conceptually illustrating an example of a wireless communication network, in accordance with various aspects of the present disclosure.
  • Fig. 2 is a block diagram conceptually illustrating an example of a base station in communication with a user equipment (UE) in a wireless communication network, in accordance with various aspects of the present disclosure.
  • UE user equipment
  • Fig. 3 is a diagram illustrating an example of radio resource control (RRC) connection releases in a non-standalone (NSA) network, in accordance with various aspects of the present disclosure.
  • RRC radio resource control
  • Figs. 4 and 5 are diagrams illustrating examples of restoring data connectivity after failure by RRC connection releases in an NSA network, in accordance with various aspects of the present disclosure.
  • Fig. 6 is a diagram illustrating an example process performed, for example, by a UE, in accordance with various aspects of the present disclosure.
  • Fig. 7 is a conceptual data flow diagram illustrating an example of a data flow between different components in an example apparatus.
  • Fig. 8 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.
  • aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as Fifth Generation (5G) and later, including New Radio (NR) technologies.
  • 5G Fifth Generation
  • NR New Radio
  • Fig. 1 is a diagram illustrating a wireless network 100 in which aspects of the present disclosure may be practiced.
  • the wireless network 100 may be a Long Term Evolution (LTE) network or some other wireless network, such as a 5G or NR network.
  • the wireless network 100 may include a number of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities.
  • a BS is an entity that communicates with user equipment (UEs) and may also be referred to as a base station, a NR BS, a Node B, a gNB, a 5G node B (NB) , an access point, a transmit receive point (TRP) , and/or the like.
  • Each BS may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used.
  • a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or another type of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG) ) .
  • 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 BS 110a may be a macro BS for a macro cell 102a
  • a BS 110b may be a pico BS for a pico cell 102b
  • a BS 110c may be a femto BS for a femto cell 102c.
  • a BS may support one or multiple (e.g., three) cells.
  • eNB base station
  • NR BS NR BS
  • gNB gNode B
  • AP AP
  • node B node B
  • 5G NB 5G NB
  • cell may be used interchangeably herein.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS.
  • the BSs may be interconnected to one another and/or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, and/or the like using any suitable transport network.
  • Wireless network 100 may also include relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS) .
  • a relay station may also be a UE that can relay transmissions for other UEs.
  • a relay station 110d may communicate with macro BS 110a and a UE 120d in order to facilitate communication between BS 110a and UE 120d.
  • a relay station may also be referred to as a relay BS, a relay base station, a relay, and/or the like.
  • Wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/or the like. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100.
  • macro BSs may have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts) .
  • a network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs.
  • Network controller 130 may communicate with the BSs via a backhaul.
  • the BSs may also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.
  • UEs 120 may be dispersed throughout wireless network 100, and each UE may be stationary or mobile.
  • a UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, and/or the like.
  • a UE may be a cellular phone (e.g., a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet) ) , an entertainment device (e.g., a music or video device, or a satellite radio) , a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.
  • PDA personal digital assistant
  • WLL wireless local loop
  • Some UEs may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, and/or the like, that may communicate with a base station, 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.
  • Some UEs may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband internet of things) devices.
  • IoT Internet-of-Things
  • NB-IoT narrowband internet of things
  • UE 120 may be included inside a housing that houses components of UE 120, such as processor components, memory components, and/or the like.
  • the processor components and the memory components may be coupled together.
  • the processor components e.g., one or more processors
  • the memory components e.g., a memory
  • the processor components and the memory components may be operatively coupled, communicatively coupled, electronically coupled, electrically coupled, and/or the like.
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies.
  • a RAT may also be referred to as a radio technology, an air interface, and/or the like.
  • a frequency may also be referred to as a carrier, a frequency channel, and/or the like.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another) .
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, and/or the like) , a mesh network, and/or the like.
  • V2X vehicle-to-everything
  • the UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.
  • wireless network 100 may be a non-standalone NSA deployment of a wireless network.
  • wireless network 100 includes BSs 110 that operate using a plurality of wireless network technologies (e.g., LTE, 5G/NR, and/or the like) , and that are communicatively connected to one or more network controllers 130 in a core network operating using one of the plurality of wireless network technologies (e.g., LTE) .
  • the BSs 110 in wireless network 100 may include one or more BSs 110 that operate using LTE and one or more BSs 110 that operate using 5G/NR.
  • a UE 120 in the wireless network may be capable of supporting a dual connectivity connection with a plurality of serving cells.
  • the UE 120 may be simultaneously connected to a first serving cell (e.g., a primary serving cell via which the UE 120 performs control communications and data communications) and a second serving cell (e.g., a secondary serving cell via which the UE 120 performs data communications) .
  • the first serving cell and the second serving cell may be provided by one or more BSs 110 of the same wireless network technology (e.g., LTE, 5G/NR, and/or the like) .
  • the first serving cell and the second serving cell may be provided by one or more BSs 110 that use different wireless network technologies.
  • the BS 110 providing the first serving cell may use LTE
  • the BS 110 providing the second serving cell may use 5G/NR.
  • Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
  • Fig. 2 shows a block diagram of a design 200 of base station 110 and UE 120, which may be one of the base stations and one of the UEs in Fig. 1.
  • Base station 110 may be equipped with T antennas 234a through 234t
  • UE 120 may be equipped with R antennas 252a through 252r, where in general T ⁇ 1 and R ⁇ 1.
  • a transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based at least in part on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS (s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and/or the like) and control information (e.g., CQI requests, grants, upper layer signaling, and/or the like) and provide overhead symbols and control symbols.
  • MCS modulation and coding schemes
  • Transmit processor 220 may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS) ) and synchronization signals (e.g., the primary synchronization signal (PSS) and secondary synchronization signal (SSS) ) .
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM and/or the like) to obtain an output sample stream.
  • TX transmit
  • MIMO multiple-input multiple-output
  • Each modulator 232 may process a respective output symbol stream (e.g., for OFDM and/or the like) to obtain an output sample stream.
  • Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.
  • the synchronization signals can be generated with location encoding to convey additional information.
  • antennas 252a through 252r may receive the downlink signals from base station 110 and/or other base stations and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively.
  • Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples.
  • Each demodulator 254 may further process the input samples (e.g., for OFDM and/or the like) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller/processor 280.
  • a channel processor may determine reference signal received power (RSRP) , received signal strength indicator (RSSI) , reference signal received quality (RSRQ) , channel quality indicator (CQI) , and/or the like.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSRQ reference signal received quality
  • CQI channel quality indicator
  • one or more components of UE 120 may be included in a housing.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) from controller/processor 280. Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, and/or the like) , and transmitted to base station 110.
  • modulators 254a through 254r e.g., for DFT-s-OFDM, CP-OFDM, and/or the like
  • the uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 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 UE 120.
  • Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller/processor 240.
  • Base station 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244.
  • Network controller 130 may include communication unit 294, controller/processor 290, and memory 292.
  • Controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component (s) of Fig. 2 may perform one or more techniques associated with restoring data connectivity after failure by radio resource control (RRC) connection releases in an NSA network, as described in more detail elsewhere herein.
  • controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 600 of Fig. 6, and/or other processes as described herein.
  • Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively.
  • memory 242 and/or memory 282 may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication.
  • the one or more instructions when executed (e.g., directly, or after compiling, converting, interpreting, and/or the like) by one or more processors of the base station 110 and/or the UE 120, may perform or direct operations of, for example, process 600 of Fig. 6, and/or other processes as described herein.
  • executing instructions may include running the instructions, converting the instructions, compiling the instructions, interpreting the instructions, and/or the like.
  • a scheduler 246 may schedule UEs for data transmission on the downlink and/or uplink.
  • UE 120 may include means for determining, while registered with an NSA network, whether a count of RRC connection releases satisfies a release threshold, based at least in part on transmitting one or more service requests, means for transmitting, based at least in part on determining that the count satisfies the release threshold, an indication that the UE 120 does not support dual connectivity with New Radio (DCNR) , and/or the like.
  • DCNR New Radio
  • such means may include one or more components of UE 120 described in connection with Fig. 2, such as controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and/or the like.
  • Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
  • Fig. 3 is a diagram illustrating an example 300 of RRC connection releases in an NSA network, in accordance with various aspects of the present disclosure.
  • Fig. 3 illustrates an example signaling diagram for a UE registered with an NSA network.
  • the UE may include an application processor (AP) and a UE modem.
  • the AP may use the UE modem to access services for applications.
  • An NSA network may be supported by existing LTE infrastructure and may provide access to the Internet and/or other packet switched (PS) data services for the UE registered in the NSA network.
  • the UE may seek to enhance a user experience by accessing a 5G (NR) data service.
  • the UE may transmit an attach request communication or a tracking area update (TAU) request to a serving cell (e.g., an LTE cell and/or another type of cell) .
  • the request (e.g., ATTACH_REQ or TRACKING_AREA_UPDATE_REQ) may include an indication of support for dual connectivity with New Radio (DCNR) to inform the serving cell that the UE is NR capable.
  • DCNR New Radio
  • the UE may receive an attach accept communication (e.g., ATTACH_ACCEPT) or a TAU accept communication (e.g., TRACKING_AREA_UPDATE_ACCEPT) from the serving cell.
  • an attach accept communication e.g., ATTACH_ACCEPT
  • a TAU accept communication e.g., TRACKING_AREA_UPDATE_ACCEPT
  • the UE may attempt to access the NR data service by transmitting a service request to the serving cell.
  • the service request may be an RRC connection establishment request communication (e.g., RRC_CONNECTION_EST_REQ) .
  • RRC connection release communication e.g., RRC_CONNECTION_REL
  • EPS evolved packet system
  • the UE may attempt to set up EPS bearers again.
  • the AP of the UE may signal for the UE modem to request a data call setup for PS data transfer (e.g., SETUP_DATA_CALL_REQ) .
  • the UE may transmit a packet data network (PDN) connectivity request communication.
  • PDN packet data network
  • the UE may activate a default EPS bearer context.
  • Reference numbers 315 through 340 may be referred to as Procedure 1.
  • the UE requests NR data service again, such as shown by reference number 315, the UE may again receive an RRC connection release and drop any EPS bearers.
  • Procedure 1 continues in a never-ending loop, where data service is requested and then data bearers are dropped due to an RRC connection release. As a result, the UE loses all data service.
  • Fig. 3 is provided as an example. Other examples may differ from what is described with respect to Fig. 3.
  • Fig. 4 is a diagram illustrating an example 400 of restoring data connectivity after failure by RRC connection releases in an NSA network, in accordance with various aspects of the present disclosure.
  • example 400 may include communication between a UE (e.g., a UE 120 illustrated and described above in connection with Figs. 1 and 2) and a serving cell (e.g., a BS 110 illustrated and described above in connection with Figs. 1 and 2) .
  • the UE and the serving cell are included in a wireless network such as wireless network 100.
  • the wireless network is an NSA network.
  • the UE and the serving cell communicate on a wireless access link, which may include an uplink and a downlink.
  • the UE may include an AP component (e.g., controller/processor 280) and a UE modem (e.g., receive processor 258, transmit processor 264, and/or the like) .
  • the AP may use the UE modem to access services for applications.
  • the UE supports DCNR, in which case the UE may be capable of communicatively connecting and communicating with an LTE cell and a 5G NR cell.
  • the serving cell for the UE may be an LTE cell in an NSA configuration.
  • the UE may halt the never-ending loop of Procedure 1 illustrated and described above in connection with Fig. 3, which may include the actions performed in connection with reference numbers 315-340.
  • the UE may transmit, to a serving cell, an attach request communication or a TAU request communication that indicates the UE supports DCNR.
  • the UE may receive an attach accept communication or a TAU accept communication from the serving cell based at least in part on transmitting the attach request communication or the TAU request communication to the serving cell.
  • the UE may halt the never-ending loop of Procedure 1 by performing a detach and attach procedure after a particular quantity of RRC connection releases (e.g., 3 RRC connection releases, 5 RRC connection releases, or another quantity of RRC connection releases) in Procedure 2 illustrated in Fig. 4.
  • a particular quantity of RRC connection releases e.g., 3 RRC connection releases, 5 RRC connection releases, or another quantity of RRC connection releases
  • Performing the detach and attach procedure after the particular quantity of RRC connection releases enables the UE and the serving cell to perform multiple attempts to establish PS data transfer, while permitting the UE to restore PS data transfer via the NSA network after multiple failed attempts.
  • the UE modem may count a quantity of RRC connection releases, and determine whether the count of RRC connection releases satisfies a release threshold (e.g., maximum count) .
  • the UE modem may count the quantity of RRC connection releases using a counter, which may be referred to as MAX_NSA_Failure or another parameter.
  • the UE modem determines the count of RRC connection releases during a release timer.
  • the release timer may be set to a particular duration of time and/or be reset when PS data transfer is restored.
  • the UE may repeat Procedure 2 by transmitting another service request communication to the serving cell (first signal of Procedure 2) . If the UE modem determines that the count satisfies the release threshold (405-YES) , the UE (e.g., using a receive processor 258, a transmit processor 264, and/or the like) may exit Procedure 2 and perform a detach and attach procedure.
  • the UE may transmit (e.g., using an antenna 252, a MOD 254, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, and/or the like) a detach request to the serving cell.
  • the UE may receive (e.g., using an antenna 252, a DEMOD 254, a MIMO detector 256, a receive processor 258, a controller/processor 280, and/or the like) a detach accept communication from the serving cell based at least in part on transmitting the detach request communication to the serving cell.
  • the detach request communication from the UE may be an indication that the UE is detaching from the serving cell and that the UE may not wait to receive a detach accept communication to detach.
  • the UE may then attempt a new attachment to the serving cell.
  • the UE may transmit (e.g., using an antenna 252, a MOD 254, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, and/or the like) an attach request communication to the serving cell.
  • the UE may transmit the attach request communication based at least in part on receiving (e.g., using an antenna 252, a DEMOD 254, a MIMO detector 256, a receive processor 258, a controller/processor 280, and/or the like) the detach accept communication from the serving cell.
  • the detach request communication may include an indication that the UE does not support dual connectivity (e.g., may include an indication that the UE does not support DCNR) .
  • the detach request communication may include a flag, a bit field, or another indicator configured to indicate that the UE does not support DCNR.
  • the UE may receive an attach accept communication.
  • the attach request may involve or may follow a random access channel (RACH) procedure.
  • RACH random access channel
  • the UE may indicate, using the detach and attach procedure, that the UE does not support DCNR as a fallback to LTE data transfer to resolve a particular issue that caused the RRC connection releases and associated drop in PS data service.
  • the UE may transmit (e.g., using an antenna 252, a MOD 254, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, and/or the like) a service request communication to the serving cell based at least in part on receiving the attach accept communication.
  • the UE may activate (e.g., using a receive processor 258, a transmit processor 264, and/or the like) one or more EPS bearers and not receive an RRC connection release shortly thereafter.
  • the UE may then transfer data between the serving cell and the UE as part of a PS data service.
  • the UE may reset the count of RRC connection releases based at least in part on establishing and/or maintaining a successful RRC connection. In some aspects, the UE may reset the count based at least in part on a serving cell change. The UE may adjust the release threshold based at least in part on a history of RRC connection releases, information from a base station, and/or the like.
  • Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.
  • Fig. 5 is a diagram illustrating an example 500 of restoring data connectivity after failure by RRC connection releases in an NSA network, in accordance with various aspects of the present disclosure.
  • example 500 may include communication between a UE (e.g., a UE 120 illustrated and described above in connection with Figs. 1 and 2) and a serving cell (e.g., a BS 110 illustrated and described above in connection with Figs. 1 and 2) .
  • the UE and the serving cell are included in a wireless network such as wireless network 100.
  • the wireless network is an NSA network.
  • the UE and the serving cell communicate on a wireless access link, which may include an uplink and a downlink.
  • the UE may include an AP component (e.g., controller/processor 280) and a UE modem (e.g., receive processor 258, transmit processor 264, and/or the like) .
  • the AP may use the UE modem to access services for applications.
  • the UE supports DCNR, in which case the UE may be capable of communicatively connecting and communicating with an LTE cell and a 5G NR cell.
  • the serving cell for the UE may be an LTE cell in an NSA configuration.
  • the UE may halt the never-ending loop of Procedure 1 illustrated and described above in connection with Fig. 3, which may include the actions performed in connection with reference numbers 315-340.
  • the UE may transmit, to a serving cell, an attach request communication or a TAU request communication that indicates the UE supports DCNR.
  • the UE may receive an attach accept communication or a TAU accept communication from the serving cell based at least in part on transmitting the attach request communication or the TAU request communication to the serving cell.
  • the UE may halt the never-ending loop of Procedure 1 by performing a TAU procedure after a particular quantity of RRC connection releases (e.g., 2 RRC connection releases, 7 RRC connection releases, or another quantity of RRC connection releases) in Procedure 3 illustrated in Fig. 5.
  • Performing the TAU procedure after the particular quantity of RRC connection releases enables the UE and the serving cell to perform multiple attempts to establish PS data transfer, while permitting the UE to restore PS data transfer via the NSA network after multiple failed attempts.
  • the UE modem may count a quantity of RRC connection releases, and determine whether the count of RRC connection releases satisfies a release threshold (e.g., maximum count) .
  • the UE modem may count the quantity of RRC connection releases using a counter, which may be referred to as MAX_NSA_Failure or another parameter.
  • the UE modem determines the count of RRC connection releases during a release timer.
  • the release timer may be set to a particular duration of time and/or be reset when PS data transfer is restored.
  • the UE may repeat Procedure 3 by transmitting another service request communication to the serving cell (first signal of Procedure 3) . If the UE modem determines that the count satisfies the release threshold (505-YES) , the UE (e.g., using a receive processor 258, a transmit processor 264, and/or the like) may exit Procedure 3 and perform a TAU procedure.
  • the TAU procedure may include the UE transmitting (e.g., using an antenna 252, a MOD 254, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, and/or the like) a TAU request communication (TAU_REQ) to the serving cell.
  • the TAU procedure may include the UE receiving (e.g., using an antenna 252, a DEMOD 254, a MIMO detector 256, a receive processor 258, a controller/processor 280, and/or the like) a TAU accept communication (TAU_ACCEPT) from the serving cell based at least in part on transmitting the TAU request communication to the serving cell.
  • TAU_ACCEPT TAU accept communication
  • the TAU request communication from the UE may be a request to update one or more tracking parameters of the UE, such as a location of the UE, a connectivity state of the UE, a zone identifier associated with the UE, and/or the like.
  • the TAU accept communication may indicate acceptance of the updated tracking parameters by the serving cell.
  • the TAU request communication may include an indication that the UE does not support dual connectivity (e.g., may include an indication that the UE does not support DCNR) .
  • the TAU request communication may include a flag, a bit field, or another indicator configured to indicate that the UE does not support DCNR.
  • the UE may indicate, using the TAU procedure, that the UE does not support DCNR as a fallback to LTE data transfer to resolve a particular issue that caused the RRC connection releases and associated drop in PS data service.
  • the UE may transmit (e.g., using an antenna 252, a MOD 254, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, and/or the like) a service request communication to the serving cell based at least in part on receiving the TAU accept communication.
  • the UE may activate (e.g., using a receive processor 258, a transmit processor 264, and/or the like) one or more EPS bearers and not receive an RRC connection release shortly thereafter.
  • the UE may then transfer data between the serving cell and the UE as part of a PS data service.
  • the UE may reset the count of RRC connection releases based at least in part on establishing and/or maintaining a successful RRC connection. In some aspects, the UE may reset the count based at least in part on a serving cell change. The UE may adjust the release threshold based at least in part on a history of RRC connection releases, information from a base station, and/or the like.
  • Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.
  • Fig. 6 is a diagram illustrating an example process 600 performed, for example, by a UE, in accordance with various aspects of the present disclosure.
  • Example process 600 is an example where the UE (e.g., a UE 120 depicted in Figs. 1 and 2, an NSA UE modem depicted in Figs. 4 and/or 5, and/or the like) performs operations associated with NR data connectivity from an NSA network.
  • the UE e.g., a UE 120 depicted in Figs. 1 and 2, an NSA UE modem depicted in Figs. 4 and/or 5, and/or the like
  • process 600 may include determining, while registered with an NSA network, whether a count of RRC connection releases satisfies a release threshold, based at least in part on transmitting one or more service requests (block 610) .
  • the UE e.g., using receive processor 258, transmit processor 264, controller/processor 280, memory 282, and/or the like
  • process 600 may include transmitting, based at least in part on determining that the count satisfies the release threshold, an indication that the UE does not support DCNR (block 620) .
  • the UE e.g., using an antenna 252, a MOD 254, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, and/or the like
  • Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • transmitting the indication that the UE does not support DCNR comprises transmitting a detach request communication to a serving cell that transmitted the RRC connection releases, wherein the detach request communication includes the indication that the UE does not support DCNR.
  • process 600 includes receiving, based at least in part on transmitting the detach request communication, a detach accept communication from the serving cell; transmitting, based at least in part on receiving the detach accept communication, an attach request communication to the serving cell; receiving, based at least in part on transmitting the attach request communication, an attach accept communication from the serving cell; and transmitting, based at least in part on receiving the attach accept communication, a service request to the serving cell.
  • the serving cell is an LTE cell.
  • transmitting the indication that the UE does not support DCNR comprises transmitting a TAU request communication to a serving cell that transmitted the RRC connection releases, wherein the TAU request communication includes the indication that the UE does not support DCNR.
  • process 600 includes receiving, based at least in part on transmitting the TAU request communication, a TAU accept communication from the serving cell; and transmitting, based at least in part on receiving the TAU accept communication, a service request to the serving cell.
  • the serving cell is an LTE cell.
  • process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.
  • Fig. 7 is a conceptual data flow diagram 700 illustrating a data flow between different components in an example apparatus 702.
  • the apparatus 702 may be a UE (e.g., UE 120 illustrated and described above in connection with one or more of Figs. 1, 2, 4, and/or 5) .
  • the apparatus 702 includes a reception component 704, a determining component 706, and a transmission component 708.
  • reception component 704 may receive one or more RRC connection releases 710 from a serving cell 750 (e.g., BS 110 illustrated and described above in connection with one or more of Figs. 1, 2, 4, and/or 5) based at least in part on transmission component 708 transmitting one or more service requests 712.
  • determining component 706 may determine, while the apparatus 702 is registered with an NSA network, whether a count of the RRC connection releases 710 satisfies a release threshold.
  • transmission component 708 may transmit an indication 714 that the apparatus 702 does not support DCNR to the serving cell 750.
  • transmission component 708 may transmit the indication 714 based at least in part on determining component 706 determining that the count satisfies the release threshold.
  • the apparatus may include additional components that perform each of the blocks of the aforementioned process 600 of Fig. 6 and/or the like. Each block in the aforementioned process 600 of Fig. 6 and/or the like 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.
  • Fig. 5 The number and arrangement of components shown in Fig. 5 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 7. Furthermore, two or more components shown in Fig. 7 may be implemented within a single component, or a single component shown in Fig. 7 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of components (e.g., one or more components) shown in Fig. 7 may perform one or more functions described as being performed by another set of components shown in Fig. 7.
  • Fig. 8 is a diagram 800 illustrating an example of a hardware implementation for an apparatus 702'employing a processing system 802.
  • the apparatus 702' may be a UE (e.g., UE 120 illustrated and described above in connection with one or more of Figs. 1, 2, 4, and/or 5) .
  • the processing system 802 may be implemented with a bus architecture, represented generally by the bus 804.
  • the bus 804 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 802 and the overall design constraints.
  • the bus 804 links together various circuits including one or more processors and/or hardware components, represented by the processor 806, the components 704, 706, 708, and the computer-readable medium/memory 808.
  • the bus 804 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described any further.
  • the processing system 802 may be coupled to a transceiver 810.
  • the transceiver 810 is coupled to one or more antennas 812.
  • the transceiver 810 provides a means for communicating with various other apparatuses over a transmission medium.
  • the transceiver 810 receives a signal from the one or more antennas 812, extracts information from the received signal, and provides the extracted information to the processing system 802.
  • the transceiver 810 receives information from the processing system 802, and based at least in part on the received information, generates a signal to be applied to the one or more antennas 812.
  • the processing system 802 includes a processor 806 coupled to a computer-readable medium/memory 808.
  • the processor 806 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory 808.
  • the software when executed by the processor 806, causes the processing system 802 to perform the various functions described herein for any particular apparatus.
  • the computer-readable medium/memory 808 may also be used for storing data that is manipulated by the processor 806 when executing software.
  • the processing system further includes at least one of the components 704, 706, and 708.
  • the components may be software modules running in the processor 806, resident/stored in the computer readable medium/memory 808, one or more hardware modules coupled to the processor 806, or some combination thereof.
  • the processing system 802 may be a component of the UE 120 and may include the memory 282 and/or at least one of the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, and/or the controller/processor 280 described above in connection with Fig. 2.
  • the apparatus 702/702' for wireless communication includes means for determining, while registered with an NSA network, whether a count of RRC connection releases satisfies a release threshold, based at least in part on transmitting one or more service requests, means for transmitting, based at least in part on determining that the count satisfies the release threshold, an indication that the apparatus 702/702'does not support DCNR, and/or the like.
  • the aforementioned means may be one or more of the aforementioned components of the apparatus 702 and/or the processing system 802 of the apparatus 702'configured to perform the functions recited by the aforementioned means.
  • the processing system 802 may include the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, and/or the controller/processor 280 described above in connection with Fig. 2.
  • the aforementioned means may be the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, and/or the controller/processor 280 configured to perform the functions and/or operations recited herein.
  • Fig. 8 is provided as an example. Other examples may differ from what is described in connection with Fig. 8.
  • ком ⁇ онент is intended to be broadly construed as hardware, firmware, and/or a combination of hardware and software.
  • a processor is implemented in hardware, firmware, and/or a combination of hardware and software.
  • satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and/or the like.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
  • the terms “has, ” “have, ” “having, ” and/or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.

Landscapes

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

Abstract

D'une manière générale, divers aspects de la présente divulgation se rapportent à la communication sans fil. Selon certains aspects, un équipement utilisateur (UE) peut déterminer, tout en étant enregistré auprès d'un réseau non autonome, si un nombre de libérations de connexion de commande de ressource radio satisfait un seuil de libérations, au moins partiellement en fonction de la transmission d'une ou plusieurs demandes de service. L'UE peut transmettre, au moins partiellement en fonction de la détermination du fait que le nombre satisfait le seuil de libérations, une indication du fait que l'UE ne prend pas en charge une connectivité double avec une nouvelle radio. La divulgation concerne également de nombreux autres aspects.
PCT/CN2020/085233 2020-04-17 2020-04-17 Restauration de connectivité de données après une défaillance par libérations de connexion rrc dans un réseau non autonome WO2021208051A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/085233 WO2021208051A1 (fr) 2020-04-17 2020-04-17 Restauration de connectivité de données après une défaillance par libérations de connexion rrc dans un réseau non autonome

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/085233 WO2021208051A1 (fr) 2020-04-17 2020-04-17 Restauration de connectivité de données après une défaillance par libérations de connexion rrc dans un réseau non autonome

Publications (1)

Publication Number Publication Date
WO2021208051A1 true WO2021208051A1 (fr) 2021-10-21

Family

ID=78083756

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/085233 WO2021208051A1 (fr) 2020-04-17 2020-04-17 Restauration de connectivité de données après une défaillance par libérations de connexion rrc dans un réseau non autonome

Country Status (1)

Country Link
WO (1) WO2021208051A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019031827A1 (fr) * 2017-08-07 2019-02-14 Lg Electronics Inc. Procédé et appareil de maintien de configuration de dc
US20190253945A1 (en) * 2018-02-15 2019-08-15 Qualcomm Incorporated Enhanced make-before-break handover
CN110557778A (zh) * 2019-05-16 2019-12-10 Oppo广东移动通信有限公司 一种终端的功耗控制方法、装置及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019031827A1 (fr) * 2017-08-07 2019-02-14 Lg Electronics Inc. Procédé et appareil de maintien de configuration de dc
US20190253945A1 (en) * 2018-02-15 2019-08-15 Qualcomm Incorporated Enhanced make-before-break handover
CN110557778A (zh) * 2019-05-16 2019-12-10 Oppo广东移动通信有限公司 一种终端的功耗控制方法、装置及存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Multi-connectivity support in IAB", 3GPP DRAFT; R2-1906350_MULTI-CONNECTIVITY-IAB-V0, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, U.S.A.; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051729817 *
T-MOBILE USA: "Initial network selection for collocated EN_DC and NR SA", 3GPP DRAFT; R2-1805930 INITIAL NETWORK SELECTION FOR COLLOCATED EN_DC AND NR SA V.10, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Sanya China; 20180416 - 20180420, 14 April 2018 (2018-04-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051429541 *

Similar Documents

Publication Publication Date Title
US11252718B2 (en) Configuration of resource patterns for integrated access and backhaul
US11540211B2 (en) Techniques for integrated access and backhaul capability indication
WO2020222946A1 (fr) Partage de ressources de canal de commande de liaison descendante physique dynamique (pdcch) entre une surveillance de pdcch et une transmission de pdcch dans un réseau à sauts multiples
WO2021168779A1 (fr) Techniques de configuration d'une table de bits mac-ce pour la récupération de défaillance de faisceau
WO2021042125A1 (fr) Activation et désactivation d'état d'indicateur de configuration de transmission
US11533219B2 (en) Prioritizing procedures for transmission of a beam failure recovery request via a secondary cell used for carrier aggregation
WO2021223053A1 (fr) Traitement d'une défaillance de liaison radio répétée associée à un mode de connectivité double
US11937311B2 (en) Techniques for network node conflict resolution
US11071152B2 (en) Access barring and radio resource control connection in new radio to long-term evolution voice fallback
WO2021226982A1 (fr) Augmentation de décalage de rapport de mesure pour éviter le ping-pong entre des cellules d'évolution à long terme en mode non autonome
WO2021237547A1 (fr) Demande d'attachement pour désactiver une nouvelle radio avec des modules d'identité d'abonné doubles
WO2021138753A1 (fr) Techniques permettant d'indiquer une capacité de module d'identité multi-abonné d'un dispositif à un réseau
WO2021208051A1 (fr) Restauration de connectivité de données après une défaillance par libérations de connexion rrc dans un réseau non autonome
WO2021207917A1 (fr) Restauration de connectivité de données après défaillance par libérations de connexions de rrc en réseau non autonome
WO2021212452A1 (fr) Rétablissement de connectivité de données lors d'une élimination de support après un transfert intercellulaire
WO2021207918A1 (fr) Restauration de connectivité de données après un échec d'appel de données dans un réseau non autonome
WO2021212299A1 (fr) Service de données avec doubles modules d'identité d'abonné
US11924837B2 (en) Techniques for physical uplink control channel beam failure recovery reselection
WO2021212401A1 (fr) Rétablissement de connectivité de données
WO2021223202A1 (fr) Restauration de service de données avec des modules d'identité d'abonné doubles
WO2021226859A1 (fr) Restauration de connectivité de données après un problème d'accès aléatoire dans un réseau non autonome
WO2021203346A1 (fr) Connectivité de données de nouvelle radio à partir d'un réseau non autonome
WO2021237683A1 (fr) Résolution de défaillance de liaison radio due à une capacité d'équipement utilisateur
WO2021203339A1 (fr) Configuration de duplexage par répartition dans le temps flexible
WO2021208074A1 (fr) Service de données à deux modules d'informations d'abonné

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

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

Country of ref document: EP

Kind code of ref document: A1