Method and apparatus for resource allocation and operation in a wireless communication system to support unicast and multicast / broadcast services

Abstract

Embodiments herein disclose a method and apparatus for resource allocation in a wireless communication system supporting multicast and broadcast service (MBS). The method comprises receiving, from a base station, configuration information associated with the MBS; and receiving, from the base station, MBS data on a common frequency resource (CFR) configured based on the configuration information, wherein the CFR is configured in a unicast bandwidth part (BWP).

Description

Technical Field

[0001] The embodiments disclosed herein relate to multicast / broadcast services in fifth-generation (5G) communication networks, and more specifically, to resource allocation and operation for multicast / broadcast services in 5G networks. Background Technology

[0002] To meet the growing demand for wireless data services since the deployment of 4G (4th generation) communication systems, efforts have been made to develop improved 5G (5th generation) or near-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as 'super 4G networks' or 'post-LTE systems'.

[0003] 5G communication systems are envisioned to be implemented in higher frequency (mmWave) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G communication systems.

[0004] In addition, in 5G communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation.

[0005] In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM), and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) have been developed as advanced access technologies.

[0006] The Internet, a human-centric network for generating and consuming information, has evolved into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), a combination of IoT technology and big data processing technology, has emerged through connectivity to cloud servers. With the increasing demand for technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology in the realization of IoT, sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have recently been researched.

[0007] This IoT environment can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to a variety of fields through the integration and combination of existing information technology (IT) with various industrial applications, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0008] 5G supports legacy Multimedia Broadcast Multicast Service (MBMS) in 4G LTE radio systems. However, the architecture and requirements of 5G MBMS may be significantly different compared to 4G LTE networks.

[0009] Specifically, multicast service refers to a service sent and utilized by a group of User Equipments (UEs) registered with the group, such as the MCPTT (Mission Critical Talk-Touch) service. Broadcast service refers to a service sent to all UEs within a specific coverage area and available to all UEs, and typically, no UE registration is required to utilize the broadcast service. Therefore, in practice, both multicast and broadcast services are PTM (Point-to-Multipoint) services, due to the existence of one sender and multiple receivers. Similarly, multicast and broadcast services are provided in PTP (Point-to-Point), which involves multiple PTP connections to share the same MBS service with multiple receivers. Besides MBS, there is another category of service known as unicast service, which is only for one receiver. For unicast services, a one-to-one dedicated connection between the sender and receiver is required.

[0010] PTM bearers, PTP bearers, or a combination of PTM and PTP bearers can carry the same MBS service. The combination of PTM and PTP bearers can provide many features such as improved reliability of receiving MBS service packets and efficient switching between the two reception modes when needed, for example, due to mobility, network load conditions, or based on the density of user requests to receive MBS services. Therefore, the network can determine the delivery mode and / or handover. This paper mentions a bearer configuration that may have two branches, PTM and PTP, referred to as MBS split bearer. Summary of the Invention

[0011] Technical issues

[0012] An aspect of the embodiments herein is to disclose a method and apparatus for resource allocation in a wireless communication system supporting multicast and broadcast services (MBS).

[0013] An aspect of the embodiments herein is to disclose a method and apparatus for resource allocation and operation of multicast / broadcast services in a 5G network, including several configuration modes or alternatives of MBS BWP and / or public MBS CFR (public frequency resources).

[0014] Solution to the problem

[0015] Therefore, embodiments of this document provide a method performed by a user equipment (UE) in a wireless communication system supporting multicast and broadcast services (MBS), the method comprising: receiving configuration information associated with MBS from a base station; and receiving MBS data on a common frequency resource (CFR) configured based on the configuration information from the base station, wherein the CFR is configured in a unicast bandwidth portion (BWP).

[0016] Therefore, embodiments of this document provide a UE in a wireless communication system supporting MBS, the UE including: a transceiver; and a processor configured to: receive configuration information associated with MBS from a base station via the transceiver; and receive MBS data on a CFR configured based on the configuration information from the base station via the transceiver, wherein the CFR is configured in a unicast BWP.

[0017] Therefore, embodiments of this document provide a method performed by a base station in a wireless communication system supporting MBS, the method comprising: transmitting configuration information associated with MBS; and transmitting MBS data on a CFR configured based on the configuration information, wherein the CFR is configured in a BWP.

[0018] Therefore, embodiments of this document provide a base station in a wireless communication system that supports MBS, the base station comprising: transmitting configuration information associated with MBS; and transmitting MBS data on a CFR configured based on the configuration information, wherein the CFR is configured in a BWP.

[0019] Therefore, embodiments of this document provide a method for allocating resources to multicast and broadcast services (MBS) in a network. The method includes a user equipment (UE) determining, by means of a user equipment (UE), the resource allocation of an MBS on at least one MBS BWP (bandwidth portion) or CFR (common frequency resource) and the association of the MBS BWP or CFR with a unicast BWP. The MBS BWP or CFR may be one of the following: entirely confined within a unicast BWP, partially overlapping with a unicast BWP, or separately spaced from a unicast BWP. The method further includes: being performed by the UE based on the determination that the MBS BWP or CFR is entirely confined within a unicast BWP; and the UE (100) receiving MBS services on an active unicast BWP or CFR according to a radio resource control (RRC) configuration, wherein if the unicast BWP is deactivated, the UE stops receiving MBS services on the BWP and terminates the MBS service. The method further includes: being performed by the UE based on determining that the MBS BWP or CFR partially overlaps with or is separately spaced from the unicast BWP; and being received by the UE (100) using dynamic switching between the MBS BWP or CFR and the unicast BWP and utilizing at least one of multiple receiver chains (such as carrier aggregation across the MBS BWP / CFR and the unicast BWP) to receive MBS services on the MBS BWP or CFR.

[0020] Embodiments herein also disclose providing resource allocation for at least one MBS BWP or CFR in at least one of a Time Domain Resource Allocation (TDRA) field and a Frequency Domain Resource Allocation (FDRA) field, wherein at least one of the TDRA field and FDRA field for MBS is configured or preconfigured via at least one of an RRC reconfiguration message or a broadcast message (such as an SIB (System Information Block) or an MCCH (MBS Control Channel)), and the MBS resource allocation via at least one of the TDRA field and FDRA field is dynamically indicated in DCI (Downlink Control Information) signaling via a PDCCH (Physical Downlink Control Channel). The DCI is scrambled with the G-RNTI of the relevant MBS service.

[0021] The embodiments of this document also disclose a method that further includes: the UE sending an RRC connection request or RRC recovery request to the network to continue receiving MBS services, and also includes an indication of MBS services and / or BWP / CFR information so that the network appropriately configures active downlink (DL) and / or uplink (UL) unicast BWP and / or MBS BWP or CFR to support the UE continuing to receive MBS services while receiving MBS services in idle mode or inactive mode and transitioning from idle mode or inactive mode to connected mode.

[0022] The embodiments in this article also disclose that the UE maintains a BWP inactivity timer while receiving MBS services, wherein the BWP inactivity timer is configured by the network via RRC signaling.

[0023] The embodiments of this document also disclose that when a UE receives a PDCCH addressed to a G-RNTI (Group Radio Network Temporary Identifier) / G-CS-RNTI (Group Configuration Scheduling Radio Network Temporary Identifier) ​​or C-RNTI (Cell Radio Network Temporary Identifier), the PDCCH indicates a downlink assignment received on an MBS BWP or CFR, or a MAC PDU received in a downlink assignment configured for multicast.

[0024] The embodiments in this document also disclose that, upon receiving MBS service and the expiration of the BWP inactivity timer, the UE performs either a BWP handover to the default downlink BWP (if a default downlink BWP is configured) or a BWP handover to the initial downlink BWP.

[0025] The embodiments herein also disclose the maintenance of the MBS-bwp-InactivityTimer for MBS service reception on the MBS BWP or CFR. If a PDCCH addressing to a G-RNTI / G-CS-RNTI or C-RNTI indicating a downlink assignment received on the active MBS BWP, CFR, or MAC PDU is received in the downlink assignment configured for multicast, then the UE initiates or restarts the MBS-bwp-InactivityTimer of the MBS BWP or CFR associated with the active DL BWP. When both the bwp-InactivityTimer and the MBS-bwp-InactivityTimer associated with the active DL BWP expire, the UE performs a BWP handover to the default downlink BWP (if a default downlink BWP is configured); otherwise, the UE performs a BWP handover to the initial downlink BWP.

[0026] The embodiments herein also disclose that if MBS service reception is configured and / or activated and associated with an MBS BWP or MBS sub-BWPCFR within a unicast BWP, then the UE begins receiving MBS services on the activated MBS BWP or MBS sub-BWPCFR within the activated unicast BWP according to the Radio Resource Control (RRC) configuration.

[0027] The embodiments of this document also disclose that when the unicast BWP is deactivated, the UE performs at least one of the following operations: clearing the downlink assignment and uplink authorization of the configuration authorization type 2 associated with at least one of the unicast service or MBS service on the BWP; and suspending the uplink authorization of the configuration authorization type 1 associated with at least one of the unicast service or MBS service on the BWP.

[0028] The embodiments herein also disclose that after a unicast BWP is deactivated or put to sleep, the UE performs at least one of the following operations: stops receiving MBS services on the MBS BWP / CFR associated with the unicast BWP and terminates the MBS service; or switches the MBS service to either the default BWP or the initial BWP.

[0029] The embodiments described herein also disclose that if the unicast BWP is reactivated, then MBS reception is switched back to the unicast BWP.

[0030] The embodiments of this document also disclose that if MBS service reception is configured and / or activated and associated with an MBS BWP or CFR configured within a unicast BWP, and the unicast BWP is deactivated or dormant and no uplink feedback is configured, then the UE continues to receive MBS services on the MBS BWP or CFR.

[0031] The embodiments of this document also disclose that if an MBS service is received for broadcast service and is associated with an MBS BWP or CFR configured within a unicast BWP, and the unicast BWP is deactivated or dormant, then the UE continues to receive the MBS service on the MBS BWP or CFR.

[0032] In one aspect, embodiments of this document provide a user equipment (UE). The UE includes a memory, at least one processor, and a resource allocation controller. The memory and at least one processor are connected to the resource allocation controller. The resource allocation controller is configured to determine resource allocation of an MBS on at least one MBS BWP (Bandwidth Partial) or CFR (Common Frequency Resource) and the association of the MBS BWP or CFR with a unicast BWP, wherein the MBS BWP or CFR can be one of: entirely confined within a unicast BWP, partially overlapping with a unicast BWP, or separately spaced from a unicast BWP. Based on the determination that the MBS BWP or CFR is entirely confined within a unicast BWP, the resource allocation controller is further configured to receive MBS service on an active unicast BWP or CFR according to Radio Resource Control (RRC) configuration; if the unicast BWP is deactivated, the resource allocation controller stops receiving MBS service on the BWP and terminates the MBS service. Based on the determination that the MBS BWP or CFR partially overlaps with the unicast BWP or is separately spaced from the unicast BWP, the resource allocation controller is also configured to receive MBS services on the MBS BWP or CFR by dynamically switching between the MBS BWP or CFR and the unicast BWP and by utilizing at least one of multiple receiver chains (such as carrier aggregation across MBS BWP / CFR and unicast BWP).

[0033] Embodiments herein also disclose providing resource allocation for at least one MBS BWP or CFR in at least one of a Time Domain Resource Allocation (TDRA) field and a Frequency Domain Resource Allocation (FDRA) field, wherein at least one of the TDRA field and FDRA field for MBS is configured or preconfigured via at least one of an RRC reconfiguration message or a broadcast message (such as an SIB (System Information Block) or an MCCH (MBS Control Channel)), and the MBS resource allocation via at least one of the TDRA field and FDRA field is dynamically indicated in DCI (Downlink Control Information) signaling via a PDCCH (Physical Downlink Control Channel). The DCI is scrambled with the G-RNTI of the relevant MBS service.

[0034] The embodiments herein also disclose that the resource allocation controller sends an RRC connection request or an RRC recovery request to the network, and further include an indication for at least one of MBS service and MBS BWP / CFR information, so that the UE (100) continues to receive MBS service when it is receiving MBS service in one of idle mode or inactive mode and when it transitions from one of idle mode or inactive mode to connected mode.

[0035] The embodiments in this article also disclose that the UE maintains a BWP inactivity timer while receiving MBS services, wherein the BWP inactivity timer is configured by the network via RRC signaling.

[0036] The embodiments of this document also disclose that when a UE receives a PDCCH addressed to a G-RNTI (Group Radio Network Temporary Identifier) / G-CS-RNTI (Group Configuration Scheduling Radio Network Temporary Identifier) ​​or C-RNTI (Cell Radio Network Temporary Identifier), the PDCCH indicates a downlink assignment received on an MBS BWP or CFR, or a MAC PDU received in a downlink assignment configured for multicast.

[0037] The embodiments in this document also disclose that, upon receiving MBS service and the expiration of the BWP inactivity timer, the UE performs either a BWP handover to the default downlink BWP (if a default downlink BWP is configured) or a BWP handover to the initial downlink BWP.

[0038] The embodiments in this document also disclose that if MBS service reception is configured and / or activated and associated with an MBS BWP or CFR within a unicast BWP, then the UE

[0039] Based on the Radio Resource Control (RRC) configuration, begin receiving MBS services within an active unicast BWP or on a CFR.

[0040] The embodiments in this document also disclose that when the unicast BWP is deactivated, the UE performs at least one of the following operations:

[0041] Clear the downlink assignment and uplink authorization of configuration authorization type 2 associated with at least one of the unicast service or MBS service on the BWP; and

[0042] Suspend uplink authorization for configuration authorization type 1 configurations associated with at least one of the unicast service or MBS service on BWP.

[0043] The embodiments herein also disclose that after a unicast BWP is deactivated or put to sleep, the UE (100) performs at least one of the following operations:

[0044] Stop receiving MBS services on the MBS BWP / CFR associated with the unicast BWP and terminate the MBS service; or switch the MBS service to either the default BWP or the initial BWP.

[0045] These and other aspects of the embodiments herein will be better understood and appreciated when considered in conjunction with the following description and accompanying drawings. However, it should be understood that while the following description indicates at least one embodiment and its many specific details, these descriptions are given by way of illustration and not limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit of this document, and the embodiments herein include all such modifications. Attached Figure Description

[0046] The embodiments disclosed herein are illustrated in the accompanying drawings, throughout which the same reference numerals indicate corresponding portions in the various figures. The embodiments herein will be better understood from the following description with reference to the accompanying drawings, in which:

[0047] Figure 1A , Figure 1B and Figure 1C An example architecture of the protocol stack for a UE implementation supporting MBS services is depicted;

[0048] Figure 2 Various hardware components of a UE for allocating resources to multicast and broadcast services (MBS) in a network, according to embodiments disclosed herein, are shown.

[0049] Figure 3A , Figure 3B , Figure 3C , Figure 3D , Figure 3E , Figure 3F , Figures 3G to 3H Various configuration modes or alternatives of MBS BWP and / or MBS CFR according to embodiments disclosed herein are described;

[0050] Figure 4A A method for operating a BWP inactive timer while receiving an MBS and for switching the BWP after the BWP inactive timer expires while receiving an MBS, according to embodiments disclosed herein;

[0051] Figure 4B A method is described for operating a BWP inactivity timer while MBS and unicast reception are being performed, and for switching BWPs after the BWP inactivity timer expires while MBS and unicast reception are being performed, according to embodiments disclosed herein.

[0052] Figure 4CA method is described, according to embodiments disclosed herein, for operating an MBS BWP inactivity timer during MBS reception and during unicast reception, and for performing BWP handover after the MBS BWP inactivity timer expires during MBS reception and after the BWP inactivity timer expires during unicast reception; and

[0053] Figure 5 A method for allocating resources to multicast and broadcast services (MBS) in a network, according to embodiments disclosed herein, is described. Detailed Implementation

[0054] In describing embodiments of this disclosure, descriptions related to techniques well-known in the art and not directly associated with this disclosure will be omitted. This omission of unnecessary descriptions is intended to prevent obscuring the main ideas of this disclosure and to more clearly convey the key concepts.

[0055] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the size of each element does not perfectly reflect its actual size. Identical or corresponding elements in the drawings are given the same reference numerals.

[0056] The advantages and features of this disclosure, and the ways in which they are implemented, will become apparent from reference to the embodiments described in detail below in conjunction with the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided merely to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements. Furthermore, in describing this disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where such detailed descriptions might unnecessarily obscure the subject matter of the disclosure. The terminology described below is defined in consideration of the functions in this disclosure and may vary depending on the user, the user's intention, or custom. Therefore, the definitions of the terminology should be made based on the entire contents of the specification.

[0057] In the following text, a base station is the entity that performs resource allocation to user equipment (UE) and can be at least one of a gNode B, gNB, eNode B, eNB, Node B, base station (BS), radio access unit, base station controller, and nodes on the network. A base station can be a network entity in an NR system, including at least one of an Integrated Access and Backhaul (IAB) donor and an IAB node. The IAB donor is a gNB that provides network access to (multiple) UEs via a network of backhaul and access links. The IAB node is a radio access network (RAN) node that supports multiple NR access links to (multiple) UEs and supports NR backhaul links to the IAB donor or other IAB nodes. UEs can wirelessly connect via IAB nodes and can send data to or receive data from an IAB donor connected to at least one IAB node via a backhaul link.

[0058] The UE may include a terminal, mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, "downlink" refers to a radio link through which a base station transmits signals to the UE, and "uplink" refers to a radio link through which the UE transmits signals to the base station. Furthermore, although the following description may refer to LTE or LTE-A systems by way of example, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types to embodiments of this disclosure. Examples of other communication systems may include fifth-generation mobile communication technologies (5G, New Radio, NR) developed in addition to LTE-A, and in the following description, "5G" may be a concept encompassing existing LTE, LTE-A, and other similar services. Moreover, based on determinations made by those skilled in the art, this disclosure may be applied to other communication systems with modifications without explicitly departing from the scope of this disclosure.

[0059] In this document, it should be understood that each box in a flowchart illustration, and combinations of boxes in a flowchart illustration, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create parts for implementing the functions specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium, which can instruct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of art comprising instruction parts that implement the functions specified in one or more flowchart boxes. Computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowchart boxes.

[0060] Additionally, each box in the flowchart diagram can represent a module, code segment, or code section, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in the boxes may not appear in a specific order. For example, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order, depending on the functionality involved.

[0061] As used herein, "cell" refers to a software or hardware element that performs a predetermined function, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC). However, "cell" is not always limited to software or hardware. A "cell" can be configured to be stored in addressable storage media or to execute one or more processors. Thus, a "cell" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a "cell" can be combined into a smaller number of elements or "cells," or divided into a larger number of elements or "cells." Furthermore, elements and "cells" can be implemented as replicas of one or more CPUs within a device or secure multimedia card. Additionally, a "cell" in an embodiment may include one or more processors.

[0062] Wireless communication systems have evolved from initial wireless communication systems that provided voice-oriented services to broadband wireless communication systems that provide high-speed and high-quality packet data services, such as wireless communication systems based on communication standards including 3GPP High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE) (or Evolved Universal Terrestrial Radio Access (E-UTRA)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2 High-Speed ​​Packet Data (HRPD), Ultra Mobile Broadband (UMB), and IEEE 802.16e.

[0063] In LTE systems, a representative example of broadband wireless communication systems, the downlink (DL) uses an Orthogonal Frequency Division Multiplexing (OFDM) scheme, and the uplink (UL) uses a Single-Carrier Frequency Division Multiple Access (SC-FDMA) scheme. The uplink refers to the radio link through which the UE transmits data or control signals to the base station (BS) (or eNode B), while the downlink refers to the radio link through which the base station transmits data or control signals to the UE. In this multiple access scheme, data or control information for each user is typically distinguished by assigning and manipulating time-frequency resources. Each user's data or control information is transmitted at that time-frequency resource to avoid overlap, i.e., orthogonality is established.

[0064] 5G communication systems (i.e., future communication systems after LTE) should be able to freely reflect the various requirements of users, service providers, etc., so as to support services that simultaneously meet various requirements. Services considered for 5G communication systems include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC).

[0065] eMBB aims to provide significantly higher data transmission rates than existing LTE, LTE-A, or LTE-Pro systems. For example, in a 5G communication system, from a base station's perspective, eMBB should be able to provide a maximum data rate (peak data rate) of 20Gbps in the downlink and a peak data rate of 10Gbps in the uplink. 5G communication systems need to provide both peak data rates and increased perceived data rates for the UE. To meet these requirements, various transmit and receive technologies need improvement, including more advanced multi-antenna (Multiple-Input Multiple-Output (MIMO)) transmission technologies. While a maximum transmit bandwidth of 20MHz can be used in the 2GHz band used in LTE, in 5G communication systems, the required data transmission rates can be met by using a wider frequency bandwidth than 20MHz in the 3GHz to 6GHz band or at 6GHz or higher.

[0066] Meanwhile, mMTC is being considered to support application services in 5G communication systems, such as the Internet of Things (IoT). To efficiently deliver IoT, mMTC may need to support large-scale UE access within a cell, enhanced UE coverage, improved battery life, and reduced UE cost. IoT attaches to multiple sensors and various devices to support communication functions, meaning it should be able to support a large number of UEs within a cell (e.g., 1,000,000 UEs / km²). Due to the nature of the service, UEs supporting mMTC may be located in shadow areas not covered by the cell (such as basements of buildings), and therefore may require wider coverage compared to other services provided by 5G communication systems. UEs supporting mMTC may need to be low-cost UEs, and due to the difficulty in frequently replacing UE batteries, they may need very long battery lives, such as 10 to 15 years.

[0067] Finally, URLLC corresponds to cellular-based wireless communication services for specific purposes (mission-critical). Examples include services for remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, emergency alerts, etc. Therefore, communication provided by URLLC should also offer very low latency and very high reliability. For example, services supporting URLLC should meet an air interface latency of less than 0.5 milliseconds and a packet error rate of 10⁻⁵ or lower. Therefore, services supporting URLLC may require 5G systems to provide shorter Transmission Time Intervals (TTIs) than other services, and may also require design considerations for allocating wide resources in the frequency band to ensure the reliability of the communication link.

[0068] Three 5G services—eMBB, URLLC, and mMTC—can be reused and transmitted within a single system. Different transmission or reception technologies and parameters can be used between these services to meet their varying requirements. 5G is not limited to these three services.

[0069] For ease of description below, some terms and names defined in 3GPP standards (standards for 5G, NR, LTE, or similar systems) may be used. However, this disclosure is not limited to these terms and names and can be applied equivalently to systems conforming to other standards. Terms used in the following description to identify access nodes, to indicate network entities, to indicate messages, to indicate interfaces between network entities, to indicate various identification information, etc., are for illustrative purposes only. Therefore, this disclosure is not limited to the terms used herein, and other terms referring to objects with equivalent technical meanings may be used.

[0070] The embodiments described herein, along with their various features and advantageous details, are explained more fully with reference to the non-limiting embodiments illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques have been omitted to avoid unnecessarily obscuring the embodiments herein. The examples used herein are merely intended to facilitate understanding of how the embodiments described herein can be practiced and to enable those skilled in the art to practice the embodiments described herein. Therefore, these examples should not be construed as limiting the scope of the embodiments described herein.

[0071] Figures 1A to 1C An example architecture of the protocol stack for a UE implementation supporting MBS services is depicted. Primarily, three types of radio bearer architectures are shown, as follows:

[0072] 1. PTP MRB based on PTP RLC bearer

[0073] 2. PTM MRB based on PTM RLC bearer

[0074] 3. MBS segmented bearer based on PTM+PTP RLC bearer

[0075] RLC PTM is UM (Unacknowledged Mode) RLC, which does not support ARQ (Automatic Repeat Request) functionality; that is, it supports RLC-level transmission because there is no feedback or status report between the transmitting and sending RLC entities. RLC PTM can be either UM mode or AM (Acknowledged Mode) RLC. AM RLC supports status / feedback sharing from receiver to transmitter and retransmission of negatively acknowledged RLC packets from transmitter to receiver. Therefore, there is a further enhancement in reliability that can be ensured by utilizing the AM RLC layer. Effectively, lossless operation is achieved when utilizing AM RLC mode.

[0076] The PDCP layer performs reordering operations and employs a reordering timer (t-Reordering) to ensure that out-of-order packets received from the RLC (or from two RLCs in the MBS split bearer) are rearranged in order of their sequence numbers (SNs) before the t-Reordering timer expires. If the reordering timer expires and there is still a gap with the PDCP receive window (i.e., a missing PDCP PDU SN, preventing reordering and in-sequence delivery from being completed to a higher layer), PDCP further moves the receive window (i.e., updates its state variable RX_DELIV) and performs delivery of the received PDCP PDUs until the lower edge of the window, RX_DELIV (the gap where the missing PDCP PDU SN is also delivered), is reached.

[0077] MBS segmented bearers with both PTM RLC and PTP RLC bearers increase the reliability of MBS bearers due to lossless operation from the PTP path, while the PTM path provides less delay for packets because no retransmissions are involved, although there is a possibility of loss. By combining these two paths via PDCP reordering operations, there is a greater chance of receiving PDCP PDUs before t-Reordering expires and providing ordered, sequential delivery to higher layers.

[0078] The embodiments described herein implement methods and systems for resource allocation and operation of multicast / broadcast services in 5G networks. Reference is now made to the accompanying drawings, and more specifically to... Figures 2 to 5 C, where similar reference numerals are used throughout the figures to indicate corresponding features, illustrates at least one embodiment.

[0079] Figure 2 Various hardware components of a UE for allocating resources to multicast and broadcast services (MBS) in a network, according to embodiments disclosed herein, are illustrated. UE 100 includes a resource allocation controller 110, a communicator (e.g., a transceiver) 120, a memory 130, and a processor 140. Furthermore, a base station communicating with the UE may be configured to include a transceiver and a processor.

[0080] Resource allocation controller 110 can determine the resource allocation of MBS on at least one MBS BWP (Bandwidth Part) or CFR (Common Frequency Resource) and the association between the MBS BWP or CFR and the unicast BWP, wherein the MBS BWP or CFR can be one of the following: completely confined within the unicast BWP, partially overlapping with the unicast BWP, or separately spaced from the unicast BWP. Based on the determination that the MBS BWP or CFR is completely confined within the unicast BWP, resource allocation controller 110 is also configured to receive MBS service on the MBS BWP or CFR within the active unicast BWP according to Radio Resource Control (RRC) configuration, wherein if the unicast BWP is deactivated, then the resource allocation controller stops receiving MBS service on the BWP and terminates the MBS service. Based on determining that the MBS BWP or CFR partially overlaps with the unicast BWP or is separately spaced from the unicast BWP, the resource allocation controller 110 is also configured to dynamically switch between the MBS BWP or CFR and the unicast BWP and to receive MBS services on the MBS BWP or CFR using at least one of multiple receiver chains (such as carrier aggregation across MBS BWP / CFR and unicast BWP).

[0081] Resource allocation controller 110 can also receive unicast services and MBS services from the network.

[0082] In some embodiments, resource allocation for at least one MBS BWP or CFR is provided in at least one of a Time Domain Resource Allocation (TDRA) field and a Frequency Domain Resource Allocation (FDRA) field, wherein at least one of the TDRA and FDRA fields for MBS is configured or preconfigured via at least one of an RRC reconfiguration message or a broadcast message (such as an SIB (System Information Block) or an MCCH (MBS Control Channel)), and the MBS resource allocation via at least one of the TDRA and FDRA fields is dynamically indicated in DCI (Downlink Control Information) signaling via a PDCCH (Physical Downlink Control Channel). The DCI is scrambled with G-RNTI associated with MBS service.

[0083] In some embodiments, the resource allocation controller is configured to send an RRC connection request or RRC recovery request to the network to continue receiving MBS services, and also includes an indication of MBS services and / or BWP / CFR information so that the network appropriately configures active downlink (DL) and / or uplink (UL) unicast BWPs and / or MBS BWPs or CFRs to support the UE to continue receiving MBS services while receiving MBS services in idle or inactive mode and transitioning from idle or inactive mode to connected mode.

[0084] In some embodiments, the resource allocation controller is configured to maintain a BWP inactivity timer while receiving MBS services, wherein the BWP inactivity timer is configured by the network via RRC signaling. The resource allocation controller is also configured to start or restart the BWP inactivity timer upon receiving a PDCCH addressed to a G-RNTI (Group Radio Network Temporary Identifier) / G-CS-RNTI (Group Configuration Scheduling Radio Network Temporary Identifier) ​​or C-RNTI (Cell Radio Network Temporary Identifier), which indicates a downlink assignment received on the MBS BWP or CFR, or a MAC PDU received in a downlink assignment configured for multicast.

[0085] In some embodiments, upon receiving MBS service and the BWP inactivity timer expiring, the resource allocation controller is configured to perform either a BWP handover to the default downlink BWP (if a default downlink BWP is configured) or a BWP handover to the initial downlink BWP.

[0086] In some embodiments, an MBS-bwp-InactivityTimer is maintained for MBS service reception on an MBS BWP or CFR. If a PDCCH addressing to a G-RNTI / G-CS-RNTI or C-RNTI indicating a downlink assignment received on an active MBS BWP, CFR, or MAC PDU is received in the downlink assignment configured for multicast, then the resource allocation controller is configured to start or restart the MBS-bwp-InactivityTimer of the MBS BWP or CFR associated with the active DL BWP. When both the bwp-InactivityTimer and MBS-bwp-InactivityTimer associated with the active DL BWP expire, the resource allocation controller is configured to perform a BWP handover to the default downlink BWP (if a default downlink BWP is configured); otherwise, the resource allocation controller is configured to perform a BWP handover to the initial downlink BWP.

[0087] In some embodiments, if MBS service reception is configured and / or activated and associated with an MBS BWP or MBS CFR within a unicast BWP, then the resource allocation controller is configured to begin receiving MBS services on the activated MBS BWP or CFR within the activated unicast BWP according to the Radio Resource Control (RRC) configuration.

[0088] In some embodiments, when the unicast BWP is deactivated, the resource allocation controller is configured to perform at least one of the following operations: clear the downlink assignment and uplink authorization of the configuration authorization type 2 associated with at least one of the unicast service or MBS service on the BWP; and suspend the uplink authorization of the configuration authorization type 1 associated with at least one of the unicast service or MBS service on the BWP.

[0089] In some embodiments, after a unicast BWP is deactivated or hibernated, the resource allocation controller is configured to perform at least one of the following operations: stop receiving MBS services on the MBS BWP / CFR associated with the unicast BWP and terminate the MBS service; or switch the MBS service to either the default BWP or the initial BWP.

[0090] In some embodiments, if the unicast BWP is reactivated, then MBS reception is switched back to the unicast BWP.

[0091] In some embodiments, if MBS service reception is configured and / or activated and associated with an MBS BWP or CFR configured within a unicast BWP, and the unicast BWP is deactivated or dormant and no uplink feedback is configured, then the resource allocation controller is configured to continue receiving MBS services on the MBS BWP or CFR.

[0092] In some embodiments, if the MBS service is received for broadcast service and is associated with an MBSBWP or CFR configured within a unicast BWP, and the unicast BWP is deactivated or hibernated, then the UE continues to receive the MBS service on the MBS BWP or CFR.

[0093] Additionally, processor 140 is configured to execute instructions stored in memory 130 and to execute various processes. Communicator 120 is configured to communicate internally between internal hardware components and with external devices via one or more networks. Memory 130 also stores instructions to be executed by processor 110. Memory 130 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Furthermore, in some examples, memory 130 may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not contained in a carrier wave or propagating signal. However, the term "non-transitory" should not be construed as meaning that memory 130 is immovable. In some examples, non-transitory storage media may store data that can change over time (e.g., stored in random access memory (RAM) or cache).

[0094] At least one of the multiple modules can be implemented using an AI model. AI-related functions can be executed using non-volatile memory, volatile memory, and processor 140. Processor 140 may include one or more processors. These processors may be general-purpose processors, such as a central processing unit (CPU), application processor (AP), etc.; graphics processing units only, such as a graphics processing unit (GPU); a vision processing unit (VPU); and / or AI-specific processors, such as a neural processing unit (NPU).

[0095] One or more processors control the processing of input data based on predefined operating rules or artificial intelligence (AI) models stored in non-volatile and volatile memory. These predefined operating rules or AI models are provided through training or learning.

[0096] Here, providing through learning means generating predefined operating rules or AI models with desired characteristics by applying a learning algorithm to multiple learning datasets. Learning can be performed within the device itself that performs the AI ​​according to the embodiment, and / or can be implemented via a separate server / system.

[0097] AI models can include multiple neural network layers. Each layer has multiple weight values, and layer operations are performed by computing the previous layer and operating on the multiple weights. Examples of neural networks include, but are not limited to, Convolutional Neural Networks (CNNs), Deep Neural Networks (DNNs), Recurrent Neural Networks (RNNs), Restricted Boltzmann Machines (RBMs), Deep Belief Networks (DBNs), Bidirectional Recurrent Deep Neural Networks (BRDNNs), Generative Adversarial Networks (GANs), and Deep Q-Networks.

[0098] A learning algorithm is a method used to train a predetermined target device (such as a robot) using multiple training data sets so that the target device makes a determination or prediction. Examples of learning algorithms include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0099] although Figure 2 Various hardware components of UE 100 are illustrated, but it should be understood that other embodiments are not limited thereto. In other embodiments, UE 100 may include fewer or more components. Furthermore, the labels or names of components are for illustrative purposes only and do not limit the scope of the invention. One or more components may be combined together to perform the same or substantially similar functions in UE 100.

[0100] Figures 3A to 3F Various configuration modes or alternatives for MBS BWP and / or public MBS CFR are described. For example, the first mode is considered as 'X', the second mode as 'Y', and the third mode as Y1...Yn.

[0101] Case 1 :like Figure 3A As described, the MBS BWP or MBS CFR 'Y' is confined within the unicast BWP 'X', such that X > Y. In the PDCCH configuration, there is no need for BWP handover across unicast services and MBS, and therefore no handover latency. UE100 can receive both unicast and MBS services simultaneously. The MBS BWP or MBS CFR can be statically or dynamically assigned.

[0102] Case 2 :like Figure 3BAs described, the MBS BWP or MBS CFR 'Y' is confined within the unicast BWP 'X', such that X = Y. In the PDCCH configuration, there is no need for BWP handover across unicast and MBS, and therefore no handover delay. UE 100 can receive both unicast and MBS services simultaneously.

[0103] Case 3 :like Figure 3C As described, the MBS BWP or MBS CFR 'Y' also extends beyond the unicast BWP 'X', such that X < Y. If UE 100 dynamically switches between the MBS BWP or MBS CFR and the unicast BWP, or uses two different reception paths or carrier aggregation, then UE 100 can receive both unicast and MBS services simultaneously.

[0104] Case 4 :like Figure 3D As described, the MBS BWP or MBS CFR 'Y' is not entirely limited to the unicast BWP 'X'. There is a starting offset of the MBS BWP or MBS CFR relative to the unicast BWP. All three cases—X > Y, X = Y, and X < Y—are possible. If the UE 100 dynamically switches between the MBS BWP or MBS CFR and the unicast BWP, or utilizes two different receive paths, or utilizes carrier aggregation, then the UE 100 can receive both unicast and MBS services simultaneously.

[0105] Case 5 :like Figure 3E As described, MBS BWPs or MBS CFRs 'Y1', 'Y2', and 'Yn' are confined within unicast BWP 'X', such that X > Y1, X > Y2, ..., X > Yn. In the PDCCH configuration, BWP handover across unicast services and MBS is not required, and therefore there is no handover latency. UE 100 can receive both unicast and MBS services simultaneously. MBS BWPs or MBS CFRs Y1, Y2, ..., Yn can be statically or dynamically assigned.

[0106] Case 6 :like Figure 3F As shown, the MBS BWP or MBS CFR'Z' is not entirely different from the unicast BWP X. All three cases—X>Y, X=Y, and X<Y—are possible. Therefore, there is a BWP handover involved. If UE 100 dynamically switches between the MBS BWP or MBS CFR and the unicast BWP, or uses two different receive paths, or uses carrier aggregation, then UE 100 can receive both unicast and MBS services simultaneously.

[0107] Case 7Static MBS configuration within a BWP can limit the flexibility of MBS and unicast resource scheduling. Therefore, dynamic / semi-static MBS frequency allocation can be provided within the BWP. Dynamic or semi-static "sub-BWPs (MBS)" can be configured via RRC signaling, and MAC-CE or PDCCH indications can be used to activate or deactivate the configuration.

[0108] Case 7.1 Dynamic or semi-static configurations within a BWP that vary across "sub-BWPs" will also increase the flexibility of resource management based on channel conditions and geographic regions, thereby minimizing interference in MBS resources (e.g., Figure 3G (As depicted in the text).

[0109] Case 7.2 In configuration mode, the MBS uplink (UL) BWP Y' is shown together with the MBS downlink (DL) BWP Y. In the example, the MBS UL BWP Y' can be located outside the unicast DL BWP (e.g., Figure 3H (As depicted in the text).

[0110] Mapping BWP / MBS CFRs to different use cases and channels of MBS services

[0111] The embodiments herein disclose mapping unicast BWPs and MBS BWPs or MBS CFRs to different use cases, operating states / modes, and physical channel uses for MBS service purposes.

[0112] Unicast BWP:

[0113] - It is mapped for unicast service delivery.

[0114] - Mapped for separate service delivery for MBS service (PDU session). The control channel PDCCH is addressed by the UE 100's C-RNTI. MBS service data is mapped to the UE 100-specific PDCCH.

[0115] - The PTP mode for delivery by the gNB is mapped for shared service delivery of MBS services. The control channel PDCCH is addressed by the UE 100's C-RNTI. MBS service data is mapped to the UE 100-specific PDCCH.

[0116] - The PTM mode for delivery by gNB is mapped for shared service delivery of MBS services. In unicast BWP, the control channel PDCCH is addressed by UE 100's C-RNTI. MBS service data is mapped to the group common PDSCH in MBS BWP or MBS CFR. This can be used for connection-only multicast and connection-only broadcast services that may require higher reliability or QoS.

[0117] -Mapped for connection-only mode of multicast services and connection-only mode of broadcast services that may require higher reliability or QoS.

[0118] - HARQ feedback, CSI feedback, measurement reports, UE assistance information, or other uplink signaling / message delivery for unicast services and / or individual MBS service delivery on unicast BWP and / or PTP MBS delivery mode and / or PTM MBS service delivery on MBSBWP or MBS CFR. These are carried over uplink physical channels (such as PUCCH or PUSCH) on unicast BWP.

[0119] MBS BWP or MBS CFR:

[0120] - The PTM mode for delivery by the gNB is mapped for shared service delivery of MBS services. The control channel PDCCH is addressed by UE 100's G-RNTI / G-CS-RNTI. MBS service data is mapped to the group common PDSCH. This can be used for connection-only multicast and connection-only broadcast services that may require higher reliability or QoS. This can be used for connection / idle / inactive modes of broadcast services or connection / idle / inactive modes of multicast services that do not require high reliability or QoS, and will be received by different UEs in idle, inactive, or connected modes.

[0121] - The PTM mode for delivery by the gNB is mapped for shared service delivery of MBS services. The control channel PDCCH is addressed by the UE 100's C-RNTI. MBS service data is mapped to the group common PDSCH. This can be used for connection-only multicast and connection-only broadcast services that may require higher reliability or QoS.

[0122] - PTM MBS service delivery on MBS BWP or MBS CFR is mapped for HARQ feedback, CSI feedback, measurement reports, UE assistance information, or other uplink signaling / message transmission. These are carried over the uplink physical channels (such as PUCCH or PUSCH) on MBS BWP / MBS CFR.

[0123] In the embodiments described herein, HARQ feedback, CSI feedback, measurement reports, UE assistance information, or other uplink signaling / message transmission related to MBS service are carried via an uplink physical channel (such as PUCCH or PUSCH) mapped to one of the following:

[0124] -Mapped to the unicast uplink BWP, and UE 100 exclusively uses the UE-specific PDCCH on the unicast BWP and the UE-specific PDSCH on the unicast BWP.

[0125] -Mapped to the unicast uplink BWP, and UE 100 exclusively uses the UE-specific PDCCH on the unicast BWP and the group common PDSCH on the MBS BWP or MBS CFR.

[0126] -Mapped to the MBS uplink BWP / MBS CFR, which may or may not be the same as the (downlink) MBS BWP or MBS CFR for which UE 100 receives PTM MBS services, and UE 100 exclusively uses the UE-specific PDCCH on the unicast BWP and the group common PDSCH on the MBS BWP or MBS CFR.

[0127] -Mapped to the MBS uplink BWP / MBS CFR, which may or may not be the same as the (downlink) MBS BWP or MBS CFR for which UE 100 receives PTM MBS services, and UE 100 exclusively uses the group common PDCCH on the MBS BWP / MBS CFR and the group common PDSCH on the MBS BWP or MBS CFR.

[0128] -Mapped to the MBS uplink BWP / MBS CFR, which may or may not be the same as the (downlink) MBS BWP or MBS CFR on which the UE receives PTM MBS service, and the UE 100 exclusively uses the UE-specific PDCCH on the MBS BWP / MBS CFR and the group common PDSCH on the MBS BWP or MBS CFR.

[0129] In one embodiment of this document, resource allocation for MBS BWP or MBS CFR is provided in the TDRA (Time Domain Resource Allocation) and / or FDRA (Frequency Domain Resource Allocation) fields of the DCI (Downlink Control Information) field in the PDCCH. The PDCCH may be associated with a UE-specific PDCCH carried via unicast BWP or CORESET and / or a UE-specific PDCCH or group common PDCCH carried via MBS BWP, MBS CFR, or CORESET. Different TDRA / FDRA combinations of resources can also be pre-configured using RRC reconfiguration messages and / or broadcast messages (such as SIB or MCCH), and only the TDRA / FDRA index field is provided in the PDCCH at runtime and / or dynamically. Information transmitted in the TDRA includes at least one of the following: start slot / symbol, offset, allocated duration or length, and / or end slot / symbol. Information transmitted in the FDRA includes at least one of the following: start physical resource block (PRB), offset, PRB allocated length, and / or end PRB, BWP, or MBS CFR size. The DCI carrying TDRA and / or FDRA is scrambled with G-RNTI or G-CS-RNTI of the relevant MBS service.

[0130] CFR transitions across PTM / PTP / unicast and idle / inactive / connected and BWP / MBS

[0131] For example, in 3GPP 38.321, BWP handover for the serving cell is used to activate inactive BWPs and deactivate active BWPs each time. BWP handover is controlled by the PDCCH indicating downlink assignment or uplink grant after initiating a random access procedure or when a consistent LBT (Listen-After-Talk) failure is detected on the SpCell, by the bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself. After RRC (re)configuration or SCell activation of the firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id of the SpCell, the DL BWP and / or UL BWP (indicated by firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id, respectively) are active without receiving a PDCCH indicating downlink assignment or uplink grant. The active BWP of the serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP handover is common to both UL and DL.

[0132] For each SCell, a dormant BWP can be configured with a dormantDownlinkBWP-Id via RRC signaling. Entering or leaving a dormant BWP for a SCell can be accomplished by switching BWPs by pressing the SCell. Entering or leaving a dormant BWP for a SCell can also be accomplished by pressing the dormant SCell group based on instructions from the PDCCH. Dormant SCell group configuration can be configured via RRC signaling. Upon receiving a PDCCH indicating a leave of a dormant BWP, the DL BWP indicated by firstOutsideActiveTimeBWP-Id or firstWithinActiveTimeBWP-Id is activated. Upon receiving a PDCCH indicating an enter of a dormant BWP, the DL BWP indicated by dormantDownlinkBWP-Id is activated.

[0133] The embodiments in this paper disclose various scenarios and methods for addressing BWP handover and state / mode transitions by combining MBS reception services.

[0134] In the embodiments described herein, for each active serving cell configured with a unicast BWP, and with UE 100 configured and / or activated to receive multiple MBS services on the active unicast BWP, the UE begins receiving MBS services on the active BWP according to the RRC configuration and / or broadcast configuration. The MBS service may correspond to an MBS service received in unicast mode or received PTP mode. The PDCCH is addressed using a UE-specific C-RNTI. MBS content is received via a UE-specific PDSCH. Additionally, the PTM mode for receiving MBS services on the MBS BWP or MBS CFR can be restricted to the active unicast BWP. Therefore, MBS services requiring uplink feedback transmission on the unicast uplink physical channel can also be received. This includes HARQ feedback, CSI feedback, measurement reports, UE assistance information, or other uplink signaling / message transmission for unicast services, and / or individual MBS service delivery on the unicast BWP and / or PTP MBS delivery modes. These are carried via uplink physical channels (such as PUCCH or PUSCH) on the unicast uplink BWP. The selection of the target BWP should be based on the maximum (unicast, MBS) service; that is, the selection of the BWP should be based on the maximum requirement of MBS or unicast.

[0135] For each active serving cell configured with BWP, the MAC entity will:

[0136] 1> If the BWP is activated, and the serving cell's active DL BWP is not a dormant BWP:

[0137] 2> Send on UL-SCH on BWP;

[0138] 2> If PRACH timing is configured, then it will be sent on RACH on the BWP;

[0139] 2> Monitor PDCCH on BWP;

[0140] 2> Send PUCCH on BWP, if configured;

[0141] 2> Report CSI to BWP;

[0142] 2> Send SRS on BWP, if configured;

[0143] 2> Receive DL-SCH on BWP;

[0144] 2> If the MBS service reception is configured and / or activated and is associated with an active BWP or MBS sub-BWP within a unicast BWP:

[0145] 3> Based on the RRC configuration, start receiving MBS services from the active BWP or MBS sub-BWP within the unicast BWP.

[0146] 2> Reinitialize uplink authorization for any suspended configuration of type 1 on the active BWP based on the stored configuration (if it exists), and start in the symbol according to the rules in Section 5.8.2;

[0147] 2> If consistent LBT fault recovery is configured:

[0148] 3> Stop lbt-FailureDetectionTimer if it is running;

[0149] 3> Set LBT_COUNTER to 0;

[0150] 3> As specified in Clause 5.21.2, monitor LBT fault indications from the lower level.

[0151] In the embodiments described herein, UE 100 notifies the network of MBS service interruption by signaling, if possible, on a newly activated unicast BWP and / or an activated serving cell, which may be due to unicast BWP deactivation / sleep and / or serving cell deactivation. In response, UE 100 receives a new configuration for MBS service from the network to continue MBS service.

[0152] Alternatively, UE 100 switches from PTP or unicast mode to receive PTM mode and continues to receive MBS services on MBS BWP or MBS CFR.

[0153] Alternatively, UE 100 switches from PTM mode with a UE-specific PDCCH addressed by C-RNTI / CS-RNTI on a unicast BWP to PTM mode with a group common PDCCH addressed by G-RNTI / G-CS-RNTI on an MBS BWP / MBS CFR. UE 100 can also switch from uplink physical channels PUCCH or PUSCH mapped to a unicast BWP to uplink physical channels PUCCH or PUSCH mapped to an MBS BWP / MBS CFR.

[0154] UE 100 utilizes MBS service on the newly activated DL BWP, if it is available or provided on request. In another embodiment herein, once the unicast BWP is deactivated, UE 100 can be configured to the default BWP in the connected / idle / inactive mode of MBS reception. Furthermore, if the unicast BWP is reactivated, MBS reception can be switched back to the unicast BWP.

[0155] 1> If the BWP is activated, and the serving cell's active DL BWP is a dormant BWP:

[0156] 2> Stop the bwp-InactivityTimer of the serving cell if it is running.

[0157] 2> Do not monitor PDCCH on BWP;

[0158] 2> PDCCH is not monitored for BWP;

[0159] 2> Do not receive DL-SCH on BWP;

[0160] 2> Perform periodic or semi-persistent CSI measurements on BWP, if configured;

[0161] 2> Do not send SRS on BWP;

[0162] 2> Do not send on UL-SCH on BWP;

[0163] 2> Do not send PUCCH on BWP;

[0164] 2> Clear downlink assignments and uplink authorization type 2 of any configurations associated with SCell;

[0165] 2> Suspend uplink authorization type 1 for any configuration associated with SCell;

[0166] 2> If configured, beam fault detection and beam fault recovery will be performed for SCell in the event of a beam fault.

[0167] 2> If MBS service reception is configured and / or activated and associated with BWP, then:

[0168] 3> Stop receiving MBS service on BWP and terminate the service.

[0169] Alternatively, the MBS service can switch to the default BWP in idle / inactive mode. The MBS service can also switch to the default MBS DL BWP in connected mode, where the associated configured / active MBS UL BWP is used to send feedback, such as... Figure 3H As shown in the image.

[0170] If MBS service is received on BWP, then UE 100 does not consider BWP to be dormant, and continues to monitor PDCCH and perform semi-persistent CSI measurements of BWP.

[0171] 1> If the BWP is deactivated and / or due to cross-BWP monitoring PDCCH / feedback-drx timing issues, activation / deactivation timers, BWP timers and operations, delays or gaps during BWP switching, or transition from PTP to PTM:

[0172] 2> Do not send on UL-SCH on BWP;

[0173] 2> Do not send on the RACH of the BWP;

[0174] 2> Do not monitor PDCCH on BWP;

[0175] 2> Do not send PUCCH on BWP;

[0176] 2> Do not report CSI to BWP;

[0177] 2> Do not send SRS on BWP;

[0178] 2> Do not receive DL-SCH on BWP;

[0179] 2> Clear downlink assignments and uplink authorizations configured for type 2 on the BWP;

[0180] 2>Suspend uplink authorization for any configuration of type 1 on an inactive BWP.

[0181] 2> If MBS service reception is configured and / or activated and associated with BWP, then:

[0182] 3> Stop receiving MBS service on BWP and terminate the service.

[0183] In another embodiment of this document, the MBS service can switch to the default BWP in idle / inactive mode. The MBS service can also switch to the default MBS DL BWP in connected mode, where the associated configured / active MBS UL BWP is used to send feedback, such as... Figure 3H As shown in the image.

[0184] In the embodiments described herein, if no uplink feedback is configured for MBS service, UE 100 continues to receive MBS service despite unicast BWP deactivation / sleep and / or serving cell deactivation; or if uplink feedback is configured for MBS service, UE 100 does not provide feedback but facilitates HARQ retransmission of MBS service.

[0185] If uplink feedback has been configured, or a new unicast BWP providing MBS service has been activated, or a new unicast BWP has been configured, and UE 100 cannot operate unicast and MBS services together, then UE 100 will stop / terminate the MBS service.

[0186] UE 100 notifies the network by signaling on the newly activated unicast BWP, and may receive new configurations for MBS service from the network to continue MBS service.

[0187] UE 100 switches the MBS BWP or MBS CFR to the MBS BWP or MBS CFR associated with the newly activated unicast BWP and / or configured by the network, and utilizes / continues MBS service.

[0188] In the embodiments described herein, by switching the uplink feedback to an uplink physical channel (such as PUCCH or PUSCH) mapped to the MBS BWP or MBS CFR, the UE 100 continues to receive MBS service even when the uplink feedback is configured for MBS service, despite unicast BWP deactivation / sleep and / or serving cell deactivation.

[0189] Alternatively, the MBS service can switch to the default BWP in idle / inactive mode. The MBS service can also switch to the default MBS DL BWP in connected mode, where the associated configured / active MBS UL BWP is used to send feedback, such as... Figure 3H As shown in the image.

[0190] 1> If BWP is deactivated, then:

[0191] 2> Do not send on UL-SCH on BWP;

[0192] 2> Do not send on the RACH of the BWP;

[0193] 2> Do not monitor PDCCH on BWP;

[0194] 2> Do not send PUCCH on BWP;

[0195] 2> Do not report CSI to BWP;

[0196] 2> Do not send SRS on BWP;

[0197] 2> Do not receive DL-SCH on BWP;

[0198] 2> Clear downlink assignments and uplink authorizations configured for type 2 on the BWP;

[0199] 2>Suspend uplink authorization for any configuration of type 1 on an inactive BWP.

[0200] 2> If MBS service reception is configured and / or activated and associated with an MBS BWP or MBSCFR restricted to a unicast BWP, and no uplink feedback is configured; or

[0201] 2> If MBS service reception is for broadcast MBS and is related to an MBS BWP or MBSCFR that is confined to a unicast BWP, then:

[0202] 3> Continue receiving MBS services on MBS BWP / MBS CFR

[0203] 3> Continue monitoring PDCCH on MBS BWP / MBS CFR;

[0204] 3> Continue to receive the DL-SCH of the group public PDSCH for MBS services on MBS BWP / MBS CFR.

[0205] MBSBWP switching when receiving unicast service

[0206] In the embodiments described herein, UE 100 receives an RRC reconfiguration or broadcast message, such as an SIB or MCCH, which provides a modified configuration for the PTM service, such as changes to the MBS BWP or MBS CFR and / or other parameters or MAC CE-based signaling, thereby causing a handover of the MBS BWP or MBS CFR of the PTM service being utilized by UE 100. In this scenario, UE 100 performs a reconfiguration and / or a handover to a new BWP or MBS CFR associated with the same or different unicast BWP. During the reconfiguration, UE 100 runs an MBS-bwpSwitchTimer, and during this period, UE 100 does not receive MBS transmissions associated with the affected MBS BWP or MBS CFR. The timer value may also depend on the subcarrier spacing (SCS), BWP, MBS CFR, frequency range (e.g., FR1 below 6 GHz or FR2 above 6 GHz), and / or other parameters. In the case where UE 100 involves a split MBS bearer with PTM and PTP tributaries, and only PTM reception is affected due to an interruption, UE 100 continues to receive on the PTP tributary during the interruption of MBS BWP or MBS CFR handover. Additionally, if HARQ feedback (related to PTM reception by UE 100) is carried on the PTP, the absence of HARQ feedback on the PTP during the PTM interruption period will not be considered DTX or NACK and will not be considered for retransmission. In another embodiment, if the uplink feedback is mapped to an uplink physical channel (e.g., PUCCH or PUSCH) on the MBS BWP / MBS CFR, it is mapped to an uplink physical channel on the unicast BWP.

[0207] In the embodiments described herein, if the current BWP is insufficient for MBS service but sufficient for unicast service, UE 100 should be configured for a wider BWP (considering MBS service), where the BWP configuration can be MAX(MBS, unicast).

[0208] In the embodiments described herein, certain low QoS services can be received by UEs in idle, inactive, or connected states in multicast and / or broadcast delivery modes. These services are typically low QoS-dependent and do not require HARQ or ARQ retransmissions, and are therefore suitable for reception in any RRC state. For example, a UE already connected for unicast services can receive these services in connected mode, while a UE in idle or inactive mode (or a UE that can move into idle or inactive mode) can also receive these services with better battery performance. Two alternatives can be considered for receiving these low QoS services by UEs in different RRC states:

[0209] 1. Deliver MBS services in PTM mode, where the MBS service is using an MBS BWP or MBS CFR and shares active BWPs across connected mode and initial and / or default BWPs across idle / inactive mode.

[0210] 2. MBS service is delivered in PTM mode, using either an MBS BWP or MBS CFR. This differs for the active BWP in connected mode, the default MBS BWP in connected mode, and the initial and / or default BWP in idle / inactive mode. When UE 100 switches RRC states, UE 100 also moves across the active BWP in connected mode, the default MBS BWP in connected mode, and the initial / default BWP in idle / inactive mode. Signaling and control information (such as SIB, MCCH, paging for PTM UEs, etc.) is also sent in the corresponding BWP or MBS CFR. Additionally, the service information for PTM service carries the MBS CFR information in both the configuration of the connected and idle / inactive mode BWPs or in broadcast signaling (such as SIB, MCCH, or RRC reconfiguration messages), allowing UE 100 to utilize PTM service in the corresponding RRC state, across RRC state transitions, and continue receiving MBS service after appropriate reconfiguration.

[0211] UE 100 transitions from connected mode to idle or inactive mode when one of the following events occurs:

[0212] -RRCRelease message received: UE 100 transitions to idle mode. UE 100 continues to receive MBS services in idle mode.

[0213] - Serving cell deactivation: UE 100 transitions to idle / inactive mode. UE 100 continues to receive MBS service in idle / inactive mode.

[0214] - Unicast BWP Deactivation: UE 100 transitions to idle / inactive mode. UE 100 continues to receive MBS service in the initial and / or default BWP of idle / inactive mode.

[0215] -MBS BWP or MBS CFR deactivation: UE 100 transitions to idle / inactive mode. UE 100 continues to receive MBS service in the initial and / or default BWP of idle / inactive mode.

[0216] - Unicast reception DataInactivityTimer expires: When the DataInactivity timer used for unicast reception expires, UE 100 releases the RRC connection and transitions to idle mode. UE 100 continues to receive MBS services in idle mode.

[0217] - When receiving MBS on a unicast BWP, the DataInactivityTimer expires: In addition to the unicast DataInactivityTimer, UE 100 operates an additional MBS-DataInactivityTimer, or a single timer for both MBS and unicast service packets. When either of these timers or the single timer expires, UE 100 transitions to idle mode. UE 100 continues to receive MBS services in idle mode.

[0218] - When receiving MBS on MBS BWP or MBS CFR, the DataInactivityTimer expires: The UE maintains the MBS-DataInactivity Timer when the timer expires (when no MBS service packet is received within the specified time of the MBS-DataInactivityTimer). If no other unicast service is received or the unicast DataInactivityTimer has also expired or is not yet running, then UE 100 transitions to idle / inactive mode. In other words, if the dataInactivity Timer expires for a unicast service and the MBS dataInactivityTimer is running, then UE 100 will remain in connected mode to receive MBS service using the connected mode MBS defaultBWP. Alternatively, UE 100 does not need to attempt to continue receiving MBS service in idle / inactive mode. Upon notification to UE 100 of MBS service availability / restart or paging / group paging or broadcast information regarding MBS service, UE 100 begins receiving MBS service in idle / inactive mode and / or transitions to connected mode.

[0219] If no unicast service is received and the data inactivity period has expired, but the MBS service continues, then UE 100 can move to the default MBS-BWP in connected mode and deactivate the UE-specific BWP, or alternatively, UE 100 can move to idle / inactive mode and receive MBS service on the initial or default BWP.

[0220] - RRCRelease with pause configuration: UE 100 transitions to inactive mode, and UE 100 continues to receive MBS services in inactive mode.

[0221] - RRCRelease with redirection: UE 100 performs a reselection of the redirected frequency or cell, and UE 100 continues to receive MBS service in idle mode.

[0222] UE 100 performs a transition from idle or inactive mode to connected mode while already receiving MBS service in idle or inactive mode due to UL or DL ​​data arrival, service requests, TAU / RAN updates, or other signaling. UE 100 initiates an RRC connection request or RRC Resume request, which also includes an indication of MBS service or BWP / MBS CFR information, enabling the network to appropriately configure active DL and / or UL unicast BWP and / or MBS BWP / MBS CFR to support the continuation of MBS service reception for UE 100.

[0223] Switching between PTM delivery mode and PTP delivery mode

[0224] In the embodiments described herein, UE 100 switches between PTM delivery mode and PTP delivery mode when notified by the gNB, for example, through RRC reconfiguration or signaling from the MAC CE. To achieve this, UE 100 also performs handover across MBS BWP / MBS CFR and unicast BWP.

[0225] HARQ feedback for PTM services received on the MBS BWP or MBS CFR in the downlink, or PTP services received on the unicast BWP in the downlink, is carried to the gNB via the PUCCH or PUCCH physical channel through the unicast uplink BWP when supported. A mapping or identifier associated with the HARQ feedback exists to indicate whether it is related to a PTM path or a PTP path; for example, C-RNTI / G-RNTI / G-CS-RNTI / LCID / TMGI and / or PTM / PTP type, BWP / MBS CFR type, configuration ID, HARQ process ID, etc., can be used for identification. The number of feedbacks and identifiers carried depends on whether it is a PTP-only bearer, a PTP-only bearer, or a PTP+PTM segmented MBS bearer.

[0226] If UE 100 involves a split MBS bearer with both PTM and PTP tributaries and only PTM reception is affected due to an interruption, UE 100 continues reception on the PTP tributary during the MBS BWP or MBS CFR handover interruption. Additionally, if HARQ feedback related to PTM reception performed by UE 100 is carried on the PTP, the absence of HARQ feedback on the PTP during the PTM interruption period will not be considered DTX or NACK and will not be considered for retransmission. Furthermore, when there is a transition from PTM to PTP or PTP to PTM, temporary parallel reception can exist on the PTM and PTP paths to ensure a lossless transition. UE 100 maintains a transition timer and performs both types of reception. After the transition timer expires, UE 100 suspends the previous reception path and only continues the subsequent reception path. To facilitate a smooth transition, the gNB also ensures that the PTP / PTM reception path is established in advance or maintained during handover. Additionally, during the transition between the PTM and PTP paths, the HARQ feedback and transmission channels are switched accordingly.

[0227] For example, in 3GPP 38.321, if a MAC entity is configured with one or more SCells, the network can activate and deactivate the configured SCells. After a SCell is configured, it is deactivated unless the sCellState parameter is set by the upper layer to activate the SCell.

[0228] The following steps can be used to activate and deactivate configured (multiple) SCells:

[0229] - Receive SCell activation / deactivation MAC CE;

[0230] - Configure the sCellDeactivationTimer timer for each configured SCell (except for SCells with PUCCH configured, if present): The associated SCell is deactivated upon its expiration.

[0231] For each configured SCell, the MAC entity should:

[0232] 1> If the SCell is configured with an sCellState set to activate after the SCell is configured, or if a SCell activation / deactivation MAC CE is received that activates the SCell, then:

[0233] 2> If firstActiveDownlinkBWP-Id is not set to the dormant BWP, then:

[0234] 3> Activate the SCell according to the timing defined in TS 38.213; that is, apply normal SCell operations, including:

[0235] 4> SRS transmission on SCell;

[0236] 4>SCell's CSI report;

[0237] 4> PDCCH monitoring on SCell;

[0238] 4> SCell PDCCH monitoring;

[0239] 4> Send PUCCH on SCell, if configured;

[0240] 3> If the SCell is deactivated before receiving the SCell activation / deactivation MAC CE, or if the SCell is configured with an sCellState set to activate after the SCell is configured, then:

[0241] 4> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively;

[0242] 3> If the MBS service is configured and / or activated on SCell, then

[0243] 4> Start receiving MBS service on SCell on DL BWP as indicated by firstActiveDownlinkBWP-Id

[0244] 4> If it has already started, then continue, or start receiving MBS services on the SCell on the MBS BWP or MBS CFR associated with the DL BWP indicated by firstActiveDownlinkBWP-Id;

[0245] 5> Perform CSI reporting for MBS services on MBS BWP, MBS CFR, or unicast uplink resources identified by MBS CSI reports.

[0246] 3> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213;

[0247] 3> Reinitialize uplink authorization for any suspended configuration of configuration authorization type 1 associated with SCell based on the stored configuration (if it exists), and start in the symbol according to the rules in Section 5.8.2;

[0248] 3> Trigger PHR according to clause 5.4.6.

[0249] 2> Otherwise, if firstActiveDownlinkBWP-Id is set to the dormant BWP, then:

[0250] 3> Stop the bwp-InactivityTimer of the serving cell if it is running.

[0251] 3> If the SCell is deactivated before receiving the SCell activation / deactivation MAC CE, or if the SCell is configured with an sCellState set to activate after the SCell is configured, then:

[0252] 4> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively.

[0253] 3> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213.

[0254] Alternatively, the MBS service can switch to the default BWP in idle / inactive mode. The MBS service can also switch to the default MBS DL BWP in connected mode, where the associated configured / active MBS UL BWP is used to send feedback, such as... Figure 3H As shown in the image.

[0255] If a deactivation SCell MAC CE is received; or

[0256] 1> If the sCellDeactivationTimer associated with the activated SCell expires, then:

[0257] 2> Activate and deactivate the SCell according to the timing defined in TS 38.213;

[0258] 2> Stop the sCellDeactivationTimer associated with SCell.

[0259] 2> Stop the bwp-InactivityTimer associated with SCell;

[0260] 2> Deactivate any active unicast BWPs associated with SCell;

[0261] 2> If uplink feedback is not configured for the MBS service, then any active MBS BWP or MBS CFR associated with the SCell will not be activated.

[0262] 2> Clear downlink assignments and uplink authorization type 2 of any configurations associated with SCell;

[0263] 2> Remove any PUSCH resources used for semi-persistent CSI reports associated with SCell;

[0264] 2> Suspend uplink authorization type 1 for any configuration associated with SCell;

[0265] 2> Refresh all unicast HARQ buffers associated with SCell;

[0266] 2> Cancel (if any) the consistency LBT failure triggered by SCell.

[0267] When an SCell and / or SCG (secondary cell group) on which an MBS BWP or MBS CFR (i.e., associated with a unicast BWP of the SCell) is deactivated, if no uplink feedback is configured for MBS service, then UE 100 continues to receive MBS service on the MBS BWP or MBS CFR associated with the SCell.

[0268] 1> If SCell is deactivated, then:

[0269] 2> Do not send SRS on SCell;

[0270] 2> Do not report CSI for SCell;

[0271] 2> Do not send on the UL-SCH on the SCell;

[0272] 2> Do not send on the RACH on the SCell;

[0273] 2> Do not monitor PDCCH on SCells used for unicast;

[0274] 2> Not for monitoring PDCCH for SCell used for unicast;

[0275] 2> Do not send PUCCH on SCell.

[0276] 2> If no uplink feedback is configured for MBS service, then continue to receive MBS service on the MBSBWP or MBS CFR associated with the SCell.

[0277] 3> Monitor PDCCH on the SCell used for MBS;

[0278] 3> Monitoring PDCCH for SCell used in MBS;

[0279] The embodiments described herein also support cross-carrier scheduling for MBS reception. UE 100 receives PDCCH on the scheduling cell and monitors MBS allocation based on G-RNTI / G-CS-RNTI and / or C-RNTI on the unicast BWP and / or MBS BWP or MBS CFR on the scheduling cell (e.g., secondary cell SCell). If no uplink feedback is configured for MBS service, UE 100 monitors the PDCCH on the serving cell for MBS reception even when the SCell is deactivated. If no uplink feedback is configured for MBS service, UE 100 monitors the PDCCH for the serving cell for MBS reception even when the serving cell is deactivated.

[0280] Alternatively, even when the serving cell is deactivated, UE 100 monitors the PDCCH on the serving cell used for MBS reception and maps uplink feedback onto the uplink physical channel on the MBS BWP or MBS CFR.

[0281] In one embodiment of this document, when an associated unicast BWP is deactivated or switched and / or the serving cell is deactivated, MBS service on an MBS BWP or MBS CFR can be scheduled via PDCCH on a new or different active unicast BWP and / or a new / different serving cell. The new or different active unicast BWP can be associated with a service of the same serving cell or a service different from that of the serving cell on the same frequency as the MBS BWP; that is, it can be cross-carrier scheduling and / or cross-BWP scheduling. During the transition of a unicast BWP or serving cell, MBS service can be switched or utilized between PTM and PTP and / or unicast BWP and MBS BWP and / or connected and idle / inactive modes.

[0282] When UE 100 receives MBS service on unicast BWP, receives preemptive DCI and configures HARQ retransmission for MBS service, UE 100 applies preemptive DCI for MBS service reception, discards the indicated HARQ CBG (code block group) or TB (transmission block), and retransmits the required CBG / TB, and performs HARQ soft combining.

[0283] When UE 100 receives MBS services on MBS BWP / MBS CFR restricted to unicast BWP, receives a preemptive DCI and configures HARQ retransmission for MBS services, UE 100 ignores the preemptive DCI for MBS service reception purposes and continues HARQ soft combining.

[0284] In the embodiments described herein, the target cell MBS BWP or MBS CFR or unicast BWP configuration information is provided to UE 100 by the source gNB in ​​a handover command (RRC reconfiguration message). The source gNB and the target gNB exchange UE 100's interest indications and / or service information and / or BWP / MBS CFR information from the source gNB / cell, etc. The target gNB provides the source gNB with appropriate MBS BWP or MBS CFR and / or unicast BWP configurations to support the desired service continuity and lossless handover in PTM or PTP receive modes.

[0285] Figure 4A A method is described according to an embodiment for operating a BWP inactivity timer while receiving an MBS and for switching the BWP after the BWP inactivity timer expires while receiving an MBS.

[0286] In the embodiments described herein, an MBS-bwp-InactivityTimer is maintained for MBS service reception on MBS BWP or MBS CFR. (See reference...) Figure 4A In step 401, UE 100 is configured with a BWP inactivity timer and is receiving unicast, and UE 100 is configured with an MBS BWP inactivity timer and is receiving MBS. In step 402, if a PDCCH indicating a downlink assignment to a G-RNTI / G-CS-RNTI or C-RNTI is received in the downlink assignment configured for multicast, then in step 403, UE 100 starts or restarts the MBS-bwp-InactivityTimer associated with the active DL BWP or MBS CFR. In step 404, if a PDCCH indicating a downlink assignment to a C-RNTI is received on the active unicast BWP, then in step 405, UE 100 starts or restarts the bwp-InactivityTimer associated with the active DL BWP.

[0287] If the result is negative in step 404, then in step 406, when both the bwp-InactivityTimer and MBS-bwp-InactivityTimer associated with the active DL BWP expire, in steps 407 to 409, if defaultDownlinkBWP-Id is configured, then UE 100 performs a BWP handover to the default downlink BWP indicated by defaultDownlinkBWP-Id. Otherwise, UE 100 performs a BWP handover to the initial downlink BWP. If the result is negative in step 406, then UE 100 proceeds to step 402.

[0288] Furthermore, when the bwp-InactivityTimer associated with the active DL BWP expires, if defaultDownlinkBWP-Id is configured, UE 100 can perform a BWP handover to the default downlink BWP indicated by defaultDownlinkBWP-Id. Otherwise, UE 100 can perform a BWP handover to the initial downlink BWP.

[0289] For each active serving cell configured with bwp-InactivityTimer, the MAC entity should:

[0290] 1> If defaultDownlinkBWP-Id is configured, and the active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id, and the active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, if configured; or

[0291] 1> If defaultDownlinkBWP-Id is not configured, and the active DL BWP is not initialDownlinkBWP, and the active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, if it is configured; or

[0292] 2> If a PDCCH addressing to a C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received on the active BWP; or

[0293] 2> If a PDCCH addressing to a C-RNTI or CS-RNTI is received for an active BWP, indicating downlink assignment or uplink grant; or

[0294] 2> If a MAC PDU is sent in the configured uplink grant and no LBT fault indication is received from the lower layer; or

[0295] 2> If a MAC PDU is received in the configured downlink assignment:

[0296] 3> If there is no ongoing random access procedure associated with the serving cell; or

[0297] 3> If, after receiving the PDCCH addressed to the C-RNTI, the ongoing random access procedure associated with the serving cell is successfully completed (as specified in Clauses 5.1.4, 5.1.4a, and 5.1.5), then:

[0298] 4> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0299] 2> If an indication addressed to a G-RNTI or C-RNTI is received in the downlink assignment configured for multicast, the PDCCH of the downlink assignment received on the active MBS BWP or MBS CFR or MAC PDU;

[0300] 4> Start or restart MBS-bwp-InactivityTimer associated with the active DL BWP or MBS CFR.

[0301] 2> If the bwp-InactivityTimer and MBS-bwp-InactivityTimer associated with the activity DL BWP expire, then:

[0302] 3> If defaultDownlinkBWP-Id is configured, then:

[0303] 4> Perform a BWP switch to the BWP indicated by defaultDownlinkBWP-Id.

[0304] 3> Otherwise:

[0305] 4> Execute the BWP switch to initialDownlinkBWP.

[0306] 1> If a PDCCH for BWP handover is received, and the MAC entity is switching the active DL BWP, then:

[0307] 2> If defaultDownlinkBWP-Id is configured, and the MAC entity switches to a DL BWP that is not indicated by defaultDownlinkBWP-Id and not by dormantDownlinkBWP-Id (if configured); or

[0308] 2> If defaultDownlinkBWP-Id is not configured, and the MAC entity switches to a DL BWP that is not initialDownlinkBWP and is not indicated by dormantDownlinkBWP-Id (if configured), then:

[0309] 3> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0310] Figure 4B A method is described according to an embodiment for operating a BWP inactivity timer while MBS and unicast reception are being performed, and for performing a BWP switchover after the BWP inactivity timer expires while MBS and unicast reception are being performed.

[0311] refer to Figure 4B In step 411, UE 100 is configured with a BWP inactivity timer and is receiving MBS. When UE 100 receives MBS services associated with a unicast BWP, such as MBS services on a BWP or CFR (e.g., ...), Figure 4B (As shown) and in step 412, if an indication to G-RNTI / G-CS-RNTI or C-RNTI is received in the downlink assignment configured for multicast, indicating that a downlink assignment has been received on the active MBS BWP or MBS CFR or MAC PDU, then in step 413, UE 100 starts or restarts the bwp-InactivityTimer associated with the active DL BWP. In step 414, when the bwp-InactivityTimer associated with the active DL BWP expires, in steps 415 to 417, if defaultDownlinkBWP-Id is configured, then UE 100 performs a BWP handover to the default downlink BWP indicated by defaultDownlinkBWP-Id. Otherwise, UE 100 performs a BWP handover to the initial downlink BWP. If not in step 414, then UE 100 continues to step 412.

[0312] Figure 4C The invention describes a method according to an embodiment for operating an MBS BWP inactivity timer while receiving an MBS and operating a BWP inactivity timer while receiving a unicast, and for performing a BWP handover after the MBS BWP inactivity timer expires while receiving an MBS and after the BWP inactivity timer expires while receiving a unicast.

[0313] In the embodiments described herein, UE 100 can use MBS services for MBS BWP or MBS CFR to receive (e.g., Figure 4C (As shown) and the same public bwp-InactivityTimer used for unicast and / or MBS services on unicast BWP. Reference Figure 4C In step 421, UE 100 is configured with a BWP inactivity timer and is receiving unicast and / or MBS. In step 422, if a PDCCH addressing to a G-RNTI / G-CS-RNTI or MAC PDU is received in the downlink assignment configured for multicast, or a C-RNTI indicating downlink assignment received on the active MBS BWP or MBS CFR or MAC PDU is received in the downlink assignment configured for unicast, then in step 423, UE 100 starts or restarts the bwp-InactivityTimer for the MBS BWP or MBS CFR associated with the active DL BWP. In step 424, when the bwp-InactivityTimer associated with the active DL BWP expires, in steps 425 to 427, if defaultDownlinkBWP-Id is configured, then UE 100 performs a BWP handover to the default downlink BWP indicated by defaultDownlinkBWP-Id. Otherwise, UE 100 performs a BWP handover to the initial downlink BWP. If the result in step 424 is negative, then UE 100 proceeds to step 422.

[0314] In this embodiment, when a PDCCH addressing to G-RNTI / G-CS-RNTI for broadcasting MBS is received, bwp-InactivityTimer is not started or restarted.

[0315] For each active serving cell configured with bwp-InactivityTimer, the MAC entity should:

[0316] 1> If defaultDownlinkBWP-Id is configured, and the active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id, and the active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, if configured; or

[0317] 1> If defaultDownlinkBWP-Id is not configured, and the active DL BWP is not initialDownlinkBWP, and the active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, if it is configured; or

[0318] 2> If a PDCCH addressing to a C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received on the active BWP; or

[0319] 2> If a PDCCH addressing to a C-RNTI or CS-RNTI is received for an active BWP, indicating downlink assignment or uplink grant; or

[0320] 2> If the addressing of the G-RNTI / G-CS-RNTI or C-RNTI indicates a downlink-assigned PDCCH received on the MBSBWP or MBS CFR associated with the active unicast BWP; or

[0321] 2> If a MAC PDU is sent in the configured uplink grant and no LBT fault indication is received from the lower layer; or

[0322] 2> If a MAC PDU is received in the configured downlink assignment: or

[0323] 2> If a MAC PDU is received in the downlink assignment configured for multicast: or

[0324] 3> If there is no ongoing random access procedure associated with the serving cell; or

[0325] 3> If, after receiving the PDCCH addressed to the C-RNTI, the ongoing random access procedure associated with the serving cell is successfully completed (as specified in Clauses 5.1.4, 5.1.4a, and 5.1.5), then:

[0326] 4> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0327] 2> If the bwp-InactivityTimer associated with the activity DL BWP expires, then:

[0328] 3> If defaultDownlinkBWP-Id is configured, then:

[0329] 4> Perform a BWP switch to the BWP indicated by defaultDownlinkBWP-Id.

[0330] 3> Otherwise:

[0331] 4> Execute the BWP switch to initialDownlinkBWP.

[0332] 1> If a PDCCH for BWP handover is received, and the MAC entity is switching the active DL BWP, then:

[0333] 2> If defaultDownlinkBWP-Id is configured, and the MAC entity switches to a DL BWP that is not indicated by defaultDownlinkBWP-Id and not by dormantDownlinkBWP-Id (if configured); or

[0334] 2> If defaultDownlinkBWP-Id is not configured, and the MAC entity switches to a DL BWP that is not initialDownlinkBWP and is not indicated by dormantDownlinkBWP-Id (if configured), then:

[0335] 3> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0336] When UE 100 is receiving or is interested in receiving MBS services (which are essentially low QoS broadcast or multicast), UE 100 does not need to receive dedicated configuration from the network and / or UE 100 does not provide any uplink feedback for MBS service packet reception, such as HARQ feedback, RLC status reports, etc. The network may not be aware that UE 100 is receiving MBS services on an MBS BWP or MBS CFR that is restricted to a unicast BWP. Therefore, any further decisions made by the network to switch, deactivate, or hibernate the current unicast BWP (including switching to a smaller or larger unicast BWP or a unicast BWP that does not support an MBS BWP or MBS CFR or (multiple) specific MBS services, etc.) and / or serving cell deactivation affect UE 100's MBS service reception. Using UE 100 assistance information, UE 100 may notify one or more of the following (but not limited to):

[0337] -MBS receive status, for example, receiving broadcast / multicast in PTM mode for non-uplink feedback mode.

[0338] -MBS BWP

[0339] -MBS CFR

[0340] -UE 100 is receiving or is interested in receiving (multiple) MBS services in PTM mode.

[0341] - Requests to postpone or prevent unicast BWP deactivation and / or switching

[0342] - Preferred DRX parameters for MBS or unicast reception to better align unicast and MBS reception or enhance power efficiency.

[0343] -UE 100 is used for simultaneous reception capabilities, such as support for BWP, CA, dual / multiple RX / TX capabilities, carrier aggregation support, dual connectivity support, etc.

[0344] -Preferred RRC state of the UE based on MBS reception

[0345] -Requires BWP switching or MBS CFR including smaller or larger BWPs or MBS CFRs, or maintenance of existing BWP / MBS CFRs.

[0346] - The maximum bandwidth or BWP size required for unicast, multicast, or combination.

[0347] In the embodiments described herein, UE 100 may have multiple RX / TX capabilities and / or support for dual connectivity and / or MUSIM (multiple SIMs) and / or carrier aggregation (CA) and / or support for multiple RATs (Radio Access Technologies, such as 4G or 5G or LTE eMBMS or NR MBS). UE 100 can simultaneously support MBS reception and unicast reception on two different carriers / cells / SIMs / RATs / RF / BWPs, etc. UE 100 notifies the network of its capabilities. In addition, UE 100 utilizes its capabilities to perform concurrent unicast and multicast data reception, as well as uplink HARQ feedback, measurement operations, measurement reporting, CSI feedback, and / or mobility transitions.

[0348] In the embodiments described herein, UE 100 supports DSS (Dynamic Spectrum Sharing) as well as unicast and / or MBS reception. DSS involves sharing spectrum in the time / frequency domain with two RATs (e.g., LTE and NR), and the sharing can be based on a fixed or dynamic ratio.

[0349] In the embodiments described herein, UE 100 may provide one or more of the aforementioned information or parameters to the network in an MBS interest indication message, a count response message, a UL information delivery message, an RRC connection request, an RRC Resume request (e.g., when receiving MBS service in idle or inactive mode), or any other RRC message or MAC CE (control element). Message transmission may be triggered periodically or upon the occurrence of predefined events (e.g., when the unicast service mode changes, the DataInactivityTimer expires, UE 100 receives a DCI / MAC / RRC message for BWP handover, or when the unicast BWP is deactivated or put to sleep, or when an MBS interest indication or count response is triggered, etc.).

[0350] Figure 5 A method 500 for allocating resources to multicast and broadcast services (MBS) in a network, according to an embodiment, is shown.

[0351] In step 502, method 500 includes the UE 100 determining the resource allocation of an MBS on at least one MBS BWP or CFR and the association between the MBS BWP or CFR and the unicast BWP. In step 504, method 500 includes the UE 100 checking whether the MBS BWP or CFR is completely confined within the unicast BWP. If so, in step 508, method 500 includes the UE 100 checking whether the unicast BWP is activated, deactivated, or not dormant. If so, in step 510, method 500 includes the UE 100 receiving MBS services on the MBS BWP or CFR within the activated unicast BWP according to the RRC configuration. Otherwise, in step 512, method 500 includes the UE 100 stopping receiving MBS services on the MBS BWP or CFR within the inactive unicast BWP and terminating the MBS service. In step 506, method 500 includes checking whether UE 100 can support multiple receiver chains. If so, then in step 514, method 500 includes UE 100 using multiple receiver chains to receive MBS service on MBS BWP or CFR. In step 516, method 500 includes UE 100 receiving MBS service on MBS BWP or CFR during dynamic handover between MBS BWP or CFR and unicast BWP.

[0352] The embodiments disclosed herein can be implemented by at least one software program that runs on at least one hardware device and performs network management functions to control the elements.

[0353] The foregoing description of specific embodiments will so fully reveal the general nature of the embodiments herein that others can readily modify and / or adapt such specific embodiments for various applications by applying present knowledge without departing from the general concept, and therefore such adaptations and modifications should and are intended to be understood as being within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the wording or terminology used herein is for descriptive purposes and not as a limitation. Therefore, while embodiments herein have been described according to at least one embodiment, those skilled in the art will recognize that modifications can be made to practice the embodiments herein within the spirit and scope of the embodiments described herein.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system supporting multicast and broadcast services (MBS), the method comprising: Configuration information for configuring MBS frequency resources within the downlink bandwidth portion (BWP) is received from the base station via Radio Resource Control (RRC) signaling. On the Physical Downlink Control Channel (PDCCH), the base station receives downlink control information (DCI) scrambled with a Group Radio Network Temporary Identifier (G-RNTI). The DCI includes a Time Domain Resource Assignment (TDRA) for scheduling the Physical Downlink Shared Channel (PDSCH) for multicast and a Frequency Domain Resource Assignment (FDRA) for scheduling the PDSCH for multicast, wherein the FDRA is based on the configuration information for configuring the MBS frequency resources. Based on receiving a DCI scrambled by G-RNTI on an active BWP, start or restart the BWP inactivity timer, wherein the BWP inactivity timer is configured for each active serving cell of the UE; and Based on the expiration of the BWP inactivity timer, a BWP handover is performed to the BWP indicated by the default downlink BWP-ID.

2. The method of claim 1, wherein the configuration information indicates a common frequency resource (CFR) associated with the downlink BWP, and the MBS frequency resource includes the CFR.

3. The method of claim 2, wherein the configuration information includes at least one of information about the size of the CFR and information about the frequency domain location of the MBS.

4. The method according to claim 1, further comprising: The inactivity timer associated with the active BWP has expired, and the default downlink BWP-ID has been configured. and Based on the identification that the BWP inactivity timer associated with the active BWP has expired and the configuration of the default downlink BWP-ID, the BWP handover to the BWP indicated by the default downlink BWP-ID is performed.

5. The method of claim 1, further comprising: The BWP inactivity timer has expired and a default downlink BWP-ID has not been configured. and The BWP handover to the initial downlink BWP is performed based on the recognition that the BWP inactivity timer has expired and the default downlink BWP-ID has not been configured.

6. A user equipment (UE) in a wireless communication system supporting multicast and broadcast services (MBS), the UE comprising: transceiver; and Processor, the processor being configured to: The transceiver receives configuration information from the base station via Radio Resource Control (RRC) signaling for configuring MBS frequency resources within the downlink bandwidth portion (BWP). The transceiver receives downlink control information (DCI) scrambled with a Group Radio Network Temporary Identifier (G-RNTI) from the base station on the Physical Downlink Control Channel (PDCCH). The DCI includes a Time Domain Resource Assignment (TDRA) for scheduling the Physical Downlink Shared Channel (PDSCH) for multicast and a Frequency Domain Resource Assignment (FDRA) for scheduling the PDSCH for multicast, wherein the FDRA is based on the configuration information for configuring the MBS frequency resources. Based on receiving a DCI scrambled by G-RNTI on an active BWP, start or restart the BWP inactivity timer, wherein the BWP inactivity timer is configured for each active serving cell of the UE; and Based on the expiration of the BWP inactivity timer, a BWP handover is performed to the BWP indicated by the default downlink BWP-ID.

7. The UE of claim 6, wherein the configuration information indicates a common frequency resource (CFR) associated with the downlink BWP, and the MBS frequency resource includes the CFR.

8. The UE according to claim 7, wherein, The configuration information includes at least one of information about the size of the CFR and information about the frequency domain location of the MBS.

9. The UE according to claim 6, wherein, The processor is further configured to: The inactivity timer associated with the active BWP has expired, and the default downlink BWP-ID has been configured. Based on the identification that the BWP inactivity timer associated with the active BWP has expired and the configuration of the default downlink BWP-ID, the BWP handover to the BWP indicated by the default downlink BWP-ID is performed.

10. The UE according to claim 6, wherein, The processor is further configured to: The BWP inactivity timer was identified as having expired and a default downlink BWP-ID was not configured. Based on the discovery that the BWP inactivity timer has expired and the default downlink BWP-ID has not been configured, a BWP handover to the initial downlink BWP is performed.

11. A method performed by a base station in a wireless communication system supporting multicast and broadcast services (MBS), the method comprising: Configuration information for configuring MBS frequency resources within the downlink bandwidth portion (BWP) is sent to the user equipment (UE) via Radio Resource Control (RRC) signaling; On the Physical Downlink Control Channel (PDCCH), downlink control information (DCI) scrambled with Group Radio Network Temporary Identifier (G-RNTI) is sent to the UE. The DCI includes a Time Domain Resource Assignment (TDRA) for scheduling the Physical Downlink Shared Channel (PDSCH) for multicast and a Frequency Domain Resource Assignment (FDRA) for scheduling the PDSCH for multicast, wherein the FDRA is based on the configuration information for configuring the MBS frequency resources. Based on transmitting DCI scrambled by G-RNTI on the active BWP, a BWP inactivity timer is configured, wherein the BWP inactivity timer is configured for each active serving cell of the UE; and Based on the expiration of the BWP inactivity timer, determine whether to configure a default downlink BWP-ID associated with BWP handover.

12. The method of claim 11, wherein the configuration information indicates a common frequency resource (CFR) associated with the downlink BWP, the MBS frequency resource including the CFR.

13. The method of claim 12, wherein the configuration information includes at least one of information about the size of the CFR and information about the frequency domain location of the MBS.

14. A base station in a wireless communication system supporting multicast and broadcast services (MBS), the base station comprising: transceiver; and Processor, the processor being configured to: The transceiver transmits configuration information for configuring MBS frequency resources within the downlink bandwidth portion (BWP) to the user equipment (UE) via Radio Resource Control (RRC) signaling. The transceiver transmits downlink control information (DCI) based on the Group Radio Network Temporary Identifier (G-RNTI) to the UE on the Physical Downlink Control Channel (PDCCH). The DCI includes a Time Domain Resource Assignment (TDRA) for scheduling the Physical Downlink Shared Channel (PDSCH) for multicast and a Frequency Domain Resource Assignment (FDRA) for scheduling the PDSCH for multicast, wherein the FDRA is based on the configuration information for configuring the MBS frequency resources. Based on transmitting DCI scrambled by G-RNTI on the active BWP, a BWP inactivity timer is configured, wherein the BWP inactivity timer is configured for each active serving cell of the UE; and Based on the expiration of the BWP inactivity timer, determine whether to configure a default downlink BWP-ID associated with BWP handover.

15. The base station of claim 14, wherein the configuration information indicates a common frequency resource (CFR) associated with the downlink BWP, and the MBS frequency resource includes the CFR.

16. The base station of claim 15, wherein the configuration information includes at least one of information about the size of the CFR and information about the frequency domain location of the MBS.

Images