Patent Description:
<CIT> relates to evolved multimedia broadcast multicast service (eMBMS) on enhanced component carriers (eCCs). <CIT> relates to extending a length of a cyclic prefix used for transmitting signals in a wireless communication system implementing a mixed carrier design.

<NUM> NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (such as with Internet of Things (IoT)), and other requirements.

Some wireless communication technologies support the transmission of broadcast services to various devices. In some regions, however, it is possible that the channelization of broadcast frequency band(s) for a broadcast service may not be compatible with bandwidths defined in the wireless communication technology that is desired for transmitting the broadcast service.

However, it will be apparent to those of ordinary skill in the art that these concepts may be practiced without these specific details. In some instances, structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Various implementations relate generally to providing multicast broadcast services. Some implementations more specifically relate to providing a multicast broadcast (MB) service using one or more system bandwidths defined for a desired radio access technology over which the MB service is provided. Bandwidth sizes of the system bandwidths supported by the desired radio access technology, however, may not include or match the bandwidth sizes defined by the specific channelization for the MB services. For example, the permitted bandwidth sizes for channels of the MB service may include <NUM>, <NUM>, or <NUM> megahertz (MHz), whereas the system bandwidth sizes defined for channels of the desired radio access technology (for example, fifth generation (<NUM>) new radio (NR), long term evolution (LTE)) may include <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>, among other examples, but not <NUM>, <NUM> or <NUM> (or otherwise not include the bandwidth size defined for the MB service). Aspects described herein relate to supporting MB services over a radio access technology in such scenarios in which the bandwidth size defined for the MB service does not match the supported bandwidth sizes of the radio access technology.

In some aspects, new system bandwidths, or bandwidth sizes, can be defined and supported in the radio access technology for providing MB services. In some implementations, a node (for example, a base station) can indicate the new bandwidth sizes for the MB services in a master information block (MIB), for example, by using otherwise unused values of an existing field or information element (IE), or by defining or using a new or different field or IE to indicate the new bandwidth sizes, among other examples. In some implementations, nodes communicating in the wireless network can initially select, indicate, or otherwise utilize, for the radio access technology, a bandwidth size supported by the radio access technology that is larger or smaller than the bandwidth size defined for the MB service. In some such implementations, a node (for example, a base station) can subsequently signal the bandwidth size for the MB service (the "MB bandwidth" or "MB bandwidth size") to UEs desiring to receive the MB service. For example, the MB bandwidth size can be signaled for a multicast-broadcast single-frequency network (MBSFN) area in a system information block (SIB) or in a broadcast channel information list, among other examples. A node (for example, a UE) receiving the signaling can subsequently utilize the MB bandwidth size for obtaining the MB service. In some implementations, the nodes can combine multiple component carriers (CCs) of the radio access technology to achieve the MB bandwidth size. For example, the CCs may have individual associated bandwidth sizes that are each smaller than the MB bandwidth size but, when the CCs are combined together, they may collectively achieve (or constitute) a resulting aggregate bandwidth size that at least matches (or exceeds) the MB bandwidth size for communicating the MB service.

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, among other examples (collectively referred to as "elements").

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, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more examples, the functions described may be implemented in hardware, software, or any combination thereof. By way of example, and not limitation, such computer-readable media can include 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.

The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations <NUM>, UEs <NUM>, an Evolved Packet Core (EPC) <NUM>, and another core network <NUM> (for example, a <NUM> Core (5GC)). The base stations <NUM> may include macrocells (high power cellular base station) or small cells (low power cellular base station).

The base stations <NUM> configured for <NUM> LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through first backhaul links <NUM> (for example, an S1 interface). In addition to other functions, the base stations <NUM> 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 (for example, 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 <NUM> may communicate directly or indirectly (for example, through the EPC <NUM> or core network <NUM>) with each other over third backhaul links <NUM> (for example, X2 interface). The third backhaul links <NUM> may be wired or wireless.

For example, the small cell 102a may have a coverage area 110a that overlaps the coverage area <NUM> of one or more macro base stations <NUM>. The communication links <NUM> between the base stations <NUM> and the UEs <NUM> may include uplink (UL) (also referred to as reverse link) transmissions from a UE <NUM> to a base station <NUM> or downlink (DL) (also referred to as forward link) transmissions from a base station <NUM> to a UE <NUM>. The communication links <NUM> may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, or transmit diversity. The base stations <NUM> / UEs <NUM> may use spectrum up to Y MHz (for example, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, among other examples) bandwidth size per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. Allocation of carriers may be asymmetric with respect to DL and UL (for example, more or fewer carriers may be allocated for DL than for UL).

Some UEs <NUM> may communicate with each other using device-to-device (D2D) communication link <NUM>.

The small cell 102a may operate in a licensed or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102a may employ NR and use the same <NUM> unlicensed frequency spectrum as used by the Wi-Fi AP <NUM>. The small cell 102a, employing NR in an unlicensed frequency spectrum, may boost coverage to or increase capacity of the access network.

A base station <NUM>, whether a small cell 102a or a large cell (for example, macro base station), may include or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB <NUM> may operate in a traditional sub <NUM> spectrum, in millimeter wave (mmW) frequencies, or near mmW frequencies in communication with the UE <NUM>. Communications using the mmW / near mmW radio frequency band (for example, <NUM> - <NUM>) has extremely high path loss and a short range. The base station <NUM> and the UE <NUM> may each include a plurality of antennas, such as antenna elements, antenna panels, or antenna arrays to facilitate the beamforming.

The base station <NUM> may transmit a beamformed signal to the UE <NUM> in one or more transmit directions 182a. The UE <NUM> may receive the beamformed signal from the base station <NUM> in one or more receive directions 182b.

The IP Services <NUM> may include the Intemet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, or other IP services.

The IP Services <NUM> may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, or other IP services.

The base station may include or be referred to as a gNB, 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), a transmit reception point (TRP), or some other suitable terminology. Examples of UEs <NUM> 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 (for example, MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs <NUM> may be referred to as IoT devices (for example, parking meter, gas pump, toaster, vehicles, heart monitor, among other examples).

Referring again to <FIG>, in some aspects, the UE <NUM> may include a communicating component <NUM> configured to receive a multicast broadcast (MB) service from a base station <NUM>, determine a MB bandwidth size for receiving communications related to the MB service, which may be determined based on a configuration of multiple bandwidth sizes defined for a radio access technology (for example, NR, LTE, etc.), one or more related parameters, or otherwise, or other functionalities described herein. In some aspects, the base station <NUM> may include a configuring component <NUM> configured to transmit the MB service to one or more UEs <NUM>, indicate the configuration of multiple bandwidth sizes defined for the radio access technology or for indicating the one or more parameters for determining the MB bandwidth size, or other functionalities described herein. Although the following description may be described in terms of <NUM> NR and related features, the concepts described herein may be applicable to other areas or wireless communication technologies, such as LTE, LTE-A, CDMA, GSM, etc..

In the examples provided by Figure s 2A, 2C, the <NUM>/NR frame structure is assumed to be TDD, with subframe <NUM> being configured with slot format <NUM> (with mostly DL), where D is DL, U is UL, and X is flexible for use between DL/UL, and subframe <NUM> being configured with slot format <NUM> (with mostly UL). Note that the description presented herein applies also to a <NUM>/NR frame structure that is TDD.

Other wireless communication technologies may have a different frame structure or different channels.

The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), or UCI.

The controller/processor <NUM> provides RRC layer functionality associated with broadcasting of system information (such as MIB, SIBs), RRC connection control (such as 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 TX processor <NUM> handles mapping to signal constellations based on various modulation schemes (such as binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (such as a pilot) in the time 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 channel estimate may be derived from a reference signal or channel condition feedback transmitted by the UE <NUM>.

The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal.

The controller/processor <NUM> is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station <NUM>, the controller/processor <NUM> provides RRC layer functionality associated with system information (for example, 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.

The controller/processor <NUM> is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.

At least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM> may be configured to perform aspects in connection with communicating component <NUM> of <FIG>.

At least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM> may be configured to perform aspects in connection with configuring component <NUM> of <FIG>.

Some wireless communication technologies, such as LTE, support dedicated broadcast carriers. For example, in LTE, a carrier can be downlink-only, multimedia broadcast multicast service (MBMS)-only (for example, no unicast support). This can be similar in spirit to MB standards like DVB-T, ATSC. Content can typically be free-to-air, where receivers may not need to be registered with the network or have credentials (such as subscriber identity module (SIM) credentials) to receive the service (for example, TV service, car or automobile related broadcast information). In many countries around the world, the channelization of broadcast frequency bands for MB services is in units of bandwidth sizes that are not compatible with LTE bandwidths. For example, LTE supports system bandwidth sizes of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> megahertz (MHz), which correspond to <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> physical resource blocks (PRBs). In Europe, for example, channelization for MB service channels may be in chunks of bandwidth of <NUM>, <NUM>, <NUM>. For deploying in some regions and some frequency bands, aspects described herein relate to supporting these MB bandwidth sizes in the radio access technology (for example, NR, LTE).

<FIG> is a flowchart of an example of a method <NUM> for determining a MB bandwidth size for receiving communications related to an MB service in accordance with some aspects of the present disclosure. The method <NUM> may be performed by a UE (such as the UE <NUM>, the apparatus <NUM>, the processing system <NUM>, which may include the memory <NUM> and which may be the entire UE <NUM> or a component of the UE <NUM>, such as the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>).

In method <NUM>, at Block <NUM>, a device (for example, a UE <NUM>) can receive a configuration for a first set of multiple configurable bandwidth sizes for receiving unicast services. In an aspect, communicating component <NUM>, for example, in conjunction with one or more of the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>, the memory <NUM>, the receiver 354RX, can receive (for example, from a base station <NUM>) a configuration for the first set of multiple configurable bandwidth sizes for receiving unicast services. For example, a radio access technology (such as NR, LTE, other cellular communication technologies) can define the multiple configurable bandwidth sizes for receiving unicast services or other services that may not specifically include a MB service, and in one example, the multiple configurable bandwidth sizes can correspond to the radio access technology (e.g., for unicast or other services defined by the radio access technology). For example, the configurable bandwidth sizes can include multiple bandwidth sizes that can be used in configuring a system bandwidth for a CC of the radio access technology, in terms of a number of resource blocks that can be associated with a frequency range.

For example, communicating component <NUM> can receive the configuration in a MIB for a CC, where the MIB has a downlink bandwidth IE indicating the downlink bandwidth or bandwidth size for the CC. In an example, the IE can be defined to indicate one of a set of configurable bandwidth sizes defined for the radio access technology, such as <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, and <NUM> PRBs (corresponding <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>, respectively) in NR/LTE. In a specific example, a base station can specify or fix the system bandwidth in MIB for both MBMS-dedicated and normal carriers in NR/LTE. The MIB format for each can be separate, but both may include an IE indicating downlink bandwidth for the CC, as shown in the examples below. An example of a MIB for a MBMS-dedicated carrier may have a format similar to the following:
<IMG>
An example of a MIB for a normal carrier may have a format similar to the following:
<IMG>
<IMG>.

In an example, MBMS-dedicated and normal (or mixed) carriers may use different scrambling for a primary broadcast channel (PBCH), so the UE can try both hypotheses when decoding (and then correspondingly interpret the MIB). In this regard, in an example, the UE <NUM> can determine the downlink bandwidth for the CC as one of the configurable bandwidth sizes in the configuration.

In method <NUM>, at Block <NUM>, the device (for example, UE <NUM>) can determine a MB bandwidth size for receiving a MB service, where the MB bandwidth size is different than each bandwidth size in the set of multiple configurable bandwidth sizes for receiving unicast services. In an aspect, communicating component <NUM>, for example, in conjunction with one or more of the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>, the memory <NUM>, can determine the MB bandwidth size for receiving the MB service, the MB bandwidth size being outside of the set (e.g., being different than each bandwidth size in the set) of multiple configurable bandwidth sizes for receiving unicast services. For example, the MB bandwidth size can correspond to a channelization of a broadcast frequency band for the MB service, as described, which may be defined as a bandwidth size of <NUM>, <NUM>, or <NUM> in some examples, or otherwise defined as a bandwidth size that is outside of the set of bandwidth sizes defined as configurable bandwidth sizes for the radio access technology (for example, not in the set of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> for NR/LTE). Various implementations, which can be provided in conjunction with one another or alternatively to one another, are described herein for determining the MB bandwidth size for providing the MB service using the radio access technology based on or otherwise in view of one or more of the multiple configurable bandwidth sizes of the radio access technology.

In one example, the MIB that indicates the downlink bandwidth for a CC can be adapted to indicate MB bandwidth sizes as well, and communicating component <NUM> can determine the MB bandwidth size based on the MIB in this regard. In a specific example, the MIB as defined may have two spare values possible for indicating in the enumeration for the downlink bandwidth IE (for example, beyond indicating <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, and <NUM> PRBs). In an example, a base station <NUM> (or other network component, the base station <NUM> or other network component being more generally referred to herein as the "network") can use one or more of the spare values of the enumeration to indicate one or more MB bandwidth sizes, which can be for a given CC in one example. In one specific example, if the number of new channel bandwidth sizes for MB is two or less, the dl-bandwidth-MBMS-r14 field can be used (which has two spare values) to introduce the new channel bandwidth sizes. For example, <NUM> and <NUM> PRBs can be introduced, corresponding approximately to <NUM> and <NUM>, respectively. In a specific example, the MIB can have a format similar to the following:
<IMG>
where "n30" and "n40" occupy the spare values. In this example, communicating component <NUM> can receive the MIB, and where the downlink bandwidth IE indicates one of the spare values for the downlink bandwidth, the communicating component <NUM> can determine the associated MB bandwidth size for the CC (for example, as <NUM> or <NUM> PRBs, or correspondingly <NUM> or <NUM> in the above example). For example, legacy UEs may not understand these values, and thus may not camp on, or try to access services of, this cell. In this regard, potential incompatibility issues can be avoided. Additionally, the set of possible bandwidth sizes for dedicated-MBMS carriers may be different from the set of possible bandwidths for normal LTE/NR carriers (e.g. the values "n30" and "n40" are only present in a MIB over a dedicated-MBMS carrier).

In another specific example, the MIB can be adapted such that the network can use one of the spare values of the enumeration to indicate an extended MIB. The extended MIB can have another IE defining a new enumeration of one or more MB bandwidth sizes. This can allow for supporting more than two possible MB bandwidth sizes where the MIB can indicate the spare value and then can indicate the MB bandwidth size in the new enumeration. In this example, communicating component <NUM> can determine the MB bandwidth size based on detecting the spare value in the downlink bandwidth used to signal that the MIB has the new enumeration, and then determining the MB bandwidth size based on the value of the new enumeration. For example, if the number of new channel bandwidth sizes for MB is more than two (for example, more than the number of spare values), some of the spare bits can be used to signal this information. For example, the MIB can introduce new channel bandwidth sizes with <NUM>, <NUM>, <NUM> PRBs. In this example, the dl-bandwidth IE can be set to a different value (to prevent legacy UEs from camping in this cell), and some of the spare bits can be used to signal the real value. In a specific example, the MIB can have a format similar to the following:
<IMG>
where the network can indicate "other" in the downlink bandwidth IE to signal the existence of dl-Bandwidth-MBMS-r17 IE, which can specify the MB bandwidth size, and accordingly communicating component <NUM> can determine the MB bandwidth size (as <NUM>, <NUM>, or <NUM> PRBs, in this example). In another specific example, the MIB can have a format similar to the following:
<IMG>
<IMG>
where one spare value of the downlink bandwidth IE can defined to signal one MB bandwidth size (for example, <NUM> PRBs) and the other spare value (for example, as "other") to signal the existence of the dl-Bandwidth-MBMS-r17 IE, from which the communicating component <NUM> can determine the MB bandwidth size as <NUM> or <NUM> PRBs. In any case, in this example, communicating component <NUM> can determine the MB bandwidth size based on the MIB value(s), as described above.

In another example, the network can use certain combinations of channel bandwidth sizes and frequencies of the radio access technology that are not yet defined for use (for example, in a standard of the radio access technology) to indicate MB bandwidth sizes. For example, in a given frequency range for the radio access technology, a downlink bandwidth size of <NUM> PRBs (<NUM>) may not be currently supported, and for example, the network can use this combination of <NUM> PRBs in the given frequency range to indicate or imply configuration of a MB bandwidth size (for example, <NUM> PRBs, or <NUM>). The network and UE can know or configure the mapping of the frequency range and bandwidth combination(s) to the associated MB bandwidth size(s) such that when the communicating component <NUM> receives the frequency range and bandwidth combination(s) in the MIB, the communicating component <NUM> can instead determine the associated MB bandwidth size. For example, the interpretation of channel bandwidth can be based on the raster frequency (or E-UTRA Absolute Radio Frequency number (EARFCN)). For example, in this case, there may be no UEs in those bands today (as those frequencies are not supported now). An alternative may be to reuse the entries for some of those bands, and repurpose them for the new channel bandwidth sizes. In any case, the communicating component <NUM>, when encountering such a frequency/bandwidth combination, can interpret or substitute the indicated downlink bandwidth as a specific MB bandwidth size known or otherwise configured to correspond to the frequency/bandwidth combination.

In another example, in determining the MB bandwidth size, the MIB can indicate one of the configurable bandwidth sizes for receiving unicast services (for example, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, or <NUM> PRBs in NR/LTE) as a system bandwidth, but the network can expand or reduce the MB bandwidth size from the configured system bandwidth. Currently, in LTE, the transmission bandwidth of PMCH matches that of system bandwidth (in other words, PMCH is fixed in the specification to use the same number of PRBs as the system bandwidth), whereas other channels (for example, PDSCH) are dynamically scheduled, and do not necessarily use the whole system bandwidth. In examples described herein, communicating component <NUM> can determine the system bandwidth from the MIB and can determine the MB bandwidth or MB bandwidth size to be different from the system bandwidth (for example, expanded or reduced from the system bandwidth), as described herein. For example, for a given MB bandwidth size, communicating component <NUM> can determine from the MIB either of: a maximum one of the configurable bandwidth sizes for receiving unicast services that is smaller than the MB bandwidth size; or a minimum one of the configurable bandwidth sizes for receiving unicast services that is larger than the MB bandwidth size. In various examples, for a CC to provide a MB service having <NUM> MB bandwidth size, the MIB can possibly configure a <NUM> (<NUM> PRBs) or <NUM> (<NUM> PRBs) downlink bandwidth, and the MB bandwidth size can accordingly be expanded or reduced therefrom.

In these examples, the communicating component <NUM> can receive the MIB and determine the specified downlink bandwidth. The communicating component <NUM> can begin decoding at least some system information (for example, SIBs) based on the specified downlink bandwidth at least until the communicating component <NUM> is able to determine the MB bandwidth size (for example, in a SIB, MCCH, PMCH).

For example, where the MB bandwidth size is larger than the specified downlink bandwidth, MIB can indicate a system bandwidth size of x PRBs. At some point, the network can inform the UE of the true MB bandwidth size y PRBs (where y > x in this example). For example, communicating component <NUM> can decode system information based on the bandwidth size of x PRBs at least for some of the system information, and then communicating component <NUM> can decode subsequent system information (for example, subsequent to the MB bandwidth being determined) based on the MB bandwidth size of y PRBs.

In one specific example, the network can signal bandwidth size per MBSFN area (in SIB). When configuring an MBSFN area (for example, in IE MBSFN-AreaInfo-r9 in SIB13), the UE can be configured with a bandwidth size to be used for the PMCH reception, and the communicating component <NUM> can receive and determine the bandwidth size for the MB service. In the present invention, different MBSFN areas have different bandwidth sizes. For backwards compatibility, in an example, the network can use one MBSFN area to serve legacy devices (that do not understand the new system bandwidth), and another MBSFN area to fill the whole system bandwidth. The communicating component <NUM>, based on receiving the indication of bandwidth size for the MBSFN area in the SIB, can decode PMCH (for example, MCCH) for the corresponding MBSFN area using the channel bandwidth size of y PRBs (in other words, the MB bandwidth size) as indicated in the SIB.

In another example, where the MB bandwidth size is larger than the specified downlink bandwidth, MIB can indicate a system bandwidth size of x PRBs and the network can signal MB bandwidth size in a broadcast channel information (for example, a PMCH-InfoList) received over a broadcast control channel (for example, MCCH). In this example, different services in the same MBSFN area can have different channel bandwidth sizes. In addition, in this example, the communicating component <NUM> can receive and decode PMCH based on bandwidth size of x PRBs indicated in the MIB. Then, for PMCH with no "bandwidth overriding" (for example, as indicated in the PMCH-InfoList), the communicating component <NUM> can decode the channel based on x PRBs channel bandwidth size. For PMCH with "bandwidth overriding" (for example, as indicated in the PMCH-InfoList), the communicating component <NUM> can use the channel based on y PRBs, where the bandwidth size of y PRBs (or the corresponding MHz) can be indicated in, and communicating component <NUM> can determine the bandwidth size of y PRBs from, the PMCH-InfoList. For the subframes where the network sends MCCH (and potentially also some of the MCH corresponding to services with larger system bandwidth), the communicating component <NUM> can use a channel based on x PRBs (for example, until the MB bandwidth size is indicted in, and determined by the communicating component <NUM> based on, the PMCH-InfoList sent via the MCCH).

For example, where the MB bandwidth size is smaller than the specified downlink bandwidth, MIB can indicate a system bandwidth size of x PRBs that is larger than the MB bandwidth size. At some point, the network can inform the UE of the true MB bandwidth size, y PRBs. In one specific example, when decoding the system information, the communicating component <NUM> assumes x PRBs. The base station <NUM> may only be transmitting y of these x PRBs (for example by filtering out the edges of the channel). The communicating component <NUM> can decode the PDCCH and system information even with this mismatch (for example, the channel estimation can give lower gain in the edges). By implementation, as described further herein, the base station <NUM> may not schedule SIB in the edges to assist in proper decoding. In one example, as described, the network can signal the MB bandwidth size of y PRBs in SIB (for example, per MBSFN area), in MCCH (for example, per PMCH in PMCH-InfoList), or other information. The communicating component <NUM> can accordingly receive and use this information for channel estimation, demodulation after receiving (for example, after the SIB decode or MCCH). In this regard, for example, communicating component <NUM> can perform initial SIB or other decoding based on x PRBs until the communicating component <NUM> receives the indication of MB bandwidth size of y PRBs in a SIB or MCCH. As described above, at this point, for example, communicating component <NUM> can decode subsequent SIBs based on the MB bandwidth size of y PRBs.

Where the MB bandwidth size is smaller than the specified downlink bandwidth, in an example, the eNB can still schedule PMCH with x PRBs and filter out the edges (by implementation), but in this case there may be loss of the outermost PRBs. Said differently, the outer PRBs or corresponding resource elements (REs) are "punctured" from the UE perspective, so the code rate may be decreased to be able to decode. For example, punctured can refer to the REs being considered to not include communications from the base station, and can be excluded from decoding. For a given bandwidth size, considering REs as punctured and not decoding the REs can reduce the achievable code rate for a give communication.

In another example, in determining the MB bandwidth size, the network or UE can combine multiple CCs having one of the configurable bandwidth sizes for receiving unicast services (for example, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, <NUM> PRBs, or <NUM> PRBs in NR/LTE) to achieve the total MB bandwidth size. For example, to achieve a MB bandwidth size of <NUM>, the base station <NUM> can configure one CC with <NUM> (<NUM> PRB) and another CC with <NUM> (<NUM> PRBs). In this example, there may not be tying between CCs (for example, where different CCs can broadcast different MB services). In another example, the CCs can be tied to facilitate transmitting the same MB service (for example, identified by the same temporary mobile group identifier (TMGI)) across multiple CCs. For example, in determining the MB bandwidth size in this regard, the communicating component <NUM> can receive (e.g., from the network) an indication of tying between the CCs to receive the same MB service. In one example, the communicating component <NUM> can receive information about a TMGI in a first CC (CC1 - for example, in the in MCCH transmitted over CC1), which can also include a pointer to a second CC (CC2 - for example, the pointer can be a point to or of a EARFCN). In this example, communicating component <NUM> can receive signaling over both CCs, and an upper layer (e.g., radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, application layer, or other layers) can merge the corresponding communications to receive the MB service. In another example, the communicating component <NUM> can receive the MBSFN area information (for example, in SIB13, as described above), and can detect a pointer to a different CC to determine that the two CCs may share services.

In method <NUM>, at Block <NUM>, the device (for example, UE <NUM>) can receive the MB service over an MB bandwidth of the MB bandwidth size. In an aspect, communicating component <NUM>, for example, in conjunction with one or more of the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>, the memory <NUM>, the receiver 354RX, can receive the MB service over the MB bandwidth of the MB bandwidth size. For example, the MB bandwidth size can be the MB bandwidth size determined as described in the examples above in reference to Block <NUM>, and as further described in reference to <FIG> herein. In this regard, for example, communicating component <NUM> can receive the MB service over a CC defined to have a MB bandwidth size determined based on a specified downlink bandwidth, where the downlink bandwidth may, in some examples, be a bandwidth size defined for unicast services. In another example, communicating component <NUM> can receive the MB service over multiple CCs defined to have respective bandwidth sizes defined for unicast services that can be combined to achieve a MB bandwidth size. In an example, in receiving the MB service, communicating component <NUM> can receive communications over a MCCH, MTCH in the MB bandwidth.

As described in further examples herein, the communicating component <NUM> (for example, via TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>, the memory <NUM>, the transmitter 354TX) can also report a MBMS interest indication, which may indicate a corresponding MB bandwidth size, to the base station <NUM>. A given base station, however, may not understand the new MB bandwidth size (for example, as differing from the configurable bandwidth sizes defined for unicast services). In an example, the communicating component <NUM> can instead report the MBMS interest indication to the base station <NUM> indicating a next highest bandwidth size defined for unicast services. Said differently, communicating component <NUM> can determine a minimum bandwidth size of the configurable bandwidth sizes for unicast communications that is larger than the desired MB bandwidth size, and can include an indication of that bandwidth size in the MBMS interest indication or other report to the base station <NUM>. In this or another example, the communicating component <NUM> can also report the MB bandwidth size in a new field of the MBMS interest indication or another report. The base station <NUM> may determine the MB bandwidth size or the one of the configurable bandwidth sizes for unicast services to utilize based on the indication received from the UE <NUM>.

<FIG> is a flowchart of an example of a method <NUM> for configuring a MB bandwidth size for receiving communications related to an MB service in accordance with some aspects of the present disclosure. The method <NUM> may be performed by a base station (such as the base station <NUM>, the apparatus <NUM>, the processing system <NUM>, which may include the memory <NUM> and which may be the entire base station <NUM> or a component of the base station <NUM>, such as the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>).

In method <NUM>, at Block <NUM>, the base station can transmit a configuration for a first set of multiple configurable bandwidth sizes for receiving unicast services. In an aspect, configuring component <NUM>, for example, in conjunction with one or more of the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>, the memory <NUM>, the transmitter 318TX, can transmit the configuration for the first set of multiple configurable bandwidth sizes for receiving unicast services. For example, the configuring component <NUM> can transmit the configuration including a MIB that indicates one of the configurable bandwidth sizes.

In method <NUM>, at Block <NUM>, the base station can determine a MB bandwidth size for receiving a MB service where the MB bandwidth size is different than each bandwidth size in the set of multiple configurable bandwidth sizes for receiving unicast services. In an aspect, configuring component <NUM>, for example, in conjunction with one or more of the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>, the memory <NUM>, can determine the MB bandwidth size for receiving (by a UE) the MB service, the MB bandwidth size being outside of (e.g., being different than each bandwidth size in) the set of multiple configurable bandwidth sizes for receiving unicast services. For example, the configuring component <NUM> can determine the MB bandwidth size as related to the MB service, which may be <NUM>, <NUM>, or <NUM>, and outside of the configurable bandwidth sizes supported by a radio access technology, such as <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> in LTE/NR.

In method <NUM>, at Block <NUM>, the base station can transmit an indication of the MB bandwidth size. In an aspect, configuring component <NUM>, for example, in conjunction with one or more of the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>, the memory <NUM>, the transmitter 318TX, can transmit the indication of the MB bandwidth size. In some implementations, as described, configuring component <NUM> can transmit the indication of the MB bandwidth size in the MIB by using one or more spare values of the downlink bandwidth IE to indicate the MB bandwidth size or the existence of a new MB bandwidth size enumeration (in which case the new MB bandwidth size enumeration can indicate the MB bandwidth size).

In other implementations, as described, configuring component <NUM> can first transmit an indication of a system bandwidth selected from the configurable bandwidth sizes supported by the radio access technology (for unicast communications), and then can transmit a separate indication of the MB bandwidth size. For example, configuring component <NUM> can transmit the indication of the a system bandwidth selected from the configurable bandwidth sizes in the MIB, and then can transmit an indication of the MB bandwidth size in a SIB, PMCH, where the MB bandwidth size can be larger or smaller than the size of the system bandwidth in various examples. For example, where the MB bandwidth size is larger, configuring component <NUM> can transmit the indication of the MB bandwidth size when configuring a MBSFN area (for example, in SIB13), such that different MBSFN areas can have different bandwidth sizes (for example, MB bandwidth sizes or unicast bandwidth sizes for legacy devices). In this example, configuring component <NUM> can transmit SIBs before and including the SIB that configures the MB bandwidth size based on the system bandwidth specified in the MIB, and can transmit subsequent SIBs or PMCH based on the MB bandwidth size.

In another example, configuring component <NUM> can transmit the indication of the MB bandwidth size in MCCH control data (for example, in the PMCH-InfoList), which can allow different channel bandwidths or bandwidth sizes for different services in the same MBSFN area. In this example, configuring component <NUM> can transmit PMCH, indicated having "no bandwidth overriding" in the PMCH-InfoList, based on the system bandwidth indicated in the MIB, can transmit PMCH, indicated having "bandwidth overriding" in the PMCH-InfoList, based on the MB bandwidth size indicated in the PMCH-InfoList or other control data.

Where the MB bandwidth size is smaller than the system bandwidth configured in the MIB, for example, configuring component <NUM> can transmit SIB or PMCH only over the MB bandwidth within the system bandwidth (for example, by filtering out the edges of the channel), and the UE can decode the SIB or PMCH, as described above. Additionally, for example, the configuring component <NUM> may not schedule SIB in the edges of the channel that do not include the MB bandwidth. For example, the MB bandwidth may be centered around a center of the system bandwidth resulting in similar edges over the system bandwidth that can be not scheduled (for SIB) or filtered out (for PMCH). In addition, in this example, configuring component <NUM> may similarly indicate the MB bandwidth size in a SIB (for example, SIB13 when configuring MBSFN area), in PMCH, as described above, and can accordingly transmit SIBs before and including the SIB that indicates MB bandwidth size using the system bandwidth and subsequent SIBs using the MB bandwidth.

In another example, configuring component <NUM> can configure multiple CCs having a system bandwidth selected from the configurable bandwidth sizes in the MIB, and can combine the multiple CCs to achieve the MB bandwidth size. In one example, configuring component <NUM> can indicate a relationship or tying between the CCs for receiving the MB service (for example, a relationship to the same TMGI). In one example, configuring component <NUM> can transmit a TMGI in a configuration for a first CC (CC1 - for example, in MCCH), and can include a pointer to a second CC (CC2 - for example, a pointer to a corresponding EARFCN). In another example, configuring component <NUM> can configure CC1 in the MBSFN area (for example, in SIB13) and can indicate a pointer to a different CC (CC2) to inform that the two CCs can be used for a given MB service.

In method <NUM>, at Block <NUM>, the base station can transmit the MB service over an MB bandwidth of the MB bandwidth size. In an aspect, configuring component <NUM>, for example, in conjunction with one or more of the TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>, the memory <NUM>, the transmitter 318TX, can transmit the MB service over the MB bandwidth of the MB bandwidth size. For example, configuring component <NUM> can transmit the MB service over the MB bandwidth as indicated in the transmitted indication described in reference to Block <NUM>. In another example, configuring component <NUM> can transmit the MB service over multiple CCs as indicated in the transmitted indication and each configured based on a system bandwidth that is less than the MB bandwidth size, as described in reference to Block <NUM>, that are combined to achieve the MB bandwidth size.

As described in further examples herein, the UE <NUM> can also report a MBMS interest indication or other report, which may indicate a corresponding MB bandwidth size or a unicast bandwidth size selected based on the MB bandwidth size, to the base station <NUM>, which can be received by the configuring component <NUM> (for example, via TX processor <NUM>, the RX processor <NUM>, or the controller/processor <NUM>, the memory <NUM>, the receiver 318RX). Where the report includes the unicast bandwidth size (for example, a minimum configurable bandwidth size defined for unicast service that is higher than the MB bandwidth), configuring component <NUM> can be conservative in scheduling MB service communications (for example, based on assuming that the UE <NUM> has less resources available than it actually has). Where the report includes the MB bandwidth size, configuring component <NUM> can configure the MB service over an MB bandwidth that is of the MB bandwidth size as described herein.

<FIG> illustrates an example of a system <NUM> for determining an MB bandwidth size for receiving a MB service in accordance with some aspects of the present disclosure. System <NUM> includes a UE <NUM> and a base station <NUM> that can communicate to configure a MB service, as described herein. For example, the base station <NUM> can transmit a configuration of bandwidths to the UE <NUM> at <NUM>. As described, the configuration of bandwidths <NUM> can include at least one of a configuration of configurable bandwidth sizes for unicast services or otherwise defined by a radio access technology (for example, NR or LTE) or an indication of a MB bandwidth size (for example, indicated in spare values of a downlink bandwidth indicated in the MIB). The UE <NUM> can determine a MB bandwidth size based on the configuration of bandwidths at <NUM>. The UE <NUM> can then receive the MB service communicated over an MB bandwidth that is of the MB bandwidth size from the base station <NUM> at <NUM>.

<FIG> illustrates an example of a system <NUM> for determining an MB bandwidth size for receiving a MB service based on an initial system bandwidth in accordance with some aspects of the present disclosure. System <NUM> includes a UE <NUM> and a base station <NUM> that can communicate to configure a MB service, as described herein. For example, the base station <NUM> can transmit one or more of a MIB, one or more SIBs, or a MCCH based on a first bandwidth at <NUM>. As described, the first bandwidth can be one of multiple configurable bandwidth sizes that can be configured for unicast services and indicated in the MIB (as described above). For example, the UE <NUM> can decode the MIB, SIB, MCCH based on the first bandwidth. For example, the base station <NUM> can transmit a configuration of bandwidths to the UE <NUM> at <NUM>, as described in reference to <FIG>. As described, the configuration of bandwidths <NUM> can include an indication of a MB bandwidth (for example, in one or more SIBs, in MCCH, or other signaling). The UE <NUM> can determine a MB bandwidth size based on the configuration of bandwidths at <NUM>. The UE <NUM> can then receive additional SIB or MCCH based on the MB bandwidth size from the base station <NUM> at <NUM>, and can accordingly decode the additional SIB or MCCH based on the MB bandwidth size. The UE <NUM> can also receive the MB service communicated over an MB bandwidth that is of the MB bandwidth size from the base station <NUM> at <NUM>.

<FIG> illustrates an example of a system <NUM> for determining an MB bandwidth size for receiving a MB service based on a collection of multiple CCs in accordance with some aspects of the present disclosure. System <NUM> includes a UE <NUM> and a base station <NUM> that can communicate to configure a MB service, as described herein. For example, the base station <NUM> can transmit a configuration of bandwidths to the UE <NUM> at <NUM>, as described in reference to <FIG>. As described, the configuration of bandwidths <NUM> can include a configuration of configurable bandwidth sizes for unicast services or otherwise defined by a radio access technology (for example, NR or LTE). In addition, for example, the configuration of bandwidths can include configurations of bandwidth sizes for multiple CCs. The UE <NUM> can also receive a configuration of CCs to achieve the MB bandwidth size from the base station <NUM> at <NUM>, which can indicate a relationship between multiple CCs for the MB service. The UE <NUM> can determine a MB bandwidth size based on the configuration of bandwidths at <NUM>, which can also include determining the MB bandwidth size based on a collection of multiple CCs at <NUM> that are combined to achieve the MB bandwidth size. The UE <NUM> can receive the MB service communicated over an MB bandwidth that is of the MB bandwidth size (for example over the multiple CCs) from the base station <NUM> at <NUM>.

<FIG> illustrates an example of a system <NUM> for reporting an MB bandwidth size for receiving a MB service in accordance with some aspects of the present disclosure. System <NUM> includes a UE <NUM> and a base station <NUM> that can communicate to configure a MB service, as described herein. For example, the base station <NUM> can transmit a configuration of bandwidths to the UE <NUM> at <NUM>. As described, the configuration of bandwidths <NUM> can include a configuration of configurable bandwidth sizes for unicast services or otherwise defined by a radio access technology (for example, NR or LTE). The UE <NUM> can determine a MB bandwidth size based on the configuration of bandwidths at <NUM>, as described. The UE <NUM> can then report a bandwidth size to the base station <NUM> based on the MB bandwidth size at <NUM>. For example, the UE <NUM> can report the MB bandwidth size of the desired MB service, a minimum bandwidth size of the configurable bandwidth sizes for unicast services indicated in the configuration at <NUM> that is higher than the MB bandwidth size, as described. The UE <NUM> can then receive the MB service communicated over an MB bandwidth that is of the MB bandwidth size from the base station <NUM> at <NUM>.

<FIG> is a conceptual data flow diagram <NUM> illustrating the data flow between different means/components in an example apparatus <NUM>. The apparatus may be a UE or may include a portion of the UE, such as a communicating component <NUM>, that can communicate with a base station <NUM>. The apparatus includes a configuration reception component <NUM> that receives a configuration for a first set of multiple configurable bandwidth sizes for receiving unicast services, such as described in connection with Block <NUM> of method <NUM> in <FIG>. The apparatus includes a bandwidth determining component <NUM> that determines a MB bandwidth size for receiving a MB service, such as described in connection with Block <NUM> of method <NUM> in <FIG>. The apparatus includes a MB service reception component <NUM> that receives the MB service over an MB bandwidth of the MB bandwidth size, such as described in connection with Block <NUM> of method <NUM> in <FIG>. The apparatus includes a transmission component <NUM> for transmitting certain communications, such as a report of MB bandwidth size as described in other examples herein.

<FIG> is a diagram <NUM> illustrating an example of a hardware implementation for an apparatus employing a processing system <NUM>. The processing system <NUM> may be implemented with a bus architecture, represented generally by the bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> links together various circuits including one or more processors or hardware components, represented by the processor <NUM>, the components <NUM>, <NUM>, <NUM>, and <NUM>, and the computer-readable medium / memory <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits.

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the configuration reception component <NUM>, MB service reception component <NUM>, etc. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the transmission component <NUM>, and based on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described herein for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system <NUM> further includes at least one of the components <NUM>, <NUM>, <NUM>, and <NUM>. The components may be software components running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware components coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the UE <NUM> and may include the memory <NUM> or at least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM>. Alternatively, the processing system <NUM> may be the entire UE (such as UE <NUM> of <FIG>).

In one configuration, the hardware implementation of the apparatus for wireless communication includes means for means for receiving a configuration for a first set of multiple configurable bandwidth sizes for receiving unicast services, means for determining a MB bandwidth size for receiving an MB service, the MB bandwidth size being outside of the set of multiple configurable bandwidth sizes for receiving unicast services; and means for receiving the MB service over an MB bandwidth of the MB bandwidth size. The aforementioned means may be one or more of the aforementioned components of the apparatus <NUM> or the processing system <NUM> of the apparatus <NUM> configured to perform the functions recited by the aforementioned means. As described herein, the processing system <NUM> may include the TX Processor <NUM>, the RX Processor <NUM>, and the controller/processor <NUM>.

<FIG> is a conceptual data flow diagram <NUM> illustrating the data flow between different means/components in an example apparatus <NUM>. The apparatus may be a base station or may include a portion of the base station, such as a configuring component <NUM>, that can communicate with a UE <NUM>. The apparatus includes a configuration transmission component <NUM> that transmits a configuration for a first set of multiple configurable bandwidth sizes for receiving unicast services, such as described in connection with Block <NUM> of method <NUM> in <FIG>. The apparatus includes a bandwidth determining component <NUM> that determines a MB bandwidth size of an MB bandwidth for receiving a MB service, such as described in connection with Block <NUM> of method <NUM> in <FIG>. The apparatus includes a bandwidth indicating component <NUM> that transmits an indication of the MB bandwidth or MB bandwidth size, such as described in connection with Block <NUM> of method <NUM> in <FIG>. The apparatus includes a MB service transmission component <NUM> that transmits the MB service over an MB bandwidth of the MB bandwidth size, such as described in connection with Block <NUM> of method <NUM> in <FIG>. The apparatus includes a reception component <NUM> for receiving certain communications, such as a report of MB bandwidth size as described in other examples herein.

<FIG> is a diagram <NUM> illustrating an example of a hardware implementation for an apparatus employing a processing system <NUM>. The processing system <NUM> may be implemented with a bus architecture, represented generally by the bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> links together various circuits including one or more processors or hardware components, represented by the processor <NUM>, the components <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>, and the computer-readable medium / memory <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits.

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the reception component <NUM>, etc. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the configuration transmission component <NUM>, bandwidth indicating component <NUM>, MB service transmission component <NUM>, etc., and based on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described herein for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system <NUM> further includes at least one of the components <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>. The components may be software components running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware components coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the base station <NUM> and may include the memory <NUM> or at least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM>. Alternatively, the processing system <NUM> may be the entire base station (such as base station <NUM> of <FIG>).

In one configuration, the apparatus <NUM> for wireless communication includes means for transmitting, in a cell, a configuration for a first set of multiple configurable bandwidth sizes for receiving unicast services, determining a MB bandwidth size for transmitting an MB service, the MB bandwidth size being outside of the set of multiple configurable bandwidth sizes for receiving unicast services, transmitting an indication of the MB bandwidth size, and transmitting, in the cell, the MB service over an MB bandwidth of the MB bandwidth size. The aforementioned means may be one or more of the aforementioned components of the apparatus <NUM> or the processing system <NUM> of the apparatus <NUM> configured to perform the functions recited by the aforementioned means. As described herein, the processing system <NUM> may include the TX Processor <NUM>, the RX Processor <NUM>, and the controller/processor <NUM>.

The specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of example approaches. Based upon design preferences, the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged.

Claim 1:
A method (<NUM>) of wireless communication at a user equipment, UE, the method (<NUM>) comprising:
receiving (<NUM>) a configuration for a first set of multiple configurable bandwidth sizes for receiving unicast services, wherein the configuration includes a master information block, MIB, that indicates one bandwidth size of the first set of multiple configurable bandwidth sizes for receiving unicast services and that indicates a system information block, SIB;
receiving the SIB;
determining (<NUM>) a multicast broadcast, MB, bandwidth size for receiving an MB service, the MB bandwidth size being different than each bandwidth size in the set of multiple configurable bandwidth sizes for receiving unicast services, wherein determining the MB bandwidth size is further based on one or more information elements in the SIB that indicate the MB bandwidth size as being different than the one bandwidth size, wherein the SIB configures a multicast-broadcast single-frequency network, MBSFN, area, of a number of different MBSFN areas, for the MB service, wherein the number of different MBSFN areas have different bandwidth sizes; and
receiving (<NUM>) the MB service over an MB bandwidth of the MB bandwidth size.