WO2018058586A1

WO2018058586A1 - Drx command in sc-ptm environments

Info

Publication number: WO2018058586A1
Application number: PCT/CN2016/101224
Authority: WO
Inventors: Kuo-Chun Lee; Sivaramakrishna Veerepalli; Feilu Liu; Ralph Akram Gholmieh; Masato Kitazoe; Xipeng Zhu; Alberto Rico Alvarino; Hao Xu
Original assignee: Qualcomm Incorporated
Priority date: 2016-09-30
Filing date: 2016-09-30
Publication date: 2018-04-05

Abstract

A first apparatus may initiate an on-timer in response to waking from a sleep cycle of a discontinuous reception (DRX) configuration, wherein the waking from the sleep cycle starts an on-cycle of the DRX configuration. The first apparatus may receive an initial portion of broadcast content during the on-cycle of the DRX configuration. The first apparatus may initiate an inactivity-timer in response to the reception, the on-timer and the inactivity-timer each having default durations. The first apparatus may receive a subsequent portion of the broadcast content and a broadcast end command, wherein the initial portion and the subsequent portion define the entire broadcast content. The first apparatus may initiate a sleep-cycle prior to the expiration of the on-timer and the inactivity-timer default durations based on the broadcast end command.

Description

DRX COMMAND IN SC-PTM ENVIRONMENTS

BACKGROUND

Field

The present disclosure relates generally to communication systems, and more particularly, to a base station that is configured to send, to a user equipment, a command to stop one or more timers at the user equipment.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

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 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 support mobile broadband access through improved spectral efficiency, lowered costs, and improved services using OFDMA on the downlink, SC-FDMA on the uplink, and multiple-input multiple-output (MIMO) antenna technology. However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in LTE technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus be a user equipment (UE) . The apparatus may initiate an on-timer in response to waking from a sleep cycle of a discontinuous reception (DRX) configuration, wherein the waking from the sleep cycle starts an on-cycle of the DRX configuration. The apparatus may receive an initial portion of broadcast content during the on-cycle of the DRX configuration. The apparatus may initiate an inactivity-timer in response to the reception, the on-timer and the inactivity-timer each having default durations. The apparatus may receive a subsequent portion of the broadcast content and a broadcast end command, wherein the initial portion and the subsequent portion define the entire broadcast content. The apparatus may initiate a sleep-cycle prior to the expiration of the on-timer and the inactivity-timer default durations based on the broadcast end command.

In an aspect of the disclosure, a second method, a second computer-readable medium, and a second apparatus are provided. The second apparatus may transmit, to a UE, information associated with a DRX configuration, the information including at least a default duration of an on-timer associated with an on-cycle of the UE and a default duration of an inactivity-timer. The second apparatus may transmit, to the UE, an initial portion of broadcast content during the on-cycle of the DRX configuration. The second apparatus may transmit, to the UE, a subsequent portion of the broadcast content, wherein the initial portion and the subsequent portion define the entire broadcast content. The second apparatus may transmit, to the UE, a first broadcast end command, wherein the first broadcast end command is intended to cause the UE to transition to a sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration apparatus may be a base station.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIGs. 2A, 2B, 2C, and 2D are diagrams illustrating LTE examples of a DL frame structure, DL channels within the DL frame structure, an UL frame structure, and UL channels within the UL frame structure, respectively.

FIG. 3 is a diagram illustrating an example of an evolved Node B (eNB) and user equipment (UE) in an access network.

FIG. 4A is a diagram illustrating an example of Multicast Broadcast Single Frequency Network areas in an access network.

FIG. 4B is a diagram illustrating an example of an evolved Multimedia Broadcast Multicast Service channel configuration in a Multicast Broadcast Single Frequency Network.

FIG. 4C is a diagram illustrating a format of a Multicast Channel (MCH) Scheduling Information (MSI) Medium Access Control element.

FIG. 5 is a diagram of a wireless communications system.

FIG. 6 is a diagram of a wireless communications system.

FIG. 7 is a call flow diagram of a method of wireless communication.

FIG. 8 is a diagram of a wireless communications system.

FIG. 9 is a diagram of a wireless communications system.

FIG. 10 is a call flow diagram of a method of wireless communication.

FIG. 11 is a diagram of a wireless communications system.

FIG. 12 is a flowchart of a method of wireless communication.

FIG. 13 is a flowchart of a method of wireless communication.

FIG. 14 is a conceptual data flow diagram illustrating the data flow between different means/components in an exemplary apparatus.

FIG. 15 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

FIG. 16 is a conceptual data flow diagram illustrating the data flow between different means/components in an exemplary apparatus.

FIG. 17 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

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 the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, and an Evolved Packet Core (EPC) 160. The base stations 102 may include macro cells (high power cellular base station) and/or small cells (low power cellular base station) . The macro cells include eNBs. The small cells include femtocells, picocells, and microcells.

The base stations 102 (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) interface with the EPC 160 through backhaul links 132 (e.g., S1 interface) . In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160) with each other over backhaul links 134 (e.g., X2 interface) . The backhaul links 134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102'may have a coverage area 110'that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macro cells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20 MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .

The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell 102'may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102'may employ LTE and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102', employing LTE in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. LTE in an unlicensed spectrum may be referred to as LTE-unlicensed (LTE-U) , licensed assisted access (LAA) , or MuLTEfire.

The millimeter wave (mmW) base station 180 may operate in mmW frequencies and/or near mmW frequencies in communication with the UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW /near mmW radio frequency band has extremely high path loss and a short range. The mmW base station 180 may utilize beamforming 184 with the UE 182 to compensate for the extremely high path loss and short range.

The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service (PSS) , and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The base station may also be referred to as a Node B, evolved Node B (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , or some other suitable terminology. The base station 102 provides an access point to the EPC 160 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, or any other similar functioning device. The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

Referring again to FIG. 1, the UE 104 may operate according to a discontinuous reception (DRX) configuration, for example, to conserve power at the UE. According to DRX, data communication cyclically occurs at intervals. Between those intervals, the UE 104 may enter a low-power state, a “sleep-cycle, ” an off-cycle, or similar power-conservation state in which data reception by the UE is paused or suspended. The UE 104 may enter a high-power state, a “wake-up” cycle, an on-cycle, or similar state in which the UE 104 receives data, e.g., from the eNB 102. The duration of the on-cycle may be dictated by one or more timers of the UE 104. For example, the UE 104 may include an on-timer that defines the duration for which the UE 104 remains in the on-cycle, and an inactivity timer that defines duration for which the UE 104 should be remain active after successfully decoding a data. The timers may be defined by one or more technical specifications promulgated by 3GPP for wireless communication standards (e.g., LTE, LTE-A, and the like) .

The eNB 102 may be configured to transmit broadcast content to the UE 104. However, the UE 104 may be required to wait for both the on-timer and the inactivity-timer to expire before the UE 104 may enter the sleep-cycle of a DRX configuration, even after the broadcast content has ended (i.e., the eNB 102 has no further broadcast content to transmit to the UE 104) . Consequently, the UE 104 may be required to remain in an on-cycle even after data transmission to the UE 104 has ended. Accordingly, current wireless communications systems may benefit from a system or method that allows the UE 104 to enter the sleep-cycle when data transmission to the UE 104 has ended but before the on-timer and inactivity-timer of the UE 104 have expired. In certain aspects, the eNB 102 may be configured to may be configured to cause the UE 104 to transition to the sleep-cycle of the DRX configuration prior to expiration of one or more timers associated with the DRX configuration at the UE 104.

The eNB 102 may transmit, to the UE 104, information associated with the DRX configuration. This information may include at least a default duration of an on-timer associated with the on-cycle of the UE 104 and a default duration of an inactivity-timer. The UE 104 may be configured to initiate the on-timer in response to waking from a sleep-cycle of the DRX configuration. This waking may initiate the on-cycle of the DRX configuration, the duration of which may be defined by the eNB 102.

The eNB 102 may transmit, to the UE 104, an initial portion of broadcast content during an on-cycle of the DRX configuration. In aspects, the UE 104 may receive the initial portion of the broadcast content and may initiate the inactivity timer in response to the reception of the initial portion.

In aspects, each portion of the broadcast content may be packetized at different layers –e.g., a respective portion of the broadcast content may be packetized into a packet data unit (PDU) that includes a header and a data portion. Accordingly, the eNB 102 may transmit other portions of the broadcast content to the UE 104, including at least a subsequent portion such that the initial portion and the subsequent portion define the entire broadcast content. Each reception of a respective portion of the broadcast content by the UE 104 may cause the UE 104 to restart the inactivity timer.

The eNB 102 may determine that the subsequent portion (e.g., including at least a last packet) defines the entire broadcast content and therefore the UE 104 should be allowed to enter a sleep-cycle even though the on-timer and/or the inactivity-timer at the UE 104 have not yet expired. Accordingly, the eNB 102 may transmit, to the UE 104, a first broadcast end command 198 that is intended to cause the UE 104 to transition to the sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration.

The UE 104 may receive the subsequent portion of the broadcast content and the broadcast end command 198. The UE 104 may initiate the sleep-cycle prior to the expiration of the on-timer and inactivity-timer default durations based on the broadcast end command 198.

FIG. 2A is a diagram 200 illustrating an example of a DL frame structure in LTE. FIG. 2B is a diagram 230 illustrating an example of channels within the DL frame structure in LTE. FIG. 2C is a diagram 250 illustrating an example of an UL frame structure in LTE. FIG. 2D is a diagram 280 illustrating an example of channels within the UL frame structure in LTE. Other wireless communication technologies may have a different frame structure and/or different channels. In LTE, a frame (10 ms) may be divided into 10 equally sized subframes. Each subframe may include two consecutive time slots. A resource grid may be used to represent the two time slots, each time slot including one or more time concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs) ) . The resource grid is divided into multiple resource elements (REs) . In LTE, for a normal cyclic prefix, an RB contains 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols (for DL, OFDM symbols； for UL, SC-FDMA symbols) in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB contains 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry DL reference (pilot) signals (DL-RS) for channel estimation at the UE. The DL-RS may include cell-specific reference signals (CRS) (also sometimes called common RS) , UE-specific reference signals (UE-RS) , and channel state information reference signals (CSI-RS) . FIG. 2A illustrates CRS for

antenna ports

0, 1, 2, and 3 (indicated as R0, R1, R2, and R3, respectively) , UE-RS for antenna port 5 (indicated as R5) , and CSI-RS for antenna port 15 (indicated as R) . FIG. 2B illustrates an example of various channels within a DL subframe of a frame. The physical control format indicator channel (PCFICH) is within symbol 0 of slot 0, and carries a control format indicator (CFI) that indicates whether the physical downlink control channel (PDCCH) occupies 1, 2, or 3 symbols (FIG. 2B illustrates a PDCCH that occupies 3 symbols) . The PDCCH carries downlink control information (DCI) within one or more control channel elements (CCEs) , each CCE including nine RE groups (REGs) , each REG including four consecutive REs in an OFDM symbol. A UE may be configured with a UE-specific enhanced PDCCH (ePDCCH) that also carries DCI. The ePDCCH may have 2, 4, or 8 RB pairs (FIG. 2B shows two RB pairs, each subset including one RB pair) . The physical hybrid automatic repeat request (ARQ) (HARQ) indicator channel (PHICH) is also within symbol 0 of slot 0 and carries the HARQ indicator (HI) that indicates HARQ acknowledgement (ACK) /negative ACK (NACK) feedback based on the physical uplink shared channel (PUSCH) . The primary synchronization channel (PSCH) is within symbol 6 of slot 0 within

subframes

0 and 5 of a frame, and carries a primary synchronization signal (PSS) that is used by a UE to determine subframe timing and a physical layer identity. The secondary synchronization channel (SSCH) is within symbol 5 of slot 0 within

subframes

0 and 5 of a frame, and carries a secondary synchronization signal (SSS) that is used by a UE to determine a physical layer cell identity group number. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DL-RS. The physical broadcast channel (PBCH) is within

symbols

0, 1, 2, 3 of slot 1 of subframe 0 of a frame, and carries a master information block (MIB) . The MIB provides a number of RBs in the DL system bandwidth, a PHICH configuration, and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.

As illustrated in FIG. 2C, some of the REs carry demodulation reference signals (DM-RS) for channel estimation at the eNB. The UE may additionally transmit sounding reference signals (SRS) in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by an eNB for channel quality estimation to enable frequency-dependent scheduling on the UL. FIG. 2D illustrates an example of various channels within an UL subframe of a frame. A physical random access channel (PRACH) may be within one or more subframes within a frame based on the PRACH configuration. The PRACH may include six consecutive RB pairs within a subframe. The PRACH allows the UE to perform initial system access and achieve UL synchronization. A physical uplink control channel (PUCCH) may be located on edges of the UL system bandwidth. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and HARQ ACK/NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.

FIG. 3 is a block diagram of an eNB 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting； PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions； RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs； and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then 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 eNB 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the eNB 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting； PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ； RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs； and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the eNB 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the eNB 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

FIG. 4A is a diagram 410 illustrating an example of MBSFN areas in an access network. The eNBs 412 in cells 412'may form a first MBSFN area and the eNBs 414 in cells 414'may form a second MBSFN area. The

eNBs

412, 414 may each be associated with other MBSFN areas, for example, up to a total of eight MBSFN areas. A cell within an MBSFN area may be designated a reserved cell. Reserved cells do not provide multicast/broadcast content, but are time-synchronized to the cells 412', 414'a nd may have restricted power on MBSFN resources in order to limit interference to the MBSFN areas. Each eNB in an MBSFN area synchronously transmits the same eMBMS control information and data. Each area may support broadcast, multicast, and unicast services. A unicast service is a service intended for a specific user, e.g., a voice call. A multicast service is a service that may be received by a group of users, e.g., a subscription video service. A broadcast service is a service that may be received by all users, e.g., a news broadcast. Referring to FIG. 4A, the first MBSFN area may support a first eMBMS broadcast service, such as by providing a particular news broadcast to UE 425. The second MBSFN area may support a second eMBMS broadcast service, such as by providing a different news broadcast to UE 420.

FIG. 4B is a diagram 430 illustrating an example of an eMBMS channel configuration in an MBSFN. As shown in FIG 4B, each MBSFN area supports one or more physical multicast channels (PMCH) (e.g., 15 PMCHs) . Each PMCH corresponds to an MCH. Each MCH can multiplex a plurality (e.g., 29) of multicast logical channels. Each MBSFN area may have one multicast control channel (MCCH) . As such, one MCH may multiplex one MCCH and a plurality of multicast traffic channels (MTCHs) and the remaining MCHs may multiplex a plurality of MTCHs.

A UE can camp on an LTE cell to discover the availability of eMBMS service access and a corresponding access stratum configuration. Initially, the UE may acquire a SIB 13 (SIB13) . Subsequently, based on the SIB13, the UE may acquire an MBSFN Area Configuration message on an MCCH. Subsequently, based on the MBSFN Area Configuration message, the UE may acquire an MSI MAC control element. The SIB13 may include (1) an MBSFN area identifier of each MBSFN area supported by the cell； (2) information for acquiring the MCCH such as an MCCH repetition period (e.g., 32, 64, …, 256 frames) , an MCCH offset (e.g., 0, 1, …, 10 frames) , an MCCH modification period (e.g., 512, 1024 frames) , a signaling modulation and coding scheme (MCS) , subframe allocation information indicating which subframes of the radio frame as indicated by repetition period and offset can transmit MCCH； and (3) an MCCH change notification configuration. There is one MBSFN Area Configuration message for each MBSFN area. The MBSFN Area Configuration message may indicate (1) a temporary mobile group identity (TMGI) and an optional session identifier of each MTCH identified by a logical channel identifier within the PMCH, and (2) allocated resources (i.e., radio frames and subframes) for transmitting each PMCH of the MBSFN area and the allocation period (e.g., 4, 8, …, 256 frames) of the allocated resources for all the PMCHs in the area, and (3) an MCH scheduling period (MSP) (e.g., 8, 16, 32, …, or 1024 radio frames) over which the MSI MAC control element is transmitted. A particular TMGI identifies a particular service of available MBMSs services.

FIG. 4C is a diagram 440 illustrating the format of an MSI MAC control element. The MSI MAC control element may be sent once each MSP. The MSI MAC control element may be sent in the first subframe of each scheduling period of the PMCH. The MSI MAC control element can indicate the stop frame and subframe of each MTCH within the PMCH. There may be one MSI per PMCH per MBSFN area. A logical channel identifier (LCID) field (e.g., LCID 1, LCID 2, …, LCID n) may indicate a logical channel identifier of the MTCH. A Stop MTCH field (e.g., Stop MTCH 1, Stop MTCH 2, …, Stop MTCH n) may indicate the last subframe carrying the MTCH corresponding to the particular LCID.

FIG. 5 is a diagram of a wireless communications system. In aspects, the base station 502 and the UE 504 may be configured for communication according to a single-cell point-to-multipoint (SC-PTM) configuration, which may allow transmission of broadcast content from the base station 502 to a group of UEs, including the UE 504. Accordingly, the base station 502 may determine a group that includes the UE 504, and the group may be associated with a group radio network temporary identifier (G-RNTI) . The G-RNTI may be used for scrambling the downlink control information (DCI) , such as to indicate a bandwidth allocation of transmitting broadcast service.

In various aspects, the base station 502 may determine a DRX configuration for a G-RNTI, for example, so that a group of UEs may wake up at the same time to receive broadcast content. The base station 502 may transmit, to the UE 504, information 540 associated with the DRX configuration. This information 540 may include at least a default duration of an on-timer associated with the on-cycle of the UE 504 and a default duration of an inactivity-timer.

In an aspect, a single-cell multicast traffic channel (SC-MTCH) may carry the information 540. In an aspect, the SC-MTCH may further carry the G-RNTI. Therefore, the UE 504 may be configured to determine the G-RNTI for the UE 504 by decoding data carried on the SC-MTCH. In an aspect, a service that the UE 504 wants to receive is granted by a downlink control information (DCI) which is scrambled using the G-RNTI.

Therefore, the UE 504 may operate according to a DRX configuration, for example, to conserve power at the UE. Thus, the UE 504 may enter a low-power state, a “sleep-cycle, ” an off-cycle, or similar power-conservation state in which data reception by the UE is paused or suspended when the UE 504 does not expect to receive broadcast content from the base station 502. Similarly, the UE 504 may enter a high-power state, a “wake-up” cycle, an on-cycle, or similar state when the UE 504 does not expect to receive broadcast content from the base station 502. The duration of the on-cycle may be dictated by the on-timer and the inactivity-timer configured in the DRX configuration. The UE 504 may be configured to initiate the on-timer in response to waking from a sleep-cycle of the DRX configuration. This waking may initiate the on-cycle of the DRX configuration.

The base station 502 may be configured to transmit broadcast content to the UE 504. In an aspect, the base station 502 may transmit the broadcast content on a PDSCH through the SC-PTM configuration. For example, the SC-MTCH and/or the single-cell multicast control channel (SC-MCCH) may be carried on the PDSCH.

The UE 504 may receive broadcast content from the base station 502, but may be required to wait for both the on-timer and the inactivity-timer to expire before the UE 504 may enter the sleep-cycle of a DRX configuration, even after the broadcast content has ended (i.e., the base station 502 has no further broadcast content to transmit to the UE 504) . Consequently, the UE 504 may be required to remain in an on-cycle even after data transmission to the UE 504 has ended. Thus, the base station 502 may be configured to may be configured to cause the UE 504 to transition to the sleep-cycle of the DRX configuration prior to expiration of one or more timers associated with the DRX configuration at the UE 504.

In an aspect, the UE 504 may initiate 520 an on-timer in response to waking from the sleep-cycle of the DRX configuration. When the UE 504 wakes from the sleep-cycle, the on-cycle of the UE 504 may be started, during which time the UE 504 may receive broadcast content from the base station 502.

The base station 502 may transmit, to the UE 504, an initial portion 542 of broadcast content during an the cycle of the DRX configuration. In aspects, the UE 504 may receive the initial portion 542 of the broadcast content and may initiate 522 the inactivity timer in response to the reception of the initial portion.

In aspects, each portion of the broadcast content may be packetized at different layers –e.g., a respective portion of the broadcast content may be packetized into a packet data unit (PDU) that includes a header and a data portion. Accordingly, the base station 502 may transmit other portions of the broadcast content to the UE 504, including at least a subsequent portion 544 such that the initial portion and the subsequent portion define the entire broadcast content. Each reception of a respective portion (e.g., a packet or MAC PDU) of the broadcast content by the UE 504 may cause the UE 504 to restart or reinitiate 522 the inactivity-timer.

The base station 502 may determine that the subsequent portion 544 (e.g., including at least a last packet) defines the entire broadcast content and therefore the UE 504 should be allowed to enter a sleep-cycle even though the on-timer and/or the inactivity-timer at the UE 504 have not yet expired. Accordingly, the base station 502 may transmit, to the UE 504, a first broadcast end command 546 that is intended to cause the UE 504 to transition to the sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration.

In an aspect, the first broadcast end command 546 may be a MAC control element (CE) included in a MAC packet data unit (PDU) . Such a PDU may carry a payload, for example, that includes a portion of the broadcast content. Therefore, The first broadcast end command 546 and the subsequent portion may be included in a same PDU. In an aspect, a MAC PDU that includes both the first broadcast end command 546 and the subsequent portion 544 may include padding in the payload. In another aspect, the first broadcast end command 546 may be included in a MAC PDU having a payload that is only padding.

Table 1 illustrates MAC subheader types in a MAC PDU. The first broadcast end command 546 may be least one MAC CE may be used for SC-PTM so that the base station 502 may send a specific G-RNTI command to one or more UEs (e.g., of a group) that is intended to cause the UE 504 to transition to the sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration. In an aspect, the first broadcast end command 546 may be indicated using an logical channel identifier (LCID) of 11110. Various LCID values may be found in one or more 3GPP Technical Specifications, such as Table 6.2.2-1 of 3GPP TS 36.321. A 3GPP TS may be updated to reflect that the DRX command MAC CE (e.g., the first broadcast end command 526) may cause a UE to stop both an on-timer and an inactivity-timer.

Index	LCID Values
00000	Common Control Channel (CCCH)
00001-01010	Identity Of The Logical Channel
01011-10111	Reserved
11000	Activation/Deactivation (4 Octets)
11001	SC-MCCH, SC-MTCH
11010	Long DRX Command
11011	Activation/Deactivation (1 Octet)
11100	UE Contention Resolution Identity
11101	Timing Advance Command
11110	DRX Command
11111	Padding

TABLE 1

The UE 504 may receive the subsequent portion 544 of the broadcast content and the broadcast end command 546. The UE 504 may initiate 524 the sleep-cycle prior to the expiration of the on-timer and inactivity-timer default durations based on the broadcast end command 546.

In various aspects, the UE 504 may lack a mechanism to acknowledge reception of the first broadcast end command 546. For example, hybrid automatic repeat request (HARQ) and RLC retransmission mechanisms are not supported by broadcast. Accordingly, the base station 502 may transmit multiple broadcast end commands in multiple subframes to increase the probability that the UE 504 receives the broadcast end command. Accordingly, the base station 502 may transmit at least a second broadcast end command intended to cause the UE 504 to transition to the sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration. The second broadcast end command may be similar to the first broadcast end command 546. In an aspect, the second broadcast end command is transmitted in a subframe that immediately follows the subframe in which the first broadcast end command 546 is transmitted. In another aspect, there is at least one gap subframe separating the subframe in which the second broadcast end command and the subframe in which the first broadcast end command 546 is transmitted.

FIG 6 illustrates a wireless communications environment 600. The wireless communications environment 600 may be an aspect of the wireless communications environment 500. SC-PTM may be an alternative to eMBMS broadcast. For example, SC-PTM may be used for mission-critical push-to-talk (MCPTT) , evolved machine-type communication (eMTC) , and or vehicle-to-entity (V2X) (e.g., V2V) . The base station 602 may employ an SC-PTM configuration in the cell 610. To deliver broadcast content to a group of

UEs

604, 606, the base station 602 may determine a G-RNTI for the

UEs

604, 606. The base station 602 may provide the G-RNTI to the

UEs

604, 606, and use the G-RNTI to scramble the downlink control information (DCI) that can allocate bandwidth to transmit broadcast content intended for the

UEs

604, 606.

In the cell 610, the PDSCH 642 may be used to broadcast data and control information to a group of

UEs

604, 606. Data of specific service may be sent on the PDSCH using the G-RNTI and control information may be sent using a single-cell radio network temporary identifier (SC-RNTI) .

In aspects, the logical channels 620 of an SC-PTM configuration may include at least the SC-MTCH 624 and the SC-MCCH 622. The logical channels 620 of the SC-PTM configuration may be carried on a downlink shared channel (DL-SCH) 632 for the transport channel 630. Further, the DL-SCH 632 may be carried on the PDSCH 642 at the physical channel 640. Accordingly, logical channels 620 of the SC-PTM configuration may be carried on the PDSCH 642.

FIG. 7 is a call flow diagram of a method 700 of wireless communication. In an aspect, a UE 704 may determine a service of interest to the UE 704. The UE 704 may indicate this service to the base station 702 using a TMGI. According to various aspects, the UE 704 may transmit, to the base station 702, an MBMS interest indication 722 that includes a TMGI.

While operating on a cell provided by the base station 702, the base station 702 may broadcast one or more system information blocks (SIBs) . At least one SIB may be a SIB20 724. The SIB20 724 may include information related to the SC-MCCH. The UE 704 may receive the SIB20 724 and determine configuration information for receiving the SC-MCCH. For example, the UE 704 may determine an SC-RNTI.

The base station 702 may transmit the SC-MCCH 726 and, based on the SIB20 724, the UE 704 may receive the SC-MCCH 726. The SC-MCCH 726 may include at least an SC-PTM configuration message. Further, the SC-MCCH 726 may indicate available TMGIs and how to receive the SC-MTCH 728. From the SC-MCCH 726, the UE 704 determine at least the G-RNTI, based on which the UE 704 may receive the SC-MTCH 728.

The base station 702 may transmit the SC-MCCH 726 and, based on the SC-MCCH 726, the UE 704 may receive the SC-MTCH 728. The SC-MTCH 728 may carry data of an MBMS service (e.g., broadcast content) of interest to the UE 704. Accordingly, the UE 704 may receive broadcast content according to an SC-PTM configuration.

In aspects, the SC-MTCH may use DRX, for example, to save power at the UE 704. A DRX configuration for an SC-MTCH may vary for different TMGIs (e.g., different services use different reception cycles) . The UE 704 may determine a DRX configuration for a TMGI of interest based on the SC-MTCH 728. For example, the UE 704 may determine default durations for an on-timer and an inactivity-timer, as well as an offset from the beginning of a DRX cycle that indicates when broadcast content associated with the TMGI is to begin. In an aspect, the on-timer and the inactivity-timer are defined in subframes of the PDCCH (psf) , while the offset is defined in subframes (sf) .

FIG. 8 is a diagram of a wireless communications system. In aspects, a DRX configuration may be implemented by the UE 504. In aspects, a DRX configuration includes cycles 808, each of which may be 320 milliseconds. During a cycle 808, the UE 504 may be in an on-state 810. While in the on-state 810, the UE 504 may receive data from the base station 502. While not in the on-state 810, the UE 504 may be in the sleep-state.

The on-state 810 may begin after an offset 806 from the beginning of a cycle 808. After the offset 806, the UE 504 may transition from the sleep-state to the on-state 810, the default duration of which may be defined by an on-timer 802 (for SC-PTM, the onDurationTimerSCPTM) . In one approach, the UE 504 may be configured to wait for expiration of the default duration of the on-timer 802 before transitioning to the sleep-state.

The UE 504 may further include an inactivity-timer 804 (for SC-PTM, the drx-InactivityTimerSCPTM) . The inactivity-timer 804 may cause the UE 504 to remain in the on-cycle for a default duration after reception of each portion of broadcast content. That is, the UE 504 may start the inactivity timer in response to the reception of the initial portion 542 of broadcast content, and may restart the inactivity-timer 804 after each reception of another portion of broadcast content, including the subsequent portion 544.

FIG. 9 is a diagram of a wireless communications system. Between the respective on-states 810, there may be an idle period 912 during which the UE 504 may enter the sleep-state. However, the UE 504 may be configured to remain in the on-state 810 until expiration of the default durations of both the on-timer 802 and the inactivity-timer 804. Consequently, even if broadcast content has ended, the UE 504 may still remain in the on-state 810, which may unnecessarily consume resources (e.g., battery power) of the UE 504. If the idle period 912 begins before expiration of the default durations of the on-timer 802 and/or the inactivity-timer 804, the UE 504 may could potentially conserve resources by transitioning to the sleep-state during the idle period 912, even if the default durations of the on-timer 802 and/or the inactivity-timer 804 have not yet expired.

FIG. 10 is a call flow diagram of a method 1000 of wireless communication. In an aspect, the base station 1002 may transmit an SC-MTCH 1022, which may carry broadcast content. The UE 1004 may receive the SC-MTCH 1022, and may decode the information carried thereon using a G-RNTI (determined from an SC-MCCH, such as the SC-MCCH 726) .

Each portion of the broadcast content (e.g., a PDU) may cause the UE 1004 to restart the inactivity-timer 804. Accordingly, the UE 1004 may be configured to remain in the on-state 810 until expiration of a default duration of the inactivity- timer 804. However, the UE 1004 may be further configured to transition to the sleep-state before expiration of the default duration of the inactivity-timer 804 (and the on-timer 802) when the UE 1004 receives a broadcast end command, here a MAC CE that includes a DRX command (e.g., as described with respect to Table 1, the first broadcast end command 526) .

In the illustrated aspect, the UE 1004 may receive a MAC PDU 1024 carried on the SC-MTCH. The MAC PDU 1024 may include SC-MTCH data (e.g., broadcast content) and, optionally, padding (e.g., if the broadcast content does not consume the entire payload of the MAC PDU) . The MAC PDU 1024 may carry the last portion of broadcast content, such that there is no further broadcast content of a service to transmit from the base station 1002. Therefore, the base station 1002 may indicate, to the UE 1004, that the MAC PDU 1024 carries the end of the broadcast content by including a DRX command.

Because there is no acknowledgment mechanism at the MAC layer (e.g., HARQ is implemented at the RLC layer) , the UE 1004 may lack a mechanism to confirm to the base station 1002 that the DRX command carried in the MAC PDU 1024 was received. Thus, if the UE 1004 misses (e.g., is unable to decode) the DRX command carried in the MAC PDU 1024, the UE 1004 may remain in the on-state 810, which may be unnecessary because the broadcast content has ended. To increase the probability that the UE 1004 will receive the DRX command, the base station 1002 may repeatedly transmit the DRX command, as illustrated in

subsequent MAC PDUs

1026, 1028. That is, the base station 1002 may transmit at least one additional MAC PDU 1026 that includes the DRX command. The additional MAC PDU 1026 may only include padding in a payload, e.g., because the broadcast content has ended.

In the illustrated aspect, the UE 1004 may be unable to decode the next additional MAC PDU 1026 following the first MAC PDU 1024, but the base station may transmit a plurality of

additional MAC PDUs

1026, 1028. The UE 1004 may receive and successfully decode the last MAC PDU 1028 that carries the DRX command. In response to the DRX command, the UE 1004 may transition 1050 to the sleep-state, including stopping the inactivity-timer 804 (and the on-timer 802) . FIG. 11 illustrates different aspects for signaling a broadcast end command to a UE. The broadcast end command may be signaled by a DRX command, which may be a MAC CE.

In one aspect, a first MAC PDU 1100 may include a first MAC CE 1102 that indicates the DRX command. The first MAC CE 1102 may indicate the DRX command by inclusion of a predefined value (e.g., 11110) in the LCID of the first MAC CE 1102. The first MAC PDU 1100 may include a second MAC subheader 1104 (e.g., LCID 11001) that indicates the first MAC PDU 1100 carries SC-MTCH and/or SC-MCCH in a payload 1108 of the first MAC PDU 1100. The SC-MTCH data may not consume the entire payload portion of the first MAC PDU 1100 and, therefore, the remainder of the payload 1108 may include padding. The first MAC PDU 1100 may include a third MAC subheader 1106 (e.g., LCID 11111) that indicates the first MAC PDU 1100 carries padding in a payload 1108 of the first MAC PDU 1100.

In one aspect, a second MAC PDU 1120 may include a second MAC CE 1122 that indicates the DRX command. The second MAC CE 1122 may indicate the DRX command by inclusion of a predefined value (e.g., 11110) in the LCID. The second MAC PDU 1120 may include a second MAC subheader 1124 (e.g., LCID 11001) that indicates the second MAC PDU 1120 carries SC-MTCH and/or SC-MCCH in a payload 1128 of the second MAC PDU 1120. The SC-MTCH data may not consume the entire payload 1128 of the first MAC PDU 1100 and, therefore, no padding may be included or indicated in a MAC subheader.

In one aspect, a third MAC PDU 1140 may include a third MAC CE 1142 that indicates the DRX command. The third MAC CE 1142 may indicate the DRX command by inclusion of a predefined value (e.g., 11110) in the LCID. The third MAC PDU 1140 may include a second MAC subheader 1144 (e.g., LCID 11111) that indicates the third MAC PDU 1140 carries only padding in a payload 1148 of the third MAC PDU 1140. This third MAC PDU 1140 may be used to repeatedly signal the DRX command to a UE, even after broadcast content has ended.

FIG. 12 is a flow diagram illustrating a method 1200 of wireless communication. The method 1200 may be performed by a UE (e.g., the UE 504, the apparatus 1402/1402’ ) .

At operation 1202, the UE may determine a G-RNTI. For example, the UE may decode an SC-MCCH received from a base station in order to determine a G-RNTI for a service in which the UE is interested. In the content of FIG. 5, the UE 504 may determine a G-RNTI, e.g., based on information received from the base station 502.

At operation 1204, the UE may initiate an on-timer in response to waking from a sleep-cycle of a DRX configuration, and the waking from the sleep cycle may start an on-cycle of the DRX configuration. In the context of FIG. 5, the UE 504 may initiate 520 an on-timer in response to waking from a sleep-cycle of a DRX configuration.

At operation 1206, the UE may receive an initial portion of broadcast content during the on-cycle of the DRX configuration. In the context of FIG. 5, the UE 504 may receive the initial portion 542 of the broadcast content during the on-cycle of the DRX configuration.

At operation 1208, the UE may initiate an inactivity-timer in response to the reception of the initial portion. The on-timer and the inactivity-timer may each have a respective default duration (which may not be the same) . In the context of FIG. 5, the UE 504 may initiate 522 the inactivity-timer in response to reception of the initial portion 542.

At operation 1210, the UE may receive a subsequent portion of the broadcast content and a broadcast end command. The subsequent portion of the broadcast content and the initial portion may define the entire broadcast content. Accordingly, the broadcast end command may indicate, to the UE, that there is no more broadcast content to be received during the on-cycle. In the context of FIG. 5, the UE 504 may receive the subsequent portion 544 of the broadcast content and the broadcast end command 546.

At operation 1212, the UE may initiate a sleep-cycle prior to the expiration of the on-timer and the inactivity-timer default durations based on the broadcast end command. In the context of FIG. 5, the UE 504 may initiate 524 the sleep-cycle prior to the expiration of the on-timer and the inactivity-timer default durations based on the broadcast end command.

FIG. 13 is a flow diagram illustrating a method 1300 of wireless communication. The method 1300 may be performed by a base station (e.g., the base station 502, the apparatus 1602/1602’ ) .

At operation 1302, the base station may determine a G-RNTI associated with a group that includes a UE. The G-RNTI may be associated with a service that is of interest to the UE and may be associated with a TMGI. In the context of FIG. 5, the base station 502 may determine a G-RNTI associated with a group that includes the UE 504.

At operation 1304, the base station may transmit an indication of the G-RNTI to the UE. The indication may be carried on an SC-MCCH. In the context of FIG. 5, the base station 502 may transmit an indication of the G-RNTI to the UE 504.

At operation 1306, the base station may transmit, to the UE, information associated with a DRX configuration. The information may include at least a default duration of an on-timer associated with an on-cycle of the UE and a default duration of an inactivity-timer. In the context of FIG. 5, the base station 502 may transmit, to the UE 504, the information 540 associated with a DRX configuration.

At operation 1308, the base station may transmit, to the UE, an initial portion of broadcast content during the on-cycle of the DRX configuration. In the context of FIG. 5, the base station 502 may transmit, to the UE 504, the initial portion 542 of broadcast content during the on-cycle of the DRX configuration.

At operation 1310, the base station may transmit, to the UE a subsequent portion of the broadcast content. The initial portion and the subsequent portion may define the entire broadcast content. In other words, the base station may no additional portions of broadcast content to transmit to the UE in connection with a service. In the context of FIG. 5, the base station 502, may transmit, to the UE 504, the subsequent portion 544 of the broadcast content.

At operation 1312, the base station may transmit, to the UE, a first broadcast end command. The first broadcast end command may be intended to cause the UE to transition to the sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration. In the context of FIG. 5, the base station 502 may transmit, to the UE 504, the first broadcast end command 546.

Because the layer at which the broadcast end command is implemented may lack a mechanism to acknowledge reception of the broadcast end command, the base station may repeatedly transmit the broadcast end command. Thus, at operation 1314, the base station may transmit, to the UE, at least a second broadcast end command after transmission of the first broadcast end command. In the context of FIG. 5, the base station 502 may transmit, to the UE 504, at least a second broadcast end command after transmission of the first broadcast end command 546.

FIG. 14 is a conceptual data flow diagram 1400 illustrating the data flow between different means/components in an exemplary apparatus 1402. The apparatus 1402 may be a UE. The apparatus 1402 includes a reception component 1404 configured to receive signals from a base station (e.g., the base station 1450) . The apparatus 1402 includes a transmission component 1410 configured to transmit signals to a base station (e.g., the base station 1450) .

In an aspect, the apparatus 1402 may include a DRX component 1412. The DRX component 1412 may be configured to receive a DRX configuration from the base station 1450. The DRX component 1412 may be configured to cause the apparatus 1402 to transition between a sleep-cycle and an on-cycle based on the DRX configuration. For example, the DRX component 1412 may provide an indication to the reception component 1404 that causes the reception component to transition between a sleep-cycle and an on-cycle.

In aspects, the DRX component 1412 may include at least an on-timer and an inactivity-timer, each of which may have a respective default duration. The DRX component 1412 may be configured to initiate the on-timer in response to waking from a sleep-cycle of the DRX configuration, which may start the on-cycle of the DRX configuration. During the on-cycle, the reception component 1404 may be awake to receive data.

The content component 1416 may receive, through the reception component 1404, an initial portion of broadcast content during the on-cycle of the DRX configuration. The broadcast content may be associated with a service in which the apparatus 1402 is interested. In an aspect, the broadcast content is received on a PDSCH through an SC-PTM configuration.

The initial portion of the broadcast content may be packetized as a PDU (e.g., a MAC PDU) . A control component 1414 may parse the header (e.g., MAC CE) of the PDUs and determine if a packet includes data (e.g., SC-MTCH data) for the apparatus 1402. If so, the control component 1414 may indicate to the DRX component 1412 that data has been received. The DRX component 1412 may initiate the inactivity-timer in response to the indication from the control component 1414 that data has been received.

In one aspect, the control component 1414 may be configured to determine a G-RNTI associated with a group that includes the apparatus 1402. From the G-RNTI, the control component 1414 may determine commands that are applicable to the apparatus 1402.

The content component 1416 may receive, through the reception component 1404, a subsequent portion of broadcast content (e.g., during the on-cycle of the DRX configuration) . The subsequent portion and the initial portion may define the entire broadcast content.

The control component 1414 may receive, through the reception component 1404, a PDU that includes a subheader of a MAC CE that indicates a broadcast end command (e.g., a DRX command) . In an aspect, the broadcast end command is a MAC CE included in a MAC PDU. In an aspect, the broadcast end command MAC CE is included in a MAC PDU that includes the subsequent portion of the broadcast content. In an aspect, the broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.

The control component 1414 may then instruct the DRX component 1412 that the broadcast content is completed. In response, the DRX component 1412 may initiate the sleep-cycle prior to the expiration of the on-timer and the inactivity-timer based on the broadcast end command.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIG. 12. As such, each block in the aforementioned flowcharts of FIG. 12 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

FIG. 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1402'employing a processing system 1514. The processing system 1514 may be implemented with a bus architecture, represented generally by the bus 1524. The bus 1524 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1514 and the overall design constraints. The bus 1524 links together various circuits including one or more processors and/or hardware components, represented by the processor 1504, the

components

1404, 1410, 1412, 1414, 1416, and the computer-readable medium /memory 1506. The bus 1524 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 1514 may be coupled to a transceiver 1510. The transceiver 1510 is coupled to one or more antennas 1520. The transceiver 1510 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1510 receives a signal from the one or more antennas 1520, extracts information from the received signal, and provides the extracted information to the processing system 1514, specifically the reception component 1404. In addition, the transceiver 1510 receives information from the processing system 1514, specifically the transmission component 1410, and based on the received information, generates a signal to be applied to the one or more antennas 1520. The processing system 1514 includes a processor 1504 coupled to a computer-readable medium /memory 1506. The processor 1504 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory 1506. The software, when executed by the processor 1504, causes the processing system 1514 to perform the various functions described supra for any particular apparatus. The computer-readable medium /memory 1506 may also be used for storing data that is manipulated by the processor 1504 when executing software. The processing system 1514 further includes at least one of the

components

1404, 1410, 1412, 1414, 1416. The components may be software components running in the processor 1504, resident/stored in the computer readable medium /memory 1506, one or more hardware components coupled to the processor 1504, or some combination thereof. The processing system 1514 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.

In one configuration, the apparatus 1402/1402'for wireless communication includes means for means for initiating an on-timer in response to waking from a sleep-cycle of a DRX configuration, wherein the waking from the sleep-cycle starts an on-cycle of the DRX configuration. The apparatus 1402/1402’ may further include means for receiving an initial portion of broadcast content during the on-cycle of the DRX configuration. The apparatus 1402/1402’ may further include means for initiating an inactivity-timer in response to the reception, the on-timer and the inactivity-timer each having default durations. The apparatus 1402/1402’ may further include means for receiving a subsequent portion of the broadcast content and a broadcast end command, wherein the initial portion and the subsequent portion define the entire broadcast content. The apparatus 1402/1402’ may further include means for initiating a sleep-cycle prior to the expiration of the on-timer and the inactivity-timer default durations based on the broadcast end command.

In an aspect, the broadcast end command is a MAC CE included in a MAC PDU. In an aspect, the broadcast end command MAC CE is included in a MAC PDU that further includes the subsequent portion of the broadcast content. In an aspect, the broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.

The apparatus 1402/1402’ may further include means for determining a group radio network temporary identifier (G-RNTI) , the G-RNTI associated with a group that includes the UE. In an aspect, the broadcast content is received on a PDSCH through SC-PTM configuration.

The aforementioned means may be one or more of the aforementioned components of the apparatus 1402 and/or the processing system 1514 of the apparatus 1402'configured to perform the functions recited by the aforementioned means. As described supra, the processing system 1514 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

FIG. 16 is a conceptual data flow diagram 1600 illustrating the data flow between different means/components in an exemplary apparatus 1602. The apparatus 1602 may be a base station. The apparatus 1602 includes a reception component 1604 configured to receive signals from a UE (e.g., the UE 1650) . The apparatus 1602 includes a transmission component 1610 configured to transmit signals to a UE (e.g., the UE 1650) .

The apparatus 1602 includes a DRX component 1612. The DRX component 1612 may be configured to determine information associated with a DRX configuration (e.g., for a TMGI associated with the UE 1650) . The information may include at least a default duration of an on-timer associated with an on-cycle of the UE and a default duration of an inactivity-timer. The DRX component 1612 may cause the transmission component 1610 to transmit the information associated with the DRX configuration to the UE 1650 so that the UE 1650 will be in on-cycle when the apparatus 1602 transmits broadcast content.

The apparatus 1602 may include a control component 1614. In an aspect, the control component 1614 may be configured to determine a G-RNTI associate with a group that includes the UE 1650, such as a group associated with a service that the UE 1650 would like to receive (e.g., a TMGI) . The control component 1614 may cause the transmission component 1610 to transmit an indication of the G-RNTI to the UE 1650.

The apparatus may include a content component 1616. The content component 1616 may determine broadcast content to transmit to the UE 1650. The content component 1616 may cause the transmission component 1610 to transmit, to the UE 1650, an initial portion of broadcast content during the on-cycle of the DRX configuration.

Further, the content component 1616 may cause the transmission component 1610 to transmit, to the UE 1650, a subsequent portion of broadcast content during the on-cycle of the DRX configuration. The initial portion and the subsequent portion may define the entire broadcast content. The content component 1616 may cause transmission of the portions of the broadcast content on a PDSCH through an SC-PTM configuration.

The control component 1614 may be configured to determine that the broadcast content of current DRX cycle has been transmitted to the UE 1650 and, therefore, the UE 1650 may transition to the sleep-cycle. Therefore, the control component 1614 may cause the transmission component 1610 to transmit, to the UE 1650, a first broadcast end command. The first broadcast end command may be intended to cause the UE to transition to the sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration. In an aspect, the first broadcast end command is a MAC CE included in a MAC PDU. In an aspect, the first broadcast end command MAC CE is included in a MAC PDU that includes the subsequent portion of the broadcast content. In an aspect, the first broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.

Because the layer at which the broadcast end command is implemented may lack a mechanism to acknowledge reception of the broadcast end command, the control component 1614 may repeatedly transmit the broadcast end command. Thus, control component 1614 may cause the transmission component 1610 to transmit, to the UE 1650, at least a second broadcast end command after transmission of the first broadcast end command. The second broadcast end command may be similar to the first broadcast end command, but may only include padding in the payload.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIG. 13. As such, each block in the aforementioned flowcharts of FIG. 13 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

FIG. 17 is a diagram 1700 illustrating an example of a hardware implementation for an apparatus 1602'employing a processing system 1714. The processing system 1714 may be implemented with a bus architecture, represented generally by the bus 1724. The bus 1724 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1714 and the overall design constraints. The bus 1724 links together various circuits including one or more processors and/or hardware components, represented by the processor 1704, the

components

1604, 1610, 1612, 1614, 1616, and the computer-readable medium /memory 1706. The bus 1724 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system 1714 may be coupled to a transceiver 1710. The transceiver 1710 is coupled to one or more antennas 1720. The transceiver 1710 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1710 receives a signal from the one or more antennas 1720, extracts information from the received signal, and provides the extracted information to the processing system 1714, specifically the reception component 1604. In addition, the transceiver 1710 receives information from the processing system 1714, specifically the transmission component 1610, and based on the received information, generates a signal to be applied to the one or more antennas 1720. The processing system 1714 includes a processor 1704 coupled to a computer-readable medium /memory 1706. The processor 1704 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory 1706. The software, when executed by the processor 1704, causes the processing system 1714 to perform the various functions described supra for any particular apparatus. The computer-readable medium /memory 1706 may also be used for storing data that is manipulated by the processor 1704 when executing software. The processing system 1714 further includes at least one of the

components

1604, 1610, 1612, 1614, 1616. The components may be software components running in the processor 1704, resident/stored in the computer readable medium /memory 1706, one or more hardware components coupled to the processor 1704, or some combination thereof. The processing system 1714 may be a component of the eNB 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

In one configuration, the apparatus 1602/1602'for wireless communication includes means for means for transmitting, to a UE, information associated with a DRX configuration, the information including at least a default duration of an on-timer associated with an on-cycle of the UE and a default duration of an inactivity-timer. The apparatus 1602/1602'may further include means for transmitting, to the UE, an initial portion of broadcast content during the on-cycle of the DRX configuration. The apparatus 1602/1602'may further include means for transmitting, to the UE, a subsequent portion of the broadcast content, wherein the initial portion and the subsequent portion define the entire broadcast content. The apparatus 1602/1602'may further include means for transmitting, to the UE, a first broadcast end command, wherein the first broadcast end command is intended to cause the UE to transition to a sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration.

In an aspect, the first broadcast end command is a MAC CE included in a MAC PDU. In an aspect, the first broadcast end command MAC CE is included in a MAC PDU that further includes the subsequent portion of the broadcast content. In an aspect, the first broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.

The apparatus 1602/1602'may further include means for determining a G-RNTI, the G-RNTI associated with a group that includes the UE. The apparatus 1602/1602'may further include means for transmitting an indication of the G-RNTI to the UE. In an aspect, the broadcast content is transmitted on a PDSCH through SC-PTM configuration. The apparatus 1602/1602'may further include means for transmitting at least a second broadcast end command after the transmission of the first broadcast end command. In an aspect, the first broadcast end command is transmitted in a first subframe and the second broadcast end command is transmitted in a second subframe that immediately follows the first subframe. In an aspect, the first broadcast end command is transmitted in a first subframe and the second broadcast end command is transmitted in a second subframe, wherein at least one other subframe separates the first subframe and the second subframe.

The aforementioned means may be one or more of the aforementioned components of the apparatus 1602 and/or the processing system 1714 of the apparatus 1602'configured to perform the functions recited by the aforementioned means. As described supra, the processing system 1714 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375. As such, in one configuration, the aforementioned means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the aforementioned means.

Further disclosure is included in the Appendix.

It is understood that the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”

Claims

A method of wireless communication by a user equipment (UE) , the method comprising:

initiating, by the UE, an on-timer in response to waking from a sleep-cycle of a discontinuous reception (DRX) configuration, wherein the waking from the sleep-cycle starts an on-cycle of the DRX configuration；

receiving an initial portion of broadcast content during the on-cycle of the DRX configuration；

initiating an inactivity-timer in response to the reception, the on-timer and the inactivity-timer each having default durations；

receiving a subsequent portion of the broadcast content and a broadcast end command, wherein the initial portion and the subsequent portion define the entire broadcast content； and

initiating a sleep-cycle prior to the expiration of the on-timer and the inactivity-timer default durations based on the broadcast end command.
The method of claim 1, wherein the broadcast end command is a Medium Access Control (MAC) control element (CE) included in a MAC packet data unit (PDU) .
The method of claim 2, wherein the broadcast end command MAC CE is included in a MAC PDU that further includes the subsequent portion of the broadcast content.
The method of claim 2, wherein the broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.
The method of claim 1, further comprising:

determining a group radio network temporary identifier (G-RNTI) , the G-RNTI associated with a group that includes the UE.
The method of claim 1, wherein the broadcast content is received on a physical downlink shared channel (PDSCH) through single-cell point-to-multipoint (SC-PTM) configuration.
A method of wireless communication by a base station, the method comprising:

transmitting, to a user equipment (UE) , information associated with a discontinuous reception (DRX) configuration, the information including at least a default duration of an on-timer associated with an on-cycle of the UE and a default duration of an inactivity-timer；

transmitting, to the UE, an initial portion of broadcast content during the on-cycle of the DRX configuration；

transmitting, to the UE, a subsequent portion of the broadcast content, wherein the initial portion and the subsequent portion define the entire broadcast content； and

transmitting, to the UE, a first broadcast end command, wherein the first broadcast end command is intended to cause the UE to transition to a sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration.
The method of claim 7, wherein the first broadcast end command is a Medium Access Control (MAC) control element (CE) included in a MAC packet data unit (PDU) .
The method of claim 8, wherein the first broadcast end command MAC CE is included in a MAC PDU that further includes the subsequent portion of the broadcast content.
The method of claim 8, wherein the first broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.
The method of claim 7, further comprising:

determining a group radio network temporary identifier (G-RNTI) , the G-RNTI associated with a group that includes the UE； and

transmitting an indication of the G-RNTI to the UE.
The method of claim 7, wherein the broadcast content is transmitted on a physical downlink shared channel (PDSCH) through single-cell point-to-multipoint (SC-PTM) configuration.
The method of claim 7, further comprising:

transmitting at least a second broadcast end command after the transmission of the first broadcast end command.
The method of claim 13, wherein the first broadcast end command is transmitted in a first subframe and the second broadcast end command is transmitted in a second subframe that immediately follows the first subframe.
The method of claim 13, wherein the first broadcast end command is transmitted in a first subframe and the second broadcast end command is transmitted in a second subframe, wherein at least one other subframe separates the first subframe and the second subframe.
A user equipment (UE) comprising:

means for initiating, by the UE, an on-timer in response to waking from a sleep-cycle of a discontinuous reception (DRX) configuration, wherein the waking from the sleep-cycle starts an on-cycle of the DRX configuration；

means for receiving an initial portion of broadcast content during the on-cycle of the DRX configuration；

means for initiating an inactivity-timer in response to the reception, the on-timer and the inactivity-timer each having default durations；

means for receiving a subsequent portion of the broadcast content and a broadcast end command, wherein the initial portion and the subsequent portion define the entire broadcast content； and

means for initiating a sleep-cycle prior to the expiration of the on-timer and the inactivity-timer default durations based on the broadcast end command.
The UE of claim 16, wherein the broadcast end command is a Medium Access Control (MAC) control element (CE) included in a MAC packet data unit (PDU) .
The UE of claim 17, wherein the broadcast end command MAC CE is included in a MAC PDU that further includes the subsequent portion of the broadcast content.
The UE of claim 17, wherein the broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.
The UE of claim 16, further comprising:

means for determining a group radio network temporary identifier (G-RNTI) , the G-RNTI associated with a group that includes the UE.
The UE of claim 16, wherein the broadcast content is received on a physical downlink shared channel (PDSCH) through single-cell point-to-multipoint (SC-PTM) configuration.
A base station comprising:

means for transmitting, to a user equipment (UE) , information associated with a discontinuous reception (DRX) configuration, the information including at least a default duration of an on-timer associated with an on-cycle of the UE and a default duration of an inactivity-timer；

means for transmitting, to the UE, an initial portion of broadcast content during the on-cycle of the DRX configuration；

means for transmitting, to the UE, a subsequent portion of the broadcast content, wherein the initial portion and the subsequent portion define the entire broadcast content； and

means for transmitting, to the UE, a first broadcast end command, wherein the first broadcast end command is intended to cause the UE to transition to a sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration.
The base station of claim 22, wherein the first broadcast end command is a Medium Access Control (MAC) control element (CE) included in a MAC packet data unit (PDU) .
The base station of claim 23, wherein the first broadcast end command MAC CE is included in a MAC PDU that further includes the subsequent portion of the broadcast content.
The base station of claim 23, wherein the first broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.
The base station of claim 22, further comprising:

means for determining a group radio network temporary identifier (G-RNTI) , the G-RNTI associated with a group that includes the UE； and

means for transmitting an indication of the G-RNTI to the UE.
The base station of claim 22, wherein the broadcast content is transmitted on a physical downlink shared channel (PDSCH) through single-cell point-to-multipoint (SC-PTM) configuration.
The base station of claim 22, further comprising:

means for transmitting at least a second broadcast end command after the transmission of the first broadcast end command.
The base station of claim 28, wherein the first broadcast end command is transmitted in a first subframe and the second broadcast end command is transmitted in a second subframe that immediately follows the first subframe.
The base station of claim 28, wherein the first broadcast end command is transmitted in a first subframe and the second broadcast end command is transmitted in a second subframe, wherein at least one other subframe separates the first subframe and the second subframe.
A user equipment (UE) comprising:

a memory； and

at least one processor coupled to the memory and configured to:

initiate, by the UE, an on-timer in response to waking from a sleep-cycle of a discontinuous reception (DRX) configuration, wherein the waking from the sleep-cycle starts an on-cycle of the DRX configuration；

receive an initial portion of broadcast content during the on-cycle of the DRX configuration；

initiate an inactivity-timer in response to the reception, the on-timer and the inactivity-timer each having default durations；

receive a subsequent portion of the broadcast content and a broadcast end command, wherein the initial portion and the subsequent portion define the entire broadcast content； and

initiate a sleep-cycle prior to the expiration of the on-timer and the inactivity-timer default durations based on the broadcast end command.
The UE of claim 31, wherein the broadcast end command is a Medium Access Control (MAC) control element (CE) included in a MAC packet data unit (PDU) .
The UE of claim 32, wherein the broadcast end command MAC CE is included in a MAC PDU that further includes the subsequent portion of the broadcast content.
The UE of claim 32, wherein the broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.
The UE of claim 31, the at least one processor further configured to:

determine a group radio network temporary identifier (G-RNTI) , the G-RNTI associated with a group that includes the UE.
The UE of claim 31, wherein the broadcast content is received on a physical downlink shared channel (PDSCH) through single-cell point-to-multipoint (SC-PTM) configuration.
A base station comprising:

a memory； and

at least one processor coupled to the memory and configured to:

transmit, to a user equipment (UE) , information associated with a discontinuous reception (DRX) configuration, the information including at least a default duration of an on-timer associated with an on-cycle of the UE and a default duration of an inactivity-timer；

transmit, to the UE, an initial portion of broadcast content during the on-cycle of the DRX configuration；

transmit, to the UE, a subsequent portion of the broadcast content, wherein the initial portion and the subsequent portion define the entire broadcast content； and

transmit, to the UE, a first broadcast end command, wherein the first broadcast end command is intended to cause the UE to transition to a sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration.
The base station of claim 37, wherein the first broadcast end command is a Medium Access Control (MAC) control element (CE) included in a MAC packet data unit (PDU) .
The base station of claim 38, wherein the first broadcast end command MAC CE is included in a MAC PDU that further includes the subsequent portion of the broadcast content.
The base station of claim 38, wherein the first broadcast end command MAC CE is included in a MAC PDU having a payload that is only padding.
The base station of claim 37, the at least one processor further configured to:

determine a group radio network temporary identifier (G-RNTI) , the G-RNTI associated with a group that includes the UE； and

transmit an indication of the G-RNTI to the UE.
The base station of claim 37, wherein the broadcast content is transmitted on a physical downlink shared channel (PDSCH) through single-cell point-to-multipoint (SC-PTM) configuration.
The base station of claim 37, the at least one processor further configured to:

transmit at least a second broadcast end command after the transmission of the first broadcast end command.
The base station of claim 43, wherein the first broadcast end command is transmitted in a first subframe and the second broadcast end command is transmitted in a second subframe that immediately follows the first subframe.
The base station of claim 43, wherein the first broadcast end command is transmitted in a first subframe and the second broadcast end command is transmitted in a second subframe, wherein at least one other subframe separates the first subframe and the second subframe.
A computer-readable medium storing computer-executable code for wireless communication by a user equipment (UE) , comprising code to:

initiate, by the UE, an on-timer in response to waking from a sleep-cycle of a discontinuous reception (DRX) configuration, wherein the waking from the sleep-cycle starts an on-cycle of the DRX configuration；

receive an initial portion of broadcast content during the on-cycle of the DRX configuration；

initiate an inactivity-timer in response to the reception, the on-timer and the inactivity-timer each having default durations；

receive a subsequent portion of the broadcast content and a broadcast end command, wherein the initial portion and the subsequent portion define the entire broadcast content； and

initiate a sleep-cycle prior to the expiration of the on-timer and the inactivity-timer default durations based on the broadcast end command.
A computer-readable medium storing computer-executable code for wireless communication by a base station, comprising code to:

transmit, to a user equipment (UE) , information associated with a discontinuous reception (DRX) configuration, the information including at least a default duration of an on-timer associated with an on-cycle of the UE and a default duration of an inactivity-timer；

transmit, to the UE, an initial portion of broadcast content during the on-cycle of the DRX configuration；

transmit, to the UE, a subsequent portion of the broadcast content, wherein the initial portion and the subsequent portion define the entire broadcast content； and

transmit, to the UE, a first broadcast end command, wherein the first broadcast end command is intended to cause the UE to transition to a sleep-cycle of the DRX configuration prior to expiration of the on-timer default duration and the inactivity-timer default duration