Physical downlink control channel monitoring for multicast broadcast services

Abstract

Certain aspects of the present disclosure provide techniques for physical downlink control channel (PDCCH) monitoring for multicast broadcast service (MBS). A method of wireless communication by a wireless node includes obtaining signaling indicating one or more search space (SS) parameters, the one or more search space (SS) parameters comprising at least one of: a defined set of control channel element (CCE) aggregation levels or a number of one or more PDCCH candidates per CCE aggregation level; and monitoring one or more PDCCHs that schedule communications via the one or more MBS channels based on the one or more SS parameters.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Patent Application No. 18 / 448,623, filed August 11, 2023, which is hereby incorporated by reference herein. BACKGROUND TECHNICAL FIELD

[0004] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for physical downlink control channel (PDCCH) monitoring for multicast broadcast services (MBS).

[0005] Related Art

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). Long Term Evolution (LTE) is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0007] Despite the tremendous technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between a wireless transmitter and a wireless receiver. Thus, there is a continuing desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of use of shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access a wireless communication system, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media that are available for use, and so on. Thus, there is a need to further improve wireless communication systems to overcome the aforementioned technical challenges and others. SUMMARY

[0008] One aspect provides a method for wireless communications by a wireless node. The method includes obtaining signaling indicating one or more search space (SS) parameters including at least one of: a defined set of control channel element (CCE) aggregation levels or a number of PDCCH candidates per CCE aggregation level; and monitoring, based on the one or more SS parameters, one or more PDCCHs scheduling communications via one or more MBS channels.

[0009] Another aspect provides a method for wireless communication by a network entity. The method includes outputting, for transmission, signaling indicating one or more SS parameters including at least one of: a defined set of CCE aggregation levels or a number of one or more PDCCH candidates per CCE aggregation level; and outputting, for transmission, one or more PDCCHs scheduling one or more MBS channels based on the one or more SS parameters.

[0010] Other aspects provide an apparatus capable of, configured for, or otherwise adapted to perform any one or more of the methods previously described and / or those described elsewhere herein; a non-transitory computer readable medium comprising instructions to cause an apparatus to perform the methods previously described and those described elsewhere; a computer program product embodied on a computer readable medium comprising code to perform the methods previously described and those described elsewhere; and / or an apparatus comprising means to perform the methods previously described and those described elsewhere. By way of example, an apparatus can include a processing system, a device having a processing system, or a processing system in cooperation with one or more networks.

[0011] The following description and drawings are illustrative of certain aspects. BRIEF DESCRIPTION OF DRAWINGS

[0012] The attached drawings illustrate certain aspects of the various aspects described herein and are a part of the specification. The drawings provided are intended to facilitate an understanding of the various aspects, and are not intended for descriptive purposes, as the aspects can be practiced with other elements and dimensions.

[0013] FIG. 1 An example wireless communication network is depicted.

[0014] FIG. 2 An example disaggregated base station architecture is depicted.

[0015] FIG. 3 Aspects of an example base station and an example user equipment are depicted.

[0016] FIG. 4A 、 FIG. 4B 、 FIG. 4C And FIG. 4D Various example aspects of data structures for a wireless communication network are depicted.

[0017] FIG. 5 Tables of control channel element (CCE) aggregation levels and numbers of PDCCH candidates per CCE aggregation level are depicted.

[0018] FIG. 6Process flows are depicted for communications in a network between a wireless node and a network entity.

[0019] FIG. 7 Methods for wireless communications by a wireless node are depicted.

[0020] FIG. 8 Methods for wireless communications by a network entity are depicted.

[0021] FIG. 9 Aspects of example communication devices are depicted.

[0022] FIG. 10 Aspects of example communication devices are depicted. DETAILED DESCRIPTION

[0023] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable media for monitoring PDCCH scheduling MBS channels. Some aspects relate to monitoring PDCCH scheduling MBS services, such as PDCCH for MBS control channel (MCCH) or MBS traffic channel (MTCH) of MBS broadcast. Some aspects relate to monitoring PDCCH scheduling MBS broadcast. Some aspects relate to monitoring PDCCH scheduling MBS multicast. Some aspects relate to monitoring PDCCH scheduling MBS while in radio resource control (RRC) inactive mode.

[0024] According to certain aspects, to monitor PDCCH scheduling broadcast MCCH and / or broadcast MTCH, a limitation on search space is assumed. In some aspects, the PDCCH is monitored in Type 0B-PDCCH common search space (CSS). In some aspects, the assumed limitation is aggregation level and number of PDCCH candidates per aggregation level.

[0025] According to certain aspects, to monitor PDCCH scheduling multicast MCCH and / or MTCH in RRC inactive mode, a limitation on search space is assumed.

[0026] According to certain aspects, to monitor PDCCH scheduling multicast MTCH in RRC inactive mode, a mapping of synchronization signal block (SSB) to MTCH PDDCH occasions is configured by RRC release message or system information block (SIB).

[0027] According to certain aspects, to monitor PDCCH scheduling multicast MTCH in RRC inactive mode, the PDCCH is monitored in Type 0 / 0B-PDCCH CSS or Type-3-PDCCH CSS.

[0028] According to certain aspects, monitoring PDCCH scheduling MBS multicast MTCH in RRC inactive mode follows as in RRC connected mode until RRC release message or SIB is received.

[0029] Aspects of the disclosure for monitoring PDCCH scheduling MCCH and MTCH can allow for reduced hardware, software, and / or firmware complexity and / or reduced power consumption of user equipment (UE) and network entities.

[0030] Introduction to Wireless Communication Networks

[0031] The techniques and methods described herein can be used for various wireless communication networks. Although aspects can be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure can be applied in other communication systems and standards not explicitly mentioned.

[0032] FIG. 1 An example of a wireless communication network 100 in which aspects described herein can be implemented is depicted.

[0033] Generally, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communication device and / or a communication function performed by a communication device (e.g., a user equipment (UE), a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network and various devices associated with and interacting with a network can be considered network entities. Further, the wireless communication network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BSs 102), and non-terrestrial aspects, such as satellites 140 and aircraft 145, which can include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipment.

[0034] In the depicted example, the wireless communication network 100 includes BSs 102, UEs 104, and one or more core networks, such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190, that interoperate to provide communication services over various communication links, including wired and wireless links.

[0035] FIG. 1Various example UEs 104 are depicted, which can more generally include: a cellular telephone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an always-on (AON) device, an edge processing device, or other similar device. A UE 104 can also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and other.

[0036] The BSs 102 wirelessly communicate (e.g., transmit to and / or receive from) with the UEs 104 via communication links 120. The communication links 120 between the BSs 102 and the UEs 104 can include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104. In various aspects, the communication links 120 can use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0037] The BSs 102 can generally include: a NodeB, an enhanced NodeB (eNB), a next generation enhanced NodeB (ng-eNB), a next generation NodeB (gNB or gNodeB), an access point, a transceiver base station, a radio base station, a radio transceiver, a transceiver function, a transmit receive point, and / or other. Each of the BSs 102 can provide communication coverage for a respective geographic coverage area 110, which can sometimes be referred to as a cell, and which, in some cases, can overlap with other cells (e.g., small cell 102' can have a coverage area 110' that overlaps with a coverage area 110 of a macro cell). For example, a BS can be a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (covering a relatively small geographic area, e.g., a home), and / or other types of cells.

[0038] While the BS 102 is depicted as a single communication device in various aspects, the BS 102 can be implemented in various configurations. For example, one or more components of the base station can be split, including a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-RT RIC. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples in which a base station includes components located at various physical locations, the various components can each perform functions such that the various components collectively implement similar functionality as a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a disaggregated radio access network architecture, such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture. FIG. 2 An example disaggregated base station architecture is depicted and described.

[0039] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 through first backhaul links 132 (e.g., S I interface). BSs 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with the 5GC 190 through second backhaul links 184. The BSs 102 can communicate with one another directly or indirectly (e.g., through the EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0040] Wireless communications network 100 can subdivide the electromagnetic spectrum into various classes, bands, channels, or other characteristics. In some aspects, the subdivision is based on wavelength and frequency, where frequency can also be referred to as a carrier, subcarrier, frequency channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) to include 410-7125 MHz, which is often (interchangeably) referred to as “sub-6 GHz.” Similarly, 3GPP currently defines frequency range 2 (FR2) to include 24,250- 71,000 MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further subdivided into sub-ranges, such as a first sub-range FR2-1 including 24,250-52,600 MHz and a second sub-range FR2-2 including 52,600-71,000 MHz. Base stations configured to communicate using mmWave / near-mmWave radio frequency bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0041] Communication links 120 between BS 102 and UEs 104, for example, can be through one or more carriers, which can have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz) and can be arranged to carry downlink or uplink (DL / UL) data or control information. Carrier can be interlaced across the available spectrum, or divided into separate frequency regions spaced along the spectrum. Each frequency region can be assigned to carry one or multiple signals for transmission by BS 102 to a single UE 104 or multiple UEs 104, or to carry a single signal for transmission by a single UE 104 to BS 102. In some aspects, carriers can be arranged for transmission to or from one or more UEs 104.

[0042] Communication using higher frequency bands can have higher path loss and shorter range than lower frequency communications. Thus, certain base stations (e.g., gNBs 180) can be configured to use beamforming and directional transmission techniques (e.g., in millimeter wave (mmW) frequency bands or other high frequency bands) to compensate for the path loss and transmit further efficiently. FIG. 1The use of beamforming 182 with the UEs 104 can improve path loss and range in the communications between BS 180 and the UEs 104. For example, the BS 180 and the UEs 104 can each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 can transmit beamformed signals to the UEs 104 in one or more transmit directions 182'. The UEs 104 can receive beamformed signals from the BS 180 in one or more receive directions 182". The UEs 104 can also transmit beamformed signals to the BS 180 in one or more transmit directions 182". The BS 180 can also receive beamformed signals from the UEs 104 in one or more receive directions 182'. The BS 180 and the UEs 104 can then perform beam training to determine the best receive and transmit directions for each of the BS 180 and the UEs 104. Notably, the transmit and receive directions of the BS 180 can or can not be the same. Similarly, the transmit and receive directions of the UEs 104 can or can not be the same.

[0043] The wireless communications network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0044] Certain UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 can use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0045] The EPC 160 can include various function components, including a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the depicted example. The MME 162 can be in communication with a home subscriber server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management.

[0046] Generally, user Internet Protocol (IP) packets are conveyed through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation as well as other functions. The PDN gateway 172 and BM-SC 170 are connected to the IP services 176, which can include, for example, the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switched (PS) streaming sendee, and / or other IP services.

[0047] The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmission, can be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS Gateway 168 can be used to

[0048] The 5GC 190 can include various function components including an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 can be in communication with a Unified Data Management (UDM) 196.

[0049] The AMF 192 is the control node that processes the signaling between the UE 104 and the 5GC 190. For example, the AMF 192 provides quality of service (QoS) flow and session management.

[0050] Internet Protocol (IP) packets are conveyed through the UPF 195, which connects to the IP Services 197 and provides IP address allocation as well as other functions for the UE 104 to the 5GC 190. The IP Services 197 can include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.

[0051] In various aspects, a network entity or network node can be implemented as an aggregated base station, disaggregated base station, component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0052] FIG. 2An example disaggregated base station 200 architecture is depicted. The disaggregated base station 200 architecture can include one or more central units (CU) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 can communicate with one or more distributed units (DU) 230 via respective fronthaul links, such as Fl interfaces. The DU 230 can communicate with one or more radio units (RU) 240 via respective front-haul links. The RU 240 can communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 can be simultaneously served by multiple RUs 240.

[0053] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission media. For example, the units can include wired interfaces configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally or alternatively, the units can include wireless interfaces, which can include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive or transmit signals to one or more of the other units over a wireless transmission medium, or both.

[0054] In some aspects, the CU 210 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), and / or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 can be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bi-directionally with the CU-CP units via an interface, such as an El interface. The CU 210 can be implemented to communicate with the DUs 230 as needed for network control and signal transfer.

[0055] The DUs 230 can correspond to logical units that include one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DUs 230 can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and / or the like) in accordance with, at least in part, a function split, such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DUs 230 can further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DUs 230 or with control functions hosted by the CU 210.

[0056] The lower layer functionality can be implemented by one or more RUs 240. In some deployments, the RUs 240 controlled by the DUs 230 can correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, and / or the like) or both based, at least in part, on a function split, such as a lower layer function split. In such an architecture, the RUs 240 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 240 can be controlled by the corresponding DUs 230. In some scenarios, this configuration can enable the DUs 230 and the CUs 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0057] The SMO framework 205 can be configured to support RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non- virtualized network elements, the SMO framework 205 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform, such as Open Cloud (O-Cloud) 290, to perform network element lifecycle management, such as instantiating virtualized network elements, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240, and near-RT RICs 225. In some implementations, the SMO framework 205 can communicate with hardware aspects of a 4G RAN, such as Open eNBs (O-eNBs) 211, via the Ol interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via the Ol interface. The SMO framework 205 can also include a non-RT RIC 215 configured to support functionality of the SMO framework 205.

[0058] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based direction of applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to, or in communication with, the near-RT RIC 225, such as via an Al interface. The near-RT RIC 225 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface, such as via an E2 interface, that connects one or more CUs 210, one or more DUs 230, or both, and an O-eNB with the near-RT RIC 225.

[0059] In some implementations, to generate AI / ML models to be deployed in near-RT RIC 225, non-RT RIC 215 can receive parameters or external enrichment information from an external server. Such information can be utilized by near-RT RIC 225 and can be received at SMO framework 205 or non-RT RIC 215 from non-network data sources or from network functions. In some examples, non-RT RIC 215 or near-RT RIC 225 can be configured to tune RAN behavior or performance. For example, non-RT RIC 215 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through SMO framework 205, such as via reconfiguration of Ol, or via creation of RAN management policies, such as Al policies.

[0060] FIG. 3 Aspects of an example BS 102 and UE 104 are depicted.

[0061] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively, 334), transceivers 332a-332t (collectively, 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement various functions related to wireless communication described herein.

[0062] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively, 352), transceivers 354a-354r (collectively, 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement various functions related to wireless communication described herein.

[0063] With respect to example downlink transmissions, the BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical HARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), and / or other. In some examples, the data can be for the physical downlink shared channel (PDSCH).

[0064] The transmit processor 320 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 can also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS).

[0065] A transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and / or the reference symbols, if applicable, and can provide output symbol streams to the modulators (MODs) in the transceivers 332a-t. Each modulator in transceivers 332a-t can process a respective output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 332a-t can be transmitted via the antennas 334a-t, respectively.

[0066] To receive downlink transmissions, the UE 104 includes antennas 352a-352r, which can receive the downlink signals from the BS 102 and can provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0067] A MIMO detector 356 can obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0068] With respect to example uplink transmissions, the UE 104 further includes a transmit processor 364 that can receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller / processor 380. The transmit processor 364 can also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 364 can be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.

[0069] At the BS 102, the uplink signals from the UE 104 can be received by the antennas 334a-334t, processed by the demodulators in the transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information transmitted by the UE 104. The receive processor 338 can provide the decoded data to a data sink 339 and to the controller / processor 340.

[0070] The memory 342 and the memory 382 can store data and program codes for the BS 102 and the UE 104, respectively.

[0071] A scheduler 344 can schedule UEs for data transmission on the downlink and / or uplink.

[0072] In various aspects, the BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms of outputting data, such as from the data source 312, the scheduler 344, the memory 342, the transmit processor 320, the controller / processor 340, the TX MIMO processor 330, the transceivers 332a-332t, the antennas 334a-334t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms of obtaining data, such as from the antennas 334a-334t, the transceivers 332a-332t, the RX MIMO detector 336, the controller / processor 340, the receive processor 338, the scheduler 344, the memory 342, and / or other aspects described herein.

[0073] In various aspects, the UE 104 can likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms of outputting data, such as from a data source 362, a memory 382, a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms of obtaining data, such as from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, and / or other aspects described herein.

[0074] In some aspects, one or more processors can be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0075] FIG. 4A 、 FIG. 4B 、 FIG. 4C and FIG. 4D depicts aspects of data structures for a wireless communication network, such as the wireless communication network 100 of FIG. 1 .

[0076] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.

[0077] A wireless communication system can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such a system can also support half-duplex FIG. 4B and FIG. 4D The system bandwidth is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain with OFDM and / or in the time domain with single-carrier frequency division multiplexing (SC-FDM), e.g., as described in

[0078] The wireless communication frame structure can be frequency division duplex (FDD) where for a particular set of subcarriers, the subframes within that set of subcarriers are dedicated for either DL or UL. The wireless communication frame structure can also be time division duplex (TDD) where for a particular set of subcarriers, the subframes within that set of subcarriers are dedicated for both DL and UL.

[0079] In FIG. 4A and FIG. 4C , the wireless communication frame structure is TDD where D is DL, U is UL, and X is flexibly used between DL / UL. A UE can be configured with a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through a received slot format indicator (SFI). In the depicted example, a 10 ms frame is divided into 10 equal sized 1 ms subframes. Each subframe can include one or more slots. In some examples, each slot can include 7 or 14 symbols, depending on the slot format. A subframe can also include mini-slots, which generally have fewer symbols than a full slot. Other wireless communication technologies can have different frame structures and / or different channels.

[0080] In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerologies (μ) 0-6 allow for 1, 2, 4, 8, 16, 32, and 64 slots per subframe, respectively. For slot configuration 1, different numerologies 0-2 allow for 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and numerology μ, there are 14 symbols per slot and 2μ slots per subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing can equal kHz, where μ is a numerology 0-6. Thus, numerology has a subcarrier spacing of 15 kHz, and numerology has a subcarrier spacing of 960 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 4A , FIG. 4B , FIG. 4C and FIG. 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0081] As FIG. 4A , FIG. 4B , FIG. 4C and FIG. 4DAs illustrated in the example of FIG. 1A, a resource grid can be used to represent the frame structure. Each time slot includes resource blocks (RBs) (also referred to as physical RBs (PRBs)) that extend for the duration of the time slot in the frequency domain. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0082] As FIG. 4A illustrated in the example of FIG. 1A, some of the REs carry reference (pilot) signals (RS) for the UEs (e.g., 104). The RS can include demodulation RS (DM-RS) and / or channel state information RS (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS). FIG. 1 and FIG. 3

[0083] FIG. 4B Examples of various DL channels are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including, for example, nine RE groups (REGs), each REG including, for example, four consecutive REs in an OFDM symbol.

[0084] A primary synchronization signal (PSS) can be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., 104) to determine subframe / symbol timing and a physical layer identity. FIG. 1 and FIG. 3

[0085] A secondary synchronization signal (SSS) can be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.

[0086] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides system bandwidth configuration information and a scheduling of SI messages. The physical downlink shared channel (PDSCH) carries user

[0087] As FIG. 4C ​​As illustrated in the middle, some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE can transmit DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS can be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS can be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the particular PUCCH format used. The UE 104 can transmit a sounding reference signal (SRS). The SRS can be transmitted, for example, in the last symbol of a subframe. The SRS can have a comb structure and a UE can transmit SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling for the UL.

[0088] FIG. 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and can additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0089] Aspects Related to Monitoring PDCCH Scheduling MBS

[0090] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer readable mediums for monitoring PDCCH scheduling MBS. Some aspects relate to monitoring PDCCH scheduling broadcast of MBS, such as monitoring PDCCH scheduling broadcast of MCCH or MTCH. Some aspects relate to monitoring PDCCH scheduling multicast of MCCH or MTCH. Some aspects relate to monitoring PDCCH scheduling MBS while in RRC inactive mode.

[0091] MBS is a service that enables efficient distribution of multimedia (e.g., video, audio, and other multimedia) content to a large number of users. MBS efficiently delivers content such as video, audio, and other multimedia data to multiple recipients at the same time. MBS can be applicable to scenarios such as mobile TV, live event streaming, software updates, emergency alerts, and the like. MTCH and MCCH enable MBS. Broadcast MTCH and MCCH can be broadcast to all users within a cell or coverage area. Multicast MTCH and MCCH can be multicast to a group of users that have subscribed to the MBS multimedia content.

[0092] MTCHs can be broadcast to carry multimedia content to users. In one example, a broadcast MTCH can be a radio channel shared among all users in a particular cell or coverage area that receive the same multimedia data. MTCHs can be multicast to a particular group of users that have expressed interest in receiving the multimedia data (e.g., subscribed to a multicast group).

[0093] MCCHs are used to carry control information related to MBS services. The control information can include details about the content being broadcast in the MTCHs, scheduling information, service notifications, and other signaling. MCCHs can be broadcast to all devices within a cell or coverage area that are capable of receiving the broadcast MCCH. MCCHs can be multicast to a particular group of users that have expressed interest in receiving the multimedia data (e.g., subscribed to a multicast group).

[0094] Monitoring PDCCH scheduling broadcast MBS: In some aspects, a set of PDCCH candidates for a UE to monitor is limited according to a PDCCH search space set. The search space set can be a CSS set or a user-specific search space (USS) set. In certain systems, such as 3GPP Release 17 NR systems, blind detection of PDCCH consumes a large amount of UE power and results in UE complexity. To reduce the number of PDCCH candidates for blind detection, the maximum number of PDCCH candidates per CCE aggregation level and CCE aggregation level can be limited when monitoring PDCCH.

[0095] In certain systems, Type0B-PDCCH CSS is introduced for monitoring PDCCH scheduling broadcast MCCH and MTCH. According to certain aspects, to reduce the number of PDCCH candidates for blind detection of PDCCH scheduling MBS channels, the maximum number of PDCCH candidates per CCE aggregation level and CCE aggregation level can be limited when monitoring Type0B-PDCCH CSS. FIG. 5 is a table 500 depicting example CCE aggregation levels and maximum number of candidates per CCE aggregation level. In some aspects, a UE assumes the maximum number of CCE aggregation levels and candidates per CCE aggregation level when performing blind detection to monitor Type0 / 0B-PDCCH for broadcast MCCH and / or MTCH.

[0096] In some aspects, a control resource set (CORESET) accommodates a multiple of aggregation levels. An aggregation level indicates how many CCEs are allocated for a PDCCH. Aggregation levels include NA CCE includes a plurality of resource element groups (REGs), e.g., 6 REGs. Each REG includes a plurality of resource blocks (RBs) and OFDM symbols (e.g., 1 RB and 1 symbol per REG). In some aspects, a set of PDCCH candidates for a UE to monitor is defined according to a PDCCH search space set. The search space set can be a CSS set or a UE-specific search space (USS) set. The UE monitors PDCCH candidates in one or more of the following search space sets.

[0097] According to certain aspects, for common frequency resources (CFRs) for MBS broadcast, if a UE is not provided with searchSpaceMCCH or searchSpaceMTCH for a Type0B-PDCCH CSS set, the UE does not monitor the Type0B-PDCCH CSS set on the MBS CFR. The CCE aggregation levels for Type0B-PDCCH CSS and the number of PDCCH candidates per CCE aggregation level are given in the configured limits (e.g., table 500).

[0098] In some aspects, the parameters PDCCHConfigCommon and searchSpaceMCCH are provided in the IE searchSpaceMTCH In some aspects, the parameter searchSpaceMCCH provides an ID of a search space for MCCH. If this field is not present, the UE does not receive the MCCH in this BWP. In some aspects, the parameter searchSpaceMTCH provides an ID of a search space for MTCH for MBS broadcast. In some aspects, if this field is not present, the UE also applies searchSpaceMCCH to the MTCH.

[0099] According to certain aspects, a UE assumes a restricted set of CCE aggregation levels and number of candidates per CCE aggregation level for monitoring both a Type0B-PDCCH CSS for PDCCH scheduling MBS broadcast MCCH and a Type0B-PDCCH CSS for PDCCH scheduling MBS broadcast MTCH (e.g., the UE is configured with both searchSpaceMCCH and searchSpaceMTCH ).

[0100] According to certain aspects, a UE assumes a restricted set of CCE aggregation levels and number of candidates per CCE aggregation level for monitoring a Type0B-PDCCH CSS for PDCCH scheduling MBS broadcast MCCH (e.g., configured for searchSpaceMCCH ), but does not monitor a Type0B-PDDCH CSS for PDCCH scheduling MBS broadcast MTCH (e.g., configured for searchSpaceMTCH). Therefore, for Type0B-PDCCH CSS used for broadcast MTCH, there is no limit on the CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level.

[0101] According to certain aspects, the UE assumes a restricted set of CCE aggregation levels and the number of candidates per CCE aggregation level for monitoring Type0B-PDCCH CSS (e.g., configured for searchSpaceMTCH ) used for scheduling PDCCH for broadcast MTCH, but not for Type0B-PDDCH CSS (e.g., configured for searchSpaceMCCH ) used for scheduling PDCCH for broadcast MCCH. Therefore, for Type0B-PDCCH CSS used for scheduling PDCCH for broadcast MCCH, there is no limit on the CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level.

[0102] According to certain aspects, the UE does not assume a restricted set of CCE aggregation levels and the number of candidates per CCE aggregation level for monitoring Type0B-PDCCH CSS (e.g., configured for searchSpaceMTCH ) used for scheduling PDCCH for broadcast MTCH or Type0B-PDDCH CSS (e.g., configured for searchSpaceMCCH ) used for scheduling PDCCH for broadcast MCCH. Therefore, for Type0B-PDCCH CSS used for scheduling PDCCH for broadcast MCCH and Type0B-PDCCH CSS used for scheduling PDCCH for broadcast MTCH, there is no limit on the CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level.

[0103] According to certain aspects, a new parameter (e.g., nrofCandidates-MBS ) is provided to the UE to indicate the maximum number of PDCCH candidates for configured aggregation levels of MBS. In some aspects, the new parameter indicates the number of PDCCH candidates for DCI format 4_0 that are dedicated for configured aggregation levels. The new parameter can be provided in an SearchSpace IE that defines how and / or where to search for PDCCH candidates.

[0104] In some aspects, an RRC information element (IE) defines how and / or where to search for PDCCH candidates. Each search space is associated with one CORESET (e.g., ControlResourceSet ). For scheduled secondary cells (SCells) in cross-carrier scheduling cases, in addition to the field nrofCandidatesIn addition, all optional fields are absent (regardless of their presence conditions) except for nrofCandidates In addition, all optional fields of the search space in the scheduled SpCell are absent (regardless of their presence conditions) except for

[0105] According to certain aspects, a UE can be configured to monitor Type3-PDCCH CSS for MBS broadcast MCCH / MTCH on an SCell in RRC CONNECTED mode by unicast RRC signaling. For MBS broadcast on an SCell, the UE can assume a restricted set of CCE aggregation levels and number of candidates per CCE aggregation level for monitoring Type3-PDCCH CSS for MBS broadcast MTCH (e.g., configured for searchSpaceMTCH ) or Type3-PDDCH CSS for MBS broadcast MCCH (e.g., configured for searchSpaceMCCH ). The CCE aggregation levels and number of PDCCH candidates per CCE aggregation level for Type3-PDCCH CSS for MBS broadcast MCCH and / or MTCH on an SCell can be given in a configured limit (e.g., table 500). Alternatively, for Type3-PDCCH CSS for broadcast MCCH and Type3-PDCCH CSS for broadcast MTCH on an SCell, there is no limit on the CCE aggregation levels and number of PDCCH candidates per CCE aggregation level.

[0106] Monitoring PDCCH scheduling multicast MBS channels in RRC_INACTIVE: When a UE powers on, the UE is in a disconnected / idle mode. The UE can perform initial access or connection establishment with the network to move to RRC CONNECTED mode. The UE can transition between RRC CONNECTED mode and RRC INACTIVE mode. For example, if there is no activity from the UE for a period of time, the UE can suspend its session by moving to RRC INACTIVE mode, and can resume its session by returning to RRC CONNECTED mode. In RRC CONNECTED mode, the UE can monitor PDCCH scheduling multicast MTCH. When the UE transitions to RRC INACTIVE mode, the UE can be able to keep monitoring PDCCH scheduling multicast MTCH. In addition, for a UE in RRC INACTIVE mode, a multicast MCCH is configured, and the UE can also monitor PDCCH scheduling multicast MCCH.

[0107] In some respects, the PDCCH for scheduling multicast MTCH uses DCI format 4_1 and / or DCI format 4_2 for dynamic scheduling of multicast MTCH in RRC_INACTIVE mode. In some respects, the slot-level physical downlink shared channel (PDSCH) is reused for multicast MTCH PDSCH reception in RRC_INACTIVE mode.

[0108] In some respects, the PDCCH that schedules the multicast MCCH uses DCI format 4_0 for scheduling the multicast MCCH in RRC_INACTIVE mode.

[0109] In some respects, separate CSS is configured for the PDCCH of multicast MCCH and multicast MTCH in scheduling RRC_INACTIVE mode.

[0110] In some respects, Type0B-PDCCH CSS is used for PDCCH monitoring of multicast MCCHs in RRC_INACTIVE mode. In some respects, Type0B-PDCCH CSS with beam scanning is used for PDCCH scheduling of multicast MCCHs in RRC_INACTIVE mode. In some respects, Type0B-PDCCH CSS for monitoring and scheduling multicast MCCHs in RRC_INACTIVE mode is for... searchSpaceMCCH-Multicast Configured.

[0111] In some respects, restrictions on CCE aggregation levels and the number of candidates per CCE aggregation level are used for monitoring the PDCCH of scheduled multicast MCCHs under RRC_INACTIVE. In some respects, the UE assumes... FIG. 5 The table in Table 500 depicts the CCE aggregation levels and the number of candidates per CCE aggregation level.

[0112] In some aspects, the Type0B-PDCCH CSS is used to monitor the PDCCH scheduling multicast MTCH in RRC_INACTIVE mode. In some aspects, the Type0B-PDCCH CSS with beam scanning is used to monitor the PDCCH scheduling multicast MTCH in RRC_INACTIVE mode. In some aspects, the Type0B-PDCCH CSS for monitoring the PDCCH scheduling multicast MTCH in RRC_INACTIVE mode is targeted at... searchSpaceMTCH-Multicast Configured.

[0113] In some respects, searchSpaceMTCH_Multicast can be RRCRelease The message or SIB message is configured for multicast reception under RRC_INACTIVE. In some respects, it is used for multicast MTCH.searchSpaceMTCH_ Multicast The Type0B-PDCCH CSS for PDCCH monitoring for broadcast MTCH is configured separately from the Type0B-PDCCH CSS for monitoring PDCCH scheduling broadcast MTCH. searchSpaceMTCH The Type0B-PDCCH CSS for PDCCH monitoring for broadcast MTCH is configured separately from the Type0B-PDCCH CSS for monitoring PDCCH scheduling broadcast MTCH.

[0114] According to certain aspects, SSBs can be transmitted by the network using beam sweeping and the SSBs are mapped to MCCH or MTCH PDCCH occasions. In some aspects, the beam sweeping for Type0B-PDCCH CSS for PDCCH monitoring for multicast MTCH in RRC_INACTIVE mode is configured separately from the beam sweeping for Type0B-PDCCH CSS for monitoring PDCCH scheduling multicast MTCH in RRC_INACTIVE mode.

[0115] According to certain aspects, the multicast MTCH PDCCH occasion to SSB mapping for multicast reception in RRC_INACTIVE is configured by the MCCH message (MCCH-Message-r17) in the MCCH message (MCCH-Message-r17). In some aspects, the MCCH message is a set of RRC messages transmitted from the network to the UE on the MCCH logical channel. MCCH-Message MCCH-Message An example format of the MCCH message is shown below: -- ASN1START -- TAG-MCCH-MESSAGE-START MCCH-Message-r17 ::= SEQUENCE { message MCCH-MessageType-r17 } MCCH-MessageType-r17 ::= CHOICE { c1 CHOICE { mbsBroadcastConfiguration-r17 MBSBroadcastConfiguration-r17, spare1 NULL }, messageClassExtension SEQUENCE {} } MCCH-MessageType-Multicast-r18 ::= CHOICE { c1 CHOICE { mbsMulticastConfiguration-r18 MBSMulticastConfiguration-r18, spare1 NULL​}, messageClassExtension SEQUENCE {} In some aspects, the multicast MTCH PDCCH occasion to SSB mapping for multicast reception in RRC_INACTIVE is configured by an IE (e.g., mbs-SSB-InfoList-Multicast-r17) in the MBS multicast configuration MCCH message (e.g., MBSMulticastConfiguration-r18) as follows: mbsMulticastConfiguration-r18 In some aspects, the MBS multicast configuration message contains control information applicable to the MBS multicast service. MTCH- SSB-MappingWindowList-Multicast In some aspects, the MBS multicast configuration message contains control information applicable to the MBS multicast service. MBSMulticastConfiguration An example format of the MBS multicast configuration message is shown below: -- ASN1START -- TAG-MBSMULTICASTCONFIGURATION-START MBSMulticastConfiguration-r18 : : = SEQUENCE { criticalExtensions CHOICE { mbsMulticastConfiguration-r18 MBSMulticastConfiguration-r18-IEs, criticalExtensionsFuture SEQUENCE {} } } MBSMulticastConfiguration-r18-IEs : : = SEQUENCE { mbs-SessionInfoList-Multicast-r18 MBS-SessionInfoList-r17 OPTIONAL, -- Need R mbs-NeighbourCellList-Multicast-r18 MBS-NeighbourCellList-r17OPTIONAL, -- Need S drx-ConfigPTM-List-Multicast-r18 SEQUENCE (SIZE (1..maxNrofDRX-ConfigPTM-r17)) OF DRX-ConfigPTM-r17 OPTIONAL, -- Need R pdsch-ConfigMTCH-Multicast-r17 PDSCH-ConfigMulticast-r17 OPTIONAL, -- Need S mtch-SSB-MappingWindowList-Multicast-r18 MTCH-SSB-MappingWindow List-r17 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-MBSMULTICASTCONFIGURATION-STOP -- ASN1STOP In some aspects, the multicast MTCH PDCCH occasion to SSB mapping for multicast reception in RRC_INACTIVE is configured with a related period and offset parameters. MTCH-SSB-MappingWindowList-Multicast An example format of the IE is shown below: -- ASN1START -- TAG-MTCH-SSB-MAPPINGWINDOWLIST-START MTCH-SSB-MappingWindowList-r17 : : = SEQUENCE (SIZE (1..maxNrofMTCH-SSB-MappingWindow-r17)) OF MTCH-SSB-MappingWindowCycleOffset-r17 MTCH-SSB-MappingWindowCycleOffset-r17 : : = CHOICE { ms10 INTEGER(0..9), ms20 INTEGER(0..19), ms32 INTEGER(0..31), ms64 INTEGER(0..63), ms128 INTEGER(0..127), ms 256 INTEGER (0..255) } -- TAG-MTCH-SSB-MAPPINGWINDOWLIST-STOP -- ASN1STOP In some aspects, a parameter (e.g., periodicityAndOffset) in the IE configures parameters for multicast MTCH PDCCH occasion to SSB mapping for multicast reception in RRC_INACTIVE. MTCH-SSB-MappingWindowCycleOffset In some aspects, the values of the periodicity and offset are in units of ms. For example, ms10 corresponds to a periodicity of 10 ms with a corresponding offset between 0 ms and 9 ms, the value ms20 corresponds to a periodicity of 20 ms with a corresponding offset between 0 ms and 19 ms, for the value ms32 , ms64 , ms128 and ms256 and so on. In some aspects, the mapping window starts at a subframe of a system frame number (SFN) where [(SFN number x 10) + subframe number] modulo (periodicity) = offset.

[0116] In some aspects, PDCCH monitoring occasions for MTCH in the mapping window that do not overlap with uplink (UL) symbols (e.g., determined according to the signaled parameters tdd-UL-DL-ConfigurationCommon ) are sequentially numbered starting from 1 in the mapping window. For example, the x-th PDCCH monitoring occasion for multicast MTCH in the mapping window corresponds to the K-th transmitted SSB, where x = 0, 1, …, X-1, K = 1, 2, …, N, N is the number of actually transmitted SSBs determined according to SIB1 in ssb- PositionsInBurst X is equal to CEIL (number of PDCCH monitoring occasion to SSB mapping transmission window in MTCH / N). The actually transmitted SSBs are sequentially numbered starting from one in ascending order of their SSB index.

[0117] Monitoring PDCCH scheduling multicast MTCH in RRC_CONNECTED and RRC_INACTIVE: A UE can be capable of multicast reception in both RRC_CONNECTED mode and RRC_INACTIVE mode. In RRC_CONNECTED mode, the UE can receive a configuration for monitoring a search space for PDCCH for multicast in RRC_CONNECTED mode. In some aspects, the configuration is a signaled parameter (e.g., periodicityAndOffset) in a message (e.g., RRCReconfiguration) that includes an IE (e.g., SearchSpace). pdcch-ConfigMulticast SearchSpace ​received in a system information block (SIB).

[0118] When the UE transitions from RRC CONNECTED mode to RRC INACTIVE mode, the UE can receive a configuration for monitoring a search space for PDCCH for multicast in RRC INACTIVE mode. For example, the UE can receive a signaled parameter (e.g., searchSpaceMTCH_Multicast ) that configures a search space for monitoring PDCCH scheduling multicast MTCH in RRC INACTIVE mode. In some aspects, the signaled parameter is received in a radio resource control (RRC) release message or in a system information block (SIB).

[0119] According to certain aspects, if the signaled parameter (e.g., searchSpaceMTCH_Multicast ) that has a configuration for monitoring a search space for PDCCH for multicast in RRC INACTIVE mode is not provided in an RRC release message, but is provided in a SIB, the UE continues to monitor a search space configured for monitoring PDCCH scheduling multicast in RRC CONNECTED mode (e.g., by pdcch-ConfigMulticast the SearchSpace configuration in the IE), until a multicast MCCH change notification broadcast in the SIB is received.

[0120] According to certain aspects, if the signaled parameter (e.g., searchSpaceMTCH_Multicast ) that has a configuration for monitoring a search space for PDCCH for multicast in RRC INACTIVE mode is provided in an RRC release message, the UE continues to start monitoring a search space for PDCCH scheduling multicast provided in the RRC release message in RRC INACTIVE mode until a multicast MCCH change notification broadcast in a SIB is received.

[0121] Monitoring Type0 / 0B-PDCCH CSS for PDCCH scheduling Multicast MTCH in RRC_INACTIVE: According to certain aspects, Type0 / 0B-PDCCH CSS with beam sweeping is used for monitoring PDCCH scheduling multicast MTCH in RRC INACTIVE.

[0122] In certain systems, such as 3GPP Release 17 5G NR systems, Type0 and Type0B (e.g., sometimes denoted as Type0 / 0B) CSS supports DCI format 4_0 for broadcast MCCH and broadcast MTCH. DCI format 4_0 can include frequency domain resource assignment, time domain resource assignment (e.g., 4 bits), virtual resource block (VRB) to physical resource block (PRB) mapping (e.g., 1 bit), modulation and coding scheme (e.g., 5 bits), redundancy version (e.g., 2 bits), MCCH change notification (e.g., 2 bits), and reserved bits (e.g., 14 bits).

[0123] In some aspects, for multicast MCCH, Type0 / 0B-PDCCH CSS uses DCI format 4_0. However, according to certain aspects, Type0 / 0B-PDCCH CSS for multicast MTCH (e.g., by searchSpaceMTCH_ Multicast configuration) uses DCI format 4_1. DCI format 4_0 can include frequency domain resource assignment, time domain resource assignment (e.g., 4 bits), virtual resource block (VRB) to physical resource block (PRB) mapping (e.g., 1 bit), modulation and coding scheme (e.g., 5 bits), new data indicator (e.g., 1 bit), redundancy version (e.g., 2 bits), hybrid automatic repeat request (HARQ) process number (e.g., bits), downlink assignment index (e.g., 2 bits), physical uplink control channel (PUCCH) resource indicator (e.g., 3 bits), physical downlink shared channel (PDSCH) to HARQ feedback timing indicator (e.g., 3 bits), and reserved bits (e.g., 3 bits).

[0124] In some aspects, a UE monitors PDCCH candidates in a Type0-PDCCH CSS set on a primary cell of a master cell group (MCG). In some aspects, Type0-PDCCH is configured by parameters, parameter values of common search space #0 (e.g., searchSpaceZero where searchSpaceID = 0) for MBS multicast MCCH (e.g., for searchSpaceMCCH_Multicast ) or MBS multicast MTCH (e.g., for searchSpaceMTCH_Multicast ). In some aspects, Type0-PDCCH for MBS multicast MCCH or for MBS multicast MTCH uses DCI format 4_0 with cyclic redundancy check (CRC) scrambled by MCCH radio network temporary identity (MCCH-RNTI) or group RNTI (G-RNTI) for multicast.

[0125] In some aspects, the UE monitors PDCCH candidates in a Type0B-PDCCH CSS set. In some aspects, the Type0B-PDCCH CSS set for multicast MCCH is configured on a primary cell of the MCG for DCI format 4_0 with CRC scrambled by MCCH-RNTI for multicast (e.g., MCCH-RNTI-Multicast) (e.g., for searchSpaceMCCH_ Multicast ). In some aspects, the Type0B-PDCCH CSS set for multicast MTCH is configured on a primary cell of the MSG for DCI format 4_1 with CRC scrambled by G-RNTI for multicast (e.g., for searchSpaceMTCH_ Multicast ).

[0126] In some aspects, the RNTI used to scramble the CRC of the DCI is configured via a signaled parameter (e.g., parameter MBS-SessionInfo ).

[0127] According to certain aspects, the limits on CCE aggregation levels and number of candidates per CCE aggregation level are used for monitoring Type 0 / 0B-PDCCH CSS for PDCCH scheduling multicast MTCH in RRC_INACTIVE. In some aspects, the UE assumes FIG. 5 the CCE aggregation levels and number of candidates per CCE aggregation level in table 500 depicted in FIG. 5.

[0128] Monitoring Type3-PDCCH CSS for PDCCH scheduling Multicast MTCH in RRC_INACTIVE: In certain systems, Type3-PDCCH CSS is configured via unicast RRC signaling and QCL assumptions are determined but UEs in RRC CONNECTED mode are not beam swept. According to certain aspects, Type3-PDCCH CSS with beam sweeping can be used for monitoring PDCCH scheduling multicast MTCH in RRC_INACTIVE.

[0129] In some aspects, Type3-PDCCH CSS with beam sweeping (e.g., searchSpaceMTCH_ Multicast ) is configured by a multicast MCCH-Message-Multicast for multicast reception in RRC_INACTIVE. In some aspects, Type3-PDCCH CSS with beam sweeping for monitoring PDCCH scheduling multicast MTCH in RRC_INACTIVE is separately configured from a broadcast MTCH search space and separately configured from a multicast MCCH search space. In some aspects, the mapping of multicast MTCH PDCCH occasions to SSBs (e.g.,MTCH-SSB- MappingWindowCycleOffset_Multicast It is configured for the multicast MTCH PDCCH search space.

[0130] In some systems (such as 3GPP Release 17 5G NR systems), Type3-PDCCH CSS supports both DCI format 4_1 and DCI format 4_2 for MTCH. For multicast MTCH, if Type3-PDCCH CSS is used (e.g., for...), searchSpaceMTCH_Multicast If RRC_INACTIVE is used, the DCI format of the multicast MTCH can be restricted to only one DCI format (e.g., only DCI format 4_1). In some aspects, the UE is configured for monitoring the Type 3-PDCCH CSS set (e.g., for the MBS multicast MTCH) with DCI format 4_1 scrambled by G-RNTI for multicast. searchSpaceMTCH_Multicast ).

[0131] In some respects, restrictions on CCE aggregation levels and the number of candidates per CCE aggregation level are used to monitor Type 3-PDCCH CSS for multicast MTCH under RRC_INACTIVE. In some respects, the UE assumes... FIG. 5 The table in Table 500 depicts the CCE aggregation levels and the number of candidates per CCE aggregation level.

[0132] In some respects, restrictions on CCE aggregation levels and the number of candidates per CCE aggregation level are not applied to monitoring Type 3-PDCCH CSS for multicast MTCH under RRC_INACTIVE. In other respects, UE monitoring is unrestricted by CCE aggregation levels and the number of candidates per CCE aggregation level.

[0133] Example operations of an entity in a communication network

[0134] FIG. 6 A process flow 600 for communication in a network between network entity 602 and wireless node 604 is described. In some aspects, network entity 602 can be relative to... FIG. 1 and FIG. 3 The BS 102 depicted and described or relative to FIG. 2 An example of a decomposed base station is depicted and described. Similarly, wireless node 604 can be relative to... FIG. 1 and FIG. 3 The example of UE104 depicted and described herein. However, in other respects, wireless node 604 may be another type of wireless communication device, and network entity 602 may be another type of network entity or network node, such as those described herein.

[0135] likeFIG. 6 As shown, at step 606, wireless node 604 and network entity 602 can establish a connection (e.g., through initial attach). In some aspects, after establishing the connection at step 606, wireless node 604 is in RRC CONNECTED mode. At step 608, wireless node 604 can receive system information from the network entity. The system information can configure PDCCH search space for MBS broadcast and / or multicast MCCH and / or MBS broadcast and / or multicast MTCH. At step 610, wireless node 604 can transition to RRC INACTIVE mode.

[0136] At step 612, wireless node 604 receives system information from network entity 602. The system information can configure PDCCH search space for MCCH and / or MTCH in RRC INACTIVE mode. In some aspects, the system information configures Type0 / 0B-PDCCH CSS for multicast MCCH. In some aspects, the system information configures Type0 / 0B / 3-PDCCH CSS for multicast MCCH. In some aspects, the system information configures Type0 / 0B-PDCCH CSS for multicast MCCH of DCI format 4_0. In some aspects, the system information configures Type0 / 0B / 3-PDCCH CSS for multicast MCCH of DCI format 4_1. In some aspects, the system information configures PDCCH CSS for multicast MCCH and / or MTCH with beam sweeping in RRC INACTIVE mode. In some aspects, the system information is received in one or more RRC IEs, an RRC release message, and / or a SIB.

[0137] At step 616, wireless node 604 determines search space, CCE aggregation level, and number of candidates per CCE aggregation level to monitor PDCCH for MCCH and / or multicast MTCH in RRC INACTIVE mode. In some aspects, wireless node 604 assumes a preconfigured limited set of CCE aggregation levels and number of candidates per CCE aggregation level (e.g., as shown in table 500 as depicted in FIG. 5B) for monitoring Type0 / 0B / 3-PDCCH CSS set for MCCH and / or MTCH in RRC INACTIVE mode. FIG. 5

[0138] ​At step 618, the wireless node 604 monitors a PDCCH scheduling a MCCH and / or MTCH from the network entity 602 based on the search space, CEE aggregation level, and number of candidates per CEE aggregation level determined at step 616. In some aspects, the MCCH indicates a mapping of MBS multicast MTCH PDDCH monitoring occasions to SSBs. As shown, at step 614, the network entity 602 transmits SSBs with beam sweeping to the wireless node 604. Based on the SSBs and the configured mapping, the wireless node 604 can determine the MTCH PDDCH monitoring occasions for monitoring the PDCCH for the MBS multicast MTCH.

[0139] Example operations of a user equipment

[0140] FIG. 7 A method 700 for wireless communication by a wireless node, such as a UE 104, is shown. FIG. 1 and FIG. 3 A method 700 for wireless communication by a wireless node, such as a UE 104, is shown.

[0141] The method 700 can begin, at operation 702, with obtaining signaling indicating one or more search space (SS) parameters including at least one of: a defined set of control channel element (CCE) aggregation levels or a number of one or more physical downlink control channel (PDCCH) candidates per CCE aggregation level.

[0142] The method 700 can proceed to operation 704, with monitoring, based on the one or more SS parameters, one or more PDCCHs scheduling communications via one or more multicast broadcast service (MBS) channels.

[0143] In some aspects, the one or more MBS channels include at least one of: a MBS control channel (MCCH) or a MBS traffic channel (MTCH).

[0144] In some aspects, the monitoring at operation 704 includes monitoring a PDCCH scheduling communications via a multicast MBS control channel (MCCH), the monitoring being performed during a radio resource control (RRC) inactive mode.

[0145] In some aspects, the method 700 optionally further includes, at operation 706, obtaining at least one of: a system information block (SIB) or an RRC release message configuring a SS for PDCCH scheduling communications via a multicast MCCH.

[0146] In some aspects, the monitoring at operation 704 includes monitoring for a first downlink control information (DCI) format scheduling communications via a multicast MBS control channel (MCCH) in a Type0-PDCCH common SS (CSS) or a Type0B-PDCCH CSS.

[0147] In some aspects, the first DCI format is a DCI format 4_0.

[0148] In some aspects, the monitoring at operation 704 includes monitoring for a PDCCH scheduling communications via a multicast MBS traffic channel (MTCH), the monitoring being performed during a radio resource control (RRC) inactive mode.

[0149] In some aspects, the method 700 optionally further includes obtaining, at operation 708, an MBS control channel (MCCH), where the MCCH includes control information configuring a mapping of PDCCH monitoring occasions of the multicast MTCH to synchronization signal blocks (SSBs).

[0150] In some aspects, the method 700 optionally further includes detecting one or more of the SSBs, where the monitoring includes monitoring the PDCCH monitoring occasions of the multicast MTCH based on the mapping.

[0151] In some aspects, the method 700 optionally further includes obtaining at least one of a system information block (SIB) configuring the SSBs or an RRC release message, where the monitoring includes monitoring for a PDCCH scheduling communications via the multicast MTCH in the SSBs.

[0152] In some aspects, the method 700 optionally further includes monitoring for a PDCCH scheduling communications via the multicast MTCH in another configured SSB, the monitoring being performed during an RRC connected mode; and entering the RRC inactive mode, where an RRC release message configuring the SSBs has been obtained.

[0153] In some aspects, the method 700 optionally further includes monitoring for a PDCCH scheduling communications via the multicast MTCH in another configured SSB, the monitoring being performed during an RRC connected mode; and entering the RRC inactive mode, where the monitoring includes continuing to monitor for the PDCCH scheduling the multicast MTCH in the other SSB until a SIB is obtained.

[0154] In some aspects, the monitoring at operation 704 includes monitoring for a second downlink control information (DCI) format scheduling communications via a multicast MTCH in a Type0-PDCCH common SS (CSS) or a Type0B-PDCCH CSS.

[0155] In some aspects, the second DCI format is DCI format 4 1 or DCI format 4 2 for scheduling communications via a multicast MTCH.

[0156] In some aspects, the monitoring at operation 704 includes monitoring in a Type3-PDCCH common SS (CSS) with a third downlink control information (DCI) format for scheduling communications via a multicast MTCH.

[0157] In some aspects, the third DCI format is DCI format 4 1 for scheduling communications via a multicast MTCH.

[0158] In some aspects, the monitoring at operation 704 includes monitoring at least one of a limited set of CCE aggregation levels for PDCCHs scheduling communications via a multicast MTCH or a number of one or more PDCCH candidates per CCE aggregation level in a Type3-PDCCH CSS, the monitoring being performed during an RRC inactive mode.

[0159] In some aspects, the monitoring at operation 704 includes monitoring, in a Type3-PDCCH CSS, an unrestricted CCE aggregation level and an unrestricted number of PDCCH candidates per CCE aggregation level for PDCCHs scheduling communications via a multicast MTCH, the monitoring being performed during an RRC inactive mode.

[0160] In some aspects, the monitoring at operation 704 includes monitoring, in a TypeOB-PDCCH common SS (CSS) or a Type3-PDCCH CSS, PDCCHs scheduling communications via a broadcast MBS control channel (MCCH) and a broadcast MBS traffic channel (MTCH).

[0161] In some aspects, the monitoring at operation 704 includes monitoring at least one of a limited set of CCE aggregation levels for PDCCHs scheduling communications via one of a broadcast MTCH and a broadcast MCCH or a number of one or more PDCCH candidates per CCE aggregation level; and monitoring an unrestricted CCE aggregation level and an unrestricted number of PDCCH candidates per CCE aggregation level for PDCCHs scheduling communications via the other of the broadcast MTCH and the broadcast MCCH.

[0162] In some aspects, the monitoring at operation 704 includes monitoring at least one of a limited set of CCE aggregation levels for both PDCCHs scheduling communications via a broadcast MTCH and PDCCHs scheduling communications via a broadcast MCCH or a number of one or more PDCCH candidates per CCE aggregation level.

[0163] In some respects, monitoring at Operation 704 includes: monitoring the unrestricted CCE aggregation level or the number of unrestricted PDCCH candidates per CCE aggregation level for both the PDCCH used to schedule communications via broadcast MTCH and the PDCCH used to schedule communications via broadcast MCCH.

[0164] In some respects, during Radio Resource Control (RRC) connection mode, the PDCCH that schedules communications via the broadcast MBS channel is located on at least one of the primary cell (PCell) or secondary cell (SCell).

[0165] In one aspect, method 700 or any aspect related to the method may be made by means of a device (such as...) FIG. 9 The communication device 900 performs the operation, and the device includes various components operable to, configured to, or adapted to perform the method 700. The communication device 900 is described in more detail below.

[0166] It should be noted that FIG. 7 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0167] Example operations of a network entity

[0168] FIG. 8 It shows the method for network entities (such as FIG. 1 and FIG. 3 BS 102 or as relative to FIG. 2 The method 800 for wireless communication using a decomposed base station (discussed in this paper).

[0169] Method 800 may begin at operation 802, wherein signaling indicating one or more search space (SS) parameters is output, the one or more search space (SS) parameters including at least one of the following: a limited set of control channel element (CCE) aggregation levels or the number of one or more physical downlink control channel (PDCCH) candidates per CCE aggregation level.

[0170] Method 800 can proceed to operation 804, in which one or more PDCCHs are output based on one or more SS parameters to schedule communications via one or more multicast broadcast service (MBS) channels.

[0171] In some respects, the one or more MBS channels include at least one of the following: MBS control channel (MCCH) or MBS traffic channel (MTCH).

[0172] In some aspects, the outputting at operation 804 includes outputting a PDCCH scheduling a communication via a multicast MBS control channel (MCCH), the monitoring being performed during a radio resource control (RRC) inactive mode.

[0173] In some aspects, the method 800 optionally further includes outputting, at operation 806, at least one of: a system information block (SIB) configuring a SS for PDCCH scheduling a communication via a multicast MCCH or an RRC release message.

[0174] In some aspects, the outputting at operation 804 includes outputting a first downlink control information (DCI) format scheduling a communication via a multicast MBS control channel (MCCH) in a Type0-PDCCH common SS (CSS) or a Type0B-PDCCH CSS.

[0175] In some aspects, the first DCI format is a DCI format 4 0.

[0176] In some aspects, the outputting at operation 804 includes outputting a PDCCH scheduling a communication via a multicast MBS traffic channel (MTCH), the monitoring being performed during a radio resource control (RRC) inactive mode.

[0177] In some aspects, the method 800 optionally further includes outputting, at operation 708, an MBS control channel (MCCH), wherein the MCCH includes control information configuring a mapping of PDCCH monitoring occasions of a multicast MTCH to synchronization signal blocks (SSBs).

[0178] In some aspects, the method 800 optionally further includes outputting one or more of the SSBs, wherein the outputting includes outputting the PDCCH monitoring occasions of the multicast MTCH based on the mapping.

[0179] In some aspects, the method 800 optionally further includes outputting at least one of: a system information block (SIB) configuring a SS or an RRC release message, wherein the outputting includes outputting, in the SS, a PDCCH scheduling a communication via a multicast MTCH.

[0180] In some aspects, the method 800 optionally further includes outputting, in another configured SS, a PDCCH scheduling a communication via a multicast MTCH, the outputting being performed during an RRC connected mode; and entering an RRC inactive mode, wherein an RRC release message configuring the SS is outputted.

[0181] In some aspects, the method 800 optionally further includes outputting, in another configured SS, a PDCCH scheduling a communication via a multicast MTCH, the outputting being performed during an RRC connected mode; and entering an RRC inactive mode, wherein the outputting includes outputting, in the other SS, one or more PDCCHs scheduling a multicast MTCH until a SIB is output.

[0182] In some aspects, the outputting at operation 804 includes outputting, in a Type0-PDCCH common SS (CSS) or a Type0B-PDCCH CSS, a second downlink control information (DCI) format scheduling a communication via a multicast MTCH.

[0183] In some aspects, the second DCI format is a DCI format 4 1 or a DCI format 4 2 for scheduling a communication via a multicast MTCH.

[0184] In some aspects, the outputting at operation 804 includes outputting, in a Type3-PDCCH common SS (CSS) with a third downlink control information (DCI) format for scheduling a communication via a multicast MTCH.

[0185] In some aspects, the third DCI format is a DCI format 4 1 for scheduling a communication via a multicast MTCH.

[0186] In some aspects, the outputting at operation 804 includes outputting at least one of: a limited set of CCE aggregation levels for a PDCCH scheduling a communication via a multicast MTCH or a number of one or more PDCCH candidates per CCE aggregation level in a Type3-PDCCH CSS, the outputting being performed during an RRC inactive mode.

[0187] In some aspects, the outputting at operation 804 includes outputting, in a Type3-PDCCH CSS, an unrestricted CCE aggregation level and an unrestricted number of PDCCH candidates per CCE aggregation level for a PDCCH scheduling a communication via a multicast MTCH, the outputting being performed during an RRC inactive mode.

[0188] In some aspects, the outputting at operation 804 includes outputting, in a Type0B-PDCCH common SS (CSS) or a Type3-PDCCH CSS, a PDCCH scheduling a communication via a broadcast MBS control channel (MCCH) and a broadcast MBS traffic channel (MTCH).

[0189] In some aspects, the output at operation 804 includes outputting at least one of: a limited set of CCE aggregation levels or a number of one or more PDCCH candidates per CCE aggregation level for PDCCHs scheduling communications via one of a broadcast MTCH and a broadcast MCCH; and an unlimited CCE aggregation level and an unlimited number of PDCCH candidates per CCE aggregation level for PDCCHs scheduling communications via the other of the broadcast MTCH and the broadcast MCCH.

[0190] In some aspects, the output at operation 804 includes outputting at least one of: a limited set of CCE aggregation levels or a number of one or more PDCCH candidates per CCE aggregation level for both PDCCHs scheduling communications via a broadcast MTCH and PDCCHs scheduling communications via a broadcast MCCH.

[0191] In some aspects, the output at operation 804 includes outputting an unlimited CCE aggregation level or an unlimited number of PDCCH candidates per CCE aggregation level for both PDCCHs scheduling communications via a broadcast MTCH and PDCCHs scheduling communications via a broadcast MCCH.

[0192] In some aspects, the PDCCHs scheduling communications via the broadcast MBS channel are located on at least one of a primary cell (PCell) or a secondary cell (SCell) during a radio resource control (RRC) connected mode.

[0193] In one aspect, the method 800, or any aspect related to the method, can be performed by a device, such as the communication device 100, that includes various components that can be operable to, configured to, or adapted to perform the method 800. The communication device 900 is described in greater detail below. FIG. 10

[0194] Note that FIG. 8 The method is just one example, and other methods including fewer, additional, or alternative steps can also be consistent with the present disclosure.

[0195] Example communication device

[0196] FIG. 9 Aspects of an example communication device 900 are depicted. In some aspects, the communication device 900 is a user equipment, such as the UE 104 described above with respect to FIG. 1 and FIG. 3 the UE 104 described above with respect to

[0197] ​The communication device 900 includes a processing system 902 coupled to a transceiver 908 (e.g., a transmitter and / or receiver). The transceiver 908 is configured to transmit and receive signals for the communication device 900 via an antenna 910, such as various signals as described herein. The processing system 902 may be configured to perform processing functions of the communication device 900, including processing signals received by the communication device 900 and / or to be transmitted by the communication device.

[0198] Processing system 902 includes one or more processors 920. In various aspects, the one or more processors 920 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as relative to... FIG. 3 As described. One or more processors 920 are coupled to a computer-readable medium / memory 930 via a bus 906. In some aspects, the computer-readable medium / memory 930 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 920, cause the one or more processors 920 to perform relative to FIG. 7 The described method 700 or any aspect thereof. It should be noted that references to a processor performing the functions of the communication device 900 may include one or more processors performing those functions of the communication device 900.

[0199] In the depicted example, computer-readable medium / memory 930 stores code (e.g., executable instructions) 931 for acquisition, code 932 for monitoring, code 933 for detection, and code 934 for entry. Processing of codes 931-934 enables communication device 900 to perform actions relative to... FIG. 7 The method described 700 or any aspect thereof.

[0200] One or more processors 920 include circuitry configured to implement (e.g., execute) code stored in a computer-readable medium / memory 930, the circuitry including circuitry 921 for acquisition, circuitry 922 for monitoring, circuitry 923 for detection, and circuitry 924 for entry. Processing performed using circuitry 921-924 enables the communication device 900 to perform actions relative to… FIG. 7 The method described 700 or any aspect thereof.

[0201] The various components of the communication device 900 can provide for performing relative to FIG. 7 The described method 700 or any related components. For example, components for outputting for transmission, components for sending, or components for conveying may include... FIG. 3 The transceiver 354 and / or antenna 352 of the illustrated UE 104FIG. 9 The communication device 900 includes a transceiver 908 and an antenna 910. Components for acquiring, detecting, receiving, or monitoring may include... FIG. 3 The transceiver 354 and / or antenna 352 of the UE 104 illustrated herein FIG. 9 The communication device 900 includes circuits 921, 922, 923, a transceiver 908, and / or an antenna 910. Components for access may include... FIG. 3 The controller / processor 380 and / or UE 104 illustrated herein FIG. 9 Circuit 924 of the communication device 900 in the middle.

[0202] FIG. 10 Various aspects of the example communication device are described. In some aspects, the communication device 1000 is a network entity, such as... FIG. 1 and FIG. 3 BS 102 or relative to FIG. 2 The decomposed base station under discussion.

[0203] Communication device 1000 includes a processing system 1002 coupled to a transceiver 1008 (e.g., a transmitter and / or receiver) and / or a network interface 1012. Transceiver 1008 is configured to transmit and receive signals for communication device 1000 via antenna 1010, such as various signals as described herein. Network interface 1012 is configured to transmit and receive signals for communication device 1000 via a communication link (such as those described herein, such as relative to...). FIG. 2 The described backhaul link, midhaul link, and / or fronthaul link are used to acquire and transmit signals for the communication device 1000. The processing system 1002 can be configured to perform the processing functions of the communication device 1000, including processing signals received by the communication device 1000 and / or to be transmitted by the communication device.

[0204] Processing system 1002 includes one or more processors 1020. In various aspects, the one or more processors 1020 may represent one or more of a receive processor 338, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340, as relative to... FIG. 3 As described. One or more processors 1020 are coupled to a computer-readable medium / memory 1030 via a bus 1006. In a particular aspect, the computer-readable medium / memory 1030 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1020, cause one or more processors 1020 to perform relative to FIG. 8The described method 800 or any aspect thereof. It should be noted that references to the processor of the communication device 1000 performing the function may include one or more processors of the communication device 1000 performing that function.

[0205] In the depicted example, computer-readable medium / memory 1030 stores code (e.g., executable instructions) 1031 for output and code 1032 for input. Processing of codes 1031-1032 enables communication device 1000 to perform operations relative to... FIG. 8 The method described 800 or any aspect thereof.

[0206] One or more processors 1020 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1030, including circuitry 1021 for output and circuitry 1022 for input. Processing performed using circuitry 1021-1022 enables the communication device 1000 to perform operations relative to... FIG. 8 The method described 800 or any aspect thereof.

[0207] The various components of the communication device 1000 can provide for performing tasks such as those related to communication equipment 1000. FIG. 8 The components of the described method 800 or any aspect thereof. Components used for sending, transmitting, or outputting for transmission may include... FIG. 3 The transceiver 332 and / or antenna 334 of the illustrated BS102 FIG. 10 The communication device 1000 includes circuitry 1021, transceiver 1008, and antenna 1010. Components for receiving or acquiring data may include... FIG. 3 The transceiver 332 and / or antenna 334 of the illustrated BS 102 FIG. 10 The communication device 1000 includes a transceiver 1008 and an antenna 1010. Components for access may include... FIG. 3 The controller / processor 340 and / or UE 104 illustrated herein FIG. 9 Circuit 1022 of the communication device 900 in the middle.

[0208] Example clauses

[0209] Specific implementation examples are described in the following numbered clauses.

[0210] Clause 1: A method for wireless communication at a wireless node, the method comprising: obtaining signaling indicating one or more search space (SS) parameters, said one or more search space (SS) parameters including at least one of: a defined set of control channel element (CCE) aggregation levels or the number of one or more physical downlink control channel (PDCCH) candidates per CCE aggregation level; and monitoring one or more PDCCHs for scheduling communication via one or more multicast broadcast service (MBS) channels based on said one or more SS parameters.

[0211] Clause 2: The method described in Clause 1, wherein the one or more MBS channels include at least one of the following: MBS control channel (MCCH) or MBS traffic channel (MTCH).

[0212] Clause 3: The method according to any combination of Clauses 1 to 2, wherein the monitoring includes: monitoring the PDCCH of communications scheduled via the multicast MBS control channel (MCCH), the monitoring being performed during Radio Resource Control (RRC) inactive mode.

[0213] Clause 4: The method according to Clause 3 further includes: obtaining at least one of the following: configuring a System Information Block (SIB) or RRC Release Message of an SS for scheduling communication via the multicast MCCH using the PDCCH.

[0214] Clause 5: The method according to any combination of Clauses 1 to 4, wherein the monitoring includes: monitoring the format of the first downlink control information (DCI) that schedules communications via the multicast MBS control channel (MCCH) in the Type 0-PDCCH common SS (CSS) or Type 0B-PDCCH CSS.

[0215] Clause 6: The method described in Clause 5, wherein the first DCI format is DCI format 4_0.

[0216] Clause 7: The method according to any combination of Clauses 1 to 6, wherein the monitoring includes: monitoring the PDCCH of communications scheduled via the Multicast MBS Traffic Channel (MTCH), the monitoring being performed during Radio Resource Control (RRC) inactive mode.

[0217] Clause 8: The method according to Clause 7 further includes: obtaining the MBS control channel (MCCH), wherein the MCCH includes control information configuring the mapping of the PDCCH monitoring timing of the multicast MTCH to the synchronization signal block (SSB).

[0218] Clause 9: The method according to Clause 8 further includes: detecting one or more SSBs among the SSBs, wherein the monitoring includes: monitoring the PDCCH monitoring timing of the multicast MTCH based on the mapping.

[0219] Clause 10: The method according to any combination of Clauses 7 to 9, the method further comprising: obtaining at least one of: configuring a System Information Block (SIB) or an RRC release message of the SS, wherein the monitoring includes: monitoring the PDCCH in the SS that schedules communication via the multicast MTCH.

[0220] Clause 11: The method according to Clause 10 further comprises: monitoring the PDCCH of communication scheduled via the multicast MTCH in another configured SS, the monitoring being performed during RRC connection mode; and entering the RRC inactive mode, wherein the RRC release message configured by the SS has been obtained.

[0221] Clause 12: The method according to any combination of Clauses 10 to 11, the method further comprising: monitoring the PDCCH that schedules communication via the multicast MTCH in another configured SS, the monitoring being performed during RRC connected mode; and entering the RRC inactive mode, wherein the monitoring includes: continuing to monitor the PDCCH that schedules the multicast MTCH in the other SS until the SIB is obtained.

[0222] Clause 13: The method according to any combination of Clauses 7 to 12, wherein the monitoring includes: monitoring the second downlink control information (DCI) format that schedules communications via the multicast MTCH in the Type 0-PDCCH public SS (CSS) or Type 0B-PDCCH CSS.

[0223] Clause 14: The method according to Clause 13, wherein the second DCI format is DCI format 4_1 or DCI format 4_2 for scheduling communications via the multicast MTCH.

[0224] Clause 15: The method according to any combination of Clauses 7 to 14, wherein the monitoring includes: monitoring in a Type 3-PDCCH common SS (CSS) having a third downlink control information (DCI) format for scheduling communications via the multicast MTCH.

[0225] Clause 16: The method according to Clause 15, wherein the third DCI format is DCI format 4_1 for scheduling communications via the multicast MTCH.

[0226] Clause 17: The method according to any combination of Clauses 15 to 16, wherein the monitoring comprises: monitoring at least one of the following: the number of PDCCH candidates of the defined set of CCE aggregation levels of the PDCCH for scheduling communication via the multicast MTCH in the Type 3-PDCCH CSS, or one or more PDCCH candidates per CCE aggregation level, wherein the monitoring is performed during the RRC inactivity mode.

[0227] Clause 18: The method according to any combination of Clauses 15 to 17, wherein the monitoring comprises: monitoring in a Type 3-PDCCH CSS the unrestricted CCE aggregation level of the PDCCH for scheduling communication via the multicast MTCH and the unrestricted number of PDCCH candidates per CCE aggregation level, said monitoring being performed during said RRC inactivity mode.

[0228] Clause 19: The method according to any combination of Clauses 1 to 18, wherein the monitoring includes: monitoring the PDCCH that schedules communications via the Broadcast MBS Control Channel (MCCH) and the Broadcast MBS Traffic Channel (MTCH) in a Type 0B-PDCCH Common SS (CSS) or a Type 3-PDCCH CSS.

[0229] Clause 20: The method according to Clause 19, wherein the monitoring comprises: monitoring at least one of the following: the limited set of CCE aggregation levels of the PDCCH for scheduling communication via one of the broadcast MTCH and the broadcast MCCH, or the number of one or more PDCCH candidates per CCE aggregation level; and monitoring the unrestricted CCE aggregation levels of the PDCCH for scheduling communication via the other of the broadcast MTCH and the broadcast MCCH, and the unrestricted number of PDCCH candidates per CCE aggregation level.

[0230] Clause 21: The method according to any combination of Clauses 19 to 20, wherein the monitoring comprises: monitoring at least one of the following: the defined set of CCE aggregation levels for scheduling communication via the broadcast MTCH and scheduling communication via the broadcast MCCH, or the number of one or more PDCCH candidates per CCE aggregation level.

[0231] Clause 22: The method according to any combination of Clauses 19 to 21, wherein the monitoring comprises: monitoring the unrestricted CCE aggregation level or the unrestricted number of PDCCH candidates per CCE aggregation level for both the PDCCH used to schedule communication via the broadcast MTCH and the PDCCH used to schedule communication via the broadcast MCCH.

[0232] Clause 23: The method according to any combination of Clauses 19 to 22, wherein during Radio Resource Control (RRC) connection mode, the PDCCH that schedules communications via the broadcast MBS channel is located on at least one of the primary cell (PCell) or secondary cell (SCell).

[0233] Clause 24: A method for wireless communication at a network entity, the method comprising: outputting signaling indicating one or more search space (SS) parameters for transmission, said one or more search space (SS) parameters including at least one of: a defined set of control channel element (CCE) aggregation levels or a number of one or more physical downlink control channel (PDCCH) candidates per CCE aggregation level; and outputting one or more PDCCHs scheduling one or more multicast broadcast service (MBS) channels for transmission based on said one or more SS parameters.

[0234] Clause 25: The method described in Clause 24, wherein the one or more MBS channels include at least one of the following: MBS control channel (MCCH) or MBS traffic channel (MTCH).

[0235] Clause 26: The method according to any combination of Clauses 24 to 25, wherein the output includes: outputting the PDCCH of communications scheduled via the multicast MBS control channel (MCCH), the monitoring being performed during Radio Resource Control (RRC) inactive mode.

[0236] Clause 27: The method according to Clause 26 further comprises: outputting at least one of the following: configuring a System Information Block (SIB) or RRC Release message for the PDCCH to schedule communication via the multicast MCCH.

[0237] Clause 28: The method according to any combination of Clauses 24 to 27, wherein the output includes: outputting a first downlink control information (DCI) format in the Type 0-PDCCH common SS (CSS) or Type 0B-PDCCH CSS to schedule communications via the multicast MBS control channel (MCCH).

[0238] Clause 29: The method described in Clause 28, wherein the first DCI format is DCI format 4_0.

[0239] Clause 30: The method according to any combination of Clauses 24 to 29, wherein the output includes: outputting the PDCCH of communications scheduled via the Multicast MBS Traffic Channel (MTCH), the monitoring being performed during Radio Resource Control (RRC) inactive mode.

[0240] Clause 31: The method according to Clause 30 further includes: outputting an MBS control channel (MCCH), wherein the MCCH includes control information configuring the mapping of the PDCCH monitoring timing of the multicast MTCH to the synchronization signal block (SSB).

[0241] Clause 32: The method according to Clause 31 further includes: outputting one or more of the SSBs, wherein the output scheduling of the PDCCH via the multicast MTCH includes: outputting the PDCCH at one or more monitoring times of the multicast MTCH based on the mapping.

[0242] Clause 33: The method according to any combination of Clauses 30 to 32, the method further comprising: obtaining at least one of: configuring a System Information Block (SIB) or RRC Release Message for the SS, wherein the PDCCH for output scheduling of communication via the multicast MTCH includes: output scheduling of communication via the multicast MTCH in the SS.

[0243] Clause 34: The method according to Clause 33 further comprises: outputting a PDCCH that schedules communication via the multicast MTCH in another configured SS, the output being performed during RRC connection mode; and entering the RRC inactive mode, wherein the RRC release message configured by the SS is output.

[0244] Clause 35: The method according to any combination of Clauses 33 to 34, the method further comprising: outputting a PDCCH that schedules communication via the multicast MTCH in another configured SS, the output being performed during RRC connected mode; and entering the RRC inactive mode, wherein the output includes: outputting the PDCCH that schedules the multicast MTCH in the other SS until the SIB is output.

[0245] Clause 36: The method according to any combination of Clauses 30 to 35, wherein the output includes: outputting a second downlink control information (DCI) format in the Type 0-PDCCH common SS (CSS) or Type 0B-PDCCH CSS to schedule communications via the multicast MTCH.

[0246] Clause 37: The method according to Clause 36, wherein the second DCI format is DCI format 4_1 or DCI format 4_2 for scheduling communication via the multicast MTCH.

[0247] Clause 38: The method according to any combination of Clauses 30 to 37, wherein the output comprises: outputting in a Type 3-PDCCH common SS (CSS) having a third downlink control information (DCI) format for scheduling communications via the multicast MTCH.

[0248] Clause 39: The method according to Clause 38, wherein the third DCI format is DCI format 4_1 for scheduling communications via the multicast MTCH.

[0249] Clause 40: The method according to any combination of Clauses 38 to 39, wherein the output comprises: outputting the limited set of PDCCHs of the CCE aggregation level of the PDCCH for scheduling communication via the multicast MTCH in a Type3-PDCCH CSS, the output being performed during the RRC inactivity mode.

[0250] Clause 41: The method according to any combination of Clauses 24 to 40, wherein the output includes: one or more PDCCHs that schedule communication via the Broadcast MBS Control Channel (MCCH) and the Broadcast MBS Traffic Channel (MTCH) in a Type 0B-PDCCH Common SS (CSS) or a Type 3-PDCCH CSS.

[0251] Clause 42: The method according to Clause 41, wherein the output comprises: a PDCCH of the limited set of CCE aggregation levels for scheduling communication of the PDCCH via one of the broadcast MTCH and the broadcast MCCH; and a PDCCH of the unrestricted CCE aggregation level for scheduling communication of the PDCCH via the other of the broadcast MTCH and the broadcast MCCH.

[0252] Clause 43: The method according to any combination of Clauses 41 to 42, wherein the output comprises: a limited set of PDCCHs for outputting the CCE aggregation level of both the PDCCH for scheduling communication via the broadcast MTCH and the PDCCH for scheduling communication via the broadcast MCCH.

[0253] Clause 44: The method according to any combination of Clauses 41 to 43, wherein the output comprises: a PDCCH of an unrestricted CCE aggregation level for both the PDCCH for scheduling communication via the broadcast MTCH and the PDCCH for scheduling communication via the broadcast MCCH.

[0254] Clause 45: The method according to any combination of Clauses 41 to 44, wherein during Radio Resource Control (RRC) connection mode, the PDCCH that schedules communications via the broadcast MBS channel is located on at least one of the primary cell (PCell) or secondary cell (SCell).

[0255] Clause 46: A wireless node comprising: a memory including computer-executable instructions; and one or more processors configured to execute the executable instructions, the computer-executable instructions being capable of causing the wireless node to perform a method according to any one of Clauses 1 to 45.

[0256] Clause 47: An apparatus comprising: a component for performing the method according to any one of Clauses 1 to 45.

[0257] Clause 48: A non-transitory computer-readable medium comprising executable instructions that, when executed by one or more processors of the device, cause the device to perform the method according to any one of Clauses 1 to 45.

[0258] Clause 49: A computer program product embodied on a computer-readable storage medium, the computer program product comprising code for performing a method according to any one of Clauses 1 to 45.

[0259] Clause 50: A wireless node comprising: at least one transceiver; a memory including instructions; and one or more processors configured to execute the instructions and cause the wireless node to perform a method according to any one of Clauses 1 to 23.

[0260] Clause 50: A network entity comprising: at least one transceiver; a memory including instructions; and one or more processors configured to execute the instructions and cause the network entity to perform a method according to any one of Clauses 24 to 45.

[0261] Additional notes

[0262] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Moreover, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be embodied by one or more elements of these claims.

[0263] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0264] As used herein, "processor," "at least one processor," or "one or more processors" generally refers to a single processor configured to perform one or more operations, or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, the execution of one or more operations may be divided among different processors, but one processor may perform multiple operations, and multiple processors may collectively perform a single operation. Similarly, "memory," "at least one memory," or "one or more memory" generally refers to a single memory configured to store data and / or instructions, or multiple memories configured to collectively store data and / or instructions.

[0265] As used in this article, the phrase “at least one of the items” refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0266] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, etc. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Furthermore, "determine" can include parsing, selecting, picking, building, etc.

[0267] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0268] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. No element of any claim shall be interpreted in accordance with 35 USC §112(f) unless that element is explicitly stated using the phrase “for a component of.” All structural and functional equivalents of the elements throughout the various aspects described herein that are known to a person of ordinary skill in the art, or will later be known, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. An apparatus for wireless communication, the apparatus comprising: at least one memory including computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the apparatus to: obtain signaling indicating one or more search space (SS) parameters, the one or more search space (SS) parameters comprising at least one of: a defined set of control channel element (CCE) aggregation levels or a number of one or more physical downlink control channel (PDCCH) candidates per CCE aggregation level; and monitor one or more PDCCHs scheduling communications via one or more multicast broadcast service (MBS) channels based on the one or more SS parameters.

2. The apparatus of claim 1, wherein the one or more MBS channels comprise at least one of: an MBS control channel (MCCH) or an MBS traffic channel (MTCH).

3. The apparatus of claim 1, wherein the monitoring comprises: monitor a PDCCH scheduling communications via a multicast MBS control channel (MCCH), the monitoring being performed during a radio resource control (RRC) inactive mode.

4. The apparatus of claim 3, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to obtain at least one of: a system information block (SIB) or an RRC release message configuring an SS for the PDCCH to schedule communications via the multicast MCCH.

5. The apparatus of claim 1, wherein the monitoring comprises: monitor a first downlink control information (DCI) format scheduling communications via a multicast MBS control channel (MCCH) in a Type0-PDCCH common SS (CSS) or a Type0B-PDCCH CSS.

6. The apparatus of claim 5, wherein the first DCI format is a DCI format 4_0.

7. The apparatus of claim 1, wherein the monitoring comprises: monitor a PDCCH scheduling communications via a multicast MBS traffic channel (MTCH), the monitoring being performed during a radio resource control (RRC) inactive mode.

8. The apparatus of claim 7, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to obtain an MBS control channel (MCCH), wherein the MCCH comprises control information configuring a mapping of PDCCH monitoring occasions for the multicast MTCH to synchronization signal blocks (SSBs).

9. The apparatus of claim 8, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to detect one or more of the SSBs, wherein the monitoring comprises: monitor the PDCCH monitoring occasions for the multicast MTCH based on the mapping.

10. The apparatus of claim 7, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to obtain at least one of: a system information block (SIB) that configures the SS or a RRC release message, wherein the monitoring comprises: monitor the PDCCH scheduling communications via the multicast MTCH in the SS.

11. The apparatus of claim 10, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to: monitor a PDCCH scheduling communications via the multicast MTCH in another configured SS, the monitoring being performed during an RRC connected mode; and entering the RRC inactive mode, wherein the RRC release message configuring the SS has been obtained.

12. The apparatus of claim 10, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to: monitor a PDCCH in another SS that schedules communications via the multicast MTCH, the monitoring being performed during an RRC connected mode; and entering the RRC inactive mode, wherein the monitoring comprises: continue monitoring the PDCCH in the other SS that schedules the multicast MTCH until the SIB is obtained.

13. The apparatus of claim 7, wherein the monitoring comprises: monitor a second downlink control information (DCI) format in a TypeO-PDCCH common SS (CSS) or a TypeOB-PDCCH CSS that schedules communications via the multicast MTCH.

14. The apparatus of claim 13, wherein the second DCI format is a DCI format 4_1 or a DCI format 4_2 used to schedule communications via the multicast MTCH.

15. The apparatus of claim 7, wherein the monitoring comprises: monitoring in a Type3-PDCCH common SS (CSS) that has a third downlink control information (DCI) format used to schedule communications via the multicast MTCH.

16. The apparatus of claim 15, wherein the third DCI format is a DCI format 4_1 used to schedule communications via the multicast MTCH.

17. The apparatus of claim 15, wherein the monitoring comprises: monitor at least one of a limited set of CCE aggregation levels of PDCCH candidates or the number of one or more PDCCH candidates per CCE aggregation level of the PDCCH in a Type3-PDCCH CSS that schedules communications via the multicast MTCH, the monitoring being performed during the RRC inactive mode.

18. The apparatus of claim 15, wherein the monitoring comprises: monitor an unrestricted CCE aggregation level and an unrestricted number of PDCCH candidates per CCE aggregation level of the PDCCH in a Type3-PDCCH CSS that schedules communications via the multicast MTCH, the monitoring being performed during the RRC inactive mode.

19. The apparatus of claim 1, wherein the monitoring comprises: monitor a PDCCH in a TypeOB-PDCCH common SS (CSS) or a Type3-PDCCH CSS that schedules communications via a broadcast MBS control channel (MCCH) and a broadcast MBS traffic channel (MTCH).

20. The apparatus of claim 19, wherein the monitoring comprises: monitoring at least one of the limited set of CCE aggregation levels or the number of one or more PDCCH candidates per CCE aggregation level of the PDCCH that schedules communications via one of the broadcast MTCH and the broadcast MCCH; and monitoring an unrestricted CCE aggregation level and an unrestricted number of PDCCH candidates per CCE aggregation level of the PDCCH that schedules communications via the other of the broadcast MTCH and the broadcast MCCH.

21. The apparatus of claim 19, wherein the monitoring comprises: monitoring the defined set of control channel element (CCE) aggregation levels or the number of one or more PDCCH candidates per CCE aggregation level for both the PDCCH scheduling communications via the broadcast MTCH and the PDCCH scheduling communications via the broadcast MCCH.

22. The apparatus of claim 19, wherein the monitoring comprises: monitoring an unrestricted CCE aggregation level or an unrestricted number of PDCCH candidates per CCE aggregation level for both the PDCCH scheduling communications via the broadcast MTCH and the PDCCH scheduling communications via the broadcast MCCH.

23. The apparatus of claim 19, wherein during a radio resource control (RRC) connected mode, the PDCCH scheduling communications via the broadcast MBS channel is on at least one of a primary cell (PCell) or a secondary cell (SCell).

24. The device of claim 1, further comprising: at least one transceiver configured to receive the signaling and to receive the one or more PDCCHs, wherein the apparatus is configured as a user equipment (UE).

25. A method for wireless communication at a wireless node, comprising: obtaining signaling indicating one or more search space (SS) parameters comprising at least one of: a defined set of control channel element (CCE) aggregation levels or a number of one or more physical downlink control channel (PDCCH) candidates per CCE aggregation level; and monitoring, based on the one or more SS parameters, one or more PDCCHs scheduling communications via one or more multicast broadcast service (MBS) channels.

26. An apparatus for wireless communication, comprising: at least one memory including computer-executable instructions; and one or more processors configured to execute the computer-executable instructions and cause the apparatus to: output, for transmission, signaling indicating one or more search space (SS) parameters comprising at least one of: a defined set of control channel element (CCE) aggregation levels or a number of one or more physical downlink control channel (PDCCH) candidates per CCE aggregation level; and output, for transmission, one or more PDCCHs scheduling one or more multicast broadcast service (MBS) channels based on the one or more SS parameters.

27. The apparatus of claim 26, wherein the one or more MBS channels comprise at least one of: an MBS control channel (MCCH) or an MBS traffic channel (MTCH).

28. The apparatus of claim 26, wherein the output comprises: output a PDCCH scheduling communications via a multicast MBS control channel (MCCH), the output being performed during a radio resource control (RRC) inactive mode.

29. The apparatus of claim 28, wherein the one or more processors are further configured to execute the computer-executable instructions and cause the apparatus to: output at least one of a system information block (SIB) or an RRC release message that configures an SS for the PDCCH to schedule communications via the multicast MCCH.

30. The device of claim 26, further comprising: at least one transceiver configured to transmit the signaling and to transmit the one or more PDCCHs, wherein the apparatus is configured as a network entity.

Images