Method and user equipment (UE) for handling mbs services in a wireless network

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose a method for processing, by a UE (100), a MBS service in a wireless network (400). The method comprises receiving, in a SIB, a MCCH configuration and at least one parameter associated with the MCCH configuration. Further, the method comprises configuring a MCCH channel based on the MCCH configuration and the parameter associated with the MCCH configuration. Further, the method comprises receiving a MCCH information message over the MCCH channel. Further, the method comprises configuring at least one MTCH based on the MCCH information message. Further, the method comprises receiving the MBS service over the MTCH.

Description

Technical Field

[0001] The embodiments disclosed herein relate to wireless communication networks, and more specifically, to multicast / broadcast control signaling and idle / inactive mode procedures for multicast / broadcast service (MBS) of new radio (NR) in fifth-generation radio access technology (RAT). Background Technology

[0002] 5G mobile communication technology defines a wide frequency band to enable high transmission rates and new services, and it can be implemented not only in the "sub-6GHz" band, such as 3.5GHz, but also in the "above 6GHz" band, including 28GHz and 39GHz, known as millimeter waves. Furthermore, to achieve transmission rates 50 times faster than 5G and ultra-low latency one-tenth that of 5G, implementation of 6G mobile communication technology (referred to as Beyond 5G systems) in terahertz bands (e.g., the 95GHz to 3THz band) has been considered.

[0003] In the early stages of 5G mobile communication technology development, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization has been underway for beamforming and massive MIMO to mitigate radio wave path loss and increase radio wave transmission distance in millimeter waves. This supports parameter sets for dynamic operation of millimeter wave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technologies to support multi-beam transmission and broadband, the definition and operation of BWP (bandwidth portion), new channel coding methods (such as LDPC (low-density parity-check) codes for large data transmissions and polar codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology will support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization for technologies such as V2X (Vehicle-to-Everything) is also in place to assist autonomous vehicle driving decisions based on information sent by the vehicle regarding its location and status, and to enhance user convenience, NR-U (Unlicensed New Radio) for system operation in unlicensed frequency bands in compliance with various regulatory requirements, NR UE power saving, UE-satellite direct communication non-terrestrial networks (NTN) for providing coverage in areas where communication with terrestrial networks is unavailable, and positioning.

[0005] Furthermore, standardization is underway in the air interface architecture / protocol for technologies such as: Industrial Internet of Things (IIoT) to support new services through interoperability and convergence with other industries; IAB (Integrated Access and Backhaul) for nodes to provide network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover; and two-step random access (2-step RACH for NR) to simplify random access procedures. Standardization is also underway in the system architecture / services area for technologies such as: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and mobile edge computing (MEC) for UE location-based reception services.

[0006] With the commercialization of 5G mobile communication systems, an exponential increase in connected devices will be applied to communication networks. Consequently, enhanced functionality and performance of 5G mobile communication systems, as well as the integrated operation of connected devices, are expected to be necessary. To this end, new research is planned related to: Extended Reality (XR) for effectively supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc.; 5G performance improvements and complexity reductions through the utilization of Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will form the basis for developing technologies that include not only new waveforms for providing terahertz band coverage for 6G mobile communication technologies, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO), metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum), and the foundation of RIS (reconfigurable smart surfaces), but also full-duplex technologies for improving the frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technologies for implementing system optimization by leveraging satellites and AI (artificial intelligence) from the design phase and internalizing end-to-end AI support capabilities, and next-generation distributed computing technologies for implementing services with complexity exceeding the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical issues

[0009] One aspect of this disclosure is to provide an efficient and effective method and UE for configuring and operating the MCCH in a wireless communication system and for handling idle / inactive mode operation.

[0010] Solution to the problem

[0011] To address the problems described above, according to certain embodiments of this disclosure, a method for processing a multicast broadcast service (MBS) in a wireless network (400) by a terminal is proposed, the method comprising: receiving an MBS control channel (MCCH) configuration and at least one parameter associated with the MCCH configuration in a system information block (SIB) by a user equipment (UE) (100); configuring an MCCH channel by the UE (100) based on the MCCH configuration and the parameter associated with the MCCH configuration; receiving an MCCH information message by the UE (100) through the MCCH channel; configuring at least one MBS traffic channel (MTCH) by the UE (100) based on the MCCH information message; and receiving the MBS service by the UE (100) through the MTCH.

[0012] Meanwhile, according to various embodiments of this disclosure, a terminal for processing multicast broadcast service (MBS) services is provided. The terminal includes a transceiver and at least one processor, the at least one processor being configured to: receive an MBS control channel (MCCH) configuration and at least one parameter associated with the MCCH configuration in a System Information Block (SIB) via the transceiver; configure an MCCH channel based on the MCCH configuration and the parameter associated with the MCCH configuration; receive an MCCH information message through the MCCH channel; configure at least one MBS traffic channel (MTCH) based on the MCCH information message; and receive MBS services through the MTCH.

[0013] Beneficial effects of the invention

[0014] Embodiments of this disclosure may disclose an efficient and effective method and UE for MCCH configuration and operation of NR Multicast Service (MBS) for New Radio (NR) in fifth-generation radio access technology (RAT) and for handling idle / inactive mode operation. Attached Figure Description

[0015] The embodiments disclosed herein are illustrated in the accompanying drawings, in which the same reference numerals denote corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the accompanying drawings, wherein:

[0016] Figure 1A illustrates MBS delivery from 5G CN to 5G RAN and UE;

[0017] Figure 1B depicts an example protocol stack used for MBS in NR;

[0018] Figure 1C depicts an example of control information signaling used for MBS in NR;

[0019] Figure 1D depicts an example of control information signaling used for MBS in NR;

[0020] Figure 2 An overview of a wireless network for processing various services according to embodiments disclosed herein is shown;

[0021] Figure 3 Various hardware components of a UE according to embodiments disclosed herein are shown;

[0022] Figure 4 Various hardware components of a network entity according to embodiments disclosed herein are shown;

[0023] Figure 5 This is a flowchart illustrating a method for processing MBS services in a wireless network according to embodiments disclosed herein;

[0024] Figure 6 This is a flowchart illustrating a method for processing MBS services in a wireless network according to embodiments disclosed herein;

[0025] Figure 7 This is a flowchart illustrating a method for processing on-demand MBS SIB reception in a wireless network according to embodiments disclosed herein;

[0026] Figure 8 This is a flowchart illustrating a method for processing on-demand MBS SIB reception in a wireless network according to embodiments disclosed herein;

[0027] Figure 9a This is a flowchart illustrating a method for handling MBS BWP handover in a wireless network according to embodiments disclosed herein;

[0028] Figure 9b This is a flowchart illustrating a method for processing a switch from one of an MBS BWP and a CFR to an initial BWP in a wireless network according to embodiments disclosed herein;

[0029] Figure 10 This is a flowchart illustrating a method for processing a switch from one of an MBS BWP and a CFR to an initial BWP in a wireless network according to embodiments disclosed herein;

[0030] Figure 11 This is a flowchart illustrating a method for handling a switch from an initial BWP to one of an MBS BWP and a CFR in a wireless network according to embodiments disclosed herein;

[0031] Figure 12 This is a flowchart illustrating a method for handling a switch from an initial BWP to one of an MBS BWP and a CFR in a wireless network according to embodiments disclosed herein;

[0032] Figure 13 This is a flowchart illustrating a method for processing DRX configuration in a wireless network according to embodiments disclosed herein;

[0033] Figure 14 This is a flowchart illustrating a method for processing signaling of MBS interest indication in a wireless network according to embodiments disclosed herein;

[0034] Figure 15 This is a flowchart illustrating a method for processing broadcast MRB reservations in a wireless network according to embodiments disclosed herein; and

[0035] Figure 16 This is a flowchart illustrating a method for processing multicast reception in a wireless network according to embodiments disclosed herein.

[0036] Figure 17 This is a flowchart illustrating a method for processing multicast reception in a wireless network according to embodiments disclosed herein.

[0037] Figure 18 This is a flowchart illustrating a method for processing multicast reception in a wireless network according to embodiments disclosed herein. Detailed Implementation

[0038] The following description, provided with reference to the accompanying drawings, is intended to aid in a full understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. It includes various specific details to aid understanding, but these are to be considered exemplary only. Accordingly, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.

[0039] The terms and words used in the following description and claims are not limited to their documentary meaning, but are used solely by the inventors to ensure a clear and consistent understanding of this disclosure. Accordingly, it will be apparent to those skilled in the art that the following description of various embodiments of this disclosure is provided for illustrative purposes only and is not intended to limit the disclosure as defined by the appended claims and their equivalents.

[0040] It should be understood that the singular forms “a,” “an,” and “the” include plural indicators unless the context explicitly specifies otherwise. Thus, for example, referring to “component surface” includes referring to one or more such surfaces.

[0041] 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. In the accompanying drawings, identical or corresponding elements have the same reference numerals.

[0042] The advantages and features of this disclosure, as well as the ways in which they are implemented, will become apparent from the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in a variety of different forms. The following embodiments are provided only to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

[0043] Here it will 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 the processor of a general-purpose computer, 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 writing including instruction parts that implement the functions specified in one or more flowchart boxes. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide operations for implementing the functions specified in one or more flowchart boxes.

[0044] Furthermore, each box in the flowchart diagram may represent a module, code segment, or code section, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions mentioned in the boxes may appear out of order. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions involved.

[0045] As used herein, "unit" 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, "unit" does not always have a meaning limited to software or hardware. A "unit" can be configured to be stored in addressable storage media or to execute one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, programs, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a "unit" can be combined into a smaller number of elements or "units," or divided into a larger number of elements or "units." Furthermore, elements and "units" can be implemented as replicas of one or more central processing units (CPUs) within a device or secure multimedia card. Additionally, a "unit" in an embodiment may include one or more processors.

[0046] The operating principles of this disclosure will be described in detail below with reference to the accompanying drawings. In the following description of this disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where such descriptions might make the subject matter of this disclosure quite unclear. The terminology described below is defined in consideration of the functions in this disclosure and may vary depending on the user, user intent, or custom. Therefore, the definitions of terminology should be based on the entire contents of this specification.

[0047] In the following description, for convenience, terms used to identify access nodes, network entities, messages, interfaces between network entities, and various types of identification information are used illustratively. Therefore, this disclosure is not limited to the terms used below, and other terms relating to the subject matter with equivalent technical meaning may be used.

[0048] In the following description, for ease of description, the terms and names defined in the 3GPP Long Term Evolution (3GPP LTE) standard (the latest existing communication standard) will be used to describe this disclosure. However, this disclosure is not limited to these terms and names and can be applied in the same manner to systems conforming to other standards. Specifically, this disclosure can be applied to 3GPP New Radio (NR: 5G mobile communication standard) systems.

[0049] The embodiments 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 to facilitate understanding of how the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Therefore, these examples should not be construed as limiting the scope of the embodiments herein.

[0050] Generally, the New Radio Multicast Broadcast Service (NR MBS) includes the following services:

[0051] 1. Multicast service: For this purpose, the wireless network transmits public user data intended to be received only by a specific group of user equipment (UEs) that has joined the relevant multicast group.

[0052] 2. Broadcast service: For this purpose, the wireless network transmits public user data that can be received by all UEs interested in receiving the service.

[0053] A wireless network can provide MBS service in a limited portion of the wireless network, and the coverage area of ​​the MBS service can be a cell or larger.

[0054] The 5G core network (CN) (300) can deliver MBS user data to the radio access network (RAN) (200) (as shown in Figure 1A) using the following delivery methods:

[0055] 1. Independent delivery: For each individual UE (e.g., terminal) (100) receiving MBS service, the 5G CN (300) CN delivers a separate copy of the MBS user data packet to the RAN (200a) (i.e., via each UE's PDU session, which is similar to the case of unicast delivery).

[0056] 2. Shared delivery: The 5G CN (300) delivers a single copy of MBS user data to the RAN (200a) (i.e., via a shared PDU session / tunnel), where the RAN (200a) handles delivery to one or more UEs (100).

[0057] In the case of shared delivery by the 5G CN (300), the RAN (200a) delivers MBS data to the UE (100) using point-to-point delivery (PTP) or point-to-multipoint (PTM) delivery. Furthermore, at the UE (100), the following can be used to support reception via the MBS radio bearer (MRB):

[0058] 1. Single / public SDAP entity.

[0059] 2. Single / public PDCP entity.

[0060] 3. A single PTM RLC bearer, a single PTP RLC bearer, or a combination thereof, i.e., a UE (100) that is configured with both PTM and PTP RLC bearers (also known as PTM and PTP tributaries).

[0061] More specifically, UE(100) can be configured with:

[0062] 1. Only PTM RLC can carry it.

[0063] 2. PTP RLC only, using RLC unacknowledged mode (UM) or RLC acknowledged mode (AM).

[0064] 3. Split RLC bearers, i.e., PTM and PTP RLC bearers, both of which use RLC UM.

[0065] 4. Split the RLC bearer into two types: PTM and PTP RLC bearers, using RLC UM and RLC AM respectively.

[0066] Figure 1B depicts an example protocol stack (10b) for MBS in NR. In one embodiment, the terms MCCH (MBS Control Channel) and MTCH (MBS Traffic Channel) are defined for delivering broadcast services in Mode 2 and / or Idle / Inactive / Connected modes. MTCH (MBS Traffic Channel) is used for delivering multicast services in Mode 1 and / or Connected modes, and MCCH is not present.

[0067] For broadcast services, MCCH and MTCH support control signaling and services, respectively. MCCH configuration is provided by BCCH (i.e., System Information Block). Furthermore, MCCH carries configuration and service-related information for the MTCH channel. Broadcast MBS services can be supported in idle, inactive, or connected modes in the same manner. This also means that only PTM mode is feasible for broadcast services. Figures 1C and 1D depict examples of control information signaling for MBS in NR.

[0068] Referring to Figure 1C, UE (100) is in idle mode. At 102a, RAN (200a) sends BCCH / MCCH to UE (100). At 104a, UE (100) sends auxiliary information / feedback to RAN (200a). At 106a, a connection is established between UE (100) and RAN (200a). Referring to Figure 1D, UE (100) is in connected mode. At 102b, RAN (200a) sends BCCH / MCCH to UE (100). At 104b, RAN (200a) sends DCCH to UE (100).

[0069] 3GPP is currently studying and specifying the Rel-17 NR MBS work project. However, the following points remain unclear:

[0070] 1. How is MCCH configured?

[0071] 2. What are the configuration parameters for MCCH?

[0072] 3. How can single and / or multiple MCCHs work, and how are they scheduled?

[0073] 4. What information should the MCCH carry?

[0074] 5. How are idle and / or inactive mode operations performed for MBS service reception?

[0075] 6. How is MBS operation performed when the UE moves to or leaves the idle / inactive state?

[0076] Accordingly, embodiments of this document provide a method for processing MBS services in a wireless network. The method includes a UE receiving MCCH configuration and at least one parameter associated with the MCCH configuration in an SIB. Furthermore, the method includes the UE configuring an MCCH channel based on the MCCH configuration and the parameters associated with the MCCH configuration. Additionally, the method includes the UE receiving an MCCH information message through the MCCH channel. Furthermore, the method includes the UE configuring at least one MTCH based on the MCCH information message. Finally, the method includes the UE receiving MBS services through the MTCH.

[0077] The proposed method can be used in an efficient and effective manner for MCCH configuration and operation of NRMBS in fifth-generation radio access technology (RAT), as well as for handling idle / inactive and connected mode operations.

[0078] Now refer to the attached diagram (for more specific reference) Figures 2 to 18( ), wherein similar reference numerals in all the figures always denote corresponding features, illustrating exemplary embodiments.

[0079] Figure 2 An overview of a wireless network (400) for processing various services according to embodiments disclosed herein is shown. The wireless network (400) may be, for example, but not limited to, a 5G network, a 6G network, an ORAN network, etc. In one embodiment, the wireless network (400) includes a UE (100) and a network entity (200). The UE (e.g., a terminal) (100) may be, for example, but not limited to, a laptop computer, a desktop computer, a notebook computer, a smartphone, a foldable phone, a smart TV, a tablet computer, an immersive device, a television, a connected car, and an Internet of Things (IoT) device. The network entity (200) may also include, or be referred to by those skilled in the art, a base station, a base transceiver station, a radio base station, an access point, a radio transceiver, an eNB, a gNodeB (GNB), a 5G gNB, etc. Services may be, for example, but not limited to, MBS services, on-demand MBS SIB reception, broadcast MRB reservation, multicast reception, etc.

[0080] In one embodiment, a single and / or multiple MCCHs are configured for the NR MBS. The configuration and associated parameters are provided by a System Information Block (SIB). This SIB can be SIB1 and / or different SIBs and / or a new SIB defined for the NR MBS purpose (e.g., MBS SIB). The MBS SIB can be referred to as "sibx" or other names. When more than one MBS SIB exists, the second MBS SIB can be referred to as "sibx1," and so on. The transmission window for one or more MCCHs (e.g., consisting of MCCH modification periods and / or MCCH repetition periods) can be configured to be the same as or an integer multiple or approximation of one or more other MCCHs. Furthermore, these MCCHs can have the same or different radio frame offsets (e.g., MCCH-Offset).

[0081] In one embodiment, when more than one MCCH is configured, each MCCH uses a different RNTI (such as x-MCCH-RNTI), and therefore they correspond to different MAC PDUs (when they are scheduled in the same time slot).

[0082] Furthermore, there may be limitations on the number of RNTIs and / or physical channels and / or MAC PDUs and / or DCIs (downlink control information), which can be supported together for a given time slot. This will limit the number of MCCHs that can be supported simultaneously (when they are scheduled together in the same time slot).

[0083] In one embodiment, when more than one MCCH is configured, each MCCH uses the same RNTI (e.g., MCCH-RNTI), and therefore they can correspond to the same MAC PDU (when they are scheduled in the same time slot). Furthermore, the MCCHs are distinguished by different Logical Channel IDs (LC IDs), and the MCCHs (multiple) that the UE (100) is not interested in are discarded at the MAC layer. The MCCHs (multiple) that the UE (100) is interested in are processed by the UE (100) at the MAC layer and passed to the RRC layer.

[0084] In one embodiment, the same RNTI is used for both change notification and MCCH. This same RNTI is referred to as the MCCH-RNTI. Since change notification and MCCH (at least the start of MCCH) can occur in the same time slot, the DCI information used for MCCH can also carry change notification information.

[0085] In one embodiment, different RNTIs are used for change notifications and MCCH. When change notifications and MCCH (at least the start of MCCH) occur in the same time slot, separate DCIs exist for MCCH change notifications and MCCH.

[0086] In one embodiment, information about the allocation of multiple time slots for MCCH is provided in the first time slot via DCI (Downlink Control Information). That is, when MCCH is split and / or occupies more than one time slot, the DCI in the first time slot can provide allocation information for multiple time slots together.

[0087] In one embodiment, DCI (Downlink Control Information) and MCCH occupy more than one time slot, and this depends on the beamforming used (e.g., number of beams, number of MCCH segments).

[0088] In one embodiment, more than one MCCH can be time-multiplexed, that is, scheduled across different time slots (or time slots with different MCCH-Offsets), so that the UE can decode and receive MCCHs at different times and / or use the same RNTI for these MCCHs.

[0089] In one embodiment, more than one MCCH can be multiplexed in the frequency domain. Furthermore, they can occupy the same or different transmission bandwidths (e.g., MBS BWP, CFR, or CORESET). Additionally, the MBS BWP / CFR can be confined within, contain, or extend beyond the initial BWP. This makes it feasible to receive SIBs and paging simultaneously with MCCH reception. Furthermore, the UE (100) can keep its frequency monitoring window within the larger of the MBS BWP or the initial BWP, and include the other.

[0090] In one embodiment, the same beamforming method is used for (multiple) MCCHs and / or (multiple) MTCHs, regardless of whether the UE reception is in an idle, inactive, or connected state. (Multiple) MCCHs and / or (multiple) MTCHs in the MBS BWP or CFR can be quasi-co-located with the SSBs in the initial BWP. This means that the same beamforming and beam selection are as effective for (multiple) MCCHs and / or MTCHs as for SSBs. When the UE (100) has identified the optimal beam for the relevant SSB index, the UE (100) uses that optimal beam for (multiple) MCCHs and / or MTCH reception purposes.

[0091] In one embodiment, the MCCH reception operation is identical for the UE regardless of whether the UE is in an idle, inactive, or connected state. In another embodiment, the MCCH content can be provided to the connected-mode UE via dedicated signaling.

[0092] In one embodiment, signaling configured via SIB or MBS SIB signaling is provided for MCCH.

[0093] In one embodiment, for NR MBS, SIB, or MBS SIB, a list of "N" parameter sets is carried, where N is the number of MCCHs provided by the wireless network (400) on a cell or area (where 1 ≤ N). Each parameter set includes at least one of the following

[0094] MCCH-Offset: Indicates the radio frame offset used for MCCH scheduling.

[0095] MCCH-First-Sub-frame: Indicates the first subframe in which the MCCH is scheduled.

[0096] MCCH-First-Slot: Indicates the first slot in a subframe in which the MCCH is scheduled. The range of this parameter can be based on the subcarrier spacing (SCS) and / or BWP used for MCCH transmission.

[0097] MCCH-Duration: Indicates the duration (number of time slots) in which MCCH is scheduled. This parameter can be indicated as consecutive downlink time slots in which MCCH is transmitted by the wireless network (400).

[0098] MCCH-Repetition-Period: Indicates the interval used for MCCH within the modified period in which MCCH is repeated.

[0099] MCCH-Modification-Period: Indicates the time period or interval used to send updates for MCCH.

[0100] 1. MCCH-DRX-Scheduling-Info: DRX configuration for MCCH. If it does not exist, there is no DRX for MCCH.

[0101] 2. MCCH-RNTI: Indicates the RNTI used for a given MCCH.

[0102] 3. MCCH-MCS: Indicates the MCS (modulation and coding scheme) used for a given MCCH.

[0103] 4. MCCH-Area-Identity: Indicates the identity of the service area or transmission area used for a given MCCH. When the UE (100) moves across cells / areas, one or more MCCH-Area-Identities can be indicated as the same as the previous cell, and the UE (100) can assume the continuity of the relevant (multiple) MCCHs.

[0104] Furthermore, in one embodiment, MCCH-First-Sub-frame and MCCH-First-Slot can be combined into a single parameter, for example, expressed as a parameter given by (MCCH-First-Sub-frame * {number of slots / per sub-frame} + MCCH-First-Slot) or a parameter for slot offsets in a radio frame. Additionally, this can be the number of downlink slots or (downlink + flexible) slots, excluding uplink slots (if any) in between.

[0105] In another embodiment, regardless of the number of MCCHs "N" (where 1≤N), only one set of parameters is provided. In this case, all MCCHs share the same set of configuration parameters. Alternatively, the MCCHs are organized in a time-division multiplexing manner, with one MCCH followed by the next, and so on.

[0106] In another embodiment, as previously described, some MCCHs can be grouped together and provided with the same set of parameters; while other MCCHs or groups of MCCHs can be provided with different sets of parameters. For this purpose, a bitmap or field is provided together with a given set of parameters to indicate which MCCHs are addressed by that set of parameters.

[0107] In another embodiment, a subset of parameters can be shared for more than one MCCH; while for more than one MCCH, another subset of parameters may be different.

[0108] In one embodiment, the MBS SIB provides the maximum duration for MCCH. That is, the UE (100) can decode for MCCH scheduling up to this maximum duration (i.e., the number of slots). Alternatively, the maximum duration for MCCH is provided in the 3GPP specification.

[0109] In one embodiment, the MCCH duration is not provided by the SIB, and the MCCH duration is blindly decoded; that is, the UE (100) continues to decode the MCCH RNTI through consecutive downlink time slots, and when no MCCH RNTI is decoded, the UE (100) suspends the blind decoding of the MCCH.

[0110] In one embodiment, an example signaling message structure is provided for MCCH configuration (i.e., timing-related configuration) in MBS SIB (also known as SIBx), as shown in Table 1 below:

[0111] Table 1

[0112]

[0113] When there is a change to the MCCH content, the UE (100) is notified via a change notification (PDCCH or DCI) in the first subframe and / or first time slot of each repetition period for the relevant MCCH. The UE (100) can then obtain the updated relevant MCCH in the same first subframe and / or first time slot and / or specified subframe and / or time slot, wherein the relevant MCCH is scheduled according to the SIB or MBS SIB configuration.

[0114] When more than one MCCH is supported in a cell or area, a bitmap or field corresponding to a specific MCCH can be used. The order of the bits in the bitmap is related to the MCCH configuration order in the SIB or MBS SIB.

[0115] In one embodiment, an MCCH-Duration field is provided in the change notification (PDCCH or DCI), and accordingly, the UE (100) can decode the MCCH from the first subframe and / or the first time slot in which the change notification is received, up to MCCH-Duration time slots. This can also be the number of downlink time slots.

[0116] For UEs actively receiving MBS services, when changes to the MCCH duration need to be transmitted via paging or SIB signaling and the corresponding MCCH repetition / modification duration in the cell is very small, receiving MCCH duration information in the SIB or MBS SIB inherently limits MCCH scheduling. Furthermore, this configuration involves SIB acquisition and processing delays, which may lead to potential MCCH loss, resulting in MBS data loss. This is especially true for low-latency and critical services. Therefore, determining that RRC-level signaling is not suitable for conveying MCCH duration information to UEs actively receiving MBS services is not ideal. The ideal approach would be a power-efficient method based on lower-layer signaling with low latency, localized in the implementation, such as utilizing indications on the PDCCH (similar to MCCH change notifications).

[0117] In one embodiment, when the MCCH is scheduled across multiple time slots, the UE (100) can use the available bits of the MCCH change notification in the PDCCH to effectively communicate the MCCH duration. For example, three unused bits in the PDCCH are used to indicate the duration of the MCCH segmented therein, which can then be used by UEs actively receiving MBS services.

[0118] When the MCCH configurations (e.g., MCCH-Offset, etc.) of these MCCHs are different, MCCH-Duration can also be provided for more than one MCCH.

[0119] In one embodiment, the PDCCH or DCI provides the maximum duration for the MCCH. That is, the UE (100) can schedule the decoding of the MCCH up to this maximum duration (i.e., the number of time slots).

[0120] In one embodiment, the MCCH duration is not provided by the change notification (PDCCH / DCI), and the MCCH duration is blindly decoded; that is, the UE (100) continues to decode the MCCH RNTI through consecutive downlink time slots, and when no MCCH RNTI is decoded, the UE (100) suspends the blind decoding of the MCCH.

[0121] In one embodiment, MCCH decoding and reception are based on DRX scheduling for MCCH. The UE (100) continues to decode the MCCH according to the DRX activity time (on-duration and / or inactivity timer).

[0122] In one embodiment, the UE (100) applies the MBS SIB acquisition procedure in at least one of the following situations.

[0123] Cell selection (e.g., after power is supplied).

[0124] The neighborhood was re-selected.

[0125] Return from outside the coverage area.

[0126] After the reconfiguration is completed using synchronization.

[0127] After entering the network entity from another RAT.

[0128] After receiving an indication that system information or MBS SIB has been changed.

[0129] Whenever the UE (100) does not have a valid version of the stored SIB or MBS SIB, or a valid version of the requested MBS SIB.

[0130] When an MBS request is activated by a user or service layer.

[0131] When an MBS service / session start request is made by a user or service layer.

[0132] When the MCCH change instruction is notified and the UE (100) needs to know the duration for the MCCH.

[0133] In one embodiment, the UE (100) checks whether it has a stored version of the MBS SIB (e.g., SIBx and / or SIBx1) and whether it is valid (e.g., the cell or area range of the SIB is valid). If the condition is met, the UE (100) does not acquire or receive the MBS SIB. Otherwise, the UE acquires and receives the MBS SIB. Furthermore, the UE (100) may check the validity of the MCCH (e.g., the cell or area range of the MCCH is valid), and accordingly may acquire or not acquire the MCCH.

[0134] In one embodiment, on-demand system information for MBS is supported. To this end,

[0135] - If SIB1 includes si-SchedulingInfo containing si-RequestConfig

[0136] - The UE (100) triggers a lower layer to initiate a random access procedure on the normal uplink and / or supplementary uplink using multiple PRACH preambles and multiple PRACH resources in the si-RequestConfig corresponding to multiple SI messages, which are required by the UE (100) to receive MBS SIBs within the cell and whose si-BroadcastStatus is set to "not broadcast". When an acknowledgment for the SI request has been received from the lower layer, the UE (100) acquires the multiple SI messages for the MBSSIB request.

[0137] -If SIB1 does indeed include si-SchedulingInfo containing si-RequestConfig

[0138] -UE(100) initiates the transmission of the RRCSystemInfoRequest message;

[0139] - If an acknowledgment is received from a lower layer for the RRCSystemInfoRequest message, the UE (100) immediately acquires the requested (multiple) SI messages.

[0140] In one embodiment, if the UE (100) is in connected mode and has a valid storage version of the MBS SIB (e.g., SIBx and / or SIBx 1) required for the UE (100) to operate within the cell, then the UE uses the required storage version of the MBSSIB.

[0141] In one embodiment, if the UE (100) is in connected mode and its active BWP does not include or has not been configured with a common search space for the MBS SIB, and the UE (100) does not have a valid stored version of the MBS SIB (e.g., SIBx and / or SIBx1), then the UE (100) requests an on-demand MBS SIB. To this end,

[0142] 1> For SI messages(s) containing at least one required MBS SIB based on the mbsSI-SchedulingInfo in the stored SIB1:

[0143] 2> If onDemandSIB-Request is configured and timer Txxx is not running:

[0144] 3> Initiate the transmission of the DedicatedSIBRequest message;

[0145] 3> Start the timer value by setting the timer Txxx of onDemandSIB-RequestProhibitTimer;

[0146] In one embodiment, if the UE (100) is in connected mode and its active BWP includes or is configured with a common search space for the MBS SIB, and the UE (100) does not have a valid stored version of the MBS SIB (e.g., SIBx and / or SIBx1), then the UE (100) requests an on-demand MBS SIB. To this end,

[0147] 1> For SI messages(s) that contain at least one required MBS SIB based on the si-SchedulingInfo in the stored SIB1 and whose si-BroadcastStatus is set to "Broadcast":

[0148] 2> Retrieve (multiple) SI messages;

[0149] 2> For (multiple) SI messages that contain at least one required MBS SIB based on the si-SchedulingInfo in the stored SIB1 and whose si-BroadcastStatus is set to "not broadcast":

[0150] 3> If onDemandSIB-Request is configured and timer Txxx is not running:

[0151] 4> Initiate the transmission of the DedicatedSIBRequest message;

[0152] 4> Start the timer value by setting the timer Txxx of onDemandSIB-RequestProhibitTimer;

[0153] 4> Obtain the requested SI messages corresponding to the requested MBS SIBs.

[0154] In one embodiment, the UE (100) may include on-demand requests for SIBs and / or (multiple) posSIBs and / or (multiple) MBS SIBs (referred to as sibx and sibx1) within the same DedicatedSIBRequest message. To do this, the UE (100) sets the desired (multiple) MBS SIBs in the requestedSIB-List within the onDemandSIB-RequestList of the DedicatedSIBRequest message. As an example,

[0155]

[0156] In one embodiment, if the UE (100) is in connected mode and its active BWP does not include or is not configured with a common search space for the MCCH, and / or the UE does not have a valid stored version of the MCCH, then the UE (100) requests the on-demand MCCH. To this end,

[0157] 1> For SI messages(s) containing at least one required MBS SIB and / or having MCCH configuration based on the mbsSI-SchedulingInfo in the retrieved / stored SIB1:

[0158] 2> If onDemandMCCH-Request is configured and timer Txxx is not running:

[0159] 3> Initiate the transmission of the DedicatedMCCHRequest message;

[0160] 3> Start the timer value by setting the timer Txxx of onDemandMCCH-RequestProhibitTimer;

[0161] In addition, the UE (100) sets up a DedicatedMCCHRequest message for one or more MCCHs, as shown in the following example.

[0162] DedicatedMCCHRequest-IEs::=SEQUENCE{

[0163] onDemandMCCH-RequestList SEQUENCE{

[0164] requestedMCCH-List SEQUENCE(SIZE(1..maxOnDemandMCCH))OF MCCH-ReqInfoOPTIONAL,

[0165] }OPTIONAL,

[0166] lateNonCriticalExtension OCTET STRING OPTIONAL,

[0167] nonCriticalExtension SEQUENCE{}OPTIONAL

[0168] }

[0169] MCCH-ReqInfo::=ENUMERATED{mcch1,mcch2,mcch3,spare5,spare4,spare3,spare2,spare1}

[0170] In one embodiment, for MBS SIB (or related SI message) and / or MCCH acquisition, the timing of PDCCH monitoring is determined based on the searchSpaceOtherSystemInformation defined in the traditional NR specification or the newly defined searchSpaceMBSSystemInformation for NR MBS.

[0171] In one embodiment, MCCH transmissions (e.g., repeated and / or modified) from the network side are scheduled such that they are offset from the SIB or MBS SIB (e.g., repeated and / or modified) scheduling. This prevents potential conflicts between BCCH and MCCH. Furthermore, the offset can be controlled in such a way that once the UE (100) acquires the SIB or MBS SIB, there is minimal delay when acquiring the MCCH.

[0172] In one embodiment, if the UE (100) is in connected mode and its active BWP does not include or is not configured with a common search space for MBS SIB, and the UE (100) is broadcasting MBS service or is interested in receiving MBS service and / or has received an MCCH change instruction:

[0173] 1. If on-demand MBS SIB is supported and / or configured, the UE (100) obtains the on-demand MBS SIB message.

[0174] If on-demand MBS SIB is not configured or supported, the UE (100) initiates an MBS interest indication to the wireless network (400), and / or the UE (100) abandons broadcasting MBS services, and / or the UE utilizes the relevant MBS services from the network via PTP or unicast.

[0175] In one embodiment, if the UE (100) is in connected mode and its active BWP includes or is configured with a common search space for MCCH, and the UE (100) is broadcasting MBS service and / or receives an MCCH change indication, then the UE (100) acquires the MCCH message.

[0176] In one embodiment, if the UE (100) is in connected mode and its active BWP does not include or is not configured with a common search space for MCCH, and the UE (100) is broadcasting MBS service and / or has received an MCCH change indication:

[0177] 1. If on-demand MCCH is configured, the UE (100) obtains the on-demand MCCH message.

[0178] 2. If on-demand MCCH has not been configured, the UE (100) initiates an MBS interest indication to the network, and / or the UE (100) abandons broadcasting MBS services, and / or the UE (100) utilizes the relevant MBS services from the network via PTP or unicast.

[0179] In one embodiment, the UE (100) may notify the network of interest indications, thus ensuring delivery of broadcast services based on best possible effort. However, the network may not be bound by this signaling. Furthermore, it is noteworthy that MBS interest indication requirements are more critical and incentivized for multicast services (delivery mode 1) to enable the setup, maintenance, and pursuit of multicast services with network involvement. Therefore, from a triggering and reporting perspective, it appears important to merge MBS interest indications (i.e., common interest indication messages) for broadcast and multicast services in connected mode. Additionally, the same interest indication message may have separate parts / sets for broadcast and multicast services, along with associated parameters such as preferred BWP, priority, service list, frequency, preferred mode (e.g., RLC AM or UM, PTP or PTM, etc.). In other embodiments, a common set is used for both broadcast and multicast services, and the network may distinguish between broadcast and multicast services based on their identifiers (e.g., TMGI).

[0180] In another embodiment, the triggering and reporting of interest indications for broadcast and multicast services are performed separately.

[0181] In another embodiment, when the UE (100) has 0 MBS services of interest, an MBS interest indication is sent to the network entity. It is conceivable that 0 MBS services of interest are only for broadcast services and / or only for multicast services and / or for both broadcast and multicast services. Furthermore, an identifier or field is used in the interest indication message to indicate whether the interest indication includes broadcast and / or multicast services.

[0182] In one embodiment, when interest is completely lost at the UE, an example signaling structure is provided for an MBS interest indication message that includes 0 MBS services, as shown in Table 2 below:

[0183] Table 2

[0184]

[0185] In one embodiment, the UE (100) receives NR MBS (Change Notification and / or MCCH and / or MTCH) based on TDD-UL-DL-Config-common / TDD-UL-DL-Config-dedicated and / or SFI signaling and / or dynamic DCI based on UE state (idle or inactive or connected) to determine downlink slots or downlink symbols and / or flexible slots / symbols.

[0186] In one embodiment, the UE (100) acquires the MCCH when at least one of the following conditions is met:

[0187] 1. The UE (100) is powered on, and the cell it is camped on is broadcasting MBS SIB and / or SIB, including the MCCH configuration.

[0188] 2. During cell selection, the selected cell is broadcasting MBS SIB and / or SIB, including the MCCH configuration.

[0189] 3. During cell reselection, the cell being reselected is broadcasting MBS SIB and / or SIB, including those configured in the MCCH.

[0190] 4. During handover, the target cell is broadcasting MBS SIB and / or SIB, including the MCCH configuration.

[0191] 5. When MCCH changes (e.g., service starts, MCCH changes, service stops, etc.).

[0192] 6. When at least one NR MBS service is activated and / or deactivated.

[0193] 7. When at least one NR MBS service is suspended and / or resumed.

[0194] 8. When the UE (100) is already receiving NR MBS service (e.g., broadcast service), the UE acquires the MCCH at each modification period (e.g., at the beginning of each modification period). If the UE can receive the MCCH, the UE (100) may not receive the MCCH at other repetitions within the same modification period.

[0195] 9. During MBS activation by the user or service layer.

[0196] 10. When MBS services are changed by the user or service layer and mapped to different MCCHs.

[0197] 11. When the service that the UE is interested in changes.

[0198] 12. When receiving an MBS SIB in response to a DedicatedSIBRequest in connection mode.

[0199] 13. When MBSSIB is received in idle / inactive mode in response to random access according to si-RequestConfig.

[0200] 14. When receiving MBS SIB in response to RRCSystemInfoRequest in idle / inactive mode.

[0201] 15. When the active BWP in connected mode is changed and its new active BWP does not include and / or is not configured with a common search space for MCCH, and the UE (100) is broadcasting MBS service and / or has received an MCCH change indication.

[0202] 16. - When the active BWP in connected mode is changed and its new active BWP includes and / or is configured with a common search space for MCCH, and the UE (100) is broadcasting MBS service and / or has received an MCCH change indication.

[0203] MCCH configuration: In one embodiment, the configuration for MCCH can be provided by an SIB or an MBS SIB (e.g., SIBx). When an MBS-specific SIB exists / is used, scheduling information for the MBS SIB is provided in the SIB (e.g., SIB1).

[0204] In one embodiment, the configuration parameters include at least one of the following

[0205] 1. Configured MBS BWP (Bandwidth Part) or CFR (Common Frequency Resource). This includes frequency domain resources, such as the starting physical resource block (PRB), the number of PRBs, subcarrier spacing (SCS), etc.

[0206] 2. Search space (e.g., identifiers for search spaces such as searchspace#0, other public search spaces).

[0207] 3. Beamforming parameters (e.g., the number of SSBs transmitted, the number of PDCCH monitoring opportunities used for MCCH)

[0208] 4. Quasi-co-address information (e.g., quasi-co-address with SSB).

[0209] 5. Bandwidth used for MCCH (e.g., same as the initial BWP, same as CORESET#0, same as the configured MBS BWP or MBS CFR, same as the bandwidth used for MTCH, explicitly configured per MCCH or explicitly configured for all MCCHs).

[0210] 6. Subcarrier spacing (SCS) (e.g., it can be explicitly configured or can be the same as that used for the initial BWP).

[0211] 7. Cyclic prefix (CP) (e.g., it can be configured explicitly or can be the same as that used for the initial BWP).

[0212] 8. Modulation and coding scheme (MCS) (e.g., it can be based on MCCH or be common to all MCCH).

[0213] 9. HARQ configuration (e.g., no HARQ mode or no feedback HARQ retransmission mode or the same as used for MTCH).

[0214] Furthermore, for example, when the configured MBS BWP or CFR is smaller than or limited to the initial BWP, the UE (100) can receive MCCH change notifications (PDCCH / DCI) and / or MCCH in the initial BWP and / or the configured MBS BWP or CFR. Configuration parameters in the SIB or MBS SIB also include HARQ (e.g., no HARQ mode or no feedback HARQ retransmission mode), CORESET, and beamforming-related configurations for the MCCH. Furthermore, the MCCH can further carry configuration parameters including HARQ (e.g., no HARQ mode or no feedback HARQ retransmission mode) for MBS service or MTCH and / or the MBS BWP or CFR configured for the MBS.

[0215] In one embodiment, an example signaling message structure is provided for the MCCH configuration (i.e., BWP / CFR related configuration) in the MBS SIB (also known as SIBx), as shown in Table 3 below:

[0216] Table 3

[0217]

[0218]

[0219] MCCH content:In one embodiment, MCCH signaling can be performed more efficiently by utilizing a total list of DRX scheduling configurations at the beginning of the MCCH message, or by broadcasting system information, and by configuring an index of this list for each service. In effect, it provides a mapping between DRX scheduling configurations and PTM services. The embodiments described herein can have more than one index for services; that is, in addition to one-to-one mappings, one-to-many or many-to-one mappings are also possible in this method. Furthermore, multiple services with a common DRX scheduling configuration can be grouped together, which facilitates UE (100) operation and reduces signaling message size.

[0220] In one embodiment, DRX scheduling configuration information is provided as a list of DRX schedules, where each schedule has one or more associated PTM services. This specifies the possibility that multiple multicast / broadcast services can share a common DRX scheduling configuration. Furthermore, UEs capable of receiving more than one multicast / broadcast service simultaneously can also efficiently receive these services together, thereby saving power. It is possible that network entities can schedule certain services that are decoupled from different DRX scheduling configurations to enable UEs to receive these services, even if the UE (100)'s ability to receive more services simultaneously is limited.

[0221] In one embodiment, an exhaustive predefined list is provided in the specification, and this list does not need to be sent. This would include all possible combinations of DRX scheduling parameters, i.e., different values ​​of DRX timers organized in a table, with the index of the table entry referring to a specific combination of these DRX timers. It is also feasible to define multiple subsets of the list, considering that different deployments may use subsets of the list instead of the complete exhaustive list.

[0222] In one embodiment, an example signaling message structure is provided for the MCCH content (i.e., the DRX and PTM service configuration mapping) in the MCCH message, as shown in Table 4 below:

[0223] Table 4

[0224]

[0225] To avoid frequent MCCH readings, in the embodiments described herein, an additional bit indicating "SC-MCCH change" is provided in the PDCCH notification. This bit differs from the traditional PDCCH notification indicating "start of new service" in LTE MBMS. In practice, using the proposed method, a UE (100) actively receiving one or more PTM services does not need to read the MCCH for every modification period. The new bit indicating "MCCH change" is used in the PDCCH notification to pre-notify the UE (100) on the MCCH in the next modification period. This bit indicates a change to the MCCH when set; otherwise, the MCCH remains unchanged. More specifically, a 2-bit bitmap is carried as the MCCH change notification in DCI format 4_0 scrambled by MCCH-RNTI. The MSB in this bitmap, when set to 1, indicates the start of an MBS session. The LSB in this bitmap, when set to 1, indicates a modification of MCCH information other than the start of an MBS session, and it can indicate a modification of the configuration of at least one ongoing MBS session, the termination of at least one MBS session, or a change in at least one neighboring cell information.

[0226] In one embodiment, power saving is the objective due to frequent monitoring of MCCH change notifications. MCCH changes can be indicated via DCI on the first subframe used for the duration of active service. Thus, the UE (100) does not need to monitor MCCH change notifications in specific subframes and interrupt its power-saving cycle.

[0227] In one embodiment, power saving is the objective due to frequent monitoring of MCCH change notifications. MCCH changes can be indicated via MAC-CE on the first subframe used for the duration of active service. Thus, the UE (100) does not need to monitor MCCH change notifications in specific subframes and interrupt its power-saving cycle.

[0228] In one embodiment, energy saving is a primary objective due to frequent monitoring of MCCH change notifications. Any changes to the MCCH can be indicated at specified or configured time intervals via paging messages or group paging messages used for active services.

[0229] In one embodiment, the MCCH can be empty, meaning it does not contain any MTCH configuration information in the message. This implies that zero MTCH is a valid scenario. A potential use case might be for networks that have suspended and / or disabled all their MTCH services and / or have not yet started transporting their MTCH services.

[0230] In one embodiment, MBS service suspension / deactivation and / or resumption / activation information is transmitted in the MCCH message. For this purpose, each MBS service to be suspended and / or paused is indicated by a field indicating suspension. Alternatively, the absence (presence) of MBS service information from the MCCH message can indicate the suspension (resumption) of the relevant MBS service.

[0231] Idle / Inactive Mode Operation: In one embodiment, the UE (100) switches from the configured MBS BWP (bandwidth portion) or CFR (common frequency resource) to the initial BWP (e.g., when the configured MBS BWP / CFR is greater than the initial BWP).

[0232] 1. When UE (100) stops / abandons MBS service reception, for example, when the last active MBS service that UE (100) is receiving is stopped.

[0233] 2. The required MBS service is abandoned by the wireless network (400) (e.g., suspended / disabled or stopped).

[0234] 3. The neighborhood / area has been changed, causing MBS service to be no longer supported.

[0235] 4. MCCH instructs the removal or termination of MBS services.

[0236] 5. - SIB or MBS SIB provides MBS BWP / CFR configurations that have been changed to be less than or equal to the initial BWP.

[0237] In one embodiment, for example, when the configured MBS BWP / CFR is greater than the initial BWP, the UE (100) switches from the initial BWP to the configured MBS BWP (bandwidth portion) or CFR (common frequency resource).

[0238] 1. When UE (100) starts receiving MBS service.

[0239] 2. The required MBS service is started / restored / activated by the wireless network (400).

[0240] 3. The neighborhood / area has been changed, making MBS service supported or available.

[0241] 4. MCCH change notification and / or MCCH indication of the commencement of the required service.

[0242] 5. SIB or MBS SIB provides MBS BWP / CFR that has been modified to a configuration larger than the initial BWP.

[0243] 6. Service continuity during RRC state changes to and from RRC_CONNECTED. MBS broadcast reception can continue on the configured MBS CFR. (This overcomes some issues, such as the potential for intermittent interruptions due to BWP / CFR changes when performing RACH on the initial BWP. Similarly, during an RRC state change from RRC_CONNECTED, if the UE begins using the initial BWP, there may be interruptions and / or loss of MBS.)

[0244] In one embodiment, when the configured MBS BWP / CFR is smaller than the initial BWP and / or the configured MBS BWP / CFR is limited to the initial BWP, the UE (100) continues to receive MCCH change notifications, MCCH, and MBS services (e.g., MTCH) from the initial BWP.

[0245] In one embodiment, the UE (100) receives the MCCH and / or MTCH from one or more configured MBS BWPs or CFRs. To support simultaneous SIB and / or paging reception, these MBS BWPs or CFRs may be confined within and / or include the initial BWP. In some cases, these MBS BWPs or CFRs may also partially or completely overlap. In the case of complete overlap, the UE (100) may monitor the largest MBS BWP or CFR. Otherwise, the UE (100) may switch from one MBS BWP / CFR to another (e.g., in the time or frequency domain) or may utilize multiple RF capabilities. The UE (100) may indicate its RF capabilities to network entities in a UE capability information message, UE auxiliary information message, or interest indication message.

[0246] In one embodiment, when a network entity releases the UE (100) from connected mode (e.g., due to congestion), the UE (100) continues to receive multicast services in idle or inactive mode. To this end, as one approach, in delivery mode 1, multicast services are received in idle and / or inactive modes (i.e., maintaining the same connected mode BWP and multicast PDCCH and / or PDSCH channels, and skipping certain UE-specific operations for HARQ / CSI feedback and configuration). This also means that dedicated signaling mechanisms in connected mode can be implemented by utilizing SIB / MCCH / paging-based signaling. As another approach, in delivery mode 2, multicast services are received in idle and / or inactive modes (i.e., the delivery mode for multicast services is switched from DM1 to DM2, and the DM2 mode mechanism for receiving multicast services is applied in idle / inactive modes). This also means that SIB, MCCH, and paging methods are used to receive configurations for multicast services in idle / inactive modes.

[0247] In one embodiment, when a network entity releases the UE (100) from connected mode (e.g., due to congestion), the UE (100) continues to receive multicast services in idle or inactive mode. At least one of the following actions may be performed:

[0248] 1. Release PTP configuration for multicast service. PTP-related RLC entities are released and MAC configuration is released. MAC entities can also be reset.

[0249] 2. The PTM configuration (or a subset thereof related to idle / inactive mode) can be preserved and continued in idle or inactive mode. For example, for idle / inactive mode, the HARQ feedback configuration may not be preserved; however, the UE (100) can utilize HARQ retransmission.

[0250] 3. The network entity provides the UE (100) with a new configuration for the idle or inactive mode for MBS services via dedicated signaling (e.g., via RRC reconfiguration and / or RRC release and / or RRC release with suspend configuration).

[0251] 4. The UE (100) receives a new configuration for the idle and / or inactive mode for MBS service via broadcast signaling (e.g., SIB, MCCH).

[0252] 5. The BWP configuration for MBS is changed from a dedicated BWP to the initial BWP or the configured MBS BWP or CFR. Alternatively, the UE (100) can continue to use the dedicated BWP for multicast service reception without actually being in a connected state.

[0253] 6. Obtain the BWP, search space, HARQ and DRX configuration for MCCH from the MBS SIB, and / or provide the pre-configuration to the UE (100) by the network entity via dedicated signaling.

[0254] 7. For idle / inactive mode reception, the DRX configuration used for MBS service may or may not be changed. That is, the UE (100) may continue to use the same PTM DRX configuration previously used in the connected state.

[0255] 8. A paging configuration suitable for idle / inactive modes is provided and applied to the UE (100).

[0256] In one embodiment, triggering the UE (100) to receive multicast services in idle mode or inactive mode includes at least one of the following:

[0257] 1. When a network entity (200) releases a UE (100) from connected mode using an indication to continue MBS multicast service in idle or inactive mode (e.g., due to congestion), an indication may be provided to the UE (100) via RRC signaling, such as an RRC reconfiguration message and / or MAC signaling (e.g., MAC CE and / or RRC release and / or RRC release or NAS signaling with suspend configuration).

[0258] 2. When the MCCH or paging or group paging in idle or inactive mode indicates the availability and / or activation of multicast service, but the UE (100) cannot switch to connected mode (e.g., due to congestion).

[0259] In one embodiment, when the UE (100) transitions to connected mode (e.g., to start a new unicast service, alleviate congestion conditions, or meet signal strength conditions), the UE (100) continues to receive multicast services in connected mode. Instructions to continue MBS multicast services in connected mode can be provided to the UE (100) via SIB, MCCH, paging, or group paging. Alternatively, the UE (100) may decide independently to return to connected mode. To do so, the UE (100) initiates an RRC connection request and / or RRC connection restoration based on idle or inactive conditions, respectively. The UE (100) may also indicate the reason for connection establishment and / or restoration (i.e., continuation of multicast services). Furthermore, high access priority can be assigned to such UEs to ensure they can establish or restore connections. At least one of the following actions can be performed when transitioning to connected mode:

[0260] 1. PTM configuration received in idle / inactive mode is released for multicast service. The PTM-related RLC entity and MAC configuration are released. The MAC entity can also be reset. Alternatively, the same configuration continues in connected mode (i.e., the PTM configuration used in idle / inactive mode continues for multicast service; the PTM-related RLC entity and MAC configuration continue; the MAC entity is not reset).

[0261] 2. The BWP, search space, HARQ, and DRX configurations obtained from the MBS SIB for MCCH are also released for multicast services. (Assuming the UE (100) is not broadcasting MBS services). If the UE (100) uses the same configuration in idle / inactive mode as it does in connected mode, the UE (100) does not need to release the configuration and can continue transitioning to connected mode.

[0262] 3. The network entity provides the UE (100) with a new configuration for multicast MBS service via dedicated signaling.

[0263] 4. The BWP configuration used for MBS is changed from the initial BWP or the configured MBS BWP or CFR to a dedicated BWP. If the BWP configuration used in idle / inactive mode is a BWP configuration of a dedicated BWP for connected mode, the UE (100) continues to use the same dedicated BWP when switching to connected mode.

[0264] In one embodiment, at least one of SIB / MBS SIB, MCCH, paging, and PDCCH is used to notify the UE (100) receiving multicast services in idle and / or inactive modes of configuration (BWP, DRX, HARQ, etc.) and / or service-related changes (stop, suspend, deactivate, etc.) of the multicast service. These can be explicit configuration / service parameters and / or change indications. Based on this, the UE (100) can modify the configuration or service parameters and / or switch to a connected mode (e.g., to utilize only the new configuration or switch to a connected mode for multicast service reception).

[0265] In one embodiment, as an example, the MCCH carries an explicit configuration and / or a configuration / service change indication for receiving multicast services in idle / inactive mode. Based on the explicit configuration, the UE (100) applies the new configuration and continues to receive multicast services in idle / inactive mode. Based on the change indication, the UE (100) switches to connected mode to utilize the new configuration. As another example, the paging carries a configuration / service change indication for multicast services. Based on the change indication, the UE (100) switches to connected mode to utilize the new configuration. Furthermore, the UE (100) may return to idle / inactive mode or may be switched back to idle / inactive mode by a network entity.

[0266] In one embodiment, when a network entity releases the UE (100) from connected mode, or when the data-InactivityTimer or bwp-InactivityTimer expires, and the UE (100) continues to receive broadcast services in idle or inactive mode, it may perform at least one of the following actions.

[0267] 1. Retain the PTM configuration received from MCCH.

[0268] 2. Retain the PTM RLC entity and release all other RLC entities.

[0269] 3. For PTM, retain the MAC entity and MAC configuration, and release all other MAC configurations / timers.

[0270] 4. Retain the initial BWP and / or configured MBS BWP / CFR. Release any other BWPs (e.g., dedicated BWPs).

[0271] 5. Retain the HARQ buffers / processes and configurations used for PTM. Reset all other HARQ buffers / processes and release the HARQ configurations.

[0272] 6. Retain the DRX configuration used for PTM. Release all other DRX configurations (e.g., PTP DRX or unicast DRX) except for the idle mode paging / DRX configuration.

[0273] 7. Retain the MBS radio bearer for broadcast services.

[0274] In one embodiment, when the UE (100) transitions from idle or inactive mode, the UE (100) continues to receive broadcast services in connected mode by sending an RRC connection request or RRC recovery request to the network entity.

[0275] 1. Retain the PTM configuration received from MCCH.

[0276] 2. Retain the PTM RLC entity.

[0277] 3. For PTM, retain the MAC entity and MAC configuration.

[0278] 4. Retain the initial BWP and / or the configured MBS BWP / CFR.

[0279] 5. Retain the HARQ buffer / procedure and configuration used for PTM. Retain the DRX configuration used for PTM.

[0280] 6. Retain the MBS radio bearer for broadcast services.

[0281] 7. Assuming that random access resources and operations are not interrupted or restricted from receiving broadcast services, the UE (100) performs random access while receiving broadcast services.

[0282] 8. If the active BWP in connected mode does not support MBS BWP / CFR for broadcast services, then UE (100) terminates the broadcast service.

[0283] In one embodiment, when the UE (100) is receiving MBS services and the Data-InactivityTimer or MBS-Data-InactivityTimer expires in connected mode, the UE (100) is switched to idle and / or inactive mode.

[0284] In one embodiment, the UE (100) is switched to idle and / or inactive mode only when the multicast service is disabled / suspended or terminated by the network entity (200) or abandoned / stopped by the UE (100), when the Data-InactivityTimer or MBS-Data-InactivityTimer expires in connected mode while the UE (100) is receiving the MBS multicast service.

[0285] In one embodiment, when receiving MBS service, the UE (100) maintains a Data-InactivityTimer or an MBS-Data-InactivityTimer in idle and / or inactive mode. The timer is started or restarted when an MBS service packet is received and / or the MBS service is activated. When no MBS service packet is received and the timer expires, the UE (100) abandons receiving MBS service in idle and / or inactive mode. In one example, the MCCH modification period may be quite long (e.g., around 5ms or 10ms), and notifying the UE (100) via the MCCH that service suspension / deactivation requires more time. Furthermore, the UE (100) may perform one or more of the following actions:

[0286] 1. The UE (100) switches from the MBS BWP or CFR to the initial BWP (e.g., when this is the last MBS service and / or other MBS services can be received within or on the initial BWP).

[0287] 2. The UE (100) sends an MBS interest indication and attempts to move to the RRC connection state.

[0288] 3. The UE (100) prioritizes mobility (cell reselection from cell) in order to receive MBS service.

[0289] 4. The UE (100) notifies the user of the service unavailability / suspended / disabled.

[0290] In one embodiment, broadcast and multicast services can be received by the UE (100) together (e.g., in connected mode, and in idle / inactive mode when broadcast and low QoS multicast services are received together). Furthermore, the Logical Channel Identifier (LC ID) for broadcast services configured via MCCH and the LC ID for multicast services configured via dedicated signaling (PTM) use different / separate LC ID spaces. In another embodiment, the LC ID space can be common for both broadcast services configured via MCCH and multicast services configured via dedicated signaling (PTM); however, network entities ensure that there are no conflicts or overlaps in use (e.g., at least in a given BWP and / or cell and / or PLMN). However, PTP multicast services in connected mode can use the same LC ID space as the DRB.

[0291] In another embodiment, when there is a PTP HARQ retransmission for the initial PTM transmission, LC ID mapping information is provided so that the retransmitted PDU is processed (e.g., soft-combined, decoded) and appropriately routed to the relevant PTM RLC entity.

[0292] Figure 3 Various hardware components of a UE (100) according to embodiments disclosed herein are illustrated. In one embodiment, the UE (100) includes a processor (110), a communicator (120), a memory (130), an MBS service controller (140), an on-demand MBS SIB receive controller (150), a broadcast MRB reservation controller (160), and a multicast receive controller (170). The processor (110) is coupled to the communicator (120), the memory (130), the MBS service controller (140), the on-demand MBS SIB receive controller (150), the broadcast MRB reservation controller (160), and the multicast receive controller (170).

[0293] In one embodiment, the MBS service controller (140) is configured to receive MCCH configuration and at least one parameter associated with the MCCH configuration in the SIB. The MCCH configuration includes at least one PDCCH addressed to the MCCH-RNTI, providing at least one of a time-domain allocation and a frequency-domain allocation for receiving a PDSCH channel carrying MCCH information messages. The at least one parameter may be, for example, but not limited to, MCCH offset, MCCH first timeslot, MCCH duration, MCCH repetition period, MCCH modification period, resource configuration parameters for the MCCH, configured MBS BWP, CFR, search space, bandwidth for the MCCH, and bandwidth for the MTCH.

[0294] The MBS SIB acquisition procedure receives the MCCH configuration and at least one parameter associated with the MCCH configuration in the SIB. The MBS SIB acquisition procedure is applied in at least one of the following situations: the UE (100) is powered on and the cell in which the UE (100) is camped is broadcasting an MBS SIB including the MCCH configuration; the cell selected during cell selection is broadcasting an MBS SIB including the MCCH configuration; the cell reselected during cell reselection is broadcasting an MBS SIB including the MCCH configuration; the target cell is broadcasting an MBS SIB including the MCCH configuration during handover; and the UE (100) is already receiving NR MBS service. The MBS SIB acquisition procedure is applied during at least one of the following periods: MCCH change indication, NR MBS service activation, NR MBS service recovery, MBS activation by the user or service layer, MBS service change by the user or service layer, service change of interest to the UE (100), receiving an MBS SIB in response to a dedicated SIB request in connected mode, receiving an MBS SIB in response to random access according to si-RequestConfig in at least one of idle mode and inactive mode, and receiving an MBS SIB in response to an RRC system information request in at least one of idle mode and inactive mode.

[0295] Based on the MCCH configuration and the parameters associated with the MCCH configuration, the MBS service controller (140) configures the MCCH channel and receives MCCH information messages through the MCCH channel. Based on the MCCH information messages, the MBS service controller (140) configures at least one MTCH and receives MBS services through the MTCH.

[0296] In one embodiment, the MBS service controller (140) is configured to receive MCCH change notification information and the MCCH using the MCCH-RNTI. The MBS service controller (140) is configured to acquire the MCCH in response to determining that a network entity (200) has indicated MCCH change notification information. Alternatively, the MBS service controller (140) is configured to use a stored MCCH in response to determining that a network entity (200) has not indicated MCCH change notification information. The MCCH change notification information is carried by a first DCI bit and a second DCI bit, wherein the first DCI bit indicates the start of a new MBS session, and the second DCI bit indicates at least one of an MBS session configuration change, an MBS session termination, and a neighboring cell information change. If the MCCH change notification information and the MCCH appear in the same time slot, wherein the same time slot includes a first time slot for the MCCH duration, the DCI of the PDCCH for the MCCH addressed by the MCCH-RNTI carries the change notification information in its DCI bit.

[0297] In one embodiment, the MBS service controller (140) is configured to receive SIB1 and determine whether SIB1 includes Si-Scheduling information containing si-RequestConfig for the MBS SIB. When the UE (100) does not have a stored version of the MBS SIB or the UE (100) has an invalid stored version of the MBS SIB, the UE (100) receives the on-demand MBS SIB. Upon receiving an acknowledgment for the SI request from a lower layer, the UE (100) acquires the SI message requesting the MBS SIB. Upon receiving an acknowledgment for the RRCSystemInfoRequest message from a lower layer, the UE (100) immediately acquires the requested SI message. The MBS service controller (140) is configured to, in response to determining that SIB1 includes Si-Scheduling information containing a si-RequestConfig for the MBS SIB, trigger a lower layer to initiate a random access procedure on the normal uplink or supplementary uplink using at least one of the PRACH preamble and PRACH resources in the si-RequestConfig corresponding to the SI message, which is required by the UE to receive the MBS SIB within the cell and whose si-BroadcastStatus is set to "not broadcast". Alternatively, the MBS service controller (140) is configured to, in response to determining that SIB1 does not include Si-Scheduling information containing a si-RequestConfig for the MBS SIB, initiate the transmission of an RRCSystemInfoRequest message.

[0298] In one embodiment, the MBS service controller (140) is configured to detect a handover event for switching from one of the configured MBS BWP and CFR to the initial BWP. The handover event corresponds to at least one of the following: the UE (100) stops receiving MBS service; the network entity (200) relinquishes the desired MBS service; a cell change occurs so that the MBS service is no longer supported; an RRC state change occurs; the MCCH indicates the removal or cessation of the MBS service; and the SIB or MCCH provides a configured MBS BWP or CFR that has been changed to be less than or equal to the initial BWP. Based on the handover event, the MBS service controller (140) is configured to switch from one of the configured MBS BWP and CFR to the initial BWP.

[0299] In one embodiment, the MBS service controller (140) is configured to determine whether the RRC state changes from an RRC connected state to at least one of an RRC inactive state and an RRC idle state. Furthermore, the MBS service controller (140) is configured to determine whether the UE (100) has already received an MBS broadcast in the RRC connected state. In response to determining that the UE (100) has not yet received an MBS broadcast in the RRC connected state, the MBS service controller (140) is configured to switch the UE (100) to the initial BWP in at least one of the RRC inactive state and the RRC idle state. In response to determining that the UE (100) has already received an MBS broadcast in the RRC connected state, the MBS service controller (140) is configured to determine whether one of the MBS BWP and CFR used for broadcast reception is greater than the initial BWP.

[0300] Furthermore, in response to determining that one of the MBS BWP and CFR used for broadcast reception is greater than the initial BWP, the UE (100) continues MBS broadcast reception on one of the configured MBS BWP and MBS CFR in at least one of the RRC idle state and RRC inactive state. Alternatively, in response to determining that one of the MBS BWP and CFR used for broadcast reception is not greater than the initial BWP, the UE (100) switches to the initial BWP, and the UE (100) continues MBS broadcast reception in the initial BWP in either the RRC idle state or the RRC inactive state.

[0301] The MBS service controller (140) is configured to determine whether the RRC state changes from at least one of the RRC inactive state and the RRC idle state to the RRC connected state. Furthermore, the MBS service controller (140) is configured to determine whether the UE (100) has already received an MBS broadcast in at least one of the RRC inactive state and the RRC idle state. In response to determining that the UE (100) has not yet received an MBS broadcast in at least one of the RRC inactive state and the RRC idle state, the MBS service controller (140) is configured to switch the UE (100) to the RRC connected state and monitor it according to the dedicated unicast BWP. In response to determining that the UE (100) has already received an MBS broadcast in at least one of the RRC inactive state and the RRC idle state, the MBS service controller (140) is configured to determine whether one of the MBS BWP and CFR used for broadcast reception is greater than the initial BWP.

[0302] Furthermore, the MBS service controller (140) is configured to perform a RA procedure on the initial BWP, wherein in response to determining that one of the MBS BWP and CFR used for broadcast reception is greater than the initial BWP, the UE (100) continues MBS broadcast reception on one of the configured MBS BWP and MBS CFR. Alternatively, the UE (100) performs the RA procedure on the initial BWP, and the UE (100) continues MBS broadcast reception in the initial BWP, wherein in response to determining that either the MBS BWP or CFR used for broadcast reception is not greater than the initial BWP, the UE (100) monitors the BWP and CFR or the initial BWP.

[0303] The MBS service controller (140) is configured to detect handover events for switching from the initial BWP to one of the configured MBS BWP and CFR. The handover events correspond to: UE (100) initiating MBS service reception; desired MBS service initiated by network entity (200); desired MBS service restored by network entity (200); desired MBS service activated by network entity (200); cell change to make MBS service supported or available; RRC state change; MCCH change notification indicating desired service initiation; MCCH indicating desired service initiation; and SIB or MCCH providing a configured MBS BWP or CFR that is changed to be greater than the initial BWP. Based on the handover event, the MBS service controller (140) is configured to switch from the initial BWP to one of the configured MBS BWP and CFR.

[0304] The MBS service controller (140) is configured to receive at least one MBS service in RRC connected state and report an MBS interest indication message to the network entity (200), wherein the MBS interest indication message includes at least one of an MBS service list, a frequency list, and priority MBS services. Furthermore, the MBS service controller (140) is configured to stop receiving all MBS services from the network entity (200) and send an MBS interest indication message with an empty message to indicate a complete loss of interest in MBS, and thereafter, the UE (100) stops reporting MBS interest indications.

[0305] The MBS service controller (140) is configured to receive broadcast signaling messages and determine that the configured MBS BWP or CFR is one of the following: the same as CORESET index 0, the same as the initial BWP, or greater than the initial BWP. Based on this determination, the MBS service controller (140) is configured to configure the start and length of the PRB for one of the MBS BWP or CFR when the MBS BWP or CFR used for broadcast service reception is greater than the initial BWP. The broadcast signaling message may be an MBS SIB (e.g., SIBx). Furthermore, the MBS service controller (140) is configured to receive MBS services from the configured MBS BWP or CFR.

[0306] In one embodiment, the on-demand MBS SIB receive controller (150) is configured to determine whether the UE (100) is in connected mode and has a valid stored version of the MBS SIB and the UE (100) needs to operate within the cell; or, the UE (100) is in connected mode and the active BWP does not include or has not configured a common search space and the UE (100) does not have a valid stored version of the MBS SIB; or, the UE (100) is in connected mode and the active BWP includes or has configured a common search space and the UE (100) does not have a valid stored version of the MBS SIB and the cell is broadcasting; or, the UE (100) is in connected mode and the active BWP includes or has configured a common search space and the UE (100) does not have a valid stored version of the MBS SIB and the cell is not broadcasting. The on-demand MBS SIB receive controller (150) is configured to utilize the stored version(s) of the MBS SIB in response to determining that the UE (100) is in connected mode and has a valid stored version of the MBS SIB.

[0307] Alternatively, the on-demand MBS SIB receiving controller (150) is configured to request an on-demand MBS SIB if the UE (100) is in connected mode and the active BWP associated with the UE (100) does not include or has not been configured with a common search space for the MBS SIB, and the UE (100) does not have a valid stored version of the MBS SIB. Alternatively, the on-demand MBS SIB receiving controller (150) is configured to request an on-demand MBS SIB and obtain an SI containing at least one desired MBS SIB if the UE (100) is in connected mode and the active BWP associated with the UE (100) includes or has been configured with a common search space for the MBS SIB, and the UE (100) does not have a valid stored version of the MBS SIB.

[0308] In one embodiment, the broadcast MRB reservation controller (160) is configured to receive at least one MBS broadcast service when the UE (100) is in one of the following states: RRC connected state, RRC idle state, and RRC inactive state. Furthermore, the broadcast MRB reservation controller (160) is configured to continue receiving the MBS broadcast service and to reserve the broadcast MRB when the UE (100) receives one of the following from the network entity (200): RRC release and RRC release with suspend configuration, or when the dataInactivityTimer expires. Additionally, the broadcast MRB reservation controller (160) is configured to continue receiving the MBS broadcast service and to reserve the broadcast MRB when the UE (100) receives one of the following from the network entity (200): RRC establishment and RRC recovery. The broadcast MRB reservation controller (160) is configured to perform at least one action based on continuing to receive the MBS broadcast service and reserving the broadcast MRB. At least one action includes: retaining the PTM configuration received from the MCCH, retaining the PTM RLC entity used for broadcasting the MRB, releasing all other RLC entities, retaining the MAC entity and MAC configuration used for broadcasting the MRB, releasing all other MAC configurations, retaining at least one of the initial BWP, the configured MBS BWP, and the configured MBS CFR, releasing the other BWPs, retaining the DRX configuration and timer of the PTM used for MBS broadcasting, and retaining the HARQ buffer and configuration of the PTM used for MBS broadcasting.

[0309] In one embodiment, the multicast reception controller (170) is configured to continue receiving at least one multicast service in an RRC inactive state when the network entity (200) releases the UE (100) from the RRC connected state, and to perform actions based on continuing to receive at least one multicast service in the RRC inactive state. At least one action includes: releasing the PTP configuration for multicast services, releasing the PTP-related RLC entity and MAC configuration, partially or completely resetting the MAC entity, retaining the PTM configuration for multicast in the inactive state, providing the UE with the inactive state configuration for multicast services by the network entity via at least one of RRC reconfiguration and RRC release with a pending configuration through broadcast signaling and / or dedicated signaling, changing the BWP configuration for multicast from a dedicated BWP to one of an initial BWP, a configured MBS BWP, and a CFR, or continuing to utilize the dedicated BWP for multicast service reception without actually being in a connected state, and managing the DRX configuration for multicast service reception in the inactive state.

[0310] In another embodiment, the multicast receive controller (170) is configured to receive at least one MBS multicast service when the UE (100) is in an RRC connected state. Furthermore, the multicast receive controller (170) is configured to receive one of a combination of a reconfiguration message and an RRC release message with a suspended configuration from the network entity (200). Furthermore, the multicast receive controller (170) is configured to switch the RRC connected state to an RRC inactive state based on receiving one of the combination of the reconfiguration message and the RRC release message with a suspended configuration from the network entity (200). Furthermore, the multicast receive controller (170) is configured to continue receiving at least one MBS multicast service in the RRC inactive state via one of a first delivery mode and a second delivery mode. Furthermore, the multicast receive controller (170) is configured to receive dedicated signaling for receiving at least one MBS multicast service in RRC connected mode when at least one related configuration change for the RRC inactive state is determined via at least one of the SIB, MCCH, and paging messages. Alternatively, the multicast receiver controller (170) is configured to receive notification signaling and configuration signaling in the RRC inactive state via at least one of SIB, MCCH and paging messages.

[0311] In one embodiment, upon detecting congestion at network entity (200), at least one of a reconfiguration message and an RRC release message with a pending configuration is received, wherein the first delivery mode maintains the same connection mode BWP and multicast PDCCH and PDSCH channels, and at least one UE-specific operation for at least one of Hybrid Automatic Repeat Request (HARQ) and Channel State Information (CSI) feedback and configuration is skipped, and multicast service is received.

[0312] In one embodiment, upon detection of congestion at network entity (200), at least one of a reconfiguration message and an RRC release message with a suspended configuration is received, wherein a second delivery mode releases the connection mode BWP and the multicast PDCCH and PDSCH channels, and at least one UE-specific operation is performed for at least one of Hybrid Automatic Repeat Request (HARQ) and Channel State Information (CSI) feedback and configuration, wherein the UE (100) is configured according to a new configuration for the RRC inactive state and receives multicast services.

[0313] In one embodiment, the multicast receive controller (170) is configured to continue receiving at least one MBS multicast service in an RRC inactive state and to send an RRC recovery request to the network entity (200). Furthermore, the multicast receive controller (170) is configured to perform at least one action in response to sending the RRC recovery request to the network entity (200). Additionally, the multicast receive controller (170) is configured to continue receiving at least one MBS multicast service in an RRC connected state. In one embodiment, the at least one action includes: continuing the PTM configuration used for multicast services in the RRC inactive state, continuing the PTM-related RLC entity and MAC configuration, not resetting the MAC entity, receiving the configuration for multicast MBS services from the network entity via dedicated signaling, and enabling the UE (100) to continue using the same dedicated BWP while transitioning to the RRC connected state.

[0314] In another embodiment, at least one action includes: releasing the PTM configuration used for multicast services in the RRC inactive state, releasing the PTM-related RLC entity, releasing the MAC configuration, resetting the MAC entity, releasing at least one of the BWP, search space, HARQ, and DRX configurations obtained from the SIB or MCCH for multicast services, receiving the configuration for multicast services via dedicated signaling, changing the BWP configuration for MBS from the initial BWP or configured MBS BWP or CFR to a dedicated BWP if the BWP configuration is being used in the inactive mode, and continuing to use the same dedicated BWP while transitioning to the RRC connected state.

[0315] The UE (100) continues to receive at least one MBS multicast service in the RRC connected state, wherein the UE (100) switches from the RRC inactive state to the RRC connected state in at least one of the following situations: the UE (100) receives an instruction to receive the MBS multicast service in the RRC connected state through at least one of the SIB, MCCH and paging messages in the RRC inactive state, and the UE (100) decides autonomously to return to the RRC connected state.

[0316] The MBS service controller (140) is physically implemented by analog or digital circuitry (such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc.) and may optionally be driven by firmware.

[0317] The on-demand MBS SIB receiver controller (150) is physically implemented by analog or digital circuitry (such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc.) and may optionally be driven by firmware.

[0318] The broadcast MRB reservation controller (160) is physically implemented by analog or digital circuitry (such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc.) and may optionally be driven by firmware.

[0319] The multicast receiver controller (170) is physically implemented by analog or digital circuitry (such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, etc.) and may optionally be driven by firmware.

[0320] Furthermore, the processor (110) is configured to execute instructions stored in the memory (130) and perform various processes. The communicator (120) is configured for internal communication between internal hardware components and for communication with external devices via one or more networks. The memory (130) also stores instructions to be executed by the processor (110). The 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, the memory (130) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagating signal. However, the term "non-transitory" should not be construed as meaning that the memory (130) is immovable. In some examples, a non-transitory storage medium may store data that can change over time (e.g., in random access memory (RAM) or a cache).

[0321] Furthermore, at least one of the multiple modules / controllers can be implemented using an AI model of a data-driven controller. The data-driven controller can be an ML-based controller or an AI-based controller. Functionality associated with the AI ​​model can be executed via non-volatile memory, volatile memory, and a processor (110). The processor (110) can include one or more processors. Here, the one or more processors can be general-purpose processors (such as a central processing unit (CPU), application processor (AP), etc.), graphics-specific processing units (such as a graphics processing unit (GPU), vision processing unit (VPU)), and / or AI-specific processors (such as a neural processing unit (NPU)).

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

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

[0324] 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.

[0325] A learning algorithm is a method that uses multiple training datasets to train a predetermined target device (e.g., a robot) to enable, allow, or control the target device to make a determination or prediction. Examples of learning algorithms include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0326] although Figure 3 Various hardware components of the UE (100) are illustrated, but it should be understood that other embodiments are not limited thereto. In other embodiments, the 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 the UE (100).

[0327] Figure 4Various hardware components of a network entity (200) according to embodiments disclosed herein are illustrated. In one embodiment, the network entity (200) includes a processor (210), a communicator (220), a memory (230), and an MBS service controller (240). The processor (210) is coupled to the communicator (220), the memory (230), and the MBS service controller (240). The MBS service controller is configured to send MCCH signaling messages to the UE (100). The MCCH signaling messages include a DRX scheduling configuration list and an MBS service configuration list. Furthermore, the MBS service controller is configured to map DRX scheduling configurations to PTM service configurations based on an index of the DRX scheduling configuration provided in the PTM service configuration in the MCCH signaling message.

[0328] The MBS service controller (240) is physically implemented by analog or digital circuitry (such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc.) and may optionally be driven by firmware.

[0329] Furthermore, the processor (210) is configured to execute instructions stored in the memory (230) and perform various processes. The communicator (220) is configured for internal communication between internal hardware components and for communication with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) 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, the memory (230) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagating signal. However, the term "non-transitory" should not be construed as meaning that the memory (230) is immovable. In some examples, a non-transitory storage medium may store data that can change over time (e.g., in random access memory (RAM) or a cache).

[0330] Furthermore, at least one of the multiple modules / controllers can be implemented using an AI model of a data-driven controller. The data-driven controller can be an ML-based controller or an AI-based controller. Functionality associated with the AI ​​model can be executed via non-volatile memory, volatile memory, and a processor (210). The processor (210) can include one or more processors. Here, the one or more processors can be general-purpose processors (such as a central processing unit (CPU), application processor (AP), etc.), graphics-specific processing units (such as a graphics processing unit (GPU), vision processing unit (VPU)), and / or AI-specific processors (such as a neural processing unit (NPU)).

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

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

[0333] 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.

[0334] A learning algorithm is a method that uses multiple training datasets to train a predetermined target device (e.g., a robot) to enable, allow, or control the target device to make a determination or prediction. Examples of learning algorithms include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0335] although Figure 6 Various hardware components of the UE (100) are illustrated, but it should be understood that other embodiments are not limited thereto. In other embodiments, the 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 the UE (100).

[0336] Figure 5 and Figure 6These are flowcharts (500 and 600) illustrating a method for processing MBS services in a wireless network (400) according to embodiments disclosed herein.

[0337] refer to Figure 5 Operations (502-510) are performed by the terminal. According to one aspect of this disclosure, operations (502-510) are processed by the MBS service controller (140). At 502, the method includes receiving MCCH configuration and at least one parameter associated with the MCCH configuration in the SIB. At 504, the method includes configuring the MCCH channel based on the MCCH configuration and the parameter associated with the MCCH configuration. At 506, the method includes receiving an MCCH information message through the MCCH channel. At 508, the method includes configuring the MTCH based on the MCCH information message. At 510, the method includes receiving MBS services through the MTCH.

[0338] refer to Figure 6 Operations (602-606) are performed by the terminal. According to one aspect of this disclosure, operations (602-606) are processed by the MBS service controller (140). At 602, the method includes using MCCH-RNTI to receive MCCH change notification information and MCCH. At 604, the method includes acquiring MCCH in response to determining that network entity (200) has indicated MCCH change notification information. At 606, the method includes using the stored MCCH in response to determining that network entity (200) has not indicated MCCH change notification information.

[0339] Figure 7 This is a flowchart (700) illustrating a method for processing on-demand MBS SIB reception in a wireless network (400) according to embodiments disclosed herein.

[0340] refer to Figure 7Operations (702-708) are performed by the terminal. According to one aspect of this disclosure, operations (702-708) are processed by the MBS service controller (140). At 702, the method includes receiving SIB1. At 704, the method includes determining whether SIB1 includes Si-Scheduling information containing si-RequestConfig for MBS SIB. At 706, the method includes initiating the transmission of an RRCSystemInfoRequest message in response to determining that SIB1 does not include Si-Scheduling information containing si-RequestConfig for MBS SIB. At 708, the method includes triggering a lower layer to initiate a random access procedure on a normal uplink or supplementary uplink using at least one of a PRACH preamble and PRACH resources in the si-RequestConfig corresponding to the SI message, in response to determining that SIB1 includes Si-Scheduling information containing si-RequestConfig for MBS SIB, and its si-BroadcastStatus is set to "not broadcast".

[0341] Figure 8 This is a flowchart (800) illustrating a method for processing on-demand MBS SIB reception in a wireless network (400) according to embodiments disclosed herein.

[0342] refer to Figure 8 Operations (802-808) are performed by the terminal. According to one aspect of this disclosure, operations (802-808) are processed by the MBS service controller (140). At 802, the method includes determining whether the UE (100) is in connected mode and has a valid stored version of the MBS SIB and the UE (100) needs to operate within the cell, or, the UE (100) is in connected mode and the active BWP does not include or is not configured with a common search space and the UE (100) does not have a valid stored version of the MBS SIB, or, the UE (100) is in connected mode and the active BWP includes or is configured with a common search space and the UE (100) does not have a valid stored version of the MBS SIB and the cell is broadcasting, or, the UE (100) is in connected mode and the active BWP includes or is configured with a common search space and the UE (100) does not have a valid stored version of the MBS SIB and the cell is not broadcasting.

[0343] At 804, the method includes utilizing the stored version of the MBS SIB in response to determining that the UE (100) is in connected mode and has a valid stored version of the MBS SIB. At 806, the method includes requesting an on-demand MBS SIB if the UE (100) is in connected mode and the active BWP associated with the UE (100) does not include or has not been configured with a common search space for the MBS SIB and the UE (100) does not have a valid stored version of the MBS SIB. At 808, the method includes requesting an on-demand MBS SIB and obtaining an SI containing at least one desired MBS SIB if the UE (100) is in connected mode and the active BWP associated with the UE (100) includes or has been configured with a common search space for the MBS SIB and the UE (100) does not have a valid stored version of the MBS SIB.

[0344] Figure 9a This is a flowchart (900a) illustrating a method for handling MBS BWP handover in a wireless network (400) according to embodiments disclosed herein. Operations (902a-906a) are performed by a terminal. According to one aspect of this disclosure, operations (902a-906a) are processed by an MBS service controller (140). In 902a, the method includes receiving a broadcast signaling message and determining that the configured MBS BWP or CFR is one of the following: identical to CORESET index 0, identical to or greater than the initial BWP, wherein the broadcast signaling message is an MBS System Information Block (SIB). In 904a, the method includes, based on this determination, configuring the start and length of a Physical Resource Block (PRB) for one of the MBS BWP or CFR when the MBS BWP or CFR for broadcast service reception is greater than the initial BWP. In 906a, the method includes receiving MBS service from the configured MBS BWP or CFR.

[0345] Figure 9b and Figure 10 The flowcharts (900b and 1000) illustrate a method for processing a switch from one of MBSBWP and CFR to an initial BWP in a wireless network (400) according to embodiments disclosed herein.

[0346] refer to Figure 9b Operations (902b and 904b) are performed by the terminal. According to one aspect of this disclosure, operations (902b and 904b) are processed by the MBS service controller (140). In 902b, the method includes detecting a handover event for switching from one of the configured MBS BWP and CFR to an initial BWP. In 904b, the method includes switching from one of the configured MBS BWP and CFR to the initial BWP based on the handover event.

[0347] refer to Figure 10 Operations (1002-1012) are performed by the terminal. According to one aspect of this disclosure, operations (1002-1012) are processed by the MBS service controller (140). At 1002, the method includes determining that the RRC state has changed from an RRC connected state to at least one of an RRC inactive state and an RRC idle state. At 1004, the method includes determining whether the UE (100) has already received an MBS broadcast in the RRC connected state. If the UE (100) has not yet received an MBS broadcast in the RRC connected state, then at 1006, the method includes switching the UE (100) to the initial BWP in at least one of the RRC inactive state and the RRC idle state. If the UE (100) has already received an MBS broadcast in the RRC connected state, then at 1008, the method includes determining whether the MBS BWP or CFR used for broadcast reception is greater than the initial BWP. If the MBS BWP or CFR used for broadcast reception is greater than the initial BWP, then at 1010, the UE (100) continues MBS broadcast reception on the configured MBS BWP or MBS CFR in at least one of the RRC idle state and RRC inactive state. If the MBS BWP or CFR used for broadcast reception is not greater than the initial BWP, then at 1012, the UE (100) switches to the initial BWP, and the UE (100) continues MBS broadcast reception in the initial BWP in either the RRC idle state or the RRC inactive state.

[0348] Figure 11 and Figure 12 The flowcharts (1100 and 1200) illustrate a method for processing a switch from an initial BWP to one of an MBS BWP and a CFR in a wireless network (400) according to embodiments disclosed herein.

[0349] refer to Figure 11Operations (1102-1112) are performed by the terminal. According to one aspect of this disclosure, operations (1102-1112) are processed by the MBS service controller (140). At 1102, the method includes determining that the RRC state changes from at least one of an RRC inactive state and an RRC idle state to an RRC connected state. At 1104, the method includes determining whether the UE (100) has already received an MBS broadcast in at least one of an RRC inactive state and an RRC idle state. If the UE has not yet received an MBS broadcast in at least one of an RRC inactive state and an RRC idle state, then at 1106, the method includes switching the UE (100) to the RRC connected state and monitoring according to a dedicated unicast BWP. If the UE (100) has already received an MBS broadcast in at least one of an RRC inactive state and an RRC idle state, then at 1108, the method includes determining whether the MBS BWP or CFR used for broadcast reception is greater than the initial BWP. If the MBS BWP or CFR used for broadcast reception is greater than the initial BWP, then at 1110, the method includes performing a RA procedure on the initial BWP, wherein the UE (100) continues MBS broadcast reception on the configured MBS BWP or MBSCFR. If the MBS BWP or CFR used for broadcast reception is not greater than the initial BWP, then at 1112, the method includes performing a RA procedure on the initial BWP, and the UE (100) continues MBS broadcast reception in the initial BWP. The UE (100) monitors the BWP / CFR or the initial BWP.

[0350] refer to Figure 12 Operations (1202-1204) are performed by the terminal. According to one aspect of this disclosure, operations (1202 and 1204) are processed by the MBS service controller (140). In 1202, the method includes detecting a handover event for switching from an initial BWP to one of a configured MBS BWP and CFR. In 1204, the method includes switching from the initial BWP to one of the configured MBS BWP and CFR based on the handover event.

[0351] Figure 13 This is a flowchart (1300) illustrating a method for processing DRX configuration in a wireless network (400) according to embodiments disclosed herein. Operations (1302 and 1304) are performed by a network entity (e.g., a base station). According to one aspect of this disclosure, operations (1302 and 1304) are processed by an MBS service controller (240).

[0352] At 1302, the method includes sending an MCCH signaling message to the UE (100). The MCCH signaling message includes at least one of a DRX scheduling configuration list and an MBS service configuration list. At 1304, the method includes mapping the DRX scheduling configuration to the PTM service configuration based on an index of the DRX scheduling configuration provided in the PTM service configuration in the MCCH signaling message.

[0353] Figure 14 This is a flowchart (1400) illustrating a method for processing signaling of MBS interest indication in a wireless network (400) according to an embodiment disclosed herein.

[0354] refer to Figure 14 Operations (1402-1408) are performed by the terminal. According to one aspect of this disclosure, operations (1402-1408) are processed by the MBS service controller (140). In 1402, the method includes receiving at least one MBS service in an RRC connection state. In 1404, the method includes reporting an MBS interest indication message to a network entity (200). The MBS interest indication message includes a list of MBS services, a list of frequencies, and priority MBS services. In 1406, the method includes stopping receiving all MBS services from the network entity (200). In 1408, the method includes sending an MBS interest indication message with an empty message to indicate a complete loss of interest in MBS, and thereafter, the UE (100) stops reporting MBS interest indications.

[0355] Figure 15 This is a flowchart (1500) illustrating a method for processing broadcast MRB reservations in a wireless network (400) according to embodiments disclosed herein.

[0356] refer to Figure 15Operations (1502-1508) are performed by the terminal. According to one aspect of this disclosure, operations (1502-1508) are processed by the MBS service controller (140). In 1502, the method includes receiving an MBS broadcast service when the UE (100) is in one of an RRC connected state, an RRC idle state, and an RRC inactive state. In 1504, the method includes continuing to receive the MBS broadcast service and retaining the broadcast MRB when the UE (100) receives one of an RRC release and an RRC release with a suspend configuration from the network entity (200) or when the dataInactivityTimer timer expires. In 1506, the method includes continuing to receive the MBS broadcast service and retaining the broadcast MRB when the UE (100) receives one of an RRC establishment and an RRC recovery from the network entity (200). In 1508, the method includes performing at least one action based on continuing to receive the MBS broadcast service and retaining the broadcast MRB. This action can be, for example, but not limited to: retaining the PTM configuration received from the MCCH, retaining the PTM RLC entity used for broadcasting the MRB, releasing all other RLC entities, retaining the MAC entity and MAC configuration used for broadcasting the MRB, releasing all other MAC configurations, retaining the initial BWP, the configured MBS BWP and the configured MBS CFR, releasing other BWPs, retaining the DRX configuration and timer of the PTM used for MBS broadcasting, and retaining the HARQ buffer and configuration of the PTM used for MBS broadcasting.

[0357] Figures 16 to 18 This is a flowchart (1600-1800) illustrating a method for processing multicast reception in a wireless network (400) according to embodiments disclosed herein.

[0358] refer to Figure 16Operations (1602 and 1604) are performed by the terminal. According to one aspect of this disclosure, operations (1602 and 1604) are processed by the MBS service controller (140). In 1602, the method includes continuing to receive at least one multicast service in an RRC inactive state when the network entity (200) releases the UE (100) from the RRC connected state. In 1604, the method includes performing at least one action based on continuing to receive at least one multicast service in an RRC inactive state, wherein the at least one action includes: releasing the PTP configuration for the multicast service, releasing the PTP-related RLC entity and MAC configuration, partially or completely resetting the MAC entity, retaining the PTM configuration for multicast in the inactive state, providing the UE with the inactive state configuration for multicast service by at least one of RRC reconfiguration and RRC release with a pending configuration via broadcast signaling and / or dedicated signaling by a network entity, changing the BWP configuration for multicast from a dedicated BWP to one of an initial BWP, a configured MBS BWP, and a CFR, or continuing to utilize the dedicated BWP for multicast service reception without actually being in a connected state, and managing the DRX configuration for multicast service reception in the inactive state.

[0359] refer to Figure 17 Operations (1702-171) are performed by the terminal. According to one aspect of this disclosure, operations (1702-1712) are processed by the MBS service controller (140). In 1702, the method includes receiving an MBS multicast service when the UE (100) is in an RRC connected state. In 1704, the method includes receiving one of a combination of a reconfiguration message and an RRC release message with a suspend configuration from a network entity (200). In 1706, the method includes switching the RRC connected state to an RRC inactive state based on receiving one of the combination of a reconfiguration message and an RRC release message with a suspend configuration from the network entity (200).

[0360] In 1708, the method includes continuing to receive at least one MBS multicast service in an RRC inactive state via one of a first delivery mode and a second delivery mode. In 1710, the method includes receiving dedicated signaling for receiving at least one MBS multicast service configuration in an RRC connected mode after determining at least one relevant configuration change for the RRC inactive state via at least one of a SIB, MCCH, and paging message. In 1712, the method includes receiving notification signaling and configuration signaling in an RRC inactive state via at least one of a SIB, MCCH, and paging message.

[0361] refer to Figure 18Operations (1802-1808) are performed by the terminal. According to one aspect of this disclosure, operations (1802-1808) are processed by the MBS service controller (140). At 1802, the method includes receiving at least one MBS multicast service while in an RRC inactive state. At 1804, the method includes sending an RRC recovery request to the network entity (200). In 1806, the method includes performing at least one action in response to sending an RRC recovery request to a network entity (200), wherein the at least one action includes: continuing the PTM configuration for multicast services used in the RRC inactive state, continuing the PTM-related RLC entity and MAC configuration, not resetting the MAC entity, receiving the configuration for multicast MBS services from the network entity via dedicated signaling, and enabling the UE to continue using the same dedicated BWP while transitioning to the RRC connected state, wherein the at least one action includes: releasing the PTM configuration for multicast services used in the RRC inactive state, releasing the PTM-related RLC entity, releasing the MAC configuration, resetting the MAC entity, releasing at least one of the BWP, search space, HARQ, and DRX configurations obtained from the SIB or MCCH for multicast services, receiving the configuration for multicast services via dedicated signaling, changing the BWP configuration for MBS from the initial BWP or configured MBS BWP or CFR to a dedicated BWP if the BWP configuration is used in idle mode or inactive mode, and continuing to use the same dedicated BWP while transitioning to the RRC connected state. In 1808, the method included continuing to receive at least one MBS multicast service while in an RRC connection state.

[0362] The various actions, behaviors, boxes, steps, etc. in the flowcharts (500 to 1800) can be executed in the presented order, in different orders, or simultaneously. Furthermore, in some embodiments, some actions, behaviors, boxes, steps, etc., can be omitted, added, modified, or skipped without departing from the scope of the invention.

[0363] 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 elements. These elements can be at least one of a hardware device or a combination of a hardware device and a software module.

[0364] The primary objective of the embodiments herein is to disclose an efficient and effective method and UE for MCCH configuration and operation of NR Multicast Service (MBS) for New Radio (NR) in fifth-generation radio access technology (RAT) and for handling idle / inactive mode operation.

[0365] Another objective of the embodiments herein is to disclose how to configure the MCCH, what the MCCH should be structured, what the MCCH can carry, and, in general, specifying operational details for idle and / or inactive modes.

[0366] Another objective of the embodiments described herein is to disclose on-demand MBS SIB reception.

[0367] Another objective of the embodiments described herein is to disclose the grouping of DRX configurations in MCCH and the mapping of index-based DRX configurations to MBS service configurations.

[0368] Another objective of the embodiments herein is to disclose MCCH change notification scheduling performed by MCCH PDCCH DCI and the same RNTI used for MCCH.

[0369] Another objective of embodiments of this document is to disclose MCCH change notification via a new DCI bit for “MCCH changes – in addition to the start of a new session”.

[0370] Another objective of the embodiments described herein is to publicly issue signaling notifications with interest indications of zero interested services.

[0371] Another objective of the embodiments described herein is to disclose the switching across MBS BWP / CFR and the initial BWP.

[0372] Another objective of the embodiments described herein is to disclose the retention of broadcast MRB during RRC state transitions.

[0373] Accordingly, embodiments of this document provide a method for processing MBS services in a wireless network. The method includes a UE receiving an MBS control channel (MCCH) configuration and at least one parameter associated with the MCCH configuration in a System Information Block (SIB). Furthermore, the method includes the UE configuring an MCCH channel based on the MCCH configuration and the parameters associated with the MCCH configuration. Additionally, the method includes the UE receiving an MCCH information message through the MCCH channel. Furthermore, the method includes the UE configuring at least one MBS traffic channel (MTCH) based on the MCCH information message. Finally, the method includes the UE receiving MBS services through the MTCH.

[0374] In one embodiment, the SIB includes at least one of SIB1, an existing SIB, and a dedicated SIB for new radio (NR) MBS purposes, wherein the dedicated SIB includes the MBS SIB.

[0375] In one embodiment, the MCCH includes at least one physical downlink control channel (PDCCH) addressing to the MCCH radio network temporary identifier (RNTI) that provides at least one of a time-domain allocation and a frequency-domain allocation for receiving a physical downlink shared channel (PDSCH) channel carrying MCCH information messages.

[0376] In one embodiment, at least one parameter includes at least one of MCCH offset, MCCH first time slot, MCCH duration, MCCH repetition period, MCCH modification period, resource configuration parameters for MCCH, configured MBS bandwidth portion (BWP), common frequency resource (CFR), search space, bandwidth for MCCH, and bandwidth for MTCH.

[0377] In one embodiment, the MCCH offset indicates the radio frame offset used for MCCH scheduling, wherein the MCCH first slot indicates the first slot in the subframe starting from the position where the MCCH is scheduled, wherein the MCCH duration indicates the duration, in units of slots, during which the MCCH is scheduled, wherein the MCCH repetition period indicates the interval used for the MCCH within the modification period during which the MCCH is repeated, wherein the MCCH modification period indicates the interval used for the MCCH to send updates for the MCCH, wherein, provided that the start and length of the Physical Resource Block (PRB) for the MCCH and MTCH are provided, the BWP or CFR for the configuration of the MCCH and MTCH is one of the following: the same as CORESET index 0, the same as the initial BWP, or greater than the initial BWP.

[0378] In one embodiment, the UE receiving MCCH configuration and at least one parameter associated with MCCH configuration in the SIB includes: the UE applying an MBS SIB acquisition procedure, and after applying the MBS SIB acquisition procedure, the UE receiving MCCH configuration and at least one parameter associated with MCCH configuration in the SIB.

[0379] In one embodiment, the MBS SIB acquisition procedure is applied in at least one of the following situations: the UE is powered on and the cell where the UE is camped is broadcasting an MBS SIB including the MCCH configuration; the cell selected during cell selection is broadcasting an MBS SIB including the MCCH configuration; the cell reselected during cell reselection is broadcasting an MBS SIB including the MCCH configuration; the target cell is broadcasting an MBS SIB including the MCCH configuration during handover; and the UE is already receiving NR MBS service. The MBS SIB acquisition procedure is also applied during at least one of the following periods: MCCH change indication, NR MBS service activation, NR MBS service recovery, MBS activation by the user or service layer, MBS service change by the user or service layer, service change of interest to the UE, receiving an MBS SIB in response to a dedicated SIB request in connected mode, receiving an MBS SIB in response to random access according to si-RequestConfig in at least one of idle mode and inactive mode, and receiving an MBS SIB in response to a Radio Resource Control (RRC) System Information Request in at least one of idle mode and inactive mode.

[0380] Accordingly, embodiments of this document provide a method for processing MBS services in a wireless network. The method includes a UE receiving MCCH change notification information and an MCCH using MCCH-RNTI. Furthermore, the method includes the UE performing one of the following: acquiring the MCCH in response to determining that a network entity has indicated MCCH change notification information; and using a stored MCCH in response to determining that a network entity has not indicated MCCH change notification information.

[0381] In one embodiment, the MCCH change notification information is carried by a first downlink control information (DCI) bit and a second DCI bit. When the first DCI bit is set to 1, it indicates the start of a new MBS session, and when the second DCI bit is set to 1, it indicates at least one of an MBS session configuration change, an MBS session termination, and a neighboring cell information change. When the first DCI bit is set to 0, it indicates that no new MBS session has started, and when the second DCI bit is set to 0, it indicates that there has been no MBS session configuration change, no MBS session termination, and no neighboring cell information change.

[0382] In one embodiment, if the MCCH change notification information and the MCCH appear in the same time slot, the DCI of the Physical Downlink Control Channel (PDCCH) for the MCCH carries the change notification information in the DCI bit; wherein the same time slot includes a first time slot for the MCCH duration.

[0383] Accordingly, embodiments of this document provide a method for processing on-demand MBS SIB reception in a wireless network. The method includes a UE receiving SIB1 and the UE determining whether SIB1 includes Si-Scheduling information containing a si-RequestConfig for the MBS SIB. In one embodiment, the method includes, in response to determining that SIB1 includes Si-Scheduling information containing a si-RequestConfig for the MBS SIB, triggering a lower layer to initiate a random access procedure on a normal uplink or supplemental uplink using at least one of a Physical Random Access Channel (PRACH) preamble and PRACH resources in the si-RequestConfig corresponding to a System Information (SI) message, the SI message being required by the UE to receive the MBS SIB within the cell and whose si-BroadcastStatus is set to "not broadcast". In another embodiment, the method includes, in response to determining that SIB1 does not include Si-Scheduling information containing a si-RequestConfig for the MBS SIB, initiating the transmission of an RRCSystemInfoRequest message.

[0384] In one embodiment, when the UE does not have a stored version of the MBS SIB or the UE has an invalid stored version of the MBSSIB, the UE receives the on-demand MBS SIB.

[0385] In one embodiment, when an acknowledgment for an SI request is received from a lower layer, the UE obtains an SI (System Information) message for the MBS SIB request.

[0386] In one embodiment, when an acknowledgment is received from a lower layer for an RRCSystemInfoRequest message, the UE immediately obtains the requested SI message.

[0387] Accordingly, embodiments of this document provide a method for processing on-demand MBS SIB reception in a wireless network. The method includes the UE determining whether it is in connected mode and has a valid stored version of the MBS SIB and the UE needs to operate within the cell; or, the UE is in connected mode and the active BWP does not include or has not configured a common search space and the UE does not have a valid stored version of the MBS SIB; or, the UE is in connected mode and the active BWP includes or has configured a common search space and the UE does not have a valid stored version of the MBS SIB and the cell is broadcasting; or, the UE is in connected mode and the active BWP includes or has configured a common search space, and the UE does not have a valid stored version of the MBS SIB and the cell is not broadcasting. In one embodiment, the method includes the UE utilizing the stored version(s) of the MBS SIB in response to determining that the UE is in connected mode and has a valid stored version of the MBS SIB. In another embodiment, the method includes: if the UE is in connected mode and the active BWP associated with the UE does not include or has not configured a common search space for the MBS SIB and the UE does not have a valid stored version of the MBS SIB, then the UE requests an on-demand MBS SIB. In another embodiment, the method includes: if the UE is in connected mode and the active BWP associated with the UE includes or is configured with a common search space for MBS SIBs and the UE does not have a valid stored version of the MBS SIB, then the UE requests an on-demand MBS SIB and obtains an SI containing at least one desired MBS SIB.

[0388] In one embodiment, the UE requests the (multiple) on-demand MBS SIBs contained in the SI message based on the mbsSI-SchedulingInfo in the stored SIB1. If onDemandSIB-Request is configured and the timer is not running, the UE initiates the transmission of the DedicatedSIBRequest message and starts a timer whose timer value is set to onDemandSIB-RequestProhibitTimer.

[0389] In one embodiment, the UE requests an on-demand MBS SIB and obtains an SI message in one of the following ways: obtaining an SI message in which the MBS SIB is included in an SI message based on si-SchedulingInfo in stored SIB1, wherein si-BroadcastStatus is set to "broadcast"; and requesting the on-demand MBS SIB contained in the SI message based on si-SchedulingInfo in stored SIB1, wherein si-BroadcastStatus is set to "not broadcast", and wherein the UE initiates the transmission of a DedicatedSIBRequest message, starts a timer with a timer value set to onDemandSIB-RequestProhibitTimer, and if onDemandSIB-Request is configured and the timer is not running, obtains the requested SI message corresponding to the requested MBS SIB(s), wherein the UE obtains the requested SI message including the MBS SIB.

[0390] In one embodiment, the UE includes an on-demand request for at least one of (multiple) SIBs, a location SIB, and an MBS SIB in the DedicatedSIBRequest message, wherein the UE sets the required (multiple) MBS SIBs in the SIB-ReqInfo field of the requestedSIB-List within the onDemandSIB-RequestList of the DedicatedSIBRequest message.

[0391] Accordingly, embodiments of this document provide a method for handling MBS BWP handover in a wireless network. The method includes a UE receiving a broadcast signaling message, and the UE determining that the configured MBS BWP or CFR is one of the following: identical to CORESET index 0, identical to or greater than the initial BWP, wherein the broadcast signaling message is an MBS System Information Block (SIB). Furthermore, the method includes, based on this determination, configuring the start and length of a Physical Resource Block (PRB) for one of the MBS BWP or CFR when the MBS BWP or CFR used for broadcast service reception is greater than the initial BWP. Additionally, the method includes the UE receiving MBS services from the configured MBS BWP or CFR.

[0392] Accordingly, embodiments of this document provide a method for handling a handover from one of the configured MBS BWP and CFR to an initial BWP in a wireless network. The method includes the UE detecting a handover event for a handover from one of the configured MBS BWP and CFR to the initial BWP. Furthermore, the method includes the UE handing over from one of the configured MBS BWP and CFR to the initial BWP based on the handover event.

[0393] In one embodiment, the handover event corresponds to at least one of the following: the UE stops receiving MBS service, the network entity abandons the required MBS service, the cell is changed so that the MBS service is no longer supported, the RRC state is changed, the MCCH indicates the removal or cessation of the MBS service, and the SIB or MCCH provides an MBSBWP or CFR with a configuration that has been changed to be less than or equal to the initial BWP.

[0394] Accordingly, embodiments of this document provide a method for handling a handover from one of an MBS BWP and a CFR to an initial BWP in a wireless network. The method includes the UE determining that the RRC state has changed from an RRC connected state to at least one of an RRC inactive state and an RRC idle state. Furthermore, the method includes the UE determining whether it has already received an MBS broadcast in the RRC connected state. Additionally, the method includes the UE performing one of the following actions: in response to determining that the UE has not yet received an MBS broadcast in the RRC connected state, switching the UE to the initial BWP in at least one of the RRC inactive state and the RRC idle state; and in response to determining that the UE has already received an MBS broadcast in the RRC connected state, determining whether the MBS BWP or CFR used for broadcast reception is greater than the initial BWP.

[0395] In one embodiment, in response to determining that the MBS BWP or CFR used for broadcast reception is greater than the initial BWP, the UE continues MBS broadcast reception on the configured MBS BWP or MBS CFR in at least one of the RRC idle state and the RRC inactive state.

[0396] In one embodiment, in response to determining that the MBS BWP or CFR used for broadcast reception is not greater than the initial BWP, the UE switches to the initial BWP, and the UE continues MBS broadcast reception in the initial BWP in the RRC idle state or RRC inactive state.

[0397] Accordingly, embodiments of this document provide a method for handling a handover from one of an MBS BWP and a CFR to an initial BWP in a wireless network. The method includes the UE determining that the RRC state has changed from at least one of an RRC inactive state and an RRC idle state to an RRC connected state. Furthermore, the method includes the UE determining whether it has already received an MBS broadcast in at least one of the RRC inactive state and the RRC idle state. In one embodiment, the method includes, in response to determining that the UE has not yet received an MBS broadcast in at least one of the RRC inactive state and the RRC idle state, switching the UE to the RRC connected state and monitoring according to a dedicated unicast BWP. In another embodiment, the method includes, in response to determining that the UE has already received an MBS broadcast in at least one of the RRC inactive state and the RRC idle state, determining whether the MBS BWP or CFR used for broadcast reception is greater than the initial BWP.

[0398] In one embodiment, the UE performs an RA procedure on the initial BWP, wherein in response to determining that the MBS BWP or CFR used for broadcast reception is greater than the initial BWP, the UE continues MBS broadcast reception on the configured MBS BWP or MBS CFR.

[0399] In one embodiment, the UE performs the RA procedure on the initial BWP, and the UE continues MBS broadcast reception in the initial BWP. In response to determining that the MBS BWP or CFR used for broadcast reception is not greater than the initial BWP, the UE monitors the BWP / CFR or the initial BWP.

[0400] Accordingly, embodiments of this document provide a method for handling handover from an initial BWP to one of an MBS BWP and a CFR in a wireless network. The method includes the UE detecting a handover event for handover from the initial BWP to one of the configured MBS BWP and CFR. Furthermore, the method includes the UE handover from the initial BWP to one of the configured MBS BWP and CFR based on the handover event.

[0401] In one embodiment, a handover event corresponds to the UE starting MBS service reception, the desired MBS service being initiated by a network entity, the desired MBS service being restored by a network entity, the desired MBS service being activated by a network entity, a cell change so that the MBS service becomes supported or available, an RRC status change, an MCCH change notification indicating the start of the desired service, an MCCH indicating the start of the desired service, and an MBS BWP or CFR being provided by the SIB or MCCH with a configuration changed to be greater than the initial BWP.

[0402] Accordingly, embodiments of this document provide a method for processing discontinuous reception (DRX) configurations in a wireless network. The method includes sending an MCCH signaling message to a UE by a network entity. The MCCH signaling message includes at least one of a DRX scheduling configuration list and an MBS service configuration list. Furthermore, the method includes mapping the DRX scheduling configuration to the PTM service configuration by the network entity based on an index of the DRX scheduling configuration provided in the Point-to-Multipoint (PTM) service configuration within the MCCH signaling message.

[0403] Accordingly, embodiments of this document provide a method for processing signaling for MBS interest indications in a wireless network. The method includes a UE receiving at least one MBS service in a Radio Resource Control (RRC) connected state. Furthermore, the method includes the UE reporting an MBS interest indication message to a network entity. The MBS interest indication message includes at least one of an MBS service list, a frequency list, and priority MBS services. Additionally, the method includes the UE ceasing to receive all MBS services from the network entity. Furthermore, the method includes the UE sending an MBS interest indication message with an empty message to indicate a complete loss of interest in the MBS, and thereafter, the UE ceasing to report MBS interest indications.

[0404] Accordingly, embodiments of this document provide a method for handling the reservation of a Broadcast MBS Radio Bearer (MRB) in a wireless network. The method includes having the UE receive at least one MBS broadcast service when the UE is in one of an RRC connected state, an RRC idle state, and an RRC inactive state. Furthermore, the method includes having the UE continue receiving the MBS broadcast service and reserving the broadcast MRB when the UE receives one of an RRC release and an RRC release with a suspend configuration from a network entity, or when the dataInactivityTimer expires. Additionally, the method includes having the UE continue receiving the MBS broadcast service and reserving the broadcast MRB when the UE (100) receives one of an RRC establishment and an RRC recovery from a network entity. Furthermore, the method includes having the UE perform at least one action based on continuing to receive the MBS broadcast service and reserving the broadcast MRB.

[0405] In one embodiment, at least one action includes: retaining the PTM configuration received from the MCCH, retaining the PTM RLC entity used for broadcasting the MRB, releasing all other RLC entities, retaining the MAC entity and MAC configuration used for broadcasting the MRB, releasing all other MAC configurations, retaining at least one of the initial BWP, the configured MBS BWP, and the configured MBS CFR, releasing other BWPs, retaining the DRX configuration and timer of the PTM used for MBS broadcasting, and retaining the HARQ buffer and configuration of the PTM used for MBS broadcasting.

[0406] Accordingly, embodiments of this document provide a method for processing multicast reception in a wireless network. The method includes having the UE continue receiving at least one multicast service in an RRC inactive state when a network entity releases the UE from an RRC connected state. Furthermore, the method includes having the UE perform at least one action based on continuing to receive at least one multicast service in an RRC inactive state.

[0407] In one embodiment, at least one action includes: releasing the PTP configuration for multicast services, releasing the PTP-related RLC entity and MAC configuration, partially or completely resetting the MAC entity, retaining the PTM configuration for multicast in an inactive state, providing the UE with the inactive state configuration for multicast services by a network entity via at least one of broadcast signaling and / or dedicated signaling via RRC reconfiguration and RRC release with a pending configuration, changing the BWP configuration for multicast from a dedicated BWP to one of the initial BWP, the configured MBS BWP, and the CFR, or continuing to use the dedicated BWP for multicast service reception without actually being in a connected state, and managing the DRX configuration for multicast service reception in an inactive state.

[0408] Accordingly, embodiments of this document provide a method for processing multicast reception in a wireless network. The method includes receiving at least one MBS multicast service by the UE when the UE is in an RRC connected state. Furthermore, the method includes receiving a combination of a reconfiguration message and an RRC release message with a suspended configuration from a network entity by the UE. Additionally, the method includes switching the RRC connected state to an RRC inactive state by the UE based on receiving a combination of a reconfiguration message and an RRC release message with a suspended configuration from a network entity. Furthermore, the method includes continuing to receive at least one MBS multicast service by the UE in the RRC inactive state via one of a first delivery mode and a second delivery mode. In one embodiment, the method includes receiving dedicated signaling for receiving at least one MBS multicast service in RRC connected mode after determining at least one related configuration change for the RRC inactive state via at least one of a SIB, MCCH, and paging message. In another embodiment, the method includes receiving notification signaling and configuration signaling in the RRC inactive state via at least one of a SIB, MCCH, and paging message.

[0409] In one embodiment, upon detecting congestion at a network entity, at least one of a reconfiguration message and an RRC release message with a pending configuration is received, wherein the first delivery mode maintains the same connection mode BWP and multicast PDCCH and PDSCH channels, and at least one UE-specific operation for at least one of Hybrid Automatic Repeat Request (HARQ) and Channel State Information (CSI) feedback and configuration is skipped, and multicast service is received.

[0410] In one embodiment, upon detecting congestion at a network entity, at least one of a reconfiguration message and an RRC release message with a pending configuration is received, wherein a second delivery mode releases the connection mode BWP and the multicast PDCCH and PDSCH channels, and at least one UE-specific operation is performed for at least one of Hybrid Automatic Repeat Request (HARQ) and Channel State Information (CSI) feedback and configuration, wherein the UE is configured according to the new configuration for the RRC inactive state and receives multicast services.

[0411] Accordingly, embodiments of this document provide a method for processing multicast reception in a wireless network. The method includes a user equipment (UE) continuing to receive at least one MBS multicast service while in an RRC inactive state. Furthermore, the method includes the UE sending an RRC recovery request to a network entity, and in response to sending the RRC recovery request to the network entity, the UE performing at least one action. Additionally, the method includes the UE continuing to receive at least one MBS multicast service while in an RRC connected state.

[0412] In one embodiment, the UE continues to receive at least one MBS multicast service in the RRC connected state, wherein at least one UE switches from the RRC inactive state to the RRC connected state under at least one of the following conditions: the UE receives an instruction to receive the MBS multicast service in the RRC connected state via at least one of the SIB, MCCH and paging messages in the RRC inactive state, and the UE autonomously decides to return to the RRC connected state.

[0413] In one embodiment, at least one action includes: continuing the PTM configuration for multicast services used in the RRC inactive state, continuing the PTM-related RLC entity and MAC configuration, not resetting the MAC entity, receiving the configuration for multicast MBS services from the network entity via dedicated signaling, and enabling the UE to continue using the same dedicated BWP while transitioning to the RRC connected state.

[0414] In one embodiment, at least one action includes: releasing the PTM configuration used for multicast services in the RRC inactive state, releasing the PTM-related RLC entity, releasing the MAC configuration, resetting the MAC entity, releasing at least one of the BWP, search space, HARQ, and DRX configurations obtained from the SIB or MCCH for multicast services, receiving the configuration for multicast services via dedicated signaling, changing the BWP configuration for MBS from the initial BWP or configured MBS BWP or CFR to a dedicated BWP if the BWP configuration is being used in the inactive mode, and continuing to use the same dedicated BWP while transitioning to the RRC connected state.

[0415] Accordingly, embodiments of this document provide a UE for processing MBS services in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to receive MCCH configuration and at least one parameter associated with the MCCH configuration in the SIB. Furthermore, the MBS service controller configures an MCCH channel based on the MCCH configuration and the parameter associated with the MCCH configuration. Furthermore, the MBS service controller is configured to receive MCCH information messages through the MCCH channel. Furthermore, the MBS service controller configures at least one MTCH based on the MCCH information messages. Furthermore, the MBS service controller is configured to receive MBS services through the MTCH.

[0416] Accordingly, embodiments of this document provide a UE for processing MBS services in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. Furthermore, the MBS service controller is configured to receive MCCH change notification information and the MCCH using MCCH-RNTI. In one embodiment, the MBS service controller is configured to acquire the MCCH in response to determining that a network entity has indicated MCCH change notification information. In another embodiment, the MBS service controller is configured to use a stored MCCH in response to determining that a network entity has not indicated MCCH change notification information.

[0417] Accordingly, embodiments of this document provide a UE for processing on-demand MBS SIB reception in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. Furthermore, the MBS service controller is configured to receive SIB1 and determine whether SIB1 includes Si-Scheduling information containing a si-RequestConfig for the MBS SIB. In one embodiment, the MBS service controller is configured to, in response to determining that SIB1 includes Si-Scheduling information containing a si-RequestConfig for the MBS SIB, trigger a lower layer to initiate a random access procedure on a normal uplink or supplementary uplink using at least one of the Physical Random Access Channel (PRACH) preamble and PRACH resources in the si-RequestConfig corresponding to a System Information (SI) message, which is required by the UE to receive the MBS SIB within the cell and whose si-BroadcastStatus is set to "not broadcast". Furthermore, the MBS service controller is configured to, in response to determining that SIB1 does not include Si-Scheduling information containing a si-RequestConfig for the MBS SIB, transmit an RRCSystemInfoRequest message.

[0418] Accordingly, embodiments of this document provide a UE for processing on-demand MBS SIB reception in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to determine whether the UE is in connected mode and has a valid stored version of the MBS SIB and the UE needs to operate within the cell; or, the UE is in connected mode and the active BWP does not include or has not configured a common search space and the UE does not have a valid stored version of the MBS SIB; or, the UE is in connected mode and the active BWP includes or has configured a common search space and the UE does not have a valid stored version of the MBS SIB and the cell is broadcasting; or, the UE is in connected mode and the active BWP includes or has configured a common search space and the UE does not have a valid stored version of the MBS SIB and the cell is not broadcasting. In one embodiment, the MBS service controller is configured to utilize stored versions(multiple) of the MBS SIB in response to determining that the UE is in connected mode and has a valid stored version of the MBS SIB. In another embodiment, the MBS service controller is configured to request an on-demand MBS SIB if the UE is in connected mode and the active BWP associated with the UE does not include or has not configured a common search space for the MBS SIB, and the UE does not have a valid stored version of the MBS SIB. In one embodiment, the MBS service controller is configured to request an on-demand MBS SIB and obtain an SI containing at least one desired MBS SIB if the UE is in connected mode and the active BWP associated with the UE includes or has configured a common search space for the MBS SIB, and the UE does not have a valid stored version of the MBS SIB.

[0419] Accordingly, embodiments of this document provide a UE for handling MBS BWP handover in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to receive broadcast signaling messages and determine that the configured MBS BWP or CFR is one of the following: identical to CORESET index 0, identical to or greater than the initial BWP, wherein the broadcast signaling message is an MBS System Information Block (SIB). Furthermore, the MBS service controller is configured, based on this determination, to configure the start and length of a Physical Resource Block (PRB) for one of the MBS BWP or CFR when the MBS BWP or CFR used for broadcast service reception is greater than the initial BWP, and to receive MBS services from the configured MBS BWP or CFR.

[0420] Accordingly, embodiments of this document provide a UE for handling a handover from one of an MBS BWP and a CFR to an initial BWP in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to detect handover events for a handover from one of the configured MBS BWP and CFR to the initial BWP. Furthermore, the MBS service controller is configured to handover from one of the configured MBS BWP and CFR to the initial BWP based on the handover event.

[0421] Accordingly, embodiments of this document provide a method for handling a UE switching from one of an MBS BWP and a CFR to an initial BWP in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to determine that the RRC state changes from an RRC connected state to at least one of an RRC inactive state and an RRC idle state, and to determine whether the UE has already received an MBS broadcast in the RRC connected state. Furthermore, in one embodiment, the MBS service controller is configured to switch the UE to the initial BWP in at least one of the RRC inactive state and the RRC idle state in response to determining that the UE has not yet received an MBS broadcast in the RRC connected state. Furthermore, in one embodiment, the MBS service controller is configured to determine whether the MBS BWP or CFR used for broadcast reception is greater than the initial BWP in response to determining that the UE has already received an MBS broadcast in the RRC connected state.

[0422] Accordingly, embodiments of this document provide a method for handling a UE switching from one of an MBS BWP and a CFR to an initial BWP in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to determine if the RRC state changes from at least one of an RRC inactive state and an RRC idle state to an RRC connected state. Furthermore, the MBS service controller is configured to determine whether the UE has already received an MBS broadcast in at least one of the RRC inactive state and the RRC idle state. In one embodiment, the MBS service controller is configured to switch the UE to the RRC connected state and monitor according to a dedicated unicast BWP in response to determining that the UE has not yet received an MBS broadcast in at least one of the RRC inactive state and the RRC idle state. In another embodiment, the MBS service controller is configured to determine whether the MBS BWP or CFR used for broadcast reception is greater than the initial BWP in response to determining that the UE has already received an MBS broadcast in at least one of the RRC inactive state and the RRC idle state.

[0423] Accordingly, embodiments of this document provide a UE for handling a handover from an initial BWP to one of an MBS BWP and a CFR in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to detect handover events for a handover from the initial BWP to one of the configured MBS BWP and CFR. The MBS service controller is configured to handover from the initial BWP to one of the configured MBS BWP and CFR based on the handover events.

[0424] Accordingly, embodiments of this document provide a network entity for processing DRX configuration in a wireless network. The network entity includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to send MCCH signaling messages to the UE. The MCCH signaling message includes at least one of a DRX scheduling configuration list and an MBS service configuration list. The MBS service controller is configured to map DRX scheduling configurations to Point-to-Multipoint (PTM) service configurations based on an index of the DRX scheduling configuration provided in the PTM service configuration within the MCCH signaling message.

[0425] Accordingly, embodiments of this document provide a UE for processing signaling of MBS interest indications in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to receive at least one MBS service in an RRC connected state. Furthermore, the MBS service controller is configured to report MBS interest indication messages to network entities. The MBS interest indication message includes at least one of an MBS service list, a frequency list, and priority MBS services. Additionally, the MBS service controller is configured to stop receiving all MBS services from network entities. The MBS service controller is configured to send an MBS interest indication message with an empty message to indicate a complete loss of interest in the MBS, and thereafter, the UE stops reporting MBS interest indications.

[0426] Accordingly, embodiments of this document provide a UE for handling broadcast MRB reservation in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to receive at least one MBS broadcast service when the UE is in one of an RRC connected state, an RRC idle state, and an RRC inactive state. Furthermore, the MBS service controller is configured to continue receiving the MBS broadcast service and reserve the broadcast MRB when the UE receives one of an RRC release and an RRC release with a suspend configuration from a network entity, or when the dataInactivityTimer expires. Additionally, the MBS service controller is configured to continue receiving the MBS broadcast service and reserve the broadcast MRB when the UE receives one of an RRC establishment and an RRC recovery from a network entity. Furthermore, the MBS service controller is configured to perform at least one action based on continuing to receive the MBS broadcast service and reserving the broadcast MRB.

[0427] Accordingly, embodiments of this document provide a UE for processing multicast reception in a wireless network. The UE includes an MBS service controller coupled to a processor and a memory. The MBS service controller is configured to: continue receiving at least one multicast service in an RRC inactive state when a network entity releases the UE from an RRC connected state; and perform at least one action based on continuing to receive at least one multicast service in an RRC inactive state.

[0428] Accordingly, embodiments of this document provide a UE for handling multicast reception in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to receive at least one MBS multicast service when the UE is in an RRC connected state. Furthermore, the MBS service controller is configured to receive one of a combination of a reconfiguration message and an RRC release message with a suspend configuration from a network entity. Additionally, the MBS service controller is configured to switch the RRC connected state to an RRC inactive state based on receiving one of the combination of the reconfiguration message and the RRC release message with a suspend configuration from the network entity. Furthermore, the MBS service controller is configured to continue receiving at least one MBS multicast service in the RRC inactive state via one of a first delivery mode and a second delivery mode. In addition, the MBS service controller is configured to perform one of the following: after determining at least one related configuration change of the RRC inactive state via at least one of the SIB, MCCH and paging messages, receive dedicated signaling for receiving at least one MBS multicast service configuration in RRC connected mode, and receive notification signaling and configuration signaling via at least one of the SIB, MCCH and paging messages in the RRC inactive state.

[0429] Accordingly, embodiments of this document provide a UE for handling multicast reception in a wireless network. The UE includes an MBS service controller coupled to a processor and memory. The MBS service controller is configured to continue receiving at least one MBS multicast service in an RRC inactive state. Furthermore, the MBS service controller is configured to send an RRC recovery request to a network entity. Additionally, the MBS service controller is configured to perform at least one action in response to sending the RRC recovery request to the network entity. Furthermore, the MBS service controller is configured to continue receiving at least one MBS multicast service in an RRC connected state.

[0430] 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 points to at least one embodiment and many specific details thereof, it is given by way of illustration rather than limitation. Many variations and modifications can be made within the scope of the embodiments herein without departing from the scope of the embodiments herein, and the embodiments herein include all such modifications.

[0431] The foregoing description of specific embodiments will so fully reveal the general nature of the embodiments herein that others can readily modify and / or rewrite such specific embodiments for various applications by applying present knowledge without departing from the general concept. Therefore, such modifications and alterations should and are intended to be understood 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 for limitation. Thus, although embodiments herein have been described according to at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the scope of the embodiments described herein.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: On the Multicast / Broadcast Service (MBS) Control Channel (MCCH), an MBSBroadcastConfiguration message including mbs-SessionInfoList and drx-ConfigPTM-List is received from a base station, wherein the mbs-SessionInfoList includes at least one mbs-SessionInfo, and the at least one mbs-SessionInfo includes mbs-SessionId and DRX-ConfigPTM-Index respectively; Based on the MBSBroadcastConfiguration message, identify the DRX-ConfigPTM-Index for receiving MBS corresponding to the mbs-SessionId; and When the MCCH information is changed, a MCCH change notification carrying a 2-bit bitmap is received from the base station. in, When the most significant bit (MSB) of the 2-bit bitmap is set to 1, the MSB indicates the start of a new MBS session; and Wherein, when the least significant bit (LSB) of the 2-bit bitmap is set to 1, the LSB indicates modifications to the MCCH information other than those caused by the start of the new MBS session.

2. The method according to claim 1, wherein, The mapping relationship between the DRX-ConfigPTM-Index and the mbs-SessionId is included in at least one mbs-SessionId.

3. The method according to claim 1, further comprising: Obtain updated MCCH information from the time slot where MCCH change notifications are received. Specifically, MCCH change notifications, including those in the downlink control information (DCI), are received on the physical downlink control channel (PDCCH) scrambled with the MCCH radio network temporary identifier (RNTI).

4. The method according to claim 1, further comprising: Receive System Information Block (SIB) to obtain MCCH configuration including information about Common Frequency Resources (CFRs). The information regarding CFRs includes information indicating the starting physical resource block (PRB) and the number of PRBs for CFRs used in MCCH and multicast traffic channel MTCH reception.

5. The method according to claim 4, wherein, The information indicating the starting PRB and the number of PRBs for the CFR used for MCCH and MTCH reception also includes one of the following: first information indicating that the CFR has the same location and the same size as the initial BWP configured in SIB1; second information configuring the CFR to have a larger bandwidth than the initial BWP configured in SIB1.

6. The method according to claim 1, further comprising: Under predetermined conditions, release all radio bearers except for the MBS radio bearer MRB. The predetermined conditions include the expiration of the timer for receiving or data inactivity based on the RRC release message, and the change of the terminal's Radio Resource Control (RRC) state from connected mode to idle mode.

7. A terminal in a wireless communication system, the terminal comprising: transceiver; as well as At least one processor is configured to receive, via the transceiver, an MBSBroadcastConfiguration message comprising mbs-SessionInfoList and drx-ConfigPTM-List on the Multicast / Broadcast Service MBS Control Channel MCCH, wherein the mbs-SessionInfoList comprises at least one mbs-SessionInfo, and the at least one mbs-SessionInfo comprises mbs-SessionId and DRX-ConfigPTM-Index, respectively; Based on the MBSBroadcastConfiguration message, identify the DRX-ConfigPTM-Index for receiving MBS corresponding to the mbs-SessionId; and In the event that the MCCH information has been changed, the transceiver receives an MCCH change notification carrying a 2-bit bitmap from the base station. Wherein, when the most significant bit (MSB) of the 2-bit bitmap is set to 1, the MSB indicates the start of a new MBS session; and Wherein, when the least significant bit (LSB) of the 2-bit bitmap is set to 1, the LSB indicates modifications to the MCCH information other than those caused by the start of the new MBS session.

8. The terminal according to claim 7, wherein, The mapping relationship between the DRX-ConfigPTM-Index and the mbs-SessionId is included in at least one mbs-SessionId.

9. The terminal according to claim 7, wherein, The at least one processor is further configured to: Obtain the updated MCCH information from the slot where the MCCH change notification is received. Specifically, MCCH change notifications, including those in the downlink control information (DCI), are received on the physical downlink control channel (PDCCH) scrambled with the MCCH radio network temporary identifier (RNTI).

10. The terminal according to claim 7, wherein, The at least one processor is further configured to: The transceiver receives a System Information Block (SIB) to obtain an MCCH configuration including information about Common Frequency Resources (CFRs). The information regarding CFRs includes information indicating the starting physical resource block (PRB) and the number of PRBs for CFRs used in MCCH and multicast traffic channel MTCH reception.

11. The terminal according to claim 10, wherein, The information indicating the starting PRB and the number of PRBs for the CFR used for MCCH and MTCH reception also includes one of the following: first information indicating that the CFR has the same location and the same size as the initial BWP configured in SIB1; second information configuring the CFR to have a larger bandwidth than the initial BWP configured in SIB1.

12. The terminal of claim 7, wherein the at least one processor is further configured to release all radio bearers except the MBS radio bearer MRB upon satisfying predetermined conditions. in, The predetermined conditions include the expiration of the receiving or data inactivity timer based on the RRC release message, and the change of the terminal's Radio Resource Control (RRC) state from connected mode to idle mode.

Images