Independent wakeups from deep sleep for broadcast and unicast service

CROSS-REFERENCE TO RELATED APPLICATION & PRIORITY CLAIM

This application claims benefit of and priority to U.S. Provisional Patent Application Ser. No. 62/405,175, filed Oct. 6, 2016, which is herein incorporated by reference in its entirety for all applicable purposes.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and, more particularly, to adjusting how certain types of devices wake up and/or stay awake for broadcast service.

DESCRIPTION OF RELATED ART

Wireless communication systems are widely deployed to provide various types of communication content such as voice, data, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth and transmit power). Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE)/LTE-Advanced (LTE-A) systems and orthogonal frequency division multiple access (OFDMA) systems.

Generally, a wireless multiple-access communication system can simultaneously support communication for multiple wireless terminals. Each terminal communicates with one or more base stations via transmissions on the forward and reverse links. The forward link (or downlink) refers to the communication link from the base stations (e.g., Node B (NB), evolved Node B (eNB), access point (AP), base station transceiver (BST), transmission reception point (TRP), next generation NB (gNB), etc.,) to the terminals, and the reverse link (or uplink) refers to the communication link from the terminals to the BSs. This communication link may be established via a single-input single-output, multiple-input single-output or a multiple-input multiple-output (MIMO) system.

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, national, regional, and even global level. An example of an emerging telecommunication standard is NR, for example, 5G radio access. NR is a set of enhancements to the LTE mobile standard promulgated by Third Generation Partnership Project (3GPP). It is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) as well as support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE and NR technology. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

The systems, methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure as expressed by the claims which follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled “DETAILED DESCRIPTION” one will understand how the features of this disclosure provide advantages that include improved communications between base stations and terminals in a wireless network.

Certain aspects of the present disclosure generally relate to a method for wireless communications by a user equipment (UE). The method generally includes receiving a power savings configuration indicating sleep periods during which the UE is scheduled to be unreachable. The method includes determining at least one time, during at least a portion of one of the indicated sleep periods, for the UE to be wake in order to at least one of receive or discover Multimedia Broadcast Multicast Services (MBMS) user services.

Certain aspects of the present disclosure generally relate to an apparatus for wireless communications, such as a UE. The apparatus generally includes means for receiving a power savings configuration indicating sleep periods during which the apparatus is scheduled to be unreachable. The apparatus includes means for determining at least one time, during at least a portion of one of the indicated sleep periods, for the apparatus to be wake in order to at least one of receive or discover MBMS user services.

Certain aspects of the present disclosure generally relate to an apparatus for wireless communications, such as a UE. The apparatus generally includes a receiver configured to receive a power savings configuration indicating sleep periods during which the apparatus is scheduled to be unreachable. The apparatus includes at least one processor coupled with a memory and configured to determine at least one time, during at least a portion of one of the indicated sleep periods, for the apparatus to be wake in order to at least one of receive or discover MBMS user services.

Certain aspects of the present disclosure generally relate to a computer readable medium having computer executable code stored thereon for wireless communications. The computer readable medium generally includes code for receiving a power savings configuration indicating sleep periods during which the apparatus is scheduled to be unreachable. The computer readable medium includes code for determining at least one time, during at least a portion of one of the indicated sleep periods, for the apparatus to be wake in order to at least one of receive or discover MBMS user services. The phrase computer readable medium does not refer to a transitory propagating signal. Rather, the computer readable medium may be a non-transitory computer readable medium.

Aspects generally include methods, apparatus, systems, computer program products, and processing systems, as substantially described herein with reference to and as illustrated by the accompanying drawings.

Other aspects, features, and embodiments of the present invention will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, exemplary aspects of the present invention in conjunction with the accompanying figures. While features of the present disclosure may be discussed relative to certain aspects and figures below, all embodiments of the present disclosure can include one or more of the advantageous features discussed herein. In other words, while one or more aspects may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various aspects of the disclosure discussed herein. In similar fashion, while exemplary aspects may be discussed below as device, system, or method aspects it should be understood that such exemplary aspects can be implemented in various devices, systems, and methods.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. The appended drawings illustrate only certain typical aspects of this disclosure, however, and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an example of a wireless communication network, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 2</figref> shows a block diagram conceptually illustrating an example of a base station (BS) in communication with a user equipment (UE) in a wireless communications network, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram conceptually illustrating an example of a frame structure in a wireless communications network, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram conceptually illustrating two exemplary subframe formats with the normal cyclic prefix.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates various components that may be utilized in a wireless device, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates an example logical architecture of a distributed radio access network (RAN), in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 7</figref> illustrates an example physical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 8</figref> is a diagram illustrating an example of a downlink (DL)-centric subframe, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 9</figref> is a diagram illustrating an example of an uplink (UL)-centric subframe, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 10</figref> illustrates example operations performed by a UE for wireless communications, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 11</figref> illustrates an example broadcast service timeline, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 12</figref> illustrates an example user service broadcast timeline for event-based wakeup, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 13</figref> illustrates an example repeated content broadcast timeline, in accordance with certain aspects of the present disclosure.

<figref idref="DRAWINGS">FIG. 14</figref> illustrates an example timeline for wakeups, in accordance with certain aspects of the present disclosure.

To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one embodiment may be beneficially utilized on other embodiments without specific recitation.

DETAILED DESCRIPTION

Aspects of the present disclosure provide techniques that may help ensure that UEs receiving a same broadcast user service (e.g., Multimedia Multicast Broadcast Service (MBMS)) to be awake at relatively the same time(s) to receive the broadcast data. Techniques provided herein allow a UE to determine time to be awake, even during periods indicated as sleep periods (in which the UE is scheduled to be unreachable) by a power save configuration to receive or discover the broadcast data.

The techniques described herein may be used for various wireless communication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms “network” and “system” are often used interchangeably. A CDMA network may implement a radio technology such as universal terrestrial radio access (UTRA), cdma2000, etc. UTRA includes wideband CDMA (WCDMA), time division synchronous CDMA (TD-SCDMA), and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as global system for mobile communications (GSM). An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA), ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, etc. UTRA and E-UTRA are part of universal mobile telecommunication system (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A), in both frequency division duplex (FDD) and time division duplex (TDD), are new 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 radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE/LTE-Advanced, and LTE/LTE-Advanced terminology is used in much of the description below. LTE and LTE-A are referred to generally as LTE.

Some examples of UEs may include cellular phones, smart phones, personal digital assistants (PDAs), wireless modems, handheld devices, tablets, laptop computers, netbooks, smartbooks, ultrabooks, medical device or equipment, biometric sensors/devices, wearable devices (smart watches, smart clothing, smart glasses, smart wrist bands, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, smart meters/sensors, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, such as sensors, meters, monitors, location tags, etc., that may communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link.

It is noted that while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later.

Example Wireless Communications Network

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an example wireless communication network <b>100</b>, in which aspects of the present disclosure may be practiced. For example, one or more UEs <b>120</b> may be configured to determine times to be awake to receive or discover Multimedia Broadcast Multicast Services (MBMS) user services in accordance with aspects of the present disclosure.

The wireless communication network <b>100</b> may be an LTE network or some other wireless network. Wireless communication network <b>100</b> may include a number of base stations (BSs) <b>110</b> and other network entities. A BS is an entity that communicates with user equipments (UEs) and may also be referred to as a Node B, evolved NB (eNB), a next generation NB (gNB), an access point (AP), new radio (NR) BS, 5G BS, etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used.

A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in <figref idref="DRAWINGS">FIG. 1</figref>, a BS <b>110</b><i>a </i>may be a macro BS for a macro cell <b>102</b><i>a, </i>a BS <b>110</b><i>b </i>may be a pico BS for a pico cell <b>102</b><i>b, </i>and a BS <b>110</b><i>c </i>may be a femto BS for a femto cell <b>102</b><i>c. </i>A BS may support one or multiple (e.g., three) cells. The terms “eNB”, “base station” and “cell” may be used interchangeably herein.

Wireless communication network <b>100</b> may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in <figref idref="DRAWINGS">FIG. 1</figref>, a relay station <b>110</b><i>d </i>may communicate with macro BS <b>110</b><i>a </i>and a UE <b>120</b><i>d </i>in order to facilitate communication between BS <b>110</b><i>a </i>and UE <b>120</b><i>d. </i>A relay station may also be referred to as a relay BS, a relay, etc.

Wireless communication network <b>100</b> may be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in wireless communication network <b>100</b>. For example, macro BSs may have a high transmit power level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 Watts).

A network controller <b>130</b> may couple to a set of BSs and may provide coordination and control for these BSs. Network controller <b>130</b> may communicate with the BSs via a backhaul. The BSs may also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.

UEs <b>120</b> (e.g., <b>120</b><i>a, </i><b>120</b><i>b, </i><b>120</b><i>c</i>) may be dispersed throughout wireless communication network <b>100</b>, and each UE may be stationary or mobile. A UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc. A UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, etc. In <figref idref="DRAWINGS">FIG. 1</figref>, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. A dashed line with double arrows indicates potentially interfering transmissions between a UE and a BS.

<figref idref="DRAWINGS">FIG. 2</figref> shows a block diagram of a design of BS <b>110</b> and UE <b>120</b>, which may be one of the BSs and one of the UEs in <figref idref="DRAWINGS">FIG. 1</figref>. BS <b>110</b> may be equipped with T antennas <b>234</b><i>a </i>through <b>234</b><i>t, </i>and UE <b>120</b> may be equipped with R antennas <b>252</b><i>a </i>through <b>252</b><i>r, </i>where in general T≧1 and R≧1.

At BS <b>110</b>, a transmit processor <b>220</b> may receive data from a data source <b>212</b> for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based on channel quality information (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor <b>220</b> may also process system information (e.g., for static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols. Processor <b>220</b> may also generate reference symbols for reference signals (e.g., the CRS) and synchronization signals (e.g., the primary synchronization signal (PSS) and the secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor <b>230</b> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) <b>232</b><i>a </i>through <b>232</b><i>t. </i>Each modulator <b>232</b> may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator <b>232</b> may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators <b>232</b><i>a </i>through <b>232</b><i>t </i>may be transmitted via T antennas <b>234</b><i>a </i>through <b>234</b><i>t, </i>respectively.

At UE <b>120</b>, antennas <b>252</b><i>a </i>through <b>252</b><i>r </i>may receive the downlink signals from BS <b>110</b> and/or other BSs and may provide received signals to demodulators (DEMODs) <b>254</b><i>a </i>through <b>254</b><i>r, </i>respectively. Each demodulator <b>254</b> may condition (e.g., filter, amplify, downconvert, and digitize) its received signal to obtain input samples. Each demodulator <b>254</b> may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector <b>256</b> may obtain received symbols from all R demodulators <b>254</b><i>a </i>through <b>254</b><i>r, </i>perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor <b>258</b> may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE <b>120</b> to a data sink <b>260</b>, and provide decoded control information and system information to a controller/processor <b>280</b>. A channel processor may determine reference signal receive power (RSRP), receive signal strength indicator (RSSI), receive signal receive quality (RSRQ), CQI, interference feedback Rnn, etc.

On the uplink, at UE <b>120</b>, a transmit processor <b>264</b> may receive and process data from a data source <b>262</b> and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, etc.) from controller/processor <b>280</b>. Processor <b>264</b> may also generate reference symbols for one or more reference signals. The symbols from transmit processor <b>264</b> may be precoded by a TX MIMO processor <b>266</b> if applicable, further processed by modulators <b>254</b><i>a </i>through <b>254</b><i>r </i>(e.g., for SC-FDM, OFDM, etc.), and transmitted to BS <b>110</b>. At BS <b>110</b>, the uplink signals from UE <b>120</b> and other UEs may be received by antennas <b>234</b> , processed by demodulators <b>232</b>, detected by a MIMO detector <b>236</b> if applicable, and further processed by a receive processor <b>238</b> to obtain decoded data and control information sent by UE <b>120</b>. Processor <b>238</b> may provide the decoded data to a data sink <b>239</b> and the decoded control information to controller/processor <b>240</b>. BS <b>110</b> may include communication unit <b>244</b> and communicate to network controller <b>130</b> via communication unit <b>244</b>. Network controller <b>130</b> may include communication unit <b>294</b>, controller/processor <b>290</b>, and memory <b>292</b>.

Controller/processor <b>280</b> may direct the operation UE <b>120</b> to perform techniques presented herein for determining independent wakeups for to receive or discover broadcast data (e.g., in accordance with the operations shown in <figref idref="DRAWINGS">FIG. 10</figref>).

Memories <b>242</b> and <b>282</b> may store data and program codes for BS <b>110</b> and UE <b>120</b>, respectively. A scheduler <b>246</b> may schedule UEs for data transmission on the downlink and/or uplink.

<figref idref="DRAWINGS">FIG. 3</figref> shows an exemplary frame structure <b>300</b> for frequency division duplexing (FDD) in LTE. The transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 milliseconds (ms)) and may be partitioned into 10 subframes (e.g., 1 ms subframes) with indices of 0 through 9. Each subframe may include two slots. Each radio frame may thus include 20 slots with indices of 0 through 19. Each slot may include L symbol periods, e.g., seven symbol periods for a normal cyclic prefix (as shown in <figref idref="DRAWINGS">FIG. 3</figref>) or six symbol periods for an extended cyclic prefix. The 2L symbol periods in each subframe may be assigned indices of 0 through 2L−0.

In LTE, a BS may transmit a PSS and a SSS on the downlink in the center of the system bandwidth for each cell supported by the BS. The PSS and SSS may be transmitted in symbol periods 6 and 5, respectively, in subframes 0 and 5 of each radio frame with the normal cyclic prefix, as shown in <figref idref="DRAWINGS">FIG. 3</figref>. The PSS and SSS may be used by UEs for cell search and acquisition. The BS may transmit a cell-specific reference signal (CRS) across the system bandwidth for each cell supported by the BS. The CRS may be transmitted in certain symbol periods of each subframe and may be used by the UEs to perform channel estimation, channel quality measurement, and/or other functions. The BS may also transmit a physical broadcast channel (PBCH) in symbol periods 0 to 3 in slot 1 of certain radio frames. The PBCH may carry some system information. The BS may transmit other system information such as system information blocks (SIBs) on a physical downlink shared channel (PDSCH) in certain subframes. The BS may transmit control information/data on a physical downlink control channel (PDCCH) in the first B symbol periods of a subframe, where B may be configurable for each subframe. The BS may transmit traffic data and/or other data on the PDSCH in the remaining symbol periods of each subframe. In aspects, a serving cell and one or more neighbor cells are synchronous, such that SSS for the serving and the one or more neighbor cells may interfere.

<figref idref="DRAWINGS">FIG. 4</figref> shows two exemplary subframe formats <b>410</b> and <b>420</b> with the normal cyclic prefix. The available time frequency resources may be partitioned into resource blocks (RBs). Each RB may cover 12 subcarriers in one slot and may include a number of resource elements (REs). Each 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.

Subframe format <b>410</b> may be used for two antennas. A cell-specific reference signal (CRS) may be transmitted from antennas 0 and 1 in symbol periods 0, 4, 7 and 11. A reference signal is a signal that is known a priori by a transmitter and a receiver and may also be referred to as pilot. A CRS is a reference signal that is specific for a cell, for example, generated based on a cell identity (ID). In <figref idref="DRAWINGS">FIG. 4</figref>, for a given RE with label Ra, a modulation symbol may be transmitted on that RE from antenna a, and no modulation symbols may be transmitted on that resource element from other antennas. Subframe format <b>420</b> may be used with four antennas. A CRS may be transmitted from antennas 0 and 1 in symbol periods 0, 4, 7 and 11 and from antennas 2 and 3 in symbol periods 1 and 8. For both subframe formats <b>410</b> and <b>420</b>, a CRS may be transmitted on evenly spaced subcarriers, which may be determined based on cell ID. CRSs may be transmitted on the same or different subcarriers, depending on their cell IDs. For both subframe formats <b>410</b> and <b>420</b>, resource elements not used for the CRS may be used to transmit data (e.g., traffic data, control data, and/or other data).

The PSS, SSS, CRS and PBCH in LTE are described in 3GPP TS 36.211, entitled “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation,” which is publicly available.

An interlace structure may be used for each of the downlink and uplink for FDD in LTE. For example, Q interlaces with indices of 0 through Q−1 may be defined, where Q may be equal to 4, 6, 8, 10, or some other value. Each interlace may include subframes that are spaced apart by Q frames. In particular, interlace q may include subframes q, q+Q, q+2Q, etc., where q∈{0, . . . , Q−1}.

The wireless communication network may support hybrid automatic retransmission request (HARQ) for data transmission on the downlink and uplink. For HARQ, a transmitter (e.g., a BS) may send one or more transmissions of a packet until the packet is decoded correctly by a receiver (e.g., a UE) or some other termination condition is encountered. For synchronous HARQ, all transmissions of the packet may be sent in subframes of a single interlace. For asynchronous HARQ, each transmission of the packet may be sent in any subframe.

A UE may be located within the coverage of multiple BSs. One of these BSs may be selected to serve the UE. The serving BS may be selected based on various criteria such as received signal strength, received signal quality, pathloss, etc. Received signal quality may be quantified by a signal-to-noise-and-interference ratio (SINR), or a reference signal received quality (RSRQ), or some other metric. The UE may operate in a dominant interference scenario in which the UE may observe high interference from one or more interfering BSs.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates various components that may be utilized in a wireless device <b>502</b> that may be employed within the wireless communication system <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref>. The wireless device <b>502</b> is an example of a device that may be configured to implement the various methods described herein. The wireless device <b>502</b> may be any of the wireless nodes (e.g., UEs <b>120</b>). For example, the wireless device <b>502</b> may be configured to perform operations and techniques illustrated in <figref idref="DRAWINGS">FIG. 10</figref> as well as other operations described herein.

The wireless device <b>502</b> may include a processor <b>504</b> that controls operation of the wireless device <b>502</b>. The processor <b>504</b> may also be referred to as a central processing unit (CPU). Memory <b>506</b>, which may include both read-only memory (ROM) and random access memory (RAM), provides instructions and data to the processor <b>504</b>. A portion of the memory <b>506</b> may also include non-volatile random access memory (NVRAM). The processor <b>504</b> typically performs logical and arithmetic operations based on program instructions stored within the memory <b>506</b>. The instructions in the memory <b>506</b> may be executable to implement the methods described herein. Some non-limiting examples of the processor <b>504</b> may include Snapdragon processor, application specific integrated circuits (ASICs), programmable logic, etc.

The wireless device <b>502</b> may also include a housing <b>508</b> that may include a transmitter <b>510</b> and a receiver <b>512</b> to allow transmission and reception of data between the wireless device <b>502</b> and a remote location. The transmitter <b>510</b> and receiver <b>512</b> may be combined into a transceiver <b>514</b>. A single transmit antenna or a plurality of transmit antennas <b>516</b> may be attached to the housing <b>508</b> and electrically coupled to the transceiver <b>514</b>. The wireless device <b>502</b> may also include (not shown) multiple transmitters, multiple receivers, and multiple transceivers. The wireless device <b>502</b> can also include wireless battery charging equipment.

The wireless device <b>502</b> may also include a signal detector <b>518</b> that may be used in an effort to detect and quantify the level of signals received by the transceiver <b>514</b>. The signal detector <b>518</b> may detect such signals as total energy, energy per subcarrier per symbol, power spectral density and other signals. The wireless device <b>302</b> may also include a digital signal processor (DSP) <b>520</b> for use in processing signals.

The various components of the wireless device <b>502</b> may be coupled together by a bus system <b>522</b>, which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus. The processor <b>504</b> may be configured to access instructions stored in the memory <b>506</b> to perform beam refinement with aspects of the present disclosure discussed below.

Example NR/5G RAN Architecture

While aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communications systems, such as NR or 5G technologies.

New radio (NR) may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP)). NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD. NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 27 GHz or beyond), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC) service.

A single component carrier bandwidth of 100 MHz may be supported. NR RBs may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration. Each radio frame may consist of 2 half frames, each half frame consisting of 5 subframes, with a length of 10 ms. Consequently, each subframe may have a length of 1 ms. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. UL and DL subframes for NR may be as described in more detail below with respect to <figref idref="DRAWINGS">FIGS. 8 and 9</figref>.

Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells. Alternatively, NR may support a different air interface, other than an OFDM-based interface. NR networks may include entities such central units or distributed units

The RAN may include a central unit (CU) and distributed units (DUs). A NR BS (e.g., gNB, 5G Node B, Node B, transmission reception point (TRP), access point (AP)) may correspond to one or multiple BSs. NR cells can be configured as access cells (ACells) or data only cells (DCells). For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals—in some case cases DCells may transmit SS. NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates an example logical architecture of a distributed RAN <b>600</b>, according to aspects of the present disclosure. A 5G access node <b>606</b> may include an access node controller (ANC) <b>602</b>. The ANC <b>602</b> may be a central unit (CU) of the distributed RAN <b>600</b>. The backhaul interface to the next generation core network (NG-CN) <b>604</b> may terminate at the ANC <b>602</b>. The backhaul interface to neighboring next generation access nodes (NG-ANs) <b>610</b> may terminate at the ANC <b>602</b>. The ANC <b>602</b> may include one or more TRPs <b>608</b> (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term). As described above, a TRP may be used interchangeably with “cell.”

The TRPs <b>608</b> may be a distributed unit (DU). The TRPs may be connected to one ANC (ANC <b>602</b>) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, the TRP <b>608</b> may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.

The logical architecture may support fronthauling solutions across different deployment types. For example, the logical architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). The logical architecture may share features and/or components with LTE. The NG-AN <b>610</b> may support dual connectivity with NR. The NG-AN <b>610</b> may share a common fronthaul for LTE and NR. The logical architecture may enable cooperation between and among TRPs <b>608</b>. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC <b>602</b>. No inter-TRP interface may be present. The logical architecture may support a dynamic configuration of split logical function. The PDCP, RLC, and/or MAC protocols may be adaptably placed at the ANC <b>602</b> or TRP <b>608</b>.

A BS may include a central unit (CU) (e.g., ANC <b>602</b>) and/or one or more distributed units (e.g., one or more TRPs <b>608</b>).

<figref idref="DRAWINGS">FIG. 7</figref> illustrates an example physical architecture of a distributed RAN <b>700</b>, according to aspects of the present disclosure. A centralized core network unit (C-CU) <b>702</b> may host core network functions. The C-CU <b>702</b> may be centrally deployed. C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity.

A centralized RAN unit (C-RU) <b>704</b> may host one or more ANC functions. Optionally, the C-RU <b>704</b> may host core network functions locally. The C-RU <b>704</b> may have distributed deployment. The C-RU <b>704</b> may be close to the network edge.

A DU <b>706</b> may host one or more TRPs. The DU may be located at edges of the network with radio frequency (RF) functionality.

<figref idref="DRAWINGS">FIG. 8</figref> is a diagram showing an example of a DL-centric subframe <b>800</b>. The DL-centric subframe <b>800</b> may include a control portion <b>802</b>. The control portion <b>802</b> may exist in the initial or beginning portion of the DL-centric subframe <b>800</b>. The control portion <b>802</b> may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe <b>800</b>. The control portion <b>802</b> may be a physical DL control channel (PDCCH), as shown in <figref idref="DRAWINGS">FIG. 8</figref>. The DL-centric subframe <b>800</b> may also include a DL data portion <b>804</b>. The DL data portion <b>804</b> may be referred to as the payload of the DL-centric subframe <b>800</b>. The DL data portion <b>804</b> may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE). The DL data portion <b>804</b> may be a physical DL shared channel (PDSCH).

The DL-centric subframe <b>800</b> may also include a common UL portion <b>806</b>. The common UL portion <b>806</b> may be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion <b>806</b> may include feedback information corresponding to various other portions of the DL-centric subframe <b>800</b>. For example, the common UL portion <b>806</b> may include feedback information corresponding to the control portion <b>802</b>. Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion <b>806</b> may include additional or alternative information, such as information pertaining to RACH procedures, scheduling requests (SRs), and various other suitable types of information. As illustrated in <figref idref="DRAWINGS">FIG. 8</figref>, the end of the DL data portion <b>804</b> may be separated in time from the beginning of the common UL portion <b>806</b>. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., UE)). One of ordinary skill in the art will understand that the foregoing is merely one example of a DL-centric subframe <b>800</b> and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

<figref idref="DRAWINGS">FIG. 9</figref> is a diagram showing an example of an UL-centric subframe <b>900</b>. The UL-centric subframe <b>900</b> may include a control portion <b>902</b>. The control portion <b>902</b> may exist in the initial or beginning portion of the UL-centric subframe <b>900</b>. The control portion <b>902</b> in <figref idref="DRAWINGS">FIG. 9</figref> may be similar to the control portion <b>802</b> described above with reference to <figref idref="DRAWINGS">FIG. 8</figref>. The UL-centric subframe <b>900</b> may also include an UL data portion <b>904</b>. The UL data portion <b>904</b> may be referred to as the payload of the UL-centric subframe <b>900</b>. The UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS). The control portion <b>902</b> may be a physical downlink control channel (PDCCH).

As illustrated in <figref idref="DRAWINGS">FIG. 9</figref>, the end of the control portion <b>902</b> may be separated in time from the beginning of the UL data portion <b>904</b>. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity). The UL-centric subframe <b>900</b> may also include a common UL portion <b>906</b>. The common UL portion <b>906</b> in <figref idref="DRAWINGS">FIG. 9</figref> may be similar to the common UL portion <b>806</b> described above with reference to <figref idref="DRAWINGS">FIG. 8</figref>. The common UL portion <b>906</b> may additional or alternative include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information. One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.

In some circumstances, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE<b>1</b>) to another subordinate entity (e.g., UE<b>2</b>) without relaying that communication through the scheduling entity (e.g., UE or BS), even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum)

Example Independent Wakeups from Deep Sleep for Broadcast and Unicast Service

In the context of machine type communications (MTC) and Internet of Things (IoT) communications, user equipments (UEs) (e.g., such as a UE <b>120</b>) may use power saving functions in which the UEs go to deep sleep (e.g., not follow any access stratum procedure). As a result, these UEs may become unreachable to the network, for very long times (e.g., tens of minutes, hours, or even days). Examples of these power savings functions include extended idle mode discontinuous reception (eDRX) and power saving mode (PSM).

These functions have the following common characteristics: both are designed for UEs to have wakeup time windows (e.g., the paging time window (PTW) for eDRX, or the pTAU connected+active time) in a statistically distributed manner. Both of these solutions were designed for unicast service, where it is better in terms of resource utilization distribution that devices wake up at different times. However, in the case of Multimedia Broadcast Multicast Services (MBMS), it is better for all UEs to be awake at roughly the same time for broadcast delivery. MBMS is not effective if all UEs wake up at different times. In NB-IoT and/or MTC, many devices in these modes may be highly unreachable for a long time. For example, in eDRX a UE may be unreachable for up to a few hours. Even worse, for PSM, maximum unreachability may be up to ˜10 days, for example. This means potentially large delays for reconfiguration/service announcement. In particular broadcast service announcement may need to be repeated for a very long duration of time.

Aspects of the present disclosure, however, provide techniques for UEs receiving a same broadcast user service to be awake at relatively the same time (or times) to receive, or discover, the broadcast data. For example, the UE can determine times to be awake even when the power savings configuration indicates for the UE to be in a sleep mode. The time intervals the UE stays awake to receive MBMS service or to discover if there is any MBMS service requested to be received by an application scheduled for delivery, to be different from the wakeup intervals negotiated for eDRX or PSM.

Aspects of the present disclosure may allow reuse of existing multicast/broadcast architecture in networks that allow devices to enter deep sleep modes. The techniques may allow such devices to receive traffic on multicast/broadcast. The traffic may include a message for the group of UEs (e.g. device triggering to report) and/or a software update for the group of UEs, for example. Aspects of the present disclosure may help promote successful delivery of downlink data via MBMS bearer(s) by helping ensure a group of UEs in the group are awake and ready to receive MBMS traffic at that time. As will be described below, aspects of the present disclosure allow UEs to know when they should not be in a deep sleep (e.g., when they should wake from a deep sleep or stay awake rather than enter a deep sleep) in order receive or discover the broadcast data/traffic.

<figref idref="DRAWINGS">FIG. 10</figref> illustrates example operations <b>1000</b> that may be performed by a UE, such as a UE <b>120</b>, in accordance with aspects of the present disclosure. At <b>1002</b>, the UE (e.g., a receiver at the UE, which may include the antennas <b>252</b>, demodulators <b>254</b>, MIMO detector <b>256</b>, receive processor <b>258</b>, controller/processor <b>280</b>, and/or data sink <b>260</b> and/or the receiver <b>512</b>) receives a power savings configuration indicating sleep periods during which the UE is scheduled to be unreachable (e.g., for paging and/or mobile terminal unicast service).

At <b>1004</b>, the UE (e.g., at least one processor at the UE, such as the controller/processor <b>280</b> or the processor <b>504</b>, that is coupled with a memory at the UE such as memory <b>282</b> or memory <b>506</b>) determines at least one time, during at least a portion of one of the indicated sleep periods, when the UE is to be awake in order to at least one of receive or discover MBMS user services.

According to certain aspects, the UE (e.g., the controller/processor <b>280</b>) determines at least another time for the UE to be awake in order to receive and/or discover MBMS user services and performs (e.g., the receiver and/or the processor) defined connected mode procedures to receive or discover the MBMS user services if the UE is in a connected mode when the at least another time for the UE to be awake occurs. The UE (e.g. the receiver and/or the processor) perform defined idle mode procedures to receive or discover the MBMS user services if the UE is in an idle mode and reachable when the at least one time for the UE to be awake occurs. The UE (e.g., the processor) enters a sleep mode after receiving or discovering the MBMS user services if the UE is scheduled to be unreachable when the at least one time for the UE to be awake occurs.

According to certain aspects, based on a type of the MBMS user service, the UE (e.g., the processor) refrains from updating a Mobility Management Entity (MME) to enter a connected mode and receives or discovers (e.g., via the receiver) the MBMS user services while in an idle mode or enters a connected mode to receive or discover the MBMS user services.

According to certain aspects, the UE (e.g., the processor) remains awake during the at least one time for the UE to be awake if the UE is participating in an MBMS data transfer (e.g., via the receiver) when the at least one time for the UE to be awake occurs. The UE (e.g., the processor) remains awake after an MBMS data transfer if a duration between the MBMS data transfer and the at least one time for the UE to be awake is less than a threshold value. For example, the UE (e.g., the processor) does not enter a scheduled sleep period and continues an MBMS Broadcast session after completion of the MBMS data transfer. The UE (e.g., the processor) enters sleep modes during the indicated sleep periods according to the power savings configuration if the UE is not aware of a scheduled MBMS Broadcast session or ongoing MBMS data transfer during the indicated sleep period.

According to certain aspects, the UE (e.g., the processor) wakes up at to receive (e.g., via the receiver) MBMS service announcements that advertise the MBMS user services. The UE (e.g., the processor) determines the at least one time for the UE to be awake based on the MBMS service announcements. The MBMS data may be delivered in a file comprising multiple fragments. In this case, the UE (e.g., the processor) remains awake until all fragments of the file are received (e.g., via the receiver). The UE may receive (e.g., via the receiver) a schedule of the multiple fragments and decide (e.g., by the processor) whether to remain awake or enter a sleep mode in between scheduled fragments.

According to certain aspects, a UE wakeup time interval (including times a UE awakens from sleep as well as times a UE stays awake when already awake) for MBMS service may not coincide with the wakeup time windows indicated by an eDRX (PTW) and/or PSM (periodic TAU+active time) configuration. <figref idref="DRAWINGS">FIG. 11</figref> illustrates how configured wakeup time windows may not allow a UE to receive MBMS transmissions. For example, as shown in <figref idref="DRAWINGS">FIG. 11</figref>, UE<b>1</b> is awake from t<b>1</b> until t<b>5</b>. During the period between t<b>1</b> and t<b>5</b>, UE<b>1</b> receive the two MBMS data transfers starting at t<b>3</b> and t<b>4</b> of the MBMS service <b>1</b>, session <b>1</b>; however, the UE<b>1</b> goes to sleep before receiving the third data transfer starting at t<b>6</b> for the MBMS service <b>1</b>, session <b>2</b>. UE<b>2</b>, on the other hand, wakes up at t<b>2</b> and goes to sleep at t<b>7</b> and, therefore, is able to receive all three MBMS data transfers starting at t<b>3</b>, t<b>4</b>, and t<b>6</b>. As illustrated in <figref idref="DRAWINGS">FIG. 11</figref>, a broadcast service announcement announces the occurrence of broadcast services and may be designed to reach all UEs while they are awake.

Aspects of the present disclosure allow the UE “wakeups” due to MBMS user service to be relatively independent of the UE “wakeup intervals for unicast service”. The “wakeup intervals for unicast service” may correspond to periods when the UE becomes reachable (e.g. due to PTW in eDRX or trigger to connect or due to periodic TAU timer expiration) plus active time once in idle mode. In other words, aspects of the present disclosure recognize that there are times for the UE to be awake for receiving or discovering MBMS user services that may not coincide with the UE already being reachable for unicast service (i.e., times when the UE is configured with a sleep period).

Aspects of the present disclosure address various cases. For example, in one case, the MBMS broadcast (e.g., time for the UE to be awake to discover MBMS service or receive an MBMS data transfer) may coincide (e.g., occur when) with the UE already being in connected mode due to other reasons. In this case, the UE may follow normal connected mode procedures to receive and/or discover the MBMS broadcast.

In another case, the MBMS broadcast may coincide with the UE already being in idle mode and reachable (e.g. in configured active time for PSM or PTW for eDRX). In this case, the UE may follow normal idle mode procedure.

In another case, the MBMS broadcast may coincide with the UE being in idle mode and in deep sleep, and therefore, unreachable for paging to the network. In this case, the UE may leave the deep sleep (e.g., wake up) to discover and/or receive MBMS user service. As shown in <figref idref="DRAWINGS">FIG. 12</figref>, the UE<b>1</b> goes to deep sleep at t<b>1</b> after the PTW. Although the deep sleep, in the example shown in <figref idref="DRAWINGS">FIG. 12</figref>, is configured to end at t<b>4</b>, the UE <b>1</b> wakes up from t<b>2</b> to t<b>3</b> for MBMS session to receive the data transfer.

Some MBMS user services can be received in the idle mode. For these services, the idle mode UE may not transition to the connected mode to receive the MBMS user service. In that case, the UE may not update the mobile management entity (MME) to enter the connect mode to become reachable for paging. In other words, the UE is still considered unreachable for paging in the MME. This approach may help minimize the signaling between the UE and the network.

On the other hand, some MBMS user services (e.g. for HTTP reception reporting, file repair, etc.) are received in the connected mode. Thus, the idle mode UE transitions to the connected mode and then the UE may perform regular procedures to be in EPS connection management (ECM) connected mode and become reachable.

In another case, if the UE is participating in an ongoing MBMS data transfer and the UE is scheduled (e.g., by the power save configuration) to move to a deep sleep mode/state due to power saving (e.g., end of PTW for eDRX or expiration of active time for PSM), then the UE does not go to deep sleep during the remainder of the MBMS data transfer, even during scheduled sleep period. As shown in <figref idref="DRAWINGS">FIG. 12</figref>, the UE <b>2</b> PTW coincides with the MBMS broadcast session at t<b>2</b> and, thus, the UE <b>2</b> remains awake until the end of the MBMS broadcast session at t<b>3</b>. If at the end of MBMS data transfer, the UE knows if there is another MBMS data transfer scheduled soon, in that case depending of the time between MBMS data transfers, the UE may not go to sleep between MBMS data transfers. Thus, the UE may in fact not go to deep sleep while in an MBMS Broadcast session. For example, if the time between the data transfers is short, the UE remains awake. If the time between data transfers is longer (e.g., greater than a threshold duration), then the UE may return to a sleep mode between the data transfers.

There are various aspects for determining the UE wakeup time intervals for MBMS service. For event-based wakeup for MBMS user service, each UE follows regular wakeups (e.g., according to the eDRX or PSM configuration) except when the UE is aware of a scheduled MBMS Broadcast session. For example, the UE may discover a scheduled or ongoing MBMS Broadcast session for which an application has requested reception while in one of the regular wakeups for eDRX/PSM. Since the service delay may be dictated by the eDRX or PSM parameters, a UE receiving this type of broadcast service may be configured by the application server delivering the MBMS broadcast content with a maximum sleep cycle time. The UE adjusts either the requested eDRX cycle length or requested pTAU timer in the NAS attach/TAU request accordingly.

For event-based wakeup with service announcement reception, before start of MBMS Broadcast may be provided to UEs either via MBMS broadcast mode or unicast. The service announcement may be provided by MBMS Broadcast mode to advertise MBMS Broadcast user Services. For very long sleep cycles, the network broadcasts the service announcement for a very long period of time (e.g., hours for PSM), making it inefficient in terms of overhead. Other potential service announcement delivery mechanisms include, for example, a PUSH mechanism (WAP, SMS-PP, MMS) or URL (HTTP, FTP). In the URL approach, the UE may connect and fetch the configuration from the URL at a certain periodicity. File downloads may only occur every once in a while. SMS triggering may be used to notify the UEs to perform URL retrieving. A similar timeline applies to unicast service announcement.

The application server may be aware of the maximum deep sleep cycle targeted UEs have. This can be done over the top, by configuration, or received via service capability exposure function (SCEF) exposure. The time between service announcement start and the start of broadcast session should be larger than the maximum deep sleep cycle of the targeted devices.

For repeated content broadcast transmission, specific temporary mobile group identities (TMGIs) may be reserved and transmit the same content (as fragments) until all the UEs receive the full content or for a certain period of time larger than the deep sleep cycle (e.g. eDRX cycle or periodic TAU for PSM). In this case, the UE may follow the normal power cycle for unicast (eDRX and/or PSM). Once the UE wakes up, if it discovers an MBMS user service broadcast transmission that it is configured to receive, the UE may stay awake until the file is completely received.

As illustrated in <figref idref="DRAWINGS">FIG. 13</figref>, the UE<b>1</b> and UE<b>2</b> receives the MBMS broadcast data files in fragments. The UEs can decide whether to stay awake or go to sleep in between scheduled file fragments. In the example shown in <figref idref="DRAWINGS">FIG. 13</figref>, Fr. “X” refers to the fragment number of the file being announced and broadcast. For example, in <figref idref="DRAWINGS">FIG. 13</figref>, the fragments <b>1</b>, <b>2</b>, and <b>3</b> corresponds to a data file. When the UE wakes up (e.g., due to PTW start for eDRX), the UE discovers the ongoing MBMS session, and starts receiving the fragments as soon as they are being broadcasted (in any order). Once all fragments are received (in the example, Frs. <b>1</b><b>2</b> and <b>3</b>), the UE may go back to deep sleep if the eDRX configurations indicates a sleep period for that time. This approach may have a benefit that the UE only stays awake for MBMS service during broadcast session.

For periodic wakeups, the UE wakes up periodically for potential discovery of service announcements and/or for data reception of MBMS user service. As illustrated in <figref idref="DRAWINGS">FIG. 14</figref>, a UE belonging to a group or wanting to receive a specific MBMS user service (e.g., UE <b>1</b> and UE <b>2</b>) may be configured to wake up at periodic time intervals (e.g., every day at midnight) to receive service announcements and potentially receive data. As shown in <figref idref="DRAWINGS">FIG. 14</figref>, the UE <b>1</b> and UE <b>2</b> are scheduled to wake up at periodic intervals starting at t<b>1</b> and t<b>2</b>. The time interval may contain time of wakeup and time window interval. The UE may extend its wakeup time if it is receiving MBMS (e.g. still receiving a file) at the end of the time window interval, as shown in <figref idref="DRAWINGS">FIG. 14</figref> after the wakeup interval starting at t<b>2</b>. The application server may schedule file/message delivery at those wakeup time intervals.

Periodic wakeup may have the benefit that it can be supported without further changes in the network. Further, delay for broadcast reception may be independent of unicast service delay tolerance. This may also be a relatively simple approach for application developers (to deal with one interface)

The application server or the broadcast multicast service center (BM-SC) may configure the UE to wake up for potential MBMS service at specific times (e.g., every day at a specific time, every X hours, every Monday at specific time(s), specific dates in specific month(s) at a specific time(s), etc.). The UE may also receive a specific TMGI for the MBMS user service. This TMGI is statically allocated for the particular service. The UE may follow regular wakeups indicated by eDRX or PSM configuration, with exceptions for the independent wakeups to discover or receive MBMS user services. The UE wakes up and checks MBMS control channel (MCCH). The UE may receive a service announcement. If the UE recognizes a TMGI allocated to the particular service the UE is seeking, the UE may perform MBMS reception at the scheduled MBMS Broadcast session time interval. The UE may provide an application programming interface (API) for applications to configure these wakeups. This configuration may be transparent to the core network.

As described by the various options herein, eDRX/PSM configuration and configuration of wakeups for MBMS may be independent. Aspects may improve broadcast services for UEs, such as MTC and IoT UEs configured for power savings.

As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

As used herein, the term “identifying” encompasses a wide variety of actions. For example, “identifying” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “identifying” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “identifying” may include resolving, selecting, choosing, establishing and the like.

In some cases, rather than actually communicating a frame, a device may have an interface to communicate a frame for transmission or reception. For example, a processor may output a frame, via a bus interface, to an RF front end for transmission. Similarly, rather than actually receiving a frame, a device may have an interface to obtain a frame received from another device. For example, a processor may obtain (or receive) a frame, via a bus interface, from an RF front end for transmission.

The methods disclosed herein comprise one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software/firmware component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components.

The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software/firmware component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in Figures, those operations may be performed by any suitable corresponding counterpart means-plus-function components.

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or combinations thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, software/firmware, or combinations thereof. To clearly illustrate this interchangeability of hardware and software/firmware, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software/firmware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software/firmware module executed by a processor, or in a combination thereof. A software/firmware module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, phase change memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

In one or more exemplary designs, the functions described may be implemented in hardware, software/firmware, or combinations thereof. If implemented in software/firmware, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD/DVD or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software/firmware is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.