WO2017111788A1 - Dispositifs et procédés de réduction de consommation de puissance de lwa et de prévention de rlf - Google Patents

Dispositifs et procédés de réduction de consommation de puissance de lwa et de prévention de rlf Download PDF

Info

Publication number
WO2017111788A1
WO2017111788A1 PCT/US2015/000287 US2015000287W WO2017111788A1 WO 2017111788 A1 WO2017111788 A1 WO 2017111788A1 US 2015000287 W US2015000287 W US 2015000287W WO 2017111788 A1 WO2017111788 A1 WO 2017111788A1
Authority
WO
WIPO (PCT)
Prior art keywords
enb
lte
transceiver
inactive state
configure
Prior art date
Application number
PCT/US2015/000287
Other languages
English (en)
Inventor
Nupur RASTOGI
Vishnusudhan Vishnu RAGHUPATHY
Original Assignee
Intel IP Corporation
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 Intel IP Corporation filed Critical Intel IP Corporation
Priority to PCT/US2015/000287 priority Critical patent/WO2017111788A1/fr
Publication of WO2017111788A1 publication Critical patent/WO2017111788A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • FIG. 2 illustrates components of a communication device in accordance with some embodiments.
  • FIG. 3 illustrates a block diagram of a communication device in accordance with some embodiments.
  • FIG. 6 illustrates a flow diagram of exit of a UE from an LTE
  • FIG. 7 illustrates a flow diagram of a UE in an LTE Inactive state leaving access point (AP) range in accordance with some embodiments.
  • the MME 122 may be similar in function to the control plane of legacy Serving GPRS Support Nodes (SGSN).
  • the MME 122 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the serving GW 124 may terminate the interface toward the RAN 101 , and route data packets between the RAN 101 and the core network 120.
  • the serving GW 124 may be a local mobility anchor point for inter-eNB handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the serving GW 124 and the MME 122 may be implemented in one physical node or separate physical nodes.
  • the PDN GW 126 may terminate a SGi interface toward the packet data network (PDN).
  • the PDN GW 126 may route data packets between the EPC 120 and the external PDN, and may perform policy enforcement and charging data collection.
  • the PDN GW 126 may also provide an anchor point for mobility devices with non-LTE access.
  • the external PDN can be any kind of IP network, as well as an IP Multimedia Subsystem (IMS) domain.
  • IMS IP Multimedia Subsystem
  • the PDN GW 126 and the serving GW 124 may be implemented in a single physical node or separate physical nodes.
  • the eNBs 104 may terminate the air interface protocol and may be the first point of contact for a UE 102.
  • an eNB 104 may fulfill various logical functions for the RAN 101 including, but not limited to, RNC (radio network controller functions) such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller functions
  • UEs 102 may be configured to communicate orthogonal frequency division multiplexed (OFDM) communication signals with an eNB 104 over a multicarrier communication channel in accordance with an OFDMA communication technique.
  • the OFDM signals may comprise a plurality of orthogonal subcarriers.
  • LP cells 104b may be typically used to extend coverage to indoor areas where outdoor signals do not reach well, or to add network capacity in areas with dense usage.
  • the cells of different sizes may operate on the same frequency band, or may operate on different frequency bands with each cell operating in a different frequency band or only cells of different sizes operating on different frequency bands.
  • a picocell may be a wireless communication system typically covering a small area, such as in-building (offices, shopping malls, train stations, etc.), or more recently in-aircraft.
  • a picocell eNB may generally connect through the X2 link to another eNB such as a macro eNB through its base station controller (BSC) functionality.
  • BSC base station controller
  • LP eNB may be implemented with a picocell eNB since it may be coupled to a macro eNB 104a via an X2 interface.
  • Picocell eNBs or other LP eNBs LP eNB 104b may incorporate some or all functionality of a macro eNB LP eNB 104a. In some cases, this may be referred to as an access point base station or enterprise femtocell.
  • the UE 102 may communicate with an access point (AP) 104c.
  • the AP 104c may use only the unlicensed spectrum (e.g., WiFi bands) to communicate with the UE 102.
  • the AP 104c may communicate with the macro eNB 104A (or LP eNB 104B) through an Xw interface.
  • the AP 104c may communicate with the UE 102 independent of communication between the UE 102 and the macro eNB
  • the AP 104c may be controlled by the macro eNB 104A and use LWA, as described in more detail below.
  • Communication over an LTE network may be split up into 10ms frames, each of which may contain ten 1 ms subframes. Each subframe of the frame, in turn, may contain two slots of 0.5ms. Each subframe may be used for uplink (UL) communications from the UE to the eNB or downlink (DL) communications from the eNB to the UE. In one embodiment, the eNB may allocate a greater number of DL communications than UL communications in a particular frame. The eNB may schedule transmissions over a variety of frequency bands (fi and f2). The allocation of resources in subframes used in one frequency band and may differ from those in another frequency band. Each slot of the subframe may contain 6-7 OFDM symbols, depending on the system used.
  • the subframe may contain 1 2 subcarriers.
  • a downlink resource grid may be used for downlink transmissions from an eNB to a U E, while an uplink resource grid may be used for uplink transmissions from a UE to an eNB or from a UE to another UE.
  • the resource grid may be a time- frequency grid, which is the physical resource in the downlink in each slot. The smallest time-frequency unit in a resource grid may be denoted as a resource element (RE).
  • Each column and each row of the resource grid may correspond to one OFDM symbol and one OFDM subcarrier, respectively.
  • the resource grid may contain resource blocks (RBs) that describe the mapping of physical channels to resource elements and physical RBs (PRBs).
  • FIG. 2 illustrates components of a UE in accordance with some embodiments. At least some of the components shown may be used in an eNB or MME, for example, such as the UE 102 or eNB 104 shown in FIG. 1.
  • the UE 200 and other components may be configured to use the synchronization signals as described herein.
  • the UE 200 may be one of the UEs 102 shown in FIG. 1 and may be a stationary, non-mobile device or may be a mobile device. In some
  • the UE 102 may use an LTE discontinuous reception (DRX) mode to extend battery life.
  • DRX discontinuous reception
  • the UE 102 may terminate monitoring the physical downlink control channel (PDCCH) for a predetermined amount of time when in DRX mode.
  • the UE 102 may use different types of DRX modes, idle DRX mode (also called paging DRX), in which the UE 102 is in an idle state and does not have a Radio Resource Control (RRC) connection with the eNB 104, and active DRX mode, in which the UE 102 is in an RRC connected state.
  • Idle DRX mode may be used by the UE 102 primarily to monitor the data and broadcast channels.
  • the UE 102 in idle DRX mode may enter the RRC connected state from the idle state prior to monitoring the data channel. Active DRX mode may also permit power savings without the UE 102 entering the idle state, leading to a latency increase as the RRC connection may already be established. This may be beneficial for applications that do not use real-time data transfer, such as web browsing and instant messaging, in which the UE 102 may avoid continuous monitoring of the data connection and associated processing.
  • the eNB 104 may broadcast or transmit a DRX configuration to the UE 102 through the RRC connection, during initial setup or reconfiguration of the UE 102.
  • the DRX configuration may indicate which DRX modes are to be used, as well as various timers associated with the DRX mode(s). These timers may include on-duration, inactivity-timer, active-time, Hybrid Automatic Repeat Request (HARQ) round ' trip (RTT), drx-retransmissionTimer, and DRX Cycle Length.
  • HARQ Hybrid Automatic Repeat Request
  • the on duration timer may indicate the period of time (i.e., number of subframes) for the UE 102 to keep awake (i.e., prior to reentering DRX mode) after waking up from the DRX mode.
  • the UE 102 may search for a PDCCH during this period.
  • the HARQ RTT timer may indicate the minimum interval time that retransmission of data from the eNB 104 is expected to arrive.
  • the retransmission timer may indicate the maximum time period (and thus PDCCH subframes for the UE 102 to monitor) in which retransmission of data from the eNB 104 is expected.
  • the active timer may indicate the total time for the UE 102 to keep awake after waking up. During this time period, the UE 102 may monitor the PDCCH, including all states causing the UE 102 to be active (e.g., the on- duration begins, the UE 102 receives the PDCCH, or monitors a retransmission).
  • the active timer may include the On Duration Timer, the Inactivity Timer, the DRX Retransmission Timer and the media access control (MAC) Layer Contention Resolution Timer, as well as any other time period that the UE 102 determines (e.g., via control signaling) it is to stay active for communication with the eNB 104.
  • the DRX cycle length may indicate a period of time between succeeding DRX cycles.
  • the UE 102 may start the on duration timer as well as starting to monitor the PDCCH in a specific subframe corresponding to a specific system frame number (SFN) provided in the DRX configuration to acquire a paging- radio network temporary identifier (P-RNTI).
  • SFN system frame number
  • P-RNTI paging- radio network temporary identifier
  • the UE 102 may thus exit the DRX mode to determine whether it has been paged by the eNB 104.
  • Paging may occur when the network has data to be transmitted to the UE 102, to update system information or to provide an Earthquake and Tsunami Warning System (ETWS) indication to the UE 102.
  • EWS Earthquake and Tsunami Warning System
  • the MME 122 may initiate the paging sequence by transmitting an S I AP paging message to all eNB 104s within the tracking area in which the UE 102 is registered. The MME 122 may then start the paging timer T3413.
  • the eNB 104 may receive the S 1 AP paging message from the MME 122 and construct an RRC paging message for the UE 102 (along with possibly other UE 102s to be paged).
  • the UE 102 may check for paging in a paging occasion once every DRX cycle, as above searching for its P-RNTI within the PDCCH of subframe belong to paging occasion.
  • the application or processing circuitry 202 may include one or more application processors.
  • the application circuitry 202 may include circuitry such as, but not limited to, one or more single-core or multi- core processors.
  • the processor(s) may include any combination of general- purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory /storage to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 204 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206.
  • Baseband processing circuity 204 may interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 206.
  • modulation/demodulation circuitry of the baseband circuitry 204 may include FFT, precoding, and/or constellation mapping/demapping functionality.
  • encoding/decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 204 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements.
  • a central processing unit (CPU) 204e of the baseband circuitry 204 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 204f.
  • the audio DSP(s) 204f may be include elements for
  • compression/decompression and echo cancellation may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 204 and the application circuitry 202 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 204 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 204 may support communication with an evolved universal terrestrial radio access network (E- UTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • E- UTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi- mode baseband circuitry.
  • the device can be configured to operate in accordance with communication standards or other protocols or standards, including Institute of Electrical and Electronic Engineers (IEEE)
  • WiMax IEEE 802.1 1 wireless technology
  • WiFi IEEE 802.1 1 ad
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GERAN GSM EDGE radio access network
  • UMTS universal mobile telecommunications system
  • UTRAN UMTS terrestrial radio access network
  • RF circuitry 206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 206 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 206 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204.
  • RF circuitry 206 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the FEM circuitry 208 for transmission.
  • the RF circuitry 206 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 206 may include mixer circuitry 206a, amplifier circuitry 206b and filter circuitry 206c.
  • the transmit signal path of the RF circuitry 206 may include filter circuitry 206c and mixer circuitry 206a.
  • RF circuitry 206 may also include synthesizer circuitry 206d for synthesizing a frequency for use by the mixer circuitry 206a of the receive signal path and the transmit signal path.
  • the mixer circuitry 206a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206d.
  • the amplifier circuitry 206b may be configured to amplify the down-converted signals and the filter circuitry 206c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 204 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 206a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 206a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206d to generate RF output signals for the FEM circuitry 208.
  • the baseband signals may be provided by the baseband circuitry 204 and may be filtered by filter circuitry 206c.
  • the filter circuitry 206c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively.
  • the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 204 may include a digital baseband interface to communicate with the RF circuitry 206.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • the synthesizer circuitry 206d may be a fractional-N synthesizer or a fractional N/N+ 1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 206d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 206d may be configured to synthesize an output frequency for use by the mixer circuitry 206a of the RF circuitry 206 based on a frequency input and a divider control input.
  • the synthesizer circuitry 206d may be a fractional N/N+ l synthesizer.
  • Synthesizer circuitry 206d of the RF circuitry 206 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+ l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • FEM circuitry 208 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals and provide the amplified versions of the received signals to the KF circuitry 206 for further processing.
  • FEM circuitry 208 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 210.
  • the FEM circuitry 208 may include a
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 206).
  • the transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 210).
  • PA power amplifier
  • the UE 200 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface as described in more detail below.
  • the UE 200 described herein may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • a laptop or portable computer with wireless communication capability such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical
  • the UE 200 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system.
  • the UE 200 may include one or more of a keyboard, a keypad, a touchpad, a display, a sensor, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, one or more antennas, a graphics processor, an application processor, a speaker, a microphone, and other I/O components.
  • the display may be an LCD or LED screen including a touch screen.
  • the sensor may include a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may communicate with components ot a positioning network, e.g., a global positioning system (GPS) satellite.
  • GPS global positioning system
  • Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein.
  • a computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer).
  • a computer-readable storage device may include readonly memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
  • Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
  • FIG. 3 is a block diagram of a communication device in accordance with some embodiments.
  • the device may be a UE or eNB, for example, such as the UE 102 or eNB 104 shown in FIG. 1 that may be configured to track the UE as described herein.
  • the physical layer circuitry 302 may perform various encoding and decoding functions that may include formation of baseband signals for transmission and decoding of received signals.
  • the communication device 300 may also include medium access control layer (MAC) circuitry 304 for controlling access to the wireless medium.
  • MAC medium access control layer
  • the communication device 300 may also include processing circuitry 306, such as one or more single-core or multi-core processors, and memory 308 arranged to perform the operations described herein.
  • the physical layer circuitry 302, MAC circuitry 304 and processing circuitry 306 may handle various radio control functions that enable communication with one or more radio networks compatible with one or more radio technologies and, for example, may contain an LTE stack.
  • the radio control functions may include signal modulation, encoding, decoding, radio frequency shifting, etc.
  • communication may be enabled with one or more of a WMAN, a WLAN, and a WPAN.
  • the communication device 300 can be configured to operate in accordance with 3GPP standards or other protocols or standards, including WiMax, WiFi, WiGig, GSM, EDGE, GERAN, UMTS, UTRAN, or other 3G, 3G, 4G, 5G, etc.
  • the transceiver circuitry 3 12 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range.
  • RF Radio Frequency
  • the antennas 301 may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals.
  • the antennas 301 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • the communication device 300 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including DSPs, and/or other hardware elements. For example, some elements may comprise one or more
  • FIG. 4 illustrates another block diagram of a communication device in accordance with some embodiments.
  • the communication device 400 may operate as a standalone device or may be connected (e.g., networked) to other communication devices.
  • the communication device 400 may operate in the capacity of a server communication device, a client communication device, or both in server- client network environments.
  • the communication device 400 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • modules may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client or server computer system
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a communication device readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • the communication device 400 may further include a display unit 410, an alphanumeric input device 412 (e.g., a keyboard), and a user interface (UI) navigation device 414 (e.g., a mouse).
  • the display unit 410, input device 412 and UI navigation device 414 may be a touch screen display.
  • the communication device 400 may additionally include a storage device (e.g., drive unit) 416, a signal generation device 418 (e.g., a speaker), a network interface device 420, and one or more sensors 421 , such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • GPS global positioning system
  • the communication device 400 may include an output controller 428, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 416 may include a communication device readable medium 422 on which is stored one or more sets of data structures or instructions 424 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 424 may also reside, completely or at least partially, within the main memory 404, within static memory 406, or within the hardware processor 402 during execution thereof by the communication device 400.
  • one or any combination of the hardware processor 402, the main memory 404, the static memory 406, or the storage device 416 may constitute communication device readable media.
  • the term "communication device readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 400 and that cause the communication device 400 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting communication device readable medium examples may include solid-state memories, and optical and magnetic media.
  • Specific examples of communication device readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks;
  • communication device readable media may include non-transitory communication device readable media.
  • communication device readable media may include communication device readable media that is not a transitory propagating signal.
  • 1 he instructions 4 4 may iurther be transmitted or received over a communications network 426 using a transmission medium via the network interface device 420 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • the network interface device 420 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 426.
  • the network interface device 420 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) techniques.
  • SIMO single-input multiple-output
  • MIMO multiple-input single-output
  • MISO multiple-input single-output
  • the network interface device 420 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 400, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.
  • a WLAN access point may communicate data to the UE.
  • another eNB such as a macro or local eNB, may act as an intermediary, providing data from the core network to the AP or from the AP to the core network via the WLAN Termination (WT).
  • WT WLAN Termination
  • the eNB may control the AP, scheduling at least some packets to be sent to the UE to the AP, thereby providing LTE/WLAN Aggregation (LWA) capabilities according to 3GPP RAN2 and/or 3GPP RAN3 working group (WG) technical specifications (RAN2: TS 36.300, TS 36.331 ; RAN3 : TS 36.461 , 36.462, 36.463, 36.464 and 36.465).
  • LWA LTE/WLAN Aggregation
  • WG 3GPP RAN3 working group
  • a UE in RRC CONNECTED mode is configured by the eNB to utilize radio resources of LTE and WLAN.
  • the eNB and the AP may be integrated into the same device. In other non-collocated embodiments, the eNB and the AP may be connected via the WT using an Xw interface.
  • LWA may be provided based on an architecture with aggregation below Packet Data Convergence Protocol (PDCP) and LWA split and switched bearer configuration and optionally a General Packet Radio Service (GPRS) Tunneling Protocol (GTP)-User (GTP-U) tunnel between the eNB and the WT.
  • PDCP Packet Data Convergence Protocol
  • GTP-U General Packet Radio Service Tunneling Protocol
  • the GTP-U tunnel may be employed in the user plane to carry LTE user data traffic between the tunnel endpoints.
  • the WT may be located in either an AP, an Admission Control (AC) or deployed as a standalone network node.
  • AC Admission Control
  • the UE may, as shown in FIGS. 2-4, have one or more transceivers configured to communicate with the eNB and the AP. In some embodiments, the UE may have separate transceivers to communicate with the eNB and the AP.
  • Machine Type Communications (MTC) UEs may pose a particular challenges due to small battery and power availability, as well as that MTC UEs may be designed to operate for years in, at best, difficult to reach locations.
  • MTC UEs may include, for example, sensors (e.g., sensing environmental conditions) or microcontrollers in appliances or vending machines and provide a variety of services, such as smart utility metering, intelligent tracking in supply chain, fleet management and theft tracking.
  • the eNB may control transmission of data to the AP for transmission over the WLAN to the UE, in some embodiments, the proportion and/or type of data sent from the eNB to the AP may be mobility and/or location-based. For example, when the UE is stationery or has a low mobility compared to the AP range, and is connected the AP (as well as the eNB) using LWA, the eNB may decide to transmit all services and data over the WiFi link. Thus, the eNB may transmit all of the data to the AP. Using WiFi when possible may also be desirable to the end-user due to being cost effective.
  • a UE may thus desire use the LTE connection only when the UE moves out of the WiFi coverage.
  • the LTE system may still expect the UE to respond to certain signals as the UE is connected with the eNB.
  • the LTE system may transmit reference signals to the UE, which is expected to provide measurements for channel estimation and handover determination, among others.
  • the UE may also still be expected to respond to paging messages for the UE, and mobile-originated calls may continue to use LTE Radio resource management (RRM) of the LTE system.
  • RRM LTE Radio resource management
  • the UE may exit an LTE Active state and enter an LTE Inactive state in which the LTE stack is switched completely or partially off when the UE is only being served data by the AP through the WiFi connection.
  • the LTE stack in some embodiments, as discussed in more detail below, may turn on for isolated periods of time for limited reasons.
  • the UE may still remain in the RRC Connected state but may not monitor the PDCCH, whether or not in the DRX mode.
  • the UE may no longer transmit layer 3 measurement reports directly to the eNB.
  • the LTE Inactive state and LTE Active state may each thus be a subset of the RRC Connected state.
  • the RACH procedure by the UE may include preamble selection (if a preamble index was not provided by the eNB), computation of a PRACH transmission opportunity and transmission of a preamble index on a PRACH channel based on the prach-config parameter, monitoring the PDCCH channel for a RA-RNTI of the UE and, if successfully received, re-synchronizing with the eNB.
  • the UE 502 and/or the eNB 504 may determine that the UE 502 is also located sufficiently far from the edge of the AP 506 serving area that it would be beneficial to switch to the LTE Inactive state (e.g., the UE 502 may remain within range of the AP 506 for at least several sec).
  • the eNB 504 may provide all data to the UE 502 through the AP 506.
  • the UE 502, however, may still be in the RRC Connected State, in which the UE 502, e.g., may provide measurements based on reference signals transmitted by the eNB 504.
  • the UE 502 may determine that further power saving, and thus entry into the LTE Inactive state is desirable. For example, the UE 502 may determine that the UE 502 is operating under battery power rather than being plugged into a voltage source. In some embodiments, the UE 502 may be triggered to enter the LTE Inactive state once the battery power falls below a predetermined power threshold. Regardless of what triggers the determination, the UE 502 may at operation 512 transmit a request for entry into the LTE Inactive state to the eNB 504.
  • the eNB 504 may respond to the LTE Inactive state request.
  • the eNB 504 may, as shown, confirm entry of the UE 502 into the LTE Inactive state. However, in other cases, the eNB 504 may deny entry of the UE 502 into the LTE Inactive state. This may be due, for example, to the eNB 504 desiring the UE 502 to respond to the reference signals (e.g., the UE 502 is near the cell boundary and the reference signals are to be used for imminent handover) or a significant amount of additional data is to be provided to the UE 502 and the eNB 504 intends to use the LTE band.
  • the reference signals e.g., the UE 502 is near the cell boundary and the reference signals are to be used for imminent handover
  • a significant amount of additional data is to be provided to the UE 502 and the eNB 504 intends to use the LTE band.
  • the UE 502 may respond to the confirmation. Specifically, the UE 502 may switch the LTE stack completely or partially off and not respond to any LTE-related requests, such as network- initiated reference signal measurements or monitoring paging opportunities. Switching off the LTE stack may also involve powering down some or all of the physical components in the modem and transmitter/ receiver chain associated with LTE band communications. In some embodiments, the LTE stack is switched off temporarily when the LTE stack is switched partially off, so that LTE communications from the eNB 594 may not be received and no response forthcoming during the off period. The UE 502 may then enter the LTE Inactive state.
  • LTE-related requests such as network- initiated reference signal measurements or monitoring paging opportunities. Switching off the LTE stack may also involve powering down some or all of the physical components in the modem and transmitter/ receiver chain associated with LTE band communications.
  • the LTE stack is switched off temporarily when the LTE stack is switched partially off, so that LTE communications from the eNB 594 may not be received and no response forthcoming during the
  • the eNB 504 may determine that the UE 502 is to enter the LTE
  • the eNB 504 may at operation 51 2 transmit a request for entry into the LTE Inactive state to the eNB 504.
  • the eNB 504 internally move all LTE data services to the UE 502 to the WiFi band.
  • the eNB 504 may indicate to the AP 506 through an Xw message if the eNB 504 and AP 506 are separate entities or through an internal message if the eNB 504 and AP 506 are contained in the same entity.
  • the eNB 504 may then trigger the UE 502 to enter the LTE
  • the eNB 504 may at operation 526 transmit a command to the UE 502 to enter the LTE Inactive state.
  • the command may be transmitted, as shown, via higher layer signaling from the eNB 504. In other embodiments, the command may be transmitted from the eNB 504 via the AP 506.
  • the UE 502 may switch the LTE stack completely or partially off and not respond to any LTE-related requests, such as network-initiated reference signal measurements or monitoring paging opportunities. As above, switching off the LTE stack may also involve powering down some or all of the physical components in the modem and transmitter/ receiver chain associated with LTE band
  • entry into the LTE Inactive state may be controlled by the eNB 502.
  • entry into the LTE Inactive state may be controlled by the eNB 502.
  • the UE 502 may control entry into the LTE Inactive state.
  • the eNB 504 may initiate a request for the UE 502 to enter the LTE Inactive state and the UE 502 may reject this request and may, in response, transmit a rejection to the request to the eNB 504.
  • the eNB 504 may transmit a request to the UE 502 rather than a command, which the UE 502 is free to reject.
  • FIG. 6 illustrates a flow diagram of exit of a UE from an LTE
  • the UE 602, eNB 604 and AP 606 in FIG. 6 may be shown in one or more of FIGS. 1 -4.
  • the UE 602 is already RRC connected to the eNB 604 and connected via WiFi (or other IEEE 802.1 1 connection) to the AP 606.
  • the UE 602 is already in the LTE Inactive state, of which the eNB 604 is aware.
  • the eNB 604 may decide that the UE 602 is to transition out of the LTE Inactive state back to the RRC Connected state.
  • One reason for this may be that feedback from the UE 602 is desired by the eNB 604.
  • the UE 602 may only be able to be in the LTE Inactive state for up to a predetermined maximum amount of time before the eNB 604 may consider the UE 602 no longer served by the eNB 604.
  • the eNB 604 may signal the UE 602 through the AP 606.
  • the eNB 604 may page the UE 602 by embedding an LTE packet data unit (PDU) inside a special WiFi PDU and transmitting the special WiFi PDU to the AP 606.
  • the LTE PDU may be an LTE control data signal.
  • the paging from the eNB 604 may be mobile terminating call paging.
  • the AP 606 may receive the special WiFi PDU, extract the payload, and reencrypt the special WiFi PDU with the LTE PDU. At operation 612, the AP 606 may then transmit the special WiFi PDU to the UE 602 in a manner simi lar to normal data for the UE 602.
  • the UE 602 may receive the special WiFi PDU from the AP 606 and extract the LTE PDU.
  • the WiFi PDU may trigger internal messaging between WiFi and LTE stack at the UE 602 to wake up the LTE stack.
  • the eNB 604 may also deliver System Information Change notification to the UE 602 over WiFi (using WiFi embedded LTE PDU). The UE 602 may thereby wake up and read the changed LTE System Information.
  • the eNB 604 may also release the RRC Connection over WiFi (using WiFi embedded LTE PDU).
  • the UE 602 may at operation 616 initiate a RACH procedure to retrieve the timing alignment and request LTE resources. As the UE 602 is still in the RRC Connected state, the UE 602 may be able to quickly re-instate the connection with the eNB 604.
  • In response to transmitting the RACH at operation 616, the UE
  • the 602 at operation 618 retrieve the timing alignment from the eNB 604.
  • the UE 602 may receive the timing advance from the eNB 604 and may undertake additional updating operations if a contention-based resolution process is used. If the RACH procedure is unsuccessful, the UE 602 may re-initiate the RACH procedure at the next RACH opportunity.
  • the UE 602 enter the LTE Active state at operation 620. As above, this may be similar to the RRC Connected state in which the UE 602 responds to paging messages.
  • the UE 602 may avoid reporting
  • the UE 602 may enter the LTE Active state and perform LTE measurements so that the LTE RRM may decide Radio Admission based on these measurements.
  • the message containing the LTE measurements may be sent along with call setup messaging at operation 624. In some embodiments, the message containing the LTE measurements may be sent in a different message than the call setup messaging.
  • the UE 702 may determine that AP connectivity is failing and is thus going out of AP coverage. For example, the UE 702 may have moved a significant distance relative to the AP coverage area, the AP 706 may have operational issues or an interference source may have arisen and degraded the channels provided by the AP 706.
  • the UE 702 may attempt a RACH procedure at operation 726.
  • the UE 702 may attempt to reenter the LTE Active state by transmitting a RACH to the eNB l 704, the eNB with which the UE 702 was connected prior to entering the LTE Inactive state.
  • the UE 702 has also moved out of range of the eNB 1 704.
  • the RACH procedure attempted by the UE 702 on the eNB l 704 may fail.
  • the UE 702 may, in some circumstances not receive a response from the eNB 1 704.
  • In the event, the UE 702 fails to enter the LTE Active state by
  • the UE 702 may turn to the backup eNBs from the LTE Inactive confirmation message provided by the eNB l 704. Specifically, at operation 728 the UE 702 may try to find one of the PCIs from the set of PCIs provided by eNB l 704. The UE 702 may select the order of attempting the PCIs randomly, in order based on the list provided by the eNB l 704 or, as shown, based on the best signal characteristics of the reference signals received from the eNBs. The eNB l 704 may indicate the signal measurements to use to determine the best characteristics, such as the RSRP and/or RSRQ.
  • the eNB l 704 may provide the order, for example, based on distance of the UE 702 from the eNBs dependent on the location of the AP 706. The UE 702 may thus attempt RACH on the eNB2 708 corresponding to the selected PCI. As shown, the UE 702 may successfully complete the RACH procedure with the eNB2 708. Once the UE 702 knows the PCI for a given eNB, the UE 702 may also know the location of cell Reference signals used in channel estimation, cell selection/ reselection and handover procedures.
  • the UE 702 may attempt to re-establish a connection with the eNB2 708 at operation 730. As shown, the UE 702 may transmit a Reattempt Connection Request to the eNB2 708. The UE 702 may provide to the eNB2 708 in the Reattempt Connection Request the PCI of the eNB l 704 where the UE 702 was previously RRC connected while in the LTE Inactive state. In some embodiments, the Reattempt Connection Request may be modified from an RRC Re-establishment Request.
  • the eNB2 708 may transmit a message to the eNB l 704 to request whether the UE 702 was attached to the eNB l 704 and whether the eNB2 708 should permit the UE 702 to establish a RRC connection with the eNB2 708.
  • the eNB 1 704 may respond affirmatively.
  • the communication between the eNB 1 704 and the eNB2 708 may be via a backhaul. These communications may allow the Reattempted establishment to be successful even in the case where ideally normal Re-establishment would have failed due to the eNB2 708 not being initially prepared for the UE 702.
  • the eNB2 708 and other eNBs in the PCI list may be prepared (i.e., may already have the UE Context from the eNB l 704).
  • the operator in charge of the eNBs may use proprietary mechanisms to keep the participating eNBs prepared.
  • the UE 702 is permitted to re-connect to the eNB2 708 rather than the eNB l 704, the UE 702 and the eNB2 708 may complete a Reattempt procedure.
  • the eNB2 708 may in response to the reattempt connection request from the UE 702 at operation 730, respond with a reattempt connection response to the UE 702 indicating that the UE 702 may establish the LTE Active state with the eNB2 708.
  • the UE 702 may then indicate to the eNB2 708 that the reattempt connection procedure is complete through a reattempt connection complete message.
  • the S I -MME connection may still be established between the eNB l 704 and the MME 710, as shown by the dotted line in FIG. 7.
  • the eNB l 704 and eNB2 708 may combine to adjust routing of data packets from the core network to the eNB 708.
  • the eNB2 708 may initiate data forwarding from the eNB l 704 to itself to avoid data loss of the LWA bearer of the UE 702.
  • the LWA bearer a bearer whose backhaul is connected to LTE but is being served on WiFi.
  • the eNB2 708 may transmit tunnel information for the LWA bearers to the eNB l 704. [001011 In response to receiving the tunnel information, and having previously received the request from the eNB2 708 at operation 732, the eNB l 704 may switch the S I -U tunnels of the UE 702 to the eNB2 704 at operation 736.
  • the eNB 1 704 may communicate with the eNB2 708 and the MME 710 as part of the procedure to hand over the data processing.
  • the eNB l 704 may temporarily forward buffered data to the eNB2 708 and may institute an established path switch procedure (for eNB handover) at the MME 710. A procedure similar to the SN Status Transfer may be used by the UE 702 to prevent data loss after successfully re-establishing on the eNB2 708.
  • the eNB2 708 may transmit a path switch message to the MME 710 to inform the MME 710 that the UE has changed cell.
  • the MME 710 may transmit to the Serving Gateway (SGW) 712 an update user plane request.
  • the update user plane request may include the new tunnel parameters for communication of data from the MME 710 to the eNB2 708 to the UE 702.
  • the SGW 712 may switch the downlink data path to the eNB2 708 and send one or more end marker packets on the old path to the eNB 1 704.
  • the SGW 712 may subsequently release any U-plane/TNL resources towards the eNB l 704 and transmit an update user plane response to the MME 710.
  • the MME 710 may confirm the path switch message from the eNB l 704 with a path switch AC message.
  • the eNB2 708 may inform the eNB l 704 of success of the handover and trigger the release of resources by the eNB l 704.
  • the eNB2 708 may transmit this message after the path switch ACK message is received from the MME 710.
  • the eNB 1 704 may release radio and C-plane related resources associated with the UE context.
  • Switching the S I -MME context of the UE 702 to the eNB2 708 may be accomplished once the UE 702 releases the RRC Connection using a forced UE Context Release.
  • the eNB2 708 may force a RRC Connection Release along with a UE context Release after high QoS services like voice calls are released.
  • the S I -MME context between the MME 710 and the eNB l 704 may be maintained while relocating the S l -U between the eNB2 708 and the SGW 712 and the Uu between the eNB2 708 and the UE 702.
  • the eNBs may thus be connected by X2 or a proprietary backhaul.
  • FIG. 8 illustrates a flow diagram of a UE in an LTE Inactive state in accordance with some embodiments.
  • This approach to avoiding RLF at the UE may be similar to the existing LTE handover structure. Similar to FIG. 7, the process may start at operation 822 when the UE 802 transmits a request for entry into the LTE Inactive state to the eNB l 804.
  • the eNB l 804 may respond to the LTE Inactive state request and confirm entry of the UE 802 into a modified LTE Inactive state. In other embodiments, entry of the UE 802 into the modified LTE Inactive state may be initiated by the eNB l 804.
  • the eNB 804 may provide additional information to the UE 802 in the confirmation or in an eNB-initiated LTE Inactive Request. As above, the eNB 804 may configure the UE 802 with a minimum set of one or more PCIs associated with one or more eNBs in the current vicinity of the UE 802. The eNB 804 may be connected with one or more of the eNBs associated with the PCIs via an X2 or S I backhaul connection.
  • the 802 may monitor the PCIs of the set of LTE PCIs provided by the eNB 804.
  • the UE 802 may keep the LTE components activated and, instead of switching off the LTE stack, provide minimal interaction with the eNB 804. This is to say that, the UE 802 may continue to monitor only those reference signals associated with the configured PCIs.
  • the reference signals of the minimum set of PCIs may be significantly smaller than all of the reference signals available to be received and measured by the UE 802.
  • the LTE stack may be off when reference signals associated with the other PCIs arrive at the UE 802.
  • the eNB 804 may configure the UE 802 with one or more thresholds to trigger a measurement report before UE 802 enters LTE Inactive state.
  • the thresholds may be specific to each PCI.
  • the measurement report may trigger if a PCI of an eNB in the list becomes offset better than serving cell.
  • the threshold for measurement of a particular eNB may be absolute.
  • the threshold for measurement of a particular PCI may be relative to the eNB 804 or to other eNBs in the set.
  • the eNB 804 in configuring the UE 802 may provide a predetermined amount of time for the threshold to be exceeded for before the measurement is triggered.
  • the eNB 804 may configure the UE 802 with one periodicity for measuring and/or providing measurement reports for the PCIs, or with different periodicities for measurements, dependent on the particular PCI .
  • the reporting triggers may be similar to those described above.
  • the UE 802 may provide a measurement report of the PCI(s) to the AP 806.
  • the UE 802 may receive the reference signals via the LTE transceiver, the UE 802 may transmit the measurement report encapsulated in one or more WiFi PDUs via the WiFi transceiver.
  • the AP 806 may extract the LTE measurement report and determine that the LTE measurement report is to be provided to the eNB 804. At operation 828, the AP 806 may transmit the measurement report to the eNB 804 via an internal or external interface, dependent on whether the AP 806 and eNB 804 are separate devices or in one device.
  • the eNB 804 may receive the measurement report and take appropriate action. For example, the eNB 804 may determine from the measurements in the measurement report that the UE 802 is to return to the LTE Active state. Alternatively, the eNB 804 may determine that the UE 802 is to return to the LTE Active state from the mere reception of the report as the eNB 804 may otherwise not expect a report from the UE 802. The eNB 804 may, in response, transmit an LTE Active command to the AP 806.
  • the AP 806 may forward the LTE Active command from the eNB 804 to the UE 802.
  • the LTE Active command may instruct the UE 802 to re-enter the LTE Active state from the modified LTE Inactive state.
  • the UE 802 may attempt a RACH procedure at operation 834.
  • the UE 802 may attempt to reenter the LTE Active state by transmitting a RACH to the eNB 804, the eNB with which the UE 802 was connected prior to entering the LTE Inactive state.
  • the UE 802 may retrieve the timing alignment and request LTE resources from the eNB 804.
  • the UE 802 may receive the timing advance from the eNB 804 and may undertake additional updating operations if a contention-based resolution process is used.
  • the UE 802 Having successfully obtained the timing information from the eNB 804, the UE 802 enter the LTE Active state at operation 836. As above, this may be similar to the RRC Connected state in which the UE 802 may respond to paging messages and take measurements of reference signals from more than the eNBs having the PCIs in the set of PCIs.
  • the UE 802 may then continue to remain in the LTE Active state, until the eNB 804 decides that the UE 802 is safe enough to be moved back to LTE Inactive state (e.g., sufficiently far from the cell edge).
  • the safe location may be dependent on, for example, the speed at which the UE 802 is moving as well as the direction of motion.
  • the eNB 804 may perform handover to another eNB to maintain the UE Connection.
  • the UE 802 may not listen to paging occasions from the eNB 804 or monitor PDCCHs when in the LTE Inactive state.
  • the UE 802 may only wake up the LTE Firmware periodically to perform the requested measurements and relay the measurements to the WiFi stack for transmission to the eNB 804 through the AP 806.
  • the UE 802 may only measure and/or transmit the measurement report when the configured measurement and/or reporting conditions are met, if the eNB 804 has supplied the conditions to the UE 802 in response to the LTE Inactive state request from the UE 802.
  • Example 1 is an apparatus of user equipment (UE) comprising: an evolved NodeB (eNB) transceiver arranged to communicate with an eNB and an access point (AP) transceiver arranged to communicate with an AP; and processing circuitry arranged to: configure the eNB and AP transceivers to communicate data respectively with the eNB and with the AP for the eNB using Long Term Evolution (LTE)/Wireless Local Area Network (WLAN)
  • LTE Long Term Evolution
  • WLAN Wireless Local Area Network
  • Example 2 the subject matter of Example 1 optionally includes that while in the LTE Inactive state the UE is configured to be free from reception by the eNB transceiver of paging messages and a physical downlink control channel (PDCCH).
  • PDCCH physical downlink control channel
  • Example 3 the subject matter of any one or more of Examples
  • processing circuitry is further arranged to:
  • the eNB transceiver configures the eNB transceiver to receive from the eNB, free from transmission of a request from the UE to the eNB to enter the LTE Inactive state, an LTE Inactive state command to initiate entry of the UE into the LTE Inactive state.
  • Example 5 the subject matter of any one or more of Examples
  • the AP transceiver configures the AP transceiver to receive from the eNB through the AP LTE control data to initiate exit of the UE from the LTE Inactive state and entry of the UE into the LTE Active state, and in response to reception of the LTE control data, wake up the LTE stack.
  • Example 6 the subject matter of Example 5 optionally includes that the processing circuitry is further arranged to: in response to the LTE stack being woken up, initiate a Random Access Procedure (RACH) procedure to time align the UE with the eNB via the eNB transceiver, after completion of the RACH procedure, configure the eNB transceiver to receive from the eNB reference signals, measure the reference signals, and configure the eNB transceiver to transmit a measurement report comprising a measurement of the reference signals to the eNB.
  • RACH Random Access Procedure
  • Example 7 the subject matter of any one or more of Examples
  • the processing circuitry is further arranged to: detect while the UE is in the LTE Inactive state that connectivity with the AP is in the process of failure, in response to detection of the connectivity failure, initiate a Random Access Procedure (RACH) procedure to time align the UE with the eNB via the eNB transceiver, and in response to failure to complete the RACH procedure with the eNB, select a Physical Cell Identity (PCI) of a neighbor eNB to the eNB, initiate another RACH procedure to time align the UE with the neighbor eNB via the eNB transceiver, and in response to successful completion of the other RACH procedure, configure the eNB transceiver to transmit a Reattempt Connection request to the neighbor eNB and in response receive a Reattempt Connection response that indicates that the UE is to obtain LWA communications with the neighbor eNB and the AP.
  • RACH Random Access Procedure
  • PCI Physical Cell Identity
  • Example 8 the subject matter of Example 7 optionally includes that the processing circuitry is further arranged to: configure the eNB transceiver to receive, in a message from the eNB comprising an instruction to enter the LTE Inactive state, a PCI list of PCls of neighbor eNBs in a vicinity of the UE.
  • Example 9 the subject matter of Example 8 optionally includes that the processing circuitry is further arranged to: measure reference signals of the neighbor eNBs in the list of PCls, and determine the reference signals having best signal characteristics to select the neighbor eNB with which to initiate the other RACH procedure.
  • Example 10 the subject matter of any one or more of Examples 1-9 optionally include that while in the LTE Inactive state the UE is configured to periodically measure reference signals from a neighbor eNB by the eNB transceiver and be free from reception by the eNB transceiver of paging messages and a physical downlink control channel (PDCCH).
  • the UE is configured to periodically measure reference signals from a neighbor eNB by the eNB transceiver and be free from reception by the eNB transceiver of paging messages and a physical downlink control channel (PDCCH).
  • PDCCH physical downlink control channel
  • Example 1 1 the subject matter of Example 10 optionally includes that the processing circuitry is further arranged to: configure the eNB transceiver to periodically measure reference signals associated with a set of Physical Cell Identities (PCls) of a plurality of neighbor eNBs, and configure the AP transceiver to transmit a measurement report comprising the measurements to the eNB.
  • PCls Physical Cell Identities
  • Example 12 the subject matter of Example 1 1 optionally includes that the processing circuitry is further arranged to: in response to transmission of the measurement report, configure the AP transceiver to receive from the AP a LTE Active command from the eNB to enter the LTE Active state, and in response to receiving the LTE Active command, wake up the LTE stack and initiate a Random Access Procedure (RACH) procedure to time align the UE with the eNB via the eNB transceiver.
  • RACH Random Access Procedure
  • Example 13 the subject matter of any one or more of
  • Examples 1 1-12 optionally include that configure the eNB transceiver to receive, in a message from the eNB comprising an instruction to enter the LTE Inactive state, the set of PCIs.
  • Example 14 the subject matter of any one or more of
  • Examples 1-13 optionally further comprise a plurality of antennas configured to provide communications between the eNB transceiver and the eNB and the AP transceiver and the AP.
  • Example 15 is an apparatus of an evolved NodeB (eNB) comprising: a user equipment (UE) transceiver arranged to communicate with a UE; an access point (AP) transceiver arranged to communicate with an AP; and processing circuitry arranged to: configure the UE and AP transceivers to communicate data for the UE respectively with the UE and the AP using Long Term Evolution (LTE)/Wireless Local Area Network (WLAN) Aggregation (LWA) while the UE is in an LTE Active state; configure the UE transceiver to one of: determine that data services are being provided through the UE transceiver and the AP transceiver and in response configure the UE transceiver to transmit to the UE an LTE Inactive state command to initiate entry into an LTE Inactive state in which an LTE stack is one of completely and partially off and the UE remains in Radio Resource Control (RRC) connection with the eNB, free from transmission of a request from the UE to the eNB to
  • Example 16 the subject matter of Example 15 optionally includes that while in the LTE Inactive state the UE transceiver is configured to be free from response from the UE to paging messages, reference signals, and a physical downlink control channel (PDCCH) for the UE, and the processing circuitry is further arranged to: configure the AP transceiver to transmit to the UE through the AP LTE control data to initiate exit of the UE from the LTE Inactive state and entry of the UE into the LTE Active state, in response to transmission of the LTE control data, configure the UE transceiver to receive from the UE a Random Access Procedure (RACH) transmission to time align the UE with the eNB and in response transmit timing information to the UE, and after transmission of the timing information, configure the UE transceiver to transmit reference signals and receive a measurement report comprising a measurement of the reference signals from the UE.
  • RACH Random Access Procedure
  • Example 17 the subject matter of any one or more of Examples 15-16 optionally include that the processing circuitry is further arranged to: configure the UE transceiver to transmit in a message indicating permission for the UE to enter the LTE Inactive state a Physical Cell Identity (PCI) list of PCIs of neighbor eNBs in a vicinity of the UE.
  • PCI Physical Cell Identity
  • Example 18 the subject matter of Example 17 optionally includes that the processing circuitry is further arranged to: receive from one of the neighbor eNBs via a backhaul connection a request whether to allow the UE to connect to the one of the neighbor eNBs and in response: transmit an indication of allowance to the one of the neighbor eNBs, and receive tunnel information from the one of the neighbor eNBs and use the tunnel information to begin to forward data for the UE to the one of the neighbor eNBs until an end marker packet is received from a serving gateway serving the eNB.
  • Example 19 the subject matter of any one or more of
  • Examples 10-1 8 optionally include that the processing circuitry is further arranged to: while in the LTE Inactive state the UE transceiver is configured to transmit to the UE reference signals and be free from response from the UE to paging messages and a physical downlink control channel (PDCCH) for the UE, and configure the AP transceiver to periodically receive from the UE a measurement report comprising a measurement of the reference signals.
  • the processing circuitry is further arranged to: while in the LTE Inactive state the UE transceiver is configured to transmit to the UE reference signals and be free from response from the UE to paging messages and a physical downlink control channel (PDCCH) for the UE, and configure the AP transceiver to periodically receive from the UE a measurement report comprising a measurement of the reference signals.
  • PDCCH physical downlink control channel
  • Example 20 the subject matter of Example 19 optionally includes that the processing circuitry is further arranged to: in response to reception of the measurement report, configure the AP transceiver to transmit to the UE via the AP a LTE Active command to enter the LTE Active state, and in response to transmitting the LTE Active command, configure the UE transceiver to receive a Random Access Procedure (RACH) transmission from the UE to time align the UE with the eN B and transmit a response to the UE, and after transmitting the response, communicate data with the UE via the eNB transceiver.
  • RACH Random Access Procedure
  • Example 21 the subject matter of any one or more of Examples 19-20 optionally include that configure the UE transceiver to transmit to the UE, in a message indicating permission for the UE to enter the LTE Inactive state, a set of Physical Cell Identities (PCIs) of a plurality of neighbor eNBs of which the UE is to measure reference signals.
  • PCIs Physical Cell Identities
  • Example 22 is a computer-readable storage medium that stores instructions for execution by one or more processors of user equipment (UE) to communicate with an evolved NodeB (eNB) and with an access point (AP), the one or more processors to configure the UE to: communicate data respectively with the eNB and with the AP for the eNB using Long Term Evolution
  • UE user equipment
  • eNB evolved NodeB
  • AP access point
  • Example 23 the subject matter of Example 22 optionally includes that the one or more processors further configure the UE to one of: receive from the eNB an LTE Inactive state command to initiate entry into the LTE Inactive state free from transmission of a request from the UE to the eNB to enter the LTE Inactive state, and transmit to the eNB an LTE Inactive state request to initiate entry into the LTE Inactive state, and enter the LTE Inactive state in response to reception by the eNB transceiver to confirmation of the LTE Inactive state by the eNB.

Landscapes

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

Abstract

L'invention concerne des dispositifs et des procédés de réduction de consommation de puissance d'équipement utilisateur (UE) dans des scénarios de LWA. L'UE entre dans un état inactif LTE (LIS) dans lequel une pile LTE est désactivée et l'UE reste en connexion RRC avec le nœud B évolué (eNB). Dans le LIS, l'UE continue à communiquer avec l'eNB par l'intermédiaire du point d'accès (AP). L'UE peut recevoir à partir de l'eNB par l'intermédiaire de l'AP des données de commande pour déclencher une sortie vis-à-vis du LIS. L'UE peut détecter qu'une connectivité avec l'AP est dans le processus de défaillance, une synchronisation temporelle sur l'eNB ou un eNB voisin si l'eNB ne peut pas être atteint, et ensuite sortir du LIS et recevoir des données à partir de l'eNB voisin. L'UE peut continuer de mesurer des signaux de référence à partir d'un nombre minimal d'eNB, rapporter les mesures à l'eNB par l'intermédiaire de l'AP et, en réponse, recevoir une instruction en provenance de l'eNB pour sortir du LIS.
PCT/US2015/000287 2015-12-23 2015-12-23 Dispositifs et procédés de réduction de consommation de puissance de lwa et de prévention de rlf WO2017111788A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2015/000287 WO2017111788A1 (fr) 2015-12-23 2015-12-23 Dispositifs et procédés de réduction de consommation de puissance de lwa et de prévention de rlf

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2015/000287 WO2017111788A1 (fr) 2015-12-23 2015-12-23 Dispositifs et procédés de réduction de consommation de puissance de lwa et de prévention de rlf

Publications (1)

Publication Number Publication Date
WO2017111788A1 true WO2017111788A1 (fr) 2017-06-29

Family

ID=59090972

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/000287 WO2017111788A1 (fr) 2015-12-23 2015-12-23 Dispositifs et procédés de réduction de consommation de puissance de lwa et de prévention de rlf

Country Status (1)

Country Link
WO (1) WO2017111788A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019061179A1 (fr) * 2017-09-28 2019-04-04 Zte Corporation Procédé et systèmes d'échange de messages dans un réseau sans fil
US10999819B2 (en) * 2017-04-20 2021-05-04 Lg Electronics Inc. Method and apparatus to support mobility in LWA

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100165970A1 (en) * 2008-12-25 2010-07-01 Via Telecom, Inc. Apparatus and method for fast synchronization in a dual mode system
WO2012039656A1 (fr) * 2010-09-21 2012-03-29 Telefonaktiebolaget L M Ericsson (Publ) Relayage dans le regroupement mixte de porteuses réglementées et non réglementées
US20120093009A1 (en) * 2010-03-30 2012-04-19 Qualcomm Incorporated Method and apparatus to facilitate support for multi-radio coexistence
US20130229965A1 (en) * 2012-03-05 2013-09-05 Qualcomm Incorporated Paging during connected mode discontinuous reception (drx) operations
US20150036656A1 (en) * 2013-07-31 2015-02-05 Broadcom Corporation Wlan and cellular shared antennas

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100165970A1 (en) * 2008-12-25 2010-07-01 Via Telecom, Inc. Apparatus and method for fast synchronization in a dual mode system
US20120093009A1 (en) * 2010-03-30 2012-04-19 Qualcomm Incorporated Method and apparatus to facilitate support for multi-radio coexistence
WO2012039656A1 (fr) * 2010-09-21 2012-03-29 Telefonaktiebolaget L M Ericsson (Publ) Relayage dans le regroupement mixte de porteuses réglementées et non réglementées
US20130229965A1 (en) * 2012-03-05 2013-09-05 Qualcomm Incorporated Paging during connected mode discontinuous reception (drx) operations
US20150036656A1 (en) * 2013-07-31 2015-02-05 Broadcom Corporation Wlan and cellular shared antennas

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10999819B2 (en) * 2017-04-20 2021-05-04 Lg Electronics Inc. Method and apparatus to support mobility in LWA
WO2019061179A1 (fr) * 2017-09-28 2019-04-04 Zte Corporation Procédé et systèmes d'échange de messages dans un réseau sans fil
US10966275B2 (en) 2017-09-28 2021-03-30 Zte Corporation Method and systems for exchanging messages in a wireless network
US11477842B2 (en) 2017-09-28 2022-10-18 Zte Corporation Method and systems for exchanging messages in a wireless network

Similar Documents

Publication Publication Date Title
US10462774B2 (en) Discontinuous reception (DRX) schemes for millimeter wavelength (MMW) dual connectivity
US10298314B2 (en) Repeater operation method and apparatus in wireless communication system
KR102050885B1 (ko) 유휴 모드와 접속 모드 사이의 전이를 위한 진화된 노드 b, 사용자 장비 및 방법들
EP3295757B1 (fr) Initiation et configuration de relais d'un ue à un réseau
TWI596967B (zh) 用以支援延伸非連續接收機制的行動性管理實體、使用者設備與方法
US9894702B2 (en) Performing primary cell functions in a secondary cell
KR102666360B1 (ko) 무선 통신 방법, 단말 장치 및 네트워크 장치
WO2018085049A1 (fr) Systèmes, procédés et dispositifs de transfert intercellulaire à établissement avant rupture et reconfiguration de groupe de cellules secondaires
US10897694B2 (en) Personal area network communication for wearable devices
EP3437392B1 (fr) Tau pour une demande d'appel ims dans des réseaux d'accès radio
TWI821153B (zh) 移動性增強及可穿戴裝置路徑選擇之裝置及方法
CN113596935A (zh) 5g nr多rat环境中的扫描优化
WO2018106429A1 (fr) Mécanisme de transfert intercellulaire amélioré
WO2018085416A1 (fr) Support de mobilité pour systèmes 5g nr
US11057832B2 (en) Method and apparatus for transmitting and receiving a wake-up signal in a wireless communication system
CN109803335B (zh) 一种接入网络的控制方法和装置
WO2017078743A1 (fr) Dispositifs et procédés de drx et synchronisation de mode d'économie d'énergie de wlan pour lwa
WO2021000322A1 (fr) Commutation proactive de communication v2x d'une connexion en liaison latérale à une connexion cellulaire
WO2017111788A1 (fr) Dispositifs et procédés de réduction de consommation de puissance de lwa et de prévention de rlf
CN115707146A (zh) 用于促进有效rach和bfr过程的装置和方法
EP3437381A1 (fr) Échelonnement d'un trafic sans surveillance dans un système d'évolution à long terme (lte) après une interdiction
WO2018031139A1 (fr) Prise en charge améliorée d'agrégation x2 et xw de lte-wlan pour un transfert sans changement de terminaison wlan

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

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

Country of ref document: EP

Kind code of ref document: A1