WO2020243976A1 - Procédé et appareil pour un procédé destinés à améliorer l'expérience d'utilisateur pour des dispositifs à double connectivité - Google Patents

Procédé et appareil pour un procédé destinés à améliorer l'expérience d'utilisateur pour des dispositifs à double connectivité Download PDF

Info

Publication number
WO2020243976A1
WO2020243976A1 PCT/CN2019/090448 CN2019090448W WO2020243976A1 WO 2020243976 A1 WO2020243976 A1 WO 2020243976A1 CN 2019090448 W CN2019090448 W CN 2019090448W WO 2020243976 A1 WO2020243976 A1 WO 2020243976A1
Authority
WO
WIPO (PCT)
Prior art keywords
rat
reconfiguration
message
failures
connection associated
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/090448
Other languages
English (en)
Inventor
Kaikai YANG
Haojun WANG
Zhenqing CUI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2019/090448 priority Critical patent/WO2020243976A1/fr
Publication of WO2020243976A1 publication Critical patent/WO2020243976A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • 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
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer

Definitions

  • the present disclosure relates generally to communication systems, and more particularly, to methods and apparatus for improving user experience for devices capable of dual connectivity.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power) .
  • multiple-access technologies include Long Term Evolution (LTE) systems, code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
  • LTE Long Term Evolution
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • a wireless multiple-access communication system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, otherwise known as user equipment (UEs) .
  • UEs user equipment
  • a set of one or more base stations may define an eNodeB (eNB) .
  • eNB eNodeB
  • a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs) , edge nodes (ENs) , radio heads (RHs) , smart radio heads (SRHs) , transmission reception points (TRPs) , etc.
  • DUs distributed units
  • EUs edge units
  • ENs edge nodes
  • RHs radio heads
  • SSRHs smart radio heads
  • TRPs transmission reception points
  • CUs central units
  • CUs central units
  • CNs central nodes
  • ANCs access node controllers
  • a set of one or more distributed units, in communication with a central unit may define an access node (e.g., a new radio base station (NR BS) , a new radio node-B (NR NB) , a network node, 5G NB, eNB, Next Generation Node B (gNB) , etc. ) .
  • NR BS new radio base station
  • NR NB new radio node-B
  • gNB Next Generation Node B
  • a base station or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a UE to a base station or distributed unit) .
  • downlink channels e.g., for transmissions from a base station or to a UE
  • uplink channels e.g., for transmissions from a UE to a base station or distributed unit
  • NR new radio
  • 3GPP Third Generation Partnership Project
  • the method generally includes receiving a reconfiguration message to reconfigure resources used for a first connection associated with a first radio access technology (RAT) according to a first resource configuration, establishing a second connection associated with a second RAT, initiating a reconfiguration of the resources used for the first connection associated with the first RAT, detecting a number of failures of the reconfiguration of the resources used for the first connection associated with the first RAT, determining that the detected number of failures equals to or exceeds a threshold number of failures, and transmitting, based at least in part on the determination that the number of detected failures equals to or exceeds the threshold number of failures, a message to indicate a failure of the reconfiguration of the resources used for the first connection associated with the first RAT.
  • RAT radio access technology
  • Certain aspects provide a method for wireless communications (e.g., that may be performed by a network entity, such as a base station) .
  • the method generally includes transmitting a reconfiguration message to a user equipment (UE) for reconfiguring resources used for a connection associated with a first RAT according to a first resource configuration, wherein the reconfiguration message is transmitted to the UE via a network entity of a second RAT network, receiving, from the network entity of the second RAT network, a message indicating a failure of the UE to complete the reconfiguration, and avoiding transmitting another reconfiguration message to the UE for reconfiguring resources used for the connection associated with the first RAT according to the same first resource configuration, after receiving the failure indication message.
  • UE user equipment
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 is a block diagram conceptually illustrating an example telecommunications system, in which aspects of the present disclosure may be performed.
  • FIG. 2 is a block diagram illustrating an example logical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure.
  • FIG. 3 is a diagram illustrating an example physical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure.
  • FIG. 4 is a block diagram conceptually illustrating a design of an example BS and user equipment (UE) , in accordance with certain aspects of the present disclosure.
  • FIG. 5 is a diagram showing examples for implementing a communication protocol stack, in accordance with certain aspects of the present disclosure.
  • FIG. 6 is a call flow diagram illustrating an example of failure scenario that may be addressed in accordance with certain aspects of the present disclosure.
  • FIG. 7 illustrates example operations for wireless communications (e.g., by a UE) , in accordance with aspects of the present disclosure.
  • FIG. 8 illustrates example operations for wireless communications (e.g., by a network entity, such as a base station) , in accordance with aspects of the present disclosure.
  • FIG. 9 is a call flow diagram illustrating how certain aspects of the present disclosure may address an example failure scenario.
  • FIG. 10 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.
  • FIG. 11 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.
  • aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for new radio (NR) (new radio access technology or 5G technology) .
  • NR new radio access technology
  • 5G technology new radio access technology
  • NR may support various wireless communication services, such as Enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz) , massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) .
  • eMBB Enhanced mobile broadband
  • mmW millimeter wave
  • mMTC massive MTC
  • URLLC ultra-reliable low latency communications
  • These services may include latency and reliability requirements.
  • These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements.
  • TTI transmission time intervals
  • QoS quality of service
  • these services may co-exist in the same subframe.
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA) , cdma2000, etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • An OFDMA network may implement a radio technology such as NR (e.g.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • UMTS Universal Mobile Telecommunication System
  • NR is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF) .
  • 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA.
  • LTE refers generally to LTE, LTE-Advanced (LTE-A) , LTE in an unlicensed spectrum (LTE-whitespace) , etc.
  • LTE-A LTE-Advanced
  • LTE-whitespace LTE in an unlicensed spectrum
  • FIG. 1 illustrates an example wireless network 100, such as a new radio (NR) or 5G network, in which aspects of the present disclosure may be performed.
  • a UE 120 may monitor a number of network failure events (e.g., triggered by failure to support a specified resource configuration) network entity and send a reconfiguration-triggered failure message 150 to the network.
  • network failure events e.g., triggered by failure to support a specified resource configuration
  • a failure message may help break a “dead-loop” in which the UE repeatedly experiences a failure (which may negatively impact user experience) .
  • the wireless network 100 may include a number of BSs 110 and other network entities.
  • a BS may be a station that communicates with UEs.
  • Each BS 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a Node B and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used.
  • the term “cell” and eNB, Node B, 5G NB, AP, NR BS, NR BS, gNB, or TRP may be interchangeable.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station.
  • the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, or the like using any suitable transport network.
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies.
  • a RAT may also be referred to as a radio technology, an air interface, etc.
  • a frequency may also be referred to as a carrier, a frequency channel, etc.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG) , UEs for users in the home, etc. ) .
  • CSG Closed Subscriber Group
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a pico cell may be referred to as a pico BS.
  • a BS for a femto cell may be referred to as a femto BS or a home BS.
  • the BSs 110a, 110b and 110c may be macro BSs for the macro cells 102a, 102b and 102c, respectively.
  • the BS 110x may be a pico BS for a pico cell 102x.
  • the BSs 110y and 110z may be femto BS for the femto cells 102y and 102z, respectively.
  • a BS may support one or multiple (e.g., three) cells.
  • the wireless network 100 may also include relay stations.
  • a relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or a BS) .
  • a relay station may also be a UE that relays transmissions for other UEs.
  • a relay station 110r may communicate with the BS 110a and a UE 120r in order to facilitate communication between the BS 110a and the UE 120r.
  • a relay station may also be referred to as a relay BS, a relay, etc.
  • the wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100.
  • macro BS may have a high transmit power level (e.g., 20 Watts) whereas pico BS, femto BS, and relays may have a lower transmit power level (e.g., 1 Watt) .
  • the wireless network 100 may support synchronous or asynchronous operation.
  • the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time.
  • the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.
  • the techniques described herein may be used for both synchronous and asynchronous operation.
  • a network controller 130 may be coupled to a set of BSs and provide coordination and control for these BSs.
  • the network controller 130 may communicate with the BSs 110 via a backhaul.
  • the BSs 110 may also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile.
  • a UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE) , a cellular phone, a smart phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a healthcare device, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.
  • CPE Customer Premises Equipment
  • PDA personal digital assistant
  • an entertainment device e.g., a music device, a video device, a satellite radio, etc.
  • a vehicular component or sensor e.g., a smart meter/sensor, a robot, a drone, industrial manufacturing equipment, a positioning device (e.g., GPS, Beidou, terrestrial) , or any other suitable device that is configured to communicate via a wireless or wired medium.
  • a positioning device e.g., GPS, Beidou, terrestrial
  • Some UEs may be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices, which may include remote devices that may communicate with a base station, another remote device, or some other entity.
  • MTC machine-type communication
  • eMTC evolved MTC
  • Machine type communications may refer to communication involving at least one remote device on at least one end of the communication and may include forms of data communication which involve one or more entities that do not necessarily need human interaction.
  • MTC UEs may include UEs that are capable of MTC communications with MTC servers and/or other MTC devices through Public Land Mobile Networks (PLMN) , for example.
  • PLMN Public Land Mobile Networks
  • MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, cameras, location tags, etc., that may communicate with a BS, another device (e.g., remote device) , or some other entity.
  • a wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
  • MTC UEs may be implemented as Internet-of-Things (IoT) devices, e.g., narrowband IoT (NB-IoT) devices.
  • IoT Internet-of-Things
  • NB-IoT narrowband IoT
  • a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink.
  • a dashed line with double arrows indicates interfering transmissions between a UE and a BS.
  • Certain wireless networks utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink.
  • OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc.
  • K orthogonal subcarriers
  • Each subcarrier may be modulated with data.
  • modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM.
  • the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth.
  • the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a ‘resource block’ ) may be 12 subcarriers (or 180 kHz) . Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz) , respectively.
  • the system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (e.g., 6 resource blocks) , and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.
  • NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using time division duplex (TDD) .
  • TDD time division duplex
  • a single component carrier bandwidth of 100 MHz may be supported.
  • NR resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration.
  • Each radio frame may consist of 50 subframes with a length (period) of 10 ms. Consequently, each subframe may have a length of 0.2 ms.
  • subframes may have a length (duration) of 1ms and each subframe may be further divided into two slots of . 5ms each (e.g., with each slot containing 6 or 7 OFDM symbols depending on cyclic prefix (CP) length.
  • a slot may be further divided into mini-slots, each mini-slot having a smaller duration (e.g., containing fewer symbols than a full slot) .
  • Each subframe may indicate a link direction (e.g., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched.
  • Each subframe may include DL/UL data as well as DL/UL control data. Beamforming may be supported and beam direction may be dynamically configured.
  • MIMO transmissions with precoding may also be supported.
  • MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE.
  • Multi-layer transmissions with up to 2 streams per UE may be supported.
  • Aggregation of multiple cells may be supported with up to 8 serving cells.
  • NR may support a different air interface, other than an OFDM-based.
  • NR networks may include entities such CUs and/or DUs.
  • a scheduling entity e.g., a base station
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity.
  • Base stations are not the only entities that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs) .
  • the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication.
  • a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network.
  • P2P peer-to-peer
  • UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
  • a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.
  • a RAN may include a CU and DUs.
  • a NR BS e.g., eNB, 5G Node B, Node B, transmission reception point (TRP) , access point (AP)
  • NR cells can be configured as access cell (ACells) or data only cells (DCells) .
  • the RAN e.g., a central unit or distributed unit
  • DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals-in some case cases DCells may transmit SS.
  • NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.
  • FIG. 2 illustrates an example logical architecture of a distributed radio access network (RAN) 200, which may be implemented in the wireless communication system illustrated in FIG. 1.
  • a 5G access node 206 may include an access node controller (ANC) 202.
  • the ANC may be a central unit (CU) of the distributed RAN 200.
  • the backhaul interface to the next generation core network (NG-CN) 204 may terminate at the ANC.
  • the backhaul interface to neighboring next generation access nodes (NG-ANs) may terminate at the ANC.
  • the ANC may include one or more TRPs 208 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, gNBs, or some other term) .
  • TRPs 208 which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, gNBs, or some other term.
  • TRP may be used interchange
  • the TRPs 208 may be a DU.
  • the TRPs may be connected to one ANC (ANC 202) or more than one ANC (not illustrated) .
  • ANC ANC
  • RaaS radio as a service
  • a TRP may include one or more antenna ports.
  • the TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
  • the local architecture 200 may be used to illustrate fronthaul definition.
  • the architecture may be defined that support fronthauling solutions across different deployment types.
  • the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter) .
  • the architecture may share features and/or components with LTE.
  • the next generation AN (NG-AN) 210 may support dual connectivity with NR.
  • the NG-AN may share a common fronthaul for LTE and NR.
  • the architecture may enable cooperation between and among TRPs 208. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 202. According to aspects, no inter-TRP interface may be needed/present.
  • a dynamic configuration of split logical functions may be present within the architecture 200.
  • the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU or CU (e.g., TRP or ANC, respectively) .
  • a BS may include a central unit (CU) (e.g., ANC 202) and/or one or more distributed units (e.g., one or more TRPs 208) .
  • CU central unit
  • distributed units e.g., one or more TRPs 208 .
  • FIG. 3 illustrates an example physical architecture of a distributed RAN 300, according to aspects of the present disclosure.
  • a centralized core network unit (C-CU) 302 may host core network functions.
  • the C-CU may be centrally deployed.
  • C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS) ) , in an effort to handle peak capacity.
  • AWS advanced wireless services
  • a centralized RAN unit (C-RU) 304 may host one or more ANC functions.
  • the C-RU may host core network functions locally.
  • the C-RU may have distributed deployment.
  • the C-RU may be closer to the network edge.
  • a DU 306 may host one or more TRPs (edge node (EN) , an edge unit (EU) , a radio head (RH) , a smart radio head (SRH) , or the like) .
  • the DU may be located at edges of the network with radio frequency (RF) functionality.
  • RF radio frequency
  • FIG. 4 illustrates example components of the BS 110 and UE 120 illustrated in FIG. 1, which may be used to implement aspects of the present disclosure.
  • the BS may include a TRP.
  • One or more components of the BS 110 and UE 120 may be used to practice aspects of the present disclosure.
  • antennas 452, processors 466, 458, 464, and/or controller/processor 480 (used to implement transceiver or separate receiver and transmitter chain functions) of the UE 120 and/or antennas 434, processors 430, 420, 438, and/or controller/processor 440 of the BS 110 may be used to perform the operations described herein and illustrated with reference to FIGs. 7 and 8.
  • FIG. 4 shows a block diagram of a design of a BS 110 and a UE 120, which may be one of the BSs and one of the UEs in FIG. 1.
  • the base station 110 may be the macro BS 110c in FIG. 1, and the UE 120 may be the UE 120y.
  • the base station 110 may also be a base station of some other type.
  • the base station 110 may be equipped with antennas 434a through 434t, and the UE 120 may be equipped with antennas 452a through 452r.
  • a transmit processor 420 may receive data from a data source 412 and control information from a controller/processor 440.
  • the control information may be for the Physical Broadcast Channel (PBCH) , Physical Control Format Indicator Channel (PCFICH) , Physical Hybrid ARQ Indicator Channel (PHICH) , Physical Downlink Control Channel (PDCCH) , etc.
  • the data may be for the Physical Downlink Shared Channel (PDSCH) , etc.
  • the processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively.
  • the processor 420 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal.
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 432a through 432t.
  • the TX MIMO processor 430 may perform certain aspects described herein for RS multiplexing.
  • Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc. ) to obtain an output sample stream.
  • Each modulator 432 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • Downlink signals from modulators 432a through 432t may be transmitted via the antennas 434a through 434t, respectively.
  • the antennas 452a through 452r may receive the downlink signals from the base station 110 and may provide received signals to the demodulators (DEMODs) 454a through 454r, respectively.
  • Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each demodulator 454 may further process the input samples (e.g., for OFDM, etc. ) to obtain received symbols.
  • a MIMO detector 456 may obtain received symbols from all the demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. For example, MIMO detector 456 may provide detected RS transmitted using techniques described herein.
  • a receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller/processor 480.
  • CoMP aspects can include providing the antennas, as well as some Tx/Rx functionalities, such that they reside in distributed units. For example, some Tx/Rx processings can be done in the central unit, while other processing can be done at the distributed units. For example, in accordance with one or more aspects as shown in the diagram, the BS mod/demod 432 may be in the distributed units.
  • a transmit processor 464 may receive and process data (e.g., for the Physical Uplink Shared Channel (PUSCH) ) from a data source 462 and control information (e.g., for the Physical Uplink Control Channel (PUCCH) from the controller/processor 480.
  • the transmit processor 464 may also generate reference symbols for a reference signal.
  • the symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators 454a through 454r (e.g., for SC-FDM, etc. ) , and transmitted to the base station 110.
  • the uplink signals from the UE 120 may be received by the antennas 434, processed by the modulators 432, detected by a MIMO detector 436 if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by the UE 120.
  • the receive processor 438 may provide the decoded data to a data sink 439 and the decoded control information to the controller/processor 440.
  • the controllers/processors 440 and 480 may direct the operation at the base station 110 and the UE 120, respectively.
  • the processor 440 and/or other processors and modules at the base station 110 may perform or direct the processes for the techniques described herein.
  • the processor 480 and/or other processors and modules at the UE 120 may also perform or direct processes for the techniques described herein.
  • the memories 442 and 482 may store data and program codes for the BS 110 and the UE 120, respectively.
  • a scheduler 444 may schedule UEs for data transmission on the downlink and/or uplink.
  • FIG. 5 illustrates a diagram 500 showing examples for implementing a communications protocol stack, according to aspects of the present disclosure.
  • the illustrated communications protocol stacks may be implemented by devices operating in a in a 5G system (e.g., a system that supports uplink-based mobility) .
  • Diagram 500 illustrates a communications protocol stack including a Radio Resource Control (RRC) layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a Radio Link Control (RLC) layer 520, a Medium Access Control (MAC) layer 525, and a Physical (PHY) layer 530.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical
  • the layers of a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non- collocated devices connected by a communications link, or various combinations thereof.
  • Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE.
  • a network access device e.g., ANs, CUs, and/or DUs
  • a first option 505-a shows a split implementation of a protocol stack, in which implementation of the protocol stack is split between a centralized network access device (e.g., an ANC 202 in FIG. 2) and distributed network access device (e.g., DU 208 in FIG. 2) .
  • a centralized network access device e.g., an ANC 202 in FIG. 2
  • distributed network access device e.g., DU 208 in FIG. 2
  • an RRC layer 510 and a PDCP layer 515 may be implemented by the central unit
  • an RLC layer 520, a MAC layer 525, and a PHY layer 530 may be implemented by the DU.
  • the CU and the DU may be collocated or non-collocated.
  • the first option 505-a may be useful in a macro cell, micro cell, or pico cell deployment.
  • a second option 505-b shows a unified implementation of a protocol stack, in which the protocol stack is implemented in a single network access device (e.g., access node (AN) , new radio base station (NR BS) , a new radio Node-B (NR NB) , a network node (NN) , or the like. ) .
  • the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 may each be implemented by the AN.
  • the second option 505-b may be useful in a femto cell deployment.
  • a UE may implement an entire protocol stack (e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530) .
  • an entire protocol stack e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530.
  • a UE may be configured support dual connectivity, for 4G and NR/5G for the illustrated examples.
  • This type of dual connectivity (DC) is generally referred to as E-UTRA/NR DC (ENDC) .
  • ENDC E-UTRA/NR DC
  • a UE should support simultaneous connection to 4G and 5GNR together.
  • a UE with ongoing packet-switched (PS) services on an LTE network may receive an RRC connection reconfiguration (RRCConnectionReconfiguration) from the NR network to configure NR resources.
  • RRCConnectionReconfiguration RRC connection reconfiguration
  • the UE may not be able to successfully perform the reconfiguration and further attempts at this procedure may lead to repeat radio link failures (RLFs) and repeated connection reestablishment (RRCConnectionReestablishment) procedure attempts. This will result in suspension of the LTE side data service and result in a greatly diminished user experience.
  • RLFs radio link failures
  • RRCConnectionReestablishment repeated connection reestablishment
  • FIG. 6 is a call flow diagram illustrating an example of the failure scenario described above.
  • a UE may be participating in ongoing PS service via the LTE RAT.
  • the NR network via the gNB
  • the NR network may request a resource modification, relayed by the LTE network (via the eNB) via an RRCConnectionReconfiguration to (re-) configure the NR resources.
  • this reconfiguration could fail for many reasons (e.g., because of an invalid configuration or some feature not supported by the UE) .
  • the UE side would trigger a radio link failure (RLF) and the UE begins to perform a connection reestablishment (RRCConnectionReestablishment) procedure.
  • RLF radio link failure
  • RRCConnectionReestablishment connection reestablishment
  • the UE may send an RRCConnectionReestablishmentRequest message to the network side.
  • the network side may accept the reestablishment request and send an RRCConnectionReestablishment message to the UE, at 625.
  • the UE sends a connection reestablishment complete (RRCConnectionReestablishmentComplete) message to the network.
  • RRCConnectionReestablishmentComplete connection reestablishment complete
  • steps 615 through 630 may be repeated (again and again) , which may lead, for example, to a disruption of the PS service (e.g., an end to a VoLTE call, termination of a streamed video, or the like) even if the LTE side radio condition is sufficiently good to support the PS service.
  • This scenario may continue to repeat, in a condition referred to as a “dead loop. ”
  • This section also specifies that if security has not been activated, the UE is to perform the actions upon leaving RRC_CONNECTED (as specified in Section 5.3.12 of TS 36.331) , with the release cause “other” or, if security has not been activated, the UE is to initiate the connection re-establishment procedure (as specified in Section 5.3.7 of TS 36.331) , upon which the connection reconfiguration procedure ends.
  • the UE may also be configured to apply the above-described failure handling also in case the RRCConnectionReconfiguration message causes a protocol error for which the generic error handling (as defined in Section 5.7 of TS 36.331) specifies that the UE is to ignore the message.
  • the generic error handling (as defined in Section 5.7 of TS 36.331) specifies that the UE is to ignore the message.
  • the UE is not to apply any part of the configuration (i.e. there is no partial success/failure) .
  • This compliance may also cover the NR configuration carried within the reconfiguration message (e.g., via octet strings e.g. field nr-SecondaryCellGroupConfig) , such that the failure behavior described above also applies in case the UE cannot comply with the NR configuration or with the combination of (parts of) the LTE and NR configurations.
  • 3GPP TS 38.331, Section 5.3.5.8.2 addresses a UE’s inability to comply with an RRCReconfiguration message.
  • this section specifies that, if the UE is operating in EN-DC mode and is unable to comply with (part of) the configuration included in the RRCReconfiguration message the UE received (over signaling radio bearer 3-SRB3) , the UE is to continue using the configuration used prior to the reception of RRCReconfiguration message, initiate the secondary cell group (SCG) failure information procedure (as specified in subclause 5.7.3) to report an SCG reconfiguration error, upon which the connection reconfiguration procedure ends.
  • SCG secondary cell group
  • the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over the master cell group (MCG) SRB 1, the UE is to continue using the configuration used prior to the reception of RRCReconfiguration message and initiate the connection re-establishment procedure (as specified in TS 36.331 Section 10, 5.3.7) , upon which the connection reconfiguration procedure ends.
  • MCG master cell group
  • the UE may monitor (e.g., via the RRC layer) , a count of the number of times the reconfiguration failure described above occurs. If the number of failures exceeds a threshold value (e.g., within a certain time period) , the UE may trigger a failure procedure.
  • a threshold value e.g., within a certain time period
  • FIG. 7 illustrates example operations 700 for wireless communications, in accordance with aspects of the present disclosure.
  • operations 700 may be performed by a UE operation in ENDC mode, such as the UE shown in FIG. 9, to avoid or break the dead loop scenario described above.
  • Operations 700 begin, at 702, by receiving a reconfiguration message to reconfigure resources used for a first connection associated with a first radio access technology (RAT) according to a first resource configuration.
  • the UE establishes a second connection associated with a second RAT.
  • RAT radio access technology
  • an ENDC UE with LTE and NR connections may receive a reconfiguration message to reconfigure NR resources.
  • the UE initiates a reconfiguration of the resources used for the first connection associated with the first RAT.
  • the UE detects a number of failures of the reconfiguration of the resources used for the first connection associated with the first RAT.
  • the UE determines that the detected number of failures equals to or exceeds a threshold number of failures.
  • the UE transmits, based at least in part on the determination that the number of detected failures equals to or exceeds the threshold number of failures, a message to indicate a failure of the reconfiguration of the resources used for the first connection associated with the first RAT.
  • the UE may send a failure message to the LTE eNB, to be forwarded to the NR gNB.
  • the failure message may include a failure type (e.g., unsupported configuration) that the NR gNB may use to determine it should avoid re-sending a reconfiguration message with the same (unsupported) configuration.
  • FIG. 8 illustrates example operations 800 for wireless communications that may be considered complementary to operations 700.
  • operations 800 may be performed by a network entity of a first RAT (e.g., an NR gNB or LTE eNB) in communication with an ENDC UE performing operations 700.
  • a network entity of a first RAT e.g., an NR gNB or LTE eNB
  • Operations 800 begin, at 802, by transmitting a reconfiguration message to a user equipment (UE) for reconfiguring resources used for a connection associated with a first RAT according to a first resource configuration, wherein the reconfiguration message is transmitted to the UE via a network entity of a second RAT network.
  • UE user equipment
  • an NR gNB may send a reconfiguration message to a UE, via an LTE eNB.
  • the network entity of the first RAT receives, from the network entity of the second RAT network, a message indicating a failure of the UE to complete the reconfiguration.
  • the network entity of the first RAT avoids transmitting another reconfiguration message to the UE for reconfiguring resources used for the connection associated with the first RAT according to the same first resource configuration, after receiving the failure indication message.
  • FIG. 9 is a call flow diagram illustrating how certain aspects of the present disclosure may address the dead loop scenario described above.
  • the UE may perform operations 700 of FIG. 7, while NR gNB performs operations 800 of FIG. 8.
  • the gNB may send a resource modification message 610 specifying a first configuration (Config #1) , relayed to the UE as a resource reconfiguration message 615.
  • Config #1 a first configuration
  • the reconfiguration may result in a failure, prompting steps 620-630 to reestablish the connection.
  • the UE may monitor the number of such failures, for example, by initiating a counter.
  • the counter may be incremented every time a failure is detected by the UE.
  • a timer may also be used.
  • the counter may be reset after a given time period, so a failure message is only triggered if the threshold number of failures is reached within the given time period.
  • the failure type may indicate the UE does not support Config #1.
  • the failure message may be part of a scgFailureInformationNR procedure with a failure type (e.g., scg-reconfigFailure) to inform the gNB about the nature of the failure.
  • a format of the failure message may be defined in a standard.
  • the eNB may forward the failure message to the gNB, at 945 (e.g., via an X2 interface) .
  • the gNB may avoid sending a reconfiguration (resource modification) request to the UE for the same configuration (Config #1) .
  • the failure type may indicate some information to the gNB such that the gNB can modify the requested resource configuration accordingly, to avoid the endless dead loop scenario.
  • the gNB sends a resource modification request specifying a different resource configuration (e.g., Config #2) .
  • a resource modification request may be forwarded to the UE via eNB, as a connection reconfiguration request (indicating a reconfiguration of NR resources according to Config #2) .
  • the UE may repeat the operations described above, while attempting to perform according to the new reconfiguration request.
  • the UE may either successfully reconfigure or detect a failure, re-initiate the failure counter, and continue to monitor/count the failures as described above.
  • a subsequent failure e.g., if the UE is not able to support Config #2
  • the dead loop shown in FIG. 6 is broken and at least the gNB can continue to try different configurations-or decide to stop attempting to reconfigure the UE.
  • Exactly how the UE sets the counter (and/or timer) and determines the particular threshold value that triggers sending the failure message may depend on the particular implementation. In some cases, the UE may decide the threshold value (e.g., based on a particular application or desired a user experience) or the UE may be configured by the network (or pre-configured according to a standard) .
  • FIG. 10 illustrates a wireless communications device 1000 (e.g., UE 120, such as the UE shown in FIG. 9) 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.
  • 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 wireless communications device 1000 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.
  • computer-readable medium/memory 1012 may store code for establishing 1014 (e.g., for establishing a second connection associated with a second RAT) , code for initiating 1016 (e.g., for initiating a reconfiguration of the resources used for the first connection associated with the first RAT) , code for detecting 1018 (e.g., for detecting a number of failures of the reconfiguration of the resources used for the first connection associated with the first RAT) , code for determining 1020 (e.g., for determining that the detected number of failures equals to or exceeds a threshold number of failures) , and/or code for transmitting/receiving 1022 (e.g., for receiving a reconfiguration message to reconfigure resources used for a first connection associated with a first RAT according to a first resource configuration and/or transmitting, based at least in part on the determination that the number of detected failures equals to or exceeds the threshold number of failures, a message to indicate a
  • the processor 1004 has circuitry configured to implement the code stored in the computer-readable medium/memory 1012.
  • the processor 1004 may include circuitry for establishing 1030 (e.g., for establishing a second connection associated with a second RAT) , circuitry for initiating 1032 (e.g., for initiating a reconfiguration of the resources used for the first connection associated with the first RAT) , circuitry for detecting 1034 (e.g., for detecting a number of failures of the reconfiguration of the resources used for the first connection associated with the first RAT) , circuitry for determining 1036 (e.g., for determining that the detected number of failures equals to or exceeds a threshold number of failures) , and/or circuitry for transmitting/receiving 1038 (e.g., for receiving a reconfiguration message to reconfigure resources used for a first connection associated with a first RAT according to a first resource configuration and/or transmitting, based at least in part on the determination that the number
  • FIG. 11 illustrates a wireless communications device 1100 (e.g., a base station 110 such as the eNB or gNB shown in FIG. 9) 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.
  • 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 wireless communications device 1100 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.
  • computer-readable medium/memory 1112 may store code for transmitting/receiving 1122 (e.g., for transmitting a reconfiguration message to a user equipment (UE) for reconfiguring resources used for a connection associated with a first RAT according to a first resource configuration, wherein the reconfiguration message is transmitted to the UE via a network entity of a second RAT network and/or receiving, from the network entity of the second RAT network, a message indicating a failure of the UE to complete the reconfiguration) , and/or code for avoiding 1124 (e.g., for avoiding transmitting another reconfiguration message to the UE for reconfiguring resources used for the connection associated with the first RAT according to the same first resource configuration, after receiving the failure indication message) .
  • code for transmitting/receiving 1122 e.g., for transmitting a reconfiguration message to a user equipment (UE) for reconfiguring resources used for a connection associated with a first RAT according to a first resource configuration, wherein the reconfiguration message is
  • the processor 1104 has circuitry configured to implement the code stored in the computer-readable medium/memory 1112.
  • the processor 1104 may include circuitry for transmitting/receiving 1138 (e.g., for for transmitting a reconfiguration message to a user equipment (UE) for reconfiguring resources used for a connection associated with a first RAT according to a first resource configuration, wherein the reconfiguration message is transmitted to the UE via a network entity of a second RAT network and/or receiving, from the network entity of the second RAT network, a message indicating a failure of the UE to complete the reconfiguration) , and/or circuitry for avoiding 1140 (e.g., for avoiding transmitting another reconfiguration message to the UE for reconfiguring resources used for the connection associated with the first RAT according to the same first resource configuration, after receiving the failure indication message) .
  • transmitting/receiving 1138 e.g., for for transmitting a reconfiguration message to a user equipment (UE) for reconfiguring resources used for a
  • the methods disclosed herein comprise one or more steps or actions for achieving the described method.
  • the method steps and/or actions may be interchanged with one another without departing from the scope of the claims.
  • the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
  • a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
  • the term “and/or, ” when used in a list of two or more items means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed.
  • the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.
  • determining encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
  • the term “some” refers to one or more.
  • the term “or” is intended to mean an inclusive “or” rather than an exclusive “or. ” That is, unless specified otherwise, or clear from the context, the phrase, for example, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, for example the phrase “X employs A or B”is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B.
  • the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
  • the means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor.
  • ASIC application specific integrated circuit
  • operations 700 and 800 of FIGs. 7 and 8 may be performed by various processors shown in FIG. 4.
  • those operations may have corresponding counterpart means-plus-function.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • PLD programmable logic device
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • an example hardware configuration may comprise a processing system in a wireless node.
  • the processing system may be implemented with a bus architecture.
  • the bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints.
  • the bus may link together various circuits including a processor, machine-readable media, and a bus interface.
  • the bus interface may be used to connect a network adapter, among other things, to the processing system via the bus.
  • the network adapter may be used to implement the signal processing functions of the PHY layer.
  • a user interface e.g., keypad, display, mouse, joystick, etc.
  • a user interface e.g., keypad, display, mouse, joystick, etc.
  • the bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further.
  • the processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.
  • the functions may be stored or transmitted over as one or more instructions or code on a computer readable medium.
  • Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • the processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media.
  • a computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
  • the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface.
  • the machine-readable media, or any portion thereof may be integrated into the processor, such as the case may be with cache and/or general register files.
  • machine-readable storage media may include, by way of example, RAM (Random Access Memory) , flash memory, phase change memory, ROM (Read Only Memory) , PROM (Programmable Read-Only Memory) , EPROM (Erasable Programmable Read-Only Memory) , EEPROM (Electrically Erasable Programmable Read-Only Memory) , registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
  • the machine-readable media may be embodied in a computer-program product.
  • a software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media.
  • the computer-readable media may comprise a number of software modules.
  • the software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions.
  • the software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices.
  • a software module may be loaded into RAM from a hard drive when a triggering event occurs.
  • the processor may load some of the instructions into cache to increase access speed.
  • One or more cache lines may then be loaded into a general register file for execution by the processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared (IR) , radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
  • computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media) .
  • the phrase computer readable medium does not refer to a transitory propagating signal.
  • computer-readable media may comprise transitory computer-readable media (e.g., a signal) . Combinations of the above should also be included within the scope of computer-readable media.
  • certain aspects may comprise a computer program product for performing the operations presented herein.
  • a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein.
  • instructions for performing the operations described herein and illustrated in the appended figures may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein.
  • modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable.
  • a user terminal and/or base station can be coupled to a server to facilitate the transfer of means for performing the methods described herein.
  • various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc. ) , such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device.
  • storage means e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.
  • CD compact disc
  • floppy disk etc.
  • any other suitable technique for providing the methods and techniques described herein to a device can be utilized.

Landscapes

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

Abstract

L'invention concerne des procédés et un appareil destinés à améliorer l'expérience d'utilisateur pour des dispositifs capables d'effectuer une double connectivité. Un procédé comprend : la réception d'un message de reconfiguration pour reconfigurer des ressources utilisées pour une première connexion associée à une première technologie d'accès radio (RAT) selon une première configuration de ressources ; l'établissement d'une deuxième connexion associée à une deuxième RAT ; l'initiation d'une reconfiguration des ressources ; la détection d'un nombre d'échecs de reconfiguration des ressources ; la détermination que le nombre détecté d'échecs est égal ou supérieur à un nombre seuil d'échecs ; et la transmission, sur la base au moins en partie de la détermination, d'un message pour indiquer un échec de reconfiguration des ressources.
PCT/CN2019/090448 2019-06-07 2019-06-07 Procédé et appareil pour un procédé destinés à améliorer l'expérience d'utilisateur pour des dispositifs à double connectivité Ceased WO2020243976A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/090448 WO2020243976A1 (fr) 2019-06-07 2019-06-07 Procédé et appareil pour un procédé destinés à améliorer l'expérience d'utilisateur pour des dispositifs à double connectivité

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/090448 WO2020243976A1 (fr) 2019-06-07 2019-06-07 Procédé et appareil pour un procédé destinés à améliorer l'expérience d'utilisateur pour des dispositifs à double connectivité

Publications (1)

Publication Number Publication Date
WO2020243976A1 true WO2020243976A1 (fr) 2020-12-10

Family

ID=73652737

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/090448 Ceased WO2020243976A1 (fr) 2019-06-07 2019-06-07 Procédé et appareil pour un procédé destinés à améliorer l'expérience d'utilisateur pour des dispositifs à double connectivité

Country Status (1)

Country Link
WO (1) WO2020243976A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160044565A1 (en) * 2013-04-15 2016-02-11 Lg Electronics Inc. Method and apparatus for establishing connection in wireless communication system
WO2017196095A2 (fr) * 2016-05-12 2017-11-16 주식회사 케이티 Procédé de configuration de double connectivité par un terminal, et appareil associé
CN108633018A (zh) * 2017-03-23 2018-10-09 华为技术有限公司 配置方法、装置及系统
CN108632918A (zh) * 2017-03-23 2018-10-09 展讯通信（上海）有限公司 基于双连接技术的主辅基站角色变换方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160044565A1 (en) * 2013-04-15 2016-02-11 Lg Electronics Inc. Method and apparatus for establishing connection in wireless communication system
WO2017196095A2 (fr) * 2016-05-12 2017-11-16 주식회사 케이티 Procédé de configuration de double connectivité par un terminal, et appareil associé
CN108633018A (zh) * 2017-03-23 2018-10-09 华为技术有限公司 配置方法、装置及系统
CN108632918A (zh) * 2017-03-23 2018-10-09 展讯通信（上海）有限公司 基于双连接技术的主辅基站角色变换方法

Similar Documents

Publication Publication Date Title
US20240205780A1 (en) Beam selection and radio link failure during beam recovery
US11838066B2 (en) Default radio link monitoring reference signal (RLM-RS) determination procedure in new radio (NR)
US11076331B2 (en) Inter-radio access technology (RAT), inter-band, or inter-carrier switching base on power consumption
US12004032B2 (en) Nested conditional mobility procedures
US11664960B2 (en) Full-duplex slot configuration
EP3603205B1 (fr) Fourniture fiable d'informations système
EP3619959B1 (fr) Contrôle d'accès unifié
US10750520B2 (en) Radio link control/packet data convergence protocol window advance with holes
WO2022216390A1 (fr) Comptage de répétitions de canal de commande de liaison montante physique (pucch) pendant un transfert intercellulaire à double pile de protocoles active (daps)
EP4038964A1 (fr) Configuration d'agrégation de porteuses (ca) pendant un transfert (ho) de pile de protocoles actifs doubles (daps)
WO2019104979A1 (fr) Appareil et procédés pour récupérer des pdu rlc manquants
WO2019000263A1 (fr) Appareil et procédés d'amélioration de performance d'appel mt lors d'une défaillance de rach pour une réponse de page
WO2021067135A1 (fr) Deuxième considération de conception de message pour procédure de canal d'accès aléatoire en deux étapes
WO2020243976A1 (fr) Procédé et appareil pour un procédé destinés à améliorer l'expérience d'utilisateur pour des dispositifs à double connectivité
WO2018205265A1 (fr) Continuité de la signalisation dans un réseau d'accès radio à architecture divisée
WO2022056902A1 (fr) Optimisation d'ue dans une procédure de repli eps
WO2018188013A1 (fr) Transfert sans perte à reconfiguration complète de commande de ressources radio (rrc)

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

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

Country of ref document: EP

Kind code of ref document: A1