Techniques and apparatuses for long term evolution idle-mode and enhanced multimedia broadcast and multicast service concurrency operation

Certain aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may determine, that the UE is registered for a voice-over wireless local area network (WLAN) service; and forgo, based at least in part on determining that the UE is registered for the voice-over WLAN service, waking up to perform a long term evolution (LTE) idle-mode operation, wherein the LTE idle-mode operation includes monitoring for a page during a paging occasion. Numerous other aspects are provided.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication, and more particularly to techniques and apparatuses for long term evolution (LTE) idle-mode and enhanced multimedia broadcast and multicast service (eMBMS) concurrency operation.

BACKGROUND

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, a national, a regional, and even a global level. An example of a telecommunication standard is Long Term Evolution (LTE). LTE is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by Third Generation Partnership Project (3GPP). LTE is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, using new spectrum, and integrating with other open standards using OFDMA on the downlink (DL), SC-FDMA on the uplink (UL), and multiple-input multiple-output (MIMO) antenna technology.

SUMMARY

In some aspects, a method of wireless communication may include determining, by a user equipment (UE), that the UE is registered for a voice-over wireless local area network (WLAN) service; and forgoing, by the UE and based at least in part on determining that the UE is registered for the voice-over WLAN service, waking up (e.g., determining, by the UE and based at least in part on determining that the UE is registered for the voice-over WLAN service, not to wake up) to perform a long term evolution (LTE) idle-mode operation, wherein the LTE idle-mode operation includes monitoring for a page during a paging occasion.

In some aspects, a UE may include a memory and one or more processors operatively coupled to the memory. The one or more processors may be configured to determine that the UE is registered for a voice-over WLAN service; and forgo, based at least in part on determining that the UE is registered for the voice-over WLAN service, waking up (e.g., determine, based at least in part on determining that the UE is registered for the voice-over WLAN service, not to wake up) to perform a LTE idle-mode operation, wherein the LTE idle-mode operation includes monitoring for a page during a paging occasion.

In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless communication device, may cause the one or more processors to determine that the wireless communication device is registered for a voice-over WLAN service; and forgo, based at least in part on determining that the wireless communication device is registered for the voice-over WLAN service, waking up (e.g., determining, based at least in part on determining that the wireless communication device is registered for the voice-over WLAN service, not to wake up) to perform a LTE idle-mode operation, wherein the LTE idle-mode operation includes monitoring for a page during a paging occasion.

In some aspects, an apparatus for wireless communication may include means for determining that the apparatus is registered for a voice-over WLAN service; and means for forgoing, based at least in part on determining that the apparatus is registered for the voice-over WLAN service, waking up (e.g., determining, based at least in part on determining that the apparatus is registered for the voice-over WLAN service, not to wake up) to perform a LTE idle-mode operation, wherein the LTE idle-mode operation includes monitoring for a page during a paging occasion.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with the appended drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details.

The techniques described herein may be used for one or more of various wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, or other types of networks. A CDMA network may implement a radio access technology (RAT) such as universal terrestrial radio access (UTRA), CDMA2000, and/or the like. UTRA may include wideband CDMA (WCDMA) and/or other variants of CDMA. CDMA2000 may include Interim Standard (IS)-2000, IS-95 and IS-856 standards. IS-2000 may also be referred to as 1× radio transmission technology (1×RTT), CDMA2000 1×, and/or the like. A TDMA network may implement a RAT such as global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), or GSM/EDGE radio access network (GERAN). An OFDMA network may implement a RAT such as evolved UTRA (E-UTRA), ultra mobile broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and/or the like. UTRA and E-UTRA may be part of the universal mobile telecommunication system (UMTS). 3GPP long-term evolution (LTE) and LTE-Advanced (LTE-A) are example releases of UMTS that use E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the wireless networks and RATs mentioned above as well as other wireless networks and RATs.

FIG. 1is a diagram illustrating an example deployment100in which multiple wireless networks have overlapping coverage, in accordance with various aspects of the present disclosure. However, wireless networks may not have overlapping coverage in aspects. As shown, example deployment100may include an evolved universal terrestrial radio access network (E-UTRAN)105, which may include one or more evolved Node Bs (eNBs)110, and which may communicate with other devices or networks via a serving gateway (SGW)115and/or a mobility management entity (MME)120. As further shown, example deployment100may include a radio access network (RAN)125, which may include one or more base stations130, and which may communicate with other devices or networks via a mobile switching center (MSC)135and/or an inter-working function (IWF)140. As further shown, example deployment100may include a wireless local area network (WLAN)150, which may include one or more access points (APs)155(e.g., one or more Wi-Fi access points), and which may communicate with other devices or networks via IWF140(e.g., one or more devices included in an IMS core associated with a core network). As further shown, example deployment100may include one or more user equipment (UEs)145capable of communicating via E-UTRAN105, RAN125, and/or WLAN150.

E-UTRAN105may support, for example, LTE or another type of RAT. E-UTRAN105may include eNBs110and other network entities that can support wireless communication for UEs145. Each eNB110may provide communication coverage for a particular geographic area. The term “cell” may refer to a coverage area of eNB110and/or an eNB subsystem serving the coverage area on a specific frequency channel.

SGW115may communicate with E-UTRAN105and may perform various functions, such as packet routing and forwarding, mobility anchoring, packet buffering, initiation of network-triggered services, and/or the like. MME120may communicate with E-UTRAN105and SGW115and may perform various functions, such as mobility management, bearer management, distribution of paging messages, security control, authentication, gateway selection, and/or the like, for UEs145located within a geographic region served by MME120of E-UTRAN105. The network entities in LTE are described in 3GPP TS 36.300, entitled “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description,” which is publicly available.

RAN125may support, for example, GSM or another type of RAT. RAN125may include base stations130and other network entities that can support wireless communication for UEs145. MSC135may communicate with RAN125and may perform various functions, such as voice services, routing for circuit-switched calls, and mobility management for UEs145located within a geographic region served by MSC135of RAN125. In some aspects, IWF140may facilitate communication between MME120and MSC135(e.g., when E-UTRAN105and RAN125use different RATs). Additionally, or alternatively, MME120may communicate directly with an MME that interfaces with RAN125, for example, without IWF140(e.g., when E-UTRAN105and RAN125use a same RAT). In some aspects, E-UTRAN105and RAN125may use the same frequency and/or the same RAT to communicate with UE145. In some aspects, E-UTRAN105and RAN125may use different frequencies and/or RATs to communicate with UEs145. As used herein, the term base station is not tied to any particular RAT, and may refer to an eNB (e.g., of a LTE network) or another type of base station associated with a different type of RAT.

With reference to WLAN150of example deployment100, APs155may wirelessly communicate with UEs145via one or more WLAN access point antennas, over one or more communication links. In some examples, APs155may communicate with UEs145using one or more Wi-Fi communication standards, such as an Institute of Electrical and Electronics (IEEE) Standard 802.11 (e.g., IEEE Standard 802.11a, IEEE Standard 802.11n, or IEEE Standard 802.11ac). In some aspects, WLAN150may support a voice-over WLAN service, whereby UEs145receive voice calls via WLAN150(e.g., rather than E-UTRAN105or RAN125), as described below.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, and/or the like. A frequency or frequency ranges may also be referred to as a carrier, a frequency channel, and/or the like. Each frequency or frequency range may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.

UE145may be stationary or mobile and may also be referred to as a mobile station, a terminal, an access terminal, a wireless communication device, a subscriber unit, a station, and/or the like. UE145may be a cellular 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, and/or the like. UE145may be included inside a housing145′ that houses components of UE145, such as processor components, memory components, and/or the like.

Upon power up, UE145may search for wireless networks from which UE145can receive communication services. If UE145detects more than one wireless network, then a wireless network with the highest priority may be selected to serve UE145and may be referred to as the serving network. UE145may perform registration with the serving network, if necessary. UE145may then operate in a connected mode to actively communicate with the serving network. Alternatively, UE145may operate in an idle-mode and camp on the serving network if active communication is not required by UE145.

UE145may operate in the idle-mode as follows. UE145may identify all frequencies/RATs on which it is able to find a “suitable” cell in a normal scenario or an “acceptable” cell in an emergency scenario, where “suitable” and “acceptable” are specified in the LTE standards. UE145may then camp on the frequency/RAT with the highest priority among all identified frequencies/RATs. UE145may remain camped on this frequency/RAT until either (i) the frequency/RAT is no longer available at a predetermined threshold or (ii) another frequency/RAT with a higher priority reaches this threshold. In some aspects, UE145may receive a neighbor list when operating in the idle-mode, such as a neighbor list included in a system information block type 5 (SIB 5) provided by an eNB of a RAT on which UE145is camped. Additionally, or alternatively, UE145may generate a neighbor list. A neighbor list may include information identifying one or more frequencies, at which one or more RATs may be accessed, priority information associated with the one or more RATs, and/or the like.

FIG. 2is a diagram illustrating an example access network200in a LTE network architecture, in accordance with various aspects of the present disclosure. As shown, access network200may include one or more eNBs210(sometimes referred to as “base stations” herein) that serve a corresponding set of cellular regions (cells)220, one or more low power eNBs230that serve a corresponding set of cells240, and a set of UEs250.

Each eNB210may be assigned to a respective cell220and may be configured to provide an access point to a RAN. For example, eNB110,210may provide an access point for UE145,250to E-UTRAN105(e.g., eNB210may correspond to eNB110, shown inFIG. 1) or may provide an access point for UE145,250to RAN125(e.g., eNB210may correspond to base station130, shown inFIG. 1). In some cases, the terms base station and eNB may be used interchangeably, and a base station, as used herein, is not tied to any particular RAT. UE145,250may correspond to UE145, shown inFIG. 1.FIG. 2does not illustrate a centralized controller for example access network200, but access network200may use a centralized controller in some aspects. The eNBs210may perform radio related functions including radio bearer control, admission control, mobility control, scheduling, security, and network connectivity (e.g., to SGW115).

As shown inFIG. 2, one or more low power eNBs230may serve respective cells240, which may overlap with one or more cells220served by eNBs210. The eNBs230may correspond to eNB110associated with E-UTRAN105and/or base station130associated with RAN125, shown inFIG. 1. A low power eNB230may be referred to as a remote radio head (RRH). The low power eNB230may include a femto cell eNB (e.g., home eNB (HeNB)), a pico cell eNB, a micro cell eNB, and/or the like.

A modulation and multiple access scheme employed by access network200may vary depending on the particular telecommunications standard being deployed. In LTE applications, OFDM is used on the downlink (DL) and SC-FDMA is used on the uplink (UL) to support both frequency division duplexing (FDD) and time division duplexing (TDD). The various concepts presented herein are well suited for LTE applications. However, these concepts may be readily extended to other telecommunication standards employing other modulation and multiple access techniques. By way of example, these concepts may be extended to Evolution-Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations. As another example, these concepts may also be extended to UTRA employing WCDMA and other variants of CDMA (e.g., such as TD-SCDMA, GSM employing TDMA, E-UTRA, and/or the like), UMB, IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM employing OFDMA, and/or the like. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from the 3GPP organization. CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.

The eNBs210may have multiple antennas supporting MIMO technology. The use of MIMO technology enables eNBs210to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing may be used to transmit different streams of data simultaneously on the same frequency. The data streams may be transmitted to a single UE145,250to increase the data rate or to multiple UEs250to increase the overall system capacity. This may be achieved by spatially precoding each data stream (e.g., applying a scaling of an amplitude and a phase) and then transmitting each spatially precoded stream through multiple transmit antennas on the DL. The spatially precoded data streams arrive at the UE(s)250with different spatial signatures, which enables each of the UE(s)250to recover the one or more data streams destined for that UE145,250. On the UL, each UE145,250transmits a spatially precoded data stream, which enables eNBs210to identify the source of each spatially precoded data stream.

The number and arrangement of devices and cells shown inFIG. 2are provided as an example. In practice, there may be additional devices and/or cells, fewer devices and/or cells, different devices and/or cells, or differently arranged devices and/or cells than those shown inFIG. 2. Furthermore, two or more devices shown inFIG. 2may be implemented within a single device, or a single device shown inFIG. 2may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) shown inFIG. 2may perform one or more functions described as being performed by another set of devices shown inFIG. 2.

FIG. 3is a diagram illustrating an example300of a downlink (DL) frame structure in LTE, in accordance with various aspects of the present disclosure. A frame (e.g., of 10 ms) may be divided into 10 equally sized sub-frames with indices of 0 through 9. Each sub-frame may include two consecutive time slots. A resource grid may be used to represent two time slots, each time slot including a resource block (RB). The resource grid is divided into multiple resource elements. In LTE, a resource block includes 12 consecutive subcarriers in the frequency domain and, for a normal cyclic prefix in each OFDM symbol, 7 consecutive OFDM symbols in the time domain, or 84 resource elements. For an extended cyclic prefix, a resource block includes 6 consecutive OFDM symbols in the time domain and has 72 resource elements. Some of the resource elements, as indicated as R310and R320, include DL reference signals (DL-RS). The DL-RS include Cell-specific RS (CRS) (also sometimes called common RS)310and UE-specific RS (UE-RS)320. UE-RS320are transmitted only on the resource blocks upon which the corresponding physical DL shared channel (PDSCH) is mapped. The number of bits carried by each resource element depends on the modulation scheme. Thus, the more resource blocks that a UE receives and the higher the modulation scheme, the higher the data rate for the UE.

In LTE, an eNB may send a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) for each cell in the eNB. The primary and secondary synchronization signals may be sent in symbol periods6and5, respectively, in each of subframes0and5of each radio frame with the normal cyclic prefix (CP). The synchronization signals may be used by UEs for cell detection and acquisition. The eNB may send a Physical Broadcast Channel (PBCH) in symbol periods0to3in slot1of subframe0. The PBCH may carry certain system information.

The eNB may send a Physical Control Format Indicator Channel (PCFICH) in the first symbol period of each subframe. The PCFICH may convey the number of symbol periods (M) used for control channels, where M may be equal to 1, 2 or 3 and may change from subframe to subframe. M may also be equal to 4 for a small system bandwidth, e.g., with less than 10 resource blocks. The eNB may send a Physical HARQ Indicator Channel (PHICH) and a Physical Downlink Control Channel (PDCCH) in the first M symbol periods of each subframe. The PHICH may carry information to support hybrid automatic repeat request (HARQ). The PDCCH may carry information on resource allocation for UEs and control information for downlink channels. The eNB may send a Physical Downlink Shared Channel (PDSCH) in the remaining symbol periods of each subframe. The PDSCH may carry data for UEs scheduled for data transmission on the downlink.

A number of resource elements may be available in each symbol period. Each resource element (RE) may cover one subcarrier in one symbol period and may be used to send one modulation symbol, which may be a real or complex value. Resource elements not used for a reference signal in each symbol period may be arranged into resource element groups (REGs). Each REG may include four resource elements in one symbol period. The PCFICH may occupy four REGs, which may be spaced approximately equally across frequency, in symbol period0. The PHICH may occupy three REGs, which may be spread across frequency, in one or more configurable symbol periods. For example, the three REGs for the PHICH may all belong in symbol period0or may be spread in symbol periods0,1, and2. The PDCCH may occupy 9, 18, 36, or 72 REGs, which may be selected from the available REGs, in the first M symbol periods, for example. Only certain combinations of REGs may be allowed for the PDCCH.

As indicated above,FIG. 3is provided as an example. Other examples are possible and may differ from what was described above in connection withFIG. 3.

As indicated above,FIG. 4is provided as an example. Other examples are possible and may differ from what was described above in connection withFIG. 4.

FIG. 5is a diagram illustrating an example500of a radio protocol architecture for a user plane and a control plane in LTE, in accordance with various aspects of the present disclosure. The radio protocol architecture for the UE and the eNB is shown with three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various physical layer signal processing functions. The L1 layer will be referred to herein as the physical layer510. Layer 2 (L2 layer)520is above the physical layer510and is responsible for the link between the UE and eNB over the physical layer MO.

In the user plane, the L2 layer520includes, for example, a media access control (MAC) sublayer530, a radio link control (RLC) sublayer540, and a packet data convergence protocol (PDCP) sublayer550, which are terminated at the eNB on the network side. Although not shown, the UE may have several upper layers above the L2 layer520including a network layer (e.g., IP layer) that is terminated at a packet data network (PDN) gateway on the network side, and an application layer that is terminated at the other end of the connection (e.g., a far end UE, a server, and/or the like).

The PDCP sublayer550provides retransmission of lost data in handover. The PDCP sublayer550also provides header compression for upper layer data packets to reduce radio transmission overhead, security by ciphering the data packets, and handover support for UEs between eNBs. The RLC sublayer540provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to hybrid automatic repeat request (HARQ). The MAC sublayer530provides multiplexing between logical and transport channels. The MAC sublayer530is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer530is also responsible for HARQ operations.

In the control plane, the radio protocol architecture for the UE and eNB is substantially the same for the physical layer510and the L2 layer520with the exception that there is no header compression function for the control plane. The control plane also includes a radio resource control (RRC) sublayer560in Layer 3 (L3 layer). The RRC sublayer560is responsible for obtaining radio resources (i.e., radio bearers) and for configuring the lower layers using RRC signaling between the eNB and the UE.

As indicated above,FIG. 5is provided as an example. Other examples are possible and may differ from what was described above in connection withFIG. 5.

FIG. 6is a diagram illustrating example components600of eNB110,210,230and UE145,250in an access network, in accordance with various aspects of the present disclosure. As shown inFIG. 6, eNB110,210,230may include a controller/processor605, a TX processor610, a channel estimator615, an antenna620, a transmitter625TX, a receiver625RX, an RX processor630, and a memory635. As further shown inFIG. 6, UE145,250may include a receiver RX, for example, of a transceiver TX/RX640, a transmitter TX, for example, of a transceiver TX/RX640, an antenna645, an RX processor650, a channel estimator655, a controller/processor660, a memory665, a data sink670, a data source675, and a TX processor680.

In the DL, upper layer packets from the core network are provided to controller/processor605. The controller/processor605implements the functionality of the L2 layer. In the DL, the controller/processor605provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations to the UE145,250based, at least in part, on various priority metrics. The controller/processor605is also responsible for HARQ operations, retransmission of lost packets, and signaling to the UE145,250.

At the UE145,250, each receiver RX, for example, of a transceiver TX/RX640receives a signal through its respective antenna645. Each such receiver RX recovers information modulated onto an RF carrier and provides the information to the receiver (RX) processor650. The RX processor650implements various signal processing functions of the L1 layer. The RX processor650performs spatial processing on the information to recover any spatial streams destined for the UE145,250. If multiple spatial streams are destined for the UE145,250, the spatial streams may be combined by the RX processor650into a single OFDM symbol stream. The RX processor650then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB110,210,230. These soft decisions may be based, at least in part, on channel estimates computed by the channel estimator655. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB110,210,230on the physical channel. The data and control signals are then provided to the controller/processor660.

The controller/processor660implements the L2 layer. The controller/processor660can be associated with a memory665that stores program codes and data. The memory665may include a non-transitory computer-readable medium. In the UL, the controller/processor660provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packets are then provided to a data sink670, which represents all the protocol layers above the L2 layer. Various control signals may also be provided to the data sink670for L3 processing. The controller/processor660is also responsible for error detection using an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support HARQ operations.

In the UL, a data source675is used to provide upper layer packets to the controller/processor660. The data source675represents all protocol layers above the L2 layer. Similar to the functionality described in connection with the DL transmission by the eNB110,210,230, the controller/processor660implements the L2 layer for the user plane and the control plane by providing header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based, at least in part, on radio resource allocations by the eNB110,210,230. The controller/processor660is also responsible for HARQ operations, retransmission of lost packets, and signaling to the eNB110,210,230.

Channel estimates derived by a channel estimator655from a reference signal or feedback transmitted by the eNB110,210,230may be used by the TX processor680to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor680are provided to different antenna645via separate transmitters TX, for example, of transceivers TX/RX640. Each transmitter TX, for example, of transceiver TX/RX640modulates an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the eNB110,210,230in a manner similar to that described in connection with the receiver function at the UE145,250. Each receiver RX, for example, of transceiver TX/RX625receives a signal through its respective antenna620. Each receiver RX, for example, of transceiver TX/RX625recovers information modulated onto an RF carrier and provides the information to a RX processor630. The RX processor630may implement the L1 layer.

The controller/processor605implements the L2 layer. The controller/processor605can be associated with a memory635that stores program code and data. The memory635may be referred to as a computer-readable medium. In the UL, the control/processor605provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE145,250. Upper layer packets from the controller/processor605may be provided to the core network. The controller/processor605is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

In some aspects, one or more components of UE145,250may be included in a housing145′, as shown inFIG. 1. One or more components of UE145,250may be configured to perform LTE idle-mode and eMBMS concurrency operation, as described in more detail elsewhere herein. For example, the controller/processor660and/or other processors and modules of UE145,250may perform or direct operations of, for example, process800ofFIG. 8and/or other processes as described herein. In some aspects, one or more of the components shown inFIG. 6may be employed to perform example process800and/or other processes for the techniques described herein.

The number and arrangement of components shown inFIG. 6are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown inFIG. 6. Furthermore, two or more components shown inFIG. 6may be implemented within a single component, or a single component shown inFIG. 6may be implemented as multiple, distributed components. Additionally, or alternatively, a set of components (e.g., one or more components) shown inFIG. 6may perform one or more functions described as being performed by another set of components shown inFIG. 6.

A UE operating in a LTE idle-mode may be capable of receiving a call (e.g., a voice call) via a radio access network, such as a LTE network. For example, the UE, while operating in the LTE idle-mode, may be configured to periodically (e.g., at intervals of time corresponding to a DRX cycle) wake from the LTE idle-mode in order perform a LTE idle-mode operation associated with monitoring for a page indicating an incoming voice call. If a page is received during this wake-up, then the UE may establish a connection with the LTE network, and receive one or more messages, associated with initiating the call (e.g., one or more session initiation protocol (SIP) messages), after establishing the connection. If no page is received during the wake-up, then the UE may return to the LTE idle-mode until a next periodic wake-up. During a given wake-up from the LTE idle-mode, the UE may also perform one or more other LTE idle-mode operations, such as monitoring or measuring neighbor cells associated with the UE (e.g., in order to prepare for a potential handover).

The UE, while operating in the LTE idle-mode, may also be capable of receiving a call via a WLAN, such as a Wi-Fi network. For example, the UE may be connected to a WLAN and registered for a voice-over WLAN service (e.g., such that a connection is established between the UE and an evolved packet data gateway (ePDG), associated with a core network, via which the voice-over WLAN service is provided). Here, the UE may receive one or more messages, associated with a voice call (e.g., initiating a voice call) (e.g., one or more SIP messages), via a WLAN AP to which the UE is attached. Notably, when the UE is registered for the voice-over WLAN service, the UE need not wake from the LTE idle-mode in order to receive the one or more messages associated with the call. In other words, while registered for the voice-over WLAN service, the UE may receive messages, associated with a voice call (e.g., initiating incoming calls), via the WLAN (rather than the LTE network). Thus, the UE does not need to perform the LTE idle-mode operation associated with monitoring for pages while the UE145,250is registered for the voice-over WLAN service to receive the one or more messages.

Some aspects described herein provide a UE capable of forgoing (e.g., skipping) a wake-up (e.g., determining not to wake up) from a LTE idle-mode, associated with monitoring for a page indicating an incoming voice call, when the UE is registered for a voice-over WLAN service. In some aspects, rather than waking from the LTE idle-mode (e.g., based at least in part on a DRX cycle) in order to perform one or more other LTE idle-mode operations (e.g., monitoring and/or measuring neighbor cells), the UE may perform the one or more other LTE idle-mode operations during a wake-up associated with receiving a transmission, such as an evolved Multimedia Broadcast and Multicast Service (eMBMS) transmission. Here, by aligning the performance of the one or more other LTE idle-mode operations with the reception of the transmission, a single wake-up from the LTE idle-mode is needed (rather than separate wake-ups for the reception of the transmission and the performance of the one or more other LTE idle-mode operations), thereby conserving battery power and/or processing resources of the UE.

FIGS. 7A and 7Bare diagrams illustrating an example700of a UE forgoing a wake-up (e.g., determining not to perform a wake up), associated with performing a LTE idle-mode operation, when the UE is registered for a voice-over WLAN service, in accordance with various aspects of the present disclosure. InFIG. 7A, the UE is operating in a LTE idle-mode, and is attached to a WLAN AP associated with a WLAN network (e.g., such that the UE can communicate with devices in an IMS core, associated with a core network via the WLAN). Here, assume that the UE is registered for a voice-over WLAN service such that a connection is established between the UE and an ePDG, associated with a core network, via which the voice-over WLAN service is provided.

As shown inFIG. 7A, and by reference number710, the UE determines that the UE is registered for the voice-over WLAN service. For example, the UE may determine, based at least in part on information stored by or configured on the UE during registration for the voice-over WLAN service, that the UE is registered for the voice-over WLAN service.

As shown by reference number720, based at least in part on determining that the UE is registered for the voice-over WLAN service, the UE forgoes (e.g., skips) a wake-up (e.g., determines not to perform a wake up) from the LTE idle-mode associated with monitoring for a page indicating an incoming voice call (sometimes referred to as a paging occasion). For example, as described above, the UE may be configured to periodically (e.g., based at least in part on a DRX cycle of 640 milliseconds (ms), 1.28 seconds, 2.56 seconds, and/or the like) wake from the LTE idle-mode in order to monitor for pages associated with incoming voice calls. However, as shown, based at least in part on the UE being registered for the voice-over WLAN service, the UE may forgo the wake-up from the LTE idle-mode for page monitoring. In some aspects, the UE may forgo a series of wake-ups (e.g., determines not to perform a series of wake-ups) from the LTE idle-mode (e.g., the UE may skip each page monitoring wake-up during a period of time that the UE is registered for the voice-over WLAN service).

For the purposes ofFIG. 7B, assume that the UE is to wake from the LTE idle-mode in order to receive an eMBMS transmission associated with an eMBMS service. Here, the eMBMS transmission may be scheduled for a portion of a multicast control channel (MCCH) scheduling period associated with the eMBMS service (e.g., a portion of a MCCH scheduling period (MSP) with a length of 80 ms, 160 ms, 320 ms, and/or the like). As part of the eMBMS service, the UE receives scheduling information that identifies the portion of the MSP during which the eMBMS transmission, to be received by the UE, will be transmitted. Thus, the UE has information that identifies a time at which the UE should wake form the LTE idle-mode in order to receive the eMBMS transmission.

As shown byFIG. 7B, and by reference number730, the UE wakes from the LTE idle-mode in order to receive the eMBMS transmission as scheduled during the MSP. The UE may receive, based at least in part on waking from the LTE idle-mode, the eMBMS transmission during the MSP.

As shown by reference number740, during the wake-up associated with receiving the eMBMS transmission, the UE may perform one or more other LTE idle-mode operations (e.g., the UE may perform the one or more other LTE idle-mode operations during the MSP). For example, as shown, the UE may monitor and/or measure one or more neighbor cells (e.g., as part of one or more LTE idle-mode operations) during the wake-up associated with the reception of the eMBMS transmission. In some aspects, the one or more other LTE idle-mode operations may include one or more LTE idle-mode operations that the UE would typically perform during a wake-up associated with monitoring for pages indicating incoming voice calls associated with the LTE network.

In some aspects, the UE may perform the one or more other LTE idle-mode operations before receiving the eMBMS transmission. For example, the UE may wake from the LTE idle-mode before the scheduled eMBMS transmission, perform the one or more other LTE idle-mode operations, and then receive the eMBMS transmission before re-entering the LTE idle-mode. In some aspects, the UE may perform the one or more other LTE idle-mode operations after receiving the eMBMS transmission. For example, the UE may wake from the LTE idle-mode at the time of the scheduled eMBMS transmission, receive the eMBMS transmission, and then perform the one or more other LTE idle-mode operations before re-entering the LTE idle-mode.

In some aspects, the UE may perform the one or more other LTE idle mode operations before and after receiving the eMBMS transmission. For example, the UE may wake from the LTE idle-mode before the scheduled eMBMS transmission, perform a first LTE idle-mode operation, receive the eMBMS transmission, and then perform a second LTE idle-mode operation before re-entering the LTE idle-mode.

In some aspects, the UE performs the one or more other LTE idle-mode operations while the UE is not receiving the eMBMS transmission (e.g., as described in the above examples). Additionally, or alternatively, the UE may perform the one or more LTE idle-mode operations concurrently with receiving the eMBMS transmission.

Here, by aligning the performance of the one or more other LTE idle-mode operations with the period for reception of the eMBMS transmission, a single wake-up from the LTE idle-mode is needed, thereby conserving battery power and/or processing resources of the UE.

In some aspects, in order to ensure that the UE does not miss a change to system information, the UE may read system information (e.g., system information block type 1 (SIB1)) during the wake-up associated with the reception of the eMBMS transmission. Typically, the UE would receive information indicating a modification to system information during a wake-up associated with the monitoring for a page indicating an incoming call. However, since the UE may forgo one or more of these wake-ups, as described herein, the UE may not receive such information in the typical manner.

In some aspects, the UE may receive information indicating a modification to system information during the wake-up for reception of the eMBMS transmission. For example, during initial attachment to the LTE network, the UE may receive information that identifies a periodicity at which system information, associated with the LTE network, may be modified (herein referred to as a system information modification period). Here, during a given system information modification period, a system information change that is to be implemented during an upcoming (e.g., next) system information modification period may be signaled (e.g., in SIB1) by the LTE network. Here, based at least in part on the information that identifies the system information modification period, the UE may identify a wake-up, associated with receiving an eMBMS transmission, that is at, near, or overlaps the end of a system information modification period. During this wake-up, the UE may read SIB1 in order to determine whether a change to system information will be implemented in an upcoming system information modification period. In some aspects, the UE may read a SIB1 at or near the end of the system information modification period (e.g., during a wake-up that coincides with a last SIB1 of the system information modification period) since the last SIB1 will reflect a modification of the system information during the system information modification period, if any. In this way, the UE may ensure that system information modifications are known to the UE, while forgoing a wake-up associated with performing page monitoring.

As indicated above,FIGS. 7A and 7Bare provided as examples. Other examples are possible and may differ from what was described with respect toFIGS. 7A and 7B.

FIG. 8is a diagram illustrating an example process800performed, for example, by a wireless communication device, in accordance with various aspects of the present disclosure. Example process800is an example where a wireless communication device (e.g., UE145,250) performs LTE and eMBMS concurrency operation.

As shown inFIG. 8, in some aspects, process800may include determining that a UE is registered for a voice-over WLAN service (block810). For example, a UE may determine the UE is registered for a voice-over WLAN service, as described above.

As further shown inFIG. 8, in some aspects, process800may include forgoing, based at least in part on determining that the UE is registered for the voice-over WLAN service, waking up (e.g., determining not to perform a wake up) to perform a LTE idle-mode operation, wherein the LTE idle-mode operation includes monitoring for a page during a paging occasion (block820). For example, the UE may forgo, based at least in part on determining that the UE is registered for the voice-over WLAN service, waking up (e.g., determine not to perform a wake up) to perform a LTE idle-mode operation, wherein the LTE idle-mode operation includes monitoring for a page during a paging occasion, as described above.

In some aspects, the UE may perform at least one other LTE idle-mode operation during a wake-up of the UE from the LTE idle-mode, wherein the wake-up is associated with receiving an eMBMS transmission. In some aspects, the at least one other LTE idle-mode operation may include an operation associated with at least one of monitoring for or measuring a neighbor cell. In some aspects, the at least one other LTE idle-mode operation may be aligned with a period for reception of the eMBMS transmission. In some aspects, the at least one other LTE idle-mode operation may be performed during a MCCH scheduling period associated with the eMBMS transmission. In some aspects, the at least one other LTE idle-mode operation may be performed during the MCCH scheduling period, associated with the eMBMS transmission, while the UE is not receiving eMBMS data.

In some aspects, the UE may be configured to read a system information block type 1 (SIB1) during a period for reception of an eMBMS transmission. In some aspects, the SIB1 may indicate whether a system information modification has occurred. In some aspects, the SIB1 may be included in a system information modification period. In some aspects, the SIB1 may be a last transmission in the system information modification period.

In some aspects, the UE may be configured to receive a transmission, associated with a voice call, via an access point associated with the voice-over WLAN service. In some aspects, the transmission, associated with the voice call, may include a session initiation protocol message.

AlthoughFIG. 8shows example blocks of process800, in some aspects, process800may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG. 8. Additionally, or alternatively, two or more of the blocks of process800may be performed in parallel.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the aspects.

As used herein, the term component is intended to be broadly construed as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software.