WO2016026068A1 - Dispositif économique avec support de diffusion - Google Patents

Dispositif économique avec support de diffusion Download PDF

Info

Publication number
WO2016026068A1
WO2016026068A1 PCT/CN2014/084628 CN2014084628W WO2016026068A1 WO 2016026068 A1 WO2016026068 A1 WO 2016026068A1 CN 2014084628 W CN2014084628 W CN 2014084628W WO 2016026068 A1 WO2016026068 A1 WO 2016026068A1
Authority
WO
WIPO (PCT)
Prior art keywords
pmchs
subframe
pairs
pmch
sib
Prior art date
Application number
PCT/CN2014/084628
Other languages
English (en)
Inventor
Xiaoxia Zhang
Jun Wang
Xipeng Zhu
Hao Xu
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2014/084628 priority Critical patent/WO2016026068A1/fr
Publication of WO2016026068A1 publication Critical patent/WO2016026068A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path

Definitions

  • the present disclosure relates generally to communication systems, and more particularly, to an apparatus for receiving services including evolved Multimedia Broadcast Multicast Service (eMBMS).
  • eMBMS evolved Multimedia Broadcast Multicast Service
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power).
  • multiple-access technologies include 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.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • 3GPP Third Generation Partnership Project
  • LTE is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA on the downlink (DL), SC-FDMA on the uplink (UL), and multiple-input multiple-output (MIMO) antenna technology.
  • OFDMA on the downlink
  • UL uplink
  • MIMO multiple-input multiple-output
  • a method, a computer program product, and an apparatus receives one or more physical multicast channels (PMCHs) in a plurality of resource block (RB) pairs in a subframe, each of the one or more PMCHs occupying less than or equal to a total number of RB pairs in the subframe, and decodes at least one PMCH of the one or more PMCHs in the subframe.
  • the apparatus may also receive frequency resource information indicating subcarriers allocated to each of the one or more PMCHs, and receive a frequency hopping pattern for the one or more PMCHs.
  • the apparatus may also receive a physical downlink shared channel (PDSCH) in at least one other RB pair in the subframe, the PDSCH carrying unicast data.
  • the apparatus may also receive Multicast Broadcast Single Frequency Network (MBSFN) reference signals (MBSFN-RS) in the plurality of RB pairs in the subframe.
  • MBSFN Multicast Broadcast Single Frequency Network
  • the apparatus receives a paging message indicating transmission of Machine Type Communications (MTC) data and decodes a system information block (SIB) including the MTC data, in response to the receiving the paging message.
  • MTC Machine Type Communications
  • SIB system information block
  • FIG. 1 is a diagram illustrating an example of a network architecture.
  • FIG. 2 is a diagram illustrating an example of an access network.
  • FIG. 3 is a diagram illustrating an example of a DL frame structure in LTE.
  • FIG. 4 is a diagram illustrating an example of an UL frame structure in LTE.
  • FIG. 5 is a diagram illustrating an example of a radio protocol architecture for the user and control planes.
  • FIG. 6 is a diagram illustrating an example of an evolved Node B and user equipment in an access network.
  • FIG. 7A is a diagram illustrating an example of an evolved Multimedia
  • FIG. 7B is a diagram illustrating a format of a Multicast Channel Scheduling Information Media Access Control control element.
  • FIG. 8 is a diagram illustrating reception of an evolved Multimedia Broadcast Multicast Service according to one embodiment.
  • FIG. 9 is a diagram illustrating reception of an evolved Multimedia Broadcast Multicast Service according to another embodiment.
  • FIG. 10 is a diagram illustrating transmission of a SIB from multiple cells.
  • FIG. 11 is a flow chart of a method of receiving a Multimedia Broadcast Multicast Service (MBMS) service.
  • MBMS Multimedia Broadcast Multicast Service
  • FIG. 12 is a flow chart of a method of receiving MTC data.
  • FIG. 13 is a conceptual data flow diagram illustrating the data flow between different modules/means/components in an exemplary apparatus.
  • FIG. 14 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.
  • FIG. 15 is a diagram illustrating an example of service layer simplification.
  • processors include microprocessors, microcontrollers, digital signal processors (DSPs), 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.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • 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 modules, 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.
  • the functions described may be implemented in hardware, software, firmware, 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.
  • such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), compact disk ROM (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Combinations of the above should also be included within the scope of computer-readable media.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • CD-ROM compact disk ROM
  • CD-ROM compact disk ROM
  • FIG. 1 is a diagram illustrating an LTE network architecture 100.
  • the LTE network architecture 100 may be referred to as an Evolved Packet System (EPS) 100.
  • the EPS 100 may include one or more user equipment (UE) 102, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 104, an Evolved Packet Core (EPC) 110, and an Operator's Internet Protocol (IP) Services 122.
  • the EPS can interconnect with other access networks, but for simplicity those entities/interfaces are not shown.
  • the EPS provides packet-switched services, however, as those skilled in the art will readily appreciate, the various concepts presented throughout this disclosure may be extended to networks providing circuit- switched services.
  • the E-UTRAN includes the evolved Node B (eNB) 106 and other eNBs 108, and may include a Multicast Coordination Entity (MCE) 128.
  • the eNB 106 provides user and control planes protocol terminations toward the UE 102.
  • the eNB 106 may be connected to the other eNBs 108 via a backhaul (e.g., an X2 interface).
  • the MCE 128 allocates time/frequency radio resources for evolved Multimedia Broadcast Multicast Service (MBMS) (eMBMS), and determines the radio configuration (e.g., a modulation and coding scheme (MCS)) for the eMBMS.
  • MBMS evolved Multimedia Broadcast Multicast Service
  • MCS modulation and coding scheme
  • the MCE 128 may be a separate entity or part of the eNB 106.
  • the eNB 106 may also be referred to as a base station, a Node B, 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 eNB 106 provides an access point to the EPC 110 for a UE 102.
  • Examples of UEs 102 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, or any other similar functioning device.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • satellite radio a global positioning system
  • multimedia device e.g., a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, or any other similar functioning device.
  • MP3 player digital audio player
  • the UE 102 may also be referred to by those skilled in the art as 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.
  • the eNB 106 is connected to the EPC 110.
  • the EPC 110 may include a
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • MBMS Multimedia Broadcast Multicast Service
  • BM-SC Broadcast Multicast Service Center
  • PDN Packet Data Network Gateway 118.
  • the MME 112 is the control node that processes the signaling between the UE 102 and the EPC 110. Generally, the MME 112 provides bearer and connection management. All user IP packets are transferred through the Serving Gateway 116, which itself is connected to the PDN Gateway 118.
  • the PDN Gateway 118 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 118 and the BM-SC 126 are connected to the IP Services 122.
  • the IP Services 122 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service (PSS), and/or other IP services.
  • the BM-SC 126 may provide functions for MBMS user service provisioning and delivery.
  • the BM-SC 126 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a PLMN, and may be used to schedule and deliver MBMS transmissions.
  • the MBMS Gateway 124 may be used to distribute MBMS traffic to the e Bs (e.g., 106, 108) 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.
  • MMSFN Multicast Broadcast Single Frequency Network
  • FIG. 2 is a diagram illustrating an example of an access network 200 in an LTE network architecture.
  • the access network 200 is divided into a number of cellular regions (cells) 202.
  • One or more lower power class eNBs 208 may have cellular regions 210 that overlap with one or more of the cells 202.
  • the lower power class eNB 208 may be a femto cell (e.g., home eNB (HeNB)), pico cell, micro cell, or remote radio head (RRH).
  • HeNB home eNB
  • RRH remote radio head
  • the macro eNBs 204 are each assigned to a respective cell 202 and are configured to provide an access point to the EPC 110 for all the UEs 206 in the cells 202.
  • the eNBs 204 are responsible for all radio related functions including radio bearer control, admission control, mobility control, scheduling, security, and connectivity to the serving gateway 116.
  • An eNB may support one or multiple (e.g., three) cells (also referred to as a sectors).
  • the term "cell” can refer to the smallest coverage area of an eNB and/or an eNB subsystem serving are particular coverage area. Further, the terms “eNB,” “base station,” and “cell” may be used interchangeably herein.
  • OFDM frequency division duplex
  • TDD time division duplex
  • EV-DO Evolution-Data Optimized
  • UMB Ultra Mobile Broadband
  • EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations. These concepts may also be extended to Universal Terrestrial Radio Access (UTRA) employing Wideband-CDMA (W- CDMA) and other variants of CDMA, such as TD-SCDMA; Global System for Mobile Communications (GSM) employing TDMA; and Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM employing OFDMA.
  • UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from the 3 GPP organization.
  • CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.
  • the eNBs 204 may have multiple antennas supporting MIMO technology.
  • MIMO technology enables the eNBs 204 to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity.
  • Spatial multiplexing may be used to transmit different streams of data simultaneously on the same frequency.
  • the data streams may be transmitted to a single UE 206 to increase the data rate or to multiple UEs 206 to increase the overall system capacity. This is achieved by spatially precoding each data stream (i.e., applying a scaling of an amplitude and a phase) and then transmitting each spatially precoded stream through multiple transmit antennas on the DL.
  • the spatially precoded data streams arrive at the UE(s) 206 with different spatial signatures, which enables each of the UE(s) 206 to recover the one or more data streams destined for that UE 206.
  • each UE 206 transmits a spatially precoded data stream, which enables the eNB 204 to identify the source of each spatially precoded data stream.
  • Spatial multiplexing is generally used when channel conditions are good. When channel conditions are less favorable, beamforming may be used to focus the transmission energy in one or more directions. This may be achieved by spatially precoding the data for transmission through multiple antennas. To achieve good coverage at the edges of the cell, a single stream beamforming transmission may be used in combination with transmit diversity. [0033] In the detailed description that follows, various aspects of an access network will be described with reference to a MIMO system supporting OFDM on the DL.
  • OFDM is a spread- spectrum technique that modulates data over a number of subcarriers within an OFDM symbol. The subcarriers are spaced apart at precise frequencies. The spacing provides "orthogonality" that enables a receiver to recover the data from the subcarriers.
  • a guard interval (e.g., cyclic prefix) may be added to each OFDM symbol to combat inter-OFDM-symbol interference.
  • the UL may use SC-FDMA in the form of a DFT-spread OFDM signal to compensate for high peak-to-average power ratio (PAPR).
  • PAPR peak-to-average power ratio
  • FIG. 3 is a diagram 300 illustrating an example of a DL frame structure 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 two time slots, each time slot including a resource block.
  • the resource grid is divided into multiple resource elements.
  • a resource block contains 12 consecutive subcarriers in the frequency domain and 7 consecutive OFDM symbols in the time domain, for a total of 84 resource elements.
  • a resource block contains 12 consecutive subcarriers in the frequency domain and 6 consecutive OFDM symbols in the time domain, for a total of 72 resource elements.
  • Some of the resource elements, indicated as R 302, 304, include DL reference signals (DL-RS).
  • the DL-RS include Cell-specific RS (CRS) (also sometimes called common RS) 302 and UE-specific RS (UE-RS) 304.
  • UE-RS 304 are transmitted only on the resource blocks upon which the corresponding physical DL shared channel (PDSCH) is mapped.
  • PDSCH physical DL shared channel
  • the number of bits carried by each resource element depends on the modulation scheme. Thus, the more resource blocks that a UE receives and the higher the modulation scheme, the higher the data rate for the UE.
  • FIG. 4 is a diagram 400 illustrating an example of an UL frame structure in
  • the available resource blocks for the UL may be partitioned into a data section and a control section.
  • the control section may be formed at the two edges of the system bandwidth and may have a configurable size.
  • the resource blocks in the control section may be assigned to UEs for transmission of control information.
  • the data section may include all resource blocks not included in the control section.
  • the UL frame structure results in the data section including contiguous subcarriers, which may allow a single UE to be assigned all of the contiguous subcarriers in the data section.
  • a UE may be assigned resource blocks 410a, 410b in the control section to transmit control information to an e B.
  • the UE may also be assigned resource blocks 420a, 420b in the data section to transmit data to the eNB.
  • the UE may transmit control information in a physical UL control channel (PUCCH) on the assigned resource blocks in the control section.
  • the UE may transmit only data or both data and control information in a physical UL shared channel (PUSCH) on the assigned resource blocks in the data section.
  • a UL transmission may span both slots of a subframe and may hop across frequency.
  • a set of resource blocks may be used to perform initial system access and achieve UL synchronization in a physical random access channel (PRACH) 430.
  • the PRACH 430 carries a random sequence and cannot carry any UL data/signaling.
  • Each random access preamble occupies a bandwidth corresponding to six consecutive resource blocks.
  • the starting frequency is specified by the network. That is, the transmission of the random access preamble is restricted to certain time and frequency resources. There is no frequency hopping for the PRACH.
  • the PRACH attempt is carried in a single subframe (1 ms) or in a sequence of few contiguous subframes and a UE can make only a single PRACH attempt per frame (10 ms).
  • FIG. 5 is a diagram 500 illustrating an example of a radio protocol architecture for the user and control planes in LTE.
  • the radio protocol architecture for the UE and the eNB is shown with three layers: Layer 1, Layer 2, and Layer 3.
  • Layer 1 (LI layer) is the lowest layer and implements various physical layer signal processing functions.
  • the LI layer will be referred to herein as the physical layer 506.
  • Layer 2 (L2 layer) 508 is above the physical layer 506 and is responsible for the link between the UE and eNB over the physical layer 506.
  • the L2 layer 508 includes a media access control (MAC) sublayer 510, a radio link control (RLC) sublayer 512, and a packet data convergence protocol (PDCP) 514 sublayer, which are terminated at the eNB on the network side.
  • MAC media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • the UE may have several upper layers above the L2 layer 508 including a network layer (e.g., IP layer) that is terminated at the PDN gateway 118 on the network side, and an application layer that is terminated at the other end of the connection (e.g., far end UE, server, etc.).
  • the PDCP sublayer 514 provides multiplexing between different radio bearers and logical channels.
  • the PDCP sublayer 514 also provides header compression for upper layer data packets to reduce radio transmission overhead, security by ciphering the data packets, and handover support for UEs between e Bs.
  • the RLC sublayer 512 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to hybrid automatic repeat request (HARQ).
  • HARQ hybrid automatic repeat request
  • the MAC sublayer 510 provides multiplexing between logical and transport channels. The MAC sublayer 510 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer 510 is also responsible for HARQ operations.
  • the radio protocol architecture for the UE and e B is substantially the same for the physical layer 506 and the L2 layer 508 with the exception that there is no header compression function for the control plane.
  • the control plane also includes a radio resource control (RRC) sublayer 516 in Layer 3 (L3 layer).
  • RRC sublayer 516 is responsible for obtaining radio resources (e.g., radio bearers) and for configuring the lower layers using RRC signaling between the eNB and the UE.
  • FIG. 6 is a block diagram of an eNB 610 in communication with a UE 650 in an access network.
  • upper layer packets from the core network are provided to a controller/processor 675.
  • the controller/processor 675 implements the functionality of the L2 layer.
  • the controller/processor 675 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations to the UE 650 based on various priority metrics.
  • the controller/processor 675 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the UE 650.
  • the transmit (TX) processor 616 implements various signal processing functions for the LI layer (i.e., physical layer).
  • the signal processing functions include coding and interleaving to facilitate forward error correction (FEC) at the UE 650 and 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)).
  • FEC forward error correction
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase- shift keying
  • M-QAM M-quadrature amplitude modulation
  • Each stream is then 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 674 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 650.
  • Each spatial stream may then be provided to a different antenna 620 via a separate transmitter 618TX.
  • Each transmitter 618TX may modulate an RF carrier with a respective spatial stream for transmission.
  • each receiver 654RX receives a signal through its respective antenna 652. Each receiver 654RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 656.
  • the RX processor 656 implements various signal processing functions of the LI layer. The RX processor 656 may perform spatial processing on the information to recover any spatial streams destined for the UE 650. If multiple spatial streams are destined for the UE 650, they may be combined by the RX processor 656 into a single OFDM symbol stream. The RX processor 656 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT).
  • FFT Fast Fourier Transform
  • 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 e B 610. These soft decisions may be based on channel estimates computed by the channel estimator 658.
  • the soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 610 on the physical channel.
  • the data and control signals are then provided to the controller/processor 659.
  • the controller/processor 659 implements the L2 layer.
  • the controller/processor can be associated with a memory 660 that stores program codes and data.
  • the memory 660 may be referred to as a computer-readable medium.
  • the controller/processor 659 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network.
  • the upper layer packets are then provided to a data sink 662, which represents all the protocol layers above the L2 layer.
  • Various control signals may also be provided to the data sink 662 for L3 processing.
  • the controller/processor 659 is also responsible for error detection using an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support HARQ operations.
  • ACK acknowledgement
  • NACK negative acknowledgement
  • a data source 667 is used to provide upper layer packets to the controller/processor 659.
  • the data source 667 represents all protocol layers above the L2 layer.
  • the controller/processor 659 implements the L2 layer for the user plane and the control plane by providing header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations by the eNB 610.
  • the controller/processor 659 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the eNB 610.
  • Channel estimates derived by a channel estimator 658 from a reference signal or feedback transmitted by the eNB 610 may be used by the TX processor 668 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the TX processor 668 may be provided to different antenna 652 via separate transmitters 654TX. Each transmitter 654TX may modulate an RF carrier with a respective spatial stream for transmission.
  • the UL transmission is processed at the eNB 610 in a manner similar to that described in connection with the receiver function at the UE 650.
  • Each receiver 618RX receives a signal through its respective antenna 620.
  • Each receiver 618RX recovers information modulated onto an RF carrier and provides the information to a RX processor 670.
  • the RX processor 670 may implement the LI layer.
  • the controller/processor 675 implements the L2 layer.
  • the controller/processor 675 can be associated with a memory 676 that stores program codes and data.
  • the memory 676 may be referred to as a computer-readable medium.
  • the control/processor 675 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 650.
  • Upper layer packets from the controller/processor 675 may be provided to the core network.
  • the controller/processor 675 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • FIG. 7A is a diagram 750 illustrating an example of an evolved MBMS
  • the eNBs 752 in cells 752' may form a first MBSFN area and the eNBs 754 in cells 754' may form a second MBSFN area.
  • the eNBs 752, 754 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 752', 754' and 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.
  • the first MBSFN area may support a first eMBMS broadcast service, such as by providing a particular news broadcast to UE 770.
  • the second MBSFN area may support a second eMBMS broadcast service, such as by providing a different news broadcast to UE 760.
  • Each MBSFN area supports a plurality of physical multicast channels (PMCH) (e.g., 15 PMCHs). Each PMCH corresponds to a multicast channel (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.
  • PMCH physical multicast channels
  • MCH multicast channel
  • MTCHs multicast traffic channels
  • a UE can camp on an LTE cell to discover the availability of eMBMS service access and a corresponding access stratum configuration.
  • the UE may acquire a system information block (SIB) 13 (SIB 13).
  • SIB 13 system information block 13
  • the UE may acquire an MBSFN Area Configuration message on an MCCH.
  • the UE may acquire an MCH scheduling information (MSI) MAC control element.
  • MSI MCH scheduling information
  • the SIB 13 may indicate (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), sub frame allocation information indicating which sub frames of the radio frame as indicated by repetition period and offset can transmit MCCH; and (3) an MCCH change notification configuration.
  • MCS modulation and coding scheme
  • 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.
  • TMGI temporary mobile group identity
  • MSP MCH scheduling period
  • FIG. 7B is a diagram 790 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 particular device may encounter constraints particular to the device.
  • Such devices may include Machine Type Communication (MTC) devices, and DL-only devices (i.e., devices capable of supporting downlink but not uplink, for example, electronic advertisement boards, electronic news boards, stock ticker boards).
  • MTC Machine Type Communication
  • DL-only devices i.e., devices capable of supporting downlink but not uplink, for example, electronic advertisement boards, electronic news boards, stock ticker boards.
  • Such devices are examples of lower- cost devices that may not include the features of other more sophisticated devices.
  • the constraints may include constraints related to payload size, bandwidth and/or antenna configuration.
  • some devices may be limited to receiving and/or processing a payload of a particular size (e.g., 1000 bits per transmission time interval (TTI)).
  • some devices may be limited to receiving and/or processing a downlink bandwidth of a particular width.
  • the particular width may correspond to a width spanning a particular number of consecutive (or contiguous) resource blocks (RBs), such as 6 RBs).
  • RBs resource blocks
  • some devices may be configured with only a single operational antenna. The noted examples may align with requirements relating to unicast.
  • Embodiments of the present invention are directed to addressing one or more of the above constraints.
  • FIG. 8 is a diagram illustrating reception of an eMBMS service according to one embodiment.
  • a UE 806 receives one or more PMCHs from an e B 802 in a subframe 810.
  • PMCHi 840, PMCH 2 850, PMCH m 860 may be received in RB pairs in the subframe 810.
  • Each of the PMCHs 840, 850, 860 individually occupies less than or equal to a total number of RB pairs in the subframe 810.
  • the PMCHs may be frequency- division multiplexed in the subframe 810.
  • One or more of the PMCHs 840, 850, 860 may occupy only RB pairs that are within two or more contiguous RB pairs in the subframe 810.
  • the two or more contiguous RB pairs may be contiguous with respect to frequency.
  • PMCHi 840 occupies only RB pairs that are within the group of contiguous RB pairs formed by RB pairs 842-1, 842-2, 842- 3, 842-4, 842-5, and 842-6. PMCHi 840 may occupy any combination of one or more of the noted RB pairs.
  • PMCHi 840 may occupy any of the following combinations: RB pair 842-1 only; RB pairs 842-1 and 842-2 only; RB pairs 842-1 and 842-3 only; RB pairs 842-1, 842-2, and 842-3 only; RB pairs 842-1 and 842-4 only; RB pairs 842-1, 842-2, and 842-4 only; RB pairs 842-1, 842-2, and 842-4 only; RB pairs 842-1, 842-2, 842-3, and 842-4 only; and so forth.
  • PMCHi 840 may occupy any of 63 possible combinations of one or more RB pairs.
  • the UE 806 is not required to process a downlink bandwidth having a width that exceeds that of 6 contiguous RB pairs (i.e., a maximum occupied bandwidth of 1.08 MHz).
  • the size of the payload received by the UE 806 may be kept at or below a certain size (e.g., 1000 bits per transmission time interval (TTI)).
  • SIB 13 may include information that indicates the subframes that are allocated to the MCCH.
  • SIB 13 may include frequency resource information that indicates subcarriers allocated to each of PMCHs 840, 850, 860.
  • such frequency resource information may be included in the MCCH (which further includes information that indicates the subframes that are allocated to each PMCH).
  • such frequency resource information may be included in the MSI MAC control element (which further includes the subframes that are allocated to each MTCH).
  • the group of contiguous RB pairs corresponding to a particular PMCH may hop across frequency. In other words, the group of contiguous RB pairs may hop within frequency across different subframes. This frequency hopping achieves frequency diversity, which improves the reception performance of the UE 806.
  • a frequency hopping pattern may be indicated to the UE 806 via at least one of the SIB 13, the MCCH, or the MSI MAC control element, or may be predetermined as a function as at least one of subframe number, radio frame number, subframe index, PMCH index, MTCH index or MBSFN area index.
  • the UE 806 may receive a PDSCH carrying unicast data in at least one other RB pair in the subframe 810 (e.g., in region 820 of the subframe).
  • unicast data may be frequency-division multiplexed with the PMCHs 840, 850, 860 in the subframe 810.
  • a cyclic prefix (CP) for the PDSCH may be of a same type as a CP for the PMCHs 840, 850, 860.
  • a CP for the PDSCH may be of a different type than a CP for the PMCHs 840, 850, 860.
  • a guard band spanning at least one RB pair may be located in the subframe 810 between the PDSCH and the PMCHs 840, 850, 860 (e.g., in region 830 of the subframe). This may occur, for example, when the CP for the PDSCH is of a different type than the CP for the PMCHs 840, 850, 860.
  • NULL tones that are present in the subframe 810 may be used for interference estimation. And the power on those used tones can be made higher compared to the case where no NULL tones are present.
  • One or more RB pairs in the subframe 810 that are unoccupied by PMCHs 840, 850, 860 may correspond to one or more guard bands. For example, if one or more unoccupied RB pairs are located between PMCHi 840 and PMCH 2 850, the unoccupied RB pair(s) may be used as a guard band located between PMCHi 840 and PMCH 2 850. This improves performance in applications involving, for example, higher speed and/or frequency offset.
  • the UE 806 may receive the MBSFN-RS in the RB pairs in the sub frame 810 that are occupied by PMCHs 840, 850, 860. Alternatively (or in addition), the UE 806 may receive the MBSFN-RS in one or more RB pairs in the sub frame 810 that are not occupied by any of the PMCHs.
  • MBSFN-RS MBSFN reference signals
  • FIG. 9 is a diagram illustrating reception of an eMBMS according to one embodiment.
  • a UE 906 receives one or more PMCHs from an eNB 902 in a sub frame 910.
  • PMCHi 940, PMCH 2 950, PMCH m 960 may be received in RB pairs in the subframe 910.
  • Each of the PMCHs 940, 950, 960 individually occupies less than or equal to a total number of RB pairs in the subframe 910.
  • the PMCHs may be frequency- division multiplexed in the subframe 910.
  • Each of the PMCHs 940, 950, 960 may individually occupy no more than a particular number of RB pairs in the subframe 910. For example, each of the PMCHs 940, 950, 960 may individually occupy a predetermined number of RB pairs that is fewer than the total number of RB pairs in the subframe 910. As a further example, each of the PMCHs 940, 950, 960 may individually occupy six or fewer RB pairs.
  • the RB pairs occupied by a particular PMCH may not necessarily fall within a group of a particular number of contiguous RB pairs.
  • the RB pairs occupied by PMCHi 940 may include RB pairs in region 940-1 (e.g., RB pairs 942-1 and 942-2) as well as RB pairs in regions 940-2 and 940-3.
  • region 950-1 is located between regions 940-1 and 940-2
  • region 950-2 is located between regions 940-2 and 940-3. Because the RB pairs occupied by PMCHi 940 may span a larger frequency range (e.g., a range spanning up to the entire bandwidth of the subframe 910), frequency diversity may be achieved.
  • RB pairs occupied by PMCH 2 950 may include RB pairs in regions 950-1 and 950-2 of the subframe 910. As noted above, the region 950-1 is located between the regions 940-1 and 940-2, and the region 950-2 is located between the regions 940-2 and 940-3. Accordingly, the RB pairs occupied by PMCH 2 950 may be interleaved with the RB pairs occupied by PMCHi 940.
  • each of the PMCHs 940, 950, 960 may individually occupy no more than a particular number of RB pairs in the subframe 910. As one example, each of the PMCHs 940, 950, 960 may individually occupy six or fewer RB pairs. Therefore, the size of the payload received by the UE 806 may be kept at or below a certain size (e.g., 1000 bits per transmission time interval (TTI)).
  • TTI transmission time interval
  • each of the PMCHs may occupy a larger number of RB pairs.
  • each of the PMCHs 940, 950, 960 may individually occupy a predetermined number of RB pairs that is fewer than the total number of RB pairs in the subframe 910.
  • SIB 13 may include information that indicates the subframes that are allocated to the MCCH.
  • SIB 13 may include frequency resource information that indicates subcarriers allocated to each of PMCHs 940, 950, 960.
  • such frequency resource information may be included in the MCCH (which further includes information that indicates the subframes that are allocated to each PMCH).
  • such frequency resource information may be included in the MSI MAC control element (which further includes the subframes that are allocated to each MTCH).
  • such frequency resource information may be predetermined as a function of at least one of subframe number, radio frame number, subframe index, PMCH index, MTCH index, or MBSFN area index.
  • the UE 906 may receive a PDSCH carrying unicast data in at least one other RB pair in the subframe 910 (e.g., in region 920 of the subframe).
  • unicast data may be frequency-division multiplexed with the PMCHs in the subframe 910.
  • the RB pairs that are allocated to unicast data may be the RB pairs that remain after all available (or desired) MTCHs have been assigned to the subframe 910.
  • a CP for the PDSCH may be of a same type as a CP for the PMCHs 940, 950, 960.
  • a CP for the PDSCH may be of a different type than a CP for the PMCHs 940, 950, 960.
  • a guard band spanning at least one RB pair may be located in the subframe 910 between the PDSCH and the PMCHs 940, 950, 960 (e.g., in region 930 of the subframe). This may occur, for example, when the CP for the PDSCH is of a different type than the CP for the PMCHs 940, 950, 960.
  • NULL tones that are present in the subframe 910 may be used for interference estimation. And the power on those used tones can be made higher compared to the case where no NULL tones are present.
  • the UE 906 may receive the MBSFN-RS in the RB pairs in the subframe 910 that are occupied by PMCHs 940, 950, 960. Alternatively (or in addition), the UE 906 may receive the MBSFN-RS in one or more RB pairs in the subframe 910 that are not occupied by any of the PMCHs.
  • MBSFN-RS MBSFN reference signals
  • the UE 806 of FIG. 8 and/or the UE 906 of FIG. 9 may be a DL-only device capable of supporting DL but not UL. Such a device is not configured to support UL signaling corresponding to layers down from L3 to LI, including NAS, RRC, PDCP, RLS, MAC, and PHY. Accordingly, the DL-only device is not configured to support registration procedures. In addition, the DL-only device is not configured to support eMBMS reception procedures relating to RRC-Connected state, which may involve sending reports to a serving cell. It is possible that the DL-only device may support only a single antenna.
  • the DL-only device may not be readily mobile, i.e., it may be primarily stationary in nature. (However, the DL- only device is configured to receive paging messages, e.g., to be notified of SIB changes and MCCH change notifications.)
  • the UE 806 and/or the UE 906 may have one or more of the noted characteristics, according to embodiments of the present invention, the UE 806 and/or the UE 906 may still be capable of receiving an eMBMS service despite being a DL-only device.
  • a specific TMGI may be reserved for DL-only devices located in a specific network or area. Also, the network may have knowledge of the number of DL-only devices in the area (e.g., the number of such devices may be preconfigured).
  • FIG. 10 is a diagram illustrating transmission of a SIB from multiple cells.
  • the transmission may be used to support cell broadcasting to a lower-cost device.
  • a DL-only device is one example of a lower-cost device.
  • a SIB e.g., a new SIB
  • MTC data may include data commonly used by MTC devices in applications such as smart grid, road security and smart meters.
  • the SIB may be similar to (or the same as) existing SIBs, including SIB 10, SIB 11, and/or SIB 12.
  • the SIB may be broadcast via the BCCH.
  • the broadcast of the SIB may involve Coordinated Multipoint (CoMP) techniques. Accordingly, the SIB including the same MTC data may be concurrently transmitted from multiple cells (e.g., eNBs 1002, 1004, and 1006).
  • the coordinated transmission of the SIB on the BCCH improves spectral efficiency for users of a whole cell and, especially, for users located at the edge of a cell, who may experience a degraded level of performance.
  • decoding the SIB may involve decoding an identifier common to the cells corresponding to eNBs 1002, 1004, and 1006. Such a common ID may be used to scramble (or decode) the BCCHs received from different cells. The common ID may be provided in a separate SIB. In addition, decoding the SIB may involve combining the same MTC data that is received from the different cells.
  • a UE may assign itself to a particular category based, e.g., on whether it is capable of receiving an MBMS service (e.g., eMBMS). By reporting the particular category to a network, the UE effectively informs the network of one or more services that it is capable of receiving.
  • an MBMS service e.g., eMBMS
  • a UE may assign itself to Category 0 (CatO) if it is capable of receiving unicast data but not MBMS data, including eMBMS data.
  • the UE may assign itself to Category Y (CatY) if it is capable of receiving MBMS data (including eMBMS data) but not other data (e.g., unicast data).
  • Y may denote a nonzero integer.
  • the UE may assign itself to Category X (CatX) if it is capable of receiving unicast data and MBMS data (including eMBMS data).
  • X may denote a nonzero integer.
  • a CatO UE may optionally support eMBMS under a particular constraint (i.e., 3112 bits MCSO under 20 MHz). It is understood that no change may be necessary regarding MBMS reception on RAN (Radio Access Network). Such agreement is, however, suboptimal from a system efficiency point of view. For example, with large MBSFN gain, the supported MCS can be much higher than MCSO, however, the network is forced to use MCSO for transmission if the bandwidth is 20MHz as current MBSFN transmission has to occupy entire system bandwidth.
  • radio layer configuration and/or service layer configuration may be simplified by using a subset of current capabilities and/or features.
  • embodiments described herein may involve supporting only a limited number of MBSFN areas and/or a limited number of PMCHs.
  • a UE may support only 1 MBSFN area and 1 PMCH.
  • a UE may not necessarily be required to support particular functions associated with MBMS, such as counting and/or service continuity.
  • a UE may use a pre-configured MBMS session for one or more pre-configured groups. For example, the UE may belong to only one MTC group. A TMGI in the UE may be pre-configured for the group to which it belongs.
  • an MCCH modification period may be set to longer than a specific duration (e.g., 5 seconds, or 10 seconds) in order to conserve battery life. Accordingly, the UE may not need to check the MCCH as frequently. Alternatively, if the UE does not support MCCH Change Notification, then it may merely check the MCCH upon wake up.
  • a specific duration e.g., 5 seconds, or 10 seconds
  • the UE may support fewer TMGIs/radio bearers. For example, the UE may support only two TMGIs: a first TMGI for a service announcement channel, and a second TMGI for data downloading. As another example, the UE may support only one TMGI.
  • service announcement information may be acquired from, for example, a unicast channel.
  • preconfigured service announcement information e.g., session description protocol (SDP) data, schedule information
  • SDP session description protocol
  • embodiments described herein may involve supporting file downloading over File Delivery over Unidirectional Transport (FLUTE), but may not necessarily require supporting eMBMS streaming and/or Dynamic Adaptive Streaming over HTTP (DASH).
  • embodiments may involve supporting file repair, but may not necessarily require supporting reception report.
  • embodiments may not necessarily require supporting service layer security for file downloading.
  • FIG. 15 is a diagram illustrating an example of service layer simplification. To achieve simplification, one or more of the following may be omitted: User Service Bundle Description 1502, FEC Repair Stream Description 1510, mediaPresentationDescription 1506, Media Presentation Description 1520, or Initialisation Segment Description 1522.
  • FIG. 11 is a flow chart 1100 of a method of receiving an MBMS service.
  • the method may be performed by a UE (e.g., the UE 806, 906 of FIGs. 8, 9).
  • the UE receives one or more PMCHs in a plurality of RB pairs in a subframe, each of the one or more PMCHs occupying less than or equal to a total number of RB pairs in the subframe.
  • the UE 806 receives one or more of PMC3 ⁇ 4 840, PMCH 2 850, ..., PMCH m 860 in the subframe 810.
  • PMC3 ⁇ 4 840 receives one or more of PMCH 2 850, ..., PMCH m 860 in the subframe 810.
  • the UE 906 receives one or more of PMCHi 940, PMCH 2 950, PMCH m 960 in the subframe 910.
  • the UE decodes at least one PMCH of the one or more PMCHs in the subframe.
  • the UE may receive frequency resource information indicating subcarriers allocated to each of the one or more PMCHs.
  • the UE 806 may receive frequency resource information that indicates subcarriers allocated to each of PMCHs 840, 850, 860.
  • the UE 906 may receive frequency resource information that indicates subcarriers allocated to each of PMCHs 940, 950, 960.
  • the UE may receive a frequency hopping pattern for the one or more PMCHs.
  • the UE may receive a PDSCH in at least one other RB pair in the subframe, the PDSCH carrying unicast data.
  • the UE 806 may receive a PDSCH carrying unicast data in an RB pair in region 820 of the subframe 810.
  • the UE 906 may receive a PDSCH carrying unicast data in an RB pair in region 920 of the subframe 910.
  • the UE may also receive MBSFN-RS in the plurality of RB pairs in the subframe. For example, with reference to FIG.
  • the UE 806 may receive the MBSFN-RS in the RB pairs in the subframe 810 that are occupied by PMCHs 840, 850, 860. Alternatively (or in addition), the UE 806 may receive the MBSFN-RS in one or more RB pairs in the subframe 810 that are not occupied by any of the PMCHs.
  • FIG. 12 is a flow chart 1200 of a method of receiving MTC data.
  • the method may be performed by a UE (e.g., the UE 806, 906 of FIGs. 8, 9).
  • the UE receives a paging message indicating transmission of the MTC data.
  • the UE receives a paging message indicating transmission of the MTC data.
  • the UE decodes a SIB including the MTC data, in response to the receiving the paging message. For example, with reference to FIG. 10, the UE 1008 decodes a SIB.
  • the SIB may be concurrently transmitted from multiple cells (e.g., e Bs 1002, 1004, and 1006).
  • FIG. 13 is a conceptual data flow diagram 1300 illustrating the data flow between different modules/means/components in an exemplary apparatus 1302.
  • the apparatus may be a UE.
  • the apparatus 1302 includes a reception module 1304 and a decoding module 1306.
  • the apparatus 1302 may also include a transmission module 1310. If the apparatus 1302 is a DL-only device, it may not necessarily include the transmission module.
  • the reception module 1204 may receive one or more PMCHs in a plurality of RB pairs in a subframe, each of the one or more PMCHs occupying less than or equal to a total number of RB pairs in the subframe.
  • the reception module 1304 may also receive frequency resource information indicating subcarriers allocated to each of the one or more PMCHs.
  • the reception module 1304 may also receive a frequency hopping pattern for the one or more PMCHs.
  • the reception module 1304 may also receive a PDSCH in at least one other RB pair in the subframe, the PDSCH carrying unicast data.
  • the reception module 1304 may also receive MBSFN-RS in the plurality of RB pairs in the subframe.
  • the decoding module 1306 may decode at least one PMCH of the one or more PMCHs in the subframe.
  • the reception module 1304 may receive a paging message indicating transmission of the MTC data.
  • the decoding module 1306 may decode a SIB including the MTC data, in response to the receiving the paging message.
  • the apparatus may include additional modules that perform each of the steps of the algorithm in the aforementioned flow charts of FIGs. 11 and 12. As such, each step in the aforementioned flow charts of FIGs. 11 and 12 may be performed by a module and the apparatus may include one or more of those modules.
  • the modules 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. 14 is a diagram 1400 illustrating an example of a hardware implementation for an apparatus 1302' employing a processing system 1414.
  • the processing system 1414 may be implemented with a bus architecture, represented generally by the bus 1424.
  • the bus 1424 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1414 and the overall design constraints.
  • the bus 1424 links together various circuits including one or more processors and/or hardware modules, represented by the processor 1404, the modules 1304, 1306, 1308 and the computer-readable medium / memory 1406.
  • the bus 1424 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 1414 may be coupled to a receiver 1410. (The receiver 1410 may be a transceiver.)
  • the receiver 1410 is coupled to one or more antennas 1420.
  • the receiver 1410 provides a means for receiving communications from various other apparatus over a transmission medium.
  • the receiver 1410 receives a signal from the one or more antennas 1420, extracts information from the received signal, and provides the extracted information to the processing system 1414, specifically the reception module 1304. If the receiver 1410 is a transceiver, the receiver 1410 receives information from the processing system 1414, specifically the transmission module 1308, and based on the received information, generates a signal to be applied to the one or more antennas 1320.
  • the processing system 1414 includes a processor 1404 coupled to a computer-readable medium / memory 1406.
  • the processor 1404 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1406.
  • the software when executed by the processor 1404, causes the processing system 1414 to perform the various functions described supra for any particular apparatus.
  • the computer- readable medium / memory 1406 may also be used for storing data that is manipulated by the processor 1404 when executing software.
  • the processing system further includes at least one of the modules 1304, 1306, and 1308.
  • the modules may be software modules running in the processor 1404, resident/stored in the computer readable medium / memory 1406, one or more hardware modules coupled to the processor 1404, or some combination thereof.
  • the processing system 1414 may be a component of the UE 650 and may include the memory 660 and/or at least one of the TX processor 668, the RX processor 656, and the controller/processor 659.
  • the apparatus 1302/1302' for wireless communication includes means for receiving one or more physical multicast channels PMCHs in a plurality of RB pairs in a subframe, and means for decoding at least one PMCH of the one or more PMCHs in the subframe.
  • the apparatus 1302/1302' may also include means for receiving frequency resource information indicating subcarriers allocated to each of the one or more PMCHs, means for receiving a frequency hopping pattern for the one or more PMCHs, means for receiving MBSFN-RS in the plurality of RB pairs in the subframe (and, in one example, in at least one other RB pair in the subframe unoccupied by a PMCH), and/or means for receiving a PDSCH in at least one other RB pair in the subframe.
  • the apparatus 1302/1302' includes means for receiving a paging message indicating transmission of the MTC data, and means for decoding a system information block (SIB) including the MTC data, in response to the receiving the paging message.
  • SIB system information block
  • the aforementioned means may be one or more of the aforementioned modules of the apparatus 1302 and/or the processing system 1414 of the apparatus 1302' configured to perform the functions recited by the aforementioned means.
  • the processing system 1414 may include the TX Processor 668, the RX Processor 656, and the controller/processor 659.
  • the aforementioned means may be the TX Processor 668, the RX Processor 656, and the controller/processor 659 configured to perform the functions recited by the aforementioned means.
  • Combinations such as "at least one of A, B, or C,” “at least one 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.
  • combinations such as “at least one of A, B, or C,” “at least one 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.

Landscapes

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

Abstract

L'invention concerne un procédé, un appareil, et un produit-programme d'ordinateur pour des communications sans fil. L'appareil reçoit un ou plusieurs PMCH dans une pluralité de paires de RB dans une sous-trame. Chacun du ou des PMCH occupe un espace inférieur ou égal à un nombre total de paires de RB dans la sous-trame. De plus, l'appareil décode au moins un PMCH du ou des PMCH dans la sous-trame. L'appareil peut également recevoir des informations de ressources de fréquence indiquant des sous-porteuses attribuées à chacun du ou des PMCH, et recevoir un motif de saut de fréquence pour le ou les PMCH. L'appareil peut recevoir en outre un PDSCH dans au moins une autre paire de RB dans la sous-trame. Le PDSCH transporte des données d'unidiffusion. D'autre part, l'appareil peut recevoir un RS MBSFN dans la pluralité de paires de RB dans la sous-trame.
PCT/CN2014/084628 2014-08-18 2014-08-18 Dispositif économique avec support de diffusion WO2016026068A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/084628 WO2016026068A1 (fr) 2014-08-18 2014-08-18 Dispositif économique avec support de diffusion

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/084628 WO2016026068A1 (fr) 2014-08-18 2014-08-18 Dispositif économique avec support de diffusion

Publications (1)

Publication Number Publication Date
WO2016026068A1 true WO2016026068A1 (fr) 2016-02-25

Family

ID=55350061

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/084628 WO2016026068A1 (fr) 2014-08-18 2014-08-18 Dispositif économique avec support de diffusion

Country Status (1)

Country Link
WO (1) WO2016026068A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI724458B (zh) * 2018-07-16 2021-04-11 新加坡商聯發科技（新加坡）私人有限公司 當跳頻在移動通信中啟用時的頻域資源分配方法和裝置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130272148A1 (en) * 2012-04-13 2013-10-17 Mo-Han Fong Small data communications in a wireless communication network
CN103650374A (zh) * 2011-05-02 2014-03-19 三星电子株式会社 用户设备的接入控制方法和装置
WO2014069946A1 (fr) * 2012-11-01 2014-05-08 Lg Electronics Inc. Procédé et appareil pour gérer des groupes de programmation de caractéristiques de dispositifs dans un système de communication sans fil
US20140198749A1 (en) * 2013-01-14 2014-07-17 Qualcomm Incorporated Transmission and processing of higher order modulation
CN103973397A (zh) * 2013-01-29 2014-08-06 中兴通讯股份有限公司 Ack/nack信息的发送及接收方法、基站及终端

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103650374A (zh) * 2011-05-02 2014-03-19 三星电子株式会社 用户设备的接入控制方法和装置
US20130272148A1 (en) * 2012-04-13 2013-10-17 Mo-Han Fong Small data communications in a wireless communication network
WO2014069946A1 (fr) * 2012-11-01 2014-05-08 Lg Electronics Inc. Procédé et appareil pour gérer des groupes de programmation de caractéristiques de dispositifs dans un système de communication sans fil
US20140198749A1 (en) * 2013-01-14 2014-07-17 Qualcomm Incorporated Transmission and processing of higher order modulation
CN103973397A (zh) * 2013-01-29 2014-08-06 中兴通讯股份有限公司 Ack/nack信息的发送及接收方法、基站及终端

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI724458B (zh) * 2018-07-16 2021-04-11 新加坡商聯發科技（新加坡）私人有限公司 當跳頻在移動通信中啟用時的頻域資源分配方法和裝置
US10999023B2 (en) 2018-07-16 2021-05-04 Mediatek Singapore Pte. Ltd. Method and apparatus for frequency domain resource allocation when frequency hopping is enabled in mobile communications

Similar Documents

Publication Publication Date Title
KR102457679B1 (ko) 송신 모드의 지원 및 ptm(point-to-multipoint) 송신의 pdcch 블라인드 디코드들에 대한 영향
EP2832164B1 (fr) Extension de longueur de préfixe cyclique dans un système lte ayant une sous-trame de monodiffusion mixte
US10484193B2 (en) EMBMS session suspend/stop notification
US20130294318A1 (en) Efficient update of tmgi list in lte embms
KR102008596B1 (ko) Ｌｔｅ 에 있어서 사운딩 레퍼런스 신호들 및 근접도 검출
US20160014571A1 (en) Enhanced embms interest indication
US9532185B2 (en) Achieving fast EMBMS channel switching and adding in LTE
EP2944047B1 (fr) Transmission et traitement de modulation d'ordre supérieur
WO2017035727A1 (fr) Demande de répétition automatique de diffusion
US20150049600A1 (en) Prioritizing frequencies in embms multi-frequency deployment during rlf/oos
US20160174195A1 (en) Embms audio packets protection in dual-sim dual-standby or srlte mobile device
US9641986B2 (en) Prioritization of concurrent inter-frequency/inter-RAT measurement and eMBMS service reception
WO2015101085A1 (fr) Amélioration de consommation d'énergie de batterie d'équipement utilisateur dans des facilitateurs de système de communication de groupe
US9712981B2 (en) Client ID and multi-application support for reception reporting
WO2016026068A1 (fr) Dispositif économique avec support de diffusion

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14900325

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14900325

Country of ref document: EP

Kind code of ref document: A1