Patent Description:
The present invention relates to wireless communications, and, in particular embodiments, to methods for a multicast service, and devices.

Downlink control information (DCI) formats are communicated over a physical downlink control channel (PDCCH) to notify user equipments (UEs) of physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) resource grants. Techniques for reducing overhead when communicating PDSCH resource grants over the PDCCH are needed to satisfy the performance requirements of long term evolution (LTE) and fifth generation (<NUM>) new radio (NR) wireless standards.

In current <NUM> network system, there are two DCI formats for scheduling data in DL and two DCI formats for scheduling data in UL. An example is DCI format 1_0, known as fallback DCI for DL. If it is monitored in a common search space (CSS), the size of its frequency domain resource assignment (FDRA) field is given by the size of CORESET o if CORESET o is configured for the cell and the size of initial DL bandwidth part if CORESET o is not configured for the cell. But DCI format 1_0 does not support BWP switching and cross-carrier scheduling, thus can be used for scheduling PDSCH in the active BWP. Another example is DCI format o_o, known as fallback DCI for UL. If it is monitored in a common search space (CSS), the size of its FDRA field is given by the size of the initial UL bandwidth part. But DCI format o_o does not support BWP switching and cross-carrier scheduling. Another example is DCI format 1_1, known as non-fallback DCI for DL. It is monitored in UE-specific search space and the size of FDRA field is given by the active DL BWP. DCI format 1_1 can support BWP switching and cross-carrier scheduling. Another example is DCI format 0_1, known as non-fallback DCI for UL. It is monitored in UE-specific search space and the size of FDRA field is given by the active UL BWP. DCI format 0_1 can support BWP switching and cross-carrier scheduling. All the above <NUM> DCI formats do not support multicast scheduling with BWP switching or cross-carrier scheduling, and thus, a new DCI format design and resource allocation mechanism will be needed.

<CIT> discloses a method and apparatus for scheduling a data channel to support a user equipment (UE) using various bandwidth parts (BWPs) in a next-generation/<NUM> radio access network. According to one embodiment, a method may be provided for receiving a downlink (DL) data channel or transmitting an uplink (UL) data channel by a user equipment (UE). The method may include: receiving bandwidth part (BWP) setup information about a BWP set configured with one or more BWPs set up with regard to the UE from a base station (BS); and receiving DL control information (DCI) including information for indicating one among the one or more BWPs included in the BWP set configured by the BWP setup information from the BS, wherein a DL data channel is received or a UL data channel is transmitted through the one BWP indicated by the DCI.

Technical advantages are generally achieved by embodiments of this disclosure as defined in the attached set of claims which describe devices and methods for a multicast service. Other details of the disclosed methods and systems are set out below, which are useful for highlighting specific aspects of the claimed invention.

According to one aspect of the present disclosure, a method for a multicast service according to claim <NUM> is provided.

Optionally, the obtaining the set of RBs of the multicast PDSCH or PUSCH comprises: locating a starting RB of the multicast PDSCH or PUSCH based on the starting RB location and the reference RB location; and locating an ending RB of the multicast PDSCH or PUSCH based on the RB range and the starting RB of the multicast PDSCH or PUSCH.

Optionally, the obtaining the set of RBs of the multicast PDSCH or PUSCH comprises: locating a starting RB of the multicast PDSCH or PUSCH based on the starting RB location and a starting RB of the assigned sub-band; and locating an ending RB of the multicast PDSCH or PUSCH based on the RB range and the starting RB of the multicast PDSCH or PUSCH.

According to another aspect of the present disclosure, a method for a multicast service according to claim <NUM> is provided.

Optionally, the method further comprising: assigning, by the BS, a multicast group identity (ID) a first UE and a second UE of the group UEs, constructing, by the BS, a control format which includes the resource allocation field, and a Cyclic Redundancy Check (CRC) based on the control format, and scrambling, by the BS, the CRC by the multicast group ID.

Optionally, the resource allocation field is signaled based on at least one of: a downlink control information (DCI) for downlink multicast, wherein a size of the resource allocation field can determined in accordance with any one of a size of a common control resource set (CORESET), a size of an initial downlink BWP, a size of a downlink BWP having a smallest BWP ID among a plurality of downlink BWPs configured for a first UE and a second UE; a size of a default downlink bandwidth part (BWP) configured for the first UE and the second UE; a numerology of a current active BWP; or a downlink component carrier within which a control format is transmitted to the first UE and the second UE; a downlink control information (DCI) for uplink multicast, wherein a size of the resource allocation field is determined in accordance with a size of an uplink bandwidth part (BWP), the uplink BWP having a smallest BWP ID among a plurality of uplink BWPs configured for the first UE; or a higher-layer parameter indicating a first plurality of reference RBs comprises the (k×N)-th common RB, k being an integer and N being a predetermined value.

Optionally, the common CORESET is a CORESET with CORESET ID#o within a carrier where the DCI is received.

Optionally, the control format is size-matched to a type 1_0 DCI.

Optionally, N is a multiple of a configured RB group size or a configured RB bundle size; or N is determined in accordance with a numerology of an active downlink bandwidth part (BWP).

Optionally, the reference RB is assigned to the group UEs by a higher layer signaling, and the reference RB comprises a first plurality of reference RBs comprises a set of common RBs, the set of common RBs are configured by higher layers.

Optionally, before the sending the method further comprising: sending, by the BS, a BWP identifier (ID) indicating a first BWP to a first UE and a second BWP to a second UE, and wherein the at least one RB belongs to one of the first BWP and the second BWP.

Optionally, the first BWP is different from the second BWP in a same carrier or an aggregation of carriers.

Optionally, the at least one RB belonging to the one of the first BWP and the second BWP has a lowest RB index among a first subset of the first plurality of reference RBs, the first subset of the first plurality of reference RBs belonging to the first BWP.

Optionally, the set of RBs has a size of one of: an initial downlink bandwidth part (BWP) or an initial uplink BWP configured for a first component carrier; a downlink BWP or an uplink BWP, the downlink BWP or uplink BWP having a smallest BWP ID among a plurality of downlink BWPs or uplink BWPs configured for a first UE within a component carrier; a default downlink bandwidth part (BWP) or a default uplink BWP configured for the first component carrier; or a size in accordance with which a size of the resource allocation field is determined or configured using DCI or a higher layer signaling message.

Optionally, the resource allocation field includes a bitmap indicating the at least one RB to be used for the multicast service.

Optionally, the at least one RB includes a set of contiguously allocated RBs, and wherein the resource allocation field includes a resource indication value (RIV) corresponding to a starting RB and a length of the set of contiguously allocated RBs.

Optionally, the starting RB and the length of the set of contiguously allocated RBs are determined in accordance with the RIV and a scale factor if M is different than N, M being a size of a number of contiguous RBs, N being size in accordance with which a size of the resource allocation field is determined.

According to another aspect of the present disclosure, a device according to claim <NUM> is provided.

For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:.

The making and using of embodiments of this disclosure are discussed in detail below. It should be appreciated, however, that the present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the invention, and do not limit the scope of the invention. It should be appreciated that much of this disclosure describes the inventive aspects of multicast resource allocation within the context of two UEs, but that the disclosed inventive aspects are not so limited, and can easily be extended to groups of three or more UEs.

A multicast DL transmission refers to a scenario where a BS aims to transmit the same data (multicast DL data) to UEs within a group of UEs. In such scenario, the BS transmits a single physical downlink control channel (PDCCH) containing a DCI to schedule a single physical downlink shared channel (PDSCH) containing the multicast data for all the UEs within the group of UEs, and each UE within the group of UEs receives the same DCI and then receives the same multicast DL data within the same PDSCH scheduled by the DCI. A multicast UL transmission refers to a scenario where a BS schedules each UE within a group of UEs to transmit data (which is potentially different from the data of other UEs within the group of UEs) in physical uplink shared channel (PUSCH) over the same set of UL resources. In particular, the BS transmits a single PDCCH containing a DCI to schedule the same set of UL resources to each UE within the group of UEs, and each UE within the group of UEs receives the same DCI and transmits its own UL data over the same UL resources scheduled by the DCI.

The current scheduling DCI formats in <NUM> has the following issues/limitations: DCI format 1_0 for DL (or format 0_0 for UL) does not support BWP switching and cross-carrier scheduling. For DCI format 1_1 for DL (or format 0_1 for UL) can support BWP switching and cross- carrier scheduling, however the size of FDRA field of the DCI is based on the size of the active (DL or UL) BWP. Therefore, In order to use DCI format 1_1 or DCI format 0_1 in multicast scenario, the size of the active BWP of each UE in the group of UEs should be the same, which is an undesired limitation in BWP configuration. The invention of this disclosure provides a first solution how to allocate resources for multicast PDSCH or multicast PUSCH to a group of UEs with different active BWPs and different scheduled BWPs, and a second solution how to allocate resources for multicast PDSCH or multicast PUSCH in carrier-aggregation (specially in cross-carrier scheduling). The general concept of the two solutions is to send a multicast DCI to a group of UEs, the multicast DCI indicating a same size of the scheduled PDSCH or PUSCH within the scheduled BWP (i.e. the BWP whose ID is indicated in the DCI) for each UE in the group, for an example, the starting RB of the scheduled PDSCH or PUSCH in the scheduled BWP should be the same for all UEs in the group, and thus, achieve multicast transmission.

Aspects of this disclosure provide an efficient mechanism for signaling multicast resource grants to allow user equipments (UEs) to identify the resource blocks of multicast PDSCH (or multicast PUSCH for UL) allocated for multicast data transmissions based on a combination of the existing DCI formats (No new DCI format) with a new RNTI. For an example, use one of the current non-fallback DCI formats, i.e. DCI 1_1 for DL and 0_1 for UL, together with a new RNTI for multicast (e.g. MC-RNTI), and the RB numbering and RB range details disclosed in some of the following embodiments.

Other aspects of this disclosure provide an efficient mechanism for signaling multicast resource grants to allow UEs to identify the resource blocks of multicast PDSCH (or multicast PUSCH for UL) allocated for multicast data transmissions based on a new DCI format for multicast (i.e. a new DCI format which supports multicast scheduling in any BWP), or a combination of the new DCI format and a new RNTI (with possible size-matching of the new DCI format to DCI 0_0/1_0), and the RB numbering and RB range details disclosed in some of the following embodiments.

In particular, a base station transmits a resource allocation field (also known as frequency domain resource assignment (FDRA) field) to a group of UEs that indicates a set of RBs allocated for multicast transmission. In any of the embodiments described in this disclosure, the RBs indicated by the resource allocation field may be either virtual resource blocks (VRBs) or physical resource blocks (PRBs). Also, the terms resource allocation field and frequency domain resource assignment (FDRA) field are interchangeably used throughout this disclosure. The value of the resource allocation field is used by each UE within the group of UEs to locate the set of RBs allocated for the multicast PDSCH or PUSCH based on at least one of a reference RB location, a reference sub-band, or a multicast bandwidth part (BWP). A multicast BWP may be referred to as a group-common BWP, and both terms are used interchangeably in this disclosure. In one example, resource allocation field indicates a starting RB and an RB range. In one example, resource allocation type <NUM> may be used for multicast resource allocation, wherein the resource allocation field indicates a resource indication value (RIV) which implicitly indicates a starting RB and an RB range. The starting RB indicated by the resource allocation field is used by the UEs to locate the starting RB of a set of contiguous RBs allocated for the multicast PDSCH or PUSCH based on at least one of a reference RB location, a reference sub-band, or a multicast BWP, and the RB range indicated by the resource allocation field is used by the UEs to identify the ending RB of the set of contiguous RBs allocated for the multicast PDSCH based on the starting RB location. In another example, resource allocation type o may be used for multicast resource allocation, wherein the resource allocation field indicates a set of resource block groups (RBGs) using a bitmap wherein the RBs belonging to RBGs corresponding to bit values equal to <NUM> are allocated for multicast transmission. The bitmap indicated by the resource allocation field is used by the UEs to locate the RBGs of the multicast PDSCH or PUSCH based on at least one of a reference RB location, a reference sub-band, or a multicast BWP. The multicast PDSCH (or PUSCH for UL) may include a common set of RBs with respective bandwidth parts (BWPs) that are scheduled to the UEs. It should be appreciated that BWPs scheduled to different UEs and used for multicast transmission at least partially overlap with one another in the frequency domain, and that the common set of RBs map to frequency domain resources in the overlapping portions of the BWPs. It should further be appreciated that the respective BWPs may be located on the same component carrier or serving cell or on different component carriers or different serving cells. It should be noted that the terms "component carrier", "carrier", and "serving cell" are interchangeably used in this disclosure.

<FIG> is a diagram of a wireless network <NUM> for communicating data. The wireless network <NUM> includes a base station <NUM> having a coverage area <NUM>, a plurality of mobile devices <NUM>, and a backhaul network <NUM>. As shown, the base station <NUM> establishes uplink (dashed line) and/or downlink (dotted line) connections with the user equipments (UEs) <NUM>, <NUM>, which serve to carry data from the UEs <NUM>, <NUM> to the base station <NUM> and vice-versa. Data carried over the uplink/downlink connections may include data communicated between the UEs <NUM>, as well as data communicated to/from a remote-end (not shown) by way of the backhaul network <NUM>. As used herein, the term "base station" refers to any component (or collection of components) configured to provide wireless access to a network, such as an evolved NodeB (eNB), a generalized NodeB (gNB), a macro-cell, a femtocell, a Wi-Fi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., new radio (NR), long term evolution (LTE), LTE advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi <NUM>. 11a/b/g/n/ac. As used herein, the term "UE" refers to any component (or collection of components) capable of establishing a wireless connection with a base station. The terms "UE," "mobile device," and "mobile station (STA)" are used interchangeably throughout this disclosure. In some embodiments, the network <NUM> may comprise various other wireless devices, such as relay stations, schedulers, central controllers, and the like.

In some embodiments, multicast transmissions may be exchanged between base stations and UEs in a wireless network. Multicast transmissions may include downlink multicast transmissions communicated from a base station to UEs in a group of UEs configured for multicast reception. <FIG> is a diagram <NUM> of a multicast downlink transmission <NUM> from a base station <NUM> to UEs <NUM>, <NUM>, <NUM> in a group of UEs <NUM>. Component carrier group <NUM> includes DL component carriers <NUM>, <NUM>, and <NUM>. In this example, the multicast downlink transmission <NUM> is communicated over DL component carriers <NUM>, <NUM>, <NUM>, with the UE <NUM> receiving the multicast downlink transmission <NUM> over the component carrier <NUM>, the UE <NUM> receiving the multicast downlink transmission <NUM> over the component carrier <NUM>, and the UE <NUM> receiving the multicast downlink transmission <NUM> over the component carrier <NUM>. The component carriers <NUM>, <NUM>, <NUM> may be orthogonal or non-orthogonal in the frequency domain. In other examples, multicast downlink transmissions may be communicated to two or more UEs over the same DL component carrier. Here a component carrier refers to the primary carrier accessed by a UE, or any of the primary carrier or secondary carriers configured to a UE in the case of carrier aggregation.

Multicast transmissions may also include uplink multicast transmissions communicated to a base station from UEs in a group of UEs configured for multicast transmission. <FIG> illustrates a diagram <NUM> of a multicast uplink transmission <NUM> from the UEs <NUM>, <NUM>, <NUM> to the base station <NUM>. Similar to the multicast downlink transmission <NUM>, the multicast uplink transmission <NUM> is communicated over UL component carriers <NUM>, <NUM>, <NUM>, with the UE <NUM> transmitting the multicast uplink transmission <NUM> over the component carrier <NUM>, the UE <NUM> transmitting the multicast downlink transmission <NUM> over the component carrier <NUM>, and the UE <NUM> transmitting the multicast downlink transmission <NUM> over the component carrier <NUM>. Component carrier group <NUM> includes UL component carriers <NUM>, <NUM>, and <NUM>. The component carriers <NUM>, <NUM>, <NUM> may be orthogonal or non-orthogonal in the frequency domain. In other examples, multicast downlink transmissions may be communicated to two or more UEs over the same UL component carrier.

A multicast UL transmission refers to a scenario where a BS schedules each UE within a group of UEs to transmit data (which is potentially different from the data of other UEs within the group of UEs) in physical uplink shared channel (PUSCH) over the same set of UL resources. In particular, the BS transmits a single PDCCH containing a DCI to schedule one set of UL resources to each UE within the group of UEs, and each UE within the group of UEs receives the same DCI and transmits its own UL data over the same UL resources scheduled by the DCI.

It should be appreciated that any number of UEs may be included in the group of UEs <NUM>, and that any number of component carriers may be included in the groups of component carriers <NUM> and <NUM>. It should also be appreciated that, in some embodiments, two or more UEs may transmit and/or receive the multicast uplink transmission <NUM> and/or the multicast downlink transmission <NUM> over the same component carrier. For instance, the same UE may transmit and/or receive a multicast transmission over different component carriers to provide redundancy in order to achieve improved reliability.

Multicast transmissions may be communicated over portions of bandwidth parts (BWPs) that are assigned for multicast PDSCH (or PUSCH for UL). Aspects of this disclosure signal a resource allocation field in a DCI message to notify UEs of the RBs allocated to the multicast PDSCH or PUSCH.

In some embodiments, the resource allocation field may be used to identify the RBs allocated for a multicast PDSCH/PUSCH based on a reference RB or a combination of a reference RB and a reference size. In some embodiments, RB numbering for multicast resource allocation starts from the reference RB. The resource allocation field may be included in a downlink control information (DCI) message, which is also called multicast DCI in this disclosure. A multicast DCI message is constructed based on a DCI format which describes bitfields of the multicast DCI message. A multicast DCI message is transmitted to a group of UEs in a physical downlink control channel (PDCCH). Transmission of a multicast DCI message in a PDCCH may involve other step, including appending of cyclic redundancy check (CRC) bits to the multicast DCI message, scrambling of the a radio network temporary identifier (RNTI), and encoding of the resulting bits using a forward error correction (FEC) encoder. In one embodiment, a specific DCI format is used for scheduling multicast PDSCH (also called DL multicast DCI) and/or a specific DCI format is used for scheduling multicast PUSCH (also called UL multicast DCI). In another embodiment, the same DCI format which is used for scheduling other types of PDSCH (or PUSCH) can be used for scheduling multicast PDSCH (or PUSCH). In some embodiments, DL fallback DCI may be used as DL multicast DCI and/or UL fallback DCI may be used as UL multicast DCI. In some embodiments, the DCI 1_0 is used as DL fallback DCI and/or DCI o_o is used as fallback UL DCI. In some embodiments, DCI 1_0 may be used as DL multicast PDSCH and/or DCI 0_0 may be used as UL multicast PUSCH.

In some embodiments, a size of the resource allocation field is determined based on frequency size of a common control resource set (CORESET) in a scheduling cell or scheduling carrier. A scheduling cell is a serving cell where the UE receives the PDCCH containing the multicast DCI. The PDCCH containing the multicast DCI may be received in an active BWP of the scheduling cell of each UE within a group of UEs for multicast communication. In some embodiments, different UEs within the group of UEs may have different active BWPs and/or different scheduling cells, but they all receive the same PDCCH containing the same multicast DCI message. In some embodiments, the size of the resource allocation field is determined based on frequency size of the CORESET where the multicast DCI message is received by the UE. In some embodiments, the size of the resource allocation field is determined based on frequency size of the CORESET with CORESET ID#o in the scheduling cell. In some embodiments, the size of the resource allocation field is determined based on the size of an initial DL BWP or the size of an initial UL BWP of the scheduling cell. In some embodiments, the size of the resource allocation field is determined based on the size of DL BWP (or UL BWP) configured in the scheduled serving cell which has the smallest BWP ID or largest BWP ID among the DL BWPs (or UL BWPs) configured in the scheduling cell for a UE. In some embodiments, the size of the resource allocation field is determined based on the size of the default DL BWP (or UL BWP) in the scheduling cell. In some embodiments, the size of the resource allocation field is either a fixed number or a predefined number or a number configured by higher layers. In embodiments where the size of the resource allocation field is configured by higher layers, the size of the resource allocation field can be configured per scheduling cell, or per configured numerology of the scheduling cell, or per configured BWP of the scheduling cell. In embodiments where a UE locates the RBs allocated for multicast transmission based on a reference RB and reference size, in some examples, the size of the resource allocation field is determined based on the reference size. In embodiments where a UE locates the RBs allocated for multicast transmission based on a reference sub-band, in some examples, the size of the resource allocation field is determined based on the sub-band size. In embodiments where a UE locates the RBs allocated for multicast transmission based on a multicast or group-common BWP, in some examples, the size of the resource allocation field is determined based on the size of the multicast or group-common BWP.

Denote by A the size of the resource allocation field and by Nsize the size based on which the size of the resource allocation field (A) is determined (for examples, Nsize is any of the sizes described in the embodiments above). In some embodiments, when only resource allocation type <NUM> is configured for multicast PDSCH or PUSCH, the size of the resource allocation field is equal to <MAT> <NUM>)/<NUM>)] bits. In some embodiments, when only resource allocation type o is configured for multicast PDSCH or PUSCH, the size of the resource allocation field is equal to <MAT>, bits, where P is the RBG size and Nstart is the common resource block (CRB) index of the RB where the RB numbering for resource allocation starts from according to any of the embodiments described in this disclosure. In an example, Nstart is the CRB index of a reference RB used for multicast PDSCH or PUSCH. In another example, Nstart is the CRB index of the lowest RB of a sub-band used for the multicast PDSCH or PUSCH. In yet another example, Nstart is the CRB index of the starting RB of a multicast BWP or group-common BWP used for the multicast PDSCH or PUSCH. In some embodiments, when both resource allocation type o and resource allocation type <NUM> are configured for multicast PDSCH or PUSCH, the size of the resource allocation field is equal to A = max([log<NUM> (Nsize (Nsize + <NUM>)/<NUM>)], <MAT> <MAT> bits.

In some embodiments, a multicast DCI includes a BWP ID field to indicate the BWP ID of the scheduled BWP, i.e. a DL BWP which contains the allocated RBs for a multicast PDSCH or an UL BWP which contains the allocated RBs for a multicast PUSCH. In some embodiments, a multicast DCI includes a carrier ID field (CIF) to indicate the scheduled cell or scheduled carrier, i.e. the serving cell or component carrier i.e. a DL carrier which contains the allocated RBs for a multicast PDSCH or an UL carrier which contains the allocated RBs for a multicast PUSCH. In some embodiments, where a CIF is included in the multicast DCI, the scheduled BWP belongs to the scheduled cell.

In some embodiments, an UL multicast DCI may be size-matched to a DL multicast DCI. In some embodiments, a DL multicast DCI is size-matched to an UL multicast DCI. In some embodiments, a DL multicast DCI is size-matched to an UL multicast DCI if a size of the DL multicast DCI (before size-matching) is smaller than a size of the UL multicast DCI, and/or an UL multicast DCI is size-matched to a DL multicast DCI if a size of the UL multicast DCI (before size-matching) is smaller than a size of the DL multicast DCI. In some embodiments, a DL multicast DCI and/or an UL multicast DCI is size-matched to DCI format 1_0 or 0_0. The size-matching of a first DCI format to second DCI format may be done by truncating a number of most significant bits (MSBs) of the first DCI format or a number of MSBs of a particular bitfield (e.g. a resource allocation field) of the first DCI format so that the resulting size is equal to a size of the second DCI format. Alternatively, size-matching of a first DCI format to second DCI format may be done by appending a number of zero bits to MSBs of the first DCI format or to MSBs of a particular bitfield (e.g. a resource allocation field) of the first DCI format so that the resulting size is equal to a size of the second DCI format.

In some embodiment, a specific RNTI for multicast communication, e.g. a multicast RNTI or MC-RNTI, may be used to scramble and/or descramble cyclic redundancy check (CRC) of the multicast DCI message and/or to detect the multicast DCI message. Advantageously, because a single resource allocation field is communicated to a group of UEs, the multicast resource allocations are signaled using less overhead than would otherwise be used if resource allocations were signaled separately.

<FIG> are diagrams of multicast resource allocation schemes <NUM>-<NUM> for signaling multicast resource allocations to UEs <NUM>, <NUM>. In this example, a BWP <NUM> is assigned or scheduled to UE <NUM> and a BWP <NUM> is assigned or scheduled to UE <NUM>. The BWPs <NUM>, <NUM> may be on the same component carrier (or serving cell) or on different component carriers (or serving cells). As shown, the BWP <NUM> at least partially overlaps with the BWP <NUM> in the frequency domain such that a common sequence of contiguous RBs (RB<NUM>, RB<NUM>,. , RB<NUM>) belong to both of the BWPs <NUM>, <NUM>.

In each of the multicast resource allocation schemes <NUM>-<NUM>, the base station <NUM> sends a resource allocation field <NUM>-384to the UEs <NUM>, <NUM>. The resource allocation fields <NUM>-<NUM> indicate a starting RB index and an RB range (implicitly using RIV or explicitly), which are used to identify a set of contiguous RBs allocated for the multicast PDSCH/PUSCH. In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range. The resource allocation field384 indicates a set of RBGs, which are used to identify the RBs allocated for the multicast PDSCH/PUSCH.

The starting RB index indicated by (or derived from the RIV indicated by) the respective resource allocation fields <NUM>-<NUM> is used to identify the starting RB of a set of contiguous RBs allocated for the multicast PDSCH/PUSCH based on the reference RB location <NUM>. The RB range indicated by (or derived from the RIV indicated by)the respective resource allocation fields <NUM>-<NUM> is then used to identify the ending RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH based on the identified starting RB of the multicast PDSCH/PUSCH. In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range. The RBGs indicated by the resource allocation field <NUM> are used to identify the RBs allocated for the multicast PDSCH/PUSCH based on the reference RB location <NUM>.

In particular, the resource allocation field <NUM> indicates (implicitly using RIV or explicitly) a starting RB index of one (starting_RB =<NUM>) and an RB range of four (RB_range =<NUM>). Upon receiving the resource allocation field <NUM>, the UEs <NUM>, <NUM> identify the RB <NUM> (i.e., RB<NUM>) as the starting RB of a set of contiguous RBs allocated for the multicast PDSCH/PUSCH because the RB <NUM> is located one RB from the reference RB <NUM>. The UEs <NUM>, <NUM> then identify the RB <NUM> (i.e., RB<NUM>) as the ending RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH because the RB <NUM> is located four RBs from the starting RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH (i.e., four RBs from the RB <NUM>). In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range.

Taking <FIG> as a reference, the resource allocation field <NUM> indicates (implicitly using RIV or explicitly) a starting RB index of three (starting_RB =<NUM>) and an RB range of six (RB_range =six). Upon receiving the resource allocation field <NUM>, the UEs <NUM>, <NUM> identify the RB <NUM> (i.e., RB<NUM>) as the starting RB of a set of contiguous RBs allocated for the multicast PDSCH/PUSCH because the RB <NUM> is located three RBs from the reference RB <NUM>. The UEs <NUM>, <NUM> then identify the RB <NUM> (i.e., RBs) as the ending RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH because the RB <NUM> is located six RBs from the starting RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH (i.e., six RBs from the RB <NUM>). In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range.

Taking <FIG> as a reference, the resource allocation field <NUM> indicates (implicitly using RIV or explicitly) a starting RB index of zero (starting_RB =<NUM>) and an RB range of seven (RB_range =seven). Upon receiving the resource allocation field <NUM>, the UEs <NUM>, <NUM> identify the RB <NUM> (i.e., RB<NUM>) as the starting RB of a set of contiguous RBs allocated for the multicast PDSCH/ PUSCH because, when the starting RB is equal to zero, the reference RB is the starting RB. The UEs <NUM>, <NUM> then identify the RB <NUM> (i.e., RB<NUM>) as the ending RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH because the RB <NUM> is located seven RBs from the starting RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH (i.e., seven RBs from the RB <NUM>). In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range. Taking <FIG> as a reference, which does not fall under the scope of the attached claims, the resource allocation field <NUM> indicates a bitmap of RBGs. In this specific example, the RBG size is equal to <NUM>, i.e. each RBG (except for the first RBG) consists of <NUM> RBs. The first RBG includes reference RB <NUM>. The second RBG includes RBs <NUM> and <NUM>. The third RBG includes RBs <NUM> and <NUM>. The fourth RBG includes RBs <NUM> and <NUM>. The fifth RBG includes RBs <NUM> and <NUM>. It should be appreciated that the RBG size can be any other integer value P. In some embodiments, the RBG size can be a power of <NUM>. In some embodiments, the RBG size may be a fixed value, or a predefined value, or a value configured by higher layers, e.g. as part of BWP configuration. Upon receiving the resource allocation field <NUM>, the UEs <NUM>, <NUM> identify the RBs <NUM>, <NUM>, <NUM>, <NUM> (i.e., RB<NUM>, RB<NUM>, RB<NUM>, RB<NUM>) as RBs allocated for the multicast PDSCH or PUSCH because, the resource allocation field <NUM> is bitmap (<NUM>) indicating that the second RBG and the fourth RBG are allocated. It should be noted that the first RBG (which includes the reference RB) and/or the last RBG may have a partial size, i.e. they may consist of less than P RBs. This is because RBG boundaries may or may not be aligned with the reference RB.

In some embodiments, any of the above resource allocation fields <NUM> to <NUM> can comprise a starting RB and an ending RB to identify a set of RBs. The reference RB can be identified by a physical resource block (PRB) index or a common resource block (CRB) index. The reference RB may be a priori information, for an example, predefined to a UE or the group of UEs for multicast communication. In one embodiment, the reference RB is configured using higher layer signaling, e.g. as part of BWP configuration. In another embodiment, the reference RB may be selected from a set of multicast reference RBs. In one embodiment, the reference RB is the lowest reference RB within the set of multicast reference RBs which belongs to the scheduled BWP. In one embodiment, the reference RB from the set of multicast reference RBs is signaled to a UE via a higher layer signaling e.g., a radio resource communications (RRC) signaling, or via a MAC CE signaling or via a DCI message, or a combination thereof. In some embodiments, a subset of the set of multicast reference RBs is first activated using MAC CE or higher layer signaling and a DCI message is used to indicate the reference RB within the activated subset of the set of multicast reference RBs. The DCI message used to indicate the reference RB may be the same DCI massage that is used for scheduling the multicast PDSCH/PUSCH, in which case a separate DCI bitfield in the DCI message may be used for such indication.

In some embodiments, the set of multicast reference RBs consists either of a fixed or predefined set of PRBs or CRBs, or a set of PRBs or CRBs configured by higher layers. In some embodiments, the set of multicast reference RBs consists of CRBs with CRB index k×N, k=<NUM>,<NUM>,. , within a component carrier, where N can be either of a fixed integer or a predefined integer or an integer configured by higher layers. In embodiments where N is configured by higher layers, N can be configured per serving cell, or per configured numerology of a serving cell, per configured BWP of a serving cell. In some embodiments, N may depend on other higher layer parameters configured to a UE. As an example, N is the RBG size or a fixed integer multiple of the RBG size or a higher-layer configurable integer multiple of the RBG size configured for the scheduled BWP (i.e. the BWP in which the multicast PDSCH/PUSCH is allocated to be transmitted). As another example, N is the RB bundle size or a fixed integer multiple of the RB bundle size or a higher-layer configurable integer multiple of the RB bundle size configured for the scheduled BWP. As yet another example, for resource allocation type o, N is the RBG size or a fixed integer multiple of the RBG size or a higher-layer configurable integer multiple of the RBG size configured for the scheduled BWP, and for resource allocation type <NUM>, N is the RB bundle size or a fixed integer multiple of the RB bundle size or a higher-layer configurable integer multiple of the RB bundle size configured for the scheduled BWP.

In some embodiments, a reference size is associated to multicast PDSCH/PUSCH. The reference size may either be a priori information to a UE or a group of UEs for multicast communication or otherwise communicated via higher layer signaling, e.g., RRC signaling, or via MAC CE signaling, or via a DCI message, or a combination thereof. The DCI message that is used for indication of the reference size may be the same DCI massage that is used for scheduling the multicast PDSCH/PUSCH. In some embodiments, the reference size is equal to size Nsize that is used to determine the size of the multicast resource allocation field. In some embodiments, the reference size is either a fixed number or a predefined number or a number configured by higher layers. In embodiments where the reference size is a configurable integer, the reference size can be configured per serving cell, or per configured numerology of a serving cell, per configured BWP of a serving cell. In some embodiments, the reference size is equal to the size of a common CORESET in the scheduled serving cell (i.e. the serving cell in which or in a BWP of which the multicast PDSCH/PUSCH is allocated to be transmitted). In some embodiments, the reference size is equal to the size of the CORESET with CORESET ID#o in the scheduled serving cell. In some embodiments, the reference size is equal to the size of the initial DL BWP or the initial UL BWP of the scheduled serving cell. In some embodiments, the reference size is equal to the size of DL BWP (or UL BWP) configured in the scheduled serving cell which has the smallest BWP ID or largest BWP ID among the DL BWPs (or UL BWPs) configured in the scheduled serving cell for a UE. In some embodiments, the reference size is equal to the size of the default DL BWP (or UL BWP) in the scheduled serving cell.

In some embodiments, the resource allocation field may be used to identify the RBs allocated for a multicast PDSCH/PUSCH based on an assigned sub-band, where a sub-band is a set of contiguous RBs within a serving cell which is associated to multicast communication. In some embodiment, RB numbering for multicast resource allocation starts from the lowest RB of the assigned sub-band. The assigned sub-band may be a priori information to a UE or a group of UEs for multicast communication. In some embodiments, the assigned sub-band for multicast transmission is configured using higher layer signaling, e.g. as part of BWP configuration. In some embodiments, a serving cell is divided into a set of sub-bands and the assigned sub-band for multicast transmission is selected from the set of sub-bands. In one example, CRBs of a serving cell are divided into sub-bands of the same size, herein called sub-band size. In one embodiment, the assigned sub-band for multicast transmission is a sub-band (from the set of sub-bands of the scheduled serving cell) which is fully contained in the scheduled BWP and has the lowest sub-band index within the set of sub-bands of the scheduled serving cell. In one embodiment, the assigned sub-band for multicast transmission is indicated to a UE from the set of sub-bands of the scheduled serving cell via a higher layer signaling e.g., a radio resource communications (RRC) signaling, or via a MAC CE signaling or via a DCI message, or a combination thereof. In some embodiments, a subset of the set of sub-bands of the scheduled serving cell is first activated using MAC CE or higher layer signaling and a DCI message is then used to indicate the assigned sub-band for multicast transmission from the activated subset of the set of sub-bands of the scheduled serving cell. The DCI message used to indicate the assigned sub-band for multicast transmission may be the same DCI massage that is used for scheduling the multicast PDSCH/PUSCH, in which case a separate DCI bitfield in the DCI message may be used for such indication.

In some embodiments where the CRBs of a serving cell are divided into sub-bands of the same size (sub-band size), the sub-band size may either be a priori information to a UE or a group of UEs for multicast communication or otherwise communicated via higher layer signaling, e.g., RRC signaling, or via MAC CE signaling, or via a DCI message, or a combination thereof. The DCI message that is used for indication of the sub-band size may be the same DCI massage that is used for scheduling the multicast PDSCH/PUSCH. In some embodiments, the sub-band size is equal to the size Nsize that is used to determine the size of the multicast resource allocation field. In some embodiments, the sub-band size is either a fixed number or a predefined number or a number configured by higher layers. In embodiments where the sub-band size is a configured by higher layers, the sub-band size can be configured per serving cell, or per configured numerology of a serving cell, per configured BWP of a serving cell. In some embodiments, the sub-band size is equal to the size of a common CORESET in the scheduled serving cell (i.e. the serving cell in which or in a BWP of which the multicast PDSCH/PUSCH is allocated to be transmitted). In some embodiments, the sub-band size is equal to the size of the CORESET with CORESET ID#o in the scheduled serving cell. In some embodiments, the sub-band size is equal to the size of an initial DL BWP or an initial UL BWP of the scheduled serving cell. In some embodiments, the sub-band size is equal to the size of DL BWP (or UL BWP) configured in the scheduled serving cell which has the smallest BWP ID or largest BWP ID among the DL BWPs (or UL BWPs) configured in the scheduled serving cell for a UE. In some embodiments, the sub-band size is equal to the size of the default DL BWP (or UL BWP) in the scheduled serving cell. In some embodiments, the granularity of the sub-band size is either of one PRB, or one PRG, or one RBG, or one RB bundle, or a higher layer configurable integer number of PRBs.

<FIG> are diagrams of multicast resource allocation schemes <NUM>-<NUM> for signaling multicast resource allocations to UEs <NUM>, <NUM>. Similar to the BWPs <NUM>, <NUM> in <FIG>, the BWPs432, <NUM> are scheduled to the UEs <NUM>, <NUM> (respectively), and may be on the same component carrier (or serving cell) or on different component carriers (or serving cells). As shown, the BWP <NUM> at least partially overlaps with the BWP <NUM> in the frequency domain such that a common sequence of contiguous RBs (RB<NUM>, RB<NUM>,. , RB<NUM>) belong to both of the BWPs <NUM>, <NUM>.

In each of the multicast resource allocation schemes <NUM>-<NUM> showing in <FIG>, the base station <NUM> sends a resource allocation field <NUM>-<NUM> to the UEs <NUM>, <NUM>. Similar to the resource allocation fields <NUM>-<NUM> in <FIG>, the resource allocation fields <NUM>-<NUM> indicate a starting RB index and an RB range (implicitly using RIV or explicitly), and are used to identify a set of contiguous RBs allocated for the multicast PDSCH/PUSCH. However, the starting RB index indicated by (or derived from the RIV indicated by) the resource allocation fields <NUM>-<NUM> is used to identify the starting RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH based on the lowest RB of the sub-band <NUM>. Here the lowest RB of the sub-band refers to the starting RB of the sub-band, or equivalently, an RB which has the smallest CRB index in the sub-band. The RB range indicated by (or derived from the RIV indicated by) the respective resource allocation fields <NUM>-<NUM> is then used to identify the ending RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH based on the identified starting RB of the set of contiguous RBs allocated for the multicast PDSCH/PUSCH. In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range. Similar to the resource allocation field <NUM> in <FIG>, the resource allocation field <NUM> indicates a bitmap of RBGs, and is used to identify a set of RBs allocated for the multicast PDSCH/PUSCH. Similar to <FIG>, in the example of <FIG>, which does not fall under the scope of the attached claims, the RBG size is equal to <NUM>, i.e. each RBG (except for the first RBG in this example) consists of <NUM> RBs. The first RBG includes reference RB <NUM>. The second RBG includes RBs <NUM> and <NUM>. The third RBG includes RBs <NUM> and <NUM>. The fourth RBG includes RBs <NUM> and <NUM>. The fifth RBG includes RBs <NUM> and <NUM>. It should be appreciated that the RBG size can be any other integer value P. In some embodiments, the RBG size can be a power of <NUM>. In some embodiments, the RBG size may be a fixed value, or a predefined value, or a value configured by higher layers, e.g. as part of BWP configuration. It should be noted that the first RBG (which includes the reference RB) and/or the last RBG may have a partial size, i.e. they may consist of less than P RBs. This is because RBG boundaries may or may not be aligned with the reference RB.

Denote by M the reference size for multicast transmission or sub-band size for multicast transmission or the size of the scheduled multicast BWP (according to any of the corresponding embodiments in this disclosure). In some embodiments, if the size Nsize (which is used for determination of the size of the resource allocation field) is different from M, for resource allocation type <NUM>, a UE first obtains a starting RB index and an RB range from the resource allocation field (e.g. derives a starting RB index and an RB range from the RIV field using Nsize is the size of the BWP), and then scales the obtained starting RB index and RB range by a factor of max(M/Nsize, <NUM>)rounded down to the nearest power of <NUM>, and then uses the scaled starting RB index and RB range to identify a set of contiguous RBs allocated for the multicast PDSCH/PUSCH based on the reference RB for multicast transmission within the scheduled BWP or based on an assigned sub-band for multicast transmission within the scheduled BWP or based on the scheduled multicast BWP(according to any of the corresponding embodiments in this disclosure In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range.

Combing the above 3A to 3D and the <FIG>, <FIG> is a flowchart of a method <NUM> for multicast service as may be performed by a base station. At step <NUM>, the base station transmits a resource allocation field indicating a starting RB index and an RB range to allocate a set of contiguous RBs for a multicast PDSCH/PUSCH to a group of UEs. The group of UEs can be scheduled with different BWPs or in a carrier-aggregation. At step <NUM>, the base station transmits or receives data from the group of UEs over the set of contiguous RBs allocated for the multicast PDSCH/PUSCH to or from UEs in the group of UEs. In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range. The resource allocation field can be any one of the above details showing in 3A to 3C and the <FIG>.

Combing the above 3A to 3D and the <FIG>, <FIG> is a flowchart of a method <NUM> for multicast service performed by a UE in a group of UEs configured for multicast transmission/reception. At step <NUM>, the UE receives a resource allocation field indicating a starting RB index and an RB range from a base station. At step <NUM>, the UE identifies a set of contiguous RBs allocated for a multicast PDSCH/PUSCH based on the starting RB index and the RB range indicated by the resource allocation field. At step <NUM>, the UE transmits or receives multicast data to or from the base station over the set of contiguous RBs allocated for the multicast PDSCH/PUSCH in one BWP or group-common BWP. Before the step <NUM>, the UE obtains a reference RB for identifying the set of contiguous RBs (not shown). The reference RB can be predefined or signaling to the UE and the set of contiguous RBs allocated for multicast PDSCH or PUSCH are used for multiple UEs transmitting data to the base station at a same time slot or different time slot. In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range.

In some embodiments, a multicast DCI message is used to identify a multicast BWP (or group-common BWP) and to identify a set of RBs allocated for a multicast PDSCH/PUSCH within the identified multicast BWP. In some embodiments, RB numbering for multicast resource allocation starts from the lowest RB of the identified multicast BWP. When more than one multicast BWP are configured to a UE or a group of UEs, a BWP ID may be included in the multicast DCI to identify the scheduled multicast BWP among all BWPs configured to a UE or among the multicast BWPs configured to the UE. When only a single multicast BWP is configured to a UE or a group of UEs, the multicast DCI message may identify the scheduled multicast BWP without including a BWP ID. The multicast DCI includes a resource allocation field which indicates a set of RBs allocated for a multicast PDSCH/PUSCH within the scheduled multicast BWP. The resource allocation field may indicate a starting RB index and an RB range (implicitly using an RIV or explicitly), which are used to identify a set of contiguous RBs allocated for the multicast PDSCH/PUSCH within the scheduled multicast BWP. In some embodiments, the set of contiguous RBs is a set of contiguous VRBs, wherein the starting RB is a starting VRB and the RB range is a VRB range. Alternatively, the resource allocation field may use a bitmap to indicate a set of RBGs, which are used to identify the RBs allocated for the multicast PDSCH/PUSCH within the scheduled multicast BWP. <FIG> is a diagram of a multicast resource allocation scheme <NUM> for signaling a multicast DCI message <NUM>, to UEs <NUM>, <NUM>, <NUM> for scheduling the multicast BWP <NUM>. As shown, the DCI message <NUM> is communicated within the BWPs <NUM>, <NUM>, <NUM> which are the active BWPs of UEs <NUM>, <NUM>, <NUM> respectively, and is used to identify the scheduled multicast BWP <NUM> and to indicate a set of RBs allocated for a multicast PDSCH/PUSCH within the scheduled multicast BWP <NUM>.

<FIG> is a flowchart of a method <NUM> for multicast service as may be performed by a base station. At step <NUM>, the base station transmits a multicast DCI message identifying a multicast BWP and at least one RB allocated for multicast data transmission/reception. In this example, the multicast DCI message excludes a BWP ID. At step <NUM>, the base station transmits or receives multicast data over the at least one RB in the multicast BWP to or from UEs in the group of UEs.

<FIG> is a flowchart of a method <NUM> for multicast service performed by a UE in a group of UEs configured for multicast transmission/reception. At step <NUM>, the UE receives a multicast DCI message identifying a multicast BWP and at least one RB allocated for multicast data transmission/reception within the identified multicast BWP, where the multicast DCI message excludes a BWP ID. At step <NUM>, the UE identifies the multicast BWP based on the multicast DCI message. At step <NUM>, the UE transmits or receives multicast data over the at least one RB in the multicast BWP to or from UEs in the group of UEs.

<FIG> is a block diagram of an embodiment processing system <NUM> for performing methods described herein, which may be installed in a host device. As shown, the processing system <NUM> includes a processor <NUM>, a memory <NUM>, and interfaces <NUM>-<NUM>, which may (or may not) be arranged as shown in <FIG>. The processor <NUM> may be any component or collection of components adapted to perform computations and/or other processing related tasks, and the memory <NUM> may be any component or collection of components adapted to store programming and/or instructions for execution by the processor <NUM>. In an embodiment, the memory <NUM> includes a non-transitory computer readable medium. The interfaces <NUM>, <NUM>, <NUM> may be any component or collection of components that allow the processing system <NUM> to communicate with other devices/components and/or a user. For example, one or more of the interfaces <NUM>, <NUM>, <NUM> may be adapted to communicate data, control, or management messages from the processor <NUM> to applications installed on the host device and/or a remote device. As another example, one or more of the interfaces <NUM>, <NUM>, <NUM> maybe adapted to allow a user or user device (e.g., personal computer (PC), etc.) to interact/communicate with the processing system <NUM>. The processing system <NUM> may include additional components not depicted in <FIG>, such as long term storage (e.g., non-volatile memory, etc.).

In some embodiments, the processing system <NUM> is included in a network device that is accessing, or part otherwise of, a telecommunications network. In one example, the processing system <NUM> is in a network-side device in a wireless or wireline telecommunications network, such as a base station, a relay station, a scheduler, a controller, a gateway, a router, an applications server, or any other device in the telecommunications network. In other embodiments, the processing system <NUM> is in a user-side device accessing a wireless or wireline telecommunications network, such as a mobile station, a user equipment (UE), a personal computer (PC), a tablet, a wearable communications device (e.g., a smartwatch, etc.), or any other device adapted to access a telecommunications network.

In some embodiments, one or more of the interfaces <NUM>, <NUM>, <NUM> connects the processing system <NUM> to a transceiver adapted to transmit and receive signaling over the telecommunications network. <FIG> is a block diagram of a transceiver <NUM> adapted to transmit and receive signaling over a telecommunications network. The transceiver <NUM> may be installed in a host device. As shown, the transceiver <NUM> comprises a network-side interface <NUM>, a coupler <NUM>, a transmitter <NUM>, a receiver <NUM>, a signal processor <NUM>, and a device-side interface <NUM>. The network-side interface <NUM> may include any component or collection of components adapted to transmit or receive signaling over a wireless or wireline telecommunications network. The coupler <NUM> may include any component or collection of components adapted to facilitate bi-directional communication over the network-side interface <NUM>. The transmitter <NUM> may include any component or collection of components (e.g., up-converter, power amplifier, etc.) adapted to convert a baseband signal into a modulated carrier signal suitable for transmission over the network-side interface <NUM>. The receiver <NUM> may include any component or collection of components (e.g., down-converter, low noise amplifier, etc.) adapted to convert a carrier signal received over the network-side interface <NUM> into a baseband signal. The signal processor <NUM> may include any component or collection of components adapted to convert a baseband signal into a data signal suitable for communication over the device-side interface(s) <NUM>, or vice-versa. The device-side interface(s) <NUM> may include any component or collection of components adapted to communicate data-signals between the signal processor <NUM> and components within the host device (e.g., the processing system <NUM>, local area network (LAN) ports, etc.).

The transceiver <NUM> may transmit and receive signaling over any type of communications medium. In some embodiments, the transceiver <NUM> transmits and receives signaling over a wireless medium. For example, the transceiver <NUM> may be a wireless transceiver adapted to communicate in accordance with a wireless telecommunications protocol, such as a cellular protocol (e.g., long-term evolution (LTE), etc.), a wireless local area network (WLAN) protocol (e.g., Wi-Fi, etc.), or any other type of wireless protocol (e.g., Bluetooth, near field communication (NFC), etc.). In such embodiments, the network-side interface <NUM> comprises one or more antenna/radiating elements. For example, the network-side interface <NUM> may include a single antenna, multiple separate antennas, or a multi-antenna array configured for multi-layer communication, e.g., single input multiple output (SIMO), multiple input single output (MISO), multiple input multiple output (MIMO), etc. In other embodiments, the transceiver <NUM> transmits and receives signaling over a wireline medium, e.g., twisted-pair cable, coaxial cable, optical fiber, etc. Specific processing systems and/or transceivers may utilize all of the components shown, or only a subset of the components, and levels of integration may vary from device to device.

Claim 1:
A method for a multicast service, the method comprising:
receiving, by a user equipment, UE (<NUM>), of a group of UEs (<NUM>, <NUM>, <NUM>), a downlink control information, DCI, message comprising a resource allocation field (<NUM>, <NUM>, <NUM>, <NUM>) from a base station, BS (<NUM>), wherein the DCI message is a multicast DCI message sent to the group of UEs (<NUM>, <NUM>, <NUM>), the resource allocation field (<NUM>, <NUM>, <NUM>, <NUM>) indicates a starting resource block, RB, index and a length of a set of contiguous RBs located within a common sequence of contiguous RBs belonging to bandwidth parts, BWPs (<NUM>, <NUM>), scheduled to respective UEs (<NUM>, <NUM>) of the group of UEs (<NUM>, <NUM>, <NUM>);
identify, by the UE (<NUM>), the set of contiguous RBs located within the common sequence of contiguous RBs as a set of contiguous RBs allocated for a multicast physical downlink shared channel, PDSCH, or a multicast physical uplink shared channel, PUSCH, based on the resource allocation field (<NUM>, <NUM>, <NUM>, <NUM>); and
transmitting or receiving, by the UE (<NUM>), data over at least one RB of the set of contiguous RBs allocated for the multicast PDSCH or the multicast PUSCH.